Hey guys,
I have a One V that I successfully bootloader unlocked and rooted. I went to intall a custom ROM, both AOKP JB and then CM9 and they keep boot looping. I looked and my radio is 1.00.00.028. I had an old One V with Radio version 1.00.00.0521 and that worked fine with custom ROMs, so I am sure it is the Radio version.
I did make a back up and tried to restore but it keeps looping still becuase I think it is the wrong boot.img that I flashed in fastboot. I don't have a back up of that and I don't know how to extract that boot.img from the TWRP back up. It is a .win file.
Please help. Do you have any advice or links to point me to get this boot again.
Thank you
http://forum.xda-developers.com/showthread.php?t=1706070
Hit thanks if I helped u!!!
Related
I flashed a new kernel, I was running kkernel v14cw
and I flashed buzz_cm_1.1.4_OCUV
and now it is stuck in a boot loop.
please help me D:
I got the same problem? You found a fix yet pal???
Cheers
Try this tool for flashing your kernels instead of doing it by recovery guys. The problem its not uncommon.
http://forum.xda-developers.com/showthread.php?t=852357
Sent from my performance enhanced Desire HD.
P1xelVandal said:
I flashed a new kernel, I was running kkernel v14cw
and I flashed buzz_cm_1.1.4_OCUV
and now it is stuck in a boot loop.
please help me D:
Click to expand...
Click to collapse
Boot into recovery and flash your ROM again , this will restore the original kernel and keep your data intact
ghostofcain said:
Boot into recovery and flash your ROM again , this will restore the original kernel and keep your data intact
Click to expand...
Click to collapse
You only need to restore the kernel (boot partition, i think).
Maybe someone should make the stock kernels availible to flash? i had to reflash my roms yesterday, because i tried a kernel i didnt like, and could find the stock one to return back
Hi guys. trying to restore back to my backup stock rom. then want to update via OTA. So i restored back but i am stuck on HTC quietely brilliant screen.
I can get into HBOOT. any ideas on please what i need to do to get this working again please?
Thanks
You can get to Recovery from HBOOT surely? Just scroll down one.
You need to flash stock boot.img as nandroid restore will not restore the stock boot.img. You're still on the last boot.img that you flashed, that is why it is stuck on splash/bootloop
ckpv5 said:
You need to flash stock boot.img as nandroid restore will not restore the stock boot.img. You're still on the last boot.img that you flashed, that is why it is stuck on splash/bootloop
Click to expand...
Click to collapse
thanks. just managed to get the boot.img from a thread on Development section and just flashed it through fastboot. many thanks to you both. kinda had me there for a minute. still alot to learn on this side of the forums..many thanks
I rooted my phone and tried coredroid but decided that i preferred the stock rom and everything in it so decided to flash back. I had made a nandroid backup, so flashed it, and restored the recovery and relocked the device, however. now when trying to select music to play or to try and change the ringtone, the phone will crash and reboot. this happens every time, am downloading the RUU now to see if that will fix it, but does anyone have any ideas, any help would be much appreciated
i experienced that before and it was late when i realized it was because of the boot.img that you flashed from the custom rom, since you restored back to stock rom your boot.img file your using is still the custom rom that you used, try to post from the thread of coredroid and ask for the boot.img to be flashed for you to use your stock rom and remove the restart issues
Just extract the boot.img from your nandroid backup and flash it via fastboot (you'll need to unlock your bootloader again if you've already relocked it)
THANKS!!!
OMG thanks it worked, i dunno why the CWM didnt flash the boot.img as well, anyway it works now, thanks both of you for the help
Aidsy said:
OMG thanks it worked, i dunno why the CWM didnt flash the boot.img as well, anyway it works now, thanks both of you for the help
Click to expand...
Click to collapse
CWM can't write to the boot partition without S-OFF, which is why you have to manually flash a boot.img through fastboot when you install a new ROM. But it also means you have to do the same thing when restoring a backup.
ok...so I just got the htc one x from att tonight...i followed the guide and unlocked the bootloader, then flashed twrp v2.3.1.0 and proceeded to try and flash viperx 2.6. first thing i did is use fastboot to flash the boot.img, then i went into recovery and flashed the rom. the process of flashing the rom was extremely fast which seemed a little suspicious..when it went to reboot afterwards i keep getting the htc screen with the red letters that you get when it is loading into recovery. it freezes at that point. i tried to flash a different rom at this point: Magnolia x, i did it the same way...flashed the boot.img via fastboot then flashed the rom in recovery, this time i get an error saying "Error in /sdcard/magnolia_x_1_0.zip (status 1)
Error flashing zip...
updating partition details...
failed
like a jackass i didn't make a backup of the stock in twrp. if anyone has any suggestions i'd be extremely grateful. oh...and when i try to flash a new recovery via fastboot it freezes when loading the recovery and i have to reflash twrp. so twrp is the only recovery that i can have flashed on the phone. i know i'm a dumbass. any help would be appreciated. i'll even welcome some flaming if it leads to me getting a working phone. : )
Phone from AT&T ? dual-core phone ?
Do not flash anything from here, you are in the international quad-core phone forum.
Please go to the AT&T , ROGERS forum !
I'm hoping for you that you did not bricked the phone doing all this !!!!
thank you very very much. solved everything. i didn't even realize there was a specific thread for international vs att/bell. solved everything.
Good to hear ! Have fun with it :thumbup:
Hi XDA-developers,
Recently, I tried some new ROMs. I started by going from stock to ARHD and then switched over to Cyanogenmod. I now want to revert back to Cyanogenmod, but I've had no luck getting my phone to work. Here's what I have:
My HTC One X runs ClockWorkMod as recovery, I have three nandroid-backups: Stock, ARHD and Cyanogenmod.
I first erased my phone in CWM. I then restored the ARHD nandroid-backup and that completed succesfully. But when I tried to boot up the phone, it got stuck at the boot-screen where the phone says 'One' in big letters. I tried to wipe it again and load the stock ROM but that also got me stuck on the boot-screen. Finally, I tried reflashing the Cyanogenmod nandroid-backup but that gave me a MD5 Mismatch error...
I tried fixing the MD5 error by following this guide: http://forum.xda-developers.com/showthread.php?t=1835914 but got the 'File '*img' not found' error.
Results from fastboot get-var version-main: 3.20.401.1
If you need any additional info, I will try to provide it. Thanks for reading my question. :good:
~Willem
Willemnz said:
Hi XDA-developers,
Recently, I tried some new ROMs. I started by going from stock to ARHD and then switched over to Cyanogenmod. I now want to revert back to Cyanogenmod, but I've had no luck getting my phone to work. Here's what I have:
My HTC One X runs ClockWorkMod as recovery, I have three nandroid-backups: Stock, ARHD and Cyanogenmod.
I first erased my phone in CWM. I then restored the ARHD nandroid-backup and that completed succesfully. But when I tried to boot up the phone, it got stuck at the boot-screen where the phone says 'One' in big letters. I tried to wipe it again and load the stock ROM but that also got me stuck on the boot-screen. Finally, I tried reflashing the Cyanogenmod nandroid-backup but that gave me a MD5 Mismatch error...
I tried fixing the MD5 error by following this guide: http://forum.xda-developers.com/showthread.php?t=1835914 but got the 'File '*img' not found' error.
Results from fastboot get-var version-main: 3.20.401.1
If you need any additional info, I will try to provide it. Thanks for reading my question. :good:
~Willem
Click to expand...
Click to collapse
Did you flash matching boot.img (kernel) after each nandroid backup flash?
hpnxfox said:
Did you flash matching boot.img (kernel) after each nandroid backup flash?
Click to expand...
Click to collapse
No, because I thought the boot.img was flashed with the Nandroid-backup (according to the log that is displayed in CWM).
But I just downloaded a stock Nandroid-backup so I'll extract the boot.img from that and flash it and see if that works!
Willemnz said:
No, because I thought the boot.img was flashed with the Nandroid-backup (according to the log that is displayed in CWM).
But I just downloaded a stock Nandroid-backup so I'll extract the boot.img from that and flash it and see if that works!
Click to expand...
Click to collapse
yes cwm does that but not with one x because of S-ON thing!
hpnxfox said:
yes cwm does that but not with one x because of S-ON thing!
Click to expand...
Click to collapse
Oh, that's why. I have read about S-ON but I don't know anything about it as the One X apparently does not support it. I'll flash corresponding boot.imgs in the future!
My phone works now, I flashed a boot.img from a stock nandroid-backup. Thanks for the fast replies!
Willemnz said:
Oh, that's why. I have read about S-ON but I don't know anything about it as the One X apparently does not support it. I'll flash corresponding boot.imgs in the future!
My phone works now, I flashed a boot.img from a stock nandroid-backup. Thanks for the fast replies!
Click to expand...
Click to collapse
Good to hear! and yes, every rom (or nandroid backup) exchange require also their boot.img flashing!