Related
So on a wild hair i decided to try out the latest official firmware. Stupid i know.
Now when i SBF back to the old firmware as stated in the cyanogenmod full update guide, root and bootstrap i can get into CWM recovery but no matter what rom i use it just bootloops. Then if i try to go back into CWM i of course find its the stock 3e recovery.
Did i perma-bork my phone from having custom roms or is there a problem between the chair and monitor? lol
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
marculous said:
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
Click to expand...
Click to collapse
Yeah, after I got the first bootloop I tried with apex and liberty and on each attempt wiped data and cache 3x
wipe data and cache, factory reset, then sbf? idk, I've been where you are many times and i always have to go back to the guides to get the process right, in the correct order.
DX .605 ROOT
So is there no reason that the newest OTA* would ruin the ability to put custom roms on?
i wouldn't think so, but i know for cm7 to get on my phone i had to sbf back to 2.2 from the. 596 i was on. guess it depends on the rom. me personally, i just left cm7 for. 605, rooted because i like the blur camera and hdmi support. took off most of the bloat but not all, it jacked up my contacts.
DX .605 ROOT
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
can you sbf back to an earlier version?
DX .605 ROOT
Yes I can go back to the froyo SBF without any problem. The issue is, once i do that, then repeat the steps and flash a custom rom, no matter what rom i use, i get a bootloop. the stock SBF and OTA work fine, its just once a custom rom is installed.
spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
hootowlserenade said:
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
Click to expand...
Click to collapse
No, it bootloops at the M Logo screen.
the M logo comes up for like 2 seconds, then the phone reboots.
The only variance to this is when i flash the AIO APEX rom, then it just sits at the google logo indefinitely. But on any other rom including Cyanogenmod and Libery it bootloops at the "M" Logo.
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
infazzdar said:
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
^This werk'd! I owe you vigorous oral.
spockmeat said:
^This werk'd! I owe you vigorous oral.
Click to expand...
Click to collapse
wow...........
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck
Exactly the same problem here, cannot downgrade to CM7.
Any good news?
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?
llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.
It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.
That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense
I've done the following to my new, out-of-the-box Droid Razr M (XT907):
- Rooted it
- Unlocked the bootloader
- Installed CWM recovery
Booted into the CWM recovery mode, I cleared the memory, cache, and while trying to flash an Eclipse JellyBean custom ROM, the process failed (alas, I didn't capture the error msg, but I recall it being a bit vague). I (perhaps foolishly) rebooted using the CWM menu after this failure. Since then, the phone has been stuck in the "WARNING BOOTLOADER UNLOCKED" screen (scrshot attached). I'm able to enter the AP FastBoot mode using Power+VolumeDown, but trying to flash a stock ICS ROM using RSD is failing as well.
I'm kinda stuck at this point, and would highly appreciate any useful advice. The AP FastBoot screen says "Battery Low!" so I'm not really sure how much time I have. I've kept it connected to my PC via USB, but I'm not sure if that charges the battery or not.
Thanks much!
l_klusener said:
I'm kinda stuck at this point, and would highly appreciate any useful advice.
Thanks much!
Click to expand...
Click to collapse
To bo clear, I'd like to take the phone from its current state to _some_ working state, whether it's by flashing a custom ROM or by unrooting it and taking it back to a factory state (assuming that's even possible), so that I can fully charge it and then make another attempt of flashing a custom ROM onto it.
Thanks!
If I were you, I would download RSD, boot the phone into Fastboot AP, and flash the 4.1.1 stock image. If you download the Razr M Utility 1.10, it will have both RSD, the motorola drivers, and the stock image. It can be found here: http://forum.xda-developers.com/showthread.php?t=2207419
NOTE: Your battery should be at 100% for the flash according to the original post in that topic. I would leave it attached to the computer for a few hours or put it on the wall charger for a few hours before going any further.
l_klusener said:
To bo clear, I'd like to take the phone from its current state to _some_ working state, whether it's by flashing a custom ROM or by unrooting it and taking it back to a factory state (assuming that's even possible), so that I can fully charge it and then make another attempt of flashing a custom ROM onto it.
Thanks!
Click to expand...
Click to collapse
You could also flash cm10, either would work. Cm10 would bypass the issue of undoing your custom recovery
Sent from my XT907 using Tapatalk 2
l_klusener said:
I've done the following to my new, out-of-the-box Droid Razr M (XT907):
- Rooted it
- Unlocked the bootloader
- Installed CWM recovery
Booted into the CWM recovery mode, I cleared the memory, cache, and while trying to flash an Eclipse JellyBean custom ROM, the process failed (alas, I didn't capture the error msg, but I recall it being a bit vague). I (perhaps foolishly) rebooted using the CWM menu after this failure. Since then, the phone has been stuck in the "WARNING BOOTLOADER UNLOCKED" screen (scrshot attached). I'm able to enter the AP FastBoot mode using Power+VolumeDown, but trying to flash a stock ICS ROM using RSD is failing as well.
I'm kinda stuck at this point, and would highly appreciate any useful advice. The AP FastBoot screen says "Battery Low!" so I'm not really sure how much time I have. I've kept it connected to my PC via USB, but I'm not sure if that charges the battery or not.
Thanks much!
Click to expand...
Click to collapse
did you mount system before you flashed?
I think the Razr M Utility 1.10 can save your phone, it flash the stock rom by fastboot, not by RSD, and it will do the work. I've try it.
Coronado is dead said:
If I were you, I would download RSD, boot the phone into Fastboot AP, and flash the 4.1.1 stock image. If you download the Razr M Utility 1.10, it will have both RSD, the motorola drivers, and the stock image. It can be found here: http://forum.xda-developers.com/showthread.php?t=2207419
NOTE: Your battery should be at 100% for the flash according to the original post in that topic. I would leave it attached to the computer for a few hours or put it on the wall charger for a few hours before going any further.
Click to expand...
Click to collapse
Apologies for the delayed response here.
I followed these instructions, and it worked wonderfully. My phone is now restored to the stock image, so a huge thanks there!
shane1 said:
did you mount system before you flashed?
Click to expand...
Click to collapse
Are you referring to my attempt at flashing the custom ROM? I don't think I mounted anything. I copied the custom ROM .zip file onto the phone's SD card, booted into the CWM recovery mode, wiped out the data, cache, and dalvik cache. I then selected the "Install zip from SD card" option followed by selecting the zip I copied earlier.
Did I miss an important step here? The instructions I followed were from an external (i.e., non xda-developers) site. I'll try to look for better instructions on this forum, but if you have a pointer handy, I'd appreciate it.
Once again, thanks for saving my phone guys. I was beginning to lose hope
So I'm trying to fix a friend's Droid X that all of a sudden stopped working. I know that he didn't brick it by attempting to root it because he's not that tech-savvy. I can get into the "Android system recovery (3e)" but the only choices are reboot system now, apply sdcard/update.zip, wipe data/factory reset and wipe cache partition. There's no option to go into the sd card to look for files to flash (which I'm guessing is only available once you root.
Is there anything I can do to save this? Or is it broken beyond measure?
Also, I get into recovery mode by just turning it on, waiting for it to get to triangle exclamation point icon with the android figure and then pressing the search button. It's not responsive to any other way of getting into recovery.
can't flash anything in android recovery, on a motorola with a locked bootloader
you can try flashing a sbf in bootloader mode with rsd lite
links in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk 2
Thanks, I'll give it a shot when I get the time and let you know how it goes.
Sent from my XE Sero ROM'ed S7 with XDA premium HD app
if the search button, opens recovery, it's only running froyo android 2.2
not that it matters much, but if it was running gingerbread 2.3.x, you need to press both volume buttons to open recovery
did you try wiping data or cache?
or try Safe Mode - DROID X
sbf links
Droid X SBF Files
Using RSD Lite to flash a .SBF to restore (Stock Rom)
or
DX ezSBF
Hi guys,
I have a Milestone 2 running unofficial JB 4.3 (chinese version), and I tried to flash the file CWM 6 Recovery (.zip) via recovery. The recovery original of this rom is Android system recovery <3e>. Now when I start the device stuck in a bootloop. I don´t know what to do, and my desktop don´t recognize my device, despite all new motorola drivers installed, is impossible to make any update via RSD Lite.
I need help, any suggestion?
when you say that your desktop doesn't recognize the phone, did you put it in flash mode then?
you have to press the up button on the keyboard and the power button together to enter that mode. the phone should show you the bootloader version and some other stuff.
now you can connect it to your desktop computer and it should show as motorola flash interface in the device manager. then you can flash with rsdlite.
that said I had to do the whole procedure recently aswell. on my primary workstation rsdlite didn't recognize my ms2 at all (despite having proper drivers installed and despite it showing correctly in the device manager). so I tried it with a windows xp vm on my macbook pro and there it did work.
503e2 said:
when you say that your desktop doesn't recognize the phone, did you put it in flash mode then?
you have to press the up button on the keyboard and the power button together to enter that mode. the phone should show you the bootloader version and some other stuff.
now you can connect it to your desktop computer and it should show as motorola flash interface in the device manager. then you can flash with rsdlite.
that said I had to do the whole procedure recently aswell. on my primary workstation rsdlite didn't recognize my ms2 at all (despite having proper drivers installed and despite it showing correctly in the device manager). so I tried it with a windows xp vm on my macbook pro and there it did work.
Click to expand...
Click to collapse
No, I don´t do that, I put in the recovery mode only. I didn´t know how to enter in bootloader, now I know that, thnks! :good:
Is wrong and risky flash the cwm6 via recovery, the right is always flash via RSD Lite right?
Supposing, through this procedure that you recommend me and the RSD Lite recognizing my device...
What file I flash to solve the problem?
you can download a sbf for your phone (depending on your region) from here: sbf.droid-developers.org/umts_milestone2/list.php
after you flashed the sbf you have to boot into recovery and wipe data.
you will be back to a factory reset stock rom after that!
it might be possible to rescue your current rom/data but with that I can't help you. I don't know how to get cwm6 either.
the way I went was: gingerbread stock via rsdlite -> CM10 from tezet via the method described by tezet -> CM10.2 from Engle_Mars via the cwm recovery from tezets CM10 rom
503e2 said:
you can download a sbf for your phone (depending on your region) from here: sbf.droid-developers.org/umts_milestone2/list.php
after you flashed the sbf you have to boot into recovery and wipe data.
you will be back to a factory reset stock rom after that!
it might be possible to rescue your current rom/data but with that I can't help you. I don't know how to get cwm6 either.
the way I went was: gingerbread stock via rsdlite -> CM10 from tezet via the method described by tezet -> CM10.2 from Engle_Mars via the cwm recovery from tezets CM10 rom
Click to expand...
Click to collapse
Now, before I did the procedure to flash the rom, I start the Milestone 2 in the Bootloader mode as
recommended you.I noticed the battery´s device is discharched, and I don´t have other battery to replace.
Remembering my recovery don´t have any battery charge options.
There is one way to charge the battery or solution, without use the recovery mode or buy another battery?
mah9800 said:
Now, before I did the procedure to flash the rom, I start the Milestone 2 in the Bootloader mode as
recommended you.I noticed the battery´s device is discharched, and I don´t have other battery to replace.
Remembering my recovery don´t have any battery charge options.
There is one way to charge the battery or solution, without use the recovery mode or buy another battery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=892026
Only do this for a short period of time, else your battery could damage.
Flash something, then wipe data in stock recovery, and try to boot your device.
Good luck
mah9800 said:
Now, before I did the procedure to flash the rom, I start the Milestone 2 in the Bootloader mode as
recommended you.I noticed the battery´s device is discharched, and I don´t have other battery to replace.
Remembering my recovery don´t have any battery charge options.
There is one way to charge the battery or solution, without use the recovery mode or buy another battery?
Click to expand...
Click to collapse
Try to get a universal battery charger.
Lean946 said:
http://forum.xda-developers.com/showthread.php?t=892026
Only do this for a short period of time, else your battery could damage.
Flash something, then wipe data in stock recovery, and try to boot your device.
Good luck
Click to expand...
Click to collapse
Thanks a lot dude, I´ll try it!