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
Related
Very strange issue.
I cannot upgrade my ROM above 2.3.3 and I can't upgrade the Recovery Image to anything new as well.
Does not matter if Official ROM or Not.
I am grabbing the Official ROMs from here:
http://forum.xda-developers.com/showthread.php?t=1445570
I am currently with Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
and If I try to install, 2.3.4, 2.3.6, or 4.03 the phone wont get past the "Google Logo" right from the beginning of boot. The screen will go Blank and the 4 soft keys will light up.
Before installing each ROM I am formatting/wiping cache, data, system & dalvik.
And Each ROM installation will claim that it installed successfully.
Recovery: So I am able to install ClockWork Recovery 3.0.2.4 and have it work.
I install the latest Clockwork ver. 5.0.2.0 it will install successfully, but not work.
And stop right after the Google Logo, as with ROM.
I have been at this for 2 days now. Any help would be AMAZING!!!
One last note: The phone was dropped, so maybe some how related, but I don't see how. The phone just came back from store that replaced the LCD. They claimed it was in a Recovery Loop. So I asked them to put CynogenMod. However they strangely put CynogenMod v 2.3.1 and not rooted.
are you flashing the right cwm recovery 5.x.x.x for your phone(amoled vs lcd)? try twrp recovery. do you wipe data(factory reset)before flashing? you should.
to Start, Thank you for the reply. Its very much appreciated.
So Yes, I am performing a full factory reset before flashing. And all of my most recent trials I used the native factory recovery that comes with each of the ROM's.
And I tried all of the below listed ROMs with the issue as described abouve.
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
And regards to the Custom Recovery(cwm) issue, I used what on the CynogenMod Wiki:
wiki(dot)cyanogenmod(dot)com/wiki/Nexus_S:_Full_Update_Guide
They don't have any differenciation between the OMOLED or Super LCD Versions:
(OMOLED I9020T, I9020A)
(Super LCD I9023)
Is there in fact different Recovery's for each of the abouve listed models????
Where would I find those recoverys?
And thank you again for your time.
Help - anyone? - Please :-(
vringo said:
Help - anyone? - Please :-(
Click to expand...
Click to collapse
try using twrp recovery, i find it more useful than clockwork recovery http://teamw.in/project/twrp2
---------- Post added at 04:26 PM ---------- Previous post was at 04:18 PM ----------
if you want to flash the official 4.0.3, then you need to flash the official 2.3.6 first. if youre flashing a custom 4.0.3, like cm9, then you dont need 2.3.6.
Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?
vringo said:
Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?
Click to expand...
Click to collapse
you should be able to. try a custom rom instead of an official. lots of aosp builds in the development section. they are pretty much pure android with a few mods. theres a pure aosp build in the development section too, its pure android 4.0.3 without mods. your bootloader is unlocked, right?
Yes, bootloader is unlocked.
will give some of the aosp builds a try now
vringo said:
Yes, bootloader is unlocked.
will give some of the aosp builds a try now
Click to expand...
Click to collapse
good luck
This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)
vringo said:
This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)
Click to expand...
Click to collapse
One more thing, anyway to know if the store that fixed my phone installed the wrong screen? LCD vs OMOLED?
clarification of the "issue" if ROM not working.
- Working phone (with 2.3.3) boot description:
You see Google Logo, and then the Logo will flicker momentarily, and Google Logo some more, and then the flying colored NEXUS logo animation, etc...
- Non functioning ROM boot description: You see the Google Logo, and then at about the time you would see the Google Logo flicker, that is when the screen goes black, and all 4 soft-keys light up. if you push the power button, sometimes the soft-keys will go black, and if you push again, light up again. At this point I have to pull the battery....
Same issue if I try to load the stock recovery from a non-functioning ROM. so Fastboot Mode will work, and then select Recovery, Google logo and then Black, with 4 lit softkeys, where the logo would normally flicker.
Why can't I install the stock firmware above 2.3.3????
I just tried the update ROM from 2.3.3 to 2.3.4 or 2.3.3 to 2.3.6 (all GRI40)
What could cause this issue????
could it be a partioning issue? what would cause such a weird issue?
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
confuz said:
This is the story
I first installed Unlocked bootloader from asus, CWM recovery for tf300t, and then i used the update.zip to gain root access
I downloaded the CM nightly build, used CWM to backup, then flashed the CM ROM.
It was stuck on CM boot logo for about 30 min, so i restarted and cleared my cache.
I tried flashing again, and it was still stuck on boot.
I then restored to my backup, and now it is stuck on the original ASUS boot animation.
What do I do?
Click to expand...
Click to collapse
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
CyberdyneSystems said:
restore with cwm,ifyou can, to earlier version,working
then remove ClockWorkMod Recovery, by fastbooting TWRP instead...much more reliable (team win recovery)
then to root, theres a theres a batch script tool, that,when tablet is connected to pc, will run and reboot the tablet several times, rooting it.
ill look for the link, its in the forums here, debug,defug..something
there are other methods,that worked the best for me...
CM had been having issues, install CleanROM 2.1 HAS THE JB UPDATE V13 in it. its smooth
Click to expand...
Click to collapse
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
try this thread...otherwise...you need to RMA it to asus,or the store you bought it from
http://www.scottsroms.com/showthread.php/1637-Tf300t-sku?p=13102#post13102
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
probably the bootloader, looks for a simple command,file....its not there,so its stuck in a loop
confuz said:
I have tried recovering with CWM, and restoring to factory settings.
Both didn't work.
Click to expand...
Click to collapse
First declare your bootloader. Have you ever been on a jb-rom, stock or otherwise?
Looking at git for cm it appears the kernel is 2.6, so I would expect that is not a jb rom.
cwm has some issues on this unit.
get into cwm and use fastboot to flash twrp for the proper bootloader you have.
or get into fastboot by use of power and volume down
at that point you can twrp a rom into place; probably not to restore your backup as twrp and cwm have issues reading each others backups.
Good Luck!
Note: If you can power up and access recovery (cwm in your case) you are not bricked and should be able to recover. I have as well as many others. Take your time and go a step at a time! Make back ups and make sure you have fastboot and adb access to your unit! If you are still ics bootloader consider nvflash once you have this mess sorted.
k4killer said:
I am having the same issue installing any ASOP roms on my tf300t.
I have the TWRP recovery, gained root by flashing.
I can install ASUS based roms like CleanROM fine, but I cannot flash any ASOP roms like CM10.
Just curious on what is preventing us from doing this. Especially when our devices are supposedly "unlocked" with custom recoveries and root.
If this device still continues to be this locked up, I might just have to sell mine when the GN2 comes out.
Click to expand...
Click to collapse
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Dfanzz said:
This is a known problem... once u get the OTA asus jb update, u can no longer flash any aokp or cyanogen jb roms. This is due to the kernel in these roms which are based on ics but since uve installed new ota jb bootloader it will not work and get stuck on boot screen. Restore in recovery will not work either. U need to download latest asus firmware and flash it then fastboot a recovery (i recommend twrp) and reroot.
Click to expand...
Click to collapse
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
k4killer said:
Ah, ok. I have the JB OTA update so i have the latest bootloader :/
I restored my nandroid of stock and it worked fine.
Just flashed CleanROM which is running great. Cant wait till the CM team gets the JB bootloader worked out as i have always loved being ASOP. Any info on when it might happen?
Click to expand...
Click to collapse
Great that ur nandroid worked! I know they r working on it... dont really have a time frame... just be on the lookout
Long time lurker first time poster. I had a Nexus One two years ago so I was here very very often.. Since I got my Desire S a year ago, I haven't been able to flash a custom rom OR S-OFF.
Unlocked with HTCdev, rooted, HBOOT 2.00.0002 (downgrading hboot never worked either), S-ON
Last night I tried again to get onto ICS (official RUU doesn't install either). I installed 4EXT touch, flashed recovery, had my ROM (Fallout) on SD ready. Rebooted phone into new recovery to find that is was still the OLD revolutionary recovery and not 4EXT. This was 4am so I thought I'd try the usual wiping + rom flash. It went through normally and said completed although the progress bar only got about 1/3rd before jumping straight to finished. Rebooted.. stuck at white HTC logo screen.
My issues are that I cannot install HTC Sync phone drivers without phone powering up to be recognised by the PC, AND I cannot turn USB debugging on for obvious reasons
My phone is veryvery important and I'm now scared I won't be able to get it working again. Please help me.
TLDR; stuck on White HTC logo screen, no Android installed, cannot see how I can install one, help!
If anyone could shine some light on what I need to do next, I'd be very grateful.
Thanks in advance.. and afterwards
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
teadrinker said:
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
Click to expand...
Click to collapse
For the 4EXT recovery I 'flashed' it from inside the touch app thinking that was enough these days.. naively. Had just been fighting with GF at 4am and was fed up and about to go to bed and in Revolutionary recovery so I thought what the hay, I'll wipe etc in here and use this to try and flash the rom.
I did not flash the boot.img. I goofed. I understand that but now I'm just desperate for any route back to a functional device.
I never stopped installing ROMs and etc on my old Nexus One but that was a while ago and everything just seemed to work. Desire S is being a nightmare.
Decide what you want to do.
If you want to upgrade the phone to official ROM - relock your bootloader and run RUU.
If you want to use custom ROMs - flash the recovery from fastboot and don't forget to flash the kernel from fastboot too.
I won't get into any more details, searching for the right info with these pointers will get you whatever you might need.
Thank you, I'm all fixed. Simply found an old 2.3.5 ROM and flashed and booted fine. Reason I was so stuck was because I had formatted my PC since last installing phone drivers so I couldn't do much hurdur
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