Database Info

IF You have gotten FAIL-PU or partition errors in recovery, please read!

I'm currently trying to round up commonalities between cases of cache, etc not being able to be mounted, which seems to happen with FAIL-PU when trying to use PD15IMG. Unfortunately, to figure this out, I need at least two people who have recovered from this issue and still have the original phone.
So please, if you've had this issue and recovered, post here so i can contact you and figure some stuff out.

In the post emmc thread there was a guy who recovered from it..get with him and you are halfway there

Good to see people here took my cause and now I got the whole community involved in this grimy issue that none would shed light upon it. Far as me getting another MT4G goes for pure emmc hack goes I am still waiting maybe I can get soon. But you folks keep on with your research and collect all the people who is involved in single thread as it will be much easier for me then.

Not sure what u r looking for but I have recovered my gf mt4g a few weeks ago from this using PD15IMG
sent from my demonSPEED_EXT4 Glacier using XDA Premium App

thederekjay said:
Not sure what u r looking for but I have recovered my gf mt4g a few weeks ago from this using PD15IMG
sent from my demonSPEED_EXT4 Glacier using XDA Premium App
Click to expand...
Click to collapse
Fail-PU means failed partition update. At that point the block wouldn't update along with the radio will fail now are you absolutely sure it was fail-pu? How did you determine it was fail-pu? The E:\ can't mount on recovery is just the side effect which you see after its corrupted. So in terms you can recover from E:\ can't mount but when you receive fail-pu flag game is over as we know it. Since how our mmcblk is allocated it we can't low level format to reconstruct it. So at that point the motherboard has to be replaced.
I successfully recovered from it as I was the one who initially started this investigation few months back. I was able to push the recovery image manually. But as I stated there are alot of variables unaccounted for specially the chip difference as the device I tested was on SEM04G.
1) Make a poll between 2 chips and check which ratio is higher.
2) Those effected by the fail-pu which chip they have.
3) Which rooting meth did they use and effected the higher ratio.
Until I get my hand on another MT4G or I upgrade to newer device I can't risk my current working phone as I use it for biz.

i have gotten those cache errors on clockworkmod and i still do once in awhile but i have the SEM04G Emmc chip and i thought those errors were normal and i proceeded on flashing other roms and everything would work fine

I just encountered this fail pu when trying to get my mt4g back working after it just was stuck on splash screen and did not want to boot up. I don't know how the engineering bootloader is supposed to help since I have it and it has not helped. I loaded PD15IMG to root of sdcard and pressed vol down and power button and then got the fail-pu still.

Engineering bootloader doesn't help in case of Fail-PU, only on case of "can't mount recovery, cache, etc" but without Fail-PU.

Fail-pu doesn't let me do anything to revert to a returnable MT4G. Not cool
Sent from my SGH-T959 using XDA App

U recovered from fail-pu? How exactly ?.
UsrBkp said:
Fail-PU means failed partition update. At that point the block wouldn't update along with the radio will fail now are you absolutely sure it was fail-pu? How did you determine it was fail-pu? The E:\ can't mount on recovery is just the side effect which you see after its corrupted. So in terms you can recover from E:\ can't mount but when you receive fail-pu flag game is over as we know it. Since how our mmcblk is allocated it we can't low level format to reconstruct it. So at that point the motherboard has to be replaced.
I successfully recovered from it as I was the one who initially started this investigation few months back. I was able to push the recovery image manually. But as I stated there are alot of variables unaccounted for specially the chip difference as the device I tested was on SEM04G.
1) Make a poll between 2 chips and check which ratio is higher.
2) Those effected by the fail-pu which chip they have.
3) Which rooting meth did they use and effected the higher ratio.
Until I get my hand on another MT4G or I upgrade to newer device I can't risk my current working phone as I use it for biz.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

