Related
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Diger36 said:
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Click to expand...
Click to collapse
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Chaosblast said:
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Click to expand...
Click to collapse
Now that IS weird. The screenshot you took is indeed the screen you get in Stock Recovery and pressing Volume up + Power simultaniously should bring you into the recovery menu.
If not: I'm afraid this problem is over my head. Sorry about that... Maybe anyone else?
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
Diger36 said:
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
Click to expand...
Click to collapse
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
jhuynh said:
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
Click to expand...
Click to collapse
Oh ok I thought that was the issue! So it's when you install a custom recovery that the OTA updates won't work. Sorry for the incorrect info.
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
danger-rat said:
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
Click to expand...
Click to collapse
Thanks for that. I got bootloader and recovery mixed up!
Thanks all of you guys. That should be the problem. Then I delete the CWM and then update with the OTA. Then I reinstall the CWM and that should be fine.
It's weird because I my cousin has installed the OTA, and he had also rooted his Galaxy Nexus, and I think he also changed the recovery.
Anyway, it's good to know. Thanks again.
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
danger-rat said:
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
Click to expand...
Click to collapse
I don't want to flash any update via CWM for now. I prefer doing that by the official way until I see some ROM that I like.
I understand what you mean of the firmware. But I think I haven't changed the firmware. I mean, I have only unlocked the bootloader, rooted, and then installed CWM. I don't think that changes my firmware.
By the way, I have installed Android System Info, and checked it. But I don't know how to stay sure. I have attached the screenshot.
Thank you.
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
danger-rat said:
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
Click to expand...
Click to collapse
It's true, but where can I find the exact update (not the full ROM) in a zip package? I don't know how to get it from the OTA, and didn't find it on the forum either.
I want to be sure it's the correct update for my version and only the 4.0.1 to 4.0.2 package.
Bump! Could you answer my last question? It's the last one and all this thread is done.
Thank you.
I have exactly the same problem that Chaos, i tried to do the same as you told him but the problem persist, each time that i try to upgrade 4.04 by OTA it stopped and appair the android with the red exclamation on it.
I have the Nexus rooted and the stock recovery flashed
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Jubakuba said:
That's the stock recovery you're seeing.
What images have you changed?
If you revert to the stock ones (radio/bootloader/etc) you should get the OTA.
Click to expand...
Click to collapse
Why dont you show this guy the light and let him flash google factory image by himself..
OP: there you go http://forum.xda-developers.com/showthread.php?p=23229558
Galaxy Nexus AOKP m5 Franco kernel m3
Thank you, guys.
RaptorHawk said:
Hi guys, each time that I try to upgrade 4.04 by OTA, it stopped and appear the Android with the red exclamation on it.
I've used the 'WugFresh unlocked toolkit' to root/unlock Galaxy Nexus.
For install OTA 4.0.4 from Google, I need to lock the phone again?
If I back to default configs - using WugFresh again - the OTA, and after the root/unlock, work without problems?
Thanks.
Click to expand...
Click to collapse
You are seen that screen because you have something on your device that is not stock. (Unlocked and rooted makes no difference.)
To be 100% sure that an OTA update will install automatically, you need to have all of the following:
1) the radio that came with the ROM that you are using;
2) the stock recovery that came with the ROM that you are using;
3) the stock kernel that came with the ROM that you are using;
4) all of the original files in /system that came with the ROM that you are using.
Have a look at the thread here. It is for manual installation of an update, but the requirements still apply to an automatic update OTA.
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
You are not reading at all at what efrant says and you havent looked at the link i provided.. Until you do so you wont go farther
Galaxy Nexus AOKP m5 Franco kernel m3
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Forget about toolkits, follow this guide please
http://forum.xda-developers.com/showthread.php?p=25477039
Galaxy Nexus AOKP m5 Franco kernel m3
RaptorHawk said:
Yes, I read, but maybe I did not quite understand ...
To recap: I used Wug's Toolkit and now I can no longer install the 4.0.4 update official Google OTA. So I would like to know how to undo it, install 4.0.4 and then apply the Wug toolkit again.
According to the links, I need to undo the changes before, but I can not undo the root by Wug's Toolkit, because he can not download a file, appear an error message that could not be found.
What I wonder is, how to get back to what it was prior to applying the 4.0.4 update and then do the root again? Is that possible?
Thanks.
Click to expand...
Click to collapse
There are two ways to get 4.0.4:
1) Flash a full 4.0.4 ROM, which is what the link msedek posted is.
2) Upgrade 4.0.2 to 4.04, which is the link I posted a couple of posts back.
In the first case, you easily end up with a clean install, but your data is erased (so back up before)
In the second case, you need to make sure that you undo any modifications you made to the /system partition, the kernel, the radio, and the recovery. Then you apply the update, and you will have an upgraded ROM with all your data and settings intact.
RaptorHawk said:
So if I uninstalled apps to the system and do the lock/unroot, this will cause problems when I try to upgrade from version 4.0.2 to version 4.0.4?
I uninstalled Google Maps, Youtube and Earth.
Click to expand...
Click to collapse
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
PaisanNYC said:
Actually, this is true. I was having the same issues. When i rooted, I deleted system apps I did not want. For weeks and weeks I kept receiving the popup message saying that the update to 4.0.4 was available. When attempting to upgrade, it would always fail on reboot.
Just two days ago, I received the upgrade notice again. I immediately went into Recovery mode, and attempted to manually install the update file from the system directory. When I did, I received an error right away saying the update could not find "TabletBooks.apk" (I deleted Google Play Books since I dont use it).
I reinstalled a clean image of 4.0.2 I made with ROM Manager weeks ago, then applied the update to 4.0.4 again, and it ran smoothly with no errors, since all System apps were installed with the clean image I saved.
Hope this helps...
Click to expand...
Click to collapse
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If you are going to install a clean image anyway, it doesn't make much sense to install 4.0.2 and upgrade to 4.0.4. Just install the 4.0.4 image immediately...
Click to expand...
Click to collapse
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
PaisanNYC said:
Because you cant just download the full 4.0.4 image and install it via Recovery, can you? I thought you can only install the full image via ADB?
I was able to do all of this while sitting down in the lil boys room, doing my business LOL
Click to expand...
Click to collapse
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
efrant said:
LOL!
Well, I'm not sure where you got a stock 4.0.2 CWM-flashable file, but FYI, you can flash 4.0.4 the same way if you have a 4.0.4 CWM-flashable file (or just replace the 4.0.2 image with the 4.0.4 image in the same CWM-flashable file.
Click to expand...
Click to collapse
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
PaisanNYC said:
Thanks, that's good to know! I come from HTC phones (G1, Nexus One, etc), so Samsung and modding is kinda new to me.
I had a CWM-flashable 4.0.2 file because ROM Manager created the image for me when I first rooted and wanted a backup of a clean stock ROM. I wouldnt even know where to find a CWM-flashable 4.0.4 file on the web. I only know of the stock source files Google has posted. I read that those files can only be flashed with ADB on a PC.
Thanks again!
Click to expand...
Click to collapse
Oh, you were referring to a CWM backup. I understand now.
But regardless, you can still flash the Google images via CWM, they just have to be packaged up in a CWM-flashable zip.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for all help. I'm succesfull flash my GNex.
I check my phone today and I saw that there was a new update to 4.2... so I updated... phone reboot, and after reboot I saw the CWM screen (yes, I'm rooted+ CWM which I installed using toolkit) and I saw the screen on CWM that said: this zip that we are installing is not trusted, do we proceed with the installation... yes or no... so I press yes... then error message appear that cannot be install and phone rebooted again.... was on my home screen.. look over about and same old version 4.1.2... and when I check for update it say that my phone is up to date.... my phone is yakju any idea what happened? any way to OTA the new version? or I will have to flash it?
nicasoft said:
I check my phone today and I saw that there was a new update to 4.2... so I updated... phone reboot, and after reboot I saw the CWM screen (yes, I'm rooted+ CWM which I installed using toolkit) and I saw the screen on CWM that said: this zip that we are installing is not trusted, do we proceed with the installation... yes or no... so I press yes... then error message appear that cannot be install and phone rebooted again.... was on my home screen.. look over about and same old version 4.1.2... and when I check for update it say that my phone is up to date.... my phone is yakju any idea what happened? any way to OTA the new version? or I will have to flash it?
Click to expand...
Click to collapse
I believe you need the stock recovery top install the OTA.
Swype'ed on my CM10 Galaxy Nexus
Herman76 said:
I believe you need the stock recovery top install the OTA.
Swype'ed on my CM10 Galaxy Nexus
Click to expand...
Click to collapse
I just reflash the stock rom from google 4.1.2... no changes, no root (yet), just the bl unlocked. and when I push to get the update says that is up to date. :silly: I have to wait for a couple days or I'm doing something wrong?
nicasoft said:
I just reflash the stock rom from google 4.1.2... no changes, no root (yet), just the bl unlocked. and when I push to get the update says that is up to date. :silly: I have to wait for a couple days or I'm doing something wrong?
Click to expand...
Click to collapse
Go to setting-apps and look for Google Services Framework
Force close it and clear the data. Then check for the update again (it will say you're on the 60s). Keep doing this until the OTA shows up.
Sent from my Galaxy Nexus using Tapatalk HD
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
You're rooted, which means you edited the system, which means the OTA probably won't install. Always better to go back to 100% stock and re-root
ftrack said:
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
Click to expand...
Click to collapse
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
Huh.. I've received JDQ39 ota, I forgot to remove TWRP before hand, but it still went through anyway. It installed fine, surprised the hell out of me actually. TWRP 2.4.1.0. Didn't have any other mods though. Not even rooted.
Sent from my Nexus
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
you can definitely install the OTA with a custom recovery. it however will not install if you modified any /system files, bootloader or radio do not match.
Oh really? That surprises me honestly. Although I never tried it, I always assumed every partition needed to have unmodified stock files (adding extra files does not matter). Apparently the recovery partition is an exception.
Petrovski80 said:
Oh really? That surprises me honestly. Although I never tried it
Click to expand...
Click to collapse
+1
I was really surprised, in a good way! xD
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Dougmeister said:
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Click to expand...
Click to collapse
Don't you have the rom zip saved? It should say what rom it is. Although you should know what you are flashing.
Sent from my Clean Bean v2.6 Galaxy S3
Dougmeister said:
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Click to expand...
Click to collapse
System settings / build number
Sent from my blue galaxy
miller710 said:
System settings / build number
Click to expand...
Click to collapse
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Dougmeister said:
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Click to expand...
Click to collapse
I would suggest searching the Q&A thread for all this. You should read up before you start installing roms or doing any mods to your phone.
Sent from my Freeza MC3 Stock Rooted Galaxy S3
TheSocalGuy79 said:
I would suggest searching the Q&A thread for all this. You should read up before you start installing roms or doing any mods to your phone.
Sent from my Freeza MC3 Stock Rooted Galaxy S3
Click to expand...
Click to collapse
Thanks. Will do.
Dougmeister said:
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Click to expand...
Click to collapse
Might I interject here? If the only reason you want to go back to stock recovery is to get the OTA updates, I personally don't think you need to. Typically, Freeza has the most up-to-date Stock, Rooted Rom over in his thread. In my case, he usually has it well before I get the OTA notification from Sprint. If you think his thread is daunting to look at, you really only want to flash one of the following (I always remove direct links to the Roms out of respect for the dev's):
freeza said:
[size=+4]Leaked Builds[/size]
MC3 Full ROM (DeOdex): Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMC3 | Mirror (Thanks HashTagHell)
MD5: 8D714F25612D2CA8F103A63DF902E607
[size=+4]Official Software[/size]
FULL ROM:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMB1 | Mirror | Mirror 2 (Not yet active)
MD5: 37E1CCCB3A30959C64DF238D0BD2B23C
Click to expand...
Click to collapse
The MC3 Rom is a leak of a new OTA that might come out soon (or it'll be incorporated in a future OTA). The MB1 Rom is the most current, stock Rom. All you have to do is flash it and you're updated. If you need help with how to flash it, you can look to my post over here. Since you're going from 4.1.1 to 4.1.2, I'd recommend a "clean install" (step 5 in my instructions) just to minimize the chance of Force Closes, but you should be good if you want to do a "dirty flash" (only wipe cache and dalvik cache). If you dirty-flash, though, any and all troubleshooting will boil down to doing a clean install and seeing if the problem persists.
Also, CNexus has written up a really good OTA Guide to help you understand the whole OTA thing more and to recognize your options. You can check out his post over here.
Hope this helps!
Edit: It might also be good to update your Recovery before proceeding. Depending on how old your CWM is, it might be best to get an updated one (with hopefully fewer bugs). Thankfully, Naddict has created updates that are flashable from the Recovery itself. All you have to do is download the one you want (I'm using TWRP 2.5.0.0, but CWM is fine, too) and flash it in your custom Recovery, then reboot into recovery again.
topherk, thanks!
I took your advice and upgraded my ClockworkMod. (I also installed TWRP, which I think overwrote it, but that's another story).
I'm going to go over your post in more detail (hopefully) this weekend.
I tried flashing some different ROMs to see what they were like. I was not impressed, so I went back to stock.
Can you tell me something? If I use TWRP to back up everything, I still need to install GAPPS, right? Then I need to do something with GAPPS and Platinum Backup before I wipe/re-install to keep all/most of my programs/settings, right? Then run GAPPS again after I flash the new ROM?
Dougmeister said:
I took your advice and upgraded my ClockworkMod. (I also installed TWRP, which I think overwrote it, but that's another story).
Click to expand...
Click to collapse
Yeah, you can only have one recovery installed at once. I use TWRP, others use CWM. In my opinion, it shouldn't matter too much. They're both good and as far as I'm aware, the newest of each are relatively bug-free. The only thing is once you have backups for one, you can't restore them with the other. This isn't that big of a deal, but just an FYI.
Dougmeister said:
Can you tell me something? If I use TWRP to back up everything, I still need to install GAPPS, right? Then I need to do something with GAPPS and Platinum Backup before I wipe/re-install to keep all/most of my programs/settings, right? Then run GAPPS again after I flash the new ROM?
Click to expand...
Click to collapse
I'll break your questions here:
As far as I'm aware, all TouchWiz Roms include GAPPS in them by default. Of the flip side, no AOSP Roms will include them. This is because Google has asked dev's to not include them (in a Rom) unless specifically approved by Google. Samsung has gotten that approval for their TW framework, so any Rom based on TW can (and do) include GAPPS. If you're in doubt and the Rom doesn't say, first re-read the thread, as it's a common question. Then you can just flash the Rom without GAPPS and load up your phone. If GAPPS is included, you'll have a play store. If not, then you can just reboot into recovery and install it. Easy as pie.
I believe you mean Titanium Backup (another precious metal). Using TiBk, I actually have an automatic restore done every morning at 3am. Then if I decide to flash a new Rom, I always have an up-to-date backup of my apps. I never restore system apps, as that's just asking for trouble when switching Roms. I always back up my messages and phone log, but nothing that's red in TiBk. And for most apps, you don't have to restore data (only the app). I only restore data for games and apps like Hulu so I don't have to log in again.
Hoep this helps!
Yeah stock based roms will include GAPPS, AOSP roms cant because they arent officially licensed to distribute them...
As for the original question, I think I have it figured out. If you go to /system/build.prop and open that file, the great majority of devs will modify the relevant lines to the name of their custom roms. On cm roms theres a line called "cm.version=", which devs will usually modify that on a CM rom
The name is in there somewhere...could be changed on a couple lines, or on ALL the relevant lines, but it will be changed most of the time
Hope this helps
Is there a way to just directly upgrade Jellybean from 4.1.1 to 4.1.2 without having to re-install (via Gapps?) all of my applications, etc.?
I thought I read that I could unroot, do the OTA upgrade, then root again? I'm reading the OTA guide by CNexus, and 'freezing' the update app seems like a good option, but that just keeps the nag screen away.
Dougmeister said:
Is there a way to just directly upgrade Jellybean from 4.1.1 to 4.1.2 without having to re-install (via Gapps?) all of my applications, etc.?
I thought I read that I could unroot, do the OTA upgrade, then root again? I'm reading the OTA guide by CNexus, and 'freezing' the update app seems like a good option, but that just keeps the nag screen away.
Click to expand...
Click to collapse
All you need to do is follow the guide. You can download the MB1 firmware from freezas thread, and then flash an updated version of your rom. If you are on stock rooted, then you can flash one of freezas plain stock rooted roms over what you have (i would recommend a backup first though)
Just a small correction Gapps strictly refers to Google made apps (maps, play store, books, etc) you usually only flash these when working with AOSP roms. You sound like your talking about Touchwiz roms and thus your not loading all your apps through gapps, because Gapps are already included with Touchwiz roms. What you are referring to is reloading all your apps through Google Play Store and using the Google restore feature.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Yes! I'm talking about:
1) Backing up everything on my Galaxy S3
2) Installing other ROMs (sometimes stock, sometimes AOSP)
(side question: "stock" = "TouchWiz"???)
3) Magically re-installing *all* of my apps in the new ROM by clicking a single button
To do that, I'll need to use the "Google restore" feature?
Dougmeister said:
Yes! I'm talking about:
1) Backing up everything on my Galaxy S3
2) Installing other ROMs (sometimes stock, sometimes AOSP)
(side question: "stock" = "TouchWiz"???)
3) Magically re-installing *all* of my apps in the new ROM by clicking a single button
To do that, I'll need to use the "Google restore" feature?
Click to expand...
Click to collapse
Titanium backup is what I use. Paid version and you dont have to click ok for each app
Sent from my blue galaxy
miller710 said:
Titanium backup is what I use. Paid version and you dont have to click ok for each app
Sent from my blue galaxy
Click to expand...
Click to collapse
You don't have to hit ok for each app when you use google restore the correct way. It automatically reloads your apps on your device. TB is a great also but never restore data it is the root of most issues caused when people use it.
Transmitted with a portable device using Xparent Blue Tapatalk 2