I keep getting the new OTA IMM76I update for my Sprint Galaxy Nexus and every time it downloads & starts to install it just opens up TWRP recovery and nothing happens...
I tried to use the Nexus Toolkit as well and do exactly what it says but get hung up on "waiting for device" after it extracts the files and everything...
I've been searching for 4 hours to try to get this update done because my calls keep dropping...
is it because I have the Franco Kernel installed on a rooted device?
no ROM or anything, just rooted with the Franco Kernel...
I tried like hell to find the stock kernel but couldn't...
DAMN this is aggravating
could someone PLEASE either explain or point to a link where it explains how to deal with this issue?
HATE having a brand new phone and the calls keep dropping....
I know there are "lots of threads on this issue" already but none clearly explain how to fix THIS issue...
please hep me out...thanks in advance.
http://forum.xda-developers.com/showthread.php?p=20843237
While the above link is for how to manually install updates, the reasons why an ota update won't install are the same: if you want it to install ota, you need: the stock kernel, stock recovery, stock radio, and stock rom (with no original files missing/modified). Additionally, all of these have to be the same version.
Maybe you could also get the ota update file name for us as well.
Sent from my Galaxy Nexus using Tapatalk 2
does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
another issue I'm having is damn CWM....I have TWRP on here now and when I go to flash CWM through ROM Manager it get all the way to the end, freezes then fails...can't seem to get CWM installed for my life.
also what is all this "yakju, takju, etc..."??
I'm new to this device from an Evo 4G where we just download & flash and all updates work..never had an issue like this.
my device is v4.0.4., build Imm76D.L700FC12
baseband L700.05 V.FC12/L700.FC12
on the bootloader I saw "toro" on there so I'm guessing that's because it hasn't been updated, correct?
thanks.
broad_st_bully said:
does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
Click to expand...
Click to collapse
If all you changed is the kernel, then all you have to do is flash the stock kernel.
efrant said:
If all you changed is the kernel, then all you have to do is flash the stock kernel.
Click to expand...
Click to collapse
would you have the stock kernel?
can't seem to find it...
Try the GN root kit. You'll find it in the dev section. That will get you back on stock kernel.
Sent from my Galaxy Nexus using Tapatalk 2
You need to have stock recovery too.
broad_st_bully said:
would you have the stock kernel?
can't seem to find it...
Click to expand...
Click to collapse
Unfortunately I do not (I don't own a Sprint device), but I'm sure that it is floating around somewhere.
Related
Hey guys,
I'm one of the many Galaxy Nexus owners that don't like their battery usage at all. The device is a yakjuxw build running 4.0.1.
First thing I wanted to do was to update to the official 4.0.2 image from Google. Now lurking through all these threads I saw that most of you recommend franco's kernel for its awesome battery performance. By flashing that custom kernel will I still be able to get OTAs? (on a stock official 4.0.2 image)
Also, some of you reported that the 4.0.2 OTA was pulled back due to some issues. Should I still flash the 4.0.2 image in this case?
Thanks,
NiGhTTraX
To flash a kernal, you need a unsecured boot.img. Its is usually provided with roms but if you want just the Kernal you will need it. To flash that you need to flash recovery Clockworkmod preferably.that will not stop you from getting otas but ubwont be able to install them as ours need stock recovery. So in essence, yes it will prevent you
Sent from my Galaxy Nexus using XDA App
You need clockwork to flash a zipped file. To flash a boot.img all you need is fastboot. And i highly recommend manually flashing 4.0.2. You dont need clockwork recovery. And flash a radio more suitable to your region. That too will help battery life.
Sent from my Galaxy Nexus using xda premium
pr3cision said:
To flash a kernal, you need a unsecured boot.img. Its is usually provided with roms but if you want just the Kernal you will need it. To flash that you need to flash recovery Clockworkmod preferably.that will not stop you from getting otas but ubwont be able to install them as ours need stock recovery. So in essence, yes it will prevent you
Click to expand...
Click to collapse
I thought that if you don't delete the boot recovery image using the root explorer app, once you restart the phone CWM will be overwritten by the factory default image. So shouldn't that allow OTAs to be applied?
@rbiter said:
You need clockwork to flash a zipped file. To flash a boot.img all you need is fastboot. And i highly recommend manually flashing 4.0.2. You dont need clockwork recovery. And flash a radio more suitable to your region. That too will help battery life.
Click to expand...
Click to collapse
So just flashing the 4.0.2 will still get me OTAs right? And all I need is fastboot for that, am I right?
NiGhTTraX said:
Hey guys,
I'm one of the many Galaxy Nexus owners that don't like their battery usage at all. The device is a yakjuxw build running 4.0.1.
First thing I wanted to do was to update to the official 4.0.2 image from Google. Now lurking through all these threads I saw that most of you recommend franco's kernel for its awesome battery performance. By flashing that custom kernel will I still be able to get OTAs? (on a stock official 4.0.2 image)
Also, some of you reported that the 4.0.2 OTA was pulled back due to some issues. Should I still flash the 4.0.2 image in this case?
Thanks,
NiGhTTraX
Click to expand...
Click to collapse
You won't be able to use Franco's kernel unless you flash to a rom based on 4.0.3. You can always go back to stock as long as you have cwm recovery. Users always post stock back ups that you can just copy to your phone and restore from.
Sent from my Galaxy Nexus using xda premium
Question about whether I'll get OTA updates on my phone after rooting and unlocking.
I read that if the system folder is modified that will prevent OTA updates. But I'm not sure if I had done anything to modify that folder.
I unlocked and rooted the phone using the Wugfresh Galaxy Nexus Root Toolkit v1.3.
http://forum.xda-developers.com/showthread.php?t=1454314
Then updated CWM with ROM Manager.
I'm curious, too. I suppose I'll find out sooner or later since I have two Nexus at my disposal. Both unlocked, only one with root.
i have heard that you will have to flash updates if you are unlocked and rooted. So your best bet is to flash it through CWM.
I wonder if the radios get flashed with the stock updates? I did flash the leaked 4.0.3 radios and have had much better connection negotiations.
Try searching, there's a big discussion in one of the threads in this forum. It's not as simple as yes or no...
danger-rat said:
Try searching, there's a big discussion in one of the threads in this forum. It's not as simple as yes or no...
Click to expand...
Click to collapse
Yeah, I had seen this brought up in other threads. The answer usually didn't seem clear as you mentioned. So was hoping for clarification.
Sounds like I'll just have to wait and see then.
I really recommend the other thread, and ask questions there - no one wants to repeat that debate all over again, so I'm not even gonna start...
http://forum.xda-developers.com/showthread.php?t=1473305
I found out that one MUST be on the stock 4.0.2 radios in order to flash the 4.0.4 update successfully. I have not tried yet but it is good to know. The radios are definitely flashed (updated) in 4.0.2.
You can be rooted and unlocked and still get OTA updates as long as the OS is still stock. You will lose root but you can get that back by rooting again. Running a custom ROM will change that though.
Which is the best/fastest/easieast way to get the stock recovery back? After unlocking/rooting/CWMing , the stock recovery got erased and not renamed. I guess it differs form GSM to CDMA , so if anyone could help me out here (GSM stock recovery wanted) I would appreciate it..
thanks a lot.
http://code.google.com/android/nexus/images.html download the right version from the google factory images. extract the file.
Then search for the image zip, extract the recovery.img.
Then boot into the bootloader and fastboot
"fastboot flash recovery recovery.img".
This will put the stock recovery back onto your device.
thanks a lot mate...already figured it out..
I have unlocked, rooted, and installed Clockwork Recovery on my Galaxy Nexus (GSM, Wind Canada), and now I want to flash 4.0.4 yakju.
My current bootloader is PRIMEKK15 and my current radio baseband is UGLA4
Is flashing 4.0.4 yakju as simple as downloading the image found on google's site (yakju-imm76i-factory-8001e72f.tgz), putting it on the phone, going to Clockwork Mod, navigating to "install zip from SDcard", then choosing yakju-imm76i-factory-8001e72f.tgz, or do I have to open the tgz, then open the tar inside, and then extract this zip and install that in CWM http://i.imgur.com/wXC64.png
Since it's not a custom ROM like AOKP or CM, do I have to wipe data/factory reset in clockwork? Do I have to flash gapps?
Do I have to flash the new bootloader and radio baseband found in 4.0.4 separately?
Also, some people report reception problems with the baseband included in 4.0.4. If I want to go back to UGLA4, is that possible? I would be using the CWM "radio.img" for UGLA4 found here http://forum.xda-developers.com/showpost.php?p=23149491&postcount=139
I think that's all the questions I have, lol.
Well first off, if you're going to do it I'd just recommend you wait for the 4.1.1 image for the GSM GNex to drop. If you're really ansy, then you could flash 4.0.4 and you'll still get the OTA, but just something to think about.
Now to the question, no, you don't flash it like a ROM in CWM recovery. If you wish to completely move to yakju (or takju) to get on the Google update line (not sure why else you'd do it), you need to flash the images via fastboot. All parts of the images. It's important to have the proper bootloader and radio if you intend to receive and automatically install OTA updates. If you don't, you won't be able to install it as it checks for the radio and bootloader as part of the install process.
Follow this guide from Efrant, it's gold: http://forum.xda-developers.com/showthread.php?t=1626895
Don't use a toolkit!
Also, some people report reception problems with the baseband included in 4.0.4. If I want to go back to UGLA4, is that possible? I would be using the CWM "radio.img" for UGLA4 found here http://forum.xda-developers.com/show...&postcount=139
Click to expand...
Click to collapse
I haven't heard about any issues with the latest 4.0.4 radio outside of isolated problems. You can change the radio if you want (via fastboot, rly quick), but as I said, it'll stop you from auto-installing OTAs (which is why you went to yakju, isn't it?). You'll also get a new radio with 4.1.1.
Hmm, I might not even bother, seeing as to get the updates I'd lose CWM and root. Perhaps I will just wait for 4.1 like you said and install that.
By the way, since I am on 4.0.2 but I have CWM, does that mean even if my yakjuux build got 4.0.4 OTA, I wouldn't get notified (because of the custom recovery)??
EDIT: Say Google puts up a 4.1 image next week, I would just need to download it and follow the same steps that are outlined in that post (flashing all the different images in fastboot)?
Matt08642 said:
Hmm, I might not even bother, seeing as to get the updates I'd lose CWM and root. Perhaps I will just wait for 4.1 like you said and install that.
Click to expand...
Click to collapse
You can flash CWM and root it again after going to yakju, but you'll have to update manually (no auto-installing OTA) after that. You have to pull the image and flash it, and use an app like "OTA root keeper" to hold onto root.
By the way, since I am on 4.0.2 but I have CWM, does that mean even if my yakjuux build got 4.0.4 OTA, I wouldn't get notified (because of the custom recovery)??
Click to expand...
Click to collapse
You'll be notified, but the update won't install. It requires stock recovery to auto-install.
Cool. In that case, I will just wait for JB, then once I flash that image myself, I will reflash CWM and root my phone again.
Thanks for the help, and thanks for the link to that thread!
Matt08642 said:
Cool. In that case, I will just wait for JB, then once I flash that image myself, I will reflash CWM and root my phone again.
Thanks for the help, and thanks for the link to that thread!
Click to expand...
Click to collapse
No problem.
Sent from my Galaxy Nexus using xda premium
I am a n00b.
Just today I changed my phone from yakjuux to yakju, and it all seemed to go smoothly.
I am receiving texts, and everything seems to be working, and when I was trying to update to jelly bean OTA, everything was going well, until a little red triangle popped up over the little android, and my phone restarted with no change. I flashed my original radio image (UGLA4) so Im not sure whats up with that. If anyone has any suggestions about how I can fix this it would be greatly appreciated.
If not, I would like to restore my phone to yakjuux using a backup I made using this website: http://forum.xda-developers.com/showpost.php?p=21266325&postcount=239 as a guide. I have all the files saved onto my laptop, but Im unsure about how to use them and restore my phone to its original state (yakjuux)
Many thanks
lechickenwing said:
I am a n00b.
Just today I changed my phone from yakjuux to yakju, and it all seemed to go smoothly.
I am receiving texts, and everything seems to be working, and when I was trying to update to jelly bean OTA, everything was going well, until a little red triangle popped up over the little android, and my phone restarted with no change. I flashed my original radio image (UGLA4) so Im not sure whats up with that. If anyone has any suggestions about how I can fix this it would be greatly appreciated.
If not, I would like to restore my phone to yakjuux using a backup I made using this website: http://forum.xda-developers.com/showpost.php?p=21266325&postcount=239 as a guide. I have all the files saved onto my laptop, but Im unsure about how to use them and restore my phone to its original state (yakjuux)
Many thanks
Click to expand...
Click to collapse
You are seeing the little red triangle because you have an image that is not stock. You need to do the optional steps to get the ota (i.e., you need to flash the bootloader, radio and recovery). Go back to the convert to yakju guide and do them.
P.S. why did you not flash the JB images instead of the ICS images??
Sent from my Galaxy Nexus using Tapatalk 2
thanks
efrant said:
You are seeing the little red triangle because you have an image that is not stock. You need to do the optional steps to get the ota (i.e., you need to flash the bootloader, radio and recovery). Go back to the convert to yakju guide and do them.
P.S. why did you not flash the JB images instead of the ICS images??
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I flashed the bootloader, radio and recovery(I probably should have mentioned that in my initial post). Do I need to download a new image to flash onto my device? And how can I tell if its stock? I got my factory image from the link from your guide.
Im not sure why I didnt flash the JB images... I'll blame it on my n00bery.
Redoing
lechickenwing said:
I flashed the bootloader, radio and recovery(I probably should have mentioned that in my initial post). Do I need to download a new image to flash onto my device? And how can I tell if its stock? I got my factory image from the link from your guide.
Im not sure why I didnt flash the JB images... I'll blame it on my n00bery.
Click to expand...
Click to collapse
Will there be any problems if I follow all the steps in your guide, and pretty much redo everything? I would flash the bootloader, flash the same radio (UGLA4), flash the data paritition, flash the system partition, flash the kernel and flash the recovery the only difference being that I would use the JB image rather than the ICS image.
Thanks again
lechickenwing said:
Will there be any problems if I follow all the steps in your guide, and pretty much redo everything? I would flash the bootloader, flash the same radio (UGLA4), flash the data paritition, flash the system partition, flash the kernel and flash the recovery the only difference being that I would use the JB image rather than the ICS image.
Thanks again
Click to expand...
Click to collapse
There will be no issues. Note that if you flash the UGLA4 radio, the next OTA update will not install. You will need to flash the XXLF1 radio before attempting to install the next OTA update. (That is probably why you are seeing the red triangle -- the OTA is expecting to see the XXLA2 radio, and it is seeing the UGLA4. If you want the update to JB to install, just flash the XXLA2 radio, and the update will install.)
radio
efrant said:
There will be no issues. Note that if you flash the UGLA4 radio, the next OTA update will not install. You will need to flash the XXLF1 radio before attempting to install the next OTA update. (That is probably why you are seeing the red triangle -- the OTA is expecting to see the XXLA2 radio, and it is seeing the UGLA4. If you want the update to JB to install, just flash the XXLA2 radio, and the update will install.)
Click to expand...
Click to collapse
Im worried about not flashing the original radio... Im with wind mobile, and I heard that ugla4 is designed to fix roaming issues with winds service. If I switch the radio to xxla2, Im worried that I might get some of these roaming issues and a rather expensive bill.... thoughts?
lechickenwing said:
Im worried about not flashing the original radio... Im with wind mobile, and I heard that ugla4 is designed to fix roaming issues with winds service. If I switch the radio to xxla2, Im worried that I might get some of these roaming issues and a rather expensive bill.... thoughts?
Click to expand...
Click to collapse
Flash the XXLA2, install the update, then flash back your UGLA4 if you feel it necessary...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Flash the XXLA2, install the update, then flash back your UGLA4 if you feel it necessary...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
After updating to JB, I got prompted to update the OS to 4.1.2 and tried the OTA. For some reason it worked even though i wasn't using the corresponding stock radio image, and now I'm being prompted to do another OTA update (4.2.1). Seeing as the OTA worked last time, I tried to do it once more with the 4.2.1. update, but i ran into the same problem as last time: a little red triangle appeared over the little green android. So I did what you suggested, and flashed the xxla02 radio, and then tried to install the OTA but the little red triangle appeared again. So my question is; are there new corresponding stock boot, radio, and recovery images for JZO54K? If so, i probably still have the boot, radio, and recovery images that were stock to JRO03C.
I figure that if i flash the new stock boot radio and recovery images, the OTA should go smoothly. Any thoughts? Or should I just manually flash the 4.2.1 update that i can download from the google developers website ?
lechickenwing said:
After updating to JB, I got prompted to update the OS to 4.1.2 and tried the OTA. For some reason it worked even though i wasn't using the corresponding stock radio image, and now I'm being prompted to do another OTA update (4.2.1). Seeing as the OTA worked last time, I tried to do it once more with the 4.2.1. update, but i ran into the same problem as last time: a little red triangle appeared over the little green android. So I did what you suggested, and flashed the xxla02 radio, and then tried to install the OTA but the little red triangle appeared again. So my question is; are there new corresponding stock boot, radio, and recovery images for JZO54K? If so, i probably still have the boot, radio, and recovery images that were stock to JRO03C.
I figure that if i flash the new stock boot radio and recovery images, the OTA should go smoothly. Any thoughts? Or should I just manually flash the 4.2.1 update that i can download from the google developers website ?
Click to expand...
Click to collapse
Not all updates will update the radio or boot images, but some will. If you are on 4.1.2, for future updates to work, including 4.2.1, you need the boot, recovery and Radio images from 4.1.2.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Not all updates will update the radio or boot images, but some will. If you are on 4.1.2, for future updates to work, including 4.2.1, you need the boot, recovery and Radio images from 4.1.2.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks efrant, youre a legend. Do you by chance know what the stock radio image for 4.1.2 is? And the boot and recovery images can be downloaded from the google developers web site right?
lechickenwing said:
Thanks efrant, youre a legend. Do you by chance know what the stock radio image for 4.1.2 is? And the boot and recovery images can be downloaded from the google developers web site right?
Click to expand...
Click to collapse
I think it is xxlf1. Go to randomphantasmagoria.com. Oldblue910 has mirrored all the old factory images there.
Sent from my Galaxy Nexus using Tapatalk 2
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
The status 7 error happens when the ROM ur about to flash, checks to see if the model of ur phone is compatible with said ROM. Its a good thing(safety mechanism) but can be a pain at the same time. What version of cwm are u using? Download the latest cwm recovery thru the ROM manager app and that can sometimes fix the issue. What ROM are you trying to install?
Sent from my SAMSUNG-SGH-I337 using xda premium
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
shewantsmyduck said:
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
Click to expand...
Click to collapse
Latest cwm is at 6.0.3.1
I think you're getting a little confused.
You need to be rooted to have any custom recovery installed, so right off the bat you are rooted. You shouldn't flash anything with rom manager, it can cause serious harm to your phone. Tom manager is best for just updating your recovery.
There are two main reasons for a status7 error, out of date recovery or an out of date bootloader.
Update your recovery to 6.0.3.1 and he to flash it again, if it comes back you'll need to update your bootloader a two second search in these threads will provide you with a large handful of threads where people had identical issues as you
Sent from my SGH-I747 using xda app-developers app
Checked my bootloader and it says i747UCDLK3 and I think that's the latest... I'll root and install latest CWM through rom manager once I get home
And one question though... I tried using TWRP 2.5 (the latest) and I still got the status 7 error...?
shewantsmyduck said:
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
Click to expand...
Click to collapse
Can you flash any stock modded rom's ? You state you went back to stock but what method did you use to go back to stock ?
Why oh why were you using jellybam...
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
shewantsmyduck said:
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
Click to expand...
Click to collapse
The ODIN flash to stock 4.0.4 probably installed the old ics bootloaders, and the ota update to 4.1.1 may not have included the new jb bootloaders.
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
shewantsmyduck said:
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
Click to expand...
Click to collapse
That's the right one
Sent from my SGH-I747 using xda premium
So what should I do now then :s
You're trying to flash the wrong rom for your device, or you're not using the right recovery for your device. What Galaxy S3 model do you have? On which carrier are you and where did you buy the phone?
I have an AT&T i747 that I got at an AT&T store. The Rom is correct as I've downloaded it numerous times and I've tried the latest TWRP recovery and still received the error.
I'm going to try and flash a factory image tomorrow from the development section and root afterwards. As Michael3214 pointed out in a pm, the issue may be that my phones id has changed, hopefully a factory image will fix that.