Database Info

sparse error

Hi, So I am trying to restore to factory firmware (Telus/Koodo) firmware and I keep getting this error:
Code:
error: cannot load 'system.img_sparsechunk.1 ': No Error
I get the error for all the sparsechunks. I'm not sure what to do. If this is any help My phone is unlocked status code 3. However, it is stuck in bootloop.
Thanks!

Canuckfan101 said:
Hi, So I am trying to restore to factory firmware (Telus/Koodo) firmware and I keep getting this error:
Code:
error: cannot load 'system.img_sparsechunk.1 ': No Error
I get the error for all the sparsechunks. I'm not sure what to do. If this is any help My phone is unlocked status code 3. However, it is stuck in bootloop.
Click to expand...
Click to collapse
What are the actual files you have downloaded called? It could be: system.img_sparsechunk1 - also flash them in order, system.img_sparsechunk0, system.img_sparsechunk1, system.img_sparsechunk2

Hi! Thanks for the reply! I checked the name and I did not enter it in correctly! It now works! But antoher problem has occured! I managed to lock the device ( i ended the program with fastboot oem lock) and the moto g said locked! in blue. I thought it got stuck so i pressed the power button. The warning unlocked bootloader still shows but the phone is Locked Status 2. The CMD prompt gave me this when I entered fastboot oem lock
Code:
...
FAILED (status read failed (too many links))

There are already numerous threads on the subject of 'fastboot oem lock failed' - I don't know why it fails.
This is one alternative solution:
http://forum.xda-developers.com/showthread.php?t=2548530​

"FAILED (remote: flash write failure)"

Hello,
I was facing a lot of issues with my YUPHORIA. So, I tried to flash it using the official instructions on official forum using Fastboot.
The flashing got stuck when it was trying to flash the "system" partition. I disconnected the cable and tried the flashing process again.
Now, I am able to flash everything else except "system"
It is giving an error -
"FAILED (remote: flash write failure)"
ADB is not detecting my phone.
QFIL is also showing "No Ports Found"
However, Fastboot is working fine.
I donot have TWRP on my phone as of now.
Please help !

I am having exact same problem. Were you able to find solution for it?

Same issue here
Did you get the final solution?
I cant not flash system.img to my softbricked Yu Yuphoria 5110 even with the latest version of adb and fastboot and even with the -S option! Nothing works! Can't flash only system.img, other images are getting flashed. Pl help!

How to change the red boot warning back to the normal unlocked bootloader start warn.

To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.

Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix

Linux_fart_18.3 said:
To be clear im trying to bring back the old "boot loader is unlocked and software integrity cannot be guaranteed" boot message from the red one that says "Your device is corrupt. It can’t be trusted and may not work properly." Now I no this topic has already been on the forums but I read them, and made several attempts to fix the issue but was unsuccessful. every time I end up losing my all my **** and as soon as i upgrade to the latest pie ota it goes right back to the red boot message. One time I even hard bricked my phone and had to use the msmdownloadtool to get me back to hydrogen os and still the same thing happend when I upgraded to pie. Can anyone point me in the right direction on how to fix this problem.
p.s. I know its not a "problem" really but its one of those things that’s been pestering me for over a month. thanks for your concern.
Click to expand...
Click to collapse
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter

abasba said:
Did you use in-built updater or flashed pie via twrp?
If you flashed by twrp, you may need to flash twice for both a and b bootslots.
You may try to lock bootloader, use msm again then update pie.
After that try to unlock it may fix
Click to expand...
Click to collapse
unfortunate for me ive tried all the above except locking bootloader before msm which i have also tried both separtatly but not in that order.

ab123pro said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command

Linux_fart_18.3 said:
ill give it a try thanks also do you know the command to switch partitions when in fastboot? im stuck on a partion and stuck only rebooting to fastboot cant flash twrp img or boot img id really appreciate it any know the command
Click to expand...
Click to collapse
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root

ab123pro said:
Run "fastboot boot twrp-3.3.1-3-enchilada.img" in command line https://androidfilehost.com/?fid=6006931924117908950
then from within twrp flash twrp installer - https://androidfilehost.com/?fid=6006931924117908949
and magisk if you want root
Click to expand...
Click to collapse
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.

Linux_fart_18.3 said:
sudo fastboot boot ./twrp-3.2.3-x_blu_spark_v9.91_op6.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.924s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.939s
every time. thats why im in need of a command to get me back to the (b) partition and also
fastboot –set-active=_b just get me "waiting for device" and nothing more.
Click to expand...
Click to collapse
looks like your boot partition got corrupted some how im not sure tho
maybe try to flash one of those fastboot roms - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

Oneplus 7 Pro Nasty Brick - Custom ROM, no root, no TWRP - help?

Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.

Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.

I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862

x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.

Wiped OS, cannot process past bootloader

I wiped my OS and was having issues installing a custom ROM through TWRP. My phone rebooted and now I'm stuck in the bootloader and unable to get back into TWRP. I've tried using fastboot, but that also fails:
Code:
~\Downloads\TWRP>fastboot boot twrp-3.5.2_9-0-enchilada.img
Sending 'boot.img' (32604 KB) OKAY [ 0.823s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Is there some way I can recover (even if back to stock), or am I screwed?
Thanks

zodac01 said:
I wiped my OS and was having issues installing a custom ROM through TWRP. My phone rebooted and now I'm stuck in the bootloader and unable to get back into TWRP. I've tried using fastboot, but that also fails:
Code:
~\Downloads\TWRP>fastboot boot twrp-3.5.2_9-0-enchilada.img
Sending 'boot.img' (32604 KB) OKAY [ 0.823s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Is there some way I can recover (even if back to stock), or am I screwed?
Thanks
Click to expand...
Click to collapse
You are not screwed,2 choices you have-flash fastboot stock Rom or use MSM tool,for me personally i always use fastboot roms.Good luck

zodac01 said:
I wiped my OS and was having issues installing a custom ROM through TWRP. My phone rebooted and now I'm stuck in the bootloader and unable to get back into TWRP. I've tried using fastboot, but that also fails:
Code:
~\Downloads\TWRP>fastboot boot twrp-3.5.2_9-0-enchilada.img
Sending 'boot.img' (32604 KB) OKAY [ 0.823s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Is there some way I can recover (even if back to stock), or am I screwed?
Thanks
Click to expand...
Click to collapse
You can revive any ROM mate. All you need is patience and a small knowledge in debugging the error.
If you are stuck on Bootloader. Try flashing rom on both slots from bootloader directly
Below link has process to do so
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
If you can boot to recovery, try flashing roms directly by downloading stock roms. If you get stuck, try postng error message with screenshot using another mobile.