Any way to get the bootloader and radio out of this build? Is the bootloader different than the grouper release? Is the radio even new?
Is it possible to flash only kernel to get pre-root over my stock. I 'd like to retain stock recovery while wanting get rooted. Thanks.
There are bootloader.raw and radio.raw in ota-zip, I'm not sure that we can use fastboot to flash it.
New bootloader version 4.18
New radio version 1231_0.17.0_1205
Sent from my Nexus 7 using Tapatalk HD
I updated the radio and it still shows the old version in about tablet, but it shows the new version if I run dumpstate and on the bootloader screen. Any ideas how to fix this?
Mine shows old baseband in tablet info too. Bootloader shows correct info. I used the Wugs Toolkit to flash the bootloader and radio files from the 2nd post.
Flashed via Fastboot and the same things for me. Bootloader shows correct info but SO report the old...
Why flash new bootloader?
Hi, what´s the advantage of flashing the new bootloader? Will that not break root?
Hi, what´s the advantage of flashing the new bootloader? Will that not break root?
The same situation here: after the flashing bootloader is correct, but the version of radio stays old - 1231_0.10.0_1021.
I ran into many issues trying to get the OTA update to work properly with upgrading the bootloader and radio.
Long story short, I had to do it manually and only after the full system images were released.
If you are running into the problem where the bootloader isn't updated or your radio baseband is showing one thing in bootloader and another in the system status, here is a quick fix:
1) Download the full system image from Google. Untar and unzip.
2) Fastboot flash the bootloader (4.18). Fastboot reboot bootloader. Verify that the version is correct and updated.
3) Fastboot flash the STOCK 4.2.2 RECOVERY. Do not attempt to use CWM or TWRP, otherwise you will have issues.
4) Fastboot flash the 1231_0.17... radio.
5) Reboot into (stock) recovery mode.
6) At this point, the stock recovery should begin to process the radio update and do the actual installation of it. You will see the progress bar moving. When it's done, the tab will automatically reboot into normal mode.
7) Verify that your radio (in system settings) is updated to the latest version.
8) Reflash custom recovery if you want.
After many wasted hours dealing with this issue when the update first came out (OTA), it seems to be related to the bach_update.modem function not being present in custom recoveries. Unlike the system, boot, etc. image files, the radio update is not an actual "image", at least like the others. While it is an ext4 filesystem system, the way it works is more similar to a recovery flashable zip file. It has a set of instructions for recovery to install the radio update. Custom recoveries break at this point, and so far I've only been able to get the stock one to work properly. For some reason, failing on the radio can also break the bootloader update as well, not to mention the build.prop update which is after the radio and might result in an incorrect Android version being identified.
Long story short, I had to do it manually and only after the full system images were released.
If you are running into the problem where the bootloader isn't updated or your radio baseband is showing one thing in bootloader and another in the system status, here is a quick fix:
1) Download the full system image from Google. Untar and unzip.
2) Fastboot flash the bootloader (4.18). Fastboot reboot bootloader. Verify that the version is correct and updated.
3) Fastboot flash the STOCK 4.2.2 RECOVERY. Do not attempt to use CWM or TWRP, otherwise you will have issues.
4) Fastboot flash the 1231_0.17... radio.
5) Reboot into (stock) recovery mode.
6) At this point, the stock recovery should begin to process the radio update and do the actual installation of it. You will see the progress bar moving. When it's done, the tab will automatically reboot into normal mode.
7) Verify that your radio (in system settings) is updated to the latest version.
8) Reflash custom recovery if you want.
After many wasted hours dealing with this issue when the update first came out (OTA), it seems to be related to the bach_update.modem function not being present in custom recoveries. Unlike the system, boot, etc. image files, the radio update is not an actual "image", at least like the others. While it is an ext4 filesystem system, the way it works is more similar to a recovery flashable zip file. It has a set of instructions for recovery to install the radio update. Custom recoveries break at this point, and so far I've only been able to get the stock one to work properly. For some reason, failing on the radio can also break the bootloader update as well, not to mention the build.prop update which is after the radio and might result in an incorrect Android version being identified.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
40ONLY FLASH THIS IF YOU HAVE NEXUS 7 (GSM/HSPA+)
This is a 4.2.2 (JDQ39) Stock Rom made from Factory Image (Nakasig) released by Google on 02/14/13.
Both Deodexed and Odexed versions are available. Both of them are rooted with unsecured boot with init.d support and includes busybox.
Wipe cache/dalvik. Flash via CWM or TWRP. Your data will be preserved.
Deodexed: Link 1
Odexed: Link 1
Please don't forget to hit Thanks and give proper credit when/if you decide to use this as a base.
Cheers!11I ran into many issues trying to get the OTA update to work properly with upgrading the bootloader and radio.
Long story short, I had to do it manually and only after the full system images were released.
If you are running into the problem where the bootloader isn't updated or your radio baseband is showing one thing in bootloader and another in the system status, here is a quick fix:
1) Download the full system image from Google. Untar and unzip.
2) Fastboot flash the bootloader (4.18). Fastboot reboot bootloader. Verify that the version is correct and updated.
3) Fastboot flash the STOCK 4.2.2 RECOVERY. Do not attempt to use CWM or TWRP, otherwise you will have issues.
4) Fastboot flash the 1231_0.17... radio.
5) Reboot into (stock) recovery mode.
6) At this point, the stock recovery should begin to process the radio update and do the actual installation of it. You will see the progress bar moving. When it's done, the tab will automatically reboot into normal mode.
7) Verify that your radio (in system settings) is updated to the latest version.
8) Reflash custom recovery if you want.
After many wasted hours dealing with this issue when the update first came out (OTA), it seems to be related to the bach_update.modem function not being present in custom recoveries. Unlike the system, boot, etc. image files, the radio update is not an actual "image", at least like the others. While it is an ext4 filesystem system, the way it works is more similar to a recovery flashable zip file. It has a set of instructions for recovery to install the radio update. Custom recoveries break at this point, and so far I've only been able to get the stock one to work properly. For some reason, failing on the radio can also break the bootloader update as well, not to mention the build.prop update which is after the radio and might result in an incorrect Android version being identified.1
google is your friend.....
http://droidxblog.wordpress.com/2010/11/10/what-is-odex-and-deodex-in-android-a-complete-guide/
teshxx,
Any better mirror for the deodexed? 4 hours to download for me right now.1
Want to go back to stock so going to give this a whirl but is it necessary to flash these 2 on their own as well??
TIA
