Database Info

Bricked when returning to stock (No command)

Hey guys,
decided to flash the latest DBT Firmware via Odin to get back to stock completely. (G930FXXU3ESA3)
After flashing the firmware through Odin the phone reboots and then installs an update and erases data (blue background).
After a second reboot I end up with a blue screen and the simple error: "No command".
I can not get into recovery, as I end up with the same error message wether booting into recovery or the system.
I CAN however get into downloadmode and flash twrp, after that I can boot into system but I want to keep the whole system vanilla, without TWRP.
Installing TWRP keeps the device encrypted, no matter what. I can wipe, then install no-verity-encrypt and as soon as I reboot the device is encrypted again.
Ive tried: Different Firmware Version (December 2018), 3 different cables, different odin versions.
Edit: attached an Image of the message that Pops up after about 30sec on the no command screen.

Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.

FLASH No verity.zip
VIA TWRP
https://forum.xda-developers.com/attachment.php?attachmentid=4490455&d=1525176288

cooltt said:
Ok, so your device will take UK Unbranded BTU firmware. You can get it from a few sources and even direct from Samsung servers with Samtool.
Forget all that flashing TWRP and non verify nonsense, if you can get into download mode you can flash firmware, obviously make sure the firmware downloaded is not corrupt etc.
I've used Odin V10 -13 to flash BTU and every version flashed it correctly. Sometimes you do get that "installing update" and then "erasing" but that's fine just leave the phone for a few minutes it should eventually reboot normally.
Click to expand...
Click to collapse
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP

Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)

Scorpionea said:
Did u try in Odin nand erase and repatition option? If not try it ( make sure u have pit file extracted or downloaded from the net)
Click to expand...
Click to collapse
Did a efs backup through TWRP just in case, then flashed the latest DBT firmware with nand erase -> still the same problem.
I can only guess that this was caused by using a backup from another phone back when Oreo came out, this probably messed something up really badly. Very weird, im kinda lost.

Killuminati91 said:
Just tried the latest BTU with Odin 3.13.1, same problem. Its reboots into the blue screen, applying system update to about 32% and then switches to "Erasing". After about 1min it reboots, shows "Installing System update" for a second and I end up with "No command" again. And from there on it just constantly reboots into the "No command" screen.
This seems like the same problem. I can not enter stock recovery to wipe though...
Things ive tried so far:
- Different firmware Versions (all oreo since downgrading is impossible)
- Formating with pit files
- Different Odin Versions
- Unplugging and replugging the battery
- Installing TWRP, wiping data and then installing stock recovery through TWRP
Click to expand...
Click to collapse
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.

cooltt said:
Ok, from the no command screen do the following.
Hold power until phone switches off, then press power+home+volume up. The phone should now boot into original recovery screen. Select "wipe/factory reset" and then reboot device. Job done.
Click to expand...
Click to collapse
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.

Killuminati91 said:
Tried that, recovery is simply not working. If I hold vol - + power + home to restart and switch immediatly to vol + I boot into the usual blue screen with No command. I even tried unplugging the battery to shut off the phone and boot into recovery from there but that is not working either. Sorry should have stated that more clearly.
If I flash TWRP however, I can easily boot into TWRP with the recovery button combo.
Click to expand...
Click to collapse
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.

cooltt said:
Ok it's a tricky one so one more thing I would suggest is download and install Samsung smart switch on your PC, place the phone in download mode plug it into lap top and choose emergency software recovery in smart switch
Edit. I just remembered before that try this button combo from the no command screen volume up+volume down+power.
Click to expand...
Click to collapse
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.

Killuminati91 said:
Hmmh. Searched a lot for the version that still supported emergency recovery. (which seems to be 4.0). If I go into download mode, start smartswitch and try to use emergency recovery there is nothing for me to select.
Volume up + down and power gives me the terminal like look which I attached in the first post with all those error messages.
Click to expand...
Click to collapse
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.

cooltt said:
The EFS partition is corrupt or blank, it's the only logical explanation but the TWRP back up should solve that, without looking at it my self and running some commands i cant help your further.
Click to expand...
Click to collapse
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.

