Develop Bugs

[urgent help needed]. LG G3 bricked and stuck in download mode.

hi.
i have LG G3 d855 32 gb version. i was trying to upgrade it from kitkat but there wasnt any option in the settings, so i tried to do it by using flashtool method. now i downloaded the stock firmware by using my imei number which shows my device is for hongkong. so i downloaded the tot file as well as kdz file. when i tried to flash tot file i got an error after 6% and it said that "Partition Change Fa.. (failed maybe coz i cant read after that).. now the version installed on my device was "lgd855-v10m-ISR". i havent made any backup and phone is stuck in download mode. i'm completely lost now. any help would be appreciated.
Thanks in Advance

software info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Belalsuleman said:
hi.
i have LG G3 d855 32 gb version. i was trying to upgrade it from kitkat but there wasnt any option in the settings, so i tried to do it by using flashtool method. now i downloaded the stock firmware by using my imei number which shows my device is for hongkong. so i downloaded the tot file as well as kdz file. when i tried to flash tot file i got an error after 6% and it said that "Partition Change Fa.. (failed maybe coz i cant read after that).. now the version installed on my device was "lgd855-v10m-ISR". i havent made any backup and phone is stuck in download mode. i'm completely lost now. any help would be appreciated.
Thanks in Advance
Click to expand...
Click to collapse

It doesn't matter what your phone's imei is, all you need is to download the correct kdz files for your phone model. Try looking for a kdz for D855 instead of the imei. All you need is to flash the correct file for your phone model. You will never go wrong.

Problem: LG G3 d855 reboot after flashing official images (kdz)

Hi,
I used a long time CyanogenMod 12 and 13 with my LG G3 (d855). Suddenly some problems occurred. I flashed a lot of images and TWRP versions.
Last days I tried to flash wit the LG Tool 2014 original kdz images from LG.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried:
D85521C_00_1204 (21C).kdz
D85530C_00_0211 (30C).kdz
D85530F_00_0329 (30F).kdz and
Europe D85530B_00_1217 (30B).kdz.
Normally KingRoot and AutoRec worked fine. A short time. After using my phone a few minutes or hours i got bootloops and I had to flash again a clean official ROM. Sometimes I couldn't enter TWRP via buttons.
I think my phone has a hardware failure.
In the past few minutes I tried to flash the 30F image above. Android started regular and asked my which language I want to use. I scrolled down, selected German and the phone rebooted. Now I've a bootloop again. After a few seconds after flashing a original ROM.
Can you help me? Is the phone hardware bricked?
Best regards
Tim
Now I will try http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3

Katzenstreu said:
Hi,
I used a long time CyanogenMod 12 and 13 with my LG G3 (d855). Suddenly some problems occurred. I flashed a lot of images and TWRP versions.
Last days I tried to flash wit the LG Tool 2014 original kdz images from LG.
I tried:
D85521C_00_1204 (21C).kdz
D85530C_00_0211 (30C).kdz
D85530F_00_0329 (30F).kdz and
Europe D85530B_00_1217 (30B).kdz.
Normally KingRoot and AutoRec worked fine. A short time. After using my phone a few minutes or hours i got bootloops and I had to flash again a clean official ROM. Sometimes I couldn't enter TWRP via buttons.
I think my phone has a hardware failure.
In the past few minutes I tried to flash the 30F image above. Android started regular and asked my which language I want to use. I scrolled down, selected German and the phone rebooted. Now I've a bootloop again. After a few seconds after flashing a original ROM.
Can you help me? Is the phone hardware bricked?
Best regards
Tim
Edit 1:
Now I will try http://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
Click to expand...
Click to collapse
Edit 2:
Same Problem

https://youtu.be/6MlxVDFYpW0

Bricked OP3 - MD5 Checksum System: Failed

Hi All,
First off, this is what I did that led to this problem:
*** Beforehand, phone is unlocked, rooted, and updated to latest OTA OOS version (I think 3.2.7)
*** Unlock, recovery, root and NFS backup was implemented using this guide
*** OEM unlocking was turned off in the Developer Options
1. DPI was changed using the [email protected]_radaideh as recommended by some in Reddit -- this was OK
2. DPI was changed again using Le DPI Changer (found in play store), but used "EDIT BUILD.PROP" option
3. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
4. Booted into TWRP, and restored NFS backup (pre-root) and it was successful according to TWRP
5. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
Now after this moment, I tried Method 1 of the mega unbrick guide, but I encountered multiple md5 check failures upon boot. I then tried Method 2, and the md5 check failures were reduced to just one: system: failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can boot into fastboot, but I can't boot into recovery and system because of said error. Please help!

flash stock system.img

I already tried that using:
system.img from FULL unbrick tool -- doesn't work
system.img from 3.2.5 found somewhere here in XDA -- doesn't work
As mentioned above, the OOS version was at 3.2.7. I couldn't find it in the OP downloads site, but I did download the 3.2.6 image. That, however, did not contain any system.img.

did you find a solution

Try method 2 unbrick tool as per what they said, again. No other choice.

Hi, did you find a solution for this ? I have a similar issue and even after several flashes, i still have the failed md5 failure on system.img.

Resolved! Find device storage corrupted and Wifi does not work.

