FORUMS

What Do You Think About Fingerprint Scanners?

More and more phones are featuring fingerprint scanners, and with many promising … more

What’s Next for Samsung and Its Flagships?

If we were to say that the Galaxy S6 was a leap of faith made by Samsung, we … more

The Ultimate Showcase of dBrand Skins

In the search for ways to protect, accessorize, and personalize; a user has many options. One … more

Huawei’s Rapid Rise to Third Place in the Smartphone Race

Huawei has quickly grown to become one of the world’s biggest … more

Android 4.1.2 is here!

515 posts
Thanks Meter: 108
 
By rockvoid, Senior Member on 9th October 2012, 06:16 PM
Post Reply Subscribe to Thread Email Thread
9th October 2012, 08:34 PM |#111  
ncguy68's Avatar
Senior Member
Flag North Carolina
Thanks Meter: 39
 
More
Will having the tablet UI cause any problems? Will the tablet UI survive the update?

Sent from my Nook Tablet using XDA Premium
 
 
9th October 2012, 08:35 PM |#112  
Senior Member
Flag Central Kentucky
Thanks Meter: 1,160
 
More
So far Flipboard loaded updates in like 10 seconds and I flipped through one section really fast, no lag, no stuttering. Of course I just booted the system, but in the past, Flipboard would lag terribly and take 30-45s to load updates.

Crossing fingers this fixed the IO lag problems..
9th October 2012, 08:35 PM |#113  
SquireSCA's Avatar
Senior Member
Atlanta, GA
Thanks Meter: 255
 
More
Quote:
Originally Posted by sikagoon7

For those who lost root just flash a custom recovery with fastboot, copy these two files to your sd, and flash 'em. I think it should work to at least reinstall su and busybox into your /bin.

Credits go to Wugfresh

What about the all in 1 toolkit that a lot of us used to root and get recovery in 4.1.1?

In it, you can restore the tablet to stock using the latest release from Google. Could we not use that to restore it, take the OTA and then use it again to re-root it and all that?
9th October 2012, 08:35 PM |#114  
sikagoon7's Avatar
Senior Member
Flag Stockbridge, GA
Thanks Meter: 198
 
More
Quote:
Originally Posted by oscillik

Looks like if you've modded your build.prop or put the AOSP browser on your Nexus 7, then you're out of luck.

Gonna have to reflash to factory before I can update now

Awww man! Back to JRO03D...
9th October 2012, 08:35 PM |#115  
oscillik's Avatar
Senior Member
Flag Widnes
Thanks Meter: 133
 
More
Quote:
Originally Posted by ncguy68

Will having the tablet UI cause any problems? Will the tablet UI survive the update?

Sent from my Nook Tablet using XDA Premium

I said a few posts ago - modded build.prop means you can't update.
9th October 2012, 08:37 PM |#116  
Senior Member
San Diego
Thanks Meter: 28
 
More
change log is here:

http://www.funkyandroid.com/aosp-JRO03R-JZO54K.html
The Following 7 Users Say Thank You to denimjunkie82 For This Useful Post: [ View ]
9th October 2012, 08:38 PM |#117  
sikagoon7's Avatar
Senior Member
Flag Stockbridge, GA
Thanks Meter: 198
 
More
Quote:
Originally Posted by SquireSCA

What about the all in 1 toolkit that a lot of us used to root and get recovery in 4.1.1?

In it, you can restore the tablet to stock using the latest release from Google. Could we not use that to restore it, take the OTA and then use it again to re-root it and all that?

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.
9th October 2012, 08:39 PM |#118  
mobilehavoc's Avatar
Senior Member
Thanks Meter: 347
 
More
Anybody have a link to stock kernel and modules for JR003D?

Sent from my Nexus 7 using Tapatalk 2
9th October 2012, 08:41 PM |#119  
NeoMagus's Avatar
Senior Member
Flag East Coast
Thanks Meter: 472
 
Donate to Me
More
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
9th October 2012, 08:47 PM |#120  
mobilehavoc's Avatar
Senior Member
Thanks Meter: 347
 
More
Quote:
Originally Posted by masully84

I got the same thing here man, I restored all disabled apps, never removed any stock apps, no other modifications except renaming the stock recovery awhile ago from .p to .bak. Dunno if that's why or not

Sent from my Galaxy Nexus using xda app-developers app

Getting same thing but I'm running custom kernel so I think that's what it is

Sent from my Nexus 7 using Tapatalk 2
9th October 2012, 08:49 PM |#121  
PTzero's Avatar
Senior Member
Thanks Meter: 91
 
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!
Last edited by PTzero; 10th October 2012 at 05:28 AM.
The Following 5 Users Say Thank You to PTzero For This Useful Post: [ View ]

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes