Database Info

Can you restore a nexus s to "factory" settings to receive OTA updates?

Hi Guys, as subject really! Is it possible to get the phone in a "Google" state to pull down updates, obviously meaning the impending ICS one!
B

I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz

frutelaken said:
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
Click to expand...
Click to collapse
Hey mate, thankyou for helping. I've not actually received it yet, bought one off ebay and I am just pre-empting - If you flash stock does the root and unlocked bootloader become standard again??
(I'm upgrading from an old Galaxy 3, so am reasonably familiar with flashing, but want a simple life now and am going stock Google )
B

Nope, flashing a stock image will not affect your bootloader being unlocked. You'll have to run the "fastboot oem lock" command to lock the bootloader again. Check one of the turorials here
Greetz
//edit: Actually, I'm suddenly not sure of this. Sunday evenings' got me confused. Please wait for someone else to verify.

Thankyou I'll have a look round

I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.

n00bfuscator said:
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
Click to expand...
Click to collapse
That's normal, the OTA's reset the permissions on key folders, effectively SU looses it's execute permissions, removing root. What i do now is download the OTA to the SD card, apply it, re-apply the SU.zip to keep root, modify the restore-recovery script so i can keep CWM, then reboot.
I'm not sure how it's going to go with ICS, but we shall see.

Recommendations on OTA (ATT 4.0.3/4.0/1.73)

Hey all,
I rooted my HOX (1.73, 4.0.3) with the kpenn ne-Click a few days after I got it for the Tether and to de-bloat. Since then I haven't read anything on the One X till I heard Jelly Bean coming along. Anyhoo my question is what the upside of getting the new OTA (4.0.4) would be and how I would go about it if I wanted to (I've never updated before and ATT has stopped asking me to update, also I get nothing when I try to check for an update).
I've been reading around and it seems like most people are on to 1.85 and are flashing 4.1/2.2. My primary uses of my phone are for the media applications/web browsing and I haven't noticed any real drop in performance but I have heard the new updates have sped up the HOX considerably which is something I'm always interested in.
Thanks!

DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:

Shaddy-Z. said:
DON'T flash any OTA you will lose your root and will lose your ability to re root because there is no boot loader unlock for the new base. If you want to update and flash a new ROM and want to stick to sense, look at clean rom or xi40. Both are updated on the new base and are heaps and bounds better than the original ATT software :thumbup:
Click to expand...
Click to collapse
i one-clicked unrooted my phone earlier and freaked out (and the new updates didn't work out on my phone anyway). i ended up getting kpenn's one click again and putting SU back into my phone. Do you have any links that can take me on a step by step process of unlocking my phone and flashing those roms on it? I just love being able to control my phone and pushing it to its absolute limits.

Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.

Pbdeng said:
Sigh. I followed the tutorial but I made a few mistakes...
1) I unlocked my phone way earlier than I should have so I wiped everything before I could make a back-up..
2) Re-locked accordingly to see if I could keep updating. I did manage to get to 1.85 like the tutorial said but.....
3) Since I didn't have a custom recovery I wasn't sure how to proceed. I couldn't get the root to flash so I tried using the 1-click 1.85 root since my phone was running 1.85.
....This ended up updating to 2.2 so now I have an unlocked HOX 2.2/4.0.4. With all the bloat.
Dumb dumb dumb. Ugh.
Click to expand...
Click to collapse
it's UNLOCKED?
you're lucky then.
just push a recovery like twrp then push root. Then you can debloat.

Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.

Pbdeng said:
Yep, it's still unlocked. That was around the 4-7th reset I did (I messed up a lot). Do you have a link that shows me how to do that? I'm actually not as bummed about going to 2.2 since it runs so much faster than 1.73 did.
Click to expand...
Click to collapse
make sure you have your unlock token and then go to http://www.htcdev.com/bootloader/unlock-instructions/page-4/
and follow the directions.
after that look at this thread to install twrp http://forum.xda-developers.com/showthread.php?t=1777773
then this one to re-root
http://forum.xda-developers.com/showthread.php?t=1673935

