Database Develop

can anyone tell me what im doing wrong

C:\adb>fastboot devices
ZL52249ZLW fastboot
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.028s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 535822336 bytes
sending 'bootloader' (7483 KB)...
OKAY [ 0.261s]
writing 'bootloader'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.290s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 535822336 bytes
sending 'modem' (68142 KB)...
OKAY [ 2.223s]
writing 'modem'...
OKAY [ 0.986s]
finished. total time: 3.215s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 535822336 bytes
sending 'fsg' (5188 KB)...
OKAY [ 0.176s]
writing 'fsg'...
OKAY [ 0.128s]
finished. total time: 0.311s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.036s]
finished. total time: 0.038s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.036s]
finished. total time: 0.038s
C:\adb>fastboot flash bluetooth BTFM.bin
error: cannot load 'BTFM.bin'
C:\adb>fastboot flash dsp dspso.bin
error: cannot load 'dspso.bin'
C:\adb>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.559s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.354s]
finished. total time: 0.919s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 535822336 bytes
sending 'system' (512397 KB)...
OKAY [ 16.663s]
writing 'system'...
OKAY [ 6.223s]
finished. total time: 22.892s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 535822336 bytes
sending 'system' (475855 KB)...
OKAY [ 15.484s]
writing 'system'...
OKAY [ 5.472s]
finished. total time: 20.963s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 535822336 bytes
sending 'system' (523076 KB)...
OKAY [ 16.997s]
writing 'system'...
OKAY [ 6.090s]
finished. total time: 23.094s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 535822336 bytes
sending 'system' (508867 KB)...
OKAY [ 16.536s]
writing 'system'...
OKAY [ 5.792s]
finished. total time: 22.334s
C:\adb>fastboot flash system system.img_sparsechunk.4
error: cannot load 'system.img_sparsechunk.4'
C:\adb>fastboot flash system system.img_sparsechunk.5
error: cannot load 'system.img_sparsechunk.5'
C:\adb>fastboot flash system system.img_sparsechunk.6
error: cannot load 'system.img_sparsechunk.6'
C:\adb>fastboot flash system system.img_sparsechunk.7
error: cannot load 'system.img_sparsechunk.7'
C:\adb>fastboot flash system system.img_sparsechunk.8
error: cannot load 'system.img_sparsechunk.8'
C:\adb>fastboot flash system system.img_sparsechunk.9
error: cannot load 'system.img_sparsechunk.9'
C:\adb>fastboot flash vendor vendor.img_sparsechunk.0
error: cannot load 'vendor.img_sparsechunk.0'
C:\adb>fastboot flash vendor vendor.img_sparsechunk.1
error: cannot load 'vendor.img_sparsechunk.1'
C:\adb>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.071s]
finished. total time: 0.072s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.183s]
finished. total time: 0.186s
C:\adb>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 535822336 bytes
sending 'logo' (1423 KB)...
OKAY [ 0.053s]
writing 'logo'...
OKAY [ 0.090s]
finished. total time: 0.150s
C:\adb>fastboot reboot

I don't root my phones anymore, but when I did, I always found the instructions to be light. A lot of people think that if you can't figure it out without much help then you shouldn't be rooting your phone. I've nearly bricked more than once phone before I figuring things out.
Read every set of directions you can find on Google, and if you can combine the puzzle pieces together correctly, then you win.

Are you sure you are flashing correct firmware for your device? what device do you have and what firmware are you trying to flash?

It the moto G6 play from Best Buy unlocked xt1922-9 this is the firmware I was told was full my device. Aljeter_0pp27.61-14_4-cid50_subsidy-DEFAULT_regulatory. But every time I flash it as you can see it comes up with errors in the bootloader even though the system images flash fine and it boots up I don't have Wi-Fi,data or Bluetooth

anotherfakeusername said:
I don't root my phones anymore, but when I did, I always found the instructions to be light. A lot of people think that if you can't figure it out without much help then you shouldn't be rooting your phone. I've nearly bricked more than once phone before I figuring things out.
Read every set of directions you can find on Google, and if you can combine the puzzle pieces together correctly, then you win.
Click to expand...
Click to collapse
Well I tried just about all of the firmware on XDA nothing seems to work even though they say it's for the G6 play I have my doubts

