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.

[Q] Obtain root access without computer? (apk? TermEmu?)

Is this possible? I recently messed up my laptop and now I can't mess with my new N5! So is there a way I can root without a computer? Like a APK or do it in Terminal Emulator or something? Sheesh, not being able to mess with my phone is driving me nuts
Thanks.

Carloskeee said:
Is this possible? I recently messed up my laptop and now I can't mess with my new N5! So is there a way I can root without a computer? Like a APK or do it in Terminal Emulator or something? Sheesh, not being able to mess with my phone is driving me nuts
Thanks.
Click to expand...
Click to collapse
No, you need to unlock the bootloader which requires a computer.
Sent from my Nexus 5

I was wondering about this too. My boot loader is unlocked but I'm completely stock at the moment
Sent from my Nexus 5

pepdavies said:
I was wondering about this too. My boot loader is unlocked but I'm completely stock at the moment
Sent from my Nexus 5
Click to expand...
Click to collapse
If the BL is unlocked you don`t need a PC to flash and modify your phone. Just download a custom recovery (.img file) and flash it with Flashify from Play.
-Edit- missread and assumed you had root. Nope can`t flash custom software from third (stock) recovery.

gee2012 said:
If the BL is unlocked you don`t need a PC to flash and modify your phone. Just download a custom recovery (.img file) and flash it with Flashify from Play.
Click to expand...
Click to collapse
Not if he is unrooted. Flashify requires root
Sent from my Nexus 5 using Tapatalk

gee2012 said:
If the BL is unlocked you don`t need a PC to flash and modify your phone. Just download a custom recovery (.img file) and flash it with Flashify from Play.
Click to expand...
Click to collapse
Flashify requires root.. So if he just has the bootloader unlocked, he couldn't do anything with it..
Edit: Ninja'd..lol

rootSU said:
Not if he is unrooted. Flashify requires root
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was just about to say that. I've used flashify before. I know how to root with a custom recovery, I was just curious if there was a way to do it on the move.
Sent from my Nexus 5

There isn't. Android blocks access to all / (root) by default. The only way to root android from within Android itself is to take advantage of an exploit but as yet there doesn't seem to be one for KK /N5.
All unlocking the bootloader does is allow you to fastboot flash a custom recovery. Rooting from a recovery is easy because android is running therefore not "blocking" / (root). But since the recovery partition is on the / root of the device, you cannot flash a recovery whilst android is running....unless you have root access.
....so fastboot flash a recovery is the only way to get root, which requires obviously a computer.
Hope this helps to understand
Sent from my Nexus 5 using Tapatalk

Yes I understand. That is everyone.
Reason I asked. When I had my Nexus 4, all I did was download SuperSU. It was a stock device. But supersu asked to update us binary and it rooted the phone from there. I then downloaded a app to unlock the bl and did it all without a computer. Just curious if this could be done on the n5 as well. But I guess not. Thanks everyone.

Carloskeee said:
Yes I understand. That is everyone.
Reason I asked. When I had my Nexus 4, all I did was download SuperSU. It was a stock device. But supersu asked to update us binary and it rooted the phone from there. I then downloaded a app to unlock the bl and did it all without a computer. Just curious if this could be done on the n5 as well. But I guess not. Thanks everyone.
Click to expand...
Click to collapse
on the n4, and n5, there are apps that can lock and unlock the bootloader. but you need root for that. if you downloaded supersu and it asked to update the binaries, that means that your device had root(old) already, and just had its bootloader relocked..

[Q] Can you OTA update a Nexus 5 and keep root?

Ok so I just recently got my hands on a Nexus 5 which I rooted with CF Auto Root and relocked the bootloader with Bootunlocker for security (I'm guessing I should unlock before the update). I see reports surfacing of a possible 4.4.3 update in the near future. So before that happens I want to figure out the best practice for updating a N5 with CF Auto Root. It stands to reason I'll do a full backup so that's a given.
I'm not new to rooting. Done it a few times. Just haven't had a device that gets regular OTAs in my country so it hasn't come up.
Is there a way to update so that root is preserved? Obviously I'd like to keep the process as simple as possible but if I have to work from scratch it's not the end of the world.
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Or perhaps it's better to ask what the best procedure for updating a stock Nexus 5 with CF Auto Root.

Everything that you have ever wanted to know about OTA can be found here http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217

Ah thanks. Appreciate it.

generally no, after ota you lose root. but there are apps that will save your root so that you keep root after an update.

I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.

Reaper1242 said:
I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.
Click to expand...
Click to collapse
ive never used any since i dont ota, i update my custom rom as soon as its updated, but ive heard of success with rootkeeper. but it doesnt matter, it literally takes 3 minutes to root a nexus the right way(via fastboot).

Yea, I should use fastboot in future.

Reaper1242 said:
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Click to expand...
Click to collapse
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)

jj14 said:
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)
Click to expand...
Click to collapse
you would need to flash a custom recovery first, then supersu in your custom recovery.

Thanks everyone for the responses.You've made everything much clearer.

simms22 said:
you would need to flash a custom recovery first, then supersu in your custom recovery.
Click to expand...
Click to collapse
Good point. I assumed that op had installed a custom recovery when he rooted, but that is not always the case.

Ok so I'm going to sideload myself. Been a while so I just want to confirm the process so I don't screw up.
I'm using TWRP
Obviously I'll do a NANdroid and probably Titanium as well.
1) Unlock bootloader with Bootunlocker
2) Connect device to PC
3) Boot into TWRP recovery and go to Advanced > ADB Sideload
4) type adb sideload update.zip (or whatever I call the file)
5) reboot device and check if it's working
6) reboot to recovery and reflash superuser.zip
I think that's it. Is there anything else I need to be aware of? If I'm right it should then be updated, rooted and in the same state before I updated.

I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app

dec1153 said:
I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flash stock system.img and flash recovery.img and then do the update.zip from the stock recovery..
If you don't want to flash, then make sure you have removed all the modifications you have done to system apps. If you don't remember then I would certainly recommend flashing stock images...
Sent from my Nexus 5 using Tapatalk

(NEED HELP ASAP) Phone wont boot after updating Bootloader via flashify

I have to go to uni in 1 hour and updated my bootloader via flashify, now its stuck in bootloader and wont boot. TWRP is the only accesible option for me. Tried to reflash the bootloader via fast boot but nothings happening.
Bootloader : hhz11k
Rom : N5X 5.0 AOSP Ver. 5.4

Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC

EddyOS said:
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
Click to expand...
Click to collapse
I'm restoring right now. Doy you know why this happened? Isn't flashify able to flash the bootloader, and if that was the case, shouldn't a flash via fastboot be the solution to my problem?
Anyways thx for your quick answer!

I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device

EddyOS said:
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
Click to expand...
Click to collapse
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway

Escoban said:
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Click to expand...
Click to collapse
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick

rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5

Ben36 said:
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.

rootSU said:
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
Click to expand...
Click to collapse
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.

Escoban said:
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Click to expand...
Click to collapse
Were you flashing zips instead do you mean?

rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Glad i said "le'ts google it" before going full wipe, i owe you dude.
I downloaded 5.1 radio and bootloader and flashed them using Flashify, then i got the same problem as OP. Reflashing the kernel fixed it.
*deletes Flashify*

Unlock bootloader then rooting method?

Hey everyone, I've been lurking around for about two months, from when I picked up this phone. It's still completely stock. Unrooted, S-ON, all that. Well, after the update to Nougat, I've been searching for a way to unlock the bootloader & root. Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.

acesavant00 said:
Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
Click to expand...
Click to collapse
Go to http://htcdev.com and make an account, then follow the steps and unlock your bootloader from there. After that you fastboot flash TWRP using ADB, and then use TWRP to flash a root solution. I prefer Magisk.

Alright, just unlocked the bootloader, going through the process of setting up my phone once again. Do you have a link to the Magisk & TWRP programs that I can use? Also, should I put the TWRP file in the same folder as the fastboot files?
I greatly appreciate the assistance you've given me so far, I'm deeply grateful man.

Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?

acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
try this step by step.. :good:
1.Flash TWRP 3.0.3-8 via Fastboot.. Do not reboot into system, enter into recovery..
2.Do a factory Reset via TWRP.. Do not reboot into system
3.Now flash SuperSU 2.79 SR3.. Reboot into system..
couple of bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..

acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.

Captain_Throwback said:
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Click to expand...
Click to collapse
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.

acesavant00 said:
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
Click to expand...
Click to collapse
Can't you just flash the Nougat RUU?

Captain_Throwback said:
Can't you just flash the Nougat RUU?
Click to expand...
Click to collapse
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.

acesavant00 said:
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
Click to expand...
Click to collapse
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.

Captain_Throwback said:
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Click to expand...
Click to collapse
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?

acesavant00 said:
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
Click to expand...
Click to collapse
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.

Captain_Throwback said:
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Click to expand...
Click to collapse
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.

acesavant00 said:
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
Click to expand...
Click to collapse
Your bootloader will stay unlocked.

Captain_Throwback said:
Your bootloader will stay unlocked.
Click to expand...
Click to collapse
Awesome, I appreciate all of the help, man. Sorry again if I annoyed you with all of my incessant questions. Just didn't wanna mess up my phone even further.

Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance

rilley said:
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
Click to expand...
Click to collapse
Unlocking your bootloader will wipe the device.

Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you

sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
+1 I`m interested on this question, I have Nougat installed

sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
rilley said:
+1 I`m interested on this question, I have Nougat installed
Click to expand...
Click to collapse
Yes, you can root and debloat Nougat. Though you should make a stock system image backup first of you ever want to receive an OTA again. The TWRP thread FAQ has a lot of information about this.