Develop Bugs

[Q] Persistent low battery error while using flashing tool

hi,
My phone is soft bricked and stuck at boot logo. I am trying to flash stock recovery/kdz file using flash tool but getting stuck at"low battery" error.
Could you please help how i can bypass this error? I have spend a lot of time online and tried few methods but always getting stuck at this error. I dont have any alternative phone and this is really disappointing.
I am using E988 India model.

CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets

uppon2 said:
CLICK HERE MATE. LET ME KNOW IF IT HELPS. IF NOT USE THE INSTRUCTIONS BELOW
I'm using same phone and have the same problem. I still can't flash stock with the tool but I can tell you how to get out of soft brick. Download madmacks e980 lokified TWRP recovery and also CM 11 latest version. Get in to recovery mode and go to install file (sideload) and flash the recovery first then reboot in to recovery again and sideload CM 11. When I get a definitive solution to flash stock I will let you know mate. If you have problems or don't know what I'm talking about then reply here. You well need adb installed on computer and open a new command window by holding shift and click right noise button at the same time. Make sure you perform this from the same directory as where there files are that your flashing. Once your phone prompts you to sideload type in to the command window adb sideload (the exact file name of the file you want to flash.zip) but without the brackets
Click to expand...
Click to collapse
Thank you very much for this help. I have never tried adb. Probably I shall now learn it and then try to do as you suggested. I am not particular about stock ROM. In fact I will be happy if there is stable cm ROM for this phone.
I juts bought this phone two days back. There are too many model numbers n am little scared now about choosing the right ROM. Do you mind sharing link for correct cm11 ROM please?,
Thanks again for your help!
Sent from my GT-I9500 using xda app-developers app

Unable to mount partitions after flashing TWRP on Nexus 7 (2013, WiFi, flo)

I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux

You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.

Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.

lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.

Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).

lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!

Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice

a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.

Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice

a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.

theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?

a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.

theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.

Lg g3 700 fastboot mode started when going to recovery

Hello I hope someone could help me.
I have an lg g3 D855 international version, with kit kat 4.4.2 and its the 10e version.
I've root my device in order to install new custom rooms. At first I wanted to go to android marshmallow official and wanted to do the flashing with lg flash tool, but in every computer I have, it does not working, its either stuck in 2% and then it fails, or 4% and then it fails, and I tried to erase an install the new drivers and the old ones in the computer... But I couldn't get it to work. So I decided to root my device, and install twrp recovery, so I did. First I try to install the latest version of twrp, this I did it directly from the phone via TWRP manager. It was supose to work... But when I finish installing and went to recovery.. It went to a black screen saying "[700] fastboot mode started" or sometimes "[760] fastboot mode started" to my surprise the phone is not softbrick. I removed the battery and then reboot the phone and it works... But everytime I go to recovery or tried to install a new bump recovery... Because i thought that was the problem is still the same. I tried to install a new recovery with ADB but when I put the file path in order to install it... It said it couldn't find the recovery img in the path... But it was there... And I tried, but couldn't get it to work. I have some experience with custom roms on samsung galaxy s3, but change my phone, and this lg g3 is really making me crazy.
Thank you very much in advanced.

Any updates? Im having the same exact problem (d851)

In which computer you are trying the process. Which windows is installed on computer that you are using for installing stock rom.
Which guide you are following to install stock rom. Have you unlocked your device for bump, if not follow the guide.
http://forum.xda-developers.com/lg-g3/orig-development/bump-unlock-lg-g3-twrp-d852-d852g-f400-t2900614

I am dead sure that your board is not d855.open your phone to confirm this.that is the reason your twrp is not compatible with your board.

droidrzr1610 said:
Any updates? Im having the same exact problem (d851)
Click to expand...
Click to collapse
Same problem for me.
I was using TWRP for weekly update of LineageOS 16.1 on D855 with no problem.
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App.
Then I tried to boot in Recovery mode and I got black screen with the message:
[700] fastboot mode started
I tried older version with no success installing them with ADB or TWRP App.
---------- Post added at 06:55 AM ---------- Previous post was at 06:32 AM ----------
Polex73 said:
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App..
Click to expand...
Click to collapse
I noticed the twrp-3.4.0-0-d855.img file was corrupted.
I downloaded from the https://eu.dl.twrp.me/d855/ directly to the phonr.
Problem solved

LG G4 H815 Stock Marshmallow - Can't seem to flash TWRP

