Develop Bugs

[Q] Update messed up G-Pad

I had stock installed, rooted and twrp install, I downloaded the update and now it only boots into twrp. So i tried factory reset and restoring a backup I had, still nothing. Just now I pressed advanced wipe everything except SD Card, now I have no OS And no backup to restore.
For some reason twrp doesn't recognise any micro sd card I put in, says it cant mount them.
I can't get adb working whilst in recovery. I just want to go back to stock.
Also holding down vol down and up to get into download mode doesn't work.
Thanks for any advice.

Got it into download mode now somehow (rebooting from twrp instead of cold boot) and downloading the stock firmware from LG mobile support tool.

mike_1983 said:
Got it into download mode now somehow (rebooting from twrp instead of cold boot) and downloading the stock firmware from LG mobile support tool.
Click to expand...
Click to collapse
same problem here.. how did you get to download mode? cannot find a way..

Trunkam said:
same problem here.. how did you get to download mode? cannot find a way..
Click to expand...
Click to collapse
1. Turn off the tablet. (from twrp menu )
2. Push vol+ and vol- same time.
3. Insert usb cable.
4. Release both buttons. Now you should be in download mode.

hi mike_1983, but have you solved with this method?

Palux said:
hi mike_1983, but have you solved with this method?
Click to expand...
Click to collapse
I was in same situation. And i solved installing stock room with LG Mobile Launcher.
Go in download mode, and then follow this method: http://forum.xda-developers.com/showthread.php?t=2471370 is 100% working.

dont update the official rom if you re rooted or you have a custom recovery, they ll brick your tablet. If you have access to recovery you can install a custom rom and there is no need to go back to full stock (unless ofc you want to keep the stock rom in which case you need to flash it using the lg mobile support tool)

I think I did it by holding down vol up and vol down whilst in twrp, then pressing reboot, system (or perhaps pressing reboot system then holding them down). I'm not sure if the usb cable was plugged in or not. I tried holding down vol up and down from powered off, but it seemed to still always go into twrp.
Then you need B2CAppSetup.exe which is LGMobile Support Tool, you can then download the stock rom, it overwrites everything, like recovery and root.

Made the same mistake : said yes when the tablet proposed me to update. Booted in TWRP.
Tried to flash with support tool but it stops at 95% and tells me in german (!) to remove the battery and try again... I've tried many times (without removing the battery obviously), just the same.
And now I can't get out of the download mode. Everytime I plug the USB cable, it goes to download mode.
Any suggestion ?
EDIT :
I even tried this method : http://forum.xda-developers.com/showthread.php?t=2622777
and it stops giving me a decompression error...
Edit 2 : it finally uncomressed corectly but i'm still stucked at 95% when installing : WPARAM_UPGRADE_ERROR
EDIT 3 :
Using the method http://forum.xda-developers.com/showthread.php?t=2622777 and leaving default parameters : Korean language and country it finaly worked with the V50010A_00.kdz firmware.
My lg g pad is finally booting ! (the battery is totally drained)
Thanks to all !

Exoten said:
Made the same mistake : said yes when the tablet proposed me to update. Booted in TWRP.
Tried to flash with support tool but it stops at 95% and tells me in german (!) to remove the battery and try again... (..)
EDIT 3 :
Using the method http://forum.xda-developers.com/showthread.php?t=2622777 and leaving default parameters : Korean language and country it finaly worked with the V50010A_00.kdz firmware.
My lg g pad is finally booting ! (the battery is totally drained)
Thanks to all !
Click to expand...
Click to collapse
Many Tanks to Exoten (and others) :highfive:
Same mistake... Same errors (no standard flash / method available)... Try method from Edit 3 and ... My wife is happy again (this is her tablet)
++ No Wipe data necessary - All data (SD and internal were kept)
+ the OTA upgrade was applied, even if I selected A version of KDZ (and not B version)
- I lost the root
F'bien

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?

Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?

If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.

joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...

I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps

Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse

xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.

This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse

xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.

actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.

dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.

5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

Today's CM14 bricked my H815 (no bootloader, no fastboot, no recovery)

Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?

bestouff said:
Hi,
My H815 always suffered from this problem: http://forum.xda-developers.com/g4/help/fastboot-download-mode-problem-t3466649 - the only way I could have fastboot was from an adb shell.
Well, that was not a problem until today: CM14's nightly broke (booting just loops at the moving logo) and now I have no way to go back to fastboot. And if I try the recovery mode, I just have a blurry circle saying "erasing" for a few seconds, then a looping CM logo.
Anyone has a way out of this mess ?
Click to expand...
Click to collapse
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?

Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)

Tycoon282 said:
Same thing happened to me, tried to install, just got put straight back in to TWRP after boot. Tried installing a stock ROM, CM ROM & using LG Bridge to recover, to no avail. Help appreciated, (i'm assuming LGUP is going to come up a lot)
Click to expand...
Click to collapse
The OP has another issue pls do not hijack.

steadfasterX said:
The OP has another issue pls do not hijack.
Click to expand...
Click to collapse
Sorry, it's nearly the same issue though, CM14.1 broke phones today.

Today's update broke mine as well. Looking for solutions. Will follow your thread and progress.

Same for me. Tried download mode with lgup to flash stock which worked once - but I kind of bricked it again by trying to install cm14.1 again. Then i tried to go back to stock using lgup again, but now lgup it just crashes. The phone now goes automatically to download mode after turning it on, the progress bar stays at 0%, the phone says "633A B100" and lgup crashes after 9% "prepare dlmode" or something similar. any ideas? :/

Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.

thewild said:
Some people seem to have fixed this issue by flashing the official Cyanogenmod Recovery.
Click to expand...
Click to collapse
After flashig the CM Recovery via TWRP, i can't use the recovery anymore. If i boot into CM-Recovery the display shows "Ereasing" and start the system. After that i got a bootloop.
Is it possible to use fastboot??

You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.

thewild said:
You guys should also check CM14.1 thread because people there are talking about the same problem. The latest post says the only solution was to flash an official kdz with LGUP.
Click to expand...
Click to collapse
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.

onlyolli said:
Did that. Worked once. Then i tried to flash cm again and had the same problems, so i wanted to flash stock again... now lgup crashes at 9% and the phones goes directly to download mode after turning it on.
Click to expand...
Click to collapse
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?

thewild said:
And the two times you tried to flash CM, that was with the same recovery ?
Can you go into fastboot mode ?
Click to expand...
Click to collapse
Yes, it was with cm recovery 20161130, if i remember correctly.
Sadly now, i can not go into fastboot. The phone goes directly into download mode. My windows vm detects the phone, and tries to flash a recent kdz, but lgup crashes at 9%. The phone still shows "0%".

Oh that's bad. What about another kdz ?

thewild said:
Oh that's bad. What about another kdz ?
Click to expand...
Click to collapse
Already tried like 3-4.... Its always the same. If the tool would at least give me a little bit more information, but it just stops.

I don't know then. Some users seem to have had the same problem (stuck at 9%) : http://forum.xda-developers.com/search/forum/4233?query=lgup 9%

I had the same issue, tried several things, my final solution was:
- Start in download mode (Volumen up and then plug in cable)
- use "LG Brigde" on Mac to install stock Rom ( Software update tab in APP ) guess should also work with Windows
- Boot original android
- enable usb debug
- Start bootloader via ADB
- fastboot flash recovery to twrp 3.0.2
- Boot in recovery via power and vol down (first factory reset from stock appears but after this twrp is starting)
- install cm nighty of 1 DEC via ADB sideload
- reboot and done
In the meantime i updated to twrp 3.0.2-1., installed gapps etc. everything is now working fine again.
Hope this is also working for you.

Which version of cm14 did u download and install? Can u please post the exact version?

Mmh ... LGUP is the Windows utility right ? How do I do if I only have a Linux machine ?

steadfasterX said:
When you say you try the recovery mode how do you try to get into it? Btw do you have twrp installed?
Click to expand...
Click to collapse
I'm trying to get to it via power+down, I get to the double "do you want to factory reset ?" question, but then :
- sometimes the CM recovery just says "erasing" for a few seconds and reboots to (non-working) CM
- sometimes it just plainly boots to (non-working) CM
I used to have TWRP installed but it didn't work with CM update, so I let CM install its own recovery.

LG G4 H815 Euro - Troubles flashing stock ROM

Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...

FamousCarpet said:
Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...
Click to expand...
Click to collapse
uninstall any drive for g4 from pc and reinstall again and lgup. now reboot phone to download mode when lgup is open first check upgrade opsion and when open kdz check refurbish opsion and start. good luck

Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device

The best way to flash stock image is to use official LG Bridge app. Download it, turn off your phone, connect it to PC while holding volume up button - phone will go into download mode. Then there is option for software restore in LG Bridge but i won't tell u where exactly. If it won't work i would try on another PC. If it won't work maybe you would be able to flash stock image trough send_command but i won't help you with it.

FamousCarpet said:
Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device
Click to expand...
Click to collapse
open lgup torn off the phone press volume up insert usb cable wait to see download mode on phone release up button and see if everything go fine

Thank you a lot Avantu, the LG Bridge did the trick! I now have a factory rom!

Moto M XT1662 Hard Bricked! Blank Screen, Not charging. NEED HELP.

Long story short, my phone came from China and did not have Google Apps installed. I tried to root it with some youtube method and the boot.img file got changed, not knowing what to do next I gave it to repair shop.
They somehow managed to restore the stock rom and gave me the stock rom.zip file as well but the IMEI was removed, so after trying a few methods I realized my phone doesn't get detected in META Mode but somehow gets detected if it's turned off and connected directly. I thought should install the stock firmware again by myself.
I first tried it with Download mode only, it loaded a few files but gave some error like IMGHDR_TYPE_MISMATCHED. After that it got stuck on boot screen.
So instead of the download option in SP tool I chose Format All + Download.
The thing is my phone does not get detected in META Mode so I thought it wouldn't change anything but now the phone doesn't turn on. The screen is blank, nothing happens with phone is connected to charger.
If I connect the phone to PC, it detects a Preloader Port Android (COM 7) on device manager for a few seconds then goes off, then keeps going on and off like it's trying to boot but doesn't boot.
Please help. This phone can't be sent back to china because the warranty is possibly void as this phone has been used about 6 months and also been tried for rooting.
It still gets connected via SP Tool but gives the same error after loading a few files. Image Attached.
https://preview.ibb.co/kyJvZn/xt1662bricked.png
Any help in this regard would be much appreciated.
Thank you.

I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.

https://www.youtube.com/watch?v=jgTSbGBk1bI
I followed that and I successfully restored my lost IMEI, everything works fine now.
Hope it helps.

Tiki Thorsen said:
I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.
Click to expand...
Click to collapse
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot

earthworm82 said:
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot
Click to expand...
Click to collapse
Sadly I cannot help you since I no longer have that phone available, sorry.