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.
Related
I have a HKT75D xoom that I was trying to re-lock and unroot. Something along the way obviously went wrong. I think I may have used the wrong stock files to return it to stock and then locked it, but I am unsure. I do know that I am stuck in a boot loop now. If I turn the Xoom off...it just turns itself back on and sits and the M. I can get to fastboot, clockworkmod recovery, and rdp? (i forget the name, but its the other option under Android Recovery at startup.)
Is there any way I can use clockworkmod recovery or another method to restore my xoom to stock or have I bricked it? I have a 3G/Wifi xoom that is currently nothing more than an expensive paperweight so any help would be appreciated!
Its really really really hard to brick these things. With motorola devices, you just need to get RSD Lite running (a PC program), get into RSD mode on the device and then connect to the computer. You can then flash a stock sbf file and that will bring you back to stock firmware.
I can't provide links right now but if you look around/wait for someone, you'll be just fine. The fact that you can get into CWM, fastboot and **** is a good sign. The key is to not panic and do plenty of reading on how to troubleshoot this.
Thanks for the reply. I have done a ton of reading and became a bit overwhelmed so I knew posting would be the good thing to do. I just need some guidance here. I went and snagged RSDLite 5.6 from: http://forum.xda-developers.com/showthread.php?t=1348587
I believe that is the latest version. My question is where do I find a stock sbf file for my 3G/WiFi motorola xoom?
Edit: I got my xoom connected to RSD Lite and get the following in device properties if it helps any:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x001050
DRM Version: N / A
Phone Type: Engineering (0288504140C00557000000000000)
Click to expand...
Click to collapse
What region is your device from?
My Xoom is US.
Ok, in order to have your xoom seen in RSD you need to be in RSD mode on the Xoom. In order to get there, turn it off. Then hold power and volume up and it'll get you into rsd mode. Once it says something like "starting RSD support protocol" you can plug it in and RSD lite should recognize it.
Now you need the sbf file. I'll have a look around but I swear the file was posted on these boards somewhere before.
Edit: Found a thread with a ton of different SBF files for various regions. There is a VZW 3.2.2 sbf file toward the bottom of the OP. Make sure to charge up before you flash and as per usual, I am not responsible for anything that happens from flashing. Best of luck to you!
Thanks again for the help...unfortunately the filesharing sites linked no longer allow downloads.
I will keep an eye out for the file but if anyone knows a place then please let me know !
oh damn
I'm sorry
I found this. I don't know about legitimacy but perhaps its worth testing.
Hacktually said:
I have a HKT75D xoom that I was trying to re-lock and unroot. Something along the way obviously went wrong. I think I may have used the wrong stock files to return it to stock and then locked it, but I am unsure. I do know that I am stuck in a boot loop now. If I turn the Xoom off...it just turns itself back on and sits and the M. I can get to fastboot, clockworkmod recovery, and rdp? (i forget the name, but its the other option under Android Recovery at startup.)
Is there any way I can use clockworkmod recovery or another method to restore my xoom to stock or have I bricked it? I have a 3G/Wifi xoom that is currently nothing more than an expensive paperweight so any help would be appreciated!
Click to expand...
Click to collapse
Are you locked or not? I don't know if your stock restoration project was successful since you say you can boot into CWM recovery (stock would overwrite the recovery). Just make sure that you have a flashable rom zip file on your sdcard and then boot into CWM recovery and flash it. You're rooted so you know how to do that. FYI, you should probably do a complete data wipe/factory reset, cache wipe and dalvik cache wipe.
Why did you want to revert to stock/re-lock? Are you selling your Xoom or sending it to be fixed? If you wanted to upgrade to ICS, there a CWM flashable stock ICS rom available in the Development section.
I figured out that I was using the wrong stock img's from motorola dev. Used the right ones and now running Ice Cream!!!!!
ty for all the answers and help
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!
Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
marzell88 said:
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
Click to expand...
Click to collapse
are you able to put your phone in bootloader mode ? and witch version you use to flash your phone with RSD use one of those
http://sbf.droid-developers.org/umts_milestone2/list.php
yes i used the retail british 2.4
i am able to flash sbf file but it still wont go past moto logo and stock recovery cant install any roms. not allowed to install or something like that.
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
jakkokko said:
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
Click to expand...
Click to collapse
thank you i will try this. the battery is currently drained, so i need to recharge first. using wall charger (usb unit) but it didnt charge yet. keeps telling me the batt is low. any tips for that? only thing i found on here is to use a wall charger.
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
jakkokko said:
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
Click to expand...
Click to collapse
this worked as far as the batery problem, pita to do thou. now hope i can root the thing, since i did not yet succeed to run the adb drivers..
update: well, i fear the worst. after the last time flashing the sbf it wont turn on anymore. guess i did screw up the wire-DIY. will update if there is any good news. but for now it seems i should start looking for a new phone.,.
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