Root Update.zip for . 340 Kernel, Radio Image, Bootloader, and System!

[Kevmueller]

Darn. I was on an old Kernel. This updated me. Thank you. I'm whole.

I know you are (or have been) on ApeX. Did you do anything other than just run the zip for this to work? I want to apply this as well, but I love my set-up right now and don't want to redo it. I am also using JRummy16's Overclocking. Thanks

 

[digdug1]

Bootloader update worked fine. Kernel update is stuck on bootup logo, pulled the battery but it just sticks on the logo. Any thoughts?

Update: went into Moto Recovery and wiped data/factory reset. stuck on boot logo still.

I am on .320

I may need the TBH .320 full sbf, how do I get this if I cannot get to the app?

see my above post. i did a nandroid backup and when my phone rebooted successfully i had the new kernal

 

[GrandMasterB]

Bootloader update worked fine. Kernel update is stuck on bootup logo, pulled the battery but it just sticks on the logo. Any thoughts?

Update: went into Moto Recovery and wiped data/factory reset. stuck on boot logo still.

I am on .320

I may need the TBH .320 full sbf, how do I get this if I cannot get to the app?

I believe the 2.3.340 Kernel Updater (2.6.32.9-g55626e1) is intended for .340 or has it been confirmed to work with .320? Also make sure you uninstall and overclock apps from the market before installing the kernel and then reinstall after boot. But if you wiped data and it still won't boot that is likely not your problem.

If you still need that SBF let me know.

I know you are (or have been) on ApeX. Did you do anything other than just run the zip for this to work? I want to apply this as well, but I love my set-up right now and don't want to redo it. I am also using JRummy16's Overclocking. Thanks

Same as above ^ make sure you uninstall your overclock app before installing the kernel and then reinstall after boot. Otherwise you may be stuck at the M and have to wipe data.

GMB

 

[gmenfan83]

I believe the 2.3.340 Kernel Updater (2.6.32.9-g55626e1) is intended for .340 or has it been confirmed to work with .320? Also make sure you uninstall and overclock apps from the market before installing the kernel and then reinstall after boot. But if you wiped data and it still won't boot that is likely not your problem.

If you still need that SBF let me know.




Same as above ^ make sure you uninstall your overclock app before installing the kernel and then reinstall after boot. Otherwise you may be stuck at the M and have to wipe data.

GMB

maybe if you dont actually use and apply your oc app it will be ok because i used all of these while having my oc app installed or maybe i just got lucky

 

[GrandMasterB]

maybe if you dont actually use and apply your oc app it will be ok because i used all of these while having my oc app installed or maybe i just got lucky

Yeah, you dont have to remove the OC apps. Its just a precautionary measure because there were quite a few people who got stuck at the M after updating the kernel because the OC app was trying to OC at boot. I removed mine just to be safe

GMB

 

[gmenfan83]

Yeah, you dont have to remove the OC apps. Its just a precautionary measure because there were quite a few people who got stuck at the M after updating the kernel because the OC app was trying to OC at boot. I removed mine just to be safe

GMB

i see , just another reason why i dont set mine to boot ...granted for those of us who are constantly flashing and rebooting it can be a pain to remember to reset your oc after a boot but the set on boot can cause a mess

 

[Napalm]

I can't seem to sbf so let me ask a what is probably a set of dumb questions.

Can I use recovery on a rooted stock rom 2.3.15, and use the TBH zips to update all the bits?

