Related
ello please i need help here the story
i just received my droid x(i am not neebi but not expert neither) ok i received the 2.1u1 version i rooted using easy root....then i download rom manager and boot strap....i was tryinig to get the leaked version of froyo,no sure if i found it but i install the stock version in rom manager....first i move the su file to xbin to keep rooting....in thi spoint everything fie...i started to download apps and everything....than i tried to install some stuff from rom manager but when tried to get into recovery the phone stuck in moto logo i fixed that pulling off the battery ok than i wen to market and downloaded the boot strap cause i realized after install the version 2.2 from rom manager the app wasnt there so i re install than when i tried to get a goodie(not sre is the name??/ u know some king of modding)when rom manager went to recovery stuck in moto logo and i can pass by that please help is my droidx bricked...can i flash the sbf file cause i dont know if my froyo is oficil or leaked i download from rom manager....
PS. when i turn the phone on first i see the moto logo...then the recovery menu(whith the options reboot....apply sdcard.....wipe etc...) when i click the reboot system now option then the moto logo stuck////
Did you make a backup? You should be on the 2.1 kernal if you got 2.2 from rom manager.
Sent from my DROIDX using XDA App
If you havent updated to the 2.2 OTA you shouldnt have any problem using the 2.1 SBF as far as i know.
citanes-26 said:
Did you make a backup? You should be on the 2.1 kernal if you got 2.2 from rom manager.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
no i didnt...i was on 2.1u1 than i root and everything and install the 2.2 from rom manager do u think i can flash the 2.1 sbf file???
citanes-26 said:
Did you make a backup? You should be on the 2.1 kernal if you got 2.2 from rom manager.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
nop
skraapz27 said:
If you havent updated to the 2.2 OTA you shouldnt have any problem using the 2.1 SBF as far as i know.
Click to expand...
Click to collapse
i think that but i am afrraid to brick the phone...i read some about the sbf file from the black hat team did u hear about it
The 2.2 in Rom Manager is a leak, you need the 2.1 sbf
Sent from my DROIDX using XDA App
Thanks for all replies i already fixed just flash the 2.1 sbf....first time failed and said code corrupt second time gooddd
Morning all,
Is anyone running the Gbread 595 leak yet? I am thinking about trying it out this morning, as everything I read indicates it will be the launching point for what could be the official 596 release on the 13th.
Let me know if you have any observations on this.
Thanks,
Steve
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
owenbeals said:
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I agree. Apex is amazing. I will wait for it to update
Weird issue I am running into....
I upgraded to 588 with no problems from 340 Froyo. I used DroidX recovery to accomplish this. When I rebooted 588 I tried to go to 595. I tried using DroidX recovery but this did not allow me to boot into recovery...it only gave me a blank screen. When I got back to 588 I uninstalled DroidX recovery and then installed Droid2 recovery. I was then able to reboot into recovery and try to install 595. The install aborted saying it was looking for 3 arguments and got 4.
Any ideas? Which recovery should I be using thoughtout this?
Thanks,
Steve
Both recoveries (AFAIK) are the same clockwork recovery, it's just a different method of "bootstrapping" so that you can get into the recovery. Droid2 bootstrap works on gbread unless USB debugging is disabled, then droidx bootstrap works.
Sounds like you got a bad file.
Just redownload the file and it should work
Yes the one I downloaded yesterday was bad, and a new one was uploaded. I just downloaded the new one and am going to try again to move back up to 595. Once that happens I am hanging on til the 13th.
I would assume once this official update comes out then VZW will no longer support the DX with official updates. We really need to get Moto to unlock the bootloader for us, so we can continue to develop for the DX.
Steve
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
stevefxp said:
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
Click to expand...
Click to collapse
P3Droid released three different versions of .595: full stock, rooted and odexed, and rooted and deodexed.
You can try flashing one of the rooted .595 releases.
Sent from my DROIDX using XDA App
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
You shouldn't need Gingerbreak on the rooted ones, as they are already rooted.
stevefxp said:
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
Click to expand...
Click to collapse
If you are going to flash a rooted version what do you need gingerbreak for?
smiteme said:
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Click to expand...
Click to collapse
So you're not running it at all then... lol. You downgraded it back to .591 when you installed Liberty.
Sent from my DROIDX using Tapatalk
Curious, I'm running .573 now, if I flashed the latest rooted & deoxed, do I really have to sbf back to Froyo before hand like I've read in other places? OR can I just flash over it and roll on?
You only need to flash back if you don't have root, I believe.
Sent from my DROIDX using XDA App
Not having luck.
I tried to install, initially from my rooted deoxed stock .340 to rooted deoxed .595, first got a corrupted file report....would not upgrade.
Next got boot loop (repeating M), so SBF back to stock 340...Rooted and tried again with the same file and got a very unstable phone, reboots etc.
The only thing I can think of is that the phone was stock rooted but not deoxed, so when I tried loading the deoxed version it didn't like it? no idea.
I did a wipe before each load but can't seem to get it to work on my phone. My phone is very new.
SBF'd back to stock unrooted and I'll leave it like that to see if I can get the update from VZW.
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
I'm on 2.2 and waiting. Just not convinced about 595 and getting the update. How do we know its going to be 596.
Sent from my DROIDX using XDA App
infazzdar said:
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Not completely accurate.. I went from .588, to .595 without any adverse effects. Phone is a bit snappier than before too, app drawer scrolls more fluidly, etc.
I'm running 4.5.595 on my Droid X.... I can't pull the update. I am not rooted right now but I wanna get the final update..... Help?
Thanks -dom
dominicricci said:
I'm running 4.5.595 on my Droid X.... I can't pull the update. I am not rooted right now but I wanna get the final update..... Help?
Thanks -dom
Click to expand...
Click to collapse
More than likely you'll have to AND back to froyo
Anyone seeing a failed update? It made it through the download and rebooted probably went a quarter of the way and the triangle with exclamation point rebooted and reported failure.
went back to froyo and now im running .596 ,,,,, kind of a hassle but im good to go now
hanone said:
More than likely you'll have to AND back to froyo
Click to expand...
Click to collapse
I had my DX Z4 Rooted and got the OTA update... installed fine. Then bricked my phone.
Thank god I'm still in warranty
well im a super noob lol......just got gingerbread on my Droid X and for whatever reason gingerbreak will not work....it just sits there and runs forever....ive tried both version 1.1 and 1.2
any ideas ?
http://droidmodderx.wordpress.com/l...4-5-596-upgrade-from-froyo-or-gb-588-591-595/
Check this link for files and instructions
Sent from my DROIDX using XDA App
monstercojones said:
I had my DX Z4 Rooted and got the OTA update... installed fine. Then bricked my phone.
Thank god I'm still in warranty
Click to expand...
Click to collapse
Are you serious????? You were too Damn lazy to search the forums and google on how to fix it? This is the reason we have locked bootloaders. NEVER root your phone again if you aren't going to try to find out how to fix it if it breaks
jakool said:
well im a super noob lol......just got gingerbread on my Droid X and for whatever reason gingerbreak will not work....it just sits there and runs forever....ive tried both version 1.1 and 1.2
any ideas ?
Click to expand...
Click to collapse
There's no root available for the OTA.
I am on a Thunderbolt but I am helping some friends today upgrade to a rooted version of GB using P3droid's method listed previously in this Thread. My question is, during the install while in CWMod recovery do I need to format system/data/ and Cache and then Mount system before installing the individual zips? It isn't clear to me in the instructions. A response would be much appreciated, Thanx
jakool said:
well im a super noob lol......just got gingerbread on my Droid X and for whatever reason gingerbreak will not work....it just sits there and runs forever....ive tried both version 1.1 and 1.2
any ideas ?
Click to expand...
Click to collapse
The GB OTA is NOT rootable.......yet.
Sent from my DROIDX using XDA Premium App
tenyrnote said:
I am on a Thunderbolt but I am helping some friends today upgrade to a rooted version of GB using P3droid's method listed previously in this Thread. My question is, during the install while in CWMod recovery do I need to format system/data/ and Cache and then Mount system before installing the individual zips? It isn't clear to me in the instructions. A response would be much appreciated, Thanx
Click to expand...
Click to collapse
What version is the dx on now? If its already on leaked gingerbread then just flash the deodexed .596 update... If coming from any custom rom or stock froyo then wipe data and cache, I didnt mount
Sent from my DROIDX using XDA App
ok so i upgraded to the milestone x from the htc heroC. when i got the phone (3 days ago) it was preloaded with:
android version: 2.3.5
system version: 4.5.602.MB809.ACG-CS.en.US
Baseband Version: BP_C_02.12.00R
Kernel Version: [email protected] #1
Build number: 4.5.1_57_MX2-32
i have tried everything to root the device to no avail. z4, superoneclick, PetesMotorolaRootTools, MotorolaOneClickRoot by psouzza4, UniversalAndRoot and GingerBreak.
anyone have any ideas?
wow... really? no one?
Better late than never!
I have Cellular South...or C-Spire also, and I just upgraded to the Milestone X from a HeroC as well. I just typed you up this nice and helpful response to help you, but unfortunately, I'm a new user, so I could't post any outside links. IF you'd still like the help, you can email me and I'll send you back the response that I saved. Just put MILESTONE X in the subject line so I won't miss it.
My email is: [email protected]
Why is this post in the Droid X forum?...
voyageurs60 said:
Why is this post in the Droid X forum?...
Click to expand...
Click to collapse
The Milestone X is identical to the Droid X, it's just renamed by C Spire to avoid licensing issues I suppose.
brandon.smiley said:
I have Cellular South...or C-Spire also, and I just upgraded to the Milestone X from a HeroC as well. I just typed you up this nice and helpful response to help you, but unfortunately, I'm a new user, so I could't post any outside links. IF you'd still like the help, you can email me and I'll send you back the response that I saved. Just put MILESTONE X in the subject line so I won't miss it.
My email is: [email protected]
Click to expand...
Click to collapse
hey thanks for your effort, i did eventually get it rooted.
ngholson said:
hey thanks for your effort, i did eventually get it rooted.
Click to expand...
Click to collapse
How? I was able to get my nTelos one rooted running the 2.2.2 but the Gingerbread 2.3.5 update is coming soon and I'm scared to upgrade. Is it worth it? How did you root?
cfultz said:
How? I was able to get my nTelos one rooted running the 2.2.2 but the Gingerbread 2.3.5 update is coming soon and I'm scared to upgrade. Is it worth it? How did you root?
Click to expand...
Click to collapse
use this DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
So did you just create an ADB and root it with that package. Where did you find that package? Any instructions?
It is weird coming from the HTC Hero with tons of information on rooting, etc and coming to the Milestone X where there isn't too much.
What else have you done your Milestone X?
jvatio said:
So did you just create an ADB and root it with that package. Where did you find that package? Any instructions?
It is weird coming from the HTC Hero with tons of information on rooting, etc and coming to the Milestone X where there isn't too much.
What else have you done your Milestone X?
Click to expand...
Click to collapse
the root package? lots of searching.... credit goes to whomever created it, i am just glad that they did.
just unzip and run the file, and follow the instructions on screen
I just bricked my ntelos Milestone X. It had done the OTA 2.3.5 update today, and I tried to sbf back to 2.2. Silly me! Now when I turn it on, all I get is the bootloader screen with a MEM_MAP Blank error. Looks like there is no way to sbf out of this either....presently. Any thoughts?
lexridge said:
I just bricked my ntelos Milestone X. It had done the OTA 2.3.5 update today, and I tried to sbf back to 2.2. Silly me! Now when I turn it on, all I get is the bootloader screen with a MEM_MAP Blank error. Looks like there is no way to sbf out of this either....presently. Any thoughts?
Click to expand...
Click to collapse
can you boot recovery?
EDIT: nevermind silly question.... same thing happened to me... had no choice but to warranty the phone... without a working sbf for the milestone x, that mem_map blank error pretty much means your are fully bricked.
Anyone with luck flashing a Milestone X w/ a custom ROM?
Running Rooted 2.3.5 w/bloatware removed (but backed up) along w/ DROID X Bootstrapper.
Have made my first full system backup using this tool.
If complete ROMS could not be used, what components would I need to modify, replace, ... exchange to get it to work on C-Spire (say, Verizon).
I've heard that there are some ROMS that don't mess with the baseband and other communications settings, files, frequencies, protocol, etc... What are these type called if they exist? Where can I find them? Are these a safer alternative to full ROMS?
Will DX Bootstrapper get the job done? Reports ClockworkMod REcovery v2.5.0.6.
I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.
Rocheforte said:
I would recommend staying off custom roms for the Milestone X until a working sbf for us makes an appearance. Myself and ngholson both had issues where we got stuck in a bootloop and the sbf just output more errors until a replacement device was needed.
Click to expand...
Click to collapse
agreed. [10chars...............
another thing to consider, since we cannot sbf at this time, is that the bootstrapper will break your ability to install any future ota updates. it modifies the logwrapper and makes a copy called logwrapper.bin, however, uninstalling the bootstrapper and restoring the logwrapper file does not correct the problem. best i can tell the only answer that i can find when this happens is to sbf back to stock... well you see where this is going.... currently we cannot do this, so unless you never want the ota upgrades i do not recommend installing the bootstrapper on cspire's milestone x.
oh well nevermind went back and re-read your post, you already have the bootstrapper installed. (at least you did it after ota)
here is a link to the post that has the sbf that is reported to work with cell south (cspire) http://forum.xda-developers.com/showthread.php?t=1117885
maybe someone else can try it again and report back.
daywalker04 said:
SBF flash for MB809 - Milestone X Generic North America
SHADO_X6_3.1.39_SHADOW_BP_C_02.06.00R_AP_BP_Flex_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
http://www.filesonic.com/file/11766...x_1E_signed_secure_dist_1ff_P3_USERBLD.sbf.gz
Compression MD5 - BF942D55992C774446F24B56116649A1
SBF MD5 - 2EAEBD1540D563114523BEB09539A8AF
Click to expand...
Click to collapse
abcleanonme said:
Well I can confirm it works on Cellular South.
Sent from my MilestoneX using XDA Premium App
Click to expand...
Click to collapse
I can confirm that the old sbf it does not work after ota update. I had to get a new phone. I have rooted, but I am not installing a bootstrapper until a working sbf is available. Hopefully that will happen soon.
I am on C spire out of Byram, MS and can in fact confirm that "Droid X Bootstrapper" from the market indeed works like a charm on the Milestone X with stock versions 2.2.2 and 2.3.5.
I use "Super One Click" to root, then the same prog to "Allow non market apps" then buy "Droid X Bootstrapper" from market, run it. Reboot while holding camera button and power button,,,,voila
Confirmed roms that I have and currently run or ran: CM 7 nightlies, Liberty 1.5, and Fission 2.5.7 DroidX
---------- Post added at 07:12 AM ---------- Previous post was at 06:57 AM ----------
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...
Brickster said:
A little trick I figured out to sbf back to stock,,,,download the latest ota from Cspire "Blur_Version.3.2.6.MB809.ACG-CellSouth.en.US" blah blah,,,,,rename it to "update.zip",,,,not "update.zip.zip"put it on the root of your sd card and boot into stock recovery or clockwork mod and run update.......BLAM! Simple as that...
Click to expand...
Click to collapse
i tried that too it didn't work for me.
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
is there a reason that your not using the new liberty rom and used 1.5?
tylorjefcoat said:
is there a reason that your not using the new liberty rom and used 1.5?
Click to expand...
Click to collapse
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.
Brickster said:
Nah, it's a cool rom .....I'm just a flash whore. I like cm7 nightlies the best though.
Click to expand...
Click to collapse
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?
Brickster said:
I dunno,,,, it worked for me twice. I tried to update cwm from the app using the flash for droid x and it messed up my recovery. So i updated to the latest ota from Cspire via the stock android recovery by naming the ota file to update.zip and running it like that.
I'm running CM7 nightlies for the droid x on the Milestone x....you might have to remove the line of code in the update file that asked for Kernel assert,,,,I can't remember, but seems like it kept giving me an error that says, "assert failed: run_program("/tmp/check_kernel") but after that all was fine.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.
thenig said:
I am getting the exact same error. Where do I need to go to eliminate this line of code. I have setup everything else up until this point and it works perfectly with recovery and everything. A bit of help please.
Click to expand...
Click to collapse
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.
tylorjefcoat said:
what has been the best in your opinion? i just upgraded from the hero and was running aosp and loved it.
i actually like some of the blur apps, hard to believe that i like a custom ui on android lol.
i have been reading on the droid x vs milestone x and i am weary of flashing update that also includes the radio/baseband.
what version of cm7 nightfiles are you on? any complaints?
Click to expand...
Click to collapse
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.
Brickster said:
Open the ROM zip and go: META-INF/com/google/android/ and in the updater-script, remove the code that asked for Kernel assert.
Click to expand...
Click to collapse
Open the updater-script with notepad (new to this) and found no mention of kernel assert. Almost there...a bit more help would get me in.
It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App
Brickster said:
It should be the top 3 lines, if I remember correctly.... I checked it out on my phone to make sure but,,,, duh, I already removed it (face palm).
It's in there somewhere.
Run install again and right down all the errors... Then try to find them in the script file.
I'm new to this also (as far as motorola stuff) too. And I take risks that most people wouldn't..... Hell, if I mess something up bad enough , just sbf back.
I'll try to help you more when I get off work... Maybe send you my roms that have already been fixed.
Make sure to turn off script and signature asserts off in cwm... Sometimes that helps.
Sent from my Milestone X using XDA App
Click to expand...
Click to collapse
Thank you sir! I'm gonna try that.
Brickster said:
I too just upgraded from the Hero....and I still love that phone! My hero has had every rom known on it,,,and some that weren't even made for it....It's unbrickable! LOL
Yea, the Milestone is a little more finicky than the Hero, and with Motorola's locked bootloaders, one could get in a fix..
I've ran the past 3 nightlies and currently on cm_shadow_full-154.zip.
I tell ya, they all have some kind of bug somewhere. It all depends on what you want to put up with. Me, personally, I like the stock ota 2.3.5 from Cspire. It works. Plain and simple. Now, I would like some of the CM7 options and spare parts.
Click to expand...
Click to collapse
I despised that phone lol, wait i take that back, i guess i had "phone" envy lol Mine was a rom whore as well, it was rooted almost immediately after i got it with the ole gold card method.
the ota 2.3.5 is actually a good CLEAN rom, i do like the fact that it is so clean, just need a few tweaks as you said from the cm7 build, status bar tweaks ect..
may build up one.
built a rom for a tablet we are selling here, BIG learning curve but the locked boot-loader throws a real curve ball
now, have you gotten it to overclock?
Brickster said:
. Hell, if I mess something up bad enough , just sbf back.
Click to expand...
Click to collapse
that still amazes me. i haven't tried it on 2.3.5, but when i did it from stock 2.2.2 it was a no go.... maybe it will only work if you are already on 2.3? hell i dunno... motorola has me chasing my tail.... like everyone else, i came from the hero too, that was one awesome little phone. i read somewhere that the motorola bootloader had been cracked by someone on here but..... not sure what ever happened there.....