what qfil partions should not be flashed from att and others? - LG V40 Questions & Answers

hi all which specific partions should not be flashed via qfil so i dont loose my imei and anything else seriously important? but also have a bootable device. i know abl and boot a and b dont need to be touched bootloader and twrp.

Nobody knows? Really?

to avoid losing imei and s/n don't flash over ftm, modem, modemst1, modemst2, fsg.
I have no idea what u mean by "I know abl and boot a and b don't need to be touched bootloader and twrp"...

Related

[Q] MOTO X Bricked

My moto X has a problem , let me show you the log file first
-Unlocked using motorola's website
-Flashed TWRP recovery
-Created a backup
-[MISTAKE 1]Wiped using advanced wipe
-Everything including the backup I created got wiped ,with no OS
-Mounted and tried to install CyanogenMod 11
-[ERROR 1]This rom is supported by ghost xt1053(my model number) ,and your device is . (like just a dot) //Cannot install the zip file
-[BRICKED]
-Then I searched what to do ,downloaded "TMO_213.44.1.ghost_row.Retail.en.US" firmware
-Using fastboot ,I flashed the firmware using the following commands
After downloading the image for your device:
Unzip the image.
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock​
-It showed an error During locking the device
-The phone finally started working [UNBRICKED?]
-My sim card wasnt detecting
-So I searched more ,and checked my IMEI
-Dialed *#06# and got "IMEI 0"
-For confirmation ,I went again to settings->about->Status
-Everything was fine except "IMEI 0",and "IMEI SV 00"
-I couldnt find anything online except changing my IMEI ,which is ,one: illegal and two: not possible since I do not have Engineering mode app in my phone
-Headed over to the service center and they told me that my motherboard is gone ,you have to pay 291.050 US Dollars to change it
-But if the motherboard is gone ,how can my phone work ?
Here is my question to you guys ,what should I do ? Can I do anything to get my phone working again ? Please help me as I am not using a phone ,and I really need to use this one .
Thanks in advanced
Sorry for my bad English
I think there was a step you missed there when flashing:
fastboot flash modem NON-HLOS.bin
and it's better to use Motorola fastboot aka mfastboot instead of regular old fastboot. if you don't have it just Google for it.
for a more complete guide see option 5 on this site: http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Also there is absolutely no need for that last step you tried, fastboot oem lock... that will relock your bootloader which is totally unnecessary. you don't need it for otas or anything else, and as for warranty your phone is already flagged as unlocked and relocking it won't change that.
dtg7 said:
I think there was a step you missed there when flashing:
fastboot flash modem NON-HLOS.bin
and it's better to use Motorola fastboot aka mfastboot instead of regular old fastboot. if you don't have it just Google for it.
for a more complete guide see option 5 on this site: http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Also there is absolutely no need for that last step you tried, fastboot oem lock... that will relock your bootloader which is totally unnecessary. you don't need it for otas or anything else, and as for warranty your phone is already flagged as unlocked and relocking it won't change that.
Click to expand...
Click to collapse
Okay so I tried the whole process with "fastboot flash modem NON-HLOS.bin" ,and restarted ,but my IMEI is still showing 0 .
I was using mfastboot from the start. Any help ?
Guys please help me ,I know its torturous for you'll ,but I'm helpless right now
dkaushik95 said:
Guys please help me ,I know its torturous for you'll ,but I'm helpless right now
Click to expand...
Click to collapse
It's OK dude first step is to relax and realize that losing imei is not a new thing, it's happened to countless others. what that means is there should be a huge amount of info on what people have tried and what worked and didn't work. You'll find all the info by using Google search and changing keywords.
some keywords to try:
fastboot imei
Motorola recover imei
Restore imei
imei 0
recover imei
efs imei
and so on. if you read through them and feel you're not up to it, or if you try everything and nothing works, you have another option maybe:
Take it in / send it in for repair to Motorola or other (certified) repair shop
good luck.
BTW: The original box the phone comes in has your imei written on it. otherwise you can try the fastboot getvar method but that might or might not work.
Can you try to falsh using RSD lite it Completly safe and esay process . Try it once
MAhesh
Mahesh8348 said:
Can you try to falsh using RSD lite it Completly safe and esay process . Try it once
MAhesh
Click to expand...
Click to collapse
I tried everything including RSD Lite and several other methods ,and I've given it to Motorola . I hope they fix it
[UPDATE]
I sent my phone to the service center ,and they replaced the phone with a new one !
Everything is back to normal ,thanks for the support guys ,really appreciate it

[guide] workaround - no network / imei = 0 after flashing custom rom

Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
 @Sri Datta for discovering this workaround
GZOSP and Validus Devs
 @premaca and GZOSP/ Validus devs
