[Q] Problems with trying to update to 4.2.2 - Samsung Galaxy Nexus

I have a sprint phone and am trying to update my phone to 4.2.2. A few months ago when I first got the phone I had attempted to root it. Long story short, it totally didn't work (i accidentally installed verizon root), had to use odin to reinstall my radios and whatnot. In the end, I decided to just not root my phone.
However, I think i am screwing my phone up to the point that it won't update. Whenever I try to let it update, it goes into (what i imagine) is the recovery mode where it shows a picture of the android bot with a red alert sign as if there is an error. Furthermore, I went in to fastboot and tried to go to recovery but can't (it shows that same android with it's front open and an error sign on it).
I am not even sure where to start here. Any advice? I tried to reinstall my recovery using the nexus toolkit but that didn't work.:crying:

do this: http://forum.xda-developers.com/showthread.php?t=1626895

Related

[Q] Stuck on current ROM cant update or switch

Hi all
I unlocked and rooted my Galaxy Nexus (Verizon) phone months ago and recently have struck a very weird prob. I had been swapping ROMs for a while, when recently the phone bricked on a ROM switch and would not go past the loading part of any rom I tried. I used RootKit to flash it back to the manf. Rom and that seems to have worked. The problem is though that my phone can not update (to manufacturer jellybean update, It starts but then hits red triangle android) or even flash clockwork recovery image. Every time i try any Recovery installer it just freezes up and says the app is not responding. Additionally though I have rooted and unlocked the phone and have superuser app, root checker tells me my phone is not rooted.
Please help
Thank You
1) stop using toolkits. you have no idea what it is doing, and sounds like it didnt really root your phone
2) return your phone to stock with this: http://forum.xda-developers.com/showthread.php?t=1626895
3) root your phone with this: http://forum.xda-developers.com/showthread.php?t=1529058

[Q] Nexus 7 (2013) fails OTA update to 5.01 with Android Error

My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.

[Q] help - i think my phone is temporary bricked

hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)
Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though

S6 Edge+ (G928) t-mobile soft bricked after OTA upgrade to 6.0.1 while overseas HELP!

