[FASTBOOT] How to Flash Fastboot Firmware - Asus ZenFone Max Pro M1 Guides, News, & Discussio

Make sure you’ve backed up all of your IMPORTANT DATA before flashing FASTBOOT ROM because this process WILL DELETE ALL OF YOUR IMPORTANT DATA !
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
This process will not void the device warranty & you will get OTAs
First and foremost, please install ZenFone Max Pro M1 Drivers via Device Manager (Download drivers on ASUS Support Website)
1) Download RAW Firmware
15.2016.1805.309
15.2016.1805.311
15.2016.1805.318
15.2016.1808.326
15.2016.1808.327
2) Download & Install ASUS Flash Tool : Link
3) Open ASUS Flash Tool and connect your device to PC in FASTBOOT Mode (Power + Volume Up)
4) Select your device model, RAW firmware and your device's serial number.
5) Hit Start and wait 5 - 10 minutes
Congratulations, you have flashed RAW firmware successfully

Bro This Settings Developer Options & MTP Not Enabled In Asus Zenfone Max Pro M1 Working Or Not Device Is Locked With Password
Only Fastboot Mode Working Or Not

Kiran02 said:
Bro This Settings Developer Options & MTP Not Enabled In Asus Zenfone Max Pro M1 Working Or Not Device Is Locked With Password
Only Fastboot Mode Working Or Not
Click to expand...
Click to collapse
What are you trying to say?

DatBoiii said:
Make sure you’ve backed up all of your IMPORTANT DATA before flashing FASTBOOT ROM because this process WILL DELETE ALL OF YOUR IMPORTANT DATA !
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
This process will not void the device warranty & you will get OTAs
First and foremost, please install ZenFone Max Pro M1 Drivers via Device Manager (Download drivers on ASUS Support Website)
1) Download RAW Firmware
15.2016.1805.309
15.2016.1805.311
15.2016.1805.318
15.2016.1808.326
15.2016.1808.327
2) Download & Install ASUS Flash Tool : Link
3) Open ASUS Flash Tool and connect your device to PC in FASTBOOT Mode (Power + Volume Up)
4) Select your device model, RAW firmware and your device's serial number.
5) Hit Start and wait 5 - 10 minutes
Congratulations, you have flashed RAW firmware successfully
Click to expand...
Click to collapse
I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down".

Thanks for the firmware...

not working
Utsav_vats said:
I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down".
Click to expand...
Click to collapse
DatBoiii said:
Make sure you’ve backed up all of your IMPORTANT DATA before flashing FASTBOOT ROM because this process WILL DELETE ALL OF YOUR IMPORTANT DATA !
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
This process will not void the device warranty & you will get OTAs
First and foremost, please install ZenFone Max Pro M1 Drivers via Device Manager (Download drivers on ASUS Support Website)
1) Download RAW Firmware
15.2016.1805.309
15.2016.1805.311
15.2016.1805.318
15.2016.1808.326
15.2016.1808.327
2) Download & Install ASUS Flash Tool : Link
3) Open ASUS Flash Tool and connect your device to PC in FASTBOOT Mode (Power + Volume Up)
4) Select your device model, RAW firmware and your device's serial number.
5) Hit Start and wait 5 - 10 minutes
Congratulations, you have flashed RAW firmware successfully
Click to expand...
Click to collapse
this method not work even after the successfull process is done. At last the window shows the download pass message but when i restart i boot normal to old rom.

i was not getting the model ZB601KL.. What should i choose ?

App just won't open
How to fix that?
Win10 1809 AMD E1?

Utsav_vats said:
I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down".
Click to expand...
Click to collapse
i reckon you have AMD RYZEN CPU? try using usb 2.0 port

339
https://www.androidfilehost.com/?fid=1395089523397911199
Sent from my ASUS_X00TD using Tapatalk

kumeipark said:
339
https://www.androidfilehost.com/?fid=1395089523397911199
Sent from my ASUS_X00TD using Tapatalk
Click to expand...
Click to collapse
Error regarding platform.txt

SonOfSparda said:
Error regarding platform.txt
Click to expand...
Click to collapse
Flash with AFT.
I don't face any issue with AFT
Sent from my ASUS_X00TD using Tapatalk