timelessxiii said:
Well I tried just about all of the firmware on XDA nothing seems to work even though they say it's for the G6 play I have my doubts
Click to expand...
Click to collapse
You're using the wrong commands that's it.
Gimme a screenshot of all the files in your firmware's folder and I'll give you a script

{
"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"
}

here you go
CreasingMass Dev said:
You're using the wrong commands that's it.
Gimme a screenshot of all the files in your firmware's folder and I'll give you a script
Click to expand...
Click to collapse

timelessxiii said:
View attachment 4549977
Click to expand...
Click to collapse
also send me a copy of your file flashfile.xml pls

View attachment flashfile.xml
CreasingMass Dev said:
also send me a copy of your file flashfile.xml pls
Click to expand...
Click to collapse

timelessxiii said:
View attachment 4549977
Click to expand...
Click to collapse
Here's your script, paste it inside your firmware's folder and open it with your device connected in fastboot mode, should work.
https://drive.google.com/open?id=1jhhRS2ZrkROfqULjI49Zus2xj9v-gGAt

CreasingMass Dev said:
Here's your script, paste it inside your firmware's folder and open it with your device connected in fastboot mode, should work.
https://drive.google.com/open?id=1jhhRS2ZrkROfqULjI49Zus2xj9v-gGAt
Click to expand...
Click to collapse
i give up it all started when i unlocked the bootloader the phone did not reboot and wipe data like it should have instead i got a message saying badkey in the left top screen, so when i rebooted pnone it came up but i did not have bluetooth wifi or data i thought reflashing always worked will i guess not lol , if there was a flash file for data or wifi hell i maybe able to fix it through OTAs

timelessxiii said:
i give up it all started when i unlocked the bootloader the phone did not reboot and wipe data like it should have instead i got a message saying badkey in the left top screen, so when i rebooted pnone it came up but i did not have bluetooth wifi or data i thought reflashing always worked will i guess not lol , if there was a flash file for data or wifi hell i maybe able to fix it through OTAs
Click to expand...
Click to collapse
I was able to flash twarp hopfully a custom rom would work

timelessxiii said:
I was able to flash twarp hopfully a custom rom would work
Click to expand...
Click to collapse
DaxUser has stoped , what ever that mean

could you possibly repost this script. its no longer available on google drive and it would help me tremendously.

LOCKED BOOTLOADER No USB DEBUGGING STUCK IN FASTBOOT LOOP

Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP

try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.

No such options
Psychotic0666 said:
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
Click to expand...
Click to collapse
Dude thanks, but i dont have WIPE CACHE RESTART OPTIONS, plus i cant boot into any recovery TWRP or CHINESE stock, Thankfully i found a way to unlock bootloader i guess via FASTBOOT, , still no response and unable to get into OTG OR DATA RESET OR CACHE RESET OPTIONS
Here is the list of options i got.
REBOOT SYSTEM NOW = BOOTLOOP AGAIN
REBOOT TO RECOVERY MODE = BOOTLOOP AGAIN
REBOOT TO EMEG RECOVERY MODE = Black Screen no response.
BOOT TO EDLOAD = Success as PC detects the phone as a Qualcomm Device, NUBIA Recovery soft (Very old) also detects phone
POwer off = Bootloop AGAIN
KIndly help

thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.

Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.

JerryYin said:
Hi, maybe you should flash the twrp and use twrp to flash the stock udate package, the RM3 twrp can flash stock ota
package
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

Psychotic0666 said:
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.

JerryYin said:
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Click to expand...
Click to collapse
thel'vadam said:
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Click to expand...
Click to collapse
My suggestion is that flash the global version recovery first, and see if it can boot.

JerryYin said:
My suggestion is that flash the global version recovery first, and see if it can boot.
Click to expand...
Click to collapse
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,

thel'vadam said:
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
Click to expand...
Click to collapse
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"

JerryYin said:
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED

thel'vadam said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
Click to expand...
Click to collapse
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this

JerryYin said:
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
Click to expand...
Click to collapse
Can please elaborate this a little bit, also be informed that my RM3 is indian variant, it has separate indian variant ROM available from Nubia India 1.96 GB, so In my opinion GLOBAL AND CHINESE ROM s both wont work, my luck rests with the indian ROM. Ill still try whatever you suggest.

Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work

