Related
I'm on an HTC Evo 4G rooted running CyanogenMod7 with Tiamat kernel and Clockwork mod. I went to sleep last night and everything was working fine, when I woke up this morning, I rolled over and my phone was stuck in a boot loop. I flashed back to my only backup (UltimateDroid) and it did the same thing. I flashed the stock rom and still no luck. Will a hard reset fix this? but more importantly, what is a possible cause? so I can avoid this happening again.
I don't know what caused the initial bootloop, but before you flash a new rom or restore from a backup, you need to wipe data, cache and dalvik. If you have problems (which is fairly common with ClockworkMod on the Evo) try wiping multiple times. You can also try using something like superwipe or a format all zip.
If the problem persists, Amon Ra is a great alternative to ClockworkMod. Many users have problems with CWM, but switching to Amon Ra usually helps.
(from... Evo/MIUI/Tapatalk)
I wiped everything several times.
I already did the hard reset and it still boot loops. it gets through the stock boot screen ( Sprint, Now Network, 4g, etc) And shows the lock screen, but before I do anything, it reboots again.
When I try to reboot into recovery it shows thoe phone with a red triangle/exclamation point icon
mrbliven said:
I wiped everything several times.
I already did the hard reset and it still boot loops. it gets through the stock boot screen ( Sprint, Now Network, 4g, etc) And shows the lock screen, but before I do anything, it reboots again.
When I try to reboot into recovery it shows thoe phone with a red triangle/exclamation point icon
Click to expand...
Click to collapse
When you boot into the bootloader, are you s-off or s-on? The red triangle means you don't have a recovery. If you're s-on, you're not rooted. When you say you flashed the stock rom, did you flash the stock rooted rom or did you use an RUU?
(from... Evo/MIUI/Tapatalk)
it's an RUU. I ran unrevoked's S tool, S is on. Then I ran the RUU as PC36IMG.zip which is the last thing I did and I'm still in a boot loop.
I downloaded the second one on this list.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
mrbliven said:
it's an RUU. I ran unrevoked's S tool, S is on. Then I ran the RUU as PC36IMG.zip which is the last thing I did and I'm still in a boot loop.
I downloaded the second one on this list.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Click to expand...
Click to collapse
The RUU is why you don't have a recovery. Since your s-on & on the stock rom, you're safe to take it in to Sprint. Delete any rooting and unrooting stuff from your SD card (back it up to your computer first if you want to save it) before you take it in. Just tell them that you don't know what happened and play dumb. I had a phone that had never been rooted before do something similar, but since I was knowledgeable about my phone, I watched the guy check the bootloader and try to go into recovery. He probably thought I had rooted it. So don't mention any rooting terminology and you should be fine... they can't prove anything anyway.
You can try another RUU again if you want, but if it still won't boot, you'll probably need to get a new phone.
(from... Evo/MIUI/Tapatalk)
Okay thanks! I'll try that. Will I have to pay the $100 deductible for the insurance, or is that covered?
mrbliven said:
Okay thanks! I'll try that. Will I have to pay the $100 deductible for the insurance, or is that covered?
Click to expand...
Click to collapse
Nope. Free of charge as long as you have insurance. The only time you should have to pay the deductible is if it's lost/stolen, if it has water damage, and possibly other physical damage like a busted screen. I'm not sure of the exact policy as it has changed a couple times, but you'll be covered.
(from... Evo/MIUI/Tapatalk)
Should I delete the RUU? (PC36IMG)
mrbliven said:
Should I delete the RUU? (PC36IMG)
Click to expand...
Click to collapse
Definitely. Any roms, kernels, format all zips, etc. You may just want to take the card out since there may be stuff like Titanium Backup backups, etc. They shouldn't look at your SD card, but if they want you to leave the phone with them to work on or test, they may look. If they ask why you took it out, just tell them there's dirty pictures or other personal info you don't want anyone seeing.
(from... Evo/MIUI/Tapatalk)
Okay, thanks for all the help. Took it back today and they're going to replace it (free of charge). Unfortunately the phone is back-ordered, so I'll have to wait till Wednesday.
mrbliven said:
Okay, thanks for all the help. Took it back today and they're going to replace it (free of charge). Unfortunately the phone is back-ordered, so I'll have to wait till Wednesday.
Click to expand...
Click to collapse
That's great! Last time they got me a new phone it was back-ordered. They told me they had no idea when it would be there (probably 4-5 days) but it was there in two. I'd call on Monday or Tuesday and see if it came in early.
It is strange how your phone pooped out randomly. I'm sure there's a reason, it's just odd.
(from... Evo/MIUI/Tapatalk)
I don't know, I'm still googling my ass off trying to figure it out. I think it may have something to do with the kernel. I'm still going to root my new phone, but be sure to keep a back-up of the original.
I had a lunch TB4g and it just bricked today, I was running ShiftAOSP 1.2 (I believe unrelated) and the .802 radio (possible) but it will just go to the HTC screen and reset and keep trying to boot. I can get into HBOOT and FASTBOOT, I have tried to reflash a root friendly RUU but it didnt fix anything and still cant boot. Just giving you a heads up. I had it overclocked to 1.22, I had it in my car on the way home, sent one text, 23% battery and I plugged it into my CPU USB to charge for a little waiting for some friends to show up and that is when it went into bootloop. Heat was not an issue as I had used it minimally the whole day sending small texts. It did sustain a major G shock 2 days prior but no excessive G or roughness today. Since it can get into HBOOT it might be recoverable but thats to the devs to decide, I have the unlocked 1.04 hboot installed.
i doubt the radio caused it, but that sucks man. see if you can talk verizon into a bionic for a replacement.
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
JBO1018 said:
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
fixxxer2008 said:
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
Click to expand...
Click to collapse
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
JBO1018 said:
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
it will boot to hboot and not reboot, but it will not boot to recovery
Have you tried flashing one of the recoveries that were modified to install through hboot? you can take your sd card out, and using a computer, place the PG05IMG.zip (search here @ XDA) and place it on the root of the card, flash through hboot. then using the computer again, remove the PG05IMG.zip from the sd card and go back into hboot and select recovery. i had to do this not too long ago and it worked for me, maybe it will help you.
I pulled the battery and wont plug it in all night to see if it resets some error it maybe had, my new phone is delivered tomorrow so its not a big deal.
fixxxer2008 said:
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
Click to expand...
Click to collapse
I would agree. The whole reason I asked about recovery boot looping is because if it is thats pretty much identical symptoms everyone who had the boot loop of death "brick" thing had. If that is what the situation is I would get it s-on and get VZW to replace because I doubt he caused it.
Sent from my HTC Thunderbolt
fillyo said:
All you cheap ****ers trying to get something for free, if he bricked, his loss. Period.
Click to expand...
Click to collapse
Ditto. He probably told insurance he lost the phone and paid his $100 bucks.
People are so greedy these days. All for nothing and nothing for all.
Doesn't sound design like there was much effort to fix it either.
Questioned posted and shortly after a new one is on the the way?
Keep an extra phone around for instances like this.
Not everything is an insurance claim.
Sent from my A500 using XDA Premium App
You wonder why all the major companies are starting to hate people who root phones. Some people will flash a Rom everyday just to do it and if they miss up their phone they don't seem to care. Now do I think a thunderbolt is worth 700 bucks retail hell no it only cost about 125 to build. But people need to hit up these forums to try to fix their phones before they call Verizon. I read a few post of guys who buy bricks phone fix them and sell them so any bricked phone can be fixed as far as he said. Read up and don't be so quick to clear data as first sign of a problem. Always try what got me out of the bootloop of death.
1. Battery pull
2. Power and hold down volume button
3. Never and I mean never keep a radio stored on root of SD card after install this will cause Hboot to install radio and that is not what we want to do here.
4. Go to recovery
5. Under download folders in your SD card always keep a updated ROM of what ever ROM you are currently using or at least a stable build inside that folder if you are using AOSP keep a stable ROM that last worked for you so no data clear is needed if you are using Sense do the same.
6. I never flash a recovery at this point follow this it saved my phone. Clear cache, clear delvik, format system under mounts and storage.
7. Format is most important since it will not delete recovery if you need to try again. Go to install zip file, select zip file, and install your fresh ROM or a stable build I never have flashed a normal ROM or have I flashed back to a down graded GB ROM.
8. Reboot after ROM has flashed and your phone will boot correctly.
I hope this has helped it saved me a few times in boot loop of death. Stop clearing data you lose your recovery and stop flashing old GB ROMs thinking they will save you, it might but message me so I can say I told you so.
****NOTE also make sure you are updated to newest CWM there was a problem with bootlooping after flashing a kernel and maybe Rom. I had the problem with flashing a kernel sent me into a bootloop. Update or roll back.******
Sent from my ADR6300 using XDA App
The OP probably gets into recovery for a few seconds then bootloops randomly. If you are not bootlooping in hboot, you are not bricked. Find the stock ruu file and flash that through hboot. Although you will lose root, the phone should work again.
If it's bricked, throw it to the ground and stomp on it til it breaks and claim insurance..... That should piss some people off here
Seriously tho some guy mentioned something about a HBoot friendly RUU. You should look into it
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
JBO1018 said:
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
Sent from my ADR6400L using XDA App
Grnlantern79 said:
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
If he can't think of a way to fix it send it to me will have it running in a couple of google searches.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App
I tried to get into recovery a few times before doing anything, it would just go black and reboot to the HTC logo. As a last attempt I tried to load a rooted a ruu, it installed but didnt not boot. I have the 1.04 modded hboot so I dont think I can overwrite recovery. Either way, contrary to your beliefs I will not claim insurance on it, although this is a warranty issue, these phones are dropping left and right. I just moved to tmobile this week and my sensation 4g and G2x are supposed to be delivered today.
Thanks for your ideas but I tried to reflash recovery and it installed through hboot but it will just reset before it loads. I still have s-off and my emmc was the sem08g. I am going to plug it in and just let it boot loop all day while I am at work, maybe it will get out, maybe it wont, either way is it wont hurt anything.
I recently brought a htc desire s rooted with sense 3.0. Today when i was downloading an app the phone blocked on the start screen and i couldn t do anything. I got the battery out and reiserted it but after de load screen ..nothing..i could see the screen was lit but nothing.After repeteing the process for 5 times it finally worked and the phone started..What could be the problem? Please help me. And also superuser is not working. it says it failed application or something like that every time i use it or some program tries to use it..The same with programs that require root.They just fail.the rest of the programs work perfectly and the Sense ui is smooth. What could be the problem?
hey..may be the root was done badly..steps missed..try reformating ur fone..re-root and install a fresh rom..Htc runnymede sense3.5
works grt!
the good thing is that your phone is not bricked
i would check what eMMC phone has
and of course flash a new rom
reboot to recovery and check for error messages like: "E:Can't mount /cache/recovery/last_log"
mixalakis32 said:
the good thing is that your phone is not bricked
i would check what eMMC phone has
and of course flash a new rom
Click to expand...
Click to collapse
how do i check what emmc chip it has?And what do i need to look for?
Just be careful with pulling the battery... there is a known issue with the Desire S where that menrioned eMMC chip gets messed up when power is disrupted by pulling battery... apparently Power and Vol up Vol down all at the same time pressed do reset the Desire S when a freeze occurs... also.. update apps in market only one by one... and read the threads here in general section a but further down.. Greets
Sent from my HTC Desire S using xda premium
hardstuffmuc said:
Just be careful with pulling the battery... there is a known issue with the Desire S where that menrioned eMMC chip gets messed up when power is disrupted by pulling battery... apparently Power and Vol up Vol down all at the same time pressed do reset the Desire S when a freeze occurs... also.. update apps in market only one by one... and read the threads here in general section a but further down.. Greets
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Thanks for the info...but how do i find out what emmmc chip i have and what is the best rom to flash? Mine says proxuser but i cant overclock or anythnig? Cyanogen for the desire s is good?
use esfile explorer start it up tap left upper corner the star select phone then follow this path /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/ tap name open as text tap the first choice.
Mine is m4g2de which is the crappy one i think not sure
Do an s-off and re-root the phone with this
Don t install su 3.0 ,it s terrible unstable on desire s.
Try to flash a custom rom( that is more powerful than Stock rom)
Sent from my HTC Desire S using XDA Premium App
kamei said:
use esfile explorer start it up tap left upper corner the star select phone then follow this path /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/ tap name open as text tap the first choice.
Mine is m4g2de which is the crappy one i think not sure
Click to expand...
Click to collapse
the same here...so i have a crappy chip/?
cristiedward said:
the same here...so i have a crappy chip/?
Click to expand...
Click to collapse
We all are in the same boat!
I was getting system freeze in the market too... but after proper system formating... and flashing fresh ROM it was OK!
so what is the best rom? i am really afraid now that i might broke it..should i sell it and biu a new one with stock rom? wait for the official 3.0?
cristiedward said:
Thanks for the info...but how do i find out what emmmc chip i have and what is the best rom to flash? Mine says proxuser but i cant overclock or anythnig? Cyanogen for the desire s is good?
Click to expand...
Click to collapse
I used four the last few month the Virtuous Unity ROM which runs perfectly on my Desire S with excellent battery use...ATM however I am on MIUI ROM which I also really like as it is so cool with theming...just try them all out...at the end your own preference rules! ;-)
Sent from my HTC Flyer P510e using xda premium
i have entered recovery and it says saga pvt s off rl , hboot 6.98.1002 , radio is 3805 06 02 03 , emmc boot and i have clockwork recovery 5.0.2.0..is it all good? can i roor uin rom manager? thanks very much
cristiedward said:
i have entered recovery and it says saga pvt s off rl , hboot 6.98.1002 , radio is 3805 06 02 03 , emmc boot and i have clockwork recovery 5.0.2.0..is it all good? can i roor uin rom manager? thanks very much
Click to expand...
Click to collapse
Just copy the ROM in my signature to your sd card and boot into recovery, and use install from sd card option to flash it.
If you want a sense 3.0 ROM, this is the best out there. For Non-sense ROMs, you can try CyanogenMod or MIUI
However, i would first recommend that you download 4EXT recovery (link in my sig) and flash that instead of CWM (from inside recovery). Then use the format option to reformat your system, data and cache partitions to ext4 and then flash the ROM.
enigmaamit said:
Just copy the ROM in my signature to your sd card and boot into recovery, and use install from sd card option to flash it.
If you want a sense 3.0 ROM, this is the best out there. For Non-sense ROMs, you can try CyanogenMod or MIUI
However, i would first recommend that you download 4EXT recovery (link in my sig) and flash that instead of CWM (from inside recovery). Then use the format option to reformat your system, data and cache partitions to ext4 and then flash the ROM.
Click to expand...
Click to collapse
i saw your post to late..i already installd cm7 for the desire s..it works great by now
cristiedward said:
i saw your post to late..i already installd cm7 for the desire s..it works great by now
Click to expand...
Click to collapse
Glad to know youre up and running without problems. Just trying to help.
Might i suggest that you edit your first post and amend the topic by adding the prefix [SOLVED] to it, so its clear that you've found the answer you were looking for?
It will also attract the attention of those in a similar predicament as you were in when you started the thread.
Cheers.
enigmaamit said:
Glad to know youre up and running without problems. Just trying to help.
Might i suggest that you edit your first post and amend the topic by adding the prefix [SOLVED] to it, so its clear that you've found the answer you were looking for?
It will also attract the attention of those in a similar predicament as you were in when you started the thread.
Cheers.
Click to expand...
Click to collapse
i have another question. if u have this chips my phone will fry eventualy no matter what?
cristiedward said:
i have another question. if u have this chips my phone will fry eventualy no matter what?
Click to expand...
Click to collapse
No. I have this "chip" too, and as long as you do not do a battery pullout when the phone is switched on, you are safe. There is no hard and fast rule that your phone will get fried just because you have this chip. Lots of people have it on their phones and most aren't even aware of it! So i wouldn't worry too much about it.
Even if by mistake, you do pull out the battery while the phone is powered up, DO NOT REINSERT IT IMMEDIATELY. Wait for around 30 sec to a minute, then reinsert it.
This is very important. You shouldn't be doing battery pulls, but if you HAVE to, wait for some time before putting it back in... i guess it'll give some time for the capacitors to discharge and not cause a spike of current when you reinsert after some time.
Seems to be working well for people who are doing frequent battery pulls, despite being on the same eMMC chip as us.
Hope this helps you.
enigmaamit said:
No. I have this "chip" too, and as long as you do not do a battery pullout when the phone is switched on, you are safe. There is no hard and fast rule that your phone will get fried just because you have this chip. Lots of people have it on their phones and most aren't even aware of it! So i wouldn't worry too much about it.
Even if by mistake, you do pull out the battery while the phone is powered up, DO NOT REINSERT IT IMMEDIATELY. Wait for around 30 sec to a minute, then reinsert it.
This is very important. You shouldn't be doing battery pulls, but if you HAVE to, wait for some time before putting it back in... i guess it'll give some time for the capacitors to discharge and not cause a spike of current when you reinsert after some time.
Seems to be working well for people who are doing frequent battery pulls, despite being on the same eMMC chip as us.
Hope this helps you.
Click to expand...
Click to collapse
yes thank..and btw Cm7 runs flawlesly by now..and the battery life is..OMG almost double..i hope it reamins the same
Hi all, I am sorry if this is already posted or answered but I spent all day yesterday searching and reading and cannot find the answer.
I have 2 Htc sensations that I messed up some how and would be very grateful if you could help me with them.
Phone 1 has been rooted for a long time and in preparation for ICS I flashed T-mobil: Download 3.32 from here
http://forum.xda-developers.com/showthread.php?t=1459767
and now the phone works but it will randomly reboot. I have wiped the cache, delvak cache and battery stats.
I am completely lost please help.
Phone 2 I think I may have messed up real bad here is what I did to it.
I rotted it from here
http://forum.xda-developers.com/showthread.php?t=1192300
I got to step 2 sub step 6 and now it continuously reboots it starts with the white screen with HTC on it then goes to another white screen that says HTC Quietly brilliant for a second and repeats.
Please help me yes I am a noob and grateful for any help.
Wow that was a fun ride (not really) it appears I did not flash the PG58IMG file correctly, after I flashed it correctly I got Insert Coin installed and so far it seems that they both are working. only time will tell.
Thanks anyway guys.
A.J.
If you are trying to install the latest firmware and having the HTC log restart problem. Try to super wipe on the recovery and install first the 3.12 firmware.
HTH
Did you install supercid after root?
Sent from my HTC Sensation 4G using xda premium
Both phones are working fine but I have a new question, I can not get the voice dialer to work ie I long press the button on my plantronics bt and say call tom.
I have tried vlingo from the market and this fix
http://forum.xda-developers.com/showthread.php?t=1133246
but nothing has worked. is it just not working in Insert Coin rom?
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
which of the 2 phones you are talking about?
In a previous post you said that problem was solved, now what?
Also, it would be better to know what your bootloader says and what you were attempting to do before black screen.
area1509 said:
Did I just brick my phone?
I tried to flash the 1.17 firmware and the last step failed, now it wont boot at all just a black screen the only thing it will do is the charge lite will come on bit it stays on after I unplug it.
Click to expand...
Click to collapse
Sounds like a brick to me, but since the problem is unclear, it's possible to fix. I wish I could help but I don't understand your issue to be honest!
I had 3.32 on it with Insert Coin ICS and thought I have 2 so might as well restore one to factory setting that's when I tried to flash the 1.17 and it never started again.
T-Mobile HTC Sensation 4G
The other one is working so I am not messing with it.
I had the same thing happen to me and it was over for the phone. Took it in to tomo and told them it died and after I charged it and went to turn it on, bam, went black and never came back. They never got it to work either and replaced it for me
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
kualmente said:
You mean 1.17 is the hboot?
In this case you installed a hboot for GB while on ICS rom. Obviously it won't work.
If you want to downgrade to GB you can try to run a GB RUU while in bootloader - fastboot usb (if you can still reach it)
Click to expand...
Click to collapse
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
mugetsu666 said:
He was in the process of going back to gb and that's 1 of the steps. U have to flash a gb firmware to go back to it from ics. I've done it countless times with no issues.
Click to expand...
Click to collapse
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
No what's happened to him is what happened to me. It's like it gets fried or something. The screen goes black and u can't turn it on or get into bootloader. Tmobile told me when it happened it was dead and got me a new 1
kualmente said:
Oh yes I have made many times too buf, if he changed firmware without changing rom obviously get stuck, and this seems happening to him.
Click to expand...
Click to collapse
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
area1509 said:
Yes you got it I will try to get it replaced. Wish me luck.
Thank you guys so much.
Click to expand...
Click to collapse
Good luck mate. Just let us know if it worked
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Andrew10567 said:
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Click to expand...
Click to collapse
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Don't panic.right now there is no solution.There will be one soon.
GOOD LUCK
Wrong section ...... And not to be a **** the but hahaha people really need to Stop and read
Sent from my Nexus 7 using Tapatalk 2
Andrew10567 said:
Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Taking the time to research before flashing a ROM that is not even meant for your phone would have saved a lot of heartache:
http://forum.xda-developers.com/showthread.php?t=1974101
I thought the ICJ Bricking Crew was no more. I guess those clowns are trying to make a comeback.
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
I have downgraded using JET from 1.14 to 2.20. Process includes bricking your phone to get into special recovery mode that give RW access to hboot, but you do need TWRP at some point I think (not sure though) to get in bricked, before you start downgrade, so you might not be able to downgrade.
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
OP gives you there way to verify that device is connected and part of the steps is listing partitions. If you can get partitions listed on your PC, then I think you can just dd system image and it should come back to life... also have you tried 2.20 RUU? I had a corrupted system partition (bad sector causing reboot when I would try to access system - including booting phone or into twrp recovery). I ended up using RUU (which also failed from the same bug, but It actually reformatted my system partition giving me access to twrp and then I was able to restore).
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Lol. wow kid.
Sent from my HTC One XL
rpomponio said:
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It hurts to laugh so hard.
igagnidz said:
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Sent from my One X using xda premium
Myrder said:
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Click to expand...
Click to collapse
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
iElvis said:
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
Click to expand...
Click to collapse
I don't ever wipe /system when flashing ROMs. It gets wiped when you flash anyway. I always wipe user data (factor reset), Dalvik and cache. But that's it.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
Yep, if you format /system, the build.prop is gone, and the assert looks to the build.prop.. why it flashes, I don't know.
The way its set up seems like it would only flash if "ro.device=endeavoru" or whatever the line is, is present. I guess there is no fail safe to stop the process if the build.prop isn't present
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They do and you're not the first to ask. I think they just swap up the motherboard.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They can fix any software corruption they have the tools too they know their phones front to back and can rewrite anything to them...just tell them what happened and they'll tell you the cost( maybe they'll feel bad and give a nice price) honesty can get you in good places sometimes
Thanks. Will send everyone who replied a thank button. Regardless of what type of comment...... I'll need to check the cost. Hopefully its below 100....