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:
Related
Hi All,
OK, bootloader is unlocked, I am working on recovery, so the next challenge is....................S-OFF!!! Aw, f%@ck, I thought i had my life back...
I invite all users with ideas and/or knowledge to jump in and tell me what they think I am doing right and what makes me a moron. I have no pride, so lay it on me.
I will post progress reports in Post #2.
Anyway, here's to getting this done quickly.
Steve
Moderator Edit
This Thread has been moved back to the development section in an effort to put an end to the off topic discussion.
Given the size of this thread I'm going to suggest that you USE the Search thread feature located at the top to make sure your suggestion or idea has not been attempted already.
ANY OFF TOPIC POSTS WILL BE DELETED!
Progress Reports
Just starting out...
One More
This is just in case...
Excellent.
JSLEnterprises said:
Excellent.
Click to expand...
Click to collapse
Thought I'd get out of your thread and the root thread....
sk806 said:
Thought I'd get out of your thread and the root thread....
Click to expand...
Click to collapse
I had to send another message to red not to reopen the think tank thread (title would have been edited obviously), but to still go ahead with the cleanups... lol
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
you have to use this unlock method for the bootloader so why would it screw anything else up? It opens up all possibilities, not close them.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
Nope. I have flashed CWM recovery at least 4 times on an international One X AFTER unlocking the bootloader. I wish that were it....
I think you may be thinking of firmware, which is a real mess, because unlocking your bootloader can set your CID to "none", and thus, you can't flash different firmware (i.e., an EU firmware on an Asian phone)...not that that would matter for these carrier-branded phones...
Good job and great progress. Unfortunately, none of us AT&T users can join in on the fun.
killathenoob said:
Sorry if I'm totally off base here but I do believe reading on XDA somewhere that with the HTC One series phones when you unlock the bootloader it locks the phone from being able to flash recoverys.
This is the reason why I have waited to do the bootloader unlock I didnt want to screw myself from ever being able to flash custom roms.
Click to expand...
Click to collapse
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
JSLEnterprises said:
If that was completely true, then the Tegra 3 model's would not have cwm recovery... yet they do.
We just havent figured out a working method for ours.
Click to expand...
Click to collapse
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...just THINK TANKING is all
LNKNPRKFN said:
i think what Killathehnoob is trying to say is that its only the ROGERS version of the ONE X that when unlocking the BLer HTC has somehow lock the other partitions so that custom recoveries and kernels are not able to be flashed to the phone...which essentially could be the case because all they said they will "unlock" the BLer...BUT they never said they would NOT do anything else in the process. maybe its a possibillity that has been over looked...
Click to expand...
Click to collapse
I understand what you mean
I wonder if the fact that its new proprietary qualcomm chip is the reason why its being 'limited'... so we may have to rethink the whole initialization process.
we cant even get to the point that the logcat is able to start logging. So we're flying blind.
We've extended the time between loading to the soft reboot after the flash... but that doesnt tell us much.
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernel development on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX, althoug i read it again, anf maybe they are talking about more than that. I am not sure that the article is saying that there is something different with the Rogers version vs other versions, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
sk806 said:
Interesting. I think the lack is fastboot boot is what they are referring to. This would prevent custom kernels being flashed on an s-off device, but should still allow flashing of insecure stock boot images, as with the int. HOX. I am not sure that the article is saying that there is something different with the Rogers version, but it seems like there may be, and obviously with the Att version. I think I will spend a day just reading, trying to pick other devs' brains, and start fresh...thanks for the input.
Steve
Click to expand...
Click to collapse
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Here is the actual rootzwikk article
http://rootzwiki.com/news/_/articles/dear-htc-can-we-have-our-phones-back-r709
JSLEnterprises said:
The fastboot boot command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Whoa, very interesting. I was certain it did not on the Int one x.
JSLEnterprises said:
The 'fastboot boot' command works however, its how we got root in the first place.
... delegated to a Nigerian prince. Send money.
Click to expand...
Click to collapse
Just to be clear, you are not referring to fastboot flash boot, right?
Edit, nevermind, jut looked at Paul's post, it is fastboot boot. Wow.
killathenoob said:
I found the artice I read check it out
http://mobilesyrup.com/2012/05/02/i...bootloader-unlock-tool-on-one-series-devices/
Click to expand...
Click to collapse
Again thanks for this. Back to the drawing board!!!!
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
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
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....
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question