The latest TWRP img was leaving me stuck with a fastboot screen, assumed twrp version was too high EVEN THOUGH EVERYWHERE I was seeing "It is recommended you flash latest twrp" and NOTHING about what TWRP is for what Android version WTF!
So yeah I just got 3.2.3-2 to work, now wondering if I should install latest TWRP zip after flashing the 9.0.17 or after flashing the OOS 11.1.1.1? Can you install the latest TWRP zip while using an earlier TWRP img??
Related
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.
Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis
mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.
Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.
Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.
Its a shame.
7 years unlocking bootloaders, installing CWM or TWRP or Philz recovery, flashing rom after rom, not even one device bricked, and today, i messed up, i hope its not bad.
So the short version of what i did is that i flashed twrp.img trough and older version of twrp and now it wont boot into twrp, it says that it failed to verify the recovery image or something like that, and my laptop wont recognize the cellphone, the cellphone boots into the latest Havoc rom but without Gapps and without root because i did not install it beforehand, when in bootloader mode it just says that it could not recognize the device.
The long version is that i had Resurrection Remix, obviously an unlock bootloader, magisk etc... everything was fine until today that i tried to install Havoc, the installation went well but i found out that ambient display was not working, someone told me that the previous version of Havoc did not had that problem so i tried to flash it but it bootlooped for like 1hr, so i read that the version of TWRP provided by the OP was the way to get it to work, i downloaded the .img file and flashed it trough TWRP and tried to install Havoc again but i was stuck in a bootloop, so i flashed the latest Havoc build so i could download the latest version of twrp, i did not flash Gapps or Magisk because i was going to re flash the rom and then flash Gapps and magisk, so i downloaded TWRP and flashed trough TWRP and thats when the sh$& hit the fan, now it wont boot into TRWP and my laptop wont recognize the device, neither on android nor in bootloader mode.
So, thank you guys in advance for your help, tomorrow im going to try on a computer at my work and see if its my computer and if not, well, ill have to se what you geniuses come up with. thank you so much again.
Info:
Rom build number: opm6.171017.030.h1 or 20180811 android 8.1.0
TWRP: i started with 3.2.2-0 then i downgraded to 3.2.1-0 and the one that messed up everything was 3.2.3-0
By the way, I have a full twrp backup of when my phone was stock, (but no way to use it) T_T
I have blu_spark TWRP and working root on my international 6T. I would like to upgrade the recovery to the official TWRP now, as file decryption is working now in the official.
Is this the correct process to go from blu_spark to official?
Download the fajita TWRP .img and .zip files (from https://forum.xda-developers.com/oneplus-6t/development/recovery-unofficial-twrp-touch-recovery-t3861482
Connect phone to PC and enter fastboot mode
Boot the .img file
Once in recovery, flash the new .zip file
My plan is to then flash the new Oxygen OS released from OnePlus and then flash Magisk.
Looks okay
However, the flash of the OS in TWRP is not clearly defined. Everyone is waiting for new update to try it in the TWRP... So, basically if you wanna flash it that way, you'll probably be the first.... This could put you in the risk of bricking the device though.
I have just done this. Yes you can boot the unofficial 6T recovery and then flash the installer no problem. However if you were running a OP6 ROM the 6T will not decrypt it, unless Im soing something wrong. On my phone once Im on a OP6 rom like LOS16 I can only use the Blu TWRP, if I go back to stock 6T OOS I have to use the 6T TWRP to decrypt. On either system I can bounce between TWRP versions without issue doing as you said, boot the img, then flash the zip, but I cant view anything. Going back to thr correct TWRP restores data access, no bricking worries that Ive run into personally.
There is no official TWRP yet...
Sent from my OnePlus 6T using Tapatalk
celtic426 said:
I have blu_spark TWRP and working root on my international 6T. I would like to upgrade the recovery to the official TWRP now, as file decryption is working now in the official.
Is this the correct process to go from blu_spark to official?
Download the fajita TWRP .img and .zip files (from https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Connect phone to PC and enter fastboot mode
Boot the .img file
Once in recovery, flash the new .zip file
My plan is to then flash the new Oxygen OS released from OnePlus and then flash Magisk.
Click to expand...
Click to collapse
I did a post below for the update to Unofficial version with decryption working
https://forum.xda-developers.com/showpost.php?p=78267079&postcount=299
Sent from my OnePlus6T using XDA Labs
Thanks for the replies.
I successfully went from blu_spark TWRP to the newer faijta TWRP which has the option for decrypting.
That allowed me to use the recovery to flash the new OTA OxeygenOS update which I downloaded from oneplus.com.
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
lenci98 said:
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
Click to expand...
Click to collapse
You guessed right. You need to flash stock 5.1.4 OxygenOS (which will create the vendor partition).
Then you can update to 9.0.4/9.0.5(remove the compatibility.zip from the rom files) either with OTA or manually flashing(see official oxygenOS rom threads for 9.0.5)then you can update the twrp to 3.3.x.
After this you can flash XXX magisk mod 4.3 onwards as it's a magisk module.
lenci98 said:
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
Click to expand...
Click to collapse
That's exactly how to do it. Use an Oreo era Codeworkx TWRP to flash a full OOS ROM. You have to have used 5.1.4 to create the Vendor partition so flash that. Let it overwrite TWRP with the stock recovery, and then OTA up to latest OOS. Fastboot flash latest Codeworkx TWRP and you're done.
Uninstall Magisk before you begin.
strongst said:
You guessed right. You need to flash stock 5.1.4 OxygenOS (which will create the vendor partition).
Then you can update to 9.0.4/9.0.5(remove the compatibility.zip from the rom files) either with OTA or manually flashing(see official oxygenOS rom threads for 9.0.5)then you can update the twrp to 3.3.x.
After this you can flash XXX magisk mod 4.3 onwards as it's a magisk module.
Click to expand...
Click to collapse
Exactly this was my plan. Thanks for the help. I struggled with this for literally months!
Hi, my device is currently without an OS after a full wipe. I have fastboot access and latest 3.6 TWRP recovery.
Can someone please share the link to last updated Android 10 OxygenOS stock ROM and how to flash it?
Also, how can I root via Magisk after installing OOS?
myblessayu said:
Hi, my device is currently without an OS after a full wipe. I have fastboot access and latest 3.6 TWRP recovery.
Can someone please share the link to last updated Android 10 OxygenOS stock ROM and how to flash it?
Also, how can I root via Magisk after installing OOS?
Click to expand...
Click to collapse
Curious why you want a10? The latest oos is a11. You just flash the zip for oos in twrp. It will replace your recovery so always reflash twrp after if you want it. Magisk can also be installed from twrp.
Brettroth said:
Curious why you want a10? The latest oos is a11. You just flash the zip for oos in twrp. It will replace your recovery so always reflash twrp after if you want it. Magisk can also be installed from twrp.
Click to expand...
Click to collapse
Wasn't my device so had to go with A10. Was able to install OS, recovery and root using THIS thread.
Thanks for the response anyway!