[Q] Completely awkward behaving Nexus S - Nexus S Q&A, Help & Troubleshooting

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.

Related

cant load recovery

Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.
krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.
n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App
This is about the third or fourth time this question has come up over the past week...
bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App

Help Please!!!

Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that

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.

[Bootloader] [Android 4.2] JOP40C Bootloader version 4.13 flashable in recovery

Update: This bootloader is older and is not the newest available one. If you want the 4.18 version one go to THIS post and flash it with fastboot.
Older bootloader version: Doesn't flash and take hold for everyone, flash at your own risk
Usefull for people that don't want to flash in fastboot. The official OTA for 4.2 flashes this bootloader through recovery in the exact same manner
Code:
md5sum: 7cb16bc418e15ee2c7c48b82ea923e23
Code:
sha1sum: 6151d4afd075d03cfdfa33d111a1a6bba25fcab8
Code:
sha256sum: 2b7efeade37c1ec00d03ba71a56d5b921e6c27d4393298020bcd1601ae079605
Code:
sha512sum: cd7444ec7073e553b7715e4ee30d69f64b06ab3846f1d0ff3d9129f652ab4e90c3400f139a0347f0b78a0719c86b6e2d7f41d36068f032472dbc90c3530cefcb
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
remmyhi said:
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
Click to expand...
Click to collapse
I need to be aware of problems that happens on your Nexus7? I don't have that issue I flashed TWRP Recovery just fine on this booloader...
No, I did not write to you personally. Glad it worked on your side.
Just the people to know.
That's really strange. I would try flashing the 4.1.2 factory images even though it might wipe everything including your sdcard.
Sent from my Nexus 7 using Tapatalk 2
Did that, thanks. Indeed wiped everything
Glad I had a backup
Hey guys,
So, I can flash this file from TWRP and it will upgrade my bootloader?
Thanks in advance!
you can, but make sure you check MD5, flashing a corrupt download can kill your device. OP, you should add a MD5 check in the zip if possible. but thanks for this none the less.
If you have a rom like cm10 installed or other rom that has buysbox in it, just type busybox md5sum /sdcard/bootloader-grouper-4.13.zip
Either in terminal emulator or adb shell.
If your on stock you'll probably want to check it with a program on your pc or install busybox from one of the playstore busybox apps. Of course you'll need to be rooted.
Sent from my Nexus 7 using Tapatalk 2
I went ahead and added sha1sum, sha256sum and sha512sum checks.
I have just flashed the file and thank you, I no longer have to keep my power button pressed for 20 seconds just to have my tablet go on
Thank you so much!!!
If anyone has any problems there is a link in my SIG to fix it or if you just need to revert back...
Just a FYI the older bootloaders are in the factory images! You can extract them out and flash the bootloader separately if you don't want to flash ALL the factory images. So far flashing this with twrp I have not had one single issue yet to speak of... Each bootloader is meant to run on specific platforms, recoveries, kernels ect. So on that note I still suggest if you want to revert your bootloader you revert completely with the factory images.
Sent from my Nexus 7 using Tapatalk 2
Hi,
thanks for that but when i falsh it in TWRP it's wipe all my data but i still have the 3.41 bootloader?
I'm not sure if i understood the thing to do with the md5sum?
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
CWM + CM10 stable
I just flashed this bootloader using CWM 6.0.1.0 and CM10 stable. I used Chrome to download it and the md5sum command in terminal emulator to check the md5 hash before hand. It flashed fine, I have the new version number, everything continues to work. Very easy.
farshad.shirzadii said:
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showpost.php?p=32735541&postcount=5039
Thanks, easy flash, works perfectly
Sent from my Nexus 7 using xda app-developers app
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
blucmal said:
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
When you power your device on you hold the volume down button to get into bootloader. On the main screen it will say what version it is.
Sent from my Nexus 7 using Tapatalk 2

How to unlock the bootloader of a Verizon Galaxy S3 (i535) running 4.4.2

