Database Develop

Can't root LG-H811 20p because supersu soft bricks phone

So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.

theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.

raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?

theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing

raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse

theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse

OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...

can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update

theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.

theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"

king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.

theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!

emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)

I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.

Trying to install TWRP on my Nexus 6 - keeps reverting back to stock recover

I have tried a number of times to install TWRP (unrooted) on my Nexus 6. I am following the instructions from here
https://twrp.me/devices/motorolanexus6.html
I am noting the warnings here
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Once I issue the fastboot reboot command before the Nexus 6 shows anything on the display I press power and vol down and get into TWRP. It seems to what it's supposed to do (presumably patch the stock ROM) and then I reboot to Android.
But the next time I boot to recovery I end up with stock recovery again. I have tried this a number of times and while I can get TWRP installed it always reverts to stock recovery after the next restart.
Is there something else I have missed here in the instructions? They seem fairly clear.
Not that I think it matters but I am running 7.1.1 (flashed with the OTA image since I was not getting OTA updates)
Thanks

Instead of using the fastboot command to reboot to recovery after you have flashed TWRP do it manually. Been a while but I believe that should work.

Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.

TMG1961 said:
Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.
Click to expand...
Click to collapse
I have done that several times. This is the screen I see when TWRP is loading for the first time.
Not sure if those red messages are fatal or not
When I am in TWRP I can reboot to recovery and it gets back to TWRP but if I reboot to system and then try to enter TWRP on a reboot (holding power and volume up/down it boots into the Fastboot and when I choose Recovery mode I send up with stock recovery again.

Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.

TMG1961 said:
Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.
Click to expand...
Click to collapse
That is pretty much what I have been doing. The only difference is, the first time I did this (before I realised it wasn't working), I rebooted from adb and I did see the swipe to allow changes. But since then if I boot from abd or boot from the bootloader, I don't see the TWRP option to swipe to allow changes anymore.
I wonder if it's because the data is encrypted (standard on a N6?)

I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.

TMG1961 said:
I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.
Click to expand...
Click to collapse
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?

lchiu7 said:
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?
Click to expand...
Click to collapse
After using fastboot to flash TWRP, use the volume and power buttons​ to boot into TWRP, and allow modifications, then make a backup and reboot system. Go back to recovery and if all is well, then flash your ROM. Make sure you've got your TWRP issue fixed first though.

The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.

Depending on what your doing, typically you have to manually boot into recovery after flashing twrp (from fastboot), don't use fastboot reboot xxxx. Use the power/volume key combo to reboot. Then accept either system modification or flash a systemless root solution. This will enable custom recovery to "stick". Otherwise, stock android will overwrite recovery on boot.
The TWRP thread has discussions about this. Starting at post 1044 should help.

mrcreativity said:
The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.
Click to expand...
Click to collapse
Is your device encrypted before you flash TWRP?

Yes it is encrypted.
Anyway, I tried all the various methods and combinations but ended up going back to stock recovery. What worked was flashing SU after TWRP.
I'm running pure nexus now and enjoying it.

Rooting Problems Need Help

Hi I'm a new Android user and don't know much about it :'( I recently got my OnePlus 3T and I wanted to root it
so I followed a tutorial video from YouTube successfully unlocked bootloader and flashed twrp recovery then I tried to install SuperSU... well it installed but the device got soft bricked when I rebooted after finishing the installation and wiping cache/dalvik
then I format/factory reset everything using twrp recovery and it's working now but the device isn't rooted :'( tried to install SuperSU again and it got bricked again
Also I'm getting these messages on the startup screen-
1st one: Your device has been unlocked and can't be trusted. If you don't want to see this screen please lock your device by "fastboot oem lock" and erase user data.
2nd one: The dm-verity is not started in enforcing mode and may not work properly.
(My os version is 4.1.7)
device OP 3t A3010
plz help me :'(

The 1st and the 2nd msg that gets displayed is shown because the bootloader is unlocked..
Bootloops are common while flashing su...when I flashed super su for the first time, I got 3 or 4 random reboots and took almost 7 to 10 mins for the phone to boot up..

I would suggest using Magisk as a rooting method instead of SuperSU. If you use SuperSU then some apps can detect root and object to you being rooted and Google's SafetyNet gets triggered. Magisk solves this by trying to hide root from apps and Google so that you can use your device as if it wasnt rooted at all (but in fact is rooted). Go the the Magisk forum and download Magisk 13.3 zip from there.
I am assuming you are using OxygenOS (Oneplus's software) and not a custom ROM. Download the Open Beta or Stable build from here/
These steps will erase all the data on your phone permanently (including internal storage) so please backup anything in there.
To fix the DM verity error youll have to follow the steps outlined here
Once you have fixed that, flash oneplus recovery via fastboot which you can download here
To flash it go to fastboot mode, and cd into the folder where you downloaded it. Run the command 'fastboot flash recovery <RECOVERY_NAME>'.
Then run the command 'fastboot oem lock' to lock the bootloader. After you confirm the prompt on screen, the phone will boot into the recovery and youll see a progress bar. Once the progress completes and the screen turns off, be ready to immediately go back to fastboot mode by pressing volume up and power.
When you enter fastboot mode again, run the command 'fastboot oem unlock' and follow the same steps as before.
Once you are in fastboot mode, the phone is now in a clean state with no OS.
Follow the steps outlined on the oneplus website to flash a clean OxygenOS build (stable or open beta as per your taste)
Once the flashing is complete you have to let the phone boot up completely once. When you get to the setup screen, go through it and reach the launcher.
Now we flash TWRP recovery. Reboot to fastboot again. Flash TWRP recovery (I personally use blu_spark's twrp but you can use one of your choice). When it is done, boot into the recovery. Youll now be able to copy magisk zip into the internal sd. Do that, and flash it. Reboot.
Youll now be rooted. If you have any problems holla at me.

Redmi 4X bootloop after installing TWRP?

Hi,
I'm having a bit of trouble. I had a brand new Redmi 4X, and I was advised to install TWRP, root it, and install the Xiaomi.eu rom until LineageOS is released. I unlocked the bootloader, flashed TWRP, managed to get into it once and now I can't do it again. When TWRP loaded it asked me for a password for decryption but it let me just skip it it seems (not sure if that is the problem) but now I can't boot normally, I can't boot into recovery, but fastboot seems to work okay. How do I go about fixing this?
I've tried reflashing TWRP but I still can't get to it, and I don't really know enough about this stuff to know where I've gone wrong.
UPDATE - I think this is to do with dm-verity and having the stock kernel installed. Now it's too late to undo what I've already done, so I hope to god that someone knows how to fix this.
UPDATE - Right, the problem is solved I think. I had to do an awful lot of googling, and I'm not entirely sure what it was specifically that fixed it. But I found a guide that taught me the fastboot command "fastboot boot twrp.img" which saved the day. Even when my phone wouldn't let me into recovery, it allowed me to flash a no-verity.zip which i think is what allowed me to boot, and it allowed me to flash superSU.zip and then the ROM I was aiming for. And now I've booted into the ROM successfully and hopefully I am rooted and all is well. Plus I can access TWRP as normal now.
Any help would be greatly appreciated

Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.

brljak83 said:
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
Click to expand...
Click to collapse
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?

brokemyG2 said:
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
Click to expand...
Click to collapse
Hii
I just have been reading about this bootloop
Go over here and read all of the 6 pages..will not take much time but could help you out much
https://forum.xda-developers.com/xiaomi-redmi-4x/development/official-twrp-3-2-1-0-xiaomi-redmi-4x-t3718217

Hey, I have exactly the same problem. Latest stock rom, flashed twrp in fastboot and got into the boot loop. Nothing works. I can only enter fastboot. What exactly did you do then? What is this no-verity.zip? I can't find anything about it.

I had a problem
I unlocked bootloader then installed redwolf recovery and took a nandroid backup. After that i rebooted to system but stuck into bootloop, could not boot to recovery, could not boot into system, So the only thing worked was that i flashed fastboot rom with mi flasher. And syccessfully rebooted to system with bootloader locked and stock recovery. So, if anyone have same problem you can do the same. How do i install recovery safely again? Should i use TWRP only? Should i flash v3.1.0 with lazy flasher or v3.2 directly without lazy flasher? I don't want to stuck into bootloader again, have to get all data deleted.

TWRP Recovery keeps being overridden

Hi,
I unlocked the bootloader on my Oneplus 3T, then flashed TWRP. Unfortunately I misread and tapped on the read-only bit, and since then I am not able to boot into TWRP after the first time.
These are my steps (which I am trying over and over)
- fastboot;
- flash TWRP with fastboot flash recovery recovery.img
- disconnect the phone and shutdown
- boot into recovery with power/vol-
- twrp boots; I reboot into system
- system boots; i shut down
- boot into recovery with power/vol-
- the default recovery loads instead of TWRP.
I tried ticking and unticking the checkbox for read only under Mount in TWRP; I tried restoring the full backup. Every time it keeps going into the default recovery
from TWRP, I can shut down and boot into recovery and I'll get TWRP. I can reboot into recovery and I'll get TWRP. But as soon as I reboot into system, TWRP is gone
any ideas?

https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034

eLcTrOn said:
https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034
Click to expand...
Click to collapse
hm, ok thanks; I must have missed that bit.
I flashed TWRP again, then installed SuperSU from it. It went fine, then it prompts me to reboot. upon reboot I am using root checker and it says it's not done. I reboot into recovery and I get the default one again...
edit: nevermind, I used another zip for supersu and it worked. now it boots into twrp, many thanks.

Wouldn't it be better to use Magisk?

przemcio510 said:
Wouldn't it be better to use Magisk?
Click to expand...
Click to collapse
I flashed FreedomOS with Magisk at the end.