I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.

Pbdeng said:
I notice one of the links is for 1.85. Does that mean that I'll go from 2.2 back to 1.85? I just wanted to make sure since my impression from the forums is that there is no 2.2 root yet unless it was flashed.
Click to expand...
Click to collapse
no those pages just tell you how to manually install root and recovery.
your bootloader is still unlockable
unlock it
then install a recovery
then install root via that recovery

Ahh, thanks a bunch man.

Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?

Pbdeng said:
Sorry if this is repetitive....
So I've checked my phone and currently it states that it is
"Re-locked"
I downloaded a recovery so it's currently on my phone. Furthermore I all ready had a copy of SU sitting in my phone's download folder.
Does this mean that I'm going to...
- Unlock bootloader (that is currently relocked) and have everything erased again.
- Reboot from recovery (of the evita 2.2.img I just downloaded with TWRP)
- Then flash the SU root I all ready have on my phone?
Click to expand...
Click to collapse
yeah unlock the boot loader. set up the phone again
then install the recovery then root.
to make your unlock stick, turn off fastboot in power options, then power down phone completely then restart it to the bootloader.

Hmm, so my phone is definitely unlocked now. I installed the recovery and I manually flashedthe new SuperSU in that link you posted for me. As far as I can tell nothing is happening.
Note: It says that it installs the recovery but there is no reboot that occurs. I've done this both with the android app and manually and nothing is happening.
I don't see SuperSU and rootchecker is confirming that my phone isn't rooted yet.

so you reboot to recovery, choose the superSU package to install then what happens?
I know this works I've done it quite a few times myself.