I can't sbf to any version as RSD lite doesn't recognize my device. (no I haven't tried different computers as I only own one computer)

or ?

 

[GrandMasterB]

I can't seem to sbf so let me ask a what is probably a set of dumb questions.

Can I use recovery on a rooted stock rom 2.3.15, and use the TBH zips to update all the bits?

I can't sbf to any version as RSD lite doesn't recognize my device. (no I haven't tried different computers as I only own one computer)

or ?

I don't want to break your heart but it is very possible that you will end up needing to SBF when you start flashing these updates. If you end up stuck at the M like dhoffman above and you cant SBF....truly SOL.

Lets figure out why you can't SBF first. Have you tried manually putting the device in bootloader and then connecting to RSD lite? Power on while holding the camera button and volume down until you see a little screen flash, then let go. (my apologies if you have already tried this)

GMB

 

[Kevmueller]

I thought I would share with everyone what I did this morning in hopes that it will help if it happens to anyone else.

I was/am on Apex 1.3.0 with the .320 leak applied, however I wanted to clean-up all my apps so I figured it would be nice to have a clean .340 back-up of the basic OTA. So I started by doing a factory reset.

I then updated the bootloader and rebooted, no problems.
I then updated the kernel and rebooted, no problems.
I then updated the baseline and rebooted, no problems.
I then did a data and cache wipe and updated the system .340 and rebooted.....oh crap! I am booting in to the bootloader screen. This has never happened before so I freaked out for a moment and then remembered what I had read before. I had a copy of RSD Lite 4.8 with me at work and TBH's .320 SBF. So I got everything ready to SBF my phone for the second time (the first time was just to go from the leaked 2.2 back to 2.1 to get the OTA). I had no problems and after about 10 minutes everything worked fine and I was back up and running.
The one thing I noticed was that the kernel was not updated anymore, but the bootloader and baseline both were updated. So instead of trying to use the system zip again and since RSD was already up I found the .340 system only SBF and used that with no problem.
Then I rerooted with z4root, no problems and downloaded clockwork recovery and then reapplied the kernel. Rebooted and now I am up with the .340 OTA rooted. I have made a back-up and have flashed Apex 1.3.0.

I was hoping that I never had to use a SBF to get my phone back working, but I did today and it worked just fine. Not that I wanted to go through this everyday, but it is nice to know with what I have learned from everyone on here and all the tools that the developers have given us that this can be done.

 

[pm1066]

Is there any benefit performance wise to the kernal or baseband updates?

 

[Deleted User]

Is there any benefit performance wise to the kernal or baseband updates?

From what version?

If you're asking if the kernel was improved from 2.2 -> 2.2.1, yes, there were benefits. If you're asking if the kernel was improved from the SBF version of the kernel to this update ZIP file, the answer is a little more vague... but since a major part of this update was to improve kernel stability (i.e. reduce random reboots), there's a good chance that there is some level of improvement.

 

[pm1066]

Sorry I wasn't more clear--from 320 to 340. I only had to update the kernel and baseband. Don't recall the kernel update, but the baseband went from 06 to 07.

 

[madAdam]

I thought I would share with everyone what I did this morning in hopes that it will help if it happens to anyone else.

I was/am on Apex 1.3.0 with the .320 leak applied, however I wanted to clean-up all my apps so I figured it would be nice to have a clean .340 back-up of the basic OTA. So I started by doing a factory reset.

I then updated the bootloader and rebooted, no problems.
I then updated the kernel and rebooted, no problems.
I then updated the baseline and rebooted, no problems.
I then did a data and cache wipe and updated the system .340 and rebooted.....oh crap! I am booting in to the bootloader screen. This has never happened before so I freaked out for a moment and then remembered what I had read before. I had a copy of RSD Lite 4.8 with me at work and TBH's .320 SBF. So I got everything ready to SBF my phone for the second time (the first time was just to go from the leaked 2.2 back to 2.1 to get the OTA). I had no problems and after about 10 minutes everything worked fine and I was back up and running.
The one thing I noticed was that the kernel was not updated anymore, but the bootloader and baseline both were updated. So instead of trying to use the system zip again and since RSD was already up I found the .340 system only SBF and used that with no problem.
Then I rerooted with z4root, no problems and downloaded clockwork recovery and then reapplied the kernel. Rebooted and now I am up with the .340 OTA rooted. I have made a back-up and have flashed Apex 1.3.0.

I was hoping that I never had to use a SBF to get my phone back working, but I did today and it worked just fine. Not that I wanted to go through this everyday, but it is nice to know with what I have learned from everyone on here and all the tools that the developers have given us that this can be done.

Good recommendation for starting fresh with OTA.

I don't care about OTA so here's what I did for my "fresh start" using the TBH files:

1. Factory reset
2. SBF Froyo 2.2.1 Full SBF File (Blur Version 2.3.32)
3. SBF Froyo 2.2.1 System Only SBF File (Blur Version 2.3.340)
4. Root with Z4Root
5. Install DroidX Bootstrapper
6. Boot in recovery, install 2.3.340_kernel_updater.zip
7. Make a backup of your fresh .340 with the latest bootloader, baseband and kernel

You're ready to install the ROM of your choice. I recommend TranQ 3.6 plus the TranQ Toolbox Update.

 

[northernmoris]

I just finished updating all for from .32. I didnt have to clear data or cache. Worked flawless, had to reactivate but kept root and everything else.