Database Info

Completely unable to boot into download mode

As the title says i am completely unable to boot into download mode. I gave tried every method other than adb (I can't for the life of me figure out how to use adb) and my device simply WILL NOT boot into download mode. This is a rather discouraging issue for me, since it disables me from flashing kernels with odin3...
I have tried booting while plugged in and turned off with Odin open, tried with the phone unplugged and turned off (volume down + power) and every method simply starts the phone as normal, or loops boot animations until I release the buttons. And both volume buttos +power simply leads to recovery mode.
Please help >.

you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.

1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons

Even easier than navigating is shift clicking on the tools folder and opening the prompt that way.
Sent from my SAMSUNG-SGH-I897 using XDA App

masterofthebass said:
you aren't /completely/ unable. You just refuse to use the easiest way. ADB is ridiculously easy to use, you plug your phone in and type stuff into the command prompt. If you aren't able to use a computer, I'm not too sure you should be messing with your phone anyway.
Click to expand...
Click to collapse
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App

rkorzuch said:
1.Remove the battery, sim card, sdcard if you have one
2.Insert the battery
3.Hold both Volume buttons
4.Plug in the USB cable and continue holding both Volume buttons
Click to expand...
Click to collapse
You're my hero. Thank you.

djgleebs said:
I don't refuse, I just don't know how. Almost every tutorial takes for granted you know how to use adb pretty well...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)

Please next time when you have questions, post in the general. Unless you are helping with development, post it in the general with all your questions. Please also learn how to read and learn how to use the search button.
Sent from my GT-I9000 using XDA App

Why doesnt anyone read the stickies anymore??

I think the easiest way is (from rooted phone):
Open Terminal Emulator
>su <ENTER>
>reboot download <ENTER>

Easiset way is to google Android SDK. Open the folder, then open the tools folder. In there you will see adb. Drag adb onto your command window that you've opened to run commnads and then type in what you want it to do, ie: reboot recovery, reboot download then hit enter.

masterofthebass said:
I'm going to guess you are using windows.
1. download android sdk (google it)
2. open up a command prompt (windows+r cmd)
3. navigate to the sdk tools folder (using cd to change directories)
4. type whatever adb command you are supposed to. (adb reboot download in this case)
Click to expand...
Click to collapse
Step 3 is not necessary unless you are using adb push or adb pull.
Open command prompt, type command. Using ADB is not a skill. There are a whole 5 commands. adb shell, adb pull, adb push, adb reboot, and adb remount.

[Guide] [Mac OSX] The Mac Guide to Flashing Custom ROMs on 2.20

I had a first generation Galaxy S and was fairly involved in XDA until I traded it in for an iPhone. A few days ago I bought the One X and I noticed there weren't any guides tailored to Mac users on how to flash custom ROMs from a brand new stock device. So here I go. If I have time and get the permission of the developers of the root exploit I might eventually create a mac program that automates the process. Over time I will also try to improve this with screenshots and better instructions. I take no liability if your phone blows up or if it doesn't work for you.
This is just a rough draft, use at your own risk.
Overview
Root the Device
Install Custom Recovery
Install Custom ROM
Directions
Assuming you are on the latest firmware, 2.20, you have to use the X-Factor root exploit. It should be in the downloads folder that you will download below. I did not come up with this expliot so if it works you should donate to its creator. For convenience I bundled the tools you will need into a single zip file. You can download it here. Place the unzipped folder on your desktop. You will also need a custom ROM downloaded from the Android Dev portion of this forum.
Rooting
Back up all data that you would miss if lost.
Open up settings > Developer Options > USB Debugging
Plug your phone into your computer. Do not mount the drive; just leave it in charging mode.
Move the folder you downloaded earlier onto your mac's desktop. Now open a terminal window and type "cd desktop/htconexmac" and press enter.
Now type "sh run.sh" and press enter.
Press enter again when the disclaimer pops up.
If it works, on your phones screen a message should pop up asking for backup restorations as well as a prompt for passwords. Ignore the password spaces and autorize it. It should prompt you twice.
The phone should restart into "bootloader mode." Press the enter button on your computer once this loads and it should confirm that your new CID is "11111111" if it worked. If it doesn't say that then try again from scratch.
Press enter again and you should get a big block of text copy the whole block including the tags on either side of it. You will need this to unlock the bootloader.
Go to htcdev.com and make an account. Now go to htcdev.com/bootloader and in the drop down box select All Other Supported Models press enter and follow their directions.
Recovery
Close terminal entirely (not really necessary, it just makes things go smoother) and reopen it. Now type "cd desktop/htconexmac" and press enter.
Now turn your phone off entirely and turn it back on by pressing the power and volume down buttons at the same time. You should boot back into recovery mode. This time, use the volume keys to select fastboot
With your phone plugged in and USB Debugging still enabled, type "./fastboot.osx flash recovery twrp.img" This will install the TWRP Custom Recovery. I did not make this, if it works for you I would suggest donating to its developer.
When it is done installing you can turn off your phone and then boot back into the bootloader by holding the power button and volume down button at the same time.
Now scroll to recovery and press the power key. You should boot to a screen with lots of buttons.
Flashing the ROM
Press the button that says "Mount" and then press the button that says "Mount USB Storage." In a moment you should see your phone appear mounted as a disk on your computer. Drag the .zip file of whatever ROM you downloaded to this disk as well as the file titled "gaaps.zip." Once they finish copying press "unmount."
Press the back button to return to the main screen and then press the button titled "Wipe"
Do a factory reset. Press back. Wipe the cache. Press back. Wipe the Dalvik cache. Press back twice to get to the main menu.
Press "Install" and then select the zip file on the ROM you want to install. Press "add more zips" and select "gapps.zip." Finally slide to confirm the flash.
When it is done flashing go back to the main menu and press "reboot" and then "bootloader"
Make sure it says "FASTBOOT USB" in red. On your computer find the folder where you kept your ROM and extract the zip file. Find the file called "boot.img" and copy it into the htconexmac file on your desktop.
In terminal type "./fastboot.osx flash boot boot.img"
When it is completed type "./fastbook.osx reboot"
Your phone should boot with its ROM!

