[Q] Milestone 2 won´t turn on after a failed attemptive of ROM installation - Milestone 2 General

I tried to install a room with the Android Boostrap 2 help, since I was getting nothing from the regular recovery manager.
Well, Everything was going ok at the installation moment, but then something went wrong (didn´t find some file (and I was stupid enough to NOT write the file name down)) and aborted the installation of the room. So, I tried to do the regular boot and TA-DA! I´m stuck in the Motorola logo and the phone won´t turn on. Anything I can do from my PC with the USB cable? Or using the device itself?
Thank you.

http://forum.xda-developers.com/showthread.php?t=1032372
Have fun with this guide.

Get to Bootloader Mode (Power + Volume Up + Camera) and flash a SBF with RSD Lite 4.9+ (google it, or in the forum)
http://www.and-developers.com/sbf:milestone2

good!
Thank both of you!
Really worked SUPER-mEGA-HYPER-NICE =D

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] Milestone 2 Bricked! Help Me

Hi,
I'm trying to install a Droid 2 Rom (Liberty) on my Milestone, because i thook that was the same phone.
After install it, the phone load the logo (Liberty) and then became black.
There is a solution?
I've tried to apply the sbf file throught the RDS, but it don't find the phone.
HELP ME please
PS. Sorry for my bad english
Can you boot the phone into recovery mode?
I don't know the combination... Do you know it?
Thank You
Shut down the phone and turn it on again with pressing Power + "Up-Arrow" for something like 10 seconds, phone should be in Bootloader Mode then and be found by RSD Lite.
i've just done it. The problem is that the pc (Win 7) don't install the driver...
Any solution?
Goto the Motorola.com website and download the latest USB drivers.
EDIT: here you go http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.8.0.exe

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

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.

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