OTA fix bricked phone? - Defy Q&A, Help & Troubleshooting

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

Related

[Q] Bricked Defy and not recognized by my USB

Guys,
First of all, hello to all! So, I followed a tutorial to install Froyo on my Defy. Now I'm stuck with my phone trying to boot as soon as i put the battery on, but it never makes it past the "M". I can get into recovery. I wiped data, cache and tried to install the "update.zip" but it aborts saying "signature verification failed." I have the boot file (that was the next step) to install using RSDlite 4.9 but the phone is not even recognized any of my USB ports. Any ideas? Thanks to all in advanced.
press volumn up buton and power button on boot , once you saw the backlit is on , release the button , you will see the rsd litle showing your usb .
dont worry . i think it is your first time to use RSD only
yea i been through that ( doesnt work on vista )
you need to install rsd lite and 2.51 UK Firmware ( no usa )
google it and you will find it or on this forum
install usb driver from motorola webiste
install rsd lite
put uk firmware in ... C drive/ program files / motorola / rsd lite
install driver
If your phone is stuck on " M " then pull battery out
turn on and quicky press power + vol up ( i think ) before M even appear
wait till it say your boot loader and your battery
plug phone in
start rsd lite
on ... look up your uk firmware that you you recently put in rsd lite folder
then you should see your phone connected on the 1 slot
then hit start or something and wait it out .
Thanks guys! But I've been messing around with this thing for so long, I drained the battery. I had to run it up to the local phone store to get it charged. I'll pick it up in a couple of hours and give your advice a try.
Hey guys! it worked! I'm up and running. Now, anyone has a link to bypass this Welcome to Motoblur screen. Is there a Custom Froyo or Gingerbread Rom out there without Motoblur?
Alright... I'm up and running, but no camera!!! Heck, it was a learning experience. I guess I'll go back to 2.1 now. LOL
So the Chinese ROM was rooted. I installed Clockworkmod and restored from the backup i had made of the original 2.1 OS. I'm back to a rebooting phone not making it past the "M" I went back to RSDlite and realized the boot file said 2.2 only. Can anyone assist me finding the right one to go back to original. I haven't been able to find a thread about reverting back to original.
The more I read, the smarter I get seems like the only thing I'm missing here is the SBF file for my original T-Mobile OS. I'm looking at the motorola website, but I can't find it. Can anyone point me to it? Thanks all! Oh yeah, this is the first android phone i mess with so my apologies.
There is no us sbf file. You have to flash a uk version and restore 3g with the posted fix. You can find the links to available sbf files on this forum. They are not available thru moto's site.
Sent from my ME525 using Tapatalk
Just to make sure I got it right. After using clockworkmod to restore to my factory backup, I need to use the UK sbf to be able to boot to it. Correct?
I found the sbf for Central Europe with no Motoblur. Does anyone know of any issues with it?
well the only way to fix this if you previously backed up your rom/files with recovery ( good thing i did this ). If not then you have to live with what you got.
I backed up my original firmware using clockworkmod. I flashed to the Chinese 2.2 but my camera didn't work. Since the camera is important to me, the Chinese Froyo was a deal breaker. I installed clockworkmod again and "recovered" from my original backup but now my defy won't boot. Did I miss a step?
Your data from the backup may cause issues when rolling backwards. Install an eclair sbf, then restore. That worked for me.
On another note there is a fix for the camera. Check the forums.
Sent from my ME525 using Tapatalk
Bricked Defy and not recognized by my USB
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
arulshoponline said:
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
Click to expand...
Click to collapse
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
kvigneshkrish said:
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
Click to expand...
Click to collapse
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
arulshoponline said:
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
Click to expand...
Click to collapse
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
nsm1234 said:
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
Click to expand...
Click to collapse
I do not hear any sound from desktop/laptop.
I think I stuck in boot loop. When I try to power on the phone, it just shows CM7 boot logo for few seconds then restarts again shows the boot logo... this happens continually. When I try to enter into recovery, it does not go to CWM recovery instead it goes to stock recovery. I am still able to enter into boot loader. In boot loader, it says battery OK connect USB to program. When I connect USB, it is recognized by phone and says transfer mode: USB. But my PC does not shows up the phone.
I tried re-installing drivers and RSDlite many times but no luck. But I have nandroid backup of CM7. Is there any possibilities to enter into CWM recovery?
Any help is appreciated.
Edit:
I tried even different USB cables and PCs also.

[Q] Recovery...where are you?

