Database Develop

Cherry Mobile Android One G1 Stock Rom Fastboot Flashable (LUZ59M build)

After Flashing This Stock Rom you will still receive ota Updates Without Any Error!!!
Android One G1 Stock Rom Fastboot Flashable - This is 100% Working and Tested before posting
Things Needed :
A Laptop/Desktop
ADB and Fastboot Drivers Installed (If you dont have one you can check it here - http://forum.xda-developers.com/showthread.php?t=2588979 - 15 Seconds ADB Installer)
The Downloaded Android One G1 Stock Rom (LUZ59M) - http://www.mediafire.com/download/6shl7b41fzdaku4/Android_One_G1_Stock_Rom_Fastboot_(LUZ59M).zip. kalvin is the PASSWORD of the Zip/ROM
Procedure :
1. Download The Stock Rom and Extract it any location on your Laptop/Desktop.
2. Boot your Android One G1 to Fastboot mode.
How to Boot To Fastboot Mode?
( Volume Down + Power Button ) - Release it when you see the G1 logo (you will have to stuck on G1 logo that means you successfully booted to fastboot)
For Cyanogen Os Users Use the (Advance reboot to Bootloader or Volume Up + Power) there will be a screen notification that you are on a fastboot mode
Next option if you cant manually boot to fastboot just plug your G1 to pc/laptop (properly booted/Nka open)
make sure you installed the drivers properly after you plug the phone Just run the bat file and it will boot your phone to fastboot mode and the Rom Installation Will Begin
Just Run The .Bat file i created and the installation is all Automated
Notice : If an ERROR is prompt after the splash.img before the System.img flashing just ignored it , the installation still continues and running dont unplug your phone just wait it until your phone Reboots and its all done you are now on STOCK ROM LUZ59M Build ( Dont Worry if you Encounter An Error While Flashing ,the rom will be installed properly ) i just encounter this when you are from a cyanogen OS Rom
Do a Factory Reset After you Booted the ROM Properly
Credits to :
ME
August
JoeyHuab
MeteBerkErgun/Sadronis
Snoop05(xda) - 15 seconds adb/fastboot installer
To All my Fellow AndroidOne Admins 1st Gen & 2nd Gen
Enjoy and Goodluck!!!! - Kalvin/KShen

kalvin026 said:
After Flashing This Stock Rom you will still receive ota Updates Without Any Error!!!
Android One G1 Stock Rom Fastboot Flashable - This is 100% Working and Tested before posting
Things Needed :
A Laptop/Desktop
ADB and Fastboot Drivers Installed (If you dont have one you can check it here - http://forum.xda-developers.com/showthread.php?t=2588979 - 15 Seconds ADB Installer)
The Downloaded Android One G1 Stock Rom (LUZ59M) - http://www.mediafire.com/download/6shl7b41fzdaku4/Android_One_G1_Stock_Rom_Fastboot_(LUZ59M).zip. kalvin is the PASSWORD of the Zip/ROM
Procedure :
1. Download The Stock Rom and Extract it any location on your Laptop/Desktop.
2. Boot your Android One G1 to Fastboot mode.
How to Boot To Fastboot Mode?
( Volume Down + Power Button ) - Release it when you see the G1 logo (you will have to stuck on G1 logo that means you successfully booted to fastboot)
For Cyanogen Os Users Use the (Advance reboot to Bootloader or Volume Up + Power) there will be a screen notification that you are on a fastboot mode
Next option if you cant manually boot to fastboot just plug your G1 to pc/laptop (properly booted/Nka open)
make sure you installed the drivers properly after you plug the phone Just run the bat file and it will boot your phone to fastboot mode and the Rom Installation Will Begin
Just Run The .Bat file i created and the installation is all Automated
Notice : If an ERROR is prompt after the splash.img before the System.img flashing just ignored it , the installation still continues and running dont unplug your phone just wait it until your phone Reboots and its all done you are now on STOCK ROM LUZ59M Build ( Dont Worry if you Encounter An Error While Flashing ,the rom will be installed properly ) i just encounter this when you are from a cyanogen OS Rom
Do a Factory Reset After you Booted the ROM Properly
Credits to :
ME
August
JoeyHuab
MeteBerkErgun/Sadronis
Snoop05(xda) - 15 seconds adb/fastboot installer
To All my Fellow AndroidOne Admins 1st Gen & 2nd Gen
Enjoy and Goodluck!!!! - Kalvin/KShen
Click to expand...
Click to collapse
Hi! Can I use this to downgrade from Marshmallow? Thanks and Happy New Year!

kalvin026 said:
Just Run The .Bat file i created and the installation is all Automated
Click to expand...
Click to collapse
Where is the .bat file?

vel_tins said:
Where is the .bat file?
Click to expand...
Click to collapse
Look for Windows Batch File
---------- Post added at 06:43 AM ---------- Previous post was at 06:41 AM ----------
gabrieladrian said:
Hi! Can I use this to downgrade from Marshmallow? Thanks and Happy New Year!
Click to expand...
Click to collapse
Yes. The build number LMY refers to a marshmallow build.

rho57 said:
Look for Windows Batch File
Click to expand...
Click to collapse
?
Again, where is the .bat file, mentioned in the first post?

vel_tins said:
?
Again, where is the .bat file, mentioned in the first post?
Click to expand...
Click to collapse
Dude. Did you even at least download the stock dump? Everything that's needed is in that zipped package. Don't go around asking where the bat file because everything's in there. I'm guessing that either you haven't seen what's inside the package, or you're just lazy enough to look for it.
Better yet, learn how to flash factory images manually so you don't have to ask where that stupid bat file is anymore.

rho57 said:
Dude. Did you even at least download the stock dump? Everything that's needed is in that zipped package. Don't go around asking where the bat file because everything's in there. I'm guessing that either you haven't seen what's inside the package, or you're just lazy enough to look for it.
Better yet, learn how to flash factory images manually so you don't have to ask where that stupid bat file is anymore.
Click to expand...
Click to collapse
Seem to me that some people in this forum have short fuses. Cool down and hold your horses tight. There's no need for unnecessary and inflammatory rhetorics.

ondoy1943 said:
Seem to me that some people in this forum have short fuses. Cool down and hold your horses tight. There's no need for unnecessary and inflammatory rhetorics.
Click to expand...
Click to collapse
First of all, I don't care about your opinion. Secondly, you had the choice to help him find the bat file, but instead criticized the way I post. I don't see the point in that.

rho57 said:
First of all, I don't care about your opinion. Secondly, you had the choice to help him find the bat file, but instead criticized the way I post. I don't see the point in that.
Click to expand...
Click to collapse
Think your post as a ball; I'll hit it with a bat, and return it to you. Ha..ha. Lol...

ondoy1943 said:
Think your post as a ball; I'll hit it with a bat, and return it to you. Ha..ha. Lol...
Click to expand...
Click to collapse
Go find somebody else to troll.

inside the zip
vel_tins said:
Where is the .bat file?
Click to expand...
Click to collapse
the bat file is inside the zip file, many already tried this dump , and i will sure to you that this will work

yes 100% sure
gabrieladrian said:
Hi! Can I use this to downgrade from Marshmallow? Thanks and Happy New Year!
Click to expand...
Click to collapse
yes 100% sure but first you need to have an unlocked bootloader to do fastboot

kalvin026 said:
yes 100% sure but first you need to have an unlocked bootloader to do fastboot
Click to expand...
Click to collapse
Hi @kalvin, and a Happy new Year to you and all fellow followers of the 2nd gen android one devices. Mine is Cherry Mobile H220, I want to try going back from MM to the zip you posted. Would it be Lazy of me, if I asked you to supply the order of commands I need to get The Zip LUZ59M into the H220?. I have adb /fastboot prog running ok now(I think). In Device manager it shows that I have the necessary drivers installed, Android Composite ADB interface at top, and further down in list Portable Devices shows H220..Phone shows usb debugging connected and usb for file transfer(mtp), (in the dropdown notification list).,So, awaiting maybe a reply from you, Wish I had experimented with version 5.1.1 lollipop, before I accepted last OTA major update,,I,m a real newbie to android one devices, but have used MTK socs before with always success. The adb /fastboot thingy is a new adventure for me. I like this H220 device and dont want to ruin it,. Thank you for your time,, and to you @ vel-tins for answering my last post in another thread, The Xmas holiday period sort of held things up a bit, bending my elbow too much,LOL.....

Sockit2me said:
Hi @kalvin, and a Happy new Year to you and all fellow followers of the 2nd gen android one devices. Mine is Cherry Mobile H220, I want to try going back from MM to the zip you posted. Would it be Lazy of me, if I asked you to supply the order of commands I need to get The Zip LUZ59M into the H220?. I have adb /fastboot prog running ok now(I think). In Device manager it shows that I have the necessary drivers installed, Android Composite ADB interface at top, and further down in list Portable Devices shows H220..Phone shows usb debugging connected and usb for file transfer(mtp), (in the dropdown notification list).,So, awaiting maybe a reply from you, Wish I had experimented with version 5.1.1 lollipop, before I accepted last OTA major update,,I,m a real newbie to android one devices, but have used MTK socs before with always success. The adb /fastboot thingy is a new adventure for me. I like this H220 device and dont want to ruin it,. Thank you for your time,, and to you @ vel-tins for answering my last post in another thread, The Xmas holiday period sort of held things up a bit, bending my elbow too much,LOL.....
Click to expand...
Click to collapse
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot

rho57 said:
fastboot flash aboot emmc_appsboot.mbn
@rho57, Thanks for answer friend, but my question was meant to be, What adb commands do I use in Minimal adb and fastboot, , Anyway I,ve managed to get Luz59m into the H220, but I seem to be stuck in a bootloop situation?, The 4 moving colours are there now, which suggests Android 5,1,1 is in the phone,Then says android is starting, then maybe 101 apps need optimizing, then back to the same colours rotateing, and back to optimizing apps, (said 82 second time), now optimizing again 101, , oh dear, need help now on what went wrong?. Any ideas?..Thanks.
Click to expand...
Click to collapse

^^
Have you tried a factory reset from recovery?

vel_tins said:
^^
Have you tried a factory reset from recovery?
Click to expand...
Click to collapse
@Vel-tins. I think your referring to my last post, no I did not, slipped up on thinking about recovery, but anyway my Cherry Mobile is now a IQ2II, running 5.1.1. LUZ59Q.lol, seems to be ok, its asking me to update to the latest MM, might go back to MM after I play about a bit with Lollipop. Thanks for answering.

good day sir .. should i root first my phone H220 before to flash this rom? thank you

jsab20 said:
good day sir .. should i root first my phone H220 before to flash this rom? thank you
Click to expand...
Click to collapse
@jsab20, No need to root H220 first, I imagine your already in MM 6.0.1 version, (mmb29k). I did not wish to root,because of losing OTA upgrades, Anyway, I failed at first attempt,probably by not going into recovery,and rebooting. I downloaded version IQII from another thread by mrdmacdonald, , done exactly as he recommended and then I had successfully downgraded to 5.1.1. (luz59I), As soon as it installed it downloaded 3 updates,(wifi on) then asked if I wanted The MM major upgrade., I refused that update, till I want to go back to it later,..Go to thread I-Mobile IQII OTA URLs,, post number #20...If you try those instructions and succeed, you will have your H220 looking like an IQII on first screen,..Hope this helps my friend, good luck.

Sockit2me said:
@jsab20, No need to root H220 first, I imagine your already in MM 6.0.1 version, (mmb29k). I did not wish to root,because of losing OTA upgrades, Anyway, I failed at first attempt,probably by not going into recovery,and rebooting. I downloaded version IQII from another thread by mrdmacdonald, , done exactly as he recommended and then I had successfully downgraded to 5.1.1. (luz59I), As soon as it installed it downloaded 3 updates,(wifi on) then asked if I wanted The MM major upgrade., I refused that update, till I want to go back to it later,..Go to thread I-Mobile IQII OTA URLs,, post number #20...If you try those instructions and succeed, you will have your H220 looking like an IQII on first screen,..Hope this helps my friend, good luck.
Click to expand...
Click to collapse
@Sockit2me ..pardon me sir for asking many question cuz its my first time to handle an andriod one device and flashing using a fastboot is a new experience to me , my previous phone was a MTK device .. Yes i already upgraded to MMB29K over-the-air . I installed adb fastboot installer , and its already running , on my phone i enable usb debugging and oem unlock but when i try to flash a twrp it gets error and cannot load:crying:.. can u pls help me how to get on this ,thank you sir :good:

installing Magisk on Xiaomi A2 fails

First I unlocked the boot loader, although I doubt that’s needed for installing Magisk:
A2/Android (Oreo 8.1): Enabled developer options, enabled unlocking of boot loader, enabled debugging via USB.
PC/Linux: $ adb reboot bootloader
A2 boots into boot loader.
PC/Linux: $ fastboot oem unlock
Then I tried installing Magisk:
A2/Android: Re-enabled developer options, enabled debugging via USB, disabled automatic system updates (just in case, for later).
PC/Linux: $ adb reboot recovery
A2/Android: On the dialog asking for permission to allow USB debugging, selected to always allow from this computer and hit OK.
A2 displays screen with lying robot, saying No command. I held power, pressed volume-up once, released power.
A2 boots into recovery.
A2/Recovery: Selected Apply update from ADB.
PC/Linux:
$ adb sideload Magisk-v16.0.zip
Total xfer: 1.01x
A2/Recovery: Error message failed to verify whole-file signature
PC/Linux: Checked the zip file. It can be unzipped just fine, so it’s OK.
What else can I try?
PS: I do have detailed screen shots of the critical steps, but I don’t find an option to upload them to the forum.

You can't sideload the Magisk zip on a stock recovery. If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.

Didgeridoohan said:
You can't sideload the Magisk zip on a stock recovery.
Click to expand...
Click to collapse
Thanks!
If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
Click to expand...
Click to collapse
Tried that, but did something extremely stupid in the process, knowing full on that this could cause an issue (I assumed things are easy to fix in case something goes wrong):
I did not run any system updates, leaving the Android 8.1 ROM at V9.6.5.0. (no problem so far)
I downloaded V9.6.10.0 of the ROM, and had Magisk patch the included boot.img to create patched_boot.img (still no problem)
I flashed patched_boot.img onto my A2. Now the device did not boot anymore. It hung at the loader animation showing a horizontal bar with varying colors.
To get the A2 to boot again, I obtained V9.6.9.0 of the ROM, I flashed the included boot.img, and I cleared the cache. Unfortunately, while the device boots into Android now, I cannot enable WLAN. It simply doesn’t work. Again, no surprise: V9.6.9.0 ≠ V9.6.5.0
Not being able to find the V9.6.5.0 ROM, I got the idea to update the half broken A2 to the latest ROM, i.e. V9.6.10.0. But how, without WLAN? Well, I found out that it is possible to use the WLAN connection of another Android device via Bluetooth. This is what I used, and I had to be very patient – it’s dog slow. Anyhow, I waited, and the installer started to do its job. The download succeeded, but the installation failed.
Phew, for now I’m out of options, and I’ve a non functioning device.
In another thread on the XDA Forums, I did find an unofficial dump of V9.6.5.0. But 1. I’m hesitant to install from unofficial dumps, and 2. the dump does not include a boot.img. Instead it includes one big payload.bin. Don’t know what to make out of that.
The alternative could be to install either V9.6.10.O or V9.6.9.O manually, possibly by flashing each partition image individually from fastboot. I don’t know, however, if that is a great idea.
PS: Sorry about the confusion with all those numbers.

Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.

Didgeridoohan said:
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
Click to expand...
Click to collapse
Went ahead with that. In fact, included in the full ROM archive are scripts for doing the update, sorted by an increasing number of steps performed:
flash_all_except_data.sh
flash_all.sh
flash_all_lock.sh
flash_all_lock_crc.sh
The last one also flashes CRC check sums into crclist and sparsecrclist. Included is a script to generate these check sums form the image files: flash_gen_crc_list.py
Here’s how I got back to a system that boots up fine:
PC/Linux: $ tar xfz jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
PC/Linux: $ cd jasmine_global_images_V9.6.10.0.ODIMIFE_8.1
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Following this success, I did another attempt at installing Magisk:
PC/Linux: $ cp ../patched_boot.img images/boot.img
(created with Magisk Manager from the V9.6.10.0 boot.img)
PC/Linux: $ python2.7 flash_gen_crc_list.py
(thought it’s a good idea, but doesn’t help – see below)
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Unfortunately, upon reboot I get:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
Eventually the device doesn’t show the message anymore, instead hanging permanently at a androidone logo.
Not locking the boot loader after flashing solves the issue, but: For security reasons, I don’t want to use a device with an unlocked boot loader!
Any idea?

Uh-oh! Now it seems like I eclipsed my previous stupidity.
In the Android developer settings, I disabled OEM unlocking. Then I rebooted the device, locked the boot loader: fastboot oem lock This was still possible.
As result, I get the aforementioned error message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
But now I cannot unlock the device anymore. fastboot oem unlock gives: FAILED (remote: Flashing Unlock is not allowed)
Bricked for good, right? :crying:

Oh... I saw your first message about getting things working (post #5), but I didn't have time to answer (work, work, work).
Now I wished I would have had the time, since I would have posted that you should never lock your bootloader on a modded device. The risk of something going wrong and not being able to unlock the bootloader again is too great...
If you're lucky there's still some kind of hack available that you can use, but you'd have to take that in your device's forum, where they know the device best.
That sucks... I hope you get things sorted. Good luck.

Didgeridoohan said:
Now I wished I would have had the time, […]
Click to expand...
Click to collapse
Don’t worry. I like to take systems to their limit.
[…] since I would have posted that you should never lock your bootloader on a modded device.
Click to expand...
Click to collapse
For security reasons, I don’t like the idea of leaving the boot loader open. While I understand that – due to encryption – it’s not possible to access my data, I assume it would be feasible to modify boot.img to install a rootkit in a few minutes. Just the thought of this being possible makes me uncomfortable and not trust the device for productivity use.
I wonder if I would also get the your device is corrupt message with Lineage installed.
If you're lucky there's still some kind of hack available
Click to expand...
Click to collapse
Yes, I’m betting on that, or perhaps the Xiaomi Mi Flash Tool can be used. (looking for an official download location)

feklee said:
I wonder if I would also get the your device is corrupt message with Lineage installed.
Click to expand...
Click to collapse
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...

Didgeridoohan said:
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
Click to expand...
Click to collapse
No:
I’m almost certain that I did not enable dm-verity.
The device is corrupt message appears right after the reboot following ./flash_all_lock.sh or ./flash_all_lock_crc.sh, i.e. without any setup by Magisk Manager, and dm-verity is disabled by default.
BTW I got around to trying Xiaomi Mi Flash Tool, but it’s useless: It seems to be simply an ugly GUI for the fastboot commands. It cannot flash a device in locked state. In the end I was able to revive the device by opening it and using the test point method. Phew, gotta be more careful the next time…

HELP! My device is corrupt

I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?

features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...

Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.

I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat

jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...

Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help

features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.

If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.

Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work

features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.

Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!

features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.

Question soft bricked oneplus 10 pro that worked great with lineage os

I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!

This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
yedashare said:
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
Click to expand...
Click to collapse

Savio Dantes said:
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
Click to expand...
Click to collapse
Thank you Savio, but this is my main issue, I cannot enter fastbootD.
Whether using the tool "fastboot enhance" or using the command line. I cannot reach FastboodD.
When I try to reach this using the tool, it's looping with no error log.
And when I try from CMS:
C:\Users\me\Downloads\from dumper> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

It also still sounds like your recovery.img and/r boot.img still may be corrupted.
this needs to MATCH in BOTH slots A & B
Try this:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713

Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery

yedashare said:
and this is where I CRUSHED down by running this:
The rooting​get you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Click to expand...
Click to collapse
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers

u can try to fix sms mms problem using this thread
xiaomi 12/moto edge x30(or any device with sm8450) sms＆ims error · Issue #2246 · phhusson/treble_experimentations
Now gsi is able to boot on devices with sm8450.But sms doesn't work.And ims settings shows "not supported" .I tried to install q-ims.apk or ims.apk from the stock rom.Still ,ims does work at all. A...
github.com
@yedashare
@dladz maybe we can share it groups ?

beatbreakee said:
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
Click to expand...
Click to collapse
Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
I thought that as long as I reach the recovery mode, I can still fix it.
If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
Many thanks for your efforts.

Damn. Nice to know Lineage works well on this phone with extensive tweaking. GSI's can be pretty unstable from what I've seen, missing cell reception and the like.
Yeah, flashing that image killed the phone. I've seen some people recover by flipping their boot slot to the other one and forcing the phone to boot the stock boot there. But if you've flashed to both slots, you're most likely SOL and need a MSM flash. In which case, you could try flashing the complete stock boot image for your OOS version you were on before moving to GSI to both slots as sort of a last resort, but even then I've only seen minimal success.

Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use MSM.
I understand that MSM is no longer available.
Any other direction how I can just fix the booting process?
And this is another error I received which gets closer to the source of the problem:
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer

I’m assuming Adb does not work?

why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.

Arealhooman said:
I’m assuming Adb does not work?
Click to expand...
Click to collapse
Yes right, adb doesn't work, only fastboot is still alive

TuLy2702 said:
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Click to expand...
Click to collapse
Thanks for taking time to answer.
Could you be more specific?

I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.

yedashare said:
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
Click to expand...
Click to collapse
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS

yedashare said:
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
Click to expand...
Click to collapse
you make me laugh

yedashare said:
EoS
Click to expand...
Click to collapse
Damn. I think what happened is you lost your persist.img when initially flashing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.

Prant said:
Damn. I think what happened is you lost your persist.img when initially flaahing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Click to expand...
Click to collapse
It's okay to spend a little money. It's very risky to do it yourself

Did you managed to get fingerprint working on gsi ?

Question CRC Error on flashing via Fastboot

Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....

flashernoob said:
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
Click to expand...
Click to collapse
Developer options USB debugging is activated?
Search for flashing instructions in this forum for your preferred ROM and it's easier to flash Roms, in my opinion, with orange fox recovery (or TWRP)

Can't and won't activate USB debugging as phone is softbrick now. Didn't need to on my RN8Ts, either.
The ROM is Xiaomi stock, flashing instructions are "unpack tgz, connect phone in fastboot mode, start flash_all.bat", which is what i did (as with all the RN8Ts i have)
TWRP it is the next step, but first i need it to work with the latest official ROM...
I'd prefer OFox but i think there is no version for Android 12/MIUI 13. The beta has V11 in the name so it's for Android11, not?

flashernoob said:
Can't and won't activate USB debugging as phone is softbrick now. Didn't need to on my RN8Ts, either.
The ROM is Xiaomi stock, flashing instructions are "unpack tgz, connect phone in fastboot mode, start flash_all.bat", which is what i did (as with all the RN8Ts i have)
TWRP it is the next step, but first i need it to work with the latest official ROM...
I'd prefer OFox but i think there is no version for Android 12/MIUI 13. The beta has V11 in the name so it's for Android11, not?
Click to expand...
Click to collapse
Perhaps you find here ideas
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com
The Complete Guide to Flashing Factory Images on Android Using Fastboot
If your phone has an unlocked bootloader, you can use Fastboot commands to flash factory images. That may sound like a bunch of technical jargon, but when it comes down to it, this is the best method for updating a rooted device, fixing a bricked phone, reverting to stock, or even getting new...
android.gadgethacks.com

Thank you very much, your first link had a hint on the solution, thanks a lot!
I used the latest google/android fastboot 33.0.3, but tried another as to the thread posted, and the years old fastboot 1.4.3 from https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/#post-42407269 did the trick!
Never would i have thought that a 4 year old hack would work better than the latest official google file....

flashernoob said:
Ayo,
i got a new N10Pro EEA and tried to update it to the latest official ROM to play a bit with it.
Bootloader is unlocked since yesterday, and i tried to download the 13.0.15 and 13.0.16 from different sites. Checked CRCs and all are good.
Unpacked the TGZ file and added the necessary fastboot.exe and files. (Did it this way a lot of Redmi Note 8T times... )
Got the device in fastboot mode, connected it and started the flash_all.bat
It goes through until it tries to flash part 7 of the super image, then it fails with a CRC error.
It does this on either the EEA version (13.0.16) and the global (13.0.15), and i've checked repeatedly that my files are ok and i'm positive they are.
I edited the super line out of the file and all the others go through flawlessly, but now my device just bootloops because the most of data is corrupt of course.
What did i do wrong?
I just had a SIM in there, registered the Mi account (i used it for all my RN8Ts), unlocked it with a week wait and nothing more.
No Wifi, no other accounts, just the minimum necessary to unlock it, then tried to flash....
Click to expand...
Click to collapse
I solved my soft brick using the 13 image files on my RN11. This got me out of a perpetual fastboot loop. (It should also work on the RN10P)
i.e. fastboot flash boot boot.img, fastboot flash super super.img etc for all 13 images.
I tried the flash_all.bat several times but it just kept borking at different spots and I needed to get out of that fastboot loop hell.

The flash_all bat works like a charm for me, there's no sense in typing all the lines one for one.
The exe seems to bork at the size of the super image, the RN8 hadn't such a thing, the RN10 has a 7G file the exe couldn't stand, obviously.
At least it did CRC error repeatedly, with different ROMs, all at the 7 of 10 or 7 of 11 stage...