Database Info

Please help my nexux s

I just unrooted my nexus s (9020t) and returned it to stock. It came up with 2.3.1 originally and wanted to update it back to 2.3.3. I found the update drivers and tried to update it, and came up with the status 7 errors. If found the solutions, and tried to go from 2.3.1 to 2.3.2, than install the radio thing to 2.3.3. Up to 2.3.2, it came up with the same error and tried the last resort of updating it to the full 2.3.3 os.
After the update, the nexus s turns on to the google splash screen and hangs up there. I can still access the recovery by holding the volume up and power. I also tried to do factory reset, and wipe data. Nothing seems to help.
Any help?

I'm no expert by any means but you may have to use odin to get it going again. You will probably need to make a jig or buy one to get into download mode.
I hope this helps you and your able to get up and running again.
Sent from my Nexus S using XDA Premium App

I'm totally new into the android community and have no idea what Odin or jig is.
Since the fastboot is working, is there something that I'm missing with resetting orders or something else? I found that some one did a wipe dalvik (I think) with factory reset and cache, but I cannot find the dalvik.

donharden2002 said:
I'm no expert by any means but you may have to use odin to get it going again. You will probably need to make a jig or buy one to get into download mode.
I hope this helps you and your able to get up and running again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
You dont need a jig to get into download mode
Aslong as the bootloader is unlocked
Power down phone hold volume up/down then plug in USB from computer ....in download mode
Sent from my Nexus S using XDA App

im thinking if you could still access the bootloader then you can still flash clockworkmod. when you get that running, flash any rom u want in clockwork including stock 2.3.3. no odin necessary.

As long as you can still use fastboot there's no need to use Odin or JIG to flash the ROM.
I assume that:
you already have clockworkmod recovery installed and it's working properly.
your phone model is I9020T (SAMOLED)
If those are correct, I'd suggest you to download the 2.3.3 OTA package and flash it via clockworkmod (use the menu "Install zip from sdcard")
After flashing you'll have 2.3.3 on GRI40 running. And if you want to continue updating to 2.3.4, there's a thread dedicated to the topic.

PROBLEM SOLVED! Big appreciation to sonnysekhon who helped me over the phone at 11 in the night!
I was guided to just unlock fastboot, load the cwr and go into usb storage, add the cyanogen mod 7 and voila, problem solved. Now my only problem is, I've got 2.3.3 and want to update it to 2.3.4. Is there any easy way to do this?
Again, I want to thank you guys for the help!

SovereigN7 said:
PROBLEM SOLVED! Big appreciation to sonnysekhon who helped me over the phone at 11 in the night!
I was guided to just unlock fastboot, load the cwr and go into usb storage, add the cyanogen mod 7 and voila, problem solved. Now my only problem is, I've got 2.3.3 and want to update it to 2.3.4. Is there any easy way to do this?
Again, I want to thank you guys for the help!
Click to expand...
Click to collapse
Are you on cm7 or stock?
Sent from my Nexus S using XDA Premium App

I'm on cm7. It shows the cyanogen mod splash screen during bootup and has rom manager, file manager preinstalled.
I'm not really savvy when it comes to android mechanics because I just moved from itouch and iphones to androids couple days ago.

First of all. Congratulations on making the best decision! Iphone sucks. Lol.
Anyway, you can't update to 2.3.4 yet since its only available on stock right now. We're gonna have to wait until devs incorporate it into their custom roms. I believe there is a nightly version of cm7 that is already 2.3.4 but its not as stable as the 2.3.3 yet. hope that helps.
Sent from my Nexus S using XDA Premium App

yea you made the right move switching
Give it time you will get use to messing with Roms ..ect

Clockwork mod

I have rooted and unlocked phone but when it reboots into recovery its not listing all the options that will allow me to flash cm 7 nor cm9. Any help to get past this hurdle would be great thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Although I might be using the wrong recovery file if so direction the right one would be appreciated
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

What does it say the recovery version is ?

The first would be recovery 3e no Sig and then I've tried the advice from an earlier post for the galaxy is9000 I do believe. I just dropped 3e and going to try again with simply the is9000
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

OK- you are not rooted- you can go to post 2 here and get root and red cwm recovery - thanks to qkster and Entropy
http://forum.xda-developers.com/showthread.php?t=1524081

i thought that i might have been rooted since i can run diff rom managers, i do have super user access, titanium back up and a few others must have root apps. But i will try and thank you very much sir

If Titanium Backup asked for Superuser permission and you granted and TB did not say you are not rooted then you are correct, you are rooted. My answer still holds to go to post 2 to get the proper recovery.
Edit: + 10 on not using ROM Manager. (from Andros11 below)

Do not use Rom Manager. You can either flash Entropy's DD kernel to get red cwm recovery or look in the iset thread for gtg's guide for installing cwm, and use method 1 which requires you have the 3e modded recovery.
Sent from my sweet & buttery Infuse

ok ok for sure thank you very much i was wondering what i was doing wrong so i will take it all back to stock and start from scratch on this one here. But one more question i feel like there is an instability in the os so this what really prompted me to root this phone. The usb works at times, it turns on when it wants, it turns off and locks freezes completely when it wants, to turn it on i have to remove the battery put it back in then when the battery shows i have to plug in to the usb port for the computer to get it to start. Overall i do not know what my friend did to his phone but it's a night mare. have you heard of this occuring with anybody else sir?
But i have managed to unlock and get free wifi hotspot out of it smh

I like your approach, however it sounds like the problems may be related more to:
a : power button may be sticking
b: may have issues with usb connection, either on phone or on computer or both.
Before you go any further, make a backup of the current rom on the phone if possible.

Understood, i will flash the new CWM, back up then progress forward on that note. As for the usb i've used several and the one i am using right now is not registering where it did yesterday, and it is like a females emotions very fickle in nature. I will play with it a lil bit more to see if i can download via usb if not i'll use the sd-ms card to pick up the files and move forward at that point. Thank you very much sir you have been a big !!

[Q] (Q) Was on CM10, Flashed CWM 6.0.1.2 - "Could not do normal boot"

Okay, I've been running CM10 M1, and was ready to upgrade to M2 tonight.
I decided I'd go ahead and flash over to CWM 6.0.1.2 Touch while I was at it, as I would rather use a touch recovery.
Using the guide here in the first post...
http://forum.xda-developers.com/showthread.php?t=1840414
It says...
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
Click to expand...
Click to collapse
This is the file it has you download.
http://goo.im/devs/invisiblek/i535/recoveries/cwm-6.0.1.2-touch.img
Using that link you get an error,
The file you requested was not found
Lets see if we can find that for you...
Click to expand...
Click to collapse
I then backed up to this URL
http://goo.im/devs/invisiblek/i535/recoveries/
And downloaded...
cwm-6.0.1.2-touch.tar.md5
http://goo.im/devs/invisiblek/i535/recoveries/cwm-6.0.1.2-touch.tar.md5
I flashed it using Custom mode on EZ Recovery, and after rebooting into recovery, I get the "could not do normal boot" error screen, and can't do anything other than pull the battery.
I DID do a backup right before this, so what would be the best way for me to unscrew this?
Thanks for help ahead of time.

I'm pretty sure you're soft bricked. I don't think restoring your nandroid would fix this.
Follow Step #6 in droidstyle's guide(linked in my sig) and use the rooted version and start over.
For future reference .md5 files are to be flashed in Odin. That's where you went bad, flashing that md5 file thru the EZ Recovery.
Once you're back to where you were before it got fubar'd, here's the touch recovery that you can flash in EZ Recovery, https://www.dropbox.com/s/aqnnl5j8xc2u0ah/recovery-clockwork-touch-6.0.1.2-d2vzw.img (If this doesn't work I may need to re-share it. Just lemme know if it doesn't)