Thanks and best regards.
gebcruz06 said:
Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
@Sri Datta for discovering this workaround
GZOSP and Validus Devs
@premaca and GZOSP/ Validus devs
Thanks and best regards.
Click to expand...
Click to collapse
the 4g network here does not work, I've tried several tutorials
juniorhonorato1986 said:
the 4g network here does not work, I've tried several tutorials
Click to expand...
Click to collapse
What problem do you have?
No imei, no 4g, what have you done
gebcruz06 said:
Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
@Sri Datta for discovering this workaround
GZOSP and Validus Devs
@premaca and GZOSP/ Validus devs
Thanks and best regards.
Click to expand...
Click to collapse
Thanks for this. Wish it was up when it happened to me. I was ready to try and take back the phone while it was dead and hope they didn't try to turn it on. Lol. I loose my 4g everytime and 3g sometimes after flashing. In theroy I can do this after flashing a custom rom to get my 4g back right? I hope so cause I'm gonna try it. Once again, thanks for this!
always6s said:
Thanks for this. Wish it was up when it happened to me. I was ready to try and take back the phone while it was dead and hope they didn't try to turn it on. Lol. I loose my 4g everytime and 3g sometimes after flashing. In theroy I can do this after flashing a custom rom to get my 4g back right? I hope so cause I'm gonna try it. Once again, thanks for this!
Click to expand...
Click to collapse
You don't need to do all that - just flash stock (remove SIM before flashing and pop it back in after you've booted to stock).
Phazmos said:
You don't need to do all that - just flash stock (remove SIM before flashing and pop it back in after you've booted to stock).
Click to expand...
Click to collapse
On my experience, I have flashed every stock ROM for xt1805 there is as it is my model, flashed and reflashed modems, cleared modemst1 and modemst2 to no avail. IMEI=0. I removed​ sim before flash and popped it after booting, but still same result. It went on for almost 2 weeks. One thing I noticed is that the modem version becomes MSM8953_27.36.07.41u while the version in the xml file in stock zip is ***.41R. I don't​ know what that means, I flashed the latest firmware for xt1805. I am thinking that the letter stands for your region (u=US, e=EMEA, etc). My phone now after it has regai ed IMEI is ***.41e. Maybe it's a mismatch of modem since the bad flash that wrecked my phone and it changed something​ that makes it swtich to the right bands. I'm not quite sure though.
gebcruz06 said:
On my experience, I have flashed every stock ROM for xt1805 there is as it is my model, flashed and reflashed modems, cleared modemst1 and modemst2 to no avail. IMEI=0. I removed​ sim before flash and popped it after booting, but still same result. It went on for almost 2 weeks. One thing I noticed is that the modem version becomes MSM8953_27.36.07.41u while the version in the xml file in stock zip is ***.41R. I don't​ know what that means, I flashed the latest firmware for xt1805. I am thinking that the letter stands for your region (u=US, e=EMEA, etc). My phone now after it has regai ed IMEI is ***.41e. Maybe it's a mismatch of modem since the bad flash that wrecked my phone and it changed something​ that makes it swtich to the right bands. I'm not quite sure though.
Click to expand...
Click to collapse
Fwiw - I'm in the us, my baseband is 40e, so I think you might have the us firmware.
Where did u get the firmware? And how are you flashing it?
Edit , just noticed your baseband is 41e , disregard the above - but - do answer the questions.
Phazmos said:
Fwiw - I'm in the us, my baseband is 40e, so I think you might have the us firmware.
Where did u get the firmware? And how are you flashing it?
Edit , just noticed your baseband is 41e , disregard the above - but - do answer the questions.
Click to expand...
Click to collapse
Q: Where did u get the firmware?
A: I got the firmware I am using here:
https://androidfilehost.com/?fid=889964283620776326
Q: And how are you flashing it?
A: I am flashing it by following the sequence in flashfile.xml. I put it in a proper syntax in notepad and paste it line by line.
gebcruz06 said:
Q: Where did u get the firmware?
A: I got the firmware I am using here:
https://androidfilehost.com/?fid=889964283620776326
Q: And how are you flashing it?
A: I am flashing it by following the sequence in flashfile.xml. I put it in a proper syntax in notepad and paste it line by line.
Click to expand...
Click to collapse
Sounds like the flash procedure is correct , as long as each step flashed successfully.
I believe you mentioned flashing every firmware available - including from firmware center?
If so - all I can say its contact your carrier - if it was ok out of the box, and you've flashed the original firmware, it should work again.
Good luck!
not woring jio sim
umair09 said:
not woring jio sim
Click to expand...
Click to collapse
If u went to service centre for fixing volte then pls share Ur experience here
Your link to my twrp stock zip 404's, just saying.
I am following this so far, but i can't figure out where you got those files from:
fastboot flash modemNON-HLOS.bin fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Are they from the ROM you decided to be your Stock ROM? Because the Custom ROM doesn't contain those. And i am not sure i want to put just some random ROM Files in there...
Thanks for the help you provided with this Thread so far anyway =)
Edit: I tried it with the Files from the Stock ROM and it actually worked =)
Phazmos said:
You don't need to do all that - just flash stock (remove SIM before flashing and pop it back in after you've booted to stock).
Click to expand...
Click to collapse
I got my 4g back but I still lose it when I flash a custom ROM. I've tried flashing the room then restoring my efs. Nothing. Taking out sim card for flash then reinserting it. Nothing. I can get 3g just fine in all roms but 4g only in stock.......
always6s said:
I got my 4g back but I still lose it when I flash a custom ROM. I've tried flashing the room then restoring my efs. Nothing. Taking out sim card for flash then reinserting it. Nothing. I can get 3g just fine in all roms but 4g only in stock.......
Click to expand...
Click to collapse
When will u install custom rom.. after that just do 1 thing open bootloader menu and paste this commonds.... 1. fastboot erase modemst1
2. fastboot erase modemst2
Tadaaa you get 3g and 4g network
Thanks..Successfully did But VOLTE is not working...
gebcruz06 said:
Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
@Sri Datta for discovering this workaround
GZOSP and Validus Devs
@premaca and GZOSP/ Validus devs
Thanks and best regards.
Click to expand...
Click to collapse
Thanks..Successfully did But VOLTE is not working.
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
umair09 said:
not woring jio sim
Click to expand...
Click to collapse
Hi i did successfully ,network is coming but my jio sim is not working..i mean i am unable receive or make the calls ...what should we do...please reply immediately..
I have tried everything. Restoring efs. Flash non hlos. Erasing modemst. I cannot get my 4g back after flashing custom ROM. So so aggravated. 3g sucks so I can't run a rom that won't do 4g. If any new info comes up someone please let me know.
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Kdemwa said:
When will u install custom rom.. after that just do 1 thing open bootloader menu and paste this commonds.... 1. fastboot erase modemst1
2. fastboot erase modemst2
Tadaaa you get 3g and 4g network
Click to expand...
Click to collapse
Tried that. Nothing still just 3g.
Always6z said:
I have tried everything. Restoring efs. Flash non hlos. Erasing modemst. I cannot get my 4g back after flashing custom ROM. So so aggravated. 3g sucks so I can't run a rom that won't do 4g. If any new info comes up someone please let me know.
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Tried that. Nothing still just 3g.
Click to expand...
Click to collapse
Try *#*#4636#*#*
Sri Datta said:
Try *#*#4636#*#*
Click to expand...
Click to collapse
Then what?
I am.coming from regular Moto G5 where this was a problem too. The solution over there was, if you are on a custom 8.x oreo rom, you needed, before going to stock, flash 32 bit twrp and a 32 bit rom. Then, after first boot, you could go back to stock with no problems. Just got this one and not planning to move from stock as I feel official oreo is right at the corner, but give it a try like this and report back if you were able to

