Sometimes you need to factory reset more than once...
Sent from my DROIDX using Tapatalk
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!
Complete Droid X .sbf Flashing Guide
- Thread starter maderschramm
- Start date
Sent from my DROIDX using Tapatalk
Lol. Went to ubuntu and ran the 320. Still the same. Factory reset 3 times. No ota. Old market too. Flashed 340 sys on it, activated it, and all looks stock again. So ill go with it.
Sent from my DROIDX using DroidForums App
Sent from my DROIDX using DroidForums App
Haven't been watching this thread...
The OTA is designed for 2.3.15. You will NEVER be able to OTA from 2.3.320 to 2.3.340.
Once on 2.3.320, you have 2 options that I know of to get back to 2.3.340:
--Maderstcok to 2.3.340 (This actually will load the 2.3.320, then do all of the patches to get you to 2.3.340
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
--The hard way... Load all of the patches here:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader
HTH!
Haven't been watching this thread...
The OTA is designed for 2.3.15. You will NEVER be able to OTA from 2.3.320 to 2.3.340.
Once on 2.3.320, you have 2 options that I know of to get back to 2.3.340:
--Maderstcok to 2.3.340 (This actually will load the 2.3.320, then do all of the patches to get you to 2.3.340
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
--The hard way... Load all of the patches here:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader
HTH!
Hey kudos on your website!
Yeah I figured that out. I like flashing believe it or not. I ran maders all in one and it was good but I swear I had traces of tbh still and nfs shift wasn't there. Prob faulty dl but im good now. Besides, who stays on stock long anyways?
Sent from my DROIDX using DroidForums App
Haven't been watching this thread...
The OTA is designed for 2.3.15. You will NEVER be able to OTA from 2.3.320 to 2.3.340.
Once on 2.3.320, you have 2 options that I know of to get back to 2.3.340:
--Maderstcok to 2.3.340 (This actually will load the 2.3.320, then do all of the patches to get you to 2.3.340
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
--The hard way... Load all of the patches here:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader
HTH!
Hey kudos on your website!
Yeah I figured that out. I like flashing believe it or not. I ran maders all in one and it was good but I swear I had traces of tbh still and nfs shift wasn't there. Prob faulty dl but im good now. Besides, who stays on stock long anyways?
Sent from my DROIDX using DroidForums App
Ahh, I didn't think about Preinstall.. Bleh, TBH and Fission still put crap in the /preinstall dirs...
If you use root explorer, wipe that folder out completely, and then re-do the Maderstcok folder.
Also, NFSShift comes by defaut in the /preinstall dir as well.
I could probably throw together a patch to put it back.. if you ***really*** wanted it back.. hehAnd about the site, thanks! Still working hard on it.. more to come in the near future...
Im not worried about it nfs really. That damn preinstall always gets me on the dx.
Don't worry about. But thx for the offer!
Sent from my DROIDX using DroidForums App
Don't worry about. But thx for the offer!
Sent from my DROIDX using DroidForums App
The sbf wont update to latest kernel. Just fyi to anyone using this. You will have to manually update to latest kernel to be truly stock again.
Sent from my DROIDX using DroidForums App
Sent from my DROIDX using DroidForums App
Hmm, which .sbf? As long as it's not a system only .sbf, it does indeed update the kernel.
Of course, after saying that... know that after using the 2.3.320 .sbf, you still should update your kernel, baseband, and bootloader to 2.3.340... ?
I applied the 320 sbf. Let all my apps download. Then flashed the 340 sys only once I realized the ota wouldn't come thru(like u said) and just realized my kernel was wrong. Had to update it with tbh zip. Same with 2 others im working with.
Sent from my DROIDX using DroidForums App
Sent from my DROIDX using DroidForums App
maderschramm
Member
Zomg
I forgot about the preinstall dir!
To update maderstcok or not to update...that is the question...
Sent from my DROIDX using DroidForums App
I forgot about the preinstall dir!
To update maderstcok or not to update...that is the question...
Sent from my DROIDX using DroidForums App
maderschramm
Member
PRL = Preferred Roaming List
it's a value that changes based on which of Verizon's partner's towers you'll be using, it's not really all that important, it doesn't improve or hinder call performance (at least when you're not roaming, while is debatable).
My best guess is upon reactivation with *228 it updates? Not positive, I'd call verizon if you REALLY wanted an answer.
it's a value that changes based on which of Verizon's partner's towers you'll be using, it's not really all that important, it doesn't improve or hinder call performance (at least when you're not roaming, while is debatable).
My best guess is upon reactivation with *228 it updates? Not positive, I'd call verizon if you REALLY wanted an answer.
Very nice, sir! Makes complete sense. So now I am going to maderstok the sbf'd phone. I feel like maderstok just works. And I DL'd from the new link. I graciously thank you.
I need help guys. I woke up this morning with the phone running fine. I clicked on Market to check for any app updates and the phone rebooted. Now the phone is messed up. Clicking Market forces an immediate reboot, Gmail force closes, the phone will run for a bit then go into a reboot loop, I get a google framework error, and it loses network connections. It was running fine until I picked Market this morning, I have made no new changes to it in some time. I can't get it to factory reset, or even restore the hidden files through adb (renamed from apk to bak, not deleted). So I have been trying to flash a sbf with this guide and it fails with both Rds_lite and through Ubuntu. The phone had the OTA .340 update, so I picked that sbf file. I even tried it with the .320 with no luck. It has the .304 boot loader. I am at a complete loss at this point, every time it reboots, it seems to reboot into a state that was from this morning, no new messages even show in the history. Here is what I got the last time through Ubuntu, please help.
Motorola AP Flash found.
>> sending erase
>> uploading CG31: 100%
>> uploading CG33: 100% %
>> uploading CG34: 100%
>> uploading CG35: 100% %
>> uploading CG39: 100% %
>> uploading CG40: 100%
>> uploading CG42: 100%
>> uploading CG47: 100% %
>> uploading CG61: 100%
>> uploading CG64: 100%
>> uploading CG65: 100%
>> uploading CG66: 100% %
>> verifying CG31
!! failed
>> verifying CG33
!! failed
>> verifying CG34
-- OK
>> verifying CG35
-- OK
>> verifying CG39
!! failed
>> verifying CG40
!! failed
>> verifying CG42
-- OK
>> verifying CG47
-- OK
>> verifying CG61
-- OK
>> verifying CG64
-- OK
>> verifying CG65
-- OK
>> verifying CG66
!! failed
>> rebooting
Motorola AP Flash found.
>> sending erase
>> uploading CG31: 100%
>> uploading CG33: 100% %
>> uploading CG34: 100%
>> uploading CG35: 100% %
>> uploading CG39: 100% %
>> uploading CG40: 100%
>> uploading CG42: 100%
>> uploading CG47: 100% %
>> uploading CG61: 100%
>> uploading CG64: 100%
>> uploading CG65: 100%
>> uploading CG66: 100% %
>> verifying CG31
!! failed
>> verifying CG33
!! failed
>> verifying CG34
-- OK
>> verifying CG35
-- OK
>> verifying CG39
!! failed
>> verifying CG40
!! failed
>> verifying CG42
-- OK
>> verifying CG47
-- OK
>> verifying CG61
-- OK
>> verifying CG64
-- OK
>> verifying CG65
-- OK
>> verifying CG66
!! failed
>> rebooting
Update to my issue. I can get into adb shell and unhide the bloat (.bak to .apk), I can delete applications, but no changes stay once rebooted. Its almost like it reverts to a saved image of itself before the issue, but all problems are still there. It will not let me sbf or factory reset, it reverts back to this screwed up state. I have a warranty, but I cant get root, or any other programs off it, which could pose a warranty issue. I have even tried to remove them through adb shell with the rm command, they disappear off the list, but once rebooted, everything comes back.