Related
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
Click to expand...
Click to collapse
wow so much information don't know where to start!!!
hard to say..someone managed to the the phone to respond to fastboot/adb by starting up ADB..
wait for the waiting for device msg, then connect the phone to usb and turn it on.
if all method fails, bring it back to claim for warranty.
edugg said:
Test methods need to unbrick my magic, so far I've tried one that I have not worked. If someone want to try things that I communicate them and I try.
After an upgrade of radio has been fried. I can not get into recovery, or fastboot. Even so I try to send commands and the command window stays and even restart <waiting for device> clicking to enter recovery fastboot or does nothing.
Excuse the translation but my English is very bad and I use the google translator
Click to expand...
Click to collapse
What OS are you using on your computer?
zeroplace said:
What OS are you using on your computer?
Click to expand...
Click to collapse
I tested with Windows 7, Vista and XP and the same.
You know any way to flash as factory?
Will it actually turn on or does it just flash a red led when you press power?
bonesy said:
Will it actually turn on or does it just flash a red led when you press power?
Click to expand...
Click to collapse
Starts, appears the splash but only gets to that point
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
bonesy said:
In that case it isnt bricked its just stuck...Bricked is when it wont turn on at all
Do you have a nandroid backup?
Have you taken the battery out and the power lead so it has no power?
i have had this problem
If you have a backup get it ready, Once you have let the phone power down totally (battery out and no lead) hold back and press power (keep holding back) this should get you into fastboot.if it doesnt unplug the lead and try again.
If thats successful.... using your nandroid files
FASTBOOT COMMANDS
fastboot erase system -w
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
Sorry if you cant get this to work i have to go out and wont be back to check till tomorrow so just giving you all the info
Click to expand...
Click to collapse
I have tried many times to do this and nothing ever stays <waiting for device> and does nothing
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
daihiep said:
Phone is not bricked, so this shouldnt be a problem.
If you cant get into fastboot with current setups, then use another recovery image and a custom rom.
(all that stuff is on SD-card.. its not that hard)
Update SDK.
Click to expand...
Click to collapse
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
The magic will hang at the first splashscreen no matter which buttons are pushed during power up. If the track ball is pressed during power on, the led lights up blue (still hanging at first splash). All other combos of buttons during power on makes no difference at all.
I have tried keeping fastboot waiting while power cycling the device (as explained in another thread), but there are no reaction. I have tried in xp, vista and linux.
I have also tried with a gold card, but since the phone seems unable to get any further than the first splash, this will not work.
So unless someone has a _NEW_ method to actually enter fastboot/ADB mode, these devices are BRICKED!
People have been discussing what the criteria for calling a phone a brick, but as far as I have care my Magic can only function as a paper weight and can therefore be called bricked.
Help
I have the same problem , the fastboot can not acces, i stay at the vodafone logo.
Any ideas?
HHHHHHHHHHHEEEEEEEEEEEELLLLLLLLLLPPPPPPPPPP.
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
Click to expand...
Click to collapse
take out the sd card, put it in a usb adaptor and copy them over.
Also search for a thread "how i unbricked my phone"
frankiboy1 said:
Great! And how should the recovery image and custom rom be put into the Magic? Sledgehammer?
The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Click to expand...
Click to collapse
Think before answering.
Btw, question answered by htcmagic.
daihiep said:
Think before answering.
Btw, question answered by htcmagic.
Click to expand...
Click to collapse
I repeat: The problem that almost everyone seems to not understand is that it's impossible to access fastboot, adb or any other (known) means.
Having a recovery image and a custom rom on the SD card is useless if you are not able to get the phone accessing those files.
I have tried the "how I unbricked my phone" method (like I wrote in my first post) without any success. If you read the whole "how I unbricked my phone" thread you can see that there are several guys that did not have success with this method.
I have done a lot of thinking.... and searching...
Thanks
http://forum.xda-developers.com/showthread.php?t=571457 try there
Wrong HBOOT = real brick
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
just curious.
superkikim said:
Guys,
With a wrong HBOOT (what happend to me), the phone is a real brick...
And they refused to repair it... I bought a new phone. But I keep the old one in case someone break his screen. Then I can get the mobo.
Click to expand...
Click to collapse
How did you brick it?
Btw, have you tried to run any RUU update?
At least singapore one.
I found a site with someone who bricked their phone but found a loop hole. I have never bricked my phone and hoping i never will but for those who have bricked their phone here are some steps to try to unbrick it! HOPE IT HELPS! SEND FEED BACK!!
So you can’t access bootloader or recovery and the only thing that works is the blue led trick when pressing trackball + power button??
Try the procedure below.
Step 1: Turned Phone off by taking out the battery.
Step 2: Prepared SD card
Put SD card in card reader and formatted it as FAT32, copied the DREAIMG.nbh onto it.
Or try Sapphimg.nbh
Step 3: Put SD card back in phone
Step 4: Hold Vol down + Power + track ball together and put battery to start phone
Step 5: Run update
IF THAT DIDNT WORK!
TRY THIS!
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.
The G1 screen will hang there for a good minute or two, but be paticiant, it will boot. Now you have a choice. Try to hack your phone again, because you're in the correct state to have another go, or, you can stick with the official Android. Now if you choose to stick with the official Android, here's what you do.
Step 1: Upgrading to Android 1.0 RC33
Download the file signed-PLAT-RC33-from-RC30.zip
Rename the file to update.zip and copy it to your SD card
Reboot your phone into recovery mode. Power off the phone first and then hold down the Home key while powering it back on.
The recovery mode is finished loading when you see the ! mark inside the triangle. Press Alt + L to display the list of options.
Press Alt + S to flash the file update.zip.
Wait for the update to apply. Your phone may reboot during this process so be patient.
Press Home + Back if prompted to reboot your phone.
Step 2: Upgrading to Android 1.5 CRB43
Download the file signed-kila-ota-148830.de6a94ca.zip
Repeat the steps from above to flash the update file.
Step 3: Upgrade to Android 1.5 CRC1
Download the file signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
Repeat the steps from above to flash the update file.
Step 4: Upgrade to Android 1.6 DRC83
Download the file signed-kila-DRC83-from-CRC1.c41b93c1.zip
Repeat the steps from above to flash the update file.
PM FOR THE DIRECT WEBSITES!
This is a tut for soft bricked devices, nice try. A brick is when your device will NOT boot into the bootloader or the recovery. Not quite sure about the top part, will test >_>
protomanez said:
More spam. This is a tut for soft bricked devices.
Click to expand...
Click to collapse
This isnt even bricked.
If yuor device is really acutally truelly bricked (no reccvery/Boot) check out the think-tank threads and the consistently updating JTAG thread.
...
protomanez said:
This is a tut for soft bricked devices, nice try. A brick is when your device will NOT boot into the bootloader or the recovery. Not quite sure about the top part, will test >_>
EDIT: Read more, ignore the above. Testing...
Click to expand...
Click to collapse
Like i said idk if it will work .. i wanted it to be tested by bricked phones.. you never know whats possible
zeezee said:
This isnt even bricked.
If yuor device is really acutally truelly bricked (no reccvery/Boot) check out the think-tank threads and the consistently updating JTAG thread.
Click to expand...
Click to collapse
Yeah, that's what I was talking about. Soft Brick is when you can get into recovery/bootloader. I've seen the JTAG thread, imo waste of time.
...
zeezee said:
This isnt even bricked.
If yuor device is really acutally truelly bricked (no reccvery/Boot) check out the think-tank threads and the consistently updating JTAG thread.
Click to expand...
Click to collapse
I'll continue to look for info on this..
kemimarie said:
I found a site with someone who bricked their phone but found a loop hole. I have never bricked my phone and hoping i never will but for those who have bricked their phone here are some steps to try to unbrick it! HOPE IT HELPS! SEND FEED BACK!!
Click to expand...
Click to collapse
Nice try. It'll surely help someone out, but the phones that are totally dead (rather than just having a borked boot, system, and/or recovery partition) won't benefit from this.
This procedure depends on a living SPL, which you simply don't have in a truly bricked device.
protomanez said:
I've seen the JTAG thread, imo waste of time.
Click to expand...
Click to collapse
Its a good thing that other people don't share your perspectives. If everybody just gave up the moment that something doesn't work *right now*, not a single human would be alive today.
The top part is talking about a brick. I have always figured there is some "ancient Chinese secret" to getting it to reload. I don't have a brick but if I did I would not ignore the possibility this could work.
I would have thought a desperate user would have tried every button combo by now though.
yeap, not a real brick
....
Ive seen a few people that lucked up and unbricked their phones .. some waited did every possible combo .. yes .. but i think somehow there is a way .. and im still looking lol
Possible hint!
Has anyone tried using adb .. Reflashing the recovery img??
if seen 2 or 3 people say they saw somewhere on the interwebz about a guy who un-bricked his device.
i have yet to see any of those people give a link or anything.
... ummm ...
havikx said:
if seen 2 or 3 people say they saw somewhere on the interwebz about a guy who un-bricked his device.
i have yet to see any of those people give a link or anything.
Click to expand...
Click to collapse
It was on here! i read it in the forums ...
look for yourself.. people on here have bricked their phone and successfully unbricked it.
..
havikx said:
if seen 2 or 3 people say they saw somewhere on the interwebz about a guy who un-bricked his device.
i have yet to see any of those people give a link or anything.
Click to expand...
Click to collapse
Idk i guess it depends on what caused the brick.. people say flashing spls and radios wrong.
...another hint..
kemimarie said:
Has anyone tried using adb .. Reflashing the recovery img??
Click to expand...
Click to collapse
run fastboot boot recovery-image.img or whatever you named your recovery image. It'll display "waiting for device..." message just keep pluging it in, unplugging, popping the battery and eventually your device will respond and boot into recovery.
Someone bricked and i did it... twice trying to flash the eng 2010 SPL. It worked the third time and my device is up and running again with an engineering SPL.
if your device is stuck on the first splash but displays in red "Fastboot USB" message in the upper left corner of the screen, DO NOT power it down. run the above mentioned command and reflash.
Found another hint
ch3w said:
confirmed...
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
Click to expand...
Click to collapse
try that on your g1/mytouch!
As already said, a brick is where you get to stare at the lovely splash1 all day. Who needs recovery or bootloader when you can see your phone's name?
protomanez said:
You made me chuckle a bit, it is quite nice isn't it?
Click to expand...
Click to collapse
I have nexus envy so I have the Nexus splash1 on right now
....
JAguirre1231 said:
As already said, a brick is where you get to stare at the lovely splash1 all day. Who needs recovery or bootloader when you can see your phone's name?
Click to expand...
Click to collapse
And as i said, people have unbricked there "dead" phone so its possbile.
kemimarie said:
And as i said, people have unbricked there "dead" phone so its possbile.
Click to expand...
Click to collapse
You've said you've read someone doing it. You did not give hard facts or evidence, you READ it. I've read many things that aren't true....
OMG I GOT BLUETOOTH WORKING IN TEH HEROZZZZ!!!!!
You read it, does that mean it is true? No, it does not.
Bootloops are some general problems while flashing incompatible contents in your phone. Sometime they lead to heart attacks for newbies and even sometime for Senior Citizens
Ok , Bootloop is the situation when you phone doesnt loads up the OS and keeps repeating the boot animation.
TIPS :
1. Always keep a stock ROM backup and current ROM backup in mmc or sdcard.
2. If you are not familiar with adb click here and set it up as fast as possible because who knows in the next boot you are going to be stuck.
3. Never pull battery, If stuck always press[ (VOL +) + (VOL -) + POWER] or connect phone to PC and start adb.
4. Always keep the FASTBOOT- OFF & USB Debugging - ON,
Settings->Power->Fastboot = OFF
Settings->Applications->Devlopment->USB Debugging=ON
Click to expand...
Click to collapse
PROCEDURE 1 : [RECOMENDED]
1. If you are stuck , never pull battery. Press [ (VOL +) + (VOL -) + POWER]
4. Connect Phone to Computer
5. Open cmd
7. Write [ adb reboot bootloader] + [VOL -], Now your phone will be in boot menu
8. While in boot menu, go to recovery(if present) and flash the previous ROM from backup
OR
Do a factory reset from boot menu(if recovery not present)
9. You are done , Now everything will be fine and You are now safe from heartattacks and paranormal activities.
Click to expand...
Click to collapse
PROCEDURE 2 :
1. If you are stuck , never pull battery. Press [ (VOL +) + (VOL -) + POWER]
2. Your phone will reboot within a gap of 5sec
3. In this time take out you battery cover(I mean only the upper battery cover shield)
4. Connect Phone to Computer
5. Open cmd
6. Write [ adb reboot recovery], if recovery installed else goto Step 7
7. Write [ adb reboot bootloader], only if recovery not installed and do a factory reset
8. While in recovery flash the previous ROM from backup
9. You are done , Now everything will be fine and You are now safe from heartattacks and paranormal activities.
Click to expand...
Click to collapse
Next time dont do anything stupid. Learn to be satisfied..
Note : If you have learnt atleast 0.01% , Support me pressing the Thanks button
Click to expand...
Click to collapse
I hope this will give you a little Knowledge. If any problem Please POST your prob.
Have FUN, Enjoy ; )
You should be recommending rebooting to bootloader (adb reboot bootloader), then powering down from there, as opposed to hard resetting and pulling the battery.
zeekiz said:
You should be recommending rebooting to bootloader (adb reboot bootloader), then powering down from there, as opposed to hard resetting and pulling the battery.
Click to expand...
Click to collapse
Tried it in my case but didnt worked, anyways thanks
when you say Always keep a stock ROM recovery and current ROM recovery in mmc. I think that you should say on the SD card? otherwise I believe that the terminology might confuse.
I also agree that you shouldn't say remove battery cover - people (especially non English speakers) may too easily confuse this for remove the battery - which isn't what you want! As recommended above adb reboot bootloader and then Power Down in case it does work for some.
Although it's probably too late by the time people read this thread, I'd also suggest that you recommend they turn off FASTBOOT and enable USB debugging (there's always the chance that they'll read this thread before the sh1t has hit the fan!).
Settings->Power->Fastboot = OFF
Settings->Applications->Devlopment->USB Development=ON
This tutorial is already there in the forum. I would recommend to search the forum before starting a new thread.
Lets keep our forum clean.
ben_pyett is right edit it accordingly in your post. And its "boot loop" not "bootloop".
ben_pyett said:
when you say Always keep a stock ROM recovery and current ROM recovery in mmc. I think that you should say on the SD card? otherwise I believe that the terminology might confuse.
I also agree that you shouldn't say remove battery cover - people (especially non English speakers) may too easily confuse this for remove the battery - which isn't what you want! As recommended above adb reboot bootloader and then Power Down in case it does work for some.
Although it's probably too late by the time people read this thread, I'd also suggest that you recommend they turn off FASTBOOT and enable USB debugging (there's always the chance that they'll read this thread before the sh1t has hit the fan!).
Settings->Power->Fastboot = OFF
Settings->Applications->Devlopment->USB Development=ON
Click to expand...
Click to collapse
Thanks for the info.. I will update it
onlyankush_s said:
This tutorial is already there in the forum. I would recommend to search the forum before starting a new thread.
Lets keep our forum clean.
ben_pyett is right edit it accordingly in your post. And its "boot loop" not "bootloop".
Click to expand...
Click to collapse
Huh I searched for this kind of thread, but didnt found anything useful
So I treied to make this guide so that anyone other than me should not be trapped in such Situation
Any ways thanks for info
Thanks for this Guide.
I like the TIPS section. It really can spare you a lot of troubles.
Q1: why to keep a Recovery image? It is not used in the described procedures.
Q2: please explain why we have to remove the battery cover (Pr.2)
Q3: what is the state of the system after Hboot Factory reset - is the ROM still there or it is necessary to flash again?
amidabuddha said:
Thanks for this Guide.
I like the TIPS section. It really can spare you a lot of troubles.
Q1: why to keep a Recovery image? It is not used in the described procedures.
Q2: please explain why we have to remove the battery cover (Pr.2)
Q3: what is the state of the system after Hboot Factory reset - is the ROM still there or it is necessary to flash again?
Click to expand...
Click to collapse
A1) I personally always keep everything loaded on my phone on the SD, including a clean nandroid backup, because you never know!
A2) ??? not sure of this either......was it so that you can possibly remove battery slightly quicker?
A3) As far as I believe Factory Reset simply formats - DATA and CACHE, returning the phone to the state that you bought it, of course assuming you have a working ROM and BOOT loaded!
ben_pyett said:
A1) I personally always keep everything loaded on my phone on the SD, including a clean nandroid backup, because you never know!
A2) ??? not sure of this either......was it so that you can possibly remove battery slightly quicker?
A3) As far as I believe Factory Reset simply formats - DATA and CACHE, returning the phone to the state that you bought it, of course assuming you have a working ROM and BOOT loaded!
Click to expand...
Click to collapse
A1) Agree, maybe he added it lately but it's used
A2) Also don't know, but you could be on the right track, I unfortunatly done this before cause I forgot wiping before flashing and the rom i used startet an reboot script after flashing, also fastboot where enabled by default and no pc in sight^^ So I pulled off the cover restartet with vol+ vol- power und pulled the battery within the small delay of shutdown and boot^^
A3) Agree, factory reset within the bootloader does the same as factory reset within the recovery
OK Thanks. Q2 and Q3 are clear now
A1) then it has to be written "Recovery BACKUP " not a "Recovery" (recovery.img) because this is double meaning and a bit confusing
blindndumb said:
1. Always keep a stock ROM recovery and current ROM recovery in mmc or sdcard.
Click to expand...
Click to collapse
Did you mean this?
Cause I can't find the words recovery image, sry^^
But anyway your right, backup would be much clearer then recovery.
Tectas said:
Did you mean this?
Cause I can't find the words recovery image, sry^^
But anyway your right, backup would be much clearer then recovery.
Click to expand...
Click to collapse
Yes my bad. Edited the previous post. But since most of us here are not a native English speakers it is good to be specific.
amidabuddha said:
OK Thanks. Q2 and Q3 are clear now
A1) then it has to be written "Recovery BACKUP " not a "Recovery" (recovery.img) because this is double meaning and a bit confusing
Click to expand...
Click to collapse
Changed to backup instead of recovery
My mistake , actually as soon as I got out of boot loop , i wrote the guide in no time
Anyways , Can you list all my mistakes instead of pointing one at a time
blindndumb said:
Anyways , Can you list all my mistakes instead of pointing one at a time
Click to expand...
Click to collapse
Take it easy your guide is great
blindndumb said:
Tried it in my case but didnt worked, anyways thanks
Click to expand...
Click to collapse
Considering you would so easily rip out the battery I doubt you have any patience, but everytime I have been caught in a bootloop I have reset using vol up down power, waited for the phone to appear in device manager, then executed adv reboot bootloader, everytime without fail.
Sent from my HTC Desire S using xda premium
zeekiz said:
Considering you would so easily rip out the battery I doubt you have any patience, but everytime I have been caught in a bootloop I have reset using vol up down power, waited for the phone to appear in device manager, then executed adv reboot bootloader, everytime without fail.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
May be I have done something wrong but as far as I know in my case after boot loop I pressed Vol+ , Vol- and power then phone automatic restarted. I checked adb but no luck
next time did the same as you mentioned but error: device not found
So I took out upper battery cover and then orange light flashed up, my device was detected and adb helped rebooting into recovery
Then i flashed htc kernel as boot loop met due to flashing hyperion kernel
Minutes ago I "bricked" my phone again by downgrading the Radio. Hboot Factory reset sucks.
I managed to fix with Solution No.2 im my Guide
Ok, I think I've buggered my DS. Did s-off then root then installed cyanogen stable 7.
Now it's just looping, I didn't make a back up (NOOB), am I screwed?
Thanks.
fatfingers73 said:
Ok, I think I've buggered my DS. Did s-off then root then installed cyanogen stable 7.
Now it's just looping, I didn't make a back up (NOOB), am I screwed?
Thanks.
Click to expand...
Click to collapse
Have you tried holding Volume down in an attempt to get into recovery? if not then power off, hold in volume down and then power on.
sounds like you missed wiping cache or dalvik cache post/pre install.
I'm having a few problems with my Desire S at the moment, I can't seem to find a working fix for it :/
It all started about 2 days ago, when my phone froze in a bootloop. I removed the battery, put it back in and turned it on. All it does now is stay on the white HTC screen. I went into Clockwork Recovery to try and sort it out, only to see E:Can't open /cache/recovery/log.
I've tried some of the suggestions in another thread to sort this, but none of them seem to work - I can't access ADB shell because I can't change it to USB Debugging so I can fix it.
Does anyone have another fix for this or is my eMMC chip truly fried?
MehLon said:
I'm having a few problems with my Desire S at the moment, I can't seem to find a working fix for it :/
It all started about 2 days ago, when my phone froze in a bootloop. I removed the battery, put it back in and turned it on. All it does now is stay on the white HTC screen. I went into Clockwork Recovery to try and sort it out, only to see E:Can't open /cache/recovery/log.
I've tried some of the suggestions in another thread to sort this, but none of them seem to work - I can't access ADB shell because I can't change it to USB Debugging so I can fix it.
Does anyone have another fix for this or is my eMMC chip truly fried?
Click to expand...
Click to collapse
Have you gone into CWM and formatted the CACHE partition? what happened?
ben_pyett said:
Have you gone into CWM and formatted the CACHE partition? what happened?
Click to expand...
Click to collapse
Within cwm should it be possible to access your device with adb.
If wiping cache doesn't solve your issue try a factory reset or/and newly flash your ROM, a restoration of a backup would also be an option.
Swyped from my Desire S
Tried that, "Error formatting /cache!"
Next option is the instal a ruu, this performs a fresh build of you're partitions and should solve the issue.
Swyped from my Desire S
Do you have a link to the RUU?
Not only to one^^
http://forum.xda-developers.com/showthread.php?t=1002506
Swyped from my Desire S
OK, trying to run it but it won't find the phone - what do I need to mount in CWM?
Instal HTC sync to be sure that the drivers are installed, after this uninstall it, the drivers will still stay on your system.
Run the ruu and follow the instructions
Swyped from my Desire S
Installed/uninstalled HTC Sync, but it still won't find my phone Do I have to mount /data or /system or just put it on USB storage?
Run the ruu with unplugged phone don't close it, look into your temp folder, there must be an rom.zip.
Copy it to another folder.
Close the ruu.
Rename it to pg88img.zip.
Copy it to the root of your sd.
Reboot into bootloader and let it flash.
Within the rom zip you could delete hboot-xxxxx.img, boot-signed.img and recovery.img, cause these you got, but you don't have to.
Before trying the above solution. Check solution 4 in the guide "Read before going for a replacement of eMMC in my signature it might work for you (no need of USB debugging enabled).
Sry, everytime I forget about fastboot when it comes to ruu, thanks for the hint
Sorry if I'm being a complete and utter idiot, but I don't actually know where to find the temp folder :/ Can you tell me where it is?
MehLon said:
Sorry if I'm being a complete and utter idiot, but I don't actually know where to find the temp folder :/ Can you tell me where it is?
Click to expand...
Click to collapse
just do a search for rom.zip which should locate it for you.
MehLon said:
Sorry if I'm being a complete and utter idiot, but I don't actually know where to find the temp folder :/ Can you tell me where it is?
Click to expand...
Click to collapse
Before going to rom.zip solution try the others in the mentioned above guide.
amidabuddha said:
Before going to rom.zip solution try the others in the mentioned above guide.
Click to expand...
Click to collapse
+1
What he said!
Before trying the above solution. Check solution 4 in the guide "Read before going for a replacement of eMMC in my signature it might work for you (no need of USB debugging enabled).
Click to expand...
Click to collapse
Tried that 2 or 3 times, just freezes the Fastboot when I try it
just do a search for rom.zip which should locate it for you.
Click to expand...
Click to collapse
Also tried that, doesn't show up any results
MehLon said:
Tried that 2 or 3 times, just freezes the Fastboot when I try it
Click to expand...
Click to collapse
? please describe the steps. How it freezes fastboot?
I plugged my phone in, put it into Fastboot and launched the RUU on my PC. It kept trying to reboot to the bootloader, but it wasn't doing anything - I tried using the volume keys but they were not working.
Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk
imk79 said:
Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk
Click to expand...
Click to collapse
When you plug it into your USB cable do you have the charging light?
Also that rom is for the Tegra One X not the Dual Core Adreno One X, i've done this before and if im still right you can get into download mode you can go back to stock.
MrKickstand said:
When you plug it into your USB cable do you have the charging light?
Click to expand...
Click to collapse
No nothing is happen. Phone is giving no response
imk79 said:
No nothing is happen. Phone is giving no response
Click to expand...
Click to collapse
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.
MrKickstand said:
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.
Click to expand...
Click to collapse
When I connect the device nothing happened and device showed like in the attached screenshot.
imk79 said:
When I connect the device nothing happened and device showed like in the attached screenshot.
Click to expand...
Click to collapse
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into bootloader mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into bootloader mode.
MrKickstand said:
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into download mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into download mode.
Click to expand...
Click to collapse
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen
imk79 said:
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen
Click to expand...
Click to collapse
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)
MrKickstand said:
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)
Click to expand...
Click to collapse
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?
imk79 said:
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?
Click to expand...
Click to collapse
Here ya go.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
MrKickstand said:
Ok, im pretty sure you can recover from that,
Click to expand...
Click to collapse
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.
redpoint73 said:
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.
Click to expand...
Click to collapse
Thanks for the info
Any other solution rather then Jtag ?
imk79 said:
Any other solution rather then Jtag ?
Click to expand...
Click to collapse
If you originally rooted (or later RUUed) to 2.20 firmware or later, than no. If you were on 1.85 or 1.73 firmware, you can try the unbricking thread and/or JET tool. Unbricking thread is linked in the ICJ "warning" thread I posted above. JET tool can be found in the Development forum.