Database Users

[Q] Bricked Milestone2? Wont Charge/Stuck at M logo

So a couple days ago I installed MIUI to my phone. Everything went great, it booted successfully and worked for 2 days or so, until i accidentally let the battery die (not sure if this is related to the problem or not). Since this day, it wont charge or turn on while connected to the wall. When it is connected to the wall, it starts the screen and show a big battery with a question mark inside. I tried a friends battery and it gets stuck at the M logo. The only thing i can access now is the stock recovery screen. Any ideas on how to solve this? Thanks

viiniq said:
So a couple days ago I installed MIUI to my phone. Everything went great, it booted successfully and worked for 2 days or so, until i accidentally let the battery die (not sure if this is related to the problem or not). Since this day, it wont charge or turn on while connected to the wall. When it is connected to the wall, it starts the screen and show a big battery with a question mark inside. I tried a friends battery and it gets stuck at the M logo. The only thing i can access now is the stock recovery screen. Any ideas on how to solve this? Thanks
Click to expand...
Click to collapse
1.Download RSD Lite
2.Download the stock .sbf file for your device
3.Use your friends battery and boot into bootloader by holding Power+Volume Down+Camera button
4.Open RSD Lite, choose the .sbf file you downloaded, connect your phone to pc with usb cable and flash it.
If your pc doesn't reckognize your phone, you'll have to download and install the latest motorola milestone 2 usb drivers.

Ok. So i tried to apply the sbf file, but as soon as the process starts, RSDLite says under the status area "Phone[0000]:Creating Image File." and it wont get thru this. Any ideas?

Maybe try sbf_flash on linux?

Will the sbf_flash work the same on the mac? Or should they work differently on mac and linux? I tried it earlier today and i got stuck at some part i cant remember...I'll recharge the battery with a universal charger that i found (cause it's saying its too low to program) and try it again tomorrow, so i just wanna be sure that i can do it on the mac...
Thanks

It should work same way. OS X version is just port from the linux version.

You have to run RSDlite as an administrator. Right click on RSD.exe or RSDlite.exe not shure what's the exe file named and Run as administrator.
br Zola

having the same problem
after flashed MIUI/CM7
the battery died then the phone cant boot to desktop
tried RSD Lite, flash failed lol

Tried to run RSD as administrator. Still stuck at the same point.
Tried sbf_flash, stuck at 'waiting for phone:'.
I'll try to download the sbf file again, just in case it is corrupted.
Any other ideas?
PS.: I'm running rsd on VMWare, could this be the problem??

Dunno how exactly works USB bridge in VMWare, but rsd on pure (not virtualised) system is worth a try. Also - are you sure, your battery is charged? I know, that if your phone can't boot, the battery will not charge via USB - you should use universal charger or somebody here recommended (and successfully repaired MS2 this way) put contacts directly on the battery to charge it little (just for RSD flash).

I charged it on a charger that you put the battery directly into the contacts. I'm sure that it is charged cause 1) the led display on the charger says so and 2) when i get to bootloader mode to apply sbf, it says 'Battery OK / OK to program' , and before i charged it, it would say: "battery too low, cant program", or something like that.
I'll try to get a windows pc and try to apply the sbf

Thank you guys.
I was trying to flash it with a sbf that was on a pendrive. All i did was transfer the file to the HD and flashed it via RSDLite, using VMWare.
Now my phone is working again.
Thank you very much to everyone that helped me

ADB suicide

