First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is*actually*bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article). For those other problems, you have a few options.
If Your Phone Keeps Rebooting: Wipe Your Data and Cache

If you've flashed a ROM and your phone won't boot into the home screen, it's probably because you forgot to wipe your data and/or cache. It's trying to boot into the ROM, but some leftover data from your last ROM is causing it to error out, and it'll reboot itself over and over again. If your phone's eating a big bowl of boot loops, your first course of action should be to wipe its data and cache, which you can do from recovery mode. This method assumes you're using ClockworkMod Recovery, like the majority of Android users, but if your particular phone uses a different third-party recovery (like AmonRA), you should still be able to find these options in the interface. They might just be in a different place. To wipe your data and cache:
Power down your phone. Turn it back on and boot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to Advanced, and choose "Wipe Dalvik Cache". When that's finished, go back to the main screen and choose "Wipe Cache Partition". Lastly, head to "Wipe Data/Factory Reset". This will delete all your settings and apps, but you should still be using the correct ROM.Reboot your phone.
With any luck, it should boot right into your ROM. If that didn't work, try the below method with the same ROM (or with a different ROM) and see if you get different results.
If Your Phone Boots Straight Into Recovery: Flash a New ROM

If, when you boot up your phone, it goes straight into ClockworkMod, then there's likely an issue with the ROM you flashed. Note that some ROMs boot into recovery mode automatically after flashing, so reboot your phone once from recovery mode to make sure you're having a problem. HTC users: if you boot up your phone, it might go straight into the bootloader—check to see whether you can choose "Recovery" from the list before continuing to the next step. HTC phones usually don't boot straight into recovery.
In this case, you'll want to reflash the ROM from scratch. Try again with the ROM that messed up your phone, if you so choose, but if that doesn't work, try an entirely different ROM. The best way to do this is to download a ROM from somewhere on the net and putting it on your*SD card. You'll need to take the SD card out of your phone, and you'll need an SD card reader that you can plug into your computer. Here's how it works:
Plug the SD card into your computer. Drag the ROM's ZIP file to your SD card, and wait for it to copy.When it's done copying, eject the SD card and put it back in your phone. Reboot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to "Install ZIP From SD Card" and navigate to the ZIP file you just copied over. Give it time to flash the ROM.When it's done, reboot your phone.
Hopefully, your phone should successfully boot into the new ROM. From there, you can probably assume that the previous ROM that messed up your phone isn't going to work, and you'll have to find another ROM for now—or find another copy of that ROM that isn't corrupted. Remember to make backups of your working ROMs so you don't lose all your data!
If Your Phone Boots Straight Into its Bootloader: Restore From a Stock ROM
If you're really having trouble, one of the most surefire ways to get your phone working again is to restore from the original ROM your phone came with—unrooted, stock, stable goodness. Each manufacturer and phone has a different method for doing this, and we can't go into too much detail here, but we can steer you in the right direction.
Note that this will unroot your phone, and return it to exactly how it was when you bought it from the store. You'll lose all your apps, settings, ClockworkMod recovery, you'll get over-the-air updates again, and you'll even have to re-activate your phone if you're on a CDMA provider like Verizon or Sprint.
This is less likely, but it's a problem I and a few others have run into on occasion: sometimes your SD card just gets corrupted, which makes the above methods useless (since they rely on your SD card to work). Take your SD card out of your phone, put it into your computer using an SD card reader, and format it. It's very important that you format it through an SD card reader directly and not by plugging in your phone in USB mode—I learned this the hard way. Format it as FAT32 and try the above methods again.
Other errors, like during the ROM flashing process, might give you a hint as to what's wrong. Try heading to the*XDA Developers forums*and asking for help, as your phone could have one of a million specific problems we can't address here today. Remember, if your phone turns on, there's still a good chance you can recover from whatever error you're experiencing, so don't give up just yet!
If Your Phone Is Truly Bricked: Take It Into the Store and Play Dumb
If your phone is actually bricked—that is, it won't turn on at all, no matter how hard you try—it's time to give up and move on. The first thing you can do in this situation is try to take it back to your carrier's store and play dumb—just say something like "I don't know what happened, but my phone won't turn on anymore" (don't tell them you rooted it, obviously). Most carriers don't have time to deal with such issues and they'll just give you a new phone. Sure, it's a tad evil, but it should work most of the time.
If they're wise to your act, though, you can try another store or just sell your bricked phone for a few bucks on Craigslist. Sadly, if no one will replace your phone, you'll have to buy an entirely new one. Such are the dangers of rooting, but don't be discouraged! Bricking your phone is pretty rare, so I wouldn't worry about it being a common occurrence. As always, though, when you void your warranty, only do so if you're ready to replace that device completely, since you never know what can happen.
Sincerely,
Clowntown Developers
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
you can simply say hard brick and soft brick bro
i think you a thanx collector,all threads are known looooong time,so please help other user with usefull potsts
-CALIBAN666- said:
i think you a thanx collector,all threads are known looooong time,so please help other user with usefull potsts
Click to expand...
Click to collapse
Isn't this useful?
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
sangalaxy said:
you can simply say hard brick and soft brick bro
Click to expand...
Click to collapse
Yes we can, but this one is in detail.
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Clowntowndevs said:
Isn't this useful?
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Click to expand...
Click to collapse
yeah but it is posted already in the newbie guides and all
sangalaxy said:
yeah but it is posted already in the newbie guides and all
Click to expand...
Click to collapse
I am new, I did not know it.
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Clowntowndevs said:
First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is*actually*bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article). For those other problems, you have a few options.
If Your Phone Keeps Rebooting: Wipe Your Data and Cache

