accidentaly boot erased in download menu-now download mode not get.so can not flash
but usb detects when connect-but rsd lite not detect
any way to boot repair?
phone detect as ZEUS FLASH DEVICE
What phone, what OS ?
From your moms basement / using hacked rotary phone
BigBoyPhone said:
What phone, what OS ?
From your moms basement / using hacked rotary phone
Click to expand...
Click to collapse
droid pro mb632 -android
This strange, because zeus is majorly used by sony devices for flashing. Maybe, now your phone is unrecognizable like a motorola device, and that's why rsd lite, doesn't recognize it.
migui0401 said:
This strange, because zeus is majorly used by sony devices for flashing. Maybe, now your phone is unrecognizable like a motorola device, and that's why rsd lite, doesn't recognize it.
Click to expand...
Click to collapse
it happened after """"boot erased in download menu"""""
any way to repair?
zonetrichur said:
it happened after """"boot erased in download menu"""""
any way to repair?
Click to expand...
Click to collapse
Then, your phone doesn't turn on. I must ask, why did you erase the boot and why the **** there is an option to delete in the download mode, i have not used that model.
Related
Hi, today i was changing my rom From MIUI 1.9 to Gingerbread Retail, i've used the RSD Lite 4.9, after appear FINISH and PASS at RSD LITE i've closed the RSD and get my M2, when i try turn on my smartphone, it don't give me any signal, the screen stay black, anyone could help me?
First check - isn't battery empty?
Anonymous_ said:
First check - isn't battery empty?
Click to expand...
Click to collapse
MS2 is charging even using RSD.....
RSDLite only shows the PASS sign after the device completely booted and connected again via Motorola Phone Utilities or something like that.
Considering your battery isn't empty: turn on the phone, and connect it to your PC. Start up RSD Lite and the device should show up. Now flash again
newbie20110920 said:
MS2 is charging even using RSD.....
Click to expand...
Click to collapse
This isn't true. MS2 is charging only when fully and successfully booted. However, it isn't charging when on bootloop or in bootloader menu ("RSDLite mode").
But if you are sure your battery is charged, you should try to flash it again (and then don't forget to wipe data/factory reset in recovery) as w0ndersp00n already suggested.
w0ndersp00n said:
RSDLite only shows the PASS sign after the device completely booted and connected again via Motorola Phone Utilities or something like that.
Considering your battery isn't empty: turn on the phone, and connect it to your PC. Start up RSD Lite and the device should show up. Now flash again
Click to expand...
Click to collapse
this should work
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
So it looks like this phone is not completely unbrickable. I've seem to brick mine pretty bad.
The phone doesn't turn on at all. No vibration or other kind of feedback.
Doesn't appear on the computer either.
So my question is: is there any emergency download mode like in qualcomm based phones?
randhackr said:
So it looks like this phone is not completely unbrickable. I've seem to brick mine pretty bad.
The phone doesn't turn on at all. No vibration or other kind of feedback.
Doesn't appear on the computer either.
So my question is: is there any emergency download mode like in qualcomm based phones?
Click to expand...
Click to collapse
I don't know about it.
michal383 said:
I don't know about it.
Click to expand...
Click to collapse
It seems completely dead. Probably only with test point. Warranty most likely will refuse it since it is boot loader unlocked.
randhackr said:
It seems completely dead. Probably only with test point. Warranty most likely will refuse it since it is boot loader unlocked.
Click to expand...
Click to collapse
Yes Warranty falls if the bootloader unlocked. Test Point could help.
Well warranty will most likely only complain if it was bricked by the user and software modification.
If your phone broke because of an hardware issue, you have a chance that warranty still repairs it for free.
Schlengge said:
Well warranty will most likely only complain if it was bricked by the user and software modification.
If your phone broke because of an hardware issue, you have a chance that warranty still repairs it for free.
Click to expand...
Click to collapse
Well since it broke after I flashed b160 firmware I am most likely SOL. Since I had twrp flashed they will find out that it was modified..
My advice is not to mess with fastboot mode. Flash twrp and be careful with what you flash.
Did you tried to flash original firmware with the three buttons?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Potato997 said:
Did you tried to flash original firmware with the three buttons?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yup. It's completely dead. No fastboot mode, no recovery or erecovery. It simply does not turn on (or enumerate in a computer either).
If you could boot into recovery,the rest would be simple....download the stock firmware, unzip it and push the file to your phone,then install
LiaquateRahiman said:
If you could boot into recovery,the rest would be simple....download the stock firmware, unzip it and push the file to your phone,then install
Click to expand...
Click to collapse
He can't enter in recovery or fastboot.
Potato997 said:
He can't enter in recovery or fastboot.
Click to expand...
Click to collapse
Have you tried to enter fastboot or recovery solely using the button combos? or did you try using adb as well? It's possible your battery deep-discharged, or your power adapter/connectors are faulty.
Potato997 said:
He can't enter in recovery or fastboot.
Click to expand...
Click to collapse
Yes I cant enter anything in fact. There was a suggestion to connect the phone without battery to the computer but it implies opening up the phone and even if it did something I don't have the tools to flash it. (dc-phoenix only seems to work with phones with fastboot working)
As far as I know the symptoms that my phone is experiencing are due to the fastboot partition being messed up.
As far I was able to research there is another boot loader before the fastboot one. But the phone doesn't respond at all, it is dead. I will ask around in phone repair shops if they can reflash the phone.
randhackr said:
Yes I cant enter anything in fact. There was a suggestion to connect the phone without battery to the computer but it implies opening up the phone and even if it did something I don't have the tools to flash it. (dc-phoenix only seems to work with phones with fastboot working)
As far as I know the symptoms that my phone is experiencing are due to the fastboot partition being messed up.
As far I was able to research there is another boot loader before the fastboot one. But the phone doesn't respond at all, it is dead. I will ask around in phone repair shops if they can reflash the phone.
Click to expand...
Click to collapse
Before you do anything rash, have you considered getting a usb jig? Simply put the stock firmware on the jig then plug it into the usb port on your phone. It will automatically put your phone into download mode and install the firmware. Here's the link to make your own usb jig http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707. Hopefully this helps!!!
LiaquateRahiman said:
Before you do anything rash, have you considered getting a usb jig? Simply put the stock firmware on the jig then plug it into the usb port on your phone. It will automatically put your phone into download mode and install the firmware. Here's the link to make your own usb jig http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707. Hopefully this helps!!!
Click to expand...
Click to collapse
That is for samsung phones. I gave on trying to fix the phone. Next week I'm going to send it to a phone repair shop and see what they can do.
Edit: The phone repair guy says that the only way it can be repaired is by replacing the emmc or replacing the motherboard. So for now the phone will sit in the drawer until I manage to get a new board.
Hello
I had the same problem with my honor 7, the only solution is to replace the motherboard :/
If the phone is completely dead, warranty will accept it just because they will change your motherboard if they can't turn it on. I had the same problem last week, probably an hardware fail, I gave it to them saying that the phone simply turned off and they changed the whole motherboard (bootloader unlocked, twrp and root).
Well I tried sending it to the repair center. Two days later they replaced the whole phone, they said that there was an issue with the power ic.
B160 works for me.. hmm.... using it for like a [email protected]@
might be your hardware that cause the problem and not the firmware?
ivanwong1989 said:
B160 works for me.. hmm.... using it for like a [email protected]@
might be your hardware that cause the problem and not the firmware?
Click to expand...
Click to collapse
I'm starting to think so, I've flashed the replacement and it didn't brick. May or may not be related to the headers, but I don't want to be creative right now since I need the phone lol.
What is b160 can you explain
Hi everybody, recently decided to fix up my old motorola defy. Got it up and running with a new housing, lcd and battery. Decided to flash a custom rom, guess what, phone got bricked.
I'm currently stuck with the motorola log in an infinite loop so i cant use the volume down button to restore via my back up. Tired restore in bootloader mode using rsdlite following the steps from here. But Some how rsd lite doesn't detect the phone. Tried most versions and have installed the drivers repeated but nothing works.
Anybody have any good suggestions as to what i should do? dont really wanna use it as a paper weight. Thanks for reading.
Bump!
Uizpall said:
Hi everybody, recently decided to fix up my old motorola defy. Got it up and running with a new housing, lcd and battery. Decided to flash a custom rom, guess what, phone got bricked.
I'm currently stuck with the motorola log in an infinite loop so i cant use the volume down button to restore via my back up. Tired restore in bootloader mode using rsdlite following the steps from here. But Some how rsd lite doesn't detect the phone. Tried most versions and have installed the drivers repeated but nothing works.
Anybody have any good suggestions as to what i should do? dont really wanna use it as a paper weight. Thanks for reading.
Click to expand...
Click to collapse
Flash SBF using RSD Lite, this will fix your problem. Read this guide: https://forum.xda-developers.com/showthread.php?t=1216982
rootdefyxt320 said:
Flash SBF using RSD Lite, this will fix your problem. Read this guide: https://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
I tried but my rsd lite doesnt detect my phone, now the battery is flat and cant charge so i cant get into bootloader.
Uizpall said:
I tried but my rsd lite doesnt detect my phone, now the battery is flat and cant charge so i cant get into bootloader.
Click to expand...
Click to collapse
Use Macgyver method.
rootdefyxt320 said:
Flash SBF using RSD Lite, this will fix your problem. Read this guide: https://forum.xda-developers.com/showthread.php?t=1216982
Click to expand...
Click to collapse
rootdefyxt320 said:
Use Macgyver method.
Click to expand...
Click to collapse
My com and rsd still doesnt detect my phone in bootloader mode. Any way around that?
i was flashing wayne image on a2 via flashtool but by mistake i disconnected my device in midway of flashing.
now my phone is booting to fastboot mode and also showing androidone logo, but it isnt being detected by the device manager.
i have another a2 that is being detected on same pc without any issues in fastboot mode as well so it cant be drivers issue.
this worked for me:
https://en.miui.com/thread-3052407-1-1.html
asiranno said:
this worked for me:
https://en.miui.com/thread-3052407-1-1.html
Click to expand...
Click to collapse
Is that the Unique solution?
kevin2546 said:
Is that the Unique solution?
Click to expand...
Click to collapse
yes cause both phones are the same
asiranno said:
yes cause both phones are the same
Click to expand...
Click to collapse
I'm going to try, hope it can be recognize by my PC