Related
Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.
Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.
Hi all,
I have thus far killed two Defy+ mobiles ($600 worth) following poor instructions on this site. I am now stuck using a 7" tablet as a phone!!!
My latest effort failed after installing 2ndinit 2.0 Stable, rebooting after turning USB Debugging off. Now it boot loops with the red Moto label. I have since read that one should never use 2.0 for Defy+ as it is known to have issues, even though the thread I took these instructions and the link from was referring specifically to a Defy+!!!
The last one I had did the same thing, only I thought it was because of the fact I chose to use the Latest rather than the Stable install of 2ndinit. I then proceeded to attempt to flash an SBF via the bootloader but now it is not booting at all, no logos, cant get to bootloader, nothing.
So, my question is, where can I get the latest Telstra Australia DEFY PLUS SBF from (please link me??) or one that I can flash over it that will work? Does anyone have any tips on how to recover this safely without sending it completely blank?
Also, does anyone have advice on how to recover the blank one?? Or is it useless?
Then, I would like to know, after I successfully recover the Defy+, HOW TO SAFELY 2ndinit it!!! I cannot afford to destroy another handset.
Thank you all for your prompt assistance! =)
which bootmenu did u install?and did u try flashing the SBF file via rsd lite?
fr0dzy said:
I have since read that one should never use 2.0 for Defy+ as it is known to have issues
Click to expand...
Click to collapse
I have run 2ndinit 2.0 on my Defy+ with no problem at all. I installed the latest bootmenu (1.0.7). Do you get the blue LED after powering the phone on?
You could try wiping data and cache in standard recovery. You should still be able to get in to that by holding vol- when you press and release the power button (press vol- and vol+ simultaneously when the android with the "!" in a red triangle appears). Your phone should still be rooted and have 2ndinit in place after a wipe. (Presumably you had rooted the phone? 2ndinit won't work otherwise.)
If that doesn't work then you may need to re-flash the SBF. If you know the build number of the ROM on your you can have a look on this thread to see if there is an SBF for it available online.
As a last resort, you could ask Motorola to fix it. If it's rooted then you've voided the warranty but if all it needs is a ROM flashing then they shouldn't charge you very much to do that. Better spend a few tens of dollars to fix the phone than write it off at a cost of several hundred dollars, surely?
recall while doing the install
did u root first??? did u get superuser permission prompt on downloading 1.0.7?did ur led flash GREEN???ensure that these are all yes
Dont worry brother. I had the same issue. I too got stuck in bootloop i.e at the M !
All I did was went in the stock bootloader ( POWER + VOL UP ) , connected it to my laptop. Downloaded RSDLite and the compatible sbf for my device ( Indian Version ) and then flashed it and it worked like charm
I would suggest you to use WiFi while using 2ndInit.
fr0dzy said:
Hi all,
I have thus far killed two Defy+ mobiles ($600 worth) following poor instructions on this site. I am now stuck using a 7" tablet as a phone!!!
My latest effort failed after installing 2ndinit 2.0 Stable, rebooting after turning USB Debugging off. Now it boot loops with the red Moto label. I have since read that one should never use 2.0 for Defy+ as it is known to have issues, even though the thread I took these instructions and the link from was referring specifically to a Defy+!!!
The last one I had did the same thing, only I thought it was because of the fact I chose to use the Latest rather than the Stable install of 2ndinit. I then proceeded to attempt to flash an SBF via the bootloader but now it is not booting at all, no logos, cant get to bootloader, nothing.
So, my question is, where can I get the latest Telstra Australia DEFY PLUS SBF from (please link me??) or one that I can flash over it that will work? Does anyone have any tips on how to recover this safely without sending it completely blank?
Also, does anyone have advice on how to recover the blank one?? Or is it useless?
Then, I would like to know, after I successfully recover the Defy+, HOW TO SAFELY 2ndinit it!!! I cannot afford to destroy another handset.
Thank you all for your prompt assistance! =)
Click to expand...
Click to collapse
There's always this quote: "Do it at your own risk"..
Never say it's the forumers instructions wrong or incorrect.
Read and double confirmed before taking the plunge modifying any system files.
Besides.. The death of your Defy is not really dead yet. I think your Defy boot just fine in the first place after installing 2nd-init. The only thing you need to do is press -Vol (when the blue light blink in the booting sequence) to enter into bootmenu and select boot normal as default. Because if this is your first installing 2nd-init, it might get you boot 2ndinit which was the cause of your bootlooping. Now you had flashed another sbf.. It's good to flash just Defy+ sbf and start again the process you failed in the attempt to get 2nd-init.
We learned from the mistake and master it over relentless practicing..
farsight73 said:
There's always this quote: "Do it at your own risk"..
Never say it's the forumers instructions wrong or incorrect.
Read and double confirmed before taking the plunge modifying any system files.
Besides.. The death of your Defy is not really dead yet. I think your Defy boot just fine in the first place after installing 2nd-init. The only thing you need to do is press -Vol (when the blue light blink in the booting sequence) to enter into bootmenu and select boot normal as default. Because if this is your first installing 2nd-init, it might get you boot 2ndinit which was the cause of your bootlooping. Now you had flashed another sbf.. It's good to flash just Defy+ sbf and start again the process you failed in the attempt to get 2nd-init.
We learned from the mistake and master it over relentless practicing..
Click to expand...
Click to collapse
+1 for your comment
Same thing happened to me as the OP.
Installed 2ndinit onto my Defy+, said installed and asked to switch off USB debugging and then reboot. I did that and am now in a boot loop. I didn't see the blue led when the phone rebooted, just straight to loop (red M logo, black screen, repeat).
I have tried taking the battery in and out (didn't help), celared cache and also factory wipe/reset (didn't work either). I can get the factory recovery and bootloader, but no android or 2ndinit recovery.
I assume I have to reflash with a full sbf. My question is this -
Does anyone have the stock Defy+ Telstra AU sbf for 2.3.4 (4.5.1-134 DPF-891) or more recent updates?
If not what is closest? I have found a few here but some of the 2.3.4 ones (bl5??) have no links (megaupload etc been pulled) or no root. This one looked promising (here) but no link. Would this one (here) be good?
Can I then apply OTA update to get back to AU firmware if I need? I would use MS2Ginger or CM7 if/when I get the phone working again, but return to stock is still useful.
Thanks for your help,
Nova
i must say u need to flash proper sbf to recover...
just wanna share my experience...
after installing SndndInit v2.0 ( with stock 2.3.6_134 DFP1321 ), i installed stable version of recovery & rebooted my phone...all of this with usb debugging "ON"...n got no errors! maybe there is no need to keep debugging off...
Sent from my MB526 using XDA App
OK, I flashed full sbf and got the phone working again (uses the sbf from the second link in my previous post). Then rooted and install 2ndinit again.
Boot loop again, exactly the same as the first time.
Install goes well, says it is installed, green led is on, however when I reboot, boot loop. There is no recovery screen or anything (except stock).
Is there some more detailed install instructions other than in the 2dninit thread? I have been transferring to sd card root, click apk to run 2ndinit, select 1.0.7 and it says everything worked. Just doesn't when I reboot.
Cheers,
Nova
No-one has any suggestions?
Do I need to put 2ndinit.apk in phone and not sd card?
I am going to try an older version and see if that works.
Cheers,
Nova
i hope you have rooted your phone properly else use SuperOneClick from here
you can download different versions of SndInitDefy.apk form here
go to Setings -> Applications -> Manage Application
look for SndInitDefy & clear its data (your previous install)
put the downloaded apk in SD card & run it (fresh install)
MY NOTE--keep usb debugging ON all the time...
run defy2ndInit - install 2ndInit Recovery - select latest version...
let it download...1st RED led lights then Green...wait for 2 minutes...reboot your phone...
when phone reboots BLUE led flashes for just 3-4 seconds...press VOL DOWN button when its flashing...
i hope this helps..im not a pro but i did follow exact same steps just 2 days back..
PS i did used v2.0 of SndInitDefy.apk...no problems yet..made backup twice & recovered too..
Well I tried v1.7 and that worked. I then updated to version 2.0 and that worked as well so i don't know what was going wrong. The only thing that happened different was the red led came on while 2ndinit 1.7 was loading (this had not happened before), so I would guess that 2.0 wasn't properly installing even though it said that it was installed.
Thanks for all your help.
Cheers,
Nova
hit thanks if I've helped
right now I'm having ICS on my phone thanks to quarx
Sent from my MB526 using XDA
apurvdate said:
hit thanks if I've helped
Click to expand...
Click to collapse
Did that. And thanks again for your help.
Cheers,
Nova
Had exactly same problem
I did the same experience as you after locking up after 2ndInit.
I used your recovery sbf as suggested and the phone works again. Thanks!
Were you able to find a Telstra Defy sbf and were you able to get 2ndInit to work and upgrade to CM9 & ICS?
Cheers,
apurvdate said:
i hope you have rooted your phone properly else use SuperOneClick from here
you can download different versions of SndInitDefy.apk form here
go to Setings -> Applications -> Manage Application
look for SndInitDefy & clear its data (your previous install)
put the downloaded apk in SD card & run it (fresh install)
MY NOTE--keep usb debugging ON all the time...
run defy2ndInit - install 2ndInit Recovery - select latest version...
let it download...1st RED led lights then Green...wait for 2 minutes...reboot your phone...
when phone reboots BLUE led flashes for just 3-4 seconds...press VOL DOWN button when its flashing...
i hope this helps..im not a pro but i did follow exact same steps just 2 days back..
PS i did used v2.0 of SndInitDefy.apk...no problems yet..made backup twice & recovered too..
Click to expand...
Click to collapse
I have rooted phone and tried both the 1.7 and 2.3 apps for 2ndInit Recovery and still on stock ROM but i never get the blue led flashing on boot up.
Any ideas?
Defy Plus indian firmware
nidhish91 said:
Dont worry brother. I had the same issue. I too got stuck in bootloop i.e at the M !
All I did was went in the stock bootloader ( POWER + VOL UP ) , connected it to my laptop. Downloaded RSDLite and the compatible sbf for my device ( Indian Version ) and then flashed it and it worked like charm
I would suggest you to use WiFi while using 2ndInit.
Click to expand...
Click to collapse
Can u please provide me the indian firmware link
Thanks
Zafar
Black camera!
Black camera!
Hey!
Somebody help me!!
Defy +: I put the original ruins of the ruins Rotolo, then the Boot Menu in Hungarian translation, and are followed by the error in the "Blade" my brain that I installed along with the 720p and panorama for Gingerbread Motorola
and since then my camera does not work, just great blackness!
Somebody help me!
green lenses!
---------- Post added at 06:31 PM ---------- Previous post was at 06:23 PM ----------
Black camera!
Hey!
Somebody help me!!
Defy +: I put the original ruins of the ruins Rotolo, then the Boot Menu in Hungarian translation, and are followed by the error in the "Blade" my brain that I installed along with the 720p and panorama for Gingerbread Motorola
and since then my camera does not work, just great blackness!
Somebody help me!
green lenses!
first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
http://sbf.droid-developers.org/umts_jordan/list.php
ive tried the first and last one not sure witch one is for my phone
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram to bootloader
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
jimbob60 said:
sorry about pic i cant post them
they are on my fb my only public album
my fackbook url:
/jacob.g.shaffer
first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=1743764
It worked for me.
i have now tried that and it was useful as far as the commands in the bat file but still nothing i did worked
i unrooted it the wipe cash and factory restore the Zerg Exploit did not work it would not root it so i used the commands to install bootloader it worked with no errors my led turned green to show success but still no blue light or Boot-loader. even when i use
E:\android\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
$ su
su
# reboot boot-loader
reboot boot-loader
it just reboots normally
any one else have some info?
so i still cant get a bootloader to come up ive been at this for a while and am still stumped i gain root and su but no custom boot loader just the stock one.
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps.
^
so this is just so people can see where im at in the chain of things here. im at the install 2ndinit
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
jimbob60 said:
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
Click to expand...
Click to collapse
I don't think the XT555c has a JB or even a ICS ROM. You can debloat GB and stay on it.
Sent from my Nexus 7 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2392187
http://forum.xda-developers.com/showthread.php?t=1216982
http://forum.xda-developers.com/showthread.php?t=1768702
http://forum.xda-developers.com/showthread.php?t=1032212
ive read thru a few threads other than those also and other people with the same mn and build have done it......
thats from my understanding that they wer able to get a boot-loader to work witch i can not get into a bootloader at all.and RSD wont flash anything to the phone evern tho ive used diffrent vr of rsd and the moto drivers.
so am i to assume that it just cant b done? that i could understand but other people with this phone/67d have done it and ive sent them pms but no reply same with some of the devs here who have helped others get this phone going so i guess im at a loss with this straight talk phone at least with installing a custom boot-loader/ROM.at least the phone works.....just outdated.screw you motorola
just a reply
@jimbob it my feelings that the "USA Moto defy xt555c, Straighttalk" does not have a blue LED built in. There is no evidence of it other than i have never seen one during the last year or so of having the phone (yes i do a lot of bluetooth stuff). Also to shed some light on your situation it is my understanding that 67d firmware has patched an exploit with the older bootloader and now has been upgraded to bl7. if this is your bl ver number then it is slim you will find the answer to your problems here. the only option i can come up with is to get or make fixed sbf for the device and flash/ downgrade. fixing the sbf only lies to the phone and tells it you have a higher ver android than you really do.... go figure motorola would be good at burning bridges! LMAO
thanks for replying. not to sure how to make a fixed sbf and the ones i found would not work because i couldn't get the program to flash anything to the phone. but then agen i never made a custom one
Hi!
I know that that I am mentioning now very old device as Motorola Defy MB525 green lense.
I wanted to flash Cyanogenmod 10.1 again in my Defy. I did full wipe and removed some folders on SD card reffering to old apps.
And it seems I messed up with Clockworkmod Recovery folder on SD and I left myself without it. And I tried to reinstall it using official guide found here: wiki.cyanogenmod.org/w/Install_CM_for_jordan[/url]
But I did not unpack all the files, so the installation was not fulfilled and I got like empty Android boot menu 0.6.1 without possibility to boot an operating system or to do anything (got errors whatever I choose: E:Error in /system/bootmenu/script/recovery.sh)
I have read tons of online materials and forums, and I could only restore stock Defy ROM 2.3.4 using RSD lite.
And I didn't find solution how to reinstall the boot menu :crying: So that is why I am asking you for help.
I can run only Download Mode and this useless Android Boot Menu.
How to reinstall Android boot menu/install custom recovery back?
I like my Defy and I do not want to put it in the drawer yet
Thank you in advance!
Vixificent
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
cristiand391 said:
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
Click to expand...
Click to collapse
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible. When I run my Defy it goes directly to Android Boot menu 0.6.1, which is not installed properly (source files missing, eg. ".sh" files).
Should I try to root it via computer? Then, how to do it with only Download Mode available?
Any help would be appreciated!
Vixificent said:
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible
Click to expand...
Click to collapse
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
robbak said:
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
Click to expand...
Click to collapse
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Vixificent said:
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Click to expand...
Click to collapse
I have a similar issue. How did you do the fix you used? The SBF files don't seem to be on the site you were referred to anymore.
Years ago, my unmodified (not rooted) Defy (running Android 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, although certain apps were suddenly no longer compatible) and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen.
However I could still get to the bootloader, so I tried to use RDS lite.
I got one sbf to say it passed, but the phone did not reboot. (I could only find 2 SBF's for the US and only got one to work). Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_J ORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.
I am not that tech savy regarding Android, so i am looking for some help.
Thanks!
Hi DefyVictim,
I understand your concerns - the restore process is a little bit complicated, but still not impossible. There is a strange procedure how to get your phone connected in such a way that RSD lite sees it. In the link given by robbak there is a video which is an exactly described tutorial. Did you follow it carefully?
It goes like - you need to FIRST get the bootloader and then connect it to the PC. If I understood it right, you tried to get the bootloader after you got the phone connected - which did not work.
I had a similar issue but finally figured it out. Oh, and there was just another thing - the battery was too low, so I had to do quite risky McGyver method to charge the battery somehow (no charging when your phone is bricked!), but be careful, this is potentially dangerous. Nothing happend for me, because I charged my phone for a minimum of time (like half an hour) to get it working.
Check this thread if you face battery low warning:
https://forum.xda-developers.com/showthread.php?t=892026
I know now it is a pain to get a SBF file, but not sure if the T-mobile should be working unless your phone wasn't coming from T-mobile (?)