Psychotic0666 said:
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.166s]
finished. total time: 0.167s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modem
erasing 'modem'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.748s]
writing 'dsp'...
OKAY [ 0.343s]
finished. total time: 2.093s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash parameter parameter.img
target reported max download size of 805306368 bytes
sending 'parameter' (0 KB)...
OKAY [ 0.009s]
writing 'parameter'...
OKAY [ 0.004s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 3.432s]
writing 'boot'...
OKAY [ 0.406s]
finished. total time: 3.840s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 2.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.207s]
writing 'splash'...
OKAY [ 0.056s]
finished. total time: 0.265s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144180 KB)...
OKAY [ 3.778s]
writing 'modem'...
OKAY [ 1.045s]
finished. total time: 4.826s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.027s]
sending sparse 'system' 1/5 (778291 KB)...
OKAY [ 17.596s]
writing 'system' 1/5...
OKAY [ 0.004s]
sending sparse 'system' 2/5 (697207 KB)...
OKAY [ 22.095s]
writing 'system' 2/5...
OKAY [ 0.003s]
sending sparse 'system' 3/5 (752301 KB)...
OKAY [ 24.678s]
writing 'system' 3/5...
OKAY [ 0.003s]
sending sparse 'system' 4/5 (782303 KB)...
OKAY [ 30.918s]
writing 'system' 4/5...
OKAY [ 0.003s]
sending sparse 'system' 5/5 (723054 KB)...
OKAY [ 30.517s]
writing 'system' 5/5...
OKAY [ 0.002s]
finished. total time: 125.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>
STILL SAME

Did you flash the files from global rom?

same incident.
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?

godric12 said:
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
Click to expand...
Click to collapse
i was once able to get a white screen with green highlighted squicircles, it did allow me to acess the boot from OTG option, i tried installing the indian ROM, it installed successfully, then after restart, same FASTBOOT LOOP WITH ERROR, i dont know how i got to that menu, i repeated the exact steps again, im still not able to get PAST BOOT LOOP.

Psychotic0666 said:
Did you flash the files from global rom?
Click to expand...
Click to collapse
YES TRIED ALL GLOBAL CHINESE indian, all variants. All recovery files all respective System.img files.
IM USING ORIGINAL IN BOX USB C cable if thats a thing,
Though i do get this ERROR (( Invalid sparse file format at header magic )) while pushing SYSTEM.img, it still suceeds, in 5/5 parts. after brief waiting.

Switch off the device and turn back on the Try going to recovery manually with vol and power button

[ROM][RAV*/SOFIA*][11][UNOFFICIAL] SuperiorOS-Xcalibur

{
"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"
}
About US:
Superior OS is a AOSP based custom ROM with some minimal features to fulfill the users demands nowadays.
********************************************
UPDATES WILL BE ADDED TO THIS POST EACH MONTH AS MUCH AS POSSIBLE. CHECK FOR UPDATED LINKS! IM UPDATING THE LINKS TO THE FEB PATCH
********************************************
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
"This is a user friendly thread, all your suggestions are important to us and will be taken into consideration.."
***GAPPS ARE INCLUDED IN ROM***
HOW TO INSTALL:
1. Fastboot -w (in bootloader)
2. Flash images
- fastboot reboot fastboot
- fastboot set_active a
- fastboot flash boot boot.img
- fastboot flash system system.img
- fastboot flash product product.img
- fastboot flash vbmeta vbmeta.img
3. Reboot
AND THATS IT!
****FLASHING MICROG BUILD****
1. Flash all images (same steps above)
2. Boot into rom
3. Reboot into TWRP
4. Flash magisk
5. Flash microg.zip (included in the link provided)
6. Reboot
New Update:
- Added new thermals from Xiaomi
- Improved RAM management
- Performance Optimizations
- Added Pixel Camera blobs
- Added Miracast
Download ROM:SuperiorOS_May-patch
SuperiorOS Core Team
AOSP
Lineage OS
DirtyUnicorns
PixelExperience
AospExtended
Syberia OS
Nitrogen OS
Pixys OS
@bcrichster
@Beetle84
@asineth
@Rondeau79
@gearsofwar567
@kjjjnob
Special thanks:
@vache
Important Links
Loved the ROM? Want to help it imporove? Gift us with some credits!
Superior OS source
Device Trees: https://github.com/h0pk1do/android_device_motorola_sofiar
Vendor Trees: https://github.com/moto-sm6xxx/android_vendor_motorola_sofiar
Kernel Trees: https://github.com/Odin1101/Project-Sofia
Telegram Group
Telegram Channel
EXPERIENCING BUGS?
PLEASE LET ME KNOW!
SuperiorOS Version Name: Xcalibur
Build Type: UNOFFICIAL
Source Code: SuperiorOS
XDAevDB Information
SuperiorOS A11 sofia*/rav*, ROM for the Moto G8 Family
Contributors
Source Code: https://github.com/SuperiorOS
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2021-01-27
Last Updated 2021-03-26

