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
Over the past few weeks I have been switching between roms...
I started with Birdmans Fly then to Fission 2.5.7 then went to Liberty.
This whole time my camera has been malfunctioning. Anytime I take a picture it shows up as an invalid file or a black screen. I've tried using 3rd party camera applications but nothing is working
HEEEELLLLLPPPPP me please
abrumlev said:
Over the past few weeks I have been switching between roms...
I started with Birdmans Fly then to Fission 2.5.7 then went to Liberty.
This whole time my camera has been malfunctioning. Anytime I take a picture it shows up as an invalid file or a black screen. I've tried using 3rd party camera applications but nothing is working
HEEEELLLLLPPPPP me please
Click to expand...
Click to collapse
Sounds like a problem writing the image to your sdcard. Tried backing it up, formatting it and seeing if that fixes the issue?
Just curious... what version of MOTO software are you running on? 2.3.15, 2.3.320, or 2.3.340?
Mine did the same thing. The problem was caused by flashing from a 2.3.15 rom to a 2.3.340 without first getting the official O.T.A 2.3.340 from VZW. I also had trouble with streaming Pandora and with the stock music player. What I did to fix it was, use RSD Lite to flash back to a stock 2.3.15 rom, then got the official 2.3.340 O.T.A update. Rebooted Re-rooted and Re-Flashed Apex 1.3.1 and all was well.
THanks guys Ill try that.
I thought i was running 2.3 something but it shows me with 2.2.1
abrumlev said:
THanks guys Ill try that.
I thought i was running 2.3 something but it shows me with 2.2.1
Click to expand...
Click to collapse
the file is 2.3.15 which is android 2.1, 2.3.320 2.2, and 2.3.340 is 2.2.1 at least i believe thats what they are
ive been having a similar problem to this only my videos dont save, ill take a video then when i go to watch it after it saves its all black and a pop up says "unsupported video file" or "video cannot be played" either way, it doesnt work, pictures are fine though
Ok so i was running Apex 1.4.1.
I SBFed using VRZ_MB810_2.3.34_1FF_01.sbf
rooted, etc etc, got latest gingerbread up and working fine.
Didnt like it, Trying to go back to Apex.
Im trying to SBF again, but cant get it to go through now. Keeps failing at 97% sending RAM to bootloader. Ive already flashed like 4 or 5 times using different RSDLite versions, and now im afraid my battery is probably getting low. What can i do!??
Try this. It has a really good track record. http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
So, everyone has heard that team black hat has released the new moto gingerbread for D2 and DX. Has anyone gotten theirs to work properly? I'll list the problems.
1. I literally waited for my phone to actually call out for fifteen minutes after dialing a number and tapping the send button.
2. All around sluggish and slow like honeycomb.
3. Motorola stock launcher will not open. Period. And most blur widgets and actions will automatically shut you out when you try to access them. Sometimes even text messaging!
4. Desk clock takes about three to five minutes to actually show up after placing the phone onto the dock and then three to five minutes for the phone to realize that it's been taken off of its dock.
These are just some that I noticed. Am I doing something wrong or is team black hat's material simply junk? I tried the rooted version and overclock to 1.3 GHz and it still did not work, by the way. So if anyone has some good advice or tips or anything, let me know. And I would like to know if this has happened to anyone else. Thanks!
> Posted using my stock 2.2 Motorola Droid 2, (successfully!) Overclocked to 1.3 GHz.
When you upgraded, did you clear the cache and the data in recovery?
Tappin' and Talkin' with Tapatalk
You know I don't know that I did... Are you running on the team black hat?
I wiped everything and now it seems to be working perfectly. Thanks!
I'm glad to see that you got it running so smoothly, hope your enjoying it
Sent from my DROID2 using XDA App
No. I'm not on Team Blackhat. The instructions are that you clear the cache and wipe the data in the bootloader before applying the update.
Soooo.... Is anyone out there running any GB rom > 2.3.3 4.5.153? If so... How the F* did you do it???
Tried loading the Deodexed 4.5.595 from the STOCK VRZ_A955_2.3.20.sbf flashed phone... and upon reboot, All I got was a string of errors on the boot loader.
I also tried loading 4.5.588 and I can never get past part 1 of the 3 part zips. The beginning of the script looks for an app that should have come with the device (which it can't find) and then proceeds to fail the installation.
I have not tried downloading an accountandsyncsettings.apk (the file it is looking for) and dropping it into the app folder.
Installed multiple 2.3.20 sbf files
Downloaded part 1 of 588 from all 3 mirrors (MD5s are identical on all 3)
maderstocked the phone (I know it was a dx firmware) and cooked the bootloader
All 3 zips were in the root of the SDcard.
4.5.153 is actually working perfectly... I just like to keep things current is all.
robonutz said:
Soooo.... Is anyone out there running any GB rom > 2.3.3 4.5.153? If so... How the F* did you do it???
Tried loading the Deodexed 4.5.595 from the STOCK VRZ_A955_2.3.20.sbf flashed phone... and upon reboot, All I got was a string of errors on the boot loader.
I also tried loading 4.5.588 and I can never get past part 1 of the 3 part zips. The beginning of the script looks for an app that should have come with the device (which it can't find) and then proceeds to fail the installation.
I have not tried downloading an accountandsyncsettings.apk (the file it is looking for) and dropping it into the app folder.
Installed multiple 2.3.20 sbf files
Downloaded part 1 of 588 from all 3 mirrors (MD5s are identical on all 3)
maderstocked the phone (I know it was a dx firmware) and cooked the bootloader
All 3 zips were in the root of the SDcard.
4.5.153 is actually working perfectly... I just like to keep things current is all.
Click to expand...
Click to collapse
As far as I know, .153 is the current working leak for the Droid 2. The Droid X leaks have gone up to .595 I think, but not compatible yet with Droid 2 completely.
Honestly, .153 IMO is the best you're going to get until the OTA for Droid 2 arrives, which should hopefully be sometime soon after the Droid X and Droid X2.
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
BrownEye02 said:
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
Click to expand...
Click to collapse
im no pro but hopefully this info will help you, it did me.
http://forum.xda-developers.com/showthread.php?t=1073841 liberty info
http://forum.xda-developers.com/showthread.php?t=1085323 sbf'ing
The new 2.3.3 OTA is stable and very nice looking on my DX, OTA not rootable yet but give it time.
Biggest life saver about the DX is the the part of the phone that ppl mess up and turn their phones to bricks is extremely safe on the X, not bulletproof but all the info in these forums I believe can bring them back regardless of what happens. I was very overwhelmed at first with my X but very comfortable now that ive successfully managed the sbf.
Yeah that's one of the things I really noticed. If you brick your phone it seams its not the end. So im still a little confused with your explanation on SBFing. You say that 2.3.3 is the latest OTA but its not rootable. So am I looking at the wrong number when I say my version is 4.5.588.
Sent from my Rooted DROIDX.
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
chbennett said:
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
WOW that is easy. To bad you cant select what version it flashes. But still EASY. Ill keep that in mind if I need to SBF. THANKS!
http://droidmodderx.wordpress.com/how-to-sbf-your-droid-x-full-2-3-340/
Good video tutorial there... It also has files there as well
Sent from my DROIDX using XDA App
Well I gave liberty 1.5 another try and it still got stuck on the liberty screen. Any ideas?
Sent from my Rooted DROIDX.
Was able to flash the liberty gingerbread rom tonight! I am kind of wondering if the version of ota/bootloader I have is the reason liberty 1.5 wouldn't work for me.
BrownEye02 said:
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
Click to expand...
Click to collapse
your looking at the version of the software build, complete jargon here but say your on android 2.2.1 version blah blah blah, what i was referring to was although you may have a higher version of 2.2.1 than what you are reading, a lower version of a higher android software such as 2.3.3 is better than a higher version of 2.2.1 same page?