Hi I have just recently unrooted my phone and back to stock with stock boothloader and recovery.
I did this because I am just patiently
Waiting for the ICS update.
My questing is...how do I lock the OEM on my phone? I know you could but I want to know how. And ....if I do that....WOULD IT WIPE MY PHONE?
I want to relock my OEM, but keep all my apps on my phone.
So again, if I lock my OEM, would it wipe my phone?
PS. I have 19020A
Sent from my Nexus S using XDA App
Don't think it wipes ur phone... maybe I'm wrong but here ya go
>Fastboot Device
>Fastboot OEM Lock
Sent from my Nexus S using xda premium
Yup it will wipe everything
Sent from my HTC Sensation 4G using XDA App
mathkid95 said:
Yup it will wipe everything
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
fastboot oem lock
Locking doesn't wipe anything. Unlocking wipes.
Sent from my Nexus S using xda premium
You don't have to lock bootloader to recieve OTA updates, unlocked bootloader just allows you to flash something via fastboot (usually CWM). Just be unrooted and have stock recovery, as I do. This way you can always flash CWM, make a nandroid backup and flash someting else...without losing any data (you don't unlock bootloader).
Ahhh damnit. Thanks krohn, had a bit of a brain freeze there.
Sent from my HTC Sensation 4G using XDA App
dan542 said:
You don't have to lock bootloader to recieve OTA updates, unlocked bootloader just allows you to flash something via fastboot (usually CWM). Just be unrooted and have stock recovery, as I do. This way you can always flash CWM, make a nandroid backup and flash someting else...without losing any data (you don't unlock bootloader).
Click to expand...
Click to collapse
Yea, why lock the bootloader? It doesn't need to be.
I thought locking the bootloader DID wipe. I guess I myself am mistaken too. (It would tell you though when you go to do it.).
Lastly, don't you think it's a little earlier to be going back to stock for the ICS update when it's not even announced as far as it being done and the phone; nor, is it announced of when the phone itself will be coming out. And, it won't be sometime till after that as well.
Just my opinion.
(You also didn't need to go unroot if you were stock rooted with no modifications).
Its just that I have lots of apps and I want to have them for when ICS comes out.
And....idk....I just figures if I am not rooted I might-as-well OEM lock just invade..if I might need to...for warenty
Sent from my Nexus S using XDA App
Nah your good on that... while it's rooted and awaiting the OTA... give your phone some Cyber air... over clock it with an app... install a better radio.. do something =]
Sent from my Nexus S using xda premium
BlackHawkA4 said:
Yea, why lock the bootloader? It doesn't need to be.
I thought locking the bootloader DID wipe. I guess I myself am mistaken too. (It would tell you though when you go to do it.).
Lastly, don't you think it's a little earlier to be going back to stock for the ICS update when it's not even announced as far as it being done and the phone; nor, is it announced of when the phone itself will be coming out. And, it won't be sometime till after that as well.
Just my opinion.
(You also didn't need to go unroot if you were stock rooted with no modifications).
Click to expand...
Click to collapse
Yes, you can be rooted, but you'll have to have stock recovery and you'll lose root with OTA update.
Sent from my Nexus S using XDA App
dan542 said:
Yes, you can be rooted, but you'll have to have stock recovery and you'll lose root with OTA update.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You don't need stock recovery. Stock recovery is not checked with an assert and is not patched, it is deleted and flashed using a full image. You can flash the OTA with CWM without any issues.
You will lose root in one of two scenarios with the OTAs, it recursively chmod's /system or formats /system (full update, not incremental). At this point all you need to do it flash the su binary again though to regain root access.
krohnjw said:
You don't need stock recovery. Stock recovery is not checked with an assert and is not patched, it is deleted and flashed using a full image. You can flash the OTA with CWM without any issues.
You will lose root in one of two scenarios with the OTAs, it recursively chmod's /system or formats /system (full update, not incremental). At this point all you need to do it flash the su binary again though to regain root access.
Click to expand...
Click to collapse
Ok
Sent from my Nexus S using XDA App
Related
My question is, if you relock the bootloader on ns4g after unlocking and rooting, will you loose the root or the ability to flash any custom roms or mods?
chrissboston said:
My question is, if you relock the bootloader on ns4g after unlocking and rooting, will you loose the root or the ability to flash any custom roms or mods?
Click to expand...
Click to collapse
No. You can still flash anything via custom recovery.
You will, however, lose the ability to flash a custom recovery if it is overwritten via fastboot. If you have root access you can still use the flash_image binary from the device or flash via Rom Manager. If you lose root and recovery though you will have to unlock again.
chrissboston said:
My question is, if you relock the bootloader on ns4g after unlocking and rooting, will you loose the root or the ability to flash any custom roms or mods?
Click to expand...
Click to collapse
This is a dev phone, so you can lock and unlock the bootloader as you please. You will not be able to switch the recovery with it locked.
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
If the bootloader is locked you can not flash roms. This is a dev phone, so you can lock and unlock the bootloader as you please.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Yes you can - via a custom recovery you can flash whatever you want.
Pre 2.3.3 you could fastboot boot a custom recovery and flash whatever you wanted without even touching the stock recovery. That was never the intended functionality though and 2.3.3 took that ability away again (so that you now have to initially unlock in order to flash a custom recovery).
Thanks
Thank you Rem3Dy & krohnjw, I understand now. And thanks for the tip about flashing through rom manager krohnjw, its very usefull and easier instead of flashing manually.
chrissboston said:
And thanks for the tip about flashing through rom manager krohnjw, its very usefull and easier instead of flashing manually.
Click to expand...
Click to collapse
And is causing problems en masse.
rentaric said:
And is causing problems en masse.
Click to expand...
Click to collapse
erasing before flashing seems to help, I just use fastboot though as it's easy and doesn't have any issues. I don't recommend locking the bootloader if you plan on flashing, but it is possible.
Sent from my Nexus S using XDA Premium App
I agree with you krohnjw as sometimes when you don't do a full wipe the new flashed rom gives you problems, specially with FC's, but I've never had a problem when flashing after doing a full wipe.
So I traded my galaxy s 4g on craigslist about a month ago for a nexus s (t-mobile) which besides the 4g antenna is 100% better in every way possible. I absolutely love the phone. It came previously rooted which I was ok with. It is on 2.3.3. Not sure what method was used to gain root. Now that the backstory is done here is my dilemma:
I constantly get the update message. I guess I wouldn't mind so much if I could just get rid of the message but the problem isn't just that. I also want to be on the latest greatest version of android. So I've read a bunch of walkthroughs and various ways to update to the latest firmware on a custom rom like cm7 and keep the root, or un root and go to stock 2.3.3 and manually update to stock 2.3.4.
I need an opinion on which would be my easiest way (new to android previous iPhone jail breaker) to get to 2.3.4?
You cannot lose root on a nexus s. No matter the update you can always reroot as its a developer phone with an unlocked bootloader.
Sent from my PC36100 using XDA Premium App
Do the update
Download su.zip and the right cwm recovery image for your phone
Mount USB storage
Copy su.zip on sdcard and recovery image goes into /tools folder inside your adb/sdk folder on pc
Boot into fastboot, vol up+power
In a cmd prompt do 'fastboot devices' should return a number (this step is just to check if fastboot/adb is working properly)
'fastboot flash recovery recoveryimagename.img'
Choose recovery option on phone
Install su.zip from sdcard
Done
Sent from my Nexus S using XDA App
I forgot to mention that it will not take the update. I tried a bunch of times and it doesn't work, just gets locked up during the process.
Sent from my Nexus S using XDA App
stompincc said:
I forgot to mention that it will not take the update. I tried a bunch of times and it doesn't work, just gets locked up during the process.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i'm pretty sure that's just cause you're on a custom rom. flash a stock rom and the update should work fine
My gf got a Nexus S last month and loves it! She just needs BLN to work... so we unlocked the bootloader and installed a custom Kernel (Matr1x I believe). Will the OTA come through? If so, will it wipe out anything like CWR or the unlocked bootloader? I saw Matr1x already released a ver for ICS so it would be an easy install...
Sent from my XT860 using xda premium
danifunker said:
My gf got a Nexus S last month and loves it! She just needs BLN to work... so we unlocked the bootloader and installed a custom Kernel (Matr1x I believe). Will the OTA come through? If so, will it wipe out anything like CWR or the unlocked bootloader? I saw Matr1x already released a ver for ICS so it would be an easy install...
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
No it wont update.
Sent from my Nexus S using xda premium
thegtfusion said:
No it wont update.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
How would I go about updating the device? She's pretty excited for ICS.
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
snandlal said:
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
Click to expand...
Click to collapse
So if I restore the Kernel (I'm not sure how I would go about doing that though, can someone provide instructions? ) would it apply the update at that point? Or do I need to re-lock the bootloader? Relocking would be a pain........
danifunker said:
So if I restore the Kernel (I'm not sure how I would go about doing that though, can someone provide instructions? ) would it apply the update at that point? Or do I need to re-lock the bootloader? Relocking would be a pain........
Click to expand...
Click to collapse
If you have a nand backup of stock restore it, Otherwise download one of the stock roms from here and flash it in recovery.
http://forum.xda-developers.com/showthread.php?t=1063664
snandlal said:
It will fail the verifying stage of the update. All the original files of the previous version of the update your flashing needs to be there.
Click to expand...
Click to collapse
That depends on what kind of update it will be ... The update from 2.3.3 to 2.3.4 on my i9023 nexus was a full rom and could be flashed without a problem.
Verstuurd van mijn Nexus S met Tapatalk
Go back to latest available stock version. (Rooted with Superuser.apk in /system/app is OK) & Keep your Custom Recovery or reflash it.
Put a Superuser flashable zip on your sdcard.
When you have the OTA update.zip somewhere on your sdcard ( Copied from /cache) boot into custom recovery
Flash update.zip manually and directly after it flashes, flash the Superuser.zip right on top of update.
Wipe /cache
Reboot
Download Joeykrim's flash_image gui from the market.
Place custom-recovery.img on root of sdcard. (Rename it to recovery.img)
Flash custom recovery in flash_image gui
Change permissions of /system/etc/install-recovery.sh & /system/recovery-from-boot.p to "000"
I would just wait till ics is out and then youll find a flashable .zip here on xda and you can just flash that like you did with the matr1x kernel... not shure if full wipe would be nescesary but if yes then you can backup your apps through titanium or sth similar!
Sent from my Nexus S using XDA App
Edit: what i actually wanted to say that theres no need to go back to stock now because you can get the update over xda and just flash that!
while we're on the topic....would editing the build.prop keep an OTA from installing? For example, LCD density??
Why not just wait like one day for someone to post a rooted stock ICS rom? I am sure one of our wonderful devs here will be all over it. It will probably show up in one of those REF threads pretty quickly. Then you don't have to mess around with setting root up again. That's what I always did with my EVO Shift so I'll probably do it with this phone as well.
If you hadn't modified your build.prop or removed system apps, you'll just need to flash the stock kernel. Theres no need to flash the whole stock Rom.
What if your bootloader is unlocked and nothing else. Will it get the OTA?
Question since we on the subject when will ics be released for our phones or is it still unknown as to when is gonna be released?
Sent from my Nexus S 4G using Tapatalk
cpaixao said:
If you hadn't modified your build.prop or removed system apps, you'll just need to flash the stock kernel. Theres no need to flash the whole stock Rom.
Click to expand...
Click to collapse
That's exactly what I was looking for... but where would I find the stock Kernel and can I overwrite it while the system is in use? I downloaded the entire stock ROM for her phone so I should have the file somewhere in one of the IMG files (yes, I have mounted them before in Windows)
Sent from my XT860 using xda premium
danifunker said:
That's exactly what I was looking for... but where would I find the stock Kernel and can I overwrite it while the system is in use? I downloaded the entire stock ROM for her phone so I should have the file somewhere in one of the IMG files (yes, I have mounted them before in Windows)
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
boot.img is the kernel.
How do I apply just boot.img?
Sent from my XT860 using xda premium
Fastboot flash boot boot.img
Sent by breaking the sound barrier
Hey guys, I've read a lot on updating after being rooted, but just need to confirm before I do mess up anything.
All I have done is Rooted Stock (I have TWRP on the phone), and have flashed volume mod, and also battery percent mod. (Other then that I am running Nova Launcher, Titanium Backup)
Guessing I need to flash the back to stock for volume and battery percent (Correct if I am wrong).
And then how exactly do I go about updating to 4.4.2 and preferably retaining root?
Sorry I know noob question, just making sure as I've always unrooted, and never had any mods when I have done updates in the past.
1) you have to flash back to stock system image since you modded your phone
2) once you either get the OTA or sideload it, you just flash cwm/twrp in fastboot and then flash the supersu.zip
thats all
so in other words go back and unroot completely, go completely back to stock, and redo everything from the beginning?
Just flash the 4.4.2 stock rooted rom in the dev section
sent from my HAMMERHEAD neXus
Or you can flash the Updated Super SU zip right?
Sent from my Nexus 5 using Tapatalk
AndroidRaven said:
so in other words go back and unroot completely, go completely back to stock, and redo everything from the beginning?
Click to expand...
Click to collapse
You are flashing back the stock ROM. If you want to keep data intact, flash only the boot.img, system.img
niv3d said:
Or you can flash the Updated Super SU zip right?
Click to expand...
Click to collapse
that won't help you get back to stock.
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
AndroidRaven said:
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Follow this guide --> http://forum.xda-developers.com/showthread.php?t=2523217
Best guide out there, with big thanks to El Daddy
AndroidRaven said:
I guess I need a tutorial on what you guys are talking about because I still am not understanding..
Would flashing the rooted 4.4.2 work? And if so what do I need to do before I flash this?
How exactly do I go about only flashing only the boot.img and system.img?
Will I loose anything through this process?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One safe way to get the OTA, taking into account that you modded your phone, is:
i) flash system.img then flash stock recovery,
ii) once the OTA update is on your phone and you have accepted it (it installed itself) you are back to stock.
iii)flash your custom recovery and re-install your SuperSu to get back your root.
Good luck
Is there any tool that will reinstall the stock rom on a Nexus 5 with LOCKED bootloader? Something like emergency reflash from LG Support Tool.
LG Support Tool? There's something LG Flashtool and that works.
albwh said:
Is there any tool that will reinstall the stock rom on a Nexus 5 with LOCKED bootloader? Something like emergency reflash from LG Support Tool.
Click to expand...
Click to collapse
If you have to reinstall the stock firmware why do you care? Just unlock the bootloader, you're going to lose everything anyway.
What situation are you in. There may be ways to save your data
Sent from my Nexus 5 using XDA Free mobile app
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
albwh said:
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
Click to expand...
Click to collapse
If you're rooted but otherwise completely stock, you should get OTA updates no problem.
albwh said:
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
Click to expand...
Click to collapse
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
There's a whole sticky on returning to stock so you can get OTAs. </thread>
If you're able to flash the stock ROM, you should be past the point where you need to worry about being able to get any updates.
Yeah. I'd highly recommend just flashing a prerooted busybox stock ROM. You can always do a dirty flash over stock ROM and still keep data.
jd1639 said:
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You do get the OTA, but if you modify /system/ or something else, the OTA won't install.
It takes 10 minutes to return to stock for an OTA. Just do what you want with the phone now and enjoy!
The next OTA will be months from now. Return to stock then.
You dont need any tool. Download factory image and flash that by executing flash-all.bat (for windows, if you use linux execute flash-all.sh). Flash a custom recovery. Then remove hidden tampered flag by flashing tampered flag remover zip. Then flash stock recovery and lock bootloader by typing fastboot oem lock.
yashade2001 said:
You dont need any tool. Download factory image and flash that by executing flash-all.bat (for windows, if you use linux execute flash-all.sh). Flash a custom recovery. Then remove hidden tampered flag by flashing tampered flag remover zip. Then flash stock recovery and lock bootloader by typing fastboot oem lock.
Click to expand...
Click to collapse
You can do the last 2 steps using bootunlocker from play
Sent from my Nexus 5 using Tapatalk
rootSU said:
You can do the last 2 steps using bootunlocker from play
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes that is an awesome app.
yashade2001 said:
Yes that is an awesome app.
Click to expand...
Click to collapse
Yeah agreed. I use it to keep my bootloader locked but so I can unlock it without a wipe on the fly.
rootSU said:
Yeah agreed. I use it to keep my bootloader locked but so I can unlock it without a wipe on the fly.
Click to expand...
Click to collapse
Why do you keep your bootloader locked?
yashade2001 said:
Why do you keep your bootloader locked?
Click to expand...
Click to collapse
So no one can get my data
rootSU said:
So no one can get my data
Click to expand...
Click to collapse
How someone can get my data if i have a unlocked bootloader?
yashade2001 said:
How someone can get my data if i have a unlocked bootloader?
Click to expand...
Click to collapse
Locking the bootloader isn't enough on its own.
Android: adb pull data, MTP (Screen lock can prevent)
Custom recovery: adb pull data, flash zip to turn off android lock screen (Recovery lock can prevent)
Lock bootloader: Prevent replacing locked recovery with unlocked recovery,