Develop Bugs

Unlock Bootloader on Android 5.1.1 A5CN701?

I've been trying to unlock the bootloader since the A5CN701 update. Here's how i've tried:
1. Go to developer options -> Tick OEM Unlocking
2. Use the launcher.bat from IntelAndroid-FBRL-05-16-2015.7z from this topic http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
3. Use the T4 option and the tablet ends up like this (because the bootloader is locked):
{
"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"
}
4. Use fastboot and enter this code:
Code:
fastboot oem unlock
Then the cmd console and the tablet should look like this:
5. Select ''Yes: change device state'' using the UI on the N1 but here's all i've received:
The result is :''Fail: couldn't change state''
So that's pretty much about how i've tried to unlock the bootloader. I don't know why i couldn't change the device state! Is there anyone that can help me?
I posted this topic so that everyone can join and make suggestions & solutions to rooting the A5CN701 firmware!
Any help would be much appreciated!
P/s: sorry for the sloppy photos, i didn't have time to crop and edit them

it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.

乄Rain丶Man said:
it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.
Click to expand...
Click to collapse
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out

When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.

Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
you reboot into the Temporary CWM success?

Xkernels said:
you reboot into the Temporary CWM success?
Click to expand...
Click to collapse
Yes

Drivknuten said:
Yes
Click to expand...
Click to collapse
please, you could post your image?

colorado48 said:
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out
Click to expand...
Click to collapse
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
p233 said:
please, you could post your image?
Click to expand...
Click to collapse
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.

乄Rain丶Man said:
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.
Click to expand...
Click to collapse
Here is the original old version download link
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529 #3

p233 said:
please, you could post your image?
Click to expand...
Click to collapse
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
乄Rain丶Man said:
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
Click to expand...
Click to collapse
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.

Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
2.adb reboot bootloader?
can you provide some pic?

Xkernels said:
2.adb reboot bootloader?
can you provide some pic?
Click to expand...
Click to collapse
Yes that should be adb reboot bootloader.
NO pics possible, my device is in a bootloop and i dont have the time to fix the device until the weekend.

Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks

pdt100 said:
Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks
Click to expand...
Click to collapse
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update

Drivknuten said:
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update
Click to expand...
Click to collapse
Hi, i was able to submit the command successfully however no change unfortunately. any other ideas? thanks

Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
Then did you root your device successfully？or did you rollback to old version？

乄Rain丶Man said:
Then did you root your device successfully？or did you rollback to old version？
Click to expand...
Click to collapse
Nah i bricked it,

the same thing to me, after i relock bootloader, it jump into a big problem: bootloop, whenever i turn on devices, it just show "android" screen

It's been a while now, can anybody confirm that a root for A5CN701 is on the way?

Drivknuten said:
Nah i bricked it,
Click to expand...
Click to collapse
Oflyt...

Pixel C - fastboot unsupported command

Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !

Did you unlock your device first with "fastboot oem unlock"?

redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS

I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.

-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.

Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !

@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html

peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?

viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.

peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse

viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.

rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.

viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?

mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.

did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command

richardwia said:
did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.

viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really？where I can find the“fix fastboot in advanced options”？

richardwia said:
really？where I can find the“fix fastboot in advanced options”？
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.

I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.

I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...

FastbootD mode

i'm on stock 10.0.12 firmware using r30.0.4 platform tools. when i'm in bootloader mode and type fastboot reboot fastboot i get just fastboot help:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools>
how can i enter fastbootD mode?

To enter in fastbootd you need the newest platforn-tools aka adb and fastboot files
When you got that you reboot to bootloader(fastboot mode) and then use the fastbootd
Just use google tobsearch for fastbootd op7t
---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------
Or look closely here
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
It gives link to latest platfom-tools

Makerrr said:
To enter in fastbootd you need the newest platforn-tools aka adb and fastboot files
When you got that you reboot to bootloader(fastboot mode) and then use the fastbootd
Just use google tobsearch for fastbootd op7t
---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------
Or look closely here
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
It gives link to latest platfom-tools[/QUOTE
thanks for your reply but i think that platform tools r30.0.4 is the newest platform tools. if u know abt newest one and be kind enough to give the link i'll be more than grateful
Click to expand...
Click to collapse

That's the latest one.
You should be able to boot fastbootd!
When in fastboot mode run fastboot reboot fastbootd
And your device should reboot in a stock recovery looking environment, that's fastbootd

Makerrr said:
That's the latest one.
You should be able to boot fastbootd!
When in fastboot mode run fastboot reboot fastbootd
And your device should reboot in a stock recovery looking environment, that's fastbootd
Click to expand...
Click to collapse
maybe it should but it doesn't. that's how my problem started.

altojd said:
maybe it should but it doesn't. that's how my problem started.
Click to expand...
Click to collapse
Execute command with .exe once you're in the folder like fastboot.exe reboot fastboot

Lossyx said:
Execute command with .exe once you're in the folder like fastboot.exe reboot fastboot
Click to expand...
Click to collapse
did it and nothing has changed. the problem remains

have you found a solution to this? i am unable to get onto fastbootd mode
C:\platform-tools>adb reboot fastboot
C:\platform-tools>fastboot getvar is-userspace
is-userspace: no
Finished. Total time: 0.009s

I'm having a similar problem: I can get into fastbootd (chinese/english menu), but I can't send any fastboot commands, it always just says "waiting for device" and 'fastboot devices' shows nothing. If I try to flash things half will fail with "partition not found" because I can only flash in fastboot, not fastbootd. Once flashed I only get bootloader booting message and then it crashes into Qualcomm CrashDump mode and all I can do is wait and then hours later it's magically back to fastbootd but still can't send commands to it, even though OnePlus_USB_Drivers_Setup.exe is installed. Any ideas??

I had issues until used the all in one tool to flash it, then it worked perfect.

thetoady said:
I had issues until used the all in one tool to flash it, then it worked perfect.
Click to expand...
Click to collapse
is fastbootd any good? i tried to use fastboot devices and getvar all command but does not do anything this on lg v60

altojd said:
i'm on stock 10.0.12 firmware using r30.0.4 platform tools. when i'm in bootloader mode and type fastboot reboot fastboot i get just fastboot help:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools>
how can i enter fastbootD mode?
Click to expand...
Click to collapse
Reflash stock recovery, then fastboot reboot fastboot to get into fastbootd

HueyT said:
Reflash stock recovery, then fastboot reboot fastboot to get into fastbootd
Click to expand...
Click to collapse
where is stock recovery?

can someone explain me the use for fastbootd, in my case i seem to have regular fastboot and fastbootd. in fastbootd i cant execute any commands. its completely new to me and i havent found any proper documentation or tutorials going in depth with it so its all just going over my head.

HueyT said:
Reflash stock recovery, then fastboot reboot fastboot to get into fastbootd
Click to expand...
Click to collapse
I'd be surprised if reflashing the stock recovery magically fixed the problem.

Makerrr said:
That's the latest one.
You should be able to boot fastbootd!
When in fastboot mode run fastboot reboot fastbootd
And your device should reboot in a stock recovery looking environment, that's fastbootd
Click to expand...
Click to collapse
i have installed twrp recovery so am i able to go in fastbootd mode?

FakeGemstone said:
I'd be surprised if reflashing the stock recovery magically fixed the problem.
Click to expand...
Click to collapse
fastbootd is apart of recovery on many devices.
"The bootloader is expected to load and boot into the recovery image upon seeing boot-fastboot in the BCB command. Recovery then parses the BCB message and switches to fastbootd mode."

shaniKhan0 said:
i have installed twrp recovery so am i able to go in fastbootd mode?
Click to expand...
Click to collapse
If your TWRP is newer then you can still enter fastboot from TWRP, on my device using "adb reboot fastboot" will reboot my device into TWRP then enter some weird TWRP fastboot mode. However windows doesn't seem to detect that this is a device in ADB/Fastboot mode and won't load drivers so if you're on windows you'd have to enter device manager, browse for drivers, "let me pick from all available drivers" find google inc (Assuming you already have those drivers) and select android debugging interface drivers and install. After that your device should work just fine and "getvar is-userspace" should return "yes"

Brandon.Bissonnette said:
If your TWRP is newer then you can still enter fastboot from TWRP, on my device using "adb reboot fastboot" will reboot my device into TWRP then enter some weird TWRP fastboot mode. However windows doesn't seem to detect that this is a device in ADB/Fastboot mode and won't load drivers so if you're on windows you'd have to enter device manager, browse for drivers, "let me pick from all available drivers" find google inc (Assuming you already have those drivers) and select android debugging interface drivers and install. After that your device should work just fine and "getvar is-userspace" should return "yes"
Click to expand...
Click to collapse
not working....facing same problem . on oneplus 8T. can you suggest something

Question [help] Global Stock doesn't boot up. Hopefully soft-bricked it?

I've got my POCO F3 global for 4 months or so and unlocked the bootloader to install a custom ROM.
Since then I've installed Pixel Extended (stayed with it for 2 months or so) and then installed crDroid. I experienced a lot of random reboots since then which I thought could be a rom install problem or something like that so I clean flashed arrow OS but the device wouldn't boot up at all. So I downloaded fastboot stock V12.5.2.0.RKHMIXM GLOBAL (which is as of now the latest stable for Global version) but the device would always bootloop and eventually go to fastboot mode. I tried reflashing it several times and even flashing a previous version of the GLOBAL V12.0.2.0.RKHMIXM and it just doesn't boot the system up - it just bootloops and eventually falls into fastboot mode. I've learned that when I have just flashed it, I'm even able to go POWER + VOL(+) to go to Mi recovery (and even tried to wipe all data from there hoping it would make a difference). But if I let it try boot the system, after it goes to fastboot mode once, I can never access the recovery again.
I'm currently able to boot TWRP, and flash any ROM on top of this non booting stock image and sometimes it does boot up the first time but if I try to flash anything on top of it like opengapps it just fails to boot up ever again. I must say that even after I flash crDroid, it bootloops a lot of time before crDroid logo appears.
So my problem is that for the last 3 weeks or so I'm not able to boot up stock flashed on fastboot and if I flash any custom ROM on top of it it is completely bugged out (random reboots, can't flash gapps, bootloops 10 times before loading the ROM when restarting the phone). I don't know if I somehow messed up any partitions or if there's any problem with my actual hardware that may be causing this. By the way I've been using TWRP-3.5.1-alioth-Nebrassy-2 for flashing and latest platform tools for adb and fastboot (31.0.3). And also, I've been using the usb c cable that came with the device connected to a usb 2.0 hub.
I have the impression that if I'm able to flash stock appropriately and boot it up it might fix the problem but I could be wrong. Also, it's the first time that I flash an A/B device which sometimes gets me confused about the slots.
I've been flashing my android devices since 2010 (Motorola Quench was my first android device) and I've always had to read the forums but I never encountered a problem I couldn't just fix it by returrning to stock or wiping it.