So I unlocked my bootloader when running Lolipop and then flashed H81520A_00.kdz using LG UP. Now I have what I think is a stock Marshmallow with no root and no custom recovery. I've been trying to flash TWRP and all the guides say pretty much the same thing. So I use adb to boot into bootloader, then try and flash an image from the TWRP website and everything seems to go well however every time I try to boot into recovery I get the same dead droid with ! in a red triangle. I read on the TWRP website that the images I've been trying to flash require 2.8.4 but I can't find it available for download anywhere.
I've basically being going in circles and repeating pretty much the same actions over and over for hours now. I'm sure I'm making a simple newbie mistake but I can't figure it out. Any assistance would be greatly appreciated.

dave852 said:
So I unlocked my bootloader when running Lolipop and then flashed H81520A_00.kdz using LG UP. Now I have what I think is a stock Marshmallow with no root and no custom recovery. I've been trying to flash TWRP and all the guides say pretty much the same thing. So I use adb to boot into bootloader, then try and flash an image from the TWRP website and everything seems to go well however every time I try to boot into recovery I get the same dead droid with ! in a red triangle. I read on the TWRP website that the images I've been trying to flash require 2.8.4 but I can't find it available for download anywhere.
I've basically being going in circles and repeating pretty much the same actions over and over for hours now. I'm sure I'm making a simple newbie mistake but I can't figure it out. Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Ensure you have the oem unlock active (see screenshot)
When flashing twrp use the latest one available
1. Boot into bootloader
2. Use
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
3. Then copy the twrp.img to your device while in twrp
4. Flash the twrp.img with twrp to the recovery partition (choose the button at the bottom named image to show the copied image)
5. done
.
Sent from my LG-H815 using XDA Labs

Thanks for this guide. Fastboot loading the image and then flashing the image worked. It's kind of annoying how little this method is publicised although maybe the fault lies with my ability to use Google.
Anyway, thanks again, I know a post just saying that isn't useful and there's a thanks button but I am grateful for your assistance.

dave852 said:
Anyway, thanks again, I know a post just saying that isn't useful and there's a thanks button but I am grateful for your assistance.
Click to expand...
Click to collapse
Saying thanks this way is fully ok
( clicking thanks too )
Glad that I could help you out
.
Sent from my LG-H815 using XDA Labs

lg g4 bootloop after twrp and supersu

so i tried rooting my g4 h815. i followed multiple guides and got bootloader unlocked and twrp installed it however bootlooped after flashing supersu. i restarted the phone and went into recovery mode and hit yes to enter twrp it however did not go into twrp and now no longer boots... anybody got an idea how to fix this?
Anna

just_anna said:
so i tried rooting my g4 h815. i followed multiple guides and got bootloader unlocked and twrp installed it however bootlooped after flashing supersu. i restarted the phone and went into recovery mode and hit yes to enter twrp it however did not go into twrp and now no longer boots... anybody got an idea how to fix this?
Anna
Click to expand...
Click to collapse
Without knowing exactly what you have done, it is pretty well impossible to give any helpful suggestions. You will have to be more specific.
- what model of LG G4 do you have? H815, H811, H810, H812 ..... ?
- what guides did you follow?
- exactly how did you unlock your bootloader?
- what TWRP version did you install? Did you follow the installation process in the LG G4 TWRP thread?
- did you flash a custom rom, if so what one? What SUperSU version did you install?
- etc., etc.

sdembiske said:
Without knowing exactly what you have done, it is pretty well impossible to give any helpful suggestions. You will have to be more specific.
- what model of LG G4 do you have? H815, H811, H810, H812 ..... ?
- what guides did you follow?
- exactly how did you unlock your bootloader?
- what TWRP version did you install? Did you follow the installation process in the LG G4 TWRP thread?
- did you flash a custom rom, if so what one? What SUperSU version did you install?
- etc., etc.
Click to expand...
Click to collapse
i used the following quides and used the official lg method of unlocking the bootloader
https://www.youtube.com/watch?v=skmGRgfx2V8
https://www.**************/install-twrp-recovery-on-lg-g4-international-variant/
https://www.**************/how-to-root-lg-g4-h815-using-supersu/
https://forum.xda-developers.com/g4/general/discussion-unlock-root-situations-please-t3122752
and downloaded twrp and supersu from the following sites
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://dl.twrp.me/g4/twrp-2.8.6.0-h815.img.html

