Develop Bugs

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.

Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.

ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.

Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.

Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!

hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.

Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.

c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.

Accidental double post, sorry.

You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.

Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.

Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.

http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.

If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.

I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.

http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .

Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.

Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...

The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .

Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....

Gnex: bricked or dead? Please help.

Hey guys, I just inherited a non-functioning gnex. The previous owner said the phone was working fine until it fell of a ledge whilst in a bag. There is no obvious physical damage to the phone chassis or screen.
When I try to power on the phone, it vibrates once but nothing further seems to happen and the screen stays black. Several minutes later though, it starts making some of the android system noises seemingly at a random. If I press either of the volume buttons, it makes the standard volume up or volume down ringer noise. But nothing else really happens other than a continuation of some of the system noises. Sometimes it seems to load a media file or a game once the phone has been powered on with the battery in. When connected to a windows machine, the device mounts and the contents of the phone are uncorrupted.
I've tried different combinations of the power buttons+volume rockers to get into recovery or fastboot, but so far no luck.
I've also tried the OMAP flash but can't get the computer to recognize the phone as a omap4460 for more than a couple of seconds. I've tried the Samsung drivers and the universal naked driver.
The only thing I haven't tried is ODIN (which I'm assuming won't work without being able to enter fastboot or recovery?), which might be last act of desperation before giving up. I'll update accordingly.
Any other suggestions would be greatly appreciated.

I think you have a damaged screen.
try to put phone in odin mode, pull battery out, reinsert it, press volume down with power button for 3 seconds, connect to pc, open odin, see if odin recognize your phone.

Yep it sound like everything is working except for screen. You can try to open it to disconnect and reconnect the screen: http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/1 (not sure exactly how) if it doesn't work you can order a replacement screen (eBay or such) and do it yourself (expensive and not easy) or give it to a repair shop (expensive but easy).

Sounds like it's a damaged LCD, not cheap...
I'd buy it off you if its the vz nexus (For parts.)

Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.

horseycraze said:
Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.
Click to expand...
Click to collapse
I'd recommend fastboot. Same thing, less steps, though you will need adb...
(If its available for your model, if not odin would be your only choice. )
Odin has a few more steps...
Long story short you wouldn't know if the screen is dead sadly, with out a replacement, best of luck!

Any insight on how to get into ADB or fastboot? As stated in the OP, the power button combos don't work. Furthermore, I don't have a way of enabling debugging mode.
I still haven't tried Odin, I won't have access to a windows pc for a few more days. I'll update accordingly.

Getting into fastboot is very easy:
Turn off. Since you can't see anything pull battery and reinsert to make sure.
Press volume up, volume down and power at the same time for few seconds.
You feel a vibration like it does on every boot.
That's it, you are in fastboot mode.
To verify, plug into computer and type fastboot devices
If it writes something like this:
0149BD34ABCDABCD fastboot
then you are in fastboot mode.
If it doesn't work, check the drivers. Remember that you need to install the drivers once for every mode (in Windows). fastboot? drivers. MTP? drivers. ADB? drivers. ADB in custom recovery? drivers. Download mode? drivers. OMAPFlash? drivers again. And different modes have different drivers too.

Stuck on 'Android is upgrading... Starting Apps'. HELP

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

[Q] Battery went to 0% now stuck on firmware update screen LG G3 (D855)

Hi!
I would need some help with my LG G3.
Last night my phone went to 0% battery because I didn't put it onto the charger. Before it was working fine, I didn't make any modifications to it.
This morning I plugged it into the charger (so not into a computer), and it shows a screen: " Firmware update. Do not unplug the USB connection until the process is complete*. 0% (it hasn't moved since). There is also a box on the bottom saying: 910K B1. It is a European 16GB model.
It doesn't respond when I press the on/off button. Should I try removing the battery?
I haven't touched it since I put it onto the charger because I don't want to damage it or something, so I would be very grateful for any help.
Thanks.

My guess would be that there was some kind of flashing program running on your computer. The program rebooted your phone into download mode and is now trying to flash a file onto your G3. If you unplugged your phone fast enough you could just try rebooting, otherwise there is a possibility the program already prepared to flash the file onto your phone and now you have a 910K B1 (??) firmware on your phone.
If your phone isn't booting anymore I suggest flashing the right kdz/tot file on your phone. Good luck.

Madi4 said:
Hi!
I would need some help with my LG G3.
Last night my phone went to 0% battery because I didn't put it onto the charger. Before it was working fine, I didn't make any modifications to it.
This morning I plugged it into the charger (so not into a computer), and it shows a screen: " Firmware update. Do not unplug the USB connection until the process is complete*. 0% (it hasn't moved since). There is also a box on the bottom saying: 910K B1. It is a European 16GB model.
It doesn't respond when I press the on/off button. Should I try removing the battery?
I haven't touched it since I put it onto the charger because I don't want to damage it or something, so I would be very grateful for any help.
Thanks.
Click to expand...
Click to collapse
The only way out of download mode seems to be pulling the battery, so that should be okay. It sounds like you just accidentally held Volume Up when you plugged it up and tricked it into download mode so hopefully a battery pull will reset it. Let me know if the issue persists after a battery pull. If that's the case, it may need to be restored to stock.
---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------
sprremix said:
My guess would be that there was some kind of flashing program running on your computer. The program rebooted your phone into download mode and is now trying to flash a file onto your G3. If you unplugged your phone fast enough you could just try rebooting, otherwise there is a possibility the program already prepared to flash the file onto your phone and now you have a 910K B1 (??) firmware on your phone.
If your phone isn't booting anymore I suggest flashing the right kdz/tot file on your phone. Good luck.
Click to expand...
Click to collapse
He said in the OP that he plugged it into a charger not a computer so that can't be the case.