kumeipark said:
Flash with AFT.
I don't face any issue with AFT
Click to expand...
Click to collapse
Giv download link

Kali Linux said:
Giv download link
Click to expand...
Click to collapse
https://forum.xda-developers.com/asus-zenfone-max-pro-m1/how-to/how-to-asus-flash-tool-aft-t3923941
Sent from my ASUS_X00TD using Tapatalk

Please provide fastboot flashable rom for pie version , as my phone has "device corrupted" error on pie firmware

The link you've provided above doesn't seem to work . Can you provide a new link which will give me the flash tool

Related

Bricked Mi3 - Showing QHUSUB Bulk in PC

I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Don't worry have you backup you data?
if you have, just install the driver for qhusb
then your phone should be able to recognises by MIflash then flash any fastboot rom, You phone should be good to go.
I had a similar issue but i tried to hold the power button for like 30 seconds and the phone booted. If it didn't work, you should follow this thread: en.miui.com/forum.php?mod=viewthread&tid=73348&highlight=Mi3%2Bunbrick&mobile=no
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
murattiy said:
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
Click to expand...
Click to collapse
Did you personally tried that? Because flash all bat do uses fastboot to flash, which can't be accessed.
I wonder whether the other one u poster doesn't use fastboot, cant check the file content atm
I have tried many times
last times tried 3 hours ago, for alpha 5.12.24
my video under explain
http://m.youtube.com/watch?v=fSl9xrR_J4g
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
you need to do İnstall spacial flash_all.batt change to in flash_all.batt "cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global"
dont use miFlash .. enough u clik speical flash_all.batt
If your device not boot into fastboot/recovery mode press power button for around 30-40 seconds .
and still not boot into fastboot/recovery mode
battery cable exist than try.. i tried many times))
Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Prince Chandela said:
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
coolkillermax said:
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Click to expand...
Click to collapse
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
回复: Bricked Mi3 - Showing QHUSUB Bulk in PC
Prince Chandela said:
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
Click to expand...
Click to collapse
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
coolkillermax said:
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
Click to expand...
Click to collapse
flash miui fastboot rom then
Prince Chandela said:
flash miui fastboot rom then
Click to expand...
Click to collapse
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
coolkillermax said:
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
Click to expand...
Click to collapse
can you boot in recovery now?
Prince Chandela said:
can you boot in recovery now?
Click to expand...
Click to collapse
No...
http://forum.xda-developers.com/xiaomi-mi-3/help/mi3w-lost-partition-userdata-img-t3293583
Me_Ashish_ said:
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
Click to expand...
Click to collapse
Really need your help..
Can you explain it further?
please..

UNLOCK Bootloader Zenfone 5z APK from ASUS Website

