Database Info

[Q] Switch from CWM to TWRP

I have CWM installed now, but I need to RMA because of some excessive screen bleeding in the upper left corner of my N5. On the return to stock thread, there is a section that involves resetting the tamper flag, and it says that it works best with TWRP.
I've only used CWM before, so can I just download TWRP and flash it in adb the same way I initially installed CWM?
Thanks for any help.

vinnycogs820 said:
I have CWM installed now, but I need to RMA because of some excessive screen bleeding in the upper left corner of my N5. On the return to stock thread, there is a section that involves resetting the tamper flag, and it says that it works best with TWRP.
I've only used CWM before, so can I just download TWRP and flash it in adb the same way I initially installed CWM?
Thanks for any help.
Click to expand...
Click to collapse
yes just download the .img from twrp website and flash in recovery. "fastboot flash recovery filename.img"

Boblank said:
yes just download the .img from twrp website and flash in recovery. "fastboot flash recovery filename.img"
Click to expand...
Click to collapse
awesome thanks man, that worked perfectly. one other question if you know this, when I do the factory reset in CWM and in TWRP, it seems to get hung up and never finishes. Is there anything I can do to make sure that it fully wipes?
I was going to play around with a few ROMs before my new N5 gets here.

vinnycogs820 said:
awesome thanks man, that worked perfectly. one other question if you know this, when I do the factory reset in CWM and in TWRP, it seems to get hung up and never finishes. Is there anything I can do to make sure that it fully wipes?
I was going to play around with a few ROMs before my new N5 gets here.
Click to expand...
Click to collapse
I don't know why TWRP hangs during factory reset, but you can get the same result using fastboot. Just flash the userdata partition and erase the cache partition.

[Q] TWRP flash says successful... but stock recovery is still there?

Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?

fastboot reboot-bootloader ; just after recovery flash.

Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.

Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon

I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!

theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon

cube power m3 tablet TWRP img

Caution!
i have no responsibility if your device bricked
What i read
https://www.techora.net/port-twrp-for-mediatek-64-bit-mt67xx.html
TWRP img based on
https://forum.xda-developers.com/coolpad-note-3/development/note3-t3572794
tools
SPFlash Tool https://spflashtool.com/
Android scatter file and twrp.img
https://goo.gl/CAij4G
1. Download flash tool, scatter file and twrp.img. place them in same folder
2. Load scatter on flashtool and choose recovery. *download only
3. turn off your tablet and connect to pc
4. will be install
I make this img with linked tutorial, and coolpad img file
Choose it cause same cpu model
to install some zips from twrp you need SD card
i dont know why it doesnt read internal storage, adb sideload
Magisk install worked and module looks fine
Didn't try Xposed
I'm not dev
i just one who knows a bit how device work
(with lot bricked devices in my storage)
Might can't answer your questions
I'm not used to on xda forum, so i don't know where to post unlisted device things
https://drive.google.com/open?id=0Bzm7uALjk4svNG0tVjhHSkJFUUZwYW0yQkh6Yk0tTE95djRj
https://drive.google.com/open?id=0Bzm7uALjk4svOURqaUt1ZE9pM0lxS25IQ2NNNTBERGRTVFBn
https://drive.google.com/open?id=0Bzm7uALjk4svOTZ5bWRETmVWaUhDYWJzUV9UTHI5dWpVZy1z

and unlock OEM bootloader with dev option

My Cube Power M3 is now rooted with your twrp file. I just had to use my original scatter file because it didn't worked with yours.
Thank you

... my mistake ... all your files are ok
Good work

mrtee03 said:
... my mistake ... all your files are ok
Good work
Click to expand...
Click to collapse
sometimes work, sometimes not
when try to flash all, or use original boot.img for loading scatter and change it will work
i might have to upload original one later

You're right, that's what I did

chocodesk said:
sometimes work, sometimes not
when try to flash all, or use original boot.img for loading scatter and change it will work
i might have to upload original one later
Click to expand...
Click to collapse
Add some files and flash guide
New link is here
https://goo.gl/CAij4G
It was first time to share my files so i forgot to change link option as public
Sorry for that guys

thank you

Hi guys, I need some help.
I just flashed the TWRP included in Google Drive, everything went fine, the flashing was successful.
I then booted to recovery, TWRP Recovery was installed, I swiped to allow partition modification as asked.
Then I rebooted and was stuck on the Alldocube logo for several minutes.
I tried flashing the original recovery you included back again and same problem, I'm stuck on boot logo :/
Any idea how to deal with this ?
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
I've just tried Wiping Cache and Data / Factory Reset from original Recovery, but still stuck :/

OK guys, I flashed the whole original firmware back in and it's solved the problem.
I guess no TWRP recovery for me :/

PiNgOa said:
OK guys, I flashed the whole original firmware back in and it's solved the problem.
I guess no TWRP recovery for me :/
Click to expand...
Click to collapse
i had same problem and solved with twrp availiable,
but i refund this tablet long ago
i dont remember
sorry for i cant help

worked perfectly to get TWRP, Magisk 16.4 on device running Stock ROM - thank's !

edit

