Okay let me run through a couple of scenarios so that we can understand the main issue here. I flashed my i9250 GNEX phone with the linaro OMNI Metal's new update.... with a broken volume up button manually through CWM. Upon rebooting, the phone shows the starting logo and then gets to the updates eventually ending up with the: 'Android is upgrading... Starting Apps' screen. It's stuck there and I do not know what to do next.
I went to the shop to try and fix the volume button but for some reason I could not get into the recovery by holding the vol up, vol down + pwr button. THEY MIGHT HAVE NOT FIXED IT, but then again... how we're they going to test it anyways when the phone can't even boot up right?
They told me to sideload adb and flash the original stock image using a micro usb (they have this microusb that gets the phone to the download screen) so get to the update/download screen -> but I do not have that USB that allows me to do that now...
Any ideas on how I can revive this phone?? It's really a good phone and though I have the Nexus 5 now.. I still think about the Galaxy Nexus a lot... =/
Please help me T_T
:crying:
I understand your frustration, this happened to me a couple months ago after doing a custom update. I don't remember the exact solution, but I have some solid ideas. First we have to get into recovery.
Hold volume up + volume down + power to do this. (Using one volume and power just goes to Odin download mode / last resort of last resorts)
When you're in recovery, do a nandroid backup since well be trying a bunch of stuff, permission fixing, formatting.
After a nandroid try:
-fix permissions through recovery
-wipe cache and dalvik cache through recovery
If those don't boot you, try wiping data (NOT sdcard). If this doesn't work the problem is what's installed to /system..and we'll go from here.
We need to get into recovery first and sequentially try the things I listed. Let me know if this is now possible.
7175 said:
I understand your frustration, this happened to me a couple months ago after doing a custom update. I don't remember the exact solution, but I have some solid ideas. First we have to get into recovery.
Hold volume up + volume down + power to do this. (Using one volume and power just goes to Odin download mode / last resort of last resorts)
When you're in recovery, do a nandroid backup since well be trying a bunch of stuff, permission fixing, formatting.
After a nandroid try:
-fix permissions through recovery
-wipe cache and dalvik cache through recovery
If those don't boot you, try wiping data (NOT sdcard). If this doesn't work the problem is what's installed to /system..and we'll go from here.
We need to get into recovery first and sequentially try the things I listed. Let me know if this is now possible.
Click to expand...
Click to collapse
Sorry I forgot to mention that I can't boot into recovery using [vol up, down + pwr button] (sorry i didn't include vol down before) as my power up volume rocker is broken and not functioning. I just need to be able to get into recovery but not possible with the up rocker not functioning.
Is there any other way to get through to recovery by side loading? The phone can't get past the android is upgrading screen... so, I'm lost.
shencez said:
Sorry I forgot to mention that I can't boot into recovery using [vol up, down + pwr button] (sorry i didn't include vol down before) as my power up volume rocker is broken and not functioning. I just need to be able to get into recovery but not possible with the up rocker not functioning.
Is there any other way to get through to recovery by side loading? The phone can't get past the android is upgrading screen... so, I'm lost.
Click to expand...
Click to collapse
OK that makes sense, sorry I must have missed that. Have you tried booting the phone in safe mode? To do this, turn the phone off, then hold power to turn it on. Once you see the Google logo press and hold "volume down" until the phone has fully booted. Once the phone is booted, you will see the "safe mode" logo and can stop holding "volume down." If one of your apps in /data is causing the boot issue, this will get you into Android.
I see in the first post that you don't have a USB cable to attach to a computer? If this is true, we won't be able to adb, fastboot, or Odin download to push a ROM to the phone. Most people have this cable since it also attaches to a usb wall charger. Without it, there's maybe one last sketchy thing we can try, which would be to take the phone apart and electrically short the volume buttons to get into recovery. Even though the volume button is broken, the connection is still definitely there. The button just doesn't work or is disconnected.
Let us know if the safe mode gets you booted and whether or not you have a USB cable to connect your phone to a computer. I just want to double check about the cable cause if you don't have it. Our last resort attempt would be to short the broken volume button.
7175 said:
OK that makes sense, sorry I must have missed that. Have you tried booting the phone in safe mode? To do this, turn the phone off, then hold power to turn it on. Once you see the Google logo press and hold "volume down" until the phone has fully booted. Once the phone is booted, you will see the "safe mode" logo and can stop holding "volume down." If one of your apps in /data is causing the boot issue, this will get you into Android.
I see in the first post that you don't have a USB cable to attach to a computer? If this is true, we won't be able to adb, fastboot, or Odin download to push a ROM to the phone. Most people have this cable since it also attaches to a usb wall charger. Without it, there's maybe one last sketchy thing we can try, which would be to take the phone apart and electrically short the volume buttons to get into recovery. Even though the volume button is broken, the connection is still definitely there. The button just doesn't work or is disconnected.
Let us know if the safe mode gets you booted and whether or not you have a USB cable to connect your phone to a computer. I just want to double check about the cable cause if you don't have it. Our last resort attempt would be to short the broken volume button.
Click to expand...
Click to collapse
Thanks for your reply once again, I tried what you said about holding the vol down button once I see the google logo. However, the animation screen just comes up and goes back to Android is upgrading... optimizing apps 1 of 1.. starting apps... then it stops there as usual.
The USB i was referring to was the USB dongle which is similar to the ones like the hdmi cable. I have the usb cable for connecting to pc and may have to try the adb way to resolve the issue. Any steps on what I could do at this point? I've never flashed via adb in this situation so I may need some guidance.
Once again, thanks for you help very much appreciated.
UPDATE: I tried ADB REBOOT RECOVERY and I ended up with this error message. Attached is the photo to see it. 'error: device unauthorized. Please check the confirmation dialog n your device.'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update II: http://forum.xda-developers.com/showthread.php?t=2522401
This thread... I finally found what I need. a USB JIG. Where can I find these???
Sorry for the late reply, but glad you found a good thread link to this problem. I'm not sure what that guy means by USB jig, but I'm guessing he rigged up something to short out "volume down" when powering it on thereby getting to Odin mode. If you can get into Odin mode, by pressing "volume down" and "power", you won't need to do this. Let us know if you can get there. You'll see "Odin mode" in tiny red letters in the upper left corner.
Here's a good walkthrough (w/ mysid and yakju ICS images): http://www.inspiredgeek.com/2011/12...d-cf-root-insecure-kernels-step-by-step-guide
Maguro Odin Firmware Images:
takju: https://dl.google.com/dl/android/aosp/takju-jwr66v-factory-c2ef855e.tgz
yakju: https://dl.google.com/dl/android/aosp/yakju-jwr66v-factory-ad817ccc.tgz
(Here's another one in case: http://androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2
..and also... http://www.theandroidsoul.com/update-galaxy-nexus-to-android-4-0-4-using-odindownload-mode)
Make sure you download and flash the right firmware image. International devices aka (maguro) use "yakju" and the USA ones like (toro,toroplus) use "mysid", I think "takju" is for engineer samples. By flashing this you'll temporarily downgrade back to 4.3, but then you can boot, download a new ROM. Forewarning, this will reformat the entire device but is probably the last reasonable option at this point.
Update to original problem: 'System hangs at the end of boot sequence when it says "starting apps" or "finishing boot".'
I ran into this problem finally, again, and I'm pretty sure that what's causing it are incorrect/misconfigured permissions on the /data/data/* directories for each data app. This is likely caused by dirty flash upgrading or incorrectly fixing the permissions. TWRP "fix permissions" might cause this too or fix the problem, seems like a gamble each time, so use with caution as a last resort attempt to fix a non booting android with this problem.
The best thing to do is restore the /data partition from a previous back up point. There's no easy fix for this, but there is a script you can run to try and reset the permissions and fix the "end of boot hang" issue. It's similar to the one TWRP uses.
7175 said:
Update to original problem: 'System hangs at the end of boot sequence when it says "starting apps" or "finishing boot".'
I ran into this problem finally, again, and I'm pretty sure that what's causing it are incorrect/misconfigured permissions on the /data/data/* directories for each data app. This is likely caused by dirty flash upgrading or incorrectly fixing the permissions. TWRP "fix permissions" might cause this too or fix the problem, seems like a gamble each time, so use with caution as a last resort attempt to fix a non booting android with this problem.
The best thing to do is restore the /data partition from a previous back up point. There's no easy fix for this, but there is a script you can run to try and reset the permissions and fix the "end of boot hang" issue. It's similar to the one TWRP uses.
Click to expand...
Click to collapse
How do I use this? Sorry. I probably need some steps for this :|
Hi shencez, does your problem still persist with the boot hanging? If only you could get to adb, we could totally fix this.
Anyway, for anybody wanting to run this, here's generally what to do:
The script needs to be downloaded or pushed via adb to android:
> adb push "windows or Linux path to file" "path_to_android_directory"
(e.g.: adb push C:\fix_permissions /fix_permissions)
Then make sure it's executable with:
> busybox chmod +rx
/path_to_android_directory/fix_permissions
(e.g.: busybox chmod +rx /fix_permissions)
The script uses /sbin/sh, so make sure that exists or do:
> cp -a /system/bin/mksh /sbin/sh
Execution:
> /path_to_android_directory/fix_permissions
(e.g.: /fix_permissions)
You should get an output like this:
./fix_permissions.sh 2.04 started at 08-10-2014 13:01:04
./fix_permissions.sh 2.04 ended at 08-10-2014 13:01:04 (Runtime:0m0s)
Hi i have same problem with samsung galaxy s6 it stuck with rotating gears i already posted this in a few places so hope so someone can help
Thanks in advance
I think busybox problem, trying to restore and stuck somewhere, best is flash official rom
hey i have the same problem. My galaxy s4 goes into an infinite boot cycle at the "android is upgrading optimizing apps" screen. Every so often it will finish the boot and go to the lockscreen but I can't remember my pin code After it gets to the lockscreen for 10 seconds it turns off and goes back into its infinite boot cycle. Please help me solve this problem! P.S I can't boot into safe mode for some reason. Whenever I try to the phone turns off before it boots.
Without working volume+ button you can flash stock using Odin. To boot in odin mode press power and volume - button.
Hey i know its late but
7175 said:
Hi shencez, does your problem still persist with the boot hanging? If only you could get to adb, we could totally fix this.
Anyway, for anybody wanting to run this, here's generally what to do:
The script needs to be downloaded or pushed via adb to android:
> adb push "windows or Linux path to file" "path_to_android_directory"
(e.g.: adb push C:\fix_permissions /fix_permissions)
Then make sure it's executable with:
> busybox chmod +rx
/path_to_android_directory/fix_permissions
(e.g.: busybox chmod +rx /fix_permissions)
The script uses /sbin/sh, so make sure that exists or do:
> cp -a /system/bin/mksh /sbin/sh
Execution:
> /path_to_android_directory/fix_permissions
(e.g.: /fix_permissions)
You should get an output like this:
./fix_permissions.sh 2.04 started at 08-10-2014 13:01:04
./fix_permissions.sh 2.04 ended at 08-10-2014 13:01:04 (Runtime:0m0s)
Click to expand...
Click to collapse
hey I know this is late but my note 4 keeps starting and saying android is upgrading optimizing apps 1 of 17 and gets stuck at 5 or any other number and restarts and some times it just completely turns of and I was wondering if their is a fix for this and I tried everything I could think of and also tried everything I found on the internet but it just wont work. Thank you in advance
Thanks a lot 7175! ))))))))
i ran into the same issue with a HTC Desire 10 pro and tried the recovery mode and it brought the device back to the normal home screen. Thnkxxxx
7175 said:
I understand your frustration, this happened to me a couple months ago after doing a custom update. I don't remember the exact solution, but I have some solid ideas. First we have to get into recovery.
Hold volume up + volume down + power to do this. (Using one volume and power just goes to Odin download mode / last resort of last resorts)
When you're in recovery, do a nandroid backup since well be trying a bunch of stuff, permission fixing, formatting.
After a nandroid try:
-fix permissions through recovery
-wipe cache and dalvik cache through recovery
If those don't boot you, try wiping data (NOT sdcard). If this doesn't work the problem is what's installed to /system..and we'll go from here.
We need to get into recovery first and sequentially try the things I listed. Let me know if this is now possible.
Click to expand...
Click to collapse
yesterday i unlocked the bootloader, and used ADB and FASTBOOT to flash TWRP 3.0.2 and then rooted by flashing superSU v2.76
the phone was still S-on
i attempted to modify the buildprop file and used TWRP to mount system and copy the file over to /system/
i did have other things ticked as being mounted, like /data and one other partition that escapes me now.
anyway, i copied the buildprop back and used CHMOD755 but thought choosing 644 would be better so i choose CHMOD but entered 0644 as it was asking for 4 characters. after hitting boot system the phone just went black, trying to boot into bootloader mode now doesn't work, nothing happens. the only way i get any sign of life out of the phone now is by holding volume up and power. then the phone will boot for about 5 to 6 secs before going black screened again.
so i can't boot, cant enter recovery or bootloader.
usb debuggung was ticked previously but i'm not sure i even have a working rom now. ADB fails to find a device and trying
Code:
abd reboot bootloader
just brings
Code:
error: device '(null)' not found
am i totally screwed ? or is this something i can fix ???
help needed...
Connect to PC so you can hear connect/disconnect sound.
Press & hold power + volume up buttons to force reboot, once you hear the disconnect sound on PC, release both buttons and quickly press & hold volume down button. This will take you to hboot, select recovery and restore your backup or install ROM zip
ckpv5 said:
Connect to PC so you can hear connect/disconnect sound.
Press & hold power + volume up buttons to force reboot, once you hear the disconnect sound on PC, release both buttons and quickly press & hold volume down button. This will take you to hboot, select recovery and restore your backup or install ROM zip
Click to expand...
Click to collapse
connecting up to PC i don't get any "bing bong" sounds at all. if i try booting with volume up and power while connected to PC i still don't get the bing bong, quickly switching to holding volume down as you suggest doesn't stop the phone going back to black screen.
HEEEEELLLLP !!!!!
EDIT: additional info
the phone has been this way for a few hours now and twice in that time the phone has started booting up by itself (without me touching it), only to go back off again the same as every other time...
EDIT: after leaving the phone to go nuts all by itself and let the battery run down and recharging it, I was able to get back into bootloader mode and recovery to restore a backup.
I am now happily running GPe MM, and about to test out ElementalX
This is for the Galaxy S20+ Exynos. I tried restoring from backups in TWRP. The phone is stuck in a boot loop. I tried pressing the volume up/power button to get into recovery but nothing happens. At what exact point should I do it? I also tried pressing the volume down/power button to get it to shut off but it didn't work. I tried connecting it to my computer and running adb. ADB devices lists it, but I can't run any other commands as it says it's unauthorized.
Got into TWRP The button combination didn't work at first, but if I had the USB cable plugged into the phone and computer then it could restart to recovery.
Once in TWRP do a factory reset by wiping data, cache and dalvik.
Out of curiosity does anyone know why Samsung phones sometimes can't get into certain modes without things plugged into its USB?
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.