Hey dear community,
today i've tried to flash a gsi, cuz OOS 12 was just too buggy to use. I know that using gsis is not a good idea but i thought it couldn't get worse than oos 12.
So, couldn't get them to boot so i reflashed the stock rom using fastboot enhance. Altough, now it's always just booting to download mode and i can't get it to boot again.
Thank's for any help :c
Do you get any message on the screen?
rokkdroid said:
Do you get any message on the screen?
Click to expand...
Click to collapse
It's displaying the 1+ logo and tell's me smth about my bootloader being unlocked. After that it reboots again and displays [Fastboot Mode]
Xekresis said:
It's displaying the 1+ logo and tell's me smth about my bootloader being unlocked. After that it reboots again and displays [Fastboot Mode]
Click to expand...
Click to collapse
Also, if that helps... TWRP is showing /product & /my_product (Block device required)
Xekresis said:
Also, if that helps... TWRP is showing /product & /my_product (Block device required)
Click to expand...
Click to collapse
Which variant of Nord 2T do you own?
PattasuBalu said:
Which variant of Nord 2T do you own?
Click to expand...
Click to collapse
I own the global 128 gig version
Xekresis said:
It's displaying the 1+ logo and tell's me smth about my bootloader being unlocked. After that it reboots again and displays [Fastboot Mode]
Click to expand...
Click to collapse
With an unlocked bootloader the message during boot is normal. Can you reach your 2T via ADB?
Fastboot seems to work?
About '/product & /my_product (Block device required)' I can't help.
So first, I don't think a GSI will work, we need to have "Project Treble" support for this. And afaik, while there are hints at it (like vendor_boot) it seems disabled / unavailable.
Need to validate this.
The problem with flashing is, the phone has dynamic partitions.
You need a userspace fastbootd, or local OTA installer.
A few options that come to mind:
- If you have OxygenOS in an old slot still working, you can change slots.
- If you have a backup of your partitions (critical are boot_a / boot_b, metadata and super) you can try restore those. Make sure metadata and super are part of the same backup. They must be in sync!
Right now my TWRP build does not support installing a full OTA of the stock roms, because they have a non-standard format OTA. We'd need to patch the OTA or mod TWRP for this.
Beanow said:
So first, I don't think a GSI will work, we need to have "Project Treble" support for this. And afaik, while there are hints at it (like vendor_boot) it seems disabled / unavailable.
Need to validate this.
The problem with flashing is, the phone has dynamic partitions.
You need a userspace fastbootd, or local OTA installer.
A few options that come to mind:
- If you have OxygenOS in an old slot still working, you can change slots.
- If you have a backup of your partitions (critical are boot_a / boot_b, metadata and super) you can try restore those. Make sure metadata and super are part of the same backup. They must be in sync!
Right now my TWRP build does not support installing a full OTA of the stock roms, because they have a non-standard format OTA. We'd need to patch the OTA or mod TWRP for this.
Click to expand...
Click to collapse
Well my other slot isn't working either. I don't have a partition backup but i've reinstalled OOS using Oxygen Updater and Fastboot Enhance so the whole stock rom is on my phone again. But still Fastboot mode.
Xekresis said:
Well my other slot isn't working either. I don't have a partition backup but i've reinstalled OOS using Oxygen Updater and Fastboot Enhance so the whole stock rom is on my phone again. But still Fastboot mode.
Click to expand...
Click to collapse
Well I tried flashing GSI on my phone. My phone was too rebooting to fastboot. But flashing my backup super.img via fastboot d fixed it.
Edit: super.img is version specific. So flash the one which suits your phone's last firmware.
PattasuBalu said:
Well I tried flashing GSI on my phone. My phone was too rebooting to fastboot. But flashing my backup super.img via fastboot d fixed it.
Edit: super.img is version specific. So flash the one which suits your phone's last firmware.
Click to expand...
Click to collapse
I've downloaded the latest stock rom using oxygen updater and flashed it but it still boots to fastboot mode
Xekresis said:
I've downloaded the latest stock rom using oxygen updater and flashed it but it still boots to fastboot mode
Click to expand...
Click to collapse
Which firmware version were you using on your device?
PattasuBalu said:
Which firmware version were you using on your device?
Click to expand...
Click to collapse
The A.15 version. Idk the exact number
Related
I am currently on OOS 10 OB2/31 and can't seem to find a way to install TWRP and Magisk. Found ways to install TWRP and Magisk via patched boot images on OOS 10 stable but not for OB2/31.... anyone know why it's not as simple as flashing TWRP via fastboot?
I also have a problem
'OOS10beta31' Root
XcutionerX said:
[...] anyone know why it's not as simple as flashing TWRP via fastboot?
Click to expand...
Click to collapse
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
Thank you for your help, gonna try following those. Hopefully I don't f up and have to do a msm restore. But why would they disable that command?... Just to make everything complicated? Guess I will not stick to Oneplus next year.
XcutionerX said:
But why would they disable that command?
Click to expand...
Click to collapse
Security? Deprecated or soon-to-be-deprecated command? Dunno really, lol.
XcutionerX said:
... Just to make everything complicated?
Click to expand...
Click to collapse
To be fair, the only difference between this method and the old method is just one word and manually rebooting to recovery. You still have to flash the twrp.zip after flashing from bootloader file to install TWRP, so it's not too radically different.
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
I have successfully installed TWRP and Magisk with the help of those links. Thank you again for your help.
quizzina said:
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
Click to expand...
Click to collapse
Thank your for the in-depth explanation.
Just download oxygen updater and install 10.0.1 and be done with it
TWRP 3.5.0_9.0 for Razer PhoneWhats working:
Almost everything
Follow The Guide To Install
https://forum.xda-developers.com/t/twrp-for-razer-phone.3727333/
Big Thanks
PIPIPIG233666
Download
TWRP Website
I tried the flashing instructions, but my Razer Phone is stuck on the Razer Logo "Powered By Android" screen.
Edit: Grabbed the wrong file! lol
FanboyStudios said:
I tried the flashing instructions, but my Razer Phone is stuck on the Razer Logo "Powered By Android" screen.
Edit: Grabbed the wrong file! lol
Click to expand...
Click to collapse
Mine is stuck at the Razer Logo "Powered by Android" screen as well. When I first installed TWRP it worked okay and I could access the menus, but now I can only access the Fastbook menu and the device is no longer recognized on my computer.
In FastBoot it's showing the following options:
START
Restart bootloader (does nothing but restart to the Razer Logo screen)
Unlock bootloader [Unlocked]
Recovery mode (does nothing but restart to the Razer logo screen)
Wipe Userdata
Power Off
Secure boot shows "yes"
DEVICE STATE - unlocked
Any suggestions?
Thanks
jkimrey said:
Mine is stuck at the Razer Logo "Powered by Android" screen as well. When I first installed TWRP it worked okay and I could access the menus, but now I can only access the Fastbook menu and the device is no longer recognized on my computer.
In FastBoot it's showing the following options:
START
Restart bootloader (does nothing but restart to the Razer Logo screen)
Unlock bootloader [Unlocked]
Recovery mode (does nothing but restart to the Razer logo screen)
Wipe Userdata
Power Off
Secure boot shows "yes"
DEVICE STATE - unlocked
Any suggestions?
Thanks
Click to expand...
Click to collapse
Which file did you download? ZIP or IMG?
If you downloaded the ZIP and tried to flash that with Fastboot, then you screwed up. You may need to download and flash a boot image. You can find this on the Razer Developer Portal, just Google search Razer Phone Stock ROM. You should keep a copy of the latest firmware anyway just in case their site goes down. Extract the zip and you'll want to flash "boot.img" using fastboot flash boot (path to boot.img here). Flash it to both A and B slots, then try flashing the TWRP IMG again.
Note: If you want Magisk, flash the Magisk ZIP after you install TWRP. Then flash the TWRP ZIP to install the recovery. Flashing the TWRP will unroot your phone.
BUT... This TWRP build seem to have issues. It does not remember settings and it is unable to read the internal storage /sdcard folder.
I suggest using an older build.
FanboyStudios said:
Which file did you download? ZIP or IMG?
If you downloaded the ZIP and tried to flash that with Fastboot, then you screwed up. You may need to download and flash a boot image. You can find this on the Razer Developer Portal, just Google search Razer Phone Stock ROM. You should keep a copy of the latest firmware anyway just in case their site goes down. Extract the zip and you'll want to flash "boot.img" using fastboot flash boot (path to boot.img here). Flash it to both A and B slots, then try flashing the TWRP IMG again.
Note: If you want Magisk, flash the Magisk ZIP after you install TWRP. Then flash the TWRP ZIP to install the recovery. Flashing the TWRP will unroot your phone.
BUT... This TWRP build seem to have issues. It does not remember settings and it is unable to read the internal storage /sdcard folder.
I suggest using an older build.
Click to expand...
Click to collapse
Thanks for the info! The problem I'm running into now is that fastboot no longer recognizes a device is connected (although it shows in device manager). I would have to resolve that before I can flash a boot image right?
Thanks again
jkimrey said:
Thanks for the info! The problem I'm running into now is that fastboot no longer recognizes a device is connected (although it shows in device manager). I would have to resolve that before I can flash a boot image right?
Thanks again
Click to expand...
Click to collapse
I'm actually seeing the device now when running "fastboot devices", but when I try to flash the razer image (or any other) I'm getting "fastboot: error: Couldn't parse partition size '0x'". Any suggestions with that? Thanks!
jkimrey said:
I'm actually seeing the device now when running "fastboot devices", but when I try to flash the razer image (or any other) I'm getting "fastboot: error: Couldn't parse partition size '0x'". Any suggestions with that? Thanks!
Click to expand...
Click to collapse
Try wiping user data and flashing the phone completely back to stock. That might be able to fix it, but if it doesn't you may have bricked your phone. If you did, someone else on here might be able to help you.
wubaolong said:
TWRP 3.5.0_9.0 for Razer PhoneWhats working:
Almost everything
Follow The Guide To Install
https://forum.xda-developers.com/t/twrp-for-razer-phone.3727333/
Big Thanks
PIPIPIG233666
Download
TWRP Website
Click to expand...
Click to collapse
This build seems to have some issues.
1. Internal Storage shows up empty with 0mb.
2. It does not remember the user's settings. You can check the box for "Never show this again during boot" (for allowing changes) and it'll show up again during the next boot.
FanboyStudios said:
This build seems to have some issues.
1. Internal Storage shows up empty with 0mb.
2. It does not remember the user's settings. You can check the box for "Never show this again during boot" (for allowing changes) and it'll show up again during the next boot.
Click to expand...
Click to collapse
This issues will only show up when data can't decrypt.
So I guess you're using Razer official Android 9 ROM, but this build doesn't support Razer official ROM data decrypt yet.
It only support 3rd-party ROM data decrypt such as LineageOS, Pixel Experience, exTHmUI, etc.
jkimrey said:
I'm actually seeing the device now when running "fastboot devices", but when I try to flash the razer image (or any other) I'm getting "fastboot: error: Couldn't parse partition size '0x'". Any suggestions with that? Thanks!
Click to expand...
Click to collapse
try this command
Code:
fastboot boot:raw twrp.img
wubaolong said:
This issues will only show up when data can't decrypt.
So I guess you're using Razer official Android 9 ROM, but this build doesn't support Razer official ROM data decrypt yet.
It only support 3rd-party ROM data decrypt such as LineageOS, Pixel Experience, exTHmUI, etc.
Click to expand...
Click to collapse
Yep, I'm on stock Razer Android 9.
wubaolong said:
This issues will only show up when data can't decrypt.
So I guess you're using Razer official Android 9 ROM, but this build doesn't support Razer official ROM data decrypt yet.
It only support 3rd-party ROM data decrypt such as LineageOS, Pixel Experience, exTHmUI, etc.
Click to expand...
Click to collapse
Which Factory build does this version of TWRP support?
HI Everybody,
I have a Oneplus 8T, European, I installed lineage recovery and Lineage OS 18.1, rooted, but now I would like to reinstall Oxygen 11. Please, can you tell me how to do or where to find the answer?
Please, don't tell me to use TWRP because at moment it's not available for this smartphone.
Thank you All in advance!
You'll need to download the msm recovery tool for your device. Will take it back to new
11mackey11 said:
You'll need to download the msm recovery tool for your device. Will take it back to new
Click to expand...
Click to collapse
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I guess you could try to fastboot flash a full rom zip I think that should work. If not you can just use the MSM tool to restore.
The steps to fastboot flash a full OOS rom zip should be the same as listed in this conversion thread https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/
matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I believe it can fastboot flashed. I just haven't tried it yet. I did see another post where the steps were laid out but remember where I saw it
I am also very interested in the answer to this question. And I think I know why the answer is "use the MSM tool".
Here's how I arrived at that:
If you use payload_dumper to have a look at what gets flashed when installing a rom, there's a number of image files that aren't listed in /dev/block/by-name such as odm, product, vendor and even system(!). This means that you cannot flash them using fastboot and the only way to flash them is via fastbootd (which is in recovery.img).
So the theoretical process is:
- boot into fastboot
- flash boot, recovery, and the other "normal" partitions
- start fastbootd using "fastboot reboot fastboot"
- flash the remaining partitions
- reboot
The problem with OOS is that fastbootd looks very much like recovery: it has no ADB/fastboot connectivity. So you cannot flash the remaining partitions.
Conclusion: the MSM Tool is the only way to return.
Acknowledgment: thanks to @chandu dyavanapelli for the Evolution-X rom installer script which helped me understand what's going on. See https://forum.xda-developers.com/t/...0_r34-evolution-x-passion-22-04-2021.4266067/
I recently updated to MIUI v12.5.1.0.RCDMIXM using a recovery zip through TWRP. A few days later I decided to flash Magisk by patching the boot.img from the same zip and flashed using fastboot.
Everything worked fine until I rebooted to recovery using the Magisk app. Now it's stuck at the TWRP splash screen, can't even reboot or enter fastboot with power and volume buttons because it will always try to boot to TWRP.
What do I need to do to fix this?
This is where I got the TWRP
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
VD171 said:
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
Click to expand...
Click to collapse
Okay, but how exactly can I do that? It's been stuck like this since last night and won't go to fastboot with vol keys..
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Reyproject said:
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
Click to expand...
Click to collapse
Exactly.
You need to bypass EDL auth:
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
Reyproject said:
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Click to expand...
Click to collapse
You said "fastboot", so you need the fastboot ROM.
SP flash tool does NOT need the device to be turned off, it just need to REBOOT.
If you try to flash while a reboot to another reboot, it will works perfectly.
Which magisk did you flash? 23 is not working for 9A
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk V23.0 is the BEST MAGISK EVER !
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Applewubs said:
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Click to expand...
Click to collapse
Are you still in 12.5? Do you also use a custom recovery in that version?
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk v23 works just fine, just patch the boot.img file of your ROM version and flash it with custom recovery or fastboot.
Reyproject said:
Are you still in 12.5? Do you also use a custom recovery in that version?
Click to expand...
Click to collapse
Theres one TWRP that doesnt have a splashscreen, in that one just block and unblock the screen while on recovery and it'll work fine. BUT your internal storage isn't going to be accesible, its encrypted and (for some reason) on 12.5 twrp cant unlock the storage, you'll have to do everything on your sdcard
Reyproject said:
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
Click to expand...
Click to collapse
I thinks its because they cant unlock the storage, they keep trying and just keeps stuck on trying.
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