It's almost done...
D!OS is rolling out the next Days. It's pretty basic for now. Based on latest Android 12.1/12L with Google Apps.
If You want to be one of the first who uses this new Xperia exclusive OS, leave a Comment and become a Tester!
Need Testers for J9110 Xperia 1 Dual Sim
J8110 Xperia 1 Single Sim Builds will come later. But feel free to try out the Xperia 1 Dual Sim Variant...
I'm in!
mikaelgr717 said:
I'm in!
Click to expand...
Click to collapse
Great. You can grab the Zip from here once it's uploaded:
Dev Ice Technologies - AOSXP
AOSXP (PREVIEW)
sites.google.com
Just extract the Zip to Your Fastboot Folder and double click the AOSXP Flash .bat File
Download and extract the Xperia Software Binaries from Sony to the same folder
Rename the Image to oem.img and run the OEM Flash .bat File to flash the Binaries
Done. You can access the Recovery by holding Volume down while turning on the Device. In case You want to wipe or so...
Please leave Feedback here once You tried it
I give it a try.
(J9110)
It's up. Camera may not work and same for Mobile Data but thats due to the SODP and should be fixed soon...
And thanks for Your Interest Folks! Really looking forward to let AOSXP grow as owner of Dev Ice Technologies (The Company behind it). Be prepared for awesome Things!
im stuck on sony boot logo, im not sure maybe i use a wrong Software Binaries??
SW_BINARIES_FOR_XPERIA_ANDROID_12_4.19_V1C_KUMANO.ZIP
xpt1 said:
im stuck on sony boot logo, im not sure maybe i use a wrong Software Binaries??
SW_BINARIES_FOR_XPERIA_ANDROID_12_4.19_V1C_KUMANO.ZIP
Click to expand...
Click to collapse
You did everything right i guess. So it stays at the Sony boot logo not the Android Bootanimation?
Sounds like an SElinux issue in this case. I will set it to permissive and upload an new Zip. Thanks for Your Feedback btw!
Miustone said:
You did everything right i guess. So it stays at the Sony boot logo not the Android Bootanimation?
Sounds like an SElinux issue in this case. I will set it to permissive and upload an new Zip. Thanks for Your Feedback btw!
Click to expand...
Click to collapse
yes it stop at the sony logo.
xpt1 said:
yes it stop at the sony logo.
Click to expand...
Click to collapse
Dang. I played around with Permissions and SElinux. Should be fixed now. I also found some neat things out. The next drop should boot and include some cool stuff from the Pixels
Ill keep You informed...
Miustone said:
Dang. I played around with Permissions and SElinux. Should be fixed now. I also found some neat things out. The next drop should boot and include some cool stuff from the Pixels
Ill keep You informed...
Click to expand...
Click to collapse
did you update/upload the fixed AOSXP_J9110.zip ?
i tryed it again but same problem stuck on sony logo
xpt1 said:
did you update/upload the fixed AOSXP_J9110.zip ?
i tryed it again but same problem stuck on sony logo
Click to expand...
Click to collapse
{
"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"
}
No, but work is going on. 10 Hours+ each day
Any news about AOSXP for now?
Miustone said:
伟大的。上传后，您可以从此处获取 Zip：
Dev Ice Technologies - AOSXP
AOSXP (PREVIEW)
sites.google.com
只需将 Zip 解压缩到您的 Fastboot 文件夹，然后双击 AOSXP Flash .bat 文件
从 Sony 下载 Xperia 软件二进制文件并将其解压缩到同一文件夹
将映像重命名为 oem.img 并运行 OEM Flash .bat 文件以刷新二进制文件
完毕。您可以通过在打开设备时按住音量来访问恢复。万一你想擦什么……
尝试后请在此处留下反馈
Click to expand...
Click to collapse
惯于
New Builds incoming! Be prepared for something You haven't ever seen before <3
#D!OS
Miustone said:
New Builds incoming! Be prepared for something You haven't ever seen before <3
#D!OS
Click to expand...
Click to collapse
Can you also insert the sony camera apk, I need the dedicated button, the button unfortunately does not work with gcam
D!OS_J9110.zip tested right now, still stuck on sony logo.
xpt1 said:
D!OS_J9110.zip tested right now, still stuck on sony logo.
Click to expand...
Click to collapse
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Miustone said:
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Click to expand...
Click to collapse
Miustone said:
Time for troubleshooting. What did the Script Say? Flashing was fine?
Flashed latest and correct oem with the other Script? Are You on latest Android Stock before flashing D!OS?
Click to expand...
Click to collapse
my latest android stock: J9110_Customized EU_55.2.A.4.332-R10C
oem: SW_binaries_for_Xperia_Android_12_4.19_v1c_kumano.img ( renamed to oem.img )
i will flash one more time an copy the script.
D!OS installation started...
Setting current slot to 'a' OKAY [ 0.016s]
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.188s]
Writing 'dtbo_a' OKAY [ 0.031s]
Finished. Total time: 0.266s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.203s]
Writing 'dtbo_b' OKAY [ 0.047s]
Finished. Total time: 0.297s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.015s]
Writing 'vbmeta_a' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta_b' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'boot_a' (65536 KB) OKAY [ 1.515s]
Writing 'boot_a' OKAY [ 0.266s]
Finished. Total time: 2.203s
Sending 'boot_b' (65536 KB) OKAY [ 1.531s]
Writing 'boot_b' OKAY [ 0.251s]
Finished. Total time: 2.235s
Sending 'vendor_a' (117496 KB) OKAY [ 2.745s]
Writing 'vendor_a' OKAY [ 0.000s]
Finished. Total time: 2.776s
Sending 'vendor_b' (117496 KB) OKAY [ 2.777s]
Writing 'vendor_b' OKAY [ 0.000s]
Finished. Total time: 4.104s
Sending sparse 'system_a' 1/5 (775200 KB) OKAY [ 18.492s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 2/5 (774120 KB) OKAY [ 18.532s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 3/5 (774120 KB) OKAY [ 18.708s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 4/5 (774120 KB) OKAY [ 18.525s]
Writing 'system_a' OKAY [ 0.016s]
Sending sparse 'system_a' 5/5 (566052 KB) OKAY [ 13.684s]
Writing 'system_a' OKAY [ 0.000s]
Finished. Total time: 89.373s
Sending sparse 'system_b' 1/5 (775200 KB) OKAY [ 18.204s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/5 (774120 KB) OKAY [ 18.467s]
Writing 'system_b' OKAY [ 0.016s]
Sending sparse 'system_b' 3/5 (774120 KB) OKAY [ 18.560s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 4/5 (774120 KB) OKAY [ 18.448s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 5/5 (566052 KB) OKAY [ 13.607s]
Writing 'system_b' OKAY [ 0.000s]
Finished. Total time: 94.854s
Sending 'userdata' (544 KB) OKAY [ 0.016s]
Writing 'userdata' OKAY [ 0.000s]
Finished. Total time: 7.708s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
D!OS installed. Press any Key to exit...
XPERIA OEM installation started...
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.005s
Sending 'oem_a' (279196 KB) OKAY [ 7.131s]
Writing 'oem_a' OKAY [ 13.073s]
Finished. Total time: 20.283s
Sending 'oem_b' (279196 KB) OKAY [ 6.522s]
Writing 'oem_b' OKAY [ 13.005s]
Finished. Total time: 19.558s
Erasing 'userdata' OKAY [ 76.212s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 28074734 4k blocks and 7020544 inodes
Filesystem UUID: b91d1bf4-c4b1-11ec-a85f-5f6820032de7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (544 KB) OKAY [ 0.016s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' FAILED (remote: 'Erasing is not allowed for partition
')
fastboot: error: Command failed
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
XPERIA OEM installed. Press any Key to exit...
Related
I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.
Latheman said:
I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.
Click to expand...
Click to collapse
is this a 926 or 925
if 926
use rsd lite and this guide form @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 i would recommend the full script since you are already unlocked and it was a used phone
if 925
same procedure but with the correct sbf from http://sbf.droid-developers.org/
I did this earlier. Same problem
Latheman said:
I did this earlier. Same problem
Click to expand...
Click to collapse
try this utility. it is a special version to fix certain issues that cant be fixed with fastboot and rsd.
watch the dialog and let me know if any operations fail, or copy and paste the output here for me to see.
i may have to update it for you if a couple specific things fail.
windows or linux?
Latheman said:
windows or linux?
Click to expand...
Click to collapse
windows only
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Latheman said:
windows or linux?
Click to expand...
Click to collapse
flash in fastboot same as the rest.
OK thanks. give me 10 minuets
this phone has the 9/9/14 update that won't be a problem right? just making sure
Latheman said:
this phone has the 9/9/14 update that won't be a problem right? just making sure
Click to expand...
Click to collapse
it wont be a problem, but some parts will fail. im downloading the files now to compare the parts i would like to see work.
either way, try that for now and let me know how it goes. there should be no added danger, the trust zone and partition files are what could fail, neither can be downgraded, so i dont see it making things worse if it doesnt work.
the phone says update gpt-main partition failed then the terminal end is FAILED (remote failure)
here is the output on the computer, sorry it is so long
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.187s
sending 'sbl2' (126 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.172s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.370s
sending 'rpm' (140 KB)...
OKAY [ 0.029s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.315s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.200s
sending 'aboot' (256 KB)...
OKAY [ 0.039s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.346s
sending 'modem' (30720 KB)...
OKAY [ 2.299s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.464s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.187s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.083s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'logo' (854 KB)...
OKAY [ 0.083s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.238s
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.929s
sending 'recovery' (10240 KB)...
OKAY [ 0.805s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.969s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'system' (30720 KB)...
OKAY [ 2.357s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 2.447s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.188s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.009s
Hit ENTER to return.
Latheman said:
here is the output on the computer, sorry it is so long
Click to expand...
Click to collapse
dammm
my file is almost done, let me compare a couple md5's from the old update and ill get right back to ya with what it looks like.
---------- Post added at 06:35 PM ---------- Previous post was at 06:24 PM ----------
@Latheman
ok, they changed the partition table again, not saying the phone is fixable, but this is the best chance i could have wanted to fix it.
its going to take me 1/2 hour to fix the script, and an hour (barring issue) to upload it.
ill send it over as soon as its done, if not tonight, then tomorrow.
Thank-you
Latheman said:
Thank-you
Click to expand...
Click to collapse
test flash on my updated phone, only tz failed because i removed it, but will be in your version as you already took it.
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.015s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.859s]
finished. total time: 0.874s
sending 'sbl1' (101 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
OKAY [ 0.648s]
finished. total time: 0.668s
sending 'sbl2' (127 KB)...
OKAY [ 0.183s]
writing 'sbl2'...
OKAY [ 1.033s]
finished. total time: 1.216s
sending 'sbl3' (512 KB)...
OKAY [ 0.052s]
writing 'sbl3'...
OKAY [ 1.113s]
finished. total time: 1.165s
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.473s]
finished. total time: 0.496s
error: cannot load 'tz.mbn'
sending 'aboot' (256 KB)...
OKAY [ 0.193s]
writing 'aboot'...
OKAY [ 1.594s]
finished. total time: 1.788s
sending 'modem' (30720 KB)...
OKAY [ 2.320s]
writing 'modem'...
OKAY [ 2.680s]
sending 'modem' (19212 KB)...
OKAY [ 3.845s]
writing 'modem'...
OKAY [ 1.095s]
finished. total time: 9.944s
sending 'fsg' (165 KB)...
OKAY [ 0.027s]
writing 'fsg'...
OKAY [ 0.855s]
finished. total time: 0.882s
erasing 'modemst1'...
OKAY [ 1.698s]
finished. total time: 1.699s
erasing 'modemst2'...
OKAY [ 1.232s]
finished. total time: 1.232s
sending 'logo' (854 KB)...
OKAY [ 0.076s]
writing 'logo'...
OKAY [ 1.955s]
finished. total time: 2.032s
sending 'boot' (10240 KB)...
OKAY [ 0.784s]
writing 'boot'...
OKAY [ 5.946s]
finished. total time: 6.730s
sending 'recovery' (10240 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 4.749s]
finished. total time: 5.530s
sending 'system' (30720 KB)...
OKAY [ 2.324s]
writing 'system'...
OKAY [ 2.254s]
sending 'system' (30720 KB)...
OKAY [ 5.467s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.223s]
writing 'system'...
OKAY [ 0.015s]
sending 'system' (30720 KB)...
OKAY [ 4.727s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.983s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.718s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.729s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.646s]
writing 'system'...
OKAY [ 0.023s]
sending 'system' (30720 KB)...
OKAY [ 5.097s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 5.140s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.662s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.067s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.677s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.682s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.696s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.232s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.636s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.750s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.715s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.701s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.604s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.694s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.708s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.710s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.034s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.686s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (21722 KB)...
OKAY [ 4.040s]
writing 'system'...
OKAY [ 1.323s]
finished. total time: 285.670s
erasing 'tombstones'...
OKAY [ 2.049s]
finished. total time: 2.049s
erasing 'cache'...
OKAY [ 2.632s]
finished. total time: 2.632s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.005s
Hit ENTER to return.
so what should I do? remove a file from the folder you sent me?
Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
no, i was just showing you the new version is built, tested, working and uploading now.
so, when i post it later for you to try, this is pretty much a last resort script. if it doesn't work for you, the phone is likely gone.
---------- Post added at 07:42 PM ---------- Previous post was at 07:05 PM ----------
Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
ok she is done
http://www.mediafire.com/download/5mmd0jv84c51rvt/DROID_RAZR_HD_Utility_1.4gpt-2a_KK.rar
edit: just changed the download link to another version containing the tz file i forgot to replace, for whoever might need it in the future.
Thanks I'll try it soon.
Latheman said:
Thanks I'll try it soon.
Click to expand...
Click to collapse
i forgot to drop the tz file back in before i uploaded it, its no big deal and shouldnt matter, but you should drop this into the directory in the rare event it becomes needed.
https://www.dropbox.com/s/f27cfsjyewlnlu4/tz.mbn?dl=0
I tried it, and no soap, I think this one is a loss . (first one of every phone I have worked on). the BL is still unlocked so if anybody ever comes up with something in the future, or I can put something together I might be able to restore it.
Did you try to flash stock with rsd 6.1.5 and editing xml file, say removing tz line
Hello Friends! I'm Getting This Error While I'm Trying To Flash Stock Rom In Lenovo TB-8704X.
{
"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"
}
<!-----The Error Msg Start-----!>
Sending 'tz' (1519 KB) OKAY [ 0.071s]
Writing 'tz' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'sbl1' (378 KB) OKAY [ 0.039s]
Writing 'sbl1' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'rpm' (170 KB) OKAY [ 0.037s]
Writing 'rpm' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'aboot' (605 KB) OKAY [ 0.047s]
Writing 'aboot' FAILED (remote: 'Critical partition flashing is not allowed')
fastboot: error: Command failed
Sending 'devcfg' (38 KB) OKAY [ 0.037s]
Writing 'devcfg' OKAY [ 0.020s]
Finished. Total time: 0.111s
Sending 'keymaster' (220 KB) OKAY [ 0.026s]
Writing 'keymaster' OKAY [ 0.005s]
Finished. Total time: 0.160s
Sending 'cmnlib' (200 KB) OKAY [ 0.037s]
Writing 'cmnlib' OKAY [ 0.012s]
Finished. Total time: 0.122s
Sending 'cmnlib64' (254 KB) OKAY [ 0.036s]
Writing 'cmnlib64' OKAY [ 0.017s]
Finished. Total time: 0.110s
Sending 'tzbak' (1519 KB) OKAY [ 0.077s]
Writing 'tzbak' OKAY [ 0.013s]
Finished. Total time: 0.159s
Sending 'sbl1bak' (378 KB) OKAY [ 0.047s]
Writing 'sbl1bak' OKAY [ 0.016s]
Finished. Total time: 0.123s
Sending 'rpmbak' (170 KB) OKAY [ 0.036s]
Writing 'rpmbak' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'abootbak' (605 KB) OKAY [ 0.047s]
Writing 'abootbak' OKAY [ 0.018s]
Finished. Total time: 0.126s
Sending 'devcfgbak' (38 KB) OKAY [ 0.037s]
Writing 'devcfgbak' OKAY [ 0.010s]
Finished. Total time: 0.123s
Sending 'keymasterbak' (220 KB) OKAY [ 0.031s]
Writing 'keymasterbak' OKAY [ 0.009s]
Finished. Total time: 0.112s
Sending 'cmnlibbak' (200 KB) OKAY [ 0.036s]
Writing 'cmnlibbak' OKAY [ 0.005s]
Finished. Total time: 0.117s
Sending 'cmnlib64bak' (254 KB) OKAY [ 0.027s]
Writing 'cmnlib64bak' OKAY [ 0.011s]
Finished. Total time: 0.122s
Erasing 'boot' OKAY [ 0.027s]
Finished. Total time: 0.055s
Sending 'modem' (86016 KB) OKAY [ 3.267s]
Writing 'modem' OKAY [ 0.399s]
Finished. Total time: 3.836s
fastboot: error: cannot load 'system.img': No such file or directory
Sending 'cache' (6248 KB) OKAY [ 0.249s]
Writing 'cache' OKAY [ 0.040s]
Finished. Total time: 0.479s
fastboot: error: cannot load 'userdata.img': No such file or directory
Sending 'recovery' (16587 KB) OKAY [ 0.699s]
Writing 'recovery' OKAY [ 0.079s]
Finished. Total time: 0.896s
Sending 'dsp' (16384 KB) OKAY [ 0.641s]
Writing 'dsp' OKAY [ 0.085s]
Finished. Total time: 0.816s
Sending 'mdtp' (17390 KB) OKAY [ 0.724s]
Writing 'mdtp' OKAY [ 0.093s]
Finished. Total time: 0.919s
Erasing 'splash' OKAY [ 0.025s]
Finished. Total time: 0.057s
Sending 'splash' (313 KB) OKAY [ 0.047s]
Writing 'splash' OKAY [ 0.009s]
Finished. Total time: 0.182s
Erasing 'DDR' OKAY [ 0.018s]
Finished. Total time: 0.045s
Sending 'boot' (11741 KB) OKAY [ 0.366s]
Writing 'boot' OKAY [ 0.053s]
Finished. Total time: 0.723s
Rebooting OKAY [ 0.008s]
Finished. Total time: 0.023s
Press any key to continue . . .
<!-----Error Msg End-----!>
And One MOre Thing! In The Stock Rom, There Is system.img and userdata.img Files Are Missing.
I Have Downloaded Stock Rom From Many Popular Sites, But Those Files Are Missing Also There.
...
Then I Have Tryed To Flash With QFIL
But I Got These Error Here:
Can Any One Please Help Me About This? I Don't Have Any Recovery In This Devices. So I Have To Do This With PC.
Pls If U or Your Any Friend Know a Solution About This Then Tell ME PLS
<!-----More Attachment-----!>
Unlock Critical partitions by means of Fastboot then retry.
jwoegerbauer said:
Unlock Critical partitions by means of Fastboot then retry.
Click to expand...
Click to collapse
So How Can I Unlock It?
Code:
fastboot flashing unlock_critical
jwoegerbauer said:
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
Thanks A Lot. But There Is system.img and userdata.img File are Missing. Can U Please Help Me?
Looks like the ROM you try to flash is corrupted, because the 2 mentioned img-files are missing therein.
jwoegerbauer said:
Looks like the ROM you try to flash is corrupted, because the 2 mentioned img-files are missing therein.
Click to expand...
Click to collapse
No, I Don't think soo. I Have Downloaded Rom From Many Popular Site. But There's Also these files are missing. And In the QcomDloader Tool, When I Try to flash. It Says, "Cannot Read Rawprogram.xml" file
Well, you have a contrary opinion ...
If you're using the same .xml firmware in fastboot as you are in QPST or QFIL the system.img file is most likely system_1.img system_2.img and so on, quite a few of them. Just check your firmware and see what your missing files are named or if they are actually missing.
tek3195 said:
If you're using the same .xml firmware in fastboot as you are in QPST or QFIL the system.img file is most likely system_1.img system_2.img and so on, quite a few of them. Just check your firmware and see what your missing files are named or if they are actually missing.
Click to expand...
Click to collapse
Yes U Are Right! There Is System.img and userdata.img File Are Missing. But system_1.img to system_47.img (47 System.img files) and userdata_1.img to userdata_77.img (77 userdata.img files) are exist. But How Can I Flash Them with QFIL/QcomDloader/Fastboot Mode?? And The Raw program or other xml files are not damaged. I can open them with notepad++ and XML Language is All right.
[email protected] said:
Yes U Are Right! There Is System.img and userdata.img File Are Missing. But system_1.img to system_47.img (47 System.img files) and userdata_1.img to userdata_77.img (77 userdata.img files) are exist. But How Can I Flash Them with QFIL/QcomDloader/Fastboot Mode?? And The Raw program or other xml files are not damaged. I can open them with notepad++ and XML Language is All right.
Click to expand...
Click to collapse
ok, you are looking at the diff between using raw and sparse images. When you ask how to with QFIL/QcomDloader/Fastboot Mode you can't use them the same way. QFIL and the double handful of Qualcomm flashing utilities like it don't use fastboot, they use sahara. They are different protocols dealing with different formats. I linked a short tutorial to point you in the right direction, maybe, or I hope so anyway. tutorial
I found the hardware is different
US retail is 6/256
T-Mobile/Metro is 4/128
It may have negative impact if you cross flash ROM
I bit the bullet and attempted the flash...
It won't work, the vbmeta_system.img flashes fine with no issues (which is needed to flash an image to the system partition). It seems the ROM wont fit in the system ROM space completely, leading to corruption of the system partition. I'd definitely advise against trying this yourself.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRES31.Q2-11-103-2_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.161s]
Finished. Total time: 0.167s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.008s
Sending 'super' (459104 KB) OKAY [ 12.920s]
Writing 'super' OKAY [ 0.079s]
Finished. Total time: 13.008s
Sending 'super' (507816 KB) OKAY [ 14.361s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 16.088s
Sending 'super' (513096 KB) OKAY [ 13.386s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.285s
Sending 'super' (515124 KB) OKAY [ 12.993s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.627s
Sending 'super' (502664 KB) OKAY [ 12.930s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.175s
Sending 'super' (512856 KB) OKAY [ 13.320s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.476s
Sending 'super' (461208 KB) OKAY [ 11.963s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 13.153s
Sending 'super' (524244 KB) OKAY [ 13.649s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.510s
Sending 'super' (524240 KB) OKAY [ 13.687s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.586s
Sending 'super' (524256 KB) OKAY [ 12.149s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 12.994s
Sending 'super' (524208 KB) FAILED (remote: 'Error: Last flash failed : Invalid Parameter')
fastboot: error: Command failed
Another thing... when trying to install an older version of the RETUS stock image on my TMO variant, I got a rollback warning.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRE31.Q2-11-66_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 3 vs 5
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
After a restore my device works just fine
DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC
ArtiicPanda said:
I bit the bullet and attempted the flash...
It won't work, the vbmeta_system.img flashes fine with no issues (which is needed to flash an image to the system partition). It seems the ROM wont fit in the system ROM space completely, leading to corruption of the system partition. I'd definitely advise against trying this yourself.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRES31.Q2-11-103-2_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.161s]
Finished. Total time: 0.167s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.008s
Sending 'super' (459104 KB) OKAY [ 12.920s]
Writing 'super' OKAY [ 0.079s]
Finished. Total time: 13.008s
Sending 'super' (507816 KB) OKAY [ 14.361s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 16.088s
Sending 'super' (513096 KB) OKAY [ 13.386s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.285s
Sending 'super' (515124 KB) OKAY [ 12.993s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.627s
Sending 'super' (502664 KB) OKAY [ 12.930s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.175s
Sending 'super' (512856 KB) OKAY [ 13.320s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.476s
Sending 'super' (461208 KB) OKAY [ 11.963s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 13.153s
Sending 'super' (524244 KB) OKAY [ 13.649s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.510s
Sending 'super' (524240 KB) OKAY [ 13.687s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.586s
Sending 'super' (524256 KB) OKAY [ 12.149s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 12.994s
Sending 'super' (524208 KB) FAILED (remote: 'Error: Last flash failed : Invalid Parameter')
fastboot: error: Command failed
Another thing... when trying to install an older version of the RETUS stock image on my TMO variant, I got a rollback warning.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRE31.Q2-11-66_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 3 vs 5
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
After a restore my device works just fine
DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC
Click to expand...
Click to collapse
If all of that works fine then will flashing Cricket firmware with TMO firmware work?
NonStickAtom785 said:
If all of that works fine then will flashing Cricket firmware with TMO firmware work?
Click to expand...
Click to collapse
Bootloader must be unlocked if you want to cross flash
mingkee said:
Bootloader must be unlocked if you want to cross flash
Click to expand...
Click to collapse
What if you had a blankflash file? Doesn't the EDM for Qualcomm allow flashing new everything onto a device? Including bootloader? I might be wrong. But this is the method I was going to take when I first began trying to root this phone.
It doesn't matter it will cross flash I did it with mine there were no system errors no none of that
Gave it a go and oddly enough, while I am now unable to flash to the Metro ROM, the RETUS ROM seems to work almost flawlessly. 5G works as intended too.
I just wish I was able to use this phone on Cricket Wireless.
DragonfireEX402 said:
Gave it a go and oddly enough, while I am now unable to flash to the Metro ROM, the RETUS ROM seems to work almost flawlessly. 5G works as intended too.
I just wish I was able to use this phone on Cricket Wireless.
Click to expand...
Click to collapse
I flashed RETUS as well on my Boost Mobile variant. However, it looks like gyroscope and accelerometer don't work for me. Are you having issues?
itzimeow said:
I flashed RETUS as well on my Boost Mobile variant. However, it looks like gyroscope and accelerometer don't work for me. Are you having issues?
Click to expand...
Click to collapse
Never actually tried to use either of those things, so I don't know yet.
Hello, I have a concern. Looking to unlock my MetroPCS network cell phone, I flashed the original firmware it came with, for the RETUS one. I have tried to go back to the TMO rom but it stays in the logo, is there any way to go back?
ArtiicPanda said:
I bit the bullet and attempted the flash...
It won't work, the vbmeta_system.img flashes fine with no issues (which is needed to flash an image to the system partition). It seems the ROM wont fit in the system ROM space completely, leading to corruption of the system partition. I'd definitely advise against trying this yourself.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRES31.Q2-11-103-2_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.001s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.161s]
Finished. Total time: 0.167s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.008s
Sending 'super' (459104 KB) OKAY [ 12.920s]
Writing 'super' OKAY [ 0.079s]
Finished. Total time: 13.008s
Sending 'super' (507816 KB) OKAY [ 14.361s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 16.088s
Sending 'super' (513096 KB) OKAY [ 13.386s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.285s
Sending 'super' (515124 KB) OKAY [ 12.993s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.627s
Sending 'super' (502664 KB) OKAY [ 12.930s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 15.175s
Sending 'super' (512856 KB) OKAY [ 13.320s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.476s
Sending 'super' (461208 KB) OKAY [ 11.963s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 13.153s
Sending 'super' (524244 KB) OKAY [ 13.649s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.510s
Sending 'super' (524240 KB) OKAY [ 13.687s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 14.586s
Sending 'super' (524256 KB) OKAY [ 12.149s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 12.994s
Sending 'super' (524208 KB) FAILED (remote: 'Error: Last flash failed : Invalid Parameter')
fastboot: error: Command failed
Another thing... when trying to install an older version of the RETUS stock image on my TMO variant, I got a rollback warning.
Code:
[email protected] XT2131-1_DENVER_RETUS_11_RRE31.Q2-11-66_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml % bash flashfile.sh
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.001s]
Finished. Total time: 0.001s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 3 vs 5
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
After a restore my device works just fine
DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC
Click to expand...
Click to collapse
Hi friend, could you provide the ROM DENVER_GLOBAL_RRE31.Q2-11-52-4_subsidy-TMO_UNI_RSU_QCOM_regulatory-DEFAULT_cid50_CFC to return the firmware from RETUS to TMO, please.
NonStickAtom785 said:
What if you had a blankflash file? Doesn't the EDM for Qualcomm allow flashing new everything onto a device? Including bootloader? I might be wrong. But this is the method I was going to take when I first began trying to root this phone.
Click to expand...
Click to collapse
Dude, how did that work out for you? I flashed RETUS on the TMO ROM, and now I need to switch to the original (TMO), I thought about using the blankflash that appears on lolinet servers, you did the test and could you switch?
I want to flash the TMO rom on my AT&T device.
I have a guess that possibly if I can do that, it will give me a bootloader unlock code that Motorola will accept.
@ArtiicPanda do you think that could work?
@itzimeow do you think it could work?
mingkee said:
I found the hardware is different
US retail is 6/256
T-Mobile/Metro is 4/128
It may have negative impact if you cross flash ROM
Click to expand...
Click to collapse
That may be because the US retail is Mediatek and the TMo version is Qualcomm.
I have the mediatek version and I flash retail just fine.
Wow all you guys are scarring me
All xt2131-1,2,3,4,DL are Qualcomm driven
And RETUS firmware (REtailUS) loaded and CID unlocked are preloaded with US and Canada carrier programs and will work with all north American carrier.
XT2131-3 is ATT firmware and -4 is cricket, all others use -1 firmware as stock.
With the exception of Verizon and ATT branded phone can be reflashed with same or newer RETUS firmware.
Blankflash is akin to a reformat and should only be used if the phone has been corrupted.
Articul8Madness said:
That may be because the US retail is Mediatek and the TMo version is Qualcomm.
I have the mediatek version and I flash retail just fine.
Click to expand...
Click to collapse
Not sure why you guys say T-Mobile/Metro is 4/128. Both T-Mobile and Metro's website list the Moto G Stylus 5G 2022 as 6/128.
Motorola moto g stylus 5G (2022) | 1 color in 128GB | T-Mobile
Meet the moto g stylus 5G featuring a built-in stylus, a 50 MP camera system, a massive 6.8" FHD+ display, and much more. Order today at T-Mobile.
www.t-mobile.com
nookin said:
Not sure why you guys say T-Mobile/Metro is 4/128. Both T-Mobile and Metro's website list the Moto G Stylus 5G 2022 as 6/128.
Motorola moto g stylus 5G (2022) | 1 color in 128GB | T-Mobile
Meet the moto g stylus 5G featuring a built-in stylus, a 50 MP camera system, a massive 6.8" FHD+ display, and much more. Order today at T-Mobile.
www.t-mobile.com
Click to expand...
Click to collapse
This post is about the 2021 model XT2131.
Then the thread should be moved to G Stylus 2021.
nookin said:
Then the thread should be moved to G Stylus 2021.
Click to expand...
Click to collapse
Yeah, right here is where's at.
im getting this error when im flashing an image
{
"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"
}
MehmetCanWT said:
im getting this error when im flashing an image
View attachment 5694307
Click to expand...
Click to collapse
Newer devices have two modes for fastboot commands.
bootloader (fastboot).
fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.
ipdev said:
Newer devices have two modes for fastboot commands.
bootloader (fastboot).fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
Example from OnePlus 7T.
Bootloader (fastboot).
Code:
Invalid sparse file format at header magic
Sending sparse 'system_ext' 1/2 (786356 KB) OKAY [ 32.517s]
Writing 'system_ext' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/2 (786288 KB) OKAY [ 32.146s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Fastboot (fastboot_d).
Code:
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.004s]
Sending sparse 'system_ext_b' 1/6 (262112 KB) OKAY [ 11.085s]
Writing 'system_ext_b' OKAY [ 1.698s]
Sending sparse 'system_ext_b' 2/6 (262128 KB) OKAY [ 11.182s]
Writing 'system_ext_b' OKAY [ 1.708s]
Sending sparse 'system_ext_b' 3/6 (262116 KB) OKAY [ 10.854s]
Writing 'system_ext_b' OKAY [ 1.676s]
Sending sparse 'system_ext_b' 4/6 (262128 KB) OKAY [ 10.923s]
Writing 'system_ext_b' OKAY [ 1.677s]
Sending sparse 'system_ext_b' 5/6 (230160 KB) OKAY [ 9.749s]
Writing 'system_ext_b' OKAY [ 1.481s]
Sending sparse 'system_ext_b' 6/6 (158200 KB) OKAY [ 6.649s]
Writing 'system_ext_b' OKAY [ 1.071s]
Finished. Total time: 69.990s
Invalid sparse file format at header magic
Resizing 'system_b' OKAY [ 0.004s]
Sending sparse 'system_b' 1/6 (262108 KB) OKAY [ 10.725s]
Writing 'system_b' OKAY [ 1.684s]
Sending sparse 'system_b' 2/6 (262120 KB) OKAY [ 10.835s]
Writing 'system_b' OKAY [ 1.675s]
Sending sparse 'system_b' 3/6 (262060 KB) OKAY [ 10.865s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 4/6 (262128 KB) OKAY [ 11.052s]
Writing 'system_b' OKAY [ 1.668s]
Sending sparse 'system_b' 5/6 (262140 KB) OKAY [ 11.024s]
Writing 'system_b' OKAY [ 1.676s]
Sending sparse 'system_b' 6/6 (32956 KB) OKAY [ 1.360s]
Writing 'system_b' OKAY [ 0.320s]
Finished. Total time: 64.798s
What device do you have?
If it is a Legion Phone Duel 2, then you more than likely need to flash using fastboot_d mode.
Hope it helps more than confuse.
Cheers.
Click to expand...
Click to collapse
i have fastbootd and bootloader
my phone is trident a24
im flashing image on fastbootd
If you still get the error in fastbootd, then..
- Try a different usb cable or port.
- Make sure to use a USB-2 port on the computer.
Known issues using a USB-3 or USB-C port for flashing devices.
- Incompatible version of fastboot.
- Incompatible image file format or corrupted image file.
Newer versions of fastboot should detect the active slot.
Some older devices (and older fastboot), you have to call the slot you want to flash.
fastboot flash flash system_a legion.img
fastboot system_b legion.img
--
I looked up the trident a24, nice looking phone.
Released with Android 10 (?), it should be a slot device.
I could not find out if it was a normal A/B device or one of the odd few A-Olny slot devices.
You can find the current (active) slot.
fastboot getvar current-slot
You can set the active slot.
fastboot set_active a
fastboot set_active b
Cheers.
PS.
When I updated my main computer, I only have USB-C ports on new computer.
I use a cheap USB-C hub that includes a USB-2 port and do all my flashing using it.
i just waited a night and problem solved thanks to all
Hi, flashing android 9 gsi roms, works fine on my device(TA-1191). But any/all A11 gsi's just don't. Ok so i flashed the a9 nokia firmware from the unlock guide, then did an OTA update and flashed magisk. Everything is fine up to this point. But flashing the following gsi's don't work:
Corvus_vS3.0-Revenant-treble_arm64_ab_vndklite-Beta-Official-0800.img
Corvus_vS4.0-Leviathan-treble_arm64_ab_vndklite-Official-0038.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img
system-roar-arm64-ab-vndklite-floss.img
And a few other unamed/system gsis...
This the method or guide being followed:
Code:
PS C:\adb\platform-tools_r31.0.3-windows> fastboot devices
HZAL1670EAJ81901791 fastboot
PS C:\adb\platform-tools_r31.0.3-windows> fastboot flash system lineage-20.0-20230324-UNOFFICIAL-arm64_bvS-vndklite.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/17 (131028 KB) OKAY [ 5.882s]
Writing 'system_b' OKAY [ 1.966s]
Sending sparse 'system_b' 2/17 (131052 KB) OKAY [ 5.944s]
Writing 'system_b' OKAY [ 1.928s]
Sending sparse 'system_b' 3/17 (131064 KB) OKAY [ 5.973s]
Writing 'system_b' OKAY [ 2.396s]
Sending sparse 'system_b' 4/17 (131056 KB) OKAY [ 5.940s]
Writing 'system_b' OKAY [ 2.449s]
Sending sparse 'system_b' 5/17 (131052 KB) OKAY [ 5.922s]
Writing 'system_b' OKAY [ 1.948s]
Sending sparse 'system_b' 6/17 (131056 KB) OKAY [ 5.940s]
Writing 'system_b' OKAY [ 1.919s]
Sending sparse 'system_b' 7/17 (131068 KB) OKAY [ 5.947s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 8/17 (131052 KB) OKAY [ 5.899s]
Writing 'system_b' OKAY [ 2.532s]
Sending sparse 'system_b' 9/17 (131068 KB) OKAY [ 5.942s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 10/17 (131060 KB) OKAY [ 5.895s]
Writing 'system_b' OKAY [ 1.925s]
Sending sparse 'system_b' 11/17 (130928 KB) OKAY [ 5.920s]
Writing 'system_b' OKAY [ 1.988s]
Sending sparse 'system_b' 12/17 (130525 KB) OKAY [ 5.967s]
Writing 'system_b' OKAY [ 2.680s]
Sending sparse 'system_b' 13/17 (131032 KB) OKAY [ 5.931s]
Writing 'system_b' OKAY [ 2.488s]
Sending sparse 'system_b' 14/17 (131048 KB) OKAY [ 6.210s]
Writing 'system_b' OKAY [ 1.942s]
Sending sparse 'system_b' 15/17 (131060 KB) OKAY [ 5.928s]
Writing 'system_b' OKAY [ 1.927s]
Sending sparse 'system_b' 16/17 (131068 KB) OKAY [ 5.913s]
Writing 'system_b' OKAY [ 1.920s]
Sending sparse 'system_b' 17/17 (57706 KB) OKAY [ 2.675s]
Writing 'system_b' OKAY [ 1.900s]
Finished. Total time: 150.659s
PS C:\adb\platform-tools_r31.0.3-windows> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_b' OKAY [ 0.002s]
Finished. Total time: 0.032s
PS C:\adb\platform-tools_r31.0.3-windows> fastboot -w
Erasing 'userdata' OKAY [ 0.224s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
PS C:\adb\platform-tools_r31.0.3-windows> fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
PS C:\adb\platform-tools_r31.0.3-windows>
And the issue eperienced is either Bootlooping or rebooting into twrp recovery. Also formating data in twrp makes no difference. The vbmeta.img used, is from the ota updated firmware base.
I don't if i might be flashing the wrong gsi images ? If someone could correct me please.
Thanks.
Still can't seem to fix it. Help anyone ?
Ok realized that the los 20 and the above gsi's are a12/13 based. And that the gsi rom should match your base firmware android version. So I tried the following gsi's that are a11 and still no luck:
bless-v306-210502-arm64-bvZ-lite.img
caos-v316-220321-arm64-bvZ-lite.img
HavocOS-arm64-bvN-lite.img (also a11)
system-roar-arm64-ab-vndklite-vanilla.img (also a11)
Could anyone share some links of working android 11 gsi's ? Please ?