[SOLVED]Recovery image won't flash - Motorola Atrix 2

I was doing a stock restore on my phone (manually with fastboot as I was in Ubuntu.) and erased system and userdata and recovery, then flashed system (no need to do boot on my case) and tried recovery, but it kept giving me preflash validation failure. Now I have no stock recovery?!?! This could end up being a problem at some point, so How can I get it back. It wouldn't go as part of the stock restore scrip yet. Haven't tried RSDlite.

Bump, really need help here.

lkrasner said:
I was doing a stock restore on my phone (manually with fastboot as I was in Ubuntu.) and erased system and userdata and recovery, then flashed system (no need to do boot on my case) and tried recovery, but it kept giving me preflash validation failure. Now I have no stock recovery?!?! This could end up being a problem at some point, so How can I get it back. It wouldn't go as part of the stock restore scrip yet. Haven't tried RSDlite.
Click to expand...
Click to collapse
Dude did u try bpears one click method to restore? It works for me
Sent from my MB865 using XDA

daavvis said:
Dude did u try bpears one click method to restore? It works for me
Sent from my MB865 using XDA
Click to expand...
Click to collapse
yep, but it doesn't even try recovery at all

lkrasner said:
yep, but it doesn't even try recovery at all
Click to expand...
Click to collapse
Damn.... did u pm jim? Bet he knows... lol... no way to pull it from a different phone and push it to yours i bet either.....:/
Sent from my MB865 using XDA

Try rsdlite it might see your phone. Even if your screen is blank it still might be in fastboot mode. Rsdlite will tell you
Sent from my MB865 using Tapatalk 2

daavvis said:
Damn.... did u pm jim? Bet he knows... lol... no way to pull it from a different phone and push it to yours i bet either.....:/
Sent from my MB865 using XDA
Click to expand...
Click to collapse
all because we have a locked boot loader. now I'm even more pissed about it. I don,t think I can update to ics without it
Sent from my MB865 using xda premium

rdhoggattjr said:
Try rsdlite it might see your phone. Even if your screen is blank it still might be in fastboot mode. Rsdlite will tell you
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
my phone works fine. I just have no stock recovery on it, which may be a problem down the line. RSD does not try to flash recovery and it won't flash with manual fastboot, so I don't know how to get it back.

You mentioned manual "fastboot", now you are using the moto-fastboot utility, correct?
You might try both of these things, one at a time though:
1) Try and flash the device_tree.bin file with the moto-fastboot util, then try and flash them in this order - system.img, boot.img, recovery.img, radio.img, cdrom, preinstall.img, webtop (grfs.img)
2) Restore the backup that some others had to do to get going again after I think something similar.
http://forum.xda-developers.com/showthread.php?t=1493386

jimbridgman said:
You mentioned manual "fastboot", now you are using the moto-fastboot utility, correct?
You might try both of these things, one at a time though:
1) Try and flash the device_tree.bin file with the moto-fastboot util, then try and flash them in this order - system.img, boot.img, recovery.img, radio.img, cdrom, preinstall.img, webtop (grfs.img)
2) Restore the backup that some others had to do to get going again after I think something similar.
http://forum.xda-developers.com/showthread.php?t=1493386
Click to expand...
Click to collapse
I'll try the dev tree thing. I sort of tried the other one already, but I will do it completely too. Thanks.

jimbridgman said:
You mentioned manual "fastboot", now you are using the moto-fastboot utility, correct?
You might try both of these things, one at a time though:
1) Try and flash the device_tree.bin file with the moto-fastboot util, then try and flash them in this order - system.img, boot.img, recovery.img, radio.img, cdrom, preinstall.img, webtop (grfs.img)
2) Restore the backup that some others had to do to get going again after I think something similar.
http://forum.xda-developers.com/showthread.php?t=1493386
Click to expand...
Click to collapse
Lol..... called it!!! Lol
Sent from my MB865 using XDA

