FORUMS

Android 5.1.1 Omni ROM For Motorola Xoom

Back in Feb 2011, the Motorola Xoom became the first device to be sold with Android 3.0 … more

CleanSlate Brings Fingerprint Scanner Mod to HTC One M9+

Work of XDA Recognized Developer tbalden, CleanSlate custom kernel for the HTC … more

Sunday Debate: Which Factors Caused HTC’s Woes?

Join us in a fun Sunday Debate on HTC’s situation. Come with your … more

HTC’s New Ad Campaign And What It Really Means

HTC has just released three new blind test adverts comparing app loading … more

[ROM][Factory Image][4.2.2] Nakasig -::- Odex, Deodex, Rooted -::- teshxx (02/14/13)

1,630 posts
Thanks Meter: 3,313
 
Post Reply Subscribe to Thread Email Thread
17th February 2013, 08:00 AM |#41  
Member
Thanks Meter: 14
 
More
Quote:
Originally Posted by phonic

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.

YES!!! It's great solution Thanks!
 
 
17th February 2013, 08:58 AM |#42  
Member
Flag Las Vegas
Thanks Meter: 18
 
More
Quote:
Originally Posted by phonic

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.

If I think my bootloader updated ok do I really have to start at step 1 again? Or can I find the stock 4.2.2 recovery and start at step 3?
17th February 2013, 10:05 AM |#43  
Member
Thanks Meter: 14
 
More
That does not matter. If you are sure that bootloader is correct (the version number displays in bootloader mode), you can start with the flashing of recovery. But even if you start with step 1, it will not hurt.
The Following User Says Thank You to verfahrer For This Useful Post: [ View ]
17th February 2013, 04:33 PM |#44  
enzoevo's Avatar
Senior Member
Thanks Meter: 140
 
More
Quote:
Originally Posted by psloan

Odd since flashing the image. The nexus root toolkit v1.62 from WugFresh won't recognize an ADB device. Anyone else?

Did you update adb and flashboot to the latest versions?
17th February 2013, 05:19 PM |#45  
Junior Member
Flag Singapore
Thanks Meter: 1
 
More
Re: [ROM][Factory Image][4.2.2] Nakasig -::- Odex, Deodex, Rooted -::- teshxx (02/14/
Finally managed to update my N73G to 4.2.2 thru OTA.

Following the advise of the kind ppl here, I had restored to the stock recovery which is critical to the update process.

Sent from my GT-I9300 using Tapatalk 2
17th February 2013, 05:32 PM |#46  
enzoevo's Avatar
Senior Member
Thanks Meter: 140
 
More
Quote:
Originally Posted by phonic

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.

Thank you so much for this. Worked like a charm.
18th February 2013, 08:33 PM |#47  
Senior Member
Thanks Meter: 11
 
More
thanks phonic.
worked wonderful
19th February 2013, 06:43 AM |#48  
Member
Flag Las Vegas
Thanks Meter: 18
 
More
Used Wugs Toolkit to restore stock recovery. Then flashed the radio again. This time it shows correctly in rom.

I thought it was odd that originally when I flashed the radio that it sent me to TWRP instead of starting SaberMod rom. It makes sense now. Recovery Mode was supposed to finish the process but a custom recovery won't begin the final process.
23rd February 2013, 10:16 AM |#49  
Junior Member
Thanks Meter: 0
 
More
Sorry for newbie question, can someone teach me how to actually flash the bootlaoder and radio through Fastboot?
17th March 2013, 09:31 AM |#50  
Senior Member
Thanks Meter: 20
 
More
Quote:
Originally Posted by phonic

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.

Thank you for the above steps!

http://forum.xda-developers.com/show....php?t=2175086

However I read from the above thread that there's another step to do - Flashing the undo-perm-recovery zip. Is this step needed?

I'm just trying to learn more and clarify things further before proceeding. Hehe
Post Reply Subscribe to Thread

Tags
deodex, nakasig, nexus 7 3g, odex, tilapia
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes