Related
HI FRIENDS TODAY I AM GOING TO GIVE FULL AND EXPLAINED TUTORIAL TO UNBRICK ANY LG MODEL ( NOT SUPPORTED BY JTAG,OCTOPUS BOX)
PROBLEM INTRODUCTION
NO DOWNLOAD MODE
NO RECOVERY MODE
NO FASTBOOT MODE
FASTBOOT MODE
LG LOGO STUCK
PC DETECT AS QHSUSB BULK
PARTITION POP UP WHEN CONNECTED TO PC
SECURITY ERROR
KERNEL CRASH
NO SIGN OF LIFE
WHY MY PHONE BRICKED????????JUST FLASHING WRONG ROM ( MOST IN CASE OF REFURBISHED PHONE PURCHASED FROM THIRD PARTY SELLER)
FLASHING WRONG RECOVERY
FLASHING KERNEL
FLASHING KERNEL
DURING UPDATES ( FAILED OR INTERRUPTED)
AND MANY OTHER CAUSES
TOOLS REQUIREMENT LG FLASH TOOL FOR KDZ AND TOT FILE( http://forum.xda-developers.com/showthread.php?t=2432476(CREDIT GOES TO HYELTON)TOT OR KDZ FILE ( DEPENDING ON SITUATION) >>>>>>>>>>( KEEPING BOTH FILES RECOMMENDED)LG FIRMWARE EXTRACTOR ( http://forum.xda-developers.com/showthread.php?t=2600575) >>>>>>>>>>>> ( DOWNLOAD LATEST VERSION)
ANDROID SDK SLIM mod edit - malicious link removed) >>>>>>>>>>>> ( USEFULL TO UNBRICK PHONE IN FASTBOOT MODE)
QUALCOMM DRIVER ( http://www.mediafire.com/download/pba9wajnehr9qwg/Qualcomm+USB+Drivers.rar )>>>>>>>> ( for qhsusb bulk mode)
PDANET FOR ADB DRIVER ( http://pdanet.co/a/)
IF YOU FLASHED WRONG RECOVERY OR MODIFY PARTITION THEN YOU WILL STUCK IN FASTBOOT
SOLUTION FOR FASTBOOT
EXTRACT ANDROIDSDKSLIM.ZIP FILE ON DESKTOP ( ANY WHERE)
INSTALL PDANET AND CHOOSE LG COMPLETE INSTALLATION
DOWNLOAD PARTITION FILE FOR YOUR MODEL ( IF D802 THEN USE ONLY PARTITION FILE FOR D802) >>>>>>>>>> ( http://downloads.codefi.re/autoprime/LG/LG_G2)
NOTE : 1) YOU CAN EXTRACT PARTITION FILE FROM KDZ OR TOT FILE USING LGFIRMWARE EXTRACTOR TOOL
FOLLOW THIS VIDEO TO KNOW HOW TO EXTRACT PARTITION FILE
2) PARTITION FILE MUST BE IN .img FORMAT ( WHEN WE EXTRACT PARTITION FILE FROM KDZ OR TOT THEN IT IS IN .bin FORMAT SO SIMPLY RENAME FROM .bin to .img )
3) YOU NEED TO EXTRACT 10 FILES FROM TOT ( aboot, boot, sbl1, dbi, laf, recovery, modem, misc, rpm, tz ) and 9 FILES FROM KDZ ( misc file is not present in kdz so dont worry it is not important)
AFTER EXTRACTING PARTITION FILE AND RENAMING THEM YOU WILL GET 10 OR 9 FILE ( aboo.img, boot.img, laf.img, recovery.img, sbl1.img, dbi.img, rpm.img, tz.img, misc.img) and REMOVE ANY NUMBER FROM THE NAME OF FILES ( SUPPOSE YOU GET aboot_21345.bin THEN RENAME TO aboot.img)
NOW COPY THESE PARTITION FILE IN THE LAST FOLDER (PLATFORM-TOOLS) OF ANDROIDSDKSLIM FOLDER.
NOW CONNECT YOUR PHONE TO PC IN FASTBOOT MODE ( OPEN DEVICE MANAGER AND SEE ON THE TOP THERE WILL ANDROID ADB INTERFACE UNDER ANDROID PHONE. IF NOT THEN CHECK ADB DRIVER INSTALLED PROPERLY OR NOT.
NOW GO TO THE THE FOLDER PLATFORM -TOOL INSIDE ANDROIDSDKSLIM FOLDER.
NOW PRESS AND HOLD SHIFT BUTTON ON KEYBOARD AND RIGHT CLICK IN THAT FOLDER AND YOU WILL GET AN OPTION OPEN COMMAND PROMPT OR WINDOW HERE. CLICK ON IT AND YOU WILL GET CMD WINDOW.
NOW TYPE fastboot devices ( IT WILL SHOW YOUR DEVICES )
NOW TYPE THESE COMMAND
fastboot erase recovery
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
exitNOW REMOVE USB CABLE AND SWITCH OFF YOUR PHONE BT LONG PRESSING POWER BUTTON
NOW PRESS AND HOLD VOL UP AND CONNECT TO PC AND YOU WILL GET DOWNLOAD MODE FIXED
HURREYYYYYYYYYYYYYY
GO AND FLASH STOCK ROM ( http://forum.xda-developers.com/showthread.php?t=2432476)
IF YOU STILL STUCK IN FASTBOOT MODE THEN TYPE THESE COMMAND ( erase all 10 or 9 file and flash them one by one as shown)
fastboot erase aboot ( this command will erase aboot.img from phone)
fastboot flash aboot aboot.img ( this command will flash aboot to phone )
fastboot erase boot
fastboot flash boot boot.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase rpm
fastboot flash rpm rpm.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase modem
fastboot flash modem modem.img
fastboot erase misc
fastboot flash misc misc.img
fastboot erase sbl1
fastboot flash sbl1 sbl1.img
fastboot erase tz
fastboot flash tz tz.img
fastboot erase dbi
fastboot flash dbi dbi.img
fastboot reboot
exitNOW REMOVE USB CABLE AND SWITCH OFF YOUR PHONE BT LONG PRESSING POWER BUTTON
NOW PRESS AND HOLD VOL UP AND CONNECT TO PC AND YOU WILL GET DOWNLOAD MODE FIXED
HURREYYYYYYYYYYYYYY
GO AND FLASH STOCK ROM ( http://forum.xda-developers.com/showthread.php?t=2432476)
SOLUTION FOR ALL THE PROBLEM WITH NO DOWNLOAD MODEYOU NEED TO FORCE PHONE INTO QHSUSB BULK MODE BY SHORTING TEST POINT
WHEN YOU GET QHSUSB BULK MODE IN DEVICE MANAGER THEN INSTALL QUALCOMM DRIVER ( http://www.mediafire.com/download/pba9wajnehr9qwg/Qualcomm+USB+Drivers.rar)
NOTE : THERE ARE TWO MODE IN QHSUSB BULK
1) QUALCOMM HS-USB 9006
THIS MODE IS VERY EASY TO FIX. YOU NEED THE PARTITION FILE THAT WE GET IN THE STARTING TO SOLVE FASTBOOT MODE)
TO SOLVE 9006 FOLLOW THIS METHOD ( http://forum.xda-developers.com/showthread.php?t=2582142 )
UBUNTU METHOD IS UNIVERSAL IT CAN BE USED FOR ANY PHONE IN 9006 ( UNBRICK VERY PARTITION METHOD ( http://forum.xda-developers.com/lg-g2/general/unbrick-lg-g2-qhsusbbulkqualcomm-9006-t2939627) BY TUNG KICK IS ONLY FOR G2 HOWEVER IT CAN BE USED FOR GPRO2 AND G FLEX BUT I M NOT SURE IT MAY NOT WORK OR BRICKED MORE)
WHEN YOUR PHONE GET STUCK IN 9006 THEN LOTS OFF DRIVE POP UP WHEN CONNECTED TO PC ( MOST IMPORTANT IDENTIFICATION)
2 ) QUALCOMM HS-USB 9008
IF YOU STUCK IN 9008 THEN THIS IS THE SUPER HARD BRICK MODE.
CONTACT aftabalam8c2 ( http://forum.xda-developers.com/member.php?u=4554553 ) this guy not only can unbrick lg g2 , g3 but g pro 2, g flex, vu3, vu2, nexus4 , nexus 5, lg g , lg gpro, and around MORE THAN 30 ( I DONT KNOW BUT HE TOLD ME ALL HE CAN UNBRICK MORE THAN 50 ) devices of lg which not supported by JTAG OR OCTOPUS BOX.
ACCORDING TO HIM MOST USER DAMAGED DURING SHORTING OF TEST POINT ( SO BETTER TO ASK HIM BEFOR SHORT)
I NEVER SHORTED SO DONT ASK ME. HE ALSO MADE A SERIES OF TEST POINT ON YOU TUBE FOR MANY DEVICES BUT THESE VIDEO ARE NOT PUBLIC NOW. MAY BE HE MAKE ALL VIDEOS PRIVATE AFTER SOME GUY CHEATED HIM ON XDA ( CONCLUDED FROM HIS COMMENTS)
AND THE ACCOUNT OF THIS GUY DISABLED BY XDA FOR 1 WEEK ( I ASKED HIM PERSONALY ON WHATS APP)
SO IF YOU WANT THE TEST POINT FOR ANY PHONE ASK HIM.
THIS GUY UNBRICKED MY LG G FLEX IN 20 MINUTES IN FRONT OF ME ( WE ARE FROM SAME STATE SO I WENT HIS HOME)
FO THE FULL STORY OF LG G FLEX UNBRICKING SEE THIS ( http://forum.xda-developers.com/lg-...nload-mode-t3059257/post59555140#post59555140)
SO THE MOST IMPORTANT THING IS TO SHORT THE TEST POINT CORRECTLY WITHOUT DAMAGING EMMC ( I WOULD ADVICE ALL OF YOU PLEASE ASK HIM BEFOR SHORTING MAY HE SHARE THOSE VIDEOS ON YOU TUBE )
FOR COLLECTION OF TEST POINT SEE THIS ( http://forum.xda-developers.com/hardware-hacking/hardware/collection-test-phone-t3048736 )
SOLUTION FOR ERROR DURING FLASHINGFOLLOW THIS GUIDE ( http://forum.xda-developers.com/lg-g2/general/lg-g2-cross-dll-device-model-fota-laf-t3003717 )
THERE ARE MANY GUYS WHO CLAIM TO FIX YOUR BRICKED LG PHONE BUT I DONT KNOW THE AUTHENTICITY OF THESE GUYS
TUNGKICK WHICH IS ALSO WHO UNBRICK HAS VERY BAD RECORD, I SEEN THE POST MANY GUYS CLAIM THAT HE STEAL PASSWORD AND DATA FROM THEIR PC AND TOOL HE USED INSTALL KEYLOGGER TO YOUR PC ( I AM JUST TELLING THE COMMENTS ON GUYS AND THEY ALSO UPLOADED SOME PIC FOR THE PROOF)
THANKS SO MUCH
THREAD UNDER CONSTURCTION ( I WILL UPDATE PICTURE FOR MORE DETAILS )
to be continue..........
Hi Guys, pls help me.
This is not the first time i tried to update firmware using KDZUpdater [KDZ_FW_UPD.exe] .
But this is the first time my device has been bricked.
During updating my firmware, i was in "Emergency Mode" and i received some error on KDZUpdater GUI Console.
As i was unable to move from "Emergeny Mode", i tried again to update firmware, but again i got some error.
I thought removing the battery will do some good, but i was wrong.
Now my mobile is as good as "BLACK BRICK".
It even doesn't detect in "Device Manager".
Note:
Before using "KDZUpdater", i had disabled "LG modems" from device manager.
Pls help me on this.
Sent from my TCL J636D+ using XDA Free mobile app
vcforums said:
Hi Guys, pls help me.
This is not the first time i tried to update firmware using KDZUpdater [KDZ_FW_UPD.exe] .
But this is the first time my device has been bricked.
During updating my firmware, i was in "Emergency Mode" and i received some error on KDZUpdater GUI Console.
As i was unable to move from "Emergeny Mode", i tried again to update firmware, but again i got some error.
I thought removing the battery will do some good, but i was wrong.
Now my mobile is as good as "BLACK BRICK".
It even doesn't detect in "Device Manager".
Note:
Before using "KDZUpdater", i had disabled "LG modems" from device manager.
Pls help me on this.
Sent from my TCL J636D+ using XDA Free mobile app
Click to expand...
Click to collapse
You have only one option.
You need to force your phone into qhsusb bulk mode by shorting test point.
What does that mean??
Will this be done through software or I need some special hardware or should I sent to LG service centre.
Pls guide
Sent from my TCL J636D+ using XDA Free mobile app
vcforums said:
What does that mean??
Will this be done through software or I need some special hardware or should I sent to LG service centre.
Pls guide
Sent from my TCL J636D+ using XDA Free mobile app
Click to expand...
Click to collapse
You need to open your phone and do short of some pins.
A guys named aftabalam8c2 has full tutorial video how to do this.
And he will help u.
I m posting his contact details in pm
I have no download mode, but rom still works fine. cant root and cant start into recovery.
I solved the QHUSB 9006 Method in ubuntu, but after filling the partitions, all is like before, still NO download mode.....
Lg g3 f460s no download mode nor flashboot
I have lg g3 prime.
Lg g3 f460s from koria, sk telecom.
I want to install a custom rom, but it failed and i havent kept backup of stock rom, so first it shows " secure boot error" then i again go to fastboot mode and by mistake flash wrong file at boot partition & recovery partition.
After that when i switch on my phone it shows secure boot error & after it 's switched off.
When i press vol+ and insert in usb , download mode dialog comes and after 5 to 6 seconds it switch off automatically.
Not any key combination work for recovery mode & fastboot mode.
Means my phone have not download mode and not fastboot mode.
Now what should i do for unbrick it.
Don't support with lg l65 D280g?
friend you help me with D280g lg? help me pliz
I have the g pro 2 with no download mode just lg logo what should I do?
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
SANJAYTHL said:
I have lg g3 prime.
Lg g3 f460s from koria, sk telecom.
I want to install a custom rom, but it failed and i havent kept backup of stock rom, so first it shows " secure boot error" then i again go to fastboot mode and by mistake flash wrong file at boot partition & recovery partition.
After that when i switch on my phone it shows secure boot error & after it 's switched off.
When i press vol+ and insert in usb , download mode dialog comes and after 5 to 6 seconds it switch off automatically.
Not any key combination work for recovery mode & fastboot mode.
Means my phone have not download mode and not fastboot mode.
Now what should i do for unbrick it.
Click to expand...
Click to collapse
Same here..have you found a fix yet?
daredavel said:
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
Same here..have you found a fix yet?
Click to expand...
Click to collapse
got the solution but can't find the apropriate files, i am showing the method, if you find the files let me know.
1. with willcracker board diag,
in that case you need chipset file for apq8084 (snapdragon 805), i have searched to many but cant find. in that case you need original (latest on your phone) firmware in .tot file and convert it in .mbn file. this you can do in willcracker. only the problem is apq8084 chipset files and latest firmware in tot file. you can find it in .kdz but cant get it in .tot file.
2. with qpst programme. (qfil programe)
in this method you need programmer file, rawprogram.xml & patch.xml of the same version phone (f460s) and yes original firmware.
you can find both program on google or xda.
if you got the appropriate files let me know and share with me.
thanks in advance.
Help
Cannot unbrick ls996 in q-bulk mode. tried everything...every site. Even tried to contact member mentioned in post. Im willing to work hard to unbrick, NOT looking for easy way...out...but im no phone technican by all means. Thanks!!!
I've got a E975 (Optimus G Intl) to unbrick here.
I've got it to fastboot mode, but I can't get the laf.img and dbi.img files (they are not in the .kdz or .dz files).
Can anyone give me a help?
Wrong ROM install in LG f460s
SANJAYTHL said:
got the solution but can't find the apropriate files, i am showing the method, if you find the files let me know.
1. with willcracker board diag,
in that case you need chipset file for apq8084 (snapdragon 805), i have searched to many but cant find. in that case you need original (latest on your phone) firmware in .tot file and convert it in .mbn file. this you can do in willcracker. only the problem is apq8084 chipset files and latest firmware in tot file. you can find it in .kdz but cant get it in .tot file.
2. with qpst programme. (qfil programe)
in this method you need programmer file, rawprogram.xml & patch.xml of the same version phone (f460s) and yes original firmware.
you can find both program on google or xda.
if you got the appropriate files let me know and share with me.
thanks in advance.
Click to expand...
Click to collapse
I have same issue wrong ROM installed on LG f460s and I have no download mode, no recovery, no fastboot no charging shown, no sign of life, just Qualcomm HS-USB QDLoad 9008 is shown in device manager when connect to PC.. I am searching APQ8084 folder to paste in boarddiag tool, Dear if you have found any other way to solve this issue please let me know. thanx in advance
power outage while flashing kdz on LG C660
Please help... I know my phone is a little outdated but I would still love use it for my daily routine . I'm in the middle of flashing the original firmware when the power outage happened. Now it won't power on at all. Been searching for days on what pins/components to short to force it into qhsusb bulk mode but no luck. I hope someone can help me...:crying:
tobitab said:
Please help... I know my phone is a little outdated but I would still love use it for my daily routine . I'm in the middle of flashing the original firmware when the power outage happened. Now it won't power on at all. Been searching for days on what pins/components to short to force it into qhsusb bulk mode but no luck. I hope someone can help me...:crying:
Click to expand...
Click to collapse
Which phone??
Anyone there" help me" i hav bricked my lg g2 f320k" wenever i connect my phone to pc" lots of partitions comes up
superguy19 said:
Which phone??
Click to expand...
Click to collapse
My phone is LG Optimus Pro C660...
---------- Post added at 01:32 PM ---------- Previous post was at 01:18 PM ----------
superguy19 said:
Which phone??
Click to expand...
Click to collapse
Ajayz said:
Anyone there" help me" i hav bricked my lg g2 f320k" wenever i connect my phone to pc" lots of partitions comes up
Click to expand...
Click to collapse
Have you tried checking on the 'Device Manager' what mode is the phone in 'Ports' section when connected to pc?
After that there are instructions in the first page for every mode. My phone doesn't show up and I needed it to force into
qhsusb bulk mode in order to proceed...
Bricked LG H440n
Hello guys I have bricked my LG H440n in an attempt of unlocking the bootloader. My phone doesn't get recognised by pc, I can only enter fastboot mode, but command like "fastboot erase aboot" are not working, it just says remote: "unknown command". Can anyone help me where can I find the pins to short on this phone?
Hello!
I would like to ask some help with my hard bricked G3 D855 16GB, i installed wrong rom
My english is not a best, and i dont dare to do anything. I have win 8.1. I dont know about Linux, and virtual PC.
I will very glad that someone can help me maybe via teamviewer. I also donate You. Please
If you think that You can help me maybe, please write me.
Hello Friends,
At last I figured out how to unlock bootloader, root & flash TWRP recovery !!
To achieve the above you should have some basic knowledge of adb, fastboot & flashing.
The usual warning... Try the following on your own risk, don't blame me if your device is dead, burnt or you lose your job because your boss couldn't contact you on your dead cell phone :laugh:.
Lets Begin !!
1) Download & install ADB-setup and Qiku Download Assistant.
2) Go to bootloader, switch off your phone and press and hold volume up button while connecting usb cable. When you see bootloader press volume up again to enter fastboot mode.
3) Go to device manager and you should see “Android or unknown” with a yellow exclamation mark under “other device”. You have to manually install fastboot driver here, just google it how to do it. You to have
go to C:\Program Files (x86)\Qiku\adb and select QK_ANDROID_ADB to install drivers.
4) Unzip the firmwares zip files.
5) Now to unlock bootloader we have flash the following firmware 6.0.018.P2.160720.QK8692.CPD but we have to force close Qiku flashing tool when flashing is at 1-2%. To do that open task manager on your pc before flashing and end Qiku flashing when the flashing is 1-2%.
6) Disconnect phone from pc and reconnect while pressing & holding volume up if you see completely black display it means now you have unlocked bootloader. Always refer to the device manager in your pc if your device is in fastboot mode as you would not see anything on the device display once you flashed the above mentioned firmware.
7) Go to the folder where you have the TWRP custom recovery. While in the folder press shift and right click and select “open command prompt here” from the menu. Copy “fastboot -i 0x1EBF flash recovery Qiku-TWRP-recovery.img” without quotes and paste in the cmd and enter.
8) Once Qiku TWRP recovery is flashed successfully lets boot the same from bootloader. While in the folder press shift and right click and select “open command prompt here” from the menu. Copy “fastboot -i 0x1EBF boot Qiku-TWRP-recovery.img” without quotes. Your device should boot in TWRP recovery.
9) In the TWRP recovery on your phone go to advance and select adb sideload and start the same.
10) Go to the folder where you have the SuperSu.zip and open command prompt here. Copy “adb sideload UPDATE-SuperSU-v2.78-20160905010000.zip” paste in the cmd and enter, without quotes.
11) Now if you wish to lock bootloader again then select reboot option in the recovery and select bootloader. Go to the folder where you have the emmc_appsboot.mbn file and open command prompt here. Copy “fastboot -i 0x1EBF flash aboot emmc_appsboot.mbn” without quotes and paste in the cmd and enter. This will lock the bootloader and you can always unlock the bootloader by following above mentioned instructions.
13) Copy “fastboot -i 0x1EBF reboot” in cmd and enter. This should reboot you phone.
14) If everything went well you should see supersu app in the phone. You can also check by an app called root checker from play store if you have successfully rooted your device.
When you have the unlocked bootlader there would be no display when you're in fastboot mode hence you have to check in device manager to ensure that the device is fastboot mode. Plus while booting or rebooting there would not be any boot animation but only the boot sound. This is due to the unlock bootloader.
Contents of the download link :
A) Stock firmware for the device v21. incase you have trouble and wish to flash stock firmware.
B) Firmware to unlock bootloader 6.0.018.P2.160720.QK8692.CPD.
C) 8692_I02 individual .img of stock.
D) adb-setup for adb & fastboot drivers
E) Stock aboot .img to lock bootloader.
G) Qiku download assistant.
E) Qiku TWRP recovery
F) SuperSu.zip.
Download link -- https://drive.google.com/drive/folders/0Bwy9M10qfmJLNElFemQwTTFXcTQ
Upgrade to the latest 360 OS, Android 6.0.1 and also activate VoLTE - https://forum.xda-developers.com/android/general/upgrade-qiku-cp8692i02-to-6-0-1-t3529352
Have fun :good::good:
Thanks! It's interesting method, but a little bit risky.
Zauq said:
Root Qiku Q Terra 808 (CP8692_I02), unlock bootloader & flash TWRP recovery
Click to expand...
Click to collapse
I want to change CP8692_I02 to CP8692, because i want up firmware android 6 Chinese Version
youngbi said:
I want to change CP8692_I02 to CP8692, because i want up firmware android 6 Chinese Version
Click to expand...
Click to collapse
You can change the same in buid.prop once you're rooted however you would not just be able to flash and boot Andoird 6 Chinese firmware on your device. I have tried the same but it does not work.
djking2 said:
Thanks! It's interesting method, but a little bit risky.
Click to expand...
Click to collapse
Not at all if you ask me as I have been playing with my device for past 8 months or so. I did hard brick my device at several occasions but was always be able to recover it. During those hard brick the device goes into fastboot mode on it's own or one can press and hold power key & volume up to force the device to go into fastboot mode which it always does.
To recover the device from hard brick it needs to be in fastboot mode whether locked bootloader or unlocked bootloader. If the bootloader is locked then the official tool can flash the stock firmware and boom... The device will be Alive again. Incase of unlocked bootloader it's just the matter of flashing the firmware .imgs through fastboot mode:good: or if you've taken backup in TWRP then just boot TWRP and restore your device.
One warning though... Do not try to flash any other OEM's firmware as I am not sure what would be the outcome as I have only tried our device OEM's firmware. Yes can try porting other custom rom to our device as it only involves flashing system.
i can confirm this mathod is 100% working thanks man
yogesh1970 said:
i can confirm this mathod is 100% working thanks man
Click to expand...
Click to collapse
:good::good::good::good::good:
please tell me why firmware 6.0.018.P2.160720.QK8692 is not booting
hello Zauq please help me
i have screwed modem.img of my qiku q terra .
i am able to write imei back but no signal because of screwed baseband.
i just flashed the baseband of moto x pure edition to enhance the lte signal and all this **** happens.
however i have backuped the modem 1 and modem 2 .img files via partion backup and restore . but forgot to backup modem.img
please provide me modem.img from your qiku phone so i can restore my signal
please :crying::crying::crying::crying::crying:
thanks
Zauq said:
yogesh1970 said:
hello Zauq please help me
i have screwed modem.img of my qiku q terra .
i am able to write imei back but no signal because of screwed baseband.
i just flashed the baseband of moto x pure edition to enhance the lte signal and all this **** happens.
however i have backuped the modem 1 and modem 2 .img files via partion backup and restore . but forgot to backup modem.img
please provide me modem.img from your qiku phone so i can restore my signal
please :crying::crying::crying::crying::crying:
thanks
Click to expand...
Click to collapse
I had backed up the modem using Flashfire app and I have uploaded the same. Check the given link in the original post, there is a new folder by Modem name.
Click to expand...
Click to collapse
hello Zauq thanks for ur reply. i flashed all the modem files but so signal
only u in this world can give breathe to my qiku
can you please give me QPST qcn backup made from qiku
it will repair my nvram files
please help
here is some info
download these driver
http://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/
and install QPST
http://www.androidbrick.com/download/qpst-2-7-430-latest-qfil-qualcomm-flasher/
1 Enable Usb Debugging .
go adb fast boot and type
adb shell
2 Then
su
3Give Root Permission In Your Device . then type
setprop sys.usb.config diag,adb
This Comand Will Open DIAG COM Port
then go device manager under port tab there is qualcomm diagnostic port
then go to C:\Program Files (x86)\Qualcomm\QPST\bin\QPSTConfig
there u see ur port
uder start client
go to soft download
than backup tab
backup ur qcn
please give me that file
it will fix my nvram files and give me signal
my 20k depends on ur qcn backup
thanks
yogesh1970 said:
hello Zauq thanks for ur reply. i flashed all the modem files but so signal
only u in this world can give breathe to my qiku
can you please give me QPST qcn backup made from qiku
it will repair my nvram files
please help
here is some info
download these driver
http://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/
and install QPST
http://www.androidbrick.com/download/qpst-2-7-430-latest-qfil-qualcomm-flasher/
1 Enable Usb Debugging .
go adb fast boot and type
adb shell
2 Then
su
3Give Root Permission In Your Device . then type
setprop sys.usb.config diag,adb
This Comand Will Open DIAG COM Port
then go device manager under port tab there is qualcomm diagnostic port
then go to C:\Program Files (x86)\Qualcomm\QPST\bin\QPSTConfig
there u see ur port
uder start client
go to soft download
than backup tab
backup ur qcn
please give me that file
it will fix my nvram files and give me signal
my 20k depends on ur qcn backup
thanks
Click to expand...
Click to collapse
I would love to help you but I hard bricked my device about 2 days ago while playing with emmc_appsboot.mbn . As you know to recover the device we need rawprogarm0.xml, patch0.xml etc and the stock rom doesn't contain any of the said files.
Fortunately, I am in touch with another Qiku user and I have already written to him about your requirement. I have also requested to him to respond to you on the xda forum itself. Let's wait for his response.
Besides, I was wondering if you know any ways to get the rawprogram0.xml, patch0.xml etc from a working Qiku for recovering my hard bricked device?? or any other method which can help?. Can Qdart tool help in anyway??.
I have searched Qiku Chinese forum but unable to find the required files.
Any help would be much appreciated :fingers-crossed::fingers-crossed::fingers-crossed: !!
Sure i ll send those files to you in a day or two!
yogesh1970 said:
please tell me why firmware 6.0.018.P2.160720.QK8692 is not booting
Click to expand...
Click to collapse
Not sure of the reason. I was just able to boot v109 which is 5.1.1 same as our current android version.
Help me with my hard brick phone qiku terra china version
Zauq said:
I would love to help you but I hard bricked my device about 2 days ago while playing with emmc_appsboot.mbn . As you know to recover the device we need rawprogarm0.xml, patch0.xml etc and the stock rom doesn't contain any of the said files.
Fortunately, I am in touch with another Qiku user and I have already written to him about your requirement. I have also requested to him to respond to you on the xda forum itself. Let's wait for his response.
Besides, I was wondering if you know any ways to get the rawprogram0.xml, patch0.xml etc from a working Qiku for recovering my hard bricked device?? or any other method which can help?. Can Qdart tool help in anyway??.
I have searched Qiku Chinese forum but unable to find the required files.
Any help would be much appreciated :fingers-crossed::fingers-crossed::fingers-crossed: !!
Click to expand...
Click to collapse
Help! l have qiku terra china after flash qk8692_l02 rom it is boot normal but l reflash to china qk8692_m02 so it not boot, black sreen, no led, only fastboot work. Help me !
cuongvietnam said:
Help! l have qiku terra china after flash qk8692_l02 rom it is boot normal but l reflash to china qk8692_m02 so it not boot, black sreen, no led, only fastboot work. Help me !
Click to expand...
Click to collapse
You mean you had a device QK8692_M02 and you flashed QK8692_I02 and booted normally but when you tried to go back to your QK8692_M02 it hard bricked??
Well my friend I am afraid but now you need to reflash QK8692_I02 to use the device and you might not be able to go back to your Chinese OS now. There was a similar case where this gentleman from Russia did the same thing to his Chinese Qiku device and he was not able to go back to Chinese OS now. There is something with the QK8692_I02 OS I guess.
I was able to boot v109 of Chinese OS on my QK8692_I02 and the v109 rom & the instructions are there on the given download link. I was in process of being able to use Chinese OS on my QK8692_I02 when I hard bricked my device . Now I need emmc image of Qiku to unbrick it and then I can continue my research and might be able to give solutions to the issue.
Let me know if you could get me that emmc image it would be just 200-300 mb file and the same you can upload it on google drive.
Zauq said:
You mean you had a device QK8692_M02 and you flashed QK8692_I02 and booted normally but when you tried to go back to your QK8692_M02 it hard bricked??
Well my friend I am afraid but now you need to reflash QK8692_I02 to use the device and you might not be able to go back to your Chinese OS now. There was a similar case where this gentleman from Russia did the same thing to his Chinese Qiku device and he was not able to go back to Chinese OS now. There is something with the QK8692_I02 OS I guess.
I was able to boot v109 of Chinese OS on my QK8692_I02 and the v109 rom & the instructions are there on the given download link. I was in process of being able to use Chinese OS on my QK8692_I02 when I hard bricked my device . Now I need emmc image of Qiku to unbrick it and then I can continue my research and might be able to give solutions to the issue.
Let me know if you could get me that emmc image it would be just 200-300 mb file and the same you can upload it on google drive.
Click to expand...
Click to collapse
Hi my friend! After l flash emmc in your folder it reboot to 360 company then load fastboot. l use qiku tool to flash stock rom but after complete it no boot sreen only black when plug in laptop it is bootloader coolpad driver. l can flash qk8692_m02 and qk8692_i02 but it not boot to logo and system! How to get it boot system ? Thank you!
somebody here can give me qcn backup from qpst tool from qiku ??
yogesh1970 said:
somebody here can give me qcn backup from qpst tool from qiku ??
Click to expand...
Click to collapse
Do You Still need it>?
thanks shubham cuongvietnam give me that file signal restored ok . but qiku models no gives full speed on gio networks where as RN3 pro is giving full
qiku 70 kbps
RN3 nd other models i tired 3 MBPS
any solution ??
yogesh1970 said:
thanks shubham cuongvietnam give me that file signal restored ok . but qiku models no gives full speed on gio networks where as RN3 pro is giving full
qiku 70 kbps
RN3 nd other models i tired 3 MBPS
any solution ??
Click to expand...
Click to collapse
Yes! You can use follow method:
1. Create a new APN
2. If you see on network icon is E not 3G that not support my EFS model(8692_m02) for you. So you can try a qcn file from same model.
i try to golbal rom to india rom,
try in mi flash tool via fastboot rom, but cannot flash , how to enter edl mode ?
Are u sure u provided the right location of the ROM and infact u downloaded the specific Fastboot ROM? You also need to boot into Fastboot mode on your phone, EDL is smth advanced and isn't required under such circumstances
In case you want the Fastboot ROM here it is:
https://miui.blog/redmi-note-7/violet-miui-10-v10-2-10-0-global-stable-fastboot-recovery/
It includes the recovery as well, use MiFlash to flash this. (Don't forget to select erase everything except data otherwise it will reset your internal storage)
How to enter edl mode
EDL mode isn't easy to enter ,It requires modifications (attaching a wire to a certain point inside the point) it isn't for normal or infact power users either. Just for the service centres in case all hope is lost.
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:
the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back
Where did you get the twrp from?
From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3
I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck
There were EDL files up, but apparently they were taken down for some reason.
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.
has anyone found the US EDL file yet?
Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.
I have not one, but two bricks. I bought one to unbrick the other, but the reverse happened. Using the EDL tool from this forum, I made a full and then an all backup and tried to use it to unbrick the other. No success. Now I cannot enter fastboot on either device, but both will enter EDL. I think at least one will fastboot if I can switch the active a/b slot.
Can the active a/b slot be switched via a command in the edl mode? Or is there another way to switch the active slot on a brick without fastboot access? Thank you
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
noobstyle1337 said:
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
Click to expand...
Click to collapse
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
There's no command to switch active slots that I know of and I've gone into the source on fh_loader.
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
The fact that you aren't getting a ZTE logo at all indicates that you do not have a mixed up slot a/b situation anyway. It probably means you need to fix your AOP files. Of course the original EDL tool doesn't really let you do that. If you have the US version you can use the tools I uploaded to target just the AOP files and try restoring them from your original backup... either the a or b slot one should work.
Make sure you keep your original ALL/FULL backups (both) from the EDL tool, they're probably 99% good and you'll be doing yourself a favor not to delete or modify them.
groundslug said:
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
Click to expand...
Click to collapse
You can only change the slots if you are in Fastboot. You have doing it wrong ... if you have an A2020G you can flash the firmware ... if you have the A2020u version then you should ... flash the correct one
so in itself quite simple .... flash edl firmware and then unlock .. then you boot into the fastboot mode and then you have to use these lines
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then
fastboot --set-active=a
in any case you have to unlock to access the fastboot menu
then you should be able to boot
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
remember to flash Android 9 edl firmware because otherwise the unlock won't work
---------- Post added at 04:47 PM ---------- Previous post was at 04:39 PM ----------
also remember that some firmwares have to be in the flash folder or in the backup folder if it doesn't work
bobthenormal said:
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
Click to expand...
Click to collapse
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
groundslug said:
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
Click to expand...
Click to collapse
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
bobthenormal said:
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
Click to expand...
Click to collapse
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
groundslug said:
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
Click to expand...
Click to collapse
Just replying real quick since I have a min and I saw a few things you can try... 1. make sure you're installing twrp itself with the zip after you boot into it with fastboot, 2. use the two flags when you write vbmeta just in case (I forget them but one is dm verify and the other is no verity, should be in the original LOS16 thread) and 3. try the fix bootable partition tool from my tools after you install. the LOS16 image has a similar problem as all other images that it has a specific slot it works on (B I think) so if you end up installing and trying to boot it from the other slot it locks into a fast bootloop. Don't bother installing the addons until LOS is booting, so just do a reboot to system after you flash it, fix bootable. If it doesn't boot then it has to be something I'm not thinking of. Goodluck!
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
groundslug said:
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
Click to expand...
Click to collapse
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Rise55Chrom said:
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Click to expand...
Click to collapse
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
groundslug said:
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
Click to expand...
Click to collapse
Phenomenal! Best advice, I have received... Thank you so very much. You hit it right on the head. I'll be sure to fill ya in asap when I have the time to get after it. Appreciate you.
bobthenormal said:
EDL tool
Click to expand...
Click to collapse
Hello, where can I find this program? EDL tool