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...

[ROM][10][UNOFFICIAL] OmniROM

{
"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"
}
Download :
GApps : https://dl.omnirom.org/tmp/def/
microG : https://dl.omnirom.org/def/
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it).
Get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
You should see a recovery like screen with a red "fastbood" message
Extract payload.bin using payload dumper (google it for tutorials)
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
UPDATE
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram group for One Hyper : https://t.me/MotoOneHyper
XDA:DevDB Information
OmniROM, ROM for the Motorola One Hyper
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-02-02
Created 2020-02-02
Last Updated 2020-08-15

I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?

orimigato said:
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
Click to expand...
Click to collapse
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?

vache said:
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
Click to expand...
Click to collapse
Yes I got an OTA when I got my phone today.

orimigato said:
Yes I got an OTA when I got my phone today.
Click to expand...
Click to collapse
Download stock ROM that match your current version from https://mirrors.lolinet.com/firmware/moto/def/official/
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7

vache said:
Download stock ROM that match your current version from ...
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
Click to expand...
Click to collapse
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed

orimigato said:
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip

vache said:
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!

orimigato said:
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
Click to expand...
Click to collapse
Wew cool it worked, i was running out of ideas xD

First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !

orimigato said:
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
Click to expand...
Click to collapse
Thanks for the detailed report.
1. About bluetooth, noticed that later while testing, already fixed.
2. You'd better install back Moto Camera 2 from Play Store if you want to get all stock features.
3. Never used that feature tbh, could you grab some logs ? (i'll make some tests on my side anyway)
I'll try to release the new build later today.
Edit : Created an account here : https://www.linphone.org/freesip/home
Then used https://freephonebox.net/ to call me, and it seems to work. (see attached screenshots)

SIP
Retried the SIP and now it is working. Possible was not working earlier since my old phone was still registered. Thanks for checking:good:

Any idea when you could have a build available? Thanks in advance for your efforts :good:

orimigato said:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
Click to expand...
Click to collapse
Sorry, it was delayed cause i was working on dolby. Ill post it tomorrow.
Edit : New build ->https://www.androidfilehost.com/?fid=4349826312261718849 (check OP for update instruction)
Changelog :
- Fix bluetooth audio playback
- Added Dolby audio (Use QS Tile to open it for now)
- Added Google Feed to launcher
- February security patch
- Fixed tap to wake
- Synced kernel source with CAF
https://gerrit.omnirom.org/q/status:merged
https://github.com/boulzordev/device_motorola_def/commits/android-10
https://github.com/boulzordev/kernel_motorola_sm6150/commits/android-10

Bluetooth works perfectly now. Dolby is also very nice. Many thanks!

Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?

htcmusic said:
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
Click to expand...
Click to collapse
Yes what's the best root method you guys using?

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
I will receive this phone next week (US version) and I will use patching boot.img method

mingkee said:
I will receive this phone next week (US version) and I will use patching boot.img method
Click to expand...
Click to collapse
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
young-ster said:
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
Click to expand...
Click to collapse
I see it
https://mirrors.lolinet.com/firmware/moto/def/official/RETUS/

Trying to install latest TWRP on Moto G5 gives error (bootloader) Image size exeeded partition limits

Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?

trickyDicky314 said:
Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?
Click to expand...
Click to collapse
Note later 64bit twrp version for some reason exceed partition size. If you require a permanently installed TWRP use an old version.
To use the later versions of TWRP you need to boot to TWRP instead each time you want to use it.
Click to expand...
Click to collapse
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com

As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.

sd_shadow said:
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for fast reply! I will try just booting new version and installing. I didn't realize that would work, I thought u needed TWRP permanently installed for it to work, (am not experienced with this stuff).
Thanks again!

TheFixItMan said:
As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.
Click to expand...
Click to collapse
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.

trickyDicky314 said:
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.
Click to expand...
Click to collapse
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.

sd_shadow said:
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.
Click to expand...
Click to collapse
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
{
"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"
}
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to

sd_shadow said:
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again

TheFixItMan said:
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to
Click to expand...
Click to collapse
Thanks so much! This worked, I am now in Lineage OS! Thanks for taking the time to help out a newb like me by writing out every step

trickyDicky314 said:
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again
Click to expand...
Click to collapse
Yeah, just skip that, and go straight to the rescue option

Development [ROM][11.0][OFFICIAL][ALIOTH/ALIOTHIN] EOL - crDroid v7.22 [12.09.2022]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features: https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Sources:
ROM:https://github.com/crdroidandroid
Kernel: kernel Optimus Drunk
Github: raystef66
LATEST crDroid Build
Flashing Instructions: FOLLOW NEW GUIDE
POCO F3 TELEGRAM GROUP
What's working / what's not:
* most of it is working :
ril
audio
wifi
BT
camera
NFC
FP
Faceunlock
GPS
AOD (tile)
hotspot
DT2W (on doze)
DT2S
ambient features
ok google
...
* bugs : DO SEND LOGS WHEN REPORTING BUGS
. . .
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
If you like my work, consider a donation! MY PAYPAL
Contributors
@raystef66
@jomadeto
Source Code: https://github.com/crdroidandroid/android/tree/11.0
ROM OS Version: 11.0
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, miu v12.0.x or 12.5.x
Status: stable
Sec. Patches : 2022.09.05
Created : 2021.05.07
Last Updated : 2022.09.12

CHANGELOG
Highlights & Device Specific Changes:
Build type: Monthly
Device: POCO F3 (alioth)
Device maintainer: raystef66

raystef66 said:
CHANGELOG
Click to expand...
Click to collapse
Congrats boss for being Official

raystef66 said:
GAPPS INCLUDED for now
Click to expand...
Click to collapse
"for now" gives me hope that it won't be there at some point. Yes?
BTW: Thank you very much for developing/porting this ROM

Fahmid Islam Soumya said:
Congrats boss for being Official
Click to expand...
Click to collapse
Thnx bro

Awesome work

Robert314 said:
Awesome work
Click to expand...
Click to collapse
Waiting for yours

can I flash this from xiaomi*eu latest stable rom, sir?

My poco f3 should be delivered in days, I'm so happy seeing development advancing so fast. Thank you!

Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed

Does it have OTA?

Can i flash it over base miui 12.6?

So only SSOS has a fully working D2tw right?
so far so good. love crdroid! thanks matey! <3

hkfriends said:
Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
Having the exact same issue with this ROM and Pixel Experience.... coming from a newly flashed 12.0.2 global fastboot and freshly unlocked bootloader...have no problems with xiaomi.eu though

navey said:
Having the exact same issue with this ROM and Pixel Experience.... coming from a newly flashed 12.0.2 global fastboot and freshly unlocked bootloader...
Click to expand...
Click to collapse
replug or use a different cable.
use a different platform tools (adb and fastboot exe) I prefer the one's from google but not the latest fastboot as it borks flashing stock roms via fastboot

Abaddon said:
replug or use a different cable.
use a different platform tools (adb and fastboot exe) I prefer the one's from google but not the latest fastboot as it borks flashing stock roms via fastboot
Click to expand...
Click to collapse
tried several cables and like i said I don't have any issues with xiaomi.eu at all. I see my device just fine in adb and fastboot as well.. will do more research

navey said:
tried several cables and like i said I don't have any issues with xiaomi.eu at all. I see my device just fine in adb and fastboot as well.. will do more research
Click to expand...
Click to collapse
I said those because I had a similar scenario. xiaomi eu fastboot flashes fine but other fastboot roms wont flash properly. its either my port (had to replug), usb drivers and the fastboot exe itself. I fixed it by changing the fastboot.exe to an older one. goodluck with yours hope u get it fixed asap

hkfriends said:
Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
Fixed this! Enabled system wide ADB on my machine and now its working smoothly so far with no errors whatsoever. Follow this link
Set up System-wide ADB and Fastboot on Windows 10/11
Here's how to set up system-wide ADB and Fastboot on Windows 10 and 11. Download SDK platform tools and enjoy universal ADB and Fastboot.
technastic.com

Abaddon said:
I said those because I had a similar scenario. xiaomi eu fastboot flashes fine but other fastboot roms wont flash properly. its either my port (had to replug), usb drivers and the fastboot exe itself. I fixed it by changing the fastboot.exe to an older one. goodluck with yours hope u get it fixed asap
Click to expand...
Click to collapse
Thanks man i actually got it fixed by installing system wide adb but it was your thoughts that lead me there. THANK YOU!!

navey said:
Fixed this! Enabled system wide ADB on my machine and now its working smoothly so far with no errors whatsoever. Follow this link
Set up System-wide ADB and Fastboot on Windows 10/11
Here's how to set up system-wide ADB and Fastboot on Windows 10 and 11. Download SDK platform tools and enjoy universal ADB and Fastboot.
technastic.com
Click to expand...
Click to collapse
will try this out tonight... strangely it is due to missing system path to execute fastboot?

Question Need help, Can't figure out how to change my ROM

Exactly a year ago I bought Poco F3, unlocked the bootloader and installed ArrowOS. Now I'm trying to figure out how to change my ROM and I can't really find any answers. I have the ArrowOS recovery and it's useless, I can't install another recovery with it. My fastboot also seems to be broken(?), it has a different logo and it's detected on my computer when I do (fastboot devices) but other than that it gives me a bunch of errors
I would like to at least know how to change the recovery. Is it possible that my bootloader got locked? One last thing, when I installed ArrowOS I used TWRP and updated it using OTA updates, now TWRP is gone.
Please help me

You need fastboot for TWRP.

It could not have gotten locked, no.

Arealhooman said:
It could not have gotten locked, no.
Click to expand...
Click to collapse
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?

Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.

Arealhooman said:
Uh….maybe… did you lock it… what does it say in dev Setting sunder oem unlock.
Click to expand...
Click to collapse
I don't have any oem unlock option in ArrowOS and I never locked anything wtf, I just used it as a normal phone and only did OTA updates + sometimes FW updates when required
Is there anyway to fix it?

ADB & Fastboot Binaries: https://developer.android.com/studio/releases/platform-tools
OrangeFox Recovery (recommended): https://orangefox.download/device/alioth
Install the Recovery ZIP by either ADB Sideload in ArrowOS Recovery
or you can extract the "recovery.img" and fastboot boot it ("fastboot boot recovery.img") and select "Install current Recovery"
Then you simply flash the ROM.zip (select "Reflash Recovery after ROM Flash") -> Reboot Recovery -> Format Data
The OTA Update has replaced your TWRP with ArrowOS Recovery, because ROM Updates replace the boot-partition (along with other system related partitions). The boot-partition contains the recovery-environment.
Only install Custom Recoveries from inside the Recovery, because Fastboot can only replace partitions entirely (and boot-partitions contains both bootloader & recovery)
The bootloader of the Poco F3 cannot (or shouldn't) be locked on Custom Software.

gobertel said:
I just found a guide on Youtube for flashing twrp and I followed it to the (fastboot boot <TWRP>) part and I got this error
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Does this mean it got locked..?
Click to expand...
Click to collapse
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.

Also, what's the problem with ArrowOS anyway? We've ArrowOS MiPa, it's a good and reliable ROM.

cyanGalaxy said:
Download these:
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/boot.img/download
https://sourceforge.net/projects/mipa-project/files/arrow-mipa/arrow-13.0/alioth/Additions/vendor_boot.img/download
First link, "fastboot flash boot boot.img"
Second link, "fastboot flash vendor_boot vendor_boot.img"
Then Fastboot booting into your Recovery-file should work.
Click to expand...
Click to collapse
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general

Thank you for helping me out by the way

gobertel said:
I noticed that these are for ArrowOS 13, I'm on 12.1 and they did not work
Do you also suggest I go into fastboot by which method because each one looks different
Recovery > Advanced > Enter fastboot
Or
Hold power button with volume down method
Also I'm just looking to update to Android 13 in general
Click to expand...
Click to collapse
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.

Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com

cyanGalaxy said:
Both methods of booting into Fastboot is the same I would guess.
Yes we do have ArrowOS MiPa, you should only need to flash the ArrowOS 13 MiPa ROM ZIP in Recovery, but I rather recommend you using OrangeFox or TWRP for that.
What do you mean by "did not work". "Did not work" can mean anything.
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
fastboot boot recovery.img
Sending 'boot.img' (196608 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Another thing to add is I still I get the unlock symbol when booting up the phone, I dont know if that makes a difference

cyanGalaxy said:
Are you using the latest official ADB & Fastboot Binaries? The ones I've given you?
If yes, you can use this Payload Dumper Tool, to extract the "vendor_boot.img" and "boot.img" from ArrowOS 12. Maybe those from Arrow v12 can be flashed.
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes I'm using the exact one you gave me and I will try it

gobertel said:
Yes I'm using the exact one you gave me and I will try it
Click to expand...
Click to collapse
Yup try it.
Else, here I have the vendor_boot.img & boot.img from the latest ArrowOS MiPa (February). More up-to-date than the SourceForge links.
Either the 2 files from ArrowOS v12, or the latest v13 ones that I've uploaded here, should definitely work.
Also try rebooting Fastboot Mode.

XDA doesn't let me upload the boot.img ඞ

cyanGalaxy said:
XDA doesn't let me upload the boot.img ඞ
Click to expand...
Click to collapse
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything

gobertel said:
Starting to think I should just give up, no matter what I do I get (Download is not allowed on locked devices)
The fastboot method you suggested does not work, it gets stuck on (waiting for any devices) but the recovery one works although like I said, I get the error no matter what I do
Is it locked or what?? I'm trying to figure that out and if it is how did it even get locked in the first place
I'm guessing there's no way to resolve it and that I'll be stuck on Android 12 for eternity
So sorry for wasting your time, I always end up with weird issues in everything
Click to expand...
Click to collapse
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.

cyanGalaxy said:
Waiting for any devices means your PC does not detect the phone.
Download this: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
And install the USB driver.
And no it's not locked, the Unlocked symbol during Boot is normal. I think it was a bug with older ArrowOS Bootloader versions. Not quite sure.
Click to expand...
Click to collapse
IT WORKED. Thank you so much, it was a driver issue but the exact version you gave me didn't work, I had to find another one