Do you want to bootloader and unlock and root your V35? Do you want to do this yourself? Are you feeling the need for some adventure? If you answered yes to these questions, then you are at the right place. The goal with these instructions is to make the process as smooth and pain-free as possible. These instructions are based upon what I know works through firsthand experience and what I have gathered reading. My experience is with an AT&T branded V350AWM. Others also report success. That said, there can still be problems leading to bricked phone so don’t continue if you are not comfortable with the risk. An unavoidable side-effect of bootloader unlocking is that all data on your phone will be erased. Make a back up if you don’t want to lose it permanently.
This is what you will be doing in a nutshell.
Setting the phone into a baseline Oreo conditions
Extraction of abl, laf, and boot partititions
Installation of the engineering abl and erasing the laf's using QFIL
Unlocking the phone
Flashing to Pie and maybe Q in the future if you want to update from Oreo
Generation and installation of a magisk-patched boot image for root
Upon successful completion, you will have a fresh, bootloader unlocked and rooted phone that is otherwise stock.
Preparation and requirements:
On the hardware side, you will need a PC with MS Windows installed either directly or as a virtual machine and a high quality USB cable designed for data transfer. Older USB 2.0 hardware is preferred when working with LG phones. There is a long list of software to install.
Minimal adb and fastboot
Instructions: https://forum.xda-developers.com/showthread.php?t=2317790
Download: https://www.androidfilehost.com/?fid=746010030569952951
The LG mobile drivers, http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Dev-Patched LGUP
Instructions and warnings in post #6 with thanks to @ChazzMatt: https://forum.xda-developers.com/lg-v35/help/att-v35-unlocked-wont-verizon-t3958765
Download with thanks to @tecknight for the software: https://androidfilehost.com/?fid=11410963190603845019
9008 Port Driver:
https://raw.githubusercontent.com/g...alcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
QPST with QFIIL
Some basic instructions: https://androidmtk.com/use-qpst-flash-tool
Download: https://qpsttool.com/qpst-tool-v2-7-480
Download and install each of these programs on your PC in the listed order.
You are also going to need some super important supporting files that make all of this magic possible.
The V35 engineering abl that will give you fastboot with thanks to @vlad48 for making it available: https://www.androidfilehost.com/?fid=1395089523397895796. Yes,it says V20, ignore it, it is fine. Extract abl_a and abl_b, and append a “.img” extension to each. Note the locations on your PC for future use.
The recently available emergency download (EDL) firehose that makes direct partition flashing possible released by Biao on Telegram. It is available here:
https://androidfilehost.com/?fid=4349826312261705871
or as an attachment in @Xsavi’s similar and earlier instructions for the V40: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Note its location for later use.
Troubleshooting:
These instructions assume that your phone boots normally. Even with that there can still be issues due to software drivers and pc-hardware. They can be broadly summarized as a difficulty getting the computer to recognize and communicate with the phone and vice-versa. They arise frequently. If you encounter difficulties, review these troubleshooting tips compiled and written by @ChazzMatt and taken from his V30 WTF instructions.
Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
Re-install LG mobile drivers, https://is.gd/Jbrvx1.
Try another USB cable.
Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
Reboot the computer.
Try another computer. (THIS usually solves the problem, https://goo.gl/x637H1. Kudos if you find an an old Win7 PC, https://goo.gl/EaGMhs.)
Master Reset (full reset of phone using hardware buttons), https://goo.gl/N4LcLD. Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
Step 1: Setting an Oreo baseline:
The engineering files for bootloader unlock of the V35 phone are designed to work with Oreo. If you are an Pie or Q, it is highly recommended that you flash back to Oreo. For those of you with the common AT&T V350AWM model that is not on Oreo, there are a couple of points to consider
AT&T does not release flashable roms. If you are on AT&T Pie or eventually Q, there is no going back unless of course you take the time to make a backup of the rom itself. That is not covered in this guide nor am I aware of a guide on how to do this.
AT&T sim-locks its branded V35’s and the menu to unlock is specific to the AT&T rom. You should strongly consider purchasing of a sim-unlock code and applying it before flashing another rom!
To set the baseline:
If you are already on Oreo perform a master reset. To do this, start by turning the phone off. Then press and hold the power and volume - buttons at the same time until you see the LG logo appear. When the LG log appears, release the power button and then press and hold it again while continuing to press the volume – button. Follow the menus to perform the reset.
If you are on Pie or Q, you are going to flash or cross-flash back to Oreo. The kdz's are available for downloaded from https://lg-firmwares.com/lg-lmv350ulm-firmwares/#tab=firmwares. Reports are that roms can be cross-flashed across V35 models with the exception of the Korean V350N. If you are not familiar with the roms, the favored ones are the Google Fi / North American versions for the V350ULM. Down load the latest Oreo version
https://lg-firmwares.com/downloads-file/18971/V350ULM10i_00_NAO_US_OP_0221, md5sum: 64554877b692601d5906d2bdc9691712To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 2: Partition Extraction, Modification and Bootloader Unlock
Enable “OEM Unlock”: Turn on the phone and go through a minimal set-up process. Next go to Settings→ System→ About Phone→ Software info. Repeatedly tap on “Build Number” until you receive a message that you are now a “Developer”. Next go to Next go to Settings→ System→Developer options. Look for “OEM unlock” and flip the switch to on. Exit the “Settings” menus.
Boot the phone in EDL 9008 mode: The “button dance” to put the phone into EDL mode requires quick hands. To increase the likelihood of success, take the phone out of any case to expose the volume buttons. With the phone fully booted and turned on, connect it to your computer by USB. Press and hold the power and volume – keys at the same time. The phone will likely take a screenshoot, keep holding the buttons, afterwards it will bring up a reboot countdown message. With one second left, start pressing the volume + button while still keeping the power and volume – buttons pressed. The phone will show a black screen and windows with make its connection sound if you succeeded in reaching ECL mode. Release the button immediately. Look at your computer, you should also see an entry in the Windows Device Manager under “Ports” that reads:
“Qualcomm HS-USB QDLoader 9008 (COMXX)”
where XX is the port. The phone will just reboot if you didn’t click the volume + button sufficiently fast. Keep trying, you will eventually succeed. If the screen on the phone does go black and you don't see the phone listed in the Windows Device Manager, then you should check installation of 9008 port driver.
Start and configure QFIL: Go to the Start Menu or whatever passes for it on your Windows computer and fire up QFIL. Survey the screen:
You should see “Qualcomm HS-USB QDLoader 9008 XX” next to “Select Port…”.
There should be small text in the lower right corner that reads “Storage Type:”; Select “ufs”.
There is a subheading near the upper left that reads “Select Build Type”. Tick “Flat Build”.
Now using the “Browse…” button under the “Select Programmer", navigate to the folder that contains the firehose file, “prog_ufs_firehose_Sdm845_lgev40.elf” and select it.
Extract partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look for “abl_a”, “laf_a”, “abl_b”, and “laf_b”.
Right click on “abl_a”
Select “Manage Partition Data”
Select “Read Data…”
Open a folder and navigate to location where the extracted file is located. The QFIL “Status” output shows the location and filename. On my PC, it reads:
“C:\Users\whoiam\AppData\Roaming\Qualcomm\QFIIL\COMPORT_XX\ReadData_ufs_xxxxx.bin” where XX is the port number and the “xxxxx” are details about the partition name. Copy the file to a dedicated folder and rename it “abl_a.img”.
Repeat the this process for “laf_a”, “boot_a”, “abl_b”, “laf_b”, and “boot_b” partitions. Note the locations of these files as back-ups and also for the following section on rooting.
Use QFIL to get fastboot:
Write the engineering abl’s: In QFIL, do the following:
Right click on abl_a.
Select “Manage Partition Data”
Select “Load Image”
In the dialog, Navigate to the location of the engineering abl_a.img file you downloaded in the preparation section, select it, and click “Open”.
Repeat this same procedure for abl_b.
Erase laf’s: In QFIL, do the following:
Right click on “laf_a”
Select “Manage Partition Data”
Select “Erase”
Confirm that you want to erase
Repeat for laf_b.
Unplug the phone from USB
Press and hold the power and volume - buttons until the LG V35 boot logo appears. Allow the phone to reboot.
Turn the phone off.
Unlock the bootloader:
Enter fastboot mode: Hold the volume + button and plug in the USB cable. The phone will boot to a series of menus that include “Start” and “Power off”.
Run a command prompt as Administrator. If necessary navigate to the directory where you installed adb.exe and fastboot.exe.
Check that the phone communicates with fastboot: Type “fastboot devices” and press enter. It should return details about your device. It reads “LMV350AWMxxxxxxx fastboot” with my phone.
Bootloader unlock: Type “fastboot oem unlock”. Congratulations if it reports OK, your phone is now unlocked. If it reports failed then try another USB port on your PC, a better/different cable, and potentially even another PC.
Reboot the phone
Step 3: Restore download mode and flash to desired rom:
If the current version of Oreo is where you want to be then skip to Step 4.
If you want to upgrade to Pie or eventually Q, then you need to restore the laf_a, laf_b, abl_a, and abl_b partitions to recover download mode. It should be clear from what you have done above with QFIL how to do this.
Download the kdz of your desired rom. The Google/NAO version of Pie is recommended and available at this link, https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218.
To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 4: Install Magisk for Root:
Re-enter EDL mode with the above button dance procedure
Extract boot_a and boot_b partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look "boot_a” and “boot_b”.
Generate a Magisk-patched booted image working directly with the phone:
Download a stable version of Magisk Manager from the official website: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. It should be saved in the “Download” folder.
In Settings, navigate to Apps & Notifications→ Special access → Install unknown apps. Click on File Manager and set it to allowed.
Open the “File Manager” app and navigate to the Download folder.
Select and install the “MagiskManager-v7.5.1.apk” file keeping in mind that the version numbers may be different.
Connect the phone to USB and place it in file transfer mode.
Copy boot_a.img and boot_b.img to the phone Download folder
Start “MagiskManager” and select “Install”. When presented with the option, tap “Select and Patch a File”.
Navigate to the “Downloads” folder where and select boot_a.img.
There will now be a file named “magisk_patched.img” in the “Downloads” folder. Change its name to magisk_patched_a.img.
Repeat this process with boot_b.img.
Install the Magisk-patched boot images using the PC:
Copy the magisk_patched_a.img and magisk_patched_b to the windows computer.
Put the phone into 9008 EDL mode with the button dance described above.
Start QFIL, configure it as described above, and then click on “Tools” in the menu bar of QFIL and Select “Partition Manager”.
Scroll through the list of partitions and locate boot_a. Right click on it and select “Load Image”. Point it to the magisk_patched_a.img file.
Repeat the previous step for boot_b and load the magisk_patched_b.img file
Reboot your rooted phone.
Step 5: Remove Root Checker: (Added 20200409)
I say with sarcasm that another way that LG has made our lives better was to implement a root-check and monitoring system. Many here are familiar with the root check daemon from the V30. There is a root-check disable twrp package to fix this problem. Installation and use of TWRP for the V35 is tricky. Don't worry, there is another way.
Put the phone in USB debug mode
Connect to your computer
With adb from a command prompt on the computer do the following
adb devices <-- If your devices is properly connect and recognized, adb will respond
List of devices attached
LMV350XXXXXXXXX device
adb shell <-- If you have a shell into the phone you will now see
judyp:/ $
pm uninstall -k --user 0 com.lge.srtc <-- This command removes the root checker, if it succeeds you will get the response:
Success
pm uninstall -k --user 0 com.lge.mlt <-- This command removes the LG monitor, if it succeeds you will get the response:
Success
Happy Rooting!
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
THANK YOU for this. Seriously. Really well done. I can't wait to try it if I ever get my phone back into shape where I CAN try it. ?
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
cmrntnnr said:
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
Click to expand...
Click to collapse
I was one of those who leaped to the Korean KDZ. Now I am running NAO firmware. Guide looks well written. I might wind up taking the leap. Good job bro!
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Nicely done. Thank yoh for sharing the result.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
vavoo said:
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Click to expand...
Click to collapse
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
I am stuck at Fastboot Mode. It says the "Device state - Unlocked", but when if I choose Start or Power off/on my phone it just goes back into fastboot everytime.
1. I installed and flashed the Pie rom you linked in step 1
2. I turned "Oem unlock" to On.
3. placed the phone in 9008 mode, backed up abl_a, laf_a, boot_a, abl_b, laf_b, and boot_b.
Loaded the img to abl_a and abl_b.
Finally, Erased laf_a and laf_b
4. within fastboot, unlocked bootloader
Any ideas ?
If the phone unlocked, go back into 9008 EDL mode and restore the laf and abl images using your backups. That should get you booting.
dave1567 said:
Any ideas ?
Click to expand...
Click to collapse
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
vlad48 said:
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
Click to expand...
Click to collapse
I didn't use your bat since it looks like I can still boot into 9008 mode with the button dance method.
Unfortunately, still nothing!
I flashed my abl_a.img and abl_b.img backups I made to the abl_a/b partitions and flashed your FTM_BL.img to my FTM partition, but it didn't seem to do anything except cause some graphical glitches within fastboot menu (everything still functioned though)
Just in case, I re-locked my phone (fastboot oem lock) and started the QFIL process over (flashing with engineered abl_a and abl_b imgs)
Then within fastboot mode, I ran "fastboot oem unlock" a few times because it fails, but finally it went through
Now the phone is unlocked again, but still just always just boots into fastboot mode!
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
vlad48 said:
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
Click to expand...
Click to collapse
Unfortunately, I don't understand. Thanks for trying to help though.
Anyways, I managed to fix the problem and I'm all set.
- Restored my laf_a and laf_b partitions
- Booted into download mode and re-installed the pie image with LG Up.
- Was now able to boot normally
- Followed the instructions in the guide to get magisk installed and now I'm all set!
Thanks all and hope this helps someone
I scouted my way through these very same steps a couple weeks ago. Soft bricked my device a couple times ? but eventually got her there. Glad too see a dedicated guide is out now. Only problem I've run into is the ctsprofile:fail problem. Been able to fix with spoof pixel fingerprints but it's not ideal. Still looking for solutions if anyone knows anything.
Iantuition said:
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
Click to expand...
Click to collapse
What is the minimum needed for you to enter download mode? I have backups of most partitions i will be happy to share and you can use Qfil to flash those to get to download mode then use LGUP to flash a normal kdz? If so, let me know.
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Sorry to hear that. The first time I tried to use QFIL I got a Sahara error and could not see partitions. It was resolved by reinstalling the 9008 port driver and then QPST in that order. It happened again later when windows tries to be helpful by automatically reinstalling drivers when the phone is plugged in but with a mode change.
Flowtron3000 said:
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Click to expand...
Click to collapse
Will this help me sim/carrier unlock my v35awm?
Can you lock the bootloader after this is done and keep root? Need it for banking apps.
Related
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
with flashtool impossible to rollback . and impossible to flash kdz 6.0... a lot of people with this issue
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
gregor.eesmaa said:
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
Click to expand...
Click to collapse
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
rotoko said:
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
Click to expand...
Click to collapse
There you go. Can't do any better as I am not an expert in how Android precisely works at this level.
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
leegreggs said:
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
Click to expand...
Click to collapse
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
gregor.eesmaa said:
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
Click to expand...
Click to collapse
No I've decided to go back to my LG g2 till either flashtool gets updated or till a tot & dll comes out
gregor.eesmaa said:
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
Click to expand...
Click to collapse
:crying::crying: i forget to enable usb debugging, now my pc can not connect to phone under downloadmode. And i can not use adb to let it reboot bootloader.
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
rav0r said:
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
Click to expand...
Click to collapse
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
AndHD2 said:
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
Click to expand...
Click to collapse
Same here, only a software issue. I cannot boot to download mode, and my device is locked.
Hello
My LG k10 430dsy is stuck on a bootloop and I cant boot into recovery and fatboot and download mode, I just get the message "Your device is corrupt. It cant be trusted and may not work proper"
no download mode no recovery and no fastboot mode
how can I fix this? I could use some help please, even if it means reformatting the phone any way possible, thanks.
LG phones are much nonsense
please do not buy LG phones if you are user advanced
All ways are bricked or locked
When you removed battery and loaded it again, did you try holding volume up and connecting using USB cable to PC?
As wizzardsk sais you have to try connect it holding volume up + lg bridge update error recovery.
Or what about hard reset ( http://www.hardreset.info/devices/lg/lg-k10/ )?
Anyways if your phone connects and stays connected for more a second or two you might have a chance just PM me...
What coused the situation if i may ask?
I want to root lg k10 430dsy ando this commands
1. Enable developer options on the lg K10
2. Enable OEM unlocking and USB debugging
3. Copy twrp.img to disk C: /
3. Go to C: / and open command window. Enter: adb reboot bootloader (phone will start in fastboot mode)
4. Once in the fastboot mode enter the command: fastboot boot twrp.img
5. Once inside TWRP press cancel and then slide to allow modifications.
6. Mount System, data and sdcard.
7. Make BOOT-only backup (uncheck all other partitions)
8. Mount MTP
9. Copy BOOT backup from TWRP folder in our SD card (Boot.emmc.win) and rename bootlz4.img
10. Copy to Boot-resources of CARLIV IMAGE KITCHEN
11. Decompress with Carliv
12. Open bootlz4 folder and find the file "boot.img-ramdisk-compress".
13. Edit "boot.img-ramdisk-compress" with notepad ++ and change "lz4" to "gz"
14. Save
15. Recompress bootlz4.img
16. Go to output folder and look for bootlz4xxxxx.img and rename it as bootgz.img
17. Go to TWRP and restart in bootloader mode
18. Write in command window: fastboot flash boot bootgz.img
19. Then write in command window: fastboot boot twrp.img to return to TWRP
I must flash bootgz_0.img in TWRP
by cpatrick3000 method is false
Plese use method gottlasz for root
i can't aging boot twrp because error "larg size" and remove batterry and my device is bricked
I do hard reset not work
flash lg and lg up not work for 430dsy ony work lg Bridge i use lg bridge for flashing firmware but can't because trying to enter download mode and nothing happens, just text "download boot" download mode is bricked too
My LG k10 430dsy is stuck on a bootloop.show logo lg then show message "Your device is corrupt. It cant be trusted and may not work proper"
holding volume up and connecting using USB cable to PC only connecting two seconds then disconnect
and trying to enter download mode and nothing happens, just text "download boot: after five seconds show message :your device is ........." then turn off bootloop
still not found any way to go to fastboot
Device is corrupted
123xdagsm said:
Hello
My LG k10 430dsy is stuck on a bootloop and I cant boot into recovery and fatboot and download mode, I just get the message "Your device is corrupt. It cant be trusted and may not work proper"
no download mode no recovery and no fastboot mode
how can I fix this? I could use some help please, even if it means reformatting the phone any way possible, thanks.
Click to expand...
Click to collapse
We have a same problem bruh I tried to boot on twrp.img after that my k10 shutsdown and when its reboot a notice say (your device is corrupted it cant be trusted and may not work properly) I try to recover but nothing happens its like bootlooping and no fastboot no download boot no recovery WTF. many tutorial on youtube and says boot to qualcom mode but I cannot locate the killer switch inside the k10 main board.
@123xdagsm OP did you actually tried the download mode? i have the same problem at the exactly same phone, the solution for me afaik is rolling back the software, then go for root..
bricked LG K430dsY
bricked my LG K10 trying to root it (430dsY), the only thing I can do is connect the USB and hold it in "firmware update" mode, ... my command prompt with adb and fastboot is non-responsive... loaded TWRP through fastboot and ran rce.img,- twice, following instructions from a youtube.be link (cMipOfeW6B0)
after second flash of rce.img, it busted. yeah, I feel really stupid. I never got to super-user, any help?
I do have a backup image file made with TWRP on phone, (backup.ab) 437MB, anyway to flash the device from command prompt, get device to respond to command prompt?
"...Anyways if your phone connects and stays connected for more a second or two you might have a chance just PM me...
What caused the situation if i may ask?[/QUOTE]
---------- Post added at 06:49 PM ---------- Previous post was at 06:43 PM ----------
bricked my LG K10 trying to root it (430dsY), the only thing I can do is connect the USB and hold it in "firmware update" mode, ... my command prompt with adb and fastboot is non-responsive... loaded TWRP through fastboot and ran rce.img,- twice, following instructions from a youtube.be link (cMipOfeW6B0)
after second flash of rce.img, it busted. yeah, I feel really stupid. I never got to super-user, any help?
I do have a backup image file made with TWRP on phone, (backup.ab) 437MB, anyway to flash the device from command prompt, get device to respond to command prompt?
just trying to get some help...
"...Anyways if your phone connects and stays connected for more a second or two you might have a chance just PM me...
What caused the situation if i may ask?[/QUOTE]
gottlasz said:
As wizzardsk sais you have to try connect it holding volume up + lg bridge update error recovery.
Or what about hard reset ( hardreset.info/devices/lg/lg-k10/)?
Anyways if your phone connects and stays connected for more a second or two you might have a chance just PM me...
What coused the situation if i may ask?
Click to expand...
Click to collapse
---------- Post added at 07:38 PM ---------- Previous post was at 06:49 PM ----------
didn't know about LG Bridge,- yes, downloaded, installed and used the error recovery option while phone was in "update firmware" mode connected to usb... whew. hehe... may try rooting again... or not
curtgriff said:
bricked my LG K10 trying to root it (430dsY), the only thing I can do is connect the USB and hold it in "firmware update" mode, ... my command prompt with adb and fastboot is non-responsive... loaded TWRP through fastboot and ran rce.img,- twice, following instructions from a youtube.be link (cMipOfeW6B0)
after second flash of rce.img, it busted. yeah, I feel really stupid. I never got to super-user, any help?
I do have a backup image file made with TWRP on phone, (backup.ab) 437MB, anyway to flash the device from command prompt, get device to respond to command prompt?
"...Anyways if your phone connects and stays connected for more a second or two you might have a chance just PM me...
What caused the situation if i may ask?
Click to expand...
Click to collapse
rebamontan22 said:
We have a same problem bruh I tried to boot on twrp.img after that my k10 shutsdown and when its reboot a notice say (your device is corrupted it cant be trusted and may not work properly) I try to recover but nothing happens its like bootlooping and no fastboot no download boot no recovery WTF. many tutorial on youtube and says boot to qualcom mode but I cannot locate the killer switch inside the k10 main board.
Click to expand...
Click to collapse
I could not find any way to solve the problem
I sold the phone to the same state, and bought a new phone
Perhaps there is a way!
I have the same problem with my K3. I know this is an old thread, but is there any solution at all?
123xdagsm said:
Hello
My LG k10 430dsy is stuck on a bootloop and I cant boot into recovery and fatboot and download mode, I just get the message "Your device is corrupt. It cant be trusted and may not work proper"
no download mode no recovery and no fastboot mode
how can I fix this? I could use some help please, even if it means reformatting the phone any way possible, thanks.
Click to expand...
Click to collapse
I want to take of heads off for these who makes LG Nokia Samsung phones. I waste lots off money for phone and after 2 month it breaks. Its product what you can not sell afterwards. Somebody needs to die.
lg k430ds your device is corrupt and cannot go to download mode
I have the same problem :crying: with my k430dsy ( k10 )
no download mode like this video www youtube com /watch?v=s_bx9sr6lL8"
pleas if you found the solution send it to me on my gmail
"[email protected]
Hi, I had LG K430DSY and rooted it, with TWRP and Xposed.
The device is corrupted appears when you unlock the bootloader and allow TWRP to modify system.
It must be there if you want root.
I followed this procedure https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
You cant install TWRP permanently so you will need to port your TWRP.
https://forum.xda-developers.com/lg-k10/development/mtk-portable-twrp-porter-t3536123
STEP 1 - Get your phone's KDZ firmware
1. method:
- reboot your phone into download mode (http://www.hardreset.info/devices/lg...download-mode/)
- start LG Bridge, go to software update and chose update error recovery (right bottom corner).
- from here follow kappu's guide to get your .kdz file: https://forum.xda-developers.com/lg-...ridge-t3504497
- you can let lg bridge finish the flashing process, no data will be lost.
2. method:
- download firmware for your device:
k10: https://forum.xda-developers.com/lg-...g-k10-t3457319
k8: https://forum.xda-developers.com/lg-...mware-t3456467
- now you have your kdz however you better do the next step if you are not sure thats the exact firmware your device has
- use lg up (https://forum.xda-developers.com/lg-...ng-lg-t3517839) to flash that firmware on your device (just to make sure you are really using that particular firmware)
- all data will be lost
Now you have your kdz, lets extract the recovery image:
- download lg firmware extractor: https://forum.xda-developers.com/sho....php?t=2600575
- upack it somewhere and put the kdz file into that folder
- run "WindowsLGFirmwareExtract.exe"
- open your kdz file (first open button from above)
- tick the first entry under file name (the .dz file) and click on "Extract KDZ"
- you will get that .dz file extracted in your LGFirmwareExtract folder
- close LG Firmware extractor and open it again
- now open .dz file (second open button from above)
- find your stock recovery image under file name (usually it's "recovery_190464.bin"), tick that entry and click on "Extract DZ"
- your stock recovery image will be extracted in the LGFirmwareExtract folder.
Now you just copy this "recovery_190464.bin" (or whatever it's name is - just make sure it's a .bin file) into the "twrp_port" folder and run "twrp_port.bat"
YOU WILL NOW HAVE YOUR PORTED TWRP RECOVERY as yourTWRP.img
STEP 2 - UNLOCK YOUR BOOTLOADER
- in settings/about phone/software info tap on build number about 7 times unlock developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
- make sure you installed all the drivers for your mobile from lg's site
- set up adb/fasboot https://forum.xda-developers.com/sho....php?t=2588979
- go to the folder it's installed (in my case it's C:/adb - adb.exe and fastboot.exe supposed to be there) hold shift and right click "open cmd here"
- in the command window type "adb devices"
it will start adb services and will print a line like "...lgk350... or ...lgk420... lgk430, etc"
if you can't find your device there check device manager or google how to work things out
normally in device manager, you should find "LGE Mobile USB Serial Port" under Ports
- now reboot to fastboot mode typing the command: "adb reboot bootloader"
your phone should go blank and only print fastboot mode on the bottom of the screen
- check your fastboot connection:
type: "fastboot devices"
- In case you have a working adb and fastboot connection type
"fastboot oem unlock" - the phone will ask you if you really mean it, using the volume and the on/off buttons (twice) you can accept
you will lose all your data!!! and most likely lose warranty as well!!!
however your phone shell restart just fine (you have to manually restart it by taking out the battery or boot into twrp and reboot from there.
There should be some message during boot up that your system is vulnerable from now on.
- after reboot you may want to check if your bootloader is really unlocked:
get back to fastboot and type "fastboot getvar all"
and find the line which says if your bootloader is unlocked (if it's not you may repeat the process)
set up developer settings again:
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
STEP 3 - ROOTING
- put the recovery image that we ported earlier (e.g "yourTWRP.img") into your ADB folder (like c:\adb - where you opened command prompt earlier)
- Get back to fastboot again and boot to TWRP - type in cmd: "fastboot boot yourTWRP.img" (or whatever your TWRP image's filename is)
- on the first screen of the TWRP it's asking for password to decrypt data - just hit cancel
in case you have no device corrupt message during every boot up follow the next steps
- on the keep system read only? screen of the TWRP let it allow modifications (swipe!)
- reboot to System
you must see the device corrupt message during boot up -> you are ready to go for a root
the rooting part
- download the ramdisk compression exchanger: https://forum.xda-developers.com/app...anger-t3533327 (we need this because SuperSU can only work with gzip compressed ramdisks while we have lz4 compressed ones)
- download latest SuperSU TWRP flashable version: https://forum.xda-developers.com/app...lease-t3452703
- put this (rce_univ.zip) and latest SuperSU (i used v2.79) on your sd card (you need external sd because the internal sd is encrypted in TWRP)
- reboot your device into TWRP (through adb and fastboot as before)
- cancel decrypt data
- don't swipe on system modifying screen just click on "keep read only"
- go to backup, backup your boot image (tick only boot partition /untick the rest/ and select storage as micro sd card) in case anything goes wrong during the rest of the process you can always restore it
- go to install
- select storage and chose micro sd card
- install rce_univ.zip (it will recompress your ramdisk to gzip - so SuperSU can tweak it)
- when it's finished don't wipe or don't reboot! Go back (hit back button button) and install SuperSUxxx.zip
- go back again (without restart or wipe) and install rce.zip again (this will recompress your ramdisk to lz4)
- now you can reboot to system (without any wipe) - it will bootloop a few times, be patient!
If you have any problem with installing rce_univ.zip please post comments to it's thread:
https://forum.xda-developers.com/app...anger-t3533327
Please follow those instructions if you want to Root.
---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------
123xdagsm said:
Hello
My LG k10 430dsy is stuck on a bootloop and I cant boot into recovery and fatboot and download mode, I just get the message "Your device is corrupt. It cant be trusted and may not work proper"
no download mode no recovery and no fastboot mode
how can I fix this? I could use some help please, even if it means reformatting the phone any way possible, thanks.
Click to expand...
Click to collapse
Use LG Up to unbrick your device.
That's what i used then i had LG K430DSY
Install LG UP, then download the firmware and flash it with LG UP.
Alternatively,
Install LG Bridge, then make sure your device is switched off,
Hold the volume up key then plug in the usb cable to the phone
It will enter download mode.
USB Bridge option to fix recovery error, It will flash new KDZ firmware and your device will be unbricked.
I solved this problem, if you can inter download mode, you can do so.
1. download your model kdz file.
2. download lgup 1.14 and install it
3. download uppercut from this link (then your phone model will be detected by lgup1.14)
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
4. inter download mode (volume up+ connect with usb cable)
5. open lgup 1.14, thick upgrade in process, select your kdz file in file path and start.
Well, now I have the same problem. No way to get into download mode. Lg sucks...
We need to access to emmc and rewrite stock binaries. But there isn't any way to do it at home. We need something like 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"
}
And connect it to board like this:
Then we can write stock boot/system/recovery etc..
Note: This scheme is for MTK chipsets.
123xdagsm said:
Hello
My LG k10 430dsy is stuck on a bootloop and I cant boot into recovery and fatboot and download mode, I just get the message "Your device is corrupt. It cant be trusted and may not work proper"
no download mode no recovery and no fastboot mode
how can I fix this? I could use some help please, even if it means reformatting the phone any way possible, thanks.
Click to expand...
Click to collapse
take a look on that method https://forum.xda-developers.com/lg-k10/how-to/guide-to-flash-official-firmware-lg-k-t3761728
Let me dig up this old thread real quick
I have same problem, Model LG K10 K430dsE
Phone has bootloop, says it's corrupted and not trusted etc
When i enter download mode it stays for 10s then bootloops again,
PC does not recognize the device but it did before, tried uninstalling/reinstalling LGUP/BRIDGE/USB DRIVERS etc
This happened after i tried to flash twrp.img
If anyone has any suggestion, answer below or reply here
Thread: https://forum.xda-developers.com/t/lg-k10-cannot-launch-twrp-or-download-mode-bootloop.4258773/
fml4days said:
Let me dig up this old thread real quick
I have same problem, Model LG K10 K430dsE
Phone has bootloop, says it's corrupted and not trusted etc
When i enter download mode it stays for 10s then bootloops again,
PC does not recognize the device but it did before, tried uninstalling/reinstalling LGUP/BRIDGE/USB DRIVERS etc
This happened after i tried to flash twrp.img
If anyone has any suggestion, answer below or reply here
Thread: https://forum.xda-developers.com/t/lg-k10-cannot-launch-twrp-or-download-mode-bootloop.4258773/
Click to expand...
Click to collapse
There is no way to fix this. I've had the same and even though I tried to access to emmc directly, I was not unable to solve it. I had sent it to LG for repair and my device was repaired (motherboard changed).
berkantkz said:
There is no way to fix this. I've had the same and even though I tried to access to emmc directly, I was not unable to solve it. I had sent it to LG for repair and my device was repaired (motherboard changed).
Click to expand...
Click to collapse
Thank you for the response bro, i have read many of your posts and im pretty sure this is 100% accurate
fml4days said:
Thank you for the response bro, i have read many of your posts and im pretty sure this is 100% accurate
Click to expand...
Click to collapse
There might be a way for those who has advanced tools to modify/access the stuff on motherboard but since I don't have them, that's the only accurate thing I could say.
Thanks for trusting in me and you're welcome.
Really need help!
I successfully unlocked my Mi Max 3 using the official process. 14 day wait. No issues...booted back into MIUI 10' restored backup from MiCloud and was back to normal, except now it showed "unlocked" on startup screen.
It was running CN MIUI 10 V10.0.6.0 OEDCNFH
I had been reading that it was possible to flash the device with the global version of the ROM
I had several Google related issues with the Chinese ROM so I downloaded the MiFlash tool (2018.5.28.0), got the ROM from here: https://xiaomifirmware.com/roms/latest-official-miui-roms-for-xiaomi-mi-max-3/
and tried to flash it with Global 10.0.1.0 OEDMIFH
Result was the error "flash crclist error"
screenshot here
https://1drv.ms/u/s!ArN9mSbbMVT8gohpA03ob7X2FhjspQ
After this, the device is stuck in Fastboot mode and seems to no longer have a bootable ROM. Booting into recovery mode with vol up + power and restarting that way also just boots back into Fastboot.
I downloaded the Fastboot version of the ROM the phone was originally running 10.0.6.0 OEDCNFH and tried to flash that.
It also failed with the same error.
This user had the same issue with a Mi8:
https://forum.xda-developers.com/mi-8/help/failed-to-install-global-rom-via-mi-t3851636
The thread did not help me. There seems to be almost nothing related to this issue "flash crclist error" on XDA
My phone is not bootable now. No idea what to try next, I am a total novice in this area. I have since been reading about Anti Rollback Protection, I just don't know if this has anything to do with my issue. My device is not dead....it is booting into Fastboot, and I can still see it in MiFlash. If anyone could advise me I would be very grateful.
https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.
The path of the rom seems too long.
Create a new folder at the root of your C drive and give it a name without spaces, move all the contents of the extracted rom to that folder and try to flash again
opasha - thanks for reply
opasha said:
https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.
Click to expand...
Click to collapse
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.
richard.rea said:
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.
Click to expand...
Click to collapse
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.
can not flash ROM
opasha said:
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.
Click to expand...
Click to collapse
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.
richard.rea said:
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.
Click to expand...
Click to collapse
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.
Just run the damn flash-all.bat for God sake...
SOLVED thank you!
opasha said:
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.
Click to expand...
Click to collapse
You were right. I extracted using 7Zip instead of Winzip. Pointed MiFlash at the extracted folder. 10.0.1.0 Global flashed successfully.
**HUGE** thanks to you for your replies and help. Painful learning curve for me. Very happy to get my phone working again, this time with the ROM I wanted.
Thanks again
best regards
so im on the same version but xiaomi.eu... 10.0.6.0 can i go downgrade that global? using same method?
flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.
flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.
Help. I need to sell my H932 but the buyer is afraid of having root and not getting ota updates.
I was never too smart in regards to cell phones. But 2 weeks ago I had brain surgery and I'm even dumber now. I need steps written for a child. I have lgup but don't have a current .kdz. Its currently running H93220s.
Is Android 9 available ota?
Thanks in advance.
bsliv said:
Help. I need to sell my H932 but the buyer is afraid of having root and not getting ota updates.
I was never too smart in regards to cell phones. But 2 weeks ago I had brain surgery and I'm even dumber now. I need steps written for a child. I have lgup but don't have a current .kdz. Its currently running H93220s.
Is Android 9 available ota?
Thanks in advance.
Click to expand...
Click to collapse
Android 9 is not available yet for h932
Your other question someone else can answer. Don't know much about h932.
Thanks for the no 9 news. Oh well.
lg-firmware.com find H932SV then download kdz latest 20s, use correct lgup to flash it, reset phone.
immns said:
lg-firmware.com find H932SV then download kdz latest 20s, use correct lgup to flash it, reset phone.
Click to expand...
Click to collapse
Thanks. Downloading the .kdz right now.
I already have lgup installed. While trying to install this new lgup, I get the message, "Error 1316. The specified account already exists." I'm assuming I have this version installed but don't know for sure.
I may be wrong, but if you're on stock 20s you're on the most recent update from LG.
conbak49 said:
I may be wrong, but if you're on stock 20s you're on the most recent update from LG.
Click to expand...
Click to collapse
I'm on a rooted 20s. I want to be on an unrooted, any version.
The instructions on LG's website say to hold the volume up button and plug it into a pc. I do that and it boots in TWRP. Typing adb devices from a Windows command prompt shows the V30 and it being in recovery mode. But starting lgup, it says, "There is no handset connected. Please connect a handset."
If I use TWRP to boot into the system, adb devices doesn't show any handsets connected. LGUP does see it but doesn't see the new .kdz file. And the phone reboots about once a minute.
If I boot into TWRP and do a default Wipe, it doesn't reboot.
What did I do wrong?
bsliv said:
I'm on a rooted 20s. I want to be on an unrooted, any version.
The instructions on LG's website say to hold the volume up button and plug it into a pc. I do that and it boots in TWRP. Typing adb devices from a Windows command prompt shows the V30 and it being in recovery mode. But starting lgup, it says, "There is no handset connected. Please connect a handset."
If I use TWRP to boot into the system, adb devices doesn't show any handsets connected. LGUP does see it but doesn't see the new .kdz file. And the phone reboots about once a minute.
If I boot into TWRP and do a default Wipe, it doesn't reboot.
What did I do wrong?
Click to expand...
Click to collapse
Doing a default wipe eliminates the OS from your phone so you don't have an OS to boot into. If you want unrooted stock and are able to boot into TWRP, you should be able to to just flash the flashable 20s kdz for the H932 w/o Magisk and that will put you back on stock. See the thread with instructions. I believe if you flash w/o Magisk that will also eliminate your ability to get back to TWRP. To root again I believe you'd have to start all over again so choose carefully.
Actually, you'd have to use the flashable 20s Stock ZIP, not the KDZ, if you want to flash it with TWRP. But that wouldn't restore stock Recovery nor Download mode (laf). Thus the new owner wouldn't be able to update with OTA or LG Bridge.
The best way to ensure complete stock is to flash KDZ, as you tried. Since your Download mode seems to be gone, I would flash the laf ZIP file in TWRP. You can find it in the Stock H932 ZIP thread and in the H932 root thread.
After that, follow the exact steps in the H932 root guide to get into Download mode, then flash the 20s KDZ using LGUP Refurbish Mode.
To be truly stock (and avoid the warning screen during boot) you have to also lock the bootloader, but you can only do that once all partitions are completely stock, otherwise you could brick the phone.
TheDannemand said:
Actually, you'd have to use the flashable 20s Stock ZIP, not the KDZ, if you want to flash it with TWRP. But that wouldn't restore stock Recovery nor Download mode (laf). Thus the new owner wouldn't be able to update with OTA or LG Bridge.
The best way to ensure complete stock is to flash KDZ, as you tried. Since your Download mode seems to be gone, I would flash the laf ZIP file in TWRP. You can find it in the Stock H932 ZIP thread and in the H932 root thread.
After that, follow the exact steps in the H932 root guide to get into Download mode, then flash the 20s KDZ using LGUP Refurbish Mode.
To be truly stock (and avoid the warning screen during boot) you have to also lock the bootloader, but you can only do that once all partitions are completely stock, otherwise you could brick the phone.
Click to expand...
Click to collapse
When I hold volume up and plug the USB into my pc, it briefly says Download Mode then TWRP goes on the screen.
I can't get the 20s.kdz to install using LGUP.
I truly appreciate all the help but this may be beyond my capabilities. (Brain surgery sucks.)
bsliv said:
When I hold volume up and plug the USB into my pc, it briefly says Download Mode then TWRP goes on the screen.
I can't get the 20s.kdz to install using LGUP.
I truly appreciate all the help but this may be beyond my capabilities. (Brain surgery sucks.)
Click to expand...
Click to collapse
It's OK, people here want to help
Did you flash the laf ZIP in TWRP to fix your Download Mode? If not, that should be your first step. (If you end up losing TWRP too, it gets much more difficult.)
1. Download the StockLAF from this post by weakNPCdotCom's. Verify its MD5 to make sure it downloaded properly.
2. Transfer StockLAF.zip to you phone by whichever means (USB cable, SD card etc).
3. Boot into TWRP, either deliberately or by trying to get into Download Mode
4. Flash StockLAF.zip to restore your Download Mode.
5. Use TWRP to turn off the phone (I forget the exact command) and disconnect its cable.
6. Download and install LGUP from this post by runningnak3d. It's not the latest, but we know it works on H932.
7. Now try Download mode again: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
8. If you manage to get into Download mode, launch LGUP and make sure it detects the phone.
9. Flash the H932 20s KDZ using LGUP Refurbish mode. Of course if you don't already have it, download it from lg-firmwares.com and verify its MD5.
10. Unplug cable and let phone reboot after LGUP (hopefully) completes flashing the KDZ.
11. Once (hopefully) in stock Oreo, tap Settings>General>About phone>Software info>Build number until Developer Options are enabled.
12. Enable Settings>General>Developer Options>Enable OEM unlock.
13. Turn phone off and unplug the cable.
14. With phone off, enter Fastboot mode by holding Vol Down and plugging in the USB cable. Plug into computer.
15. In ADB window, enter fastboot devices to verify ADB is working.
16. In ADB window, enter fastboot oem lock to re-lock the bootloader.
17. Use fastboot keys to reboot phone into OS.
18. Run Settings>General>Reset>Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch.
19. Done. Ship the phone to your buyer.
I'm insanely busy tonight, so afraid I won't be there for any follow-up questions. But anybody here should be able to help with those steps.
TheDannemand said:
It's OK, people here want to help
Did you flash the laf ZIP in TWRP to fix your Download Mode? If not, that should be your first step. (If you end up losing TWRP too, it gets much more difficult.)
1. Download the StockLAF from this post by weakNPCdotCom's. Verify its MD5 to make sure it downloaded properly.
2. Transfer StockLAF.zip to you phone by whichever means (USB cable, SD card etc).
3. Boot into TWRP, either deliberately or by trying to get into Download Mode
4. Flash StockLAF.zip to restore your Download Mode.
5. Use TWRP to turn off the phone (I forget the exact command) and disconnect its cable.
6. Download and install LGUP from this post by runningnak3d. It's not the latest, but we know it works on H932.
7. Now try Download mode again: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
8. If you manage to get into Download mode, launch LGUP and make sure it detects the phone.
9. Flash the H932 20s KDZ using LGUP Refurbish mode. Of course if you don't already have it, download it from lg-firmwares.com and verify its MD5.
10. Unplug cable and let phone reboot after LGUP (hopefully) completes flashing the KDZ.
11. Once (hopefully) in stock Oreo, tap Settings>General>About phone>Software info>Build number until Developer Options are enabled.
12. Enable Settings>General>Developer Options>Enable OEM unlock.
13. Turn phone off and unplug the cable.
14. With phone off, enter Fastboot mode by holding Vol Down and plugging in the USB cable. Plug into computer.
15. In ADB window, enter fastboot devices to verify ADB is working.
16. In ADB window, enter fastboot oem lock to re-lock the bootloader.
17. Use fastboot keys to reboot phone into OS.
18. Run Settings>General>Reset>Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch.
19. Done. Ship the phone to your buyer.
I'm insanely busy tonight, so afraid I won't be there for any follow-up questions. But anybody here should be able to help with those steps.
Click to expand...
Click to collapse
Beautifully written. And it seamed to work!!! Thank you very much.
bsliv said:
Beautifully written. And it seamed to work!!! Thank you very much.
Click to expand...
Click to collapse
Awesome, glad to hear it. Good job :good:
Disclaimer: Do this at your own risk, blah blah blah. Brick your phone its on you..
Just a quick tutorial on bootloader unlocking the G7 One. Lots of the info in here can be found in other areas of XDA.
*****Read full post before starting*******
1. Boot up your G7 One and turn on OEM unlocking. Settings -> About phone -> Tap on build number 7 times.
Now back to main settings menu, System -> Developer options -> turn on OEM unlock.
2. Download and install QPST which also has QFIL. QFIL will be used to back up all phone partitions, and flash bootloader.
https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file
3. Download in install minimal adb 1.43 from here: unless you already have adb installed.
https://androidmtk.com/download-minimal-adb-and-fastboot-tool
4. Download and install Sonim XP8 drivers. (I dont know why they work, but they do. i dont think there are any available 9008 drivers for the G7 One from LG) You MIGHT also need qualcomm drivers but i dont remember for sure. If so do a google search for them.
https://androidfilehost.com/?fid=4349826312261641909 Thanks to smokey710
5. Download LG V30 firehose and keep for later.
https://androidfilehost.com/?fid=4349826312261705868
6. Once QPST is installed and sonim drivers are installed, you need to do a full backup of your phone.
to do this you need to put your phone into EDL (emergency download mode) aka Qualcomm HS-USB QDLoader 9008 mode.
to get into 9008 mode, start QFIL plug your powered on phone into your pc, and go to this post to get into 9008 mode:
https://forum.xda-developers.com/t/this-is-how-to-enter-edl-mode.4048295/
7. Backing up phone: 1. Start QFIL. In QFIL click on "select port" and choose "Qualcomm HS-USB QDLoader 9008 (COM XX)"
**XX being whatever com port your phone is on.
2. Under "Select Build Type" tick flat build box.
3. Under "Select Programmer" click "Browse.." and select the V30 fire hose downloaded in step 5 above.
4. Bottom right corner set the storage type to UFS.
5. Now at the top, click on "Tools", in the drop down box click on "Partition Manager", then click ok to confirm in the pop up box.
6. If everything is done right you'll get a partition manager box pop up with a list of all your phones partitions.
7. To back up a partition, highlight it then right click -> manage partition data -> read data.
8. Do this for all partitions to have a full backup of your phone. You can skip userdata if you want as its HUGE.
9. MOST IMPORTANT partitions are modemst1&2 and FSG. These contain IMEI etc. as long as you have these 3
partitions save you can always use someone else's partitions along with those 3 to restore your phone. Keep them safe!
8. Bootloader unlocking: 1. Similar to backing up the partitions, now go to your abl_a and abl_b partitions, and instead of doing a read, select
"Load Image..." and load this engineering bootloader:
https://www.mediafire.com/file/k69bh96q0qndk16/abl_a_eng_g7one.bin/file
2. Once that is done, hold power & volume down to reboot phone. Close out QFIL and reboot your phone to fastboot by shutting your phone down, then holding volume down while plugging in usb cable.
3. Open your ADB folder, press shift, right click and open cmd (or powershell) window here.
At command prompt type: "fastboot devices" without quotes. Make sure your phone shows up.
4. Now "fastboot oem unlock" follow directions on phone to unlock bootloader.
5. Done!!! Now you can use magisk on your phone to root boot_a/b images and use either qfil
or fastboot to flash them back.
Apologies if this isnt the best tutorial, its not something i do. If you have problems with any step here do a google search, all this stuff can be found in tutorials in XDA or elsewhere. Really the only thing i provided here is the bootloader file for unlocking.
All credits go to authors of other tutorials and links in this tutorial.
Good luck!!
Looks like slowly every recent LG phone will be able to be unlocked by these tricky methods. Except G6 i believe for G6 wont be any solution because i have G6 and i dont have such fortune
Any roms yet?
@GMSS75 Would you have the instructions under Step 7 available for Linux platforms?
All I have to work with here is QDL.
acerspyro said:
@GMSS75 Would you have the instructions under Step 7 available for Linux platforms?
All I have to work with here is QDL.
Click to expand...
Click to collapse
As far as I know qfil is windows only
GMSS75 said:
As far as I know qfil is windows only
Click to expand...
Click to collapse
I think QFIL is just a front-end to QDL, could be wrong though
acerspyro said:
I think QFIL is just a front-end to QDL, could be wrong though
Click to expand...
Click to collapse
It could be, I've never used it so I can't help with it, sorry.
After finished this step "Now "fastboot oem unlock" follow directions on phone to unlock bootloader." my phone stuck at fastboot mode, althought t choose restart or powerdown, my phone alway reboot into fastboot mode.
dkmhariwon said:
After finished this step "Now "fastboot oem unlock" follow directions on phone to unlock bootloader." my phone stuck at fastboot mode, althought t choose restart or powerdown, my phone alway reboot into fastboot mode.
Click to expand...
Click to collapse
Flash your original abl files
stock framework-res.apk file needed!!
Hi, I would like to have a copy of the stock framework-res.apk file in order to create a good overlay for GSI treble rom. https://forum.xda-developers.com/t/guide-how-to-make-gsis-overlay-file-for-your-phone.3878974/