[Nokia 1] Guide on acquiring root on Android 10 Stock ROM - Nokia 1 Guides, News, & Discussion

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!

Related

[Guide] Root your Tab A6 T280

Credits go to: @ashyx, @mauam, @jedld, @Chainfire
Prerequisite:
Padded kernel for T280
http://forum.xda-developers.com/attachment.php?attachmentid=3881481&d=1474417563 (unpack with 7zip and put it to memory card)
SYSTEMMODE SuperSU (REQUIRED)
http://forum.xda-developers.com/attachment.php?attachmentid=3861602&d=1472738213 (put it to memory card)
All required drivers from Samsung Smart Switch
Odin 3.10
TWRP
https://www.androidfilehost.com/?fid=312968872162492913
Your unit should be fully charged
OEM unlock and USB Debugging enabled and allow your host computer
Steps:
1. Connect your tablet with your host computer
2. Open prompt and locate to your adb folder (platform-tools) and enter
Code:
adb reboot download
If it doesn't work, look at your tablet to see any prompt to allow your host computer
3. Open your Odin. Make sure auto reboot is not checked (but TWRP isn't overridden). Choose AP and locate your TWRP file. You may see secure check failed. Don't worry. Just press and hold power+volume down+home key together and wait for few seconds.
4. Enter TWRP by pressing power+volume up+home key together. You should see the boot screen. Keep pressing these buttons until the boot screen disappears. You should enter TWRP.
5. Locate your memory card. Flash systemmode SuperSU first, go back, and flash padded image as "boot".
6. (Optional) wipe cache and dalvik cache.
7. Reboot
8. It may take a while to boot up
9. You tablet rooted.
Hey, this works! Thank you for writing it up!
Success on a Samsung A6 SM-T280 (version 5.1.1 if memory serves).
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
sovereignjerk said:
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
Click to expand...
Click to collapse
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
mdsohal02 said:
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
Click to expand...
Click to collapse
Make sure you OEM unlock under the developer settings.
jedld said:
Make sure you OEM unlock under the developer settings.
Click to expand...
Click to collapse
Thank you Sorry, I haven't rooted an android device since the EVO 4G. Things have changed in the meantime.
---------- Post added at 02:48 AM ---------- Previous post was at 02:11 AM ----------
Does anyone know how to disable the OTA update notification once I am rooted ?
Does really count as a root? I thought needed bootloader...
sovereignjerk said:
Does really count as a root? I thought needed bootloader...
Click to expand...
Click to collapse
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
mingkee said:
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
Click to expand...
Click to collapse
Hi guys, has anyone tried APP2SD after rooting.?
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Can someone do a video tutorial about this root?
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
i advise you to search youtube on how to use adb. This is how i learned. Its too complicated to write it. But when you see video its easy. In simplest way adb is cmd opened in adb file. Than in cmd you write commands like adb flash, or adb format and stuff
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
You don't need adb. Just boot to download mode normally.
ashyx said:
You don't need adb. Just boot to download mode normally.
Click to expand...
Click to collapse
Ashyx
Will link2sd/app2sd after root.?
ahmedyar91 said:
Ashyx
Will link2sd/app2sd after root.?
Click to expand...
Click to collapse
I don't see why not.
Will try and post
Finally rooted.
I came across this post and worked first time.
I installed supersu via trwp, then flashed img as boot in trwp also.
Worked perfectly
http://forum.xda-developers.com/gal...covery-samsung-galaxy-tab-a6-sm-t280-t3475381
ecstaseey said:
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Click to expand...
Click to collapse
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
raakaysh said:
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
Click to expand...
Click to collapse
That is the old method and no longer relevant.
Just follow the steps in the OP below.
http://forum.xda-developers.com/showthread.php?t=3475381

How To Guide Full recover to stock - If things went really bad :)

Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Do you believe this could help with the ram dump issue?
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Blumi511 said:
Do you believe this could help with the ram dump issue?
Click to expand...
Click to collapse
I have no idea, but I think it can't get worse by trying it.
Flashing the firmware (so called "RAW"-firmware) that allows one to turn back to A11 on the A12 beta page, should get back every device back to a working condition if the problem isn't hardware or extremely messed up in the few partitions that the raw doesn't flash.
I tried using this method to get back to stock from OmniROM, but after several reboots, the phone is stuck in fastboot mode. I tried booting normally and recovery mode, and it immediately goes back to fastboot mode. Any ideas?
/Edit: Got it to boot by flashing Lineage recovery, rebooting into it, and doing a factory reset from there.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...KS-30.11.51.115-MR0-user_20210826-release.zip
Turn of your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
# Thanks to NisseGurra for the link to the latest RAW image.
Click to expand...
Click to collapse
Thank you very much! This safed my phone! I stupidly flashed the boot image from a different build and wasn't able to boot. Only your flash.cmd worked! I hat to comment out the hardwareid check though, because mine was 0 somehow.
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This could also be just an issue with the fastboot drivers. Try reinstalling them, also clearing up orphaned devices in device manager could help.
amdpcman said:
I guess I have terrible luck. My zf8 isnt getting detected on fastboot but is visible on ADB. Have a stupid issue with the playstore where it is throwing up the authentication error and isnt logging into anything. I thought ill flash the stock rom back but no joy. driver not found on device manager.
Click to expand...
Click to collapse
This is a known issue with Windows 10 computers. They have some sort of signature check where even if you install the correct drivers, they don't really get "installed" because of this check. There is a workaround for this though, I'm not sure how.
However, if you have a Win 7, Vista / 8 PC, adb and fastboot will both work flawlessly with no hassles (experienced personally).
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Where do you get latest RAW links from?
I could not find them via Asus site.
HyperCriSiS said:
Where do you get latest RAW links from?
I could not find them via Asus site.
Click to expand...
Click to collapse
A12 beta page. The firmware that allows you to go back to A11
NisseGurra said:
There is a newer raw out:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip
Click to expand...
Click to collapse
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Yippee38 said:
Is this download working for anybody? I've downloaded it twice (at 10 hours each), and both times it fails to extract. It gives a "data error" on the super.img file.
Click to expand...
Click to collapse
Works for me.
is there a newer image out?
it would be good if there is a full raw android 12 image posted...since android 12 is released now.
Hi there,
Installed LineageOS 18.1 yesterday because my phone was having awkward moments, I want to go back to RAW stock, but I can't finalize the install.
I followed OP's instructions, but I never could find the flashall_AFT.cmd from the extracted archive.
Anyway, i managed to use LineageOS Recovery, but it requires signature at 47% , and when I press Yes, it says :
E:error: 21
Installing update...
E: Package is for product ASUS_I006D but expected sake.
Installation version
Installation tried : UL-I006D-ASUS-31.1004.0404.81-1.1.25-2111-user.zip.
When I tried WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, it required signature after 0.2 seconds, with following message :
E:footer is wrong
update package verificationtook 0.2 s (result 1).E:Signature verification failed
E:error: 21
Installing update...
E:Open failed: /metadata/ota: No such file or directory
E:Couldn't mount Metadata.
E:Failed to find update binary META-INF/com/google/android/update-binary.
I resetted before launching above operations, everytime.
What can I do to go back to Asus RAW Rom ?
Forward thanks and best regards.
EDIT : OK, found it, I just had to extract the .zip file. I thought I had to flash it like any image.
My bad.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thank you so much! You saved my phone! The only thing is that I couldn't find the flashall_AFT.cmd file in the new image, I had to use the WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, and it worked perfectly. After I flashed the boot.img trying to get root on android 12 several times, my phone was in a ram dump state.
HyperCriSiS said:
Hi,
I want to share how I recovered my Zenfone 8 from some really bad flashing, ending up with nothing more than fastboot access.
It is really simple:
Get ADB/Fastboot drivers, for example from here:
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Downoad and extract this RAW image from ASUS:
https://dlcdnets.asus.com/pub/ASUS/...06D-ASUS-99.1004.0404.82-1.1.31-9999-user.zip
Turn off your phone
Reboot to fastboot mode by pressing and holding the Volume Up and Power keys simultaneously
Connect your phone to the PC
Run the flashall_AFT.cmd from the extracted archive
When finished, reboot if not already done automatically
It could happen, that the system still won't start now, but don't worry, just wait it out.
After several reboots it will offer to do a factory reset. Do it and the system will boot properly afterwards.
Regards,
Hyper
Click to expand...
Click to collapse
Thanks! This helped me after I got into a ramdump situation. I flashed a rom and a boot image through the bootloader instead of fastboot and got things corrupted.
On my Asus Zenfone 8, I upgraded from Lineage OS 18.1 to 19.1.
When I wanted to flash gapps and did a reboot into recovery, since then the device no longer works.
I can't get into recovery and I can't get into fastboot mode.
When I turn off the device and turn it on again, the following appears on the screen.
Waiting for flashing full ramdump...
PLS help me

How To Guide Master Guide to Unlock Bootloader/Flash TWRP/Root Device/Flash EU ROM/Pass SafetyNet

Hi All, as this device is fairly new and there is not much clarity on things so, I decided to create a master guide as you see below. I am also attaching a PDF version of this guide as I have not formatted this XDA post to what I feel it should be like. You may download and follow that, I will keep updating things as I find.
Lets start​
1. Unlock Bootloader​1.1 Apply for Bootloader Unlock​
Enable developer settings
Go to Settings>About phone/My device> All specs> Hit MIUI Version 8 times
Access Developer Settings from Settings>Additional Settings
Enable OEM Unlocking option
Now login to your desired Mi Account that you wish it to be associated with your device (Mi account should have a mobile number registered for OTP and verification sometime asked by MI flash unlock tool)
Your unlock bootloader wait time starts now. Wait for 7 days (168 hours from the time you added MI account) to unlock bootloader
1.2 Unlocking Bootloader​So you have crossed the wait period…. Now follow below to unlock assuming you have all the USB drivers for Mi devices (usually auto installed when you connect mobile)
Warning: All your userdata (including pictures and files) will be wiped out
Download official Mi flash unlock tool from this link: https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.24/miflash_unlock-en-5.5.224.24.zip
Boot into Booloader: Power off your mobile then hold Volume Down + Power Button till fastboot bunny pops up
Open Mi Flash unlock tool downloaded in step 1
Sign in with same account that you used to sign in in Developer Settings in step 1.1.d. It may ask to verify your account with OTP. do it.
Click Unlock on the tool.
Your device will be unlocked and rebooted. Wait till reboot.
Congrats… you have an unlocked mobile device now
Now let’s go to Rooting your device for which we will have to flash TWRP to Mobile
2 TWRP Flash and Rooting​2.1 TWRP Flash​
Download and Install Minimal ADB and Fastboot for windows for this link: https://androiddatahost.com/wp-content/uploads/Minimal_ADB_Fastboot_v1.4.3.zip
Download unofficial TWRP (only one available as of writing this guide) from here: https://sourceforge.net/projects/xi....6.0_11-0_LOCAL-20220203-01-vili.img/download and rename it to twrp.img
Also download Magisk from below link: https://github.com/topjohnwu/Magisk/releases/download/v24.0/Magisk-v24.0.apk we will use it next section for rooting.
Rename the downloaded magisk file from magisk.apk to magisk.zip and copy it to your device’s storage
Copy the above twrp.img file to Minimal ADB and Fastboot folder (not necessary if you know some directory navigation using command prompt)
Boot mobile into bootloader (follow 1.2.b)
From your Minimal ADB and Fastboot folder open Cmd here.exe file to access the ADB tool
Connect your device to PC
Verify if device has connected successfully using the command below
Fastboot devices
This should return your device id
Now boot into TWRP using below commands
Fastboot boot “twrp.img” if you pasted twrp.img in minimal adb and fastboot folder
Fastboot boot “path to twrp.img” if you did not move it to the minimal adb and fastboot folder
Let the device boot to TWRP
In above step we just booted by TWRP which is temporary. Now let’s flash it to make it permanent:
Go to Advanced settings in TWRP and click Flash Current TWRP
Reboot to TWRP
2.2 TWRP Backup of Current Rom​
You should have a working TWRP
Boot to TWRP and navigate to Backup section
Select all partitions and swipe to confirm
If you see error in backing up, uncheck Data and EFS partition backup
The backup should complete successfully
Have this backup copied to a PC for emergency wipout of your mobile
2.3 Rooting/Flashing Magisk​
Go to Install in TWRP and select magisk.zip you copied in step 2.1.d
This will flash magisk and root your device. Now reboot to system from recovery
Once you have the device booted, rename the magisk.zip to magisk.apk again and install the magisk app on device
You may update if you see any updates to magisk or app
2.4 Passing Safetynet​
Download this magisk module zip from here: https://drive.google.com/file/d/1QJHPpL4R8fcxjB35XbcpaCOipKzpvL2I/view?usp=sharing
Go to magisk app settings and enable Zygisk (beta) also enable Enforce Deny List
Select Hide the Magisk app and give any desired name for Magisk to hide its identity
Now go to modules page in Magisk app.
Select Install from source/storage option and chose the downloaded safteynet zip
Reboot
This will pass safetynet but still Indian bank apps won’t work. Keep following below for clear
Go to magisk settings and enter Configure DenyList
Add all the apps you want to hide magisk and root from (such as phonepe, Gpay)
Don’t leave any service from the selected apps unchecked
3. Flash EU Rom​Warning: All your userdata (including pictures and files) will be wiped out
A TWRP backup of current rom is recommended before following the next steps
You can see section 2.2 for the instruction on backup
Download Fastboot EU rom from here: https://androidfilehost.com/?fid=17825722713688263895
Extract all the contents in zip file to any normal folder
We will be using Bootloader/Fastboot mode. Boot into Bootloader: Power off your mobile then hold Volume Down + Power Button till Fastboot bunny pops up
Connect your device to PC
From the extracted folder Open windows_fastboot_first_install_with_data_format.bat(for windows).
You may execute appropriate similar named file if you are running Linux or MacOS
The EU rom flashing process will start. Hit “Y” on keyboard to accept Formatting
Wait patiently while the PC does its Job.
You may see a long pause post “writing Cust” command depending on PC configuration. You should wait for 5 minutes at least, then try hitting any letter key on your keyboard, the process continues this way.
You may hit letter key whenever you see unusual pauses during pushing of super partition file sparse sending 1 of 9 to 9 of 9
Wait till process finishes and reboots
For TWRP and Rooting you can follow the same guide in section 2.
Updating to Miui13/Android 12 EU Rom​
Check out this guide to Update to Android 12
Happy Rooting… Njoy your device.
Lastly.. All the credit goes to respective owners, I have just compiled everything together and in an easy manner. PM me for credits.
Do let me know if you have any suggestions and corrections.
Thanks & Regards,
Abdus Saboor Asad
Reserved
Reserved
Much appreciated, good overview.
Will try when I get my bootloader unlocked.
Rammetje.b said:
Much appreciated, good overview.
Will try when I get my bootloader unlocked.
Click to expand...
Click to collapse
You are welcome.
sasaboor64 said:
You are welcome.
Click to expand...
Click to collapse
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram
Rammetje.b said:
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram
Click to expand...
Click to collapse
Good question... I think we should hook once, that's how I unlocked. But I feel it should work without hooking as well.
Anyone should test it and update for us the other way.
When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?
working on miui 13 android 12?
paulboqs said:
working on miui 13 android 12?
Click to expand...
Click to collapse
you may go through the last thread in my post for miui 13 related rooting. this guide is for miui12 rooting and there is no TWRP yet for miui13 for our device
at what point exactly will all my data be wiped?
yuukiw said:
at what point exactly will all my data be wiped?
Click to expand...
Click to collapse
the moment u hit unlock after your waiting period...
sasaboor64 said:
the moment u hit unlock after your waiting period...
Click to expand...
Click to collapse
is there a way to back upp all apps + data?
MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?
m38d1 said:
MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?
Click to expand...
Click to collapse
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.
AwkwarddWhale said:
When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?
Click to expand...
Click to collapse
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.
Jctatis said:
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.
Click to expand...
Click to collapse
There is no solution, there is no twrp for Android 12 / MIUI13 yet.
Well I did manage to make it work using a mouse otg. But it useless since theres no storage to flash
mm_rajesh said:
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.
Click to expand...
Click to collapse
thanks
The problem was the phone cable
This TWRP from the first post is Android 12 too?

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