lkrasner said:
I'll try the dev tree thing. I sort of tried the other one already, but I will do it completely too. Thanks.
Click to expand...
Click to collapse
Now if you are flashing the 2.3.5 over 2.3.6 or even ICS, you still have to replace those files the same as you would for RSDlite.
Not sure if you knew that, so I thought I would just throw it out there.

daavvis said:
Lol..... called it!!! Lol
Sent from my MB865 using XDA
Click to expand...
Click to collapse
LOL!
Oh Jim, why must you know so much! If I do end up getting another phone you better join that forum t0o. I suppose I should fix this before I trade it away though.

jimbridgman said:
Now if you are flashing the 2.3.5 over 2.3.6 or even ICS, you still have to replace those image files the same as you would for RSDlite.
Not sure if you knew that, so I thought I would just throw it out there.
Click to expand...
Click to collapse
speaking of ics, and totaly off topic for here, do you think I can flash the boot.img that I got dumped from someone who had it working on my ATT phone or no. Will it hurt anything/can I get back to the original one.

lkrasner said:
LOL!
Oh Jim, why must you know so much! If I do end up getting another phone you better join that forum t0o. I suppose I should fix this before I trade it away though.
Click to expand...
Click to collapse
Let me know which phone you go to.... I am also looking for something else. I am keeping the A2, so that I can really tear it apart.
Right now it looks like the Galaxy S III will be out soon, so I might be looking into that. I will definitely NOT have another Moto phone though, after this... now if Google guts them and they actually produce a true open phone, then maybe.

jimbridgman said:
Let me know which phone you go to.... I am also looking for something else. I am keeping the A2, so that I can really tear it apart.
Right now it looks like the Galaxy S III will be out soon, so I might be looking into that. I will definitely NOT have another Moto phone though, after this... now if Google guts them and they actually produce a true open phone, then maybe.
Click to expand...
Click to collapse
I'm kind of broke so I will be trading plus maybe some cash. I have possible offers for an gs2 skyrocket and htc vivid. Both look pretty good. Development is pretty good for both but probably better for the skyrocket.

lkrasner said:
speaking of ics, and totaly off topic for here, do you think I can flash the boot.img that I got dumped from someone who had it working on my ATT phone or no. Will it hurt anything/can I get back to the original one.
Click to expand...
Click to collapse
I would say give it a try, but, I would have a computer ready that can run RSDlite.... My macbook pro has windblows 7 installed in bootcamp just for this purpose. Previous to this phone, I NEVER had a need to actually BOOT windblows (never had bootcamp working), I have it running in VMs on my ubuntu and my macs/hackintoshes, for other things.
YOU MUST NOT RUN RSDLITE IN VMWARE!!!! I tried and it was dismal, I had to exchange that phone it was so bad, that it would not even power on, and RSDlite said success.

jimbridgman said:
I am also looking for something else.
Right now it looks like the Galaxy S III will be out soon, so I might be looking into that. I will definitely NOT have another Moto phone though
Click to expand...
Click to collapse
Same here...was considering the HTC One X but man, the non-removable battery and lack of microSD slot are deal breakers for me since 12gb of useable space just won't cut it. So i'm holding out hope the SGS3 comes out here by July and is around the $250 price point on contract.

916x10 said:
Same here...was considering the HTC One X but man, the non-removable battery and lack of microSD slot are deal breakers for me since 12gb of useable space just won't cut it. So i'm holding out hope the SGS3 comes out here by July and is around the $250 price point on contract.
Click to expand...
Click to collapse
Hey, haven't seen you in a while...
I was thinking the exact same thing. The one x just is not doing it for me... all in the cloud.... LOL... that is the next crap carriers are going to sell us, cloud space and a more expensive data plan for that.
Yeah the gs III is it for me.. I hope it is 299 or less on contract.
Sent from my MB865 using xda premium