Presently I installed the latest img file with TWRP with the app. There is not reboot that occurs (unless I'm suppose to reboot on my own?). If that's the case then I've been a total idiot.
I've just been installing the openrecovery and then I press "Flash Roms" to flash the supersu. I get a little notification that says "Preparing to Flash" and then nada.

After you install twrp recovery you reboot. Then you boot to recovery and flash the super su zip manually

Wooh! I got it to work! Thank you so much!

Pbdeng said:
Wooh! I got it to work! Thank you so much!
Click to expand...
Click to collapse
No problemmo.

Does this also mean that I can flash any ROMs I want on my phone now?

Yes. But you will have to flash kernels aka boot.img separately using fast boot.

Jelly Bean OTA effects on rooting, unlocking bootloader etc...

Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app

GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Check out this thread over in the dev section.
http://forum.xda-developers.com/showthread.php?t=2046439

GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.

GoodVibrant-ions said:
Basically I'm asking before I apply the ORA whether or not it will be a harder, easier, or exactly the same process to get root and unlock the bootloader.
Any extra steps to flash or incompatible roms afterwards?
Just curious. I am not rooted but have studied the process to where I know I could if I wanted to. Wondering if applying the OTA will change what I already know and/or make it harder to get root.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.

Frunple said:
If you use cwm6 you won't lose anything. Accept the update, after booting into recovery cwm will ask if you want to install un trusted . zip. Say yes. It installs, just before reboot it will ask if you want to keep root, then ask if you want to keep custom recovery. Answer yes and you're good. It will reboot and say update failed but that's just because you kept the recovery. If you go to check for update it will say you are up to date.
Click to expand...
Click to collapse
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh

Knightvision said:
This is correct. Same thing happened on my rooted GS 3. The update menu said "failed" but the update did actually take.
But don't do what I just did: try to back up the ROM Manager. It will not make the phone happy. Now stuck at the soft brick screen. Argh
Click to expand...
Click to collapse
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.

BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
I can confirm that this method works. I used Voodoo to keep my root and then answered yes to allowing CWM to install the unsigned .zip and answered yes to keeping root. I then got the dreaded Verizon warning triangle and was prepared to Odin back to Stock and start over. Just by chance I went into download mode and it allowed me boot my Rom. Once in, I checked EZ-unlock and it said I was unlocked, so I went ahead and locked and then unlocked and all was good! Hope this helps saves someone else some hassle.

Real_JESRadio said:
I re rooted after going back to stock ICS. Verified root, then upgraded to OTA Jellybean. Root stayed via OTA Rootkeeper.
Click to expand...
Click to collapse
man I tried this but it didnt work rootkeeper says its rooted but no root access the super user app is there...could i have done something wrong?? do i have do something after i upgrade to get to work?? thanx

BigErnM said:
If you haven't already fixed it, this happened to me upgrading to the various JB leaks once when I forgot to re-unlock the bootloader and tried to boot into CWM recovery. It gave me the Verizon warning screen, but I was able to use the Vol. Down + Home method to get into download mode and then just had the phone reboot. It booted normally and then you can use EZ-unlock to unlock the bootloader again. It might tell you that it is already unlocked, which isn't right so lock it and then unlock it.
Click to expand...
Click to collapse
It's fixed now. The CMW recovery mode wasn't working for some reason. Whatever broke ROM Manager did so by breaking CMW Recovery. I blame myself for stupidly trying to run a backup like that. Anyway, all I could get was the triangle screen and it would only reboot to that or the CMW that wasn't working. Ended up putting it in Odin mode and reflashing with one of the no-wipe leaks. Works fine now. And VZW says I am up to date.
Will get around to rerooting/unlocking again later today. And smacking myself for getting into this mess.
Good to learn from mistakes that are not fatal. Good to have LOTS of resources to figure out how to bail it out too!

Can't seem to boot into recovery...

What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!

LifeAsADroid said:
What's up everybody. I've searched through the questions forum and can't seem to find a thread to help me, so...
I wanted to flash dhacker's 4.4 ROM. So first I want to make a backup of my phone pending something goes horribly wrong. I'm having issues booting into recovery. When I click on "recovery", the phone seems to restart like it's going into recovery, then I get a sleeping android bot with his belly open and a red triangle with an exclamation point in it on my screen, forcing me to reboot the phone. Any ideas?
- Is it that I don't have an updated version of CWM or TWRP? Anyone have links to working versions?
- Is it that I have the "lite" versions of said apps above and need to donate to open the recovery features?
- Is it something else and I'm just not smart enough to think of what it could be?
Thanks for the help!
Click to expand...
Click to collapse
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?

RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.

LifeAsADroid said:
Thanks, I'll give it a try.
I did at one point have an unlocked bootloader, but I wasn't sure whether the latest OTA updates only blocked the ability to unlock (if someone hadn't already unlocked) or if it locked back up the already unlocked ones.
Click to expand...
Click to collapse
once the bootloader is unlocked, it cant be locked back.

Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.

LifeAsADroid said:
Bonus. That's what I thought, something about creating a small nuclear explosion in the phone that destroys the bootloader locking resistor or something. Glad I took care of that prior to the update that shut the door on that exploit.
Something else I thought of... I'm reading that 4.4 makes it much harder to root phones. I guess we won't know until the OTA release comes out, but I'm hoping Voodoo Rootkeeper maintains root during the update like it has in the past for me in previous updates.
Click to expand...
Click to collapse
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.

so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
RikRong said:
If your bootloader is unlocked, you don't need to maintain root. You just need to flash a SU zip in recovery.
Click to expand...
Click to collapse

peladoro said:
so if i unlock my bootloader, i will still be able to receive the eventual ota 4.4 update correct?
Click to expand...
Click to collapse
Yes, but you won't be able to unlock if you're system version is newer than May.

hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
RikRong said:
Yes, but you won't be able to unlock if you're system version is newer than May.
Click to expand...
Click to collapse