If you've flashed a ROM and your phone won't boot into the home screen, it's probably because you forgot to wipe your data and/or cache. It's trying to boot into the ROM, but some leftover data from your last ROM is causing it to error out, and it'll reboot itself over and over again. If your phone's eating a big bowl of boot loops, your first course of action should be to wipe its data and cache, which you can do from recovery mode. This method assumes you're using ClockworkMod Recovery, like the majority of Android users, but if your particular phone uses a different third-party recovery (like AmonRA), you should still be able to find these options in the interface. They might just be in a different place. To wipe your data and cache:
Power down your phone. Turn it back on and boot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to Advanced, and choose "Wipe Dalvik Cache". When that's finished, go back to the main screen and choose "Wipe Cache Partition". Lastly, head to "Wipe Data/Factory Reset". This will delete all your settings and apps, but you should still be using the correct ROM.Reboot your phone.
With any luck, it should boot right into your ROM. If that didn't work, try the below method with the same ROM (or with a different ROM) and see if you get different results.
If Your Phone Boots Straight Into Recovery: Flash a New ROM

If, when you boot up your phone, it goes straight into ClockworkMod, then there's likely an issue with the ROM you flashed. Note that some ROMs boot into recovery mode automatically after flashing, so reboot your phone once from recovery mode to make sure you're having a problem. HTC users: if you boot up your phone, it might go straight into the bootloader—check to see whether you can choose "Recovery" from the list before continuing to the next step. HTC phones usually don't boot straight into recovery.
In this case, you'll want to reflash the ROM from scratch. Try again with the ROM that messed up your phone, if you so choose, but if that doesn't work, try an entirely different ROM. The best way to do this is to download a ROM from somewhere on the net and putting it on your*SD card. You'll need to take the SD card out of your phone, and you'll need an SD card reader that you can plug into your computer. Here's how it works:
Plug the SD card into your computer. Drag the ROM's ZIP file to your SD card, and wait for it to copy.When it's done copying, eject the SD card and put it back in your phone. Reboot into Recovery mode. This is a bit different for every phone, so you'll have to Google how to do it for your specific model. Usually it involves holding down another button, like Volume Down, as you turn your phone on. HTC phones will have to then select "Recovery" from a menu, while other phones will boot directly into ClockworkMod. You'll know you're in ClockworkMod by the words "ClockworkMod Recovery" at the top of the screen.Use your volume keys to navigate the menus, and your power button to select menu items. Scroll down to "Install ZIP From SD Card" and navigate to the ZIP file you just copied over. Give it time to flash the ROM.When it's done, reboot your phone.
Hopefully, your phone should successfully boot into the new ROM. From there, you can probably assume that the previous ROM that messed up your phone isn't going to work, and you'll have to find another ROM for now—or find another copy of that ROM that isn't corrupted. Remember to make backups of your working ROMs so you don't lose all your data!
If Your Phone Boots Straight Into its Bootloader: Restore From a Stock ROM
If you're really having trouble, one of the most surefire ways to get your phone working again is to restore from the original ROM your phone came with—unrooted, stock, stable goodness. Each manufacturer and phone has a different method for doing this, and we can't go into too much detail here, but we can steer you in the right direction.
Note that this will unroot your phone, and return it to exactly how it was when you bought it from the store. You'll lose all your apps, settings, ClockworkMod recovery, you'll get over-the-air updates again, and you'll even have to re-activate your phone if you're on a CDMA provider like Verizon or Sprint.
This is less likely, but it's a problem I and a few others have run into on occasion: sometimes your SD card just gets corrupted, which makes the above methods useless (since they rely on your SD card to work). Take your SD card out of your phone, put it into your computer using an SD card reader, and format it. It's very important that you format it through an SD card reader directly and not by plugging in your phone in USB mode—I learned this the hard way. Format it as FAT32 and try the above methods again.
Other errors, like during the ROM flashing process, might give you a hint as to what's wrong. Try heading to the*XDA Developers forums*and asking for help, as your phone could have one of a million specific problems we can't address here today. Remember, if your phone turns on, there's still a good chance you can recover from whatever error you're experiencing, so don't give up just yet!
If Your Phone Is Truly Bricked: Take It Into the Store and Play Dumb
If your phone is actually bricked—that is, it won't turn on at all, no matter how hard you try—it's time to give up and move on. The first thing you can do in this situation is try to take it back to your carrier's store and play dumb—just say something like "I don't know what happened, but my phone won't turn on anymore" (don't tell them you rooted it, obviously). Most carriers don't have time to deal with such issues and they'll just give you a new phone. Sure, it's a tad evil, but it should work most of the time.
If they're wise to your act, though, you can try another store or just sell your bricked phone for a few bucks on Craigslist. Sadly, if no one will replace your phone, you'll have to buy an entirely new one. Such are the dangers of rooting, but don't be discouraged! Bricking your phone is pretty rare, so I wouldn't worry about it being a common occurrence. As always, though, when you void your warranty, only do so if you're ready to replace that device completely, since you never know what can happen.
Sincerely,
Clowntown Developers
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Click to expand...
Click to collapse
Ain't nobody got that much time to read
Sent from my GT-S5360
Read/Search before posting........
And correct the thread's title
Sent from my GT-I9300
fifa2151 said:
Ain't nobody got that much time to read
Sent from my GT-S5360
Click to expand...
Click to collapse
Depends, if someone wanna know, he may read it.
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
D4rkSh4dow said:
Read/Search before posting........
And correct the thread's title
Sent from my GT-I9300
Click to expand...
Click to collapse
I dont think that there is any such article, if any please gimme the link.
And what correction?
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Clowntowndevs said:
I dont think that there is any such article, if any please gimme the link.
And what correction?
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Click to expand...
Click to collapse
USEFULL THREADS
http://forum.xda-developers.com/showthread.php?t=1883161
NEWBIE GUIDE
http://forum.xda-developers.com/showthread.php?t=1675474
sangalaxy said:
USEFULL THREADS
http://forum.xda-developers.com/showthread.php?t=1883161
NEWBIE GUIDE
http://forum.xda-developers.com/showthread.php?t=1675474
Click to expand...
Click to collapse
Yes, ou are right bro but its just about bricks.
#Nooffence
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Never experience with hard brick, i hope don't
Sofyanization said:
Never experience with hard brick, i hope don't
Click to expand...
Click to collapse
Same here
I dont wanna lose my device
⊙facebook.com/clowntowndevs⊙ ♥Please like Us♥
Related
I tried rooting my evo and can't get past the boot screen. Is my phone ****ed or can it be saved.
sent from my nootered nook
ruiza997 said:
I tried rooting my evo and can't get past the boot screen. Is my phone ****ed or can it be saved.
sent from my nootered nook
Click to expand...
Click to collapse
What method did you use. What is your phone software and hardware setup?
Sent from my PC36100 using XDA App
this is the method that i used [ROOT] ~~~ HTC EVO - Universal Auto Root ~~~ v2.2 (works with all version)(2/1/11). im sure i did something wrong do not want to make it seem like i am placing the blame on the dev that wrote this. as for the other info well lets just say im an ass cus i didnt write it down like it was recomended. if it helps any i bought it a month ago max 2 months not shure it that helps.
Can you Boot into Recovery? (Hold Power+Volume Down when phone is off)
Did you create a Nandroid backup?
yes i did trying it now thank you for the help
after i boot into recovery what is next
go down to where it says recovery using the down volume button and click on with the the power button. Hopefully this will take you into recovery mode. If it does take you into recovery mode go down to where it says wipe cache partition and click on it and select wipe. Then go to where it says advanced and click on it. Then click on dalvik cache and click on the then select wipe. If you can do this they you can try to reboot your phone. If not. Let me know.
If you didn't do a backup and you can get into recovery you can do a data factory reset. Its on the green recovery menu.
If you cant get into any of that and you get stuck on a red triangle try holding the power button and the volume up and you should see a menu with a factory reset. click on that and it should wipe your phone.
i tried the first step and it did not take me to recovery mode and of course i did not do a back up cus im a dumb ass. I did manage to get to the screen with the red triangle and did a factory rest. ok another stupid question do i reboot the system or select apply sdcard update zip.
if you did a factory data reset just reboot. Hopefully this will get you back.
It might take a few extra minutes to start up so give it a few extra minutes.
on the white htc evo screen
has it been more that 5 minutes.
still on the evo screen sorry about the delay was talking to my wife, she doesnt know i screwed up my phone had to keep her occupied
Ok give me a minute. Were having storms here so my internet is slow. First you will need a SD card for your phone. Clean it out except for one file you will need to download.
You need to download pc36ing. Zip for 3. 70. 651. 1 just search the form and you can get it for free.
Sent from my PC36100 using XDA App
got the card and the file extracting it to the new sd card as i type this
ok dont extract the file. Just put the whole zip file on the sd card. Once you do this turn off the phone. Pull the battery if you have to. Then start the phone by holding the power button down and the down volume button. This should that us to the boot loader. One click down you should see the HBOOT usb at the bottom. Click down to go there. Once there click the power button then select fastboot, then bootloader. If everything went well you should be ask to flash something. Then select your file on the sd card.
i see what happened. this is why i dont use auto scripts. if one command fails, there is no possible way to find out which. just unroot using an ruu or a pc36img.zip and then do zikronix's there will be root tutorial. i'll link it in my sig soon.
doesnt appear to be reading the file says no image. to be honest not sure if i am doing this right. did you want me to use two different sd cards.
make sure it's named pc36img.zip exactly. and is on the root of ur sdcard (not in any folders). i have the method linked in my sig now btw.
dkdude36 said:
i see what happened. this is why i dont use auto scripts. if one command fails, there is no possible way to find out which. just unroot using an ruu or a pc36img.zip and then do zikronix's there will be root tutorial. i'll link it in my sig soon.
Click to expand...
Click to collapse
try to follow the above link. This might be a little easier. Don't worry your phone can see be saved. If all else fails your phone is not rooted so you can take it to Sprint and tell them that your phone is jacked and you need a warranty replacement. Last resort.
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
Background Info
So, my DHD had a problem with the mic so I sent it to a local mobile phone store to see if they could repair it. After 3 weeks, they called me and told me there was nothing that could be done since the mic was in the motherboard and they can't change that.
I got my phone yesterday and and noticed traces and dents from using a normal screwdriver to open the led case. Apart from that and the fact that they took 3 weeks to repair nothing, everything else was ok. However, I had a custom ROM installed and when I got it, they had installed a new one whose name I can't remember ("something"-revolution maybe).
Actual problem:
It worked fine for a night but the next day, I couldnt move the ring to unlock the screen. I restarted it,k tried without sd card or sim, changed batteries and nothing. I just freezes in the "Insert pin code" screen and won't let me input anything.
I had CWR but it seems they deleted it and now I have 4ext which can only be used with touch input which doesn't even work in 4ext. (The volume and power buttons work fine).
Final thoughts
What can I do? Since there is no way I can use 4ext or anything in order to factory reset...
I am really mad at the store which f***ed up my phone but I am traveling next week and I really need my phone.
Anything I could do to factory reset?
Thanks in advance
I don't know how this works against the rules, but would it be okay to post that store's name so that others can avoid it? It sounds like they are not trained for this type of repair. I would hate for others to find out the hard way as you did.
Store
Oh, don't worry. I live in Spain and they only work nationally so I guess you don't have to worry about it. But the name of the store: MovilCom
If I understand you correctly your phone is rooted and you can access 4ext recovery? If so:
Download one of the custom roms from the development forum, there are a lot of good roms but I recommend Android Revolution HD if you are a beginner.
Place the rom file on your sd card.
Enter recovery by holding down the volume down button and pressing the power button when the phone is off.
Select the option to do a full wipe.
Select install from sd card, look for the rom file you downloaded and install. It should work now.
NOTE: this will erase all the content from your phone and give you a fresh rom install.
That won't work
Lewelynn said:
If I understand you correctly your phone is rooted and you can access 4ext recovery? If so:
Download one of the custom roms from the development forum, there are a lot of good roms but I recommend Android Revolution HD if you are a beginner.
Place the rom file on your sd card.
Enter recovery by holding down the volume down button and pressing the power button when the phone is off.
Select the option to do a full wipe.
Select install from sd card, look for the rom file you downloaded and install. It should work now.
NOTE: this will erase all the content from your phone and give you a fresh rom install.
Click to expand...
Click to collapse
I tried doing that but I can't use 4ext since the touch screen doesn't seem to respond. Before, I hade CW and I could have probabbly flashed a ROM already but as I said, the screen appears to be responseless in 4ext and in normal boot (I can't even input my pin code)
No solution...
So, I downloaded a RUU.exe from a stock Gingerbread version with Sense 2.0 (The unlicking system is the old slide down to unlock bar, not the ring) and the problem remains. When I bot, the touch screen is completeley response less. What can this be?
I am beginning to think this might actually have something to do with hardware? Maybe some wire is lose?
Thanks in advance
help
bump.help please...
Ok guys I would be eternally greatful if someone could please help me on this issue asap...I was in the process of rooting/unlocking/installing CWM on my brother's A100, and I ran into a somewhat serious issue.
Everything was going great - I rooted it, unlocked the bootloader, and started to install CWM. Unfortunately, I totally screwed up and didn't rename /etc/install-recovery.sh. I got all the way through flashing the recovery.img before I realized...I realize this is completely my fault.
After trying to reboot into CWM using the volume down key on power up, it simply shows a picture of an android with a spinning blue orb in it's stomach. After this finishes, it briefly say "Start Updating EBT" then "Finished Updating EBT". It then reboots once more back to the standard android OS. Additionally, during bootup it no longer displays the message about the bootloader being in "UNLOCKMODE".
Is there anything I can do from here? I realize I've totally screwed up, but if anyone could provide step-by-step ideas of what I need to do I would be very thankful. i.e. is the bootloader re-locked, and if so do I need to re-unlock it? and how could I successfully get CWM working? Thanks in advance!
ohlin5 said:
Ok guys I would be eternally greatful if someone could please help me on this issue asap...I was in the process of rooting/unlocking/installing CWM on my brother's A100, and I ran into a somewhat serious issue.
Everything was going great - I rooted it, unlocked the bootloader, and started to install CWM. Unfortunately, I totally screwed up and didn't rename /etc/install-recovery.sh. I got all the way through flashing the recovery.img before I realized...I realize this is completely my fault.
After trying to reboot into CWM using the volume down key on power up, it simply shows a picture of an android with a spinning blue orb in it's stomach. After this finishes, it briefly say "Start Updating EBT" then "Finished Updating EBT". It then reboots once more back to the standard android OS. Additionally, during bootup it no longer displays the message about the bootloader being in "UNLOCKMODE".
Is there anything I can do from here? I realize I've totally screwed up, but if anyone could provide step-by-step ideas of what I need to do I would be very thankful. i.e. is the bootloader re-locked, and if so do I need to re-unlock it? and how could I successfully get CWM working? Thanks in advance!
Click to expand...
Click to collapse
First off, slow down, take a breath, relax, and realize the world didn't just end, everything is fine, it just went awry at one point where alot of people miss the step of install-recovery.sh.
Start from the beginning, check if you have root.
If you have root, then use any root file manager (I use ES File Manager, in settings check "Up to root" then further down, check "Root Explorer", grant it permission, then check "Mount system Writable") and navigate to /system/etc.
Rename or move or delete install-recovery.sh. I would just rename it install-recovery.bak.
Go ahead and reboot, and verify the green acer screen does NOT say (unlocked mode) in the upper right corner. If it does in fact NOT say that (it should still be unlocked) then proceed with the previous steps starting at unlocking the bootloader.
Once the bootloader is again unlocked (remember to be quick on those volume keys) proceed with flashing CWM or TWRP or whatever you choose.
Now when you reboot into android, your custom recovery will remain intact.
Now that you have a custom recovery, boot into it, and first thing, mount either internal or external SD (I use external) and make a full backup. Do it NOW. After that is done, it takes a few minutes, you can either keep the stock ROM, flash a new one, whatever, it's up to you, but you will now have a backup to fall on if anything goes wrong.
In the guide in my sig is a ton of information, I would suggest browsing it to become familiar with some things about these devices.
pio_masaki said:
First off, slow down, take a breath, relax, and realize the world didn't just end, everything is fine, it just went awry at one point where alot of people miss the step of install-recovery.sh.
Start from the beginning, check if you have root.
If you have root, then use any root file manager (I use ES File Manager, in settings check "Up to root" then further down, check "Root Explorer", grant it permission, then check "Mount system Writable") and navigate to /system/etc.
Rename or move or delete install-recovery.sh. I would just rename it install-recovery.bak.
Go ahead and reboot, and verify the green acer screen does NOT say (unlocked mode) in the upper right corner. If it does in fact NOT say that (it should still be unlocked) then proceed with the previous steps starting at unlocking the bootloader.
Once the bootloader is again unlocked (remember to be quick on those volume keys) proceed with flashing CWM or TWRP or whatever you choose.
Now when you reboot into android, your custom recovery will remain intact.
Now that you have a custom recovery, boot into it, and first thing, mount either internal or external SD (I use external) and make a full backup. Do it NOW. After that is done, it takes a few minutes, you can either keep the stock ROM, flash a new one, whatever, it's up to you, but you will now have a backup to fall on if anything goes wrong.
In the guide in my sig is a ton of information, I would suggest browsing it to become familiar with some things about these devices.
Click to expand...
Click to collapse
Thank you very, very much! I went through everything again, and finally got CWM up and a backup taken. I was thinking those steps were what I needed to do, but didn't want to proceed without a confirmation. Thanks again for your great advice!
ohlin5 said:
Thank you very, very much! I went through everything again, and finally got CWM up and a backup taken. I was thinking those steps were what I needed to do, but didn't want to proceed without a confirmation. Thanks again for your great advice!
Click to expand...
Click to collapse
No problem, just be sure to take your time before diving into anything, and make sure everything has been read twice before starting.
pio_masaki said:
No problem, just be sure to take your time before diving into anything, and make sure everything has been read twice before starting.
Click to expand...
Click to collapse
I know lol, that why I felt like such a doofus admitting I did it, because I literally read that part about renaming twice before I even started...I guess it was one of those in-one-ear-out-the-other-cause-I'm-tired type of deals
Anyways thanks again, I'll definitely have to do this when I'm a little more awake next time...wait, here's to hoping there's not a next time :laugh: Thanks!
I used twrp because the instructions sounded so much easier, even though I've worked with cwm for over a year.
sent from my sexy-a$$-iconia tab
Hello all. Let me first thank you for your time in reading my post. I appreciate it. I'm not a fan of only posting for help but I suppose that the site suggesting to always search first is to thank for that because I am usually able to find answers. So please forgive me if this is posted elsewhere but I really have searched and asked around but haven't seen anything similar to my issue. If there is something like it I do not know what to call it. I at first thought it was a sudden death, but realized I think my device model & the symptoms have disproved this theory.
My story...
I bought my AT&T Galaxy S3 feb 2013. I have had it, spent a month or two stock everything. The past month & a half I have flashed CM 10.1 & most recently PK-2.32 for about 3 weeks. Have ran it and loved it with no issues. Used the kernel that comes with both ROMs.
4 days ago
I was charging my phone at work, picked it up after a while, and it wouldn't turn on. It was stuck in a loop of 2 of the screens in my attachments(the battery screen & the SGS3 logo). The battery screen is not in motion, it is stationary like that so that the circle doesn't move.
I have tested quite a few things in regard to what I thought might be the issue...other batteries, chargers, cables pull sim & SD and still no luck...etc.
While the phone is unplugged I get no indication of life. Only when I plug it in will it show me the battery symbol & the logo.
After some playing with it while it is plugged in I have been able to get it into download mode quite frequently with no issue as seen in the third attachment.
So yes I can get into download mode but I'm still "fairly new" and not sure where to proceed from here. I'm not sure what my options are as this is new to me and I can't find anything related, nor can my much more experience friend who is not so new at it that got me into wanting to load custom ROMs.
And yes, as you can see it has tripped my flash counter up once, from what I've read there's only one way to fix that if I need to send it in.
So...If you are able and willing to help I would greatly appreciate it and any options you might give me. I'm willing to try almost anything as my phone is of no use to me at this moment.
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
xBeerdroiDx said:
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
Click to expand...
Click to collapse
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
moose0003 said:
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Click to expand...
Click to collapse
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
Click to expand...
Click to collapse
Thanks again for your reply. I will try this and check back.
You are correct, it just did this, no kernel or anything. I will try wiping the device the data doesn't bother me. I won't lose much.
Have you or anyone else heard of this happening or know a cause? I could not find anything.
aybarrap1 said:
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
Click to expand...
Click to collapse
Thanks for your reply. I have a few backups. I will try stock first and see where that takes me and go from there.
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
moose0003 said:
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
Click to expand...
Click to collapse
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
metalsnakebite said:
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
Click to expand...
Click to collapse
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up.......
Click to expand...
Click to collapse
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
moose0003 said:
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
Click to expand...
Click to collapse
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
moose0003 said:
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
Click to expand...
Click to collapse
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
metalsnakebite said:
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
haha. i've done that before. cheers, buddy.
xBeerdroiDx said:
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
metalsnakebite said:
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
Thanks for the input guys. I'm having a difficult time to get it to stay into recovery now again. It acts like it wants to go in but it will just reboot. I will keep trying and if I need anymore help I will come back. Thanks so much again.
Back again. So I kept playing and was finally able to get into recovery as you guys suggested. Once I got in it finished the odin process and actually booted up! First time in a week. So ran through setup and then was able to determine that wifi is not working with stock ROM. Not sure if it's the phone or the ROM.
After it booted up and turned on was able actually do most functions, didn't test a lot wanted to see if it would work without being plugged in...this answer was no.
So after much testing I think what determines what will power it on and off is determined by what it is plugged into. I still think it is having hardware issues though because of the lack of powering on, but I am fairly certain that I can start it every time with a certain cable/charging dock.
I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.
Haven't done this yet but will start tonight & have it finished by tomorrow is the plan. If anyone has any better suggestions I would gladly take them.
So this should be my last post unless a question arises for me.
moose0003 said:
.....I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.....
Click to expand...
Click to collapse
This is what I said I was going to try to do. Took it to work and found time to do the above. TriangleAway worked a lot better than I ever thought it would. Flash counter reset, loaded unrooted stock and have a replacement on the way. Went very smoothly.
So doubt I will root & rom again until out of warranty. I appreciate everyone's help with my issue.
XDA is a great place.