Hello developers,
A friend of mine was using a Huawei P10 Lite (WAS-LX1A). After an OTA Update errer, the phone was running quit ****. It was laggy af, Battery was nearly empty after a view hours and much more other bugs. I flashed my Huawei P7 multiple times (30-40 flashes) and my Galaxy SIII with LionageOS was also still working untill hardware crash becouse i dropped the Phone on the street. After installing ADB and Fastboot, i wrote down the Speccs of this phone to get an unlock code from tech support. Bootloader was successfully opend, and now, im lost. Huawei eRecovery show up "Download latest version and recovery". Using this method shows up an error "Unable to recieve Device information" or something like this. it seems i lost my ADB Access, "ADB Devices" seems empty and windows is playing a sound when Plugin/out the phone from USB. Currently im unable to handle this problem, i dont know where the problem is, it seems there is no system/OS running on the device. The phone is booting endless in two screens. The 1st one is the "Your phone can not be trusted" screen wich is the result of unlocked the boot loader. The 2nd screen is Huawei eRecovery what is useless, i only can reboot and shutdown. Recovering doesnt work.
What u also need to know: I lost the unlock code, speccs and other informations abbout this phone so bootloader is unlocked, hopefully this is no major problem.
This of has NO ROOT. Only opend bootloader and a bricked OS. There is no TWRP or other stuff installed!
Hopefully there is a way to install TWRP and a OS or maybe back to stock rom. I dont care wich one if the phone works again.

BlitzlichtHD said:
Hello developers,
A friend of mine was using a Huawei P10 Lite (WAS-LX1A). After an OTA Update errer, the phone was running quit ****. It was laggy af, Battery was nearly empty after a view hours and much more other bugs. I flashed my Huawei P7 multiple times (30-40 flashes) and my Galaxy SIII with LionageOS was also still working untill hardware crash becouse i dropped the Phone on the street. After installing ADB and Fastboot, i wrote down the Speccs of this phone to get an unlock code from tech support. Bootloader was successfully opend, and now, im lost. Huawei eRecovery show up "Download latest version and recovery". Using this method shows up an error "Unable to recieve Device information" or something like this. it seems i lost my ADB Access, "ADB Devices" seems empty and windows is playing a sound when Plugin/out the phone from USB. Currently im unable to handle this problem, i dont know where the problem is, it seems there is no system/OS running on the device. The phone is booting endless in two screens. The 1st one is the "Your phone can not be trusted" screen wich is the result of unlocked the boot loader. The 2nd screen is Huawei eRecovery what is useless, i only can reboot and shutdown. Recovering doesnt work.
What u also need to know: I lost the unlock code, speccs and other informations abbout this phone so bootloader is unlocked, hopefully this is no major problem.
This of has NO ROOT. Only opend bootloader and a bricked OS. There is no TWRP or other stuff installed!
Hopefully there is a way to install TWRP and a OS or maybe back to stock rom. I dont care wich one if the phone works again.
Click to expand...
Click to collapse
https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946 this method will lock your bootloader...

Ty so much, this solved my problem. phone is nearly new now.

Essential soft brick, any way to unlock flash from fastboot to sideload OTA?

Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!

Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.

Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin

I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.

Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB

justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you

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.

Bricked phone, won't turn on/fastboot/recovery

So yeah, I screw up by a lot, but let's see if someone can help me/
I tried to update twrp on my phone and it got bricked, ADB was not seeing the device but Mi FlashTool was with a code but not COM, tried changing the phone drivers brom 900E to QL8000 and it got registered by MiFlashtool as COM and another code, the phone was still showing there even if I could not make the phone go to fastboot mode, just blackscreen; I tried to reinstall stock rom with it but got stuck at "flashing", disconnected the phone, the phone was still bricked in a black screen, when trying to reconnect the phone again to the pc, Win10 now displays an error
https://imgur.com/a/VS1yh6t
,
https://imgur.com/a/4PxUD7E
, I already tried uninstalling the device, deleting and reinstalling the drivers (unable because for some reason they won't appear now, but already tried installing the from their 1st party and prom MiFlashTool), so the phone won't turn on, display anything, go into recovery/fastboot, and I don't know what to do now, is the phone lost? I hope you can help me with this issue.

Hello Bro. Try install latest Mi Flash Tool latest version and then install the drivers. For my it's works in windows 10.