nice one bro

BreatheHT said:
nice one bro
Click to expand...
Click to collapse
Thanks. I don't think many people around here use mac though.

Very useful. Before I got my Win8 I felt like Mac users were left out. Still prefer to do things on my Mac when possible. Thanks for posting this

I am glad for the instructions. I just inherited my wife's old Mac Book and it's great to get intro to fastboot with OSX.
Sent from my HTC One X using Tapatalk 2

Thanks bro. I got a Mac and I've been waiting for clear instructions. Ill will give this a shot later today!
HtcOneXda-developers app

azd9 said:
Thanks. I don't think many people around here use mac though.
Click to expand...
Click to collapse
good job, on a mac 2

Very valuable!
Sent from my One X using Tapatalk 2

azd9 said:
I had a first generation Galaxy S and was fairly involved in XDA until I traded it in for an iPhone. A few days ago I bought the One X and I noticed there weren't any guides tailored to Mac users on how to flash custom ROMs from a brand new stock device. So here I go. If I have time and get the permission of the developers of the root exploit I might eventually create a mac program that automates the process. Over time I will also try to improve this with screenshots and better instructions. I take no liability if your phone blows up or if it doesn't work for you.
This is just a rough draft, use at your own risk.
Overview
Root the Device
Install Custom Recovery
Install Custom ROM
Directions
Assuming you are on the latest firmware, 2.20, you have to use the X-Factor root exploit. It should be in the downloads folder that you will download below. I did not come up with this expliot so if it works you should donate to its creator. For convenience I bundled the tools you will need into a single zip file. You can download it here. Place the unzipped folder on your desktop. You will also need a custom ROM downloaded from the Android Dev portion of this forum.
Rooting
Back up all data that you would miss if lost.
Open up settings > Developer Options > USB Debugging
Plug your phone into your computer. Do not mount the drive; just leave it in charging mode.
Move the folder you downloaded earlier onto your mac's desktop. Now open a terminal window and type "cd desktop/htconexmac" and press enter.
Now type "sh run.sh" and press enter.
Press enter again when the disclaimer pops up.
If it works, on your phones screen a message should pop up asking for backup restorations as well as a prompt for passwords. Ignore the password spaces and autorize it. It should prompt you twice.
The phone should restart into "bootloader mode." Press the enter button on your computer once this loads and it should confirm that your new CID is "11111111" if it worked. If it doesn't say that then try again from scratch.
Press enter again and you should get a big block of text copy the whole block including the tags on either side of it. You will need this to unlock the bootloader.
Go to htcdev.com and make an account. Now go to htcdev.com/bootloader and in the drop down box select All Other Supported Models press enter and follow their directions.
Recovery
Close terminal entirely (not really necessary, it just makes things go smoother) and reopen it. Now type "cd desktop/htconexmac" and press enter.
Now turn your phone off entirely and turn it back on by pressing the power and volume down buttons at the same time. You should boot back into recovery mode. This time, use the volume keys to select fastboot
With your phone plugged in and USB Debugging still enabled, type "./fastboot.osx flash recovery twrp.img" This will install the TWRP Custom Recovery. I did not make this, if it works for you I would suggest donating to its developer.
When it is done installing you can turn off your phone and then boot back into the bootloader by holding the power button and volume down button at the same time.
Now scroll to recovery and press the power key. You should boot to a screen with lots of buttons.
Flashing the ROM
Press the button that says "Mount" and then press the button that says "Mount USB Storage." In a moment you should see your phone appear mounted as a disk on your computer. Drag the .zip file of whatever ROM you downloaded to this disk as well as the file titled "gaaps.zip." Once they finish copying press "unmount."
Press the back button to return to the main screen and then press the button titled "Wipe"
Do a factory reset. Press back. Wipe the cache. Press back. Wipe the Dalvik cache. Press back twice to get to the main menu.
Press "Install" and then select the zip file on the ROM you want to install. Press "add more zips" and select "gapps.zip." Finally slide to confirm the flash.
When it is done flashing go back to the main menu and press "reboot" and then "bootloader"
Make sure it says "FASTBOOT USB" in red. On your computer find the folder where you kept your ROM and extract the zip file. Find the file called "boot.img" and copy it into the htconexmac file on your desktop.
In terminal type "./fastboot.osx flash boot boot.img"
When it is completed type "./fastbook.osx reboot"
Your phone should boot with its ROM!
Click to expand...
Click to collapse
it keeps saying my "CID is not 11111111".......