Hi everyone,
today I've solved my problem (http://forum.xda-developers.com/showthread.php?t=1567301), but my recovery...is brake! When I boot into recovery, there is an exclamation point...I can wipe data/cache and use zip file from sd. Stop...nothing else!
Like this....I can flash with another rom? Or maybe my recovery is "damaged"?
Sorry for my poor english...
kaiserxol said:
Hi everyone,
today I've solved my problem (http://forum.xda-developers.com/showthread.php?t=1567301), but my recovery...is brake! When I boot into recovery, there is an exclamation point...I can wipe data/cache and use zip file from sd. Stop...nothing else!
Like this....I can flash with another rom? Or maybe my recovery is "damaged"?
Sorry for my poor english...
Click to expand...
Click to collapse
I think you're in stock recovery. What you need is install 2nd-init for the custom recovery and all it's features onboard...
Thanks for your reply!
I've tried to install 2nd-init (the stable, not the latest) and all it's ok...if I restarted my phone e try to enter to recovery mod, I see an Android BootMenu ( ) and I can choose stock recovery and custom recovery. If i start the custom it retunr this message:
Code:
Start Custom Recovery...
E:Can't run /system/bootmenu/script/recovery.sh (No such file or directory)
So confused....
Something braked with che CM9 kernel? If I start the stock recovery...I see the imaged attached in this post.
Boot normally into CM9. Open 2nd init and uninstall Bootmenu, then re-install bootmenu but chose "Latest - 1.0.7", not "Stable - 0.6.7"
Boot menu 1.0.7 is available with latest Sndinit2.0 version, get that sol from dev section and then install boot menu.
Sent from my MB526 using XDA App
Thanks to everyone!
Now I'n with the 1.0.7...I have the same image on the recovery this is strange!
I've tried to flash with che CM9, but the install aborted with this message:
Code:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
EDIT: the same error with my CM7.2
I'm coming from a 7.2 NIGHTLY (cm72-120127.0846-NIGHTLY-Defy+). I've tried to install the CM9 from this link http://forum.xda-developers.com/showthread.php?t=1432100 (I've used the Quarx rom). After this my Defy+ wan unable to boot (black screen). After a few of stock rom I'm back to the default rom (the spanish version, not the italian...it doesn't work ). I would like to flash the CM9, but first I think there is a problem with the recovery...why it displayed the image with the alert? Another question...with the CM7 my recovery have got a lot of option...now I've: reboot/apply update from sd/wipe data/factory reset/wipe cache. Is it normal?
What the hell I've done?
Most likely you're trying to flash unsigned ZIPs and the recovery wants signed ones, or trying to flash what should be extracted as "backup" and restored. You can turn off signature checking in recovery, if you know that you're flashing correct ZIPs and they're unsigned.
The stock recovery ALWAYS displays an image with the alert, because you can NEVER change it, until Defy bootloader will be unlocked (if it'll ever happen). Nothing strange about it.
I was able to use recovery and I tried to reinstall the CM9, but now my phone looks dead! No boot, no boot error, no recovery...nothing! Black screen. If I plug the phone to my pc...RDS Lite does't recognized the Defy. I would try to flash the sbf and come back to the 7.2 NIGHTLY...but how?
Damn...I'm so sad for this I'm hope there is a workaround...
kaiserxol said:
I was able to use recovery and I tried to reinstall the CM9, but now my phone looks dead! No boot, no boot error, no recovery...nothing! Black screen. If I plug the phone to my pc...RDS Lite does't recognized the Defy. I would try to flash the sbf and come back to the 7.2 NIGHTLY...but how?
Damn...I'm so sad for this I'm hope there is a workaround...
Click to expand...
Click to collapse
Did you press vol up and power??! You need to go to program mode for RSD lite to recognise your phone! It may have been that you flashed CM9 for Defy instead of CM9 for Defy+!! By no recovery do you mean you can't go even to stock recovery?!(Sounds almost impossible!)
Power and Vol+/Vol- doesn't work for me. Only the white led (charging status) works if I plug the usb cable to my pc. RDS
You need to go to program mode for RSD lite to recognise your phone!
Click to expand...
Click to collapse
I didn't understand what to do...
I start normally the RDS Lite...normally I see my phone automatically, now...nothing happened
kaiserxol said:
Power and Vol+/Vol- doesn't work for me. Only the white led (charging status) works if I plug the usb cable to my pc. RDS
I didn't understand what to do...
I start normally the RDS Lite...normally I see my phone automatically, now...nothing happened
Click to expand...
Click to collapse
Normally these steps are followed to flash SBF:
1.) go to bootloader mode (Vol up + power button. That's the program mode I was talking about)
2.) Now RSD lite will recognise your phone.
3.) Flash from RSD lite.
Are you saying that Vol up + power button = nothing happening in your phone? Not even black screen with
Bootloader .... blah blah
USB
Battery OK
Ready to program
????
If that's the case:
1.) Battery not charged.
2.) Go claim warranty!
Yes...this case! I know the bootloader screen
Code:
Bootloader .... blah blah
USB
Battery OK
Ready to program
but this time nothing...
Mhh...maybe the battery is near the 0% and the usb from a pc doesn't charge the phone? The led is white...but nothing. Maybe with the AC power?
kaiserxol said:
Power and Vol+/Vol- doesn't work for me. Only the white led (charging status) works if I plug the usb cable to my pc. RDS
I didn't understand what to do...
I start normally the RDS Lite...normally I see my phone automatically, now...nothing happened
Click to expand...
Click to collapse
Charge your battery... In another Defy phone, NOT McGyver method as many have already fried their batteries, using this trick!
I don't have another Defy for try this! I will try tonight at home, with the other cable connected directly to AC, and not to my pc. I hope it's work
No matter what cable you will try. At the moment your phone is not charging the battery. In order to start charging, you need to reflash it. And in order to reflash it, you need to get your battery charged... Sweet, ha? Get a buddy with a Defy to charge your battery and then reflash the phone.
Wow...this is a problem for me. Nobody have this phone and in Italy is not so much widespread...nobody know it :-(
kaiserxol said:
Wow...this is a problem for me. Nobody have this phone and in Italy is not so much widespread...nobody know it :-(
Click to expand...
Click to collapse
Then get to Amazon.com and buy a docking station with external battery charger if you dont want to use mc guyver, thats was my backupplan if I'm too stupid to use it... well mac guyver worked for me, 5 min charging and everything was fine xD
Here is an example
http://www.amazon.com/FosmonĀ®-Premi...9TVM/ref=sr_1_1?ie=UTF8&qid=1333017207&sr=8-1
It's hard to use the McGyver method? I'm a little bit scared to do this...but if it works to you...i will try
kaiserxol said:
It's hard to use the McGyver method? I'm a little bit scared to do this...but if it works to you...i will try
Click to expand...
Click to collapse
It worked like charm, battery is fine, i was able to flash a new rom...
One Usb-Cable "broken" but well who cares.
But if you try it, you need to be very very veeery careful.
Friend of mine is Hifi-Electrician and i had a little help from him, for testing which wires are the right ones to connect.
You have to be aware, that this could kill your battery and you need to buy a new one.
But once, everything is connected the right way, you also need to know that there is no safety or fuse or whatever, that safes your battery, so dont put it on too long, in my case, it took about 5 to ten minutes for 50-70% of battery, so dont let it be connected too long.
And one last thing, make sure, that there is no possibility for the cables to hit any other connector(?) on the battery, use some kind of tape, to make them stay in there position.
If your still willing to try this, good luck to you, as I say, this works. I dont know which MC Guyver you like to try, but i would recommend the batterycharge only, so not connected to the phone, version.
But think about this docking station too, its way more comfortable, easier, less dangerous, and amazon is really fast in shipping, so it would probaply just take 1-2 days.
I fuound this in the forum
http://forum.xda-developers.com/showthread.php?t=892026
I think it's the best way...or not?
Thanks
EDIT: can I use the usb cable from a pc? Or I need to plug the cable directly into the AC power?

[Q] ZTE Blade not starting, maybe bricked...

I think my phone is bricked
When I start up my phone it just stops when it says "ZTE"
Tried to reboot but wont work, its fully charged...
Please help
Are you rooted? Do you have ClockworkMod installed? What rom were you running?
NO
matt4321 said:
Are you rooted? Do you have ClockworkMod installed? What rom were you running?
Click to expand...
Click to collapse
No. No. and none.
I weren't running any roms or anything, but i have tried to root it with z4root and gingerbreak (etc..) a million times...
Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2
if he installs stock rom and unroots then it should be fine and he will keep his warranty
Sent from my Blade using xda premium
Ehhh..
matt4321 said:
Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
I dont quiet know how to do that
I was on 2.3.5 have 2gen stock rom
how do i get into fastboot then?
To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2
matt4321 said:
To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
Still looks way to complicated for me :/
Do u know any videos that can show me how to do it?
hi is it bricked or what?
hi all xda members, im new on this forum and i really don know were to post or something like that, sorry, and i have searched on every singel page in google and on a lots of forums, and i dont find anything that can help me with my problem..:crying:
So now to my poroblem, i have a zte blade II 2.3.6 gen3 un-rooted, i tryed but no luck... and now i think its really bricked...because i cant boot it at all, not in FTM, not in bootloader mode, not in recovery, the only thing i can boot it in is DFU but i cant flash from there, it is bricked or can this be fixed easily? Thanx in advanced guys!
ZTE Blade does not respond at all
My ZTE Blade does not respond at all.
I have tried to install the official update from android 2.1 - 2.2 using this official application from ZTE
( ztedevices official site -> downloads -> Greece -> smartphone ->Blade)
It stopped in the middle of the process and after that I cannot use neither Power&volume(+) nor Power+volume(-) nor Power.
It looks completely dead.
Battery is fully charged,
When connected to charger, back button does not get red.
When connected to computer does not show android logo.
I have copied gen1 to gen 2 image folder to sd... nothing
gen2 to gen 1 the same.
I have also tried the AIO-BLADE application no respond to any action.
I have been searching this forum and the internet for 2 days now. No one answers cases whith hardbricked phones.
I think the phone is out of warranty.
PLZ it is my only smartphone and there is no money for a replacement, I am unemployed.
:crying:

asus tf300t bricked

kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.

Brick motorola deft mb525

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?

Categories

Resources