Database Develop

MihanickX's method of emergency flashing

This is a translation of MihanickX's post
Code:
h*tp://4pda.ru/forum/index.php?s=&showtopic=191005&view=findpost&p=5306386
It seems that some people were able to revive their phones using it, so it might be useful.
---
This will fix no boot logo problem after 2.1 update (maybe this method will also help to restore "dead" phones):
1. Install LG_Android_Driver Ver 1.0
Code:
h*tp://files.gameworld.kz/c5z46n1ukk.html
2. Download and extract KDZ_FW_UPD flasher
Code:
h*tp://forum.xda-developers.com/showthread.php?p=8655201
3. Download ROM (.kdz file) and place it in the flasher folder. You can find some ROMS in this thread:
Code:
h*tp://forum.xda-developers.com/showthread.php?t=802895
4. Press "volume down" key on the phone and connect usb cable.
5. Open Windows Device Manager and disable LGE Android USB Modem in device manager.
{
"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"
}
6. Run "KDZ_FW_UPD.exe" (run it as administrator if you are using Windows Vista/7).
7. Set "Type" to "3GQCT" and open your firmware file.
8. Set "PhoneMode" to "CS_EMERGENCY".
Some information about phones modes:
DIAG - standard flashing mode for phones which are turned on.
EMERGENCY - mode for flashing phones in Emergency (Download) Mode.
CS_EMERGENCY - same thing, but appears to be for non-working phones.
9. Press "Launch software update" to start update.
10. As soon as your phone turns off with sound and animation in the screen you can disconnect it (or continue waiting, but you only will get an error):
11. Now turn on the phone and do a hard reset (On the lock screen simultaneously press and hold the volume up, home and search buttons. After several seconds you will see hard reset dialog). If you want, you can now flash using "DIAG" mode.

Thanks a lot, very useful.

Thanks for this wonderful tip

i followed your guide and i get the LG screen (second one) and it just hangs there.
Any ideas?

Same problem....

[Solved] Help with TWRP and VENDOR

Hello, I am a owner of a ZUK Z2 Pro from Brazil, apologies for my english.
I tried to update the mooke rom to pie, but it wasn't working via central mooke, so I downloaded and tried to flash on TWRP, but I was possesed by a demon and instead of not deleting the internal storage, I delete all files. The problem now is that the mobile isn't reconigze in the computer and the device manager shows this:
{
"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"
}
The USBView show this:
Maybe it's something related to the vendor folder that can't be mount on TRWP. I tried adb push, but don't display my device and I don't have acess to allow the usb debugging. I tried USB OTG, but the pendrive is unrecognized. I don't know what to do anymore, but I don't think the mobile is bricked. May day may day!

In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.

craftandbuild said:
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
Click to expand...
Click to collapse
I can't mount otg because twrp don't let me selected the option, I had install all drivers I found of zuk, lenovo and qualcomm and still unrecognizable on the computer, therefore I can flash stock or the vendor image/backup, the version of my twrp is the 3.3.0.0, the most updated. You know if there is a way to force the computer to recognize the device?

Solved doind this.

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"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"
}

Please help me

{
"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"
}

Which Recovery do you use?

Bardia777 said:
Which Recovery do you use?
Click to expand...
Click to collapse
looking at the photo, it seems to be orangefox recovery

FRP_OFFICIAL said:
View attachment 5189173
Click to expand...
Click to collapse
Its look like mounting problem try googeling for How to fix mounting problem(maybe show you the twrp but thats okay its same for all devices)

The easiest solution for this error is to force Windows to re-arrange its ordering of the drives. When you get this error message, it is possible to work around it easily without having to use disk part or manually re-partition your disks and drives:
Upon seeing the error message “Setup was unable to create a new system partition or locate an existing system partition,” remove your Windows setup USB from the PC (don’t worry, this is safe since no read or write operations are being made from the USB disk).
Press the red “X” button to exit the installation wizard. You will be asked to confirm that you’re sure you want to do this and that Windows will not be installed if you do. Press OK and exit anyway. You won’t actually leave the setup environment, you’ll just be taken back to the main page.
Back at the main setup page, select “Install Now” without re-inserting your USB stick.
You’ll see an error about Windows being unable to locate setup files, and asking you to load a CD/DVD driver for Windows setup to
Click “OK” then exit the setup dialog once more to return to the main setup screen.
Re-insert your USB at this point, then select “Install Now” again.
This time, everything should go as planned since Windows has been forced to recognize that the setup USB is a removable drive, and it can identify the correct boot drive to install the Windows boot files to.

Flashing stock rom RQ3A.211001.001 on Redfin device using Android Flash Tool partial progress, fails to fastbootd when entering flashboot userspace

{
"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 previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!

brian_says_yas said:
View attachment 5517961
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
Click to expand...
Click to collapse
Hi Brian, have you tried a different usb cable? I only use windows so I can help more if you get a windows PC or run windows from a usb. I also unlock the bootloader manually with the ADB tools, first before using the flash tool.

So I switched to a macbook and a different USB cable both at the same time, and it worked. I'm speechless lol. Thank you for your help! Honestly the biggest benefit here is that I don't have to use Android 12 yet which was buggy as hell on my Pixel 6 Pro before someone did me the favor of stealing it in Miami.