sweet an android 11 rom. can you post instructions on how to flash the images? also can we get a build with gapps? I don't think twrp is useable to flash anything.

fix-this! said:
sweet an android 11 rom. can you post instructions on how to flash the images? also can we get a build with gapps? I don't think twrp is useable to flash anything.
Click to expand...
Click to collapse
i just updated the instructions and if you have the latest twrp, don't worry flashing will work

Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s

rpcribari said:
Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s
Click to expand...
Click to collapse
Okay so two things :
1. For whatever reason it's flashing to the B partition which it shouldn't.
2. You need the latest platform-tools
Before you flash again, fastboot -w and then type
Fastboot set_active a
I'll adjust that in the instructions

Getting a different error with the latest version of platform-tools.
"Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed"
C:\adb2>fastboot devices
ZY22BKVPZ4 fastboot
C:\adb2>fastboot -w
Erasing 'userdata' OKAY [ 0.042s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.010s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.087s
C:\adb2>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.309s]
Finished. Total time: 0.315s
C:\adb2>fastboot flash boot f:\boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.013s]
Writing 'boot_a' OKAY [ 0.552s]
Finished. Total time: 2.587s
C:\adb2>fastboot flash system f:\system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed

rpcribari said:
Getting a different error with the latest version of platform-tools.
"Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed"
C:\adb2>fastboot devices
ZY22BKVPZ4 fastboot
C:\adb2>fastboot -w
Erasing 'userdata' OKAY [ 0.042s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.010s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.087s
C:\adb2>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.309s]
Finished. Total time: 0.315s
C:\adb2>fastboot flash boot f:\boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.013s]
Writing 'boot_a' OKAY [ 0.552s]
Finished. Total time: 2.587s
C:\adb2>fastboot flash system f:\system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Which device do you have?

rpcribari said:
Getting an error when flashing system.img. Any ideas?
"writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)"
C:\ADB>fastboot devices
ZY22BKVPZ4 fastboot
C:\ADB>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.187s]
finished. total time: 1.189s
C:\ADB>fastboot flash boot f:\boot.img
target reported max download size of 805261312 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 2.028s]
writing 'boot_b'...
OKAY [ 0.566s]
finished. total time: 2.601s
C:\ADB>fastboot flash system f:\system.img
target reported max download size of 805261312 bytes
sending sparse 'system_b' 1/2 (720896 KB)...
OKAY [ 24.038s]
writing 'system_b' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.056s
Click to expand...
Click to collapse
XT2041-4

rpcribari said:
XT2041-4
Click to expand...
Click to collapse
We have the same exact device, where are you? Are you in bootloader? Or are you in fastbootd?

Hello gearsofwar567. in the post you mention that its possible to use the twrp to flash this? does that mean i can flash the twrp and do a backup and then go back to android 10 if i use twrp instead of flashing this directly? or does it come with some kind of recovery that can do backups?
also... i will gladly flash this and test it for you but i would like to wonder what features are software defect?
basically this is android 11 before moto released it which is fine but i am nervous about the recovery itself lol

gearsofwar567 said:
We have the same exact device, where are you? Are you in bootloader? Or are you in fastbootd?
Click to expand...
Click to collapse
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)

I flashed the rom, installed twrp and installed gapps. so far it's running flawless on my device. the only concern I have is updates. when you flash twrp it seems to wipe out fastbootd. any suggestions on how to fix this?

