Database Users

think i bricked my phone

ok so i had fresh 2.0 and the updated radio on my phone. i woke up today and flashed the damage rom, and while it was booting for the first time i decided to take a shower. when i got out, i tried to turn the screen on. nothing. rebooted, screen came on, then it went off tried to turn it back on. nothing. i nandroid resotred back to fresh 2.0, booted, screen turned off, tried to power it on, nothing. called my phone, it rang but the screen didnt turn on. i RUUed it, said it was complete, booted up and froze at the htc screen. i tried to adb into it, nothing. went into fastboot, tried to adb, nothing. turned it on to hboot, restarted, then got the image of a phone with a caution sign. got into Android system restore utility, and it says E:cant read MISC: (no space left on device) i data/factory wiped, said complete, tried to flash an update.zip from the recovery utility, keeps comming up no signature. i tried 4 different roms. wtf?

blankd3ckskat3r said:
ok so i had fresh 2.0 and the updated radio on my phone. i woke up today and flashed the damage rom, and while it was booting for the first time i decided to take a shower. when i got out, i tried to turn the screen on. nothing. rebooted, screen came on, then it went off tried to turn it back on. nothing. i nandroid resotred back to fresh 2.0, booted, screen turned off, tried to power it on, nothing. called my phone, it rang but the screen didnt turn on. i RUUed it, said it was complete, booted up and froze at the htc screen. i tried to adb into it, nothing. went into fastboot, tried to adb, nothing. turned it on to hboot, restarted, then got the image of a phone with a caution sign. got into Android system restore utility, and it says E:cant read MISC: (no space left on device) i data/factory wiped, said complete, tried to flash an update.zip from the recovery utility, keeps comming up no signature. i tried 4 different roms. wtf?
Click to expand...
Click to collapse
If the RUU was successful then you wouldn't be able to access the recovery console b/c it restores the phone & takes away root. I'd try the RUU again... Maybe download it again and be sure you follow every step to a T. It's not bricked cause it's turning on. Good luck!

mrcharlesiv said:
If the RUU was successful then you wouldn't be able to access the recovery console b/c it restores the phone & takes away root. I'd try the RUU again... Maybe download it again and be sure you follow every step to a T. It's not bricked cause it's turning on. Good luck!
Click to expand...
Click to collapse
im not talking about the rooted recovery console. im talking about the built in android recovery utility. my pc cant find my phone.

blankd3ckskat3r said:
im not talking about the rooted recovery console. im talking about the built in android recovery utility. my pc cant find my phone.
Click to expand...
Click to collapse
Built in Android Recovery? Never seen that... Idk man. I'd be running the RUU over and over all day. If that doesn't work go into a Sprint store and say your phone "just won't turn on for some reason."

How do you access the built in recovery??

mrcharlesiv said:
Built in Android Recovery? Never seen that... Idk man. I'd be running the RUU over and over all day. If that doesn't work go into a Sprint store and say your phone "just won't turn on for some reason."
Click to expand...
Click to collapse
The stock android recovery is the ! screen with no options. BTW, there isn't adb access via android recovery, you need Amon_RA's or Cyanogen's

HeroMeng said:
The stock android recovery is the ! screen with no options. BTW, there isn't adb access via android recovery, you need Amon_RA's or Cyanogen's
Click to expand...
Click to collapse
Oh... Yeah I've seen that. Thanks for clearing that up for me.

Try holding down the house and the back key and turning on the phone... should be a hard phone reset that may work.

mrcharlesiv said:
It's not bricked cause it's turning on.
Click to expand...
Click to collapse
This is untrue (unfortunately, I know from experience)... My phone "turned on" but would go into a specific FastBoot menu that did not allow anything to be performed that would take it out of that state... many people have gotten stuck at the same place and nobody has a solution. Its the Error 110 when RUU-ing...
R

thats a new one to me.

i cannot repeat cannot see my phone on my computer when booting it on. the built in recovery lets me facotry reset but says cannot read MISC and that my devices memory is full. its whatever. gettign a new hero tomorrow anyway

EI22 - stuck at loading screen

