So i have a roted droid x running rubix 1.9.0. I went back all the way to stock 2.2.1 so i could do the ota from verizon. downloaded it and installed it and was good. when my phone was rebooted by the download, i went back to rooting it with z4. i am not a noob but in no way an expert and was occupied with something else at the moment and didnt think about what i was doing and flashed a backup of exactly what i was running before the update. now i cant figure out how to get back to 2.3.340 on my phone. am i going to have to wait until a sbf file comes out for it because now in my about phone it reads like the photo i posted. now i dont know if i can go back because i never made a backup after i installed the ota and all the backups i have are from 2.2.1. and im pretty sure ill brick my phone if i sbf back to 2.2 through rsd lite. so now im not sure what i can or should do if i have any options or not or if i have to wait for a real 2.3.340 sbf.
please help!!!! thanks
im dumb and figured out everything.....but i love to learn and figure things out....reading and trying things out from this site deserves all the thanks!!
Post your fix
Post your fix "Always" so if anyone has the same problem, they will have the answer.
Thanks
spywiz said:
Post your fix "Always" so if anyone has the same problem, they will have the answer.
Thanks
Click to expand...
Click to collapse
no problem....i was able to do everything that TBH had shown
mydroidworld.com/forums/droid-x-discussion/5789-tbh-patches-2-3-340-system-baseband-2-3-340-kernel-bootloader.html
i just cleared data/cache and then went into clockwork and applied the 2.3.340 system updater and i was back to stock. now ive gone back to root and already am rocking out with tranq 3.6.0 thanks TBH!!!
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
willjohnson said:
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
Click to expand...
Click to collapse
try here http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html#comment220 scroll down towards the end (idk if you use windows or linux but the linux method of sbf'ing is alot easier ive used both) except in their directions it says an older sbf file just insert the one you have, then go here http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html to download these zip files for kernel updater, 340 system update your baseband and bootloader should already be the correct ones, (i recently bought my X too) then once you finally root your newly sbf'd X and installed droid x bootstrap etc and get into clockwork mod recovery you can flash those 2 zips (recommend flashing only one at a time, reboot, and do the next) and then you should be updated to full .340
gl
http://forum.xda-developers.com/showthread.php?t=869007
heres a thread with discussion about those update zips
Thanks for the quick replies. Gonna try your suggestion tonight or tomorrow. Now i get random lock ups followed by a boot after about five minutes. The only upside right now is that its 4 days old so if i can get some resemblance of factory back on it then i can just exchange it Thanks again will report back with results.
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
willjohnson said:
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
Click to expand...
Click to collapse
correct tho the one i used had was labeled VRZ_MB810_2.3.32_1FF_01.sbf
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Ok, so now i am starting to worry. Tried 3 different .320 full sbf's. All the same result. Failed process close to the begging. Then on the phone it says
Critical Error
FEBE
0047
Please Helppppp. I don't need a really expensive paperweight, all i need to do is get it so that GummyJar doesn't show on boot and i can take it back, its brand new.
Try removing the battery. Then boot into recovery (volume down + power) then do a factory reset/restore.
Sent from my ADR6300 using XDA App
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
willjohnson said:
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
Click to expand...
Click to collapse
ive heard there are several problems with rsd lol thats why ive stuck with my ubuntu/Linux its 10x easier
willjohnson said:
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Click to expand...
Click to collapse
i also believe you DO have to have it all in specific locations but idk i use linux to do it, if you continue to play with the X after u get new one i would read up on how to dual boot ubuntu its a whole lot easier once you find ur way around i have it booting off of a 1TB external hard drive no need to install the correct moto drives etc..just plain easy lol
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
willjohnson said:
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
Click to expand...
Click to collapse
it only takes once correctly doing it to feel comfortable lol also make sure using droid x bootstrap recovery make sure to tap the first choice and let it do its thing, otherwise it will constantly reboot to recovery EVERY time you turn it back on
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
willjohnson said:
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
Click to expand...
Click to collapse
try something blurless like darkslide, which im currently running, no random reboots
Funnyface19 said:
try something blurless like darkslide, which im currently running, no random reboots
Click to expand...
Click to collapse
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
willjohnson said:
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
Click to expand...
Click to collapse
Well I haven't overclocked yet anyway the phone gets hot enuf lol plus coming from an Eris 1k is fast lol
Um yeah it should be wright depends on what the blur clock looks like lol
Sent from my DROIDX using XDA App
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
willjohnson said:
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
Click to expand...
Click to collapse
yeah but the obsidian rom is completely blurless just not everything working
Running DarkSlide4.1 can't tell u last I had a reboot
Sent from my DROIDX using XDA App
So being a n00b, I forgot the ever so important unroot before I accepted the newest update to .340. I have tried everthing in the forums that I have read over the last few days. Have I forever lost my ability to root my DX?
Any help greatly appreciated! Sorry if this is in the wrong spot, I have never posted a thread b4!
Try z4root. Should root you just fine. Easily.
http://www.addictivetips.com/mobile...root-app-for-samsung-galaxy-s-android-phones/
And if you're running into any trouble using it, refer to this thread
http://forum.xda-developers.com/showthread.php?t=867694
FYI, you don't have to unroot for an OTA anyway.
O...I did not know that...I though u have to unroot for all updates...now I am even more confused. I lost my root privelages after the udate and have not been able to regain access. I have tried z4, rageagainstthecage, and a couple other methods. I am going to try using rsd lite next to flash, but some forums say this will work and others say u can not flash with the .340
SBF
could always do a 2.3.320 sbf and do the ota update again correct?
Haven't had to SBF in a while, but last I checked 2.3.320 was the last full SBF released. so while a there is a .340 System SBF if I were trying to make sure it wiped everything out of there, i'd go with the full sbf.
dnice102 said:
I am going to try using rsd lite next to flash, but some forums say this will work and others say u can not flash with the .340
Click to expand...
Click to collapse
Since you are running the newest update, (.340) make sure you don't use the 2.3.15 sbf since it will no longer work with your bootloader and your phone will be stuck until you flash a newer SBF. That is probably what you are hearing from other posts, with .340 you cant flash 2.3.15.
There are patches to go from .320 to .340, but for me, nothing is more simple than clicking accecpt update and going to make a sandwich.
If he SBF's to .320 he won't be able to get .340 with the OTA. Verizon doesn't
recognize .320 so the OTA won't happen. He can just go SBF .320 and use the
patches after that. It's what I did.
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
update.zip
ah, didn't know that, what about this?
http://forum.xda-developers.com/showthread.php?t=906191
update.zip to .340.
haven't tried this yet, just ran across it.
Thanks for everyone's help. The flash to .320 did the trick. However after the phone's battery died n I recharged, I am stuck on the motorola screen during boot. I can get into the factory recover, but that didnt help. Also, I can no longer access the bootloader. Am I permanantly bricked or is this a possible battery problem?
When you get into motorola recovery (holding the home button down until the android with triangle shows up), clear your cache and wipe data to factory. This might do the trick. You're just gonna have to add your google account again.
Sent from my DROIDX using XDA App
Yeah... I wiped the data and the cache a couple times...no luck. The device will not do anything unless its plugged in, so I am hoping its just the battery. I will find out later today!
Thanks for the support!
went to verizon. the rep said the last .340 update had corrupt files in it. they are overnighting a new phone at no charge!
thanks again for everyones help!
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Laramie1997 said:
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Click to expand...
Click to collapse
Boot into stock recovery and do a factory reset...
Sent from my DROIDX using XDA App
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Laramie1997 said:
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Click to expand...
Click to collapse
Its stock recovery...power off phone and then hold power and home button until you get the Android with the exclamation point. Then hit the search button
Sent from my DROIDX using XDA App
That wasn't quite what I was looking for since I don't have /sdcard/update.zip still on the card anymore. What IT DID allow me to get in and do was wipe cache which allowed a clean SBF.
THANKS!
I got this phone from eBay as "stuck in M" and thought I might give it a try to SBF it back to stock. So I tried SBFing to 4.5.605 and it works great but after the first reboot, it boots straight to stock recovery.
I read some threads online and some mention to wipe data/cache. I do that and reboot and it still keeps going back to recovery no matter what. I have complete access to the phone with RSD Lite but I cannot get it to boot to the OS. It just keeps booting back to stock recovery.
I would really appreciate some help here. It would be great if I can get this phone working again. Am I doing something wrong? Something specific about the Droid X I'm not aware of?
open1your1eyes0 said:
I got this phone from eBay as "stuck in M" and thought I might give it a try to SBF it back to stock. So I tried SBFing to 4.5.605 and it works great but after the first reboot, it boots straight to stock recovery.
I read some threads online and some mention to wipe data/cache. I do that and reboot and it still keeps going back to recovery no matter what. I have complete access to the phone with RSD Lite but I cannot get it to boot to the OS. It just keeps booting back to stock recovery.
I would really appreciate some help here. It would be great if I can get this phone working again. Am I doing something wrong? Something specific about the Droid X I'm not aware of?
Click to expand...
Click to collapse
sounds like its bricked it is possible that your sbf file is slightly corrupted or its the wrong one altogether try redownloading the sbf file or try .602 sbf dont reboot it if you can help it root it and put a different rom on it may just solve your trouble the linux method of sbf is more sound look into that instead of rsdlite if you have to use rsdlite make sure its is the newest leaked version of the program. Always make sure the program completes to the end and it says passed. pull the battery afterwards and do a factory restore hard reset should be good to go