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, so I have rooted my phone yesterday everything went fine. But today I installed the CyanogenMod 10.1 + the google apps thorugh ROM manager, everything went fine it got installed, and then my phone restartet. When it had boot up, it asked me for pin code. After that it came up and said com.google.process.gapps has stopped, and when I pressed ok it came up and said Setup Wizard has stopped. I tried to boot the phone into recovery mode, with no help (correct me if I was doing it wrong, but tried all combinations), so now Im pretty screwed, how do I fix this ? Please explain it as you would for a child, as Im pretty new to all of this.
steffenbakke said:
Hey guys, so I have rooted my phone yesterday everything went fine. But today I installed the CyanogenMod 10.1 + the google apps thorugh ROM manager, everything went fine it got installed, and then my phone restartet. When it had boot up, it asked me for pin code. After that it came up and said com.google.process.gapps has stopped, and when I pressed ok it came up and said Setup Wizard has stopped. I tried to boot the phone into recovery mode, with no help (correct me if I was doing it wrong, but tried all combinations), so now Im pretty screwed, how do I fix this ? Please explain it as you would for a child, as Im pretty new to all of this.
Click to expand...
Click to collapse
Didnt u look around this thread before playing with system files...!!!
Have you unlocked your bootloader and installed custom recovery...??
hasan4791 said:
Didnt u look around this thread before playing with system files...!!!
Have you unlocked your bootloader and installed custom recovery...??
Click to expand...
Click to collapse
I read it, and yes I have unloacked bootloader and installed ClockworkMod Recovery, so that should be fine?
Btw I found this link: forum.cyanogenmod(dot)org/topic/40609-cm9-error-unfortunately-setup-wizard-has-stopped/
And thought about if this would work also?
Did you made all 3 wifes™ before flashing cm?
Sent from LG E975 pwd by CM 10.1
Just killed my phone. I updated ROM Manager and flashed (updated) Clockworkmod recovery (I wish I didn't). Now I have LG logo over my screen i nothing else. I can't enter recovery mod. Logo just stays there. OS is ARC XP 1.3 (cynogenmod 7.2 based). What to do? First time I tried to make recovery in ROM manager months ago I bricked phone. Solved that and everything was OK. Flashed ROM several times since than. Now it's dead.
Redneck1984 said:
Just killed my phone. I updated ROM Manager and flashed (updated) Clockworkmod recovery (I wish I didn't). Now I have LG logo over my screen i nothing else. I can't enter recovery mod. Logo just stays there. OS is ARC XP 1.3 (cynogenmod 7.2 based). What to do? First time I tried to make recovery in ROM manager months ago I bricked phone. Solved that and everything was OK. Flashed ROM several times since than. Now it's dead.
Click to expand...
Click to collapse
Solved.
http://forum.xda-developers.com/showthread.php?t=2131247
Glad
Redneck1984 said:
Solved.
http://forum.xda-developers.com/showthread.php?t=2131247
Click to expand...
Click to collapse
Dude It's bricked any way happy for u r pecan Cheer's:good:
This morning I tried to do the OTA update to the stable versions listed above. The device rebooted to the blue man and stayed there for 30 minutes I figured something was wrong so I took off the battery and restarted. Now it's stuck on blue man every time I boot up the phone. I can get into download and recovery mode, I tried doing a data wipe on the phone and see if it would work from there, and nothing. I'm debating what should I do from here? I want cyanogenmod on my phone so I was wondering if I could flash it from ODIN. Any advice would be appreciated.
Pretty much the same thing happened to me, except on the d2att version. Wish I could give more help than just saying I'm in the same boat, sorry.
same
update put phone in boot loop so im going with nightly builds
Hey,
I had AOSP installed on my ascend p6, everything working no problems at all.
Suddenly when I was a week on vacation when my battery died it wouldn't get passed the rom loading screen.
I have TWRP 2.7 and have wiped everything and everything over and over but nothing is working. I am now trying to install The lastest aosp sincde OMNI and CM11 didn't work.
Any help how to fix this? it keeps happening at every rom I install.
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
UPDATE: Okay somehow after rebooting it around 20 times with fastboot, recovery and other combinations it is now booting I think. Praise the lords. It is now optimizing the apps
I have no idea what I did but I will post an update when it is done optimising
UPDATE UPDATE: Okay the weirdest thing just happened and I don't get this at all... I have wiped my whole phone like 5 times. with itsto and exsto. but somehow I now boots with all my apps, settings and launcher intact and inplace... I even installed multiple roms trying to make it work. WHAT IS THIS MAGIC?!
I know I shouldnt do this but I am going to re-install twrp 2.6.*.* and then pushing it to 2.7. Wish me luck! (following the excact instructions to make it work haha)
UPDATE UPDATE UPDATE: Okay, After seeing the wi-fi not turning on I tried rebooting my phone now it is stuck at the huawei ascend screen.
TomTheTiger said:
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
Click to expand...
Click to collapse
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
warea said:
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
Click to expand...
Click to collapse
Will try! I thought I was passed this haha. When It starts i'll try to figure out a way to install it probs trough adb fastboot. since I can't get to the recovery screen with buttons
Update: Okay I managed to boot recovery up trough adb, It automatically started installing the update.app package.
I am now hoping for the best, one good thing... My phone was luckily already in unlock state
UPdate: Succesfully flashed my phone the stock with unlocked bootloader!
UPDate: And now on omni rom Everything is working fine!