Database Users

[Q] Original 2.2 Leak to OTA 2.2?

I did the original 2.2 update.zip leak (not the more recent spf of the deodexed 2.2).
I did move the su file before the update.zip and am remained rooted through that upgrade.
What's my upgrade path now to 2.2 OTA?
Do I need to first spf back to 2.1 and then get the OTA? Will I remain rooted through that whole process or will I need to re-root (which isn't a problem?) after? If I do that, can I run a Titanium Backup of my apps and system now on 2.2 leak and just restore everything back once I'm on 2.2 OTA or will I have to reinstall/reconfigure a lot of things.
What about just a simple update.zip that would take me from 2.2 original leak to 2.2 OTA? Is that still being worked on or is this new bootloader preventing that? I saw birdman said he was working on that, but then the whole thing with the new bootloader came up and not sure how that effects this.

Just give Birdman time. If you're impatient, SBF to 2.1, update OTA, and root using the Droid 2 method. If you SBF you will have to restore everything, though.

[Q] 2.1 To 2.2 Leaked Or OTA No Bootloader Flash

So I have a rooted Droid X running official 2.1. I want 2.2 but I want to keep my original bootloader. Is there an update.zip that can take me to the OTA or the leaked OTA without messing with my booloader or recovery? I would also not like to wipe my data ether.
Also just to clarify, I have bootloader version 29.01. The stock image in ROM Manager from what I see requires me to update my bootloader.
Thanks
Edit:
Better question. I was reading around about this and I came across the system 2.2 only SBF. Now it says all it dose is write to the system and nothing else. Can I use this SBF to flash to 2.2 from 2.1 without data wipe and not touch my bootloader at v29.01? Link at http://www.mydroidworld.com/forums/...announces-froyo-system-sbf-rsdlite-4-8-a.html

So I hear there is a new OTA...

I have not installed any leaks after the last official SBF (Stock 2.2). If I SBF back to stock and install the OTA, is there a root method that still works? And is there an SBF for the new OTA? I have the SBF named Happy_Holidays_From_TBH.

zehkaiser said:
I have not installed any leaks after the last official SBF (Stock 2.2). If I SBF back to stock and install the OTA, is there a root method that still works? And is there an SBF for the new OTA? I have the SBF named Happy_Holidays_From_TBH.
Click to expand...
Click to collapse
Z4 has been confirmed to still work.
You might want to save the app to your SD card first, for convenience, and just in case it doesn't show in the market after.
I have not heard of an SBF in the wild, for the new OTA.

.340 SBF isn't out there, yet. Z4root works with 2.2.1

Good to know. I upgraded to the .320 leak. The boot loader has updated, but has the key changed? (can I nandroid back to 2.2.15)

zehkaiser said:
Good to know. I upgraded to the .320 leak. The boot loader has updated, but has the key changed? (can I nandroid back to 2.2.15)
Click to expand...
Click to collapse
Nandroid backups to 2.3.15 *seem* to work, but are strongly advised to be avoided. The kernel and bootloader (and associated keys) will still be from 2.3.320/340. You won't be able to use the OTA to get to .340. If you're already on .320, get the system only SBF to get you to .340 (yes, it's out now) and call it a day.

just updated to .602 with root/no root

Everything went fine. But titanium backup cannot acquire root permissions even though superuser is there. Tried updating superuser, but I have to flash some binary stuff. Tried to then access recovery through clockwork (rom manager) and it does nothing. Tried going through recovery the old school way (holding power and home button) and that does nothing. What the heck is going on?

You can't update to an ota without losing root. That's just how it is. Sbf and start over. Install only pre rooted updates, usually from Team Black Hat.

I did do the over the air update. I first SBF'd back to .340, then followed the steps on mydroidworld as I thought the teamblackhat app update wouldn't work and that I needed to follow the mirrors. Can I SBF back to .340 even with the new radio and update that is on .602?
edit: I'm sbfing back now, looks like the mirrors that were posted had soemthing wrong with them. I'll use the TBH app to upgrade from .340 to .602

I've got a semi related (noob) question here: I just rooted my phone and now it wants me to upgrade to. 602, and I keep telling it to do it later. I understand upgrading will cause me to lose my root, yes? If so is there a way I can get it to stop trying to upgrade? Is it safe to just remove upgrade.apk using titanium backup? Cheers,
Sent from my DROIDX using XDA App

I posted a guide on MDW, but here are the steps:
* Download .602 AIO updater from TBH App
* SBF back to .340 (Don't use the AIO)
* Activate phone,Root (Z4Root) and Bootstrap (D2Bootstrap)
* Format: System - Data - Cache - Dalvik
* Mount System
* Install .602 AIO from TBH App
* Reboot
* Profit
(In some instances you might have to go in and do a factory reset after the update to get everything up and running properly)

deadpixell said:
Everything went fine. But titanium backup cannot acquire root permissions even though superuser is there. Tried updating superuser, but I have to flash some binary stuff. Tried to then access recovery through clockwork (rom manager) and it does nothing. Tried going through recovery the old school way (holding power and home button) and that does nothing. What the heck is going on?
Click to expand...
Click to collapse
On TB when the no root message comes up click problems? and install the busybox it prompts for you. that will fix it not seeing your root

are there any methods in the works to root if you're already on .602 ota? I really don't feel like sbfing again =\.

zehkaiser said:
You can't update to an ota without losing root. That's just how it is. Sbf and start over. Install only pre rooted updates, usually from Team Black Hat.
Click to expand...
Click to collapse
Not entirely true. Do a google search for "602 update without SBF".
Basic idea:
Pre-Installed Clockwork
Superuser in zip format on sdcard
Rooted 596
Install OTA 602
Reboot
Pull battery while still on
Auto boots in Clockwork
Install SU zip file
I used this procedure. Was quick and painless. Do not simply use my instructions though. Look for the original post. I will look for the link later.
Sent from my DROIDX using Tapatalk

Tadpole's thread on MDW worked flawlessly, no SBF needed woohoo. The main factor is you have to be fully stock. Phone reboot after this method does take a little longer than usual on the first reboot but its awesome to see the little indicator after rebooting "Droid 2 Boostrapp has been granted superuser permissions" without having to SBF, install and then CWR and reinstall data blah blah blah.
Thanks again Shibbey75!

Official CM 7.2 release candidate 1

Just wanted to let folks know who may be interested in trying out the new CyanogenMod 7.2 rc1 Shadow for our Droid X that you may experience a problem like I did when you try and flash this build.
I had already taken the .621 OTA update (which made me lose root) and then flashed the Milestone X .604 sbf file (which leaves our baseband radio alone for data) using sbf_flash in linux, then using the zerg root tool to regain root on this phone, then used the Droid 2 Bootstrap to get to clockwork recovery.
When I flashed this build I get the dreaded bootloader error screen after the reboot. I've tried this CM7.2rc1 twice now and each time after I reboot it shows me the bootloader screen with an error code and doesn't go any further.
It didn't give me any problems when I flashed an unofficial CM9 beta though. It's running fine on this phone.

sjmoreno said:
Just wanted to let folks know who may be interested in trying out the new CyanogenMod 7.2 rc1 Shadow for our Droid X that you may experience a problem like I did when you try and flash this build.
I had already taken the .621 OTA update (which made me lose root) and then flashed the Milestone X .604 sbf file (which leaves our baseband radio alone for data) using sbf_flash in linux, then using the zerg root tool to regain root on this phone, then used the Droid 2 Bootstrap to get to clockwork recovery.
When I flashed this build I get the dreaded bootloader error screen after the reboot. I've tried this CM7.2rc1 twice now and each time after I reboot it shows me the bootloader screen with an error code and doesn't go any further.
It didn't give me any problems when I flashed an unofficial CM9 beta though. It's running fine on this phone.
Click to expand...
Click to collapse
What clockwork version?
Sent from my potted plant running Liberty 3

watt9493 said:
What clockwork version?
Sent from my potted plant running Liberty 3
Click to expand...
Click to collapse
I don't remember the version if you're asking for the version of cwm recovery the droid 2 bootstrapper installed on my phone before I flashed the CM9 beta.
However, there are a lot of folks reporting the same issue over on RootzWiki about not unnecessarily this CM7.2r1 but with flashing any non-2nd-init roms after going from .621 to .604.

sjmoreno said:
I don't remember the version if you're asking for the version of cwm recovery the droid 2 bootstrapper installed on my phone before I flashed the CM9 beta.
However, there are a lot of folks reporting the same issue over on RootzWiki about not unnecessarily this CM7.2r1 but with flashing any non-2nd-init roms after going from .621 to .604.
Click to expand...
Click to collapse
Try cwm 5? From rom manager?
Sent from my potted plant running Liberty 3

sjmoreno said:
I don't remember the version if you're asking for the version of cwm recovery the droid 2 bootstrapper installed on my phone before I flashed the CM9 beta.
However, there are a lot of folks reporting the same issue over on RootzWiki about not unnecessarily this CM7.2r1 but with flashing any non-2nd-init roms after going from .621 to .604.
Click to expand...
Click to collapse
Someone just posted this to the Rootz thread a bit ago:
Skreelink said:
Full process (assuming you know exact details to do each step)
1: SBF 621 with RSD Lite to make sure you have 15p Radio
2: SBF 604 in Linux to install 604 Rootable system.
3: Root with Zergrush V4
4: Use Droid 2 Bootstrap to bootstrap recovery
5: Install ROM Manager
6: Install latest CWM (Droid X version NOT DROID X 2ND INIT) using Rom Manager
7: Copy your ROM zip or previous nandroid backup to SD card.
8: Reboot into recovery from Rom Manager
9: Clear User data/Factory reset
10: For good measure, wipe cache as well.
11a: Install zip from SD card, install your rom
11b: Restore previous 602/605 GB nandroid backup.
12: Reboot and eat bacon with your awesome phone
Click to expand...
Click to collapse
Looks like you need the latest DX CWM.

So the official Droid X nightlies are finally on the Gingerbread kernel?
Sent from my DROIDX using Tapatalk

Not working for me. I've done every step in that list over the past day and no luck, I'm still getting the error when I try to flash cm7. I'm using CWM 5.0.2.0, the one that ROM Manager updated it to for me and still nothing.

BrahManty said:
Not working for me. I've done every step in that list over the past day and no luck, I'm still getting the error when I try to flash cm7. I'm using CWM 5.0.2.0, the one that ROM Manager updated it to for me and still nothing.
Click to expand...
Click to collapse
This may still be based on the Froyo kernel. I haven't heard otherwise.
Sent from my DROIDX using Tapatalk

infazzdar said:
This may still be based on the Froyo kernel. I haven't heard otherwise.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
If it is based on froyo you will get bootloader error everytime stick to gingerbread