My Droid 2 Global got Stuck on M logo - Droid 2 General

This is my bad day . My Droid 2 Global got stuck on M logo when I tried to root and install the new ROM . I have tried alot of SBF from the Droid 2 but it's seem nothing fix my phone. So, anyone can help me with the new SBF for Droid 2 Global

Which SBF did you use? I'm not aware of one being released for the D2G and using the one for the D2 will certainly screw up your phone.

There isn't a SBF for the D2G yet. You should have waited for it before trying anything like this.

If the sbf did work after you sbf you need to:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
If that doesn't work than you might be SOL.
If you get the M logo and you have a backup. (always try and restore a backup before you SBF)
Pull your battery and place it back in after 5 seconds or so (we just want the phone completely off)
(while completely off) Plug your phone into the wall charger.
Then turn your phone on. If you get the charging screen press power again.
now you should be in clockwork recovery so you can do a restore if you made a backup.

I've used all the sbf that I searched in this forum but it wasn't work. I think there are a different SBF for Droid 2 Global.

hamabucon said:
I've used all the sbf that I searched in this forum but it wasn't work. I think there are a different SBF for Droid 2 Global.
Click to expand...
Click to collapse
I assumed so but I also assumed that if the boot loader hasn't changed one could /theoretically/ flash the 2.3.2 sbf and /possibly/ be okay. I wouldn't recommend any D2 G users to flash ROMs or anything until the SBF specifically for the D2 Global is released. I would suggest rooting and getting a backup made if the user want's to eventually flash ROMs.

newk8600 said:
I assumed so but I also assumed that if the boot loader hasn't changed one could /theoretically/ flash the 2.3.2 sbf and /possibly/ be okay. I wouldn't recommend any D2 G users to flash ROMs or anything until the SBF specifically for the D2 Global is released. I would suggest rooting and getting a backup made if the user want's to eventually flash ROMs.
Click to expand...
Click to collapse
I have tried to flash the 2.3.2 but everything seem wrong and I have the Critical error 0047

hamabucon said:
I have tried to flash the 2.3.2 but everything seem wrong and I have the Critical error 0047
Click to expand...
Click to collapse
Did you make a backup with koush's bootstrapped clockwork recovery? if so you should try and restore it. otherwise you might be out of luck until the sbf drops.

Maybe I'm out of Luck . But is there a chance to update the new ROM using the stock Recovery ? . I saw there are the option apply: update.zip

It will only work if you have the rom signed with moto's keys or it won't get through. That's why we use koush's bootstrapped clockwork. Because it doesn't have signature verification. Well it does but we can toggle it off.
Sent from my DROID2 using XDA App

Can you estimate when the SBF for D2 G release ?

newk8600 said:
If the sbf did work after you sbf you need to:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
If that doesn't work than you might be SOL.
If you get the M logo and you have a backup. (always try and restore a backup before you SBF)
Pull your battery and place it back in after 5 seconds or so (we just want the phone completely off)
(while completely off) Plug your phone into the wall charger.
Then turn your phone on. If you get the charging screen press power again.
now you should be in clockwork recovery so you can do a restore if you made a backup.
Click to expand...
Click to collapse
I have the same problem with the droid 2, except i mistakenly flashed with the droid 2 global without really thinking about it. I'm stuck at the M logo, and i've tried doing all of the above but i cannot get into clockwork recovery. Any suggestions? if I bricked my phone, how would i go about getting it fixed from verizon?

I remembered that i install the stock ROm deodexed for Droid 2 Global . But why my phone bricked ? Is that the problem from my phone?

