Rooted, TWRP installed but no OS... - One (M8) Q&A, Help & Troubleshooting

Guys, I rooted some time ago but phone has been acting up lately.
I thought I'd factory reset from TWRP but must have selected to wipe the lot
Now hangs on htc logo (with the red text warning about Dev rom only) and when I can get into recovery, I have no rom to flash.
Question is: Will flashing remove root or is there a rom I should use?
I was thinking about downloading rom from htc site...

Yes you can flash the stock firmware to return to normal then if you prefer to do root again use twrp an magisk root

Xeeon2 said:
Yes you can flash the stock firmware to return to normal then if you prefer to do root again use twrp an magisk root
Click to expand...
Click to collapse
Thanks, figured I'd lose root but only wanted it to get rid of some bloat and try some battery saving apps.
Do you know if I will have to unlock the bootloader again?
BTW, isn't magisk only for M8? I have M8s...

if your phone S-Off flash stock without locking bootloader if S-ON you have to lock it
but I wanna ask you something about the battery, how long does it stay in normal use because mine doesn't live much only a few hours and when I play games it heats like hell

Xeeon2 said:
if your phone S-Off flash stock without locking bootloader if S-ON you have to lock it
but I wanna ask you something about the battery, how long does it stay in normal use because mine doesn't live much only a few hours and when I play games it heats like hell
Click to expand...
Click to collapse
Thanks again.
Battery really sucks - four/five hours and that's not playing games.
I wanted root because I wanted to try greenify, exposed, and stop some wakelocks but to be honest, they didn't help a great deal.

OK so, I have a twrp backup on my sd card which will not restore - says 'mounted read only'
I am also unable to install an RUU (from here: ruu.lalleman.net/HTC_M8S) just fails.
Do I need an RUU or can I use a stock ROM and do I need to use HTC_Fastboot?

Download this RUU
and flash it with this fastboot
boot to normal and apply the latest OTA
then flash this TWRP
and boot to TWRP and make a Nandriod backup just in case anything wrong happens
and a the end use the Magisk root from this thread
then you will have a stock rooted stable ROM with Latest Updates

Man, you're a star. Many thanks for your help and advice.
I did find out why I couldn't restore my twrp backup, it seems 2.8.6 is a bit buggy and I had to mount/unmount and mount partition again to make it writable.
Got the handset up and running and was going to flash twrp 2.8.7 but think I'll follow you plan through from start.
Once again many thanks.

beaverHausen said:
Man, you're a star. Many thanks for your help and advice.
I did find out why I couldn't restore my twrp backup, it seems 2.8.6 is a bit buggy and I had to mount/unmount and mount partition again to make it writable.
Got the handset up and running and was going to flash twrp 2.8.7 but think I'll follow you plan through from start.
Once again many thanks.
Click to expand...
Click to collapse
You are always welcome

Related

