That leak would get you to .320. I think after that you would still have to use the .340 system only sbf. I would really not attempt too much without a computer that you could use with the SBF right handy on them.... I do not think every store will do it for you, my two local stores they barely know how to turn on the phones and there response to EVERY problem is factory reset lol.... Might try it but I think with Rubix on the phone they might not wanna help too much hopefully they will for you.
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
will pay for help
- Thread starter chefb
- Start date
If he never loaded the leak, he is NOT already there. 1.8.9 build.prop reads 2.3.20, so it reads that in about phone as well.
So if he is using the thb app cant he install the blur_2.3.320_system_2.2.1 deodexed update.zip and run that from recovery then once thats done install the patches in this post? TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader
Yes he could but I would recommend he NOT do the bootloader/kernel/baseband patches until he is capable of SBFing. In the 2 attempts I've made at installing all 3 of those, I had to SBF back to 320 and then go to 340 one more time (two different Droid X's - once you get one to 340 fully, then no more SBFs were necessary except for the 340 system-only SBF).
The patches stated above are for those people who got the leak and needed to get up to date with the Verizon up date I'M looking for that fist leak from black hat that put everyone else on the path to add those patches. After I down load rubix 1.90 leaked version.
Yeah, that's normal. To get to custom recovery, you need to bootstrap every time.
Can't you just install the OTA, or the update.zip of the OTA that is floating around?
EDIT: Just read thread. Didn't realize you don't have access to a PC. There used to be a "stock" Froyo ROM on ROM Manager. I suppose you could try downloading that (or some other "stock" ROM, if you can find one). Then, you should boot in to stock recovery and do a full cache and data wipe, then re-activate your phone with Verizon.
Last edited:
Greg_droid
New Member
Good thinking jdhas, that's just crazy enough, it might work.
Chef, I hope this has taught you to always keep a backup of a stock rom
Chef, I hope this has taught you to always keep a backup of a stock rom
The thing is that I was always doing back ups. What happened was that when you back up through rom manager on the x it doesn't Really back up just reeboots. Later on in my career modifying This phone I learned manipulation/ backups happen or save in recovery. So when I went into rom manager, when I first rooted, I backed up in rom manager. Then later with the help of Some one who had a d1 he showed me how to boot into recovery, because it(the rom) was not flashing through rom manager. When he showed me how to boot into recovery and flash the rom we/ I NEVER checked to see if rom manager saved my stock rom. So now here I am trying to upgrade with nostock rom, and no pc(working) looking for help from anyone that can readjustment words.
Plain and simple, you really need a PC. You should NOT be doing this kind of stuff if you don't have a PC. It's like driving a car without a license and insurance. You really should not be doing it even though "people do it" and you'll "be okay as long as nothing happens". You're at a point where you should SBF, which requires a computer.
Yes this is normal. You need to install Bootstrap and then Install Rom Manager. And before you mess with Rom manager open Bootstrap and install it.