dotmike said:
I cannot get into clockwork recovery. Any suggestions? if I bricked my phone, how would i go about getting it fixed from verizon?
Click to expand...
Click to collapse
You should sbf your droid 2 with the 2.3.2 sbf. Search in droid 2 android development section. There are two ways to flash it. One in windows the other in linux. I made a tool so people can use any computer to flash in linux. Search in the android development section for the droid 2 and it's there if you need it. I recommend reading and reading and reading then flash it. You'll be wiser and you'll know each step before you do it. It's not difficult and if you are going to flash ROMs you need to need to know how to sbf.
If your phone boots it's not bricked. And read every post here before trying to return it to verizon. If you have the desire to flash ROMs to your phone you can to the research to fix any mishaps. If after you read every post and you still have no idea or the methods applied haven't worked then you have my permission to take it back to verizon with the excuse that the update messed up your phone. Thanks and happy fixing!
Sent from my DROID2 using XDA App

I have just bought another Droid 2 Global , is that work if I have a nandroid backup from the new one and use for the bricked one ?

newk8600 said:
You should sbf your droid 2 with the 2.3.2 sbf. Search in droid 2 android development section. There are two ways to flash it. One in windows the other in linux. I made a tool so people can use any computer to flash in linux. Search in the android development section for the droid 2 and it's there if you need it. I recommend reading and reading and reading then flash it. You'll be wiser and you'll know each step before you do it. It's not difficult and if you are going to flash ROMs you need to need to know how to sbf.
If your phone boots it's not bricked. And read every post here before trying to return it to verizon. If you have the desire to flash ROMs to your phone you can to the research to fix any mishaps. If after you read every post and you still have no idea or the methods applied haven't worked then you have my permission to take it back to verizon with the excuse that the update messed up your phone. Thanks and happy fixing!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk

hamabucon said:
I have just bought another Droid 2 Global , is that work if I have a nandroid backup from the new one and use for the bricked one ?
Click to expand...
Click to collapse
You could try, but you need to get into cw recovery on the broken one first...
Sent from my Milestone using Tapatalk

leobg said:
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
I was not commenting to hamabucon I was talking to dotmike who it seems has an Orginal Droid 2 (not global) and the advice is NOT for the Droid 2 Global. I'm sorry if it's confusing he posted in a thread about the D2 G and I was trying to help him where he posted his problem. I have not suggested that there is an Sbf for the D2 G. Sorry for the confusion but if we all read what each post relates to will help.
Sent from my DROID2 using XDA App

, Still wait for my little hopeness

leobg said:
The phone is Droid 2 Global. There is no sbf available for D2G yet. More and more users are getting confused. Please vote in the thread for dedicated section for D2G @XDA!
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
newk8600 said:
I was not commenting to hamabucon I was talking to dotmike who it seems has an Orginal Droid 2 (not global) and the advice is NOT for the Droid 2 Global. I'm sorry if it's confusing he posted in a thread about the D2 G and I was trying to help him where he posted his problem. I have not suggested that there is an Sbf for the D2 G. Sorry for the confusion but if we all read what each post relates to will help.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Yes, apologies for taking over a thread with my question, however to newk8600, I didn't know that holding the up key on the keyboard booted into the bootloader! I managed to sbf from there since RSDLite read the phone then.
Apologies for any confusion, and thank you again for the help.

Related

motorola droid 2 bricked need help

i have Motorola droid 2 on 2.2 rooted with bootstrap recovery, everything was workin fine till i decided to install custom rom, which was unleashed epic 2.5 (by mat) and now everytime i turn on my phone it goes into a loop reboots and never turns on all the way.
i have tried using sbf RSDlite to restore it, tried using linux ubuntu(newk8600 method ty btw) method as well to restore it, none seems to work i keep getting errors whenever i try to do it.
however before i installed the custom rom i did full backup using bootstrap recovery but the only way (that i know) to get in recovery is using bootstrap app, so is there a way i can manually get into bootstrap recovery so i can restore from backup?
please let me know, or if you have different method i'll appreciate your help. thanks in advance.
Which version of the software did you have before you installed epic unleashed, and which SBF did you use?
From what I have heard, Epic Unleashed will "brick" your phone if you try to install it on the 2.3.20 build. Since your phone did get bricked, it's likely that you are running 2.3.20 and not 2.2. You might want to make sure you are using the 2.3.20 SBF to flash your phone, and not the 2.2 SBF (which won't work because the kernel changed between the two)...
What type of errors do you get?
i always have luck getting into clockwork recovery by having my phone plugged in and within the first few seconds taking out my battery forcing it to take along time booting after the M logo and hence putting it into clockwork. I hope this helps
after you get passed the M pull the battery then boot back up it should come up in to recovery
thank you all for your help, however i tried all of these steps already, but i found another way to get it workin, here is the solution to whom got the same problem as mine.
its not letting me post the link for some reason, anyway just search for (Droid 2 Global SBF File (2.4.29) Full and RSDLite ).
just got relased today , big thanks to team Black Hat and MyDroidWorld
hope that helps.
Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App
orkillakilla said:
Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.
Phoible said:
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.
Click to expand...
Click to collapse
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App
orkillakilla said:
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It's all good people need to read where they are posting this is in the D2 General section not the D2 Global general section. That's half his problem, he's been looking at ROMs for the original D2 not the device that he currently uses.

