My phone was working for more than 2 years without any problems, I used the MIUI ROM 2.3.30.
Yesterday i went to holiday and when I switched off the air plane mode to login to the foreign network, my phone just freezed.
So I had to remove the battery and simply powered on again, since this moment, I got stuck into a reboot loop after the miui boot animation .
I already tried super wipe (-=SuperWipeG2=-) but still got stuck into this reboot loop.
What for steps you recommend me to try to fix this problem?
vision pvt ship s-off
hboot 0 85 0005
microp 0425
radio 26.03.02.26_M
eMMc-boot
oct 11 2010
hboot 0x446ACD38
boot 0xBB264807
recovery 0x26A3CD9C
system 0xFADFA717
Thank you very much!
Try to reflash the ROM, and since you already used superwipe, you won't lose any data.
Sent from my HTC One X using (*´>д
EDIT: erasing boot partition...
formatting and erasing system partition...
This means you've deleted boot.img and also the whole system. Your device will never boot if you don't flash or restore a nandroid backup.
VaderSKN said:
Try to reflash the ROM, and since you already used superwipe, you won't lose any data.
Sent from my HTC One X using (*´>д
EDIT: erasing boot partition...
formatting and erasing system partition...
This means you've deleted boot.img and also the whole system. Your device will never boot if you don't flash or restore a nandroid backup.
Click to expand...
Click to collapse
Thank you very much, I found an old nandroid backup, phone is working again!
Related
Hi everyone,
I need some help. I recently rooted by HTC Desire and loaded Froyo. Everything has been working perfectly. That is until I tried to run a system update.
Firstly, I got the error "cannot verify file-signature", so I renamed the update to SDCARD: update.zip and ran this from the recovery screen.
The update seemed to run fine, until I was asked to reboot the phone... now it's stuck it a constant boot cycle only getting as far as the splash screen.
Can anyone help me ?
If you rooted your phone than don't do system updated scan.
Did you make a nandroid backup after you rooted your phone?
Have you tried rebooting in recovery mode and wipe cache and wipe data/factory and then flash your phone with the rom again?
Could also try just wipeing cache.
If that dosen't work you might have to format the sd card but i wouldn't jump to doing that and if you do that you should mount your sd card via recovery mode and take the data ther you don't want to lose, like your nandroid backup and other stuff.
If not i would try that before you do it you should nandroid backup your phone!
Wiping all user data won't make a difference. A factory reset will remove all data form the data partition but sysyem stays the same, and that is where the problem is.
If you get the signature verification failed it can mean two things. Either the file was not singed or it was singed but got corrupted/changed. What where you trying to flash?
If you can still boot in to recovery, reflash a rom (with a full wipe) you still have on the sd or mount you sd as mass storage and copy a new rom to the sd.
Just in case, to do a factory reset, choose the "CLEAR STORAGE" option which can be found under the HBOOT menu.. That's what I did when my phone kept getting stuck in a bootloop once, I also did a full wipe + dalvik cache wipe, and then flashed the ROM and it worked.
I cannot do a factory reset. I tried it... same issue. The boots to the flash screen, then gets stuck in a loop. Screen off, vibrate/flash screen on, screen off, vibrate/splash screen on, etc, etc.
Looks like I'll need to do something a little more drastic. Re-flash perhaps ?
Yes, you can try without wiping if you want to keep your data but best thing is a full wipe and reflash.
Am haveing the same problem thinking i unrooted my desire and istalled froyo rom did up date.
My problem seems to be little more then just reboot loop i get red triangle at recovery Fake flash didnt help.
Any ideas?
Oh please, give a solution! on this problem!
I've done the same update and got into a boot loop.
The problem is, I can't get into the recovery menu to flash my backup.
And also tried to reflash the recovery, but Unrevoked won't recognize the phone.
WHAT SHOULD I DO??????
So you updated a rooted phone with an OTA update?
could you post more details.
eg. the rom you are using, the original rom that was on the phone, branded etc....
mikep99 said:
So you updated a rooted phone with an OTA update?
could you post more details.
eg. the rom you are using, the original rom that was on the phone, branded etc....
Click to expand...
Click to collapse
OK. It's a NOT branded Desire with original Android 2.2 (ROM version 2.10405...), HBOOT 0.93, etc. And yes, I have done system update after Unrevoked rooting (I know it's a mistake)
Any ideas?
download this..
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
boot your phone into fastboot - power and BACK button.
connect to pc.
your phone should display FASTBOOT USB.
run the exe you downloaded as administrator and with any antivirus turned off.
wait...
done...
this will put your phone back to stock and will wipe everything but not your sdcard.
let us know how you get on
mikep99 said:
download this..
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
boot your phone into fastboot - power and BACK button.
connect to pc.
your phone should display FASTBOOT USB.
run the exe you downloaded as administrator and with any antivirus turned off.
wait...
done...
this will put your phone back to stock and will wipe everything but not your sdcard.
let us know how you get on
Click to expand...
Click to collapse
Thanks, I've already got that answer. Now trying to download the RUU with my poor connection.....
by the way, do I need a sim in the phone during this process?
I don't think it matters.
Sent from my HTC Desire using Tapatalk
Just finished flashing the stock rom. It's really the only way to bring the phone alive
Hi,
After accidentally installing D2W over A2SD, I tried to revert to my nandroid. Wouldn't boot. Tried advance restoring over a clean A2SD flash, and it seems
it's the data file that's causing it to get stuck on the HTC screen - I restored just that and it failed to boot.
I'm guessing CWM didn't backup properly (although the MD5 seems to check out fine). Does that mean I've basically lost all my data? Is there a way to salvage anything? Can I extract any data manually?
Wiped everything (except FAT32-partition of SD card) before restoring backup? How long did you wait for booting?
Yup, full wipe. Waiting about 7 mins on the HTC screen after nandroid. Usually takes 1 min to get to the boot screen. Full wiped again, install clean ROM (MIUI), booted fine. I didn't know that CWM could make faulty backups
Just use the best recovery one can currently get:
4EXT Recovery Touch (see my sig).
Sent from my HTC Desire using XDA
Thanks, I'll do that now. Haven't upgraded my recovery since the first unrevoked came out..
Though so far the 4ext app keeps failing to flash the recovery.. even after rebooting / reinstalling busybox
Are you S-OFF?
my phone was running amazing
then i turned off my phone so that i could turn it back on it wouldnt got past the google boot screen
now every rom i flashed and kernal and radio combo
has rebooted it self at boot animation to repeat
Any Sugestions?
Wipe data
wiped data and cache and dalvik while doing this
jett1217 said:
my phone was running amazing
then i turned off my phone so that i could turn it back on it wouldnt got past the google boot screen
now every rom i flashed and kernal and radio combo
has rebooted it self at boot animation to repeat
Any Sugestions?
Click to expand...
Click to collapse
restores with stock 4.0.4 .....
even tried restoring another rom but it goes all fine till /data then in the middle of restoring /data it has error on all my restores and fails
when i did the google factory image restore it wiped everything now how do u put files on sd card without going into usb debugging
Are these verified working restores?
If not... .img's over 2gigs cannot be restored.
This is an AOSP issue...
(TWRP allows you to enable compression...thus shrinking you're backups to smaller than 2gigs...but that's of no use to you currently).
A few users have also reported bootlooping after flashing something else...or nandroid restoring even without errors.
I had no such problems.
Flash stock images, if all else fails.
Jubakuba said:
Are these verified working restores?
If not... .img's over 2gigs cannot be restored.
This is an AOSP issue...
(TWRP allows you to enable compression...thus shrinking you're backups to smaller than 2gigs...but that's of no use to you currently).
A few users have also reported bootlooping after flashing something else...or nandroid restoring even without errors.
I had no such problems.
Flash stock images, if all else fails.
Click to expand...
Click to collapse
i have flashed 4.0.4 stock image
holy **** right as i was typing this my phone booted properly
jett1217 said:
i have flashed 4.0.4 stock image
holy **** right as i was typing this my phone booted properly
Click to expand...
Click to collapse
Same thing happened to me on v2 and I was using TWRP. Backed up /data/media rebooted into boot loader and ran fastboot -w and it booted right up. Using cwm to be safe now
EDIT: MAKE SURE YOU BACKUP /DATA/MEDIA BEFORE DOING FASTBOOT -W OR ALL YOUR SDCARD DATA WILL BE GONE!!!
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.
Hello!
After some fiddling around I have finally succeeded into installing the MIUI custom rom. (had a heck of a work around to perform because I forgot to put the custom ROM on my SD card first.)
Right now, I've got Clockwork Recovery 5.8.4.0 installed with the latest miui. Fastboot is also installed and working, and my phone is unlocked. The correct boot.img has also been installed.
It even boots. BUT. After it has showed the MIUI logo and goes to my home screen, it starts loading for like 4-5 seconds where everything still works, and it then stops. Crash. The screen freezes and my phone reboots. It seemed like a SIM card problem to me, but even removing the SIM card and booting my phone wont solve this issue. Does anyone have any clue what I can do?
Summary of installed software:
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
Latest MIUI for One X (downloaded this afternoon)
Latest ADB Development Kit. (Not used though)
Latest Flashboot.
Factory Reset performed (Whole phone is empty except for above mentioned programs.
Thanks in Advance!
P
Erase Cache
While in Fastboot Mode .Perform This command
Fastboot erase cache
Should do the job for u!
I would suggest flash the boot.img again and then erase cache again.Will work
Tried it, but..
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
^^ for ARHD 16 u need hboot 1.33 , 1.36 depending on your CID
for miui did you do full wipe?
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Did you wipe cache and dalvik cache? I think ARHD does that anyway, but might be worth doing the superwipe.
Oh, and if you're restoring system data or system apps with Titanium backup, stop it.
HBOOT!
I am afraid ur not on the right CID version for installing JB roms.
Please update ur Hboot
@ali3nfr3ak: Yes, I did a full wipe before MIUI. After every flash I do a Dalvik Cache Wipe, Factory Reset Wipe and Cache Wipe. Even the fastboot receive a cache wipe after every flash.
How do I update my HBOOT? The rest seemed pretty straight forward, but there are tons of versions out there, and I do not know which one I should be taking. And what is CID? I've also been having troubles porting a Super Wipe toward my mobile phone. Can a Super Wipe be performed within fastboot/recovery?
Haha and no, I'm not using Titanium Backup
Right, I've succesfully restored my phone to it's old state. Flashing MIUI again provided the same error. Could it be that my hBoot is out of date here? My One X still has the 4.0.4 android version, whilst MIUI is based on 4.1, right?
Change the rom, miui isn't good.