Database Develop

[FIX] Bionic (Boot FAILURE) & (CDT FAILURE)

Okay so I have noticed that there are still some people out there having issues with either going back from Update .901 or have dropped into a (Boot Failure) mode and cannot find a solution. I have decided to post up what works for me. Mind you I have personally and purposely bricked my Bionic multiple times to ensure that this works. However:
I am in no way responsible for any permanent damage you do to your phone. If you have an issue I will do the best I can to assist as I’m sure the rest of the members will. But you take full responsibility for anything you decide to attempt.
While some of you have been able to use the one click method provided by , some of you can’t follow through with the fix due to the (Boot Failure) or (CDT Failure). I have changed some of the files in the One Click method provided by. These files worked for me multiple times but I cannot gauruntee they will do the same for you. But if you are brave enough giver er hell.
Step One: Download these files. You will need all three if you want to go through to .901. Each update is labeled as such to limit the confusion. Once downloaded move all folders to your desktop and unzip the CDT file ONLY!!!
http://www.megaupload.com/?d=GZ4AC6ML
http://www.megaupload.com/?d=3XE1OFOM
http://www.megaupload.com/?d=TSYCAFP4
Step Two: Plug your Bionic in via USB. Once plugged in you can either boot into Fastboot mode by holding the POWER + VOLUME DOWN. If you are in (CDT Failure) you won’t be able to reach fast boot but that’s okay. In fact “Fastboot” mode isn’t necessary as long as you are in one of these error screens.
Step Three: Open the folder labeled “CDT_BOOT_FIX” and double click “EVERYTHING”. The system will begin running the install of the files contained. ALL FILES SHOULD SUCCEED. Not one of these files should fail and in the event one does please post so we may figure it out together.
Edit: You will need to also download this and place it into the unzipped CDT folder:
Sorry I must have forgotten to add it originally when composing the file.
Step Four: Once the files have finished running, reboot your Bionic. You should now have a running system. YOU ARE NOT FINISHED YET, so please pay attention. Failure to do so will only cause you to go through this again.
Step Five: Move the Update files (893 if you only want to go that far or 893 and 901 to go all the way) to your SD card. Make sure both files are on the root of the SD card. Now shut down your phone.
Step Five: Boot into recovery and choose “Update Zip on SD Card”. Choose the 893 file and click okay. Your phone will now install the 893 update. Reboot. STILL NOT DONE. As noted below if you plan to go to the .901 update then you can skip step six and just flash both the 893 and 901 one right after the other. If only going to 893 then proceed to step six.
Step Six: Your phone will now boot into “CDT Failure”. Make sure your Bionic is plugged into the USB port. Hover your mouse over the “CDT_BOOT_FIX” folder, hold SHIFT and RIGHT CLICK your mouse. A pop-up box comes up. Click “Open Command Prompt Here”. Once the Command Prompt comes up type:
moto-fastboot flash cdt.bin cdt.bin
/\ You can copy and paste this if you would like.
Your phone will now flash the CDT file. It should succeed. Once this is complete you are full OTA 893. You now have the choice of booting into recovery and loading the 901 file should you choose to do so.
That should be it. Thank you to all who have contributed. The scripting for the Everything command came from P3DROID. If you object to me using it please let me know. I appreciate it but the files can be run manually so no biggy. Thanks
If you have any problems feel free to ask

If you are still having problems I will do my best to assist. If it comes down to it download Team Viewer (www.teamviewer.com) and all files posted here. I will then run the repair process for you. Just for some peace of mind Team Viewer is a remote PC control program. It generates a password each time it is opened so it can never be replicated unless you choose to set a password. If at anytime you feel uncomfortable with what's going on you can immediately close Team Viewer and break the connection. If you need help this badly send me a PM and we will set up a time. As it stands now I am on duty from 6 P.M. to 6 A.M. And yes if it helps you any I am a Police Officer in the State of Ohio.

i just unpacked the 901 update and flashed the cdt file from it to get by this problem. took me a few different cdt files to get it right though.

Glad you found a solution. Some people just can't seem to get through this issue. Doing this process will put you back on 893 updatable.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk

I'm having an issue now it wont let me use your recovery img and I have to use one from 893 FXZ rather then yours. but then once I get to recovery it wont let me update to 893 (I guess it thinks I'm already there?) so I'm not sure what to do atm.
I also noticed on your batch file you put "moto-fastboot boot boot.img" it should be "moto-fastboot flash boot boot.img"

Eluvatar said:
I'm having an issue now it wont let me use your recovery img and I have to use one from 893 FXZ rather then yours. but then once I get to recovery it wont let me update to 893 (I guess it thinks I'm already there?) so I'm not sure what to do atm.
I also noticed on your batch file you put "moto-fastboot boot boot.img" it should be "moto-fastboot flash boot boot.img"
Click to expand...
Click to collapse
I apologize and will fix this. Thank you for pointing it out. I also posted a reply to your thread on Rootzwiki.

Hello, first off, I will like to thank for all the help!
Ever since I tried upgrading to 901, I been having a brick for 2 days now.
I read through your post a few times and I am using your method to fix the problem.
You specifically stated, everything should be OKAY. But in my case,
boot.img and recovery both failed.
Any help will be greatly appreciated!
Thank you again for all the help and support!
Gil
Here is a copy of my output:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.008s]
writing 'cdt.bin'... OKAY [ 0.864s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.000s]
Press any key to continue . . .
erasing 'cache'... OKAY [ 0.013s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.008s]
writing 'lbl'... OKAY [ 0.466s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.062s]
writing 'logo.bin'... OKAY [ 0.379s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.466s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.002s]
writing 'mbr'... OKAY [ 0.404s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.044s]
writing 'devtree'... OKAY [ 0.511s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 17.225s]
writing 'system'... OKAY [ 24.643s]
sending 'system' (229120 KB)... OKAY [ 15.139s]
writing 'system'... OKAY [ 22.028s]
Press any key to continue . . .
downloading 'boot.img'... OKAY [ 0.553s]
booting... FAILED (remote: unsupported command)
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 0.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 0.908s]
writing 'cdrom'... OKAY [ 2.269s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 16.790s]
writing 'preinstall'... OKAY [ 23.150s]
sending 'preinstall' (49152 KB)... OKAY [ 3.175s]
writing 'preinstall'... OKAY [ 4.221s]
Press any key to continue . . .
sending 'webtop' (262144 KB)... OKAY [ 17.211s]
writing 'webtop'......

Can you try manually pushing the boot and recovery images. Some users have reported that the one click want able to do this. Let me know what happens.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk

There is a missing command in the batch file I have.
This below should do what you need it to do, I still have the recovery flashing error though.
ERROR
sending 'recovery' (9216 KB)... OKAY [ 0.663s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )​
Which actually doesn't matter once you can get into a working system.
Contents of the corrected batch file
@echo off
pause
moto-fastboot flash cdt.bin cdt.bin
pause
moto-fastboot reboot-bootloader
pause
moto-fastboot erase cache
pause
moto-fastboot flash lbl lbl
pause
moto-fastboot flash logo.bin logo.bin
pause
moto-fastboot flash ebr ebr
pause
moto-fastboot flash mbr mbr
pause
moto-fastboot flash devtree device_tree.bin
pause
moto-fastboot flash system system.img
pause
moto-fastboot flash boot boot.img
pause
moto-fastboot flash recovery recovery.img
pause
moto-fastboot flash cdrom cdrom
pause
moto-fastboot flash preinstall preinstall.img
pause
moto-fastboot flash webtop grfs.img
pause
moto-fastboot flash radio radio.img
pause
moto-fastboot -w
pause​
The fixed batch file can be downloaded [HERE]

Terror_1 said:
There is a missing command in the batch file I have.
This below should do what you need it to do, I still have the recovery flashing error though.
ERROR
sending 'recovery' (9216 KB)... OKAY [ 0.663s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )​
Contents of the corrected batch file
@echo off
pause
moto-fastboot flash cdt.bin cdt.bin
pause
moto-fastboot reboot-bootloader
pause
moto-fastboot erase cache
pause
moto-fastboot flash lbl lbl
pause
moto-fastboot flash logo.bin logo.bin
pause
moto-fastboot flash ebr ebr
pause
moto-fastboot flash mbr mbr
pause
moto-fastboot flash devtree device_tree.bin
pause
moto-fastboot flash system system.img
pause
moto-fastboot flash boot boot.img
pause
moto-fastboot flash recovery recovery.img
pause
moto-fastboot flash cdrom cdrom
pause
moto-fastboot flash preinstall preinstall.img
pause
moto-fastboot flash webtop grfs.img
pause
moto-fastboot flash radio radio.img
pause
moto-fastboot -w
pause​
Click to expand...
Click to collapse
That is awesome and thank you. As for the Recovery what is your current system info?

darkstarsinner said:
That is awesome and thank you. As for the Recovery what is your current system info?
Click to expand...
Click to collapse
Doesn't matter, once the phone gets to a point where it will boot you can use the 1 click path saver to get things back up and running.

Good deal. Hopefully that will work for everybody. There are so many different errors out there we should compile a list of fixes into one thread to make it a little easier for everyone to find.
Sent from my super awesome Kindle Fire running CM7 with Tapatalk

Hi everybody,
A buddy of mine bricked his bionic by attempting the 901 update with root so I attempted this fix since it was stuck in boot failure. The phone will now boot up but doesn't pull in any service. Am able to connect it to wi-fi, but once you hit the droid to run thru set up, it sits there thinking, telling me, "please wait, this may take a few moments." I attempted going back into recovery and installing the 893 zip and 901 zip and both fail. I've also attempted using rsd lite with the 893 fxz but no dice. Here's what I'm looking at when running the script:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.011s]
writing 'cdt.bin'... OKAY [ 0.564s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.008s]
Press any key to continue . . .
< waiting for device >
erasing 'cache'... OKAY [ 0.039s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.016s]
writing 'lbl'... OKAY [ 0.486s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.162s]
writing 'logo.bin'... OKAY [ 0.309s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.013s]
writing 'ebr'... OKAY [ 0.468s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.398s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.094s]
writing 'devtree'... OKAY [ 0.518s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 81.860s]
writing 'system'... OKAY [ 22.592s]
sending 'system' (229120 KB)... OKAY [ 45.569s]
writing 'system'... OKAY [ 20.132s]
Press any key to continue . . .
sending 'boot' (8192 KB)... OKAY [ 1.674s]
writing 'boot'... OKAY [ 1.139s]
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 1.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 2.443s]
writing 'cdrom'... OKAY [ 2.109s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 46.399s]
writing 'preinstall'... OKAY [ 22.774s]
sending 'preinstall' (49152 KB)... OKAY [ 8.490s]
writing 'preinstall'... OKAY [ 4.404s]
Press any key to continue . . .
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Press any key to continue . . .
sending 'radio' (21768 KB)... OKAY [ 3.661s]
writing 'radio'... OKAY [ 2.052s]
Press any key to continue . . .
Any help would be greatly appreciated! Thanks again for all the hard work that goes into this!