Welcome to the forum mate.
Did you flash the Global Fastboot Stock ROM using Mi Flash? I'd recommend it, instead of using the .BAT files directly.
After it's done, it should automatically boot you into System.

dreamytom said:
Welcome to the forum mate.
Did you flash the Global Fastboot Stock ROM using Mi Flash? I'd recommend it, instead of using the .BAT files directly.
After it's done, it should automatically boot you into System.
Click to expand...
Click to collapse
Thank you for a prompt response, @dreamytom
I think I've used that but of course I'll try it again. I'm downloading MiFlash20210226 (latest as of now).
Should I check clean all before flashing it?

chrisparkerrr said:
Thank you for a prompt response, @dreamytom
I think I've used that but of course I'll try it again. I'm downloading MiFlash20210226 (latest as of now).
Should I check clean all before flashing it?
Click to expand...
Click to collapse
Just dont select flash and lock...

I reflashed it using MiFlash the first time and it gave me a crclist flash error.
I proceeded and removed the following 2 lines from flash_all.bat file
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist
I've seen this trick before on other forums and I've never seen it gone badly so I'm trying again without those lines

Rstment ^m^ said:
Just dont select flash and lock...
Click to expand...
Click to collapse
oh, that lesson I learned the hard way in the past. thanks for reminding me of that

