Database Develop

[ROM] [NANDROID BACKUP] Stock GRH78 for Nexus S Android 2.3.1

I created a Nandroid backup of the stock Nexus S Rom. This includes the latest OTA GRH78 that just got pushed out today 12/22/10. This is 100% stock.
Link: http://www.mediafire.com/?ontvvh8z9h9lb7a
WARNING: This will wipe everything on your phone
Requirements:
-Clockwork recovery or other custom recovery
-The nandroid backup from here http://www.mediafire.com/?ontvvh8z9h9lb7a
-Transfer cable, to transfer contents of downloaded file to phone's internal memory
Instructions:
1. Download nandroid file from link provided above
2. Extract the .zip file on your computer
3. Move the folder "2010-12-22.21.06.07" to the clockworkmod/backup/ directory of your phones internal storage
Note: if you have never used nandroid you wont have the directory clockworkmod/backup on your phones internal storage, so you will have to manually create those folders, then put the folder "2010-12-22.21.06.07" in the new folders you created
4. Now go into your clockwork recovery manager, you can do this by typing in "adb reboot recovery" if you have adb setup on your computer, and the phone is connected. Or while the phone is turned off hold the volume up+power to get into bootloader mode, then go down to "recovery" by using the volume up/volume down keys to scroll up or down, then press the power button to launch it, and this will launch the recovery manager
5. Once your in clockwork mod recovery select "backup and restore"
6. Then click "restore"
7. Now you should be able to choose and select "2010-12-22.21.06.07"
8. Clockwork will now restore this nandroid backup
9. Reboot system
Note: This version of android build "GRH78" will make sure you have the stock recovery manager everytime you reboot the phone. So after doing this, after you reboot you will no longer have clockwork mod.
Edit: According to xda member Luxferro the new update introduced /etc/install-recovery which may have not been in 2.3, but anyways, it runs this on bootup, and if the MD5 of the recovery doesn't match what is expected, it reflashes the stock recovery back over, so if you dont want the stock recovery to be flashed everytime you boot if your on clockwork or another non stock rom, just rename it to prevent it from running on boot. And for those of you who want to return your phone back to stock this nandroid will do that for you since it also flashes the stock recovery.
Video on how to unroot the nexus s and return to stock
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Video via xda member dcogen

will this method rest the phone and erase phone info?

yungfresh said:
will this method rest the phone and erase phone info?
Click to expand...
Click to collapse
yes this will erase everything, this is meant for people who want to go back to stock.

I unlocked the bootloader and flashed clockword mod only. I didn't flash any custom roms. If I do this method, will it lock the bootloader and remove clockword mod?

yungfresh said:
I unlocked the bootloader and flashed clockword mod only. I didn't flash any custom roms. If I do this method, will it lock the bootloader and remove clockword mod?
Click to expand...
Click to collapse
No, this will not touch the bootloader, or the recovery. The phone bootloader will stay unlocked, and the recovery manager will stay in tact.

Hi there, your "stock" nandroid is screwed up.
I just tried it right now and TONS of apps are missing from the market with your nandroid.
PayPal, NYTimes, aFile, Fios Mobile Remote, TONS of stuff that I had are gone from the Market.
I pulled out my SIM card, and still all missing.
I restored my Nandroid of my current system, and they're all back in the Market.

nxt said:
Hi there, your "stock" nandroid is screwed up.
I just tried it right now and TONS of apps are missing from the market with your nandroid.
PayPal, NYTimes, aFile, Fios Mobile Remote, TONS of stuff that I had are gone from the Market.
I pulled out my SIM card, and still all missing.
I restored my Nandroid of my current system, and they're all back in the Market.
Click to expand...
Click to collapse
Hmm, very odd. Anyone else having this issue?
Sent from my Nexus S using XDA App

momohammed20 said:
No, this will not touch the bootloader, or the recovery. The phone bootloader will stay unlocked, and the recovery manager will stay in tact.
Click to expand...
Click to collapse
so... for people that want to fully return to stock:
apply this update. go to fastboot mode and then do a fastboot oem lock. this will reset the phone and recovery partition to full stock.
you can check this by rebooting into recovery and now the recovery will be stock.

I don't think his nandroid file is messed up, there's a different market version its now 2.13 not 2.12 like on the previous build. I think that has something to do with it

Now I'm having a problem with everytime I reboot the phone I lose clockworkmod recovery an I got to reflash it with rom manager. I don't lose root tho but I lost it when I did his nandroid an had to reroot

momohammed20 said:
Hmm, very odd. Anyone else having this issue?
Click to expand...
Click to collapse
Yup. I tried it, and I'm missing those apps as well.

Yes, me too. I lost many of the apps available in the market and the ability to go into recovery.

*Facepalm
These apps were missing from the Nexus S originally on day 1... Lol.
It's how Android market works. New builds don't get full market support. You need to wait for Google to update their system to allow the new build to get copy protected apps from the market.
Will this wipe my sd card?

I just checked and I don't have those apps either in market, and I'm on stock.
Sent from my Nexus S using XDA App

Sigh! You're not supposed to have those apps.
It's not an issue with this nandroid, it's an issue with every single new version / update to android on any phone. You will always have missing apps until Google adds the build number to its servers.
Other than that, thanks a lot for posting this OP! Saved me a huge pain in the ass getting updated -_-

Yes, maybe the apps issue is an issue with the server not updating yet, but have you noticed any problem with the clockwork recovery not functioning after reboot?

My recovery reverted to 3e recovery after flashing this. Clockwork is gone. No problem though, I wanted clockwork gone.
Now how do we root without flashing clockwork ?

I will try to investigate the recovery issue. But some people wanted to go back to stock recovery, and were not able to with the stock recoveries floating around, so that's pretty odd that this nandroid takes you back to stock recovery.
Sent from my Nexus S using XDA App

bogdi1988 said:
so... for people that want to fully return to stock:
apply this update. go to fastboot mode and then do a fastboot oem lock. this will reset the phone and recovery partition to full stock.
you can check this by rebooting into recovery and now the recovery will be stock.
Click to expand...
Click to collapse
Really? That's interesting. Has anyone actually done this and confirmed it restores stock recovery? Easy fix for something that's been vexing quite a few people the last few days.

How long till the Market "fixes" itself and updates to 2.1.2 so the missing apps appear on the market?

Weird issue with flashing

Hey Guys,
Before i start let me explain that i use to cook roms for my magic, so i know what im doing with this stuff.
Anywho i have been having a weird issue where whenever i flash a rom, it will not boot to either the rom or back into the recovery. my only option is to relock the bootloader and flash back to the stock ruu, and reinstall recovery.. right now im stuck on the stock rom and i hate it!
btw the device is s-off and unlocked bootloader, so wth, if anyone has any advice please let me know!

Did you try reflashing the recovery? Or a different recovery ? had a problem once with my pc antivirus blocking certain files and was causing the zip to be corrupted , just some thoughts

