I have a Motorola Defy, and I'm a noob. I was trying to install Cyanogen Mod 7 on it, but something went awry, and here's a little about the situation. I'm using Motorola USB Drivers 4.9.0 and RSD Lite 5.3.1. I'm using a PNY 16 GB class 10 microSD card. I no longer have the stock 2 GB card. I flashed 3.4.2 177-5 Nordic onto the phone. I always forgot to put my phone into recovery mode before ever flashing these different sbf files. Nordic worked fine except it said the sd card was always unmounted even though it was plugged in. I couldn't do much which that so I flashed 2.2.1-3.4.2 107 T-Mobile US onto it (again not from recovery) and the sd began working again.
I allowed usb debugging and rooted with Superoneclick 1.9.5 ShortFuse and installed 2nd Init for Defy. I restarted it twice and then turned off usb debugging. I booted into 2nd Init (not 2nd boot), went to install zip from sd, and opened the cyanogen_jordain-ota-beta5.1.zip file. I then installed Google apps 20110613 and wakeup_fix.zip. I know this is stupid but I wasn't reading the output for each step, but I think I remember it saying that it was updating for the cyanogen. When I wiped the cache and the data, it said things like:
E:can't mount /dev/block/mmcblk1p24
(Invalid argument)
E:Can't mount CACHE:recovery/command
E:Can't mount/dev/block/mmcblk1p24
(Invalid argument)Can't mount CACHE:recovery/log
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
E:Can't mount /dev/block/mmcblk1p24
(Invalid argument)
Now it's stuck on the Motorola boot logo, except it'll still enter 2nd Init boot menu.
It also could not read anything from the sd card including Cynanogen for the second time until the next day after I put the sd card into my computer and viewed it. So now it can read from the sd card again. I have no backup.
I tried reflashing it, but when I put the phone in stock recovery, no device is detected, however, my computer does recognize something's plugged in by that noise the system makes whenever I plug or unplug it. I tried using ADB shell to mount the cache on recovery mode but no luck. It says no device detected. I might not have been doing that right.
I may be forgetting some information because I tried fixing it very late last night.
I don't own very many nice things, but this is one of them, and I'd really like to get it running again. Any help will be very appreciated. Thank you all for reading my post-
Kibogami
whats your email address so i can send u the original sbf
While u boot hold vol up button ull see bootloader n connect to pc
Rsd will recognize...
Sent from my MB525 using XDA Premium App
Thank you. That worked, and the phone went into bootloader mode. RSD Lite recognized it, and then, I flashed 2.2.1-3.4.2-107 T-mobile US. After I flashed it, though, I had to manually power it up. RSD Lite said finished, but now, it's stuck in a bootloop. It shows the motoblur animation, and then, the T-mobile animation and keeps repeating the 2. So I let it do that for a little while. I went to bootloader mode to flash 2.1, but it says battery too low to program, and RSD won't recognize it.
Thanks again
Kibogami
when you power up your phone go into factory recovery vol- and factory reset should boot up fine
Ok. Got everything back to normal. Thanks again everyone. I charged my phone with the wall charger for a little while, and that got things moving again. I went to bootloader, flashed 2.2.1 again with RSD Lite, did a factory reset, and was good to go.
Does anyone know about why CM7 didn't install properly in the first place?
Thanks
the cm7 zip file also flashes a new recovery sometimes you have to reinstall cm7 from the new recovery essentially install once reboot into recovery and repeat works fine have had the same problem myself a while ago anyways glad i could help and enjoy!!!!
having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect
jsteve01 said:
having the same problem but rsd isn't recognizing the phone when I connect in bootloader. windows makes a noise but nothing beyond that when i connect
Click to expand...
Click to collapse
Open RSDLite with administrator priviledges, make sure it is the latest RSDLite and moto drivers (6.1 I think).
Related
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
slowcurve said:
i think i just bricked my phone
i downloaded the RC2 rom, I have the bootstrap recovery and CWM and the unknown sourses app.
i was following your instructions on the dev release on how to install the rom
I downloaded the rom, put in on my sdcard i checked debugging usb
and then i hit the recovery bootstrap recovery button then the normal one ...
when it boots again i get critical error: CC00
DBAD
then another scren shows up with: Bootloader
09.12
Err:A5,70, 39,00,21
and i on the same screen it says: Battery: OK
OK to program
Connect USB
Data Cable
whe i conect the cable its says tranfermode: on
i dont know what to do at this point is there anything i could do to fix this?
I already tried yanking the battery out SDcard and put back in i just go back to the same screen
Click to expand...
Click to collapse
I just replied to your email, you efused!
This is exactly what happened to me when I bricked my gf's first bravo.
Good news is sbf and its fixed. You wont even lose any data.
IDK how this happens, seems it has happened twice now, there must be a specific change made before bootstraping that causes the check.
Either way the code group that is problematic is in the sbf, flash it and your good.
you will need to reroot, rerun nonmarket apps enabler, and re-bootstrap recovery, then reboto recovery and flash rc2 and you will be fine.
sorry for the spam... i panic'd..
i have the rsd lite i searched for sbf's and a whole bunch came up mind pointing which one i should use.
Edit: Its fixed thank you bando, you own half of my soul
I tried to flash my MS2, but now I have no boot and no access to the phone.
Story:
- root via paxChristos' Linux Port of DooMLoRD's Easy Rooting Toolkit
- backup via Titanium Backup
- backup via Bootstrap
- installed CyanogenMod and the nightly build cm_droid2_full-139.zip
- realized ... it is the wrong Mod, because for Druid2 and I have a Milestone2 = not the same
- sudo ./sbf_flash MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20RTDACH_P016_A005_HWp2a_Service1FF.sbf
And now, I have a dead phone ... even could not start it. It is just a black screen and nothing more!
The only thing that show "life" is the LED on the side of the USB-Cable plug!
I also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable!
Is there a way to flash the phone anyway?
Would be nice to have a little help!
A little more info:
Plug in USB cable and lsusb:
Bus 002 Device 013: ID 22b8:4280 Motorola PCS
Long press on the power button and lsusb:
no Motorola
Keep USB cabel in the phone, unplug the batterie and plug in back ... lsusb:
Bus 002 Device 015: ID 22b8:4280 Motorola PCS
And more info:
udev-rule1 (worked to flash the phone)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
udev-rule2 (tried after reboot of phone showed lsusb shown before)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="4280", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
Also ... not worked:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
$ ./adb kill-server
$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ ./adb shell
error: device not found
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
First of all ... thanks for helping me!
Anonymous_ said:
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
Click to expand...
Click to collapse
Nothing happend ... screen is black, LEDs are off!
DreadPirateDan said:
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
Click to expand...
Click to collapse
Battery should be ok, it also don't work with Charger on!
If it is impossible to remove the locked bootloader, why can I still not boot?!
If the device bricked only a black screen shows up. This is bootloader mode. RSDLite will recognise your phone and flash an SBF.
Sent from my MotoA953 using XDA App
Damn ... just bought a used one on eBay and now I have my old one fixed! *lol*
Thanks to you all ..
I used my laptop with Windows7 and RDS light from Chip Online
Then I used the SBF Version 2.3.4!
reboot ...DONE ... Milestone2 worked again!
But ...
root via zergRush_automated_Linux_root
Installed bootstrap-1.0.0.5-droid2.apk from SD-Card because:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
I think the message is very clear. The bootstrapper never installed to begin with. Second of all, why are installing the bootstrapper like that? Instead of copying it to your SD-Card and execute it from the file browser on your phone. It will be installed, after which you should execute it. It will ask for root access when you press the bootstrap button. You give it and then you press the button Reboot Recovery. Then you'll be in CWM. You can't install CM7 from Motorola's recovery, which is what you've been doing all the time.
Further: Endless7 has written a guide here: http://forum.xda-developers.com/showthread.php?t=1310641
I'd suggest you follow it, and if you don't understand something ask it.
HAPPY NEW YEAR!!!
Okay, actual I have my MS2 with the original sbf and I wait until my second MS2 is here.
Then I try to install CM!
Never the less I have questions, just to be sure.
When I install the droid2bootstrap, I just copy the file to the sdcard and then install it at the phone?! Is this correct?
Then the HowTo says: 3.open droid2bootstrap and select install recovery
But there is nothing like "install recovery" to select. There is just a screen with two buttons (Bootstrap Recovery and Reboot Recovery) ... I think "Bootstrap Recovery" first, then reboot?
If I do the steps above, I have an bootloader installed on my phone?! Which I can start with the volume buttons at bootup?
Wow, I have to learn a lot about Android phones! I read the wiki, but asking questions will help me more!
Thanks to you all!
What you described is correct except the startup with volume buttons.
You have to use the Reboot Recovery button to get in CWM, where you can flash CM7.
And just for the record: every phone has a bootloader installed, otherwise it wouldn't be able to boot an OS. Fact is that you can't replace it on the Milestone 2.
Don't mix up Recovery and Bootloader. They're different things.
sasch42 said:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
Click to expand...
Click to collapse
bootstrap is not copied to /system/app , adb said "failed to copy...".
maybe copy it do /data/app ?
You wiped data and cache.. how about dalvik?
Because the copy failed, I installed the app from the sdcard (/data/app was also read only).
But as described here (http://forum.xda-developers.com/showthread.php?t=1310641) I used the wrong app!
IMHO it is the same to copy the app via adb or install it from sdcard?!
What the shizzle, you are making it so hard for yourself.
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
EDIT: on a side note, it would seem you flashed the official gingerbread sbf, so now you will only be able to use the gingerbread kernel roms. Which is pretty much the cm9 alpha version, endless 7's cm7 defy port. Not really sure about the other gb rom (argen2stone, blurless etc). So make sure you read up on what you need and what will work
DreadPirateDan said:
...
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
...
Click to expand...
Click to collapse
Have you read all the posts?
My mistake was ti follow this guide.
And my way to install the app was, to copy it tio the sdcard because the method in the guid didn't work!
Milestone 2 Bricked
Hello friend, i am having the same problem then you...
It only show black screen and the led on the side of the usb cable and i also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable, as you and nothing...
Can you help me? please!
Do you have RSDLite? If yes, then RSDLite should detect your phone as it is already in bootloader mode (the black screen). You can flash an SBF at this point.
Download an appropriate one, if you were on Froyo then Froyo and in case you had upgraded to Gingerbread then download a GB SBF.
Flash the SBF. You would probably end up in a bootloop. Go to moto recovery, wipe data and boot. You should be good to go.
Edit: I believe that only GB sbf is gonna work for you as I suspect that you were somehow on GB and then tried to flash Froyo which led you to the black screen.
Long-time reader, first-time poster. And I think I just did something (maybe two somethings) galactically stupid...
Like a dozen times before, I rebooted my DroidX into recovery in preparation for (re)installing a custom MIUI ROM. Formatted /system, /data, and /cache, wiped Dalvik cache... and then proceeded to reformat my SD card. (WTF??) Stupid #1.
While still in recovery, I tried enabling USB storage from one of the menus, but my Win7 PC would never notice it was there. So I copied the ROM's zip file to the microSD manually by ejecting the card... which means I pulled the battery to get at the card. (Probably) Stupid #2.
So now I have a shell of a DroidX with "nothing" on it, and I don't have the first idea how to get it back to a working state.
When the phone reboots, it gets to the old MIUI boot animation and just sits there. About the only thing I can seemingly do with this phone is get to the bootloader screen (camera/volume down/power on). When I then connect it to my PC via the USB cable, the bootloader screen says "OK to Program. Transfer Mode: USB", but I can't (for example) get adb on my PC to recognize my phone (keep getting "error: device not found").
So am I FUBAR'ed, or is there a way out of my predicament?
Never mind... I actually remembered a way to get out of this myself...
I went back to the original method of rooting .621 ... Most importantly, I followed the steps to get a .604 build onto my phone from the bootloader prompt via a live CD. (I knew I had seen that before... it just took writing it down here to jog my memory...)
Anyway, I am now back to a functioning (and rooted) .621 build on my DX.
nice job dude!
Hello
During the new update (05/11 - cm10 - by quarx) I accidentally made a wipe/system and since then my defy+ doesn't turn on anymore. it stays in the google logotype forever and doesn't pass that.
yzakius said:
Hello
During the new update (05/11 - cm10 - by quarx) I accidentally made a wipe/system and since then my defy+ doesn't turn on anymore. it stays in the google logotype forever and doesn't pass that.
Click to expand...
Click to collapse
does it have a solution?
yzakius said:
does it have a solution?
Click to expand...
Click to collapse
pressing the up (volume) and volume, could enter the "boot loader" but I get a sign that the battery is low.
enter the bootloader and flash clean stock SBF rom via usb
rabe3ab said:
enter the bootloader and flash clean stock SBF rom via usb
Click to expand...
Click to collapse
You know one trick to bootloader using heindall?
don't use heindall or anything.
just connect the phone to pc and press power button + vol up to enter the bootloder, and flash SBF room using RSD Lite
As above but with more worries.
So I ALSO forgot to install a recovery after doing the TWRP->System wipe. However upon trying to restore the device over USB (RSDLite, Sideload, fastboot) I note that my computer doesn't discover the device.
"Drivers" I thought straight away, however I have MotoCast 2.0.31 installed and Motorola drivers from the Motorla Device Manager 2.3.9 installed.
So I investigated, when using Cyanogenmod Bootloader 2.1 and trying to Mount SD Card I get an error instead. Then it puts me back to the main menu, when I navigate back to the storage mounting page instead of being presented with Unmount I still get the same option to mount the sd card.
It looks like to me that the USB drivers for my Defy+ are knackered. Luckily I have a Defy knocking around somewhere and it appears I can still charge the Defy+ from the wall charger so I've got a plan of action but I really want to check with you guys first.
a) Get the files required for TWRP and CMod BL onto the SD card via the other Defy.
or
b) Find a way to restore the USB drivers on my Defy+ so I can use my PC.
Please tell me what you think?
I'm trying to restore a Defy that was hard-bricked by a failed installation of CM11. As I described in this post, the phone shows absolutely no signs of life; neither the screen nor the led light turn on at all, even though I've tried several different fully-charged batteries. The phone will not go into bootloader mode, even if I try to force it by holding power and volume+ while inserting the battery, so I cannot flash an sbf in RSD Lite.
@skeevydude and @TJKV suggested that I try using this sbf_flash tool in a Linux environment instead of using RSD Lite in Windows. I gave that a try, and unfortunately the phone still is not detected by the PC. Here's the output from sbf_flash:
Code:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ ./sbf_flash firmware.sbf
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
=== firmware.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF 4035 AP
01: CG31 0xB0280000-0xB02847FF 9A68 AP
02: CG32 0xC7A00000-0xC7A207FF 4805 AP
03: CG33 0xB2000000-0xB2DC07FF 8BAC AP
04: CG34 0xB0700000-0xB07047FF AB80 AP
05: CG35 0xB1000000-0xB17FFFFF 100C AP
06: CG39 0xB3300000-0xC79C07FF C7E6 AP
07: CG42 0xB0800000-0xB0842FFF 4BB7 AP
08: CG45 0xB0C00000-0xB0F007FF 738D AP
09: CG47 0xB1800000-0xB1FFFFFF 45F0 AP
10: CG53 0xB2F00000-0xB2F007FF FDFF AP
11: CG61 0xB0B00000-0xB0B7FFFF 4A7C AP
12: CG64 0xB0000000-0xB00047FF 85D0 AP
13: CG65 0xB0180000-0xB01847FF 2409 AP
>> waiting for phone:
It just stays on "waiting for phone" forever.
Here's how the brick happened:
After doing a clean install of @Quarx's February 2nd CM11 build (one of the "autobot" builds), I was no longer able to mount the sdcard, so I tried mounting it in TWRP, but that didn't work. I rebooted and tried again, still without success. Then I removed the original sd card and put in another sd card to see if that would mount. Still no. Then I tried partitioning the sdcard from TWRP. (I had read on some other forum that doing so might help TWRP to mount the sdcard.) When I tried to partition the sdcard, TWRP gave a "failed" message, and I later confirmed on my PC that the files on the sdcard had not been erased. After my attempt to partition the sdcard from TWRP, I was suddenly unable to mount any of the partitions! I powered off the phone (perhaps unwisely), and now it is completely dead: no led light, and nothing on the screen, no matter what I do.
I haven't been able to get the phone into bootloader mode, so I can't flash an sbf with RSD Lite in Windows, nor with sbf_flash in Linux.
When I type "lsusb" in the Linux terminal to see what usb devices are connected, the phone is not listed.
However, when I used USBDeview in Windows to see if anything shows up there, I found something interesting. When I try to force bootloader mode (by removing the battery, then replacing it while holding power and volume+), a device called "Motorola Flash Interface" shows up briefly in USBDeview, then disconnects after about a second. So maybe the phone isn't completely dead after all. Does anyone have any ideas how I can get it to stay connected to the PC (in either Windows or Linux) so I can flash an sbf?
Thanks in advance for any help.
The symptoms are similar to those which occur when internal eMMC flash memory is wiped from boot menu via a pc(I've seen this before). That however, does not help at all, since there is no fix for that
Anyways, try the factory cable once before you can use it as the most expensive paperweight you may come to own
Sent from my MB526 using Tapatalk
thekguy said:
The symptoms are similar to those which occur when internal eMMC flash memory is wiped from boot menu via a pc(I've seen this before). That however, does not help at all, since there is no fix for that
Click to expand...
Click to collapse
I was afraid of that. I suspect that TWRP wiped the internal memory instead of the sdcard.
Anyways, try the factory cable once before you can use it as the most expensive paperweight you may come to own
Click to expand...
Click to collapse
I always use the factory cable when flashing an sbf, but unfortunately that didn't help in this case. Thanks anyway for the suggestion.
Now, I'm sure that is a sign of some rather deep seated bug, but the thing is it has neither occurred on other devices, nor were the steps taken by you any different than the standard ones.
Your theory explains the outcome, but the thing is that partitions can't just "switch places", because even if such a corruption occurred, the locked boot loader should have kicked in on reboot, (probably) saving the device.
So how exactly it occurred, is quite a mystery, which lies somewhere on the eMMC chip:what:
Sent from my MB526 using Tapatalk
problem is old: Epsylon was done something like this when he try to change the partition. Result: maybe the ONLY way to hard brick the Defy.
pgreed said:
problem is old: Epsylon was done something like this when he try to change the partition. Result: maybe the ONLY way to hard brick the Defy.
Click to expand...
Click to collapse
Well, he certainly did not trigger eFuses or tamper with the partition table, atleast not by any of the steps taken. So, the diagnostics are similar, but the causes quite different
Sent from my MB526 using Tapatalk
Proverbs2 said:
I was afraid of that. I suspect that TWRP wiped the internal memory instead of the sdcard.
Click to expand...
Click to collapse
I think that is what happened: the way Linux device numbering works, when /dev(/block)/mmcblk0 doesn't exist (because your MMC card or chip was broken), /dev(/block)/mmcblk1 is never created, and becomes mmcblk0 instead. On the Defy, mmcblk0 is the external MMC card, and mmcblk1 is internal memory. TWRP probably never checked and repartitioned mmcblk0, which was your internal memory because the device it should have been never was created.
I've done something similar (tried to repartition /dev/block/mmcblk1), and thought I'd bricked my phone, but two things happened:
1. with the original cable connected to the charger, the white LED would flash for just an instant when connecting/disconnecting the charger
2. when connected to the USB port, mashing the up/down/power keys randomly for a while would eventually result in white-LED (but no screen) SBF-flashable mode. I suppose there's some sort of menu or code, but it's not as simple as holding up while pushing power.
It's recovered now and is running Quarx's CM11. Worth one last try before you give up on it entirely.
Please let me know if I've done something horribly wrong, this is my first post.
ETA: I can confirm that TWRP is misbehaving when no MMC card is inserted in the phone, though for obvious reasons I've stopped short of trying what you did (I've only got this one phone!) It's probably worth a bug report to the right people, though I'm not sure who that is.
+1 for misbehaving TWRP, however it did not mount any partition in my case, and so it was not possible to wipe anything. Not that I would have. Also, the "No OS found" message was triggered, probably because /system wasn't mounted
The difference between a fully wiped device and a partially wiped is the led, and the steady boot loader mode connection, which may or may not display any text on the device. Probably the only way to recover a fully wiped defy is JTAG(if interface exists)
Sent from my MB526 using Tapatalk
Hi
do you try to flash a mb526 sbf?
popov1100 said:
do you try to flash a mb526 sbf?
Click to expand...
Click to collapse
I can't flash any sbf at all, because it seems TWRP deleted the bootloader.
Proverbs2 said:
I can't flash any sbf at all, because it seems TWRP deleted the bootloader.
Click to expand...
Click to collapse
So , you can be happy :silly: .You are the first? one which have a unlocked bootloader on Defy. (sry for the silly)
Seems I am the second.
Today my defy suddenly can not boot into TWRP or andorid. After a sbf flash, I was following Quarx's site instruction of " from sbf to CM11 ", after a command though adb as root: cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p21 , defy got black screen and never responeded from there. No reaction on boot and plug in battery while holding vol+ and power. Still have not find a way to bring it back to life.
x.theme said:
Seems I am the second.
Today my defy suddenly can not boot into TWRP or andorid. After a sbf flash, I was following Quarx's site instruction of " from sbf to CM11 ", after a command though adb as root: cat /sdcard/bootstrap_ext3.img > /dev/block/mmcblk1p21 , defy got black screen and never responeded from there. No reaction on boot and plug in battery while holding vol+ and power. Still have not find a way to bring it back to life.
Click to expand...
Click to collapse
I'm very sorry to hear that. Maybe your battery is dead? You could try charging the battery with an external wall charger, or try the "McGyver" method to charge it.
Good luck!
Proverbs2 said:
I'm very sorry to hear that. Maybe your battery is dead? You could try charging the battery with an external wall charger, or try the "McGyver" method to charge it.
Good luck!
Click to expand...
Click to collapse
Tried both, still no luck, T_T
After the McGyver method, defy has white light on and black screen, can not get into bootloader, RSD still can not recognise anything...
Anyway, thanks for the tips!
x.theme said:
Tried both, still no luck, T_T
After the McGyver method, defy has white light on and black screen, can not get into bootloader, RSD still can not recognise anything...
Click to expand...
Click to collapse
Had the exact same unfortunate experience an hour ago, trying to update to CM11. Did someone found a method to bring the phone back to life ? Tried everything but seems that the command wiped the partition (though i don't know how or why...)
Here is the original thread :
http://forum.xda-developers.com/showpost.php?p=56228383&postcount=6049