Database Develop

Help - Stuck in Bootloop

The point in which everything took a turn for the worst was while trying to update firmware via SD update method. At which point it just stayed on android boot screen.
Recovery was broken at this point
I successfully flashed an older CWM version, but that was useless for reflashing the latest Asus firmware.
I tried flashing stock recovery again and it appeared to succeed, but now when I try to boot to recovery, it just goes back to bootloop.
I'm trying to flash the US version now via fastboot I get bootloop again and I'm getting weird errors every time I try regarding filesize. (See below)
I tried flashing CROMbi as well and it went through the install process successfully, but that resulted in bootloop as well.
Tried flashing Asus US firmware again without success,
Kind of pissed that this all started when following the instructions on the Asus site to upgrade to their latest firmware via SD card.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system
asusus.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.457s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
OKAY [ 86.837s]
writing 'system'...
OKAY [ 17.080s]
sending sparse 'system' (415060 KB)...
OKAY [ 57.305s]
writing 'system'...
OKAY [ 11.353s]
finished. total time: 174.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.021s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.

The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk

berndblb said:
The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
The attempted SD update was done with custom recovery as I couldn't get stock recovery to work after the initial SD update with stock recovery.
Thanks for the info. I'll update.

gorilla p said:
Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.
Click to expand...
Click to collapse
That error message means that your internal sdcard is no t available to format. Erasing all partitions is a dangerous thing to do.
The only way you will get back to normal is to try and flash the stock asus rom now as that will recreate everything. I recommend you start with the 4.2.2 one - need to flash it over fastboot - I can't see anything else working as you have erased it all.....
Also you used 0x0b05 which is the code for the last generation of transformers..... You don't need it for the TF701 but not sure if that has caused additional grief now. Probably not but you never know .....

Yeah IO'm getting the same issue that I was having before. I tried both the 4.3 and 4.2 boot.img and the recommended recovery.img file. Each time I ran
fasboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.121s]
booting...
OKAY [ 0.032s]
finished. total time: 1.157s
booting from downloaded boot.img (on tablet)
Then it goes to boot into the image and...bootloop.
C:\Program Files (x86)\Minimal ADB and Fastboot\asus>fastboot flash system asus4
22.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.515s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
OKAY [ 86.861s]
writing 'system'...
OKAY [ 17.098s]
sending sparse 'system' (338700 KB)...
OKAY [ 46.823s]
writing 'system'...
OKAY [ 9.280s]
finished. total time: 161.586s
Bootloop...
Could the inability to flash or boot from stock recovery have anything to do with the CWM recovery protection?

Well after those attempts it's totally shot.
Now I can't even get to fastboot. Every reboot results in "Unrecoverable bootloader error..."
Files RMA. Returned.
Moral of story. Don't do anything on a Tegra device without previous documentation that doesn't have NVFlash available.

