I'm trying to flash gsi but when I tried the command fastboot erase system I'm getting fastboot error not enough battery capacity but my phone(SM-A715F) charged 100%. Please let me know how to solve it.
I reflashed original rom and factory reset 2 times, charged phone to 100, but still shows this error battery capacity is very low
Related
My goal is to get my Moto G6 phone in Root Mode. I bought a blank phone for this purpose, so no data is at risk. After following the steps on the XDA guide, I only got so before things did not work as they described. If I reboot my phone, I get this blue Moto G6 bootscreen and the phone never boots. I can get TWRP running on the phone though. Right now, my phone is not being recognized by either adb or fastboot. The guide I've been following is at
https://forum.xda-developers.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3816569
c:\Software\MotoG6>adb shell
error: no devices/emulators found
c:\Software\MotoG6>fastboot devices
c:\Software\MotoG6>
I have the latest Moto G6 drivers installed, but I don't think they apply anymore. If I unplug and replug in the USB cable into my Windows machine, it says it does not recognize the device.
The firmware I saw on the device when it did boot was OPSS27.82-87
* I do not know how to go back to stock because it won't recognize the device enough for me to push the stock image to it. *
*** FWIW, even on step 3 of that guide, it would say the boot image was not signed or corrupt. This happened when I tried to do
fastboot flash boot <insert-boot-image-name-here>.img
someone else had that problem and the recommendation was to ignore the message and reboot to recovery.
(https://forum.xda-developers.com/moto-g4-plus/development/wip-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586/page2)
For those who would say, "Read the **** manual", bear in mind that I did read the manual. No manual said where to get the firmware information they asked for. Also, many of the image links were bad. They did not say how to handle the case where the image did not install as they said it would. Somehow these manufacturers make each phone just enough different, and each firmware is different that it's impossible to predict what a phone will say ahead of time with certainty.
When it shows no commands, press and hold the power button then tap volume up button once. Then release the power button.
If this doesn't work mostly likely needs to be sent back to the manufacturer.
I've been trying to do this for 3 days now but i can't seem to get this to work.
So the gist of it is, I have an LG G6 running Android 8.0, with a 128Gb micro-SD card, I'm running out of internal space, and apparently LG and Samsung remove the adoptable storage feature from their android versions, I found a turn around to this which was to use ADB to partition the SD drive myself, and getting it to behave as internal memory, at first I had an issue with ADB even noticing my device, which I fixed by enabling USB tethering.
Past that everything seems to be going well, do the partition and reboot my phone,(speaking of which SD card is only detected after a reboot if I physically eject it and put it back in) all looks fine as per the screenshots
https://imgur.com/a/G7OJjFJ
(I was told memory misrepresentation was normal) until I get to the migrate data option which ALWAYS crashes the settings app, on top of that when I plug my phone into my computer I can only see the default internal storage of my device without any added memory.
I've reached a dead end and would appreciate anything at this point, even alternatives if you'd recommend I do something else (rooting or other methods i don't know about). Below are the sources I followed for this process, thanks in advance and if I missed any info let me know.
https://www.xda-developers.com/install-adb-windows-macos-linux/
https://www.androidpit.com/how-to-format-microsd-cards-as-internal-storage?fbclid=IwAR1pgqf6Ti2rSf_hbiyqLl0HufPewlPCHYmfBcfEzq_XRMhKxevwwq_mk28
https://www.modaco.com/news/android/heres-how-to-configure-adoptable-storage-on-your-s7-s7-edge-r1632/
Commands i entered by order as requested:
adb shell
sm list-disks
sm partition disk:179,0 private
And yes 179,0 IS the disk name on my phone as far as i can tell
I think that after the sm partition disk there is one thing that you didnt do. That is, sm set-force-adoptable false
After this jsut restart your phone and its gonna work most prob.
When i get memory information using adb shell dumpsys meminfo it shows something called LOST RAM. I know that this equals to TOTAL - FREE RAM - USED RAM but i need to know what this really means.
Is it just a calculation error/issue ? or
Do this amount(LOST RAM) is
really lost because of some hardware or other bug?.
If this is really a bug and not a calculation error so then should i go for a device with low LOST RAM when i'm buying an android device. and should i avoid devices with high LOST RAM value. Please provide me a clear answer for this.
Lost RAM is just RAM that is unaccounted for, it will take all the processes ram usage and add them up the difference between that value and the actual amount of ram left is known as lost ram because the OS can't account for what is using it. It's software related and from what I read can be from ION debug, or drivers that allocate and track their own ram. I don't think it should play any part in your consideration when buying a new android device though.
I tried to flash the Android L Developer Preview(http://developer.android.com/preview/setup-sdk.html) onto my Nexus 5 (no custom ROM or bootloader) following the steps at https://developers.google.com/android/nexus/images. When using flash-all.bat, I ALWAYS get stuck on
erasing 'cache'...
The only thing I can do is reboot the phone by holding down the power button until it is off. Then when I boot again I see the Google logo followed by the green Droid which probably means recovery mode. Sometimes under the Droid there is a blue progress bar, just like the one that comes up when updating, but it does not show a progress but rather just indicates action. When the Droid is up I also cannot reach the phone with fastboot or adb.
I also tried reverting back to Andrid 4.4.4, but I get the same error. Nobody else seems to have this problem, they all erase their cache in a matter of seconds and then format it.
It would be really cool if anybody could help me with either reverting to Android 4.4.4 or successfully flashing Android L.
Benedikt
Is your phone with unlocked bootloader? If no, type in console:
fastboot oem unlock
After that you should to enter in bootloader, open shell and write:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Start "flash-all" script again and enjoy your Nexus.
I have (or rather had :( ) a Glass running the XE8 version of software. It did not receive any automatic updates since it was rooted (as expected).
I tried to update it to XE12 using the system image from https://developers.google.com/glass/tools-downloads/system, and now it won't boot.
I can see the screen light up for a moment when it tries to boot, but the Glass logo does not come up. Instead, it just reboots itself over and over. Sometimes the screen flashes white instead of the usual reddish-gray.
I can still boot to bootloader using the hardware method. I have tried flashing XE11 but the result is the same.
I have a couple of questions that I think could be related to the problem:
1) There is a note on the system image download page regarding a "firmware change" in XE10 that prevents installation of earlier system versions (which includes XE8). Could that be my problem? Does that refer to low-level firmware change? How is that update applied when using the OTA update mechanism and can I apply it manually?
2) There is a relatively large userdata.img file in the system image .zip, however it does not get flashed using the fastboot update method:
fastboot -w update glass_1-img-947604.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 0.5
Baseband Version.....:
Serial Number........: [device serial]
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot' (4528 KB)...
OKAY [ 0.208s]
writing 'boot'...
OKAY [ 1.670s]
sending 'recovery' (5334 KB)...
OKAY [ 0.243s]
writing 'recovery'...
OKAY [ 1.797s]
sending 'system' (485525 KB)...
OKAY [ 21.414s]
writing 'system'...
OKAY [ 64.458s]
erasing 'userdata'...
OKAY [145.384s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.002s]
erasing 'cache'...
OKAY [102.827s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.002s]
rebooting...
If I try to flash userdata.img explicitly I get the following error:
fastboot flash userdata userdata.img
sending 'userdata' (137046 KB)...
OKAY [ 6.049s]
writing 'userdata'...
FAILED (remote: : Sparsed Write)
Is the userdata image supposed to be written to the device?
3) Is there any way of getting the boot log using fastboot to determine what causes the crash?
Thanks.
UDPATE: I have flashed the XE8 image back and now the Glass is stuck on the empty battery screen despite being plugged in for a couple of hours. However I have had charging issues with this unit before, hopefully it gets resolved overnight.
UPDATE #2: Having been left to charge overnight the device was displaying the empty battery icon with a question mark when I got back to it in the morning, however after forced reboot it seems to have booted up fine into the old XE8 system. My next step will be to restore it to unrooted state and attempt to update it using the OTA update mechanism.
I have managed to get the update working.
If you are still running a pre-XE10 system, chances are that straight reflashing of the system image to a post-XE10 version is not going to work. My best guess is that it has something to do with lower level firmware that cannot be updated simply through flashing the boot/system partition.
So if you have a rooted pre-XE10 Glass, the way to get it to update to XE12 or later is to restore it to unrooted state by flashing the boot.img from an unrooted system image.
If you have already flashed a post-XE10 version and the device won't boot, make it boot to the bootloader using the hardware method as described here: Having issues seeing GLASS in Fastboot
and flash the whole system image of a pre-XE10 version.
The links to old pre-X10 images are no longer available on the Glass developers page, however the files are still there and can be located with a bit of googling.
I am not sure that restoring the oem lock after flashing the unrooted boot partition image is required, but I did that just in case:
fastboot oem lock
Reboot the Glass afterwards and it should be able to auto-update to the latest XE version. The check for updates can be triggered by plugging the USB cable in.
When the update is complete, just repeat the original rooting steps if you need it rooted.