Thank you sir, I figured it was something like that. I'm downloading all of the files now, the rooted version is 1.5GB, so it'll be awhile.
I wonder why they haven't fixed that link in the post I quoted.
I'll post back here when I'm back on.
One more question for now, can I just get back to stock rooted, and then restore my nandroid backup, and then upgrade to M2?
Also, your download above went fine, let you know if it flashes fine.

Got it all ready to go, just one last quick question.
Isn't there a way to just flash the correct recovery via ODIN and bypass all this other stuff?

Tickle me pink, I did some googling and found this...
http://www.theandroidsoul.com/official-clockworkmod-cwm-recovery-for-verizon-galaxy-s3-guide/
Which lead me to this...
http://forum.xda-developers.com/showthread.php?t=1837605
I followed those steps instead, and flashed the correct recovery, got right back into CM10. Hope this helps someone else in the future.

How is cm10-m2? I'm thinking about jumping ship from synergy for a bit while we wait for a vzw/jb leak.
Sent from my SCH-I535 using Tapatalk 2
*edit-god damn auto correct.

I used CM10 M1 from the day after I got my phone, really had VERY few issues.
M2 so far is faster, very little lag. Battery life seems as good if not better (I had very good battery life on M1).
M1 was stable enough to run for a month, with just an occasional SOD a couple of times a week, but M2 seems to be more refined. I'm also running JUSTUNBean's Inverted GAPPS, which work perfect with it.
http://forum.xda-developers.com/showthread.php?t=1797292
Needless to say, it is damned good man. Give it a shot. Nice that a rom is this refined this early on.

[Q] Unauthorized software message ONLY when booting into recovery

This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?

Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.

Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?

Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.

Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?

Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.

[Q] KitKat ROM Attempt gone horribly wrong!

So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"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."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?

You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app

dustin_b said:
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?

jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app

dustin_b said:
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
and or use the casual all in one tool and follow root, and flash insecure aboot then download Rom manager from google play and install latest CWM

I just had my s3 replaced under warranty. The new one, I used casual to root/unlock, etc. Worked great! I think I let casual install everything then flashed CM from recovery.
Sent from my SCH-I535 using xda app-developers app

jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Not sure what you are trying to achieve, but once you get it back to functional and rooted, I would recommend you try out some of the wonderful custom TouchWIz ROMs on the forum here. They have most of if not more features than are in Kit Kat and there are no fully functional Kit Kat ROMSs for the S3 yet. Plus thse ROMs are stable and all your Samsung features will work properly . MORA, Hyperdrive, Synergy, and Jelly "beans" are good examples of excellent ROMs.

So I figured out what went wrong, and I'm still kicking myself for how stupid of problem it was. The reason Odin didn't want to work was because I was using the front USB ports on my system, which are not USB 2.0... I spent 6 hours trying to figure it out. So I hooked it up to a rear USB port, flashed it back to stock ROM, redid the Root, unlocked bootloader (which I didn't do in the first place) and now I'm getting Cyanogenmod on it.
Thanks everyone for the help! I hope anyone else who comes across this who where in the same boat I was can figure it out.
Sometimes it's a user-error.

Fix
jcaauwe said:
So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"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."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
Click to expand...
Click to collapse
i know you say you are ROOT but why dont you check using ROOT CHECKER download it from the play store its gonna tell you if you are root or not. im using sspencer10 KITKAT 4.4 CM11 and is running pretty smooth why don't you try it out just download the .zip reboot into RECOVERY i preffer you use TWRP (last version) go to whipe>advanced wipe and clear, Dalvik Cache>System>Data>Cache (optional i alwayz check mark Internal storage looking for space and alwayz make a clean flash same as Format Data) make sure you backup everything first using Titatinium Backup go back, then go to Install search for your .zip file on ur SDCard or Internal Storage first select the ROM ADD MORE FILE and add the GAPPS click REBOOT SYSTEM AND ENJOY YOUR NEW KITKAT 4.4 CM11 ON YOUR SGS3.

Don't be scared of Kit Kat! Once u get ur issues figured out and get 4.4 up and running you will see its all worth it!