[Q] NEED HELP. DROID X Bootstrapper. Sending a phone back to VERIZON. Desperate

First i'm going to say sorry as i know this isn't the first and probably won't be the last thread posted about removing droid X bootstrapper. With that said thank you in advance for helping me.
Before i go on i'll preface by saying i am no expert but with proper instruction i can learn very easily. I rooted my DX using z4root and used droid x bootstrapper to create a nandroid and flashed the Fission Rom. I am new to the DX, came from the DINC, and the only reason i rooted was because my phone was rebooting randomly and i thought maybe that would fix it but it didn't so i was able to get a refurb DX which is working better already and so now i have to send my old back to Verizon. Problem is i unrooted it and restored to defaults and Bootstrapper, Terminal Emulator, and SU were all still there. so i researched the boards since this community has made me excited to be an android user, and tried both methods of Root explorer and Terminal emulator, and even flashed maderstcock340.zip but again upon restoring to defaults, all 3 apps showed up again.
I need help, i didn't want to ask for help because i dont want to bother anyone but i need the help. Even a link to something else that i should try would be a great help.
I mean even if anyone is willing to skype with me and help me out that way i'll buy you a 6 pack.
EDIT: Will using the .340 system only sbf work to remove it? and if not will using TBH's 2.3.32 fix it??!?!
Have you tried unrooting with z4, you can uninstall the other two in the market. If z4 fails to unroot, you might have to flash a sbf. Its easy find " how to's" in the forums.
Sent from my DROIDX using XDA App
thecontrolm7cl said:
First i'm going to say sorry as i know this isn't the first and probably won't be the last thread posted about removing droid X bootstrapper. With that said thank you in advance for helping me.
Before i go on i'll preface by saying i am no expert but with proper instruction i can learn very easily. I rooted my DX using z4root and used droid x bootstrapper to create a nandroid and flashed the Fission Rom. I am new to the DX, came from the DINC, and the only reason i rooted was because my phone was rebooting randomly and i thought maybe that would fix it but it didn't so i was able to get a refurb DX which is working better already and so now i have to send my old back to Verizon. Problem is i unrooted it and restored to defaults and Bootstrapper, Terminal Emulator, and SU were all still there. so i researched the boards since this community has made me excited to be an android user, and tried both methods of Root explorer and Terminal emulator, and even flashed maderstcock340.zip but again upon restoring to defaults, all 3 apps showed up again.
I need help, i didn't want to ask for help because i dont want to bother anyone but i need the help. Even a link to something else that i should try would be a great help.
I mean even if anyone is willing to skype with me and help me out that way i'll buy you a 6 pack.
Click to expand...
Click to collapse
Have you tried sbf'ing?
Sent from my DROIDX using XDA App
bigshotrob22 said:
Have you tried sbf'ing?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Well i thought that is what maderstcoks340.zip was supposed to be. A flashable sbf? can you direct me to a link where i can download the .340 SBF and the right version of RSD Lite
I'm currently at work and on my phone...so you'll have to find the links yourself...
But flashing the .340 won't get you completely back to stock. You'll need to find a link to the .320 sbf...I think there is one on droid-life.com
Apply the 320 and then the 340.
340 sbfs are easy to find...but you'll obviously need that too.
Jubakuba said:
I'm currently at work and on my phone...so you'll have to find the links yourself...
But flashing the .340 won't get you completely back to stock. You'll need to find a link to the .320 sbf...I think there is one on droid-life.com
Apply the 320 and then the 340.
340 sbfs are easy to find...but you'll obviously need that too.
Click to expand...
Click to collapse
got it all taken care of! Really pretty fearless now that i sat down and learned to SBF the problem is i run mac so i'll need to use a friends PC if i ever need to SBF again. Anyway thanks for the help!
Go go www.drewgaren.com and click on the sbf and root tab..i used his instructions to sbf...
Sent from my DROIDX using XDA App