UsrBkp said:
I successfully recovered from it as I was the one who initially started this investigation few months back. I was able to push the recovery image manually. But as I stated there are alot of variables unaccounted for specially the chip difference as the device I tested was on SEM04G.
1) Make a poll between 2 chips and check which ratio is higher.
2) Those effected by the fail-pu which chip they have.
3) Which rooting meth did they use and effected the higher ratio.
Until I get my hand on another MT4G or I upgrade to newer device I can't risk my current working phone as I use it for biz.
Click to expand...
Click to collapse
tjhnf said:
U recovered from fail-pu? How exactly ?.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
He says it "I was able to push the recovery image manually."
I've heard alot of talk about that being one of the options, but now knowing that the failpu error is caused by a hardware issue, I cant credit this method or believe that it works..

I had the error, recovered from it then got the error again a week later. Have not been able to recover again though using the same method I used last time or any other method I could find on the site. I still have the bricked device if I can help shoot me a PM. I wanna get this little demon off our back!

Where do I check to see which chip it is?
Sent from my HTC Glacier using XDA Premium App

JDV28 said:
He says it "I was able to push the recovery image manually."
I've heard alot of talk about that being one of the options, but now knowing that the failpu error is caused by a hardware issue, I cant credit this method or believe that it works..
Click to expand...
Click to collapse
For me manually pushing the recovery via fastboot did work, but I never got the failed PU error. The reason I never got it was because I never tried to flash the image the FIRST time my phone got the CWM errors. I didn't know about that being an option and off the cuff tried the whole flashing an old CWM thing and basically got lucky. Now that my phone has gotten the error again NOTHING works and I get the failed PU error. Whether I would have got this error the first time or not I have no idea.

Dcwiker05:
What command did u use? Where does the recovery get pushed to?
~noob
XDA App

fastboot flash recovery your_recovery_image.img
Obviously, recovery goes to recovery partition.

Jack_R1 said:
fastboot flash recovery your_recovery_image.img
Obviously, recovery goes to recovery partition.
Click to expand...
Click to collapse
what he said. I found it is easiest just to rename the recovery you download to recovery.img so you dont have to type as much. Also all this is done in fastboot under the hboot menu

I will try that and see if another rom loads... or at least to load original recovery to return. XDA App

Well... tried to push recovery through fastboot and nothing. Tried going and putting the command to make mt4g unable to boot or charge and still nothing.
I still have access to cwm recovery but can't do anything with it or even revert back to stock recovery. Aaaah
XDA App

tjhnf said:
Well... tried to push recovery through fastboot and nothing. Tried going and putting the command to make mt4g unable to boot or charge and still nothing.
I still have access to cwm recovery but can't do anything with it or even revert back to stock recovery. Aaaah
XDA App
Click to expand...
Click to collapse
Me too I tried hard to change S=OFF and realised that I can´t yet. God Damn Chip!

Bricked after all this time

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.

bricked one x

So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX

tae_254 said:
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX
Click to expand...
Click to collapse
so from mounting
im trying to install the Android Revolution HD 9.7.2 Ice Cream Sandwich
it allows me to choose settings, and such and start install.
after starting install, it goes through the files and such, but when it gets to /system/lib/ it just closes on itself, and goes back to twrp screen and recovery home. the rom never finishes installing. right now im gonna re-download the rom and see if that works.
if i cannot install the custom rom, how can i go back to stock exactly?
do i need to find the stock ruu?

fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?

hopefully you aren't using cwm anymore and flashed twrp for the evita.

chinaman_chong said:
fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942

CleanROM on Viper XL
---------- Post added at 12:14 PM ---------- Previous post was at 12:13 PM ----------
chinaman_chong said:
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
CleanROM or Viper XL

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942
Click to expand...
Click to collapse
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:

Crappyvate said:
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:
Click to expand...
Click to collapse
I didn't even have to use the search function. 2 are near the top of General. The remaining has slipped past the first page, but its still pretty high up there.
People who flash a ROM for the international version are simply neglecting to do any basic reading and learning before flashing things willy-nilly, that's my point.

thanks for the help guys. i flashed viper xl yesterday night right after, loving it thus far. i was just so used to the sense keyboard already, and hated the cramped jb keyboard, and this rom has simple little tweaks
i did read, but i guess not thoroughly enough. in hindsight, i wasnt aware that the one x was different than the xl, its fairly easy to miss that the other roms are not compatible with this phone. and is completely different alltogether.
if i had known that, i wouldnt have flashed cwm, and would not have need to post a help thread. all "solutions" i attempted on my own were based off readings of the hox, rather than the evita, once again causing more problems. it was easily enough fixed once i figured that bit of information out.
i am a noob, but this phone is not my first time rooting, so with my prior knowledge i felt i was more than ready to tackle this rom flashing, im sure plenty of others will make the same mistake as i did.
the other phones ive rooted and flashed had their one model of phone only, so all the roms available were compatible.
im just glad my phone is not bricked, and i now have root access

chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Do not use CMW it causes lot of problems(not recommended for our device) . Use TWRP recovery instead
Sent from my HTC One XL using xda premium

redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Click to expand...
Click to collapse
That and Superwipe. I remember that zip from other phones I used that rom on.
Sent from my HTC One XL

Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Subscribe to the OneXL forums and stay here till you recognize your community!
Sent from my HTC One XL using xda app-developers app

can't brick from it after 2.20

DvineLord said:
can't brick from it after 2.20
Click to expand...
Click to collapse
Good thing eh
Sent from my HTC One XL using xda app-developers app

InflatedTitan said:
Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Click to expand...
Click to collapse
From what others are saying, the newer hboot that came with 2.20 is write protected. Hboot can't be overwritten by flashing a ROM for the international One X. ROM just fails to flash, and you get a recoverable condition like this one, as opposed to hard bricks on the older hboot.

Yea, at least there's one good thing that came with the dreaded update
Sent from my HTC One XL using xda app-developers app

How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help

h1m said:
How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help
Click to expand...
Click to collapse
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu

omario8484 said:
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu
Click to expand...
Click to collapse
Where do i get the ruu file? I can't mount my sdcard

Bricked HTC One X

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....

[Q] Stuck on CWM Recovery Everytime

Hello everyone,
It's my first time witnessing this issue, I do have a Samsung Galaxy S 4G. So I decided to upgraded Eclairs to Gingerbread. Which I did.
Somehow I downloaded the CM7 ROM in the SGS 4G section, I have flashed it and now everytime I click "reboot system now", it's just putting me back to CWM Recovery over and over again. Now I got tired of it, so I tried flashing the SlimBean in hopes of making my device work the way they should, but it's the same result. When I cleared data, flashed the ROM and Gapps and when I click "reboot system now", It shows the boot screen but then it transferred me back to recovery. I don't really know what to do.
Urgent help needed. Thank you all.

can you acess into download mode?

PuNeTZzZ said:
can you acess into download mode?
Click to expand...
Click to collapse
Yes I can, also tried it with CM9, same results it shows recovery everytime. I need some help. :crying:

You say you went from Eclair (Did this phone even come with that? I thought it started with Froyo. Huh. At least, mine did.) to Gingerbread. Is the Gingerbread you started with CM7, or did you start with one that actually has normal GB bootloaders first? Because if you haven't yet, as with any major bootlooping issue, you'll want to use a proper GB one-click. If you failed to double-flash one of those to get the GB bootloaders earlier, do that ASAP. And hope hard that they come.

You are missing the boot loader if you went straight to Gingerbread. Use Heimdall One Click to flash to Gingerbread. Also click on the bootloader option as well when you flash.
Sent from my SGH-T959V using xda premium

Theraze said:
You say you went from Eclair (Did this phone even come with that? I thought it started with Froyo. Huh. At least, mine did.) to Gingerbread. Is the Gingerbread you started with CM7, or did you start with one that actually has normal GB bootloaders first? Because if you haven't yet, as with any major bootlooping issue, you'll want to use a proper GB one-click. If you failed to double-flash one of those to get the GB bootloaders earlier, do that ASAP. And hope hard that they come.
Click to expand...
Click to collapse
Can you give me the names of the GB one-click?

Search for lumin30. He has an awesome guide and links to what you are looking for. It's in his signature.
I'll add, back up your .efs folder. Put copy on your computer.

champ1919 said:
Search for lumin30. He has an awesome guide and links to what you are looking for. It's in his signature.
I'll add, back up your .efs folder. Put copy on your computer.
Click to expand...
Click to collapse
Can anyone tell me this guide works on starting from a CM7 Rom. I don't get it at all. Since it started from Stock Froyo.