Related
Is anyone manage to brick the phone already?
How likely/ or stupidity you need to actually bricking the phone?
What is a NO NO and how to avoid it?
That's the question.. thanks!
Main thing is read as much as you can before you do any changes, it helps to check what few sites say.
When I rooted my phone I could not get it to run the update part, tried time and time again, one site said "rename the file to update.zip and paste it" then I read on another site to just call it update as it is already a zip file.....and then it worked, small bit of detail like that stopped it working to start with so if I was you I check a few sites and get all the info you need, but also as many would say if you are that unsure dont take the risk and wait for samsung updates with Kies.
voodoochild2008 said:
if you are that unsure dont take the risk and wait for samsung updates with Kies.
Click to expand...
Click to collapse
Kies actually failed to update my phone, I have the Korean Galaxy S SHW-M100S, and it showed an update was available. So, I thought I was bricked for about 30 mins, kept trying to get it to work itself out of the problem in recovery mode, after about 4 tries (1 reboot of Windows, plus changing USB ports and 2nd try with this static new config) eventually it did, thank God.
Do not remove usb while in the middle of flashing with odin
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
madjsp said:
I was gonna say something along the lines of a smart ass, but I can't. That sucks.
why would you do a battery pull?
Click to expand...
Click to collapse
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
delete. ......
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
andrewluecke said:
I've removed the cable half way and rebooted, and it was fine..
You simply remove the USB cable, battery again, put the battery in, and you'll be able to get to downloader mode.
The phone seems to have a component that ODIN doesn't touch that is read-only that handles download mode. Most hardware devices tend to have safeguards. I haven't confirmed this, but I've noticed the same applies to NAS devices (which tend to have a special redboot which uses tftp).
I have still yet to have seen any evidence of anyone permanently bricking their phone, but I've seen a few cases of "oops, got it working again".
Remember, Samsung are eager to reduce their support costs, and failsafe's are cheap and easy to add.
Click to expand...
Click to collapse
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
amerikian said:
Wanna know HOT TO BRICK YOUR PHONE? Right when ODIN start flashing, pull the battery on your phone and see what happens.
I can't even boot up!
****
Click to expand...
Click to collapse
Similar happened to me,although I didnt pull the battery, the phone just disconnected halfway through the flash.
Had half hour of panic,where I thought it was bricked.
Had to do a few battery pulls,restart PC a couple of times and mess around with different USB ports,but finally got it working.
Have flashed a 3 times since without a problem.
chluk2425 said:
I thought in the Big FAQ, it said... do not disconnect the usb-cable but to remove the battery if want to interrupt it...
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
Click to expand...
Click to collapse
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
zenkinz said:
yes, the odin doesn't touch the 'bootloader' , or the small piece of code that enable the download mode, so there's no way you can brick the phone.
I have tried to repartition the phone while flashing firmware that has nothing except the csc data (i.e. no kernel, no factory rfs, etc) and the flash procedure went succesfully but in actual fact, my phone contains a new set of partitions that contain nothing except the small csc data.
and i still able to reflash, although I must make sure that the phone is totally shutdown (i.e. take out battery, let it stay for awhile before putting back)
Click to expand...
Click to collapse
Are you sure that flashing (through ODIN) in any case never touch that "Download Mode" piece of code ? Even you select all the options in ODIN ?
Can anyone confirm this ? Actually I want to play with Kernel and RFS (have some ideas to try) but afraid of full bricking. So if this download mode is always present then I can play with it without any problem.
Waiting for response.
amerikian said:
I've been flashing all night and wanted to do it "right" this time....realized my SIM and SD card were still in there mid-flash so wanted to pull them and start clean..........................
Yeah....don't do that.
Guess I'll be that "guy" paying a visit to the local AT&T shop tomorrow....
Luckily I'm w/in my 14 days since getting it....
Click to expand...
Click to collapse
Believe me! you can still access the download menu
The bootloader is almost always writeprotected and cannot be overwritten. You would probably have to connect a cable to some internal port like Jtag to be able to reflash the bootloader section. Atleast that is the case in 99% of all bootloaders. Im very certain that you cannot cripple the bootloader.
Sent from my GT-I9000 using XDA App
jackiechan8 said:
That means you shouldn't do any of those things! So don't disconnect usb, don't remove the battery and don't interrupt the process.
Click to expand...
Click to collapse
gosh man, thanks correcting me but if that's the case, what should i do if it doesn't reboot by itself?
take out the battery, wait for 30 to 60 secs, put the battery in and start phone with vol down + menu + power
Don't disconnect the usb or do anything else while flashing!!!
I removed the usb cable when it started flashing (i thinked it was stuck, happens sometimes), and since it does not boot anymore. I press the power button, volUp + home + power, volDown + home + power... nothing happens.... it's dead, doesn't turn on at all...
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
jodue said:
after all i have read i think it's almost impossible to brick the sgs since you always get back into download-mode. the only case i read where i believe that it's a goner is flashing with the wrong (in this case the at&t) odin version. those guy's just got a white sreen with at&t logo at boot. they didn't get into download mode any more because the button mapping on the captivate is different ... so thats really bad luck, dont't try that at home
Click to expand...
Click to collapse
well, mine doesn't boot at all, and i flashed (technically not, because i removed the usb cable at the very start) with the RIGHT odin version
Maybe if it fails when flashig sbl (secondary boot loader ) you can't go into download/recovery mode...
Here's my 4 hour journey...
I tried rooting my Evo using AutoRoot v2.4 (http://forum.xda-developers.com/showthread.php?t=838448 I would post there but I don't have permissions, plus my problem seems more general at this point anyway). I followed all of the instructions (I'm running Android 2.2 with 3.70.651.1). At first, it was telling me that it was unable to root. After trying a couple things (such as killing all running processes), I used an RUU of 3.70.651.1 (http://www.multiupload.com/W679R1W391). I ran AutoRoot again, and this time it told me Root was successful and took me to the bootloader screen. As it did this, the AutoRoot DOS window just disappeared. I rebooted and tried a few more times, same result.
Here's where I'm not quite sure what I did. I think the next thing was I went into Recovery from bootloader, didn't really know what I was doing, and did a battery pull. Then I tried to factory reset by going bootloader -> clear storage. When I went to try and run AutoRoot again, my computer wasn't recognizing my Evo (I guess restoring the Evo caused it to lose the drivers?). When I plugged it in, it briefly searched for several "Qualcomm CDMA Technologies MSM" drivers (weird, never saw it look for those before when I plugged in my Evo?), asked me if I had a disk that came with the hardware, and when I said no it told me it couldn't find the drivers.
So basically my computer doesn't seem to recognize my Evo anymore even though it seems to be at its factory original stock settings. To top it off, it now seems to be stuck in a continuous reboot cycle every couple minutes or so (the worst that's ever happened to me before was semi-random restarts, maybe a couple times per week). I tried doing a factory reset by doing bootloader -> recovery -> menu -> factory reset but that didn't do anything. And I don't think it's charging anymore, considering that the battery is slowly getting lower and lower even though the orange light goes on when it's plugged in (though maybe it's just losing more battery than its gaining through all this restarting). At this point all I want is to get out of this continuous reboot cycle that I've spent the last couple hours trying to look for solutions for, with no luck. Much less re-customize my phone to how it was pre-restore and much less actually get through rooting it... Any help?
First re-run your RUU.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install ; download the modified hboot drivers
http://unrevoked.com/recovery/ ; download unrevoked
Make sure to have installed, then uninstall htc sync on your computer, and that usb debugging is enabled on your phone. Then run unrevoked and you should be good to go.
"First re-run your RUU."
But my PC isn't recognizing my Evo, I guess because something is wrong with the drivers? I tried running the RUU and it said Error [170]: USB Connection Error.
Caperi said:
"First re-run your RUU."
But my PC isn't recognizing my Evo, I guess because something is wrong with the drivers? I tried running the RUU and it said Error [170]: USB Connection Error.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip
A 3.70 ruu in PC36IMG form. Re-name to PC36IMG, then place on your sdcard, then boot into the bootloader, and apply the update and reboot.
teh roxxorz said:
[link]
A 3.70 ruu in PC36IMG form. Re-name to PC36IMG, then place on your sdcard, then boot into the bootloader, and apply the update and reboot.
Click to expand...
Click to collapse
How should I access my sdcard, since my PC isn't recognizing my phone?
I could probably do it via another phone, but I won't have access to that until tomorrow; is that the only way?
Edit: Oh boy. Just tried typing your link in on my phone, and apparently the phone doesn't recognize its sdcard... Might be why my PC isn't seeing my phone?
Well, you can take the battery out, remove the sdcard, the mount it to your computer via micro usb adapater.
teh roxxorz said:
Well, you can take the battery out, remove the sdcard, the mount it to your computer via micro usb adapater.
Click to expand...
Click to collapse
Don't have one of those, but even if I did (or got the files on there via another phone), wouldn't the fact that it won't recognize the sdcard be a problem when trying to get it to apply the update?
The battery is starting to get really low (about 10%), I think it's not recognizing the charger
Caperi said:
Don't have one of those, but even if I did (or got the files on there via another phone), wouldn't the fact that it won't recognize the sdcard be a problem when trying to get it to apply the update?
The battery is starting to get really low (about 10%), I think it's not recognizing the charger
Click to expand...
Click to collapse
Then what you could do is copy the files on the sdcard to the pc, then re-format it from there, then place the files on it, and stick it on the charger asap.
This link to recover sd card and usb:
http://forum.xda-developers.com/showthread.php?t=695243
Then let charge, use external wall charger if needed. If you have to buy one, its like 5 or 10 bucks and its better then having to buy a whole new phone.
Then, download the PC36IMG.zip (RUU in zip form), place on root of sd card, boot into bootloader, let it scan, when it asks if you want to run the update, say yes. Bada bing bada boom, your up and running. Then go download Unrevoked, its easier if your not completely sure what your doing, plus it has a nice and pretty UI that you cant possibly screw up and 5 minutes later your completely rooted, simple as that.
RileyGrant said:
This link to recover sd card and usb:
http://forum.xda-developers.com/showthread.php?t=695243
Then let charge, use external wall charger if needed. If you have to buy one, its like 5 or 10 bucks and its better then having to buy a whole new phone.
Then, download the PC36IMG.zip (RUU in zip form), place on root of sd card, boot into bootloader, let it scan, when it asks if you want to run the update, say yes. Bada bing bada boom, your up and running. Then go download Unrevoked, its easier if your not completely sure what your doing, plus it has a nice and pretty UI that you cant possibly screw up and 5 minutes later your completely rooted, simple as that.
Click to expand...
Click to collapse
Pardon me if I'm misunderstanding, but what I'm seeing from your post is that to fix the sd card issue I need to fix the usb issue, to fix the usb issue i need to get root, and to get root i need to fix the sd card issue? Haha, yeah I lost you somewhere along the way...
@teh roxxorz - You're saying that the sd card issue should be fixed if I reformat the SD card on my PC? If so, that's what I'm going to try tomorrow when I have that other phone I can use.
That should fix your issue.
So I reformatted the sdcard on my PC, got the PC36IMG.zip on there, ran it via bootloader, and it worked. But, I'm still stuck in the continuous reboot cycle, can't connect my phone to the PC, and in the brief moments it stays on, it won't recognize the sdcard...
On the bright side, it successfully charged overnight, so that's not going to be a problem.
I'm hesitant to try rooting (if that's even possible at this point) to fix the problem while it's in this state in case I have to take it back to Sprint, unless there's a reason that should fix the problem? It seems pretty hopeless right now...
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
plainjane said:
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
Click to expand...
Click to collapse
+1.
If its acting wacky before root, rooting it wont fix it. I would take it back to Sprint, for sure.
Sent from my PC36100 using XDA App
It sounds like you put your phone in diagnostic mode, when turning it on Volume Down takes it to the bootloader while Volume Up does Diag Mode. Check to see whether or not your phone shows S-OFF in the bootloader, if so you'll want to run the FlashZip script and select the Sprint Lovers file.
However, if your computer is still having trouble recognizing your phone let it sit for two minutes without the battery. If that still does not fix it use Volume Up and power one more time to try and take it out of that. I would also recommend against running Unrevoked if your phone is in Diag mode, it is very easy to permanently mess something up with it in that state.
edit: If you need to charge it more just turn the phone off and it should charge fine.
Problem I'm seeing is that u used auto root. I've seen nothing but thread after thread of problems with it. I've always used unrevoked3 and I've rooted many different phones including...2 heros, 2 evos, an Eris, a Droid, a Droid 2, and a Droid incredible. Never once did it fail or give me any issues. Simply follow the instructions and even watch the video on their site. If I where u I'd just ruu ur phone and start all over.
xHausx said:
It sounds like you put your phone in diagnostic mode, when turning it on Volume Down takes it to the bootloader while Volume Up does Diag Mode. Check to see whether or not your phone shows S-OFF in the bootloader, if so you'll want to run the FlashZip script and select the Sprint Lovers file.
However, if your computer is still having trouble recognizing your phone let it sit for two minutes without the battery. If that still does not fix it use Volume Up and power one more time to try and take it out of that. I would also recommend against running Unrevoked if your phone is in Diag mode, it is very easy to permanently mess something up with it in that state.
edit: If you need to charge it more just turn the phone off and it should charge fine.
Click to expand...
Click to collapse
My phone has always been S-ON throughout this.
I did try leaving it off and without battery for extended periods of time - no dice.
How could I tell if it's in diagnostic mode and what does diagnotistic mode do?
plainjane said:
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
Click to expand...
Click to collapse
k2buckley said:
+1.
If its acting wacky before root, rooting it wont fix it. I would take it back to Sprint, for sure.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So I took it to Sprint, they spent a couple hours on it, placed an order for a new one, and gave me this one back saying it was dead and unfixable (I think all they did was a hard reset). When they gave it to me, it was on, and remained on without restarting for like 30 mins (I thought they had fixed it without realizing it). Just now, I turned it off and on again, and the reboot cycle started again... Any reason why it may have been working that one time? I'll probably just wait for the replacement, but just curious as to why it may have worked.
@Papa_Smurf - Yeah I tried to RUU it but that didn't fix any of the problems
I think it may have just been playing possum. Is it still doing it?
Yeah now it's in the reboot cycle again. Maybe if I was to let it run through the cycle long enough it might eventually stop until I manually powered down and on again (I'm guessing that's what had happened when I got it back from Sprint).
Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.
I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.
Try reinstall usb drivers, rsdlite, different usb port, and different pc.
@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.
If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.
im having the same issue, did you solve it?
im having the same issue, did you solve it?
try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...
You have tried the McGyver-trick?
I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.
Ok. At least you have the time now to enjoy your sunny weather in Brazil...
RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help
First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx
Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again
i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan
hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Check battery pins
hedeon said:
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Click to expand...
Click to collapse
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
whiperhack said:
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
Click to expand...
Click to collapse
That was my first idea too but, no m8, battery is placed ok....
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
if4ct0r said:
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
Click to expand...
Click to collapse
Tried that too, still dead
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
I understand I should not be worried that all of these RUU's are listed as for model: ACE?
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
if4ct0r said:
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
Click to expand...
Click to collapse
OMG! I was previously looking for stock roms and everytime I ended up on that site from your link I was annoyed that someone is giving a wrong link to roms for wrong phone. Silly me!
I am downloading right now.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
No it says phone not connected (error[170])
hedeon said:
No it says phone not connected (error[170])
Click to expand...
Click to collapse
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
when you connected it to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then sorry to say, its bricked.
The only way to recover it now is via jtagging or replacing the mainboard (which generally is what they do when you send it in for warranty repair)
whiperhack said:
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
Click to expand...
Click to collapse
Yes, I thought about it as phone behave like it has no power at all. But this is not the case, as I have been flipping that and another battery in every possible position. And I know which one is correct as I can see where pins are in battery pocket. I left it alone under charging and other time with no battery at all hoping that will hard reset phone. No effect at all .
JSLEnterprises said:
when connected to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then its bricked, sorry to say
Click to expand...
Click to collapse
I had drivers previously installed. But I am not entirely sure are we talking about same thing as I don't know what QLOAD is. Anyway comp doesn't see any recognised or unrecognised device that could be my phone...
I am not worrying about damn phone as if it is hard bricked tech guys in service will not probably spot that it was rooted. So they will replace, or if not I will go to insurance company. Problem is it takes to much time, I wont make it b4 Christmas.
Thank you guys,
anyone has some other ideas? Please...
desperation bump
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
if4ct0r said:
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
Click to expand...
Click to collapse
Sigh... I got "waiting for device" forever in CMD... As you said, it's dead. Gonna send it to HTC in Monday...
Thank you all, appreciate your time
Hello hedeon,
I have the same experience today, as you state in the first post in this thread.
Did you, and how solve the problem?
Is there people with the same problem? This morning I receive notification about system update for my HTC Desire HD. The rest is exactly same problem from the top of this story = death + death + death.....
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
GuyInTheCorner said:
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
May be, but updating started with downloading, then resetting, and then green line was growing up to 1/3 of total size, and at that size stay more then 20 min. Then I try to to push every button, and every combination of buttons, and after 10 minutes more I had pull battery out.
Was it too impatient ?
What was the Android version before you rooted if you can remember and which tool did you use to root?
From what you wrote earlier, it asked you for a 2.3 update which means you probably flashed a Froyo RUU as stock, to bring the phone back to stock ofc.
However, if your DHD came with stock Gingerbread, flashing a Froyo RUU will most definitely screw the phone. I'm not sure if it's beyond repair atm or not, but if that was the case, even if you didn't mess with the battery, chances are the phone would never boot anyway.
Look into AAHK thread, I think there is a good how to there.
I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.
edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~