rpcribari said:
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
Click to expand...
Click to collapse
are you in fastboot or fastbootd? you cant flash the images in standard fastboot mode for some reason.

Will this get updates? I have never used an unofficial rom before and I don't know how reliably updated they are.

fix-this! said:
are you in fastboot or fastbootd? you cant flash the images in standard fastboot mode for some reason.
Click to expand...
Click to collapse
I guess I don't understand the difference between fastboot and fastbootd. From TWRP 3.5 I'm going to Reboot then Fastboot.

bitscott84 said:
Hello gearsofwar567. in the post you mention that its possible to use the twrp to flash this? does that mean i can flash the twrp and do a backup and then go back to android 10 if i use twrp instead of flashing this directly? or does it come with some kind of recovery that can do backups?
also... i will gladly flash this and test it for you but i would like to wonder what features are software defect?
basically this is android 11 before moto released it which is fine but i am nervous about the recovery itself lol
Click to expand...
Click to collapse
So basically this:
1. You cannot flash the rom via twrp, you must flash the images per the instructions
2. No you cannot currently make backups with twrp because of dynamic partitions. Still trying to work that out
3. Software defects, that is something you would have to find out for yourself when you flash. The status of the rom said "stable"

rpcribari said:
Good call. I was just in the bootloader. I've now upgraded to TWRP 3.5 and found the reboot into fastboot mode and successfully flashed the system.img and remaining images. However now am getting the error:
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
Click to expand...
Click to collapse
Is it not booting?

fix-this! said:
I flashed the rom, installed twrp and installed gapps. so far it's running flawless on my device. the only concern I have is updates. when you flash twrp it seems to wipe out fastbootd. any suggestions on how to fix this?
Click to expand...
Click to collapse
Good to hear and there will be updates. In TWRP, hit the "reboot" tab and the tile That says "fastboot" is the new fastboot built into twrp

halliessed said:
Will this get updates? I have never used an unofficial rom before and I don't know how reliably updated they are.
Click to expand...
Click to collapse
You'll get updates faster than Motorola
January 5th 2021 is latest patch

gearsofwar567 said:
Is it not booting?
Click to expand...
Click to collapse
No it doesn't boot. It just keeps rebooting back to the bootloader.

Question Help restoring Stock ROM [SOLVED]

So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.

It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.

Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.

Question Bricked: Failed to boot into userspace fastboot

Hey there,
a couple of weeks ago I purchased a new smartphone with headphone jack in a reasonable size and it should run LineageOS.
So after a long search, the Zenfone 8 met all requirements.
I wanted to flash LineageOS, but went over several problems. Right now I'm stuck in a fastboot-loop. I cannot describe what I've tried to get things working again, sadly.
Recently I stumbled upon this thread and get stuck in the fastboot loop.
Flashing of boot, dtbo, vendor-boot, vbmeta and vbmeta_system seems to work, but after trying to access fastbootd, I get stuck.
Here's the output:
/run/me/g/s/a/e/payload fastboot flash boot boot.img ✔
Sending 'boot_a' (98304 KB) OKAY [ 2.520s]
Writing 'boot_a' OKAY [ 0.257s]
Finished. Total time: 2.822s
/run/me/g/s/a/e/payload fastboot flash dtbo dtbo.img ✔ 3s
Sending 'dtbo' (8192 KB) OKAY [ 0.212s]
Writing 'dtbo' OKAY [ 0.023s]
Finished. Total time: 0.272s
/run/me/g/s/a/e/payload fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB) OKAY [ 2.514s]
Writing 'vendor_boot' OKAY [ 0.278s]
Finished. Total time: 2.832s
/run/me/g/s/a/e/payload fastboot flash vbmeta vbmeta.img ✔ 3s
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.049s
/run/me/g/s/a/e/payload fastboot flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.044s
/run/me/g/s/a/e/payload fastboot reboot fastboot ✔
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components
might be unbootable.
I'd be so happy to get this working again.
Thanks in advance!

