Related
Hi,
New to this site and sorry if this is already discussed but:
I just recently got the official OTA notification for Jelly Bean for my GSM unlocked Galaxy Nexus, but here's the problem.
I bought the phone with yajkuxw 4.0.1 build on it (the one from Samsung) and flashed yakju 4.0.4 onto it. The bootloader is unlocked and it is rooted. There is not altered files on it (other than boot.img). So when I download and try to apply the 4.1 update, the phone restarts, starts the process and then freezes on the image of a little android man with his chest open with a red exclamation mark. I have re downloaded many times but no luck.
So far, I have unrooted and re-flashed the stock recovery.img on it and completely reinstalled the 4.0.4 build with nothing else on it...no luck. I locked and unlocked the bootloader and unrooted and rooted it a few times, still no luck. I have ToolKit v1.5.1 and all drivers, just a stupid problem. So everything I do, nothing works. I was hoping someone had an official untouched 4.0.1 build so I can install 4.1 directly from that that, OTA.
Please I do not want to flash 4.1 directly onto it, I wanna fix this problem so I can receive all future updates OTA!
Anyone else have this problem? Can anyone please help?
Cheers
Better to find answers from others threads, this is maybe last time when I answer to the same questions!
Download IMM76I "takju" Google Factory Image!
when it's downloaded you have to use 7-zip, winrar, or something like that to open it in Windows!
download this one: http://downloadandroidrom.com/file/GalaxyNexus/rooting/GalaxyNexusRootNew.zip
add the GalaxyNexusRootNew folder to
C:\
open the factory image file and copy files to the Galaxynexusrootnew folder and if factory image file has .zip file then open it and move the files from it to galaxynexusrootnew folder too
Download OTA update from JRN84D to JRO03C. add to galaxy nexus too.
Now boot you Nexus fastboot mode:
flash files by using fastboot flash, etc..
use these commands: http://forum.xda-developers.com/showthread.php?t=1625700 but you have to edit the file names to flash them..
then boot it when all is done and download jb-takju.zip, when it's downloaded move it to galaxy nexus and then from Galaxynexusroot folder you have to move the root bla bla bla.zip file to ROOT!
go to fastboot mode and type this one: fastboot flash recovery optimus_prime-touch-v5.5.0.4-6-GSM.img
Download radio XXLF1 flashable for fastboot and flash it via fastboot to Galaxy nexus: fastboot flash radio bla bla bla.img
now boot to rcovery mode and wipe dalvik cahce, wipe cache and now flash jb-takju.zip and then in CWM wipe factory/data flash again jb-takju.zip and now flash OTA update and reboot.. and now when those are done reboot and when it's done go to fastboot mode and flash bootloader JB's own bootloader..
I wrote this quickly because I don't have time so I hope you understood that how to do..
Here is the JB-takju.zip JRN84D for CWM http://download.clockworkmod.com/test/jb-takju.zip
FIXED!
Hey, just wanted to say the fix to the problem is to flash EVERY partition for your current version onto your Nexus (radio, bootloader, boot, system, userdata etc.). From there, the OTA works.
Cheers
Flash every partition
DanDaGamer said:
Hey, just wanted to say the fix to the problem is to flash EVERY partition for your current version onto your Nexus (radio, bootloader, boot, system, userdata etc.). From there, the OTA works.
Cheers
Click to expand...
Click to collapse
My problem is identical to yours... right down to starting with 4.0.1. I am hoping your fix of flashing every partition works for me as well.
Question: how do you flash every partition? I am asking because I thought I already did this when I initially moved to 4.0.4. However, you obviously did the same thing I did, so I am also hoping you know the reason I am asking
Looking forward to your reply
Andrew
Same
Andrew Field said:
My problem is identical to yours... right down to starting with 4.0.1. I am hoping your fix of flashing every partition works for me as well.
Question: how do you flash every partition? I am asking because I thought I already did this when I initially moved to 4.0.4. However, you obviously did the same thing I did, so I am also hoping you know the reason I am asking
Looking forward to your reply
Andrew
Click to expand...
Click to collapse
Would love to know as well Dan
Moby
Fixed
I was finally able to get Jelly Bean 4.1.1 Build number JRO03C
Here is what I did:
- Backed up my Android data
- Followed the instructions on http://forum.xda-developers.com/showthread.php?t=1626895
- The above completely "reformatted" my Android (so I lost all my data)
- Did not restore my applications... yet
- Turned off my phone's data connection, and only had WiFi.
- In "Settings"
- Selected the "About Phone" option
- Selected the "System Updates" option
- Clicked the "Check now" button
Finally the OTA update arrived and actually worked this time
Thanks
Andrew Field said:
I was finally able to get Jelly Bean 4.1.1 Build number JRO03C
Here is what I did:
- Backed up my Android data
- Followed the instructions on http://forum.xda-developers.com/showthread.php?t=1626895
- The above completely "reformatted" my Android (so I lost all my data)
- Did not restore my applications... yet
- Turned off my phone's data connection, and only had WiFi.
- In "Settings"
- Selected the "About Phone" option
- Selected the "System Updates" option
- Clicked the "Check now" button
Finally the OTA update arrived and actually worked this time
Click to expand...
Click to collapse
Thanks for that
Pink Tint after Jelly Bean update
I upgraded the phone to Jelly bean yesterday and weirdly this pinkish tint has started to appear which is slowly expanding. Is there anyway to stop it or fix it? Have attached the image.
Pink Tint after Jelly Bean update
I upgraded the phone to Jelly bean yesterday and weirdly this pinkish tint has started to appear which is slowly expanding. Is there anyway to stop it or fix it? Have attached the image.
Jellybean update freezes on the ASUS screen with the circling dots
The issue I'm facing is also an unsuccessful JB update, but a bit different.
I use an ASUS Infinity TF700T. I downloaded the Jellybean update this morning, and it went through the installation process, applying updates and recognizing apps. Then it rebooted as expected, but doesn't get past the ASUS splash screen with circle of dots. It sits there for over an hour.
I tried to hard reboot it a few times, and it still doesn't boot up. It gets as far as the circling dots and stays there.
When I plug it into my computer with USB, it's not visible to the computer.
My system is encrypted, and was working fine before the update. I haven't had any significant system problems before the update. I haven't noticed any encryption related problems (the encrypted login screen is still the same and takes the password, and then continues to try to boot, but doesn't complete the bootup.)
What are my options? Is a factory reset needed, as Andrew Field did?
FYI, My new ASUS infinity is not rooted.
Phuljum said:
The issue I'm facing is also an unsuccessful JB update, but a bit different.
I use an ASUS Infinity TF700T. I downloaded the Jellybean update this morning, and it went through the installation process, applying updates and recognizing apps. Then it rebooted as expected, but doesn't get past the ASUS splash screen with circle of dots. It sits there for over an hour.
I tried to hard reboot it a few times, and it still doesn't boot up. It gets as far as the circling dots and stays there.
When I plug it into my computer with USB, it's not visible to the computer.
My system is encrypted, and was working fine before the update. I haven't had any significant system problems before the update. I haven't noticed any encryption related problems (the encrypted login screen is still the same and takes the password, and then continues to try to boot, but doesn't complete the bootup.)
What are my options? Is a factory reset needed, as Andrew Field did?
FYI, My new ASUS infinity is not rooted.
Click to expand...
Click to collapse
Maybe you should ask in the ASUS forum...
Hi guys,
did not find any related problem, so i open this new thread:
I flashed my Samasung Galaxy Nexus GT-i9250 with the stock google factory firmware image yakju maguro IMM76I.
This worked really well and I was good to go with the ICS system.
Then i recieved the OTA update from that 4.0.4 version to the jelly bean 4.1.1
The installtion worked well and the patches/updates were applied.
To that point everything looks good. BUT, after the reboot i'm stuck in the boot up procedure on the point
where the 4 color X symbol appears. I tried that stock-flash then update method in combination with and without
the CWM tools and with/without wiping of cache, data and so on.
I can not pass that boot screen and i am already waiting for 1 hour. Restarting does not help either. Wiping also
does not help. Delvik wipe also does not help ...
Radio, System and everything was on stock before i applied the update to jb. What could be the problem here,
i run out of ideas...plz help
xpawellx said:
Hi guys,
did not find any related problem, so i open this new thread:
I flashed my Samasung Galaxy Nexus GT-i9250 with the stock google factory firmware image yakju maguro IMM76I.
This worked really well and I was good to go with the ICS system.
Then i recieved the OTA update from that 4.0.4 version to the jelly bean 4.1.1
The installtion worked well and the patches/updates were applied.
To that point everything looks good. BUT, after the reboot i'm stuck in the boot up procedure on the point
where the 4 color X symbol appears. I tried that stock-flash then update method in combination with and without
the CWM tools and with/without wiping of cache, data and so on.
I can not pass that boot screen and i am already waiting for 1 hour. Restarting does not help either. Wiping also
does not help. Delvik wipe also does not help ...
Radio, System and everything was on stock before i applied the update to jb. What could be the problem here,
i run out of ideas...plz help
Click to expand...
Click to collapse
This is happening to a few Verizon users like myself who are flashing to a JB rom and still can't get past the Google X screen. It's a shame that it is happening to someone updating through an OTA. I don't have any help for you because I have tried everything, but I want to try and keep this thread alive in hopes that someone out there has had a greater than 30 minute boot time and was able to get past it. So far I haven't found anyone.
nothingshocking said:
This is happening to a few Verizon users like myself who are flashing to a JB rom and still can't get past the Google X screen. It's a shame that it is happening to someone updating through an OTA. I don't have any help for you because I have tried everything, but I want to try and keep this thread alive in hopes that someone out there has had a greater than 30 minute boot time and was able to get past it. So far I haven't found anyone.
Click to expand...
Click to collapse
I really can not believe, that a stock ics image + update to jb does not work. And i do not see any possibility to dump get access to the
boot log information. That way i could at least try to find the point where the boot procedure stops/waits.
Hopy anybody knows a solution for this. If not, i will have to wait for the official stock image for 4.1.1 from google.
Same here I can flash ics rom..restore without problem.. but every time I flash jb rom it always stay in nexus logo.. I've waited for an hour to 2hrs... nothing only infinite boot loop.
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Same here I can flash ics rom..restore without problem.. but every time I flash jb rom it always stay in nexus logo.. I've waited for an hour to 2hrs... nothing only infinite boot loop.
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
As far as i can image, this must be due to some hardware revision differences between the devices. Since the whole firmware+software package
is exactly the same on every device after a clean flash to the factory image, this is the only difference left i can think of.
If that is true, google has to do some work on the jelly bean sources to fix that problem. And again ... i know no way to get debug information from a device taht is stuck in the boot logo... :crying:
My wife and I have the same phone, Verizon GNex. However, our phones are completely different! I'm currently on AOKP build 4. She was on Build AOKP ICS 40. I attempted to flash build 4 and gapps after a full wipe, etc, but I never could get it to flash properly. The first time I flashed it, it allowed to try to sign her into her account. She had google 2 step on and I wasn't able to get her loaded. The second phone on file for 2 step was her own, so when the text came I couldn't get to it (for whatever reason the soft keys were missing and I couldn't get out once I was stuck in the 2 step process.) I then pulled the battery to reboot. It was stuck in a boot loop that I couldn't get out. When I tried to flash back to the backup file from build 40 it was missing, as was all the other backup files. I didn't have a copy to flash to and the rom was stuck in boot loop. I couldn't use fastboot because it was saying "fastboot read error 2147483647" I decided to odin 4.02 stock software. It worked great to get me out of the loop and get the phone up and going again. Since that point I updated the stock software, rerooted ,and reinstalled CWR. However, no matter how I try to flash any build of AOKP now it fails. I even pulled the files from my phone that I had flashed just days before and put them on my wife's phone. Nope. Didn't work. I tried TWRP and I couldn't get it to work either. What other options should I take to get the rom on my wife's phone. She's about to kill me already for "messing" it up.
Redownload the ROM, make sure she doesn't have toroplus and you're trying to flash a toro ROM or something like that, make sure if she has a toro GalNex she also has a toro recovery, try flashing the latest 4.1.1 radios....
Toro is Verizon GalNex, toroplus is Sprint.
Sent from my Galaxy Nexus using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I tried something different. One phone good. One phone JACKED!
I tried a clean download via a wired connection. Same result, FAIL! Instead I used the odin files I found to flash the toro (VZW). After which I rerooted the device and downloaded CM10 nightly and flashed without ANY problems.
My phone (AOKP toro JB build 4) ran completely out of battery charge that it powered off. The ironic thing is, after charging completely in the off state I started it back up...(same) BOOT LOOP! I've searched a little bit on the forums, but I can't seem to find the exact way to undo this. This is the same boot loop I had with my wife's phone. I tried to flash my most recent JB 4 backup and it gets an error after the system restore and just before the data restore. I tried all the other backups of many different builds with CWM and had the same result. I tried flashing the AOKP JB 4 but it just ends up in the boot loop again.
I can't push any new files to it for whatever reason so I can't try to flash the radios or bootloader. Honestly, I can't even read the internal memory where everything is stored. I think it's because the debuging mode isn't turned on since I tried to reflash a new build and restore my backup. " I love AOKP, but I'm going to hold off until a new milestone build comes out. At this point I just want the pictures/videos from my phone. I have a backup on my computer saved, but none of the pictures/videos are saved.
:crying:
-Chlorine
jimmyco2008 said:
Redownload the ROM, make sure she doesn't have toroplus and you're trying to flash a toro ROM or something like that, make sure if she has a toro GalNex she also has a toro recovery, try flashing the latest 4.1.1 radios....
Toro is Verizon GalNex, toroplus is Sprint.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Chlorine tablet said:
I tried a clean download via a wired connection. Same result, FAIL! Instead I used the odin files I found to flash the toro (VZW). After which I rerooted the device and downloaded CM10 nightly and flashed without ANY problems.
My phone (AOKP toro JB build 4) ran completely out of battery charge that it powered off. The ironic thing is, after charging completely in the off state I started it back up...(same) BOOT LOOP! I've searched a little bit on the forums, but I can't seem to find the exact way to undo this. This is the same boot loop I had with my wife's phone. I tried to flash my most recent JB 4 backup and it gets an error after the system restore and just before the data restore. I tried all the other backups of many different builds with CWM and had the same result. I tried flashing the AOKP JB 4 but it just ends up in the boot loop again.
I can't push any new files to it for whatever reason so I can't try to flash the radios or bootloader. Honestly, I can't even read the internal memory where everything is stored. I think it's because the debuging mode isn't turned on since I tried to reflash a new build and restore my backup. " I love AOKP, but I'm going to hold off until a new milestone build comes out. At this point I just want the pictures/videos from my phone. I have a backup on my computer saved, but none of the pictures/videos are saved.
:crying:
-Chlorine
Click to expand...
Click to collapse
Code:
fastboot boot cwm_or_twrp.img
when in recovery:
Code:
adb pull /sdcard/
note: if no folder is really pulled, change /sdcard/ to /data/media
Some tips for the two step verification that I have found out. Although it says not to use a Google voice account it is by far the Best method for dong two step. For me I always have some other device logged into Google Voice and I use that device to get the text. The other thing I do is forward texts with that string to my gmail account so I get it as an email. I figure if someone has my device and is trying to log in then they can't see my Google voice or emails
I will try this in the morning. I just drove the family 12 hours back from our Disney vacation. Ah, my own bed to sleep in.
-Chlorine
bk201doesntexist said:
Code:
fastboot boot cwm_or_twrp.img
when in recovery:
Code:
adb pull /sdcard/
note: if no folder is really pulled, change /sdcard/ to /data/media
Click to expand...
Click to collapse
While waiting for things to settle down this morning I thought I would try one last thing to get the phone back to working. Within CWM I choose to use fix permissions. After a few minutes it finished and returned to CWM menus as normal. I rebooted the phone and it's working. I'll need to copy the files from it before progressing forward. Once I do this I will try rebooting and see what it does. Take in mind I tried flashing, recovering, etc before I even thought of the fix permissions. It stopped me in my tracks with the errors. Once I reboot I will post my results. I just hope I didn't leave my cable in Florida.
:victory:
-Chlorine
Just bought a new cable and I'm starting a full backup now. I'll reboot and see if the phone loops again or not in an hour or so. Details to come.
Reboot. No boot loop.
Hi guys.. I tried installing jelly bean on this device (i8160p and it's not mine) using odin and a stock 4.1 rom I got from samsung updates(I have no root and I went from a never-touched stock)... All went fine, It's working and has all the features. Except that now its owner is asking me constantly to revert back to the original os, since he did find 4.1.2 very slow. So I went back the same path as in the first place in an attempt to get the original gingerbread : I downloaded a stock 2.3 from the site and then tried flashing it.. All again went smooth, with no problems, until I got stuck on the bootscreen and noticed that there was no way to access recovery(download mode working fine though)... So what I'm left with now is a non-booting gingerbreak or the possibility to stay in jellybean(flashing it still works), I'd prefer if I could go back to GB; I think the problem is that there was some conflict caused by jellybean which will require a reset that I can't of course do since I can't boot into recovery, and I don't see any way to install a custom recovery. So can this be done any other way, I'm afraid I'll break this phone before I'll even come up with anything since this is my first experience with roms and boot on an android;
info : as I mentioned There is no root (for now. I might however get into that from jellybean, but I'd rather not if it's possible) and the model is i8160P . an emphasis on the P here since it's the reason I can't find any custom roms, and all I'm left with is the stuff in here
Edit : got gingerbread back after following what angrybb has suggested
Flash the working JB, and after that root your phone like here: http://forum.xda-developers.com/showthread.php?t=2139263 Reboot to recovery and after that follow the howto: http://forum.xda-developers.com/showthread.php?t=2352064 just in step 8 use original gb firmware.
If you can't get adb root access from stock recovery then flash kernel with cwm, for jb for example this: http://forum.xda-developers.com/showthread.php?t=2304432 or this http://forum.xda-developers.com/showthread.php?t=2171054
After flashing one of those kernel, again follow: http://forum.xda-developers.com/showthread.php?t=2352064 , again in step 8 use gb fw
Ok I'll see
Thanks man I'll try what you suggested as soon a I can...
I have a question though: now I noticed that some people fixed this issue by dowloading some other parts (.pit and something else), but of course I'm unable to find these for the model with the P... Now If someone can please tell me if these files have anything to do with the re-partion option in odin(I heard that it does format everything and not just put things on top of things).... Is using it safe given that I don't mind losing data, or should I stay away from it ?
For angrybb : the phone still shows as i8160p in the about section and has access to network...
Here there is a lot talking about pit files, some tehniques with flashing one fw after another, but with no real explanation why this should be done this way. I dont like doing things like that, i want to understand what i am doing. I still haven found some in depth info about pit files.
Anyway, i upgraded from GB to JB with kies, after that i compared some parts of fw and pit file is not changed. Pit from GB and JB have same md5 in my phone, so it is the exactly same file.
I know that method i suggested is not short and plain easy but it is tested and working.
Thanks
Sorry for the delay... For anyone with same problem just follow what angrybb has suggested, but do not under any circumstances ignore backing-up CSPSA_FS and MODEM_FS if you care about your phone's ability to make calls !
hey, maybe you guys could also help me out? i came from a custom ROM that i was having problems with so I wanted to go to an official ROM instead. Originally i came from a GB stock ROM, then i went straight to CM 10.1 but i didnt have any signal on my phone so i tried flashing original stock 4.1.2, now im stuck on the boot screen and i cant access recovery mode. please help?
P.S. my phone is i8160
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
mlfca said:
Hi.
My son's Galaxy Nexus (Verizon) is having some serious issues. HE has been crack flashing everything under the son (Just like his data) and recently he tried a 4.3 rom (Not sure which one). He started to get random crashes so he flashed back to one of the 4.2.2 rom. Then the phone started crashing all the time so I hooked it up the the Nexus toolkit (I assume it is the one everyone uses) and decided to do a full wipe. The phone was basically two folders and would not boot past the Google logo.
When I hooked it up to the tool kit software it was recognized and I flashed the stock (VZ) rom, no root. When I booted the phone it would go to the start screen looking for WiFi and when I tried to go through the start up process the phone would lock up and reboot. I cannot get past this point to do any troubleshooting.
So is this a hardware issue (The phone is toast) or am I missing something as far as doing a complete wipe to get back to bone stock?
Thank you for your help. (I have as well as my son have been trolling this site and others looking for answers but since I can boot up most did not apply, I think)
Click to expand...
Click to collapse
Right off the bat, do NOT use toolkits anymore. Please. You need to learn how to use Fastboot.
The best thing to do is start completely fresh. Download latest Galaxy Nexus factory images and fastboot them.
If you have no idea how to use fastboot, I suggest going to this thread and reading up my man: [GUIDE]New To Adb And Fastboot Guide
Any other questions or help I can gladly answer.