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] bootloop after installing ANY custom ROM

Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!

TheLastGringo said:
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
Click to expand...
Click to collapse
Hi,
Did you root your phone?

Did you flash the superwipe zip first?
Also are you getting full reboots with HTC splash screen then animation or just the animation looping? Sometimes I have to let mine loop for 5 minutes after first boot of new rom before it settles.
Sent from my Sensation XE using XDA App

I guess I hadn't done everything.. I didn't factory reset before flashing the new ROM... As soon as I did that it boot right in. That's a bit odd to me, as I didn't have to do that with my last phone.
Anywho, solved.
Sent from my Sensation using XDA App

[q] bricked? Arhd bootloop

Hey guys, I been away from the sensation for a few months now and I think I bricked it on my first flash back! I was flashing ARHD & I followed the noob guide, I downloaded firmware & updated, deleted the firmware file, performed super wipe, flashed the rom, and I checked my md5 sums. Now I'm bootlooping the white HTC splash screen, and sometimes I see the beats audio symbol but right back to the slash screen! Ahhh.... I use this line for work. I used the 3.30 firmware as it said to & I'm on boot 1.27? I know one of you guys can help, so please ANYONE,I've got a get this fixed tonight.....

well if its booting then fortunately you're not bricked lol
have you tried re flashing the new firmware?

I flashed the 3.30 that the installation guide I was following told me to. I have ext 2.2, so is that an issue or is it the correct recovery.

Anyone who can walk me through this I'd really appreciate it guys. Just like most, I rely on my phone for work. I'm a little worried here, I've flashed quite a few times and I've never had an issue like this that I couldn't restore out of.....

Try this??
what I did was everything you did.. except I used this firmware update...
Firmware from 3.30.401.1 & 3.30.401.101 RUU
--- MD5 checksum: 824295C6ACDC8D55BED9E0B913192DBE *PG58IMG.zip ---
--- Only for 3.30.401.1 & 3.30.401.101 based ROMs
Then I installed the ICS Energy rom, and everything works great.. I've also flashed a few other roms without issues.. I haven't tried the arhd yet.. I'm currently running the virtuous AOSP rom.. and still, everything works great.. I hope this helps
Just a side note.. have you tried formatting the sdcard then trying that setup? I did have issues with my sdcard in the beginning, but after formatting, I've had no issues..Also make sure the ROM you're using is made for the correct firmware, otherwise you'll have bootloops! hope this helped!

That's the same firmware I used, and I've ran the firmware upgrade twice now. Now right after I updated the firmware the first time I did it, I rebooted on accident & it wouldn't boot even before I flashed arhd.... is this normal?

It wouldn't boot into hboot? What I did was put all the needed files on my sdcard, flashed the firmware, removed the sdcard(while the phone is powered on).. booted into the rom, then put the scdard back in and removed the firmware update..then rebooted the phone, then wiped and loaded an ICS rom..that was really about all I did.. and so far all works well.. I'm really at a loss as to what the problem on your end is.. it sounds like you've done everything you're suppose to do..

You could try to run the relevant ruu (assume you have s-off?) and start again?
http://forum.xda-developers.com/showthread.php?t=1074559

Update::II flashed Virtuous and had no issues and everything is running perfect. Looks just like my transformer prime now. I doing know why at this point that my system would not play nice with ARHD, I followed the guide to the letter and I flashed the firmware 3.30 several timed just as directed. None the less, I am satisfied with this from, and my device is much smoother and more productive than the ****ty GS2 by T-Mobile that I had been using the last few months! I just can't retire my Sensation. Thank you to all who chimed in, you're a great community!

Bricked
That happened to me too when I tried to install ICS without updating the firmware
first.
I just re-booted to recovery and did a restore. I'm assuming you backed up your
ROM right?
Then at least your phone will go back to normal and you can start over...and use it for work haha