Forget that last post from me.. Lol I got it.
HtcOneXda-developers app

Thanks for this. Was waiting for some clear mac directions before rooting/unlocking!

Awesome. Thank you!

mikeeygee said:
Awesome. Thank you!
Click to expand...
Click to collapse
Excellent write up.
One question, is the XFactor Exploit used on Rogers phones? I seem to remember this was for AT&T models.
Thanks again.
David

dkonkin said:
One question, is the XFactor Exploit used on Rogers phones?
Click to expand...
Click to collapse
It's not needed. Rogers phones can go straight to unlocking via htcdev.

Thanks again.
Plan to put HTC One X back in order tonight.
Numerous lessons learned, thanks to all for the assist.
David

dead link
the 'You can download it here' link is dead, could someone post another please?
so I can use this guide for my s2?

ATTN: Backup your boot0 block today

ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.

very interesting Hashcode,thanks for the information :good:

Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.

Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped

esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.

Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!

AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.

seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail

AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now

Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked

Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.

seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?

Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide

AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle

How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2

had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed

dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2

I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode

PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!

You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app

Need help with UNLOCKing BOOTLOADER

Man....I just follow the steps on the official web site.
1...Put your device in fastboot mode (press the power button and volume down button at the same time and connect your device to your computer with a USB cable).
2...On your computer, open a command prompt or Terminal session.
3...Go to the Directory where you installed the Android SDK tools, and type:
$ fastboot oem get_unlock_data
4...This fastboot command will return a character string. This is the Device ID which you will be using to generate your unique unlock key.
just stuck at the step 3...i opened cmd ,and test" fastboot oem get_unlock_data".then it shows "waiting for device"..just cant get it done.. can anyone explain it more in detail ......thx...... im a chinese... finding information in a English website is a little challenging. so i just post it. if anyone ask this already ,then just sry....

Check and make sure your device is connected. It shouldn't take much time. Look at the first picture in this. Your phone should say "Transfer Mode: USB Connected". When you type in "fastboot oem get_unlock_data" it should look like the second picture in that same article.

Solust said:
Check and make sure your device is connected. It shouldn't take much time. Look at the first picture in this. Your phone should say "Transfer Mode: USB Connected". When you type in "fastboot oem get_unlock_data" it should look like the second picture in that same article.
Click to expand...
Click to collapse
i get in to AP fastboot menu , it said USB connected . then i just dont know wat to do next...

Did you install drivers?

Skrilax_CZ said:
Did you install drivers?
Click to expand...
Click to collapse
Yes ,of course . And i just followed the steps one by one. The phone said its connected. But the computer can't find the device

Trueloveice said:
Yes ,of course . And i just followed the steps one by one. The phone said its connected. But the computer can't find the device
Click to expand...
Click to collapse
Are you using Linux or Windows on your computer?

