Database Info

Can't flash twrp need help!

Okay so I received my opo today and wanted to unlock and root etc.. I managed to install drivers and download a toolkit which managed to unlock my bootloader but wouldn't flash the recovery so I attempted it manually via fastboot and after flashing it would reboot to a back screen then vibrate and reboot to system.. Been doing that all night? Any ideas? many thanks in advance new to this phone

Exactly what recovery version are you trying to flash? What OS is on the phone? Get rid of the toolkit, they're nothing but trouble.

Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused

daviss101 said:
Twrp 2.8.1. And its running android 4.4.4 cyanogen mod.. I have mate haha. I take it fastboot and adb are installed correctly as it shows my opo after typing fastboot devices and it unlocked my boot loader soo I'm confused
Click to expand...
Click to collapse
Try flashing the recovery again, followed by this command
Code:
fastboot erase cache
Then:
Code:
fastboot reboot
Then try booting into recovery.
PS. You've unchecked the "update CM recovery" option in Developer Options, right?

same problem for me. tried manually installing any custom recovery, tried two different toolkits. it flashes and reboots, but then you can never enter the recovery app. even attempting to put stock back fails. i attempted the format the cache and that didn't do a thing for me. basically had to enable cm recovery updates and reset to factory in the os. after that i was back to scratch at least.

I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler

GrizzlyD said:
I was able to figure it out. Appears the version of TWRP is quite particular for some reason. Once I tried the latest build from here dl dot twrp dot me/bacon/ the problem was solved. Thanks for the tip @snickler
Click to expand...
Click to collapse
No problemo. ^_^

Moto G3 boots into recovery every time I power on device

I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.

ItsWoffles said:
I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
Look at this thread
https://forum.xda-developers.com/2015-moto-g/help/reboot-bootloader-mode-t3653547

melp57 said:
Look at this thread
https://forum.xda-developers.com/2015-moto-g/help/reboot-bootloader-mode-t3653547
Click to expand...
Click to collapse
Do I need to type in fastboot oem fb_mode_clear while re flashing stock firmware again like I would to relock the bootloader?

ItsWoffles said:
Do I need to type in fastboot oem fb_mode_clear while re flashing stock firmware again like I would to relock the bootloader?
Click to expand...
Click to collapse
Actually it's not an issue, the command
Code:
fastboot oem fb_mode_set
makes the phone boot into bootloader mode instead of starting android. To undo this, you'll just have to type in-
Code:
fastboot oem fb_mode_clear
. No need to flash the whole firmware again if this is the only problem.
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Actually it's not an issue, the command
Code:
fastboot oem fb_mode_set
makes the phone boot into bootloader mode instead of starting android. To undo this, you'll just have to type in-
Code:
fastboot oem fb_mode_clear
. No need to flash the whole firmware again if this is the only problem.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Where do I type this command in? Using ABD and fastboot? Do I just go into the bootloader and plug my phone into my PC, then open up ABD and fastboot and type in that command or what do I do? Is that the only command I need to type in? Sorry, I'm a noob to this kinda stuff!

ItsWoffles said:
Where do I type this command in? Using ABD and fastboot? Do I just go into the bootloader and plug my phone into my PC, then open up ABD and fastboot and type in that command or what do I do? Is that the only command I need to type in? Sorry, I'm a noob to this kinda stuff!
Click to expand...
Click to collapse
Reboot the phone into bootloader mode. To do this, power off the phone, press and hold power+volume down button till it shows up.
Plug the phone into PC, open command prompt from the folder where adb.exe and fastboot.exe are present, and type that command (only that one is needed). Disconnect the phone and try rebooting to see if it boots correctly.
Broadcasted from Zeta Reticuli

ItsWoffles said:
I have unlocked my bootloader. Every time I power on my Motorola Moto G3, it boots into the recovery screen. It isn't really a problem, it's more of an annoyance. I have to use the power / volume buttons to choose start and then it boots into the OS fine.
Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
I think u flashed recovery to boot..

mg_jishad said:
I think u flashed recovery to boot..
Click to expand...
Click to collapse
If that was the case, you could never boot the phone into Android... the OP stated that he can select continue and start the device normally. It is most likely stuck in fastboot fb_mode like @Gravemind2015 stated.

Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....

Uncle Waldo said:
Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....
Click to expand...
Click to collapse
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot

acejavelin said:
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot
Click to expand...
Click to collapse
Shouldn't that make the phone stay at bootlogo as the kernel and ramdisk are overwritten by TWRP code? @Uncle Waldo stated that the phone is looping into TWRP after *moto update action*. So what I am able to figure out is that this is a OTA-on-stock-rom-with-custom-recovery situation. I am a litte doubtful though as google says the phone boots into kernel from recovery (which is evident here) instead of kernel from boot partiton (source), so you may be 100% correct here too
@Uncle Waldo : If that is indeed the case (i.e moto issued an update and since rebooting the phone it's just looping into TWRP and giving an error) then I'd recommend that-
Flash stock boot.img as @acejavelin suggested
Flash stock recovery.img (as TWRP can't nstall stock ROM updates)
This is assuming that the /system partition was never modified in any way. If the update still fails in stock revovery, I'd guess that the whole system has to be restored to a non-modified state (i.e flashing the full firmware). You can try flashing all without doing the 'fastboot erase' part though, but i'd recommend you to backup your files using TWRP when you can.
links-
Link to the flashing guide is here
Link to the firmware index is here
command to install recovery -
Code:
fastboot flash recovery recovery.img
command to flash boot.img-
Code:
fastboot flash boot boot.img

Uncle Waldo said:
Excuse any possible miss posting of My question.
Moto G 3 factory rom and rooted
Problem: Motorola security update action causes Moto to keep booting into twrp recovery loop.
Have tried to break the looping, but there is something I am missing or not doing correctly any help thanks.....
Click to expand...
Click to collapse
If it is because of an update, you can't accept it while on TWRP... If you did, try to access the TWRP menu and if you can't boot TWRP from.fadtboot (not flash) and wipe caches... It should boot normally after that.

ACE; moto has been operating for sometime now fine
acejavelin said:
Now this sounds like you flashed TWRP in your boot image... Reflash the stock boot image with fastboot
Click to expand...
Click to collapse
You believe this could be my problem as the moto boots just fine and it's only started this problem when I installed the following update.
Motorola > android security updates version 24.211.14.en.US
After this install and reboot it appears to work just fine and then shortly reboots into TWRP from here the only correcting action that stops the reboot loop is "RESTORE".
After restoring and reboot the moto is back to operating as before and at some point I get the same message to install the security updates and the dance begins anew.
If reflashing the stock boot image via fastboot could correct my problem > then I am all ears Ace, as it's been sometime since I ventured into android ville and any help in this matter thanks...

Uncle Waldo said:
You believe this could be my problem as the moto boots just fine and it's only started this problem when I installed the following update.
Motorola > android security updates version 24.211.14.en.US
After this install and reboot it appears to work just fine and then shortly reboots into TWRP from here the only correcting action that stops the reboot loop is "RESTORE".
After restoring and reboot the moto is back to operating as before and at some point I get the same message to install the security updates and the dance begins anew.
If reflashing the stock boot image via fastboot could correct my problem > then I am all ears Ace, as it's been sometime since I ventured into android ville and any help in this matter thanks...
Click to expand...
Click to collapse
You edited the original question after I replied... Read my follow-up answer. You can't take an OTA with TWRP installed, just start TWRP and wipe caches and then don't accept any further OTA.

Ace; I missed that one
acejavelin said:
You edited the original question after I replied... Read my follow-up answer. You can't take an OTA with TWRP installed, just start TWRP and wipe caches and then don't accept any further OTA.
Click to expand...
Click to collapse
Your correct I missed that one, a BC moment (before coffee) sorry.
Okay in the fog of my memory I do now remember the OTA prohibition as I said it's been a piece of time.
I've done as instructed and all is well again, but will this nag screen appear again as it has done.
Question > How do I shut the motorolia OTA update off, so I don't get their stupid never ending nag screen everytime that I look at phone?
Thanks for your help...
---------- Post added at 05:13 PM ---------- Previous post was at 04:33 PM ----------
Ace I figured it out thanks for all your help...

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.

Question Stuck in boot loop while trying to root using Magdisk help please?

Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.

Hold the power button till it turns off, volume down + power button to get to bootloader. Reflash stock boot.
ALWAYS fastboot boot first before actually flashing in case this happens

Make sure you're using the correct boot image to patch for your build number too

AphoticAffinity said:
Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Click to expand...
Click to collapse
What version of Magisk did you use? You must use 24.0 or newer.
As @ctfrommn recommended, you can "live boot" the patched image instead of flashing it:
fastboot boot <patched boot image>
If this fails for whatever reason, it'll reboot with the stock boot image.

General Official Android 13 firmware is now available

It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.

MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo

Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse

MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!

Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.

MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!

I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system

MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second

rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.

so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?

rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root

chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su

chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.

I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse

MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot

Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse

MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.

I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater

Does anyone have the full RAW firmware, flashed via fastboot? Thank you all

ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs