My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.
Related
Hi! I've managed to brick my device (d610ar) badly, i think
the device doesn't boot normally (message "Secure booting error! Cause: boot certification verify.", and i am stuck there), can't charge it with the wall charger, and the only thing that works is download mode; but flashing a kdz with LG FlashTool (the way i went back to stock a few times) says flashing and at 2% (or 3% sometimes) it says that doesn't find the device, that i have pull out the battery to reconnect my device again and when i do that it does the same thing on a loop, asking to do it again later..
the funny thing is that it appears on device manager on windows, on com port 11 for example, but the FlashTool doesn't recognize it..
so, i can't flash any kdz and doesn't boot.. i've read around here in xda to enter fastboot to fix it, but.. can this device enter fastboot? i couldn't do it, tried adb too and couldn't make the device visible..
i, before this happened, had multirom installed, rebooted to recovery and deleted secondary roms to install in primary rom cm12.1.. there started to happen strange things when rebooted normally to configure it..
after a while trying to boot found around here in xda too that i could enter twrp recovery via hardware keys to reinstall again, so got into it and installed a flashable zip to come back to stock KitKat directly, that have worked for me before..
after that rebooted and i can't do anything else than download mode..
i kinda figured that the problem must be that multirom injected the boot sector after installing the stock flashable zip, and when i did that restored the stock aboot and abootb (these, modified carefully, allowed us to unlock bootloader and flash recoveries, etc, etc.. ; by the way, many thanks to the devs that discovered it and made the guides!)..
now i have read the instructions for flash via fastboot the stock boot.img and so pass the security verification, but i can't enter it..
so, what do you think that could be the next step? or is it really hard bricked and i should forget about it? i'm really hoping to recover it but i don't know what else to do..
sorry for the bad english, not my primary language
thanks for reading and i am hoping to hear some suggestions!
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Thank you very much!
numpea said:
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Click to expand...
Click to collapse
Thank you very much! You made me realize why wasn't working..
Because of you, i started to search threads related with the "flashtool stuck at 2%" and one of the things to look at was a txt file to see what was the problem.. there i found out that the lg FlashTool recognized my device as LGD618..
That's when i realized that i must've messed up when i flashed a lollipop flashable zip for the D618(a while ago), "converting" my cellphone on that model.. so when i connected on download mode and put the LGD610 kdz the comparison of cellphone model and binary model didn't match..
Solution was to flash LGD618 kdz, boot up normally, install towelroot, install supersu, edit a line on build.prop
from persist.multisim.config=dsds to persist.multisim.config=none
rebooted and that's it.. everything works perfectly now! i won't be doing stuff to it for a while
probably will stay stock like that, because now i will be using an OnePlus One in a few days and the G2 mini will be used by my mother, i think..
Thanks again! You saved my device for being bricked forever
i glad i could helped you :good:
I tried installing kitkat having installed lollipop and did not work, also I tried installing lollipop and nothing. Well I think this update lollipop are adding some kind of lock to disallow downgrade or upgrade by KDZ. I try other methods, unlocking bootloader, and install a aboot.img, bricked my phone. I recommend that you do not attempt to unlock the bootloader and install any system image that is not official, or may end up with a dead device.
I was going back to full stock on my 5X, and things must have give sideways... It got stuck in a bootloop (even a stock recovery FDR hangs) and now I fear it might be bricked. I had always figured that if all else fails, I could flash something in fastboot, but that's not even available.
I can get out into the fastboot/rescue mode, and my laptop sees the device plugged in, but fastboot doesn't list it as a device, so I can't issue any commands.
Are there any 'last ditch' methods that might get this thing out of the toilet?
LeoRex said:
I was going back to full stock on my 5X, and things must have give sideways... It got stuck in a bootloop (even a stock recovery FDR hangs) and now I fear it might be bricked. I had always figured that if all else fails, I could flash something in fastboot, but that's not even available.
I can get out into the fastboot/rescue mode, and my laptop sees the device plugged in, but fastboot doesn't list it as a device, so I can't issue any commands.
Are there any 'last ditch' methods that might get this thing out of the toilet?
Click to expand...
Click to collapse
These are instructions I posted for someone else with a L24 you need to adjust the files to your phone L2x
The dload/update.app works, just be patient and follow the instructions I posted.
If you need to restore to Stock B151 use this TWRP backup >> https://www.androidfilehost.com/?fid=24588232905720643
You also need this version of TWRP to restore it >> https://www.androidfilehost.com/?fid=24545070682210514
Fastboot flash TWRP.img
in TWRP go to backup and check only boot.img > make the backup
now extract the b151 backup to your PC and copy it to the phone
their will be a directory named TWRP/BACKUPS/yourserialnumber/put the backup here
Now in TWRP choose Restore choose the backup you just copied over and be sure all the boxes are checked for restore
swipe to restore
be sure B331 dload/update.app are on the sdcard
In TWRP choose Reboot / Power Off
unplug the usb
hold power + volume up + volume down
when you see the first honor screen let go of power and hold the volume buttons till the update starts (be patient it takes a while)
EMUI recovery will load and do the update when it reboots your done
Click to expand...
Click to collapse
Yeah... been here, done this already unfortunately. The update.app is on there... The process actually gets to 5% then it goes and tries to boot, and hangs. That's where I was when I tried to get twrp on there to take a look at the filesystem.
Maybe the update.app file is corrupt/not fully copied. I'll copy it back on the SD and try again tonight.
Usually a very old (stable) release is more advisable if it's Lollipop.
Are you sure you're not running a second instance of ADB? I got that once and had to check windows processes.
Changing usb cable?
LeoRex said:
Yeah... been here, done this already unfortunately. The update.app is on there... The process actually gets to 5% then it goes and tries to boot, and hangs. That's where I was when I tried to get twrp on there to take a look at the filesystem.
Maybe the update.app file is corrupt/not fully copied. I'll copy it back on the SD and try again tonight.
Click to expand...
Click to collapse
So you restored a TWRP backup of the stock System / Boot and Recovery and the Update.APP failed ?
you used the wrong update.app or the wrong backup is the only explanation, as this works 100% of the time
Other option is you have messed up partitions, usually flashed img files from different rom versions.
Well, turns out that the update.app file on the SD was corrupt. I copied it again and the stock update till took over and loaded things properly.
Second issue is a bear... My laptop NP longer can communicate with the phone via fastboot. Based on what I see, it's a driver issue on my laptop... So I gotta figure that out of I want to get TWRP back on there.
LeoRex said:
Well, turns out that the update.app file on the SD was corrupt. I copied it again and the stock update till took over and loaded things properly.
Second issue is a bear... My laptop NP longer can communicate with the phone via fastboot. Based on what I see, it's a driver issue on my laptop... So I gotta figure that out of I want to get TWRP back on there.
Click to expand...
Click to collapse
[emoji3] sorry but you aren't getting any rest are you? Once you fix something you find another thing to fix...
If you use Windows, try and make restore points occasionally so that you can revert to the last fully working point.
Also if you can, see if there's any checksum for the firmware update files. It helps a lot.
Hey guys, I'm facing an issue right now.
I had a rooted OPX with TWRP and Lolipop. I downloaded the new OOS 3.1.3 from OnePlus site, flashed it. There was an error, fixed it by updating updater-script. Flashed the zip, then just after that flashed SuperSU zip and TWRP image over recovery. I don't know why I did that but that's the order. Then I forgot to wipe Dalvik/Cache and rebooted into recovery...It stuck in OnePlus Logo screen with powered by android written at bottom. Then I tried to boot into System by pressing the power button, it got stuck in the boot animation (The new one in Marshmallow update). It just keeps rotating infinitely (I think). I have waited for about 30 minutes on that screen, no luck.
What should I do? Is there a way that fastboot mode would be recognized by my PC and I can boot into recovery via image? Or any way for factory reset? Data is all backed up, so no issue about that. Just need it to get running asap.
Please reply asap.
Thanks for reading.
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Joshwin Aranha said:
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Click to expand...
Click to collapse
Just as I mentioned, booting into recovery doesn't work. Stuck at the OnePlus Logo Screen if I do that manually.
Though I can boot into fastboot. But after doing that, when I connect the phone to the PC, fastboot devices command returns an empty line.
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Exodusche said:
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Click to expand...
Click to collapse
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
choubeyaakash77 said:
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
Click to expand...
Click to collapse
You have to use the modded SuperSU. You can find it in the many guides posted for oos3.
So I rooted my device and life was good than I made something a system app and then I deleted it. :facepalm: Next thing I know I reboot and it comes to the unable to test corruption screen and the led light keeps flashing blue. I still have TWRP. Can it be saved?
I have access to fastboot via the bootloader screen. Can I flash from there?
Edit: and I a guess as soon as you start in twrp adp is activated . So I only need the kdz?
You can try the KDZ because that's basically fool proof, but you can also try to manually flash the partition image for the one that's broken. I think that's the system partition in your case.
PleaseHelpMe12 said:
I have access to fastboot via the bootloader screen. Can I flash from there?
Edit: and I a guess as soon as you start in twrp adp is activated . So I only need the kdz?
Click to expand...
Click to collapse
You're best bet would be to put it in download mode and flash the latest kdz using LGUP or uppercut. I've always used the original LGUP but seems like most now use uppercut and seems like uppercut is probably a better choice. You will have to reflash TWRP after you get back up and running and root as well as using the kdz will replace TWRP.
Sweet. It's alive again, but I can't access bootloader via adb reboot bootloader.
Edit: nevermind. I didn't update.
Hi all,
I went ahead and rooted my Mate 10 Pro today - I unlocked my bootloader, installed TWRP and got it running pretty sweet. Then, like a tool - tried installing xposed framework and got myself into a boot loop.
I can get to fastboot, I can get into twrp - but for the life of me don't know how to get a system wipe and fresh format! I've tried flashing LineageOS - but that's stuck on a loading screen and then boot loops after about 10minutes.
What happens is I turn my phone on - see the bootloader message - if I do nothing there's a 50/50 changes Huawei's eRecovery window opens (where if i connect it to the wifi, it fails and gives me the option of reboot or shutdown) or LineageOS boot animation loops for about 10minutes before shutting down.
At this stage, I don't mind what rom i get working - i just want something working and I'm really regretting xposed (I should of googled!).
I really don't want to pay $40 usd - and am happy tinkering around, but would appreciate some solid advice on how I can use TWRP to wipe everything and start again!
I'm also a little confused as to why eRecovery is coming up at all - and why it can't download anything!!!!!
Can someone help me get a phone back?
Thanks!
Yeah, I bootlooped going with xposed too, but I have the Mate 10 (regular) and no TWRP. Can you get to TWRP and simply flash a clean ROM? If not, which I presume is the case, can you get to Fastboot? To try, when you get to the eRecovery window, use the option to shut down your phone. Then press the power button and, while holding it, plus in your USB cable (the other end which should already be attached to your computer). Then go to Mankindtw's thread for flashing ROMs (Mate 10 Flash Oreo one). Basically, you download three zip files from a russian language page with all the latest Huawei ROMs, repackage them within his utility, and then flash them from within his utility. Worked for me.
download update.zip (for your firmware) from http://pro-teammt.ru/firmware-database
Extract update.app from update.zip
Download Huawei Update Extractor (open it and go to settings and disable header check)
Open update.app in Huawei Update Extractor
Extract SYSTEM from update.app using Huawei Update Extractor.
(Not sure if Xposed modifies vendor too, so you might have to extract that as well)
Fastboot flash system system.img
See if it boots now. If not you could try extracting recovery_ramdisk and flash recovery_ramdisk.img to the recovery_ramdisk partition then factory reset from stock recovery.
If it does modify vendor you'd have to flash vendor as well.
Or you could try flashing lineage os system, flash recovery_ramdisk and factory reset from stock recovery (factory reset is needed to get aosp roms running)
If it still fails, use mankindtws HWOTA as described by rogerinnyc above. (link: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814)
Stock rom seems to be installing. TY for your help
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
ChriKn said:
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Click to expand...
Click to collapse
Install this regfix https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
However, you would probably have had problems before too when flashing twrp.
But worth a shot I guess.
Didn't see it said you tried on win 7 too.
And if it worked before on Win 10 it should work without it.
I guess you could push system.img to /data/system.img then tap Install and selectInternal storage, tap on (go up one level) in browser, now you'll be at /. Tap on /data and then on system.img. Flash to 'System Image'.
Edit: I've tested with recovery and that flashes fine from /data/.
please see below;
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Toldorn said:
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Click to expand...
Click to collapse
Boot.img is for Nougat. Oreo uses ramdisk.
Try wiping data in TWRP (Wipe - Format Data).
You can't turn off encryption in TWRP. It's controlled by /vendor/etc/*.fstab (* = kirin970 in this case). (You can temporarily turn off encryption but it re-encrypts after booting if fstab is untouched)
But removing encryption won't fix you bootlooping, and that command you used is for Full disk encryption, we use file based encryption.
You could also try flashing back stock recovery and do factory reset from there.
Edit: Oh, you're the guy who PM'd me
I've reflashed my 'system.img' as before - but im having trouble getting into factory reset menu.
all it ever does is go into e'Recovery instead, which is useless.
Also, my booting image is still a green page of pixels - rather than a huawei logo.
Hi. I have a bla-a09 and need help. can boot into twrp but will not boot.