xaelith said:
Are you using Linux or Windows on your computer?
Click to expand...
Click to collapse
Im using windows . could it be the fastboot.exe that i downloaded is wrong?

if you're using the regular cmd, you're doing it wrong
when you're in the 'platform-tools' folder, hold shift and right click, in the menu click open command prompt window here

Trueloveice said:
Im using windows . could it be the fastboot.exe that i downloaded is wrong?
Click to expand...
Click to collapse
It would depend on where you downloaded the fastboot.exe from. However, if you are following the Droid-Life instructions (here), then that should be the correct program.
EDIT: I remembered that two settings on the phone need to be changed, as well. I had the same problem until I changed these options.
1. Turn USB Debugging on. (Go to Settings > Developer options, and make sure the box next to USB debugging is checked)
2. USB connection type must be MTP. (Settings > Storage > Menu (three boxes in a vertical line) > USB computer connection > and select the box next to MTP) Unless the setting has been changed, this one should be on by default.
Hope this helps.

xLoveHateLegend said:
if you're using the regular cmd, you're doing it wrong
when you're in the 'platform-tools' folder, hold shift and right click, in the menu click open command prompt window here
Click to expand...
Click to collapse
it's done , it's because of the fastboot.exe is wrong. i downloaded another one.

xaelith said:
It would depend on where you downloaded the fastboot.exe from. However, if you are following the Droid-Life instructions (here), then that should be the correct program.
EDIT: I remembered that two settings on the phone need to be changed, as well. I had the same problem until I changed these options.
1. Turn USB Debugging on. (Go to Settings > Developer options, and make sure the box next to USB debugging is checked)
2. USB connection type must be MTP. (Settings > Storage > Menu (three boxes in a vertical line) > USB computer connection > and select the box next to MTP) Unless the setting has been changed, this one should be on by default.
Hope this helps.
Click to expand...
Click to collapse
it's done , it's because of the fastboot.exe is wrong. i downloaded another one.

[MAGISK][MOD][13/01][v4] Stereo Speaker & Headphone Volume Boost Mod

Pre-requisites :
Rooted with Magisk
Disclaimer : I am not responsible for any damage to your device.
Click to expand...
Click to collapse
Download : AFH
Included Versions :
Volume Boost : Speaker & Headphone Boost
Volume Boost_Call : Speaker, Headphone & InCall Boost
Credits :
gururoop (Stock OOS)
Regards,
acervenky

If the speaker starts crackling at high volume, immediately lower the volume and report on the thread.
I've increased the gain by 4+2dB on all the versions which should be within safe threshold.
Regards,
acervenky

reserved 2

Gonna try today when my new phone arrives
#oneplus7pro
Thanx bud!

acervenky said:
Pre-requisites :
Rooted with Magisk
Download : Github
Included Versions :
Speaker Volume Boost
Headphone Volume Boost
Speaker & Headphone Volume Boost
Credits :
gururoop (Stock OOS)
Regards,
acervenky
Click to expand...
Click to collapse
so just copy paste into a directory and overwrite all?
(haven't got 7pro yet, waiting 21st to order).
thanks

entwicklun said:
so just copy paste into a directory and overwrite all?
(haven't got 7pro yet, waiting 21st to order).
thanks
Click to expand...
Click to collapse
You can do it manually, or just flash the zip via magisk.
Regards,
acervenky

acervenky said:
You can do it manually, or just flash the zip via magisk.
Regards,
acervenky
Click to expand...
Click to collapse
thank you, and I need a custom recovery for magisk?
https://www.xda-developers.com/how-to-install-magisk/

entwicklun said:
thank you, and I need a custom recovery for magisk?
https://www.xda-developers.com/how-to-install-magisk/
Click to expand...
Click to collapse
Follow this thread to install magisk : Patched Boot Image
And then install this as a module using magisk manager.
Regards,
acervenky

acervenky said:
Follow this thread to install magisk : Patched Boot Image
And then install this as a module using magisk manager.
Regards,
acervenky
Click to expand...
Click to collapse
oh man I've never command prompt stuff on a phone. I once flashed a wrong zip on my note 3 (2012 I think?) and hard bricked it lol, I'm so scared now haha!!

entwicklun said:
oh man I've never command prompt stuff on a phone. I once flashed a wrong zip on my note 3 (2012 I think?) and hard bricked it lol, I'm so scared now haha!!
Click to expand...
Click to collapse
It's not very difficult at all and is nothing to be fearful of. The beauty of OnePlus and this community is that it's difficult to royally screw up to a point of no return. If your device can get into fastboot, you're always fine. If you can get into EDL mode, you're fine. Here's a small guide of what you have to do, in order: I'm writing it out as if you are completely new in case you are or if anyone reading it is, I'm not assuming you are and don't mean to disrespect you if you aren't.
1) Download and install "Minimal ADB and Fastboot" on your computer from here: https://forum.xda-developers.com/showthread.php?t=2317790
2) Go to your phone's settings -> about phone -> then tap the build number until you've unlocked developer options.
3) Go to developer options under settings -> system -> developer options. Enable OEM unlocking, then scroll down and enable USB debugging. Connect your phone to your computer and authorise access on your phone when it prompts for it.
4) On your computer, go to the folder where you installed Minimal ADB and Fastboot. Hold your shift key and right click anywhere where there's open space (without a selected file in the window), and hit "Open Powershell Window Here"
5) Confirm your device is indeed connected by typing "adb devices". On my computer, I'm forced to type "./adb devices" with the period and forward flash for whatever reason, but the command prompt should show your device as connected. Might be a Windows 10 thing, I haven't researched it.
6) In the command prompt you've just opened, type "adb reboot-bootloader". You're now in fastboot mode.
7) Once you are in fastboot, type "fastboot oem unlock". Follow the prompts on your phone to unlock the bootloader with the volume keys. This will erase all your data on your phone. Your phone will now reboot after you've confirmed that you're okay with data being wiped.
8) Set up your phone again and unlock developer options/USB debugging again.
9) On your computer, download the correct patched version of your boot.img here: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205 - please remember to download the correct version, downloading the wrong one and flashing it will cause your WiFi not to work. You can check which version you need by going into settings -> about phone -> build number. I'm on Oxygen OS 9.5.3. If you've accidentally installed the wrong one, no worries - download the correct one and follow the steps again.
10) Drag the file you've just downloaded (filename should be: boot_patched.img) into your Minimal ADB and Fastboot folder.
11) Hold your shift key + right click anywhere in the window and open Powershell again.
12) Reboot into bootloader again by typing "adb reboot-bootloader". Again, if you're on Windows 10 or if you get some long message, you may have to type "./adb reboot-bootloader". This applies to all commands input into the command prompt, including the next steps'.
13) Once your phone has reboot into fastboot, in the command prompt, type "fastboot flash boot boot_patched.img".
14) After that's completed, type "fastboot reboot". Your phone will now reboot normally.
15) On your phone, download Magisk Manager from here: https://www.xda-developers.com/how-to-install-magisk/ - it's a 1.85 mb file that's actually just an apk file. Allow Google Chrome access to your storage, and allow Chrome to install apps from an unknown source - then continue to install Magisk Manager.
16) Once installed, you'll be prompted to finish installing Magisk, tap continue and let it do its thing. Then hit reboot.
17) Once rebooted, locate Magisk Manager and open the app. You should see the fact that it successfully installed. From there, swipe in from the left and select downloads to start looking for mods! You can download them on Chrome and find them under the modules, just gotta click the plus sign and locate it.
Cheers.

I tried the speaker mod, but I had problems with most of my applications. The mod pairs nicely with Poweramp music player, but everything else lacks that pop. I could say I tried and thanks. Here is list of the apps that had bad output
(1)OG YouTube
(2) YouTube Vanced
(3) FL Mobile
(4) Audio Evolution Mobile
(5)Ntrack DAW
(6) Audiolab
(7) Meditation Drums
(8) Bebot
(9) Deflemask
(10) Videoder
*Maybe I did something wrong or it's conflicting with other apps
Sent from my GM1917 using Tapatalk

Thanks
AhsanU said:
It's not very difficult at all and is nothing to be fearful of. The beauty of OnePlus and this community is that it's difficult to royally screw up to a point of no return. If your device can get into fastboot, you're always fine. If you can get into EDL mode, you're fine. Here's a small guide of what you have to do, in order: I'm writing it out as if you are completely new in case you are or if anyone reading it is, I'm not assuming you are and don't mean to disrespect you if you aren't.
1) Download and install "Minimal ADB and Fastboot" on your computer from here: https://forum.xda-developers.com/showthread.php?t=2317790
2) Go to your phone's settings -> about phone -> then tap the build number until you've unlocked developer options.
3) Go to developer options under settings -> system -> developer options. Enable OEM unlocking, then scroll down and enable USB debugging. Connect your phone to your computer and authorise access on your phone when it prompts for it.
4) On your computer, go to the folder where you installed Minimal ADB and Fastboot. Hold your shift key and right click anywhere where there's open space (without a selected file in the window), and hit "Open Powershell Window Here"
5) Confirm your device is indeed connected by typing "adb devices". On my computer, I'm forced to type "./adb devices" with the period and forward flash for whatever reason, but the command prompt should show your device as connected. Might be a Windows 10 thing, I haven't researched it.
6) In the command prompt you've just opened, type "adb reboot-bootloader". You're now in fastboot mode.
7) Once you are in fastboot, type "fastboot oem unlock". Follow the prompts on your phone to unlock the bootloader with the volume keys. This will erase all your data on your phone. Your phone will now reboot after you've confirmed that you're okay with data being wiped.
8) Set up your phone again and unlock developer options/USB debugging again.
9) On your computer, download the correct patched version of your boot.img here: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205 - please remember to download the correct version, downloading the wrong one and flashing it will cause your WiFi not to work. You can check which version you need by going into settings -> about phone -> build number. I'm on Oxygen OS 9.5.3. If you've accidentally installed the wrong one, no worries - download the correct one and follow the steps again.
10) Drag the file you've just downloaded (filename should be: boot_patched.img) into your Minimal ADB and Fastboot folder.
11) Hold your shift key + right click anywhere in the window and open Powershell again.
12) Reboot into bootloader again by typing "adb reboot-bootloader". Again, if you're on Windows 10 or if you get some long message, you may have to type "./adb reboot-bootloader". This applies to all commands input into the command prompt, including the next steps'.
13) Once your phone has reboot into fastboot, in the command prompt, type "fastboot flash boot boot_patched.img".
14) After that's completed, type "fastboot reboot". Your phone will now reboot normally.
15) On your phone, download Magisk Manager from here: https://www.xda-developers.com/how-to-install-magisk/ - it's a 1.85 mb file that's actually just an apk file. Allow Google Chrome access to your storage, and allow Chrome to install apps from an unknown source - then continue to install Magisk Manager.
16) Once installed, you'll be prompted to finish installing Magisk, tap continue and let it do its thing. Then hit reboot.
17) Once rebooted, locate Magisk Manager and open the app. You should see the fact that it successfully installed. From there, swipe in from the left and select downloads to start looking for mods! You can download them on Chrome and find them under the modules, just gotta click the plus sign and locate it.
Cheers.
Click to expand...
Click to collapse
I just wanted to say a big THANKS for that awesome explanation!

Hentai_expert said:
I tried the speaker mod, but I had problems with most of my applications. The mod pairs nicely with Poweramp music player, but everything else lacks that pop. I could say I tried and thanks. Here is list of the apps that had bad output
(1)OG YouTube
(2) YouTube Vanced
(3) FL Mobile
(4) Audio Evolution Mobile
(5)Ntrack DAW
(6) Audiolab
(7) Meditation Drums
(8) Bebot
(9) Deflemask
(10) Videoder
*Maybe I did something wrong or it's conflicting with other apps
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
Interesting, only with third party apps... No Google apps or sth like that

I flashed the headphone boost through Magisk and feel like it didn't do anything.

Any updates for a better mod or any way to increase the volume?

Just get Viper for volume boost.

FaflaMcDafla said:
Just get Viper for volume boost.
Click to expand...
Click to collapse
Or a custom kernel like EX so increase max volume

Eric214 said:
Or a custom kernel like EX so increase max volume
Click to expand...
Click to collapse
Or just use both

FaflaMcDafla said:
Just get Viper for volume boost.
Click to expand...
Click to collapse
Unfortunately the gain control doesn't do anything in viper on the op7 pro. and the audio is natively very low, especially on Bluetooth earphones or headphones.This mod pairs very nicely with viper. Now my op7 pro sounds nice and punchy just like my op6 does.
This mod is legit. Very happy with it.

Burt Squirtz said:
Unfortunately the gain control doesn't do anything in viper on the op7 pro. and the audio is natively very low, especially on Bluetooth earphones or headphones.This mod pairs very nicely with viper. Now my op7 pro sounds nice and punchy just like my op6 does.
This mod is legit. Very happy with it.
Click to expand...
Click to collapse
Does it boost Bluetooth? Was looking for a bit more oomph