s.dubs317 said:
Hi everybody,
A buddy of mine bricked his bionic by attempting the 901 update with root so I attempted this fix since it was stuck in boot failure. The phone will now boot up but doesn't pull in any service. Am able to connect it to wi-fi, but once you hit the droid to run thru set up, it sits there thinking, telling me, "please wait, this may take a few moments." I attempted going back into recovery and installing the 893 zip and 901 zip and both fail. I've also attempted using rsd lite with the 893 fxz but no dice. Here's what I'm looking at when running the script:
Press any key to continue . . .
sending 'cdt.bin' (16 KB)... OKAY [ 0.011s]
writing 'cdt.bin'... OKAY [ 0.564s]
Press any key to continue . . .
rebooting into bootloader... OKAY [ 0.008s]
Press any key to continue . . .
< waiting for device >
erasing 'cache'... OKAY [ 0.039s]
Press any key to continue . . .
sending 'lbl' (16 KB)... OKAY [ 0.016s]
writing 'lbl'... OKAY [ 0.486s]
Press any key to continue . . .
sending 'logo.bin' (854 KB)... OKAY [ 0.162s]
writing 'logo.bin'... OKAY [ 0.309s]
Press any key to continue . . .
sending 'ebr' (16 KB)... OKAY [ 0.013s]
writing 'ebr'... OKAY [ 0.468s]
Press any key to continue . . .
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.398s]
Press any key to continue . . .
sending 'devtree' (512 KB)... OKAY [ 0.094s]
writing 'devtree'... OKAY [ 0.518s]
Press any key to continue . . .
sending 'system' (262144 KB)... OKAY [ 81.860s]
writing 'system'... OKAY [ 22.592s]
sending 'system' (229120 KB)... OKAY [ 45.569s]
writing 'system'... OKAY [ 20.132s]
Press any key to continue . . .
sending 'boot' (8192 KB)... OKAY [ 1.674s]
writing 'boot'... OKAY [ 1.139s]
Press any key to continue . . .
sending 'recovery' (9216 KB)... OKAY [ 1.618s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Press any key to continue . . .
sending 'cdrom' (12032 KB)... OKAY [ 2.443s]
writing 'cdrom'... OKAY [ 2.109s]
Press any key to continue . . .
sending 'preinstall' (262144 KB)... OKAY [ 46.399s]
writing 'preinstall'... OKAY [ 22.774s]
sending 'preinstall' (49152 KB)... OKAY [ 8.490s]
writing 'preinstall'... OKAY [ 4.404s]
Press any key to continue . . .
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Press any key to continue . . .
sending 'radio' (21768 KB)... OKAY [ 3.661s]
writing 'radio'... OKAY [ 2.052s]
Press any key to continue . . .
Any help would be greatly appreciated! Thanks again for all the hard work that goes into this!
Click to expand...
Click to collapse
I am getting the exact same issue. I am getting errors in the recovery and cant get to the point where i can turn usb debugging on for 1 click path to work. any ideaS?

To those getting stuck at the "push the android" screen and have the recovery error,
you can touch the four corners of the LCD starting from top left and moving clockwise to each corner. This will bypass the android guy and send you to the home screen allowing you to put your device in usb debug mode and push the files through path saver.

MarcMaiden said:
To those getting stuck at the "push the android" screen and have the recovery error,
you can touch the four corners of the LCD starting from top left and moving clockwise to each corner. This will bypass the android guy and send you to the home screen allowing you to put your device in usb debug mode and push the files through path saver.
Click to expand...
Click to collapse
I wish it was that easy but it will not allow me to bypass the android guy. Usually i can click him and skip thru setup then go into settings but when clicking the android guy it just sits there thinking saying please wait, this may take a few minutes, but never gets past that point. Any other ideas?
Sent from my DROID BIONIC using xda premium

I believe my problem stems from flashing webtop grfs.img. Fails out any time i try and says:
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Please help! I would hate to see this phone a paper weight!
Sent from my DROID BIONIC using xda premium

Ok so i ended up flashing the radio.zip from the guide, how to receive otas again if you are on a leak, and was able to boot up afterwards, skip the setup and am about to run the pathsaver. Will let you know how i make out...
Sent from my DROID BIONIC using xda premium

Edit- looks like youre on your way

i attempted this method and it did this:
sending 'recovery' (9216 KB)... OKAY [ 1.594s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: >
Press any key to continue . . .
==============
EDIT: everything else was sent to the phone ok, so once done i powered it down/up, then rather then booting up normally, it automatically went into the stock recovery, so i pressed the VOL UP+DOWN to proceed and it then showed this:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/caller
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
==============
EDIT 2: I ignored the above, rebooted & chose to boot normally. Upon doing so, it loads up and gets to the "Welcome to DROID BIONIC" screen. When i tap on the android figure to begin, it just stays at "Please wait, this may take a few minutes." but never changes. Does not proceed any further.

[Q] I have brick my Droid 4 - Stuck in fastboot mode.

Hi !
I think have soft bricked my Droid 4:
Code:
Invalid flash mode (S) (boot failure)
OA.74
eMMC Info: Size 16G
To return to normal mode - first press key to power down
Device is LOCKED, Status Code :0
Battery OK
Ok to program
Transfer mode
USB connected
Invalid CG OTV (CG:system) Invalid SP Data
Invalid CG Version (CG:System)
Invalid CG OTV (CG:System)
I try to flash the ROM with VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml with RSD Lite 5.7 and it's stuck on flashing system.
If I try with fastboot he stuck on Writing :
Code:
C:\Documents and Settings\Administrateur>moto-fastboot flash system "C:\Documents and Settings\Administrateur\Bureau\VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml\system.img"
sending 'system' (262144 KB)... OKAY [203.703s]
writing 'system'...
What's happend ?
Regards,
Gaël

try different usb port, try different computer.
and try to do it quickly until battery has a charge

I have tried on different PC and USB Port
My batery is completly discharged.
I have make my own Factory Cable, to get it power up.
Now I trying to redownload the ZIP to view if it comrrupt ...

FukTheRegister said:
I have tried on different PC and USB Port
My batery is completly discharged.
I have make my own Factory Cable, to get it power up.
Now I trying to redownload the ZIP to view if it comrrupt ...
Click to expand...
Click to collapse
Same with new ZIP file...

I trying the Droid 4 ICS Utility ...
Exactly the same :'(
Code:
[*] Simple Droid 4 Restore
[*] Windows Version
[*] Created by mattlgroff (with help from dhacker29!)
[*] Follow us @mattlgroff @dhacker29 or on DroidRZR.com
[*]
[*] Before continuing, ensure your Droid is in the
[*] "AP Fastboot" mode and connected via USB.
[*]
[*]--- Also press the keys after the screen flashes back on when asked---
[*] IF YOUR PHONE SAYS STATUS 1 UNLOCKED EXIT NOW AND EMAIL ME
[*] YOU HAVE AN UNLOCKED BOOTLOADER! ! ! ! !
[*] [email protected] RUNNING THIS WILL LOCK YOUR BOOTLOADER!
[*]
[*] ** BE SURE YOUR BATTERY IS CHARGED **
[*]
Appuyez sur une touche pour continuer...
[*]
[*] Press enter to restore your phone to ICS 6.16.217 and ERASE DATA.
Appuyez sur une touche pour continuer...
[*]
sending 'mbm' (512 KB)... OKAY [ 0.406s]
writing 'mbm'... OKAY [ 0.484s]
rebooting into bootloader... OKAY [ 0.281s]
Press any key AFTER the screen comes back on
Appuyez sur une touche pour continuer...
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.063s]
writing 'mbmloader'... OKAY [ 0.297s]
sending 'mbm' (512 KB)... OKAY [ 0.672s]
writing 'mbm'... OKAY [ 0.469s]
rebooting into bootloader... OKAY [ 0.281s]
Press any key AFTER the screen comes back on
Appuyez sur une touche pour continuer...
< waiting for device >
erasing 'userdata'... OKAY [ 0.094s]
erasing 'cache'... OKAY [ 0.031s]
sending 'cdt.bin' (16 KB)... OKAY [ 0.031s]
writing 'cdt.bin'... OKAY [ 1.031s]
sending 'devtree' (512 KB)... OKAY [ 0.594s]
writing 'devtree'... OKAY [ 0.500s]
sending 'logo.bin' (854 KB)... OKAY [ 0.844s]
writing 'logo.bin'... OKAY [ 0.281s]
sending 'system' (262144 KB)... OKAY [207.781s]
writing 'system'...
...

Resolved
Hi !
I have take a old PC in y cave, an Dell Optiplex 755, reinstall XP SP3, and motorola drivers.
Put only one USB Factory (home made) to motorola.
I use this PC via RDP (I think, better for get more Power on USB ports), and flash it (with SAME ZIP before !).
The flash flash work directly, only 20 minutes !
The cause, is realy the HARDWARE, I cannot charge my baterie, don't change software from my before tests.
The PC have 3Go of RAM.
Regards, I hoppe if you are in same state, realy try to get a fresh PC, with MINAMAL on it.
(This PC is my 4th for the flashing !).

Modded build.prop, phone now stuck
Got bold and hastily modded my build.prop (probably forgot to change permissions on the file). Now my phone won't boot or shut off, any suggestions? Was on Hashcode's most recent JB AOKP when this happened. Phone isn't showing up in RSDlite. The phone has been plugged in to my computer as I've messing around with various apps all day so the drivers should be installed.

Stuck phone issue resolved
Sent from my SGH-T839 using Tapatalk

stock-device bricked itself (battery drained with pinned app, ecnrypted device)

Hi there,
tl;dr:
Basically, my problem seems to be, that any write-operation on my filesytems is refused:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Click to expand...
Click to collapse
I found threads about the same problem on Moto G 2013, where "Philz Recovery" was able to fix the partitioning and filesystems, but it seems that this does not exist vor Moto G 2014. And I don't even get any other than stock-recovery working.
TWRP site states: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. " But I could not find any key combo to enter the recovery I just flashed (at least fastboot tells me so) Using "fastboot boot recovery.img" just shows a shortly flickering Motorola-logo every 10 seconds or so.
---
I am having severe issues with my Moto G (2014).
I found some reports of similar issues, but no solution described worked, and it seems I am the only one experiencing this on a stock device.
First some facts:
Device in use since 2 months
Encyption activated about a month ago, no problems
Yesterday, I used screen pinning feature to let my son play a game.
While he was playing, the battery drained until the device shut down.
I connected the device to a charger
After charging 30%, everything first seems normal, I have to enter my encryption PIN and boot process goes on, showing boot animation.
The problem:
At the point, where it would normally finish, the screen just gets black (while still being lit up). Nothing more will happen. The device will remain in this state forever or until the battery is completely drained again.
I first tried using the official methods for (factory) reset described on Motorolas website, they did not work (I am not allowed to post links here yet, google "/prod_answer_detail/a_id/99825/p/30,6720,9151" will show the URL)
Pressing 7-8 seconds restarts the phone, same situation.
Pressing 120 seconds restarts the phone several times, still not working.
I wanted to perform a factory reset, but starting recovery from bootloader only displayed "Boot Up Failed". Choosing "factory" or "bp tools" just started normal boot process. Barcodes seems to work, it shows barcodes.
So next step was unlocking the device to install TWRP. Fastboot displayed no errors, but then not TWRP, but normal recovery starts. Well, better than "Boot Up Failed".
When now performing a factory reset, this is displayed:
Code:
-- Wiping data...
Formatting /data...
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/userdata failed
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/cache failed
-- Wiping clogo...
Data wipe complete
Obviously, the partitions are untouched (or not there?), and the problem remains.
I also tried to erase cache and userdata using fastboot, there are no error messages, but after rebooting, I am still asked for encryption PIN, so it's basically the same.
I then tried to use adb sideload to flash cm12 nightly. But the device complains that the signature verification failed.
Now, I am not even able to lock the device again, while fastboot states, it would have succeeded.
I wanted to reinstall stock images as described on thetechrism.com (Google: restore-moto-g-2and-generation-2014-stock-lock-bootloader) but I have problems downloading as I only have mobile internet connection at this moment and the download from filefactory stopped two times at 200 MB and I have only about 1 GB traffic for the rest of the month.
I am stuck here, and getting desperate. Did my device brick itself?
I have CM12 and TWRP here, but just cannot get it flashed. This would be my preferred solution, but a reliable source for stock images would also be very nice.
Did anyone experience similar problems when the battery completely drained with a pinned app on an encrypted device?
Thanks in advance for any hint.
Regards
cxxxx

I was now able to download the original firmware.
But...it's the same :'(
I did every step to reinstall stock firmware. No error-messages, neither on console nor on device, everything seems to be fine.
But when I finally reboot, the device again asks for my encryption PIN and will fail to startup!
I still cannot wipe my userdata, still cannot flash a custom recovery...nothing. It's just a ******* brick.
I found one interesting error:
Code:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.066s]
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.133s
How can I manually reformat my partitions in internal storage or how can I force automatically formatting?
Code:
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.041s]
writing 'partition'...
OKAY [ 0.304s]
finished. total time: 0.347s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.134s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.954s]
finished. total time: 1.091s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.087s]
writing 'logo'...
OKAY [ 0.044s]
finished. total time: 0.134s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.060s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.607s]
finished. total time: 1.075s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 9.899s]
writing 'system'...
OKAY [ 8.160s]
finished. total time: 18.063s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 9.860s]
writing 'system'...
OKAY [ 8.230s]
finished. total time: 18.094s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 9.874s]
writing 'system'...
OKAY [ 7.975s]
finished. total time: 17.853s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 8.841s]
writing 'system'...
OKAY [ 7.559s]
finished. total time: 16.402s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.941s]
writing 'modem'...
OKAY [ 0.854s]
finished. total time: 2.798s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.013s]
finished. total time: 0.014s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.018s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot reboot
rebooting...
finished. total time: 0.002s

