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...
I have a Yakju Maguro which is currently running JOP40D. I recently installed the ClockWorkMod v6.0.2.3 recovery, and rooted my phone. Now I received the notification for the 4.2.2 OTA update, but as expected CWM gives me an error when attempting to install it. It says "Install Untrusted Package?" and gives me Yes or No as options. Until now, I've always been weary to try the Yes option, so I've always gone for No, and the update obviously didn't install.
So my question is, will it actually work if I select Yes? And if it doesn't, in what condition will my phone be after it fails? Will it boot into the old OS, or will I have to manually re-flash a ROM?
I've tried googling the problem but no one seems to be facing the same exact condition as me. Eveyone reports that the installation simply fails with CWM, and I've never seen any mention of a Yes/No prompt. Also, I haven't found any thread that mentions in what condition the phone will be after the failure, so I'm trying to figure out what's going on.
In addition, I've manually downloaded the "07501b11ad3b.signed-yakju-JDQ39-from-JOP40D.07501b11" zip file from the Google website. Will I be able to flash that instead from CWM, make things simpler?
Thanks for any help.
Hi All,
I am lightly experience with all of this so i will try and provide some background.
I purchased my S3 and when I first rooted CyanogenMod 10.0.0 was the current stable. I have been using that until just recently when I decided it was time to upgrade as I was experiencing some serious performance issues with SMS (not getting any) and I have a few days off work. I have also been having issues with all data connectivity dropping out all the time (an issue I have just come to live with) for probably about a year now. There is was a issue submitted to the CyanogenMod Bug tracker when it was on Google (not sure if it still is). If I can dig up the link I will edit the post but I do not belie it is really relevant to this particular issue. [Edit: This looks like it may be the Jira Case. Similar issue reported.] https://jira.cyanogenmod.org/browse/CYAN-1396
See thread title for issue.
Steps I Have Taken So Far:
1. I downloaded the latest 10.1.2 stable and copied it to my external SD.
2. Reset Factory Defaults
3. Clear Cache
4. Clear Dalcik
5. Booted to recovery (ClockWorkMod) and attempted to install...received a status 7 error.
6. Removed the assert tags as instructed here: http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
7. Reset Factory Defaults
8. Clear Cache
9. Clear Dalcik
10. Attempted to install new file and not it simply failed when "Attempting to Open Update...", there was nothing in the log (under advanced in clockworkmod)
11. Looked further into the release notes of 10.1.2 and realized it might be a problem with my boot-loader (This is my active theory).
12. Went searching on how to try and "update my boot-loader" could only find topics relating to unlocking.
13. To my understanding the stock ROMs also update the boot-loader so I installed this stock ROM: http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
14. Check to see it installed OK and then booted back into recovery and attempted steps 2-10....no success.
Thoughts?
Some more info:
Sprint Galaxy S3
Model: SPH-L710
Android Version: 4.1.2
Baseband Version: L710VPLI3
Build Version: JZ054K.L710VPBMD4
Hardware Version: L710.14
ClockWorkMod Recovery: v6.0.3.1
Don't get me wrong I would love someone to just swoop in with a solution but I would really like to understand what is happening here.
- What "version" is my boot-loader / how can you tell that?
- Is there a reference somewhere about what boot-loaders are for what versions?
I have a nandroid backup of my old 10.0.0 ROM and at this moment in time I have the stock ROM image which is listed above installed and running. I DO NOT have a backup of my IMEI or my EFS so that might be a decent next step.
Thank you,
Matthew
References:
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
http://forum.xda-developers.com/showthread.php?t=1922461
http://wiki.cyanogenmod.org/w/D2spr_Info
http://wiki.cyanogenmod.org/w/Install_CM_for_d2spr
mcf747 said:
Hi All,
I am lightly experience with all of this so i will try and provide some background.
I purchased my S3 and when I first rooted CyanogenMod 10.0.0 was the current stable. I have been using that until just recently when I decided it was time to upgrade as I was experiencing some serious performance issues with SMS (not getting any) and I have a few days off work. I have also been having issues with all data connectivity dropping out all the time (an issue I have just come to live with) for probably about a year now. There is was a issue submitted to the CyanogenMod Bug tracker when it was on Google (not sure if it still is). If I can dig up the link I will edit the post but I do not belie it is really relevant to this particular issue. [Edit: This looks like it may be the Jira Case. Similar issue reported.] https://jira.cyanogenmod.org/browse/CYAN-1396
See thread title for issue.
Steps I Have Taken So Far:
1. I downloaded the latest 10.1.2 stable and copied it to my external SD.
2. Reset Factory Defaults
3. Clear Cache
4. Clear Dalcik
5. Booted to recovery (ClockWorkMod) and attempted to install...received a status 7 error.
6. Removed the assert tags as instructed here: http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
7. Reset Factory Defaults
8. Clear Cache
9. Clear Dalcik
10. Attempted to install new file and not it simply failed when "Attempting to Open Update...", there was nothing in the log (under advanced in clockworkmod)
11. Looked further into the release notes of 10.1.2 and realized it might be a problem with my boot-loader (This is my active theory).
12. Went searching on how to try and "update my boot-loader" could only find topics relating to unlocking.
13. To my understanding the stock ROMs also update the boot-loader so I installed this stock ROM: http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
14. Check to see it installed OK and then booted back into recovery and attempted steps 2-10....no success.
Thoughts?
Some more info:
Sprint Galaxy S3
Model: SPH-L710
Android Version: 4.1.2
Baseband Version: L710VPLI3
Build Version: JZ054K.L710VPBMD4
Hardware Version: L710.14
ClockWorkMod Recovery: v6.0.3.1
Don't get me wrong I would love someone to just swoop in with a solution but I would really like to understand what is happening here.
- What "version" is my boot-loader / how can you tell that?
- Is there a reference somewhere about what boot-loaders are for what versions?
I have a nandroid backup of my old 10.0.0 ROM and at this moment in time I have the stock ROM image which is listed above installed and running. I DO NOT have a backup of my IMEI or my EFS so that might be a decent next step.
Thank you,
Matthew
References:
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1910947&highlight=md4
http://forum.xda-developers.com/showthread.php?t=1922461
http://wiki.cyanogenmod.org/w/D2spr_Info
http://wiki.cyanogenmod.org/w/Install_CM_for_d2spr
Click to expand...
Click to collapse
Is this the file u flashed when u tried to update the boot loader?
http://goo.im/devs/freeza/d2sprFirmware/Galaxy-S-fre3-MD4FirmwareModemAIO.zip
I ask because where u listed addtl info it says your build is md4 but your baseband is li3(ics) I don't think your on the latest boot loader. Flashing what I have linked above will fix that. Second I don't think u had to break down that zip and start changing assert lines. Those lines are there for a reason and shouldn't have to be altered. I would update your firmware using my link then redownload cm 10 and reattempt flashing it without altering it
billard412 said:
Is this the file u flashed when u tried to update the boot loader?
[Link redacted due to the fact Im a new member and cannot post it yet.]
I ask because where u listed addtl info it says your build is md4 but your baseband is li3(ics) I don't think your on the latest boot loader. Flashing what I have linked above will fix that. Second I don't think u had to break down that zip and start changing assert lines. Those lines are there for a reason and shouldn't have to be altered. I would update your firmware using my link then redownload cm 10 and reattempt flashing it without altering it
Click to expand...
Click to collapse
No it was not...however I had it already downloaded so I must have gotten close and decided to not go down that road.
I performed the the install of the linked file and my Baseband is now L710VPBMD4 and 10.1.2 appears to have installed correctly.
NOTE: After updating firmware I immediately attempted to install 10.1.2 and it failed. I restarted into the stock ROM and then rebooted and entered recovery and it installed fine. Not sure if it was the restart or entering into a ROM that was the solution but a good note for anyone with this issue in the future.
Yes, it's necessary to restart after flashing a new bootloader. It's really not a good idea to bypass security checks like removing those lines in the bootloader, because 4.2.2 roms are implementing a RIL that relies on the MD4 bootloader.
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
Yes, it's necessary to restart after flashing a new bootloader. It's really not a good idea to bypass security checks like removing those lines in the bootloader, because 4.2.2 roms are implementing a RIL that relies on the MD4 bootloader.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
So Any idea how to pass the status 7 error, I am trying to update to CM 10.1.2 stable and I can't pass the ROM installation because of status 7, removing the security checks doesn't work either.
EDIT: I thought i had the right boot loader, It seen like i don't...
Maturola said:
So Any idea how to pass the status 7 error, I am trying to update to CM 10.1.2 stable and I can't pass the ROM installation because of status 7, removing the security checks doesn't work either.
EDIT: I thought i had the right boot loader, It seen like i don't...
Click to expand...
Click to collapse
Lol...
I just sideloaded KitKat on my Nexus 7 2013 edition 32 GB. Yesterday, however, I received a notification about a second update (KRT16S) so I download the update and proceed to install. As soon as it booted into recovery it gives an error and installation aborts. I then press power+vol.up key to get the reboot option and get back into Android. No other error surfaces at this point except I'm not running the KRT16S version and when i go to check for updates I'm no longer prompted to download anything. I'm rooted with stock recovery and stock Android 4.4 (KRT16O).
I know Google updated the firmware images and I want to make a firmware restoration from the newest firmware image but I haven't found any solid description of the procedure anywhere on the internet so I'm asking if someone could help me.
Edit:
Never mind guys. I finally made it. All I had to do was realize I had do extract the restore image in the "Platform Tools" folder and not anywhere else. Everything is fine now and I'm running KRT16S. Thanks for everyone jumping in to help anyways. Good luck.
Hello
As I see my topic is not new, seems lots of people have my problem.
My phones is I747m and Telus, I want to install a CM custom rom but i'm getting status 7 error
I tried to remove the lines till ";" but for some roms after that i get Status 6 error, and some other roms i still getting 7.
I wanted to install boot_CWM but again i got Status 7 error. I installed TWRP recovery, and tried to install rom with that one, and again i got other errors . I also Enabled signature check by clicking on "Toggle signature verification" but didn't work too.
My android version is 4.4.2
Last year i installed custom rom but now i can not do that.
would be great if someone could help me.
Solved
Hello again
Finally i made it. Instead of removing all those lines, I replace my phone model with one of them in the text. So i installed version 4.3 of cyanogenmod, because on version 4.4 i couldn't restore my xml sms backup. Now upgrading to last version.
thanks
:good::good:
Hi friend. I use Samsung Galaxy Tab 2 7.0. First, I root this device use Root Master apk and it work ! Second, I use Rom Manager to get CWM and I installed CWM from that application. Third, I download two rom which is CM KitKat and SlimKat. When I want to flash CM rom, I get 'ERROR STATUS 7, INSTALLATION ABORTED' . After a few days, I tried to install my second rom SlimKat but I also get the same error status 7. How to fix this ? Now, I run in 4.1.2 JB. Sorry for my bad english
Sent from my GT-P3100 using XDA Free mobile app