I tried the latest twrp from the official website, but to no avail
Anyway, i installed PE+ with their official recovery, but now i can't flash magisk or any module
I'm wondering if it can be done (twrp or orange fox) without having to lose all my rom data, as i am alredy settled with my current ROM
Ps: when i tried i flashed at partition be, i have no clue as to why i didn't want to boot to recovery even tho the installer said it actually said it was flashed
Thanks in advance
Hugask said:
I tried the latest twrp from the official website, but to no avail
Anyway, i installed PE+ with their official recovery, but now i can't flash magisk or any module
I'm wondering if it can be done (twrp or orange fox) without having to lose all my rom data, as i am alredy settled with my current ROM
Ps: when i tried i flashed at partition be, i have no clue as to why i didn't want to boot to recovery even tho the installer said it actually said it was flashed
Thanks in advance
Click to expand...
Click to collapse
Yes you can flash any recovery without loosing any of your data
Check the current partition and flash recovery in that partition
ABHINAV-ACHHA said:
Yes you can flash any recovery without loosing any of your data
Check the current partition and flash recovery in that partition
Click to expand...
Click to collapse
the latest official TWRP was released in June 2020. TWRP is not working for me as well after Mi update of Sept 2020.
Now if I install TWRP and boot into system via recovery, it takes me back to Fastboot. I was lucky to have a copy of Stock boot img. @Hugask
SidRose01 said:
the latest official TWRP was released in June 2020. TWRP is not working for me as well after Mi update of Sept 2020.
Now if I install TWRP and boot into system via recovery, it takes me back to Fastboot. I was lucky to have a copy of Stock boot img. @Hugask
Click to expand...
Click to collapse
May be you are trying to boot with incompatible twrp or maybe you are twrp be corrupted
I had flashed twrp in september build also.
Try using 3.4.0.0 or 3.3.1.7
SidRose01 said:
the latest official TWRP was released in June 2020. TWRP is not working for me as well after Mi update of Sept 2020.
Now if I install TWRP and boot into system via recovery, it takes me back to Fastboot. I was lucky to have a copy of Stock boot img. @Hugask
Click to expand...
Click to collapse
Oh, so an update broke it
And yeah, you pretty much described the problem, that's exacly what i'm facing
Install TWRP correctly, but ignores me when i try to boot into it and goes to fastboot
ABHINAV-ACHHA said:
May be you are trying to boot with incompatible twrp or maybe you are twrp be corrupted
I had flashed twrp in september build also.
Try using 3.4.0.0 or 3.3.1.7
Click to expand...
Click to collapse
I don't think so, i made sure to download (latest) it from the oficial website, also, i'm not the only one having this issue
Hugask said:
Oh, so an update broke it
And yeah, you pretty much described the problem, that's exacly what i'm facing
Install TWRP correctly, but ignores me when i try to boot into it and goes to fastboot
I don't think so, i made sure to download (latest) it from the oficial website, also, i'm not the only one having this issue
Click to expand...
Click to collapse
Try using SHRP recovery it is also a great option
Related
Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Mandeep Singh 07 said:
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Click to expand...
Click to collapse
Is ur bootloader updated to latest one ??
[email protected] said:
Is ur bootloader updated to latest one ??
Click to expand...
Click to collapse
yeah its latest one 3.0.3
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
actually when i root the phone , then it goes into bootloop, i didn`t backup my data so i lost my all data ,
after that i install paranoid then it stucks on boot logo , i tried it several times but none happens,
then i use adb push command ino twrp recovery(3.0.2) to copy cyanogenmod after that i flash it , it fails ,
then i flash cwm recovery then flash is succeded and currently running cm 13 ,
when i installed root checker it said your phone is partially rooted, when i enable root option in developer option then it said root verified.
But when i tried to flash other roms using twrp (3.0.3, 3.0.2) it stucks on boot logo.
Please help me
Exodusche said:
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Click to expand...
Click to collapse
lower bootloader can`t flash it fails every time....
Mandeep Singh 07 said:
lower bootloader can`t flash it fails every time....
Click to expand...
Click to collapse
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Exodusche said:
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Click to expand...
Click to collapse
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Mandeep Singh 07 said:
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Click to expand...
Click to collapse
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Exodusche said:
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Click to expand...
Click to collapse
thanks bro this works fine
Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.
Im stuck on poco boot screen and after few seconds it reboots to fastboot.
I did a twrp backup (system, vendor, data and boot) when everything was working but now after i try to restore the twrp backup, it still doesnt fix the problem.
before this, i flashed a new PE build and that had a boot loop for some reason.
wtf?
How does my twrp backup restore doesnt fix it ?
Do i have to miflash a fastboot rom ? is it the only fix for me now ?
You may find your solution here : https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004/page42
You can also install latest ROM and restore data only.
fmcheetah said:
You may find your solution here : https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004/page42
You can also install latest ROM and restore data only.
Click to expand...
Click to collapse
i dont have a firmware zip in my storage and i cant push it through adb because i didnt have debugging enabled. So i cant cleanflash because i dont have the firmware zip. Looks like i will need to use the mifash method.
flash the original Vendor image!
if you have flashed PE over MIUI10.2.x
, this mean you have used MODIFIED VENDOR IMAGE
poco supports Treble!
you cannot flash PE/ or any other custom rom over modified vendor image
take the latest vendor image from mirror.akhilnarang.me/MIUI/beryllium/
and flash it view twrp
and reboot
you wil lbe fine
i fixed the problem. I put firmware - vendor zip in sd card and flashed it through sd card. All good now. Thanks for trying to help my dumb ass.
i guess there might be some magisk module thats causing the bootloop after i flash a new build of rom . Maybe.
If thats the case. There's a flashable zip file that lets you disable a magisk module via TWRP.. ehehehe.. happened to me too. I flash gl tools via magisk systemless then it got stuck on pocofone f1 loading screen.. so i flashed that magisk module disabler.. hit some commands via TWRP TERMinal emu.. then it boot right away..
KabalLV said:
Im stuck on poco boot screen and after few seconds it reboots to fastboot.
I did a twrp backup (system, vendor, data and boot) when everything was working but now after i try to restore the twrp backup, it still doesnt fix the problem.
before this, i flashed a new PE build and that had a boot loop for some reason.
wtf?
Click to expand...
Click to collapse
Always uninstall Magisk before flashing new update if you are on official twrp cuz it doesn't support ota, update then reinstall it. If you have did so wipe encrypted internal storage , wait a bit it will boot .
aikhhk8 said:
Always uninstall Magisk before flashing new update if you are on official twrp cuz it doesn't support ota, update then reinstall it. If you have did so wipe encrypted internal storage , wait a bit it will boot .
Click to expand...
Click to collapse
Thanks. Didn't know about this.
Tell someone to call you, it was glitchy for me for the first 2-3 mins after the call but later works fine.
EEa(EU) rom 10.3.3.0 update
Received it too yesterday and all is ok.
Does anyone know how to flash that update using TWRP? I have rooted my Stock ROM with TWRP, and the Update is downloaded OTA and then reboots to recovery, but TWRP obviously is unable to install it: First it doesn't ask for the password to decrypt the data partition and shows the crypted content of the partition, making it impossible to see or select the downloaded update. A reboot into recovery decrypts the data partition and shows the downloaded Update (as a ZIP) in the folder /downloaded_rom. I tried to install that ZIP from TWRP manually, but to no avail - all you get is an error message.
Edit: Forget the question. Seems the phone healed itself. The first OTA download was an update 10.3.1 to 10.3.3 with a size of around 500 MB, and that couldn't be installed. When the System Updater saw this didn't succeed, it downloaded the complete 10.3.3 Package (2,2 GB) OTA, and installed that via TWRP with no problems whatsoever. I lost Magisk, which i needed to reinstall, but other than that, everything's fine.
Edit 2: The complete package obviously also overwrites TWRP, which i had to reinstall, too.
cgdams said:
Does anyone know how to flash that update using TWRP? I have rooted my Stock ROM with TWRP, and the Update is downloaded OTA and then reboots to recovery, but TWRP obviously is unable to install it: First it doesn't ask for the password to decrypt the data partition and shows the crypted content of the partition, making it impossible to see or select the downloaded update. A reboot into recovery decrypts the data partition and shows the downloaded Update (as a ZIP) in the folder /downloaded_rom. I tried to install that ZIP from TWRP manually, but to no avail - all you get is an error message.
Edit: Forget the question. Seems the phone healed itself. The first OTA download was an update 10.3.1 to 10.3.3 with a size of around 500 MB, and that couldn't be installed. When the System Updater saw this didn't succeed, it downloaded the complete 10.3.3 Package (2,2 GB) OTA, and installed that via TWRP with no problems whatsoever. I lost Magisk, which i needed to reinstall, but other than that, everything's fine.
Edit 2: The complete package obviously also overwrites TWRP, which i had to reinstall, too.
Click to expand...
Click to collapse
reagarding edit 2: which twrp did you use? I have real problems after the update, as the phone has no wifi now and the recovery is not working anymore
I also want to know if there's a place to get flash able zips through twrp for the latest eu roms.
lvnatic said:
I also want to know if there's a place to get flash able zips through twrp for the latest eu roms.
Click to expand...
Click to collapse
Here you can get all the official ROMs, fastboot and recovery
https://xiaomifirmwareupdater.com/archive/miui/raphael/
magdap said:
reagarding edit 2: which twrp did you use? I have real problems after the update, as the phone has no wifi now and the recovery is not working anymore
Click to expand...
Click to collapse
sorry i'm late with an answer, but i always use the newest version of mauronofrios TWRP (https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363).
Robbo.5000 said:
Here you can get all the official ROMs, fastboot and recovery
https://xiaomifirmwareupdater.com/archive/miui/raphael/
Click to expand...
Click to collapse
Thanks, can I flash the file using twrp and keep the recovery?
lvnatic said:
Thanks, can I flash the file using twrp and keep the recovery?
Click to expand...
Click to collapse
You will need to flash Magisk immediately after the ROM to stop MIUI restoring stock recovery.