I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup

izaiasfilho said:
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
Click to expand...
Click to collapse
We are not alone, see here:
http://forum.xda-developers.com/mot...ttery-left-t3085322/post60312526#post60312526
Bad news is, that the problem has not been solved and probably will not as it seems that it's hardware-failure of the flash-storage-(controller).

@cxxxx
I read about it on the moto forums, with users having lost write operations on their phone. And all had one thing in common, they had let the battery die out .
Lesson to be learnt : Never let Li ion batteries totally get drained.
One of the moto moderator told it on their forum to never let your battery totally die. I dont know how much of it rings true as I've let my phone discharged till death many times without any issues.

Same problem here.
After the battery gone once i did't manage to enter. Services errors at android home screen and i can't do recovery - wipe data - cache (all failed). The only thing that i manage is to unlock bootloader.
My question: I 'm thinking to send device for warranty (buying one month ago). Do you think that i 'll have problem with unlock bootloader at service. Somewhere i read that motorola have 2 year warranty for software no matter what. Is that real???

HardBricked unlocked stock lollipop xt1068
Same problem here. But no enconding is on thou.
Can't flash anything - stuck on black screen after boot animation.
XT1068 Unlocked bootloader, stock lollipop, no root, no Motorola service in my country.
Once this devices gone hardbrick, after freaky TWRP could not backup or do anything else. Just could not turn in on at all.
Recovered with jtag riff drivers, but this seems to help bootup, not to flash firmwares - so its not applicable for this case.
RSD Lite 6.1.6 can't see phone, ADB sideload form stock recovery gives no device for adb or windows device manager, but fastboot is okay.
Tryed different computers, different drivers, different stock roms, different fastboot\mfastboot tools, recover scripts.

Hi, guys. I'd face the same problem, but I can boot up, using a Nokia phone charger. Don't know how to explain, but the moto g 2014 charger can't charge enough to boot, when the battery is 0%, then come back to the black screen. With the nokia charger, my moto g boot up normally.
Sorry for my bad english.
Nico

For all those users with soft-bricked "nothing changes after any actions", what if we try to use:
Fastboot erase all
If this would work - bootloader will be dead. We will get the hard brick.
But I have experience of successful recovering xt1068(exactly this one) from hard-brick state, when decice does not turn on at all in any way or mode since bootloader is missing or corrupted.
But PC still can see it over USB cable as QBULC_USB. This one would not work with Motorola drivers nor with any other, but JTAG Riff drivers for QUALCOMM.
Then special low-level tool will load up bootloader.
So? Any suggestions about this?

I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app

Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Click to expand...
Click to collapse
No way of backing up this data?
I remember some of mine old RAZR - I had some backup of unique data for it.
BTW I have the box with IMEI on it, CID saved in notepad, what else...
Stock fw with no root and THIS with no reason.
Also - right before stucked - phone has drained battery from 60% to 0% in pretty short time, then this happened.
Maybe there is some hardware problem with electric circuit..

Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
With my device bricked like this I have tried, CHMOD which has unable to alter the partitions, as well as CHOWN & CHGRP(in both TWRP & ADB), Fastboot erase does nothing along with ADB wipe, TWRP does nothing and no changes can be made as nothing is overwritten, as well as with using Fastboot flash, there have been rumors that Philz can fix it but since nothing can be flashed I cannot try (Unless someone has a way to flash it to SD and let it boot from there, Let me know)
Now with my limited knowledge of android and its partitions and since none of the above methods having any effect I believe that this issue is in fact a hardware one not software related, therefore I think 'Fastboot erase all" will have no effect, that is my opinion gathered from more than two weeks testing, wiping & hoping, if there are any senior users/devs who want to correct me they may, Also if they have any other options I will be glad to try it out.
EDIT: This is purely a hardware fault and no software changes can do anything, I ran Fastboot erase all
...and a reboot later and my device is exactly the same, even boots into recovery fine and fastboot barcodes still shows my original IMEI and Serial number, ADB getvar_cid still also shows the correct CID for my device.
I would upload pictures but I haven't got enough posts to link to tinypic

