My pixel 3 is not booting up right now. Asks me to do a factory reset. Can I install a custom bootloader like twrp now without losing my data? I want to mount the data partition, backup my files and then do a factory reset. The phone is stock and locked right now, have never installed a custom rom/bootloader on it.
sdxda said:
My pixel 3 is not booting up right now. Asks me to do a factory reset. Can I install a custom bootloader like twrp now without losing my data? I want to mount the data partition, backup my files and then do a factory reset. The phone is stock and locked right now, have never installed a custom rom/bootloader on it.
Click to expand...
Click to collapse
If you are still on Android Pie and have an unlocked bootloader, you should be able to install TWRP. If your bootloader is still locked, you can't install a custom bootloader until you unlock the bootloader. Unlocking it will wipe the phone. If you have Android 10, you can't install TWRP. TWRP does not work on a Pixel 3 with Android 10.
dcarvil said:
If you are still on Android Pie and have an unlocked bootloader, you should be able to install TWRP. If your bootloader is still locked, you can't install a custom bootloader until you unlock the bootloader. Unlocking it will wipe the phone. If you have Android 10, you can't install TWRP. TWRP does not work on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
Thanks, I'm on 10 and unlocked :/
sdxda said:
Thanks, I'm on 10 and unlocked :/
Click to expand...
Click to collapse
What happens when you boot to recovery mode? You might have to wait a really long time (30 to 60 minutes) for it to recover.
If that doesn't work, and you enabled USB debugging when you unlocked the boot loader, you should be able to flash a factory image. Be sure to edit flash-all.bat (or flash-all.sh if on Linux) to remove the -w from the flashboot command at the bottom of the file. Removing the -w will prevent it from wiping your data. Be sure you execute the edited file, and not the original file. Also, be sure to get the factory image, not an OTA image, and to download the latest platform-tools. This thread is a good guide to follow to flash the image. https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
I'd try to flash an Android 10 image and recover the data instead of trying to downgrade to Android Pie and install TWRP.
dcarvil said:
What happens when you boot to recovery mode? You might have to wait a really long time (30 to 60 minutes) for it to recover.
If that doesn't work, and you enabled USB debugging when you unlocked the boot loader, you should be able to flash a factory image. Be sure to edit flash-all.bat (or flash-all.sh if on Linux) to remove the -w from the flashboot command at the bottom of the file. Removing the -w will prevent it from wiping your data. Be sure you execute the edited file, and not the original file. Also, be sure to get the factory image, not an OTA image, and to download the latest platform-tools. This thread is a good guide to follow to flash the image. https://forum.xda-developers.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269
I'd try to flash an Android 10 image and recover the data instead of trying to downgrade to Android Pie and install TWRP.
Click to expand...
Click to collapse
Recovery mode is fine. I sideloaded the latest ota 10.0.0 (QP1A.191105.003, Nov 2019).. it's 1.3 gigs. Still didnt help. Should I try an older OTA version before trying the factory image?
And my bootloader is locked, so can I flash the factory image? I'm getting the image now and will try anyways, just not sure if I want to try an older OTA first.
sdxda said:
Recovery mode is fine. I sideloaded the latest ota 10.0.0 (QP1A.191105.003, Nov 2019).. it's 1.3 gigs. Still didnt help. Should I try an older OTA version before trying the factory image?
And my bootloader is locked, so can I flash the factory image? I'm getting the image now and will try anyways, just not sure if I want to try an older OTA first.
Click to expand...
Click to collapse
okay so can't flash without unlocking. Going to try an older ota.
sdxda said:
okay so can't flash without unlocking. Going to try an older ota.
Click to expand...
Click to collapse
I don't think an OTA will fix a boot problem. According to https://developers.google.com/android/images you have to unlock the bootloader to flash a factory image. Unlocking the bootloader will wipe your data. I'm not sure the unlock command will work if you have not enabled OEM unlocking in Developer Options.
Sorry, I don't see any way to preserve your data. Maybe someone smarter than me will have some ideas.
Related
hi
had a pixel for about 8 months now, in the past i'd normally always root my device and load a custom rom (i liked tweaking DPI), didnt have to do that on the pixel, so never bother rooting etc, although i did unlock the bootloader, and then put the custom recovery in the too hard basket since it involved booting it from fastboot, ended up couldnt be bothered
i've recently loaded the Oreo update (signed up for beta releases), and since then, battery has been draining, friend of mine had the same issue, he factory resetted, and he reckons all is good now.
i'd like to take it a step further and perform a full wipe/reflash
is there a guide somewhere, that steps through performing a full wipe, and reload of a factory image?
can i do it all without unlocking/rooting?
You put custom recovery on?
Then you are already unlocked (bootloader)
You can directly flash-all (probably safely) the latest factory image available for your Pixel (search google for "Pixel google factory images"
You probably want to wipe everything and start over, so don't edit the flash-all file.
There are guides in the "Guides" section. It is a lot to write out every step. Make sure your Android SDK is up to date
Sent from my sailfish using XDA Labs
I have no custom recovery, if I unlock the bootloader and run flash-all will that do a full wipe ? I can see in the Shell script fastboot is called with -w, does that mean wipe?
gjw00 said:
I have no custom recovery, if I unlock the bootloader and run flash-all will that do a full wipe ? I can see in the Shell script fastboot is called with -w, does that mean wipe?
Click to expand...
Click to collapse
The -w tells it to do a full wipe. So, yes, running the flash-all will do a full wipe. I know you want to do a clean install but, just so you know,if you ever want to do an upgrade without wiping, simply remove that -w, save the file and run it. The result would be an upgraded phone with data fully intact.
I don't even know why I wanted to root my phone. I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img and the twrp installer .zip, I get this message saying
"Unmodified System Patition
Keep System Read only?
..."
and I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Have I bricked my phone? Is there any way for me to go back?
Thanks for the advice.
That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock
scp-507 said:
I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Click to expand...
Click to collapse
You cared enough at one point to start the process. Whether to root or not is a personal decision, based on what types of added modifications of features you want out of root, and how important those are to you. Maybe you have changed your mind to that point. And I am biased to my own opinions. But that opinion would be to go ahead and finish the job, since you got this far. Nothing wrong is going on really, you just got stuck, not knowing what to do next. It does happen from time to time, when modding these devices. And nothing to get discouraged about. You did the right thing coming onto the forum and asking before doing something you were unsure about.
scp-507 said:
Have I bricked my phone? Is there any way for me to go back?
Click to expand...
Click to collapse
This is pretty hard to brick. Unlocking the bootloader, flashing TWRP, and root likely will not result in a real brick. Even if you brick the phone, there is an unbrick tool that will mostly likely get it up and running again.
scp-507 said:
I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img
Click to expand...
Click to collapse
It's not necessary any longer to flash the patched boot.img in order to root. Follow the "Recommended" install method from the TWRP thread, which is simple and straightforward. It's pretty much what the previous response outlined above.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
The method you are following (flashing a patched boot.img) does work. But it has more steps. And you have to be careful to flash the correct boot.img for your OOS version. Otherwise, you may have some issues. So going with the easier method is better, in my opinion.
djsubterrain said:
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
Click to expand...
Click to collapse
Is that true for all phones?
If you have the Global OP7Pro and not the T-mobile variant you don't have to be afraid of bricking the phone. The MSM unbrick tool can bring your device back to stock if its bricked or even if its not. I am not sure if the MSM tool works on the T-mobile variants, but it might.
I've hard bricked this device and successfully used the tool to recover it.
djsubterrain said:
That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock
Click to expand...
Click to collapse
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?
scp-507 said:
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?
Click to expand...
Click to collapse
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Well if you relock your bootloader you won't be rooted or have TWRP... It will also wipe all of your data like starting over when you got the phone out of the box.... If you want to stay rooted and use twrp you will have to deal with the splash screen all of us see it on our phones also. Basically you need to have the bootloader unlocked to keep root and have TWRP
scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
You can't relock your bootloader, you currently do not have the default recovery partition, if you really want to relock your bootloader you would need to flash the stock rom back over itself so it replaces the recovery with the default one. Then you can run "fastboot oem lock" but be aware, as I said before, this will want to wipe your data so the rom will go back to default setup. Remember to disable bootloader unlocking from the developer settings if you do, then you will be back to the default stock rom state.
scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
If you want root, you need to leave the bootloader unlocked. That is normal, and just how it is. The warning screen is just something to live with.
You need to return to full stock (ROM, boot.img, recovery) in order to relock the bootloader (otherwise you will get a bootloop or no boot). Which of course defeats the purpose of rooting the phone. So again, having the bootloader unlocked is the normal and expected state, when you are rooted.
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
sydsick42069 said:
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
Click to expand...
Click to collapse
You can't flash TWRP from adb on DP3
:/ gives error command
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
So as said before use the msm download tool and start over
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
sydsick42069 said:
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
Click to expand...
Click to collapse
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Virus1x said:
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Click to expand...
Click to collapse
I'm not sure where you got that info, but it's definitely wrong.
Tmobile has a standard unlocking procedure, or you can utilize something like this or this if your device is not paid off yet.
However... if you are attempting the dp3 unlock method found here, and as of right now you are still locked, its because you skipped the actual unlock procedure. Which is literally steps 1 & 2 in this guide, attached in the previous dp3 unlock guide.
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
Step 1- Download the file in the original post, create a folder somewhere you know where it is and extract the downloaded files to that folder
Step 2-Turn off your OP7 Pro
Step 3-Open the folder you created and right click on MsMDownloadTool V4.0.88.exe and select run as administrator, Once open uncheck sha256 check.
Step 4-Plug the Original USB cable that came with your phone into the phone.
Step-5-Hold the Power/Volume up/Volume down button until you see Connected in MsMDownloadTool, the instant you see Connected press start. You only have 5 seconds before it's too late so be quick.
Step-6 Once you see "Download Complete" in green in the Status of Communication box in MsMDownloadTool the phone will automatically reboot and you should have the TMobile splash screen and be able to set the phone up through the set up Wizard.
If you want to use Android 10 with service working on your T-Mobile 7 Pro you NEED to be SIM unlocked.
sydsick42069 said:
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
Click to expand...
Click to collapse
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
redpoint73 said:
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
Click to expand...
Click to collapse
"From that point" would have been 9.5.3 international not 10, and I was assuming he was already carrier unlocked.
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
JWnSC said:
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
Click to expand...
Click to collapse
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
sydsick42069 said:
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
Click to expand...
Click to collapse
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
JWnSC said:
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
Click to expand...
Click to collapse
Exactly, like why go through the trouble of using certain methods of upgrading, etc. to avoid relocking If you can just go to one of the unlocking threads on xda, or just talk to TMobile support on Twitter and get sim unlocked. Like the whole process took me 30 minutes and now I don't have to worry about it because it's officially unlocked. Like, I've had my **** in a boot loop a few times, and being able to msm all the way back to stock and reunlock etc is extremely useful.
Virus1x said:
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Click to expand...
Click to collapse
Download something called "minimal adb and fastboot" (don't have the link handy) and use that fastboot to do the following:
fastboot getvar current-slot
Whichever slot it shows, a or b, you want to switch to the other. So if it says the current slot is A, you would type
fastboot --set-active=b
And if it says slot B, then you want to set A as active slot. Then after it successfully changes slots
fastboot reboot-bootloader
Now when you're back to the fastboot screen after your phone reboots, the fastboot boot command on your twrp img should work fine.
Sent from my OnePlus7Pro using XDA Labs
I spent all day trying to find a way to root my phone after moving from Lineage OS to Oxygen OS 10.01. Namely, https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853.
The problem is that the information given is out of date as of a few days ago, and installing the patched bootloader broke wifi, calling, and probably all sorts of other things.
I want to make sure this is as simple as possible for people having the same issues!
Before You Download
You MUST be running Oxygen OS 10.01 exactly.
You MUST be on a OnePlus 6 (not a OnePlus 6T)
You MUST have an unlocked bootloader (Google for instructions, "fastboot oem unlock", this will require a factory reset)
Install ADB and Fastboot on your computer (Google for instructions)
Installation Instructions
Make sure you're running Oxygen OS 10.01 for the OnePlus 6. If you're on an earlier version and need to install, download HERE and install it as a local upgrade (Google for instructions).
Download and install Magisk Manager. I'm using Version 7.40.
Download my modified boot image here
Put your OnePlus 6 in Fastboot mode and plug it into your computer (Google for instructions)
Place my boot file, new_boot_image_xda.img, in the same folder Fastboot is running
Run fastboot flash boot new_boot_image_xda.img
Run fastboot reboot or otherwise reboot your phone.
If you want to do this on other devices:
Extract boot.img from your ROM's zip file's payload.bin using Payload Dumper 64 (I can't post external links, Google it)
Place boot.img in your phone's local storage
Open Magisk Manager on Android, then "Install Magisk" -> "Patch a File" -> select boot.img
Move the modified boot image (magisk_patched.img) to your computer
Enter the fastboot commands from above, replacing new_boot_image_xda.img with your modified boot image
May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.
jacdelad said:
May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.
Click to expand...
Click to collapse
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.
mouthofrandom said:
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.
Click to expand...
Click to collapse
Nah, no problem. I have this phone since it came out and use custom ROMs since then, do not really new. I know that unlocking the bootloader resets my phone. I was just wondering if I can install your image without unlocking, because I'm currently locked (had a problem with the latest Syberia update and choose to stay with OOS). And how to update when OOS 10.0.2 arrives.
I tried it and it worked fine, but today after uninstalling some blotware and rebooting I am stucked on the bootloader warning page which takes me to the fastboot mode after a minute or so (this is what used to happen to me whenever I flash a magisk patch boot file) Now I'm downloading the stock rom to get the stock boot.img.
This one video is for oneplus 6t
Pretty clean guide
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