[CWM] JRO03R/JZO54K Binary Drivers (UPDATED 10/10/12)
- Thread starter Jay Aristide
- Start date
It could have something to do with the way PA gathers and displays build information. I'll ask moles and see what he has to say about it. If you didn't get any cwm errors, then it did indeed flash.
I don't have my tablet or PC, but you should be able to compare the md5's of the files in the zip with the files on the tablet to see if they have been replaced to verify the flash worked.
Sent from my ThunderBolt using xda premium
Sent from my ThunderBolt using xda premium
The version of CM that the current version of PA is built on is JRO03R, but without these binaries. That's why my version says JRO03R.
works for me on Stock JR003D DeOdexed with Tablet UI enabled...
Seems quicker, but then it might just be my imagination....
Seems quicker, but then it might just be my imagination....
Yes, but when using cwm, your n7 must be plugged into a computer otherwise cwm wont boot
Then something on your system is broken. The only time you should need to be plugged in to get to recovery is when you're trying to get there from fastboot.
Fixed my touch screen dead spots if I turned on the screen whilst touching it. 
Sent from my AOKP N7 by ME! using xda app-developers app
Sent from my AOKP N7 by ME! using xda app-developers app
True that. I almost never plug my N7 into computer to go into cwm and flash anything. Since I've started using wifi explorer, I generally don't even plug it in to transfer files to/from the PC.
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
98IMPORTANT: There are SEVERAL ROMs out there that build on JRO03R and above sources. Some of these ROMs do contain these binaries, and some of these ROMs do not. The only ways to know for sure would be to compare the MD5 hashes of your binaries against these or ask the developer of your ROM if it includes these binaries.
VERY IMPORTANT: I am now adding the JZO54K binaries compiled for Android 4.1.2 - I HAVE NO IDEA WHAT THESE WILL DO IF YOU FLASH THEM ON 4.1 OR 4.1.1 and I am absolutely NOT responsible for any damage you may do with them. I provide them only as a tool, or for those who may have flashed the JRO03R binaries over JZO54K - YOU HAVE BEEN WARNED
This zip contains the JRO03R/JZO54K binary drivers (depending on which you download).
Included drivers:
* WiFi, Bluetooth, and GPS by Broadcom
* Touchscreen by ELAN
* Orientation sensor by InvenSense
* Graphics & CPU by nVidia
* DRM by Widevine
BEYOND THIS POINT, THERE BE DRAGONS - I am not responsible if you FUBAR your device, but if you follow my instructions, you won't. I've tested this zip on my n7 and my brother's, as well. No issues on either device.
Just put the zip in /sdcard, reboot into recovery and flash it. No need, AFAIK, to clear cache or dalvik, as these are the actual system binaries.
I've noticed faster GPS lock times, marginally better WiFi signal, marginally faster Bluetooth transfers, and considerably better touchscreen response. I haven't done anything to test graphics or DRM yet, but when I do, I'll get back to you.
DropBox JRO03R Download: Nexus7-Binary-Update-JRO03R.zip
DropBox JZO54K Download: Nexus7-Binary-Update-JZO54K.zip5Do you need the stock ROM to flash this, or will any ROM work? I'm using CNA and want the updates.
AFAIK, it works universally. I'm on a CM10 based ROM, personally.
Awexit76, what are you on?5
They're just updated versions of the existing vendor-supplied binary drivers, there shouldn't be any interaction issues with other components. The only differences you should see will be in the components the drivers control (GPS, WiFi, Bluetooth, touchscreen, graphics, and DRM)53You're not using the 4.1.2 grouper device changes (details below)
I assume you mean the 4.1.1 kernel. I'm not familiar with "Buttery Goodness", but I am guessing that the 4.1.2 build you mention contains the new 4.1.2 stuff except for the 4.1.2 grouper device changes. It has not yet been added to the cm10 source yet because the change to fstab requires the new kernel and therefore the new kernel source (since cm10 builds kernels from source), which only showed up about an hour ago. See the "[HOWTO] Build CM10 for Nexus 7" thread where I posted more about this.
To be specific, I can pretty much guarantee you that either your "BG" build does not yet include this device commit and therefore doesn't break the old kernel, or the old kernel has mysteriously included this kernel commit.
ft
PS-- Having now added those kernel commits in and building cm10 from scratch, I can confirm that updating both the device and kernel from 4.1.2 result in a booting system. Look for this stuff upstream sometime soon.
