Related
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
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
mike216 said:
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
nghtrain88 said:
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
mike216 said:
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
How did you unlock your bootloader?
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
With the app
Sent from my SCH-I535 using xda premium
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
annoyingduck said:
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
Click to expand...
Click to collapse
link for ez-unlock 1.2
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
nghtrain88 said:
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Click to expand...
Click to collapse
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
mike216 said:
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
mike216 said:
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Cwm 6.0.1.2 for aosp jb, do not use the old 5 . something touch in ez recovery
mike216 said:
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Brian Gove said:
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Click to expand...
Click to collapse
I'm on stock ICS in want to go to paranoid android. Sorry guys but after last night I'm paranoid myself!
Sent from my SCH-I535 using xda premium
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks once again! I'm now on PA after a pack of smokes! Appreciate all your help. You were absolutely right ! Recovery stuck and it flashed with no problem. I used the current recovery straight from ROM manager
Sent from my SCH-I535 using xda premium
Good, glad to hear you got it rolling.
Hello guys, so someone had my phone and accidently hit to install the new update, and I must've did something I wasn't supposed to, trying to stop it. Now when I boot from TWRP it says theres no OS installed, is there a way I can install the OS back through TWRP or something...for some reason I dont have a back up when I thought I did...any help would be greatly appreciated.
You could flash the fxz that matches what was on there and keep data and your custom recovery. I usually flash the official firmware after it becomes available if I took the OTA just for GP. But I don't flash the recovery or boot logo since those are custom. Every so often I will wipe data if I get to much on there to clean up. But that is just me
Sent from my XT1080 using XDA Premium 4 mobile app
rekids said:
You could flash the fxz that matches what was on there and keep data and your custom recovery. I usually flash the official firmware after it becomes available if I took the OTA just for GP. But I don't flash the recovery or boot logo since those are custom. Every so often I will wipe data if I get to much on there to clean up. But that is just me
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for my dumb question but what is fxz?
TheDroidURLookinFor said:
Sorry for my dumb question but what is fxz?
Click to expand...
Click to collapse
Factory image
Hi there, I'm trying to get OTAs while still being rooted, obviously that can't be done without the stock recovery, my internet connection is too slow and has a limited download capacity(and it's shared) so I can't download the fastboot images and get the recovery from there, and I wasn't able to find it anywhere else, thanks.
OTA do not require stock recovery.I updated my phone in twrp.Just be sure just uncheck update cm recovery in developer options
Sent from my One using XDA Premium 4 mobile app
Really? I thought OTA zips can't be flashed through a custom recovery, and I'd like to update my phone without the hassle of trying to find a flashable zip file.
Sting3r. said:
Really? I thought OTA zips can't be flashed through a custom recovery, and I'd like to update my phone without the hassle of trying to find a flashable zip file.
Click to expand...
Click to collapse
You have to remember this phone is primarily done by a company that has no issues with rooting CM. Also I am quite sure finding the update zip will not be that much of a hassle. Also not sure if you know this but OnePlus One has put out a AOSP rom of there own. How man phone companies do you know that tells you how to root and puts out a rom.... :good:
Finding update.zip is difficult.Its stored in cache folder(not visible),which gets deleted once device is updated
Sent from my One using XDA Premium 4 mobile app
Thank you guys, I have decided to use TWRP instead and update manually
RISHI RAJ said:
Finding update.zip is difficult.Its stored in cache folder(not visible),which gets deleted once device is updated
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
finding an update zip is as easy as you found this thread
Hi I was going to use chainfires method but the best the web page it only sates 5.0 with the build number LRX210- which is different to 5.0.1?
Is there any way to root then?
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
Hi I was going to use chainfires method but the best the web page it only sates 5.0 with the build number LRX210- which is different to 5.0.1?
Is there any way to root then?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
of course there is a way to root 5.0.1.
use fastboot to either flash a custom recovery (TWRP is probably your best bet), or use fastboot to just boot into the custom recovery without flashing. Either way, once your in recovery, flash SuperSU (download here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
done and done.
jss2 said:
of course there is a way to root 5.0.1.
use fastboot to either flash a custom recovery (TWRP is probably your best bet), or use fastboot to just boot into the custom recovery without flashing. Either way, once your in recovery, flash SuperSU (download here http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip)
done and done.
Click to expand...
Click to collapse
You sir are very wrong, you cannot flash that zip in recovery because it no longer works with lollipop... (Sigh)
PS. I have a custom recovery and unlocked boot loader so your suggestion are invalid
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
You sir are very wrong, you cannot flash that zip in recovery because it no longer works with lollipop... (Sigh)
PS. I have a custom recovery and unlocked boot loader so your suggestion are invalid
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
actually, it does work. with 5.0.1, I'm rooted. Except when I flashed 5.0.1, SuperSU v2.40 hadn't yet been released, so I rooted with SuperSU v2.37, and then updated via the playstore when 2.40 came out. but it definitely works with Lollipop.
p.s. you need to have an unlocked bootloader to install a custom recovery (which is what I suggested doing). So in fact, my suggestion is completely valid and 100% relevant. In fact, I had assumed that you already had an unlocked bootloader when I posted.
jss2 said:
actually, it does work. with 5.0.1, I'm rooted. Except when I flashed 5.0.1, SuperSU v2.40 hadn't yet been released, so I rooted with SuperSU v2.37, and then updated via the playstore when 2.40 came out. but it definitely works with Lollipop.
p.s. you need to have an unlocked bootloader to install a custom recovery (which is what I suggested doing). So in fact, my suggestion is completely valid and 100% relevant. In fact, I had assumed that you already had an unlocked bootloader when I posted.
Click to expand...
Click to collapse
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes, and the way to "manually re-root" is to flash the ZIP in a custom recovery. You the app installed, but not the SU binary. So flash it in TWRP.
dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CF Auto Root and flashing the superSU2.40.zip in recovery both root android 5(0.1/0.2). Did it myself and confirming root access.
You can root with the same chainfires files for 5.0, and then you can update supersu and twrp
dec1153 said:
Your point is again invalid and 100% incorrect- I have just tried and it has not given Me root. I have to manually re-root not flash the zip. See attachment
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It astounds me how you have the guts to ask for help - then someone gives you an answer that is completely right and you do a hard six and blatantly flame them for trying to help you.
JayR_L said:
It astounds me how you have the guts to ask for help - then someone gives you an answer that is completely right and you do a hard six and blatantly flame them for trying to help you.
Click to expand...
Click to collapse
Crazy. Done it to me a few times. I even decided not to help him ever again some time ago, then took pity on him yesterday or the day before and the he did it AGAIN!
He's just a school kid, but you'd hope he would learn from his attitude, but apparently not.
What's worse, is he isn't even picking up the knowledge that people give him or reading the stickies. He's been Here pretty much a year in the n5 forum and cannot even be bothered to.understand the basics. Asks the most basic questions every time.