just_anna said:
i used the following quides and used the official lg method of unlocking the bootloader
https://www.youtube.com/watch?v=skmGRgfx2V8
https://www.**************/install-twrp-recovery-on-lg-g4-international-variant/
https://www.**************/how-to-root-lg-g4-h815-using-supersu/
https://forum.xda-developers.com/g4/general/discussion-unlock-root-situations-please-t3122752
and downloaded twrp and supersu from the following sites
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
https://dl.twrp.me/g4/twrp-2.8.6.0-h815.img.html
Click to expand...
Click to collapse
OK, so as you were able to unlock your H815 Officially(H815 Europe version?), there shouldn't be a problem there if you did everything correctly.
That leaves TWRP version and SuperSU where the problem is most likely arising from.
Wipe your Cache & Dalvik cache in TWRP if it's functioning
Then, go to the TWRP site I linked in my previous post that is specific for the LG G4 and find and download the latest preview version you require for the firmware you currently have installed (I'm presuming Marshmallow [M]?). Follow the fastboot flashing method as exactly outlined there.
Next, if you really require SuperSu* (no longer currently supported or updated and free version removed from Play Store) you want to use SuperSU v2.82.
* I would however, recommend Magisk for your root program - it is currently supported and updated frequently. Download the latest ZIP and apk versions abd install them.
** You will have to uninstall SuperSU first before installing Magisk. Download and use the program linked in this post to uninstall SuperSU before installing Magisk.
Note: Please learn to use the Thanks button (bottom right of post) when members answer your question or provide useful/helpful information - it's an XDA Courtesy and it only takes a quick click.

sdembiske said:
OK, so as you were able to unlock your H815 Officially(H815 Europe version?), there shouldn't be a problem there if you did everything correctly.
That leaves TWRP version and SuperSU where the problem is most likely arising from.
Wipe your Cache & Dalvik cache in TWRP if it's functioning
Then, go to the TWRP site I linked in my previous post that is specific for the LG G4 and find and download the latest preview version you require for the firmware you currently have installed (I'm presuming Marshmallow [M]?). Follow the fastboot flashing method as exactly outlined there.
Next, if you really require SuperSu* (no longer currently supported or updated and free version removed from Play Store) you want to use SuperSU v2.82.
* I would however, recommend Magisk for your root program - it is currently supported and updated frequently. Download the latest ZIP and apk versions abd install them.
** You will have to uninstall SuperSU first before installing Magisk. Download and use the program linked in this post to uninstall SuperSU before installing Magisk.
Note: Please learn to use the Thanks button (bottom right of post) when members answer your question or provide useful/helpful information - it's an XDA Courtesy and it only takes a quick click.
Click to expand...
Click to collapse
i indeed have the eu version of the h815 unfortunately twrp doesnt start from recovery mode and when not in recovery the phone bootloops (twrp did work before as i used it to flash supersu)

just_anna said:
i indeed have the eu version of the h815 unfortunately twrp doesnt start from recovery mode and when not in recovery the phone bootloops (twrp did work before as i used it to flash supersu)
Click to expand...
Click to collapse
Using adb, try booting into recovery mode directly using this command adb reboot recovery.
Failing that see if you can get into fastboot mode - try this command fastboot reboot recovery If that works, uninstall SuperSU with the zip in the post I referenced above and install the SuperSU version I referenced or Magisk and then try rebooting the system.
Failing that try re-installing TWRP in fastboot mode with this fastboot flash recovery (twrp.image name exactly) and then fastboot reboot recovery if successful. Then uninstall SuperSu etc.

[/IMG]
sdembiske said:
Using adb, try booting into recovery mode directly using this command adb reboot recovery.
Failing that see if you can get into fastboot mode - try this command adb reboot bootloader and then try booting into recovery mode directly using this command fastboot reboot recovery. If that works, uninstall SuperSU with the zip in the post I referenced above and install the SuperSU version I referenced or Magisk and then try rebooting the system.
Failing that try re-installing TWRP in fastboot mode with this fastboot flash recovery (twrp.image name exactly) and then fastboot reboot recovery if successful. The uninstall SuperSu etc.
Click to expand...
Click to collapse
i tried all the commands using dos/command prompt from my fastboot folder it however cant find my device[IMG="dos results"]https://flic.kr/p/2gpcL5k

just_anna said:
i tried all the commands using dos/command prompt from my fastboot folder it however cant find my device
Click to expand...
Click to collapse
Try rebooting your PC with your phone connected and then try in your adb/fastboot folder again to see if your device is recognized.

sdembiske said:
Try rebooting your PC with your phone connected and then try in your adb/fastboot folder again to see if your device is recognized.
Click to expand...
Click to collapse
unfortunately it did not recognize the device and gave me the same results

just_anna said:
unfortunately it did not recognize the device and gave me the same results
Click to expand...
Click to collapse
Try reinstalling your LG G4 USB driver (LGMobileDriver_WHQL_Ver_4.2.0) on your PC and test again.
Failing that, try using FWUL to see if you can connect to your device - refer to the LG G4 TWRP link again and see FAQ # 3 where it's suggested.
If successful, go through the above commands again in FWUL - it has adb/fastboot built-in.
If you're still having no luck, see FAQ # 2 in the LG G4 TWRP thread and see if you can connect with @steadfasterX (the TWRP thread author & recognized developer) to help you - if anybody can, he can. I'm out of suggestions as of now.