How To Guide Flashing a GSI to redmi note 10 5G KEEPING IT SIMPLE edition.

Flashing a GSI to redmi note 10 5G KEEPING IT SIMPLE edition.
(I dont take responsibility of you destroying your device or causing the world end by flashing. Take proper precautions before proceeding and do your research about the subject and your device)
(Before you proceed, backup important data from your internal storage, i also assume that you have adb tools and drivers installed for your device and bootloader unlocked. Please do also your own research about your device before proceeding.)
adb reboot bootloader (Booting to fastboot)
fastboot reboot fastboot (Booting from fastboot to fastbootd)
fastboot erase system
fastboot -w (deletes userdata, formats the data partition. running this just to be sure personally)
You migth get an error :
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata (wich is no cause for concern)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (Thanks 1lopes for pointing missing arguments, more information in the first 3 comments)
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.013s]
fastboot fastboot flash system GSIofyourchoice.img
Invalid sparse file format at header magic (no need for concern)
Resizing 'system_a' OKAY [ 0.008s]
Sending sparse 'system_a' 1/7 (262108 KB) OKAY [ 20.939s]
Writing 'system_a' OKAY [ 1.041s]
Sending sparse 'system_a' 2/7 (262120 KB) OKAY [ 21.163s]
Writing 'system_a' OKAY [ 1.217s]
Sending sparse 'system_a' 3/7 (262116 KB) OKAY [ 19.183s]
Writing 'system_a' OKAY [ 1.157s]
Sending sparse 'system_a' 4/7 (262120 KB) OKAY [ 15.908s]
Writing 'system_a' OKAY [ 1.052s]
Sending sparse 'system_a' 5/7 (262088 KB) OKAY [ 19.747s]
Writing 'system_a' OKAY [ 1.045s]
Sending sparse 'system_a' 6/7 (262124 KB) OKAY [ 20.658s]
Writing 'system_a' OKAY [ 1.038s]
Sending sparse 'system_a' 7/7 (166688 KB) OKAY [ 13.939s]
Writing 'system_a' OKAY [ 0.861s]
Finished. Total time: 152.907s
fastboot reboot recovery (Reboots your phone to recovery, do factory reset) (EDITED)
This way, you dont destroy ability to boot to fastboot, fastbootd and you keep your original recovery and bootloader intact. If you boot to recovery after a reboot, do a factory reset from there and try to boot again, should work. IF it dosen't, you can easily try other gsi with the same steps.
vbmeta.img provided in this guide disables Android Verified Boot (AVB), Some devices have problems booting into custom GSI:s it enabled.
EDIT:
I was in stock MIUI13 (bootloader unlocked) , did factory reset, re enabled usb debugging and followed the steps in this guide.
I personally used phusson android 12 gsi
(system-squeak-arm64-ab-vndklite-vanilla-secure)
with the vbmeta.img in this guide.
Origin of vbmeta.img and information. Please use the vbmeta.img provided below. If the drive link does not work, you can find it from the original information source below. :
vbmeta.img
drive.google.com
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

i have a question. from the other guide to flash pe, why cant we do the command
fastboot delete-logical-partition product
?
thanks for the guide btw, might try later on my redmi note 10 5g flashing pe in it, just this question tho

also i think u forgot a very important step, i think you need to disable verity and verification or that could boot up with dm-verity corruption
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

1lopes said:
also i think u forgot a very important step, i think you need to disable verity and verification or that could boot up with dm-verity corruption
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thanks for pointing that out mate ! ill be adding it to op. I did not need the arguments personally tough but it is better to be safe than sorry!
The reason i discourage the wiping of logical partition ''product'' is, it contains the original recovery for example, information for fastboot and fastbootd. It is not needed to wipe product partition at all in order to flash GSI:s and use them.
If you have software to replace the functions with 3rd party ones and you know what you are doing, you can do it but just be aware what changes you are doing for your phone's software.
it contains the crucial pieces i want to keep safe in this quide to make it easyer to go back to stock frimware.
Remember to use the vbmeta.img im pointing to in this guide. Im quoting the reason directly from xda. if the vbmeta.img direct drive link does not work, look it up from the original information source :
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
''
On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)
''
However if this information is wrong, ill admit it and pull it off. This guide contains the steps i followed personally with success and without hassle with this device.

toonTT said:
Thanks for pointing that out mate ! ill be adding it to op. I did not need the arguments personally tough but it is better to be safe than sorry!
The reason i discourage the wiping of logical partition ''product'' is, it contains the original recovery for example, information for fastboot and fastbootd. It is not needed to wipe product partition at all in order to flash GSI:s and use them.
If you have software to replace the functions with 3rd party ones and you know what you are doing, you can do it but just be aware what changes you are doing for your phone's software.
it contains the crucial pieces i want to keep safe in this quide to make it easyer to go back to stock frimware.
Remember to use the vbmeta.img im pointing to in this guide. Im quoting the reason directly from xda. if the vbmeta.img direct drive link does not work, look it up from the original information source :
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
''
On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)
''
However if this information is wrong, ill admit it and pull it off. This guide contains the steps i followed personally with success and without hassle with this device.
Click to expand...
Click to collapse
Thank you so much for the information, especially about deleting the logical partition product.
Maybe that would have had affected the last part of wiping user data in recovery after flashing a GSI? (Unless the fastboot -w already does it) in the other guide. For example, this person couldn't get any GSI booting.
Also, dont you necessarily need to set active a? ( fastboot set_active a )
toonTT said:
I did not need the arguments personally tough but it is be better to be safe than sorry!
Click to expand...
Click to collapse
Didnt mean to make a argument for you, i was just pointing it all!

1lopes said:
Didnt mean to make a argument for you, i was just pointing it all!
Click to expand...
Click to collapse
Oh dear my bad, i wasn't clear enough what i meant by that. did not mean it that way, i was talking about the command arguments what you use with fastboot while flashing vbmeta.img . '' --disable-verity --disable-verification '' i did not personally use them and had not problems.
fastboot -w formats the data partition, where user data is, thats how i understand it.
About the booting problem , that he deleted the logical partition is a red flag for me. Im no expert but thats how i see it.

toonTT said:
Oh dear my bad, i wasn't clear enough what i meant by that. did not mean it that way, i was talking about the command arguments what you use with fastboot while flashing vbmeta.img .
Click to expand...
Click to collapse
Oh! I misunderstood it. I'm sorry. Anyways, lets move on.
toonTT said:
About the booting problem , that he deleted the logical partition is a red flag for me. Im no expert but thats how i see it.
Click to expand...
Click to collapse
Actually, you probably are correct. It basically might delete recovery and fastboot information just like you said, and from here it also refers as it being a system extension, etc. that I really don't understand my self.
toonTT said:
fastboot -w formats the data partition, where user data is, thats how i understand it.
Click to expand...
Click to collapse
Oh, thanks for it, as I was unsure from my last reply. Maybe it's not really necessary, but thanks to you for pointing out that fastboot delete-logical-partition product would delete the original recovery, as for that you don't need to do that command because you only need to do fastboot reboot recovery and then select wipe data and all done.
Again, thank you for pointing the big problem of the logical partition product deleting. I was about to flash PE maybe yesterday or the day before yesterday, and I could, or many more, make this mistake and could go wrong even more than just a soft brick on the phone