[ROM] MM M1D63X ext 4 Rooted + Frankenlenok Kernel

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, thermonuclear war,
* or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point
* the finger at me for messing up your device, I will laugh at you.
*/
I've made a very fast rom, without a lot of stupid apk and with ext4 system for modifing /system.
You must say thanks to other people, I'm only a stupid "aggregator"....
But thanks also to @Cameo164, after his experience i've made a more little system.img, changing the partions size.
- Download my rom, unzip
http://www.mediafire.com/file/ke5h46vy86o23tl/DF0.1.zip
- Reboot into fastboot
- Install this Recovery (you'll find also here: http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 )
fastboot flash recovery path/to/twrp-3.0.0.img
- Reboot into recovery and Make a backup of your Rom/data/system with this recovery!!!! It's very important!
- Wipe cache and data via recovery, reboot into bootloader
- Install my boot.img
fastboot flash boot boot.img
- Go to this thred ( http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 ) and follow the steps 4-15 and then come back here
- Then:
fastboot flash system systemimageresized.img
- Reboot recovery and install supersu: Wear-SuperSU-v2.67.zip (you'll find in my zip)
- Restart system and wait..........
- Don't care for the google play error on your smartwatch, if you have
- Enable adb debug under dev options on your watch, you can also enable before paring, pushing the hardware button for about 2 seconds
- Pair with your phone
- Install busybox (you'll find in my zip)
adb install busybox.apk
- Install advanced settings for wear http://forum.xda-developers.com/android/apps-games/advanced-settings-t3341722
adb install com.sssemil.advancedsettings.apk
It's very usefull for change the screensaver brightness and other things
- Install Kernel Auditor http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
adb install KernelAudiutor4Wear.apk
For enable/disable cores and other things
- on your smartwatch if you have issue, reboot and clear data to google.play. framework (with advanced settings), reboot again
This rom is without a lot of things (like lg wathfaces, tutorial.apk and other things that i don't remeber, i'm sorry).
I use other watchfaces (with facer, this is mine: https://www.facer.io/watchface/hLzCJbTR3Z?draft=true )
Don't ask for add apks, or other things, thank you!
I suggest disable with advanced settings under apps also Bug report sender com.google...wearable.bugreportsender
Remember:
Don't change kernel or rom because you'll corrupt the new ext4 partition and you'll lose your data.
In any case before make a backup,
So, when you'll change rom/kernel you must install again the right kernel and the right rom.
If you have adb error ($ADB_VENDOR_KEYS is not set; try 'adb kill-server'), from recovery:
On your pc search adbkey.pub
cd user/.android
adb push adbkey.pub /data/misc/adb/adb_keys
You must say thanks to:
For stock Image thanks to @intersectRaven and also @vt0r http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
For This great Kernel thanks to @dirtyhank http://forum.xda-developers.com/g-watch-r/development/kernel-frankenlenok-t3342054 (look at the last page)
windroid toolkit http://forum.xda-developers.com/showthread.php?t=2499926
@Chainfire
@suleymanovemil8
@Xmaster24
@Grarak
@dirtyhank
@Cameo164

Changelog
I've uploaded my things.

Hi, thanks for your work, but for me restoring your system in twrp fails. It show's me an "ERROR: 255" close to the end. I re-downloaded the backup files, so that I can be sure that the files aren't damaged, but still no luck. I'm using the twrp.img you provided and did it like you described.
And btw. When I'm right, it should be called "adb push" not "adb pull".

http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Did you mount system in recovery?
Or try installing before leedroid rom.
Yes... is push! I'm sorry!

dettofatto said:
http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Or try installing before leedroid rom.
Click to expand...
Click to collapse
Yes I did. But it's not important if I did it, because TWRP does it before restoring anyways.
What difference would it make if install leedroid rom before restoring, when TWRP formats /system before restoring your backup ?

If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.

dettofatto said:
If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.
Click to expand...
Click to collapse
To have ext4 I don't need to install a non-mm rom like leedroid's. I can just format /system to ext4 in TWRP.
Yes I have read it. The file that causes problems is "/system/usr/icu/icudt55l.dat". I removed it from the backup file and pushed the new file to the watch. And now the restoring works. But I ended up with a bootloop (tried with SuperSu flashed & without SuperSu). I don't know if it's because I removed the file or if it has any other reason.
Thanks for trying to help me.

Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...

dettofatto said:
Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...
Click to expand...
Click to collapse
Yeah I waited 30 minutes, rebooted, waited another 30 minutes and again, again...
The bootanimation I see on watch is in the attachments but because the watch screen is too small there's only "ndroi" instead of "android" visible. And there's that darker font shadow, like a fade-out animation which is going through continuously.
I know that I can't just delete one file, but with that file I can't even restore the backup.
Then I get this error :
Code:
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/")
item name: '/usr/icu/'
dir
==> extracting: /system//usr/icu/ (mode 40755, directory)
==> setting perms: /system//usr/icu/ (mode 40755, uid 0, gid 0)
Restoring SELinux context u:object_r:system_file:s0 to file /system//usr/icu/
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/icudt55l.dat")
item name: '/usr/icu/icudt55l.dat'
reg
==> tar_extract_regfile(t=0xb56a9300, realname="/system//usr/icu/icudt55l.dat")
==> extracting: /system//usr/icu/icudt55l.dat (file size 23068784 bytes)
FAILED RESTORE OF FILE i: /system//usr/icu/icudt55l.dat
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/411KPFX0122123/DF/system.ext4.win'
Fehler während der Wiederherstellung. *should be "Error during restore process" in english
Prozess extractTarFork() endete mit FEHLER: 255 *should be "Prozess extractTarFork() ends with ERROR:255" in english
I:Failed to reset capabilities of /system/bin/run-as binary.
Can you send me the file icudt55l.dat from your running watch and then I can try replacing the file in the backup?

I'll send you icudt55l.da after, when I come back at home. But is very strange...
Anyone has this issue?

icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat

dettofatto said:
icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat
Click to expand...
Click to collapse
I tried everything I'm able to do : First pasting your new icudt55l.dat file into the backup, just gives me the same error as before. Then I tried restoring the backup without the icudt55l.dat file and push the file with adb push to /system/usr/icu, just gives me a "no space left on device error" and at last I tried to extract the system.ext4.win file on the watch with adb shell instead of twrp, this gives me a "no space left on device" error too, but it seams that I does it anyways. But still stuck on bootanimation. I just can't get this rom to work on my watch :|

After I'll try tu upload another backup...

Ok i've created a system.img_sparsechunk1 flashable via fastboot
Backup everything.
Then download: http://www.mediafire.com/file/d3yo1opb4i7j7at/system.img_sparsechunk1
Reboot into bootloader and:
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash system system.img_sparsechunk1
Flash also (I don't know if is necessary for you, but you must use mine boot.img) boot.img http://www.mediafire.com/file/w11byay60nwy5xb/boot.img
fastboot flash boot boot.img
Reboot into recovery and
Wipe data, davlink and cache
Reboot
How I've obtained this system.img_sparsechunk1?
I've extracted my system.img with: dd if=/dev/block/mmcblk0p19 of=/sdcard/system.img
but when i reflashed via fastboot I had an error because was bigger than system partition.
So i've compressed with SparseConverter v1.0.1 http://forum.xda-developers.com/showthread.php?t=2749797
to correct size: sparseconverter /compress system.img .\ 2684354560
and I've obtained the righht system.img
I hope...
In any case i've reflashed on mine and is ok

Thanks a lot for your hard work but my watch still refuses to flash the system -.-
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.288s]
sending sparse 'system' 1/2 (252175 KB)...
OKAY [ 8.280s]
writing 'system' 1/2...
FAILED (remote: size too large)
finished. total time: 8.651s
I have tried it with the latest fastboot version for windows and linux too, but both fail on "size too large". I have even downloaded SparseConverter myself, decompressed the "system.img_sparsechunk1" to "system.img" and then compressed it back into two 100MB and one 61MB sparsechunk files. Still fastboot gives me the "size too large" error.
I can flash the stock "M1D63X_system.img" successfully and it boots too.

I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe

dettofatto said:
I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe
Click to expand...
Click to collapse
I tried your fastboot version, but it happens the same :
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.300s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.332s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 8.711s

Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)

dettofatto said:
Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)
Click to expand...
Click to collapse
I don't have any ideas too, I would be very good if anyone else could try your rom and tell if installing and booting works. Then we would know if it's my watch's or my' fault or the rom's fault.

System uncompressed extracted: http://www.mediafire.com/file/g481ae7m3ayrjmb/systemuncompressed.zip
New Backup from System:
http://www.mediafire.com/file/4jc5a31xe2insc6/TWRP.7z
May be is my rom

[ROM][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
Downloads: https://asineth.me/post/android-rav/
Flashing:
1. Extract the zip and open a shell with ADB and fastboot.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
4. Wipe userdata.
Code:
fastboot -w
If you are on the Moto G8/G Fast and your display cutout is misbehaving, enable your overlay like so:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
I've tested with Magisk v20.4 & OpenGapps Pico, to flash, temporarily boot into TWRP with fastboot.
Working:
Display
Touchscreen
Wi-Fi
Bluetooth (including audio)
Headphones via 3.5mm
Internal Speaker
Moto Actions
Calls/SMS/LTE/VoLTE on Verizon
Issues:
Vibration motor is broken
Stock wallpaper animation (fixed by changing it)
Rav (G8/G Fast) users must enable their overlay manually
Source:
LineageOS
Device tree
Vendor tree
Kernel tree
Telegram:
https://t.me/MotoG8Official
Credits:
@Vachounet - helped a lot, original device/vendor tree, TWRP build
@kjjjnob - some LineageOS changes to @Vachounet's tree
This is my first ROM release, thanks for your guy's help!
XDA:DevDB Information
[ROM][RAV*/SOFIA*][10][UNOFFICIAL] LineageOS 17.1, ROM for the Moto G8
Contributors
asineth
Source Code: https://git.asineth.gq
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 17.1-20200915
Stable Release Date: 2020-09-14
Created 2020-09-15
Last Updated 2020-09-15

Nice work
Instalation was easy, everuthing is working as described or not working as described.
What would you think about setting your work for Micro G support?

atiolon said:
Instalation was easy, everuthing is working as described or not working as described.
What would you think about setting your work for Micro G support?
Click to expand...
Click to collapse
Might provide microG builds if there's interest.

asineth said:
Might provide microG builds if there's interest.
Click to expand...
Click to collapse
I vote for it.

****ed up, send help.
Okay so, I followed the instructions but I ****ed it all up. adb shell wouldn't do fastboot reboot fastboot from the bootloader, nor would the mounting command work. It still doesn't. I flashed those files thinking maybe I was already mounted and it defaulted me back to stock os. Then I tried getting back into twrp, but it wanted a password and I had a pattern, so I set a pin code, and that didn't work either. So I reset data user data and another one that was mentioned in another xda thread and now I can mount twrp and get in, but the lineage zip won't flash, it says invalid zip file format. So, I have no idea what Ive done to this phone or how to get lineage on it, or even at this point how to upgrade the firmware because it doesn't even want to do that now, via the stock rom. A little help please. fastboot set_active a returns the table of commands same with b and with .fastboot --set-active=a and b

FoxySheila said:
Okay so, I followed the instructions but I ****ed it all up. adb shell wouldn't do fastboot reboot fastboot from the bootloader, nor would the mounting command work. It still doesn't. I flashed those files thinking maybe I was already mounted and it defaulted me back to stock os. Then I tried getting back into twrp, but it wanted a password and I had a pattern, so I set a pin code, and that didn't work either. So I reset data user data and another one that was mentioned in another xda thread and now I can mount twrp and get in, but the lineage zip won't flash, it says invalid zip file format. So, I have no idea what Ive done to this phone or how to get lineage on it, or even at this point how to upgrade the firmware because it doesn't even want to do that now, via the stock rom. A little help please. fastboot set_active a returns the table of commands same with b and with .fastboot --set-active=a and b
Click to expand...
Click to collapse
I had many bad experiences trying to understand my Rav better. So I think I can help with this one. Let's try the following things:
- BOOT ON STOCK B
Turn on your phone on Fastboot (pressing and holding turn on + volume down). If it works, the screen will be with that Android toy.
Then you plug USB and type fastboot reboot fastboot to enter fastbootD mode.
When screen goes to fastbootd (if you didn't flash TWRP) you can type fastboot set_active b and then fastboot reboot. If you're on TWRP, just don't type anything in password and then set Slot B as active and reboot.
Now you're on stock again, probably.
- TRY AGAIN TO INSTALL LOS
On stock running, you can plug it again on computer and reboot via ADB to fastbootD mode with adb reboot fastboot.
In fastbootD mode, you can try again the steps, not forgetting to put them on Slot A. and wipe userdata with fastboot -w.
- DON'T FLASH TWRP. JUST BOOT FROM IT WITHOUT INSTALL IT.
When you want to use TWRP to install GApps or Magisk, use it not flashing. just type fastboot boot twrp.img from fastboot or fastbootD mode.
Everything should work from this.

Thanks for the reply, a few questions.
I already have twrp installed, I'd be happy to get rid of it but don't know how to, fastboot reboot fastboot open's twrp, or does nothing at all. Adb reboot fastboot does work, but it takes me to what I'm assuming is my stock bootloader? I think the issue is that I need to get rid of twrp and get my recovery back, but I don't have a stock recovery file to flash, "fastboot flash recovery.img" or whatever it would be. I had to use Lenovo's rescue software earlier to put my stock os back on it. The phone isn't behaving as it should, or perhaps its my computer. I digress, when I try to activate a partition with the aforementioned command to do so, it gives me an error like that's not one of the commands it accepts. I tried three different flavors of adb, and they all reproduced the same syntax error. How would you proceed; and do you have a recovery img that I could use, I can't find one via google or loli. Edit: Progress has been made as using your suggestion I was able to get into fastbootD, the **** still wount mount with that command though. Edit 2: Managed to get adb shell working as it should be and flash the files but it just boot looped the phone, please advise. I got an error that said wipe successful after the last command but then it says not automatically formatting.

...
.....

FoxySheila said:
.....
Click to expand...
Click to collapse
First, your syntax is incorrect.
Fastboot flash recovery (nor recover) recovery.img
Second, you can download firmware from lolinet.
Just google the name and you will find it. Recovery.img is bundled with your firmware

Hey there, thanks for the reply.
Beetle84 said:
First, your syntax is incorrect.
Fastboot flash recovery (nor recover) recovery.img
Second, you can download firmware from lolinet.
Just google the name and you will find it. Recovery.img is bundled with your firmware
Click to expand...
Click to collapse
Thanks for the tips, as stated above I was able to get into fastbootD. As for the syntax, that's just me not proofreading what I'm typing and including unnecessary **** into a help request. I digress, I've done everything The user above my last comment suggested, and it boot loops my device, which is my current issue. Any ideas on how I could fix that? To clarify, I'm able to now flash in adb shell the parts of lineage, however, it bootloops my device. Even more concerning and strange is that it booted to twrp even though I was using the one built into fastbootD moments earlier without me booting or flashing to it. Thanks for the help.

FoxySheila said:
Thanks for the tips, as stated above I was able to get into fastbootD. As for the syntax, that's just me not proofreading what I'm typing and including unnecessary **** into a help request. I digress, I've done everything The user above my last comment suggested, and it boot loops my device, which is my current issue. Any ideas on how I could fix that? To clarify, I'm able to now flash in adb shell the parts of lineage, however, it bootloops my device. Even more concerning and strange is that it booted to twrp even though I was using the one built into fastbootD moments earlier without me booting or flashing to it. Thanks for the help.
Click to expand...
Click to collapse
Switch the active slut and flash again...

Hey, thanks for the suggestion.
m666p said:
Switch the active slut and flash again...
Click to expand...
Click to collapse
I'll switch slots and try tomorrow , in the meantime, is this you? http://gph.is/2lgUAQ5

FoxySheila said:
I'll switch slots and try tomorrow , in the meantime, is this you? http://gph.is/2lgUAQ5
Click to expand...
Click to collapse
Yup, I become white on weekends. Also make sure you are flashing the ROM on slot A.

Flashed this no problems. Only major issue I've noticed so far is Android Auto doesn't function (plugged in, mirroring). Any chance of this being fixed?

Nothing
m666p said:
Yup, I become white on weekends. Also make sure you are flashing the ROM on slot A.
Click to expand...
Click to collapse
Tried it your way, got bootlooped again, not working.

Hi All,
I am new to android and also new to flashing custom roms.
I followed the instruction in the OP but got stuck with following error, i am in fastbootd just to get that info out of the way.
[email protected]:/home/michael/Downloads/platform-tools# fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 17.069s]
writing 'system_a' 1/2...
OKAY [ 6.594s]
sending sparse 'system_a' 2/2 (517844 KB)...
OKAY [ 16.871s]
writing 'system_a' 2/2...
FAILED (remote: Operation not permitted)
finished. total time: 44.807s
please help?
additional info, I've unlocked the bootloader via motorola website, but I did not do the patch stock firmware with magisk step and came directly to flashing custom rom, if this makes any difference?
mods: I've made the same post in the omniRom thread, if this is not allowed, I apologize here, and please remove this post and keep the omniRom post, thankis.

Heyo, wealcome to "my hell".. I mean the thread
Yea, I've tried to come at flashing this without getting bootlooped for over a month in as many ways and angles as a person can imagine, and it always boot loops, even for omni rom. Can't flash in twrp becuase it says invalid zip. I have followed the instructions both here and elsewhere to a ****ING t, but nothing. So either I'm a dumb sack of **** or there's something going on with my phone, maybe both? Anyway, a fun factoid I discovered a while back after ****ting my pants for a while thinking I bricked my phone is Lenovo has a rescue agent that for free, resets all moto firmware from regular fastboot back to stock. I've used it over a dozen times in the last month for the aforementioned boot looping. Here it is, I'll be around but for right now, it's clearly beyond me. https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa

Hi, I was able to install everything perfectly and I was also able to get the vibration to work, the only problem is that I cannot enable screen clipping, I have tested it in fastbootD as in fastboot and it does not take command "cmd overlay enable org.omnirom.overlay. moto.rav ". I would need your help to solve that little problem, many thanks to everyone who can help!

Its been a long time since I rooted a phone and I'm stuck. Here is what I've done:
1. Become a developer
2. Enabled OEM_Unlocked in developer options
3. Installed the ADB package using apt-get (I'm running Linux Mint 20 Mate)
4. Allowed debug connection to my computer (remember this PC)
5. adb reboot bootloader (works)
6. fastboot oem get_unlock_data (stuck with display of <waiting for device>
Don't know where to go from here without bricking the phone.
BL: MBM-3.0-sofiar_retail-3b6d53a311-200901
Baseband: M6125_34.30.03.38R SOFIA_LATAMDSDS_CUST
Product/Variant: sofiar XT2041-1 64GB PVT
---------- Post added at 03:20 PM ---------- Previous post was at 03:12 PM ----------
Greydesk said:
Its been a long time since I rooted a phone and I'm stuck. Here is what I've done:
1. Become a developer
2. Enabled OEM_Unlocked in developer options
3. Installed the ADB package using apt-get (I'm running Linux Mint 20 Mate)
4. Allowed debug connection to my computer (remember this PC)
5. adb reboot bootloader (works)
6. fastboot oem get_unlock_data (stuck with display of <waiting for device>
Don't know where to go from here without bricking the phone.
BL: MBM-3.0-sofiar_retail-3b6d53a311-200901
Baseband: M6125_34.30.03.38R SOFIA_LATAMDSDS_CUST
Product/Variant: sofiar XT2041-1 64GB PVT
Click to expand...
Click to collapse
Nevermind. In Linux, adb can be run normally, but fastboot is a sudo command.

To help anyone who is not familiar with flashing, especially in Linux, here is the terminal output of my successful flash:
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.006s]
Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 15.017s]
Writing 'system_a' OKAY [ 3.363s]
Sending sparse 'system_a' 2/2 (467728 KB) OKAY [ 13.203s]
Writing 'system_a' OKAY [ 3.090s]
Finished. Total time: 34.727s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.749s]
Writing 'boot_a' OKAY [ 0.473s]
Finished. Total time: 2.269s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash product product.img
Resizing 'product_a' OKAY [ 0.006s]
Sending 'product_a' (512204 KB) OKAY [ 14.631s]
Writing 'product_a' OKAY [ 3.290s]
Finished. Total time: 17.972s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot flash vbmeta vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.047s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $ sudo ./fastboot -w
Erasing 'userdata' OKAY [ 0.628s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.654s
[email protected] /media/statik/Linux_Storage/Android/platform-tools $
Click to expand...
Click to collapse
---------- Post added at 03:55 PM ---------- Previous post was at 03:55 PM ----------
Question: Can I get rid of the Motorola boot warning that says the bootloader is unlocked and has the pause?

[ROM][ResurrectionRemix 8.6.x][RAV*/SOFIA*][UNOFFICIAL][NO GAPPS]

{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
​Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome ​
combination of performance, customization, power and the most new features, brought directly to your Device.​
​
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!​
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.​
​
​
Install the stock recovery.img if you have previously installed twrp.
1. Extract the zip to your adb/fastboot directory, reboot to bootloader and open a CMD window.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta images.
Code:
[/B][/B][/CENTER]
[B][CENTER]fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
​
4. Wipe userdata.
Code:
fastboot -w
5. Reboot, Profit.
(OPTIONAL)
6. If you want to install TWRP/gapps/magisk, do so after you continue through the installation steps to the home screen.
If you have the Moto G8/G Fast and your display cutout is not right, enable the overlay via ADB:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
1. Starting screen casting/mirroring causes a reboot.
2. The in-built screen recorder also causes a reboot when started.
Dodgy Screen Recorder Fix :laugh:: Download and install the attached apk below, change the quick setting tile to the new one at the bottom of the list, and you should be able to record. (Its the screen recorder app from BlissRom, nothing malicious )
3. Let me know :good:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
​

To update to the latest version without wiping:
UPDATING FOR GAPPS/MAGISK USERS
1. Install the images as usual in fastbootd
2. Power off and boot to TWRP
3. Install GAPPS and/or Magisk
4. Reboot, profit.
UPDATING FOR NON GAPPS/Magisk USERS
Skip steps 2. and 3. from above.

Cant figure out which drive i uploaded the old files to at the moment
But heres the 8.6.9 May security patch update.
Not much new, added a KCAL enabled kernel as default, and added a color control app (root needed), fixed face unlock (g power) and added the moto clock widgets.
RR - May Patch - Google Drive
drive.google.com
TWRP zip and fastboot d images, no gapps only. Theres also some flame gapps in the folder too that i use and work well.

I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?

NeoSDAP said:
I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?
Click to expand...
Click to collapse
Try flashing product instead of system first.

Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.

_huck_ said:
Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.
Click to expand...
Click to collapse
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.

I am SO HAPPY that resurrection remix has just come out for the Moto G Power. I have been waiting!!! I just saw this today, but I can't seem to get it to work.. As seems to happen when people are trying to root the moto G power.. The touch screen will stop working.. I did get mine to root, using this page:
Messed up trying to root
i know there are other threads on this topic. But after going through them I cant find the fix. I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works. I used lmsa to download the stock rom...
forum.xda-developers.com
But I do not know how to apply the same fix after I try to install resurrection remix? I do not have touch screen working after I load.
I am using adb, not sure it twrp is available for moto g power yet, and if that would be the way to get it to work?
I'm using moto g power, sofia variant (usa).. XT2041-4

I tried again and I'm actually getting the following errors:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805263360 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.418s]
writing 'boot'...
OKAY [ 0.821s]
finished. total time: 2.248s
PS C:\adb> fastboot flash system system.img
target reported max download size of 805263360 bytes
sending sparse 'system' (786388 KB)...
OKAY [ 18.732s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.749s
PS C:\adb> fastboot flash product product.img
target reported max download size of 805263360 bytes
sending 'product' (575564 KB)...
OKAY [ 12.511s]
writing 'product'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.539s
PS C:\adb>

@cxskate
You aren't in fastbootd. You are in fastboot mode. From the screen you are at in the above screenshot, type fastboot reboot fastboot.
You should reboot to a new screen with fastbootd in red across the top.
Flash the images there.

I'm still having a problem...
My phone does not enter into FastBootD mode... The screen on my phone doesn't change at all when I enter the command, and my computer adb window reads the following:
Please any advice? Very much appreciated.
PS C:\adb> 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
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
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
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> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
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 C:\adb>

Beetle84 said:
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.
Click to expand...
Click to collapse
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!

_huck_ said:
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!
Click to expand...
Click to collapse
Awesome! What are the little things? I'll add to the bug list

I'm going for a Degoogled setup and this rom is the first one that worked with microg without hassles. I installed minMicrog standard and Majisk, toggled the baked in signature spoofing, and was up and running in minutes. VERY AWESOME!

Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks

etienne_9000 said:
Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks
Click to expand...
Click to collapse
Google 'unlock Motorola bootloader'
You need a code from Motorola.

Beetle84 said:
Google 'unlock Motorola bootloader'
You need a code from Motorola.
Click to expand...
Click to collapse
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.

etienne_9000 said:
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.
Click to expand...
Click to collapse
Did you tick the OEM unlock allowed option in developer settings?

Trying to figure out how to load gapps on with adb now??
I actually was finally able to enter FastBootD mode using a different method I found on youtube, but wasvstill getting errors when I tried to flash.. FAILED (remote: No such file or directory)
UPDATE I copied all the new files to the adb folder on the C: drive and i got it to work.. Got RR up and running, but still..
I'm trying to figure out how to load gapps on with adb now??
Method I used to get fastboot D:
(
),

Beetle84 said:
Did you tick the OEM unlock allowed option in developer settings?
Click to expand...
Click to collapse
Yes i did. Just tried again to "fastboot oem get_unlock_data" and still getting "FAILED (remote: Command not supported in default implementation)"

Question How to install custom recovery TWRP?

I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?

AceSheep said:
I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?
Click to expand...
Click to collapse
fastboot boot twrp.img
Go ti advanced and install current twrp

Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one

bambamGN2 said:
Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one
Click to expand...
Click to collapse
I use a type-c hub to connect a wireless mouse and it works

I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file

AceSheep said:
I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file
Click to expand...
Click to collapse
fastboot boot twrp_UNOFFICIAL.img
This work for sure

This topic is great, but I'm afraid many of us would totally miss the information in here, do anyone has the will to turn the information here into a little "how to TWRP" guide as a topic here? That would be awesome!

My device is Redmi Note 10 5G China and the EEA rom flashed. Using twrp will get stuck in the logo and cannot enter.
Before that, I can start twrp using China rom. I'm still looking for reasons
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help

AceSheep said:
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help
Click to expand...
Click to collapse
No but maybe this helps????
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

i suggest for now stay on stock recovery. you can root phone installing magisk via fastboot. and the only way to try custom rom is flashing the gsi ported generic rom. the nippon gsi telefram group have a lot of gsi. but my advice is wait miu13 update. most of gsi have audio incompatibility. but if you like aosp roms this is the only way. mtk full custom roms for our device dont exist