Related
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.
I can't use my internal storage!! Cant copy anything into it!! It does show that thier is internal storage shows that its free but cant copy anything into it??? I have twrp in my phone but after a factory reset in vanished!! I rooted my phone installed than uninstalled it!!! Any help?
Next time, root and install TWRP again!
Why the hell do you need to ****ed up your phone guys? Is the stock firmware not enough for you?
I'm not sure whether he wants to copy stuff into internal storage via TWRP recovery or while the phone is booted up.
Mounting issue usually means you tried to factory reset via TWRP when it probably should of been done via unlock bootloader method.
I don't think I ever did factory reset via TWRP when upgrading from Marshmallow to Nougat + Debranding + Root.
If u are using the old (wrong) twrp recovery you are not able to use your internalstorage while booted into recovery, but it should be accesable if u boot into android.
Since there is only systemless root for our device your system partition dont get touched while rooting, but if u flash SuperSu.zip which is not specially for EMUI5 (there is a special one), you maybe tried the wrong SuperSu.zip file and you "****ed" up your SystemPartition - you need to flash the right system.img now - just use official firmware and start rooting from scratch.
What you do now?
READ
READ
READ
Flash the rollback package.
Install desired firmware.
Unlock Bootloader
Flash TWRP
Flash SuperSu.zip for EMUI5 in TWRP.
Thanks for all of you guys!!! I have just got out of this ****!!!
The problem was i was not able to copy anything into my internal storage no even install apps from play store!!! !!! But it is resolved!!! Thanks for you reply guys
I was on MUI9 Nougat 7.1.2. Unlocked my bootloader properly. Wanted to try out Google Camera. So I searched the forum, found TWRP 3.0.3 Installer. Installed the TWRP successfully. Then I thought of installing the new TWRP, so flashed TWRP 3.2.1 from the previous TWRP. When I booted back to Recovery, saw the Encryption Error. I never set any password. Got tensed. Searched the forums again for solution. Found that I have to format the data. So formatted the data, flashed LazyFlasher. Did not know what else to do, tried booting and got stuck in Bootloop. I only have Internal Storage. And have one OTG Pendrive in case it comes handy. Downloaded Dot OS 7.1.2 and tried to install it from the OTG by booting back to TWRP, failed, it said Corrupt ZIP, but the zip file was ok. So started the process again, rebooted back to TWRP, wiped everything and this time tried to flash an old MIUI9 Recovery ROM through it, it still gave the same error, Corrupt ZIP. So basically what I have left is that I can boot into TWRP and also Fastboot is working well. But dont know how to get past this Bootloop. Someone please help. Really urgent. So tensed. :crying:
do you flash miui rom in twrp or miflash? try to flash the miui rom with miflash and see if ur phone booted up or not.
Deleted
Deleted
Thanks bro. Never mind. Somehow managed to flash DotOS Nougat version through TWRP 3.0.3. Now bro please tell me one thing. I wont stay at DotOS, I dont like it, just flashed it to get through the bootloop. So now I have downloaded MIUI9 8.3.22 Developer Recovery ROM. Still having TWRP 3.0.3, BL Unlocked, ADB working, Fastboot working, USB Debugging everything taken care off. Just tell me steps to flash the Developer ROM now so that I dont go into bootloop again. Please. Thanks in advance.
ummm kinda easy actually, download the miflash software, open it, it should have the select, refresh, and flash menu. click select, and navigate to your rom file (u need to download the fastboot rom version! not the recovery version, should be easy to find in google. the format should be .tgz change it to rar, extract it, it will shows another rar extract it again, it should be folder now) that folder is your rom file. now enter fastboot mode, plug ur phone, and click refresh. it will shows some number and alphabet. if the number and alphabet appears, click flash! and wait! and ur phone will boot itself
sorry for **** english
1. Go to twrp...
2. Wipe (cache, data, dalvik/cache, system)
3. flash miui 9 dev 8.3.22
4. flash lazyflasher...
Reboot..
It will take more then 5 min to start (first boot usually take that much time)
Your phone boot normally....
If you are facing TWRP Recovery Issue then update TWRP
Link :- https://drive.google.com/drive/folders/17YW09XpEHq7xgBAriwA-mgtEG0pckop2?usp=sharing
V3.2.1-5 is latest one...
Hit thanks
From my Redmi 4X using Tapatalk VIP
I was trying to root my phone and had already unlocked by bootloader, flashed TWRP, and made a NANDroid backup. I had the Magisk zip from Magisk Manager on my SD card. I booted into TWRP using the commands
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-3.2.3-0-ali.img
and
Code:
fastboot boot twrp-3.2.3-0-ali.img
Once in TWRP, I mounted the cache, vendor and micro SD card partitions. I unmounted them immediately afterwards and then installed the Magisk zip file. The reason that I mounted and unmounted the SD card was because, based on me trying random things, it was the only way for TWRP to show the zip file. Afterwards, I rebooted the system, the "Your device has been unlocked and can't be trusted" screen came up as normal, except that where it said "bad key" before, it said "N/A". The device did not move past this screen and instead stayed at that screen. I managed to turn it off by holding the power button for far longer than normal. I then booted my phone into TWRP and restored a previous backup. Is there a potential cause for this? Is there an alternative method of rooting that I'm not aware of?
did you install the no verity boot for your variant?
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
lucror said:
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
Click to expand...
Click to collapse
Check this thread
https://forum.xda-developers.com/mo...oot-magisk-installation-t3816569/post77074751
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
lucror said:
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
Click to expand...
Click to collapse
Nope, you're overwriting the boot image when flashing no-verity so Magisk would be gone anyways.
Okay. Thank you for your help everyone. I'll try that when I get the chance.
i accidentally deleted the whole system and every other files on the device and i haven't made a backup i can only get twrp working and had tried to install various ozip files from twrp which ended up with error 7.
If you still have twrp just install the stock rom then get back to stock recovery and wipe data to format the rest of the storage and you will be back to stock.
acyg said:
If you still have twrp just install the stock rom then get back to stock recovery and wipe data to format the rest of the storage and you will be back to stock.
Click to expand...
Click to collapse
Tried installing that already but it shows up error 7 msg
Also converted the ozip to zip and changed the file to remove device names
Still doesn’t work
Did you use the chinese twrp from this thread:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
I was able to install the stock ozip just fine with it.
acyg said:
Did you use the chinese twrp from this thread:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
I was able to install the stock ozip just fine with it.
Click to expand...
Click to collapse
Worked finally
But itried locking bootloader and it caused a bootloop and now i cannot access bootloader and the device isn’t showing up in fastboot.
Why would you try to re lock the bootloader while you were trying to unbrick it. I think you seriously need to read more about what can brick the phone and plan out each step if it isn't already too late.
Locked bootloader
Stuck in the same situation at the moment, if you find a way to unbrick please let us know.