I think i just bricked - Bravo General

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

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] Really could do with some help from those with experience... Please.

Hi Guys,
I am a noob to xda so please bear with me...
Hoping someone can help me out here.. I will try and explain in as much detail as possible and provide you with as much Info from my phone as I can.
Firstly my phones details
Motorola Atrix 4g (UK version) Second phone as busted the last one. Bought outright as a retail sale.
Orange UK
System Version: 45.31.0.MB860.Retail.en.GB
Android Version: 2.3.4 (After UK released update)
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0.133_38
Kernel Version: 2.66.32.9 [email protected]#2
Ok so, decided to root my phone. To do so I used petesMotorolaRootTools_V1.07 found on the website psouza4.com/bionic/
This worked fine and an app installed from the App Market confirmed that the phone was Rooted and had Superuser permissions.
Next I downloaded ClockWorkMod Rom Manager from the Market Inc Premium, SetCPU, Rom Toolbox & Titanium Backup Free. I had a quick look at these apps once downloaded but didnt really do a lot,
However, when Rom Manager opened it promted me to Flash ClockWorkMod Recovery, Which I did and then selected Back up current Rom. I also did this, (bear with me it gets a little vague here as to what I remember seeing)
Now I'm sure it said something like Nandroid Backup, which I selected. It proceeded to say something along the lines of, Backing up or phone will now reboot??
Anyhow, what ever it said, it started to reboot. The Motorola Red Circle logo came up but then at the top it said reboot failed and something ilse that didnt make sense then froze. I pulled the battery and rebooted. Seemed to work fine. Maybe a touch laggy but nothing to bad.
Next did my research into what ROM I'm likely to want to try. Found a few but seemed from what I have read on various forums that they dont work well for uk phones. Then decided perhaps then flashing should be left alone and went back to PetesMotorolaTools and unrooted. before I unrooted however i removed all apps that required root access first. Possibly a mistake?
I noticed that a few preinstalled apps werent working, nothing important or anything I use but there icons were like Blue settings icons all the same.
Did a factory reset through the handset also, in an attempt to return to factory settings.. not much changed really. Also tried to update software though the Motorola website but it said I was all up to date.
I thought maybe that something went wrong so I rooted again. This time the unroot failed. I then dowloaded all the rooted apps that I had before and then unrooted. This worked. Not sure if coincedence or not but it worked and when unrooting it said unfreezing apps about 6 times, before the complete message. Then uninstalled the root apps again.
Most, not all but most of those preinstalled apps were then working ok.
I read a little bit more bout Roms and decided to have another bash. Found and downloaded a few to comp. Then I place an SD card into phone and Flashed it. then tranferred a copy to its root.
Rooted the phone in the same way as before. Downloaded all the apps again opened CWM RM, Flashed CWM Recovery again as was unsure that the time I did it before would work. Then selected back up Current ROM. Without any message this time the phone started to reboot.
It came up with the recovery screen (Android man and !) From what I have read the next step is to tap the bottom right of the screen to bring up the menu.
This did not work nor did anything else happen. After waiting about 25mins with nothing more happening I pulled the batt again.
Decided I'd boot into recovery mode manually and see if the bottom right of screen would work that way. turned off then held On and down Vol. Fastboot showed at top, Scrolled and selected Android recovery. Same Android Man and ! came up, tried tapping the bottom right of screen again.... It didnt work.
Read more on the forums where someone said that pushing up and down on the Vol buttons works. Tried this and hey presto.. a new menu appears. Shown as follows.
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
No back up options so rebooted....
Anyway thought I'd try a few times to use CWM RM to flash a rom to device. Each time it took me throught this same process.
Eventually I though what the hec just try and flash it...
So I selected the apply update from sdcard option.
Then selected the ROM I saved to SD Card.
Then the following text appears on screen in yellow.
--Install /sdcard...
finding update package...
Openeing update package...
Verifying update package...
E:signature verification failed
Installation abborted
I tried this a few times to no avail. even tried downloading the roms from CWM RM with no change.
Read some more on the forums and somewhere read to rename the ROM update.zip
Did this and tried again.... No Joy!!!
Selected Fix permissions in an attempt to clean up and thats as far as I have got...
I'm at the end of my tether and dont know what to do...
Please, please, please someone help me get to the bottom of my dilemma..
Thanks for reading and any help in advance.
Just a little more info to help diagnose
CWM RM Details
Rom Manager Premium v4.8.1.3
Current Recovery: ClockworkMod 5.0.2.0
Latest Recover;ClockworkMod 5.0.2.0
Thanks again peoples for taking the time to at least read this..
No where in there did I see "I unlocked my bootloader"
That's fine that you're rooted, but to use CWM Recovery, install ROMs, make Nandroid Backups, etc. you need to unlock your bootloader first! See the international part of the Pudding thread (since your in UK) in the dev section.
Sent from my CM7 Atrix 4G
Ah Hah! You are correct at no point did I unlock my Booty, Thank you I shall give that a go and report back...
Ok so, I have trawled the forum and many others this avo on my research quest to unlock the bootloader as advised above but have been unsucessful so far.
I used the Pudding thread as you said.
when downloading the files advised I noticed that some were downloading as unrecognised files. I still proceeded to follow instructions as written.
Some of them like the RSD Lite I managed to unzip and extract with a programme I have however the next one needed said it was Undefined File type.
Anyway I deleted those files and tried following the other method listed underneath the driver via the link at "Guide for beginners provided by..."
This was unsucessfull as the "fastboot oem unlock" command was not recognised.
Pulled the batt and rebooted into normal mode and I'm back at SQ1
Bit stuck if anyone has any ideas..
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Dcskeete said:
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You should definatly also install busybox
Swiftks said:
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Click to expand...
Click to collapse
A BIG THANKS!!!
Thanks so much for the advice and instructions... Unlocked beautifully... Now to find the ideal ROM....
Dont suppose there are any suggestions for International (UK) Atrix users??
Really appriciate the help..
Regards
Danny
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Im not sure, maybe someone else can confirm. You should be using moto-fastboot to unlock & not regular fastboot, right?
Sent from my MB860 using xda premium
draken_1337 said:
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Click to expand...
Click to collapse
People have had problems with TWRP.............stick with Romracers CWM, it's tried and trusted. If the touch screen in CWM gets you off, so be it, but I'd rather have a recovery that works with all ROM's, and not just some.

[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?

Fatal Wipe/System [help]

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?

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

Categories

Resources