Database Info

[Q] PLEASE HELP!!! Cannot Boot Nexus S!!

Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!

Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk

If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk

So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?

Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.

I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.

What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.

At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App

To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!

Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App

[Q] Rom Flash - Gummy or CM9

Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Some notes:
I was the the newest CWM Recovery Version
I checked all the MD5 and they all aligned perfectly
Thanks for any help I receive, if you want to know something else about my phone data during this procedure, just let me know.

so you flashed back to.33 or .608 before you flash cm9?
Sent from my DROID2 GLOBAL using xda premium

odnanreh12 said:
Before I started to flash a new ICS Rom (which I am quite excited about) I had a D2G on Hexen. I flashed the CM9 ROM and got bricked, so I SBF flashed back to stock and tried again. Again, a brick. I tried a third time with the same result and then decided to try Gummy instead (thinking there may be some issues with CM9 because it is in Beta). It also bricked. In the end I just flashed back to my backup that I saved from right before I began this process, but I would really like to take advantage of these new ROMs. If anyone has any advice I would be most thankful.
Click to expand...
Click to collapse
Hexen was made for 2.4.x stock firmware (Android 2.2 and the corresponding Motorola kernel).
All newer ROMs (CM7, CM9, Gummy, Apex, etc.) are based on 4.5.x. Update to 4.5.608 (preferably via SBF; do NOT accept any OTA updates once you're on 4.5.608) and proceed from there.

Ah thanks so much, I forgot that Android Firmware numbers had to match up, I will try again later tonight

forgot that Android Firmware numbers had to match up,
Click to expand...
Click to collapse
just fyi, not android firmware, moto's system version/firmware

Firmware must be watched
Sent from my GT-I9001 using xda premium

Stock p5113 ROM, anybody?

I am getting my Galaxy Tab 2 10.1 Wi-fi today. I would really like to install a custom ROM, but I am hesitant without the stock ROM to ODIN. I have bricked my Fascinate several times, and I would have been stuck without the stock ROM. However, it's more complicated because the ROM's I use for the Fascinate use an MTD filesystem. Is there a situation where I would be bricked without a way to restore to stock on the gtab, or does that sort of thing not happen? Anyway, is there a stock ROM available and will you link me?

not yet
from what i've read, there isn't a p5113 stock rom yet but time will give us one i am sure. in the meantime, the best we can do is make a backup in CWM before rooting and that would give you an unaltered stock ROM backup to restore from.

[Q] Would Samsung fix my bricked phone?

I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy

If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?

If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham

Yeah, you can still fix it. No need it to bring to samsung

Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?

random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.

cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!

Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!

random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!

[Q] Has this been tried?

So up until a week ago I was running CM11, but for the past month I was having battery issues so I decided to revert back to stock to test if it was the battery or the ROM. So I flash my phone back to stock and update to 4.4.2 knowing that I still had all the tools still available in case I wanted to flash back to CM11. Now today I wanted to flash back to CM11, but I wanted to make sure the methods were still correct to flash back to CM most concerning the bootloader, and to my dismay I found out that everything changed for the worse. On the bright side I was able to root my phone but unfortunately I flashed CWM recovery so now I can't get into recovery, but I can still access my phone so its not hard bricked to the point I have to JTAG, but my first question is how do I revert back to system recovery, I made a nandroid backup before I flashed the recovery but would that still work? And my second question is are there any ROMS you can install that allow you to run a custom recovery or allow you to flash back to 4.1.2? Either way, I'm glad I decided to double checks facts before proceeding or I would've had a bricked phone.

Flameancer said:
So up until a week ago I was running CM11, but for the past month I was having battery issues so I decided to revert back to stock to test if it was the battery or the ROM. So I flash my phone back to stock and update to 4.4.2 knowing that I still had all the tools still available in case I wanted to flash back to CM11. Now today I wanted to flash back to CM11, but I wanted to make sure the methods were still correct to flash back to CM most concerning the bootloader, and to my dismay I found out that everything changed for the worse. On the bright side I was able to root my phone but unfortunately I flashed CWM recovery so now I can't get into recovery, but I can still access my phone so its not hard bricked to the point I have to JTAG, but my first question is how do I revert back to system recovery, I made a nandroid backup before I flashed the recovery but would that still work? And my second question is are there any ROMS you can install that allow you to run a custom recovery or allow you to flash back to 4.1.2? Either way, I'm glad I decided to double checks facts before proceeding or I would've had a bricked phone.
Click to expand...
Click to collapse
No custom recovery and no flashing back to 4.1.2. It is safestrap only and 4.4.2 touchwiz ROMs only, of which there is only one right now. Unless you are willing to send your phone to mobile tech videos and pay them $50. They are apparently ale to revert you're phone to 4.1.2.
You should have done a little more reading of all the warnings available in the forums before going back to stock and taking the update to 4.4.2.
Sent from the Shark Tank using XDA Premium 4 mobile app

landshark68 said:
No custom recovery and no flashing back to 4.1.2. It is safestrap only and 4.4.2 touchwiz ROMs only, of which there is only one right now. Unless you are willing to send your phone to mobile tech videos and pay them $50. They are apparently ale to revert you're phone to 4.1.2.
You should have done a little more reading of all the warnings available in the forums before going back to stock and taking the update to 4.4.2.
Sent from the Shark Tank using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, that answers my second question, but is there anyways to reflash the stock recovery for 4.4.2?

Flameancer said:
Ok, that answers my second question, but is there anyways to reflash the stock recovery for 4.4.2?
Click to expand...
Click to collapse
There is if you can find one, but I don't think it's posted anywhere. Your best bet is to just Odin flash a stock 4.4.2 rom and start over again.
Sent from my HTC6525LVW using Tapatalk