FIXED! - Turns out i missed out flashing the boot.img
Hi!
I've been trying to install the Slim ICS on my international HTC One X for a few days now.
1. Unlocked Bootloader
2. Installed CWM
3. Wipe Data/Factory Reset, Wipe Davlik Cache, Format /system
4. Flashed HOX_4.2.zip
5. Flashed Slim_Common.zip
The result is that I'm stuck in a boot loop with the HTC symbol and the Slim ICS boot screen.
I've also tried to erase cache while in fastboot.
I can't seem to find anyone else being unsuccessful in their attempt to flash 4.2 Slim ICS.
Did I miss out on a boot.img? The install instructions from the Slim ICS site mentions using a boot.img from essentials, but essentials were removed from 4.1 onwards so I'm a little confused there.
Otherwise, do I need to flash a kernel? If so, which kernel. Otherwise, what else should I do?
I've actually tried to flash Faux 4b5, but that bricked my phone completely on a HTC Logo only boot loop. But I managed to recover it using an RUU.
Would really appreciate any help and advice very much.
I do have a nandriod backup of the stock rom flashed so all is still good.
Related
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Probably something wrong with your install. Did you wipe dalvik cache, etc.?
Reflash new boot.img.
Sent from XDA App using HTC One X.
PCHAPM said:
I successfully loaded the latest Cordroid ROM V4 on HTC One X as far as install goes. However on reboot I get the Sense ring screen which am unable to use before phone reboots.
In a constant boot loop.
Thankfully took a Rom backup prior to install that got me out of trouble.
Anyone else managed to get this to work or is there an error in the Rom or the way I am installing?
Not had issues with previous Roms from Coredroid….
Click to expand...
Click to collapse
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
vivek_bhoj said:
perform full wipe, clear cache and dalvik cache before installing v4 as it has new kernel and reflash boot image and reinstall ROM again
Click to expand...
Click to collapse
Had done the full wipe and cleared both cache but not the reflash of boot imgage this did the trick. Thanks for the great help.......
Hi all, I'm pretty familiar with flashing custom ROMs as I previously had a Samsung Galaxy S Captivate.
I recently got a Telus T989D, and I'm having some frustrating problems trying to flash a custom ROM. I have ClockWorkMod Recovery installed, and have been trying to flash various Cyanogen CM9 ROMs onto the phone. They all install properly, but once it gets to the Cyanogen splash screen (with the Android man turning angry for CM9), it gets stuck here.
I thought perhaps I needed to flash my radio, since all these custom ROMs were for the T-Mobile T989 "hercules" model. So I flashed the SGH-T989_UVLE1_radio.zip hoping that would work. Same problem.
Kind of at a road block here - any suggestions would be very much appreciated. Thanks!
Rhombuss said:
Hi all, I'm pretty familiar with flashing custom ROMs as I previously had a Samsung Galaxy S Captivate.
I recently got a Telus T989D, and I'm having some frustrating problems trying to flash a custom ROM. I have ClockWorkMod Recovery installed, and have been trying to flash various Cyanogen CM9 ROMs onto the phone. They all install properly, but once it gets to the Cyanogen splash screen (with the Android man turning angry for CM9), it gets stuck here.
I thought perhaps I needed to flash my radio, since all these custom ROMs were for the T-Mobile T989 "hercules" model. So I flashed the SGH-T989_UVLE1_radio.zip hoping that would work. Same problem.
Kind of at a road block here - any suggestions would be very much appreciated. Thanks!
Click to expand...
Click to collapse
Oh, and to clarify in case anyone asks - I have been doing data/cache/Dalvik wipes in recovery before installing the ROM.
Rhombuss said:
Oh, and to clarify in case anyone asks - I have been doing data/cache/Dalvik wipes in recovery before installing the ROM.
Click to expand...
Click to collapse
If you are running CWM 5.0.2.7 non touch recovery, you have to use TDJs Superwipe script first to wipe data partition and system partition. Then you flash the ICS radio (if you haven't done so already) then the CM9 ROM, then ICS Gapps.
After this you need to flash TDJs Cache Wipe script. This will properly wipe cache, dalvik, and fix permissions. CWM 5.0.2.7 doesn't wipe and align the cache properly and gives problems. I never had any issues with CWM when running those scripts and it boots up everytime.
Alternatively, you may want to install TWRP 2.2.2 instead of CWM. It's a touch based recovery, but very simple to use and much better than CWM in my opinion. You also don't need to run the scripts since the data and system are wiped properly and cache and dalvik are also cleared properly as well.
If you go to the development section, under the TWRP thread, and search for flashable zip, there is a 2.2.2 flashable available that you can use in CWM. Then the next time you boot into recovery you will be in TWRP instead of CWM.
Chochiwpg said:
If you are running CWM 5.0.2.7 non touch recovery, you have to use TDJs Superwipe script first to wipe data partition and system partition. Then you flash the ICS radio (if you haven't done so already) then the CM9 ROM, then ICS Gapps.
After this you need to flash TDJs Cache Wipe script. This will properly wipe cache, dalvik, and fix permissions. CWM 5.0.2.7 doesn't wipe and align the cache properly and gives problems. I never had any issues with CWM when running those scripts and it boots up everytime.
Alternatively, you may want to install TWRP 2.2.2 instead of CWM. It's a touch based recovery, but very simple to use and much better than CWM in my opinion. You also don't need to run the scripts since the data and system are wiped properly and cache and dalvik are also cleared properly as well.
If you go to the development section, under the TWRP thread, and search for flashable zip, there is a 2.2.2 flashable available that you can use in CWM. Then the next time you boot into recovery you will be in TWRP instead of CWM.
Click to expand...
Click to collapse
I just installed TWRP and I'm still running into the same issue. The Cyanogen splash screen just runs indefinitely. Looks like that wasn't the problem? Does it matter if you're rooted or not, if you try to flash a ROM from recovery?
Rhombuss said:
I just installed TWRP and I'm still running into the same issue. The Cyanogen splash screen just runs indefinitely. Looks like that wasn't the problem? Does it matter if you're rooted or not, if you try to flash a ROM from recovery?
Click to expand...
Click to collapse
Use the Darkside Superwipe to recreate all your partitions correctly. Sometimes when they are not aligned properly (by TWRP) you get weird boot hangs.
Don't restore data! Instead back everything up with something like Titanium and restore user apps only after the ROM has booted and you are satisfied.
+1 for the last post. Should work 100%!
Sent from my SGH-T989 using xda premium
---------- Post added at 12:17 AM ---------- Previous post was at 12:09 AM ----------
http://forum.xda-developers.com/showthread.php?t=1477955
Sent from my SGH-T989 using xda premium
Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.
Ask me for information if you need it.
I've flashed ROMs so many times on this phone I got far passed used to it, and this is one of the only times I've actually managed to softbrick it. I was trying to re-flash x3reme sense after finding out CM10 has a failure of GAPPs and neither of the downloads I have of it works, kind of weird. Anyways, after flashing the ROM, then the kernel, it seemed to be softbricked. This is what I did:
1. Downloaded ROM.zip and extracted boot.img.
2. Moved ROM.zip onto SD Card
3. Wiped cache, dalvik cache, system, and did a factory reset.
4. Flashed ROM.zip
5. Flashed boot.img
6. Rebooted
Now, I am stuck on the HTC screen and I have no clue what I did wrong. I've done this every time I've installed a ROM and it never failed me, besides now. I also tried using Jmz's kernel, and I'm about to try the SuperSick kernel and probably a few others until I unbrick it. Are there other steps I should take, things I should do to troubleshoot, or what should I do to provide more information for you to help me?
'Blu said:
Ask me for information if you need it.
I've flashed ROMs so many times on this phone I got far passed used to it, and this is one of the only times I've actually managed to softbrick it. I was trying to re-flash x3reme sense after finding out CM10 has a failure of GAPPs and neither of the downloads I have of it works, kind of weird. Anyways, after flashing the ROM, then the kernel, it seemed to be softbricked. This is what I did:
1. Downloaded ROM.zip and extracted boot.img.
2. Moved ROM.zip onto SD Card
3. Wiped cache, dalvik cache, system, and did a factory reset.
4. Flashed ROM.zip
5. Flashed boot.img
6. Rebooted
Now, I am stuck on the HTC screen and I have no clue what I did wrong. I've done this every time I've installed a ROM and it never failed me, besides now. I also tried using Jmz's kernel, and I'm about to try the SuperSick kernel and probably a few others until I unbrick it. Are there other steps I should take, things I should do to troubleshoot, or what should I do to provide more information for you to help me?
Click to expand...
Click to collapse
You have to wipe the cache and dalvik AFTER you flash the kernel through the bootloader, especially when you're swapping ROMs and kernels like that. After step 5, you should have gone into recovery and wiped the cache and dalvik, then you should have rebooted into system.
Correct order-
1 2 5 3 4 6
Are u using correct kernel compatible with ur phone and rom?
R u gsm and flashing cdma packages or vice versa?
R u using-fastboot boot boot.img instead of fastboot flash boot boot.img?
Sent from my HTC One V using xda app-developers app
I'm CDMA and that's weird, the way I've done it has always worked after literally 13 flashes. But I solved my brick with a recovery that didn't appear until now.
Sent from my HTC One V using xda premium
DUDE! DO NOT FLASH THE KERNEL FROM INSIDE THE ZIP! flash a separate kernel. Flash the kernel from inside the zip IF the developer says so. If not, DO NOT TOUCH THE KERNEL INSIDE THE ZIP - it is an insecure kernel and you MIGHT break your phone!
How it all happened:
Regular day for the nexus, had just flashed 4.3 PA, twrp recovery on, stock PA kernel.
put xlouder and franco kernel on
boot to recovery
flash franco
flash xlouder
wipe cache/dalvik
reboot.
its stuck at the google logo and the unlocked locker locky thing there
things i've tried to fix it:
reflash kernel
reflash rom
reflash rom and gapps and all that
wipe, factory reset, flash, all of those, all the combinations i could think of, it still wouldn't boot.
as i saw the situation i thought only 2 things are to be done, try some other rom and if not odin flash.
i tried adb sideload, i couldn't get through with it
i tried to flash 4.2.2 rom found in a thread for unbricking gnexuses, i did it without any issues whatsoever
but it STILL wouldn't boot.
so i figured my partitions should be messed up, tried flashing with pit and still no success to boot.
now, seeing how i tried pretty much everything in the book, what other options do i have besides selling it somehow, or using it as a coaster?
Etnoscope said:
How it all happened:
Regular day for the nexus, had just flashed 4.3 PA, twrp recovery on, stock PA kernel.
put xlouder and franco kernel on
boot to recovery
flash franco
flash xlouder
wipe cache/dalvik
reboot.
its stuck at the google logo and the unlocked locker locky thing there
things i've tried to fix it:
reflash kernel
reflash rom
reflash rom and gapps and all that
wipe, factory reset, flash, all of those, all the combinations i could think of, it still wouldn't boot.
as i saw the situation i thought only 2 things are to be done, try some other rom and if not odin flash.
i tried adb sideload, i couldn't get through with it
i tried to flash 4.2.2 rom found in a thread for unbricking gnexuses, i did it without any issues whatsoever
but it STILL wouldn't boot.
so i figured my partitions should be messed up, tried flashing with pit and still no success to boot.
now, seeing how i tried pretty much everything in the book, what other options do i have besides selling it somehow, or using it as a coaster?
Click to expand...
Click to collapse
Factory image via fastboot. If that doesn't help omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
i'm trying to do that now but the drivers are all messed up
ill update after i fix that