I've seen many different rooting methods for the nexus s but unfortunately they don't allow rooting without unlocking the bootloader like the samsung vibrant allows is there anyway I can root my phone without unlocking the bootloader?
why I don't want to unloack the boot loader because I'm fine with the stock ROM on my nexus s. I was really into installing ROMs and things with my Vibrant but the Nexus S feels really complete so I feel like I don't need to unlock my boot loader
Also for the first time I have decent signal in my house after switiching from my blackberry to android so I don't wanna change my baseband and my battery life is good too so I don't want to mess with the kernel
Really? You posted in the same incorrect forum twice with the same question cut and pasted. Nice work!
Sent from my PC36100 using XDA Premium App
You know you can re-lock the bootloader with a fastboot command, right? And the little open lock goes away.
i'm sorry i accidentally reposted i pmed the moderator right away because i didn't know how to delete the post and this is the right section its a question...
i just have one question i can relock right but if i do unlock the bootloader will it change my kernel or baseband settings? i really couldn't care about the warranty and such
it's like opening the door....if you do nothing inside, nothing will happen
yes i get that but i can't flash back to the original recovery as of now and so no changes to the kernel and baseband alright thanks!!
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
anishs said:
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
Click to expand...
Click to collapse
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
suksit said:
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
Click to expand...
Click to collapse
thanks for that reply it explained everything can you just tell me if flashing a custom recovery change my baseband or kernel that's all i need to know now
@anishs no
Sent from my Nexus S using XDA App
thanks to everyone for helping a noob with a nexus s
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium
Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post
droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13
Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,
MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
Deleted
Jesus. All of these people who don't read up on things before they flash something astounds me.
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?
MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3
strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
I need to return my phone and ive used the guide to reset my flash counter with triangle away (which was never tripped, just did it for piece of mind), then i used odin and used the stock kernel and stock image to reinstall back to stock. Everything passed but when i boot my phone up right under the samsung logo it still says custom with the unlock logo. How do i get rid of this so i can return my phone back to verizon?
EDIT***** So i re-rooted then installed ez-unlocker and locked the bootloader again. Then reinstalled stock image through odin and all is well now
shortguy088 said:
I need to return my phone and ive used the guide to reset my flash counter with triangle away (which was never tripped, just did it for piece of mind), then i used odin and used the stock kernel and stock image to reinstall back to stock. Everything passed but when i boot my phone up right under the samsung logo it still says custom with the unlock logo. How do i get rid of this so i can return my phone back to verizon?
Click to expand...
Click to collapse
Try locking your bootloader with Ez-Unlock in the play store.
fr8cture said:
Try locking your bootloader with Ez-Unlock in the play store.
Click to expand...
Click to collapse
My phones not rooted so i cant use the app.
I thought using Odin with the stock rom/kernel automatically locks the bootloader?
Sent from my SCH-I535 using xda app-developers app
Jarredw said:
I thought using Odin with the stock rom/kernel automatically locks the bootloader?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I thought so as well but when I restarted my phone it still said custom. I tried to factory wipe data after I reflashed stock and still didn't work. So I dont know what happened
Tap'n
Wish i could help but i have no idea. I guess your gonna have to try your luck.
techgov8 said:
I thought so as well but when I restarted my phone it still said custom. I tried to factory wipe data after I reflashed stock and still didn't work. So I dont know what happened
Tap'n
Click to expand...
Click to collapse
that means your bootloader is indeed locked...look around on the forums a bit! When the custom unlock screen is gone then your unlocked. I believe there is a guide in the dev section that explains this. :angel:
droidstyle said:
that means your bootloader is indeed locked...look around on the forums a bit! When the custom unlock screen is gone then your unlocked. I believe there is a guide in the dev section that explains this. :angel:
Click to expand...
Click to collapse
Well when you first boot up a brand new phone it doesn't have the custom on the samsung screen and that's locked
Tap'n
Need to get rid of custom Samsung bootloader screen
techgov8 said:
Well when you first boot up a brand new phone it doesn't have the custom on the samsung screen and that's locked
Tap'n
Click to expand...
Click to collapse
. I've tried all the guides and their bot working for me on my galaxy s4 d or s anyone know where I can find a step by step guide I'm a noon on rooting
garygnobriga said:
. I've tried all the guides and their bot working for me on my galaxy s4 d or s anyone know where I can find a step by step guide I'm a noon on rooting
Click to expand...
Click to collapse
Wait hold up if you have an s4 why are you on the S3 forums? I am assuming you have at&t , T-Mobile or Sprint go to those threads as it makes much more sense to do that.
Hello everyone, I am in a bit of a pickle here, I have a galaxy s3 on verizon, and the otherday I tried to root it. and now get a "software unauthorized by verizon is installed, please contact verizon support" message everytime I try to boot the phone up. the phone was stock and unrooted when I did this, (flashed through odin.) Ive read forum after forum after forum but cant find what I need to do. Im trying to get a custom recovery on it so I can install a custom rom, but I really just dont know where to get the correct files. Please help me!
Flashing my galaxy note 2 was litterally so easy how hard can this be?
coffie60percent said:
Hello everyone, I am in a bit of a pickle here, I have a galaxy s3 on verizon, and the otherday I tried to root it. and now get a "software unauthorized by verizon is installed, please contact verizon support" message everytime I try to boot the phone up. the phone was stock and unrooted when I did this, (flashed through odin.) Ive read forum after forum after forum but cant find what I need to do. Im trying to get a custom recovery on it so I can install a custom rom, but I really just dont know where to get the correct files. Please help me!
Flashing my galaxy note 2 was litterally so easy how hard can this be?
Click to expand...
Click to collapse
From the sound of it the phone is on 4.4.2 NE1 and it's got a locked bootloader. There are no custom recoveries or custom roms. Post a screen shot of the about phone screen
At this point you would have to Odin back to stock
From my CM11 S3
ShapesBlue said:
From the sound of it the phone is on 4.4.2 NE1 and it's got a locked bootloader. There are no custom recoveries or custom roms. Post a screen shot of the about phone screen
At this point you would have to Odin back to stock
From my CM11 S3
Click to expand...
Click to collapse
I cant get to the about phone screen because i cant even boot into the os, because it is stuck at the "unauthorized verizon software detected" screen :/
Nevermind... Didn't scroll down far enough.
Sent from my SCH-I535 using XDA Free mobile app
coffie60percent said:
I cant get to the about phone screen because i cant even boot into the os, because it is stuck at the "unauthorized verizon software detected" screen :/
Click to expand...
Click to collapse
Alright but you will still have to Odin back to stock. That's pretty much your only option at this point
From my CM11 S3
ShapesBlue said:
Alright but you will still have to Odin back to stock. That's pretty much your only option at this point
From my CM11 S3
Click to expand...
Click to collapse
Would you be able to direct me to the necessary files to do so?
coffie60percent said:
Would you be able to direct me to the necessary files to do so?
Click to expand...
Click to collapse
I'm looking for the right thread at the moment. Make sure you read before flashing this
http://forum.xda-developers.com/showthread.php?t=2791801
From my CM11 S3
I have an sch-i535 Galaxy S3 Verizon phone. I'm not using it on a network anymore and just want to use a custom rom. Is there ANY way to wipe, replace, do something with the locked bootloader since I'm not using the phone as a phone?
oneway2k said:
I have an sch-i535 Galaxy S3 Verizon phone. I'm not using it on a network anymore and just want to use a custom rom. Is there ANY way to wipe, replace, do something with the locked bootloader since I'm not using the phone as a phone?
Click to expand...
Click to collapse
Your out of luck. Locked bootloader means no way to return to a previous version on Android. Even if its not being used as a phone it's basically stuck there. There are jtag services out there to revert back to 4.1.2 but I've heard a lot of mixed thoughts on those
Sent from my N5
ShapesBlue said:
Your out of luck. Locked bootloader means no way to return to a previous version on Android. Even if its not being used as a phone it's basically stuck there. There are jtag services out there to revert back to 4.1.2 but I've heard a lot of mixed thoughts on those
Sent from my N5
Click to expand...
Click to collapse
Since I'm not too concerned about breaking this phone, can someone point me to info on the procedure for using JTAG to go back to 4.1.2? I have found some advertisements but no how-to.
oneway2k said:
Since I'm not too concerned about breaking this phone, can someone point me to info on the procedure for using JTAG to go back to 4.1.2? I have found some advertisements but no how-to.
Click to expand...
Click to collapse
I'd suggest mobile tech videos. There is a thread on xda about them but there are mixed reviews
Sent from my N5
http://forum.xda-developers.com/showthread.php?t=1734949
Moved to Q&A.
If you decide not to go the jtag route you could:
1) install SafeStrap
2) flash SuperliteROM into stock slot
3) flash XPosed and the modules that would make SLR look and act as you like.
This is what I have done with the i535 I picked up that was on NE1.