Hi. I just unlocked my bootloader and was trying to flash twrp. Every time I do that the phone goes into infinite bootloop. I tired different twrp img but having the same problem. Please guide me how to flash twrp and which to use. Also I want to flash magisk to gain root.
si1233 said:
Hi. I just unlocked my bootloader and was trying to flash twrp. Every time I do that the phone goes into infinite bootloop. I tired different twrp img but having the same problem. Please guide me how to flash twrp and which to use. Also I want to flash magisk to gain root.
Click to expand...
Click to collapse
How are you flashing TWRP? What version are you trying?
Have you tried to go into recovery after flashing?
Sometimes you may need to go into recovery to correct the permissions before anything will work.
Have you tried flashing a fixed kernel for your build?
More information please.
I have just unlocked the bootloader and did not do anything else. I am on g8141. I used the flash tool to flash twrp. I used latest version of twrp, also tried 3.1.1. I also tried dragging the twrp to the command window via adb.
si1233 said:
I have just unlocked the bootloader and did not do anything else. I am on g8141. I used the flash tool to flash twrp. I used latest version of twrp, also tried 3.1.1. I also tried dragging the twrp to the command window via adb.
Click to expand...
Click to collapse
Try following the instructions on janjan's kernel thread, it's very detailed with links to files.
It suggests using ADB to push TWRP.
I would avoid flashtool.
I've use fastboot to flash TWRP.
I've used the version 3.2.3.0 (offical marple version for the G8141)
Related
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
akn4497 said:
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
Click to expand...
Click to collapse
I would flash the new RUU.
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
akn4497 said:
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
Click to expand...
Click to collapse
Why not use the new 5.0.1 RUU?
andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
andybones said:
Why not use the new 5.0.1 RUU?
Click to expand...
Click to collapse
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
akn4497 said:
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
Click to expand...
Click to collapse
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU? Fastboot flash zip nameofRUU.zip
andybones said:
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU?
Click to expand...
Click to collapse
Oh shoot, I feel dumb. I'll let you know, thanks!
The RUU worked! I used the exe and I'm up and running. Thanks!!
akn4497 said:
The RUU worked! I used the exe and I'm up and running. Thanks!!
Click to expand...
Click to collapse
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
cntryby429 said:
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
Click to expand...
Click to collapse
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
akn4497 said:
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
Click to expand...
Click to collapse
Glad to hear you're up and running my friend.
What's up everyone. So I unlocked the bootloader of my Verizon pixel OK. I then went to root it and after it rebooted once it seems to be stuck at the jumping dots screen. It's been like 5 minutes. Not sure what I should do.
Any suggestions?
From bootloader:
Using stock boot.img from your version's factory image from Google. (In a zip inside the main zip).
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot reboot
Then after setting up your phone try rooting again. You have to boot once stock after unlocking bootloader initially.
If still no dice, use flash-all.bat or .sh to go fully stock, then boot and set device up then reboot to root as per normal directions for your firmware.
Rooting won't cause a second wipe. Just unlocking or flashing factory image.
Do NOT relock bootloader (potential brick).
Sent from my sailfish using XDA Labs
Got it!! Holy Crap brother thank you!!!
Just so I don't do that again, which root files should I be using? I read it may have been caused from using outdated files
Which method did you use to gain root? Fastboot boot boot-to-root.img caused me to bootloop. I restored the factory image, installed TWRP alpha2, then flashed SuperSU 2.78 SR5 from TWRP and all was fine.
yeah i tried the boot boot method. I guess I should try the twrp method. Just so I don't screw up again, do you remember where you got the files. Figure I'll use those if they worked for you.
Everything is in the Pixel ROMs, Kernels, Recoveries, and Other Development Forum.
FernBch said:
Everything is in the Pixel ROMs, Kernels, Recoveries, and Other Development Forum.
Click to expand...
Click to collapse
Thanks! OK so i downloaded the twrp file I'm getting a failed error message. I've renamed the file twrp.img and am using this commmand to flash it fastboot flash recovery twrp.img
What am I doing wrong?
RC1 or Alpha2? RC1 kept giving me md5 mismatch errors. On the TWRP download page both Alpha2 files are also available.
I'm trying to flash alpha 2 and it keeps saying Failed remote partition recovery doesnt exist
Haven't seen that one before. When I tried the boot-to-root method I had to restore a factory image before I could try again.
FernBch said:
Haven't seen that one before. When I tried the boot-to-root method I had to restore a factory image before I could try again.
Click to expand...
Click to collapse
Yeah I'm totally stumped. I did have to reflash the boot image and am back up and running. just can't seem to get twrp to flash!! I've followed the steps from multiple threads and just can't get it to work.
Any suggestions are welcome
Boot twrp Img, not flash. Then install the twrp zip if you want it to replace the stock recovery.
Which guide says flash..theres a new rc1 out but haven't checked it. You made 2 posts regarding inability to flash but did you Google for the answer?
I kept trying to flash it cause the threads and sites I saw kept using that command. I finally used fastboot boot twrp.img and it worked fine. Also many of the guides don't say you need to have the zip on your phone to flash.
No prob, I worked it out!! Thanks for everyone's responses!!!
I am using op6 with oxygenos 5.1.11 (for unrelated reasons I cannot use android pie yet, so I had to downgrade to android 8.1 until a certain bug is fixed in 9).
I am trying to flash twrp, with no avail: when I use "fastboot flash recovery <twrp.img>", I get "FAILED (remote: '(recovery_a) No such partition')", and when I try using "fastboot boot <twrp.img>", the phone boots into an unresponsive state with a black screen and a white notification led.
what am I doing wrong? I've tried both twrp-3.2.3-x_blu_spark_v9.91_op6.img and the official twrp-3.2.3-1-enchilada.img in place of <twrp.img>, no difference.
Is your bootloader unlocked? (fastboot oem unlock)
cesar.mk4 said:
Is your bootloader unlocked? (fastboot oem unlock)
Click to expand...
Click to collapse
of course it is!
First of all you can't flash recovery in fastboot on OP6. You need to boot the image and flash the recovery.zip after that you will have recovery permanently.
BTW why don't you search and have a look at the guide?
This time I do it for you. If you exactly follow these steps you will get recovery working.
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
Follow this video. Remember to use the twrp-3.2.1-0-enchilada.img and twrp-installer-enchilada-3.2.1-0.zip, not the newer files.
https://www.youtube.com/watch?v=Es80k627kTc
Like the others said above, it sounds like you are trying to flash the version of TWRP for Pie onto an Oreo install, you need to get the last stable version of TWRP for Oreo, which I believe is 3.2.1. You'll need both the '.img' and '.zip' files. Good luck!
Kollachi said:
First of all you can't flash recovery in fastboot on OP6. You need to boot the image and flash the recovery.zip after that you will have recovery permanently.
BTW why don't you search and have a look at the guide?
This time I do it for you. If you exactly follow these steps you will get recovery working.
Click to expand...
Click to collapse
if you read my original post, I have tried to boot to recovery already, which didn't work. what I was not aware of is that the recovery image is android version-dependent. an old twrp-3.2.3-x_blu_spark_v8.83_op6.img did the job.
ahamling27 said:
Like the others said above, it sounds like you are trying to flash the version of TWRP for Pie onto an Oreo install, you need to get the last stable version of TWRP for Oreo, which I believe is 3.2.1. You'll need both the '.img' and '.zip' files. Good luck!
Click to expand...
Click to collapse
thanks! I was not aware that twrp images are android version-dependent and not backwards compatible. especially in the original enchilada twrp images one does not see it. an old twrp-3.2.3-x_blu_spark_v8.83_op6.img did the job.
I am currently on OOS 10 OB2/31 and can't seem to find a way to install TWRP and Magisk. Found ways to install TWRP and Magisk via patched boot images on OOS 10 stable but not for OB2/31.... anyone know why it's not as simple as flashing TWRP via fastboot?
I also have a problem
'OOS10beta31' Root
XcutionerX said:
[...] anyone know why it's not as simple as flashing TWRP via fastboot?
Click to expand...
Click to collapse
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
Thank you for your help, gonna try following those. Hopefully I don't f up and have to do a msm restore. But why would they disable that command?... Just to make everything complicated? Guess I will not stick to Oneplus next year.
XcutionerX said:
But why would they disable that command?
Click to expand...
Click to collapse
Security? Deprecated or soon-to-be-deprecated command? Dunno really, lol.
XcutionerX said:
... Just to make everything complicated?
Click to expand...
Click to collapse
To be fair, the only difference between this method and the old method is just one word and manually rebooting to recovery. You still have to flash the twrp.zip after flashing from bootloader file to install TWRP, so it's not too radically different.
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
I have successfully installed TWRP and Magisk with the help of those links. Thank you again for your help.
quizzina said:
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
Click to expand...
Click to collapse
Thank your for the in-depth explanation.
Just download oxygen updater and install 10.0.1 and be done with it
I ended up flashing TWRP over my boot slot (B) and now I just boot into TWRP. I have already installed TWRP on boot slot (a). I can't remember which version of oxygenOS I have installed and couldn't find a way to confirm. How can I fix this? Also want to update to latest version of oxygenOS and android. No data on phone yet. phone still connects to computer, adb sideloader and fastboot commands still work work. Thanks
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
redpoint73 said:
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
Click to expand...
Click to collapse
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
doctor_whooves said:
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
Click to expand...
Click to collapse
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
plasticarmyman said:
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
Click to expand...
Click to collapse
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
tech_head said:
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
Click to expand...
Click to collapse
in this case the best thing to do is just unbrick using MSM
plasticarmyman said:
in this case the best thing to do is just unbrick using MSM
Click to expand...
Click to collapse
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
doctor_whooves said:
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
Click to expand...
Click to collapse
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
hey guys. Not able to flash oos through twrp.
getting "error flashing zip".
tech_head said:
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
Click to expand...
Click to collapse
Doesn't TWRP back up everything including boot partitions?
Is there nothing that will take the entire internal storage and just make a 'bare metal' image of it for restoring.. the whole entire thing, byte for byte? If not, why doesn't this exist? It just seems so logical to me and would be so incredibly useful. Phone borked? No problem. Just re-image it form the archive you made. To me, that is what TWRP is all about, at least conceptually if not technically.