partitions dumped with dd in TWRP.
filename: sparrow_601_M6E69X_2017-03-24.zip
size: 270MB
link: https://mega.nz/#!AsIWSIqC!aZ03WRvKi-XsTD8Mn1M1Aq8UsUbnye20530wBT7AXqY
should be flashable with fastboot (untested)
system.simg is a sparse image
list of dumped partitions:
- aboot.img
- boot.img
- misc.img
- pad.img
- recovery.img
- system.simg
- tombstones.img
Code:
$ fastboot getvar all
(bootloader) partition: system, ,size: 0x20000000 ,type: ext4
(bootloader) partition: userdata, ,size: 0xa47fbe00 ,type: ext4
(bootloader) partition: cache, ,size: 0x19000000 ,type: ext4
(bootloader) partition: boot, ,size: 0x1000000 ,type: raw
(bootloader) partition: recovery, ,size: 0x1000000 ,type: raw
all: partitions are listed!
$ fastboot getvar [other vars]
max-download-size 0x3d00000
version 0.5
version-baseband APQ_8026 - V1
version-bootloader SPARROW3003503
M6E69Z is out. Anybody grabbed it yet?
EDIT: Specifically needing the OTA update zip.
parkerlreed said:
M6E69Z is out. Anybody grabbed it yet?
EDIT: Specifically needing the OTA update zip.
Click to expand...
Click to collapse
Is it 2.0?
Sent from my SM-G920F using XDA-Developers Legacy app
adas4190 said:
Is it 2.0?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. As the build number implies it's just another incremental update to Marshmallow. I thought my watch had downloaded it but it turned out to be corrupt (might not have finished). I cleared it from /cache and have been waiting for it to redownload without any luck.
Oh I see
Sent from my SM-G920F using XDA-Developers Legacy app
There's a new version M6E69Z with February security patches
Enviado desde mi Nexus 6P mediante Tapatalk
Here's the M6E69Z OTA zip https://android.googleapis.com/pack.../9ab7143aef49150f58b7ab33caf293916a156074.zip
i flsash only system and boot !! all ok thanks
Wait, why is the system a "simg" file? And how would someone flash this then?
EpicLPer said:
Wait, why is the system a "simg" file? And how would someone flash this then?
Click to expand...
Click to collapse
I rename it to. img and is ok now @ranf
I am stock with update again
EpicLPer said:
Wait, why is the system a "simg" file? And how would someone flash this then?
Click to expand...
Click to collapse
As I said in OP: sparse image.
dd only gave me a dump of an ext4 partition.
Flashing is just normal procedure: fastboot flash [partition] filename
needed "fastboot oem unlock" to flash boot.img recovery.img and system.simg. worked fine. after pairing the watch to my phone again it made an automatic update (which ALWAYS crashed at 50% until now). im now on M6E69Z latest build. thx man :good:
EDIT: rooted with SuperSU-2.65-wear.zip successfully.
Made a dump of M6E69Z
https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparro-wi501q-build-t3591083
4RK4N said:
needed "fastboot oem unlock" to flash boot.img recovery.img and system.simg. worked fine. after pairing the watch to my phone again it made an automatic update (which ALWAYS crashed at 50% until now). im now on M6E69Z latest build. thx man :good:
EDIT: rooted with SuperSU-2.65-wear.zip successfully.
Click to expand...
Click to collapse
How you flash simg? I rename it to. img for flash
leap_ahead said:
How you flash simg? I rename it to. img for flash
Click to expand...
Click to collapse
i just typed "fastboot flash system system.simg" and thats it. no rename. just worked as is.
used the linux version of fastboot but that shouldnt matter.
Sent from my Nexus 6P using XDA Labs
How did you manage to dump the system partition? I tried dumping it with dd 2 times now and everytime I try to flash it back via fastboot I simply get this:
Code:
target reported max download size of 63963136 bytes
Invalid sparse file format at header magi
And then fastboot via CMD crashes...
EpicLPer said:
How did you manage to dump the system partition? I tried dumping it with dd 2 times now and everytime I try to flash it back via fastboot I simply get this:
Code:
target reported max download size of 63963136 bytes
Invalid sparse file format at header magi
And then fastboot via CMD crashes...
Click to expand...
Click to collapse
That's exactly the reason to sparse.
If you quickly want to get your watch working:
- boot fastboot
- adb push system.img /sdcard/
- adb shell
- the dd command you used to dump with if= and of= parameters swapped.
ranf said:
That's exactly the reason to sparse.
If you quickly want to get your watch working:
- boot fastboot
- adb shell
- the dd comand you used to dump with if= and of= parameters swapped.
Click to expand...
Click to collapse
Well the dd command swapped I know
But I want to offer people a fastboot flashable image but I have no idea how, heh. I simply restored my watch with your image so no worries
Related
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
I would trying to flash each image in factory image individually (Flash bootloader, flash boot, flash recovery, etc.), flashing them in the order the flash-all script would flash them (If your not sure which order it would flash them in just open the flash-all.bat or flash-all.sh as a text file and look at the order they are flashed in).
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
The missing.sig errors are normal. The missing system.img is not. Try downloading the factory image again.
Sent from my Nexus 5 using XDA Free mobile app
Same here, get the same error when trying to flash factory image. I did flash the files individually, but wasn't sure how to flash the vendor.img?
any update on this?
what do we do with vendor.img?
mingiunate said:
any update on this?
what do we do with vendor.img?
Click to expand...
Click to collapse
Just an update - based on the size of vendor.img, I assumed it was the same as userdata.
here are the steps i took to manually flash:
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img
from tablet - select hboot
select factory reset
Done!
Hm, I successfully flashed vendor.img using
Code:
fastboot flash vendor vendor.img
But I'm not sure whether that was the correct way to go about things.
Hi
Thanks everyone for the replies/responses.
I will try and flash each image separately, however this shouldn't be necessary and means the image (or some setting on the Nexus 9) is wrong or broken. The whole point of the factory image is that it flashes with ease to get us back to a clean slate (well tablet), so a bit worrying they've not seemingly tested it too well.
Note I've flashed factory images dozens of times to Nexus 4, 5, 7 (both years) and never had this problem.
Perhaps Google will post a fix soon.
Best Regards
Phil
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
here are the steps i took to manually flash:
run the flash-all.bat up until the point where it fails
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
from tablet - select hboot
select factory reset
Done!
Hi
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
I did this as the first step as that is what is in the batch file with all/most Nexus factory images, didn't make a difference though. Something is definitely broken somewhere. However installing the images separately seems to work.
Best Regards
Phil
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Hi
cundiffr said:
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Click to expand...
Click to collapse
As I mentioned in the first post, after the first failure I updated my SDK to the very latest version, the result was the same. The image doesn't flash unless you separate out the individual parts and do it separately. Either the Nexus 9 isn't configured to allow enough space to accept the entire image (which clearly Google think it should as that is how they instruct it to be installed), or the image is broken in some way.
I'm sure it will get fixed at some point.
Regards
Phil
The same thing happened to my while I tried to flashed the newly released lollipop image to my nexus 5. I only had to restart my laptop and it worked.
mingiunate said:
[*]fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
Click to expand...
Click to collapse
Yep, vendor should be flashed to the "vendor" partition.
userdata is emptied during factory reset.
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
scotty1223 said:
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
Click to expand...
Click to collapse
It's the image or tablet that's at fault. I ran the flashing process on a high-end machine equipped with 32 GB of RAM.
Restart your computer!
I sat here forever trying to figure why the hell i couldn't get 5.0 to flash to my nexus 5. I looked everywhere and didn't find anything that helped at all. I restarted my computer and tried again and it worked instantly. The first thing i said to myself was are you ****ing kidding me.... my computer was the issue. Dont tell yourself bull**** about how your computer is the bees knees. Mine may only have 16 gb of ram but restarting it worked perfectly.
Do i make a fullwipe, befor i flash the Image Files, if yes how i do this.
format system
format data
format cache
????????
fastboot flash userdata vender.img actually worked for me
I flashed lrx21l yesterday, manually. But I flashed the vendor.img inside userdata and NOT in the "vendor" partition. Rooted and running ok.
Trying to fix that mistake I flashed lrx21l vendor.img again, but using "fastboot flash vendor vendor.img". All good.
And now, I manually flashed lrx21q, rooted using CF-Auto-Root and everything seems fine!
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
My questions are:
1- Am I with duplicate vendor files?
2- Will I have issues like system using the wrong/dated library?
3- Can I delete the files in the userdata without losing app, user data etc? Where are those files?
Drifus Dreskeke said:
I flashed lrx21l yesterday, manually. But I flashed the vendor.img inside userdata and NOT in the "vendor" partition. Rooted and running ok.
Trying to fix that mistake I flashed lrx21l vendor.img again, but using "fastboot flash vendor vendor.img". All good.
And now, I manually flashed lrx21q, rooted using CF-Auto-Root and everything seems fine!
My questions are:
1- Am I with duplicate vendor files?
2- Will I have issues like system using the wrong/dated library?
3- Can I delete the files in the userdata without losing app, user data etc? Where are those files?
Click to expand...
Click to collapse
Don't worry about it. Everything is ok
Sent from my Nexus 9 using XDA Free mobile app
NEW VERSION AVAILABLE!
https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
----------
Inspired by this thread!
Dumped via non-flashed (only live booted) TWRP so I can dump the original recovery too.
Can be flashed in fastboot mode!
To flash these images reboot your watch, swipe from the top left to the bottom right corner when you see the ASUS logo and connect it to your PC.
Then in a command line enter:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Download ALL-IN-ONE zip (system.img, boot.img, recovery.img): Dropbox (262MB) - OneDrive Backup
Download recovery.img: Dropbox (16 384KB) - OneDrive Backup
Download boot.img: Dropbox (16 384KB) - OneDrive Backup
If you need more partitions tell me below, I've only included these ones so far because I know they won't contain any personal or device specific information and should be flashable on other devices too. However I've dumped every single one existing on the ZW2
Please check your file, system.img have problem
leap_ahead said:
Please check your file, system.img have problem
Click to expand...
Click to collapse
What problem you mean? While flashing?
EpicLPer said:
What problem you mean? While flashing?
Click to expand...
Click to collapse
Invalid system parse
leap_ahead said:
Invalid system parse
Click to expand...
Click to collapse
Just to make sure, you do have unpacked the ZIP and flashed the system.img via fastboot, right? Not that you renamed the ZIP to IMG lol
EDIT: Okay, tried it myself and I'm getting the same error... Weird...
EpicLPer said:
Just to make sure, you do have unpacked the ZIP and flashed the system.img via fastboot, right? Not that you renamed the ZIP to IMG lol
EDIT: Okay, tried it myself and I'm getting the same error... Weird...
Click to expand...
Click to collapse
I know my friend! I use the other and is ok
leap_ahead said:
I know my friend! I use the other and is ok
Click to expand...
Click to collapse
Okay, I have no idea how to make a fastboot flashable image out of the dd system.img I made... Sorry
Flashing ok
I flashed this via fastboot without probs. system.img has been flashed splitted into some chunks.
Device booted ok. All fine.
t.daun said:
I flashed this via fastboot without probs. system.img has been flashed splitted into some chunks.
Device booted ok. All fine.
Click to expand...
Click to collapse
Hm, maybe there are some old fastboot versions around that don't know how to handle a "new system image"? Weird...
t.daun said:
I flashed this via fastboot without probs. system.img has been flashed splitted into some chunks.
Device booted ok. All fine.
Click to expand...
Click to collapse
Invalid,!!
EpicLPer said:
Okay, I have no idea how to make a fastboot flashable image out of the dd system.img I made... Sorry
Click to expand...
Click to collapse
I'm using "ext2simg".
I used to use "img2simg" but it caused trouble.
In Ubuntu it's easy peasy going (Win? try Ubuntu on Linux on Windows. Win 10 only)
Code:
sudo apt install android-tools-*
ext2simg <inputfile> <outputfile>
BTW: .simg is something I invented myself.
ranf said:
I'm using "ext2simg".
I used to use "img2simg" but it caused trouble.
In Ubuntu it's easy peasy going (Win? try Ubuntu on Linux on Windows. Win 10 only)
Code:
sudo apt install android-tools-*
ext2simg <inputfile> <outputfile>
BTW: .simg is something I invented myself.
Click to expand...
Click to collapse
Awesome! Thanks a ton man! Did that now and it worked flawlessly
@EpicLPer https://forum.xda-developers.com/zenwatch-2/general/ota-url-sparrow-build-m6e70c-t3601468 u got this ota alrdy? i cant update like always. fastboot flashable imgs would be highly appreciated ^^
can it be the root installed through live booted twrp or the now unlocked bl that prevents normal updates for me? i never did a single ota on any of my phones always custom rom so idk much about ota's.
Sent from my Nexus 6P using XDA Labs
NEW VERSION AVAILABLE!
https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3601596
leap_ahead said:
Invalid,!!
Click to expand...
Click to collapse
Hello, do you have a Chinese version of the brush bag?
I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!
saagr_2800 said:
I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!
Click to expand...
Click to collapse
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.
oneplus x fastboot images of rom
seacowx said:
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.
Click to expand...
Click to collapse
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Thats disaster. Have you tried any steps i suggested earlier?
Re-check unlocked bootloader? and try flashing compatible TWRP within fastboot? hows the results?
• Download full ROM 3.1.4 zip and place in your computer (ADB folder)
• Directly boot to TWRP and use "ADB sideload" of full ROM zip (using ADB command)
Use search button (or just google it) how to use ADB sideload.
→Worst case scenario, follow the mega unbrick guide that should help you. OK. goodluck.
Note: Easiest way, contact oneplus support team for remote session. They will help you
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that
can't flash factory oneplus rom from recovery
saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)
saagr_2800 said:
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)
Click to expand...
Click to collapse
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me
saagr_2800 said:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me
Click to expand...
Click to collapse
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.
seacowx said:
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.
Click to expand...
Click to collapse
I tried from mm recovery as well it says installation failed
saagr_2800 said:
I tried from mm recovery as well it says installation failed
Click to expand...
Click to collapse
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.
dchrono said:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that
Click to expand...
Click to collapse
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.
seacowx said:
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.
Click to expand...
Click to collapse
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks
Part.0 said:
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks
Click to expand...
Click to collapse
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
lol, nice thanks a lot man! im not intend to messing up with my modem either lol
Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
To repair EFS issues when fastboot only available. There are other ways as well however OP mentioned fastboot available only.
Edit: @Part.0 if you would have read OP correctly, you would have noticed he mentioned that he flashed the wrong modem files and my solution along with a fastboot reboot which I didn't mention would have solved his problem. fastboot erase modemst1/2 although you only know it for solving modem/GPS issues are also partitions. Remember our job here is not to convince @Part.0 of our solutions, next time a thank you would do well for teaching you something.
seacowx said:
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.
Click to expand...
Click to collapse
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)
saagr_2800 said:
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)
Click to expand...
Click to collapse
Ok since i can't reproduce your issue on this one, so i can't find the right solutions for your case.
• Unlocked bootloader + Working Recovery + Fastboot + Full ROM zip file
Those should enough fixing your issue.
Perhaps i missed something, like corrupted partitions (firmware). Maybe another user experienced with the issue can help you out.
Best luck for you.
Note: Maybe our friend here can help you out @dchrono or willing to help you. Thank you.
Ps: Try mountng of "Firmware" in mount section before flashing full ROM. So it will mounted (Firmware, System, data, cache) But wait, ask out before you do. Finger crossed
Download these files
https://www.androidfilehost.com/?fid=24269982087019810
http://www.mediafire.com/file/8g9v5fsslnbf1r6/Qualcomm+Driver+Setup.zip
1 switch off Oneplus x forced
2 install Qulacomm usb driver
3 press volume up button n connect with PC
4 extract Oneplus x unbrick tool
5 run msm downloder and click on start
6 if complete flashing flash stock ROM via memory card
Contact me on. WhatsApp if not success
+917756968834
seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
can it be done with TWRP recovery?
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