jimbridgman said:
Hey, haven't seen you in a while...
I was thinking the exact same thing. The one x just is not doing for me... all in the cloud.... LOL... that is the next crap carriers are going to sell us, cloud space and a more expensive data plan for that.
Yeah the gs III is it for me.. I hope it is 299 or less on contract.
Click to expand...
Click to collapse
Emotions were running high there for a bit so I had to take a break and let things simmer down. As popular as the SGS3 is, the dev for it should be awesome...especially with guys like you owning it It will be my first high end Android device so i'm hoping it lives up to the hype

Related

Well crap... I have a hard brick

Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!
Time to get your story straight.... "I just turned it off and it won't turn back on??? Maybe my chargers broken?"
Sent from my SCH-I535 using xda app-developers app
dushotgun said:
Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!
Click to expand...
Click to collapse
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Wait you tried to unzip the kernel in your pc? For what exactly? How did you flashed it back unzipped?
VERIZON GALAXY S 3
jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?
dushotgun said:
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?
Click to expand...
Click to collapse
You can try a USB Jig to force your phone into Download mode, but if it's truly hardbricked then JTAG or getting a replacement are your only options.
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
we're only human if i had this phone and saw this unlocked bootloader i would get excited about it as well lol i feel for the man/woman
Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.
dushotgun said:
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.
Click to expand...
Click to collapse
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help
jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Sucks, OP.
And don't even bother writing Adam. I don't know him, but I read his threads. He just had a major accomplishment (with help) and he will probably not even respond. Let him have his day/peace. He earned it. You admit that you jumped the gun.
Sent from my SCH-I535 using Tapatalk 2
Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Ohhh..c'monnnn- he/she was a Droid X user. As a fellow X2 encrypted bootloader ****ing never unlocked I was excited as **** about it being cracked too.
I'm not ****ing with my kernel or nothing.. but.. I couldn't resist. Been on lock down for 2 years- pre ordered the phone and come to find out they locked this ****er too.
Don't be so hard on the guy/gal.. :angel:
Coderedpl said:
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help
Click to expand...
Click to collapse
I sent him a message but no response yet. I tried that and I still get nothing thanks though. I've read every page of the bootloader research by adam I saw this on his original post:
"op5= aboot
This block is signed by Samsung, we will not be able to modify it
This block contains HTML information. It would appear that it is possible to put the device into a mode where it will provide a webserver which displays state information.
This block appears to be a complete operating system
This block contains the Loke Daemon which communicates with Odin3."
I take this to mean there is no way for me to communicate with odin now and jig wouldn't be able to force it into odin either since I overwrote the 0p5 block. I guess thats it since I don't have a jtag set up.
Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest
You flashed the kernel to the aboot partition, most likely meaning no booty booty to get into a state (download mode) where you can ODIN to stock. That being said, looks like you'll be JTAGing in your near future. Curious about prices, if you do it!
ooofest said:
Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest
Click to expand...
Click to collapse
It's $60
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
ooofest said:
Have you considered inquiring about JTAG rates from these folks?
- ooofest
Click to expand...
Click to collapse
Thanks for the link, it looks like thats my only option for getting it fixed.
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
It will and it will ENJOY it.
JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
dd = disk destroyer :laugh:

[MODS] Lock/Delete me [/MODS]