Killuminati91 said:
TWRP backup was created after I ran into problems though. Ive checked some more things and it seems like the serial number that is displayed (in combination rom and or Z3X) is not the same SN that is printed on the back of the phone. Could this be related? And how would I go about changing it back to the one on the sticker? The IMEI is correct.
Had someone who was more into the whole thing contact me here but when I wanted to "donate" only half of what he was asking he refused to help me.
Click to expand...
Click to collapse
Thats because he's a scammer. Never donate to get your phone fixed! Donate to Rom developers and things you like but never to get the phone fixed, they're usually lying.
The serial number should be the same ON the phone as displayed IN phone. Tell me the story about the phone, how did you get it? what region? where are you? what firmware was installed? Can you still flash a ROM with TWRP? Can you check OEM unlock?
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
nmnmnmnmnmnmnmnmnm

Pretty sure he was just trying to remote repair for a price, which is not allowed on XDA. Would obviously donated on my own if he actually fixed it.
Bought the phone unlocked directly from a provider (simply - germany - dbt - g930f) back in 2016. Tripped kn0x after a few months, installed a few custom roms until Oreo came out.
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Since then I had constant connection problems, weak internet connection, dropped calls and so on.
Broke my screen and then decided to repair it myself. Bought a new frame, screen, battery, usb-port, earpiece and vibrator - managed to assemble all of that.
I can install all latest official firmwares (bootloader 3) through Odin. If I leave it at that I have no recovery and end up with the initially shown screen and "No command".
If i install TWRP from there and simply root with magisk or apply dm-verity-fix I can boot into the stock firmware with everything working.
I can also install ROMs. Just going completely vanilla is not possible anymore. OEM Unlock is checked, USB debugging works.
Edit: What is also astounding: If I flash version DBT-G930FXXS3ERHD-20180918145033 (oldest possible Oreo Version) I can enter recovery and do a factory reset and wipe cache.
If I do that however I am stuck at the Galaxy S7 Logo, not even bootlooping.

Killuminati91 said:
This is where I messed up I think: I used a TWRP backup from someone else that he had shared here on XDA, which probably included his /efs too.
Click to expand...
Click to collapse
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.

cooltt said:
awww.....come on man you should have said this at the start! Of course you can't use someone else's EFS data, it's unique to your handset. Custom Rom's patch some but not all EFS data that's why they work and in your case that's why Stock firmware isn't going too.
Anyway if this is the problem (and i suspect it is) there is only one way to fix it with Octopus box which can write all the important info back onto the EFS. Your IMEI, Serial, Mac address etc. Odin reads the info from the EFS prior to nand write start, if the phone serials don't match it will always fail at some point.
You can install a custom via twrp but it will not work correctly due to EFS data miss match. Octopus box is your answer.
Click to expand...
Click to collapse
Dang it. Thank you! Off to find someone who can do this via remote access or in Berlin.

Same situation right now with my S7. Damn.

Hi everyone. Did you guys find any way to resolve this issue? i have exactly the same issue here.. but in my case i cannot use twrp cuz i never installed it before... the issue happened right after i tried to enter the recovery mode by pressing the buttons...
my wife's galaxy s7 touch screen was acting weird and i tried to get into the recovey mode..which is pretty muh easy to do... but once i tried the no command msg came up and now i have exatly the same case as the guy that opened this thread....also done everything hes done....any clue about this anyone?
id appreciate some help..
thanks in advance
Diego Boffa

Anyone?

I have exactly the same error with "fail to open recovery_cause(No such file or directory)#
My Tablet is now stuck with a blue "android dead" screen saying "No command".
My history to disaster:
- i've recovered a "broken" Samsung Tablet (sm-T585) with corrupted file system via
* Download Mode works -> TWRP install -> Mount option -> use ADB to recreate EFS partition -> re-flash stock image (android 8) with odin
- device works fine
- then i've noticed it can only be used with a certain cell provider (o2)
- then i've tried to flash an older version of the stock rom (android 7) due some problems in Android 8 (often some slow downs while operating)
- this doesn't work, the flash don't start
- therefore nothing should be happend, or?
- then i've can't get anymore in the stock recovery to wipe all data
...therefore the mess began:
* i can't flash TWRP anymore
* i can't flash stock recovery anymore
* i only can get into download mode
* i can only flash a certain rom type successfully (green PASS within odin), but with the final stuck with boot loop, with the mentioned blue screen
* other rom version can't flashed
I hopefully ask you guys here, if anyone can help me?
Any help would be very appreciated ...

no imei and no sim card detection

My Samsung galaxy a8 has no IMEI number and the aim card does not get detected at all and therefore no network as well although the sim card does work. There is no OEM unlock in developers option and therefore I have no idea how to proceed on fixing. The guides on how to use Odin are not clear as I am quite a noob at this and I'd rather ask for help before risking my secondary phone.
Assistance in any way would be helpful

Ricky Blaze said:
My Samsung galaxy a8 has no IMEI number and the aim card does not get detected at all and therefore no network as well although the sim card does work. There is no OEM unlock in developers option and therefore I have no idea how to proceed on fixing. The guides on how to use Odin are not clear as I am quite a noob at this and I'd rather ask for help before risking my secondary phone.
Assistance in any way would be helpful
Click to expand...
Click to collapse
Odin can be intimidating, but its not bad at all. First thing when using Odin is to make sure your phone has a high percentage of battery charge. This is important because if the battery in your phone dies and the OS end up being corrupt, there is no way to charge it and its now a paperweight unless its taken apart and either you replace the battery, or have it charged by some other means. This is a very unlikely scenario, but if you arent keenly aware of that pitfall, you could easily fall into it. Anyways, charge your phone fully, put it into download mode, connect it to a computer, if using windows 10 the drivers should automagically install, if any other version of windows, there is a tutorial on how to system wide install ADB in 10 seonds (and yes, its literally a 10 second process and its slick as hell), put the img.tar file in the ap section of odin, uncheck auto-restart, then click start.
the img.tar file you need is available at sammobile.com/firmwares and will be almost 2 GB in size and will take FOREVER to download. So dont put your phone in DL mode and think you can download the file in a resonable amount of time, have the img.tar downloaded first. Doing this will trip an alarm called the "knox e-fuse" but will probably make the device work as is should.
I assume that youve also done a factory reset
also, the OEM unlock option will nto show up until you leave the phone on for 168 hours without rebooting it. so, turn it on, put it in airplane mode to save battery, put it in a drawer and lat it sit for exactly 7 days without rebooting it and making sure the battery doesnt die as that counts as a reboot and the oem unlock option will show up in the dev options. The oem unlock showed up for me almost immediately after i flashed the stock firmware in Odin, no 168 hour wait period required

Thank you so much for this but if I may just ask to clarify what I need to do.
1 make sure battery is fully charged
2 download correct img.tar file
3 factory reset
4 boot into download mode
5 flash img.tar in ap and uncheck auto restart
6 leave in a draw for 168 hours with no reboots

youdoofus said:
Odin can be intimidating, but its not bad at all. First thing when using Odin is to make sure your phone has a high percentage of battery charge. This is important because if the battery in your phone dies and the OS end up being corrupt, there is no way to charge it and its now a paperweight unless its taken apart and either you replace the battery, or have it charged by some other means. This is a very unlikely scenario, but if you arent keenly aware of that pitfall, you could easily fall into it. Anyways, charge your phone fully, put it into download mode, connect it to a computer, if using windows 10 the drivers should automagically install, if any other version of windows, there is a tutorial on how to system wide install ADB in 10 seonds (and yes, its literally a 10 second process and its slick as hell), put the img.tar file in the ap section of odin, uncheck auto-restart, then click start.
the img.tar file you need is available at sammobile.com/firmwares and will be almost 2 GB in size and will take FOREVER to download. So dont put your phone in DL mode and think you can download the file in a resonable amount of time, have the img.tar downloaded first. Doing this will trip an alarm called the "knox e-fuse" but will probably make the device work as is should.
I assume that youve also done a factory reset
also, the OEM unlock option will nto show up until you leave the phone on for 168 hours without rebooting it. so, turn it on, put it in airplane mode to save battery, put it in a drawer and lat it sit for exactly 7 days without rebooting it and making sure the battery doesnt die as that counts as a reboot and the oem unlock option will show up in the dev options. The oem unlock showed up for me almost immediately after i flashed the stock firmware in Odin, no 168 hour wait period required
Click to expand...
Click to collapse
Hey I flashed everything as you said but nothing worked out I still have no IMEI number and no service/signal

Ricky Blaze said:
Hey I flashed everything as you said but nothing worked out I still have no IMEI number and no service/signal
Click to expand...
Click to collapse
Seems like your EFS folder is corrupted
Since your baseband is showing as unknown
Found something about this here
https://www.technobezz.com/fix-samsung-galaxy-unknown-baseband-version/

Dantar0 said:
Seems like your EFS folder is corrupted
Since your baseband is showing as unknown
Found something about this here
https://www.technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
Click to expand...
Click to collapse
Thanks seems like both the methods mentioned require root and I'm still on the prenormal stage

Ricky Blaze said:
Thanks seems like both the methods mentioned require root and I'm still on the prenormal stage
Click to expand...
Click to collapse
try leaving it on for 168 hours and the oem unlock option will show up. When it does, toggle it and you should be able to root it. When i flashed the stock firmware myself, the OEM unlock toggle showed up within 48 hours, so you might not have to wait that long. Charge it up and let it stay on without rebooting it and check it every day after work

So I got the OEM unlock,flashed twrp,flashed root
But now when trying to use efs professional it ends at checking the busy boxy with the error message "busybox applet "find" not found in this binary"
I've tried uninstalling busybox, reinstalling trying to use magisks busybox module but it's the same message everytime

Ricky Blaze said:
So I got the OEM unlock,flashed twrp,flashed root
But now when trying to use efs professional it ends at checking the busy boxy with the error message "busybox applet "find" not found in this binary"
I've tried uninstalling busybox, reinstalling trying to use magisks busybox module but it's the same message everytime
Click to expand...
Click to collapse
if at first youre fricasseed, fry fry a hen (if at first you dont succeed, try try again). Reflash stock tar.md5, boot, make sure oem lock is off, flash twrp, root, resume tinkering

OP 8 IN2017 (T-Mobile) / Hard Brick / Help with MSM or QFIL

Hey guys,
Recently after a software update my OP 8 started to crash and after that it would restart itself up. One day it just decided not to do it again, power button did nothing and it just wouldn't boot at all. I thought that the phone was dead, but after a couple of weeks I decided to connect the phone to my computer and after a "low battery warning" it boot up. When booting up, after a while it did the same thing as before, it crashed and decided to restart itself up. I did a factory reset and the same thing happened when I got to the android set up screen.
The same day, I decided that I needed to change the ROM since there could be a problem with it. While trying to unlock the bootloader I realized that I need a code from T Mobile (which I'm solicited and still waiting on), I decided to turn the phone off (so that it didn't restart or crashed) and wait for the code to get to me.
The next day, I tried to boot up the phone and it didn't. When connected to my pc i saw that it was recognized as a QCBulk (something like that), I learned about Qualcomm EDL, downloaded drivers and the phone is kinda talking to my pc. Now, I have used MSM tool to install new firmware but after installing the phone doesn't boot back up but stays on the same EDL mode.
So I need some advice,
1. I thought of waiting on the battery to run out and maybe the phone would get out of EDL mode that way.
2. Keep trying to flash different OOS roms via MSM tool and hope that the phone boots back up afterwards.
3. Using QFIL (one of Qualcomm tools) install need firmware. Problem is, I need a .efl or .mbn file which should be included in the firmware but can't find anywhere.
Please help me guys,
I just bought the phone and I miss it
THANKS!

I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?

Did you fix your problem yet? @Gipsydanger120

I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.

L0ND0NB0Y said:
I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.
Click to expand...
Click to collapse
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode

Gipsydanger120 said:
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode
Click to expand...
Click to collapse
Alright I'll give it to you as soon as I get home

There you go @Gipsydanger120 !

Report back how it goes @Gipsydanger120

L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
Thank you very much, I'll let you know if it works

trinidude4 said:
I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?
Click to expand...
Click to collapse
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.

L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?

Gipsydanger120 said:
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.
Click to expand...
Click to collapse
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.

Gipsydanger120 said:
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?
Click to expand...
Click to collapse
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.

L0ND0NB0Y said:
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.
Click to expand...
Click to collapse
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?

L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
And after you create the xmls and arrange them in folders with firmware files you are going to realize that QFIL can't flash the files for some reason and all your work have gone.

L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.

Gipsydanger120 said:
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?
Click to expand...
Click to collapse
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.

Gipsydanger120 said:
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.
Click to expand...
Click to collapse
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.

L0ND0NB0Y said:
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.
Click to expand...
Click to collapse
Hmm is it possible to get another IMEI? What if I already have the unlock_token? I'm guessing it won't even work since it doesn't have the IMEI anymore

L0ND0NB0Y said:
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.
Click to expand...
Click to collapse
Man that sucks! I don't even know how my phone got so messed up in the first place.

LMV600AM Restore/Ugrade Guide

This restore process is intended for the AT&T V60 (lmv600am) model and will WIPE your data so back it up if you want to keep it!
This process will restore the lmv600am to original factory state for the AT&T v60 v20q build (a11). I’ve dumped all the required partitions from a new replacement phone sent to me by LG. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently unable to boot or who just can’t access AT&T ota services and wishes to upgrade their lmv600am to a newer a11 build. I have only tried this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from a Android 10 rom but I haven’t tried it.
This process will not fix your erased or damage imei number problem.
Steps
Download “Lmv600am v20q Restore Partitions.7z” file from ??? and unzip. Remember the unzipped restore directory path.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose (.elf) which is included in the unzipped directory.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.​
When complete phone reboots as I recall.

try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA

Why super.bin so big? 20GB stucking at flashing super every time

peterwode said:
try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA
Click to expand...
Click to collapse
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.

peterwode said:
Why super.bin so big? 20GB stucking at flashing super every time
Click to expand...
Click to collapse
The size of the super.bin (partitions system_a and system_b) is what it is. It's not like you have a choice. Hopefully, you do realize you're restoring both sides of the phone, slot a/slot b.

hooutoo said:
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.
Click to expand...
Click to collapse
Everything is changed, but the problem is the same, just stucked, progress no move forward, no error message , is the configuaration setting's problem? I am using the same configuaration with the crossflash guide

Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help

peterwode said:
Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help
Click to expand...
Click to collapse
You're welcome.

sorry for my mistake, not update , it is downgrade to 2.0.2.3, with 2.0.3.5 showing zero disk reading of qfil progress in the task manager, with 2.0.2.3 you can see qfil reading data from disk from computer , i don't know if it is bug or just a showing problem.

report one issue, cann't boot when changed to slot_a

did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT

chamilun said:
did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT
Click to expand...
Click to collapse
If you're seeing any boot logo and then getting stuck it usually means that the phone is trying to get to userdata. This restore does not include userdata for obvious reasons. My guess is you needs to reformat/wipe userdata.
The easiest way is probably by entering restore mode and selecting "reset to factory" which both reformats and wipes userdata.
As for the cricket logo, no telling where that's coming from or where your phone's been. But as per the Op description, these are 100% AT&T a11 v20q partitions.

phone wont get into the android boot screen for wiping cache/userdata/etc. kinda odd...
something tells me I need to write something additional. because my ATT model was crossflashed to the EU firmware
to bypass the fingerprint bug. however, they are shutting off 3G networks on the 22nd so cant keep using.
anyone else have any idea what I need to do?

Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.

hooutoo said:
eng abl img
Click to expand...
Click to collapse
hooutoo said:
Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.
Click to expand...
Click to collapse
all done. loaded eng abl. erased userdata in fastboot. still is on cricket startup screen and just stays there booting forever

does yours say "cricket wireless" when booting? so odd how this thing is behaving

got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!

Did you follow the steps, recovery mode and factory reset? Did it complete?

chamilun said:
got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!
Click to expand...
Click to collapse
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.

hooutoo said:
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.
Click to expand...
Click to collapse
everything worked but something is odd. its showing as cricket boot up, LG in settings. not ATT. and the NT error.
also the hidden code menu isnt working.
somehow Ive got a frankenstein phone now. was a pure ATT phone before I crossflashed. somehow I need to figure out
what to write to the phone to get proper version back. I do have the old backup. just need to figure out how we
did the crossflashing and kind of undo

Might have bricked my phone (Alcatel Onetouch)

I rooted the phone to uninstal some bloatware, and of course I have uninstalled something I shouldn't have.
If think it was something with Lolipop in the name, which can sound pretty stupid since it's name of the OS, but the app (root uninstaller) told me it should be safe to remove...
Now either the phone doesn't start, or when it start the interface simply don't show up. I cee see the phone is running behind, If I press the power button I have the popup to restart or shut down the phone, and when I press the home button a google searsh interface appear, but I can't do anything else.
So I've been struggling all the afternoon to try to reset the firmware, I've installed QFIL, try to find the firmware, download some crap form internet that was useless since it was missing the prog_emmc_firehose file, which I've deducted should be prog_emmc_firehose_8916.mbn since the processor is a Snapdragon 410.
I found the file online, I setup the software, click on download, it load for some time... and then I have an error message (I put it on the attached image)
I have no idea what's the problem, if my files are somehow wrong or if the problem is elsewhere, since this model doesn't seem to be very popular I'm struggling to find anything. I think it's close the the Idol 3, but I don't know if both model are compatible.
I'm out of idea, if anyone can help I would greatly appreciate it.

Sylvine said:
I rooted the phone to uninstal some bloatware, and of course I have uninstalled something I shouldn't have.
If think it was something with Lolipop in the name, which can sound pretty stupid since it's name of the OS, but the app (root uninstaller) told me it should be safe to remove.
So I've been struggling all the afternoon to try to reset the firmware, I've installed QFIL, try to find the firmware, download some crap form internet that was useless since it was missing the prog_emmc_firehose file, which I've deducted should be prog_emmc_firehose_8916.mbn since the processor is a Snapdragon 410.
I found the file online, I setup the softwate, click on download, it load for some time... and then it says :
ERROR : function : sahara_rx_data: 276 Unable to read packet header. Only rea 0 bytes.
Download fails : Sahara Fail :QSaharaserver fail: Process fail
I have no idea what's the problem, if my files are somehow wrong or if the problem is elsewhere, since this model doesn't seem to be very popular I'm struggling to find anything. I think it's close the the Idol 3, but I don't know if both model are compatible.
I'm out of idea, if anyone can help I would greatly appreciate it.
Click to expand...
Click to collapse
Factory reset! By far the easiest option ( Maybe not actually... do you have any recovery installed? )
If you want to keep data you need to flash the full update image... It will re enable all the apps you disabled

Rstment ^m^ said:
Factory reset! By far the easiest option ( Maybe not actually... do you have any recovery installed? )
If you want to keep data you need to flash the full update image... It will re enable all the apps you disabled
Click to expand...
Click to collapse
If you're talking about pushing volume up + power and doing a factory reset, it's not fixing anything.
Or there's another method ?

Sylvine said:
If you're talking about pushing volume up + power and doing a factory reset, it's not fixing anything.
Or there's another method ?
Click to expand...
Click to collapse
There isn't , if you are android 5 once the app is uninstalled it's uninstalled permanently..> ( On newer android it's way harder to fully uninstall , so most apps just disable them )
To use QFIL I believe you need to enter EDL mode first? Look for some edl flashing guides , but if you can flash ANY custom recovery it's much easier that way

Rstment ^m^ said:
To use QFIL I believe you need to enter EDL mode first?
Click to expand...
Click to collapse
I think I am in EDL mode, otherwise QFIL wouldn't even start the procedure.
Just to be sure, I push both volume buttons down, then plug the cable.
Then I have a picture telling me I have to push volume up to enter Download mode, si I guess it's EDL ?
Look for some edl flashing guides , but if you can flash ANY custom recovery it's much easier that way
Click to expand...
Click to collapse
Are you saying I should be able to flash any custom recovery ?
Or that if I COULD it would be easier.
Frankly I have no idea what you're talking about, I'm totally in the dark here.

Sylvine said:
I think I am in EDL mode, otherwise QFIL wouldn't even start the procedure.
Just to be sure, I push both volume buttons down, then plug the cable.
Then I have a picture telling me I have to push volume up to enter Download mode, si I guess it's EDL ?
Are you saying I should be able to flash any custom recovery ?
Or that if I COULD it would be easier.
Frankly I have no idea what you're talking about, I'm totally in the dark here.
Click to expand...
Click to collapse
First I have limited knowledge about edl , but from what I know you can't enter edl with button combinations - download mode should not be edl... ( There are multiple ways of entering edl - You either need a special cable / Need to open phone , find test points and short them / issue correct fastboot comand for entering edl... I think it was something like fastboot reboot-edl )
And second, flashing system updates via custom recovery is usually a much simpler process than QFIL ( This is only a last resort option ! I'd use fastboot before trying qfil )
What you can do is find and download complete system update for your device , extract it and send me a screenshot. (If you can find a custom recovery for your device go ahead and flash it as well)

Sylvine said:
I rooted the phone to uninstal some bloatware, and of course I have uninstalled something I shouldn't have.
If think it was something with Lolipop in the name, which can sound pretty stupid since it's name of the OS, but the app (root uninstaller) told me it should be safe to remove...
Now either the phone doesn't start, or when it start the interface simply don't show up. I cee see the phone is running behind, If I press the power button I have the popup to restart or shut down the phone, and when I press the home button a google searsh interface appear, but I can't do anything else.
So I've been struggling all the afternoon to try to reset the firmware, I've installed QFIL, try to find the firmware, download some crap form internet that was useless since it was missing the prog_emmc_firehose file, which I've deducted should be prog_emmc_firehose_8916.mbn since the processor is a Snapdragon 410.
I found the file online, I setup the software, click on download, it load for some time... and then I have an error message (I put it on the attached image)
I have no idea what's the problem, if my files are somehow wrong or if the problem is elsewhere, since this model doesn't seem to be very popular I'm struggling to find anything. I think it's close the the Idol 3, but I don't know if both model are compatible.
I'm out of idea, if anyone can help I would greatly appreciate it.
Click to expand...
Click to collapse
Please provide the model name of the device.