Hello, I managed to soft brick my phone while overseas and am writing this message at 2:00am in the morning (at least in this time zone) after two days of trying to fix it. Some background info--I'm usually based in the U.S., have a Samsung Galaxy S6 edge+ with service from T-mobile. Have never rooted or modified the phone in any way. I'm using a macbook pro laptop (running a windows virtual machine/vmware, on the mac) on this trip.
While on this current trip to Asia (currently in the Philippines) (much to my surprise it seems like the phone was getting 4G data here), I accidentally bumped the "yes" button on t-mobile's persistent OTA upgrade request box and the phone started a OTA upgrade, I assume to Android 6.0.1. I kept an eye on the phone as it went through various stages of progress in the upgrade. didn't see any error messages. It eventually restarted, got to the T-mobile screen, and got stuck there. That was two days ago. I've done quite a bit since that time to try to figure out what went wrong, searched all over online to find potential solutions. it goes without saying if there is any way possible i need to recover many important files on the device, so a reset is the option of last resort.
Long story short, seems like the farthest I can get on the phone is to Android Recovery mode, or the download screen. I installed the android tools and have "adb" working from the mac command line. Bad news is, it looks like I didn't have USB debugging mode activated on the phone, now I can't see any possible way to activate usb debug mode because the phone just won't boot past the t-mobile screen. I can get adb to detect the phone for a moment if I select "apply update from adb" on the recovery mode screen but that's about it, haven't been able to issue any other commands to the phone through adb other than detect and sideload.
tried to reload the android image...via command line adb sideload G928TUVU2DPD1 but get error messages about failure to verify (i think), anyways adb sideload wasn't happening. I installed Odin on my windows VM, attached the usb bridge from the mac to the windows vm and Odin was able to see the device. I was able to successfully push G928TUVU2DPD1 to the phone's download mode, both Odin and phone seemed happy about the file transfer, the phone went through a install process, restarted, with the exact same result as when the OTA update finished - phone stuck at the t-mobile screen after reboot.
I tried to load TWRP to the phone with hopes to run backups, and was actually able to transfer TWRP to the phone using Odin, yet TWRP wouldn't install -- the phone complained of the unauthorized binary. i guess the phone has to be rooted first or something else needs to be flashed to defeat the binary check, haven't tried that yet.
So I'm stuck with a soft bricked phone for now, yet instinct tells me with Odin working and talking to the phone, I should be able to install -something- that will get me back in business...that's why I'm posting this message, to ask for help as it seems like this group is the go to place for this type of specific info.
i am not at all familiar with custom android work yet have been active with tech stuff for the greater part of my life, plenty of coding and experience dating back years and have done dev work in most of the popular languages, very comfortable with command lines, log files and so forth...just never had a reason to mess around at a low level with my android phone until the past 48 hours, so i'm not really familiar. does anyone have any ideas? as a next step i'm thinking of trying to push a downgrade to the phone through Odin which I suppose would be Android 5.1.1 , although I haven't yet located binaries that feel exactly right for t-mobile and s6 edge+ ... sigh, this has been quite a time consuming way of learning the bricked phone recovery process..
:good:
thanks in advance for any ideas or help on this...it's quite disturbing to be on a business trip with no phone, and the past 6+ months worth of not backed up (gulp) data still sitting on the device (hopefully)..
here's some data from the Android Recovery screen:
6.0.1/MMB29K.G928TUVU2DPD1
samsung/zenltetmo/zenltetmo
was flipping through the recovery logs and i notice quite a few log entries about "couldn't find any tzdata when looking for localtime!" , I notice entries like "Starting recovery on Fri Jan 2 03:55:29 2015" -- i'm wondering if the phone is having trouble setting internal time and date which might be preventing it from booting...just a theory.
sorry for the long message, wanted to completely describe this fun scenario, just in case anyone has any ideas..thanks again
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
platinum5 said:
keep trying to load TWRP from the download screen on my phone...but get the "custom binary blocked by FTP lock" message. There's no way to change any settings on the phone as it still won't boot past the t-mobile screen..
Click to expand...
Click to collapse
Can you download Odin?
Sent from my SM-N910T using Tapatalk
yes i have installed Odin and it's working fine...I can push files to the phone in download mode and it works fine, but the Android images i have loaded so far all seem to result in the phone getting stuck at the t-mobile screen...it won't go past there
Did you ever get this figured out? My guess is it has something to do with not being connected to t-mobile home network. The fact you can get to download mode & Odin sees your phone should mean all hope is not lost yet on recovering your files and getting it working again.
Twrp isn't going to work unless you had root installed with the USB debugging & oem unlock option turned on in developer mode.
Maybe try asking in some of the other s6 forums. There's a lot of knowledgeable people here & I'm sure someone knows how to fix this.
Goodluck, I hope you get it figured out, I know how frustrating it can be.

Lg G3 Stuck in Recover Loop After Android Update Error

Okay, So let me start from the beginning so I'm certain I'm being descriptive enough.
The other night my G3's wifi stopped working. When I went to turn it on in settings it would turn itself back off. Which I thought was strange. So, I assumed it was a software issue so I backed up any important items and factory reset my phone last night. That went over fine. Wifi worked again, all was good. Until, it said it needed an Android Software Update. I hit "update" and allowed it to do its thing. About halfway through the update the phone said "error." With an icon of the Android bot with a hazard triangle sticking out from it. I let it be for a bit and nothing happened. So in my impatience I took the battery out and put it back in and tried to restart the phone. This is where the issue occurs. The phone keeps booting to recovery mode. I'm not savvy at all with Android so I don't know if these mean anything but it says "Android System Recovery <3e> LRX21Y" The phone has had zero modifications done to it. I would really appreciate any help or any tutorials that could save the phone until my g6 preorder comes in.
Thanks!
Kyle
Your phone failed the update for some weird reasons and is now stuck. I'm afraid you'll need to restore stock Android using LG Flash tools and KDZ files to your device. It will get your phone working, but you'll lose your data in the process.
You can try mounting the phone from recovery or download mode and see if you can access your data and backup the data. You can also try the recovery option without downloading wnloaing a KDZ first.
You can fins tutorials around the forum, in the general section usually.

Categories

Resources