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:
Related
I tried to flash SlimICS 3.4 Base and essentials then it got stuck on the loading screen. (My phone was on 4.0.2 and then got the notification today 4.0.4 was available and tried to install it and got a Android laying down broken sign half way through the install, so that sparked me wanting to get a new ROM and this whole problem. Thanks for your help)
I went back in and wiped and flashed again. Now I am stuck on the Google Page.
So I need some help. I am trying to find odin for i9250 and I think i can flash it with ODIN.
I am not sure so what I know so far:
I am using the ToolKit and i can see the device connected to my computer (This gives me hope that I will be able to get my phone working again!!!!)
I need links for ODIN.
(Edit found i9250 for oden: http://forum.xda-developers.com/showthread.php?t=1405327)
I need a ROM or something that i can flash in ODIN.
I am not sure what else ... and I would like a good build of 4.0.4 build that is real light on its feet and is fast ... Thanks guys.
My phone has been prompting me to install 4.0.4 update as of late. I was running a stock 4.0.4 flash w/ root and about 2 weeks after installing it via CWM it prompted me to install. The installation failed so I yanked the battery and it successfully booted back into the phone. After this it won't prompt again until after the phone is rebooted again.
I just flashed to the 4.1 Jelly Bean release figuring that would alleviate the problem and it still exists. My phone is constantly telling me to update the phone (even though now a 4.0.4 "upgrade" would infact me a downgrade). This is driving me crazy...is there any way to stop this from happening?
DKNUCKLES said:
My phone has been prompting me to install 4.0.4 update as of late. I was running a stock 4.0.4 flash w/ root and about 2 weeks after installing it via CWM it prompted me to install. The installation failed so I yanked the battery and it successfully booted back into the phone. After this it won't prompt again until after the phone is rebooted again.
I just flashed to the 4.1 Jelly Bean release figuring that would alleviate the problem and it still exists. My phone is constantly telling me to update the phone (even though now a 4.0.4 "upgrade" would infact me a downgrade). This is driving me crazy...is there any way to stop this from happening?
Click to expand...
Click to collapse
Let me guess, you are running a custom ROM?
This will fix it: edit the line that starts with ro.build.fingerprint in your build.prop file to read like this:
ro.build.fingerprint=google/takju/maguro:4.1/JRN84D/392829:user/release-keys
I wish I could say I was talented enough to create my own ROM, however I'm just flashing ROMS from the forums here.
The Jelly Bean ROM i just flashed is the one located HERE
DKNUCKLES said:
I wish I could say I was talented enough to create my own ROM, however I'm just flashing ROMS from the forums here.
The Jelly Bean ROM i just flashed is the one located HERE
Click to expand...
Click to collapse
By custom, I meant NON-stock, like that one. Do what I posted above.
No love I'm afraid. That's actually what's already in the ro.build.fingerprint...
Any other suggestions?
DKNUCKLES said:
No love I'm afraid. That's actually what's already in the ro.build.fingerprint...
Any other suggestions?
Click to expand...
Click to collapse
Hmmm. Strange. That used to fix it for older versions. Anyway, maybe re-flash Jelly Bean, and use the stock ROM this time: http://tinyurl.com/JRN84D
I cleared the data in the Google Services Framework, restarted the phone and the notification has not popped up since.
I'm headed to NYC tonight and will have little access to the internet but I will report back.
Thank you for your help efrant!
Clearing the data from the Google Services Framework seems to have done the trick. Almost a week and no prompts to install an update.
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...
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
I really hope someone helps with this, because oddly enough, I just had the exact same problem!
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I suggest you should go check out the Sprint Samsung s3 forum under the Android development section the check out for the stock rom, try using the 1 click Odin or check out in there the proper way to restore your device, then continue reading the forums to check out when or how is the proper way to apply that update it could be that its bugged or that your device lost some permissions so best way to solve it should be to restore it to its original state.
Sent from my SPH-D710 using xda app-developers app
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You cant install an OTA update unless you have the official stock rom and the stock recovery because custom recoveries will install it and I believe im correct when I say that to flash an OTA update you have to odin to stock and then do the update.
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Most custom touchwiz roms will allow updates, but you have to flash stick recovery 1st. The 157mb update is for mb1. You could just change your build prop to get the notification nag to go away
sent from my GS3 using XDA app
If you're on stock rooted with no apps removed, do what I did. Plug phone into odin, flash stock recovery, update, flash custom after update done, re root, done.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
tazfanatic said:
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
Click to expand...
Click to collapse
Yup, if you just wanna make it go away, go into your build.prop and change all instances of "LJ7" (or "MA6" ) to "MB1"
CNexus said:
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Click to expand...
Click to collapse
That's all I do. Once an update comes out I just head over to Freezas page and update my rom. Stock look and feel with the root in place.
Sent from my stock rooted Galaxy S3
Any update on this? I have the same issue.
Thanks
coderaja said:
Any update on this? I have the same issue.
Thanks
Click to expand...
Click to collapse
There's several ways to fix this issue posted on the other page. Use one of them.
D
So my OTA installed successfully to 4.3 I also managed to root it perfectly fine and reboot with everything working correctly.
However for some reason I decided to fiddle with system/app mover, moved a few samsong and AT&T application to be user ones instead of system and rebooted. The phone starts booting and freezes in the middle displaying the ATT logo, I tried factory resetting which didn't help.
Is there a way for me to re-install 4.3 or whatever else that works. I don't think this is considered 'bricking' and I'm hesitent about using odin with 4.0.4 ROMs since I heard 'downgrading' will brick the phone.
morps said:
So my OTA installed successfully to 4.3 I also managed to root it perfectly fine and reboot with everything working correctly.
However for some reason I decided to fiddle with system/app mover, moved a few samsong and AT&T application to be user ones instead of system and rebooted. The phone starts booting and freezes in the middle displaying the ATT logo, I tried factory resetting which didn't help.
Is there a way for me to re-install 4.3 or whatever else that works. I don't think this is considered 'bricking' and I'm hesitent about using odin with 4.0.4 ROMs since I heard 'downgrading' will brick the phone.
Click to expand...
Click to collapse
If you have custom recovery you can flash another 4.3 rom.
are you sure it is stuck 4.3 takes a long time to boot up after a factory reset (mine took about 4 minutes??? after I installed 4.3 the first time and about 3 the second time I installed it.)
Thanks, I flashed the ROM from http://forum.xda-developers.com/showthread.php?t=2540998 which seems to have worked. I'm wondering if there is anyway to go to stock (ie. the original AT&T one, but apparently it's not available anywhere just as an OTA).
morps said:
Thanks, I flashed the ROM from http://forum.xda-developers.com/showthread.php?t=2540998 which seems to have worked. I'm wondering if there is anyway to go to stock (ie. the original AT&T one, but apparently it's not available anywhere just as an OTA).
Click to expand...
Click to collapse
That's the same one I have I like it. That's as close to stock you're going to get.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app