Hi everyone,
I own an LGM700SDK and I've recently tried flashing stock ROM with LGUP, but on 11% it failed and I wiped the partition at the start of the process. Now it's stuck on fastboot mode.
Several things I've tried
Try to enter download mode by pressing vol up after LG Q6 is displayed after reboot with vol down + power > didn't work
Tried flashing with adb commands > didn't work, I always got 'remote command not found' which I suspect because the bootloader is locked/phone is unrooted
Previously managed to restore with LG Bridge but it was when download mode is working, now I'm stuck on fastboot and LG Bridge doesn't recognize the device
I'm getting desperate and planning to bring my phone to the nearest service center. I'd like to kindly request your help if there's anything I should try to fix it I would be ok with either restoring back the 8.1.0 version with LG Bridge through download mode or flashing the stock rom
Looking forward to your responses, thank you
Related
Hey All,
My Dad's Xoom died over the weekend - 13months after purchase so is not covered by the warranty. He was browsing a site, it came up with a "Internet is not responding - do you want to continue to wait" message and he clicked Wait - after a second the tablet knocked off. It will not come on by pressing Power and only turns on by pressing Power and Vol +
It gets past the Motorolo logo screen and the device starts the boot animation, about 20 seconds into this it freezes and reboots - this continues in a loop. It's been GEDified and was running the last OTA update 4.1.2 - no root etc.
I can get into the stock recovery and performed a factory reset - but the same thing happens. I've also tried Update From USB with an OTG cable but the screen just shows Choose a package to install and under it has /sdcard but nothing else. I have a dummy zip on both the Flash disk and SD card so it's not reading either.
I've also tried to perform update via ADB - when I select it and connect to a PC (Win 7 32bit) it tries to install drivers but I see In Computer Management that it shows under Unknown. ADB Devices returns List of devices message but nothing under it.
I've also selected the fastboot command at boot, tried fastboot devices and the command does see the Xoom.
So my questions
1) Anyone seen anything like this issue before and know how to fix it?
2) Is it best to try to reinstall the ROM? If so, how do you suggest I can see it with ADB?
3) As I have Fastboot command, could I try to install CWM and see if that sees a ZIP on the sdcard - so I can install a new ROM.
Any help much appreciated :good:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
claned said:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
Click to expand...
Click to collapse
So just to add to this, I found the stock recovery.img, boot.img, userdata.img and system.img and used the fastboot commands to send all to the motorola - all succeeded without error....still the same problem though.
I installed RSD lite and tried a few SBF files but I'm getting an INI error - off to google possible solutions to that now
What can I do to unbrick it?
The boot loop is because I tired to fix gps with this method:
"Actually... after rooting it, go to System folder and edit Build.prop (read-only!) and add a line in the end of the file to look like this:
dalvik.vm.stack-trace-file=/data/anr/traces.txt (already exists)
dalvik.vm.execution-mode=int:fast (the line to add)"
And the result is boot loop .
I can do hard reset but nothing happened.
I can go to fastboot.
I can't flash it with LG flash tools.
Please help me.
Bumping this thread. I've got LG L Bello d331 and I bricked it trying to update it to lollipop manually. It got got stuck on the beggining of the update and I removed the USB cable. Since then the phone goes only on fastboot mode and nothing else.
Does anybody have a clue on how to resolve this issue? Any way I can flash a rom through fastboot mode?
hliasant said:
Bumping this thread. I've got LG L Bello d331 and I bricked it trying to update it to lollipop manually. It got got stuck on the beggining of the update and I removed the USB cable. Since then the phone goes only on fastboot mode and nothing else.
Does anybody have a clue on how to resolve this issue? Any way I can flash a rom through fastboot mode?
Click to expand...
Click to collapse
Maybe you can try to format userdata and cache via the fastboot command:
Code:
fastboot -w
Try this at your own risk. Your data will be lost after that.
source:
http://androidforums.com/threads/list-of-fastboot-command.714676/
i have the same problme
i can't enter in download mode
just enter in fastboot mode
Did anybody find solution?? I recently bricked my lg belo d331, only can access fastboot
cuic_cro said:
Did anybody find solution?? I recently bricked my lg belo d331, only can access fastboot
Click to expand...
Click to collapse
do you have tried this?
phone without battery (reinsert batt when beep its heard), press vol down or vol up wile connecting to pc, now look for device manager: have mtk usb port in com devices? if yes you have a hard bricked d331 (like me)
if not: you have unknow device (need install mtk drivers)
if not 2: you have a preloader mtk, in this situation you can use a Lg flash tool in fastboot mode for upload firmware kdz
I have messed up my lg volt it was on the stock rom zv5 and was running fine with root. I decided to flashify a deodexed version of my rom onto my phone, this of course went wrong as all my phone displays is the Lg boot animation with Fastboot in the top right corner i cant enter recovery mode as I have a bad recovery. I can open up the adb sideloader within Android System Recovery but have no idea how to get it to work as my command prompt does not recognize the command. I have tried a factory reset and rebooting. Help please I am getting desperate. FYI I am 14 and my knowledge on flashing is minimal.
XDA Visitor said:
I have messed up my lg volt it was on the stock rom zv5 and was running fine with root. I decided to flashify a deodexed version of my rom onto my phone, this of course went wrong as all my phone displays is the Lg boot animation with Fastboot in the top right corner i cant enter recovery mode as I have a bad recovery. I can open up the adb sideloader within Android System Recovery but have no idea how to get it to work as my command prompt does not recognize the command. I have tried a factory reset and rebooting. Help please I am getting desperate. FYI I am 14 and my knowledge on flashing is minimal.
Click to expand...
Click to collapse
Hello, and welcome to XDA! You could try to adb sideload a rom and flash it. Or fastboot flash a working recovery onto your device, and then sideload a rom and flash it. Or you may have to reflash stock firmware onto your device to get it to work. Here is a guide as to how to flash roms: http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android. To sideload, the command is simply "adb sideload name of file" without the quotation marks. For further help regarding your problem, you can register and post your questions in the XDA help forum: http://forum.xda-developers.com/general/help.
Good luck!
Good morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
jwoegerbauer said:
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
Click to expand...
Click to collapse
I see.
What can I do to try to fix this issue?
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.
I tried installing the pixel experience rom and after I flashed the aex recovery before side loading the ROM, it went into bootloop and ended up with the stock recovery and ROM. I tried to flash TWRP recovery and go a message that the the boot/recovery image is destroyed so I tried to flash the stock boot image back and since then I am not able to get it out of fastboot mode.
I tried everything, flashing the recovery again, both stock and TWRP and also tried using the flash-all to flash the stock ROM back but nothing seems to be working.
When using the flash-all, I get 'partitions not found' and 'flashing is not allowed in critical partitions' error.
I even tried msmtool but I am not able to get my phone into edl mode for the tool to detect it.
Tried holding the vol+/vol- and connecting the usb cable but to no vain, the tool does not seem to detect it.
I even tried using the all-in-one tool but my phone is not getting detected when it is turned off but it gets detected when it's in flashboot mode from where I cannot enter edl.
Let me know if there is anything I can do to fix it? Or if taking the phone to the official service center help?
Can you reboot from fastboot to edl by entering fastboot reboot-edl? Or similar, don't know exactly anymore
Alternatively see if this can help you getting into edl: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/