I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.
all i have now is stock recovery. whats the best way to manually install twrp
go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk
when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.
arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.
simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine
Related
All,
I'm coming from a nexus environment where I've been able to do fastboot boot twrp-2.6.3.1-ghost-4.4.img rather than fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img since I'm hoping to keep the stock recovery while installing supersu. It complains about "(bootloader) Command restricted" with the MotoX even though my bootloader is unlocked. Is this typical of Moto devices? Do I actually need to flash twrp, then supersu and then the stock recovery if that's the final result I want? FWIW, I want SU on it but I'd like to also receive future OTA updates w/o too much dorking around of at all possible.
thanks peterb
Are you using mfastboot or just regular fastboot?
I fastboot twrp no problem. I did however mfastboot the system.img . But to answer your question twrp will ask you if you want to root when you go to reboot.
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
I understand that you should flash if you want to have TWRP installed on your phone but that's not what I want. I'd like to just boot into TWRP, install the SuperSU.zip and then boot back up as normal leaving the stock recovery in place so that I will continue to get OTA updates. I get that this is likely not the norm but it's what I did with my N4 to get SuperSu so that I could update boot.prop for flashing a hybrid radio. Doing this made it easier to get the phone back to OTA ready w/o having to flash the stock recovery back.
I found a couple of posts in the N4 where the fastboot command failed and you needed to start using the "-c" command. I was wondering if this was the problem I was running into. The argument for -c is a bit cryptic so I worry that the one I found is likely N4 specific:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Basically what I'm wondering is if anyone has been able to just boot into TWRP w/o actually flashing it to the recovery partition.
If this is not possible then I'll flash TWRP, root and then flash the stock recovery back on since I did get the stock 4.4 image from Motorola.
thanks peterb
flashallthetime said:
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
Click to expand...
Click to collapse
Interested in this as well, for booting kernels. Device support has been hit-or-miss for me in the past.
And folks, he's asking about fastboot's ability to launch an image _without_ flashing. This is a somewhat esoteric/advanced use.
I'm interested in this too even though I have a locked Moto X.
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
thehockeydude44 said:
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
Click to expand...
Click to collapse
If I'm remembering right, google took the ability to boot a recovery without loading one away in 4.2. We tried to do this on the HTC 1 Google edition when we pulled its partitions to make a system dump. It failed.
OTA fails when the device is rooted, even if you have the stock recovery.
The OTA zip checks the system partition. If there is any single modification, it fails.
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Yea, this is the other way to do it. It's just a bummer if one can't use the flexibility to just boot into recovery. Note that I still seem to be able to boot into custom recovery on my Nexus 4 that's running KitKat. I'm curious about the comment about not getting an OTA with su installed. I know that with a modified build.prop and radio, the N4 wouldn't update but I could adb sideload successfully once I put build.prop back and the stock radio on. I figured the OTA would just unroot and then I'd have to do the process again.
Anyway, this was my plan B, just would have preferred to boot recovery.
peterb
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
if u want to "unroot" to take otas, u can just flash stock system
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
droiddog said:
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
Click to expand...
Click to collapse
you can take it from the the file used in rsdlite, according to you fw version
The only reason I want the stock recovery is because I think you can't remotely lock or erase your device on a custom recovery. Does anyone know anything to the contrary? Thanks.
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
ReproOne said:
I have been using "fastboot boot recovery.img" to load into TWRP after OTA updates to load SuperSU as I am only rooted using the stock ROM. However, after this recent update (2.16.651.4) that includes the WiFi Calling and Android 4.4.3, when I run the command it just causes the phone to reboot. It does not reboot into TWRP, which is my recovery.img file.
I found a Nexus thread talking about having to add a kernel command line for the Nexus after a certain version of hboot, so I am not sure if it is related.
Does anyone know how to fastboot boot now with the latest update? I would like to avoid replacing my stock recovery with TWRP and just continue to boot into it. Alternatively, is there any other way to install supersu?
Thank you,
Ben
Click to expand...
Click to collapse
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
Thank you for the reply. I thought about taking that approach, but I was really hoping someone would have an answer on why the procedure wasn't working now. My bootloader is still unlocked.
I found this as an approach someone did on the Nexus 4 for a similar issue:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Thoughts?
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
ReproOne said:
nfinitefx45:
I did just now flash TWRP into recovery, loaded SuperSU, and then flashed your recovery.img back to the phone. So thank you very much for the recovery.img.
I'd still like to know if fastboot boot can still work, and also if there is a way in the future I can get my own recovery.img (possibly back it up before taking an OTA)?
Click to expand...
Click to collapse
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Thank you for those steps. I do not have an external SD card installed, so I modified it to store the recovery.img on sdcard instead.
Now I can always fastboot flash twrp and then back to stock recovery.
Thank you again!
nfinitefx45 said:
not sure about the fastboot issue, but to backup your recovery any time just go to adb and type the following
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img
this will copy your recovery to the external sdcard
Click to expand...
Click to collapse
You would need root to do this. Not being able to use "fastboot boot" you would just be backing up the flashed recovery. Possibly towel root temp root, but I would assume it has been patched in newest update.
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
xPhantom said:
That's the stock recovery. Did you ever flash a custom recovery back on after the OTA?
Click to expand...
Click to collapse
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
neudof said:
I am s-on & unlocked but i was able to flash the stock recovery from sd card to take the ota.
Is it possible to flash twrp back in the same way?
Click to expand...
Click to collapse
Yes, after the OTA, just flash TWRP back through fastboot and then re-flash SuperSU to get root back.
nfinitefx45 said:
As a quick work around flash twrp onto the device, once done with it then flash the factory recovery back, Also check to make sure your bootloader didn't relock after update.
stock recovery from the update.
Click to expand...
Click to collapse
I just applied the update released today, and I tried to save the recovery.img file before flashing TWRP. However, it kept giving me permission denied. Do you have the recovery.img file from the update released today so I can use it for the next update?
fastboot not working
please any help on how to access fastboot on HTC one m8.
its showing black screen n fastboot mode...
wot can I do 2 annul d problem
rooting problem
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
jinal shah said:
hey i am using htc one m8, i unlocked the bootloader and the device reads as
device status modified
*unlocked*
s-on
after this i flashed twrp and cwm a couple of times but its not loading on the device but shows success in the command window, however after clicking on recovery the custom recovery does not show up, and it reboots back into the fastboot mode.
please help me
thank you
Click to expand...
Click to collapse
What's the output in the terminal when you fastboot flash recovery?
rooting problem
It doesn't show any error as such.
In the command window it shows successful.
But when I click on recovery it reboots back to fast boot.
Like for a second it shows the screen which reads 'this build is only for developers'
But then instead of opening Twrp it reboots back to fast boot.
Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.
oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Type: fastboot boot (path goes here)
You can drag and drop the twrp img into the command window. This will ensure you have the correct path
[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
mingkee said:
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Click to expand...
Click to collapse
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
joesee said:
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
Click to expand...
Click to collapse
The instruction shows how to flash recovery.img with TWRP though I have no clue how to do it.
I got that error the first time I did it, it was because of a misspelling of the command.
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Vseprz said:
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Click to expand...
Click to collapse
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
joesee said:
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
Click to expand...
Click to collapse
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Vseprz said:
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Click to expand...
Click to collapse
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
joesee said:
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
Click to expand...
Click to collapse
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
99problemz said:
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
If boot loader is unlocked you should load twrp from fastboot.
Vseprz said:
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
If boot loader is unlocked you should load twrp from fastboot.
Click to expand...
Click to collapse
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
joesee said:
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
Click to expand...
Click to collapse
I'm glad it all worked out! :good:
finding I have to re-flash with flashify each time
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
jdoebean said:
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
Click to expand...
Click to collapse
You drop the twrp file
In fastboot folder open command prompt and flash twrp first just rename it simply to recovery.img while in the fastboot folder
Type fastboot flash recovery recovery.img
Or just fastboot flash recovery.img
Then it should boot you into twrp
Once booting into twrp flash the supersu zip in your internal sd
Once you have root and reboot all you have to do is use flashify app and download twrp from the app and flash it Twrp sticks from there.
Sent from my LGMS631 using XDA Free mobile app
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.