I'm good now on virtuous, but I just couldn't get ARHD to work for me. Yes I had upgraded to the proper firmware first, and I always compare md5 sums. I'm by no means an expert, but I always research, read and ask all the nessecary questions before I flash anything I'm not familiar with. I think there may just be rare occasions when some of the devices just won't play nice with certain software. Virtuous took on the first flash & I'm actually very pleased with it, so all's well that ends well. ICS is just so much more intuitive & functional for me
.

New to android, a few rooting questions please.

Hey, i am new to rooting, actually the whole android intact. I decided to get a HTC ONE X after having the iPhone for a while. I have watched some videos on rooting and i think i have all that down with boot loader and stuff. I just have a few questions about other stuff regarding rooting the phone with customer ROM's.....
1) if i have a custom rom, and i get an OTA update, will that brick my phone if i do decide to update it? I know that it will take root off... but will it brick it if i just update without doing anything with custom rom?
2)Do custom roms (the one I'm looking at is the cyanogen mod for HTC ONE X) kill the battery more then normal?
3) How do you go back to stock rom if you no longer want the rom.... is it as easy as just going to the reboot screen and selecting stock rom? is the stock rom already on there or do i have to put it on there?
4) If wanted, how easy is it to un-root phone?
5) and just personal opinion, what is the best jellybean Custom rom out right now for HTC one X?
Thank you all so much!!

1 - You can't OTA update with a custom rom. Anyway, the custom roms (Sense based) are further updates than the AT&T updates.
2 - When I used CM10, it had quite a bit of wakelock but it's dependent on each phone as well. Many have great battery life.
3 - RUU
4 - When you RUU, you relock your bootloader and it brings it back to stock. Only difference is now in the bootloader, it says re-locked, not locked.
5 - CM10 is pretty good so far, but I'm a fan of AOKP.

1. The OTAs are pulled by software on the phone. Custom ROMs don't have this software and don't pull, so no need to worry.
2. Depends. Keep in mind the current JB ROMs are still a work in progress. CM10 does still have wakelocks, but its getting better.
3. Already said above. Just relock your bootloader and RUU.
4. Easy to unroot. Easy to relock. But once you unlock your bootloader your phone will never say LOCKED again. I honestly have never had an issue with it with warranty repair, but please don't be an asshat and flash a ROM for the wrong One X and then complain to AT&T.
5. Personal preference. The great things about custom ROMs is you can try a bunch out and find the one that you like. I used AOKP a while back and liked it. CM10 is pretty cool but I just had it for a few days as they work out the wakelock issues. Also check out some of the ICS ROMs. CleanROM is pretty solid as well and gives great performance. Don't necessarily limit yourself. That's the beauty of it.

On going back to stock rom, you dont necessarily need to use the ruu. After you get your phone rooted, unlocked, and a recovery for flashing your custom roms, then just make sure before you flash your first rom that you (from recovery) select factory reset (will erase all user data such as 3rd party apps and such) then perform a backup, also in recovery. Now,you have a safe stock rooted rom backup. Go flash any of the roms in this forum and at anytime you can always just go restore your stock rom back

[Q] When Flashing AOSP/AOKP/CM/PA Roms

Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..

pahlerc1 said:
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
Click to expand...
Click to collapse
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.

Abe21599 said:
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Click to expand...
Click to collapse
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again

pahlerc1 said:
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
Click to expand...
Click to collapse
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated

pahlerc1 said:
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
Click to expand...
Click to collapse
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?

Abe21599 said:
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Click to expand...
Click to collapse
It was in a different thread, can't recall which.. I have been doing way too much reading I think it was in one last few pages of the venom rom thread.. I'll just wait for Venom and Skyfall to update their baseband to the latest 1.56 build. No worries. Thanks.

Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.

ebb said:
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
Click to expand...
Click to collapse
Okay thanks for the help. I always make sure to read first and create a backup, I've made the mistake once and took a long process to get it solved and won't let that happen again that's for sure! Thanks for the response, I just flashed Skyfall 2.5 and it is amazing!