Related
So my friend went to flash that lovely new JB ROM on his Verizon GNex; everything went fine through CWM like a normal ROM flash, and upon restarting the device to boot in to Android it just stuck at the Google logo. He left it for 10 minutes and nothing changed, so he did the following:
Pulled battery
Booted back in to CWM
Erased data/cache/etc.
Tried reflashing, same issue
Repeat with erasing data/etc.
Tried to restore Nandroid backup, greeted with corrupted error when it gets to restoring Data
Tried 3 other known good Nandroid backups, all fail at the same point
Tried just flashing known working ROMs like AOKP, same boot loop error after Google logo upon restart
Is he screwed? Does he just have to ODIN? If so how can he get stuff off the internal memory, as he has lots of pictures, music, etc. on there? Thanks!
Flashed a GSM Jellybean image to a verizon nexus?
...
IINexusII said:
Flashed a GSM Jellybean image to a verizon nexus?
...
Click to expand...
Click to collapse
No it's this one for the CDMA one:
http://forum.xda-developers.com/showthread.php?t=1738018
I flashed that ROM to my GNex and it is working like a charm.
No ideas, huh?
ive tried 3 times to get JB working on my verizon gnex as well
first time, got stuck on the new booting animation (the google X)
second time, was stuck on the google boot screen (same as your friend)
thrid time, im stuck on the google boot animation (the X) again
let me know if you find a solution please!
bkang4 said:
ive tried 3 times to get JB working on my verizon gnex as well
first time, got stuck on the new booting animation (the google X)
second time, was stuck on the google boot screen (same as your friend)
thrid time, im stuck on the google boot animation (the X) again
let me know if you find a solution please!
Click to expand...
Click to collapse
How long did you let yours sit on the X boot animation? Mine sat for probably about 10 minutes the first time and then finally booted into the OS.
I waited almost 20 minutes the first time
and right now i'm sitting at about 10 minutes =(
I don't understand whats going on, its not restarting the boot sequence (not going back to the google boot screen) but just keeps playing the boot animation
Flash the stock google image for verizon version:
https://developers.google.com/android/nexus/images
directions available in other threads.
yeah I did that then tried to get JB working again, but no luck
I'll prly just try again another time =/
thanks though
The exact same thing happened to me. I used Wugfresh tool kit to go back to stock. I lost everything on my SD card. I guess that's the price you pay for being a crack flasher !
bkang4 said:
yeah I did that then tried to get JB working again, but no luck
I'll prly just try again another time =/
thanks though
Click to expand...
Click to collapse
Are you able to access the bootloader? If so it's not bricked.
You need to flash EVERY SINGLE THING, all the partitions, bootloader, recovery, etc, everything, turn it back completely to stock. (then wipe before booting back up)
yeah i can get to the boot loader.
when i flashed to stock i used the factory image of 4.0.2 with the toolkit
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
bkang4 said:
yeah i can get to the boot loader.
when i flashed to stock i used the factory image of 4.0.2 with the toolkit
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
Click to expand...
Click to collapse
I guess that's the best way then. So there's no good way to get the stuff off the SD before ODIN/flashing it back to stock?
Fix
I had this same problem a bit ago. My device wouldn't boot and would sit on the Google logo.
Go back into Clockwork Recovery,
Wipe data,
Wipe cache,
Wipe dalvik
Install Jellybean
This worked for me, the problem was that I wasn't wiping everything correctly before installing Jellybean.
bkang4 said:
everything works on 4.0.2, but i'm hell bent on getting JB to work on this phone haha
Click to expand...
Click to collapse
1. Ok good.
2. Wait for a version made for the VWZ Galaxy Nexus or go buy the GSM Galaxy Nexus.
electroholic you're right, its worked! thanks a bunch
nxt said:
1. Ok good.
2. Wait for a version made for the VWZ Galaxy Nexus or go buy the GSM Galaxy Nexus.
Click to expand...
Click to collapse
Just in case you missed it, this is a version made for it, it's on my VZW GNex just fine as well as many others. There's just a few weird scragglers here and there it seems.
HELP!!
i tried to put the jellybean update on my verizon galaxy nexus and then found out it was only for gsm. now my phone has no signal at all. what do i do, i already tried to reset and restore, then i reset it and it just can't find any signal!
Well this happened to mine as well, but the funny thing is that if you just let it sit there for 5+ minutes the phone eventually boots.
ODIN
dude you might have to use odin unfortunately.:crying:
Hey guys,
A few days ago my Nexus (yakju-4.2.1-stock) got stuck in bootloop. I remember I was using the stock camera application and five minutes after that it started bootlooping.
Initially I entered stock recovery and noticed that below the android bot it was written "No Command". Regardless, I wiped the cache but no luck. Did a system wipe through the stock recovery but still no luck.
Today I used Wug's Galaxy Nexus Root Toolkit and flashed the takju-4.2.2-stock rom (Stuck in Bootloop option). It flashed correctly. However, it's still stuck in boot loop.
This time I entered Recovery and it no longer said "No Command" below the android bot. I wiped the cache and did a system wipe through the stock recovery but once again, its stuck on boot-loop.
I've read almost all the forums and threads and no one seems to have any other solutions for a stock rom.
Any suggestions?
Thanks in advance for the help!
Update:
I re-flashed the rom again and it boot-looped 4-5 times and then went into the optimizing apps screen. After optimizing all the apps it went back into boot-loop.
Is it a software or hardware issue?
You flashed takju on a yakju device...But not sure if that's the complete problem, since you've also done a factory reset.
Try this thread : http://forum.xda-developers.com/showthread.php?t=1626895
bodh said:
You flashed takju on a yakju device...But not sure if that's the complete problem, since you've also done a factory reset.
Try this thread : http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I was under the impression you could flash takju on all yakju variants (yakju, yakjuxw, yakjuux, yakjusc, yakjuzs, yakjudv, yakjukr and yakjujp).
I guess i'll just flash a normal yakju rom on it and see.
Thanks.
That's why i say i'm not sure that's the complete problem because i also believe you can flash takju on a yakju, provided you do a factory reset. Ever had a problem before this? Not exactly sure how the camera app can be involved.
I rooted my phone with GALAXY NOTE 2 Toolkit. It was working fine for few months. Recently I noticed a problem when I tried to reboot it, but I pulled the battery out and after reinserting all went OK. then Next day or two another time when I tried to reboot, I got to the point where I cannot boo the phone anymore. I get to the initial T-MOBILE screen and that's where it gets stuck.
I tried to upload a recent ROM through Odin. It worked fine, no errors, no problems, but when I try to boo the same thing happens.
I also tried to get to the other menu ( Power+Home+VolumeUp). It shows the menu with some options but I'm not sure how can I use those. I treid few things but it does not work.
I need to use the phone for work every day so I am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
SAME HERE!!!
aklisiewicz said:
i rooted my phone with galaxy note 2 toolkit. It was working fine for few months. Recently i noticed a problem when i tried to reboot it, but i pulled the battery out and after reinserting all went ok. Then next day or two another time when i tried to reboot, i got to the point where i cannot boo the phone anymore. I get to the initial t-mobile screen and that's where it gets stuck.
I tried to upload a recent rom through odin. It worked fine, no errors, no problems, but when i try to boo the same thing happens.
I also tried to get to the other menu ( power+home+volumeup). It shows the menu with some options but i'm not sure how can i use those. I treid few things but it does not work.
I need to use the phone for work every day so i am completely stuck and this is critical for me.
I would appreciate any help.
Arthur
Click to expand...
Click to collapse
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
go to recovery mode if you can
kim621973 said:
i have same issue..
I just odin 4.3 file and everything went to okay.. But stuck on samsung galaxy note2..
I did several number and number og count became 7 and knox warranty void 1...
Could go to down or recovery mode and installing roms but stuck...
Also how can i reset the count? Can i install stock image to go back?
Thank you in advance..
Click to expand...
Click to collapse
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
kim621973 said:
i just figure it out that go back to recovery mode and do factory reset couple time and boot it!!
back up to normal mine...
do odin 4.3 stock image
go back to recovery mode.
wipe cache/factory reset x3
boot it...
one more thing that you can't downgrade to 4.1.2 or..etc.. if odin 4.3 update it..
i think that someone mentioned..be careful..
we need kill the KNOX ON 4.3 UPDATE FILE...
ALL THE TROUBLE COMING FROM THE KNOX...
THANK YOU.
I HOPE THAT IT HELP!!!!.
Click to expand...
Click to collapse
While Knox is a problem, the bootloader is the booger that won't allow return to 4.1.2. Sammy hosed us on that little bit of trickery.
If my wife didn't have a GS3 that I maintain I might have OTA'd. I have been watching their "upgrade" process for a while and knew that there was trouble in the OTA.
It will be painful for a while as people migrate in with problems that have been covered several times. We'll get through it.
Hastily spouted for your befuddlement
Hello all, I'm here today because my note 2 (SGH-I317) seems to be stuck on the samsung logo. I tried using Odin and multiple ROMs, it says "PASS" but it looks like nothing was done to the phone. I can only get into download mode and not recovery, I tried to flash a custom recovery but no dice. I put many hours into finding a solution until I came across "Sudden Death", the device might of have a faulty chipset but there's no knowing for sure. Any help would be greatly appreciated.
P.S, I hope I opened this forum in appropriate location.
What version of android were you on?
terpin32 said:
What version of android were you on?
Click to expand...
Click to collapse
I was CM10 which is 4.1.2, I wanted to go to stock so I used Odin to flash back to stock which worked the first time then I installed the OTA update then thats when the problem occurred.
1Emerson1 said:
I was CM10 which is 4.1.2, I wanted to go to stock so I used Odin to flash back to stock which worked the first time then I installed the OTA update then thats when the problem occurred.
Click to expand...
Click to collapse
Well the 4.1.2 firmware you used won't work no matter what you do here's the thread you need to get back working
http://forum.xda-developers.com/showthread.php?t=2802189
Sorry for the late reply, I sent the phone to Samsung to flashed the factory firmware. I appreciate your response.
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.