Lost imei please help me guys for 1 month i am using my phone as paper weight :((

Guys i lost my imei 1st im downgrading from pixel rom to stock via fastboot then i recoverd it via rr rom flashing but there is no volte and lte so i just backed up my efs,then flashed presist got from xda thread after that lost all restoring efs partition showing 0000000001 as imei ( nothing works ((
anyone here helping minded i will share efs can if that get worked then i can conform that is presist issue please help me
will you try my persist.img and modem.img files. I can upload if you wanna flash 'em
5P4RT0N said:
Guys i lost my imei 1st im downgrading from pixel rom to stock via fastboot then i recoverd it via rr rom flashing but there is no volte and lte so i just backed up my efs,then flashed presist got from xda thread after that lost all restoring efs partition showing 0000000001 as imei ( nothing works ((
anyone here helping minded i will share efs can if that get worked then i can conform that is presist issue please help me
Click to expand...
Click to collapse
I've backed up persist.img modem.img modemst1.img and modemst2.img from NPSS26.116-61-8 firmware
sachinsmac said:
I've backed up persist.img modem.img modemst1.img and modemst2.img from NPSS26.116-61-8 firmware
Click to expand...
Click to collapse
yes of course gemme the link
I'm unable to post link bro
---------- Post added at 04:27 AM ---------- Previous post was at 04:14 AM ----------
Code:
fastboot erase persist
fastboot erase modemst1
fastboot erase modemst2
fastboot flash persist persist.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash modem modem.img
some changes happens but still no imei
previous 000000001... now 0034001 something
https://pasteboard.co/HuwtrgU.png
Recover IMEI via Chamelephon app.
I probably know a simple fix for that!
I too lost my IMEI of my smartphone so what I did was -
· Root your smartphone.
· Install Chamelephon app from Play Store. https://play.google.com/store/apps/details?id=com.cryptotel.chamelephon
· Open the app and grant root access.
· Now enter both IMEI into the text box. If you don't know your IMEI, just check your phone's retail box where the pricing and all other stuff is mentioned. There your IMEI should be mentioned. (Or you can just enter any random IMEI if it's legal)
· Now tap the reboot option.
· Your phone will now reboot and BOOM ?... your IMEI should come back.
Hope it works for you.
(Tested on my Micromax Unite 2.)
Don't use things not designed for your device

Bootloader causing brick only when rebooting from b to a.

Can go to BL and "fastboot set_active a" then reboot to go from b to a. No problems switching a to b in TWRP or BL by set_active command. The real problem is that if I try to update and forget to go to BL I get bricked and have to run blankflash.bat.
Which takes me to a locked BL where I can't boot TWRP via fastboot...
I thought I got out the first time but I have not been able to recover without flashing stock which wipes or makes data partition unrecoverable.
Anyway... WTF did I do to BL to make it detect that it is locked when I have unlocked, and never relocked BL.
Any insight would be greatly appreciated, thanks.
What are you updating to? There was a run of 15.1 ROMs that would result in bricks. It's fixed now- so if you are trying to flash a really old rom, try flashing the latest.

V40 has unlocked bootloader and can fastboot, but is otherwise bricked. Any hope for TWRP?

Having trouble installing TWRP.
I can fastboot and attempt:
`fastboot boot TWRP.img`
But it either fails or "succeeds" and then just hangs on the LG Logo.
`fastboot flash recovery TWRP.img`
-returns an error that recovery_a doesn't exist.
`fastboot flash abl_a TWRP.img`
-returns "Volume is Full"
Any ideas what I may be doing wrong?
Device is an ATT LG V40 with the V35 Engineering Bootloader if that helps.
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
The only thing about using fastboot is you want to save the original boot_a image first. At&t doesn't make their kdz available and if u want /need to go back to stock u need to save it first.
After flashing it (either way), you need to immediately go to recovery, don't boot the device, u have to format data and reboot to recovery and then flash magisk and no verity zip. Otherwise a backup of your data won't work as it will be encrypted.
just one point, don't every flash something to a partition when yer not sure what yer doing. The abl partition is only about 1 meg in size, it's the 'android boot loader'. You could, if unlucky, flash something wrong for that partition and end up overwriting the partitions that are next to it, and essentially (just about) brick the device.
cheers
AsItLies said:
You don't say if it's at&t pie or Q. Let's assume it's Q 30b?
Click to expand...
Click to collapse
Sorry! It's Pie.
AsItLies said:
Follow this link for the bootable partition with twrp already injected. You can either use qfil to flash it, or more easily since u have fastboot, just do fastboot flash boot_a the_name_of_the_file.img.
Click to expand...
Click to collapse
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
sharpienation said:
Sorry! It's Pie.
This gives me the following:
Writing 'abl_a' FAILED (remote: 'Errorflashing partition :Volume Full')
I receive a similar message for `abl_b`, `recovery`, and `boot_a`
If I attempt flashboot boot the_image.img then I can get a success message on the fastboot-side and the phone reboots, but once again just to stick at the LG V40 screen.
Click to expand...
Click to collapse
Wow, so I don't think you understood some things. First, stop trying to flash an image to the wrong partition then what it's for. It is NOT for abl_a, and it is NOT for recovery (there is no recovery partition on a treble phone). STOP DOING THAT.
and second, because that boot_a (ONLY!!!) partition is for Q, as I said, you need one for Pie, and shouldn't even be trying to use it anyway.
and third, you can't fastboot boot these boot/twrp images, they have to be flashed to the partition and then you have to boot to recovery immediately after (don't try to boot the phone).
So if you can't flash the image with fastboot then the only option would be to use qfil, again, be sure to back up the original image first.
I'll look around and see if I can find one for Pie. We may have to create one if it's not around.
cheers
Just checking, but u do know how to use qfil yes? And, how did u get fastboot on the device? Using qfil I'm guessing? and you deleted laf_a? or the engineering abl?
This info is important because 1) the fastboot you get when simply erasing the laf_a is not as powerful and full featured as the engineering abl. The actual capabilities of the (laf_a erased) fastboot varies by OS variant, but some of them are basically worthless.
2) you'll have to be able to use qfil to get this accomplished.
let me know and we'll go from there.

Categories

Resources