Hi Guys,
I found this file for unlocking the boot loader officially from the ASUS website, It can unlock the boot loader after the latest update too.
Please note
If you unlock your boot loader you will not be able to get OTA update but you can download and update your phone manually.
Also your warranty will be void.
Your Data (Storage) and phone data will be fully gone so please take a backup.
Try at your own risk!
Dear fusioncoast - can you please link us to the page on the Asus website where you downloaded the tool from?
https://www.asus.com/Phone/ZenFone-5Z-ZS620KL/HelpDesk_Download/
You need to select android as os on the page for the download to become visible.
Hey, you can;t get to the helppage for the 5z anymore I noticed, and this unlock tool just gives me an error (something about network).
Any other way to unlock the bootloader? Or maybe newer version is needed?
Anyone?
hgoor said:
Anyone?
Click to expand...
Click to collapse
Same like Me, and no anyone reply
Yeah that sucks. The phone is still perfect bit now just lying around
hgoor said:
Yeah that sucks. The phone is still perfect bit now just lying around
Click to expand...
Click to collapse
alisyahbana said:
Same like Me, and no anyone reply
Click to expand...
Click to collapse
Ok, so I ran in the same problem. I eventually bricked my phone (not totally, fastboot was still accesible) so I tried to flash this original Asus ROM back.
Everything was fine, the phone worked as original with Android 10.
But then I noticed that when I run the script of the file that I posted above, the state of my phone was unlocked for a couple of seconds, so I imediately closed the command prompt in Windows when that happend (after the script has rebooted the phone once) and it remained unlocked. Then I have proceeded with this guide and it worked like a charm, I have succesfully installed ArrowOS 13 back on my phone without Official Asus Unlocking tool APK.
STEPS FOR UNLOCKING BOOTLOADER WITHOUT ASUS APK
(IT WORKED FOR ME, I DO NOT TAKE ANY RESPONSABILITIES FOR ANY DAMAGE THAT MAY OCCURE)
Please back up any file before proceeding the steps. THEY DO REMOVE USER DATA!
1. Download this: SCRIPT_ASUS_ORIGINAL_UNBRICKING
2. Unzip it, and run flashall_AFT.cmd while in FASTBOOT mode (power+vol up).
Leave it still until is complete (let the script execute itself completly!! It may brick device if disconnected at wrong time)
3. Let the phone start until Welcome screen. You should see original Asus first time boot.
4. Go back in fastboot mode (power+vol up)
5. Run the script again but when you see that the phone is restarting and started back in fastboot with state UNLOCKED imediately close the command prompt window from the computer.
It may brick the device if disconnected at wrong time.
Disconnect it just at the right time as I said (after first reboot in fastboot + on the screen should say state UNLOCKED).
It's better to leave the script run itself again completly if you missed the first restart and repeat the process from step 4 again.
6. Now, the bootloader is unlocked, you can follow normal process: NOOB GUIDE
Please let me know if it worked for you too.
Thanks I will try it: if it doesn't work or brick my phone it's too bad I'll just have it recycled..
hgoor said:
Thanks I will try it: if it doesn't work or brick my phone it's too bad I'll just have it recycled..
Click to expand...
Click to collapse
Awesome. You are welcome! Please let me know if it worked for you too. I used latest TWRP (3.7.0) and ArrowOS 13 Official as the CustomROM.
MrBluie_ said:
Awesome. You are welcome! Please let me know if it worked for you too. I used latest TWRP (3.7.0) and ArrowOS 13 Official as the CustomROM.
Click to expand...
Click to collapse
I'll check that rom out too. Probably going to be this weekend or so.. but many thanks so far!
A new method to unlock bootloader without ASUS APK
Here is a factory ABL (aka bootloader) image file from Android 10 user raw package, it will make bootloader unlock untill flash back to the stock file.
1. download the attach file (ZS620KL_unlock_bootloader.zip)
2. reboot zenfone 5Z to fastboot mode
3. extract the zip file
4. make sure bootloader driver is properly installed and recognized in windows
5. execute 'flash_abl.bat' (it will wipe userdata after that!!!)
6. now your device is bootloader unlocked
hgoor said:
Thanks I will try it: if it doesn't work or brick my phone it's too bad I'll just have it recycled..
Click to expand...
Click to collapse
Did it work?
DemonsterNoob said:
Did it work?
Click to expand...
Click to collapse
Not have yet time for it. Will try today...
sabpprook said:
A new method to unlock bootloader without ASUS APK
Here is a factory ABL (aka bootloader) image file from Android 10 user raw package, it will make bootloader unlock untill flash back to the stock file.
1. download the attach file (ZS620KL_unlock_bootloader.zip)
2. reboot zenfone 5Z to fastboot mode
3. extract the zip file
4. make sure bootloader driver is properly installed and recognized in windows
5. execute 'flash_abl.bat' (it will wipe userdata after that!!!)
6. now your device is bootloader unlocked
Click to expand...
Click to collapse
I must be missing something because all it says is waiting for any device...
I also get a message waiting for device.
How do I get the batch file to run?
However, it worked, I just had to reinstall the drivers,
Thanks
There doesn't seem to be a way to unlock the bootloader for the moment.
MrBluie_ said:
Ok, so I ran in the same problem. I eventually bricked my phone (not totally, fastboot was still accesible) so I tried to flash this original Asus ROM back.
Everything was fine, the phone worked as original with Android 10.
But then I noticed that when I run the script of the file that I posted above, the state of my phone was unlocked for a couple of seconds, so I imediately closed the command prompt in Windows when that happend (after the script has rebooted the phone once) and it remained unlocked. Then I have proceeded with this guide and it worked like a charm, I have succesfully installed ArrowOS 13 back on my phone without Official Asus Unlocking tool APK.
STEPS FOR UNLOCKING BOOTLOADER WITHOUT ASUS APK
(IT WORKED FOR ME, I DO NOT TAKE ANY RESPONSABILITIES FOR ANY DAMAGE THAT MAY OCCURE)
Please back up any file before proceeding the steps. THEY DO REMOVE USER DATA!
1. Download this: SCRIPT_ASUS_ORIGINAL_UNBRICKING
2. Unzip it, and run flashall_AFT.cmd while in FASTBOOT mode (power+vol up).
Leave it still until is complete (let the script execute itself completly!! It may brick device if disconnected at wrong time)
3. Let the phone start until Welcome screen. You should see original Asus first time boot.
4. Go back in fastboot mode (power+vol up)
5. Run the script again but when you see that the phone is restarting and started back in fastboot with state UNLOCKED imediately close the command prompt window from the computer.
It may brick the device if disconnected at wrong time.
Disconnect it just at the right time as I said (after first reboot in fastboot + on the screen should say state UNLOCKED).
It's better to leave the script run itself again completly if you missed the first restart and repeat the process from step 4 again.
6. Now, the bootloader is unlocked, you can follow normal process: NOOB GUIDE
Please let me know if it worked for you too.
Click to expand...
Click to collapse
Worked like a charm for me ....... thanks a bunch for sharing this buddy ...... I am up and running with Arrow OS Android 13 on my Zenfone now ..... cheers
arkanoids said:
Worked like a charm for me ....... thanks a bunch for sharing this buddy ...... I am up and running with Arrow OS Android 13 on my Zenfone now ..... cheers
Click to expand...
Click to collapse
I couldn't do the process because my computer is Linux. I doing it from Windows, is there any need for a driver or something like that?
jak0n said:
I couldn't do the process because my computer is Linux. I doing it from Windows, is there any need for a driver or something like that?
Click to expand...
Click to collapse
You should have the adb platform tools for windows, connect your phone via usb and if you see phone's serial number as output for adb devices .... you are good to go, download the zip from above, follow the steps, for sure your Zenfone 5z would be unlocked ...... I had the latest firmware from asus website installed on my phone.

