Whats the difference between flashing twrp in fastboot mode and edl qfil mode.
Can we flash the twrp.img through partition access from qfil tool and on which partition we should flash it. Lg g7 lmg710vm but after crossflashing now lmg710ulm
Related
I want to go back to download mode from fastboot..plz help me how to
If you don't have access to download mode, then you'll need to flash the laf.img file specific to your phone. If you can't locate the LAF image, then you'll need to extract it from the KDZ. Here's a tutorial on how to flash the image...
Tutorial| Fixing "Fastboot mode started"
http://forum.xda-developers.com/lg-g3/help/tutorial-fixing-fastboot-mode-started-t2995854
hello, so after trying to flash stock lollipop something went wrong and now can't access download mode, i tried to flash laf.img but i can't flash anything using adb, plz help.
When in fastboot mode:
Code:
fastboot flash laf laf.img
doesn't work?
I've restored download mode on a V410 before that way just to see if it would work, and it was successful. I nuked my laf partition intentionally because we didn't use to have a kdz for the V410, and I thought it would be easier to recover the tablet with fastboot available than a useless (for the V410 without a kdz) download mode.
jason2678 said:
When in fastboot mode:
Code:
fastboot flash laf laf.img
doesn't work?
I've restored download mode on a V410 before that way just to see if it would work, and it was successful. I nuked my laf partition intentionally because we didn't use to have a kdz for the V410, and I thought it would be easier to recover the tablet with fastboot available than a useless (for the V410 without a kdz) download mode.
Click to expand...
Click to collapse
Thank you for the replie, no, every time i trie to flash something or unlock the bootloader i get this message : failed (remote: unknown command)
recovery partitions are different in Android O that means from fastboot
fastboot flash recovery <filename>.img changed to fastboot flash recovery_ramdisk <filename>.img (i had installed twrp with help of this code in my honor 7x)
i want to know is there any change for boot image partition.
fastboot flash boot boot.img not working in my case.
device: honor x BND-AL10
stock boot image from Update.APP (OREO built)
help me on this! i need to flash boot.img into my device
babu.123 said:
recovery partitions are different in Android O that means from fastboot
fastboot flash recovery <filename>.img changed to fastboot flash recovery_ramdisk <filename>.img (i had installed twrp with help of this code in my honor 7x)
i want to know is there any change for boot image partition.
fastboot flash boot boot.img not working in my case.
device: honor x BND-AL10
stock boot image from Update.APP (OREO built)
help me on this! i need to flash boot.img into my device
Click to expand...
Click to collapse
It changed to ramdisk so fastboot flash ramdisk that's the new boot
Hi all op3 users,
Is there any twrp which supports persist partition ? So we could flash persist.img from stock rom to fix some problems with sensors for example .
We can flash persist.img in fastboot mode
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
But we have only ota.zip . Were can we find full roms for OnePlus 3 ? I mean roms which you can install with qpst/qfil or with msmdownloadtool
mar.ur said:
Hi all op3 users,
Is there any twrp which supports persist partition ? So we could flash persist.img from stock rom to fix some problems with sensors for example .
We can flash persist.img in fastboot mode
fastboot erase persist
fastboot flash persist persist.img
fastboot reboot
But we have only ota.zip . Were can we find full roms for OnePlus 3 ? I mean roms which you can install with qpst/qfil or with msmdownloadtool
Click to expand...
Click to collapse
What i have learnt that you can flash persist.img in fasboot mode if your android version is 6.0 with unlocked bootloader and root access..
I was facing same issue and was getting "FAILED (remote: Partition flashing is not allowed)" but after flashing 6.0, i was able to erase and flash persist fastboot mode.
Trying to flash Lineage 17.1 or TWRP on Cubot Quest Lite ends in Orange-State-Bootloop
After flashing Lineage 17.1 i get a Bootloop at orange state.
Restoring original System and generating TWRP with the hovatek tool and flashing only TWRP produced also a bootloop
Tried [Hovatek]_Mediatek_Auto_TWRP_Recovery_Porter_V1.7a_by_Team_Hovatek.7z
Tried also [Hovatek]_Spreadtrum_(SPD)_Auto_TWRP_Recovery_Porter_V1.4_by_Team_Hovatek.7z
Flashing is done from Linux PC with following commands:
1. Try Lineage System without a Rocovery:
fastboot flashing unlock (volume key up for confirmation)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img <-- vbmeta.img from Cubot Stock rom
fastboot flash boot boot.img
fastboot flash system lineage-17.1-20210321-UNOFFICIAL-treble_arm64_avS.img
fastboot reboot
I tried also lineage-17.1-20210321-UNOFFICIAL-treble_a64_avS.img
2. Try Only TWRP Recovery with Stock Rom System unchanged
generate recovery with Hovatek Recovery Porter, then
restore original System with SP-Flash-Tool, then
fastboot flashing unlock (volume key up for confirmation)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot
Then try to enter Recovery by pressing Volume-UP+Power-Key
I was successfull with a Cubot Kingkong Mini with the same approach. Both phones from cubot have the same CPU, RAM, Camera
Mediatek MT6761 Helio A22, 64bit
Any ideas to get Lineage or TWRP running?
Hi, I have the same phone and find android 9 very painful.....do you think I can install android 6 ?
Hi andro-try, have you solved yet problem reported (TWRP) ?