Related
This morning in my half-awake state I accidentally pressed "OK" to my phone asking me to go ahead with the (I'm guessing) 2.3.6 update. I KNEW I would end up doing something stupid like that. GRR!!
Anyway, the phone then launched itself into a white screen with blue text saying that it is doing the update, but nothing happens and it appears to be frozen.
I am rooted and was trying to avoid this update; like I said, I was half-awake.
I can't even get it to boot into download/recovery mode, it always goes straight to the white screen. Hopefully this isn't a double post; I checked here and google first but couldn't find anything for this phone. I'm really at a loss here. I have Titanium Backup and I got an external SD card, but I'm not sure if I actually backed up the apps to the external card (new to TB). I did a Kies contacts backup a few days ago so that at least is safe.
Is there any hope for my phone? If I can just get it back to a working state, I can live with my apps' data being erased. Any help appreciated.
Thank you!
Doh... sorry to hear that.. are you also running a custom rom, or customized ATT rom (I have the stock rom from the developers forums over the standard root after having tried a few custom roms).
I got the update message as well this morning, but I postponed it for 8 hours, however I am unable to get rid of the stupid notification, and am curious if after the 8 hours, it will force the update or let me postpone it agian (that will get annoying fast if I cannot disable the OTA update..)
I'd like to know how to cancel the update as well. I have it sitting in my notification bar. >_<
jvanbrecht said:
Doh... sorry to hear that.. are you also running a custom rom, or customized ATT rom (I have the stock rom from the developers forums over the standard root after having tried a few custom roms).
Click to expand...
Click to collapse
I'm still running stock 2.3.5. All I've had time to do is root and TB apps, haven't had the chance to play around with ROMs yet for this phone.
Yeah I postponed it for 8 hours, too. The 8hrs must have expired right as my alarm went off because the "Install this update?" message popped up and I hit it, thinking it was the snooze button -_-
Let me know if there's any way to get off of this screen my phone is stuck on! And then disable the obnoxious message for good.
Thanks again =)
Maybe try to remove battery.
lyndone58 said:
Maybe try to remove battery.
Click to expand...
Click to collapse
I have about 10-15 times since it first happened this morning. I also tried taking out the SIM and microSD cards. It's the only way I can get it to stay off to try to boot to recovery mode (which it still won't boot into); if I hold the power button to turn it off it just resets back into the white Software Update Screen (won't stay off).
Has anyone successfully applied this update yet?
Any other ideas? I appreciate the feedback so far!
Similar thing happened to me. I pulled the battery and booted in to CWM just fine. Restored from there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I don't believe I have CWM installed? How would I have known if I did? When I volume up + volume down + power and wait until the Samsung logo comes up it boots back to the white screen. Maybe I'm doing that process wrong?
Same thing happened to me this morning!
almost identical story
I've tried literally every combination to get to the reboot screen. ugh :'(
mrl3086 said:
I have about 10-15 times since it first happened this morning. I also tried taking out the SIM and microSD cards. It's the only way I can get it to stay off to try to boot to recovery mode (which it still won't boot into); if I hold the power button to turn it off it just resets back into the white Software Update Screen (won't stay off).
Has anyone successfully applied this update yet?
Any other ideas? I appreciate the feedback so far!
Click to expand...
Click to collapse
I haven't been rooting as much as some of the guys here, but I think if you take the battery out and it won't boot back even into recovery, you're hard-bricked and you're gonna have to start from scratch with a fresh stock rom. Go to download mode (turn off, hold vol up + down, insert powered usb cable) and put a stock rom back on using odin.
http://forum.xda-developers.com/showthread.php?t=1342348
You will basically get back to what your phone was when you took it out of the box and you'll have to install everything, your data (other than the data that is on a microSD card) won't be there.
If you have a backup that you did with CWM, then you can restore the backup after you do all this.
I think you got unlucky with the worst case scenario of what shouldn't happen during an update.
Thanks for the advice. I'll give it a try when I get home from work and will let you guys know how it goes.
For the future, is it generally recommended to de-root before doing any straight carrier update? Or is this just a total fluke that some of us are experiencing?
Will adb recognize your phone? If it does just adb reboot recovery
Sent from my SAMSUNG-SGH-I727 using xda premium
Lucidmike said:
I haven't been rooting as much as some of the guys here, but I think if you take the battery out and it won't boot back even into recovery, you're hard-bricked and you're gonna have to start from scratch with a fresh stock rom. Go to download mode (turn off, hold vol up + down, insert powered usb cable) and put a stock rom back on using odin.
http://forum.xda-developers.com/showthread.php?t=1342348
You will basically get back to what your phone was when you took it out of the box and you'll have to install everything, your data (other than the data that is on a microSD card) won't be there.
If you have a backup that you did with CWM, then you can restore the backup after you do all this.
I think you got unlucky with the worst case scenario of what shouldn't happen during an update.
Click to expand...
Click to collapse
AMAZING!! Thank you so much! Not only is my phone up and working but the update has installed!
I learned the following:
-you pretty much need a pc (not a mac) to do all the downloads correctly. I used a friends.
-to get your phone into download mode when it's frozen from the update, you have to hold down either vol + AND vol - (or just vol -) as well as the power button, simultaneously hold down power and also simultaneously plug in the usb. Then let go of the power button and remain holding down one or the two volume buttons.
THIS WAS JUST WITH MY SKYROCKET EXPERIENCE
I'm so happy. Thank you LucidMike
This just happened to my friend's phone. White screen no matter what. Stock everything, too. She's pretty bummed that there's no way to recover the videos and pictures on her phone before resetting it. Apparently she went to AT&T and they couldn't figure it out. They called tech support for her and THEY couldn't figure it out. She's currently on the phone with Samsung, but I doubt they'll be able to help either.
viralriot said:
This just happened to my friend's phone. White screen no matter what. Stock everything, too. She's pretty bummed that there's no way to recover the videos and pictures on her phone before resetting it. Apparently she went to AT&T and they couldn't figure it out. They called tech support for her and THEY couldn't figure it out. She's currently on the phone with Samsung, but I doubt they'll be able to help either.
Click to expand...
Click to collapse
AHHH!! Tell her to hang up the phone right now!! Use this method to fix her phone!! All of her data will still be there after it's done! After the process is complete, back it up to a computer (enable USB storage and just copy + paste and I used Kies to copy my contacts) and THEN do a full factory reset (reset recommended by everyone to ensure smooth function of phone). The method in the link will return her to the original stock version; I believe it may trip a counter that AT&T can use to determine if you've hacked your phone, but if you want a working phone...and there's also a chance that it WON'T trip the counter (some people say it did and some say it hasn't).
EDIT: Pictures and videos that I took with the phone are saved in /sdcard/DCIM/Camera, so you know where to copy her stuff from.
jessielooloo said:
AMAZING!! Thank you so much! Not only is my phone up and working but the update has installed!
I learned the following:
-you pretty much need a pc (not a mac) to do all the downloads correctly. I used a friends.
-to get your phone into download mode when it's frozen from the update, you have to hold down either vol + AND vol - (or just vol -) as well as the power button, simultaneously hold down power and also simultaneously plug in the usb. Then let go of the power button and remain holding down one or the two volume buttons.
THIS WAS JUST WITH MY SKYROCKET EXPERIENCE
I'm so happy. Thank you LucidMike
Click to expand...
Click to collapse
I'm trying to fix my boyfriend's phone (he actually didn't hack/root it or anything...but yesterday's update messed up his phone so it was stuck in the "SOFTWARE UPDATE" and "Loading..." frozen white screen). We tried taking out the battery, restarting it, everything. I tried your method of holding all three buttons while plugging in the USB and then letting go of the power button. What do you press when it asks you if you want to continue (up vol +) or cancel (vol -)? I chose vol -, and when it took me back to the white screen, I did it again and pressed vol +. Now I'm on a ODIN MODE page...will this affect his warranty or anything? What do I do next?
You need to have odin on your pc and the stock .tar and flash it. Here go here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1509978
Read carefully follow directions exactly
silver03wrx said:
You need to have odin on your pc and the stock .tar and flash it. Here go here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1509978
Read carefully follow directions exactly
Click to expand...
Click to collapse
Thanks! I read on the first page of the thread that it needs to be rooted though? This phone is brand new and never been rooted or hacked...will doing this void the warranty or anything unpleasant? (I'm the one that likes hacking my devices like my Nook Color...my boyfriend is a little more paranoid and would rather have it stay covered under warranty )
No actually. Thats incorrect..the stock tar. Is just as it sounds. The stock firmware the phone comes with.....dont need to be rooted to use odin. Actually if u odn the stock tar. It removes root.
mrl3086 said:
AHHH!! Tell her to hang up the phone right now!! Use this method to fix her phone!! All of her data will still be there after it's done! After the process is complete, back it up to a computer (enable USB storage and just copy + paste and I used Kies to copy my contacts) and THEN do a full factory reset (reset recommended by everyone to ensure smooth function of phone). The method in the link will return her to the original stock version; I believe it may trip a counter that AT&T can use to determine if you've hacked your phone, but if you want a working phone...and there's also a chance that it WON'T trip the counter (some people say it did and some say it hasn't).
EDIT: Pictures and videos that I took with the phone are saved in /sdcard/DCIM/Camera, so you know where to copy her stuff from.
Click to expand...
Click to collapse
Tried doing this, but this is all I get.
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/006> Added!!
That's it. Nothing else happens. Help?
EDIT: Nevermind! Plugged it into a different USB port (COM:6) and it worked flawlessly. All data is still on phone and it works like new! Thank you!
Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
roninb30 said:
Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Click to expand...
Click to collapse
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Russbad said:
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
Click to expand...
Click to collapse
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Click to expand...
Click to collapse
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Is it possible that I need a pit file for the device since no version of Odin will get past initialization? ....if so where can I get one for the this model?
roninb30 said:
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Click to expand...
Click to collapse
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
rkirmeier said:
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
Click to expand...
Click to collapse
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Huge 3rd.
Device should just plain WORK out of the box. There shouldn't have been a need to flash stock to begin with.
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Android.Ninja said:
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica....then again for it to come back. Just wanted to do everything I could before I had to send it. Thanks for the input though. I guess I learned quite a bit researching processes and terminology which will be helpful in the future. ^-^
Russbad said:
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Click to expand...
Click to collapse
Tried many times. The device pretty much gives me the finger by going blank and repeatedly showing the boot up logo when I hold the buttons down.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root.
Click to expand...
Click to collapse
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
roninb30 said:
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica
Click to expand...
Click to collapse
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
ExtremeRyno said:
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
Click to expand...
Click to collapse
After doing research, I think that even if I get a new one, I want to root it. With the problems I've read about for kitkat 4.4.2 I need to know how to fix problems, and start with a fresh install of roms and know how to use custom recovery. I haven't done anything yet, but I was wondering...
Since I'm stuck in a boot loop with no stock recovery, can I flash a custom recovery to fix my issues, flash the stock rom that is on sammobile.com and then root after that? From what I understand this is a soft brick since I can still sometimes access the device. I worked out why I couldn't access the device with adb and now it shows the device as listed. It stays on long enough to where I could flash a recovery before it restarts itself. I'm not trying to do anything stupid, just getting information before I pay the shipping for it back to the states. I've checked the knox counter in download mode, and it is still set to 0, so I haven't voided the warranty yet.
Any input would be greatly appreciated.
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Russbad said:
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Click to expand...
Click to collapse
I understand the skepticism. Yeah, I tried the button combination, usb in, usb out. I can power off the device completely only when it is plugged into power. When I hold the recovery combo from power on, the screen goes black with no flashing of the boot logo, looks as if it wants to go to recovery, and then then the boot logo comes up again, but just continues to the boot animation and continues the boot loop, even if i'm still holding down volume up and home buttons. It will sometimes boot up, then freeze after a couple of seconds, and return to boot loop. On rare occasions it will boot up, but turns me to setup like it's a brand new device. I can access everything for about 10 minutes, and then it will randomly restart and continue to boot loop again after that. I tried update/initialization in kies, but it would restart before the downloading and decompressing of binary could finish. It finished one time and then switch to a downloading screen (although it didn't say odin since you have to manually go there) but the update would freeze at 0 percent no matter how long I left the device there. It's all pretty lame ><
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
meat-rack said:
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
Click to expand...
Click to collapse
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
bweN diorD said:
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
Click to expand...
Click to collapse
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Slickville said:
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Click to expand...
Click to collapse
i wish i could help you but without knowing exactly what the ota flashed before failing, any advice i give has the real possibility of making your phone worse or possibly perma bricked. the problem is you are locked and we dont yet have a fxz for kk.
that being said, if you still want to try and fix it against my advice i will tell you what to try but I AM NOT RESPONSIBLE IF THIS BRICKS YOUR PHONE OR MAKES IT WORSE IN ANY WAY.
download this xml file http://www.mediafire.com/view/p217akcxwmijcr7/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC_DOWN.xml
download the 9.30.1 ota from sbf droid devs
extract it to a folder and DELETE the xml file, then copy the one above into the folder
make sure you have the latest rsd, i think its 6.1.5 (not positive)
load the xml file into rsd and flash as usual
if this does not work, there is no way to fix your phone until the kk fxz is leaked, assuming this doesnt make it worse.
6.1.6 is the newest RSDLite I've seen.
Go here if you haven't applied the OTA yet and your bootloader is locked.
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
If you have applied the OTA and you're locked, don't do it. You'll have to wait for the FXZ to come out. Otherwise, it will brick even further.
If you have applied the OTA AND your bootloader is UNLOCKED, then you can use the tool to flash back to stock 9.30.1.
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Grimaldus3320 said:
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Click to expand...
Click to collapse
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
iBolski said:
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
Click to expand...
Click to collapse
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Grimaldus3320 said:
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Click to expand...
Click to collapse
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
iBolski said:
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
Click to expand...
Click to collapse
I see, makes sense. Every days a school day I suppose. Thanks for the info. Guess I have to decide to either wait for the FXZ or go to verizon and see if they can get me a new phone.
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
al2fast said:
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
Click to expand...
Click to collapse
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
iBolski said:
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
Click to expand...
Click to collapse
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
al2fast said:
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
Click to expand...
Click to collapse
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
iBolski said:
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
Click to expand...
Click to collapse
Thanks for the tips. I must have done something wrong when I installed adb, I could not see the phone with the adb devices command, yet I could see the phone in the Matt utility as well as in RSD Lite. I'll give it a shot again, can't hurt. Called Moto and they escalated it and are sending me a replacement device.
So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.
Macrophage001 said:
So I've had my htc one s for about 2 years or so now and this problem has started happening rather recently. No matter what I try, I cannot access the recovery menu.
I've tried:
1.Hardware Keys (Going into bootloader and trying the recovery from there) = no go.
2.App that would allow me to reboot to recovery = no go
3.Installing another recovery to see if that would help = no go
I've also tried the method of erasing the cache through fastboot to no avail.
I'm currently running a really outdated version of cyanogenmod (10.1 i believe) and my phone is now currently stuck at the beginning trying to boot up.
I'm not sure what else I can try. Oh and another thing. It seems like when I tried to install another recovery image, it didn't overwrite what was already there and so now I believe that my phone currently has to recovery menus.
I've already searched through the forums looking for help and while some of the threads that I found came close, none of them except for the erasing of the cache one came close to helping me figure out what was going on.
Please help.
Click to expand...
Click to collapse
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.
tivofool said:
You can get into bootloader, so just relock it and run an RUU.
Then you can go through the steps of unlocking, installing a recovery and ROM again.
Click to expand...
Click to collapse
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.
Macrophage001 said:
Ah ok, I'm going to try that. The problem now is that my phone won't boot up and my volume down button doesn't work. It just stays at the portion of boot up with the cyanogenmod logo. I guess my only option now is wait until my phone dies for it to turn off since it won't stay off by simply shutting it down.
Click to expand...
Click to collapse
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.
tivofool said:
If you mean your volume down is physically broken, then yikes you might be in trouble. Might have to watch a video on youtube to learn to take it apart and fix/clean the rocker contact.
If you mean it isn't working because of the boot loop, ok. If you hold power down for like 10 seconds it should reset and then you hold down volume down to get to bootloader.
Click to expand...
Click to collapse
Yeah I meant it's actually physically broken. I was hoping that wouldn't be the case but it seems like I'm going to have to find out how to take my phone apart.
Thanks for the help.
Okay, so! Greetings all.
Back about a month ago, I successfully rooted my phone with KingoRoot, flashed TWRP 2.8.0, and installed Crdroid 7.1 Nougat for my D850.
Now, everything was fine and well, besides being one of the very unlucky users to have their phone stop being a beautiful piece of technology and, instead, become very burdensome and aggravating. It would require a battery pull, sometimes two times back to back (if it would soft reset on first pull and get stuck in boot loop), about once or twice every 3 hours, to as often as a few times an hour.
So, I tried something new. I went back to LineageOS' website and looked through the other D850 releases(all of what, 3?) and settled on the AOSP 7.1 ROM.It seemed like it'd be a great idea, having everything functioning and not having to deal with battery pulls every day. Now my phone is practically nonfunctional, as it doesn't receive cell service and can't read SIM cards.
Needed Information:
-Phone is an LG D850, running a (nonfunctional) custom AOSP 7.1 ROM
-Phone seems to lack root access, and can't be One-Click rooted as is (Haven't been successful with any one click program yet)
-Phone is also lacking in recovery (Tried to access via adb, manual hard buttons, and neither worked)
Now for the actual question: What can I do to make my phone function again, whether I have to reinstall my backup of my previous fail (thus requiring TWRP and root) or just get it back to a truly stock ROM?
Thank you all for your time and consideration. I'll check back in the morning.
Warning: I am no expert, in fact I'm barely a noob, but one thing I do well, and that is I always do a backup. That being said it appears there are two paths to salvation. Get your recovery working or go back to stock. If you installed a recovery but can't get back to it try shutting off phone then pressing power and volume down simultaneously. When logo appears release buttons and then immediately press both again. It will offer a decision screen where you use vol up/down to select. Choose yes on both, (it will not reset the phone as indicated). This should get you into recovery, from there you may be able to flash the needed rom, gapps, root, etc. My suggestion is to load the needed files onto your sd card beforehand. If this fails there is the downgrade via LGUP. This is pretty nifty. I had to rely on the expertise of a Mr. Heyelton and his post, https://forum.xda-developers.com/showthread.php?t=2785089. To my knowledge the POS known as the AT&T d850 can only be rooted at KK. Mr. Heyelton's guide can get you there. from there you can stay with stock, upgrade to a higher stock (?) or proceed to root, TWRP and rom the phone. Don't forget to upgrade your modem, https://forum.xda-developers.com/att-lg-g3/general/modems-collection-d850-21r-20f-10d-t3213856.
alliance1975 said:
Warning: I am no expert, in fact I'm barely a noob, but one thing I do well, and that is I always do a backup. That being said it appears there are two paths to salvation. Get your recovery working or go back to stock. If you installed a recovery but can't get back to it try shutting off phone then pressing power and volume down simultaneously. When logo appears release buttons and then immediately press both again. It will offer a decision screen where you use vol up/down to select. Choose yes on both, (it will not reset the phone as indicated). This should get you into recovery, from there you may be able to flash the needed rom, gapps, root, etc. My suggestion is to load the needed files onto your sd card beforehand. If this fails there is the downgrade via LGUP. This is pretty nifty. I had to rely on the expertise of a Mr. Heyelton and his post, https://forum.xda-developers.com/showthread.php?t=2785089. To my knowledge the POS known as the AT&T d850 can only be rooted at KK. Mr. Heyelton's guide can get you there. from there you can stay with stock, upgrade to a higher stock (?) or proceed to root, TWRP and rom the phone. Don't forget to upgrade your modem, https://forum.xda-developers.com/att-lg-g3/general/modems-collection-d850-21r-20f-10d-t3213856.
Click to expand...
Click to collapse
Hey man. I wanted to say thanks for pointing me in the right direction. :good: :highfive: I managed to flash it back to stock, and I'll just figure out a different rom to go with. As far as fixing the issue with the recovery not coming up, I have no idea. It was just messed up, I guess. The phone wouldn't go to recovery even after selecting yes both times on the factory reset screen; it would just go black and a red+blue notification light would pop up. Was weird. Managed to get it to stock though, so it's better than it was. Thank you!