peladoro said:
hey rikrong...as i had mentioned in another thread, found out that i am indeed able to root unlock etc...(xt925). so it's safe to say that unlocking the bootloader for obvious reasons is needed to flash roms but is not negatively affecting the phone from functioning in anyway right? sorry if these r stupid questions but just trying to understand...the only issue is warranty
Click to expand...
Click to collapse
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.

hehe...ok thanks again!!!
RikRong said:
Yeah, sorry, I lose track of the posts. Just simply unlocking the BL should have no adverse affect on the phone, just the warranty, like you said.
Click to expand...
Click to collapse

RikRong said:
The dead robot is your stock recovery screen. You need to hold vol+ and tap pwr at the same time to get into your stock recovery.
When you flash a recovery.img, you need to immediately boot back into the recovery to get the updater script to finish. If you don't boot straight into recovery after flashing, the stock recovery will override the aftermarket recovery. Also, do you have an unlocked bootloader?
Click to expand...
Click to collapse
Hello
Please can you explain step by step how to install a cwm ? (i just unlock the bootloader)
Do i have to root the phone to do that ?
Thank you

How about an updated root thread for 4.4.4 (Verizon) ?

I've been through all the threads on rooting my new M8 but they're all out of date since 4.4.4 dropped. Is there any prospect we'll see an updated thread or new simple method to root?

mk3 said:
I've been through all the threads on rooting my new M8 but they're all out of date since 4.4.4 dropped. Is there any prospect we'll see an updated thread or new simple method to root?
Click to expand...
Click to collapse
There will be when there is a way. Right now there's not

How about unlock the boot loader on HTC dev site ?

finanandroid said:
How about unlock the boot loader on HTC dev site ?
Click to expand...
Click to collapse
Verizon don't allow that.

Yes please
I also would like to see a new something to help with rooting. I have been running root on my M8 for a while and went through the weaksauce method until that was no longer available them I switched to the Towelroot method and also used sunshine. Now after the update to 4.4.4 (which I knew I should not have done) I cannot use any method. I am hoping the update to Sunshine 3.0 comes soon and that fixes the problem. Also some better instructions to turn of the firmware updates and stop those dumb notifications would help a lot.

reaperslay said:
I also would like to see a new something to help with rooting. I have been running root on my M8 for a while and went through the weaksauce method until that was no longer available them I switched to the Towelroot method and also used sunshine. Now after the update to 4.4.4 (which I knew I should not have done) I cannot use any method. I am hoping the update to Sunshine 3.0 comes soon and that fixes the problem. Also some better instructions to turn of the firmware updates and stop those dumb notifications would help a lot.
Click to expand...
Click to collapse
If you used sunshine you are s off. Boot into fastboot and flash a custom recovery and then flash a supersu.zip. If s off you are beyond needing exploits.

Thought after I donated for unlock and S-off with Sunshine, I tried to flash twrp recovery as usually do all my flashing through computer (adb)
well it was no possible, weird thought to gain root I just need to flash custom recovery and superuser. Nope It was my M7 At&t with 4.4.2 Sense5.5, (hboot 157000) was untill I installed and run TowelRoot (after Sunshine) it did the root. then i flashed inmediately twrp and sense6 OTApkg.
So i hope that jcase-beaups instruct to or write a guide how to root the M8 4.4.4 after Sunshine 3 be released . It will help alot of users that think Sunshine will root as well and awesome will be if they include the root exploit along with sunshine, I know some people do not want to root just unlock-s-off but without root privilege it make no sense a least for me. I will be waiting for Sunshine3 to unlock _S-off-root my new HTC m8, I took the ota knowing that Sunshine will not work for a while ( I wanted to take the M8-firmwares-4.4.4 from VZW) truested that sunshine will do after.
I did with my M7 as well took the ota and then used Sunshine a small support to those great developers that put all their work at our hands. Thank you.

dottat said:
If you used sunshine you are s off. Boot into fastboot and flash a custom recovery and then flash a supersu.zip. If s off you are beyond needing exploits.
Click to expand...
Click to collapse
I wish people would learn this and pay attention when it's said. Once unlocked, or in HTC's case, S-off there's no longer a need to you use a root exploit ever again.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
I wish people would learn this and pay attention when it's said. Once unlocked, or in HTC's case, S-off there's no longer a need to you use a root exploit ever again.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
That's what I though but some users run into Root annoyances included me even after flashing Recovery and Su.
and yes I used root exploit in order to root. (towelroot)
so I hoped Sunshine for 4.4.4 fix the small problem. jcase said will include su in the next version
http://forum.xda-developers.com/showpost.php?p=55985887&postcount=1218
http://forum.xda-developers.com/showpost.php?p=56167285&postcount=1341
http://forum.xda-developers.com/showpost.php?p=56119893&postcount=1312
http://forum.xda-developers.com/showpost.php?p=55874823&postcount=1176
http://forum.xda-developers.com/showpost.php?p=55884505&postcount=1179

finanandroid said:
That's what I though but some users run into Root annoyances included me even after flashing Recovery and Su.
and yes I used root exploit in order to root. (towelroot)
so I hoped Sunshine for 4.4.4 fix the small problem. jcase said will include su in the next version
http://forum.xda-developers.com/showpost.php?p=55985887&postcount=1218
http://forum.xda-developers.com/showpost.php?p=56167285&postcount=1341
http://forum.xda-developers.com/showpost.php?p=56119893&postcount=1312
http://forum.xda-developers.com/showpost.php?p=55874823&postcount=1176
http://forum.xda-developers.com/showpost.php?p=55884505&postcount=1179
Click to expand...
Click to collapse
The problem is users who are s off are trying to use hacky (towelroot etc) means of getting root back after taking an ota.
They should be using twrp or cwr flashed via flashboot. Then flash the su.zip of choosing in recovery. That's the only way you should be rooting a rom after getting s off or being s off and taking an ota.
Can't tell you how tired it gets trying to explain to an s off user who keeps trying to run an exploit to get root. First link you posted the guy used towel root after flashing twrp. Wtf. That's not how it works. That's how it breaks. /rant

dottat said:
The problem is users who are s off are trying to use hacky (towelroot etc) means of getting root back after taking an ota.
They should be using twrp or cwr flashed via flashboot. Then flash the su.zip of choosing in recovery. That's the only way you should be rooting a rom after getting s off or being s off and taking an ota.
Can't tell you how tired it gets trying to explain to an s off user who keeps trying to run an exploit to get root. First link you posted the guy used towel root after flashing twrp. Wtf. That's not how it works. That's how it breaks. /rant
Click to expand...
Click to collapse
I don't know if they are trying to hack ? i just point to a annoying may be a little bug with the intention to enrich info about sunshine and users
experiences. In my case I did Sunshine on the wife M7, never rooted, pure stock, she took the OTA, and I want to try Sunshine.
after s-off and unlock I couldnt flash recovery and Su have no binaries , use to flash from recovery su.zip to correct this problem but this time
with out custom recovery you cant. I was s-off unlocked. then I recall towelroot, run it grant me root inmediately, flash recovery and Su binaris updated immediately.

finanandroid said:
I don't know if they are trying to hack ? i just point to a annoying may be a little bug with the intention to enrich info about sunshine and users
experiences. In my case I did Sunshine on the wife M7, never rooted, pure stock, she took the OTA, and I want to try Sunshine.
after s-off and unlock I couldnt flash recovery and Su have no binaries , use to flash from recovery su.zip to correct this problem but this time
with out custom recovery you cant. I was s-off unlocked. then I recall towelroot, run it grant me root inmediately, flash recovery and Su binaris updated immediately.
Click to expand...
Click to collapse
What prevented you from flashing a custom recovery?
An unlocked s off phone will flash recoveries and firmware for that matter all day long without a complaint.
And by hacky I mean a hacky method to root. It's not clean.