Possibly bricked Droid x

My father inlaw balled up his Droid x and went and bought a new one. Looking at the supposedly bricked phone I can try to manually boot it says
Bootloader
30.04
battery ok
OK to program
Connect USB
Data Cable
Is the phone savable. Please help ! Current phone is HTC incredible running incredibly re-engineered z
Sent from my ADR6300 using XDA App
Yes, if you are at the screen you see, you can sbf (system boot file)to factory original software.
There are is a Windows way and an Ubuntu way to sbf. I prefer the Ubuntu way personally, and I have never used any Linux b4 that.
Search these forums 'SBF Droid X'
I have also found some independant electronic stores willing to do the process.
Sent from my DROID2 using XDA App
i have droid x on ntelos i rooted but didnt change bootstrap flashed a rom and ofcourse bootlooped so i flashed sbf VRZ_MB810_2.3.34_1FF_01.sbf and now it comes up as verizon any ideas how to get back to ntelos..i have searched xda droidlife google and i cant find any kind of answer..the phone was purchased thru ntleos
Personally, I have royally screwed up my Droid X in the past. At one point, RSD Lite could not bring my phone back to life. However, Ubuntu saved my buttocks. Highly recommend using Ubuntu if you need to SBF your phone. Just speaking from experience.
nygbaby91 said:
i have droid x on ntelos i rooted but didnt change bootstrap flashed a rom and ofcourse bootlooped so i flashed sbf VRZ_MB810_2.3.34_1FF_01.sbf and now it comes up as verizon any ideas how to get back to ntelos..i have searched xda droidlife google and i cant find any kind of answer..the phone was purchased thru ntleos
Click to expand...
Click to collapse
I'm pretty sure you're outta luck until someone leaks ntelos SBF file, or.. take it into ntelos and see if they can help you They might.

Milestone X - C-Spire: Custom ROMS? Droid X Bootstrapper Working

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.....

Help with my TMO US Defy

"bricked" my Tmobile US defy while working with 2ndinit. I'm sort of noobish I read the instructions and got everything I needed but apparently something went wrong. I beleive I need an SBF file to reset everything. The thing is this forum is old and links are dead everywhere I look. Any help would be welcome. my device was runnin on stock tmobile eclair version 1. I tried a factory reset on stock recovery but no go and I dont have any custom recovery.
Sent from my LG-E980 using XDA Free mobile app
axel2230 said:
"bricked" my Tmobile US defy while working with 2ndinit. I'm sort of noobish I read the instructions and got everything I needed but apparently something went wrong. I beleive I need an SBF file to reset everything. The thing is this forum is old and links are dead everywhere I look. Any help would be welcome. my device was runnin on stock tmobile eclair version 1. I tried a factory reset on stock recovery but no go and I dont have any custom recovery.
Click to expand...
Click to collapse
If all else fails, flashing an SBF with RSDlite should work; it's the one advantage of having a locked bootloader. Check the all-in-one guide for details, esp. on efuse/CG levels if you want to be able to fully revert to the stock eclair.
The problem at this point will be finding an SBF file, as it appears the droid-developers archive is no longer working...
Yeah. Thanks I already fixed mine.
Sent from my LG-E980 using XDA Free mobile app

Categories

Resources