sonix900 said:
Hey there,
a couple of weeks ago I purchased a new smartphone with headphone jack in a reasonable size and it should run LineageOS.
So after a long search, the Zenfone 8 met all requirements.
I wanted to flash LineageOS, but went over several problems. Right now I'm stuck in a fastboot-loop. I cannot describe what I've tried to get things working again, sadly.
Recently I stumbled upon this thread and get stuck in the fastboot loop.
Flashing of boot, dtbo, vendor-boot, vbmeta and vbmeta_system seems to work, but after trying to access fastbootd, I get stuck.
Here's the output:
/run/me/g/s/a/e/payload fastboot flash boot boot.img ✔
Sending 'boot_a' (98304 KB) OKAY [ 2.520s]
Writing 'boot_a' OKAY [ 0.257s]
Finished. Total time: 2.822s
/run/me/g/s/a/e/payload fastboot flash dtbo dtbo.img ✔ 3s
Sending 'dtbo' (8192 KB) OKAY [ 0.212s]
Writing 'dtbo' OKAY [ 0.023s]
Finished. Total time: 0.272s
/run/me/g/s/a/e/payload fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB) OKAY [ 2.514s]
Writing 'vendor_boot' OKAY [ 0.278s]
Finished. Total time: 2.832s
/run/me/g/s/a/e/payload fastboot flash vbmeta vbmeta.img ✔ 3s
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.049s
/run/me/g/s/a/e/payload fastboot flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.044s
/run/me/g/s/a/e/payload fastboot reboot fastboot ✔
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components
might be unbootable.
I'd be so happy to get this working again.
Thanks in advance!
Click to expand...
Click to collapse
I used the raw image for the ASUS Zenfone 8 mentioned in your post a lot of times to get my Zenfone up and running again without problems after I broke everything
How did you try to get the raw image installed?
And which version of the raw image do you use?
There are batch files in the raw image zip file to do that:
update_image.sh (for Unix)
or
update_image.bat (for Windows)
In neither of them is a command "fastboot reboot fastboot".
I never used the batch file for Windows (I do not have WIndows) but the batch file for Linux reinstallls the original ASUS Android without problems. Afterwards you can install a custom ROM like OmniROM or LineageOS using the install instructions from these ROMs.
regards
Bernd

Hm, I tried on both Windows and Linux (Manjaro).
I downloaded the raw image from the "How To Guide", but I also downloaded the latest image from Asus today and tried that one.
Then I used payload dumper to extract the images from the payload file.
After that I used the command from the "flash-all"-file from the "How To Guide".
Until the "fastboot reboot fastboot" command I get overall OK-messages, but after the reboot the Zenfone restarts into normal fastboot, and not into fastbootd. Also trying to flash the other images brings me the error message.
Could you please tell me what image zip file you have? Within the ones I have, there are noch update_image files.

sonix900 said:
Hm, I tried on both Windows and Linux (Manjaro).
I downloaded the raw image from the "How To Guide", but I also downloaded the latest image from Asus today and tried that one.
Then I used payload dumper to extract the images from the payload file.
After that I used the command from the "flash-all"-file from the "How To Guide".
Until the "fastboot reboot fastboot" command I get overall OK-messages, but after the reboot the Zenfone restarts into normal fastboot, and not into fastbootd. Also trying to flash the other images brings me the error message.
Could you please tell me what image zip file you have? Within the ones I have, there are noch update_image files.
Click to expand...
Click to collapse
Then it's not a raw image for the phone...
Download the raw image file from here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-31.1010.0410.61-MR0-2204-user-20220422.zip
Unzip the zip file, connect your phone in Bootloader mode, and execute the update_image.sh file from the zip file
(and do NOT mix files from different ZIP files )
The official images from ASUS can not be used for this purpose -- you can later use the official images for updating the installed Android OS but not for the first installation.
regards
Bernd

Wow, with your file it worked flawlessly, million thanks!!!
Apparently I really had the wrong files.
BTW, is there an official website at Asus for the raw files?

sonix900 said:
Wow, with your file it worked flawlessly, million thanks!!!
Apparently I really had the wrong files.
BTW, is there an official website at Asus for the raw files?
Click to expand...
Click to collapse
I don't know .. the raw images are the fallback solution if the installation of a new beta fails.
e.g. the link to the raw image for Android 11 is on this website
Android-12-Beta | ASUS Global
www.asus.com
and the link to the raw image for Android 12 is on this website
Android-13-Beta | ASUS Global
www.asus.com
(at the end of the page in the Section "How to opt out ..."
regards
Bernd