Okay, so i just followed the steps on how to unlock and root my phone and all was going well as i followed all the steps to the letter, however at the end when i tried to reboot my phone it got stuck on the LG screen and will not load up.
I found a similar post on this forum here: https://forum.xda-developers.com/lg-g7-thinq/help/g7-doesnt-boot-flashing-modified-boot-t3872445. However in their case the phone ran out of charge and they were able to get into download mode, my phone however is on full charge so will take ages to die and i cannot seem to access download mode. In the current state the phone is completly unresponsive without me being able to turn it off.
The root guide i use this this one: https://www.theandroidsoul.com/lg-g7-root/ and the .img was also sourced from the link on that site.
Idealy I'd like help to fix this issue continuing with the root, but am happy to reset the phone if that is easier and give up rooting the phone.
For me it sounds like wrong boot.img. I mean from other version of firmware than you have.
If you unlocked bootloader, then you have LMG710EM, but...
What version of firmware you have?
For most of EM variant, newest firmware is v10q, so first try to flash img for q version.
https://drive.google.com/drive/folders/1NtbfxAbYLeQNryPg0odgLa8hBgabrH3j here you have boot images by LameMonster82, and for me it works.
There are two versions of boot.img. Original, and patched. If you want to have root, then flash patched boot.img
So if you don't know which version you have, then flash boot for v10q, if it doesn't work, then v10p etc etc.
Juat plugg the usb cable in the phone.
Hold power and - down for about 8 sec. When it reboot release power. And just hold down - (vol minus). It should Boot into download mode. Timing is everything so keep.trying untill u get it.
Also flash the correct Boot img.
Related
Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.
Hello everyone,
So I am very new to the concepts of rooting and custom roms, and I know I should have done some more research before I started. But now I have gotten myself into a bit of a pickle. I have the SM-G920P (Sprint) S6 and earlier this week I managed to root the phone and use TWRP to download and flash a custom rom. I used MD5: 7c1d34f7ab066104c924fb7a960b57d0 to install Renegade and then the phone booted just fine. I made the mistake afterwords when I let the phone reboot, but I had not turned on the option for OEM so now my phone is stuck in a boot that gives me a FRM lock because of the custom binary. It will not let me get into the andriod recovery (volume up, home, and power) but I can get to the download mode. I cannot seem to get any firmware to flash onto the device because I always get a fail after NAND write. Any help or direction from here would be great, Thanks.
dinomut101 said:
Hello everyone,
So I am very new to the concepts of rooting and custom roms, and I know I should have done some more research before I started. But now I have gotten myself into a bit of a pickle. I have the SM-G920P (Sprint) S6 and earlier this week I managed to root the phone and use TWRP to download and flash a custom rom. I used MD5: 7c1d34f7ab066104c924fb7a960b57d0 to install Renegade and then the phone booted just fine. I made the mistake afterwords when I let the phone reboot, but I had not turned on the option for OEM so now my phone is stuck in a boot that gives me a FRM lock because of the custom binary. It will not let me get into the andriod recovery (volume up, home, and power) but I can get to the download mode. I cannot seem to get any firmware to flash onto the device because I always get a fail after NAND write. Any help or direction from here would be great, Thanks.
Click to expand...
Click to collapse
Hi, we'll walk you through it.
First off, use the PF4 firmware from here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Be sure to allow it to complete and it should reboot. If you continue to get NAND write errors you may need to try different ports on your PC or different cables.
Let us know when that completes for you.
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
Hi, i just recently bought a used zenfone 2. It has a really old version of lollipop android (2.13 version) and i want to upgrate to 6.0 android. Problem is i can't get into recovery mode. Everytime i download the update phone restarts, but instead of seeing recovery screen i see usb sign. The phone turns off after a while and tries again-but same usb screen. Getting into it manually i get the same usb screen. What to do? All i can guess that the phone was tried to be rooted and failed, as i found SU program.(Phone itself boots up normally as i should!)
I'm still new to these things, so please keep it as simple as possible and ask anything more you need to know.
here are two things if you think BL is already unlocked download latest TWRP and flash that. if you think BL is locked download recovery image for the same version you are currently on and flash via fastboot
sukhwant717 said:
here are two things if you think BL is already unlocked download latest TWRP and flash that. if you think BL is locked download recovery image for the same version you are currently on and flash via fastboot
Click to expand...
Click to collapse
Well that's the thing, i can't do both ways, cause holding power+volume up buttons i instantly get a usb screen. If I could enter it i wouldn't have any problems. Bootloader is locked, when i start up my phone the asus splash screen is black, not white.
IchiBan360 said:
Well that's the thing, i can't do both ways, cause holding power+volume up buttons i instantly get a usb screen. If I could enter it i wouldn't have any problems. Bootloader is locked, when i start up my phone the asus splash screen is black, not white.
Click to expand...
Click to collapse
one thing did you use xFSTK to recover your device recently? what is your model number? send me you device serial number. do not use xFSTK you may brick completely. after boot check with root checker app from app store if you are rooted. as you stated found su binary on device. and revert me back
So I've had a read through other threads on different sites and youtube videos etc.
Basically I was trying to root my phone using magisk following the video where TK roots a oneplus 5, but was switching out the software for the oneplus 3 version of twrp.
All was going well, connected phone to pc, unlocked it, copied the files across, flashed and installed twrp then when it rebooted after installing twrp it came up with an error saying that "dm-verirty" is not started in enforcing mode, and the phone wouldn't boot past that.
I relocked the OEM, as I couldn't get it to recovery mode (stock) so tried that and now I can get it into recovery mode.
It will happily go into fastboot mode, have tried reflashing stock recovery and trying to update the os via adb.
Have been looking at the Mega Unbrick Guide - but can't get my phone to show up on my pc to even begin there.
Would appreciate any and all help, plus tips for what to do after I get it back to stock as I'm still keen to root my phone but don't want to screw it up again and have to go through all of this again.
The Mega Unbrick guide is your best hope. Did you install all the drivers on your PC? Specially the Qualcomm ones? Also, make sure to press the volume up button like it says in the instructions for 40 seconds. Otherwise it doesn't show up. If all fails, try using a different PC.