Hi I'd apprecite assistance here.
It happened to me already before.
I did simple ROM backup of Andromadus B4 using ROM manager and from that time, device does loop reboot. It reboot itself until PIN is requested and than it loops reboot.
I had this twice before and what helped was to install again stock ROM with Goldcard, but this time i dont want to do it as i would loose root and have to go thru process again. Once they even changed my board in HTC service but it started to do same thing again after wihile.
What more i can try before start recovery with stock ROM.
advises appreciated.
Thansk.
Wipe everything, super wipe, fastboot -w
Then flash a new rom, something not beta and stable
If bthis doesn't work there may be something wrong with your emmc partitions, going stock may fix...
Sent from my HTC Vision using xda premium
And make sure you have the correct HBoot for certain ROMs.
- Sent from my POS G2
Thanks, i did superwipe with http://forum.xda-developers.com/showthread.php?t=1044992 flashed again Andro B4 and voala it works again, no loop reboots anymore.
So marking this as solved
Related
After installing Cyanogenmod 9 on the One X I started to notice extremely poor signal, Mobile and Wi-Fi. Also the phone would crash and randomly reboot when doing simple tasks such as opening messages etc.
Upon trying to get into recovery to install a different rom, the phone now flashes on a black screen and restarts the phone.
To try and solve this issue, I unrooted the phone and restored to stock recovery.
I then re-rooted the phone and installed clockworkmod recovery again.
I can now access clockworkmod recovery although it seems to have no effect. Installations of any rom fail and cyanogenmod always pops straight back up again after rebooting.
Has anyone else had this issue?
Does anyone have a way to fix this? Possibly to force the phone completely back to stock?
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Kamiil29 said:
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Click to expand...
Click to collapse
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
AndyB said:
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
Click to expand...
Click to collapse
Unfortunately I can't help you with SuperWipe, but you can find the HOX stock ROMs here.
Sent from my HTC One X using Tapatalk 2
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
AndyB said:
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
Click to expand...
Click to collapse
Did you try holding down the Power and Volume Down buttons while in the bootloop to enter the bootloader? Hold them down until the lights start to flash, the screen goes off and then the bootloader comes up.
If you can get into recovery with that, factory reset, clear cache and dalvik cache (under advanced) then try install the ROM.
I'm not the best person to be helping, but I hope that works for you!
I had a similar problem once where the phone would just sit on the HTC One X screen, and trying to go into recovery just put the phone back to the HTC screen. I fixed it by flashing the boot.img, factory reseting, clearing out caches and installing the ROM again. No problems since.
I'm afraid if this doesn't work, I may have to abandon you and let someone else take over, as I'm no expert, but I'll see what I can do to help.
Edit: sorry, it is 2AM here and I need some rest for an early start at 6AM. I will check up on this thread when I wake.
Sent from my HTC One X using Tapatalk 2
FIXED!!!
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
AndyB said:
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
Click to expand...
Click to collapse
Glad you got if working
Sent from my HTC One X using Tapatalk 2
I was a newbie, and i didn't take a backup from my stock rom, and i couldn't find it at all as it was "1.29.709.12" so with help of a friend of mine we managed to install ARHD 7.1.0 instead.
and after a while i decided to install CyanogenMod9 Beta1, so i toke a CWM 5.8.4.0 recovery backup and installed it and everything was fine, then i came across an unleashed cm9 v18 which has more fixes and i installed it, but the BT was not working at all, so i managed to get back to the backed up CM9 but the same problem occurred and the BT is not working at all, it doesn't even wanna change the on/off button.
so i tried to revert to the ARHD 7.1.0 and i restored it but it loops in quietly brilliant screen, i used aa super wipe patch and i installed it again and the same behavior happening, looping and looping
now the only rom that opened up is the "IceCold build 7"
please guys advice me what shall i do, every time i clear cash, I install the proper boot.img, wipe data/factory reset, and wipe cash partition. then whats wrong with my steps? why it doesn't work?
I advise you to stop fuking about and learn before you play.... its kind of like school but its more expensive.
crsnwby said:
I advise you to stop fuking about and learn before you play.... its kind of like school but its more expensive.
Click to expand...
Click to collapse
thanks for your advise, i promise i won't play again, but what about the this situation am in? any recommendations, tweaks, that can solve my problem will be really appreciated.
i need to get back to my stock or at least to be able to install a sense custom rom like the ARHD.
please guys help, please just give me any solution for this.
Relock flash ruu for phone and start again from begining this should sort your issue out
Sent from my HTC One X using xda app-developers app
dryan433 said:
Relock flash ruu for phone and start again from begining this should sort your issue out
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
the problem is that my RUU is "1.29.709.12" which is not exists at all, it looks like my phone is the only one world wide that has this RUU
is there anyway to flash another RUU without having "ERORR: 155"?
The RUU doesn't do anything special, it just wraps it up into a nice easy to use package. There must be quite a few threads and hundreds of posts explaining how to fix this.
Off the top of my head, quite possibly wrong.
Unlock.
Flash recovery
Flash boot.img
Fastboot erase cache
Superwipe
Flash Rom
Flash modules.
Relock
Search and you'll find.
im puzzled, why didnt u full wipe every restore?
After flashing boot image, did you do fast boot erase cache
Sent from my HTC One X using Tapatalk 2
Hi, I'm having some trouble getting a rom on my phone. It is the CDMA version that I unlocked and rooted and switched over to Page Plus. Everything worked great. I wanted to try the new ROMS, but every time I get them installed, the phone works for 5-15 seconds after booting (asks for wifi, google accounts, etc). It freezes for a moment, works for another second, and then reboots. This continues indefinitely.
I am absolutely sure that I have followed all the steps for the roms I am using. For example, here is what I do for the pacman rom:
Download the zip, extract the boot.img
Boot the phone into fastboot, run fastboot flash boot boot.img with the extracted img.
Load up the recovery, system reset, wipe cache, wipe dalvik, wipe system
Install the pacman v15.3
Boot again into fastboot and replash the boot.img just for good measure.
Reboot the phone, and then it hits the reboot loop.
I've tried to use another kernel (jmzone v4) as well as android open Kang and SuPrimo, but I get the same thing with each of them.
I also tried to restore my backup, but now it doesn't boot. I don't have the original boot.img, so can anyone tell me where to get that?
So, any help?
Thanks!
If you had investigated before posting, you would have seen that this is a common problem with an easy fix. Your radio version is too high, which means you took the update on stock rom.
Relock and ruu. There is a guide in the general section about bootlooping/rebooting upon boot.
We are all happy to help, but please investigate and do your homework first before just creating threads next time. It helps us and it helps you grow your knowledge of android.
Sent from my One V using xda app-developers app
Fix
I agree that you should have done your homework. I've had this problem too [link to my thread], and I'll save you some time by giving you the threads.
You're going to need to flash the RUU to get it back to stock.
You'll find links to your RUU on this thread (I used the "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe" for my Virgin Mobile CDMA phone).
Then follow this tutorial for exact steps on how to flash the RUU. It's the best that I've found.
Then try following the steps to flashing your ROMs. I've tried flashing AOKP and Paranoid with stock kernels and others (jmz's and SuperSick), but the only one that really has worked was recommended to me by another user. Try the CM10 ROM with the latest version of the SuperSick kernel (the latest I found was 12_21_12-16-04, which worked, but you'll have to look around for it). It's pretty awesome. Don't for get to click thanks to those posts that have helped you.
Lol you are a nicer person than I.
Sent from my One V using xda app-developers app
Haha I try to help the noobs, myself being kinda one :]
Sent from my One V using xda-dev app
Hi,
I have problem with my HTC Desire Z (Vision). I have S-OFF by this tutorial - Cyanogenmod Install CM for vision and when I install any rom I have bootloop, after configuring my device...
I tried all tricks but the problem is still on my htc...
Can anybody help me?
which roms specifically have you tried?
write down everything on boot loader screen (yes everything)
can you get a logcat of boot loop?
does it boot to os then at reboot you get a boot loop?
if so what specifically did you do before reboot?
give as much information as possible and help will be better
This has happened to me, what i did was re flash cwm touch through Odin. I was using cwm 6.0.2.9 touch when it started to boot loop.
Sent from my SCH-I535 using xda premium
ace000724 said:
This has happened to me, what i did was re flash cwm touch through Odin. I was using cwm 6.0.2.9 touch when it started to boot loop.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
which isnt an option for anyone using an htc phone....
demkantor said:
which isnt an option for anyone using an htc phone....
Click to expand...
Click to collapse
Yup... But, I back to my stock rom couse I need phone not zombie and I can't write any informations...
I remember that I have hBoot - 0.84.2000 and nothing more... ;/
EDIT:
A yo..
I have backed to custom rom, and it's similar problem.
My info:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010, 15:56:38
and ClockworkMod Recovery 5.0.2.7
Odp: Bootloop on Custom Rom
Anybody can help me?
Sent from my Nexus 7 using xda app-developers app
Try a full wipe, fastboot -w, superwipe script, whatever, just make sure phone is fully wiped. Then download a known working rom like cm7, flash that and then the gapps from recovery, reboot and let it sit a few minuets. What happens then
Sent from my MyTouch 4G Slide using xda premium
I used SuperWipe script, and I have the same problem...
I have installed MIUI and this rom have too problems... ;/
Any ideas? I don't want use old stock rom... ;/
it sounds like your doing everything right, can you pull a logcat to look at? for now read over these
HOW TO FLASH YOUR FIRST ROM
and
BOOTLOOP OR BRICK?
demkantor said:
it sounds like your doing everything right, can you pull a logcat to look at? for now read over these
HOW TO FLASH YOUR FIRST ROM
and
BOOTLOOP OR BRICK?
Click to expand...
Click to collapse
LOL, I can't do anything on Andromadus with ADB...
I try ext4 and I post here if problems with custom rom ends..
EDIT:
I have ext4 and I have the same problem...
This is link to my logcat from stock android with 1.34 version: Logcat
If this help - I have phone with chip from Sandisk
Well, I think that nobody can help me? I think that I need back to old, lag stock rom...
EDIT:
I got it!
Well I do this steps:
I have rooted my device with this tutorial: Install CM for vision and I have install 4ext Recovery on stock Android 1.34.
Next step is format all your partition to ext4 and install custom rom.
Now is very important step - BACKUP your custom rom to your SDCARD. Again install stock rom (1.34) and root system.
Again format all partitions on phone to ext4 with 4ext Recovery. RESTORE your Custom Rom and s'il vous plaît très - ENJOY YOUR CUSTOM ROM!
That's steps help me to install Custom Rom without any bootlooping. But now I have problem with SDCARD, but I think this problem is becouse Andromadus is testing version.
wow be patient a little, be happy people are wiling to help when they have time
first off the logcat was for a rom that booted, that is hard to help figure out why something didnt boot. having the sandisk emmc is good but you werent showing signs of a fried emmc so no biggie either way
first of lets just do this step by step quick ok
flash THIS or THIS in recovery, then reboot recovery
now flash THIS ROM
when finished flash THESE GAPPS
now reboot
wait even ten minuets to load
if not get me a logcat of this NOT booting
edit
i see you got things settled, good
but just so you know there is no need to back up and restore your stock rom before flashing a custom one
i figure the reason why it worked for you this time was the formatting of partitions to ext4 (needed for jb roms)
or just the fact that your formatted completely wiped your partitions something i dont think was happening before
either way im glad you go it handled, but from now on just do complete wipes between flashed and youll be fine
Odp: Bootloop on Custom Rom
Hey, thank u for your help With my problem!
Sent from my Nexus 7 using xda app-developers app
Could anyone please help me to fix my desire. I tried too restore a cwm backup using twrp recovery. The first problem of not being able to mount sdcard was cured by a post on XDA. I then tried to reinstall my favorite ROM paranoid android. It got as far as Android is upgrading and then did nothing also there was no boot screen animation. I thought that my Boot might have got corrupted so I flashed stock Hboot. Reinstalled ROM but this time it didn't do anything. I tried reformatting cache sdcard system and data to no avail. Can anyone help please!
Thanking you in advance.
Sent from my GT-N7100 using xda premium
Reminds me on my problem from last week.
It was an confusing hard work, but after flashing new hboot and recovery(!) it worked again. I used the Alpharev18 Boot-CD for S-Off, new hboot and recovery. The problem was still there. But then i was able to install under the MildWild Rom (only rom that worked) the 4ext recovery. Thats done it for me, all is working again
I wish you the best for the repair!
Ah btw, did you tried in Fastbootmode, with the fastboot (commandlinetool) from the Android SDK following command?:
fastboot oem enableqxdm 0