PiNgOa said:
OK guys, I flashed the whole original firmware back in and it's solved the problem.
I guess no TWRP recovery for me :/
Click to expand...
Click to collapse
i think you should flash magsik via twrp
remove system verify

anybody knows how to get lineage 17.1, magisk and twrp on ALLDOCUBE X1 ?

bootloop after using twrp (can't start smartphone, please help!)

i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.

TobiS137 said:
i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
Click to expand...
Click to collapse
Enter fastboot, flash official twrp.Flash magisk in twrp.

vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
can you help me further? as i said i am a huge newbie and i only understood a little of that. is there any other ways you can contact me?

vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
Can you explain what exactly were you doing ?!

Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?

I'm new to this while A/B partition. I went through all the steps and my phone is rooted, with Magisk and TWRP. All seems to be fine. My question is this. When I boot to the recovery (TWRP) and choose the reboot option it defaults to Current Slot: Partition B. If I reboot to partition B it goes back to TWRP. I have to select Partition A to get the device to boot to the system.
Is this normal? Do I need to set it up in a different way?

samteeee said:
Can you explain what exactly were you doing ?!
Click to expand...
Click to collapse
i was trying to root the phone (wich i did) and then the twrp app that was on my phone after i had tried to install it using the img. it then turned into an ap that told me to update it in google play
after that was done i tried to flash it but everytime i tried it just crashed. a little time later after trying some more times i found that i started it in the bootloader and it ended up with me stuck in a bootloop. again i might not have explained enough. i am huge noob so i really need help.

ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\ . Does it change anything that i use twrp enchilada or does that not matter?

ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\

discord
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.

TobiS137 said:
i think i did fastboot boot twrp. still not sure tho :\
Click to expand...
Click to collapse
To keep TWRP as the phones recovery, you'd first need to do as you did "Fastboot boot twrp" but that command will only allow you to boot into TWRP through your pc or whatever you ran that command on. After you've entered that temporary recovery, you'll need the TWRP installer .zip file, and flash that inside of that temporary TWRP. Then you can reboot into recovery on your phone again since it has been installed to one of the partitions.

TobiS137 said:
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
Click to expand...
Click to collapse
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about

phone open again
my phone is back up and running again. i changed the partitian slot from A( the broken one with no OS) to B(the unchanged one) and it is now working again. if anyone is having the same problem the try to change to the second slot. it happend in twrp enchilada 3.2.2-0 if it is important. thank you all for your support.

I may be mistaken but I believe all you need to do is flash magisk to get up and running again

hallo dare said:
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
Click to expand...
Click to collapse
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.

RusherDude said:
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
Click to expand...
Click to collapse
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.

iElvis said:
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
Click to expand...
Click to collapse
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...

RusherDude said:
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
Click to expand...
Click to collapse
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.

iElvis said:
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
Click to expand...
Click to collapse
I am not denying anything! just surprised because on TWRP website they clearly state that no post-twrp-flashing step is needed:
https://twrp.me/oneplus/oneplus6.html
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel.
Click to expand...
Click to collapse
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?

RusherDude said:
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
Click to expand...
Click to collapse
I think most people have moved to the official version. If it doesn't need magisk to avoid a bootloop, that's news to me. Not saying it's not the case, but I haven't seen any mention of it.

i accidentally flashed a custom rom over oxygenos lol help (really though help)

Hi.
So this was pretty stupid of me. I was trying to flash LiquidRemix onto my OP6, but I forgot to wipe the system partition. Flashed the rom, then blu_spark twrp, and rebooted into recovery to flash gapps and all. Got a black screen with a static LED. Didn't think that was a big issue cause this has happened before with normal TWRP on OB6 or OB7. Tried hard resetting to see if I could get into system, same result. Tried fastboot flashing 9.0.2, no help. And finally tried flashing OB9 via fastboot, and also no help.
I've reverted back to my tiny S6 and have sent repair request to OP. I haven't gotten anything back yet, so I thought in the mean time, I'd look for help on XDA and try to fix it before having the chance to send it in.
Any help/advice would be greatly appreciated.
Cheers
// EDIT
Figured out how to fix it. Used the MSMDownloadTool to unbrick my device. Worked wonders. Thanks to r/oneplus Discord

I did something like that I had to format data after I flashed the stock rom

mightyblazer said:
I did something like that I had to format data after I flashed the stock rom
Click to expand...
Click to collapse
How did you get to format? I really can't get into the OS or recovery at all

I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again

mightyblazer said:
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
Click to expand...
Click to collapse
I'm able to get into fastboot, but even if I fastboot boot [insert twrp file name here], it'd still result in the blank screen and static LED

Hmm I don't know then sorry

Try
fastboot flash boot twrp.zip
Then
fastboot reboot
You will need to use full stock rom first before doing anything else though.

I was in the same boat as you the other day. I flashed different versions of twrp until i managed to boot one because some twrp isn't compatible with pie.

Lol I never wipe system...

Might sound like a "hard-bricking" issue since you cant boot into the OS nor recovery. There 's a hard brick recovery guide, but it'll put you down to oreo OOS: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
As long as you can boot into fastboot, you can follow the guide's process with no problem.