HTC m9 - Bootloop After Installing BETA SuperSU 2.68 - Running TWRP 3.0.0-2

Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
cloves said:
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
Click to expand...
Click to collapse
Restore your boot partition or dirty flash rom
Fixed
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
cloves said:
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
Click to expand...
Click to collapse
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
willardwellls said:
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
Click to expand...
Click to collapse
Flashed via twrp 3.0.0-2
This is the file:
https://download.chainfire.eu/752/SuperSU
FYI, if you are flashing a ROM, sometimes they have superSU already built in. So no need to flash your own superSU. That is the case with Viper ROM. Also make sure your firmware matches the firmware that the rom is using.
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Just had the same problem. Put on 2.65 and it's now booting into the OS. Thanks!
Thanked God i found this post, tried latest stable also beta seems bootloop never ends. Try v2.6 all become alive. Many thanks Sir
Same problem after installing latest SuperSu version from TWRP recovery: eternal bootloop. I didn't know what was wrong and tried different supersu versions but I became reluctant to keep trying that method after the second time... Gladly, I found your thread before doing anything else (even posting myself a thread) and now I can continue my evil rooting plans :victory: Thank you for asking and thanks for replying you prevented me to re-lock my phone and do everything from scratch. It's my first root
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
cloves said:
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I beg to differ about xposed. One wrong mod and you're phone is bricked.
Beamed in by telepathy.
I have not had any problems with exposed and that's why I said make a backup on your card. I have installed multiple Xposed modules and have not had any issues I have not seen anybody break the phone either. As I mentioned make a trip back up what is the point of rooting your phone if you're not going to use it to its full potential that's just me
Sent from my HTC One M9 using Tapatalk
Me too - Bootloop
I have an AT&T HTC One M9. Bootloader is HtcDev Unlocked, S-On, and TWRP is installed...
I previously messed up my phone bad by trying to install a OS ROM that didn't work right... So, I used my PC to overwrite it with the HTC OTA version, and that worked. I went into the M9 and tried to download and run SunShine, to get S-OFF, but it said it couldn't temproot, I don't know why, it's pissing me off, and SunShine suggested I root the device with another means. I downloaded SuperSU 2.69 and tried that, it installed okay (I guess) and said it might loop a few times. Try 100! Infinite loop. I tried SuperSU 2.65, but it said, "it's already patched!" and the system ROM had not been backed up. (I'm assuming SuperSU patches whatever is in the system partition?)
Anyhow, it's currently stuck in an infinite loop. I'm going to try re-putting the HTC OTA system ROM on it (great, I lose another half-day at this), and then re-try SuperSU 1.65.
Any idea why SunShine won't S-OFF a device? Why won't temproot work? Any other (good) way to root it?
Twrp question?
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
thanks dude
Skorpyun812 said:
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Click to expand...
Click to collapse
i am stuck and say my phone going to crab but your post save me
cheers
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
White91 said:
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
Click to expand...
Click to collapse
i think your s-on on bootloader mape it off then install recovery

[ROM] MOAR MM Rom v4.1 - Toasted Edition - 07/22/2016

Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues
and if I'm on note 5 moar rom with patch.... no issue flashing right?
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.
MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/
yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?
bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.
Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

OnePlus 3 keeps booting into TWRP Recovery Mode - PLEASE HELP!!

I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
SOLVED : I flashed TWRP 3.0.3 once again and somehow it got fixed
'' doing a wipe help you bypass the password''... Well yes probably, but depending on what type of wipe, you might have wiped your rom/system. So if that is the case, there is no rom to boot into, and your stuck in twrp recovery. Restoring an empty Nandroid wont do anything either. So my guess is you will have to download stock or custom rom and do a fresh install.
If needed, this method works very well.
I used it to day, with success.
Good luck !
Thank you. but will this work with latest TWRP 3.0.3 or will i have to use old one as mentioned in that post?
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
rshah0429 said:
I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
Click to expand...
Click to collapse
Had the same problem and panicked like hell. I just switched a few twrp recoveries (modded and official) and found one that worked and phone booted.
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
thank you. i will try this
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
I can't find TWRP 3.0.4.0 Can you please link it?
rshah0429 said:
I can't find TWRP 3.0.4.0 Can you please link it?
Click to expand...
Click to collapse
See Here
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img
Its not official but working for me...
Try flashing the stock recovery. I got stuck in recovery loop after the OTA update got installed over twrp. Flashed the stock recovery and right away it booted me to the rom.
It's a problem of older twrp with nougat so you need to flash twrp new version

TWRP temporary?

I'll have my new OP7T by Friday, coming from OP5T. I've been reading through some of the threads. Is it correct that TWRP doesn't survive a reboot? Or is that old news?
That might be fine for me. I don't flash roms nearly as much as I used to and I think stock rooted is the way I'll go from now on.
So if I unlock the bootloader, install TWRP and root... can I then receive Ota updates?
That'd be pretty awesome.
***Also I'm tempted to flash a custom rom despite what I said . So if anyone knows of a stable one that performs well as a daily driver, please respond. Thanks
KLit75 said:
I'll have my new OP7T by Friday, coming from OP5T. I've been reading through some of the threads. Is it correct that TWRP doesn't survive a reboot? Or is that old news?
That might be fine for me. I don't flash roms nearly as much as I used to and I think stock rooted is the way I'll go from now on.
So if I unlock the bootloader, install TWRP and root... can I then receive Ota updates?
That'd be pretty awesome.
***Also I'm tempted to flash a custom rom despite what I said . So if anyone knows of a stable one that performs well as a daily driver, please respond. Thanks
Click to expand...
Click to collapse
Hi! If you BOOT twrp it will not survive a reboot, if you FLASH twrp it will still there till you reflash stock recovery or rom update. You can't receive OTA "upgrade" package with root, only full rom, maybe through oxygen updater.
And last, i've flashed Resurrection Remix this saturday, and it's amazing. Battery performance like stock oos (about 5/5:30h sot against the 4h sot of my previous op6), 90hz display and infinity customization to choose from. You're not going wrong if you try RR, trust me. RR on my "old" oneplus 6 was not like this. Here there's no bug at all and you can customize everything. Only thing that i miss is Dolby Atmos (it's still there but you can't personalize sound effect WIP in next release) and per-app lock with FP (not really a great miss).
I hope to be proved helpful
Hitman478™ said:
Hi! If you BOOT twrp it will not survive a reboot, if you FLASH twrp it will still there till you reflash stock recovery or rom update. You can't receive OTA "upgrade" package with root, only full rom, maybe through oxygen updater.
And last, i've flashed Resurrection Remix this saturday, and it's amazing. Battery performance like stock oos (about 5/5:30h sot against the 4h sot of my previous op6), 90hz display and infinity customization to choose from. You're not going wrong if you try RR, trust me. RR on my "old" oneplus 6 was not like this. Here there's no bug at all and you can customize everything. Only thing that i miss is Dolby Atmos (it's still there but you can't personalize sound effect WIP in next release) and per-app lock with FP (not really a great miss).
I hope to be proved helpful
Click to expand...
Click to collapse
Thanks for the explanation!
Sorry I'm still unclear on TWRP. I remember years ago I had a device that would not allow TWRP to stick. If you needed to flash a rom or make changes to system, you'd hook it up to your computer and use adb to boot TWRP one time.
But that was because twrp wouldn't stick. Why would you boot TWRP if you are able to make it permanent by flashing it?
I'm sure there's a simple explanation but I can't think of it...
Ideally I think I'd keep the stock recovery with root, then remove root for an update and root again. But pretty sure the only way to root is to have TWRP installed.
Thanks again for the info!
KLit75 said:
Thanks for the explanation!
Sorry I'm still unclear on TWRP. I remember years ago I had a device that would not allow TWRP to stick. If you needed to flash a rom or make changes to system, you'd hook it up to your computer and use adb to boot TWRP one time.
But that was because twrp wouldn't stick. Why would you boot TWRP if you are able to make it permanent by flashing it?
I'm sure there's a simple explanation but I can't think of it...
Ideally I think I'd keep the stock recovery with root, then remove root for an update and root again. But pretty sure the only way to root is to have TWRP installed.
Thanks again for the info!
Click to expand...
Click to collapse
With oos I was usually boot with twrp only for flashing magisk, in that case i don't really need it beside for flashing root. With RR I keep twrp flashed only "to have it" not really useful. I understand what you said, with old partition system root gone away without twrp because recovery.img was inside boot.img (magisk destination partition, and for decryption things) but with Android 10 these partitions are separated again, like old times.
Hitman478™ said:
With oos I was usually boot with twrp only for flashing magisk, in that case i don't really need it beside for flashing root. With RR I keep twrp flashed only "to have it" not really useful. I understand what you said, with old partition system root gone away without twrp because recovery.img was inside boot.img (magisk destination partition, and for decryption things) but with Android 10 these partitions are separated again, like old times.
Click to expand...
Click to collapse
I think I'm following you. So if I want to remain stock but rooted, I would just boot twrp, root it, then repeat that if I want to take a stock update?
To simplify, I guess, is it possible to run a rooted stock with a stock recovery?
Sorry. I've been tinkering with my phones less and less, and some things have changed in that time.
Take the update, DO NOT REBOOT YET! Then install Magisk from the Magisk manager. When it says to select method, choose to "Install to Inactive Slot (After OTA)" , then reboot.
No TWRP needed after an update to install root.
KLit75 said:
I think I'm following you. So if I want to remain stock but rooted, I would just boot twrp, root it, then repeat that if I want to take a stock update?
To simplify, I guess, is it possible to run a rooted stock with a stock recovery?
Sorry. I've been tinkering with my phones less and less, and some things have changed in that time.
Click to expand...
Click to collapse
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Hitman478™ said:
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Click to expand...
Click to collapse
Thanks. I used to change roms constantly a few years back. Now my phone has become something I can't get by without, for even a matter of hours on some days. So as much as I love trying things out, I just want a stable driver with little fuss. But I don't think I can go without root. I haven't since 2013.
OOS was good enough for me, though I heard theyre becoming more bloated and I hate the gestures in Android 10. It's those little things that I want to be able to change.
Do you use the modified magisk boot image to root?
KLit75 said:
Thanks. I used to change roms constantly a few years back. Now my phone has become something I can't get by without, for even a matter of hours on some days. So as much as I love trying things out, I just want a stable driver with little fuss. But I don't think I can go without root. I haven't since 2013.
OOS was good enough for me, though I heard theyre becoming more bloated and I hate the gestures in Android 10. It's those little things that I want to be able to change.
Do you use the modified magisk boot image to root?
Click to expand...
Click to collapse
Yes I'm just like you, I use my phone constantly for work, I can't accept a rom with FC and other bugs.. I need that things working properly and RR it's exceptional.
Yes I was using modified boot.img for rooting OOS, selfmade with guide in the thread because my phone is the BA version (europe) and everytime no one post boot.img ready for this. But it's not really complicated to DIY
Hitman478™ said:
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Click to expand...
Click to collapse
I do not disable or uninstall modules with this method. But I will in the future, it only takes one OH SH!T moment, before you wish you did. My luck is bound to run out.
Droid_Nut said:
I do not disable or uninstall modules with this method. But I will in the future, it only takes one OH SH!T moment, before you wish you did. My luck is bound to run out.
Click to expand...
Click to collapse
:laugh: I've passed too much "bad moments" with update and magisk, so now prevention is my cure

Categories

Resources