delete logical is not necessary. all gsi i have installed go up without do this. if you delete the patition even if uncessary, sure cold cause issues. use your brains and read the guides

Hi friends,
I just tried to flash my Redmi Note 10 5G and my phone freezes on "fastboost" every time it boots.
I tried to flash 2 "Phhusson" files:
- system-squeak-arm64-ab-vndklite-vanilla.img.xz
- system-squeak-arm64-ab-vndklite-gogapps-secure.img.xz
(same fastboot problem on startup with the 2 files)
I tried a "wipe data" in recovery mode.
If you have a solution to find my phone?
Thank you in advance for your help.
Here are the commands I sent:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 12.976s
fastboot erase system
Erasing 'system_a' OKAY [ 0.085s]
Finished. Total time: 0.116s
fastboot -w
Erasing 'userdata' OKAY [ 2.083s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 227016640 (110847 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 1d000 0 200 at offset 0x00118784
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d601, 0001d602
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118785
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d603, 0001d604
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118786
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0001d600
Info: Overprovision ratio = 0.600%
Info: Overprovision segments = 670 (GC reserved = 341)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.000s]
Writing 'userdata' OKAY [ 0.501s]
Erasing 'metadata' OKAY [ 0.016s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 8192 4k blocks and 8192 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.007s]
Writing 'metadata' OKAY [ 0.000s]
Finished. Total time: 3.717s
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.053s
fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 1/11 (261709 KB) OKAY [ 9.121s]
Writing 'system_a' OKAY [ 1.203s]
Sending sparse 'system_a' 2/11 (262124 KB) OKAY [ 8.905s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 3/11 (262116 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.024s]
Sending sparse 'system_a' 4/11 (262124 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 5/11 (262128 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 6/11 (262116 KB) OKAY [ 8.820s]
Writing 'system_a' OKAY [ 1.165s]
Sending sparse 'system_a' 7/11 (262124 KB) OKAY [ 8.874s]
Writing 'system_a' OKAY [ 1.187s]
Sending sparse 'system_a' 8/11 (259235 KB) OKAY [ 8.783s]
Writing 'system_a' OKAY [ 1.056s]
Sending sparse 'system_a' 9/11 (260056 KB) OKAY [ 8.767s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 10/11 (258520 KB) OKAY [ 8.635s]
Writing 'system_a' OKAY [ 1.065s]
Sending sparse 'system_a' 11/11 (23178 KB) OKAY [ 0.902s]
Writing 'system_a' OKAY [ 0.254s]
Finished. Total time: 109.991s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s

Glucksnip said:
Hi friends,
I just tried to flash my Redmi Note 10 5G and my phone freezes on "fastboost" every time it boots.
I tried to flash 2 "Phhusson" files:
- system-squeak-arm64-ab-vndklite-vanilla.img.xz
- system-squeak-arm64-ab-vndklite-gogapps-secure.img.xz
(same fastboot problem on startup with the 2 files)
I tried a "wipe data" in recovery mode.
If you have a solution to find my phone?
Thank you in advance for your help.
Here are the commands I sent:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 12.976s
fastboot erase system
Erasing 'system_a' OKAY [ 0.085s]
Finished. Total time: 0.116s
fastboot -w
Erasing 'userdata' OKAY [ 2.083s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 227016640 (110847 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 1d000 0 200 at offset 0x00118784
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d601, 0001d602
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118785
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d603, 0001d604
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118786
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0001d600
Info: Overprovision ratio = 0.600%
Info: Overprovision segments = 670 (GC reserved = 341)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.000s]
Writing 'userdata' OKAY [ 0.501s]
Erasing 'metadata' OKAY [ 0.016s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 8192 4k blocks and 8192 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.007s]
Writing 'metadata' OKAY [ 0.000s]
Finished. Total time: 3.717s
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.053s
fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 1/11 (261709 KB) OKAY [ 9.121s]
Writing 'system_a' OKAY [ 1.203s]
Sending sparse 'system_a' 2/11 (262124 KB) OKAY [ 8.905s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 3/11 (262116 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.024s]
Sending sparse 'system_a' 4/11 (262124 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 5/11 (262128 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 6/11 (262116 KB) OKAY [ 8.820s]
Writing 'system_a' OKAY [ 1.165s]
Sending sparse 'system_a' 7/11 (262124 KB) OKAY [ 8.874s]
Writing 'system_a' OKAY [ 1.187s]
Sending sparse 'system_a' 8/11 (259235 KB) OKAY [ 8.783s]
Writing 'system_a' OKAY [ 1.056s]
Sending sparse 'system_a' 9/11 (260056 KB) OKAY [ 8.767s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 10/11 (258520 KB) OKAY [ 8.635s]
Writing 'system_a' OKAY [ 1.065s]
Sending sparse 'system_a' 11/11 (23178 KB) OKAY [ 0.902s]
Writing 'system_a' OKAY [ 0.254s]
Finished. Total time: 109.991s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Click to expand...
Click to collapse
You used vndklite. Thats the problem.
The redmi note 10 5g doesnt has VNDK LITE Treble, only Treble VNDK version 31.0
Check:
{
"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"
}
Please check any ROM carefully that its not "vndklite" after the ROM variant (bgN-vndklite), if theres no variant information, check if it says "arm64-ab" with no vndklite and you are good to go.
Some vndklite systems are only for A slots, others are for a/b, but that doesnt solve the problem as the Redmi doesnt include vndklite treble.

1lopes said:
You used vndklite. Thats the problem.
The redmi note 10 5g doesnt has VNDK LITE Treble, only Treble VNDK version 31.0
Check:View attachment 5668855
Please check any ROM carefully that its not "vndklite" after the ROM variant (bgN-vndklite), if theres no variant information, check if it says "arm64-ab" with no vndklite and you are good to go.
Some vndklite systems are only for A slots, others are for a/b, but that doesnt solve the problem as the Redmi doesnt include vndklite treble.
Click to expand...
Click to collapse
I have unzipped the img file: "fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img"
I chose this file because on the first post of this conversation @toonTT says: "I personally used phusson android 12 gsi (system-squeak-arm64-ab-vndklite-vanilla-secure)"

Glucksnip said:
I have unzipped the img file: "fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img"
I chose this file because on the first post of this conversation @toonTT says: "I personally used phusson android 12 gsi (system-squeak-arm64-ab-vndklite-vanilla-secure)"
Click to expand...
Click to collapse
Thats the problem, Redmi Note 10 5G doesn't support vndklite. Use a ROM that is "arm64-ab" and is not intended for devices with vndklite.

1lopes said:
Thats the problem, Redmi Note 10 5G doesn't support vndklite. Use a ROM that is "arm64-ab" and is not intended for devices with vndklite.
Click to expand...
Click to collapse
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...

Glucksnip said:
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...
Click to expand...
Click to collapse
Private message me please, i will try to help you there, and so sorry for the wait and inactivity.

1lopes said:
Private message me please, i will try to help you there, and so sorry for the wait and inactivity.
Click to expand...
Click to collapse
No problem we have a life outside the internet ;-)
It's good I managed to recover my phone using a really cool application "XiaomiTool2" it fixed my phone in a few clicks, too strong !!
it installed miui 13 Global_V13.0.2.0.SKSEUXM
Thanks for the help ;-)

Glucksnip said:
No problem we have a life outside the internet ;-)
It's good I managed to recover my phone using a really cool application "XiaomiTool2" it fixed my phone in a few clicks, too strong !!
it installed miui 13 Global_V13.0.2.0.SKSEUXM
Thanks for the help ;-)
Click to expand...
Click to collapse
Im glad it worked. Sorry that I couldnt help you, but atleast you got it working againIf you need any help you can contact anyone here or me

Glucksnip said:
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...
Click to expand...
Click to collapse
In my experience, I flash MIUI 12.2 first before flash the GSI and voila it works.
If I flash GSI from MIUI 12.5 or 13, it always boot into fastboot after clear data in recovery mode.
Hope it answer your question

Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?

ThinkIt12 said:
Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?
Click to expand...
Click to collapse
Nope, since there's not even a official TWRP (but a unofficial one) for both of the devices here or a guide in this forum. Try checking a youtube video.

ThinkIt12 said:
Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?
Click to expand...
Click to collapse
flash without twrp, using fastboot commands.. is easy, safe and better than twrp (actually touch dont work, need otg cable)

How To Guide [STABLE/STOCK/GSI - Android 13] Redmi Note 10 5G (camellian) + Magisk (NO TWRP)

How to flash Google/Pixel Stock Stable Android 13 on Xiaomi Redmi Note 10 5G (in my case camellian) from any MIUI or any GSI rom without custom recoveries:
Download stock (original/unmodified) boot.img from your current MIUI Version
Download LATEST platform-tools (ADB + FASTBOOT) from Google
Download Magisk (in my case Alpha version works best on newer Androids)
Download Android 13 (stable) GSI (ARM64+GMS - Gapps version) from Google:
-- ARM64 without GMS (Gapps) also works, but upon installing Gapps manually I've gotten Bootloops (I tried serveral versions & Magisk Flashable too)
-- After downloading the GSI, extract system.img (you will be flashing this image) and vbmeta.img (and this image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Place stock boot.img with downloaded system.img and vbmeta.img in the platform-tools folder
Run CMD in platform-tools folder (by typing CMD in address bar and hitting ENTER) and connect your phone (OFC enable USB debugging)
Run following adb / fastboot commands:
Boot phone in fastbootD (important)
Code:
C:\adb\platform-tools>adb reboot bootloader
C:\adb\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Finished. Total time: 12.820s
When booted in fastbootD run:
Code:
C:\adb\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.022s]
Finished. Total time: 0.028s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.006s]
Finished. Total time: 0.050s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.044s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.043s
C:\adb\platform-tools>fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.014s]
Sending sparse 'system_a' 1/12 (262108 KB) OKAY [ 10.316s]
Writing 'system_a' OKAY [ 1.183s]
Sending sparse 'system_a' 2/12 (262120 KB) OKAY [ 10.677s]
Writing 'system_a' OKAY [ 1.087s]
Sending sparse 'system_a' 3/12 (262104 KB) OKAY [ 10.270s]
Writing 'system_a' OKAY [ 0.953s]
Sending sparse 'system_a' 4/12 (262124 KB) OKAY [ 10.131s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 5/12 (262124 KB) OKAY [ 10.749s]
Writing 'system_a' OKAY [ 1.083s]
Sending sparse 'system_a' 6/12 (262124 KB) OKAY [ 11.126s]
Writing 'system_a' OKAY [ 1.082s]
Sending sparse 'system_a' 7/12 (262124 KB) OKAY [ 10.528s]
Writing 'system_a' OKAY [ 1.045s]
Sending sparse 'system_a' 8/12 (262128 KB) OKAY [ 10.397s]
Writing 'system_a' OKAY [ 0.947s]
Sending sparse 'system_a' 9/12 (262088 KB) OKAY [ 10.333s]
Writing 'system_a' OKAY [ 1.207s]
Sending sparse 'system_a' 10/12 (262120 KB) OKAY [ 10.717s]
Writing 'system_a' OKAY [ 1.027s]
Sending sparse 'system_a' 11/12 (243488 KB) OKAY [ 9.380s]
Writing 'system_a' OKAY [ 1.433s]
Sending sparse 'system_a' 12/12 (46444 KB) OKAY [ 1.797s]
Writing 'system_a' OKAY [ 0.336s]
Finished. Total time: 139.687s
C:\adb\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.486s]
Writing 'boot_a' OKAY [ 0.337s]
Finished. Total time: 2.858s
C:\adb\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.340s]
Writing 'boot_a' OKAY [ 0.314s]
Finished. Total time: 2.690s
C:\adb\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (65536 KB) OKAY [ 2.321s]
Writing 'boot_b' OKAY [ 0.317s]
Finished. Total time: 2.671s
Now Reboot to Recovery and WIPE DATA
Code:
C:\adb\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.007s
Reboot and done!
My opinion after one day:
If u like alot of customization it's not for you, you have to install even most basic apps let it's completly stock. But battery life is improved by 35-50% !! I'm using it for over 15 hours and still 30% battery left. Google Cam works great. Performance amazing. Few bugs here and there in the UI but overall pretty stable.
Anyway not a daily driver for everyone yet, needs a bit more polish. Enjoy !!

This looks good. Will it work for camellia?
If u like alot of customization it's not for you, you have to install even most basic apps let it's completly stock.
Click to expand...
Click to collapse
That's the reason I'm still on MIUI. Small things like network speed in status bar is very important to me.

sajalkmr said:
This looks good. Will it work for camellia?
That's the reason I'm still on MIUI. Small things like network speed in status bar is very important to me.
Click to expand...
Click to collapse
I am not sure as I don't have one to test it on, but I don't see why it wouldn't; all other GSI's work so. .
Have in mind that it looks good because of the Lawnchair Launcher (god bless the developer of it, i'm using it over 5 years), otherwise you will get the most basic stock functional android quickstep launcher.

Nice wallpaper. Can you share where I can find it?

iijul said:
Nice wallpaper. Can you share where I can find it?
Click to expand...
Click to collapse
Reddit - Dive into anything
www.reddit.com

iijul said:
Nice wallpaper. Can you share where I can find it?
Click to expand...
Click to collapse
Credit to Mia

What about NFC and Bluetooth working or not?

Kubusi3kk said:
What about NFC and Bluetooth working or not?
Click to expand...
Click to collapse
Yep

Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks

doesnt work cannot make calls

NewXiaomiUser said:
Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks
Click to expand...
Click to collapse
im having the same problem, can you link me a guide to installing los 19.1?

log:
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot devices
dafi8dfurkmz9dau fastboot
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.008s]
Finished. Total time: 0.009s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.130s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_ "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Sending 'vbmeta_' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_ "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Sending 'vbmeta_' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_a "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.013s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_b "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.013s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash system "H:\platform-tools_r33.0.3-windows\platform-tools\system.img"
Resizing 'system_a' OKAY [ 0.010s]
Sending sparse 'system_a' 1/12 (262112 KB) OKAY [ 10.126s]
Writing 'system_a' OKAY [ 1.159s]
Sending sparse 'system_a' 2/12 (262120 KB) OKAY [ 9.476s]
Writing 'system_a' OKAY [ 1.118s]
Sending sparse 'system_a' 3/12 (262112 KB) OKAY [ 9.404s]
Writing 'system_a' OKAY [ 1.213s]
Sending sparse 'system_a' 4/12 (262124 KB) OKAY [ 10.100s]
Writing 'system_a' OKAY [ 1.080s]
Sending sparse 'system_a' 5/12 (262128 KB) OKAY [ 9.308s]
Writing 'system_a' OKAY [ 1.295s]
Sending sparse 'system_a' 6/12 (262124 KB) OKAY [ 9.395s]
Writing 'system_a' OKAY [ 1.147s]
Sending sparse 'system_a' 7/12 (262128 KB) OKAY [ 9.416s]
Writing 'system_a' OKAY [ 1.049s]
Sending sparse 'system_a' 8/12 (262120 KB) OKAY [ 9.430s]
Writing 'system_a' OKAY [ 1.260s]
Sending sparse 'system_a' 9/12 (262088 KB) OKAY [ 10.616s]
Writing 'system_a' OKAY [ 1.113s]
Sending sparse 'system_a' 10/12 (262120 KB) OKAY [ 9.648s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 11/12 (260716 KB) OKAY [ 9.342s]
Writing 'system_a' OKAY [ 1.360s]
Sending sparse 'system_a' 12/12 (46712 KB) OKAY [ 1.690s]
Writing 'system_a' OKAY [ 0.308s]
Finished. Total time: 196.646s
H:\platform-tools_r33.0.3-windows\platform-tools>
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.401s]
Writing 'boot_a' OKAY [ 0.316s]
Finished. Total time: 2.746s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_a "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.414s]
Writing 'boot_a' OKAY [ 0.308s]
Finished. Total time: 2.747s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_b "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_b' (65536 KB) OKAY [ 2.429s]
Writing 'boot_b' OKAY [ 0.309s]
Finished. Total time: 2.764s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.002s
H:\platform-tools_r33.0.3-windows\platform-tools>

Hi TedFin,
sure, here is how I flash back LineageOS 19.1:
First of all, I assume you have the ADB and fastboot drivers installed, you can find guides here and there.
Download LineageOS here:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.img.xz/download
Download stock firmware here:
https://xiaomifirmwareupdater.com/miui/camellian/stable/V13.0.3.0.SKSEUXM/ (choose Fastboot rom)
Extract the Xiaomi stock firware using 7zip or any other compatible software
Reboot your phone in fastboot mode (long press on volume down while booting)
Open a command prompt on the extracted folder and run
Bash:
flash_all.bat
Once completed, your phone should be back on stock rom
Reboot once again in fastboot mode
Then in cmd:
Go to the LineageOS folder
Bash:
cd /d [the folder where you decompressed lineageos]
Reboot in fastbootd
Bash:
fastboot reboot fastboot
Flash LineageOS
Bash:
fastboot flash system lineage-19.1-20220912-UNOFFICIAL-arm64_bgS.img
fastboot flash system_b lineage-19.1-20220912-UNOFFICIAL-arm64_bgS.img
Clean up
Bash:
fastboot reboot recovery
Wipe all then reboot
If you have a boot loop, reboot in Fastboot
Bash:
fastboot flash boot [the stock rom folder]\images\boot.img
fastboot flash boot_b [the stock rom folder]\images\boot.img
Voila!

NewXiaomiUser said:
Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks
Click to expand...
Click to collapse
Do you wipe data at the end before reboot?

Hi, thanks for your response,
yes I did it, I also restore the stock firmware before but it does not change anything

NewXiaomiUser said:
Hi, thanks for your response,
yes I did it, I also restore the stock firmware before but it does not change anything
Click to expand...
Click to collapse
try nother gsi. a question: what stock firmware u have installed? i must start from miui13 because have a12 vendor
second. check the active slot. gsi must be installed into primary
third: flash system without erase system partition
forth: reflash boot stock img before reboot
if your phone dont boot and stuck on logo the problem is boot.img or active slot
if your phone boot into recovery wipe data
the bootloops after flashing gsi are caused by boot.img or data that must be wiped
another thing: FLASH VBMETA DISABLING SECURE VERITY CHECK before reboot
the steps for flash gsi are simply. slect the correct gsi and start from the correct stock is important. mut most important is use your brain. i have flashed at lest 5-6 gsi without problems

Hi,
1. Here is the stock ROM I'm using: camellian_eea_global V13.0.2.0 (SKSEUXM)
2. Active slot is A (anyway, I always flash A and B)
3. System partition is erased when flash stock rom. I do not flash after stock
4. I always flash boot (both A and B) after flashing a GSI, tried with stock boot.img and Magisk's
5. After installing a GSI, I always wipe all data in recovery mode
6. flashing vbmeta is part of your process and, of course, I followed it step by step
The phone is not stuck on logo, it just keep restarting again and again without reaching the OS itself (no boot animation)
By the way, I'm able to flash LineageOS or Pixel Experience using the same procedure works without any quirks, this is the only GSI I'm having problem with.
Thanks

NewXiaomiUser said:
Hi,
1. Here is the stock ROM I'm using: camellian_eea_global V13.0.2.0 (SKSEUXM)
2. Active slot is A (anyway, I always flash A and B)
3. System partition is erased when flash stock rom. I do not flash after stock
4. I always flash boot (both A and B) after flashing a GSI, tried with stock boot.img and Magisk's
5. After installing a GSI, I always wipe all data in recovery mode
6. flashing vbmeta is part of your process and, of course, I followed it step by step
The phone is not stuck on logo, it just keep restarting again and again without reaching the OS itself (no boot animation)
By the way, I'm able to flash LineageOS or Pixel Experience using the same procedure works without any quirks, this is the only GSI I'm having problem with.
Thanks
Click to expand...
Click to collapse
I'll try to give you files and help you when I get on my PC today

Sure, no rush, anyway, LOS is pretty stable except I cannot bypass SafetyNet.
Thanks

NewXiaomiUser said:
Sure, no rush, anyway, LOS is pretty stable except I cannot bypass SafetyNet.
Thanks
Click to expand...
Click to collapse
Sorry I forgot about my post, I'll do it now... As for the Safety Net I highly recommend using Alpha (not official) build of Magisk (pay attention to other builds such as Delta and similar "Alpha" builds everywhere; this Telegram Group link is the one and only trusted place where you can find download link-I'll attach latest version down bellow). Every single problem I had with either stock or modified roms; I solved them when I started using it (except when I overdo it with modules which would be my mistake ofc.). The biggest difference is that it is closed-sourced so there is a risk when using it, but it's being maintained by one of the respected people that worked/works on official Magisk.
Next step is of course installing Universal SafetyNet Fix by kdrag0n.
And finally MagiskHide Props Config By Didgeridoohan. After flashing this one you will have to set it up with any terminal (Termux for example) to spoof your device config so the store thinks you're using - in my case Google Pixel 6 Pro. Also in my case the feature "device emulator - 3rd from above" gave me soft brick so be careful. It's easy to set it up as it guides you via terminal (I use first two options and spoofing as Pixel 6 Pro as I said).
Those things are first things I do on a new rom, and yeah I use LSPosed Framework + Zygisk.
No problems and I'm certified in Google Play/Google Games stores even tho I use modified apks to hack multiplayer games.
I'll go and give you all the files so u can try latest generic GSI by Google if you still want, using this guide.