So I have been spending a good afternoon getting the phone out of bootloop because of a fault magisk I install , and there's no TRWP to save my ass
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
didgeridoohan.com
What doesn't work :
-Safe mode (click volume down key the second loading to the system (5G screen) , pass the MIUI.
What make mine works:
1. Get the original boot.img, flash this with like how you root your phone initially in rooting magisk.
Code:
fastboot flash boot boot.img
2. Now that you can go in the phone , but you don't have root access to remove the magisk module that's nested within root. You would need to get the ADB by going to
Additional Setting> developer option> enable USB debugging to have access to ADB
3. Either go to magisk and patch the boot.img again, or use to the one you have patched previously , go to fastboot and flash the patched boot.img
4. Reboot your phone (or type fastboot reboot) and continue to plug in your phone, now that you are in boot loop but 1. Have root access 2. Able to use ADB
5. In the ADB cmd console (probably same as your fastboot cmd console)
Type in ADB devices to check if you have ADB connection to your phone .
If yes, type the code below which would remove all the magisk module
Code:
adb wait-for-device shell magisk --remove-modules
6. It will reboot on its own , I have tried the process two times but I am able to get my phone out of loop.
I have spent a good afternoon figuring out, hopefully this could save anyone a headache
Not working here, I run the command but after reboot stills at bootloop, so I will stay without root because I can boot if I flash stock boot.img, I will wait to any twrp to flash magisk unistaller. (Advice: dont try to install 2019 modules)
Before running the command ,make sure you are in adb mode by typing adb devices .
It would not work in fastboot environment.
It would work in normal boot environment after you enabled usb debugging in developer option and in normal environment (after the MIUI boot screen, it works out even you are in bootloop status )
Yeah I know, I do it like you say, flashed magisk patched boot , wait for adb devices working, run the command for remove all the modules, but after the reboot stills on bootloop.
Can you send me the list of modules that you have after run the command? I have 3 modules
use this to see the installed modules
adb wait-for-device shell magisk -list
I believe your code is abit wrong there. Theres two -
Code:
adb wait-for-device shell magisk --remove-modules
Do reference the initial link I provided earlier .
Is all the info you need.
Dude, ofc I know what command is, I didnt type it wrong, I tell you if you can send me your installed module list
The modules that failed is pix3lify .
And below is my current module list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not sure if that helps
Mahoro.san said:
The modules that failed is pix3lify .
And below is my current module list.
View attachment 5299085
Not sure if that helps
Click to expand...
Click to collapse
I need that you runs the command that I'm telling to you.
Code:
adb wait-for-device shell magisk -list
This will display your module list
Pretty much
1.
Code:
Fastboot flash boot boot.img
on flashing the original and patched IMG ( you get that right )
2. After enabling the usb debugging when you flash the original IMG, you need to flash the magisk patched IMG again. (I believe you missed this part)
Code:
Adb devices
To check if you have ADB access to the devices
Code:
adb wait-for-device shell magisk --remove-modules
To remove the module
Mahoro.san said:
Pretty much
1.
Code:
Fastboot flash boot boot.img
on flashing the original and patched IMG ( you get that right )
2. After enabling the usb debugging when you flash the original IMG, you need to flash the magisk patched IMG again. (I believe you missed this part)
Code:
Adb devices
To check if you have ADB access to the devices
Code:
adb wait-for-device shell magisk --remove-modules
To remove the module
Click to expand...
Click to collapse
Dude, without the intention of disturbing. I know what I have to do. I'm able to boot if I flash stock boot.img, if I flash magisk patched boot.img I can use adb devices command but the device is in bootloop, then I use adb devices and adb wait-for-device shell magisk --remove-modules
The problem is that nothing happens when I use the last command, just reboots but still on bootloop
this command @Mahoro.san
Btw I get magisk working, just entered in safe mode (vol - and vol+ before boot animation) and then used the command that removes all modules. This time after reboot, no bootloop and magisk working fine
Related
Hi people.
I got some problems and some questions.
Until now I was perfectly happy with CWM 2.5.0.1 Recovery, BUT, I found out about newer recoveryes, so I decided to flash one.
NOW!
I'm VERY pissed off because I can't flash it.
I tried unrEVOked method, won't work, it pushes recovery but gets stuck on WAITING FOR BOOTLOADER; MAKE SURE ALL DRIVERS ARE INSTALLED. And yes, I have all drivers installed (ones that came with HTC Sync and Android 1.0 usb driver) and I tried with unrEVOked 3.14 and with the latest unrEVOked. So, thats all about that method and we can see it DOESN'T work.
Off to the next one:
I tried flashing the image with terminal emulator. Once again I did all the steps good: Copied the recovery.img to the root of SD card, entered t.e. and wrote the command (su to get superuser access and then flash_image recovery /sdcard/recovery.img).
Once again, NOTHING.
Then I tried using ROM manager from CWM. It flashes a recovery but I can only access that recovery through ROM manager but not through bootloader, that one gets me back to 2.5.0.1.
So I would REALLY appreciate if I can get some help.
Thanks in advance.
Regards from pissed off and unhappy me.
1st of buddy , your Question should be posted in the Q|A Section
2nd , did you try to re-install your phone drivers ?
k0sh,
1) whatever, mod can transfer it there, i just want some help.
2) yes.
smokzye said:
k0sh,
1) whatever, mod can transfer it there, i just want some help.
2) yes.
Click to expand...
Click to collapse
buddy , though you are my friend , but maybe you need to re-write your last comment specially number 1) .. its really not good though
regarding 2) what you wrote exactly in terminal ?
only 1 line ?
Seriously mate, just install Android SDK, and use the Fastboot option. Easy as pie and no issues at all.
Install Android SDK, then, get the Recovery.IMG file of the Clockworkmod version you want to flash. Place this in the SDK's Tools folder. Then, reboot your Wildfire in the bootloader mode, Enter Fastboot mode (Press Power button on Fastboot).
Then, open Command Prompt on Windows, cd (browse) to the SDK's tools folder and type the following command:
fastboot flash recovery recovery.img
Done.
Screenshot here (My SDK is installed in D:\Android)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AFAIK, You dont even need SDK installed. Just the Fastboot and binary will do, which can be obtained here: (Still, not very sure of this process, as I had the SDK installed a long time back)
http://forum.xda-developers.com/showthread.php?p=14693680
enough of number 1. :S
now
first line
su (ENTER)
by that i get superuser access
then in second line
flash_image recovery /sdcard/recovery.img (ENTER)
so now i get
operation done in next line
but phone should first: freeze for a bit
then get an empty line
nothing happens to me tho, and i tried to reboot in recovery coz i thought maybe it was a success, nope. same old stuff
3xeno said:
Seriously mate, just install Android SDK, and use the Fastboot option. Easy as pie and no issues at all.
Install Android SDK, then, get the Recovery.IMG file of the Clockworkmod version you want to flash. Place this in the SDK's Tools folder. Then, reboot your Wildfire in the bootloader mode, Enter Fastboot mode (Press Power button on Fastboot).
Then, open Command Prompt on Windows, cd (browse) to the SDK's tools folder and type the following command:
fastboot flash recovery recovery.img
Done.
Screenshot here (My SDK is installed in D:\Android)
AFAIK, You dont even need SDK installed. Just the Fastboot and binary will do, which can be obtained here: (Still, not very sure of this process, as I had the SDK installed a long time back)
http://forum.xda-developers.com/showthread.php?p=14693680
Click to expand...
Click to collapse
Thanks 3xeno. ^^
3xeno said:
Seriously mate, just install Android SDK, and use the Fastboot option. Easy as pie and no issues at all.
Install Android SDK, then, get the Recovery.IMG file of the Clockworkmod version you want to flash. Place this in the SDK's Tools folder. Then, reboot your Wildfire in the bootloader mode, Enter Fastboot mode (Press Power button on Fastboot).
Then, open Command Prompt on Windows, cd (browse) to the SDK's tools folder and type the following command:
fastboot flash recovery recovery.img
Done.
Screenshot here (My SDK is installed in D:\Android)
AFAIK, You dont even need SDK installed. Just the Fastboot and binary will do, which can be obtained here: (Still, not very sure of this process, as I had the SDK installed a long time back)
http://forum.xda-developers.com/showthread.php?p=14693680
Click to expand...
Click to collapse
please help!!! android SDK says (waiting for device) when my tattoo is in fastboot usb mode. it finds my device when my tattoo is on.
I've the same problem... If you have another way to flash recovery depends on S-ON/S-OFF stuff. Take a look at this thread the part 6: Custom Recoveries
If your buzz is S-ON (like mine) there isn't any other way but unrevoked but it doesn't seem to work, at least if your phone is already rooted
u do have all your windows drivers setup, do u?
glida said:
please help!!! android SDK says (waiting for device) when my tattoo is in fastboot usb mode. it finds my device when my tattoo is on.
Click to expand...
Click to collapse
Don't flash a buzz recovery for a tattoo... you will brick your phone
Hi,
PLEASE VISIT THE CORRECT AND OFFICIAL THREAD HERE. THIS THREAD WILL NO LONGER BE UPDATED.
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Jev
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
jevtheboss said:
Hi,
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
-Jev
Click to expand...
Click to collapse
Not sure if -i 0x2970 is needed for fastboot think its only for fastboot oem
No need for battery removal there is a fastboot command ........fastboot reboot......... that does the same thing
dnahc said:
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
Click to expand...
Click to collapse
Hi,
Please could you visit the thread here and ask the question there. I think TWRP 3.0.1 will fix the issue. :good: If not, on the TWRP website, 3.0.2 has been released which is supposed to fix some decryption issues so please wait for the thread (the one I linked to earlier) to be updated
i just need to flash twrp recovery on my redmi note 5 last miui 11.0.3 android version is 9
i just follow the steps but i didnt flash to twrp recovery when i write the command in adb//
some peoples telling me that the last twrp img recovery contain password or something like this any one can help me
Unlock bootloader first
Re: @wickednight
TWRP is a custom recovery. Flash it need an unlocked bootloader.
If your bootloader is locked, go to https://en.miui.com/unlock/ to apply for unlocking permissions. Download Mi Unlock Tool and proceed to unlock. A waiting period and instruction will then be displayed in Mi Unlock Tool. Use your phone actively during the waiting period.
More information about unlocking: https://c.mi.com/thread-2262302-1-0.html
Once you successfully unlocked the bootloader, in theory, you can flash any file as you want. However, Xiaomi has enabled ANTI_ROLLBACK feature on the Redmi Note 5 (whyred). Check the anti level first so you can choose the right flashing method.
Install all drivers needed on your computer and connect your phone to PC. Hold POWER and VOLUME DOWN for about 11s to enter fastboot mode. Open a command prompt window in the adb tool folder, type this command to check the anti level of your phone:
fastboot getvar anti
Look for the number after "anti:" in output imformation in order to know about the anti level of your phone. The flashing steps is a little different for anti3 devices and anti4 devices.
If the anti level is 3 or lower, you can flash the twrp recovery img file using fastboot command directly. Make sure the twrp img file has been placed in the adb tool folder, and has been renamed to "twrp.img".Type this following command to flash twrp recovery easily:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
If the anti level is 4 or higher, the steps is more complicated. You must bypass the ARB first. Download the whyred-arbpass.img and flash it to antirbpass partition or the ARB will block all your flashing commands. All needed files I will put their links at the end of the post. Type this command to bypass the ARB for one time. You need to use the whyred-arbpass.img to bypass the ARB everytime you want to flash. Make sure the whyred-arbpass.img is placed in the adb tool folder.
Command to bypass ARB and allow you to flash the recovery:
fastboot flash antirbpass whyred-arbpass.img
Check the output, make sure "sending antirbpass" and "writing antirbpass" are all OK. Now you can flash the recovery like anti3's devices:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
All needed files:
1. TWRP recovery img files for whyred:
https://dl.twrp.me/whyred/
2. ANTI_ROLLBACK bypasser file (need to flash it to antirbpass partition):
https://drive.google.com/open?id=1cbHeULrh62R0COSD-RU9OwsWFR2zyfmc
MD5:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you find it useful, please click thanks.
First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134
Akahat27 said:
First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
View attachment 5326971
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
View attachment 5326979
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
View attachment 5326983
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
View attachment 5326989
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134
Click to expand...
Click to collapse
ON which android version u have done this given me firmware name
pankspoo said:
ON which android version u have done this given me firmware name
Click to expand...
Click to collapse
I did on the android 10 which it initially came with..
Hi guys.
I would like to install a clean Android 11 with "adb sideload", but I've encountered a problem. When I rebooted to recovery and tried "adb sideload rom.zip" it gives me this error:
adb: sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Same output goes for "adb shell"
I have also tried to see what "adb devices" returns when in recovery and it shows my devices as unauthorized, although when my phone is normally turned on "adb devices" shows my device as authorized. I have tried some solutions found online, but any didn't work (for e.g.: revoking usb debbuging keys).
I don't know if that matters, but my phone is/have:
rooted (but right now I don't have Magisk installed)
unlocked bootloader,
stock recovery.
Any help will be appreciated.
Im a n00b but, I would try to decrypt my phone data, Im guessing you have custom recovery, this is easily done, most of the times you just have to set a lockscreen pin, and then go into your custom recovery to decrypt your data, it will ask you for your password, put it and wait, then go into system and remove the lockscreen pin, or leave it or change it for whatever you had before. try the thing you wanna do again, with some luck it will work.
this data decrypting does nothing to your phone that could damage it to my knoledge, if it failed and you feel like it you can even encrypt it again.
If not that, I would try to install the libUSB driver (dont even know if this is posible on not XIAOMI phones) and use the bypass tool, but man, Im guessing you have actually wasted all your options, I dont have your phone and Im nowhere near an expert, this POST actually seems more likely to work for you, but im guessing you already tried it, if you havent, you've not searched long enough to start making your own path to solve the problem.
When I rebooted to recovery and tried "adb sideload rom.zip" it gives me this error:
adb: sideload connection failed: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Same output goes for "adb shell"
Click to expand...
Click to collapse
In recovery mode ADB isn't working. Take note that ADB Sideload is a special Android run mode you boot into to install a Stock ROM.
Code:
adb devices
adb boot sideload
adb sideload <ROM-ZIP>
adb reboot
xXx yYy said:
In recovery mode ADB isn't working. Take note that ADB Sideload is a special Android run mode you boot into to install a Stock ROM.
Code:
adb devices
adb boot sideload
adb sideload <ROM-ZIP>
adb reboot
Click to expand...
Click to collapse
When I'm trying to use the commands when phone is turned on those are my outputs (they are not working properly):
Spoiler: Console output
<I'm started trying from phone normally turned on>
C:\Users\rzadd\Desktop\platform-tools>adb devices
List of devices attached
6d737901 device
C:\Users\rzadd\Desktop\platform-tools>adb boot sideload
adb.exe: unknown command boot
C:\Users\rzadd\Desktop\platform-tools>adb boot sideload
adb.exe: unknown command boot
<now I'm trying the commands in recovery mode>
C:\Users\rzadd\Desktop\platform-tools>adb reboot recovery
C:\Users\rzadd\Desktop\platform-tools>adb devices
List of devices attached
6d737901 unauthorized
C:\Users\rzadd\Desktop\platform-tools>adb boot sideload
adb.exe: unknown command boot
C:\Users\rzadd\Desktop\platform-tools>adb devices
List of devices attached
6d737901 unauthorized
I don;t know if that helps, but when I'm rebooting to recovery there's a message that my device is encrypted and I need to type in my PIN code there to continue the process.
Ivan.Adriazola said:
Im a n00b but, I would try to decrypt my phone data, Im guessing you have custom recovery, this is easily done, most of the times you just have to set a lockscreen pin, and then go into your custom recovery to decrypt your data, it will ask you for your password, put it and wait, then go into system and remove the lockscreen pin, or leave it or change it for whatever you had before. try the thing you wanna do again, with some luck it will work.
this data decrypting does nothing to your phone that could damage it to my knoledge, if it failed and you feel like it you can even encrypt it again.
If not that, I would try to install the libUSB driver (dont even know if this is posible on not XIAOMI phones) and use the bypass tool, but man, Im guessing you have actually wasted all your options, I dont have your phone and Im nowhere near an expert, this POST actually seems more likely to work for you, but im guessing you already tried it, if you havent, you've not searched long enough to start making your own path to solve the problem.
Click to expand...
Click to collapse
Hi. I'm using stock recovery.
I've tried to boot with twrp recovery, but there I cannot switch the storage to USB OTG, but I've tried some commands from CMD and it seems that when phone is booted with TWRP adb recognizes it as in Recovery mode but I'm still not able to side load anything. Here is the console output:
Spoiler: Console output
C:\Users\rzadd\Desktop\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (78360 KB) OKAY [ 1.855s]
Booting OKAY [ 0.125s]
Finished. Total time: 2.053s
C:\Users\rzadd\Desktop\platform-tools>adb sideload OnePlus7TOxygen_14.E.35_OTA_0350_all_2206171459_2d24e8424d684e1f.zip
Total xfer: 0.00x
C:\Users\rzadd\Desktop\platform-tools>fastboot devices
(empty results)
C:\Users\rzadd\Desktop\platform-tools>adb devices
List of devices attached
6d737901 recovery
C:\Users\rzadd\Desktop\platform-tools>adb sideload OnePlus7TOxygen_14.E.35_OTA_0350_all_2206171459_2d24e8424d684e1f.zip
adb: sideload connection failed: closed
C:\Users\rzadd\Desktop\platform-tools>adb boot sideload
adb.exe: unknown command boot
Maybe it would be better to fromat the phone to it's oryginal state with fatboot somehow?
I was mistaken, pity.
The correct command sequence
would be
adb devices
adb reboot sideload
adb sideload <ZIP-FILE>
adb reboot
xXx yYy said:
I was mistaken, pity.
The correct command sequence
would be
adb devices
adb reboot sideload
adb sideload <ZIP-FILE>
adb reboot
Click to expand...
Click to collapse
unfortunatelly same situation happened as earlier. Is there any guide here on XDA which describes how to do a clean installation of stock Android 11 with fastboot?
Fastboot deals with device's bootloader, not with Android OS: this is done by means of ADB.
Have you ever installed the latest OnePlus USB drivers as provided by Oneplus?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've installed those which are avaibale from CD when you plug your phone to the PC.
I think all those issues might be caused by the fact that I had root and magisk installed and I needed to do emergency factory reset (I've forget the PIN code) and that might be the reason of all these problems.