Database Info

[Q] Completely awkward behaving Nexus S

I just bought this phone yesterday and it is the i9020t (AWS version). The phone function works fine but every so often every application fails and gives an error asking to report it. I cannot manage to change the screen lock, it just comes back after reset. I only managed to remove it once. Also I cannot reset it no matter what I do, whether it is from settings or from the recovery menu. All data seems impossible to remove. How is this happening?
So Far:
-I got the boot loader unlocked (does this mean it is rooted yet?), failed to install superboot.zip
-Got the adb setup with using only part of the sdk files
(http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/)
Now I have tried this:
http://forum.xda-developers.com/showthread.php?t=884093
I can't get clockworkmod on here, I don't even know what it is exactly.
I believe I need to flash the phone onto stock firmware, the current seems corrupt as I can't do any changes such as password or wipe data.
More info on phone:
Android version: 2.3.4; Baseband version: I9020XXKD1; Kernel version: 2.6.35.7-ge382d80 [email protected]#1; Build number: GRJ22;
BTW I am on Mac OS X but can access a PC if I really have to.
Anything else I need to provide?

Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium

He said weeny hah but other than that he's right
Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weeny very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms

sinik420 said:
He said weeny hah but other than that he's right
sent from my nexus s on a kang from simms
Click to expand...
Click to collapse
Owned by auto correct
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
Doesn't sound like an odd behaving phone, just that you weren't very prepared for the rooting process.
If your bootloader is unlocked you need to flash a custom recovery such as clockworkmod or twrp. To do this you will use the fastboot flash recovery nameofrecovery.img after you have flashed the recovery you can either flash a new rom or flash the superuser.zip to achieve root on the stock rom.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It was a messed up phone. Returned it. Nothing would write onto sdcard. Which explains why it would not allow many functions that require data retention.

Bootloader brick possible?

Hi, sorry if there is some answer to my question but i couldn't find it. Is there any chance of bricking device or screw something up when unlocking a bootloader? Tnx.
Sent from my GT-I5800

Not by unlocking it via fastboot OEM unlock. You could brick phone by flashing an incorrect bootloader..
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
Not by unlocking it via fastboot OEM unlock. You could brick phone by flashing an incorrect bootloader..
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
How to know which bootloader to use..?
Sent from my GT-I5800

Don't touch the bootloader, they generally come with the ROM. As for a recovery partition, most people use ClockWorkMod Recovery. Latest version is 5.0.2.0 and recommended.

Harbb said:
Don't touch the bootloader, they generally come with the ROM. As for a recovery partition, most people use ClockWorkMod Recovery. Latest version is 5.0.2.0 and recommended.
Click to expand...
Click to collapse
The only thing i want to do, is instal official OTA gb 2.3.6 from recovery on my nexus s, than try system upgrade from phone settings, to upgrade on ICS. Or if that is not working, to flash 2.3.6, than official OTA ICS from recovery.
My question is, do i really must unlock bootloader to flash any official or custom rom from stock recovery? As you can see i'm new to this, i have galaxy 3, there is all simple, just flash flash flash. Here i read you must unlock bootloader, than root, than install recovery..
Sent from my GT-I5800

Only need to unlock for unofficial ROMs. If you're using an official .zip (upgrade or full), you do not need an unlocked bootloader, a custom recovery or root. Just open the stock recovery and flash away.

I recently accidentally (noob) flashed a nexus s jelly bean bootloader update on my nexus s 4g and it screwed up my network, unable to be flashed for service. My USB doesn't get recognized by my computer regardless of cord or computer. Phone wi-fi works but no network, is there any way to solve this problem.

Just do a re flash using cwm, and throw it on a sd card and do it from your phone. Something similar happened to me.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Bad bootloader
Nexus85 said:
I recently accidentally (noob) flashed a nexus s jelly bean bootloader update on my nexus s 4g and it screwed up my network, unable to be flashed for service. My USB doesn't get recognized by my computer regardless of cord or computer. Phone wi-fi works but no network, is there any way to solve this problem.
Click to expand...
Click to collapse
Friend a have de same problem, my system works perfectly but doesn't have network. I put a korean version bootloader and I'm not root and don't have CWM recovery. I'm wait for jelly bean update because it has a new bootloader.img. I was reading this thread http://forum.xda-developers.com/showthread.php?t=1566475 but the nexus s 4G has all electronic things in different side.
I'm ask for help in this link http://forum.xda-developers.com/showthread.php?t=1839449.

custom opened padlock

i rooted my s3, then i unlocked the bootloader. i still havent flashed anything but now when i reboot my phone i get the custom notification with the unlocked padlock. did i do something wrong or is this normal.
edit: i used a windows based program to root and i used twrp to flash the unlocked bootloader
I am waiting on a stable completely functioning rom before flashing.

krbernier said:
i rooted my s3, then i unlocked the bootloader. i still havent flashed anything but now when i reboot my phone i get the custom notification with the unlocked padlock. did i do something wrong or is this normal.
edit: i used a windows based program to root and i used twrp to flash the unlocked bootloader
I am waiting on a stable completely functioning rom before flashing.
Click to expand...
Click to collapse
Sounds like it's not unlocked if you still have the custom boot screen. What method did you use to unlock?

You are not unlocked. When your bootloader is unlocked that Samsung screen just flies by. No padlock no waiting.
Sent from my SCH-I535 using Tapatalk 2

Thanks! i used a windows batch file to do the unlock...guess ill give it another go.

worked thanks!

My SGiii now does this when booting. I have root. I used the devFS root method. I to my knowledge I have not flashed the boot loader. Is this what people were talking about by adding one to there flash counter? If so I might as well flash cwm.
Is my warranty void now?
Sent from my SCH-I535 using xda app-developers app

Xiuix said:
My SGiii now does this when booting. I have root. I used the devFS root method. I to my knowledge I have not flashed the boot loader. Is this what people were talking about by adding one to there flash counter? If so I might as well flash cwm.
Is my warranty void now?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Has nothing to do with flash counter. It shows that software is modified and is caused by root. Unlocking the bootloader will get rid of lock. Warranty is void only if you don't revert to stock before return.

New guy

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.

Clean ROM and System software not authorized by Verizon Wireless

I now tried to load the Clean ROM twice and when it's down loading I get the System software not authorized by Verizon Wireless and had to run ODIN to get the SIII back up and running.
Anyone else having this happen?

1) root
2) Unlock your bootloader using EZ Unlock v.1.2 from Rootzwiki
3) flash CleanRom using CWM or TWRP
Your bootloader is still locked that's why you see that Verizon warning.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
1) root
2) Unlock your bootloader using EZ Unlock v.1.2 from Rootzwiki
3) flash CleanRom using CWM or TWRP
Your bootloader is still locked that's why you see that Verizon warning.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea I figured that out after the second time having to ODIN...
Thanks for the post.

I have the same issue and cannot get back to stock from odin. It keeps saying it failed
And I used odin to root the phone.
I have tried everything and nothing seems to work
I cannot get into recovery and in odin mode it dont work
Please help

NYGiants4Natic said:
I have the same issue and cannot get back to stock from odin. It keeps saying it failed
And I used odin to root the phone.
I have tried everything and nothing seems to work
I cannot get into recovery and in odin mode it dont work
Please help
Click to expand...
Click to collapse
If you are having the same problem as the op then why didn't you use the solution provided in this thread? Nevermind just seen your thread I will post there.