Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.
RegularSam said:
Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.
Click to expand...
Click to collapse
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hmm, wait, maybe I didn't catch what you were sayin, with "try to look your bootloader" you meant "try to LOCK your bootloader" right?
Because yesterday I've made root with Magisk, if I try to lock the bootloader I risk to brick the phone, isn't it true? Thanks anyway for your reply.
jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I found the trick. I applied from fastboot the two commands that I mentioned:
fastboot flash recovery recovery.img
fastboot boot recovery.img
Only difference? I didn't run the Command Prompt as administartor, as I did yesterday (I also tried before this operations using PowerShell without success), WOW. Now before reboot the phone I allowed the modification to the partition in TWRP recovery, I saved logs from kernel and recovery and I'm trying to make a backup. I will tell you the results.
Yesterday I've also tried to flash the recovery by using Flashify without success, just sayin.
EDIT:
After rebooting the stock recovery returned. I hate this thing. I've also renamed this two files:
recovery-from-boot-p
install-recovery.sh
It didn't work.
jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Click to expand...
Click to collapse
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.
RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.
CazeW said:
Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.
Click to expand...
Click to collapse
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?
RegularSam said:
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?
Click to expand...
Click to collapse
Locking the bootloader will not cause a boot loop if you're rooted. The reason I asked what happens when you lock the bootloader is that the 5x had had issues with the emmc going bad. A sure sign of that is the bootloader not staying locked after locking it and booting back up.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seriously, this thing is driving me crazy. Tried to go with your suggestions but I can't boot in the recovery, no way. I have also flashed the original recovery and the tried to get in with fastboot boot twrp.img, no success. I can't figure out why I have this problem.
EDIT: great, now even flashing the stock recovery doesn't work, the phone reboot every time I try to get in any recovery. I have no words.
EDIT 2:
GUYS, I think I've found the solution. As I said in the main post, I was thinking that maybe the problem was due to the BLOD bug, in fact the common twrp.img that you can find on the twrp page uses all the 6 cores of the Nexus 5X causing the rebooting which I mentioned. Now, I found this version of twrp 3.1.1 which is modified to use 4Cores, thanks to the user XCnathan32 and his thread about BLOD bug: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199.
Now it seems like the TWRP Recovery is stick to the phone and I'm really happy to say that. Thanks for all your support, you were very patient!
Click to expand...
Click to collapse
Related
Hi. Im stucked at fastboot... I have no OS and no TWRP.... on oneplus 2 it happen to me and I used a tool called FIRST AID, but for op3 it does not exist. I tried flash twrp by fastboot, it says success but when I boot to fastboot, I get a black screen.... Please help me
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
please help me!
infamouzwt said:
Im sorry to say this. But r.i.p oneplus 3
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
thats not true.....
Which TWRP are you flashing and what rom were you on before the speed bump
NZnewbie said:
Which TWRP are you flashing and what rom were you on before the speed bump
Click to expand...
Click to collapse
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
tuga49 said:
Hi. My rom before was freedom OS.... I tried twrp 3.0.2.0 and twrp 3.0.2.1 and stock recovery....
Click to expand...
Click to collapse
Try the modified 3.0.2-19 twrp. Search XDA for it. It's all over.
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Nilshalok said:
Flash His recovery From here Via CMD OR anytoolkit
Than Move a flashable 3.2.4 on Your Mobile Via Usb (Going Recoverymode first)
Than Install 3.2.4 reboot my be its work...
Click to expand...
Click to collapse
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
abuddlah said:
Don't panic, i had the same issue yesterday. but try to search for the 3.0.2.19 verison of TWRP and flash it with fastboot.
Click to expand...
Click to collapse
Hi. I don't find any twrp with version 3.0.2.19... please help me.
Unbrick tool
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hi! thank you all! I solved the problem flashing twrp with version 3.0.2.19! thank you all!
tuga49 said:
hi. it says success flashed on cmd, but when I boot to recovery, it just show me a black screen!
Click to expand...
Click to collapse
are you Trying 3.5.2???
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Mansquatch312 said:
Having a similar issue. I'm on 3.5.2 unlocked bootloader, no root, stock recovery. Everytime I try to flash TWRP, it appears to succeed, but will never boot to TWRP. Boots fastboot and OOS just fine, but no recovery available. I then tried to flash stock recovery, but same issue appears. I then was able to use skipsoft toolkit to get stock recovery, but only by relocking then unlocking the bootloader. Everytime I tried to simply flash a recovery it appears to succeed, but will not boot to recovery. So skipsoft was able to fix the no recovery problem, but I am still unable to flash TWRP
Click to expand...
Click to collapse
Here is the issue. 3.5.2 has a different firmware than previous OOS versions. You will need a specific 3.5.2 modified TWRP. The link is here:
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
You can see that this is discussed on the oneplus forums here: https://forums.oneplus.net/threads/...ity-update-with-working-twrp-recovery.465353/
I ran into this same problem myself, and realized that this was the issue. You should be very careful because it could cause you some grief. Whatever you do don't lock your bootloader if you end up with a nonfunctional and non functional recovery.
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Saqrez said:
I have the same issue i can flash all the recovery images but non of them worked i tried 1000 different methods and nothing works.. Getting a bit desperate is someone please able to help me got my new phone already broke it kinda..
Click to expand...
Click to collapse
I suggest you to refer to the post of @gmarondel :
gmarondel said:
Just look here it did help me in nearly the same situation:
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
Follow this guide and everything will be ok.
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Vexo_ said:
I know u fixed the problem but i think this is a general guide to fix your phone if you have this type of issue after flashing OOS 3.5.6 based roms!
i had the same issue yesterday with freedom os 1.7 (based on OOS 3.5.6) and OOS 3.5.6, here is how i fixed my phone:
- download http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
-unzip it and put it on the desktop
-put your phone in fastboot (make sure you have unloked bootloader and installed all the drivers and adb on your pc)
-press shift and right mouse click on the desktop and hit open a new prompt window here
-write "fastboot boot twrp-3.0.2-19-oneplus3.img" and press enter, your phone should reboot in recovery (keep the prompt open)
-wipe dalvik/system/data/cache/internal storage go back and do format data
-reboot in bootloader(fastboot)
-write in the prompt "fastboot flash recovery twrp-3.0.2-19-oneplus3.img"
-unplug your phone and turn it off switching in fastboot with the volume buttons
-when it's powered off press power+volume down and chose recovery
-now you should boot and flash any rom in recovery (i suggest you to not try to flash any OOS 3.5.6 based roms)
i went back to OOS 3.2.6 but any other custom rom lshould be fine!
Click to expand...
Click to collapse
I really appreciate your help but i think i fixed it. Today suddenly my phone went into recovery without doing anything except for 1000 methods. I am so happy that people like you are willing to help people.
Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !
Important: official TWRP does NOT backup the EFS partition correctly while this one does. Do NOT restore an EFS backup that you did not take on the same build of TWRP as the one you're currently using. You will lose IMEI
Get support here: https://discord.gg/UF9qnts
Same as official twrp but
Built with latest lineageOS trees
Built with latest kernel with ext4, f2fs, exfat and sdfat driver
Thanks a lot to @jcadduono for the exfat upstream
Undervolting
Supports signature verification for lineageOS official zips
Supports signature verification for haruhirom official zips
Built with GCC 8 for maximum speed
Support for backing up, restoring and flashing system image zips
Manifest: https://github.com/GlassROM-devices/platform_manifest_twrp_lineageos
Toolchain: https://bitbucket.org/anupritaisno1/aarch64-linux-gnu/overview
FPSUsername said:
You can flash a recovery using fastboot (
Code:
fastboot flash recovery recovery.img
).
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
anupritaisno1 said:
Also guys twrp can be flashed on locked bootloaders
If you are on a locked bootloader you must make sure that you ALWAYS flash twrp while booted into Android, using the dd command
Code:
dd if=recovery.img of=/dev/block/bootdevice/by-name/recovery
If you use the twrp flasher while on a locked bootloader you're just dumb
Click to expand...
Click to collapse
https://glassrom.pw/recovery.img
All sources (kernel source, device tree, etc) are bundled in the manifest. Please don't ask for separate sources just read the manifests
Just an FYI: official twrp builds are built by a bot, oneplus 2 doesn't have a twrp maintainer and nobody is reviewing the code that goes into twrp for our device
You really shouldn't use the official twrp builds
no comments, that means no issues. good job
Twrp 3.2.0 was released today so a new build for that is out
Please test and report bugs
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Sent from my OnePlus2 using XDA Labs
sanjeetkumar495 said:
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Click to expand...
Click to collapse
I did, it works.
sanjeetkumar495 said:
Install instructions please.
Can we flash the IMG file using inbuilt official twrp?
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot:
Code:
fastboot flash recovery recovery.img
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
FPSUsername said:
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot (
Code:
fastboot flash recovery recovery.img
).
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
Adding these to the main post
Also guys twrp can be flashed on locked bootloaders
If you are on a locked bootloader you must make sure that you ALWAYS flash twrp while booted into Android, using the dd command
Code:
dd if=recovery.img of=/dev/block/bootdevice/by-name/recovery
If you use the twrp flasher while on a locked bootloader you're just dumb
FPSUsername said:
Yes. You probably have never flashed something or you just don't know all features of twrp.
You can flash a recovery using fastboot:
Other method, if you already have a custom recovery (I suspect official twrp), go to the directory where you placed the recovery.img, press install img at the bottom of the twrp screen and the img should be visible.
Select it, tap on recovery and swipe to flash/install.
Click to expand...
Click to collapse
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
sanjeetkumar495 said:
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Then use the locked bootloader method
sanjeetkumar495 said:
Thanks but FYI I know all the methods of flashing recovery but currently I don't have access to a PC so just in case something goes wrong I won't be able to use recovery therefore was a little cautious so asking for twrp process of flashing.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Use Flashify.
Deleted
Sad to say but this twrp doesnt come close to the latest official. I experienced lag and slow rates.
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
sujju said:
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
Click to expand...
Click to collapse
If your phone is rooted, you might want to give flashfire or flashify a try.
erzherzog said:
If your phone is rooted, you might want to give flashfire or flashify a try.
Click to expand...
Click to collapse
It's not rooted..
sujju said:
Hi all,
I tried to install official twrp 3.2 from within twrp 3.1. and ran into issues. The recovery overall got deleted and the phone's bootloader got locked. Besides, 'allow OEM Unlock' toggle in developer options is not working. I'm seriously in a mess now.
Can someone pls detail the steps of installing this enhanced TWRP on a locked bootloader like mine? Would be extremely thankful.
Click to expand...
Click to collapse
You must patch the rom to provide SuperSU's binaries at boot with oxygenos recovery and a signed boot.img
After booting you have to flash twrp using dd
Instructions for doing so are in the haruhirom thread
This definitely isn't for beginners
Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.
When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?
Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.
@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.
motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse
Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?
Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL
edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
welp, just tried to flash the factory image and got this:
error: failed to load 'image-crosshatch-pq1a.181205.006.zip': Not enough space
mac208x said:
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
Click to expand...
Click to collapse
fastboot flash boot --slot all boot.img
#6 in this guide.
Homeboy76 said:
fastboot flash boot --slot all boot.img
#6 in this guide.
Click to expand...
Click to collapse
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
mac208x said:
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
Click to expand...
Click to collapse
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- Edit: Kernel of your choice
- Add more zips
- magisk-17.3.zip
- reboot system
Homeboy76 said:
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- ElementalX 1.02.zip
- Add more zips
- magisk-17.3.zip
- reboot system
Click to expand...
Click to collapse
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
mac208x said:
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
Click to expand...
Click to collapse
After installing the TWRP.zip change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
airmaxx23 said:
Change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
Click to expand...
Click to collapse
Im so sorry but what do you mean by slot?
mac208x said:
Im so sorry but what do you mean by slot?
Click to expand...
Click to collapse
When you're in TWRP go to reboot, then switch from your current slot to the other.
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
mac208x said:
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
Click to expand...
Click to collapse
Are you flashing Magisk in both slots?
airmaxx23 said:
Are you flashing Magisk in both slots?
Click to expand...
Click to collapse
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
mac208x said:
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
Click to expand...
Click to collapse
Try just that first and see if you can fully boot the phone.
airmaxx23 said:
Try just that first and see if you can fully boot the phone.
Click to expand...
Click to collapse
No bootloop back to trwp. Now its stuck on the white google logo screen wont go pass it
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
jd1639 said:
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been doing it all along whenever I flash anything.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
You'll have to flash back to stock in fastboot.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
airmaxx23 said:
I've been doing it all along whenever I flash anything.
You'll have to flash back to stock in fastboot.
Click to expand...
Click to collapse
jd1639 said:
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
mac208x said:
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
Click to expand...
Click to collapse
Do you have the latest sdk platform tools. If not Google that, download the zip and extract it. Replace what you do have. I create a folder c:adb and put everything in that. Then set an environment variable path in Windows so fastboot and adb are available no matter what folder I'm working in.
Sent from my [device_name] using XDA-Developers Legacy app