[Nokia 1] Guide on acquiring root on Android 10 Stock ROM

Hey everyone, I no longer have this device, but, I guarantee that these steps will work and not brick your device if you follow them correctly!
PC side:-
1) Download the latest OTA update of android 10 for the Nokia 1 from here
https://android.googleapis.com/packages/ota-api/package/8f064e008ca0bb6616e4506f9c9c0f1d68257347.zip
2) Extract this file and you should see quite a few images, then copy the boot.img to your desktop for safety
Nokia 1 side:-
1) Update your Nokia 1 to the latest os either from the system update in settings or just copy over the .zip file we downloaded to a micro sd and apply the update from recovery
2) after you are on the latest update and no other updates are available, download the magisk canary apk from magisk GitHub and then install it
3) After that, copy the boot image we extracted earlier from the pc to the phone, then patch the copied boot image
4) After it's done flashing copy the patched image (from Downloads) to your pc
5)
PC side:-
1) Load any of the scatter files you have for the Nokia 1, the one from the stock rom is recommended
2) Load it in SP Flash tools
3) After that uncheck everything except the boot partition to be flashed
4) You will see a path of where the stock boot image is loaded from, if you click on it, a window will open asking you to select the boot image
5) select the patched boot image we copied to the pc earlier
and clock select
6) then click on the download button
Nokia 1 Side:-
1) Hold both volume up and volume down buttons together and connect it to your PC
PC side:-
1) It will begin flashing the boot image and will display a success message
Nokia 1 side:-
After it flashes successfully turn your device on and open magisk app, there it should say that magisk is installed
Credits to @GuyGotMadNameGame for the inspiration!
Reserved
Reserved!
Method mentioned in the OP worked 100% for me! Thanks for the amazing tip
I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.
linuxteddy said:
I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.
Click to expand...
Click to collapse
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device
Hausemaster said:
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device
Click to expand...
Click to collapse
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.
linuxteddy said:
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.
Click to expand...
Click to collapse
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build
Hausemaster said:
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build
Click to expand...
Click to collapse
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.
linuxteddy said:
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.
Click to expand...
Click to collapse
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...
Hausemaster said:
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...
Click to expand...
Click to collapse
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?
linuxteddy said:
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?
Click to expand...
Click to collapse
Transfer by Sd card is the safest
Hausemaster said:
Transfer by Sd card is the safest
Click to expand...
Click to collapse
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!
linuxteddy said:
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!
Click to expand...
Click to collapse
No problem, hope you have fun!

Question Help with Unbricking OnePlus 10 Pro (NE2213)

My Phone is bricked during the updation with fastboot enhance tool so now my phone is in powerd off state not working with button combination even no detection with my laptop please help me if anyone have or know the solution
Well i can maybe suggest you this there is a lot of help in this group if you need too maybe they can find out a solution for you
┤Mod Edit├┤Telegram link removed as it did not meet posting requirements├
Khalid Ghouri said:
My Phone is bricked during the updation with fastboot enhance tool so now my phone is in powerd off state not working with button combination even no detection with my laptop please help me if anyone have or know the solution
Click to expand...
Click to collapse
i have same problem
Khalid Ghouri said:
My Phone is bricked during the updation with fastboot enhance tool so now my phone is in powerd off state not working with button combination even no detection with my laptop please help me if anyone have or know the solution
Click to expand...
Click to collapse
What happened where did it go wrong?
Johnstan725 said:
What happened where did it go wrong?
Click to expand...
Click to collapse
when flash payload.bin, i got an error ''the following partition to flash may be unknown'' than i check the option ''ignor unknown partitions'' after complete the flashing payload.bin my phone bricked and no battery life !
Well I want to help so I copied and paste Theo from the oneplus 10 pro group on telegram what i posted here i hope this tutorial might help you
I didn't make this tutorial so if this works join the group and thank @docnok63 i don't know if this is also his XDA name if so then you can thank him on XDA
With an unlocked bootloader, Fastboot Enhance allows you to flash stock OOS without relocking the bootloader like MSM. It can also be used to downgrade your OS without losing data. To use it, download it from Github and:
1) Put the phone in fastboot mode and connect to PC
2) Launch the Fastboot Enhance app and double-click your connected device
3) Click the “Reboot to Fastbootd” button
4) Once in fastbootd, click the Flash Payload.bin button. If you get a warning about cow files, ignore and hit the Yes button
5) Select the FULL OTA.zip of your choice (incremental patches not allowed.)
6) The app will extract the payload.bin from the full zip and begin flashing automatically. Do NOT touch your device or close the app during this time or you risk bricking your device
7) Once done flashing, you will get a “Operation completed” dialogue box. Hit Okay and then hit the “Reboot to System” button. Profit.
HessNL said:
Well I want to help so I copied and paste Theo from the oneplus 10 pro group on telegram what i posted here i hope this tutorial might help you
I didn't make this tutorial so if this works join the group and thank @docnok63 i don't know if this is also his XDA name if so then you can thank him on XDA
With an unlocked bootloader, Fastboot Enhance allows you to flash stock OOS without relocking the bootloader like MSM. It can also be used to downgrade your OS without losing data. To use it, download it from Github and:
1) Put the phone in fastboot mode and connect to PC
2) Launch the Fastboot Enhance app and double-click your connected device
3) Click the “Reboot to Fastbootd” button
4) Once in fastbootd, click the Flash Payload.bin button. If you get a warning about cow files, ignore and hit the Yes button
5) Select the FULL OTA.zip of your choice (incremental patches not allowed.)
6) The app will extract the payload.bin from the full zip and begin flashing automatically. Do NOT touch your device or close the app during this time or you risk bricking your device
7) Once done flashing, you will get a “Operation completed” dialogue box. Hit Okay and then hit the “Reboot to System” button. Profit.
Click to expand...
Click to collapse
1) Put the phone in fastboot mode and connect to PC
First step is not possible for me because my phone completely turned off no option work for me, no pc detection and no any button combination to putting in fastboot mode or etc.....
Khalid Ghouri said:
1) Put the phone in fastboot mode and connect to PC
First step is not possible for me because my phone completely turned off no option work for me, no pc detection and no any button combination to putting in fastboot mode or etc.....
Click to expand...
Click to collapse
Did you install the drivers correctly because we have some drivers in the telegram group who are working properly i couldn't even find my device 9 pro with msm until I had those drivers maybe that's the problem to but I don't know I wish I could help you further i also placed your problem in the telegram and they want to help you but then you need to explain the steps you did
HessNL said:
Did you install the drivers correctly because we have some drivers in the telegram group who are working properly i couldn't even find my device 9 pro with msm until I had those drivers maybe that's the problem to but I don't know I wish I could help you further i also placed your problem in the telegram and they want to help you but then you need to explain the steps you did
Click to expand...
Click to collapse
can you please send me the driver link which is there telegram group
steps which i did
1. unlock the bootloader successfully
2. download the indian version android 12 and extract the payload.bin file
3. flash payload.bin file with fastboot enhance tool after complete the flash process device reboot and its happen for me
Khalid Ghouri said:
steps which i did
1. unlock the bootloader successfully
2. download the indian version android 12 and extract the payload.bin file
3. flash payload.bin file with fastboot enhance tool after complete the flash process device reboot and its happen for me
Click to expand...
Click to collapse
You didn't have to unpack the file you could can flash it with the zip file it fastboot enhance unpacks it self but i can't share you the drivers there already there downloaded i could download then and send then to you
I copied and paste this from the group there it's they are download links
OnePlus USB (all purpose/data transfer):
OnePlus-USB-Drivers.zip
drive.google.com
Google USB driver (for fastboot & ADB):
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
Qualcomm drivers (for MSM):
Qualcomm_Drivers_Setup.exe
drive.google.com
Khalid Ghouri said:
steps which i did
1. unlock the bootloader successfully
2. download the indian version android 12 and extract the payload.bin file
3. flash payload.bin file with fastboot enhance tool after complete the flash process device reboot and its happen for me
Click to expand...
Click to collapse
same happened here without extracting payload.bin before
Same here No way on earth to turn the Phone on in any way!
i think its perma bricked
OnePlus picked up my phone. Looking forward to their reply
My phone also brick.
I also try payload.bin in fastboot enhanced tool.
Completely done.
Now my phone is not turning on.
No pc connect.
No charging connect.
No power on.
Anyone can help me.??
Zeescorpion said:
My phone also brick.
I also try payload.bin in fastboot enhanced tool.
Completely done.
Now my phone is not turning on.
No pc connect.
No charging connect.
No power on.
Anyone can help me.??
Click to expand...
Click to collapse
Nobody knows what the problem is. you are not the only one. No solution yet
Is that somebody that know a link to download that some is now.
Im not coming in in my phone, no usb
How could i start usb-dubugging on my phone??
zelma83 said:
Im not coming in in my phone, no usb
How could i start usb-dubugging on my phone??
Click to expand...
Click to collapse
Hey are you still having problems? Do you have a windows device to troubleshoot with?
I know you had a Mac before.
What state is your phone currently in? Still unable to boot?
You can force your phone off by holding the power button and both volume keys for an extended period of time, the phone will vibrate when it does, from then just hold down and power until it powers on, it may take a few seconds but it'll land you on a black page with recovery as one of the options, once in recovery choose from the 3 language options, from here with the up and down vol keys and power you should be able to wipe your system and recovery your phone, you will lose the content but this should work.
The only other option is to boot to the bootloader then use fastboot commands to put the OS back, or use fastboot enhance.

Endless bootloop (Redmi 9 lancelot)

I tried installing crDroid (unlock bootloader, uploaded FW, recovery SHRP, then install ROM) and after reboot the phone would go back to recovery.
By mistake I "installed" SHRP from ZIP package (I thought I need to install latest recovery file to install ROM with android 12) and phone went into reboot loop, I can't do anything, any key combination doesn't help - I can't even turn it off.
help!
I opened the phone, disconnected the battery, but nothing happened - still bootloop
I'm planning to use SP Flash Tool
Immediately after connecting USB C, the phone boots into bootlop (after disconnecting and reconnecting the battery)
What happens when you flash the custom ROM?
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.
U can also try to flash it with MI flash tool.
Sergij-SApcPro said:
What happens when you flash the custom ROM?
Click to expand...
Click to collapse
Operation completed with status [ ]. It looks like there should be a * in the middle and then it would be a sign to me that the ROM is loaded.
Sergij-SApcPro said:
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
Click to expand...
Click to collapse
At the time of writing, no key combination was working - I can't get into Fastboot or Recovery. I let the battery run out for that moment.
Sergij-SApcPro said:
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.
Click to expand...
Click to collapse
Sergij-SApcPro said:
U can also try to flash it with MI flash tool.
Click to expand...
Click to collapse
That's what I'll do first, then move on to the solution below.
I opened the phone and disconnected the battery, but plugging in the USB cable immediately turns the phone on and bootloops again.
I'm using Linux and Windows, and one user hinted at hacking the USB driver so I believe it won't boot the phone, only then will I have communication? Other than that I don't know how to do it anyway.
For now, after the phone's battery runs out, I'll try with this solution
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph
I've exhausted the battery, Mi Flash needs Fastboot, which I don't have.
I used
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me
I got to the point of connecting the phone to the computer and it connects (the procedure says to use the Power button, but I had to disconnect the battery because Bootloop was falling in), using the Vol- button - the phone keeps connecting and disconnecting....
For a while I tried to connect the phone via SP Flash under Linux - in administrator mode the message "memory protection violation" appears (I don't know how the message is in English).
Adding a udev exception was supposed to help - after lsusb the Mediatek device appeared, I added the exception, restarted - and the same thing happens (the program crashes).
I finally managed (with the help of a group on telegram https://t.me/HelioG85_Unified) by switching off the phone and carefully going through all the points (except the update at the very end) from this link
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph
There is a little problem, because SP Flash must be from the link in this post (because it will not fit DA)
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me
Wow so many posts... Did you manage to fix the phone now? What do you mean by SP Flash will not fit the DA? Did you download the eng ROM for Lancelot? BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.
Sergij-SApcPro said:
Wow so many posts...
Click to expand...
Click to collapse
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Sergij-SApcPro said:
Did you manage to fix the phone now?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
What do you mean by SP Flash will not fit the DA?
Click to expand...
Click to collapse
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Sergij-SApcPro said:
Did you download the eng ROM for Lancelot?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.
Click to expand...
Click to collapse
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Great to hear that you fixed the phone, congratulations!
TomekParuszewski said:
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
Thanks for the info, but I don't need to flash it with SP Flash tool because that was earlier when I didn't try to install custom recovery. Now I have SHRP with CRDroid A12 and its Awesome.
Thanks for reading,
Bye
TomekParuszewski said:
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Yes
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Yes
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.
SandShadow said:
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.
Click to expand...
Click to collapse
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...
voland34 said:
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...
Click to expand...
Click to collapse
The battery trick does'nt work for me. I can't remember exact version, sorry - but my way was going BACK with SP Flash tool version (from newest to working with file). When I found right version the rest was only going with procedure.
I did it twice: first time I was scared, second - with finding right version of SPFT, every time - like walk in the park. Looong walk all procedure was like 2-3 hours.
Second one try was after trying to load Andorid 13 (2x). Don't do it kids!
After all, my Revolut app stop working lately on my phone and Redmi is retired for now... (and also becoming unusable because slowing dramatically)
Thanks for your answer. it has worked with battery empty (though that might not have benn necessary); not on 1st atttempt v5.2020 but it did with version 5v.2216 in case it might help someone...it didnt flash miui fastboot rom 12.5 but it did flash engineering rom. and from there i will twrp and miui.
Thanks for your suggestion of trying different spflash versions.

Categories

Resources