shael said:
Hey Guys,
whenever i flash a rom, it will not boot to either the rom or back into the recovery.
Click to expand...
Click to collapse
All you get is the white HTC screen when you reboot?
What about when you boot into HBOOT, then choose recovery manually?
As you mentioned, you're used to this stuff, so this part probably isnt helpful - do you do the 4 wipes when flashing? (data/cache/dalvik/system?)
I wonder if (even though you are S-OFF), the kernel portion of the rom isnt flashing? This can cause your phone not to boot and just sit there... i.e. your phone hasn't experienced a stockish/insecure kernel flash first, so recovery is having trouble flashing the custom recovery that comes with the rom.
See this thread for more info (it helped another user):
http://forum.xda-developers.com/showthread.php?p=30658376#post30658376
Also - to what Bigtjmc is saying - in the link above, I mention the recovery I use (which has not let me down at all!) Maybe you want to try it (if you're not using it already?)

so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?

shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
Try Wildchild's Recovery (by far MY most favorite)
And if it's not passing verificiation, like the other user said check your anti-virus and check the MD5 Checksum to make sure you have a complete good download, wipe all data cache and blah blah blah then with fastboot "fastboot flash boot <Insert kernel file name here>.img

hmm, well in the past ive always flashed kernel with fastboot... its almost like my chip timed out and wont let me flash the kernel anymore :s

If recovery is crashing you might need to relock the bl and run the stock ics ruu to get you back up and running then try n start over , I used the tool kit just this morning for the same troubles and got back where I wanted to be in just a few minutes .

shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
This happened to me as well... can't remember what script it was that was running but there is a script that is associated with a rom (vague I know) that is messing up the cache partition. If I remember correctly I also might be associated to the recovery you are using... but I can't remember. Anyway, If you do a fastboot erase cache command from the bootloader and re-flash the recovery of your choice you should be back to normal.

Awesome, thanks for you help guys, unfortunatley i dont have easy access to a pc, so i gotta wait a bit before i can try this... thanks again though

OMG!!!!! you guys are simply amazing, thank you everyone for your help! wiping the cache from fastboot, then flashing stockish kernel, then flashing cwm recovery, then wiping cache, and factory reset, then flashing my rom worked!!! <3

Trying to install 4.4 Rom, falling at every hurdle.

Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers

Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?

If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk

eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.

Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app

shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone

SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk

Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!

Clockworkmod Recovery Galaxy s3 problems

Well guys this is my first time on the forums. My phone is rendered near useless right now. A few days ago, i rooted my phone via towelroot. as a friend reccomended, i installed ROM manager and flashed clockworkmod recovery. I backed up my stock, perfect ROM with CWM and decided to try installing cyanogenmod 10.3.1......... it wouldn't install. I even tried other apps like ROM installer. Then i came across the handy dandy Cyanogenmod Installer. This seemed great, i didn't have to do anything except click a few buttons on my PC. as i was ready to enjoy a new custom ROM, the following message popped up, "Root access possibly lost. Fix?". I was given the options of "No" and "Yes - Fix root (/system/xbin/su)". i chose the second one, and waited for my device to boot. when it did, it was stock Touchwiz Android version 4.4.2, just like i had initially. what's more is my imei and bandwidth version were both "unknown" and i my sim card was undetected. I decided that technology had gotten the better of my and i tried to flash my old stock ROM back on. i found the file in recovery mode but it kept saying "no files found" whenever i clicked on it. I tried the cyanogenmod installer again, this time choosing "No", resulting in exactly the same scenario. At this point, I would be fine having the stock ROM since i have had such bad luck with the "developer's world" of Android.......... PLEASE HELP!!!!!

Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......

EddyTeddy01 said:
Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......
Click to expand...
Click to collapse
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.

touchbattle.mika said:
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.
Click to expand...
Click to collapse
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?

EddyTeddy01 said:
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?
Click to expand...
Click to collapse
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide

MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.

EddyTeddy01 said:
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.
Click to expand...
Click to collapse
it´s the best if you also do a format of internal sd in recovery before changing the recovery, because sometimes there are some folders left of it in interrnal memory and you cant delete it, do that if this will be the case. but i think Philz and CWM use same folder, so if you flash philz it will be okay if im correct otherwise you can always format internal sd afterwards
Edit: dont use rom manager for recovery actions, use recovery itself, much more reliable

MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
That guide made it possible for me to install all custom roms. Witz the recovery installed first it did not work. Thx

Help| Get to stock Kernel and unroot

Hi, I have a OP3t running OOS4.1.1 with ElementalX Kernel.
I would like to go back to stock settings. Stock Kernel, Recovery, unroot, and maybe lock bootloader.
I've seen a lot of videos showing how to get back to stock but they showed it with the stock Kernel.
I am a little bit scared to follow their instructions since I have a different Kernel.

HeroPlane said:
Hi, I have a OP3t running OOS4.1.1 with ElementalX Kernel.
I would like to go back to stock settings. Stock Kernel, Recovery, unroot, and maybe lock bootloader.
I've seen a lot of videos showing how to get back to stock but they showed it with the stock Kernel.
I am a little bit scared to follow their instructions since I have a different Kernel.
Click to expand...
Click to collapse
Dirty flash the stock ROM and you're done
Download stock recovery and flash with twrp

dipeshdidwani said:
Dirty flash the stock ROM and you're done
Download stock recovery and flash with twrp
Click to expand...
Click to collapse
Oh wow so I don't even need to erase my personal data.
Just flash the OOS Zip with TWRP and then flash the stock recovery from fastboot, or it must be from TWRP?

HeroPlane said:
Oh wow so I don't even need to erase my personal data.
Just flash the OOS Zip with TWRP and then flash the stock recovery from fastboot, or it must be from TWRP?
Click to expand...
Click to collapse
You can do it both ways