I was going to use the EC05 to EI22 update.zip file posted here to get myself some gingerbread goodness, but I have a couple questions plus I ran into a problem.
Questions (have asked in multiple threads but because of the frenzy over gingerbread release it's like trying to talk at a heavy metal concert: I am fully stock ec05 EXCEPT for having done root so that I could do wi-fi hotspot (from advice given in this thread a little while back - http://forum.xda-developers.com/showthread.php?t=1236669). Will this interfere with doing the EI22 update or do I need to back it out? I want to say I recall someone mentioning the update would go fine and I'd just have to re-root.. but looking for specifics.
Problem: I put the update.zip onto my SDcard, reboot my phone..... and it's just sitting there staring at me, Samsung boot logo as bright as ever, for about 20 minutes now. I had been trying to do the vol-down, camera, power key set to get into service mode, but it never got past this boot screen - yanked the battery and SDcard and trying again and it's still just sitting here.
Help?
--update--
Leaving it off, plugged in the power and rather than getting a proper charging display with the battery and charge meter/status - it has a blank battery with the radial spokes that would normally be rotating just sitting there. What happened to my phone? O_O

tigerknight said:
I was going to use the EC05 to EI22 update.zip file posted here to get myself some gingerbread goodness, but I have a couple questions plus I ran into a problem.
Questions (have asked in multiple threads but because of the frenzy over gingerbread release it's like trying to talk at a heavy metal concert: I am fully stock ec05 EXCEPT for having done root so that I could do wi-fi hotspot (from advice given in this thread a little while back - http://forum.xda-developers.com/showthread.php?t=1236669). Will this interfere with doing the EI22 update or do I need to back it out? I want to say I recall someone mentioning the update would go fine and I'd just have to re-root.. but looking for specifics.
Problem: I put the update.zip onto my SDcard, reboot my phone..... and it's just sitting there staring at me, Samsung boot logo as bright as ever, for about 20 minutes now. I had been trying to do the vol-down, camera, power key set to get into service mode, but it never got past this boot screen - yanked the battery and SDcard and trying again and it's still just sitting here.
Help?
Click to expand...
Click to collapse
Pull your battery..
Boot back into stock recovery and do a full wipe/reset
Reboot.
Should be fine

Paul627g said:
Pull your battery..
Boot back into stock recovery and do a full wipe/reset
Reboot.
Should be fine
Click to expand...
Click to collapse
No joy.. all these steps started with no AC power, no SD card, and pulled battery, with at least a minute of full lack of any form of power:
insert battery, power on: sits staring at initial 'samsung' boot display
insert battery, plug in AC: gets blank battery meter as described and won't boot
no battery, plug in AC: gets blank battery meter as descrobed and won't boot

http://forum.xda-developers.com/showthread.php?t=1052813
1. Use this to get back to EC05
2. Rename update to update.zip and place in root of SD card
3. Boot into stock recovery and flash update.zip

I was having the same problem with the OTA. So I odined back to EC05 and then applied EI22 via update.zip in stock recovery. Same result, stuck at boot screen.

BLARGH. I was hoping to not have to wipe my phone. Oh well, here goes nothing. Will post results as I get them. Thanks for the assist, guys.

I have seen confirmed reports of users booting back into stock recovery and doing a full reset/wipe then rebooting with no problems.

Had to cheat to get into download mode. Page says no battery, only USB cable - soon as I plug that in though it gets stuck on the battery meter screen and won't go further.
I had to use the battery and boot into download mode that way, THEN connect the USB cable and so far it seems to be functioning as planned.. keeping my fingers crossed.
--update--
Odin completed and phone booted fine. inserted SD card - tried updating but it is refusing, complaining of low battery. Guess I'll have to let it charge for a while and try again.

Can you boot into download mode? You might have to ODIN/Heimdall EC05 and start from scratch again.
Edit: Ignore this... I don't know why your reply wasn't on the page when I replied...

I was running CWM 3.1.0.1 which gave an error when trying to apply update.zip (looks like it failed a checksum check on recovery).
Thinking it was CWM causing the issue and I needed to revert back to the stock recvoery, I took the stock recovery from this thread:
http://forum.xda-developers.com/showthread.php?t=1027904&highlight=rerfs
and renamed it recovery.zip and applied it via CWM.
After rebooting, my phone is having the same symptoms as tigerknight:
insert battery, power on: sits staring at initial 'samsung' boot display
insert battery, plug in AC: gets blank battery meter as described and won't boot
no battery, plug in AC: gets blank battery meter as descrobed and won't boot
Unfortunately, I cannot boot into recovery mode anymore either. It seems to get hung on the same "Samsung" screen as when trying to boot normally.
I'm going through the de-bricking process now. <sigh>

I let my phone charge for a little and then the update.zip ran just fine. I didn't actually lose much data thanks to stuff being on my SD card, but I need to go through and recall what apps I used regularly now.. mostly work related stuff so not a whole lot, thankfully.
Yay for EI22 and VERY snappy handling compared to before off of just completely stock image!

[Q] How to reboot into recovery?

I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.

Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?

I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.

Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.

Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.

first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.

I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.

lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT

[Q] Note 3 BRICKED even after Stock flash

So Im going to start from the beginning. I have a Verizon Note 3 MJE, rooted with VROOT, cool now Im rooted.
Now i wanted a Custom Rom, So i downloaded Safestrap 3.64 and the Hyperdrive Rom. All good..
Go into the slots of Safestrap recovery create the partition, install HyperDrive and hit Reboot...
Phone reboots but the screen stays blank.. Go do my research and says wait 5-10 minutes after install for w.e reason..
20 minutes go by... go back into safestrap re do process... nothing again.. decided to go back to stock download all Safestraps and one by one start to install and uninstall trying to verify that i have installed the correct Safestrap for installing the Rom... (i know don't tell me Im an idiot but it made sense last night) nothing that i did work... so went back to stock JB 4.3 so now Im rooted as i began...
go into the Safestrap app and uninstall from recovery this one was Safestrap 3.71.. phone is working fine..
So I have no Safestrap im good... set my phone down to clean my car, the phone Wont turn on..
NOOOOOOOO, IDK for the life of me What happened... So i try every button possible, nothing! Recovery Nothing!!!
I plug it to charge it shows the pre charging battery then shuts and repeats...
figured let me try holding Down-Menu-Power while is doing that ... i get into Download mode, Not gonna lie i cried a little lol
Flashed the Stock Firmware 4.3 with the VZW note 3 32g PIT file... finishes ... Resets now Stuck on BOOTLOOP with the Custom Note 3 Splash screen and on top says Entering Recovery but never does... I Have Tried almost everything but hit it with a BAT!!! Can someone please help me...
and YES i took the battery out and put it back in

1. pull sd card
2. hold vol down, home, power to enter "download mode"
3. hit cancel and it should fire up

fletch33 said:
1. pull sd card
2. hold vol down, home, power to enter "download mode"
3. hit cancel and it should fire up
Click to expand...
Click to collapse
The phone will only work if is plugged in to A\C OR computer usb..
I plug it in, the loading battery will pop up, turn off and then repeat.. the whole process takes about 3-4 secs..if unplugged wont do anything at all, when plugged into the computer it lets me access download mode but not recovery..

crunchy_taco said:
The phone will only work if is plugged in to A\C OR computer usb..
I plug it in, the loading battery will pop up, turn off and then repeat.. the whole process takes about 3-4 secs..if unplugged wont do anything at all, when plugged into the computer it lets me access download mode but not recovery..
Click to expand...
Click to collapse
Sent from my SM-N900V using XDA Free mobile app
I would try flashing the stock unrooted mje file by itself.
If you are in same boat then I would flash the pit file by itself. AFTER
All of which is done in odin.

i 2nd that ^^^

mike7728 said:
i 2nd that ^^^
Click to expand...
Click to collapse
Ok I will try that I soon as I get home I will let u guys know how it went
Thanks for all your help guys

crunchy_taco said:
The phone will only work if is plugged in to A\C OR computer usb..
I plug it in, the loading battery will pop up, turn off and then repeat.. the whole process takes about 3-4 secs..if unplugged wont do anything at all, when plugged into the computer it lets me access download mode but not recovery..
Click to expand...
Click to collapse
To be honest...that sounds like a dead battery. You know someone else who has a note 3 you can test by trying their battery?
Sent from my Note 3 via Tapatalk

donc113 said:
To be honest...that sounds like a dead battery. You know someone else who has a note 3 you can test by trying their battery?
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
I tried the battery on another note 3 and vise versa, I got it to go into recovery after flashing stock room at one point and full wiped factory reset it from recovery the fone reset twice and it booted to the welcome screen of picking language but shut off wont turn back on.. so square one again battery bootloop and note 3 bootloop when try to access recovery

Bricked MF3 4.2.2 rooted

Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.

DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.

DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Just reflash the rom you are on without wiping. That should fix it.

Is the phone an i337? If it is, you're in the wrong s4 forum.

GDReaper said:
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
Click to expand...
Click to collapse
Okay and suppose i could get adb working how would i copy the "usr" file back to the "/system"

audit13 said:
Is the phone an i337? If it is, you're in the wrong s4 forum.
Click to expand...
Click to collapse
Yea it is the i337 my bad i didnt noticed can it be moved?

Contact a moderator and ask him or her to move your thread.

Lennyz1988 said:
Just reflash the rom you are on without wiping. That should fix it.
Click to expand...
Click to collapse
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.

DaFrenchTaco said:
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
Click to expand...
Click to collapse
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.

Lennyz1988 said:
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Click to expand...
Click to collapse
I think AT&T and Verizon phones always had locked bootloaders, just that the earlier versions were easier to hack.

if its hard bricked, try jtag

thnx to everyone in this thread you were all of help my phone is now working even better then it did before much appreciated