acparker18 said:
The only way out of download mode seems to be pulling the battery, so that should be okay. It sounds like you just accidentally held Volume Up when you plugged it up and tricked it into download mode so hopefully a battery pull will reset it. Let me know if the issue persists after a battery pull. If that's the case, it may need to be restored to stock.
---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------
He said in the OP that he plugged it into a charger not a computer so that can't be the case.
Click to expand...
Click to collapse
Oh darn yeah, I read "into a computer". Disregard my message indeed.
OP also states that the bottom reads "bottom saying: 910K B1". I don't have my phone on me right now, but doesn't Download Mode state nothing at the bottom? Only when you use a flashing tool? I could be wrong though.

Thank you, pulling the battery helped, at first it didn't recognise the sd but taking it out and putting it back helped.
It seems to work fine now. And by the way sorry, I just had a pretty rough night out and was a bit scared of what could have happened to my phone
If anything unusual happens I'll keep you updated but really thank you

Ok so, everything works fine except when I plug it into my computer it doesn't recognise the phone anymore, it just says unknown device.
I tried installing the driver and LG PC Suite, neither of them helped.
The usual options on the phone doesn't appear (media share, charging only), it is simply just charging.

Hey so I have had the exact same problem as listed above except when I pull my battery out and tried leaving it out for a minute or two then putting it back and it's just bringing me back to being stuck on the firmware screen. Is there anything I can do to fix this?

Hold down the volume up button when turning on for a few seconds, worked for me

firmware update... do not unplug.. i did not unplug for 5 hrs and still at 0% on downloading.
this is a small lg phone w no way i can tell how to pull battery

Another Resolution...
Hi, I have decided to add another resolution you can do if none of the above resolutions work (like they didn't for me).
Some other sites suggest you should factory reset your phone, however I do not suggest this unless nothing else works.
What worked for me was just holding down the power and volume down button and quickly pressing it again when the LG Logo pops up, and instead of saying yes to factory reset, just put no and the phone should then boot up as usual without the firmware update.
Hope this helps

My LG GadF8.0 does the same thing...but sadly It has a non-removable battery. So what do I do then?
---------- Post added at 08:28 AM ---------- Previous post was at 08:04 AM ----------
Madi4 said:
Hi!
I would need some help with my LG G3.
Last night my phone went to 0% battery because I didn't put it onto the charger. Before it was working fine, I didn't make any modifications to it.
This morning I plugged it into the charger (so not into a computer), and it shows a screen: " Firmware update. Do not unplug the USB connection until the process is complete*. 0% (it hasn't moved since). There is also a box on the bottom saying: 910K B1. It is a European 16GB model.
It doesn't respond when I press the on/off button. Should I try removing the battery?
I haven't touched it since I put it onto the charger because I don't want to damage it or something, so I would be very grateful for any help.
Thanks.
Click to expand...
Click to collapse
Try unplugging your phone then turning on.

did we figure the normality of the 901K B1 -- asking because of the "901K B7" on my phone (after a few previously sketchy occurrences & me having it on charger not having held volume up). Thanks.

Solution
Press the volume up and down button same time 3 times and it brings you to this screen and you have to press the power up and down than hold the power button for 1 or 2 seconds and release but go over to power off hold it than it says you sure hold power button on yes once off power back on

Hi I have a similar problem, despite being in the same loading mode, mine is like this after I put it on the pc What should I do to fix this?

Vidius99 said:
Another Resolution...
Hi, I have decided to add another resolution you can do if none of the above resolutions work (like they didn't for me).
Some other sites suggest you should factory reset your phone, however I do not suggest this unless nothing else works.
What worked for me was just holding down the power and volume down button and quickly pressing it again when the LG Logo pops up, and instead of saying yes to factory reset, just put no and the phone should then boot up as usual without the firmware update.
Hope this helps
Click to expand...
Click to collapse
thank you very much, you saved my phone
{
"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"
}

Vidius99 said:
Another Resolution...
Hi, I have decided to add another resolution you can do if none of the above resolutions work (like they didn't for me).
Some other sites suggest you should factory reset your phone, however I do not suggest this unless nothing else works.
What worked for me was just holding down the power and volume down button and quickly pressing it again when the LG Logo pops up, and instead of saying yes to factory reset, just put no and the phone should then boot up as usual without the firmware update.
Hope this helps
Click to expand...
Click to collapse
this worked. on my lg q6+ the screen appeared on plugging into a pc on linux. this helped somewhat, as the power button itself was not responsive, but the power and vol down button combo restarted the phone promptly. i didnt take any further action, and the phone rebooted normally. thanks.

Question Bricked my Prixel 6 after flashing stock rom

Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks

Call whoever you bought the phone from and do warranty claim.

I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.

Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?

cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.

From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.

Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools

Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.

What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...

roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits

ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.

If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.

pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.

rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.

@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.

ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.

same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?

Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....

Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.

roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears