• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

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

Nice. I had the leaked .315 didn't get the radio update... The .340 OTA updated my bootloader but not my radio. Now I'm good. Thanks!
 
I updated my system to .340 by SBFing with the system update in the TBH app. I know I have the new bootloader. Do I also now have the other updated components (kernel, baseband and radio) or do I have to apply these updates to get them?
 
After last nights mess of threads, some could only wish that was released 3 hrs earlier. Nice work, this should make this smoother for nore people..
 
Hey guys, this is big! From this page: TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader

p3Droid:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader
This is a series of files that will help you update different parts of your phone. These files have all been tested on Consumer phones and have worked successfully, but as with all things hacking, you are responsible for your own phone and behavior.

Install instructions for each of the files below.

1) Download
2) Restart phone with bootstap recovery
3) Select install update.zip and then select the zip you downloaded
4) Resart the phone

*** When performing the baseband update you will need to reactive using *228 ***

_____________________________________________

MBM 30.04 Updater (also known as the bootloader)

This file can be used to update your phones bootloader from any version to the current 30.04 version. Although the current files 2.3.340 and 2.3.320 both worth with 30.03 and 30.04 this will provide you with the most current MBM.

Download file

_____________________________________________

2.3.340 Kernel Updater (2.6.32.9-g55626e1)

While the 2.3.320 kernel released by us will work with either the 2.3.320 or the 2.3.340 build, If you desire to have the most current build then download and install this file.

Download file

_____________________________________________

BP_C_1.09.07P Baseband Updater (also known as your radio file)

Some people have found it difficult to move from the 1.09.06P baseband or have refused official Verizon updates. This file will upgrade your phones radio file to the newest 1.09.07P Baseband.

Download file

_____________________________________________

2.3.340 System Updater <This file functions the same as the system only SBF file>

This file will update your phone to 2.3.340, you may want to wipe your data partition before proceeding as it can lead to a bootloop. With this file and the others above, you can completely upgrade your phone from .320 to .340 with no need for a computer.

Download file​
Click to expand...
 
I downloaded the system only update.zip. So, if sometime in the future, I would would like to return to stock, I can flash this? Or if I would get a bootloop or other nonsense?

I did do the Verizon OTA, so I have the current bootloader, kernel, and radio.
 
I'm on Fission 2.2.2. Can I install these, wiping data, and be on official? And then reroot and instal Fission 2.3?


UPDATE:

I installed them all, wiped data/cache, and did a factory reset then installed Fission 2.3.1 all in one reboot.

Don't.

I got stuck at bootloader. I SBFed, updated, rooted with z4, installed 2.3.1, then installed the Gingerbread theme. Worked like a charm.
 
C0n57an71n3 said:
I'm on Fission 2.2.2. Can I install these, wiping data, and be on official? And then reroot and instal Fission 2.3?


UPDATE:

I installed them all, wiped data/cache, and did a factory reset then installed Fission 2.3.1 all in one reboot.

Don't.

I got stuck at bootloader. I SBFed, updated, rooted with z4, installed 2.3.1, then installed the Gingerbread theme. Worked like a charm.
Click to expand...

Same thing here. You can't even go from .315 to .340, you have to first SBF the .320 full version, then the .340 System only until the full.340 SBF is out... Lame but worth it. Apex 1.3 rox!
 
BuGSmx3 said:
Same thing here. You can't even go from .315 to .340, you have to first SBF the .320 full version, then the .340 System only until the full.340 SBF is out... Lame but worth it. Apex 1.3 rox!
Click to expand...

I have went from 2.3.15 to .340 no problem.

I believe this is the suggested way since you will not get the updated kernel otherwise. If you move from .15 to .320 you will be stuck with the .340 kernel. Even if you SBF the .340 SBF, it is only a SYSTEM ONLY SBF. Which sucks, yet I'm still grateful for.

I was running ApeX - and all I did was load my CLEAN nandroid of 2.3.15 and pushed the OTA through the settings. I lost root so I'm trying to reroot it again. (Isn't everyone doing the Z4 root method now?) I'm trying to find that because it's not in the market, and if that doesn't work I'll do the D2 method.
 
aloha.android said:
I have went from 2.3.15 to .340 no problem.

I believe this is the suggested way since you will not get the updated kernel otherwise. If you move from .15 to .320 you will be stuck with the .340 kernel. Even if you SBF the .340 SBF, it is only a SYSTEM ONLY SBF. Which sucks, yet I'm still grateful for.

I was running ApeX - and all I did was load my CLEAN nandroid of 2.3.15 and pushed the OTA through the settings. I lost root so I'm trying to reroot it again. (Isn't everyone doing the Z4 root method now?) I'm trying to find that because it's not in the market, and if that doesn't work I'll do the D2 method.
Click to expand...

My Kernal is the 2.6.32.9-gca645...blah.blah.blah one. And I am meaning not to use the Updater. If I should have yes just went back to my clean .315 then went the official OTA, but I didn't, and I don't want anyone else to do the same thing and get a bootloader error. But .320 is the same as .340 except for the system items, so it works all the same. And right now with .340 and apex 1.3 my phone is running Amazing! 1.3ghz seems so much faster than .315 and apex 1.0.2.2.
 
Is that the proper method of installs to get to the current? (bootloader, kernel, radio, system) or does it not matter.
can I apply them without rebooting, or do i need to reboot between each install?
does wiping the data partition wipe all the apps and such?
 
Welll then!@@
I forged ahead, did all of them and did a format system / mount system, installed .340 updater and then let it sit.
took about ...10 minutes to boot, BUT IT MADE IT!
and no app loss!! =D I couldnt be happier!!!!!!
Made me a little nervous sitting there spinning back and forth but it worked by golly!! WOOOT!
So - instead of wiping data, try formatting the system partition first
 
dang i was on .340 tried to apply the kernal update and got caught in a bootloop. trying to restore a backup now may have to sbf again :(


EDIT: ok i dont know how to explain this but when i tried my backup it worked. but the weird part is my phone is now on the newest kernal. may be worth a try if anyone else gets caught in a bootloop when trying one of the above files.
 
I updated to 2.3.40 with the system SBF in the TBH app. My kernel version starts with 2.6.32.9, but the rest after the "-" is different from the kernel version in this post. Are they the same kernels? Do I need to update?
 
madAdam said:
I updated to 2.3.40 with the system SBF in the TBH app. My kernel version starts with 2.6.32.9, but the rest after the "-" is different from the kernel version in this post. Are they the same kernels? Do I need to update?
Click to expand...

I already replied to you on MDW but for anybody else here curious...

The system SBF only updates the SYSTEM and nothing else and that is the reason you still have an old kernel. The purpose of this thread is to give non OTA devices the option to update other components like the kernel.

GMB
 
So, I'm kinda interested here... I thought that one of the biggest problems facing the customization of the Droid X was that we had to boot to the kernel in order to launch Clockwork Recovery (i.e. the bootstrapper), thus making it impossible to update the kernel and therefore making real custom ROMs problematic.

So, while I understand that these are Motorola-supplied files and meet the signature requirements for, say, updating the bootloader, how is the kernel getting replaced while booted into Clockwork Recovery?
 
Darn. I was on an old Kernel. This updated me. Thank you. I'm whole. :D
 
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?
 
You must log in or register to reply here.
Back
Top Bottom