I need Help With updating , Im Currently on the leak 4.1 update from Google I/O Nexus which is of course rooted and Have CWM installed , now the update to 4.1.1 is showing up do I install the 8 mb file that way or there's another Method I don't want mess up the phone and having to go through the process of restoring the factory image
you can do it manually just to be safe. download this and place it in your sdcard: http://android.clients.google.com/p....signed-takju-JRO03C-from-JRN84D.edfff6d3.zip
boot to CWM and flash it. wipe cache and fix permissions and you should be ok.
once it boots you can root it and delete the recovery-from-boot.p file to get CWM back on too.
Related
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
iamTWOcats said:
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
Click to expand...
Click to collapse
??? The OTA release was for the GSM version. There are many, many 4.1 Android Jellybean roms within the Verizon-specific development sub forum (even some are clean 4.1 with only some prop changes to make it as stock 4.1 possible)
Unlock your phone and root your phone.
Use Rom manager to flash Clockwork Mod recovery.
Download a 4.1 rom from development, put on the root of your /sdcard.
Boot into clockwork with rom manager.
Make a backup of your current rom incase anything goes wrong.
Go into Advanced, Wipe Dalvik Cache.
From main menu, Wipe cache partition.
From main menu, Wipe data partition.
Install zip from sdcard, choose the rom you downloaded. After it installs there is usually the superuser zip you then flash afterword to get root.
Reboot, be patient for the first boot
Profit
iamTWOcats said:
So I found out the hard way that Jelly Bean 4.1 isn't compatible with verizon phones, when trying to upgrade to the OTA release anyway.
With that in mind, will Verizon ever get a release? Or is there a way now to make it work?
Thanks
Click to expand...
Click to collapse
Oh my Lord. Are you serious? This must be a mistaken case of "I can't read a damn thing."
Yeah, I've been running one of these clean 4.1 verizon-specific roms for about a week now, with no issues.....
NeoMagus said:
Unlock your phone and root your phone.
Use Rom manager to flash Clockwork Mod recovery.
Download a 4.1 rom from development, put on the root of your /sdcard.
Boot into clockwork with rom manager.
Make a backup of your current rom incase anything goes wrong.
Go into Advanced, Wipe Dalvik Cache.
From main menu, Wipe cache partition.
From main menu, Wipe data partition.
Install zip from sdcard, choose the rom you downloaded. After it installs there is usually the superuser zip you then flash afterword to get root.
Reboot, be patient for the first boot
Profit
Click to expand...
Click to collapse
This.
I'm on a Galaxy Nexus takju, and I'm trying to install this update. http://forum.xda-developers.com/showthread.php?t=2144568
But as you can see in that thread, I get an error7.
I guess it might has something to do with my gps.conf that I've edited, and even if I edit it back, there are still some changes done to the date and stuff..
I wonder if there are any way to see why the update fails. Like a log file or something.
Also, what is the easiest way to restor that part then, without wipeing to phone?
EDIT: Also I got the right drivers installed for my win8 computer, but with both Galaxy Nexus toolkit and Nexus Root Toolkit, I can't install the update with adb sideload...
/Söder
you will never be able to update with any method because you modified a system file. you need to completely revert it back to stock (pull it from one of the images).
also, it will tell you in the error 7 message why it failed.
Zepius said:
you will never be able to update with any method because you modified a system file. you need to completely revert it back to stock (pull it from one of the images).
also, it will tell you in the error 7 message why it failed.
Click to expand...
Click to collapse
Do you mean gps.conf or my /system?
And, how do I pull the gps.conf from a image file and push it still intact?
When I get the error I can't see the complete message. But it say something about /system/lib.
If it is my /system, can I then in some way restore just that?
/Söder
AW: [Q] Check what fails a OTA update?
soder said:
Do you mean gps.conf or my /system?
And, how do I pull the gps.conf from a image file and push it still intact?
When I get the error I can't see the complete message. But it say something about /system/lib.
If it is my /system, can I then in some way restore just that?
/Söder
Click to expand...
Click to collapse
The last time it was enough for me to reflash only the system partition. Use fast boot for it and you are on the safe side. The stock Google images are linked in the general and q&a section. The reflash should convert the main and important part back to stock and the ota is possible.
Sent from my Nexus 7
if you are on stock 4.2.1, just flash the rooted 4.2.2 bigxie rom in the dev section and u are ok, no need wipe
u will need to flash also the new radio that u can find in that thread too
Today when I was at schooI I was not able to flash OTA update even with my OTA ROM or Bixgie's OTA ROM so what I did was this:
When I went to home I donwloaded takju 4.2.1 factory images!
I opened CMW and I wiped cache and dalvik cache and then via Fastboot I flashed JB 4.2.1 Takju system and boot and then I flashed old custom recovery 5.#.#... and I was able to update to JDQ39 without losing files from my Nexus..
manumanfred said:
Today when I was at schooI I was not able to flash OTA update even with my OTA ROM or Bixgie's OTA ROM so what I did was this:
When I went to home I donwloaded takju 4.2.1 factory images!
I opened CMW and I wiped cache and dalvik cache and then via Fastboot I flashed JB 4.2.1 Takju system and boot and then I flashed old custom recovery 5.#.#... and I was able to update to JDQ39 without losing files from my Nexus..
Click to expand...
Click to collapse
I extracted the system.img from takju-jop40d-factory-e4d13f14.tar and then did a fastboot flash system system.img
After that I could update. Will boot back and restore my custom system files then, and restore root.
Thanks.
/Söder
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hey all I'm pretty noob with the flashing and wondering if someone can help me move from the ics stock zvb to something 4.2.2
I'm looking for something stable with minimal bugs and no showstopper bugs to use as a daily driver. I want something I can keep a while without reflashing.
All help and handholding appreciated.
I really don't know what steps I have to take and in what order...
Do I have to reflash the radio again?
Thanks
greenmansofla said:
Hey all I'm pretty noob with the flashing and wondering if someone can help me move from the ics stock zvb to something 4.2.2
I'm looking for something stable with minimal bugs and no showstopper bugs to use as a daily driver. I want something I can keep a while without reflashing.
All help and handholding appreciated.
I really don't know what steps I have to take and in what order...
Do I have to reflash the radio again?
Thanks
Click to expand...
Click to collapse
To jump on the 4.2.2 bandwagon you will need to do all of these steps and depending on the actual ROM might take more really read the installation steps before trying anything and definitely make a backup of your current configuration
Make sure you are on the jb ota (android os 4.1.2) or used the appropriate teeny bin
Must be unlocked ( using freegee... available in the market ), rooted, and using team win recovery (twrp)
Make sure ROM and gapps are on your sdcard
Reboot into recovery
Factory reset
Wipe system (not data/media)
Wipe cache and dalvick cache
Flash ROM
Flash gapps
Then reboot and set everything up
spleef said:
To jump on the 4.2.2 bandwagon you will need to do all of these steps and depending on the actual ROM might take more really read the installation steps before trying anything and definitely make a backup of your current configuration
Make sure you are on the jb ota (android os 4.1.2) or used the appropriate teeny bin
Must be unlocked ( using freegee... available in the market ), rooted, and using team win recovery (twrp)
Make sure ROM and gapps are on your sdcard
Reboot into recovery
Factory reset
Wipe system (not data/media)
Wipe cache and dalvick cache
Flash ROM
Flash gapps
Then reboot and set everything up
Click to expand...
Click to collapse
I didn't get the OTA update, I updated via flash to the zvb stock JB using freegee goomanager and twrp. So do I need the zv9 or zvb teenybin? That's one thing confusing me.
Or should I revert back to stock ICS, then do ota to JB then do Freegee again and flash to 4.2.2?
Aftyer all this, my next phone is going to be a Nexus.
greenmansofla said:
I didn't get the OTA update, I updated via flash to the zvb stock JB using freegee goomanager and twrp. So do I need the zv9 or zvb teenybin? That's one thing confusing me.
Or should I revert back to stock ICS, then do ota to JB then do Freegee again and flash to 4.2.2?
Aftyer all this, my next phone is going to be a Nexus.
Click to expand...
Click to collapse
Okay I got my phone restored back to stock zv8 ota updated to sv9 then zvb
Next I saved a bunch of backups both efs and twrp
Then I flashed my new rom, The very lovely Revolt JB. and after clearing cache and wiping it booted...but....I forgot Gapps...:silly:
Question:
can I flash it over the existing install or do I need to reflash both the rom and Gapps at the same time?
Thanks and cheers
just drop gapps in storage and flash it in recovery you dont need to flash rom again
greenmansofla said:
Okay I got my phone restored back to stock zv8 ota updated to sv9 then zvb
Next I saved a bunch of backups both efs and twrp
Then I flashed my new rom, The very lovely Revolt JB. and after clearing cache and wiping it booted...but....I forgot Gapps...:silly:
Question:
can I flash it over the existing install or do I need to reflash both the rom and Gapps at the same time?
Thanks and cheers
Click to expand...
Click to collapse
Hi !
My A100 is rooted and the bootloader is unlocked. It has TWRP custom recovery.
It is running ICS 4.0.3 (image version Acer_AV041_A100_RV16RC02_WW_GEN1)
System Update wanted to install Acer_AV041_A100_RV22RC02_WW_GEN1
I let it run. It downloaded the update and rebooted to Recovery. Nothing more happened.
I found a 56.26MB zip in /system/cache so I wiped Cache, Dalvik Cache and System and tried to flash it but it failed.
I decided to restore from my nandroid backup to get back to the begginig.
My question is: do I have to remove TWRP ans revert to stock Recovery for the update to be possible ?
Thanks.
i may not recommend this update as chances for bricking are very high.
now why your update is not working?
whenever you unlocked the bootloader and installed twrp, it is very likely that you disabled (renamed/deleted) the file to run the upgrade. i think i have seen pio mentioning that to avoid bricking later.
probably other more experienced devs could give more clear answers and suggestions.
DO NOT install/update stock files on custom/and unlocked bootloader. It'll brick. You need to read pio's all in one thread about the A100, before you do any more. If you're wanting to flash stock firmware, you have to flash the A100 blob (bootloader) and flash the stock recovery first.
Sent from my SCH-R760X using xda app-developers app
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
[email protected] said:
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
Click to expand...
Click to collapse
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
mdamaged said:
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
Click to expand...
Click to collapse
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
[email protected] said:
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
Click to expand...
Click to collapse
There are multiple ways to update, you asked about OTA, in order for OTA to work, the OTA expects the device to have certain files at a certain version, one of the things it checks, besides files in /system, when there is a change to it, is the kernel, so a OTA will fail if it checks the kernel and finds timur's in its place, which is why I suggested you just flash the stock boot and system (yes, you can always go back to timur's afterward assuming it is compatible with the new ROM, you will also have to reroot/redo changes to /system).
The OTA is downloaded into /cache, and if the cache is wiped the OTA file will not be there, so once it is downloaded, use a root filemanager, and copy it to your sdcard, then it won't get wiped.
The other way to update is to just flash the changed images individually from the factory images using fastboot, making sure not to flash the images which would wipe any boot, userdata, or custom recoveries...as long as you do not flash boot.img, you will keep timur's kernel, but you will have to reroot/redo changes to /system.
You can also use the factory image flash-all.bat to do this, BUT you must delete the -w option in the bat file, not doing so will result in your device being wiped, you will still have to reflash timur's kernel using this method as well as reroot/redo changes to /system.
Either way, when you update, wipe dalvik and cache before rebooting.
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
[email protected] said:
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
Click to expand...
Click to collapse
Yeah, you can use TiB to backup apps and appdata. I would also advise you do a full nandroid (no need to backup cache though). Save them all to your PC.
As for whether it's worth it, you'll have to read the changelogs for yourself and find out if it is to you or not. Really it's not much work at all to update.
You can always wait around for Android L.