dottat said:
What prevented you from flashing a custom recovery?
An unlocked s off phone will flash recoveries and firmware for that matter all day long without a complaint.
And by hacky I mean a hacky method to root. It's not clean.
Click to expand...
Click to collapse
wells ADB was giving me a error, I changed cables but wait I was with the original usb cable so
I try a second time, same error it wont let me flash nothing, weird i was s-off and unlocked! so
i did towel root, su, busybox. then I was able to flash

finanandroid said:
wells ADB was giving me a error, I changed cables but wait I was with the original usb cable so
I try a second time, same error it wont let me flash nothing, weird i was s-off and unlocked! so
i did towel root, su, busybox. then I was able to flash anything i want like allways do.
Click to expand...
Click to collapse
You would be using fastboot to flash. If you want I can help you get a working fastboot/adb setup via team viewer at some point it works for both of us.

dottat said:
You would be using fastboot to flash. If you want I can help you get a working fastboot/adb setup via team viewer at some point it works for both of us.
Click to expand...
Click to collapse
Thank you! but i have a working set up adb from long time ago updated last year, I only flash through fastboot adb you know its a piece of cake
an secure than anything, thanks again
PD: my retired HTC DNA is working on my adb, so my new HTC m8 as well.
the M7 after sunshine was the problem...solved.

finanandroid said:
wells ADB was giving me a error, I changed cables but wait I was with the original usb cable so
I try a second time, same error it wont let me flash nothing, weird i was s-off and unlocked! so
i did towel root, su, busybox. then I was able to flash anything i want like allways do.
Click to expand...
Click to collapse
finanandroid, I received an error using fastboot when flashing a recovery. Turns out I was using a fastboot.exe from 2011. Once I found a newer fastboot dated 1/17/2014 the error went away. Might want to check that. dottat knows what he is talking about. There is no need to use towel root to gain root access on an S-Off Unlocked M8.
- Just flash twrp (http://teamw.in/project/twrp2/164)
- Boot into recovery
- Hit the reboot button
- Hit the system button
- twrp will prompt you to install SuperSU. Allow twrp to install SuperSU
- Once finished boot into your phone and open SuperSU to complete setup.

Darth Grimnir said:
finanandroid, I received an error using fastboot when flashing a recovery. Turns out I was using a fastboot.exe from 2011. Once I found a newer fastboot dated 1/17/2014 the error went away. Might want to check that. dottat knows what he is talking about. There is no need to use towel root to gain root access on an S-Off Unlocked M8.
- Just flash twrp (http://teamw.in/project/twrp2/164)
- Boot into recovery
- Hit the reboot button
- Hit the system button
- twrp will prompt you to install SuperSU. Allow twrp to install SuperSU
- Once finished boot into your phone and open SuperSU to complete setup.
Click to expand...
Click to collapse
Thanks for your input, I don't doubt that Dottat is right about it, I didn't post a problem to seek a fix I fixed it since I posted, Just wanted to share sunshine user experience. however the problem wasn't fastboot adb.
the problem was with the HTC M7. state it in my first post.

So I have sun shine on my m8 and its rooted and working great. Verizon keeps trying to push the 4.4.4 ota update on me.. Is there an update i should grab or let it install since I have sunshine..
Thanks Kyle

Greetings,
Thread cleaned.
Not everyone in these threads are at the same level...if you can be helpful then please do so if not move along.
After all we were all noobs at one point.
Thanks,
BD619

i think this is the information i was looking for also.
is the problem only that sunshine wont unlock a 4.4.4 device?
but if, like me, you are s-off and unlocked already you can update by any method without worry and still be unlocked and s-off.
if you then re-lock your device (for whatever reason) after updating to 4.4.4, then you cannot re-use sunshine (until sunshine is updated)
please correct if i am wrong.
i am waiting to update to 4.4.4.