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
Related
So I wiped my phone and applied a TMO 1.6 rooted rom (http://db.androidspin.com/android_b...droid_developer_id=&NumberOfReleases=10&go=go). I then applied The expansion pack then rebooted with home+back. When the phone rebooted it cannot get passed an image of a package and an arrow towards a phone. When I remove the battery then replace it the phone turns off. When I plug the battery back it it wakes up and tries to resume the install process. I feel like I could fix the problem if the phone was not stuck at the install screen, but it is.
I tried booting with camera held down and dreaimg.nbh on the sd card but I get the same results.
What can I do about this?
Did you try to boot into recovery (Home + On)? From here it should be possible to apply the rom again.
mevets said:
So I wiped my phone and applied a TMO 1.6 rooted rom (http://db.androidspin.com/android_b...droid_developer_id=&NumberOfReleases=10&go=go). I then applied The expansion pack then rebooted with home+back. When the phone rebooted it cannot get passed an image of a package and an arrow towards a phone. When I remove the battery then replace it the phone turns off. When I plug the battery back it it wakes up and tries to resume the install process. I feel like I could fix the problem if the phone was not stuck at the install screen, but it is.
I tried booting with camera held down and dreaimg.nbh on the sd card but I get the same results.
What can I do about this?
Click to expand...
Click to collapse
Seems like you lost root access and might even have a brickm, but anyway is fastboot working for you? Maybe you can get adb working if recovery or fastboot are working.
Recovery mode and fast boot both do not work. Everytime I turn the phone on it remembers that it was installing a rom and stalls at some point.
Is it worth the time to figure out how to setup adb or do those two signs above show that even adb wont work?
I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?
Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)
There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).
A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.
ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.
I just had this exact experience; have you made any progress, goatlordbob?
same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?
why doesnt there seem to b any help for this matter, smh
bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.
Anyone bothered booting using home + power?
shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.
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
Good evening everyone,
I will start off by saying that I really didn't do things by the book this time around. I have run out of ideas even as to what to Google to find similar cases to mine.
I wanted to flash Cyanogenmod onto my G2. Since I already had CWM installed, I loaded the ROM and Gapps. After wiping the phone, I went to flash from the zip. The flash failed. I tried again, and it happened again. I wiped the cache and dalvik again, and tried again. Still no flash.
At this point I go for the reboot only to realize that my phone is now stuck in a bootloop that is contantly landing me back into recovery.
I believe I really screwed up from here as I read about a way to exit the cwm bootloop by flashing a new "exitrecovery.zip" file. Since ADP wouldn't push the file for some reason, I used that function where the phone waits the file to be pushed and flashes it. That succeeded.
The phone switched off (after hanging on CWM for a bit) and now won't do anything at all. No boot logo, nothing. Can't get into CWM anymore either.
The computer brings up a bunch off drives which it wants me to format when I plug the phone in. Only one of them has a folder called "image" on it.
The display switches on, but won't do anything there.
Holding power+up reboots it after a few seconds and so does power=down.
I am thinking of just seeing if I can get it assessed by my carrier, hoping they'll have the tools to just reflash it... somehow. Else, is there a way to potentially fix this?
Back to stock
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.
Rule number 1.
ALWAYS MAKE A BACKUP.
bodom_hc said:
Rule number 1.
ALWAYS MAKE A BACKUP.
Click to expand...
Click to collapse
I have a backup I made with CWM.
If that helps, please point me into the right direction to restore it. I fail to see how I can do that without even being able to start cwm up.
missiveusa said:
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.
Click to expand...
Click to collapse
I will try this, but the screen never shows anything at all
Hey, so I have had my phone rooted for a long time. I have a Galaxy S5 6.0.1 Marshmallow.
I decided I wanted to get Framework installed so I downloaded the right files and flashed it in TWRP.
My phone took way longer than 10 min to reboot into system so I thought I was stuck in a bootloop and decided to run my phone through TWRP again.
I tried rebooting but that didn't work. I have my phone's backup saved onto a micro SD so I did a factory reset and then tried rebooting.
I got past the rebooting logo and actually got to my lock screen where it asks for my password.
From there, I've been getting spammed with 3 different messages, one saying that IMS service is down, com.sec.vsimservice is down, and WfcService is down.
After I press ok to all 3 of the messages, my phone is still in the lock screen asking for my password but the phone doesn't recognize that im touching the screen to type. After letting the phone stay like that for a few minutes, the lock screen that asks for my password goes away and all I can see is my wallpaper background (no notification panel either) but now the phone recognizes me touching the screen ( I know that because the LED lights up for the windows button and back button )
So basically I decided to go into TWRP and flash my recovery that I had saved on the microSD.
After that didn't work, I've just been going through a series of factory resetting my phone and wiping Dalvik files and then flashing my recovery. My phone is getting unrealistically hot too.
Btw I never downloaded the Exposed Uninstaller from the forum so I tried downloading it onto my pc and then sending the file over to my phone through download mode using Odin so that I could flash the uninstaller through my TWRP but that didn't work because the PDA in Odin does not recognize the uninstaller file.
Please, I really need help and thanks to anyone who tries, it would mean a lot if someone could figure out what I can do. Thanks.
Since you've tried restoring your backup and everything seems to have failed (it sucks, I know) you should try to install a completely stock firmware which you can download from here: http://live.samsung-updates.com/index.php?device=SM-G900I Just make sure you select your exact phone model from the dropdown menu at the top right side as you didn't mentioned which of the 40 S5s you have lol. And after you flash stock firmware and successfully boot up try to restore your backup. If it's still bugged - flash stock again and start off fresh. Let me know how it turns out. I'll help with installing xposed later as well, first let's get your phone running again