Hi all and thanks in advance, I appreciate your help a lot!
I've got a V500 with Android 5 and tried to install TWRP on it.
The phone was rooted already, but the TWRP apk app did not work, telling "flashing failed".
I then used the dd method getting root in adb shell, and flashed TWRP 3.1.
Unfortunately TWRP recovery does not boot with the following message:
Secure booting Error!
Cause : boot certification verify
I guess, this is due to the locked bootloader. I could not unlock, as adb reboot bootloader
boots through to the regular UI.
Now additionally to this problem I got a soft UI boot loop. After showing the swirling LG animation,
it boots to UI, shows the desktop, and loops to the LG animation again.
I still can reliably use adb, and be root on the device.
Could you, please, help me flash TWRP right in this situation?
You could try installing v500-20F bootloader and twrp 3.1 with root adb. Check this links:
https://forum.xda-developers.com/showpost.php?p=62050593&postcount=2
qutorial said:
Hi all and thanks in advance, I appreciate your help a lot!
I've got a V500 with Android 5 and tried to install TWRP on it.
The phone was rooted already, but the TWRP apk app did not work, telling "flashing failed".
I then used the dd method getting root in adb shell, and flashed TWRP 3.1.
Unfortunately TWRP recovery does not boot with the following message:
Secure booting Error!
Cause : boot certification verify
I guess, this is due to the locked bootloader. I could not unlock, as adb reboot bootloader
boots through to the regular UI.
Now additionally to this problem I got a soft UI boot loop. After showing the swirling LG animation,
it boots to UI, shows the desktop, and loops to the LG animation again.
I still can reliably use adb, and be root on the device.
Could you, please, help me flash TWRP right in this situation?
Click to expand...
Click to collapse
Related
Hi at the moment i am unable to boot into recovery either by using twrp or the lgg4 power /vol down method also adb is seeing my phone as unauthorised so unable to reflash recovery that way do not know why this has come about as it has been fine im am running genysis 3.4 rom xposed addition i dropped my phone today but can,t see that having to much of an affect, also when i use the lgg4,s manual reboot to recovery method it justs restarts the phone normally where as it used to boot to twrp any guidance would be most welcome.
tye69 said:
Hi at the moment i am unable to boot into recovery either by using twrp or the lgg4 power /vol down method also adb is seeing my phone as unauthorised so unable to reflash recovery that way do not know why this has come about as it has been fine im am running genysis 3.4 rom xposed addition i dropped my phone today but can,t see that having to much of an affect, also when i use the lgg4,s manual reboot to recovery method it justs restarts the phone normally where as it used to boot to twrp any guidance would be most welcome.
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A to get expertise help on the issue.
-Vatsal
tye69 said:
Hi at the moment i am unable to boot into recovery either by using twrp or the lgg4 power /vol down method also adb is seeing my phone as unauthorised so unable to reflash recovery that way do not know why this has come about as it has been fine im am running genysis 3.4 rom xposed addition i dropped my phone today but can,t see that having to much of an affect, also when i use the lgg4,s manual reboot to recovery method it justs restarts the phone normally where as it used to boot to twrp any guidance would be most welcome.
Click to expand...
Click to collapse
If you rooted:
https://play.google.com/store/apps/details?id=com.davidjr621.rebooter
If no:
https://www.youtube.com/watch?v=mCxJ5k8vWEI
Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!
My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.
Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised
thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything
I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device
I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Thanks, Mike01680. trying now
When i go into sideload i can see the device listed on adb devices!
Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!
Hello
I tried rooting my LG H815 and it didn't go so well.
I managed to successfully unlock the bootloader following the steps on the LG developer website.
I downloaded SuperSu (UPDATE-SuperSU-v2.46.zip) and placed it in the internal storage of the phone.
Afterwards in order to root the device, I booted into TWRP with "fastboot boot twrp-3.0.2-1-h815.img".
In TWRP I flashed SuperSu. After it finished flashing I rebooted the device. After it attempted to start up again, it froze at the LG logo. I waited around 10 minutes and figured it's not successfully boot.
I removed the battery and tried to fire it up again, but it didn't get past the Logo screen again.
I managed to send "adb reboot recovery" to it, but all I get is an image of a little dead android. I guess this is because I only booted TWRP and did not flash it.
When I get it in fastboot mode, "fastboot boot twrp-3.0.2-1-h815.img" does work anymore now. I just says < waiting for any device >.
I managed to get into default recovery with power up + vol down where it prompted me to do a reset by responding Yes twice, but after it rebooted, it still got stuck on Lg logo.
If you cannot get to the recovery then follow these steps:
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGMobileDriver_WHQL_Ver_4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product-help/CT10000025-1438110404543-preinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
This shouldn't delete your data (no guarantees) but you will have to grant app permissions again and reapply any changes to system files e.g. root, viper4android, xposed ect.
If you have problems try this method instead:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If successful and you're brave enough to try again. Then make sure you actually flash TWRP. I think you are right in that you only booted TWRP .
You can follow my TWRP/root guide here: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Good luck
Thanks a lot for answering.
LG Bridge wasn't detecting my device. I don't remember if I was in download mode when I tried this, though. I might've not been.
I didn't know how to fix it and asked a friend for help. He managed to flash the h815 stock firmware through some Taiwanese/Korean flash tool (Edit: It was LGUP and he flash a kdz file with the stock firmware).
I followed a similar guide to yours when I flashed SuperSU from TWRP, except I didn't install twrp permanently after booting it from the .img file. I thought it was not possible to install twrp if the device is not rooted first.
I still kinda want to root the device since I voided my warranty by unlocking the bootloader, but I'm afraid I'll break it again if I use the same method.
Edit: Managed to successfully flash twrp. Booted into recovery again after rebooting system. I am now creating and saving a full backup with TWRP. Will try flashing SU again afterwards.
Edit2: I flashed SU after properly installing TWRP and it worked like a charm.
Hello all,
I'm working on getting my bootloader unlocked. I bought what I thought was a ULM model off Amazon, but it appears to be a Sprint PM model that's been flashed with the ULM firmware. Sadly the EDL method doesn't seem to work on this phone (either the drivers aren't correct or some other issue is preventing me from getting past the Partition Manager step) so I was trying the old method Here. The issue I'm having is that the rootedboot image allows me to boot and Magisk comes installed, but any su commands never bring up a root prompt, including adb shell.
I also goofed and hit the "Install" from the magisk app and it appears to have made the bootloader angry, as the phone will no longer boot without my manually pushing the rooted image. I also cannot get LGUP to recognize the phone anymore (saying "Unknown model" so I can't flash it back to factory with the KDZ.
I still have access to Download Mode, fastboot, and system by pushing the rootedboot image.
Any help would be appreciated.
UPDATE:
I managed to get a root shell by re-patching the rootedboot image using the updated magisk manager application!
Bootloader is now unlocked, and I'm working on installing TWRP etc
Edit:
I'm still on the v35 abl at the moment, and that may explain why booting to the twrp recovery isn't working. Not sure yet
Use universal twrp ON any pie+ rom
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
This is for Google Pixel 2 XL.
SonyXperiaSP said:
Please need urgent help. I had unlocked bootloader. While trying to update Magisk, my phone rebooted and got stuck on fastboot loop. Then while trying to flash TWRP using fastboot this "Your device is corrupted and cannot be trusted" error occured. I can't go into recovery, it just loops into this message. And my PC can't recognise the phone now at all. Please I need help. I have been trying to resolve this issue for hours now.
Click to expand...
Click to collapse
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Strephon Alkhalikoi said:
As long as you can get into the bootloader you're not dead in the water. Download the last factory image - NOT OTA image - from Google and flash it while in bootloader mode using ADB and Fastboot. That will return your device to its factory state. From there you can boot - NOT install - TWRP and install a custom ROM as well as root.
Click to expand...
Click to collapse
First of all thank you for the reply. I don't know but I left the phone alone for couple of hours and right before seeing your post got into bootloader by pressing volume down and power key. Tried to flash TWRP and as soon as it flashed I got the exact same error like last time. I will now be following your method and install factory image. "NOT install - TWRP and Install a custom ROM", so I will not be installing TWRP this time.
I will post updates on what goes and hopefully will be able to flash the factory image without errors.
Thank you very much for the help Strephon. Really, really appreciate it. I am now able to boot into the OS and hopefully installing custom rom or rooting afterwards won't be an issue, Again, thank you very much.