MODS: Please lock this thread. And delete it if I can keep the thanks stats, Thanks.
If your looking for an improved version, see here.
thanks!!!
tcf38012 said:
OK, so finally I recovered my phone from flashing an unsigned system.img on the 67.21.125 ICS (The second version).
I'll go into detail later but here is what I did:
First, I flashed everything included in my fxz minimal.fastboot files.
Second, I flashed the 2.3.6 boot, system, and webtop partition (DON'T FLASH ANY OTHERS RATHER THAN THE boot,system, and grfs img's or you will hard brick your device).
Third, I entered recovery and applyed the first ICS leak, then it went into fastboot and complained about recovery and cdt so I flashed it from the minimal fxz's. And then I re-applyed the ics leak and then Something unreal happened, it booted :laugh::laugh::laugh:.
Last, I OTA'ed to the .125 leak again and everything was back to %100 normal.
And thats the end of the story, someone can write a tutorial from there .
Cheers!!!
PS: I'm not responsible if you bricked your device for good becuase of this, SO DON'T BLAME ME!!!
PSS: If this helped, then please hit the THANKS button below.
Click to expand...
Click to collapse
Nice job!!!
So to make this clear, you found a way to go back to 2.3.6 from the second ics leak? Im not really understanding this.
Sent from my MB865 using xda premium
That is huge! Thank you..
Sent from my phone's mind
tmease1 said:
So to make this clear, you found a way to go back to 2.3.6 from the second ics leak? Im not really understanding this.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Accually, It is not downgrading to gb but getting ics working again. If you try to boot gb instead of going to recovery, then you would boot loop.
So if your bricked, then this is the solution to fix it.
tcf38012 said:
Accually, It is not downgrading to gb but getting ics working again. If you try to boot gb instead of going to recovery, then you would boot loop.
So if your bricked, then this is the solution to fix it.
Click to expand...
Click to collapse
Ya i got it after reading it again, thanks.
Sent from my MB865 using xda premium
Wow...this is EXACTLY what I need...I'm not sure as to how exactly you did this. The wording confuses me I guess...feel like a noob lately :/ But excellent work either, Hope I can get this down. I nees to get back to stock ICS but am only able to get into stock ICS recovery/fastboot. Awesome...I hear hope!
Sent from my MB870 using xda premium
DX2Trip said:
Wow...this is EXACTLY what I need...I'm not sure as to how exactly you did this. The wording confuses me I guess...feel like a noob lately :/ But excellent work either, Hope I can get this down. I nees to get back to stock ICS but am only able to get into stock ICS recovery/fastboot. Awesome...I hear hope!
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Yes his wording confused me a well, don't feel bad. I'm still not sure how he did this.
Sent from my MB865 using xda premium
DX2Trip said:
Wow...this is EXACTLY what I need...I'm not sure as to how exactly you did this. The wording confuses me I guess...feel like a noob lately :/ But excellent work either, Hope I can get this down. I nees to get back to stock ICS but am only able to get into stock ICS recovery/fastboot. Awesome...I hear hope!
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
tmease1 said:
Yes his wording confused me a well, don't feel bad. I'm still not sure how he did this.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Well, a few things are not so clear yet - give us a little while to try and come up with a more direct way - or for tcf to put together a guide - but this is my understanding (please correct me or add if necessary, tcf):
He's talking about the minimal fxz package he put together from here: http://forum.xda-developers.com/showthread.php?t=1912035 (which only has a linux script I believe - but you could flash them one by one through the command prompt in windows - or, we could get a batch file made up also).
Then, the system.img, recovery.img, and grfs.img only from 2.3.6 (found in the 2.3.6 fxz from here or the same are in the leak#1 2.3.6 fxz).
Then he applied the leak#1 ota package.
Got thrown back into fastboot.
Flashed the cdt.bin again from the minimal fxz package (which is actually from ICS leak#2/soak package) -- but not sure if he flashed recovery.img from there again also..
Then he re-applied the leak (#1?) again - and it booted to ICS.
So, I am not sure about the timing of things or how it exactly worked out yet, but I notice the linux script for the minimal fxz package doesn't have a reboot-bootloader before the cdt.bin flash - also there should probably be a pause after the reboot-bootloader lines to allow it to reboot completely before attempting to flash the next file. That may be partial reason for the multiple flashings of the cdt.bin.. but, again, maybe not - maybe it's all in some magical order... though a few of us will be digging a bit deeper into this I'm sure.
Thanks again to tcf38012 for pushing this thought of upgrading back to the leak - we were on that path at one time, but the pieces of the puzzle weren't fitting together..
alteredlikeness said:
Well, a few things are not so clear yet - give us a little while to try and come up with a more direct way - or for tcf to put together a guide - but this is my understanding (please correct me or add if necessary, tcf):
He's talking about the minimal fxz package he put together from here: http://forum.xda-developers.com/showthread.php?t=1912035 (which only has a linux script I believe - but you could flash them one by one through the command prompt in windows - or, we could get a batch file made up also).
Then, the system.img, recovery.img, and grfs.img only from 2.3.6 (found in the 2.3.6 fxz from here or the same are in the leak#1 2.3.6 fxz).
Then he applied the leak#1 ota package.
Got thrown back into fastboot.
Flashed the cdt.bin again from the minimal fxz package (which is actually from ICS leak#2/soak package) -- but not sure if he flashed recovery.img from there again also..
Then he re-applied the leak (#1?) again - and it booted to ICS.
So, I am not sure about the timing of things or how it exactly worked out yet, but I notice the linux script for the minimal fxz package doesn't have a reboot-bootloader before the cdt.bin flash - also there should probably be a pause after the reboot-bootloader lines to allow it to reboot completely before attempting to flash the next file. That may be partial reason for the multiple flashings of the cdt.bin.. but, again, maybe not - maybe it's all in some magical order... though a few of us will be digging a bit deeper into this I'm sure.
Thanks again to tcf38012 for pushing this thought of upgrading back to the leak - we were on that path at one time, but the pieces of the puzzle weren't fitting together..
Click to expand...
Click to collapse
Thanks for trying to clarify this. It seems like it would be time consuming for me to try since I'm a windows user. I am glad that he did find a way to get some of our soft bricked users back on track.
Sent from my SAMSUNG-SGH-I997 using xda premium
thanks for good job, waiting your instructions....
Yeah, this great man! I got an A2 that is stuck at the boot logo from a screw up on the second leak. I have a Samsung skyrocket now, so I'm the perfect guinea pig to try out what you need! Eagerly awaiting further instructions!
Sent from my SAMSUNG-SGH-I727 using xda premium
Did Anyone tested this?
I'll write a tutorial after school which I'm about to go to (High School). I get home at 3:45 - 4:30 and I get done my homework at 5:00 - 5:30 so I'll try to write it at 5:45.
Just hang in there!
Cheers!!!

Phone won't boot after rom flash?

I got my one x last week and rooted it a few days ago via the all in one method found here ( http://forum.xda-developers.com/showthread.php?t=1952426 ) and everything worked including superuser. After a few days of use I decided to try the icecoldjelly aokp rom found here ( http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/ ). The rom flash said successfull and so did the gaps zip. Then when I pressed reboot the phone never cam back on. I tired living it charging overnight in case it lost charge (even though it showed almost full before I flashed). I'm not sure but I think I may be out luck?
Is there anything I can try to get this thing to boot up?
Ezence01 said:
I got my one x last week and rooted it a few days ago via the all in one method found here ( http://forum.xda-developers.com/showthread.php?t=1952426 ) and everything worked including superuser. After a few days of use I decided to try the icecoldjelly aokp rom found here ( http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/ ). The rom flash said successfull and so did the gaps zip. Then when I pressed reboot the phone never cam back on. I tired living it charging overnight in case it lost charge (even though it showed almost full before I flashed). I'm not sure but I think I may be out luck?
Is there anything I can try to get this thing to boot up?
Click to expand...
Click to collapse
You flashed an international ROM, you now probably have an expensive paperweight. Sorry, please read the stickies next time
You may be able to dd a partition 4 to your phone if someone dumps one for you, and if you know how/someone is willing to help.
First go try this http://unlimited.io./qhsusbdload.htm
I hate seeing all these hard bricked phones I'm sorry but yeah u shoulda read:/
absolutelygrim said:
You flashed an international ROM, you now probably have an expensive paperweight. Sorry, please read the stickies next time
You may be able to dd a partition 4 to your phone if someone dumps one for you, and if you know how/someone is willing to help.
First go try this http://unlimited.io./qhsusbdload.htm
Click to expand...
Click to collapse
I figured as much. For some reason I mistook the international rom for the att one
If I tried to exchange it, would att be able to notice this?
I'll try your link first, thank you.
Ezence01 said:
I figured as much. For some reason I mistook the international rom for the att one
If I tried to exchange it, would att be able to notice this?
I'll try your link first, thank you.
Click to expand...
Click to collapse
Umm, yes they will notice it. Just don't run over it with your car and make an insurance claim :\
If you can install Ubuntu 12.04 and teamviewer i'd be willing to try and help you
absolutelygrim said:
Umm, yes they will notice it. Just don't run over it with your car and make an insurance claim :\
If you can install Ubuntu 12.04 and teamviewer i'd be willing to try and help you
Click to expand...
Click to collapse
lol, no definitely not insurance claim. I'm in the process now, I'll update with results. Thanks for the advice and help.
Ezence01 said:
lol, no definitely not insurance claim. I'm in the process now, I'll update with results. Thanks for the advice and help.
Click to expand...
Click to collapse
If it doesn't work and you still want help send me a PM
man that icecoldjelly rom is doing some damage....:crying:
Crappyvate said:
man that icecoldjelly rom is doing some damage....:crying:
Click to expand...
Click to collapse
Yea it is. But I think I have an idea that will help everyone.. Not that they will read the OP if I start a thread :beer:
absolutelygrim said:
Yea it is. But I think I have an idea that will help everyone.. Not that they will read the OP if I start a thread :beer:
Click to expand...
Click to collapse
don't tell me you want to start a tutorial on dd'ing to restore the partition that was overwritten by icecoldjelly that would be opening a big can of worms ? although maybe not since they are already bricked
Crappyvate said:
don't tell me you want to start a tutorial on dd'ing to restore the partition that was overwritten by icecoldjelly that would be opening a big can of worms ? although maybe not since they are already bricked
Click to expand...
Click to collapse
I will try that if I can't fix it.
They are already bricked so it won't hurt any more than it is right now
If I can fix this guy's phone, then i'll consider starting a tutorial.
I'm going to document everything as I do it, and make it noob proof. IF it works. BIG FAT IF
absolutelygrim said:
I will try that if I can't fix it.
They are already bricked so it won't hurt any more than it is right now
If I can fix this guy's phone, then i'll consider starting a tutorial.
I'm going to document everything as I do it, and make it noob proof. IF it works. BIG FAT IF
Click to expand...
Click to collapse
got a backup of my mmcblk0p4 if you want
Crappyvate said:
got a backup of my mmcblk0p4 if you want
Click to expand...
Click to collapse
Throw it to me
absolutelygrim said:
Throw it to me
Click to expand...
Click to collapse
just remove the .txt
Crappyvate said:
just remove the .txt
Click to expand...
Click to collapse
Right now we are trying to time it right and get his phone into emmc mode.. one that's done, I think we should have this problem fixed.
Windows recognizes it as QHSUSB_DLOAD (so its still alive), but when he holds down power, no lights flash, making this hard to time
---------- Post added 28th October 2012 at 12:22 AM ---------- Previous post was 27th October 2012 at 11:52 PM ----------
Crappyvate said:
just remove the .txt
Click to expand...
Click to collapse
Is your mmcblk0p4 from 2.20? I don't know if that would matter.
I think it's because we are using Ubuntu 12.10 and not 12.04, will report back eventually..
12.10 is not happening, if it's successful on 12.04, even just the unbrick method, I'm not concerned about the downgrade anymore, this could be good news for our little international rom lovers
Will try 12.04 sometime today
Sent from my HTC One XL using xda-developers app
absolutelygrim said:
12.10 is not happening, if it's successful on 12.04, even just the unbrick method, I'm not concerned about the downgrade anymore, this could be good news for our little international rom lovers
Will try 12.04 sometime today
Sent from my HTC One XL using xda-developers app
Click to expand...
Click to collapse
sorry i was out...no partition is from 1.85 or maybe even 1.73 don't remember,
any luck ?? have you tried to talk to beaups or 18th.abn ?
Unbricking has been a real pain in the butt using ubuntu, we found it to much easier and more successful using tinycore from a bootable USB. I don't know why, but it's been proven on several devices so try that. Also, p4 holds the device imei and cid, when it gets corrupted in may be causing the soft brick because p12 is dependent on its information since it also displays the device imei and phone info, so do p12, make sure your using a signed image and do p4, which can be any p4, the imei will just have to be repaired afterward. It will spring to life, I promise you
Sent from my HTC One XL using Tapatalk 2
Crappyvate said:
sorry i was out...no partition is from 1.85 or maybe even 1.73 don't remember,
any luck ?? have you tried to talk to beaups or 18th.abn ?
Click to expand...
Click to collapse
18th.abn said:
Unbricking has been a real pain in the butt using ubuntu, we found it to much easier and more successful using tinycore from a bootable USB. I don't know why, but it's been proven on several devices so try that. Also, p4 holds the device imei and cid, when it gets corrupted in may be causing the soft brick because p12 is dependent on its information since it also displays the device imei and phone info, so do p12, make sure your using a signed image and do p4, which can be any p4, the imei will just have to be repaired afterward. It will spring to life, I promise you
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
@crappy, nah we had to stop for the night cause I had to get up early and get senior pictures taken.
I had him install Ubuntu 12.04 rather than use a LiveCD, so we'll try it again later today.
@18th
We got to the point where it starts writing p4, but hangs and continuously sends the Reset, I posted in the thread over at the evo LTE forum asking about it, holding the power button for 30+ seconds as suggested prints an error cannot reset device
I am using mmcblk0p4 from crappy, and your hboot from dropbox.
On the hox, you only need to hold down the power button for about 10-12 seconds so 30 may be too long and sending a time out to the emmc recover tool
Sent from my HTC One XL using Tapatalk 2

[Q] Is there a way to completely wipe HTC One XL?

Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.
Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...
don't flash ICJ, just relock bootloader and ruu.
if you have no physical damage why are you getting a replacement phone?
Did you flash boot.img?
And how about you not ask how to defraud att because you don't know how to flash and fix a botched flash.
schumachermp said:
Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.
Click to expand...
Click to collapse
... and this is why we can't have nice things. Thanks, guy.
All I can think is, at least he did not throw it under his car.
It can be salvaged, where as other clown just destroyed it for nothing.
WR
Sent by WR's One XL
omario8484 said:
Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...
Click to expand...
Click to collapse
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.
schumachermp said:
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.
Click to expand...
Click to collapse
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2
InflatedTitan said:
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I did flash boot.img. It just never moved past the CM10 starting animation. And honestly, not super familiar with fastboot three days ago... fairly familiar at this point. But nothing seems to get this thing to work. Please tell me what to do!
(BTW - I only called warranty at the advice of an AT&T employee in the store. I'd love to just fix my phone)
Twrp 2.3.1.0, wipe everything, flash boot.img in fastboot, and flash cm10 and gapps in twrp.
How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
schumachermp said:
How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL
WarRaven said:
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL
Click to expand...
Click to collapse
Ok, great. I've downloaded the TWRP recovery image and the Goo Manager APK... now how do I use Goo Manager on a device that won't boot up?
You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2
InflatedTitan said:
You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.
schumachermp said:
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.
Click to expand...
Click to collapse
I'm happy you got your phone running.
Don't get it all sticky with all that love.
Lol good job bro
Sent from my One X using Tapatalk 2
ECEXCURSION said:
... and this is why we can't have nice things. Thanks, guy.
Click to expand...
Click to collapse
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started
rodpgfx said:
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started
Click to expand...
Click to collapse
Completely agreed. The notion astounds me (and disappoints me also) that the OP was going to send the phone in for a warranty replacement simply because they didn't do the proper research and learning before modding the phone. And when the condition was completely and easily reversible. If the screen comes on with this phone, it can be recovered.

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

Categories

Resources