Hello all,
Today I attempted to install android 4.0.3 ICS unofficially on my beloved AT&T Nexus S i9020A. I did this by unlocking my bootloader, then flashing clockwordkmod 3.0.0.0. crespo img, then flashing the stock i9020t (t-mobile) ics rom, planning to later flash the AT&T radios and get the update that way. This all failed however, because upon rebooting, my phone was stuck at the boot screen that says "google", and shows the unlocked lock, symbolizing the unlocked bootloader. I waited 15 minutes, and it would not go past this screen. I took out the battery and tried again, and still no luck. I then went back to the boot loader and into clockworkmod recovery (which still boots), and tried to install the stock i9020a 2.3.6. The install fails every time. It says there is no "cache" partition on my phone. I installed cyanogenmod 7 and it says the installation succeeded, but i still cannot boot past the google screen. I can only access the unlocked bootloader screen and clockwordmod. I have included screenshots of what happens in clockworkmod when I boot it up, or try to install a rom. Any help would really be very much appreciated. I am very sad to lose my beloved $529 phone, which has served me very well.
This is the guide I used to flash ICS:
http://dottech.org/mobile/android/25324/how-to-update-nexus-s-to-ice-cream-sandwich-android-4-x/
This is the guide I used to unlock my boot loader and flash clockwordmod:
http://forum.xda-developers.com/showthread.php?t=878446
you need a newer version of clockwork recovery, that one is old and wont work with ics. or you can try twrp recovery, i prefer it personally. i believe clockwork recovery is up to 5.0.2.X
Thank you so much! How would I flash a new version if I can't boot into any OS?
..
Ok. I've installed clockworkmod recovery touch (I believe it is the latest one) and was able to revert to cyanogenmod 7. THANK YOU SO MUCH!!! I really cannot thank you enough! You have saved my nexus!!!
monoloco1 said:
Ok. I've installed clockworkmod recovery touch (I believe it is the latest one) and was able to revert to cyanogenmod 7. THANK YOU SO MUCH!!! I really cannot thank you enough! You have saved my nexus!!!
Click to expand...
Click to collapse
no thanks needed, your excitement is enough
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
EDIT: I have done some tweaking with restoring my old back up and I have come to the conclusion that my /system folder is corrupt, i know a few ways to fix that but anyone one the best way and maybe a 2.3.4 system folder to use?
EDIT2: I replaced my system folder with one that i have and now it gets past the white htc screen but will loop the sprint 4g screens.
FIXED IT,\: what I did was I managed to RUU back to 2.2 through this thread, now I am on 2.2 and will continue to get an s-off root, thank you for all your help
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
Can you get into bootloader? If so, what is your hboot version and software version?
Just in case you don't know how, to get into bootloader, you need to power off or pull battery, then press and hold VolDown+Power until the white bootloader screen comes up
At the top it tells you the hboot version
Sent from my PG06100 using xda premium
I can get into bootloader.
hboot-0.99.0001
radio-1.08.01.0111
thats all I can get about my version
11telisz said:
Alright, I have looked and tried almost everything I could find to help me on this but nothing has worked yet, my problem is my screen gets stuck in the HTC boot screen and won't move any further, what I did to get it to this is I got my shift rooted though the htcdev site, but it is not s-off, I wanted to install a cyanogen mod, the 7.2 one on it, well i went to CWM and said install aborted so I tried to reboot my phone and now stuck, i can still get into the CWM recovery but nothing has helped yet,I have tried to push several boot.img files, and tried to downgrade to 2.2 and nothing...I am all up for ideas.
Click to expand...
Click to collapse
When you went through HTC-Dev.com you did not Root the Device. All you can do at the site is Unlock the Bootloader. To resolve the issue you can try a Factory Data Restore in Bootloader, but you are going to lose all the current Data on the Device. It may or may not work. If it does not then, you may have to run an RUU. To do the Factory Restore pull the Battery on the device. Then put the Battery back in. Hold Volume Button down , now at the same time press the Power Button. It will boot into Bootloader. Once it is in Bootloader use the Volume Rockers to toggle Up, or Down. Then choose Factory Restore by pressing the Pwer Button. Since your not rooted that's your only option that I know of other than an RUU. If that does get you out of the White Screen I would suggest finding out your Android version. Then following the correct process to attain Full Root.
Maybe I was a bit unclear, I went though the htcdev site to unlock the bootloader, then i moved clockworkmod recovery instead of the stock recovery, i then installed superuser through Clockworkmod, so i had root though that, but not an s-off root, so I then installed ROM manager and thought the cyanogen 7.2 rom would be a cool one to have, I forgot it was not an s-off root, so i went ahead with downloading it though Rom manager and it prompted me to install the new rom, and brought me to clockworkmod recovery and said the install was aborted, and i rebooted and then it got stuck at the htc screen, I can get into bootloader and clockworkmod recovery, I have a backup of my stock rom on my computer and put it onto my sd card hoping i can restore to that one, but i get the md5 mismatch error, working on fixing that now.
I still believe that most of the issue is that you are not Fully Rooted. What version of Android where you on when you started ? The reason I ask is because the method you used is a bit unorthodox, so I doubt your Rooted. I would still suggest doing a factory Restore. But you can look HERE on how to fix the MD5 mismatch error.
Yeah, if you only unlocked bootloader, thats not a full root, you still have a ways to go
The best thing would be to just RUU and start over using VICODAN's method, which covers 2.2 all the way up to 2.3.4
Sent from my PG06100 using xda premium
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
11telisz said:
The method i used for rooting was though this post, I got up to the step downgrading from 2.3.4 to 2.2 till about step 17 of the 2.3.4, I wasn't sure if it acutally downgraded to 2.2 because I am unable to check my version though the bootloader or clockworkmod recovery, so I most likely am still on 2.3.4
Click to expand...
Click to collapse
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
prboy1969 said:
Ok so your defiantly not on 2.2 . The question is what version of 2.3.4 are you on ? Go into HBoot and go to System Info. What is the OS Ver. ? Have you tried doing a Factory Reset just to see if it will Boot back up ?
Click to expand...
Click to collapse
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
11telisz said:
There is no system info tab in my hboot menu, but i believe i know what is wrong, somehow my /system folder got corrupt, so i have to replace my /system folder with a new one, i know a few methods but what is the best method to going about that with an s-on?
Click to expand...
Click to collapse
The only way I know how to do it would be using adb and just flashing all the images through that.
Sent from my PG06100 using xda premium
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Dissentire77 said:
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Click to expand...
Click to collapse
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
WhatTheAndroid? said:
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
Click to expand...
Click to collapse
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Dissentire77 said:
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Click to expand...
Click to collapse
Sounds like a thanks button click is on order for WhatTheAndroids post to you
ViperXL 2.4.0 w/ElementalX 3.1 kernel
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
hrrsncrawford14 said:
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
Click to expand...
Click to collapse
Had that happen to me. But just had to flash a kernel for it to boot properly. Everything fine after that.
Sent from my HTC One X using Tapatalk 2
THANKS!!! I have it working now thanks to the suggestions! :laugh::laugh:
DvineLord said:
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
Click to expand...
Click to collapse
glad u got it working again. i would recommend doing s-off so you don't have to flash boot.img separately anymore.
I have an AT&T HTC One X that's rooted. I wanted to put Cyanogenmod 10 on it, but I accidently wiped the System files instead of the cache. Now it can't boot up regularly, I've tried using Rom Update Utility but it doesn't seem to work. Factory Reset doesn't seem to work either. I didn't expect this to happen because my friend just flashed his a couple of days ago. I've tried making a backup and restoring but no matter what I can't get the phone to start up normally. Unless I put it in TWRP (Team Win Recovery Project) or the HBoot/Bootloader I really can't use it for anything. Any suggestions? I would greatly appreciate it. Also when bootloader opens it says "Tampered" and under it "Unlocked" because I did root it. It didn't have "Tampered" when I first rooted it.
I don't care about Cyanogenmod 10 anymore I just want to have it working again.
Everything else about the phone is in perfect condition but what I just said is the only problem.
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
iElvis said:
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
Click to expand...
Click to collapse
Well, I've already flashed it to a few things and so far it hasn't changed anything. Got any links?
Did you fastboot flash boot boot.IMG ? Don't know what hboot you are on, but could be it.
Sent from my Carbon-ize Evita using xda-developers app