Related
Hello everyone!
I wanted to flash my milestone 2 with the 2.3.4 sbf file but during the process, an error occured and now, my phone is booting by himself in bootloader mode. I've got this message telling me that the code is corrupted and when i try to flash it using RSD lite, the phone is detected but the process fails every time.
I've looked a bit around on google and the only solution that i found is to boot in OpenRecovery but i can't boot with anything else than Bootloader...
If you have any ideas, i'll be happy to read them. =)
You should probably flash/reflash a Milestone 2 specific SBF file.
Sent from my Transformer TF101 using XDA App
I managed to flash my phone with a 2.2 SBF file but at the end of the process, RSD lite send a message telling me to reboot it manualy. The thing is that now, i can't even turn it on and it's not recognised anymore by my computer...
goeland64 said:
I managed to flash my phone with a 2.2 SBF file but at the end of the process, RSD lite send a message telling me to reboot it manualy. The thing is that now, i can't even turn it on and it's not recognised anymore by my computer...
Click to expand...
Click to collapse
It sounds like the battery got too low. Try using a different battery.
Sent from my DROIDX using XDA App
or by a $5 battery charger from amazon
The battery won't charge but the thing is that just before flashing with the 2.3.4, i had about 50% battery so technicaly, i should have some. I'll try with another battery, i hope it will work. =)
Hi,
I am able to charge my defy via the wall mount charger but it is not being detected by rsd lite.
It is presentely under warranty .
I am able to access the recovery and bootloader.
can you help me with a update.zip file which will be able to clear all proof of root on my phone or some update file which will change the initially boot image to the deafult one.
Previously i was using cm7.
Sainyam said:
Hi,
I am able to charge my defy via the wall mount charger but it is not being detected by rsd lite.
It is presentely under warranty .
I am able to access the recovery and bootloader.
can you help me with a update.zip file which will be able to clear all proof of root on my phone or some update file which will change the initially boot image to the deafult one.
Previously i was using cm7.
Click to expand...
Click to collapse
If you have not flashed your phone with any non-downgradable Full SBF then you may use some different computer or try updating the USB drivers of your PC and then try to use RSD lite in bootloader mode and flash with some Froyo or Eclair SBF. This will turn your phone into factory defaults.
Good Luck!!
Rajneeshgadge17 said:
If you have not flashed your phone with any non-downgradable Full SBF then you may use some different computer or try updating the USB drivers of your PC and then try to use RSD lite in bootloader mode and flash with some Froyo or Eclair SBF. This will turn your phone into factory defaults.
Good Luck!!
Click to expand...
Click to collapse
Okay will try today.
Hope it works .
Okay tried every thing possible .
But nothing worked..
But thanks to wrong use of mcgyer technique i screwed up the motherboard.
And took it to motorola service centre.
And they are now going to replace it for free as it was under warranty.
I have query what will be replaced when motherboard is switched .
Will the memory(nand) be replaced or what?
Hello, i have a big problem with my motorola milestone 2 A953, I apologize for my english
pleased help me my milestone 2 a953 completely dead after trying to downgrade it with rsd lite from 2.3.6 to 2.2.1
pleeeeeeeeeased help
jakkokko said:
Hello, i have a big problem with my motorola milestone 2 A953, I apologize for my english
pleased help me my milestone 2 a953 completely dead after trying to downgrade it with rsd lite from 2.3.6 to 2.2.1
pleeeeeeeeeased help
Click to expand...
Click to collapse
You can't downgrade, search for the SBF here: http://and-developers.com/sbf:milestone2 and download it from here: http://sbf.droid-developers.org/umts_milestone2/list.php
Then, read this: http://forum.xda-developers.com/showthread.php?t=1497263
lean946 said:
you can't downgrade, search for the sbf here: http://and-developers.com/sbf:milestone2 and download it from here: http://sbf.droid-developers.org/umts_milestone2/list.php
then, read this: http://forum.xda-developers.com/showthread.php?t=1497263
Click to expand...
Click to collapse
i know that i did a big mistake there is any solution pleased
jakkokko said:
i know that i did a big mistake there is any solution pleased
Click to expand...
Click to collapse
Search for the rom you had before on the link I gave you (2.3.6 retail brazil, retail latam, personal argentina, vivo brazil, etc), copy the MD5, and search it on the other site to download it.
Then flash it with RSD.
Lean946 said:
Search for the rom you had before on the link I gave you (2.3.6 retail brazil, retail latam, personal argentina, vivo brazil, etc), copy the MD5, and search it on the other site to download it.
Then flash it with RSD.
Click to expand...
Click to collapse
sorry but i sad that i can no more get my milstone boot to flash it with rsd or with memory card i sad it is completely dad and i have exactly the rom witch i was in it and the other one witch i flash the phone with it then it become dead
pleased try to understand me an my problem and help that i think my phone need a jtag to be flashed and unbricked
Did you follow this procedure to put it in bootloader mode? http://forum.xda-developers.com/showthread.php?t=1032372
If your battery is discharged, try this: http://forum.xda-developers.com/showthread.php?p=10163846
If everything else fails, take it to Moto.
Good Luck
Lean946 said:
Did you follow this procedure to put it in bootloader mode? http://forum.xda-developers.com/showthread.php?t=1032372
If your battery is discharged, try this: http://forum.xda-developers.com/showthread.php?p=10163846
If everything else fails, take it to Moto.
Good Luck
Click to expand...
Click to collapse
first of all thank you very much for quick replay
the phone is no more able to be putted in bootloader mode
the battry is ok then the led of charg light on when lug it to usb
then there is no possibility to take it to moto for me
so there is an other method to force it (my phone) to get bootloader mode by hardware like gtag in samsung
If your phone shows a black screen right after turning it on, then it means you're on bootloader mode...
Next time pay more attention to the warnings...
Sent from my A953 using xda app-developers app
jakkokko said:
first of all thank you very much for quick replay
the phone is no more able to be putted in bootloader mode
the battry is ok then the led of charg light on when lug it to usb
then there is no possibility to take it to moto for me
so there is an other method to force it (my phone) to get bootloader mode by hardware like gtag in samsung
Click to expand...
Click to collapse
Try entering bootloader mode (vol up + camera + power). Even though the screen will stay black (but with backlight turned on), the phone will be in bootloader mode. You can see it by connecting USB cable - the white charging led will light up. At this stage you can simply start flashing latest stock gingerbread firmware via RSD lite. After several minutes the phone screen will display some info about flashing and you just have to wait a little bit longer.
You might be at a bit bigger trouble if your battery is empty. If so, you can try to recharge it with +5V current i.e. from USB port as described in this forum. Or you can find somebody with MS2, just to recharge the battery.
I also simply downgraded my MS2 to Froyo, and had problems like you. I was scared I bricked my phone, but luckily it's not so easy to be damaged!
rabinhood said:
Try entering bootloader mode (vol up + camera + power). Even though the screen will stay black (but with backlight turned on), the phone will be in bootloader mode. You can see it by connecting USB cable - the white charging led will light up. At this stage you can simply start flashing latest stock gingerbread firmware via RSD lite. After several minutes the phone screen will display some info about flashing and you just have to wait a little bit longer.
You might be at a bit bigger trouble if your battery is empty. If so, you can try to recharge it with +5V current i.e. from USB port as described in this forum. Or you can find somebody with MS2, just to recharge the battery.
I also simply downgraded my MS2 to Froyo, and had problems like you. I was scared I bricked my phone, but luckily it's not so easy to be damaged!
Click to expand...
Click to collapse
thank you for understanding my problem
i fully charge my battery with external charger then i clean it very well to be sure from the connection then i try to put the phone into bootloader mod ( volume up + camera+ power) screen still black then i plug the phone to pc the white charging led light up but the pc and RSD lite don't detect any think it is really confusing cause when i plug the phone without pressing (vol up + camera + power) the white charging dont led light up
but when i do it lghit up but nothing detected
any solution for that pleased
thank you every body i finally resolve the problem by downing this http://forum.xda-developers.com/showthread.php?p=10163846
then put the phone in bootloader mod with black screen and the RSD Lite detect it and i flash it with the good sbf and every think is ok
jakkokko said:
thank you for understanding my problem
i fully charge my battery with external charger then i clean it very well to be sure from the connection then i try to put the phone into bootloader mod ( volume up + camera+ power) screen still black then i plug the phone to pc the white charging led light up but the pc and RSD lite don't detect any think it is really confusing cause when i plug the phone without pressing (vol up + camera + power) the white charging dont led light up
but when i do it lghit up but nothing detected
any solution for that pleased
Click to expand...
Click to collapse
I'm having the exact same problem, and if someone know how to fix this I would be very grateful.
But before I log out I have a question about this? If the phone's ROM was bricked, what procedure Motorola should take to resolve the issue?
I heard that they make a direct installation on the ROM's cellphone, but just don't know how they do that. If someone knows how to, could tell us to reproduce the same strategy in our home's. I believe this knowledge could fix the problem we have.
:good:
Anyone?
alexpsad said:
I'm having the exact same problem, and if someone know how to fix this I would be very grateful.
But before I log out I have a question about this? If the phone's ROM was bricked, what procedure Motorola should take to resolve the issue?
I heard that they make a direct installation on the ROM's cellphone, but just don't know how they do that. If someone knows how to, could tell us to reproduce the same strategy in our home's. I believe this knowledge could fix the problem we have.
:good:
Anyone?
Click to expand...
Click to collapse
1. Install Moto's USB drivers.
2. Install RSD Lite
3. Download an SBF depending on the software you had before.
4. Reboot into downloader mode, and flash that.
If it still doesn´t work, google it. Use the defy forums, the MS2 has the exact same hardware.
If it STILL doesn't work, google again.
If it STILL WON'T WORK, google once again.
And if it still won't show signs of life, take it to moto's service center. Use your social skills and play dumb and maybe you get a cheap repair.
99% of problems happen when users don't read before flashing. It's explicitly written in huge bloody red letters to NOT downgrade from GB.
Lean946 said:
1. Install Moto's USB drivers.
2. Install RSD Lite
3. Download an SBF depending on the software you had before.
4. Reboot into downloader mode, and flash that.
If it still doesn´t work, google it. Use the defy forums, the MS2 has the exact same hardware.
If it STILL doesn't work, google again.
If it STILL WON'T WORK, google once again.
And if it still won't show signs of life, take it to moto's service center. Use your social skills and play dumb and maybe you get a cheap repair.
99% of problems happen when users don't read before flashing. It's explicitly written in huge bloody red letters to NOT downgrade from GB.
Click to expand...
Click to collapse
I've tried to flash the phone using sbf_flash at Linux. In older days I used RSD Lite and windows stuffs, now just Linux. But considering the behavior of the phone, it'll not meter what kind of tool I use, the problem will not be resolved. How you've said: "NOT downgrade from GB"
I've done this, and now the phone looks to be over! My mistake!! And now I would like to know if someone have the knowledge to bring the phone back from this situation, without physically change the ROM. What Motorola's service center people do to recover the phone in cases like that? If not involve hardware stuffs, just software, I believe it's possible to fix it for ourselves. And THAT was my question.
I know the things about downgrade, and the loss and bricks that this procedure could make, once I read it. I'm not worried about what was made, but about what could I do from now on, to repair the phone.
What was done there's no coming back!
But thanks anyway. If you know the "how to" to fix bricked phones, I'll be glad!
alexpsad said:
I've tried to flash the phone using sbf_flash at Linux. In older days I used RSD Lite and windows stuffs, now just Linux. But considering the behavior of the phone, it'll not meter what kind of tool I use, the problem will not be resolved. How you've said: "NOT downgrade from GB"
I've done this, and now the phone looks to be over! My mistake!! And now I would like to know if someone have the knowledge to bring the phone back from this situation, without physically change the ROM. What Motorola's service center people do to recover the phone in cases like that? If not involve hardware stuffs, just software, I believe it's possible to fix it for ourselves. And THAT was my question.
I know the things about downgrade, and the loss and bricks that this procedure could make, once I read it. I'm not worried about what was made, but about what could I do from now on, to repair the phone.
What was done there's no coming back!
But thanks anyway. If you know the "how to" to fix bricked phones, I'll be glad!
Click to expand...
Click to collapse
They use JTAGs, but even if you get your hands in a JTAG box, I don't think we have any way to flash anything with it.
My provider is releasing an OTA in the coming weeks. If I purchase a new phone, can I somehow download the new OTA to my new phone, and run an update from the recovery menu of the broken phone? This phone cannot be unlocked at the moment.
techjohnny said:
My provider is releasing an OTA in the coming weeks. If I purchase a new phone, can I somehow download the new OTA to my new phone, and run an update from the recovery menu of the broken phone? This phone cannot be unlocked at the moment.
Click to expand...
Click to collapse
So whay you need to buy new phone to unbrick your old phone. Tell how do you bricked your phone and what are symptoms of your bricked phone? When you coonect your phone to usb did you getting black screen and white led? Is RSD lite detecting your phone? Tell us more information and when i will try to help you. P.S. Defy is unbrickible phone - so it very hard to brick your defy...
turffe said:
So whay you need to buy new phone to unbrick your old phone. Tell how do you bricked your phone and what are symptoms of your bricked phone? When you coonect your phone to usb did you getting black screen and white led? Is RSD lite detecting your phone? Tell us more information and when i will try to help you. P.S. Defy is unbrickible phone - so it very hard to brick your defy...
Click to expand...
Click to collapse
Okay, RSDLite sees the phone, recovery is locked, and phone reboots after showing RW (Republic Wireless) logo, which is about 2-minutes after phone is powered on. I've tried adb wait-for-device, but nothing.
It's a XT557D Republic Wireless phone. It was officially released 2-months ago. No ROM available. I replaced the Phone.apk to brick the phone.
techjohnny said:
Okay, RSDLite sees the phone, recovery is locked, and phone reboots after showing RW (Republic Wireless) logo, which is about 2-minutes after phone is powered on. I've tried adb wait-for-device, but nothing.
It's a XT557D Republic Wireless phone. It was officially released 2-months ago. No ROM available. I replaced the Phone.apk to brick the phone.
Click to expand...
Click to collapse
Try wipe data and cache from stock recovery. Did you tried this, before bricking phone: http://forum.xda-developers.com/showthread.php?t=2023933 .Try it via fastboot. Good luck
turffe said:
Try wipe data and cache from stock recovery. Did you tried this, before bricking phone: http://forum.xda-developers.com/showthread.php?t=2023933 .Try it via fastboot. Good luck
Click to expand...
Click to collapse
I've done a stock wipe/data/cache.
techjohnny said:
I've done a stock wipe/data/cache.
Click to expand...
Click to collapse
Try install cwm via fastboot. LINK: http://forum.xda-developers.com/showthread.php?t=2023933 .I know it's xt535, but it should work on xt557, because it's hardware same, just other career... Also, try this: http://forum.xda-developers.com/showthread.php?t=18273 I'm not responsible for bricked phone.
turffe said:
Try install cwm via fastboot. LINK: http://forum.xda-developers.com/showthread.php?t=2023933 .I know it's xt535, but it should work on xt557, because it's hardware same, just other career... Also, try this: http://forum.xda-developers.com/showthread.php?t=18273 I'm not responsible for bricked phone.
Click to expand...
Click to collapse
Thanks. I just tried running it from the stock recovery, and it says "signature verification failed."
techjohnny said:
Thanks. I just tried running it from the stock recovery, and it says "signature verification failed."
Click to expand...
Click to collapse
Last .: try to flash xt535 ics, i don't know if it will work, so i dont responsible for bricked phone. But i dont think that this could happen, because difference between phones are just career. Its is on general section of defy. Good luck. Edit: try to flash that file via fastboot, connect your phone to fastboot and then unpack zip and click on bat file..
turffe said:
Last .: try to flash xt535 ics, i don't know if it will work, so i dont responsible for bricked phone. But i dont think that this could happen, because difference between phones are just career. Its is on general section of defy. Good luck. Edit: try to flash that file via fastboot, connect your phone to fastboot and then unpack zip and click on bat file..
Click to expand...
Click to collapse
This phone had fastboot removed.
--tj
techjohnny said:
This phone had fastboot removed.
--tj
Click to expand...
Click to collapse
My last hope may have been removed! Here's a response from Republic Wireless on their OTA update, which I was hoping would replace my /system/app/Phone.apk that's causing my boot-loop on my XT557D:
---START
Hi ...,
I received your help request and wanted to let you know that you won't be able to move the OTA install file. It will be downloaded to the memory of the device.
---END
Would it be possible to download the digital keys that are used on this phone and sign an application to run update in stock recovery?
techjohnny said:
My last hope may have been removed! Here's a response from Republic Wireless on their OTA update, which I was hoping would replace my /system/app/Phone.apk that's causing my boot-loop on my XT557D:
---START
Hi ...,
I received your help request and wanted to let you know that you won't be able to move the OTA install file. It will be downloaded to the memory of the device.
---END
Would it be possible to download the digital keys that are used on this phone and sign an application to run update in stock recovery?
Click to expand...
Click to collapse
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
turffe said:
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
Click to expand...
Click to collapse
If I do this, I still won't be able to connect to Republic Wireless via WIFI, since they have a special ROM cooked that connects your phone to their network to update.
turffe said:
You can't resign moto-updates.zip cause the signing keys can get only moto, if we could get that keys we would have unlocked bootloader on mb525... Try flash this 4.0.4 ICS for XT535 (dont know if this will work, so i not responsible for bricked phone..), but it should work since it also defy xt just for other career.... LINK: http://www.mediafire.com/?5bbefsbd9g64p .Try flash this, it should boot, but if it doesn't - stuck on black screen (NOT ON BOOTLOOP - M logo), blame only yourself! Also if it pass - shows M logo after flash, remove battery and boot it in stock recovery and make wiped data/factory reset. Good luck! :good: Boot it in fastboot: hold down vol-up + vol-dwn togheter and then press power button
Click to expand...
Click to collapse
BLACK SCREEN. It looks as though it was going to flash successfully, but the M logo name came back. Now, it shows up at a modem device in my syslog of Linux. Guess I've totally bricked it now?
--tj
techjohnny said:
BLACK SCREEN. It looks as though it was going to flash successfully, but the M logo name came back. Now, it shows up at a modem device in my syslog of Linux. Guess I've totally bricked it now?
--tj
Click to expand...
Click to collapse
Can you enter to fastboot? Is it stuck on bootlogo or on animated bootanimation? If you can enter to fastboot you're just in bootloop. I will try help you much as I can.. I will try to search for XT557 files...
turffe said:
Can you enter to fastboot? Is it stuck on bootlogo or on animated bootanimation? If you can enter to fastboot you're just in bootloop. I will try help you much as I can.. I will try to search for XT557 files...
Click to expand...
Click to collapse
It doesn't even seem to want to power on anymore, but when plugged into USB, it shows up as a Qual Comm Modem?
techjohnny said:
It doesn't even seem to want to power on anymore, but when plugged into USB, it shows up as a Qual Comm Modem?
Click to expand...
Click to collapse
RSD Lite showing your phone or nothing?
turffe said:
RSD Lite showing your phone or nothing?
Click to expand...
Click to collapse
Nothing now. I forced me to manually power on the phone. I've noticed the flash model is different than the flash:
My phone: MSM7627
Flash file: MSM7227
Windows is requesting a USB driver for a modem.
No Charge LED when phone is plugged into AC.
Oh well. Didn't have high hopes this would work, but was worth the try.
techjohnny said:
Nothing now. I forced me to manually power on the phone. I've noticed the flash model is different than the flash:
My phone: MSM7627
Flash file: MSM7227
Windows is requesting a USB driver for a modem.
No Charge LED when phone is plugged into AC.
Oh well. Didn't have high hopes this would work, but was worth the try.
Click to expand...
Click to collapse
Hard brick.
XT557 spec: http://pdadb.net/index.php?m=specs&id=3753&c=motorola_defy_xt_xt556__xt557
XT535 spec: http://www.gsmarena.com/motorola_defy_xt535-4622.php
F***... Different cpu.... Sorry friend, but blame only yourself, because you started bootloop with your bad Phone.apk....... & not maded CWM backup before modding I think now you can buy new XT530 or if you have warranty sent it for repair or try to tell moto & tell that it powered down itself while charging. The service will replace board or with defy xt530 phone, which is as I know low activity device, but if you bootloop it, you can reflash stock ics via RSD....
XT557D repbulic bootloop
has anybody made any progress in the boot loop... my republic xt557d is in bootloop on moto nonanimated screen
The problem started when i tried to downgrade my defy to CM7.2 from CM10.
First i was getting a problem of "Encryption unsuccessful". i browsed through a lot of threads and decided to use Rsdlite to flash a sbf file.
i tried flashing the Asia retail version.It showed 'Passed" in Rsdlite but i got stuck at the Motorola logo.
i again browsed through a number of threads, watched a few videos, and decided to flash a sbf "DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed" (i now realise this was fatal for my phone). (till this point the "SW Update" screen on phone showed the bootloder version to be 9 or 10 (dont exactly remember)). The phone just died after this. It wont start . No Motorola logo, No Recovery Mode, No bootloader mode. It just showed white led when connected to the pc and was not recognized by Rsdlite. i realised that the problem might be Empty Battery.
After this i tried the McGyver method and finally my phone was recognized by the rsdlite.
but now during the SW Update phase the screen doesnt show any bootloader version. and the end result is the same. White light at top, phone doesnt start, no M logo,,,, just a dead brick... another problem is that even after i put in a new battery, rsdlite will only recognise the phone only when i use the McGyver fix.
Please help me..... give me a working sbf file..
i dont want to just give up on this incredible phone...please help....
bhanudude said:
The problem started when i tried to downgrade my defy to CM7.2 from CM10.
First i was getting a problem of "Encryption unsuccessful". i browsed through a lot of threads and decided to use Rsdlite to flash a sbf file.
i tried flashing the Asia retail version.It showed 'Passed" in Rsdlite but i got stuck at the Motorola logo.
i again browsed through a number of threads, watched a few videos, and decided to flash a sbf "DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed" (i now realise this was fatal for my phone). (till this point the "SW Update" screen on phone showed the bootloder version to be 9 or 10 (dont exactly remember)). The phone just died after this. It wont start . No Motorola logo, No Recovery Mode, No bootloader mode. It just showed white led when connected to the pc and was not recognized by Rsdlite. i realised that the problem might be Empty Battery.
After this i tried the McGyver method and finally my phone was recognized by the rsdlite.
but now during the SW Update phase the screen doesnt show any bootloader version. and the end result is the same. White light at top, phone doesnt start, no M logo,,,, just a dead brick... another problem is that even after i put in a new battery, rsdlite will only recognise the phone only when i use the McGyver fix.
Please help me..... give me a working sbf file..
i dont want to just give up on this incredible phone...please help....
Click to expand...
Click to collapse
Do you have Defy or Defy+? If you have Defy (which lens?), then you just made your phone BL7. Follow this thread and report back - http://forum.xda-developers.com/showthread.php?t=1889325.
When downgrading from CM10 to CM7.2, always remember to format system and data to ext3 first! I made the same mistake (had the same problem as you), then I followed the above guide.
When the SW update screen comes up, bootloader version doesn't show normally.
hotdog125 said:
Do you have Defy or Defy+? If you have Defy (which lens?), then you just made your phone BL7. Follow this thread and report back - http://forum.xda-developers.com/showthread.php?t=1889325.
When downgrading from CM10 to CM7.2, always remember to format system and data to ext3 first! I made the same mistake (had the same problem as you), then I followed the above guide.
When the SW update screen comes up, bootloader version doesn't show normally.
Click to expand...
Click to collapse
Mine is a Defy (MB525) green lens and not a defy+ (mb526). U sure that i should follow this guide...??
Also i Cant manually power on my device...!!! even if i flash some sbf from the list of sbfs the rsdlite will show pass but i wont be able to power on my phone... help help...
bhanudude said:
Mine is a Defy (MB525) green lens and not a defy+ (mb526). U sure that i should follow this guide...??
Click to expand...
Click to collapse
I think you just flashed a bl7 sbf (Defy+) meaning your phone now has Defy+ firmware with green lens. If you've tried everything else and it didn't work, then do that as a last resort. Both CM10 and CM10.1 will work.
hotdog125 said:
I think you just flashed a bl7 sbf (Defy+) meaning your phone now has Defy+ firmware with green lens. If you've tried everything else and it didn't work, then do that as a last resort. Both CM10 and CM10.1 will work.
Click to expand...
Click to collapse
Btw, this is the information i get when i connect my phone to my pc through rsdlite...
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 04500210611268010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: 0a637f619605568d5c5aa50534a5bd6f5d743076
BP Public ID: 0000000000000000000000000000000000000000
To confirm you've gone to BL7, you can try flashing froyo sbf. There will be a bootloader error. If that's the case then follow that thread and CM10/10.1 or MS2Ginger are the only options I think.
hotdog125 said:
To confirm you've gone to BL7, you can try flashing froyo sbf. There will be a bootloader error. If that's the case then follow that thread and CM10/10.1 or MS2Ginger are the only options I think.
Click to expand...
Click to collapse
Thanks a lot Hotdog..!!
my defy is finally alive..!!!
but now its mb526.... so some feature wont work right..?? cn u tell me how to go back to defy from defy+ ???
bhanudude said:
Thanks a lot Hotdog..!!
my defy is finally alive..!!!
but now its mb526.... so some feature wont work right..?? cn u tell me how to go back to defy from defy+ ???
Click to expand...
Click to collapse
Yes, the camera won't work since it is green lens. The sbf you flashed in the beginning (DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed) made your Defy into Defy+. That sbf was meant to be for Defy+ users.
You cannot go back to Defy. Since your phone is now BL7, you cannot go back to froyo.
So now you can flash MS2Ginger/CM9.1 (by walter79)/CM10/CM10.1 or any 2ndboot ROM. I think you can't install CM7 also.
You can find MS2Ginger,CM10/10.1 ROMs by Googling. Download CM9.1 by walter79 here - http://d-h.st/users/walter79/.
HI, I believe I have the same problem... I tried flashing my defy + with a portuguese version of android 2.3, when I was at 2.3. Now all I have is black screen with white led and it is not recognized by rdslite. As far as I understand I have first charge the battery with McGyver method or other charger, which will make the rdslite recognize the phone, and after that I can flash it with a newer firmware and get it back to life. Is this correct?
Thank you!
lews01 said:
HI, I believe I have the same problem... I tried flashing my defy + with a portuguese version of android 2.3, when I was at 2.3. Now all I have is black screen with white led and it is not recognized by rdslite. As far as I understand I have first charge the battery with McGyver method or other charger, which will make the rdslite recognize the phone, and after that I can flash it with a newer firmware and get it back to life. Is this correct?
Thank you!
Click to expand...
Click to collapse
Unless your battery is low do not use McGyver. Use it only as a last resort.
You must have tried to downgrade, which is not possible in Defy+ through RSDLite.
Do you know if there is any way to recover my phone? It is not being recognized by rdslite anymore. While rsdlite was recognizing it I tried flashing with JORDN_U3_97.21.51, but nothing happened.
lews01 said:
Do you know if there is any way to recover my phone? It is not being recognized by rdslite anymore. While rsdlite was recognizing it I tried flashing with JORDN_U3_97.21.51, but nothing happened.
Click to expand...
Click to collapse
The usual. Update drivers and RSDLite, make sure you are in bootloader mode. If all else fails, go McGyver and get RSDLite to recognise the phone.
lews01 said:
Do you know if there is any way to recover my phone? It is not being recognized by rdslite anymore. While rsdlite was recognizing it I tried flashing with JORDN_U3_97.21.51, but nothing happened.
Click to expand...
Click to collapse
Y U FLASH ECLAIR SBF? You happened to find the retarded Eclair SBF that has a CG version of 5. Make sure that you are in bootloader, then make sure that it is really a low battery problem (either the phone doesn't turn on at all, including regular boot, bootloader or recovery) or it says "battery low, cannot program" in bootloader.
hotdog125 said:
The usual. Update drivers and RSDLite, make sure you are in bootloader mode. If all else fails, go McGyver and get RSDLite to recognise the phone.
Click to expand...
Click to collapse
And after that, with firmware should I flash it?
Thanks again!
bhanudude said:
Thanks a lot Hotdog..!!
my defy is finally alive..!!!
but now its mb526.... so some feature wont work right..?? cn u tell me how to go back to defy from defy+ ???
Click to expand...
Click to collapse
How did you do that if you can't access the recovery ??????????????
droid_<3er said:
Y U FLASH ECLAIR SBF? You happened to find the retarded Eclair SBF that has a CG version of 5. Make sure that you are in bootloader, then make sure that it is really a low battery problem (either the phone doesn't turn on at all, including regular boot, bootloader or recovery) or it says "battery low, cannot program" in bootloader.
Click to expand...
Click to collapse
From my Experience ::
1. cross your fingers :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
2.Use the Mcgyvor's method to get your phone recognized by rsdlite. (Only as a last resort)
3.After that just follow the procedure in Hotdog's Guide ( 2nd or 3rd reply in this thread)
4.After that your phone will become MB526.
5.flash any ROM designed for both 525 and 526
Cheers..!! :goodYou can treat me If you want..
bhanudude said:
From my Experience ::
1. cross your fingers :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
2.Use the Mcgyvor's method to get your phone recognized by rsdlite. (Only as a last resort)
3.After that just follow the procedure in Hotdog's Guide ( 2nd or 3rd reply in this thread)
4.After that your phone will become MB526.
5.flash any ROM designed for both 525 and 526
Cheers..!! :goodYou can treat me If you want..
Click to expand...
Click to collapse
Please help!:crying:
I can't find the sbf....the links from here doesn't work http://forum.xda-developers.com/showthread.php?t=1618718
Where did you find the sbf??
MikBre said:
Please help!:crying:
I can't find the sbf....the links from here doesn't work http://forum.xda-developers.com/showthread.php?t=1618718
Where did you find the sbf??
Click to expand...
Click to collapse
You're gonna have to wait, buddy. It says right up on the website: "Quit e-mailing me about "no links" lol ..... there was a HDD failure - links are being recovered (will take some time)."
Right now only the 2012 and 2013 phones are up (etc. Droid Razr, Droid Razr HD, Electrify M, Photon Q).
Unless someone can upload the huge-a** file to some file-sharing service, you're out of luck. Sorry. I don't even have the Defy SBFs anymore.
droid_<3er said:
You're gonna have to wait, buddy. It says right up on the website: "Quit e-mailing me about "no links" lol ..... there was a HDD failure - links are being recovered (will take some time)."
Right now only the 2012 and 2013 phones are up (etc. Droid Razr, Droid Razr HD, Electrify M, Photon Q).
Unless someone can upload the huge-a** file to some file-sharing service, you're out of luck. Sorry. I don't even have the Defy SBFs anymore.
Click to expand...
Click to collapse
Restored my phone :good:
SBF from here
:victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory:
Which SBF did you flash, please?