Do it at your own risk.
Share tutorial to help others.
This error happens because the ROM is not the correct one for the device;
Example:
PCAMIXM, OCACNXM, OCACNFK, OCAMIFH, and ETC.
If you remember what you were using before installing the rom that gave the problem just install again.
Example: I remember I was using PCAMIXM and installed OCACNXM.
Just go back to PCAMIXM.
If you do not remember you will have to test with existing, the correct rom will not display the message(Find device storage corrupted).
D̶o̶ ̶n̶o̶t̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶u̶p̶d̶a̶t̶e̶ ̶R̶O̶M̶ ̶b̶e̶c̶a̶u̶s̶e̶ ̶i̶t̶ ̶d̶o̶e̶s̶ ̶n̶o̶t̶ ̶w̶o̶r̶k̶!̶
Fastboot ROM only.
First set up the device even with the message: Find device storage corrupted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enable OEM Mode
Whebever you change ROM, enable this option first before writing the new ROM!!!
[*][font=ProximaNova, Arial, sans-serif]Unlock[/font] the boot, don't worry it will be locked again when we pass the ROM.
Please follow the steps below:
Step 1. Download Mi Unlock application on PC and sign in with your Mi account;
http://miuirom.xiaomi.com/rom/u1 ... k-en-3.5.910.35.zip
Step 2. Turn off the phone manually and hold down the Volume down key and the power button to enter fastboot mode;
Step 3. Connect your phone to the PC using the USB cable and click "Unlock".
There we have the boot unlocked.
Download the program:
XiaoMiFlash
Links to roms in fastboot mode;
V10.4.1.0.PCAMIXM:
https://bigota.d.miui.com/V10.4.1.0.PCAMIXM/sagit_global_images_V10.4.1.0.PCAMIXM_20190714.0000.00_9.0_global_dbd26e5a5e.tgz
V10.3.4.0.OCAMIXM:
https://bigota.d.miui.com/V10.3.4.0.OCAMIXM/sagit_global_images_V10.3.4.0.OCAMIXM_20190527.0000.00_8.0_global_cc4f15601b.tgz
V10.0.1.0.OCAMIFH:
https://bigota.d.miui.com/V10.0.1.0.OCAMIFH/sagit_global_images_V10.0.1.0.OCAMIFH_20180905.0000.00_8.0_global_7ce4be65b4.tgz
Extract the rom:
sagit_global_images_V10.4.1.0.PCAMIXM_20190714.0000.00_9.0_global (Do not leave subdirectories, only the folder without subfolders).
Open the program click select and select the extracted rom.[attachimg]4808252[/attachimg]
Then select the option: clean all and lock(This option is at the bottom of the program.).
Then click flash.
Wait for the process to finish...
If you get the lock state message go to next rom.
This message may also be displayed when OEM mode is disabled.
Or bootlocked, fix [font=ProximaNova, Arial, sans-serif][color=#0800]Unlock[/color][/font] the boot
Click to expand...
Click to collapse
After the flash is over you will have your cell phone working again.
Being able to repair my device like this, I can't guarantee it will work with everyone!
Hope it helps anyone who is experiencing this issues.
Here are other ROMS for other models.
MIUI Global ROM All Devices
Additional information:V10.4.2.0.PCAMIXM(Latest)
V10.4.1.0.PCAMIXM(Rolled back)
V10.3.4.0.OCAMIXM
V10.3.1.0.OCAMIXM(Rolled back)
Got any tips? post to help your friends.
Sorry for any mistakes, my time is short.
Good luck.

Help with bootloader blocked

Hello, I will use the Google translator because I am Brazilian
Today I ended up trying to install a custom rom on my moto g8, but it ended up giving some errors and I ended up blocking my bootloader manually, but now it doesn't start the phone and I can't install any stock rom with the bootloader blocked, all end up showing an error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

This website has instructions to flash stock firmware on Sofia. Everything but the link to download firmware should apply to Rav. https://www.droidwin.com/install-stock-firmware-on-motorola-g8-power-via-fastboot-commands/

Not because my bootloader is not unlocked

andr3ycarvalho said:
Not because my bootloader is not unlocked
Click to expand...
Click to collapse
A week ago I bricked my Moto g fast by attempting to flash RetUS firmware without unlocking the bootloader first. Even though most of the fastboot commands failed a handful succeeded and that was enough to prevent my phone from booting to anything but bootloader mode.
I downloaded and flashed the official Boost firmware from lolinet and while the flash succeeded my phone was still bricked.
I installed the Lenovo Motorola Rescue and Smart Assistant tool from https://support.lenovo.com/us/en/downloads/ds101291 and used it to download official firmware for my phone but the rescue tool failed at 14%.
I tried a few other things that also didn't help before I ran the LMSA rescue tool again. This time it took several minutes to complete and my phone worked again. I am not sure why it failed at first but happy to have a working phone again.

hello, i'm also brazilian and i have a problem similar to yours, after leaving a custom rom the other day, and reinstalling the stock and blocking the bootloader, my phone called with the message that it was corrupted and it wouldn't start and now i can only access his bootloader and I can't flash anything, not even the stock rom, I don't know how to solve it, but I'm in a situation similar to yours

Hello, I have a problem with my Moto G8 (XT 2045-1). I tried to install a stock rom to fix a bug, however the phone no longer connects in bootloader mode, nor does it unlock the same and I can't even install any stock rom. Can someone help me?