I am using 6 pro and got a huge problem.
My P6 pro is in fresh status and proceed a new setup with a new Google a/c. No matter in safe mode or normal mode, it always get into recovery mode - "can't load android system". Below picture is the log I capture from recovery mode. Could anybody help me? Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair
We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?
Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)
I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).
Morgrain said:
We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?
Click to expand...
Click to collapse
I did not root or install magdisk to the phone. I just openbox, turnon the phone, everything starts normal, do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
ecuchi said:
Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
I did not root my device. Everything starts normal and i do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once the phone reboots, it goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Alekos said:
I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).
Click to expand...
Click to collapse
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
RetroTech07 said:
I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair
Click to expand...
Click to collapse
No, I did not do any modification. I also try the pixel repair but no use.
jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
I have seen this Scenario hours ago when I try to disable vbmeta to get the corrupted message appearing after booting.
Because I disabled vbmeta flags, wiping is necessary, therefore I choose factory data reset. issue fixed, data lost. that's all
jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.
Alekos said:
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.
Click to expand...
Click to collapse
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?
jozifkwan said:
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?
Click to expand...
Click to collapse
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.
Alekos said:
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.
Click to expand...
Click to collapse
Thank you, I tried your guideline to flash, tick "wipe" and "flash all partitions", flash slot A first and then flash slot B.
The problem is still the same, once I finished the setup, reboot, goes into recovery again and said "cannot load android system"
Beginning to sound like you should exchange it for a new one, unfortunately.
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Sounds like a hardware issue with the NAND.
LLStarks said:
Sounds like a hardware issue with the NAND.
Click to expand...
Click to collapse
I believe it is not the NAMD.
Last night, I test the battery to see if the corruption issue is caused by unstable voltage or ampere. I run drain app + 3D mark, my phone of course heats up but no reboot or unstable issue.
The battery test drained 60% of battery and i manually reboot the phone, no problems or errors and enter system. Then I left the phone in stanby mode for 7 hours. The battery downs to 35% and I reboot the phone again but this time unfortunately goes into recovery issue again.
This is very weired and I couldn't figure out what kind of problem is that.
stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
I am wondering if anyway to skip the recovery or corrupt checking.
stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
you have the corrupt message also? Can you try what I recommended above, updating all 4 Play Services/Play Store Apps/Security Update and Play System Update with Bluetooth disabled?
If not use the Android Flash Tool and wipe the device and flash all slots, let us know if that works.
Related
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kvas said:
I am new to this forum, but have an issue with my Pixel XL that I can't specifically identify, so here I go... I have a Google Pixel XL I purchased from Verizon when they first came out in 2016: (Not sure if the phone is specific to Verizon, was told Google would not let Verizon install thier own firmware). The phone has been pretty good to me. Although I dont think I have had issues with the microphone, Google Hangouts has always been buggy, slow, and crashed. I have kept up the updates, and recently updated to PIE. Google did recommend doing a factory reset over the years which I mistakingly never did due to laziness of not backing up my files. Well, yesterday the unthinkable happened.
While test calling my phone number from another phone, I tried to call Hangouts on my Pixel XL. The phone froze as it usually does. Like a moron I was inattentive and just tried to restart the phone. I got the screen of death that said, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device." I don't want to perform a reset, because I had backup OFF (mistake). It gives me the option to continue, or factory reset. I can't boot into safe mode, but I can go to the screen with the android guy laying on his back, (power button + volume down). Once I select recovery, I get the white screen with google logo, then wait... then I get into the screen with android guy laying on his back with red triangle and exclamation point... Then after holding (Power button then volume up) I can get into the screen with "Reboot system now" "Reboot to bootloader" "Apply update from ADB" "Apply update from SD card" "Wipe data/factory reset" "Mount/system" "View recovery logs" "Run graphics test" "Run locale test" "Power off".... I also downloaded all the files from developers.googledotcom: Factory images, Full OTA images, driver binaries(I think they are correct). Problem is developer mode/usb debugging was not selected at the time of the crash and I obviously cant get into the settings. I am just unclear about which sequence could possibly restore the corrupt file preventing the phone from booting? It seems like I have the necessary usb drivers working, and it seems like my laptop is communicating with my phone while in the command prompt.
I am not very experienced anymore, but I can follow instructions. I just refuse to give up and do a factory reset. I don't care about permanently bricking my phone as it is useless to me with my lost data... CAN ANYONE HELP?? I'm sure there are some forums on here which do explain what to do, but I have searched for a whole day and I cant seem to find a specific one...
RIP 9/11 victims:angel:
Click to expand...
Click to collapse
Pics wont appear in thread from hosting
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
I thought I came across a tutorial somewhere that allows USB debugging to be bypassed
Phalanx7621 said:
Well if you can't get into your system, I'm not sure what choice you have other than to wipe and start again. If USB debugging is off, you can't even pull the files from the phone as far as I know.
Click to expand...
Click to collapse
Is there an option to enable USB debugging mode in recovery or through ADB? I can't even remember if I had debugging mode enabled.... My device was shipped through Verizon in Oct 2016, so it is bootloader locked anyway... It seems to be communicating with my laptop in CMD adp sideload, but Im not 100% sure.
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Thanks for the reply!
altwu said:
it sounds like you can boot into the bootloader and recovery, so you don't need to bother with enabling usb debugging. having usb debugging enabled applies only when the phone is running android. it doesn't affect the recovery or bootloader modes. to verify, boot into the bootloader with power + volume down. you should get the screen with the android guy on his back. connect your phone to a computer via usb, and then run "fastboot devices". fastboot should be in the same folder where adb is. if fastboot returns a device name, it sees your phone and you should be able to sideload a full ota and restore your system. follow step 5 in this guide. [Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery
good luck!
Click to expand...
Click to collapse
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
kvas said:
I read on another recovery thread for "soft bricked" Pixel XLs that it is possible to not wipe the data by modifying the batch file. To my understanding this involves going to the script and editing it by simply deleting "-w", and saving. Can anyone give me confirmation of this? I don't want to wipe my data, but I am also not clear about some instructions I saw on the Google developers site.... It explains how to apply the OTA through cmd prompt if you dont want to wipe data. Conflicts with some information in this forum. Which option is better? Can someone explain the difference? I know OTA means over the air, but why would Google say to apply this instead of the full factory image in sideload ADB. Since I have corrupt file warning preventing me from booting into the home screen I just want to know what the best option is...
Click to expand...
Click to collapse
there are 2 methods to flash android to your phone.
flash the factory image. the factory image zip contains a script that takes care of the flashing. it's basically several fastboot commands. to prevent data from getting wiped, the script needs to be edited to remove the -w option from the last fastboot command. the instructions you've seen that mention this are ones for flashing a factory image. but your bootloader needs to be unlocked to do this. since yours isn't, this isn't an option for you.
flash the ota zip. this is done with an adb sideload command. according to google's ota page(http://developers.google.com/android/ota), "This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." unlike flashing a full factory image, no extra steps are needed to prevent data from getting wiped.
i don't think one option is better than the other. some people here prefer to flash the ota, others prefer to flash the full factory image. i've been going with the factory image route ever since nougat and i can confirm that the script edit needed to prevent a data wipe works. but for you, since your bootloader is locked, you have only one option and that's to flash an ota. the instructions for flashing an ota are on google's ota page that i gave a link to or in the guide i mentioned in my previous reply.
Yup, that explains it. I wasn't clear about the instructions of the OTA method because on the developers site for Google it both talks about sideloading and enabling usb debugging in the options menu. Since I can't access my setting because my phone is soft bricked I have to use sideloader through the ADB. What I am also not clear on is the OTA for my situation. I gathered that the OTA flash was for Pixels that wouldnt take and update in a non-soft bricked phone. At this point I have no choice but to try. I talked to someone at Google and he sat on the phone for over an hour and a half with me helping me research this method. (THANKS GOOGLE))). Although I read that after the last Pie update many peoples phones became bricked so at least it shows they care. I just hope the OTA flash is provisioned for a soft bricked device. But in this business I realize nothing is guaranteed. I just wish I could locate someone who tried this on thier device so they could give some pointers....
We can all agree, if your phone is bootloader LOCKED do not do a factory flash if attempting to retain any data. Editing the script (-W) will only work with a bootloader UNLOCKED device. Long live the Pixel
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
kvas said:
Now this just gets stranger and stranger... I tried loading the OTA file from sideloader. It reads my device just fine (adb devices)... but when I type adb sideloader <space> (filename) it says it cannot locate the file? I copied and pasted the file to the folder wehre adb.exe is. Cannot locate file, but device is located with no issues in the cmd. What am I doing wrong?
Click to expand...
Click to collapse
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
sb1893 said:
1) Is the Full OTA that you downloaded from Google in the same file directory on your computer as ADB.EXE?
2) Are you typing in the file name properly? Might be easier to rename it to something easier / shorter than the default that is downloaded from Google. (or you can drag/drop the file to your cmd window which will cut/paste the file name and proper path)
3) are you using proper syntax? Your sentence above says "adb sideloader <space> (filename)"....but the command is "adb sideload" (not sideloadER)
4) Within your command window, are you in the directory containing your adb.exe and ota.zip? Depending on how you launched the cmd window, you might need to change directory (cd) to the right path/folder...
from Google page:
Run the following command:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Good luck.
Click to expand...
Click to collapse
altwu said:
in addition to what @sb1893 suggested, did you download the correct ota zip file? the latest ota zip is marlin-ota-ppr2.180905.006.a1-34e91bd3.zip. ota zip files for the pixel xl start with marlin-ota. factory images have the word factory as part of the name. if the zip you downloaded has factory in the name and not ota, you have the wrong file. if you have the correct ota zip file, don't touch it. you don't need to unzip it. this zip file is what you will sideload. also verify that the checksum matches the value that google published.
i understand your confusion about enabling usb debugging. the instructions on the google ota page say to enable it but that's only just to be able to run the adb command to reboot into recovery. usb debugging only applies to when the phone is running android. it doesn't affect the recovery or bootloader modes. if your phone is in recovery or bootloader mode and you have the correct device drivers, your computer should be able to see your phone even if usb debugging is disabled. since you can't boot into android, you need an another way to get into recovery mode and that's with power + volume down to get to the bootloader and enter recovery from there.
Click to expand...
Click to collapse
sb1893 said:
And one final thing I forgot to mention. Platform Tools had an update this month...so please make sure you have downloaded and are running the latest versions...
28.0.1 (September 2018) is the latest revision for the Platform tools SDK
Click to expand...
Click to collapse
You guys make the XDA community look good.
kudos to each of you.
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
kvas said:
Update: completed all necessary steps properly (also never actually typed command adb sideloadER before, was just a typo). I am getting a "protocol fault (no status)" when I hit enter. On my Pixel, it says "Must update to adb 1.0.32 or higher" So I located the file here on XDA. I downloaded the file and pasted in the same folder of all the other files. I found I was using the wrong path before. I will try again and see what happens. Still not sure if I extract these files.
UPDATE:
Phone took the sideload OTA just fine. Update was sucessful. Unfortunatley I still cant get into my home screen. It did not work. Still getting screen that says "Your data may be corrupt". We can safely say OTA flash will not fix this type of problem. I should have unlocked the bootloader right when I got the phone. Never again am I purchasing a Google product. Ever again. Time to get a Samsung note 9. I'm sorry, but if you pay 1000 dollars for a phone like I did barely 2 years ago it should not have this problem. Lesson learned: Backup your data to a cloud. Google is still a great company but thier phones are junk. I also had screen burn after less than 1 year, but I have that on my LG v10. Goodbye Pixel, forever.
Click to expand...
Click to collapse
Bummer - that stinks. Sounds like we are close. Out of curiousity - can you post the exact/full text (or a picture if you have a camera or second device) of that screen that shows "Your data may be corrupt"...the only "corrupt" message I am familiar with is from the Bootloader unlocked warning screen. So - want to see what specific error message you are getting.
Sorry again you weren't able to recover your device.
I tried to post a all the pictures I have taken, but the hosting site wont show them. Is there a better way to show the pics?
I just attach pics using the reply screen...Like this....
sb1893 said:
I just attach pics using the reply screen...Like this....
Click to expand...
Click to collapse
Hopefully this works... Google Pixel XL flashing OTA
kvas said:
Hopefully this works... Google Pixel XL flashing OTA
Click to expand...
Click to collapse
So you power up the device and it works on booting for a little while and then immediately drops you into that recovery screen? It doesn't give you a message when the boot fails before launching recovery?
Also - that OTA file looks to be the August 2018 OTA file, not September 2018 - which is what I thought you were trying to sideload...
I did end up flashing the latest OTA.. It let both of them install. I flashed the same one on my phone, then I flashed the newest on on the list of google developers site. PPR2. 180905.006.A1. That is what is has now. I am still stumped as to why it won't work. I'm sure it needs a full factory flash, but I cant do it because its locked. So even if I wanted to recover the files I can't. Even if I could recover the files somehow without further flashing the files would be encrypted and useless. I could either wait to see if another option is available in the future, or factory reset it losing all my precious files. Extremely frustrating. Also, Why didnt google send me a notice about the September update? I never updated this month. Probably why it froze while in Hangouts
Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
Prerequisites:
Service firmware. Can be downloaded here. It's an older build, but it will do the trick and it's the only one I could find freely available at the time of writing. Only for WW SKU
Zip for your desired build. Can be found here.
- Note: For this guide, my desired build will be WW-17.1810.1910.63, which is a special case, as you will need to flash in the following order: Service Firmware -> WW-16.1220.1909.194 -> WW-17.1810.1910.63. In other cases, unless noted otherwise in a description of the build on the ASUS website, Service Firmware -> Desired build will suffice.
Platform tools of Android SDK. Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
This is not required but for the sake of simplicity and keeping everything in one place, create a folder and name it whatever you like, for example ASUS or Unbrick
Create a sub-folder inside the folder you've created in the previous step, call it service_firmware, download and unzip service firmware into this folder
Download files for the desired builds from the above link. For this specific case, WW-16.1220.1909.194 and WW-17.1810.1910.63.
3.a If you have microSD card, transfer zip file for the desired build into its root and insert the card into the phone.
3.b. If you do not have a microSD card, download and unzip platform tools mentioned in the prerequisites as you will need adb to flash firmware/s via sideload
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode via one of the methods:
1.1. Turn off your device, then turn it on while holding down the power and volume up buttons at the same time. Release the power button when it powers up (keep holding the volume up button)
1.2. If you have platform tools, you can do adb reboot fastboot
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices
Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
It is possible to avoid userdata wipe (although not encouraged) but keep in mind, unless you flash your current build after flashing service firmware, your phone will not boot up.
If you absolutely would like to preserve your userdata, even if for the sake of backing it up before doing a factory reset, you have to edit the flashall script in the following way:
Windows: Open flashall.cmd in your favorite text editor, go to line #298 and change it from fastboot -w to REM fastboot -wand save the changes.
Unix: Open flashall.sh in your favorite text editor, go to line #275 and change it from $fastbootcmd -w to #$fastbootcmd -w and save the changes.
Once again, this is not encouraged as it can potentially cause issues later on. You've been warned.
Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Step 3 - Upgrade to your desired build
Enter Recovery mode via one of the following methods:
1.1. If your phone is turned on and USB debugging is enabled, use command adb reboot recovery
1.2. While in fastboot mode, navigate to Recovery Mode using Volume Up/Down buttons and select with a single press of a Power button
1.3. While in fastboot mode, issue one of the following commands : fastboot reboot recovery or fastboot oem reboot-recovery
Once in Recovery Mode, you have 2 ways to proceed:
A: Update from SD card
A.1. Select Apply update from SD card option
A.2. Navigate your SD card and select UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip
A.3. Confirm your choice with a single press of the Power button
A.4. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
A.5. Select Apply update from SD card option again
A.6. Navigate your SD card and select UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip
A.7. Confirm your choice with a single press of the Power button
A.8. Once you're back to the menu of Recovery Mode, select Reboot system now
B: Update through ADB Sideload
B.1. Select Apply update from ADB option
B.2. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip"
B.3. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
B.4. Select Apply update from ADB again
B.5. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip"
B.6. Once you're back to the menu of Recovery Mode, select Reboot system now
Note: Like I've mentioned earlier, these steps are specifically for build WW-17.1810.1910.63. If your target build does not require another build for an update, you can skip steps A.4 to A.7 or B3 to B5
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone with your desired build of firmware.
If you have any questions, do not hesitate to ask.
Cheers.
Hello i've a question (sorry for my bad English). This morning my phone was bricked (red message logo), and with this tuto i remove this logo and i found my original recovery.
But when i want to install firmware from recovery with SDcard option, i've a message no SDcard found and impossible to install firmware. (even after several tries)...
If i reboot my phone i have android logo bootloop...
Can you help me???
https://drive.google.com/file/d/1GStfEgZFpb66JRaAmjeYOKmyn9d8WcPz/view?usp=sharing
https://drive.google.com/file/d/1FSRZfI1vNAyDQDZaLDGrHyiC-lImsYhr/view?usp=sharing
Thank you and Happy New Year...
Thanks for the link to that service firmware!
_Kuroi_ said:
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Cheers.
Click to expand...
Click to collapse
Thanks a lot mate, you made my day!
Please, one question: can you tell me, if both slots (A & B) are flashed by this method?
Thanks!
Thank you so much!
I've wanted to go back to stock for so long, but I haven't been able to find a stock ROM. I've even contacted ASUS support and they couldn't even get it! Thank you so much for the download and for the guide, you've made my week. I'll be smiling every time I use my phone thanks to you!
Great guide. I have a soft bricked device after flashing Lineage 16.0 recovery. Have a boot loop and can't get to recovery. I realise the mistake was flashing the recovery as should have just booted it.
Has anyone else had success with this on a Zenfone 6?
For those who need it; managed to resolve by downloading the stock firmware from Asus, extracting the boot.img and flashing it. Back working.
Didn't try the guide but this is quicker in this scenario if you have flashed a custom recovery to the boot partition. There is no separate recovery partition so this soft bricked the device, overwriting boot with recovery (I followed the guide here for LineageOS which is ill advised) . Should be booting the recovery rather than flashing, or booting into stock recovery and using the installer zip for your custom recovery.
Steps to recover:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
This worked for me, but I'm still in CSC FastBoot Mode and when Android boots, I'm asked to insert a previous pin, which nothing works. Any advice?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
hey, did you manage to fix this? i'm having the exact same problem
sapientsaxonsaboo said:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Click to expand...
Click to collapse
I tried to install latest firmware from
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
everything goes fine but it shows till this moment:
fastboot flash boot_b boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.295s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed for non-official image')
any suggestions ?
kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
Taylor Moon said:
hey, did you manage to fix this? i'm having the exact same problem
Click to expand...
Click to collapse
Try flashing latest image of Android 9 and then flash Android 10
Can somebody please help me with my problem?
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
CVonV said:
Can somebody please help me with my problem?
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
When you connect it to your laptop, go to device manager and check what it is detected as.
_Kuroi_ said:
When you connect it to your laptop, go to device manager and check what it is detected as.
Click to expand...
Click to collapse
I can't seem to find any listing that would correspond to the phone under the Ports section :/
CVonV said:
I can't seem to find any listing that would correspond to the phone under the Ports section :/
Click to expand...
Click to collapse
Maybe upload a screenshot of the devices listing?
_Kuroi_ said:
Maybe upload a screenshot of the devices listing?
Click to expand...
Click to collapse
I thought it would've been listed in the Ports section but it's right at the top under "Android Device" as "Android ADB Interface". I believe I have the correct Qualcomm drivers installed.
Attached screenie also shows device not found when I try an "adb reboot" in command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hmm, I half expected it to be listed as QDLoader 9008, but then it would be under serial ports.
Try fastboot commands instead of adb and also try holding power + vol down for 10-15 seconds
Great guide @_Kuroi_ , I will be trying it out soon. The service rom you are using is pretty old. So I grabbed the last P update service firmware (WW-16.1220.1909.194) and the latest Q build I could get currently (WW-17.1810.2002.133). I have a subscription to one of the paid firmware sites for reasons like this. This way people have more options and it will simplify most people's updating because they can go from the new P service rom to any Q ota. Q firmware doesn't really make sense until it's not being updated anymore but it's here just in case someone finds it useful. If there is some incompatibility in the future or something that requires a newer update I will grab it then. If there isn't I will grab the last firmware once Q is stopped being updated.
WW-16.1220.1909.194
Here
WW-17.1810.2002.133
Here
WW-17.1810.2009.176
Here
Feel free to update your guide to incorporate these all I ask is a credit in the OP for providing it.
After running ./flashall.sh I get the following output:
Done.
target reported max download size of 805306368 bytes
File system type is raw !!!
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'userdata'...
OKAY ( 0.266s)
Sending 'userdata' (1888 KB)...
OKAY ( 0.067s)
Writing 'userdata'...
OKAY ( 0.003s)
Erasing 'metadata'...
OKAY ( 0.027s)
Finished. Total time: 0.799s
Rebooting...
(I changed square brackets to round brackets in the output because otherwise it wouldnt let me post this comment because of bbcode)
I don't seem to have a recovery partition by the end of it and "adb devices" doesn't show me anything.
Does anyone know what might have gone wrong?
Hi guys I know their are threads how to do this but they are all over the place, If you'd like a complete tutorial, that will get your 2020 MOTO G Stylus phone rooted without any errors let me know.
Edit: It looks like people are interested so here goes. The tutorial below is for the 2020 version I tested on Android 10 on two variants. This method once followed correctly will take no more than 30 min tops. Not sure if this will work on updated versions but you could try at your own risk. If this helped you leave a like, if you have any questions let me know.
prerequisites:
PC (duh lol)
Fully Charged Device
Motorola Account (for bootloader unlock purposes)
adb fastboot installed (take note of your folder location especially the platform-tools folder
motorola drivers (link in step 5 if drivers don't install correctly after connecting phone)
Tutorial:
Unlocking bootloader
1. first step is to unlock bootloader(all data will be erased) for this you will need your unlock key
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.
Rooting
1. with bootloader unlocked time to get root. download the latest magisk manager (23 I believe) let it install and power off your phone we will use it later. We will be getting the specific boot image for your device through temporary twrp.
2. go to https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-0.4155041/ and download TWRP credits to @vache. Place the file in your platform-tools folder.
3. enter fastboot mode (by now it should be second nature) and plug into pc, verify fastboot device connected, by opening command window again in platform-tools folder
4. once verified type the following command without the quotes "fastboot boot twrp-3.5.0-0-rav-sofia.img" be patient, when it boots into twrp, cancel any password creation.
5. go to backup and select storage, choose a sd card, do not decrypt or do anything besides what I'm saying here. it will take you back to the beginning after sd card selected as storage, click backup and select only boot at the very top and creat backup. once done go out to twrp main menu and hit reboot, select "reboot system"
6. now to patch boot, open magisk manager and go to install, it will then give you the option to locate and patch boot.img, however we will be going into twrp backup on your sd card and locate boot.emmc.win (not the other two) once selected hit lets go on Magisk and allow it to patch. your patched boot.img will be in a download folder on your internal memory. Copy that file to your computer and then again move it to platform-tools folder
7. power off device and enter fastboot mode for the final time connect to pc, open command window in platform-tools folder and type the following command without the quotes "fastboot flash boot nameofbootfile.img" hit enter and allow to flash, once completed type "fastboot reboot" your device should now reboot, don't worry if it takes slightly longer than usual.
8. finally go into the magisk manager and let it complete its setup, it should reboot one more time and boom, you have root, remember to use magisk hide, That's it all set. If followed correctly this should only take about 30 min to a hour.
Shucks! I thought this was a tutorial.
zapjb said:
Shucks! I thought this was a tutorial.
Click to expand...
Click to collapse
I got you, updated tutorial up. Let me know if it helps.
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm pretty sure a factory reset would restore to 11 not 10. As the 11 update replaced the 10 OS altogether.
Killabee0311 said:
If we have updated to Android 11, such as myself, and want to use the tutorial... Couldn't we just BACKUP (which is needed to root anyways), and do a FACTORY SETTINGS RESET to bring our OS back to Android 10?
Click to expand...
Click to collapse
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.
kgalv419 said:
I'm not sure if a factory reset would take the OS back to 10, you might need to search around for downgrade options. I'd advise anyone not to update to android 11, 10 is great especially with root. I have magisk pass safteynet, and even able to play pokemon go with gps spoof and smali patcher.
Click to expand...
Click to collapse
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11
kgalv419 said:
Ok if you have your unlock code you should still be able to unlock bootloader. However the first thing you need to do is enable your developer options and enable OEM unlock, enable USB debugging and disable automatic updates that should stop updates you can also go on app info when you get the notification and disable notifications for system updates. If you have an unlock bootloader you should be able to root even android 11
Click to expand...
Click to collapse
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.
For downgrading to android 10:
1. Grab the moto flash tool from here
2. Grab the a10 firmware from your device here
3. Unzip the moto flash tool and put the firmware zip in the folder called firmware
4. Plug your device in to your pc in bootloader mode
5. Start the moto flash tool and follow the instructions
(Unlocked bootloader required)
EpicSaga said:
Thank you very much. How do I disable automatic updates and how do I go on app info to disable notifications for system updates? Now a message is on the same screen that says that if I don't restart my phone by the 21st, it will automatically update it.
Click to expand...
Click to collapse
Pretty sure theres a setting in developer options to turn off automatic updates.
ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).
EpicSaga said:
Yes, it's off, and it's been turned off, but I still got a message from Motorola that if I don't restart my phone so that the security patch can update, it will restart automatically on the 21st( a few hours from now).
Click to expand...
Click to collapse
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.
ph4n70m-404 said:
Pretty sure theres a setting in developer options to turn off automatic updates.
Click to expand...
Click to collapse
I already turned it off, but I still got the notification for the update.
ph4n70m-404 said:
I don't know of any solution to this but you should be able to update and keep magisk if you let it do the ota update then use the magisk manager to flash to the other slot.
Click to expand...
Click to collapse
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
EpicSaga said:
I already turned it off, but I still got the notification for the update.
Click to expand...
Click to collapse
I got a notification again today saying that it will update today if It don't do it manually.
EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
Assuming you have a non Verizon or any other oem that blocks unlocking the bootloader follow the steps from the original post:
(step one makes no sense they wrote it kinda weird)
2. go to settings, about phone build # hit a bunch of times to enable developer options
3. once enabled go to developer option enable OEM unlock, disable automatic update (do not update), and enable USB debugging.
4. while phone is on plug into pc to allow drivers to install, also allow usb debugging when prompted. go to where you have adb installed and go in the platform tools folder (this is where I do everything on my phones without errors) hit shift+right click and choose "open command window here" type in "adb devices" without quotes and check if the device is present.
5. now to test if you have fastboot drivers power off phone, then hold power+volume down to enter fastboot mode, plug phone into your computer and repeat step 4 this time typing "fastboot devices" if your phone shows up move on to next step if not download Motorola drivers and install then repeat this step. You can get the driver here and install https://combofile.com/index.php?a=downloads&b=file&id=3396.
6. once your device is detected its time to unlock bootloader, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a sign in and follow the steps, they are simple and straight forward so I won't list them here. Once unlocked restart your phone, set up and proceed to below steps.
EpicSaga said:
I don't have magisk, my phone ia stock. Can I put magisk on my phone without unlocking the bootloader? I need some assistance with unlocking it.
Click to expand...
Click to collapse
you can install magisk manager with bootloader locked but there is no sense in installing it on locked bootloader, because when you unlock your bootloader your devices will be factory reset, if you checked my instructions you will see that magisk manager is needed to patch boot.img that you will get from TWRP backup. You seem a bit green about the whole fastboot process, if that's the case I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.
kgalv419 said:
...I'd advise you to do a little reading up on adb fastboot, which needs to be installed to unlock your bootloader, if you go in blind you can brick your device and I wouldn't want that.
Click to expand...
Click to collapse
Sometimes it's been a couple years between me rooting phones. When I come back to root another phone I read & read & read & read some more here. And I have in case the shtf a back up phone to be safe.
EpicSaga said:
I'm on stock and want to flash this rom. I need to start from scratch. I need to unlock the bootloader, I got the email from Motorola months ago, but haven't had time to figure out how to use fastboot. It's been years since I used it. I'm also on Android 11 and I need to find out how to downgrade to Android 10. Any advice is appreciated.
I have an annoying Security Update that keeps popping up saying that I need to restart my device, and that it only takes 90 seconds. I'm afraid that if I restart my device, the update will install and I won't be able to downgrade to Android 10 from 11, and then I 'll be stuck with this stock rom. Can I disable this pop up?
New Version : RPRS31.Q1-56-9-9 Includes Updates of Android Security Patches through 1 October 2021.
I have not turned iff my device or restarted it since the pop up for the update.
Click to expand...
Click to collapse
Re: bootlock unlock code email
I went on the Lenovo/Motorola website just yesterday and input the long 5-line code from my phone (required) from SDK platform. Once I did this, the website replied that I will receive email with a unique 20-character bootloader unlock code (this is the part you should check again). Instead of getting a code, the email asked that I first "verify my email", so I followed the directions, clicked the link, the link brought me to their website and I was able to verify my account. Once that happened, the page just kinda froze. So I repeated the process and when I clicked the "verify email" button, it brought me again to the website but thus time to my profile page. There was no Bootloader Unlock Code, nor was I emailed the code as assured as I was, as per their website suggests. I repeated the process a 3rd time but the same thing happened. And when I tried to went back #2 + #3 times, I input all the information again, clicked on the "send email" link (where they email you the 20-character code) I never received any additional emails. I only received 1 email (the first time I input this into their website). So, the site will only work 1 time per unique phone (serial). I called customer support and got nowhere! I have Metro by T-Mobile Motorola Moto G Stylus XT2043-4. I hope you see this and please let me know if you are able to unlock or get a email code as promised (or not). And if you have any information on how else to solve this issue, please let me know. I hope this helps & my apologies for being a bearer of bad news. If I solve this issue, I will respond back.
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Did you know that....
The CSC_OXM file is used to restore the internal memory as factory, this will delete all personal data in the phone memory, all applications and data associated with it.
The HOME_CSC_OXM file, on the other hand, will not act in any way on the internal memory. Useful if you want to update while remaining in the same type of ROM. Not recommended if your phone has a Custom ROM installed, as it may not start or give errors in previously installed applications.
If you want to do a clean install of the original ROM, always use the CSC_OMX file!
Click to expand...
Click to collapse
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
Well now you have your Samsung with Original firmware again. Enjoy
ExileTM said:
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
View attachment 5628035
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
View attachment 5629259
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
View attachment 5629261
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
View attachment 5628037
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
View attachment 5629463
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
View attachment 5629465
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
View attachment 5629265
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
View attachment 5628039
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
View attachment 5628043
View attachment 5628045
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
View attachment 5628041
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
View attachment 5629449
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
View attachment 5629493
Well now you have your Samsung with Original firmware again. Enjoy
Click to expand...
Click to collapse
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
RedSpikeJr said:
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Click to expand...
Click to collapse
ExileTM said:
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
Click to expand...
Click to collapse
I followed the full guide, but I got stuck after flashing the firmware in Odin. It shows the screen of "Erasing data", and after that, nothing more
Even after locking again the bootloader
And yes, I ticked what's needed in Odin and used the .pit file
My model it's SM-N975F
The original CSC it's ZTO. Flashed the latest firmware
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
ExileTM said:
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
Click to expand...
Click to collapse
The USB it's the original from Samsung.
The device is 256GB
ExileTM said:
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
Click to expand...
Click to collapse
Tried this already. Didn't work
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
I tried this but not in the process of "Do the format and then do the Odin process" so I can try
I'm trying now with USB OTG to know if I can flash the system.img (and know if from there I can solve this)
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
Tried from reset data on official recovery to doing the change of format in TWRP and the doing all of the process again. No success.
Also tried with USB OTG with system, vendor, product and boot image. Neither
One thing that happened is that when trying to change the system partition to exFAT, it gave an error (system is not mounted) but changed the format to vFAT. Changing it to another option doesn't give that error, so I tried to do with another option and back to ext4.
I don't think it's a physical issue, if turns on, there is some hope at least
There is almost certainly a solution to your problem. (have you tried to do "format data" and typed "yes" in TWRP recovery?). Anyway, it's night at my place now, I'll see tomorrow to think of some other solution.
Tried already. Also tried to format the data with fastboot (Lineage Recovery gives the option to fastboot in Samsung)
I have the exackt same problem with my note10+ with 256GB and dual sim. and the problem you describe is also 100% what i experienced and still have as an issue... If you get to the point where you can solve the issue then please write me my friend. I will do the same ofcourse... btw can you use your pen in TWRP? i can only mark the files but not click them to run...? i have the idea that the TWRP for our model isnt built right somehow..
I assume you haven't solved the problem yet. In these days I have looked around but I have not found much ...
I saw a video, which through the ADB shell a guy was able to find the list of all partitions with the numbers of all the blocks and information and practically managed to rebuild the system partition from scratch, but I don't know if it works on samsung.
This is video:
Then another thing, what procedure did you follow for rooting? You may have had problems during the rooting process.
I followed this guide:
To update the situation
The battery of the phone inflated like a balloon, so I needed to go to a technician. I don't know for sure if that was caused by something physical, but will update when have some news
Ok, let me know if the technician can get you to restart the phone, and out of curiosity, he can bring the knox back to 0.
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
aaaajwedk said:
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
View attachment 5647587
Click to expand...
Click to collapse
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
ExileTM said:
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
Click to expand...
Click to collapse
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
aaaajwedk said:
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
Click to expand...
Click to collapse
OK well. Glad it was helpful. Yes, however, until you root all the apps will work. The only one are some applications by Samsung that will no longer work because they are based on the knox.
Otherwise like Google Pay, all banking and account apps, software updates should work smoothly.
Hi, is this guide usable for the S22 snapdragon version? My device is rooted, and I want to back to original firmware.
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
leathan said:
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Click to expand...
Click to collapse
Sorry, I messed with the reply: it's my previous post.
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course)
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
leathan said:
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
Click to expand...
Click to collapse
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
fux1976 said:
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
Click to expand...
Click to collapse
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
leathan said:
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
Click to expand...
Click to collapse
Phone looks certified, country WW, safetynet passed and upgraded to .160. Only 2 problema left: voice dictation of GBoaed and Android auto not working.
I tried several ways but they didn't solve. Voice dictation worked and then stopped: I guess something interferes... Android Auto app crashes although phone connects to car and is recognised.
Very strange behaviour...
Do you have any idea on how to reflash last .160 zip without twrp? Once installed it gets ignored by system when saved in home directory...
Everything else is working properly.
Isn't Android Auto no more (i.e discontinued).....?
elmor0 said:
Isn't Android Auto no more (i.e discontinued).....?
Click to expand...
Click to collapse
what?!? where did you hear that? It'just something causing problems (compatibility issues with app or setting: magisk, modules, adaway, skipad, disabled system apps and so on). If I could manage to reflash the stock rom it'll work again (I hope)
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
finallau said:
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
Click to expand...
Click to collapse
I only have raw for .143 but I updated to .160*...can I use the previous version or do I get bricked? I don't trust anti roll back mechanism. I can live with this 2 "limitations" waiting for twrp and then be able to flash zip with no hassle.
*I downloaded source code from the Asus site but not sure how to use it (and unzipped is around 10 gb )
Thank you for this! I've been out of the root game for years but noticed with your post that I can hide root from Google Pay and my banking apps, so thinking of trying this. One question though - you mentioned that official updates need to be manually downloaded and the phone re-rooted. Would this wipe the phone each time?
fastboot driver doesnt support win64
Will the phone do a factory reset after unlocking the bootloader?
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
MrKioFLow said:
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
Click to expand...
Click to collapse
Yes, if you unlock the bootloader using the bootloader unlock app (which is a step that is missing in the original post), your phone will perform factory reset.
Troubleshooting
Once you boot into the bootloader with the adb reboot bootloader command, stay on the screen with the green START. Do not navigate to the fastbootd.
Use the side USB port to connect to your computer - not the bottom one.
Run the adb and fastboot commands in Command Prompt as Administrator.
Before you reboot into bootloader, remove Lock screen in Settings.
If you execute fastboot flashing unlock and you got FAILED (remote: 'permission denied'), just ignore it.
It's always better to install the latest updates, then download the firmware to your PC from ASUS Webpage and extract the boot.img and patch it in Magisk in the phone using this tutorial.
Thanks for the guide! Should add that you have to use the side port for fastboot to see the device. Was stuck for a while trying to figure out why neither mac nor pc couldn't find it when it was in bootloader mode - it was because I was using the bottom port lol!
Also if you want to disable verity and verification for the verified boot images, you have to do for both vbmeta.img and vbmeta_system.img. Didn't boot for me until I did that, and had to do an additional factory reset from recovery because of this.