Database Develop

TF701T - getting FAILED (remote: Unsupport Flash Unsparse System Image.)

I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s

I've managed to resolve it for anyone else that might read this....
Follow the guide here https://forum.xda-developers.com/tr...f701t-nvflash-unbrick-solutiontested-t3742848 and use the NvFlash TF701T Unbrick tool, you need to do a bit of prep but it worked for me
Big thanks to Mr.Bin for this fix.
Cheers and good luck
Martin
martinnut said:
I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
Click to expand...
Click to collapse

[ROM][SOFIA*/RAV*][10][UNOFFICIAL] OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
No data with carriers using Verizon network
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/MotoG8Power
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Power
Contributors
vache, Dark98
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Beta Release Date: 2020-08-02
Created 2020-08-02
Last Updated 2020-08-28

I wish I had the G8 power since there is a custom rom.
You may want to move this thread to a dedicated Moto G 8 Power Thread.
One may think this rom is for the Moto G Power.

jhjhjhjhjhjh said:
I wish I had the G8 power since there is a custom rom.
You may want to move this thread to a dedicated Moto G 8 Power Thread.
One may think this rom is for the Moto G Power.
Click to expand...
Click to collapse
I wish such forum exists.
That's why i put that big red warning text.
But making a commonized build shouldn't be hard, if you're ready to test, let me know.

Work on Moto g8 power 2041-1?

wanderleiAlfa said:
Work on Moto g8 power 2041-1?
Click to expand...
Click to collapse
Yes, XT2041-1 and XT2041-3 (sofiar).

Any way to get this without G apps? Trying to degoogle my life.

Is this just the stock rom?

BMO0071 said:
Is this just the stock rom?
Click to expand...
Click to collapse
No, this is OmniROM.
Juno_ said:
Any way to get this without G apps? Trying to degoogle my life.
Click to expand...
Click to collapse
Should be doable for the next build.

Weird. I flashed it and I was still on stock ?

Is OmniSwitch included in this ROM?
Thanks for your work.

Ulfys said:
Is OmniSwitch included in this ROM?
Thanks for your work.
Click to expand...
Click to collapse
Yes.

vache said:
I wish such forum exists.
That's why i put that big red warning text.
But making a commonized build shouldn't be hard, if you're ready to test, let me know.
Click to expand...
Click to collapse
Yes .
Thanks ..
Whenever you upload a build for the Moto g power I'll test it...

@vache
Just tried this on the g power and it bootloops.
Couldn't get a log.
Would be great if a unified build for sofia/sofiar could be achieved

I tried flashing this on my Sofiar (g8), I can flash boot.img and dtbo.img but when I try to flash system.img I get the following error:
sending sparse 'system' (786384 KB)...
OKAY [ 18.328s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.343s
I looked it up and this message on Motorola devices usually means that either the bootloader is locked or the .img attempted to flash is older than the one already installed.
My bootloader is unlocked and the last OTA (system) update I applied was on May, so I'm not sure what's going on.
I tried "fastboot erase system" and I get:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)

Ulfys said:
I tried flashing this on my Sofiar (g8), I can flash boot.img and dtbo.img but when I try to flash system.img I get the following error:
sending sparse 'system' (786384 KB)...
OKAY [ 18.328s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.343s
I looked it up and this message on Motorola devices usually means that either the bootloader is locked or the .img attempted to flash is older than the one already installed.
My bootloader is unlocked and the last OTA (system) update I applied was on May, so I'm not sure what's going on.
I tried "fastboot erase system" and I get:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Are you sure you rebooted in fastbootd mode and not fastboot ?
Also you may have to download the file again, previous link was pointing to a build for a different device. Sorry for that. (make sure it's omni-10-20200802-sofiar-IMG.zip)

Q9Nap said:
@vache
Just tried this on the g power and it bootloops.
Couldn't get a log.
Would be great if a unified build for sofia/sofiar could be achieved
Click to expand...
Click to collapse
Unified test build for sofia/sofiar/sofiap/rav : omni-10-20200806-sofia-rav-IMG.zip

vache said:
Are you sure you rebooted in fastbootd mode and not fastboot ?
Also you may have to download the file again, previous link was pointing to a build for a different device. Sorry for that. (make sure it's omni-10-20200802-sofiar-IMG.zip)
Click to expand...
Click to collapse
Hey, you were right. I couldn't boot to fastbootd after installing TWRP, so I was on fastboot mode instead.
I used the Rescue and Smart Assistant and with everything back to stock, including the recovery, I can boot to fastbootd.
However, when I try to flash boot, I get:
sending 'boot' (65536 KB)...
OKAY [ 1.437s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.437s
It can send "boot" but not write it.

Reflashed today on my g8 power and got a boot loop halp
Edit: flashed unified test build and the rom booted sucessfully

vache said:
Unified test build for sofia/sofiar/sofiap/rav : omni-10-20200806-sofia-rav-IMG.zip
Click to expand...
Click to collapse
Just tried this and it boots, but touchscreen doesn't work.
Popup to enable adb appears on boot, but cannot enable, and so cannot get a log, unfortunately.
Progress though!

Ulfys said:
Hey, you were right. I couldn't boot to fastbootd after installing TWRP, so I was on fastboot mode instead.
I used the Rescue and Smart Assistant and with everything back to stock, including the recovery, I can boot to fastbootd.
However, when I try to flash boot, I get:
sending 'boot' (65536 KB)...
OKAY [ 1.437s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.437s
It can send "boot" but not write it.
Click to expand...
Click to collapse
Something wrong on your side, make sure you're using the last fastboot version.
Q9Nap said:
Just tried this and it boots, but touchscreen doesn't work.
Popup to enable adb appears on boot, but cannot enable, and so cannot get a log, unfortunately.
Progress though!
Click to expand...
Click to collapse
https://drive.google.com/file/d/19oiGM7yRzbxOsZXd4vYKDpbTW8ajNOU5/view?usp=sharing
By using the product.img you will have adb working.
I would need kernel logs : adb shell dmesg > dmesg.txt

[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [OTA][SODP]

Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...​
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta

Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-

Reserved

First

At last The guide, source code looks great! Will install, check it next

hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.

bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!

Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.

bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:

Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?

Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).

Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse

xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)

xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).

Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools

Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.

Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?

KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!

Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'

Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!

[ROM][ResurrectionRemix 8.6.x][RAV*/SOFIA*][UNOFFICIAL][NO GAPPS]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
​Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome ​
combination of performance, customization, power and the most new features, brought directly to your Device.​
​
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!​
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.​
​
​
Install the stock recovery.img if you have previously installed twrp.
1. Extract the zip to your adb/fastboot directory, reboot to bootloader and open a CMD window.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta images.
Code:
[/B][/B][/CENTER]
[B][CENTER]fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
​
4. Wipe userdata.
Code:
fastboot -w
5. Reboot, Profit.
(OPTIONAL)
6. If you want to install TWRP/gapps/magisk, do so after you continue through the installation steps to the home screen.
If you have the Moto G8/G Fast and your display cutout is not right, enable the overlay via ADB:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
1. Starting screen casting/mirroring causes a reboot.
2. The in-built screen recorder also causes a reboot when started.
Dodgy Screen Recorder Fix :laugh:: Download and install the attached apk below, change the quick setting tile to the new one at the bottom of the list, and you should be able to record. (Its the screen recorder app from BlissRom, nothing malicious )
3. Let me know :good:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
​

To update to the latest version without wiping:
UPDATING FOR GAPPS/MAGISK USERS
1. Install the images as usual in fastbootd
2. Power off and boot to TWRP
3. Install GAPPS and/or Magisk
4. Reboot, profit.
UPDATING FOR NON GAPPS/Magisk USERS
Skip steps 2. and 3. from above.

Cant figure out which drive i uploaded the old files to at the moment
But heres the 8.6.9 May security patch update.
Not much new, added a KCAL enabled kernel as default, and added a color control app (root needed), fixed face unlock (g power) and added the moto clock widgets.
RR - May Patch - Google Drive
drive.google.com
TWRP zip and fastboot d images, no gapps only. Theres also some flame gapps in the folder too that i use and work well.

I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?

NeoSDAP said:
I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?
Click to expand...
Click to collapse
Try flashing product instead of system first.

Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.

_huck_ said:
Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.
Click to expand...
Click to collapse
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.

I am SO HAPPY that resurrection remix has just come out for the Moto G Power. I have been waiting!!! I just saw this today, but I can't seem to get it to work.. As seems to happen when people are trying to root the moto G power.. The touch screen will stop working.. I did get mine to root, using this page:
Messed up trying to root
i know there are other threads on this topic. But after going through them I cant find the fix. I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works. I used lmsa to download the stock rom...
forum.xda-developers.com
But I do not know how to apply the same fix after I try to install resurrection remix? I do not have touch screen working after I load.
I am using adb, not sure it twrp is available for moto g power yet, and if that would be the way to get it to work?
I'm using moto g power, sofia variant (usa).. XT2041-4

I tried again and I'm actually getting the following errors:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805263360 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.418s]
writing 'boot'...
OKAY [ 0.821s]
finished. total time: 2.248s
PS C:\adb> fastboot flash system system.img
target reported max download size of 805263360 bytes
sending sparse 'system' (786388 KB)...
OKAY [ 18.732s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.749s
PS C:\adb> fastboot flash product product.img
target reported max download size of 805263360 bytes
sending 'product' (575564 KB)...
OKAY [ 12.511s]
writing 'product'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.539s
PS C:\adb>

@cxskate
You aren't in fastbootd. You are in fastboot mode. From the screen you are at in the above screenshot, type fastboot reboot fastboot.
You should reboot to a new screen with fastbootd in red across the top.
Flash the images there.

I'm still having a problem...
My phone does not enter into FastBootD mode... The screen on my phone doesn't change at all when I enter the command, and my computer adb window reads the following:
Please any advice? Very much appreciated.
PS C:\adb> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>

Beetle84 said:
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.
Click to expand...
Click to collapse
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!

_huck_ said:
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!
Click to expand...
Click to collapse
Awesome! What are the little things? I'll add to the bug list

I'm going for a Degoogled setup and this rom is the first one that worked with microg without hassles. I installed minMicrog standard and Majisk, toggled the baked in signature spoofing, and was up and running in minutes. VERY AWESOME!

Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks

etienne_9000 said:
Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks
Click to expand...
Click to collapse
Google 'unlock Motorola bootloader'
You need a code from Motorola.

Beetle84 said:
Google 'unlock Motorola bootloader'
You need a code from Motorola.
Click to expand...
Click to collapse
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.

etienne_9000 said:
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.
Click to expand...
Click to collapse
Did you tick the OEM unlock allowed option in developer settings?

Trying to figure out how to load gapps on with adb now??
I actually was finally able to enter FastBootD mode using a different method I found on youtube, but wasvstill getting errors when I tried to flash.. FAILED (remote: No such file or directory)
UPDATE I copied all the new files to the adb folder on the C: drive and i got it to work.. Got RR up and running, but still..
I'm trying to figure out how to load gapps on with adb now??
Method I used to get fastboot D:
(
),

Beetle84 said:
Did you tick the OEM unlock allowed option in developer settings?
Click to expand...
Click to collapse
Yes i did. Just tried again to "fastboot oem get_unlock_data" and still getting "FAILED (remote: Command not supported in default implementation)"

Question How to install custom recovery TWRP?

I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?

AceSheep said:
I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?
Click to expand...
Click to collapse
fastboot boot twrp.img
Go ti advanced and install current twrp

Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one

bambamGN2 said:
Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one
Click to expand...
Click to collapse
I use a type-c hub to connect a wireless mouse and it works

I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file

AceSheep said:
I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file
Click to expand...
Click to collapse
fastboot boot twrp_UNOFFICIAL.img
This work for sure

This topic is great, but I'm afraid many of us would totally miss the information in here, do anyone has the will to turn the information here into a little "how to TWRP" guide as a topic here? That would be awesome!

My device is Redmi Note 10 5G China and the EEA rom flashed. Using twrp will get stuck in the logo and cannot enter.
Before that, I can start twrp using China rom. I'm still looking for reasons
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help

AceSheep said:
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help
Click to expand...
Click to collapse
No but maybe this helps????
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

i suggest for now stay on stock recovery. you can root phone installing magisk via fastboot. and the only way to try custom rom is flashing the gsi ported generic rom. the nippon gsi telefram group have a lot of gsi. but my advice is wait miu13 update. most of gsi have audio incompatibility. but if you like aosp roms this is the only way. mtk full custom roms for our device dont exist