Hey everyone,
So, I have a verizon Galaxy s3 4g (i535) and I have been searching for days now for a way to unlock my bootloader so that I can flash a recovery and then flash some new ROMS. I tried flashing a recovery through odin but it failed, I tried flashing it through the apps available in appstore like TWRP Manager, ROM Manager, Flashify even used the terminal emulator and then entered the code to flash the recovery image I had in my sd card etc but everytime I use these tools it says that the recovery has been flashed and then when I reboot to recovery, I get the screen which says that a wrong version of android was flashed and that I should contact verizon and that screen keeps on coming even when i restart the phone, until I get my phone into download mode and then restart it. I have read alot of threads but couldn't find any at all. So is there any way to unlock my bootloader or to flash a recovery and then flash ROMS without unlocking the bootloader?
Would be really thankful if anyone could help.
hamid.ishfaq said:
Hey everyone,
So, I have a verizon Galaxy s3 4g (i535) and I have been searching for days now for a way to unlock my bootloader so that I can flash a recovery and then flash some new ROMS. I tried flashing a recovery through odin but it failed, I tried flashing it through the apps available in appstore like TWRP Manager, ROM Manager, Flashify even used the terminal emulator and then entered the code to flash the recovery image I had in my sd card etc but everytime I use these tools it says that the recovery has been flashed and then when I reboot to recovery, I get the screen which says that a wrong version of android was flashed and that I should contact verizon and that screen keeps on coming even when i restart the phone, until I get my phone into download mode and then restart it. I have read alot of threads but couldn't find any at all. So is there any way to unlock my bootloader or to flash a recovery and then flash ROMS without unlocking the bootloader?
Would be really thankful if anyone could help.
Click to expand...
Click to collapse
When the bootloader is locked, especially on this specific phone the SCH-I535 your stuck with it and there is no way to unlock the bootloader. You can't run custom roms or a custom recovery either
You can however install safestrap as a recovery and there are a few bootloader locked roms you can also install
Sent from my Nexus 5
hamid.ishfaq said:
Hey everyone,
So, I have a verizon Galaxy s3 4g (i535) and I have been searching for days now for a way to unlock my bootloader so that I can flash a recovery and then flash some new ROMS. I tried flashing a recovery through odin but it failed, I tried flashing it through the apps available in appstore like TWRP Manager, ROM Manager, Flashify even used the terminal emulator and then entered the code to flash the recovery image I had in my sd card etc but everytime I use these tools it says that the recovery has been flashed and then when I reboot to recovery, I get the screen which says that a wrong version of android was flashed and that I should contact verizon and that screen keeps on coming even when i restart the phone, until I get my phone into download mode and then restart it. I have read alot of threads but couldn't find any at all. So is there any way to unlock my bootloader or to flash a recovery and then flash ROMS without unlocking the bootloader?
Would be really thankful if anyone could help.
Click to expand...
Click to collapse
Yea I had the same issue like he said there's no way to unlock it only way you can flash ROMS is buy a rooted S3 that's what I did cause I couldn't take being on a locked bootloader phone I got mine from Ebay that's one way you can fix that problem now I'm running AOSB 4.4.4
I know how to unlock the BL,look at the screenshot.
Sent from my SCH-I535 using XDA Free mobile app
PS:the baseband is locked.
yuzhongdatou said:
I know how to unlock the BL,look at the screenshot.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
You do realize this photo proves nothing, right? This post could just as easily come from someone with an unlocked bootloader who subsequently flashed AOKP and also the VRUDNE1 modem. I'm using SlimKat with the same modem, doesn't mean my bootloader was locked with the VRUDNE1 4.4.2 update.
Sent from my SCH-I535 using Tapatalk
SlimSnoopOS said:
You do realize this photo proves nothing, right? This post could just as easily come from someone with an unlocked bootloader who subsequently flashed AOKP and also the VRUDNE1 modem. I'm using SlimKat with the same modem, doesn't mean my bootloader was locked with the VRUDNE1 4.4.2 update.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Amen to that man, people don't seem to get that the bootloader cannot be unlocked once the OTA is taken. I grow seriously tired of repeating myself a million times
Sent from my Nexus 5
So what's the deal then? You know there's a $1,400+ reward for unlocking it if you're serious. I'll gladly give you props for being first if you're right.
Sent from my SCH-I535 using XDA Free mobile app
o8o.o0880o.o8o said:
So what's the deal then? You know there's a $1,400+ reward for unlocking it if you're serious. I'll gladly give you props for being first if you're right.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
I'm unsure of what information your looking for exactly
Sent from my Nexus 5

Categories

Resources