After flashing, I got an error on FlashDone step but all previous images seems to be successfully flashed.
It rebooted several times until it ended up on fastboot mode again.
Here's the tail of the log
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename set_active a ||
[1:38:59 PM 9d3839f8]:info2:Setting current slot to 'a' OKAY [ 0.008s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.010s
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename reboot ||
[1:38:59 PM 9d3839f8]:info2:Rebooting OKAY [ 0.000s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.000s
[1:38:59 PM 9d3839f8]:begin FlashDone
[1:38:59 PM 9d3839f8]:errMsg is null
[1:38:59 PM 9d3839f8]:begin checkPoint
[1:38:59 PM 9d3839f8]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[1:38:59 PM 9d3839f8]:process exit.
[1:39:00 PM 9d3839f8]:flashSuccess False
[1:39:00 PM 9d3839f8]:isFactory False CheckCPUID False
[1:39:00 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[1:39:00 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true

chrisparkerrr said:
Thank you for a prompt response, @dreamytom
I think I've used that but of course I'll try it again. I'm downloading MiFlash20210226 (latest as of now).
Should I check clean all before flashing it?
Click to expand...
Click to collapse
Yes definitely check "Clean All" before Flashing.
The default checkmark "Clean All and Lock" will lock your bootloader (which you probably don't want happening).
Let us know how it goes.

dreamytom said:
Yes definitely check "Clean All" before Flashing.
The default checkmark "Clean All and Lock" will lock your bootloader (which you probably don't want happening).
Let us know how it goes.
Click to expand...
Click to collapse
It bootloops 5 or 6 times until it lands on fastboot mode again
(flashing V12.5.2.0.RKHMIXM Global version)
I'm able to enter the MIUI recovery though

chrisparkerrr said:
After flashing, I got an error on FlashDone step but all previous images seems to be successfully flashed.
It rebooted several times until it ended up on fastboot mode again.
Here's the tail of the log
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename set_active a ||
[1:38:59 PM 9d3839f8]:info2:Setting current slot to 'a' OKAY [ 0.008s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.010s
[1:38:59 PM 9d3839f8]:info1:$fastboot -s devicename reboot ||
[1:38:59 PM 9d3839f8]:info2:Rebooting OKAY [ 0.000s]
[1:38:59 PM 9d3839f8]:info2:Finished. Total time: 0.000s
[1:38:59 PM 9d3839f8]:begin FlashDone
[1:38:59 PM 9d3839f8]:errMsg is null
[1:38:59 PM 9d3839f8]:begin checkPoint
[1:38:59 PM 9d3839f8]:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
[1:38:59 PM 9d3839f8]:process exit.
[1:39:00 PM 9d3839f8]:flashSuccess False
[1:39:00 PM 9d3839f8]:isFactory False CheckCPUID False
[1:39:00 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[1:39:00 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
Try the following:
- Disconnect phone from PC and reboot Fastboot Mode (with POWER + Volume Down)
- Close & Re-open Mi Flash
- Connect phone to PC
- Go into Mi Flash's Configuration page:
Remove the text in the picture:
https://www.thecustomdroid.com/wp-content/uploads/2018/01/Fix-Mi-Flash-Tool-Not-Catch-CheckPoint-Error.jpg
- Check "Clean All" in bottom right corner
- Flash

dreamytom said:
Try the following:
- Disconnect phone from PC and reboot Fastboot Mode (with POWER + Volume Down)
- Close & Re-open Mi Flash
- Connect phone to PC
- Go into Mi Flash's Configuration page:
Remove the text in the picture:
https://www.thecustomdroid.com/wp-content/uploads/2018/01/Fix-Mi-Flash-Tool-Not-Catch-CheckPoint-Error.jpg
- Check "Clean All" in bottom right corner
- Flash
Click to expand...
Click to collapse
Now I get a success message on MiFlash but it bootlooped 7 times until it got to fastboot mode again :/

I'm going to flash again with these configs
{
"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"
}
Trying to see if I get more detailed logs or something..

chrisparkerrr said:
Now I get a success message on MiFlash but it bootlooped 7 times until it got to fastboot mode again :/
Click to expand...
Click to collapse
Add the lines into the .BAT script again, that you've removed. This time, try flashing with "Erase All" and "Verbose" enabled in the Mi Flash Configuration-page.
You can also try "check MD5 before Flash" to see if perhaps the ROM is corrupt.
Leave the "CheckPoint" argument removed, that argument is unnecessary.
Keep in mind that you have to disconnect your phone, reboot Fastboot Mode, and re-connect phone to PC.
This is because Fastboot Mode stops receiving any input after an initiated Flash and will result in an error. It may also error out, if you reboot Fastboot Mode while it's already plugged into your PC, for some reason.

dreamytom said:
Add the lines into the .BAT script again, that you've removed. This time, try flashing with "Erase All" and "Verbose" enabled in the Mi Flash Configuration-page.
You can also try "check MD5 before Flash" to see if perhaps the ROM is corrupt.
Leave the "CheckPoint" argument removed, that argument is unnecessary.
Keep in mind that you have to disconnect your phone, reboot Fastboot Mode, and connect phone to PC again.
This is because Fastboot Mode stops receiving any input after an initiated Flash and will result in an error.
Click to expand...
Click to collapse
Will do and report back.

dreamytom said:
Add the lines into the .BAT script again, that you've removed. This time, try flashing with "Erase All" and "Verbose" enabled in the Mi Flash Configuration-page.
You can also try "check MD5 before Flash" to see if perhaps the ROM is corrupt.
Leave the "CheckPoint" argument removed, that argument is unnecessary.
Keep in mind that you have to disconnect your phone, reboot Fastboot Mode, and re-connect phone to PC.
This is because Fastboot Mode stops receiving any input after an initiated Flash and will result in an error. It may also error out, if you reboot Fastboot Mode while it's already plugged into your PC, for some reason.
Click to expand...
Click to collapse
MD5 validation succeeded, put back the CheckPoint argument and checked Verbose and EraseAll.
I just noticed that when I check EraseAll and click OK, next time I open the Configuration menu the EraseAll checkbox is unchecked. I checked it the first time anyways and procceeded with flashing.
This is the tail log:
[2:19:17 PM 9d3839f8]:info2:Sending sparse 'super' 1/9 (722352 KB) OKAY [ 17.075s]
[2:19:17 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:19:54 PM 9d3839f8]:info2:Sending sparse 'super' 2/9 (785380 KB) OKAY [ 36.804s]
[2:19:54 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:20:31 PM 9d3839f8]:info2:Sending sparse 'super' 3/9 (720896 KB) OKAY [ 37.195s]
[2:20:31 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:21:06 PM 9d3839f8]:info2:Sending sparse 'super' 4/9 (766564 KB) OKAY [ 34.844s]
[2:21:06 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.001s]
[2:21:43 PM 9d3839f8]:info2:Sending sparse 'super' 5/9 (744476 KB) OKAY [ 37.345s]
[2:21:43 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.000s]
[2:22:20 PM 9d3839f8]:info2:Sending sparse 'super' 6/9 (768840 KB) OKAY [ 36.824s]
[2:22:20 PM 9d3839f8]:info2:Writing 'super' OKAY [ 0.001s]
[2:22:57 PM 9d3839f8]:info2:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:info2:fastboot: error: Command failed
[2:22:57 PM 9d3839f8]:info1:"Flash super error"
[2:22:57 PM 9d3839f8]:begin FlashDone
[2:22:57 PM 9d3839f8]:error:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:process exit.
[2:22:57 PM 9d3839f8]:flashSuccess False
[2:22:57 PM 9d3839f8]:isFactory False CheckCPUID False
[2:22:57 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[2:22:57 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
This is what was failing before I removed the
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist
lines.

chrisparkerrr said:
...
[2:22:57 PM 9d3839f8]:info2:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]:info2:fastboot: error: Command failed
[2:22:57 PM 9d3839f8]:info1:"Flash super error"
[2:22:57 PM 9d3839f8]:begin FlashDone
[2:22:57 PM 9d3839f8]:error:Sending sparse 'super' 7/9 (727352 KB) FAILED (remote: 'failed to check sparse crc')
[2:22:57 PM 9d3839f8]rocess exit.
[2:22:57 PM 9d3839f8]:flashSuccess False
[2:22:57 PM 9d3839f8]:isFactory False CheckCPUID False
[2:22:57 PM 9d3839f8]:before:flashSuccess is False set IsUpdate:True set IsDone True
[2:22:57 PM 9d3839f8]:after:flashSuccess is False set IsUpdate:false set IsDone true
[/ICODE]
This is what was failing before I removed the
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist
lines.
Click to expand...
Click to collapse
I've seen the error "Failed to check Sparse CRC" quite a few times and had it myself.
Try Rebooting your PC and switching the USB port. You can also try changing the cable.
That doesn't sound like it'd do much, but a dude I've chatted with from here, and myself had this error, and we both succeeded in flashing our ROMs by doing the above. ^
Also make sure the path to your ROM doesn't contain spaces. Mi Flash is stubborn.
I just temporarily put the ROM folder in C:/

Try flashing with this tool.
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
While you have your phone connected to the PC, Select my device is bricked, Choose your phone model from it's list. It will download the stock ROM on itself and flash it. I had gone through the same problem a few months ago when i had the k20 pro. This tool got it sorted out. Give it a try. Goodluck.

dreamytom said:
I've seen the error "Failed to check Sparse CRC" quite a few times and had it myself.
Try Rebooting your PC and switching the USB port. You can also try changing the cable.
That doesn't sound like it'd do much, but a dude I've chatted with from here, and myself had this error, and we both succeeded in flashing our ROMs by doing the above. ^
Also make sure the path to your ROM doesn't contain spaces. Mi Flash is stubborn.
I just temporarily put the ROM folder in C:/
Click to expand...
Click to collapse
Created a folder for the image at C:\mi\ even though my previous folder didn't have any spaces.
Changed the cable and the port (I was using a USB C dock + USB A dongle and now it's directly in the back of my computer)
Result is the same 'failed to check sparse crc'
I'll try different combinations of ports and cables to see if the outcome changes and report back.

Animesh Singh said:
Try flashing with this tool.
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
While you have your phone connected to the PC, Select my device is bricked, Choose your phone model from it's list. It will download the stock ROM on itself and flash it. I had gone through the same problem a few months ago when i had the k20 pro. This tool got it sorted out. Give it a try. Goodluck.
Click to expand...
Click to collapse
Thank you for replying.
I got this tool installed and even tried it in the past weeks. It downloaded the fastboot ROM again but I had the same problems as mentioned above. I'll try it again soon.

chrisparkerrr said:
Created a folder for the image at C:\mi\ even though my previous folder didn't have any spaces.
Changed the cable and the port (I was using a USB C dock + USB A dongle and now it's directly in the back of my computer)
Result is the same 'failed to check sparse crc'
I'll try different combinations of ports and cables to see if the outcome changes and report back.
Click to expand...
Click to collapse
That sucks. Try EU ROM (or if you're not in the EU, your specific region), instead of Global.
I don't know how on earth that would make a difference, but just to see...

How To Guide RMX3363 : unlock bootloader + root + install LOS recovery & custom ROM

Because really, a Realme GT ME is a killer with an AOSP ROM...
- - - - - - - - WARRANTY VOID IF YOU DO THAT - - - - - - - -​
(Use original charger cable to connect phone to PC)
Download : ADB/fastboot, Deep Test apk, Magisk apk/zip 25.2, LOS (Lineage OS) recovery, custom ROM zip and GAPPS zip (if needed by your custom ROM)
Update phone by OTA for Android 12 RUI3 Export (french network for me)
Check options in developer menu (USB debugging/OEM unlock)
Install and launch the Deep Test apk
Restart phone into fastboot mode (power + volume down)
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot flashing unlock
Unlock bootloader on phone
Restart phone
Download firmware RMX3363export_11_C.08_2022062322020000.ofp
Extract boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img with ofp_qc_decrypt.py (Github Python3 script)
Install and launch Magisk apk
Copy extracted boot.img and vendor_boot.img on phone
Patch files with Magisk
Copy patched files on PC
Restart phone into fastboot mode
Choose "Recovery mode" and wipe data
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Type CMD : fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
Type CMD : fastboot --set-slot=all flash boot patched-boot.img
Type CMD : fastboot --set-slot=all flash vendor_boot patched-vendor_boot.img
Restart phone (rooted)
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --set-slot=all flash boot LOS-recovery_boot.img
Type CMD : fastboot --set-slot=all flash vendor_boot LOS-recovery_vendor_boot.img
Type CMD : fastboot reboot recovery
Format DATA (factory reset) into LOS recovery
Launch ADB sideload into LOS recovery (and note active slot)
Type CMD on PC : adb devices (phone must be detected)
Type CMD : adb sideload <custom ROM>.zip
Relaunch ADB sideload into LOS recovery
Type CMD : adb sideload <GAPPS>.zip
Restart phone into fastboot mode
Type CMD on PC : fastboot devices (phone must be detected)
Type CMD : fastboot --set-active=<x> (a or b, depend of active slot at step 31)
Type CMD : fastboot reboot recovery
Launch ADB sideload into LOS recovery
Type CMD on PC : adb devices (phone must be detected)
Type CMD : adb sideload <custom ROM>.zip
Relaunch ADB sideload into LOS recovery
Type CMD : adb sideload <GAPPS>.zip
Restart phone
Welcome to your custom ROM !
(Perhaps you'll have, like me, to apply Magisk.zip in recovery mode to be definitively rooted)

After tested official ElixirOS and unofficial LineageOS, I prefer the second. So for me :
- lineageos-19.1-20220823-unofficial
- NikGapps-full-arm64-12-20220904-signed
- AGC8.4.300_V9.2_fix2
{
"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"
}
Animated notification's background (with LSPosed module) :

Where can I get a supported Depth Test app? Because I have tried all the depth test apps but they don't work..

Bungaza said:
Where can I get a supported Depth Test app? Because I have tried all the depth test apps but they don't work..
Click to expand...
Click to collapse
I'm sorry. This one works for mine :
https://androidfilehost.com/?fid=14655340768118457493

Hello,
Thanks for your simple guide, it worked for me!

enonaw said:
I'm sorry. This one works for mine :
https://androidfilehost.com/?fid=14655340768118457493
Click to expand...
Click to collapse
Not work

Bungaza said:
Not work
Click to expand...
Click to collapse
Do you have C08 export firmware ?

enonaw said:
Do you have C08 export firmware ?
Click to expand...
Click to collapse
I don't have

Amazing guide!

Bungaza said:
I don't have
Click to expand...
Click to collapse
Ok, so I'm sorry, I can't help you because this guide is for C08_Export...

enonaw said:
Ok, so I'm sorry, I can't help you because this guide is for C08_Export...
Click to expand...
Click to collapse
You're talking about C08 Export while my device doesn't support deep test apk. Unless you're talking about how to get into fastboot mode. I was able to get the export C08 firmware through a google search.

You should add in the guide the fact that if you are going to use Magisk on the custom rom you need to patch the boot.img and the vendor_boot.img of the specific rom extracted using payload-dumper-go tool

Bungaza said:
You're talking about C08 Export while my device doesn't support deep test apk. Unless you're talking about how to get into fastboot mode. I was able to get the export C08 firmware through a google search.
Click to expand...
Click to collapse
Hmmm... Ok. But this guide is for C08_export OTA updated smartphone (step 2). So, if you can't do step 2 before the step 4 (deep test), I can't help you.

leoufort said:
You should add in the guide the fact that if you are going to use Magisk on the custom rom you need to patch the boot.img and the vendor_boot.img of the specific rom extracted using payload-dumper-go tool
Click to expand...
Click to collapse
No. Look at "(Perhaps you'll have, like me, to apply Magisk.zip in recovery mode to be definitively rooted)" after the last step. I only did this to be able to use Magisk on custom ROM.

hi enonaw
i download RMX3363export_11_C.08_2022062322020000.ofp but unable to extract ofp file.
can u share here boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img from your pc.
Thnks in advance

ATuthura said:
hi enonaw
i download RMX3363export_11_C.08_2022062322020000.ofp but unable to extract ofp file.
can u share here boot.img, vendor_boot.img, vbmeta.img and vbmeta_vendor.img from your pc.
Thnks in advance
Click to expand...
Click to collapse
Hi, It's not a good idea to share stock img, because files can be altered when upload/download. Why are you unable to extract ofp file ? Did you use ofp_qc_decrypt.py (it works on both linux and windows) ?
ofp_qc_decrypt.py

enonaw said:
Hi, It's not a good idea to share stock img, because files can be altered when upload/download. Why are you unable to extract ofp file ? Did you use ofp_qc_decrypt.py (it works on both linux and windows) ?
ofp_qc_decrypt.py
Click to expand...
Click to collapse
i already tried, i cant. can u help me remotely via team viewer

ATuthura said:
i already tried, i cant. can u help me remotely via team viewer
Click to expand...
Click to collapse
See attached files, that's an archive of patched files by Magisk (password : rmx3363).
But verify the hash of your download before apply
And don't forget that I'm not responsible for what you do.

i am unbale toextract file

dear sir, just try
i face this issue
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
392a6bdd fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disa
ble-verification flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (8 KB)...
OKAY [ 0.002s]
writing 'vbmeta'...
OKAY [ 0.009s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --disable-verity --disa
ble-verification flash vbmeta_vendor vbmeta_vendor.img
target reported max download size of 805306368 bytes
sending 'vbmeta_vendor' (4 KB)...
OKAY [ 0.002s]
writing 'vbmeta_vendor'...
OKAY [ 0.009s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --set-slot=all flash bo
ot patched-boot.img
fastboot: unknown option -- set-slot=all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot --set-slot=all flash ve
ndor_boot patched-vendor_boot.img
fastboot: unknown option -- set-slot=all
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse