Related
I have S off by way of Rumrunner on an HTC One Verizon. I have TWRP as recovery and i am completely stock just S off and superuser. When i accept the OTA from Verizon it boots into recovery and TWRP pops up and i am stuck from there. I cant find the file to install and the phone wont upgrade. Please help. Thanks
lan04 said:
I have S off by way of Rumrunner on an HTC One Verizon. I have TWRP as recovery and i am completely stock just S off and superuser. When i accept the OTA from Verizon it boots into recovery and TWRP pops up and i am stuck from there. I cant find the file to install and the phone wont upgrade. Please help. Thanks
Click to expand...
Click to collapse
You need to be on stock recovery as well to take the OTA. Check the bottom of post 2 of this
mademan420 said:
You need to be on stock recovery as well to take the OTA. Check the bottom of post 2 of this
Click to expand...
Click to collapse
ok i flashed stock recovery and it accepted the OTA thanks....now how do i get superuser privileges back...it says i am missing the binary
lan04 said:
ok i flashed stock recovery and it accepted the OTA thanks....now how do i get superuser privileges back...it says i am missing the binary
Click to expand...
Click to collapse
i reinstalled TWRP and flashed superuser from TWRP recovery...all seems well now thanks...btw the stock files would not go into recovery it simply went to black screen and rebooted
You mist be new. Never take otas if you need to update after soff and root do so via flashing the rooted ROM of the newest update.
Sent from my One using Tapatalk
yes i am new and trying to learn...thanks for advice
So, am I correct in understanding that my phone will not take the OTA with twrp installed? As in nothing to worry about?
Is there any command I can run in terminal to make it stop asking if I want to install the OTA?
Sent from my stock (but rooted) VZW HTC One
BaBnkr said:
So, am I correct in understanding that my phone will not take the OTA with twrp installed? As in nothing to worry about?
Is there any command I can run in terminal to make it stop asking if I want to install the OTA?
Sent from my stock (but rooted) VZW HTC One
Click to expand...
Click to collapse
Just follow the 2nd post here, then reflash TWRP. The OTA doesn't break root.
Does Voodoo OTA Root keeper work on the HTC One?
Please delete if off topic!
edster00 said:
Does Voodoo OTA Root keeper work on the HTC One?
Please delete if off topic!
Click to expand...
Click to collapse
Yes, I just used Voodoo today to restore root after taking the .15 OTA. Will not work after 4.3, though (according to Google Play).
lan04 said:
i reinstalled TWRP and flashed superuser from TWRP recovery...all seems well now thanks...btw the stock files would not go into recovery it simply went to black screen and rebooted
Click to expand...
Click to collapse
I can confirm this works fine as well. I had S-OFF through rumrunner and had flashed TWRP. To take the OTA, I re-flashed the stock recovery (.10) from the link given in this thread, then took the OTA. After the OTA installed with no problems, I re-installed a recovery (I changed to CWM, just for fun). I tested it by booting into recovery, and when I rebooted from CWM, it asked me if I wanted to re-install root (su). The phone now has the OTA (.15), still has SOFF and root was easily recovered.
I flashed the .10 stock recovery and I'm getting an error when I try the ota, any ideas why? I followed these instructions and I end up with a red triangle with exclamation point the reboot and phone works fine. Thanks for any help.
Edit:I got the congratulations message but when I checked it says failed, error 410. I've downloaded it a couple of times.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Every time I click update on my developer mode M8, it restarts automatically in the TWRP recovery mode. I have no choice but to reboot in recovery mode and the phone loads again asking me to update. Has anyone experience this? I am still on the stock ROM withe XPosed installer if that matters. Any suggestions will be appreciated, thank you!
spankyou said:
Every time I click update on my developer mode M8, it restarts automatically in the TWRP recovery mode. I have no choice but to reboot in recovery mode and the phone loads again asking me to update. Has anyone experience this? I am still on the stock ROM withe XPosed installer if that matters. Any suggestions will be appreciated, thank you!
Click to expand...
Click to collapse
Do you have a TWRP backup? You could restore it in TWRP if so.
jdk2 said:
Do you have a TWRP backup? You could restore it in TWRP if so.
Click to expand...
Click to collapse
I have a some of backups I created manually a couple of days ago but how would a restore of those backups update the system to 1.54.15409? Don't the phone still has to download the system update again?
You are asking for trouble trying to update on rooted, custom recovery and xposed framework installed..
Soff, Revert to stock, flash stock recovery, and then update
sent from my mobile device
SaHiLzZ said:
You are asking for trouble trying to update on rooted, custom recovery and xposed framework installed..
Soff, Revert to stock, flash stock recovery, and then update
sent from my mobile device
Click to expand...
Click to collapse
Oh I see. In that case I'll just get one of the custom ROMs from here that will have the new system update. Thank you!
Phone has to be 100% stock, inc. the stock recovery and kernel, to flash an OTA file as it checks to make sure the phone is stock. ANY change to the original system and it'll fail
EddyOS said:
Phone has to be 100% stock, inc. the stock recovery and kernel, to flash an OTA file as it checks to make sure the phone is stock. ANY change to the original system and it'll fail
Click to expand...
Click to collapse
How can I get to stock? I can't find it anywhere but people saying to do it. (other than Sprint, but i have unlocked)
BookOfRick said:
How can I get to stock? I can't find it anywhere but people saying to do it. (other than Sprint, but i have unlocked)
Click to expand...
Click to collapse
You have to have firmware that matches your hboot, and stock recovery. Doesn't matter if you are unlocked.
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Norcalz71 said:
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Click to expand...
Click to collapse
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then let TWRP install SU. I actually just did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
I'm pretty sure it works the same for lollipop now too. Originally you needed to flash a special kernel, but I think now you can root it the same way as Kit Kat, ie. via recovery. Someone can correct me if I'm wrong but I don't think I am.
_MetalHead_ said:
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then TWRP install SU. I did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
Click to expand...
Click to collapse
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Norcalz71 said:
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Click to expand...
Click to collapse
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
_MetalHead_ said:
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
Click to expand...
Click to collapse
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Norcalz71 said:
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Click to expand...
Click to collapse
No prob bud. One of the big benefits of Nexus devices is that they are super simple to root. Heck, they are super simple to do pretty much anything on. That's the only reason why I decided to start from scratch yesterday, because it's like nothing to do. The longest part was re-downloading all my apps, but still the whole process took about 30 min start to finish. If you're not downloading a ton of apps, it'll take you 5 minutes.
Hello I was able to easily root the newly released 6.0 update for the sprint galaxy s6.
First download
Cfroot for the G920F model
Download
Flash with Odin 3.10.6 or higher..
Wait for the script to finish etc and once the phone reboots, force the phone into download mode and flash the stock 6.0 recovery
Download
Then force the phone back into recovery mode and wipe cache then reboot phone back to system
Enjoy rooted 6.0 MM !
Props to the mighty Chainfire and his wizard skills
ok am i waiting when it attempts to boot recovery or just press the buttons to boot it into download again to re flash the stock recovery?
All we need now is twrp. I havent tried this root process yet.
weirdfate said:
ok am i waiting when it attempts to boot recovery or just press the buttons to boot it into download again to re flash the stock recovery?
Click to expand...
Click to collapse
after flashing cfroot you must wait until it finished the process..it will take a min...then after cfroot tells you it's done rooting the phone...you flash the stock recovery
Sunderwear said:
after flashing cfroot you must wait until it finished the process..it will take a min...then after cfroot tells you it's done rooting the phone...you flash the stock recovery
Click to expand...
Click to collapse
i must be doing it wrong then? it attempts to boot a recovery that is not seandroid enforcing last time i tried to install the custom recovery that was for the older firmware it stuck on that screen for ever and i needed to reflash my phone. just a little worried that its gonna get stuck there.
thank you for finding this root method
weirdfate said:
i must be doing it wrong then? it attempts to boot a recovery that is not seandroid enforcing last time i tried to install the custom recovery that was for the older firmware it stuck on that screen for ever and i needed to reflash my phone. just a little worried that its gonna get stuck there.
thank you for finding this root method
Click to expand...
Click to collapse
for me it was stuck in seandroid enforcing for like 1-2 mins...then it went to the cfroot screen
Sunderwear said:
for me it was stuck in seandroid enforcing for like 1-2 mins...then it went to the cfroot screen
Click to expand...
Click to collapse
yep
i waited then it went into cfroot
we got a dump of the stock recovery (im assuming thats what the other file is to flash) so im sure it wont be long till we get a custom recovery:good:
Confirmed, works for boost mobile 6.0.1 marshmallow.
Would TWRP 3.0.0 work with this or are we gonna have to wait for that update? Need my xposed modules for sure
We dont need a MM twrp....the current twrp will work just fine to flash a MM custom rom, someone just needs to make a rom.zip we flash it on top of LP and profit.
rafyvitto said:
We dont need a MM twrp....the current twrp will work just fine to flash a MM custom rom, someone just needs to make a rom.zip we flash it on top of LP and profit.
Click to expand...
Click to collapse
I also just realized that xposed won't work without a deodexed rom
122ninjas said:
I also just realized that xposed won't work without a deodexed rom
Click to expand...
Click to collapse
Can't we use flashify to install zip files? I've used xposed on stock ROMs before I thought.
will this work for 925p?
Awesome now i can mess with titanium backup. . Thanks Guess supersu is not working it says no su in the binary. Redid the steps i used odin 3.10.7 it didnt boot after the cfauto was flashed it actually booted into recovery is not seandroid enforcing. forced into download mode pushed down restarted again it went to the recovery is not seandroid enforcing screen. So i flashed the recovery cleared cache phone booted thought i was good to go nope lol. Also the same happened when i tried the twrp with odin but i had to flash the rom to get back up and running so heads up.
Guys I would definitely wait for a custom recovery. What if something happens and you have no backup?! Also, you need a deodexed ROM for Xposed to work anyway! This method would be good if all you care about is little stuff like AdBlocking.
you don't need deodexed rom anymore there is an exposed that work on 5.1.1 adn 6.0 but we just need a recovery to flash it.
but i agree i would wait to have a confirmed recovery for marshmallow
cyberone3 said:
you don't need deodexed rom anymore there is an exposed that work on 5.1.1 adn 6.0 but we just need a recovery to flash it.
but i agree i would wait to have a confirmed recovery for marshmallow
Click to expand...
Click to collapse
Prettttyy sure you need a deodexed ROM.
link below is the exposed i have been using on "stock" rom 5.1.1 and there is a 6.0 version i was on 5.1.1 no changes other than root
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
"Samsung made a lot of changes to ART without providing the sources, that's why it took a while to workaround some of their changes, more information here.
It supports Stock and close to stock Roms."
cyberone3 said:
link below is the exposed i have been using on "stock" rom 5.1.1 and there is a 6.0 version i was on 5.1.1 no changes other than root
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
"Samsung made a lot of changes to ART without providing the sources, that's why it took a while to workaround some of their changes, more information here.
It supports Stock and close to stock Roms."
Click to expand...
Click to collapse
I'm totally down to be a test dummy lol. Can anyone explain if flashify would be a replacement for recovery? I know the international folks used it to prevent certain things from tripping Knox, but at this point I'm pretty sure we all have tripped it by now
JoeFCaputo113 said:
Guys I would definitely wait for a custom recovery. What if something happens and you have no backup?! Also, you need a deodexed ROM for Xposed to work anyway! This method would be good if all you care about is little stuff like AdBlocking.
Click to expand...
Click to collapse
southernstyle said:
I'm totally down to be a test dummy lol. Can anyone explain if flashify would be a replacement for recovery? I know the international folks used it to prevent certain things from tripping Knox, but at this point I'm pretty sure we all have tripped it by now
Click to expand...
Click to collapse
flashify didn't work when i tried it wants twrp or cwm
So I got bored today. I decided to give MM another go. BIG mistake. I can't get back to lollipop. I made a TWRP backup but restoring from it gets stuck on the Samsung screen. It just says Kernel is not seandroid enforcing. I installed MM via odin and it must of upgraded the boot loader because now when I try to flash 5.1.1 via odin I get sw rev check fail device 4 binary 3 on my phone. HELP! I can't even get MM past the "LTE Plus" boot screen on MM. Any advice would be wonderful! Otherwise my s6 is a nice paperweight and I'm stuck without a phone
AFAIK, if you are on one of the 3-4 latest MM builds, you CANNOT go back to 5.1.1 anymore.
Samsung added the anti-downgrade function to those builds already.
You cannot downgrade as yaibakt pointed out. After installing the latest MM version via Odin, boot to stock recovery and wipe all user data. It will boot then.
Sent from my SM-G920P using Tapatalk
@Poebat, may I offer to help a bit? You won't be able to roll back, but you'll feel a whole lot better about what you have.
Follow my guide here to get up to the latest firmware, rooted and with TWRP: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Then install the latest BiggDaddy ROM: https://forum.xda-developers.com/sp...pment/biggdaddypi3grace-ux-rom-6-0-1-t3484252
Play around with the many options. It is a great ROM.
yaibakt said:
AFAIK, if you are on one of the 3-4 latest MM builds, you CANNOT go back to 5.1.1 anymore.
Samsung added the anti-downgrade function to those builds already.
Click to expand...
Click to collapse
Damn. Last time I tried I was able to downgrade. I assumed I would be able to do the same with the latest. I'm a genius. Thanks for the heads up.
koop1955 said:
@Poebat, may I offer to help a bit? You won't be able to roll back, but you'll feel a whole lot better about what you have.
Follow my guide here to get up to the latest firmware, rooted and with TWRP: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Then install the latest BiggDaddy ROM: https://forum.xda-developers.com/sp...pment/biggdaddypi3grace-ux-rom-6-0-1-t3484252
Play around with the many options. It is a great ROM.
Click to expand...
Click to collapse
Will do! I'd like to have my phone working again