FORUMS
Remove All Ads from XDA

Android 4.1.2 is here!

541 posts
Thanks Meter: 112
 
By rockvoid, Senior Member on 9th October 2012, 06:16 PM
Post Reply Email Thread
9th October 2012, 08:49 PM |#121  
PTzero's Avatar
Senior Member
Thanks Meter: 93
 
More
Quote:
Originally Posted by jaju123

Is there any way I can flash this without anything custom? Is there a recovery mode already on the Nexus 7 I can get into somehow to flash the OTA ZIP?

If you're completely stock you can use this procedure to update:
  1. Download the update file from Google: http://android.clients.google.com/pa...D.03a4eaf9.zip
  2. Download ClockworkMod recovery: http://download2.clockworkmod.com/re....0-grouper.img
  3. Enable USB debug on your Nexus 7 and plug it in to your PC.
  4. On your PC transfer the OTA zip file to your Nexus 7 /sdcard partition with the following command: "adb push 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip /sdcard/" and wait for it to complete.
  5. On your PC, type in "adb reboot bootloader"
  6. On your PC, type in "fastboot boot recovery-clockwork-touch-6.0.1.0-grouper.img". This step temporarily pushes CWM to your Nexus 7 and boots from it. This step is not permanent so you retain stock recovery.
  7. Your Nexus 7 will load up CWM recovery. Use the on screen menus to find the OTA zip file and flash it.
  8. Your Nexus 7 will prompt to reboot when completed.

Good luck!
The Following 5 Users Say Thank You to PTzero For This Useful Post: [ View ] Gift PTzero Ad-Free
 
 
9th October 2012, 08:49 PM |#122  
Junior Member
Thanks Meter: 0
 
More
Just finished updating, system is much smoother and screen sharper. I haven't lost root nor relocked bootloader. I was on Stock d ROM and with r binary drivers. Thanks a million for all the devas for the great Work.

Sent from my Nexus 7 using xda app-developers app
9th October 2012, 08:50 PM |#123  
Senior Member
Thanks Meter: 33
 
More
Quote:
Originally Posted by NeoMagus

Just use rootkeeper before updating if you are worried about root, worked fine here

and yes changing of the build.prop (changing dpi, etc) will cause the update to fail

Any idea what the fix for this is ? (to enable the OTA update)

Sent from my Nexus 7 using xda premium
9th October 2012, 08:53 PM |#124  
NeoMagus's Avatar
Senior Member
Flag East Coast
Thanks Meter: 473
 
Donate to Me
More
Quote:
Originally Posted by drpepe

Any idea what the fix for this is ? (to enable the OTA update)

Sent from my Nexus 7 using xda premium

To cause it not to fail? Be on stock JRO03D, no changes to build.prop or /system , flash back to the factory image if you need to
The Following User Says Thank You to NeoMagus For This Useful Post: [ View ] Gift NeoMagus Ad-Free
9th October 2012, 08:58 PM |#125  
SquireSCA's Avatar
Senior Member
Atlanta, GA
Thanks Meter: 308
 
More
Quote:
Originally Posted by sikagoon7

Remember how you had to specify the exact build number of you Nexus 7 when you used the kit? I doubt Wugfresh would have updated it in the past hour or so. It MAY work though but no guarantees. Flashing manually is safer as you can see what happens and catch any errors.

I didn't use that toolkit, I used another one and I just used it to restore to stock, am now awaiting the OTA and then I will try to re-root it and report back.
9th October 2012, 08:58 PM |#126  
Junior Member
Thanks Meter: 11
 
More
--Installing: /sdcard/package.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image...
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions...
Writing bootloader...
Patching remaining system files...

Install from sdcard complete.

JRO03D successfully updated using CWM 6.0.1.0
9th October 2012, 09:01 PM |#127  
Senior Member
Thanks Meter: 11
 
More
FYI. Latest Trinity breaks on 4.1.2
9th October 2012, 09:01 PM |#128  
Senior Member
Flag Holly
Thanks Meter: 72
 
More
So, I failed to flash the first time via CWM 6.0.1.0.

Read the threads and found out that the modded build_prop can cause the failure.
I removed the build_prop and restored to stock build_prop (simply renamed the build_prop.bak to build_prop after deleting the modded build_prop).

It seems to be updating successfully now.

Booting now and it seems bootloader is still unlocked (open lock icon).

Updaing the apps now. Will see if it retained the root...

Thanks

edit. looks like I have lost root...
9th October 2012, 09:04 PM |#129  
styckx's Avatar
Senior Member
Thanks Meter: 1,469
 
More
I'm just going to sit on rooted stock for a week until developers get up to speed with merging things.. Stock is nice anyway.. JB rules!
9th October 2012, 09:05 PM |#130  
Senior Member
Thanks Meter: 26
 
More
I'm on cm10 ROM with 161 trinity kernel... is there a point I'm attempting to update or will they just be merged..?

Sent from my Nexus 7 using xda premium
9th October 2012, 09:05 PM |#131  
gogol's Avatar
Senior Member
Thanks Meter: 208
 
More
[DELETED]
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes