Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick
Related
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer
Hey guys,
i've got the following problem: Unlocking the bootloader, installing TWRP and other ROMs went hassle free and worked flawless until recently.
Now, after having to reflash a clean OOS 2.2.0, it says the bootloader is locked again. TWRP is still installed. When trying to unlock the phone, it just boots to TWRP (which shortly prints an error message, but its too short to read) and shows that the bootloader is still locked in fastboot.
The problem is similar to this one:
https://forums.oneplus.net/threads/opo-back-from-the-dead-story-of-a-brick.144155/
In that thread, a solution is pointed out -- namely, this one:
http://forum.xda-developers.com/showpost.php?p=54251992
The script is for OPO only, so I'm left in the rain. Do you guys know any other way out of my misery?
Rotpeter said:
Hey guys,
i've got the following problem: Unlocking the bootloader, installing TWRP and other ROMs went hassle free and worked flawless until recently.
Now, after having to reflash a clean OOS 2.2.0, it says the bootloader is locked again. TWRP is still installed. When trying to unlock the phone, it just boots to TWRP (which shortly prints an error message, but its too short to read) and shows that the bootloader is still locked in fastboot.
The problem is similar to this one:
https://forums.oneplus.net/threads/opo-back-from-the-dead-story-of-a-brick.144155/
In that thread, a solution is pointed out -- namely, this one:
http://forum.xda-developers.com/showpost.php?p=54251992
The script is for OPO only, so I'm left in the rain. Do you guys know any other way out of my misery?
Click to expand...
Click to collapse
Install stock recovery and unlock bootloader again...
I'll give it a try. Would you point me in the direction of where to find the recovery.img for that?
EDIT: Phew, did it. Your way worked. I can't even count anymore how often I wiped and reflashed the whole thing in the last 24 hours...
I have exactly the same problem. I have the stock recovery file. Can i just flash it with TWRP ? and stock recovery will be loaded? because i can't use fastboot to load i because its locked
reboot into twrp
copy Stock_recovery.img to device folder
go to install
at the bottom select install image
select stock_recovery.img
reboot into fastboot
in cmd type fastboot oem unlock
reboot into stock recovery
wipe data/cache
format data
install from usb
go to cmd again
sideload oxygen zip instalation
in cmd write adb sideload drag and drop oxygenos.zip
reboot
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing - stock recovery
s3r3tin said:
reboot into twrp
copy Stock_recovery.img to device folder
go to install
at the bottom select install image
select stock_recovery.img
reboot into fastboot
in cmd type fastboot oem unlock
reboot into stock recovery
wipe data/cache
format data
install from usb
go to cmd again
sideload oxygen zip instalation
in cmd write adb sideload drag and drop oxygenos.zip
reboot
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing - stock recovery
Click to expand...
Click to collapse
Thanks man, you saved my life <3
Hello, fellow Android hackers.
Short: I am trying to install CM on a L21, but fail booting into TWRP (getting only stock recovery).
What I did, working with a brand-new phone:
Unlock bootloader.
Flash TWRP 3.0.2.
Boot to TWRP. It worked.
Try flashing CM, which failed due to some failed assert. Googling revealed a thread on these forums which suggested I had to do a stock update to Marshmallow first.
Downloaded the update through EMUI's updater.
The updater booted to TWRP which aborted the installation because of a failed zip signature check.
I disabled signature checking and ran the installation again. It succeeded.
Tried to directly install CM over it. I got the error message stating I couldn't flash on top of incompatible data.
At this point, I probably should just have wiped system and flash CM, but for some reason I decided to boot to stock.
Here is where it all seems to have gone wrong.
Try to flash and boot to TWRP, like in steps 13 to 18.
Push the B340 UPDATE.APP to /sdcard/dload.
Start the phone using power + vol down + vol up.
I have verified that the phone is on B340 and the builtin updater won't find further updates.
(I have repeated this step and the following ones countless times.)
Boot to bootloader and flash TWRP. Yes, the command succeeds.
Code:
…$ sudo fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.418s]
writing 'recovery'...
OKAY [ 0.641s]
finished. total time: 2.059s
fastboot reboot
adb reboot recovery # boots to stock recovery
Boot to bootloader and flash TWRP.
Hold power + vol up
I read that the duration holding the keys matters, so I tried this very often, but I always got to one of two different stock recoveries.
Factory reset and cache wipe with one of the two stock recoveries.
I also considered crushing the phone on the wall on multiple occasions, but then decided it would not help me with my goal.
Okay.
L21 with B340, how u boot to TWRP? -_-
Also, the two stock recoveries have the menu options "Download latest version and recovery, Reboot, Shutdown" and "Reboot, Wipe data/factory reset, Wipe cache partition".
I humbly thank everyone in advance who might have some contributions to share.
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b34p, but b320 is a great base and supports all custom roms..try it
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
Romiui said:
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
Click to expand...
Click to collapse
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
thilak devraj said:
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b340, but b320 is a great base and supports all custom roms..try it
Click to expand...
Click to collapse
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears pretends to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
but I know of no way to flash recoveries via ADB.
D
Click to expand...
Click to collapse
All recoveries can be Flashed throw Fast-boot ADB Boss .
ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
Click to expand...
Click to collapse
glad you did it
thilak devraj said:
glad you did it
Click to expand...
Click to collapse
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
muradulislam said:
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
Click to expand...
Click to collapse
I did, but to no avail. Reunlocking had no effect either.
muradulislam said:
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
Click to expand...
Click to collapse
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
ksdug said:
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
I did, but to no avail. Reunlocking had no effect either.
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
Click to expand...
Click to collapse
wait......
you couldnt make it?? ok right now were are you at??
how to boot Honor 5x into TWRP
I know this is an old post, but since I tried for nearly a week to get my Honor 5x to boot in TWRP when pushing volume up + power button, I just wanted to post how I finally got it working, just in case anyone else should have the same problem...
1. First, I downloaded the latest stock rom. On my Honor 5x Android 5 (Lollipop) was installed, so I downloaded an Android 6 (marshmallow) stock rom. Make sure to get the correct version for your region (e.g. C432 for Europe). I found the correct rom file by simply googeling. If you are in a boot loop or do not have a working android on your phone, read instructions below.
2. I un-zipped the rom file and copied the update.app to my sd card to folder "dload"
3. I booted regularly into Android and started the update installation from the settings, where I could select option to install from SD card.
4. once that was done, i enabled USB debugging in developer tools and booted into TWRP from ADB with command
fastboot boot twrp-3.1.0-0-kiwi.img
5. Then, I installed SuperSu (SuperSU-v2.82-201705271822.zip)
6. Then, I flahed TWRP directly FROM TWRP. To do so, I clicked "Install" button, clicked "Install Image" and then selected TWRP file (which i copied to my SD card earlier). BE CAREFUL TO FLASH TWRP as Revovery (NOT boot). Actually, I first flashed twrp-3.0.0-0-kiwi.img, then directly after flashed twrp-3.0.2-0-kiwi.img and then I flashed twrp-3.0.0-1-kiwi.img (you see I was kind of desperate...). After that, from TWRP I booted into bootloader and again flashed twrp image from PC using adb:
fastboot flash recovery twrp-3.1.1-0-kiwi.img
7. from ADB, I again booted into TWRP
fastboot boot twrp-3.1.1-0-kiwi.img
8. ... where I once more installed TWRP.
After that I clicked reboot and selected to boot into Recovery. Then it finally worked.
After endless tries to get my phone to boot into TWRP when pushing volume up and power button, I am not sure which of the above steps made the difference. I think the important part is to update to the latest android version.
BTW: my first problem was I bricked my phone by trying to install lineageos from TWRP 3.1.1.1 and was in an endless bootloop. Here is how I got a regular android running:
I booted into bootloader (power + vol DOWN) and flashed the following files from adb (i got the files by extracting an android stock rom with Huawei Update Extractor (HuaweiUpdateExtractor_0.9.9.3.zip)):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Hope this helps...
It's better to post in a new thread, that will be more helpful for you
I have used LGUP to install software (Nougat) and it's working fine..
I then install TWRP as normal, no issues reported during install (I can see via cmd screen).
I then proceed to reboot to recovery using methods I have been using for months, and it goes to yes, yes selection.
It then doesn't load TWRP but carries on wiping my phone to basics again.
Have tried various methods of putting TWRP on but does anyone think is something to do with Nougat as the bootloader unlocked screen is different, larger text etc
Have now tried a KDZ for marshmallow and recovery still won't go to TWRP.
It's almost like the recovery area is now not accessible?
Any suggestions please?
alienex said:
I have used LGUP to install software (Nougat) and it's working fine..
I then install TWRP as normal, no issues reported during install (I can see via cmd screen).
I then proceed to reboot to recovery using methods I have been using for months, and it goes to yes, yes selection.
It then doesn't load TWRP but carries on wiping my phone to basics again.
Have tried various methods of putting TWRP on but does anyone think is something to do with Nougat as the bootloader unlocked screen is different, larger text etc
Have now tried a KDZ for marshmallow and recovery still won't go to TWRP.
It's almost like the recovery area is now not accessible?
Any suggestions please?
Click to expand...
Click to collapse
Hmm strange. Have you tried rebooting using "adb reboot recovery" ?
I would suggest you flash recovery and boot straight into it not allowing the phone to boot into android. So flash recovery, remove battery, then try booting into recovery. Im pretty sure recovery can be lost if you boot into android before flashing SUPERSU (https://download.chainfire.eu/696/supersu/)
But i could be wrong
You have to do the following:
1) Flash the TWRP trouch Fastboot, don't reboot
2) Remove the battery, put it back, don't turn on the phone normally!
3) Use the button combination to enter in recovery
Ok have flashed again and it has "Stuck" this time after pulling battery before reboot so TWRP back!
Now to flash again and chill
Thanks both
Hi, I followed thew rooting instructions and got to the part where you flash the recovery after flashing I've tried to boot into recovery and all I get is your device software cannot be checked screen then it reboots or loads the factory reset screen and resets back to factory settings.
I have checked the phone is unlocked and it says it is
Jonnibravo said:
Hi, I followed thew rooting instructions and got to the part where you flash the recovery
after flashing I've tried to boot into recovery and all I get is your device software cannot be checked screen
then it reboots or loads the factory reset screen and resets back to factory settings.
I have checked the phone is unlocked and it says it is
Click to expand...
Click to collapse
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the TWRP installation/activation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else (even rebooting the phone) before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
People should really PRINT out the instructions before starting the process so they can carefully read it. It's very easy to skip over an important part or skip over a part you don't think is important?
It's all there for a reason.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the installation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I have installed using fastboot command and used the boot twrp.img command, the corruption message shows then the screen goes blank and it goes from the lg v30 logo back to corruption logo then reboots. What stage have I missed.
Jonnibravo said:
I have installed using fastboot command and used the boot twrp.img command, the corruption message shows then the screen goes blank and it goes from the lg v30 logo back to corruption logo then reboots. What stage have I missed.
Click to expand...
Click to collapse
From my instructions:
TLDR:
flash twrp: fastboot flash TWRP.img (TWRP-3.2.1-joan-v0.1.img re-named as just "TWRP.img")
boot twrp: fastboot boot TWRP.img (TWRP-3.2.1-joan-v0.1.img re-named as just "TWRP.img")
swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
select WIPE, then FORMAT DATA, then write yes
wipe cache, dalvik, data
flash magisk
flash encryption disabler
flash root disabler
reboot
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Oreo, install an app like this to easily facilliate rebooting to TWRP recovery in the future: Recovery Reboot
Even if you didn't actually install TWRP, you would still be able to boot to TWRP using the boot command ( fastboot boot TWRP.img) as long as you were connected to your computer and had TWRP.img in your ADB folder.
I've done it to make TWRP backups of "stock" systems where TWRP is not installed on purpose.
People who never finished activating TWRP have been able to do it, as they really don't have TWRP installed --- they are booting to "temporary" TWRP from their computer using fastboot boot TWRP.img. If they try to boot to TWRP from their phone, using an app they get the Android on his back which is a clue they REALLY don't have TWRP installed... but they are still able to fastboot boot TWRP.img when connected from their computer.
If you can't do that, something is very wrong. It's just that's the easiest way to get into TWRP after flashing it, so you can then "activate" it, make the installation stick.
Thanks for that its installed and I have installed a rom however I still cant boot into recovery, I have to reflash to get back in, and is there any way to get rid of the corruption message
Jonnibravo said:
is there any way to get rid of the corruption message
Click to expand...
Click to collapse
Not really. The "corruption message" is just LG's scary bootloader unlock warning to discourage you from rooting your phone. It's really a sign of freedom. Ignore it.
It's going to show up when you boot to TWRP or even when to boot to regular OS. It's just an image, a picture for LG to try to scare you. It stays up a few seconds then goes away.
Some Verizon users have found if they flash part of the Verizon firmware back it replaces the bootloader unlock warning with a few seconds of black:
datechnerd said:
I did have to wipe to reflash US998. But while I was fighting that I discovered what partition holds the bootloader warning!!!! It's rawresources. I moved the VS996 rawresources over to my US998 /dev/block/bootdevice/by-name/ and no longer have the warning. Granted it's a short black screen pause,
Click to expand...
Click to collapse
While that is very interesting, for now I would just ignore the warning. It's not preventing you from booting to TWRP. What's preventing you from booting to TWRP is somehow you haven't finished the entire TWRP installation/activation process.
Jonnibravo said:
Thanks for that its installed and I have installed a rom however I still cant boot into recovery, I have to reflash to get back in
Click to expand...
Click to collapse
If you installed the Recovery Reboot app I recommended (requires root access) you can boot to TWRP from there on your phone, IF you REALLY have TWRP installed. If you are having to boot to "temp" TWRP via ADB from your computer every time, then TWRP is not really installed on your phone. If you use that Recovery Reboot app, and it boots to Android on his back, then you still have stock recovery installed.
You need to reflash (reinstall) TWRP, then boot to TWRP immediately and go through the steps I posted to make it writable -- so it will stick as your custom recovery.
RTFM Myself
ChazzMatt said:
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the TWRP installation/activation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else (even rebooting the phone) before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
People should really PRINT out the instructions before starting the process so they can carefully read it. It's very easy to skip over an important part or skip over a part you don't think is important?
It's all there for a reason.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I just had the same issue, had it all ready went to Pie, lost Magisk root, played with it until lost it all.. so had to start again.. missed the important part after intalling TWRP.. thanks again :good::good::good: