Related
[Evert] [Stock] Firmware - Return to Stock.Disclaimer
I can not be held responsible for any type of problem with your device. This information is for the sole purpose of reporting and is delivered "as is". Only the tests will confirm if everything works well or does not work at all, proceed with caution.
Recommendations.
Make sure to back up all information, device data, and (optional) persistence partitions of the device.
Always use common sense, and confirm that you do not have an error message in the console. Verify that things are done correctly.
Requirements
Make sure that the drivers and everything related to connectivity is working properly. The official Motorola drivers work fine, and the google fastboot drivers too. Look for tutorials on installing the fastboot driver if your computer is not detecting it properly, the tutorials of other moto models (eg moto g5 plus) on the drivers and others work just as well.
All this process spends time and of course the battery of your device, make sure you have a good battery (50+) and stay connected as much as possible.
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware, but it depends on each one...
All the commands and others are done from the fastboot utility, you can find it in https://developer.android.com/studio/releases/platform-tools.
Process
Download the correct firmware for your device.
Right now there are not many firmware available, as time passes the list will grow.
One of several sites is LOLINET.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETAIL/
(If not already installed, make sure of ..) Install the drivers and download the fastboot utility. And of course, verify that the driver works properly. It will be done later.
Extract the fastboot utility, and the firmware within the same directory.
To verify the connection, enter the bootloader of your device, connect it with the PC. On the PC; run the console, go to the folder where you extracted the fastboot utility, and type fastboot.exe devices, you should see the listed device in the console.
If the connection works correctly and you notice nothing strange, you can start the process.
Open the console in the directory where the fastboot utility is on the firmware files, there should be no more folders inside. (In this case you should adjust the path of the files in the commands). And write the following commands, verify that you do not have errors.:
Warning,
The commands listed below as "optional" do not necessarily have to be executed, but to be completely safe, execute them all, as long as you have the right firmware.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img (optional)
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1 (Optional)
fastboot erase modemst2 (Optional)
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot erase carrier (Optional)
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
[I][/I]
Press the Power button, and wait a bit.. It will take a few minutes to start.
If you hear "Hello moto", congratulations you are in Stock (and everything "should work fine").
Notes
If your firmware has more or less sparsechunk files (eg, sparsechunk.3 or img_sparsechunk.7), run them all.
The bootloader will remain unlocked.
If all this was helpful, I hope your thanks.
With love by iGor.
And how remove verity Mode enabled?..and a black screen saying phone flashed with different software
IGorMcLven said:
Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware
Click to expand...
Click to collapse
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
rybshik said:
I am looking for an Oreo firmware for dual SIM XT1926-7.
Will all RETAIL version(s) support dual SIM ?
For example, does EVERT_RETAIL_8.0.0_OPWS27.113-92-5 support dual SIM?
Click to expand...
Click to collapse
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Dual SIM XT1926-7: firmware and TWRP issue
lcmp said:
I have the same phone.
Before you flash your phone make sure that you have a backup of :
EFS and Persist partitions
Click to expand...
Click to collapse
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
rybshik said:
Which TWRP version, what exact build file did you use to back up/restore partitions?
Was your TWRP capable of backing up /data partition?
In another tread, I posted that (after Magisk root) the latest twrp-3.3.1-0-evert.img failed to back up the /data partition, but twrp-3.2.3-42-evert.img worked well
Click to expand...
Click to collapse
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
TWRP decryption issue
lcmp said:
For me, it works exactly the opposite.
TWRP 3.2.3 was not able to decrypt the phone data.
But booting temporarily with TWRP 3.3.1-0 would successfully decrypt and backup everything.
Click to expand...
Click to collapse
for which firmware build? Pie or Oreo?
In my case, I was able to back up with twrp-3.3.1-0-evert.img before flashing Magisk. And I was able to Magisk-root with twrp-3.3.1-0-evert.img successfully as well.
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
So I tried twrp-3.2.3-42-evert.img and it worked.
Is it possible to permanently remove encryption?
rybshik said:
for which firmware build? Pie or Oreo?
Click to expand...
Click to collapse
PIE
rybshik said:
But once rooted, was NOT able to back up \data partition with twrp-3.3.1-0-evert.img.
Click to expand...
Click to collapse
I´m not an expert, but from what i know, You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition. Then your backups will succeed.
rybshik said:
Is it possible to permanently remove encryption?
Click to expand...
Click to collapse
I read it´s possible but i´m no expert on the subject. Why would you want to remove encryption? I think its a good feature
lcmp said:
You need to have a pin or unlock pattern on your phone. TWRP asks you for it and uses it to decrypt the data partition.
Click to expand...
Click to collapse
Does TWRP ask for a PIN during back up?
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
rybshik said:
Does TWRP ask for a PIN during back up?
Click to expand...
Click to collapse
What I noticed is that when TWRP 3.3 boots, it asks for your pin or unlock pattern in order to use that as the credential to get the decryption key and decrypt the data partition. TWRP 3.2 won't do this ( again, in my experience ) hence the back up fails because everything is encrypted.
This is how I noticed that force installing TWRP 3.2 was useless. it doesn´t ask for your pin or your unlock pattern so it doesn´t have a way of decrypting the data partition. Again this was my experience. A more advanced android / twrp user could give a definite answer.
rybshik said:
I have not set up any PIN/unlock pattern at all. So TWRP did not ask for it during back up, but just failed to back up , showing an error related to data partition.
Could absence of PIN cause the backup to fail?
Click to expand...
Click to collapse
I think so, yes. If you don´t have a pin or unlock pattern in your phone, TWRP doesn´t have a way to "authenticate" and get the decryption key and decrypt the data partition. Again, I´m assuming this out of my own experience.
Hello, can anyone share me the persist file from a xt1926-6 please?
I am having an issue with this file and I don't know what to do now
Thank you
lcmp said:
I have the same phone.
First do this:
Go to settings: tap System, tap about phone and write down which software channel you are on.
It will say something like this:
RETLA
or
TEFCO
or
TEMX
or
TIGCO
Those are the only channels which offer stock roms for the XT1926-7
If your phone is factory unlocked you will probably have to use the RETLA versions.
the on your computer go to:
mirrors . lolinet . com /firmware /moto /evert /official/
You will find the original android 8 stock rom in there:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
Hello, how did you solve the persist issue? I have it corrupt and I don't know what to do
Thanks
lcmp said:
Before you flash your phone make sure that you have a backup of :
EFS
and
Persist
partitions.
If those get corrupted or wiped you won´t have carrier signal or wifi once you reboot your phone. trust me it happened to me.
good luck.
Click to expand...
Click to collapse
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Toonka95 said:
This has happened to me, however I am dumb and did not make a back up... So, does this mean I can never get my carrier signal back? Internet works but sim card refuses to be read.
Click to expand...
Click to collapse
You can, recently I posted a solution for this issue (i believe it's the same as yours)
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t3994827
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
The following are the official firmware commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Doxmey said:
wow bro, just wow... for those who are reading this do not erase the modem and carrier my phone is now pretty much useless because I didnt know that erasing that would reset my imei. Now my phone has no wi-fi and no carrier connection. Now im running a damn reverse tethering to see if i can reverse this. Any ideas now? How the hell do i get this back?
By the way give people a warning to not do that wtf.... I can only imagine how many people you fcked with this.
Click to expand...
Click to collapse
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
sd_shadow said:
The following are the official firmware commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I don't know why there is a erase carrier command in the op
But the erase modem lines are standard
Sent from my mata using XDA Labs
---------- Post added at 04:25 AM ---------- Previous post was at 04:24 AM ----------
I would try flashing
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Again
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
WoKoschekk said:
These lines are copied from the flashfile.xml inside the stock.zip:
Code:
<step operation="erase" partition="carrier"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="ddr"/>
<step operation="oem" var="fb_mode_clear"/>
The "erase carrier" command is as usual as the "erase modemst1/2" command. That's the default.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
Erase carrier + modem will not erase your IMEI as long as your /persist is not corrupted!!
Click to expand...
Click to collapse
Yeah man it took me all day to try to get it all working again, the fix was i downloaded an older stock rom and it restored my IMEI, it had to be the older version though because the newer one would recover it. Anyways now i'm never erasing that carrier or modem if it's not really necessary.
revert xt1926-3 to factory (2020)
IGorMcLven said:
[Evert] [Stock] Firmware - Return to Stock.
Code:
...
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
...
Click to expand...
Click to collapse
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
tseeling said:
The latest factory image I downloaded from lolinet does not contain 2 files for system_b, only one, and it's named differently, so imho you have to replace the 2 above fastboot commands with the following (taken from flashfile.xml inside the download):
Code:
fastboot flash system_b system_other.img
I recommend to *always* compare flashfile.xml to zip contents before using a series of flash commands from somewhere else. Or someone could develop an XSLT file to convert flashfile.xml to a flashing script
I'm attaching a little verification shell script to check that all required files are in place.
Click to expand...
Click to collapse
Needs Termux and python.
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Flash stock rom lenovo k5
try turning off your internet connection and flash sorry for my inglis I'm using google translate
Nox.BG said:
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Click to expand...
Click to collapse
I'm stuck on the "fire hose" file. QFIL seems to not detected the phone.
Did you managed to solve the problem?
Lenovo K5 Pro ROM
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
ShmuelCohen said:
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Did you get any solution, I have the same problem.
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
help me what is the correct file to download to flash android 10 on lenovo k5 pro. Gapps and custom rom please help. Im stock the google pixel logo boot screen for almost an hour.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
shisho585 said:
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
Click to expand...
Click to collapse
.
iugleafar said:
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
Click to expand...
Click to collapse
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
Okay, so I own a Red Magic 6 and it's currently bricked. There is no unbrick tool for this device yet and there isn't going to be one for a while.
My bootloader is unlocked. I have tried reflashing the files using fastboot. However when I go to flash the system, it prints out:
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (786352 KB) OKAY [ 18.114s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
(Phone came with a/b partition just a heads up and it runs on Stock android 11)
I have searched EVERYWHERE, from forums, to tools, to python scripts.... EVERYTHING. No solution.
Yes, my fastboot is on the lastest version and yes I tried the --force command on fastboot. Still no luck.
I have researched everything about sparse images but am still having problems. I tried converting the image to a RAW ext4 img but it fails.
Is there any workaround for this?
chocolote4444 said:
Okay, so I own a Red Magic 6 and it's currently bricked. There is no unbrick tool for this device yet and there isn't going to be one for a while.
My bootloader is unlocked. I have tried reflashing the files using fastboot. However when I go to flash the system, it prints out:
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (786352 KB) OKAY [ 18.114s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
(Phone came with a/b partition just a heads up and it runs on Stock android 11)
I have searched EVERYWHERE, from forums, to tools, to python scripts.... EVERYTHING. No solution.
Yes, my fastboot is on the lastest version and yes I tried the --force command on fastboot. Still no luck.
I have researched everything about sparse images but am still having problems. I tried converting the image to a RAW ext4 img but it fails.
Is there any workaround for this?
Click to expand...
Click to collapse
I am looking for the same thing. Can't find the answer. Have you found a solution?
same here
Out of curiosity, was there ever a resolution to this issue?
Have RM6SP, was rooted- all good. Battery ran empty and shut off. When I rebooted it just boots directly to fastboot. Recovery is useless (wiped user data but no cache to erase(?)).
Extracted payload.bin, tried flashing boot.img, rebooted, only goes to fastboot. Tried flashing everything from payload.bin- some flashed, others had errors. Just endless loading to fastboot.
Curious if anyone has actually SUCCESSFULLY unbricked these devices?
Looks like your partition table may be corrupted... I don't own this device myself but have a fairly good understanding of android partitions and am happy to help.
Please show the output of
Code:
fastboot getvar ptable
and the errors you get when trying to flash
Hello DavidxxxD and thank you for replying.
Execution of "getvar ptable" results in "FAILED (remote: 'Unknown variable')
I then executed "getvar all" and attached the result. Same whether on fastboot or fastbootd.
As for your other question, when I try to flash product, system, and vendor I get the above "Invalid Sparse File Format at Header Magic" error.
Thank you for any suggestions and your time. This is not my daily driver so there is no urgent, pressing need (I'll never get rid of my trusty S7edge, lol).
EDIT: thanks to the unbrick tool in the 6S Pro forum, I have successfully unbricked this phone. Up and running and on way to getting re-rooted.
Thanks to everyone who offered help!
Glad to hear you already got it unbricked!
For the sake of it being an intresting case, here is the more complicated way I put together and what I could find out from looking at the attatchment and a payload file for your device:
Good news - Your device is not too badly bricked.
Like some other new devices, this phone does not use a cache partition. That is why the recovery has no option to wipe cache.
The "invalid sparse header" message gets triggered when using fastboot to send a filesystem image that is not in the expected android sparse format. This can safely be ignored as the images for your device are uncompressed and the program doesn't know what they're suppsed to look like.
The NX669J uses a dynamic partition and the one on yours appears messed up in a way where I have no idea how it got to this point - all partitions for the A-slot are missing and instead there is a "system" (not system_a) and "system_b-cow" (!?) - This is probably why the bootloader is freaking out.
Usually, something like this can be fixed by just reflashing the super partition. However the update payload does not seem to contain one, so - unless you have a super.img from somewhere else - you would have to manually fix the current layout.
- Put the device is fastbootd mode
Code:
fastboot reboot-fastboot
Note: To verify, you can run
Code:
fastboot getvar is-userspace
Note: Didn't expect to have to say this, but don't run these commands on devices with correctly assigned partitions, unless you know what you are doing! They can be used as an example of how to modify dynamic partitions. "system" is also used as an alias for the active system partition. You will likely softbrick your device and have to fix it!!
- Firstly, remove the strange partition entries
Code:
fastboot delete-logical-partition system
fastboot delete-logical-partition system_b-cow
- Next, re-create the missing entries
Code:
fastboot create-logical-partition system_a 1000
fastboot create-logical-partition system_ext_a 1000
fastboot create-logical-partition product_a 1000
fastboot create-logical-partition vendor_a 1000
fastboot create-logical-partition odm_a 1000
Note: 1000 will set the partition size to a kilobyte. This doesn't matter as flashing will automatically resize them.
- After that, you should be able to flash to the newly created partitions
Code:
fastboot flash system_a system.img
fastboot flash system_ext_a system_ext.img
fastboot flash product_a product.img
fastboot flash vendor_a vendor.img
fastboot flash odm_a odm.img
Note: If you get an error saying "not enough space to resize partition", try
Code:
fastboot erase system_b
fastboot resize-logical-partition system_b 1000
- Finally, set the active slot to A and reboot
Code:
fastboot set_active a
fastboot reboot
Note: If it doesn't boot or the system starts crashing, you may have to flash the other firmware images as well or try using slot B.
In case this doesn't work, you can ask someone with a rooted NX669J to dump their super partition and send it to you. If you do, make sure to check it first using lpdump. Flashing a corrupted image is going to make it worse 100% guaranteed.
I hope this gives you a better idea of what was wrong and how to deal with similar issues in the future. Of course, a low-level unbrick tool works fine too - but where's the fun in that?
P. S: I'm actually typing this on a flat S7 - still an amazing device, 6 years after release : )
Thank you, DavidxxxD, for taking the time out and providing a detailed reply. Hopefully this info might come in useful to someone one day.
I have no idea why a dead battery would "zonk" the phone, but it did. I wonder if it might have been something with magisk...?
¯\_(ツ)_/¯
Sadly, these phones are not popular and support from Nubia is painful, at best. Thanks to folks like you there is still help for those in need.
Again, many thanks for your time and help!
DavidxxxD said:
Glad to hear you already got it unbricked!
For the sake of it being an intresting case, here is the more complicated way I put together and what I could find out from looking at the attatchment and a payload file for your device:
Good news - Your device is not too badly bricked.
Like some other new devices, this phone does not use a cache partition. That is why the recovery has no option to wipe cache.
The "invalid sparse header" message gets triggered when using fastboot to send a filesystem image that is not in the expected android sparse format. This can safely be ignored as the images for your device are uncompressed and the program doesn't know what they're suppsed to look like.
The NX669J uses a dynamic partition and the one on yours appears messed up in a way where I have no idea how it got to this point - all partitions for the A-slot are missing and instead there is a "system" (not system_a) and "system_b-cow" (!?) - This is probably why the bootloader is freaking out.
Usually, something like this can be fixed by just reflashing the super partition. However the update payload does not seem to contain one, so - unless you have a super.img from somewhere else - you would have to manually fix the current layout.
- Put the device is fastbootd mode
Code:
fastboot reboot-fastboot
Note: To verify, you can run
Code:
fastboot getvar is-userspace
- Firstly, remove the strange partition entries
Code:
fastboot delete-logical-partition system
fastboot delete-logical-partition system_b-cow
- Next, re-create the missing entries
Code:
fastboot create-logical-partition system_a 1000
fastboot create-logical-partition system_ext_a 1000
fastboot create-logical-partition product_a 1000
fastboot create-logical-partition vendor_a 1000
fastboot create-logical-partition odm_a 1000
Note: 1000 will set the partition size to a kilobyte. This doesn't matter as flashing will automatically resize them.
- After that, you should be able to flash to the newly created partitions
Code:
fastboot flash system_a system.img
fastboot flash system_ext_a system_ext.img
fastboot flash product_a product.img
fastboot flash vendor_a vendor.img
fastboot flash odm_a odm.img
Note: If you get an error saying "not enough space to resize partition", try
Code:
fastboot erase system_b
fastboot resize-logical-partition system_b 1000
- Finally, set the active slot to A and reboot
Code:
fastboot set_active a
fastboot reboot
Note: If it doesn't boot or the system starts crashing, you may have to flash the other firmware images as well or try using slot B.
In case this doesn't work, you can ask someone with a rooted NX669J to dump their super partition and send it to you. If you do, make sure to check it first using lpdump. Flashing a corrupted image is going to make it worse 100% guaranteed.
I hope this gives you a better idea of what was wrong and how to deal with similar issues in the future. Of course, a low-level unbrick tool works fine too - but where's the fun in that?
P. S: I'm actually typing this on a flat S7 - still an amazing device, 6 years after release : )
Click to expand...
Click to collapse
Hi DavidxxxD,
I had a quite a similar problem here, sometimes ago while trying to install TWRP and Magisk onto my nubia Z20 NX627J, unfortunately did not succeed and got myself a bricked phone. Now phone can only go into fastboot mode.
Had been trying to flash everything from scratch via fastbboot, did not get any error messages with flashing all the img, bin except while flashing system. img, it returned with a " Invalid sparse file format at header magic" but went on with the process without issue. However, the phone still enable to boot up normally.
Is it possible that that the rom I have is not the original stock rom?
So while searching for an answer, was happy to found this thread at XDA forum. After going through the thread on your reply to SkylineDriver, i was hoping you can help and enlighten me if I had miss anything.
Attached is the getvar file from my bricked phone after flashing, another file is the fastboot command I followed, except the flash system command, i just did a "fastboot flash system system.img" without the "-S 100M' because I didn't know what "-S 100M" means".
Thanks in advance
@cksy1112 A bit late, but here are some things I noticed:
Are you sure your bootloader is unlocked? The device says it's locked. What happens when you send the unlock command?
You may need to flash vbmeta with the option --disable-verity.
This device has a painful ammount of partitions and whoever designed it should be punished for making my head hurt.
Not sure about the -S 100M thing, haven't seen that before and the system has to be larger than 100 megabytes.
Also, I don't think it's necessary to erase that many partitions before flashing.
It even has UEFI with a partition to store variables - that is very intresting and could have some great potential for multi-booting and other fun stuff - if we can understand how their implementation works.
chocolote4444 said:
Okay, so I own a Red Magic 6 and it's currently bricked. There is no unbrick tool for this device yet and there isn't going to be one for a while.
My bootloader is unlocked. I have tried reflashing the files using fastboot. However when I go to flash the system, it prints out:
Invalid sparse file format at header magic
Sending sparse 'system' 1/4 (786352 KB) OKAY [ 18.114s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
(Phone came with a/b partition just a heads up and it runs on Stock android 11)
I have searched EVERYWHERE, from forums, to tools, to python scripts.... EVERYTHING. No solution.
Yes, my fastboot is on the lastest version and yes I tried the --force command on fastboot. Still no luck.
I have researched everything about sparse images but am still having problems. I tried converting the image to a RAW ext4 img but it fails.
Is there any workaround for this?
Click to expand...
Click to collapse
Hello,
Have you find a solution to your pronlem?
is there an unbrick tool for red magic 6s pro?
I think I messed up my phone and it is brick because the super image is not updating for product system etc when I tried to flash the extracted ROM images. system and product coyld not be flashed. and sparse error apperas.
Did you install them in fastbootd mode? (Not regular fastboot)
DavidxxxD said:
Did you install them in fastbootd mode? (Not regular fastboot)
Click to expand...
Click to collapse
Thanks for the quick reply
I can’t boot to fastbootd. It gives an error and boot back to fastboot
You can try to flash the non-dynamic partitions first and then try again.
DavidxxxD said:
You can try to flash the non-dynamic partitions first and then try again.
Click to expand...
Click to collapse
hey so i also deleted cache partition
should i do
fastboot create-logical-partition cache 1000
to make cache partition?
i did do that and now its flashing, its showing less errors then last time lol
edit: what should i do to make cache partition?
Hello, I tried the commands DavidxxxD gave, but my phone is now stucked in a bootloop, I have a Xiaomi 11T. And the commands weren't working, it said "deleting 'system'..." but after it said "command failed".
Try creating it again and flash the image in fastbootd.
Is your device A/B? Use
Code:
fastboot getvar all
to learn more.
solution - Use SDK platform 33.03 instead
I flashed an image to my phone, and everything except wifi, bluetooth, and cellular are functional.
I've tried over a dozen methods now, and everything except the radios works just fine.
I've told by getdroidtips.com that I need these files:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
Click to expand...
Click to collapse
Does anyone happen to have these files? I don't have a backup of my phone, so I can't get them.
if you follow the guide I posted, youll be able to recover
All you need is the radios for the security patch you've flashed and reflash those. You didn't mention anything about the update your on. But there are radios for at least one security patch on here and you could get more help in the OnePlus Nord N20 telegram group
dmtec said:
if you follow the guide I posted, youll be able to recover
Click to expand...
Click to collapse
This guide? (https://forum.xda-developers.com/t/downgrading-restoring-to-may-and-rooting-without-a-hitch.4495801/)
Ive tried that with no luck whatsoever. It kept giving me weird errors
PsYk0n4uT said:
All you need is the radios for the security patch you've flashed and reflash those. You didn't mention anything about the update your on. But there are radios for at least one security patch on here and you could get more help in the OnePlus Nord N20 telegram group
Click to expand...
Click to collapse
I'm on 2022-05-05 running Android 11, build number CPH2459_11_A.05
i only have radios for gn2200, not cph2459.
is yours a carrier branded device?
im going to have to edit my posts to reflect the model my files are for since there seems to be another model out
PsYk0n4uT said:
i only have radios for gn2200, not cph2459.
is yours a carrier branded device?
im going to have to edit my posts to reflect the model my files are for since there seems to be another model out
Click to expand...
Click to collapse
Mine is not carrier branded, it's the unlocked model.
Here's your firmware
https://www.getdroidtips.com/oneplus-nord-2t-5g-firmware-flash-file-2/
Bro did you ever get this fixed I did the exact same thing I lost my radio then with my luck I ended up flashing the wrong opf file and to add the cherry on top I had my phone connected to a bad USB port. I moved my phone just enough to make it disconnect while it was flashing left my phone on a annoying boot loop .
Butttttt within a couple of days I got my one plus running like new and rooted. ALL thanks to a OnePlus guru here (ahh @dmtec instructions where spot on (just saw his comment haha he's the guru I'm talking about)) in xda.
If you need help restoring your phone let me know. I don't mind helping out.
Alfa-Q L83r said:
Bro did you ever get this fixed I did the exact same thing I lost my radio then with my luck I ended up flashing the wrong opf file and to add the cherry on top I had my phone connected to a bad USB port. I moved my phone just enough to make it disconnect while it was flashing left my phone on a annoying boot loop .
Butttttt within a couple of days I got my one plus running like new and rooted. ALL thanks to a OnePlus guru here (ahh @dmtec instructions where spot on (just saw his comment haha he's the guru I'm talking about)) in xda.
If you need help restoring your phone let me know. I don't mind helping out.
Click to expand...
Click to collapse
all you need to do is flash the modems that match your system and radios will work again even if other partitions dont match as long as it boots though u may have issues with fingerprint and stuff like that if other partitions arent all matching.....
Hey if anyone have these files please I need them.
What really actual happend to my phone is
I tried to cross flash to EA firmware because Verizon didn't pull the A12 before cross flashing I backed up FTM modem_a modem_b modemst1 modemst2 OP_a OP_b Sid_a and Sid_b. In the process og cross flash I lost my IMEI. Then I installed the verizon A11 kdz and try to restore my partition but IMEI didn't come back. Whenever I restore my backup partitions and boot to download mode directly from Edl LG UP recognize my phone as V600VM30A and it shows IMEI but when I flash the kdz or boot to system IMEI is zero. I just want to install v600vm30a firmware maybe it solve my problem. Thanks.
irfan64672 said:
Hey if anyone have these files please I need them.
What really actual happend to my phone is
I tried to cross flash to EA firmware because Verizon didn't pull the A12 before cross flashing I backed up FTM modem_a modem_b modemst1 modemst2 OP_a OP_b Sid_a and Sid_b. In the process og cross flash I lost my IMEI. Then I installed the verizon A11 kdz and try to restore my partition but IMEI didn't come back. Whenever I restore my backup partitions and boot to download mode directly from Edl LG UP recognize my phone as V600VM30A and it shows IMEI but when I flash the kdz or boot to system IMEI is zero. I just want to install v600vm30a firmware maybe it solve my problem. Thanks.
Click to expand...
Click to collapse
you have done big mistake when you didn't backup your Lun partition exactly the lun 5 partition which unclude your imei