Develop Bugs

[Q] help for root

Hi guys,
I have already read dozens of pages regarding the procedure to root my new Htc M8 but I am still a bit confused.
In the picture attached you can see the status of my phone, I think the previous owner has already unlocked it .
What I am kindly ask you is to help me to find the next step to root the phone. I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery" but I'm not sure and I don't want to make a disaster !!!
Can U help me? I'm on Mac.
thanks
ciao
fausto

now flash any custom recovery and then flash supersu.zip from recovery to make your handset root

fcasini said:
I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery"
Click to expand...
Click to collapse
That is not the proper way to install TWRP, and I don't know how you got that notion.
The proper way to install TWRP is described on the TWRP website (see under "Fastboot Install Method"): https://twrp.me/devices/htconem8gsm.html

fcasini said:
Hi guys,
I have already read dozens of pages regarding the procedure to root my new Htc M8 but I am still a bit confused.
In the picture attached you can see the status of my phone, I think the previous owner has already unlocked it .
What I am kindly ask you is to help me to find the next step to root the phone. I suppose that I have to download a TWRP file, copy it to the internal memory of the phone and then chose "Recovery" but I'm not sure and I don't want to make a disaster !!!
Can U help me? I'm on Mac.
thanks
ciao
your lucky to have s-off already phone lol, install TWRP via fastboot command then flash supersu in TWRP
Click to expand...
Click to collapse

ok, thanks to all,
now I have downloaded the TWRP.IMG, adb and Fastboot files and I am approaching to connect my phone to mac, open terminal and then
./adb reboot bootloader
./fastboot twrp.img
SuperSU is already installed on the phone, so I think I don't need to download and install again.
Is it right?
Once Flashed the twrp image, phone will be wiped?
Thank you again, you help and patience is very appreciated
ciao
fausto

fcasini said:
SuperSU is already installed on the phone, so I think I don't need to download and install again.
Is it right?
Click to expand...
Click to collapse
Did you check to see if the phone was still rooted? It was clearly modded by the previous owner, so may still be rooted. You can check with one of the root checker apps; or simply any app that requires root (such as Titanium Backup).
Although its also possible they unrooted and left the SuperSU app still installed. Just having the app installed does not in itself give you root, the binary also has to be installed. So if that is the case (no root) then UES you will still need to download the current version SuperSU and flash in TWRP in order to gain root.
fcasini said:
Once Flashed the twrp image, phone will be wiped?
Click to expand...
Click to collapse
Nope, TWRP just overwrites the recovery partition. Completely separate partition from user data, ROM, etc.
Regardless, I still highly recommend you backup any personal data that is important to you (preferably backup to an off-phone location) before doing any mods, just in case something goes wrong.

Hi Redpoint73, thanks for the useful info.
I am pretty sure that it is unrooted. I unsuccessfully tried to install Titanium Backup and also the SuperSu application don't start because of the missing of root permission.
Then If I have understood your suggestions:
1) connect the phone with debug Usb ON
2) type ./fastboot twrp.img
3) Phone off
4) Power+Vol-
5) Fastboot menu
6) Recovery+Power
Is it right?
And then? What's happen after? The phone will reboot himself?
thanks
ciao

My comments below in red font:
fcasini said:
Then If I have understood your suggestions:
1) connect the phone with debug Usb ON Doesn't matter if Debugging is on, this only enables adb commands. Fastboot commands work regardless of debugging on or not. But Debugging on is good to have in other situations (so I usually leave it on).
2) type ./fastboot twrp.img Don't know where you got this syntax from. Its not correct. The command given on the link I gave previously (Post #3) states: fastboot flash recovery twrp.img
If the syntax is not exactly right, the command will fail or perform the wrong action. Also note that the TWRP img filename in the command needs to match the actual TWRP file you with to flash. You will notice when you download the TWRP file, the file name is actually much longer than just "twrp.img". So you can either type that whole filename exactly, or change the name of the file to actually be "twrp.img" (with no quotes)
3) Phone off
4) Power+Vol-
5) Fastboot menu
6) Recovery+Power
Click to expand...
Click to collapse
At some point before Step 6, you need to put the SuperSU zip on the phone. You can download it direct to your phone from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
After step 6 (boot into TWRP) select "Install" from the main menu. Navigate to the SuperSU zip, then select it. Once its flashed, reboot. You should be rooted and good to go.

redpoint73 said:
My comments below in red font:
fastboot flash recovery twrp.img.
Click to expand...
Click to collapse
redpoint73, I need your precious help
I have connected my phone to the Mac but with the command "./fastboot flash recovery twrp.img" I get the message "Permission denied".
Even with other command like ./reboot or ./adb devices...
What is going wrong? Maybe I've missed something?
I followed also the instruction here https://www.youtube.com/watch?v=WOW38u-02I0 but without luck...
Help!!!
ciao
fausto

fcasini said:
redpoint73, I need your precious help
I have connected my phone to the Mac but with the command "./fastboot flash recovery twrp.img" I get the message "Permission denied".
Even with other command like ./reboot or ./adb devices...
What is going wrong? Maybe I've missed something?
Click to expand...
Click to collapse
I don't know anything about Mac's, so I probably will be of limited help in that regard.
Did you install the Android SDK, or other Mac friendly adb-fastboot environment?

it is really strange...
I have installed both Adb and fastboot but whenever I try to flash the image file I get the same error: Permission denied.
With Mac there is no need of driver to work and I don't know ho to proceed.
Thank you redpoint73, your help has been very appreciated, I will search again on the net to solve the problem.
Have a nice day
ciao
fausto

fcasini said:
it is really strange...
I have installed both Adb and fastboot but whenever I try to flash the image file I get the same error: Permission denied.
Click to expand...
Click to collapse
Make sure you are running fastboot command while the phone is in bootloader-fastboot mode. Run adb command while booted into OS (and Debugging needs to be enabled in Settings).
You are in the correct directory (where your fastboot and adb executables are located) when running the commands?
Try finding a thread specific to running adb/fastboot on a Mac (probably doesn't need to be M8 specific) and reading up or post a link to this thread. This may be some Mac-specific nuance that I am not knowledgeable in.

thanks again dear redpoint73,
I checked again and It seems to be all right but it doesn't work.
I have just one doubt yet. Perhaps I have to flash a root file like this http://www.androidrevolution.org/do...le=Android_Revolution_HD_Root_and_BusyBox.zip and then supersu.img through recovery menu?
Could it be the way to gain the permission?
thanks
ciao

Pixel xl in twrp with no OS installed?

Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..

Which guide did you use to do all of this? I will help us understand where you started

Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery

There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!

I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device

Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?

mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot

Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root

Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...

I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.

System Has Been Destroyed. probably with the OEM LOCKED.

Hello,
So today I wanted to install a Magisk module, after rebooting, it got me to a bootloop, I erased ALL DATA on adb mode (power botton and volume up). then started all over.
But the Bootloader was still unlocked (because before, I had root), The febuary update was impossible to install, so I thought, maybe locking the OEM may fix it, so I tried tool called " TOOL ALL IN ONE " that claims to have full support for my device.
After trying to OEM Lock, I get a friendly greeting that says " System has been destroyed " .
Trying to go back into ADB mode isn't working.
I have no idea if the OEM was locked, nor how to fix the phone.
I've heard of Mi Flash, but will it work on a Android One device? if so, PLEASE provide me with how to do so (in a noobie friendly way if possible)
If it'll help, I'm running on Pie with January update. No TWRP/Magisk. no current Root access.
UPDATE: I wanted to wait for an answer from you guys but I took a leap of faith and typed " fastboot oem unlock " and the phone was unlocked (showing unlocked on Android One boot screen). That got the system to start a boot! But I think it's bootlooping now. I tried entering ADB mode and I was succefully able to! then I selected to delete all data ( This helped me before to fix the bootloop ). then rebooted.
and right while I am typing this. I see a beautiful Hi there sign!!!
Bois, The phone is up and Running!!! but with all data now gone (ofc).
But still, The OEM is unlocked, Can you please recommend me a proper way to lock it?

Install dump ota febuary update in fastboot

Vitor00 said:
Install dump ota febuary update in fastboot
Click to expand...
Click to collapse
How do I do that? in a noobie way please.

wynix black said:
How do I do that? in a noobie way please.
Click to expand...
Click to collapse
Download adb and fastboot.>>>>https://androiddatahost.com/uq6us
Download ota dump>>>>>https://drive.google.com/file/d/1SZ3rOyaViNZyUzoZDbueqMAJ_Q5vKLA1/view
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one>>>>>>https://drive.google.com/open?id=1oxRLyX1x4gAQga5vwn1epHrjqtitDWRB
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot

Vitor00 said:
Download adb and fastboot.>>>>
Download ota dump>>>>>
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one>>>>>>
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot
Click to expand...
Click to collapse
Is the "ota dump" is on February update?
can I auto update easily after this or will I have to install the ota(s) manually in the future?
Are you sure that locking the oem after installing the ota won't give a system has been destroyed?
and finally, is it possible to enable Camera 2 API in the middle of the operation? Before locking the oem.
Many thanks!

Vitor00 said:
Install dump ota febuary update in fastboot
Click to expand...
Click to collapse
Vitor00 said:
Download adb and fastboot.>>>>https://androiddatahost.com/uq6us
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot
Click to expand...
Click to collapse
I extracted the OTA_DAIZY.zip that you provided in the folder of minimal adb and fastboot, then typed the first command (the bluetooth one) in cmd while the phone is in Fastboot mode, CMD says " error canont load 'bluetooth.img' : no such file or directory"
please, how do I exactly " paste files from ota in the folder of adb and fastboot " ?

You can use MiFlash on this phone and not get your hands dirty with the method mentioned above. Grab the latest available stock ROM from here: https://en.miui.com/download-354.html
Download MiFlash(latest if possible). Turn off the phone and go to fastboot mode (vol down + power). Connect the phone to PC. Open MiFlash and select ROM location then click refresh, your device should be seen now. On the bottom you have options choose one then click start. DON'T interrupt the process when it's flashing.

marstonpear said:
You can use MiFlash on this phone and not get your hands dirty with the method mentioned above. Grab the latest available stock ROM from here:
Download MiFlash(latest if possible). Turn off the phone and go to fastboot mode (vol down + power). Connect the phone to PC. Open MiFlash and select ROM location then click refresh, your device should be seen now. On the bottom you have options choose one then click start. DON'T interrupt the process when it's flashing.
Click to expand...
Click to collapse
Thank you, I'm currently dowloading the stock ROM from the link you provided.
I have some questions about this,
1-you mentioned the options at the bottom, can you explain every one of them, is it as good as it sounds? one of the options is " save user data " of course i'd prefer to save my data IF it's possible and won't ruin the procces. does the "clean data and lock" can result in the System has been destroyed sign? because currently, even if i have a fresh clean all data on my phone, whenever i try to lock the bootloader (from my pc) it says system has been destroyed, If yes, will updates work fine via the settings thing or I will have to do this manually anyways? in other words, will having the oem locked give me any benefits? I'm not intrested in any warrenty/security thing.
2- if I had Magisk with root, and some of it's modules and maybe Camera 2 API enabled and I installed an update rom using Mi Flash, are they going to be deleted?
3-will this rom replace the original that i have on my phone? and my og one will be perma deleted? if I deleted all data after this procces, will it take me to a fresh instalation of this rom? or the one I had before?
4- will my phone remain unlocked after using Mi Flash with the first two options in the bottom (not "clean all and lock" ) ?
I really apologize for asking so many questions!

1- you can try save user data but the phone may not boot, I don't know the reason but I had bricked mine once and tried to flash the stock and save my data, somehow it didn't work. Try it for yourself and if it doesn't boot, flash the ROM again via MiFlash and select clean all and lock. Clean all and lock basically cleans the device, returns it to stock ROM and locks the bootloader, makes your device basically unused, you will have to set it up from scratch. If you use the clean all and lock or the clean all option, phone will boot normally and you can have updates without any problems. Locked bootloader means you can't do any changes to partitions of the device, which is good if you're not planning on rooting etc. You can have updates with either locked or unlocked BL unless of course you haven't tampered with the partitions of the device. I like locked BL because when you unlock the BL it shows another screen when booting, which I personally don't like.
2-MiFlash returns everything to stock, you will definitely lose magisk and root and the modules you installed on Magisk because using MiFlash flashes the original boot.img which makes Magisk useless. You can however get temporary root access and enable cam2API via ADB then lock the bootloader but you need to be careful with the process because you may lose your data (Locking/Unlocking BL erases all data but there's a way to bypass that)
3-As of now, the link I provided has the 10.0.3.0 (january update), if you've downloaded it your phone will install stock(from xiaomi) Pie ROM with January security patches. I forgot to write this update has issues with SIM (reverses SIM1 to SIM2) so I suggest grabbing V10.0.2.0.PDLMIFJ (Fastboot image) from here: https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913 then flashing it via MiFlash then updating to newer versions through settings.
4- if you choose "save user data" or "clean all" your phone will stay unlocked, if you choose "clean all and lock" you will have a locked bootloader. :good:

marstonpear said:
1- you can try save user data but the phone may not boot, I don't know the reason but I had bricked mine once and tried to flash the stock and save my data, somehow it didn't work. Try it for yourself and if it doesn't boot, flash the ROM again via MiFlash and select clean all and lock. Clean all and lock basically cleans the device, returns it to stock ROM and locks the bootloader, makes your device basically unused, you will have to set it up from scratch. If you use the clean all and lock or the clean all option, phone will boot normally and you can have updates without any problems. Locked bootloader means you can't do any changes to partitions of the device, which is good if you're not planning on rooting etc. You can have updates with either locked or unlocked BL unless of course you haven't tampered with the partitions of the device. I like locked BL because when you unlock the BL it shows another screen when booting, which I personally don't like.
2-MiFlash returns everything to stock, you will definitely lose magisk and root and the modules you installed on Magisk because using MiFlash flashes the original boot.img which makes Magisk useless. You can however get temporary root access and enable cam2API via ADB then lock the bootloader but you need to be careful with the process because you may lose your data (Locking/Unlocking BL erases all data but there's a way to bypass that)
3-As of now, the link I provided has the 10.0.3.0 (january update), if you've downloaded it your phone will install stock(from xiaomi) Pie ROM with January security patches. I forgot to write this update has issues with SIM (reverses SIM1 to SIM2) so I suggest grabbing V10.0.2.0.PDLMIFJ (Fastboot image) from here: https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913 then flashing it via MiFlash then updating to newer versions through settings.
4- if you choose "save user data" or "clean all" your phone will stay unlocked, if you choose "clean all and lock" you will have a locked bootloader. :good:
Click to expand...
Click to collapse
Thank you so much for the helpful answers!
So I flashed my phone with the first link you provided ( January update ) using Mi Flash and the option to save user data, It worked perfectly fine. not just that, but I was Finally able to get the February update using the option in the settings, I'm not aware of the SIM problem you mentioned, but i'm not experiencing any major bugs right now.
I want to get camera 2 API but I'll wait till March update to bring it ( if it exists, and launched within the first 10 days ). If the March update didn't carry with Camera 2 API enabled, I'll have to do it myself.
One last question please, How to enable the cam 2 API without magisk or touching something that may stop the built-in updater from installing? how to make it (and maybe Magisk too) survive flashing an OTA?. Will the option "save user data" protect them from getting Snapped™ ?

wynix black said:
Thank you so much for the helpful answers!
So I flashed my phone with the first link you provided ( January update ) using Mi Flash and the option to save user data, It worked perfectly fine. not just that, but I was Finally able to get the February update using the option in the settings, I'm not aware of the SIM problem you mentioned, but i'm not experiencing any major bugs right now.
I want to get camera 2 API but I'll wait till March update to bring it ( if it exists, and launched within the first 10 days ). If the March update didn't carry with Camera 2 API enabled, I'll have to do it myself.
One last question please, How to enable the cam 2 API without magisk or touching something that may stop the built-in updater from installing? how to make it (and maybe Magisk too) survive flashing an OTA?. Will the option "save user data" protect them from getting Snapped™ ?
Click to expand...
Click to collapse
I don't think Xiaomi will ever let this phone have Cam2API. They even broke GCam functionality on Pie update (on Oreo Gcam worked fine but now every Gcam has focus issues). Follow this topic to have Magisk and keep it after updates: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952 Follow this topic to have Cam2API enabled if you don't want root/Magisk: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414 :good:

Trying to Root and Install Custom ROM

Edit: Issue resolved
Hello everyone,
Pardon my lack of knowledge on rooting devices and all the related things. This is my first time attempting to root a device and I am having a lot of trouble understanding how to go about things. Through my research, I'm finding a lot of different ways to do things and I want a direct opinion on my process so I don't mess up my phone. (Through as much research as I could) My end goal is to have TWRP flashed to my phone, root my device and install a custom ROM. My understanding is that I first need to unlock the bootloader, flash TWRP, install SuperSU, then flash the custom ROM. I won this phone from a raffle and I'm trying to root from a Windows 10 laptop.
I have the TWRP and SuperSU files at the ready and have also installed Kingo root. I enabled USB debugging and allowed the bootloader to be unlocked in developer settings. I tried to boot into download and bootloader and successfully recognized my device, but when trying to use "fastboot flash recovery twrp-3.2.3-0-hima.img" it gave me the error message "FAILED (remote: cannot flash this partition in s-on state)" and "FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)"
I'd assumed my phone was already unlocked but that's obviously not the case. Doing some more research I found a lot of people needed to get a bootloader unlock from HTCdev.
Is this what I need to do now to continue?
What about this "s-on state" how can I turn it off?
Will unlocking the bootloader wipe my device?
Could I just use the "root" button in the Kingo root main app?
Can anyone verify my theoretical steps and give quick notes on how I should be doing them properly?
Any help is greatly appreciated

dont worry i will help you
Download all in one Android toolkit for your PC...
https://www.google.com/url?sa=t&sou...FjAAegQIBRAB&usg=AOvVaw0sohDTlAE3UaLSgUihYhS3
and connect your phone to PC and allow USB debugging after that
go to Android all in one toolkit and select unlock bootloader....on the screen of your phone it would ask you if you want to unlock bootloader press volume up for yes
volume down for no
Select yes...but
Note:It would reset everything on your phone so back up your necessary files
Make sure you download the right twrp image for your phone (Google search)
Move the Twrp.img to your PC local directory folder and rename it to TWRP.img ....next step is to:-
next step is to go to windows command prompt on your PC and type the following commands:-
Adb devices
Adb reboot bootloader
Fastboot devices
Fastboot flash recovery TWRP.img
Note:make sure you reboot your phone to recovery before normal reboot so that it would replace your previous stock rom
Go to twrp and install the latest version of super su
https://download.chainfire.eu/696/supersu/
This steps worked for me it can work for almost all types of phone
my name is Iduh Winner
I was a root struggler like you...all thanks to God ....I love you all for more info contact me on the following social media
facebook:Iduh Winner
YouTube:Iduh Winner

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.

how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.

Thanks for the hint, but I am not happy with the idea of someone playing with my data

1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC

Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.

Any idea? Should I give up?

If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info

Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.

Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.

If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?

So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?

Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons

MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?

You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b

I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.

Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.

Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?

Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.

Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?

Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5