Related
Here's a tutorial for the new users facing unanswered (at a first glance) questions while browsing through the tremendous amount of information that can be found.
There are many tutorials about this, but I will try to make one unique tutorial that will be easy to understand for everyone.
Press a THANKS button if you think that this TUT has helped you
IMPORTANT!
Before you proceed, you need to understand one thing: although these upgrades work in 99% of the cases, you are doing this at your own risk!
If you have any problems or question with rooting and flashing ROM's DO NOT open new thread, cause I will delete it, post everything here
Before we start, here is little Q&A section, so please READ this before opening new thread!
How to format and partition SD Card?
Read this
Is my desire already rooted?
- Check if you have superuser app in the app list all rooted phones have it
If I root a device which is already rooted, can it mess anything up?
- You can't mess anything up by re-rooting.
Will my phone get the OTA froyo update from HTC here in the US or do I have to do it manually?
- No OTA updates when rooted, to get them you will have to go back to stock to get the update(yepp unroot, or wait for devs to release rooted stock version)
What is S-OFF?
-HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC. The now notorious S-OFF (security off) will disable this NAND security. Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
Here is How to S-OFF your HTC Desire
If you think I should add more questions and answers, send me a PM
The easiest root method of all is(works for any Desire!):
[GUIDE] One Click How to Root the GSM & CDMA Desire with Unrevoked 3.21
If you want to root using old method, and you have Android 2.2 you will need to downgrade your radio first
[HOWTO] Downgrade Froyo (2.2) to Stock 2.1 (ANY HBOOT | WIN/LINUX/MAC | ROOT)
or
[HOW-TO] downgrade HBOOT 0.92 to 0.80 again
Here is how this thread works:
Newbie Friendly How To's w/ Instructional Videos(tnx to dcogen) - post #1
Root guide for users who have unbranded(unlocked) Desire - post #2
Root guide for users who have branded(locked) Desire and
How to make GOLDCARD - post #3
Guide how to use fake-flash, unroot, flash ROM and updates - post #4
How to remove apps & boot sound, install apps, and many other things - Post #5
*Unrooting, flashing ROM and updates is same for every device.
There are several methods of rooting device and one of the safest is using Tiny Core Linux(Live CD), since I had several problems using Windows(64-bit) I recommend this option, but if you are using 32-bit OS you should be fine rooting in Windows.
If you have any comments, ideas or requests to improve this thread, post them here
If you find any step that is wrong, or should be improved reoprt it here
Let's start flashing
Newbie Friendly How To's w/ Instructional Videos
How To Setup ADB
How To Load a Theme
How To Flash a New Recovery Image
How To Switch to a Different SD Card (for use with Swap, Hero ROMs, etc.)
How To Backup/Restore Your Android Phone
HTC Desire How To's
How To: Root the HTC Desire
How To: Load a Custom ROM on the HTC Desire
How To: Unroot the HTC Desire
Credits
Paul - Rooting method, rooting tool, rooting software, etc
Android dev team - adb, android, etc
craigcrawford1988 - for Tiny Core Linux tut and links
MasDroid - for some tutorials
42turkeys - unroot guide
eViL D: - general help
VeeDubZ - how to remove apps
dcogen - Newbie Friendly How To's
whole XDA community
Root guide for users who have unbranded(unlocked) Desire
Guide to root with Tiny Core Linux
IMPORTANT - this tutorial will not work if you have installed 2.2 OTA update from HTC!
Download Tiny Core Linux Live CD
---- For a bootloader of 0.75.* or lower AND a current ROM of 1.15.* or lower Download
---- For a bootloader of 0.80.* or lower AND a current ROM of 1.21.* or lower Download
Burn the downloaded iso on CD/DVD
Boot your computer from that CD/DVD, once you booted it will ask you to press Enter or F2/F3 keys, you need to press Enter
Start the HTC Desire in bootloader by holding back and turning it on by the power button
Connect the USB cable to the phone and PC
Open a terminal by clicking the icon that looks like a monitor at the bottom on Tiny Core Linux and type the following commands:
Code:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/desire
sudo ./step1.sh
Wait until the phone restarts back into the white bootloader screen
In terminal type the following command:
Code:
sudo ./step2.sh
Once the phone has finished, you will see a screen with a green text. Use the optical tracker to navigate the menu to select Wipe and then press Wipe data/factory reset
Once complete you should be back in the main menu. Now select the option Flash zip from sdcard and than choose rootedupdate.zip
Once back in the main menu, choose restart the phone - the rooting process is now finished
Guide to root using Windows, MAC OS X and Linux
!Some people reported that this method needs to have GoldCard(in most cases you won't need it) even if you have unbranded device, more here
You need to have Android SDK and HTC Sync installed(for Windows users)
Download following items:
---- If you have a bootloader version 0.75.xxxx or below AND a current ROM of 1.15.xxx.x or below - DOWNLOAD / MIRROR
---- If you have a bootloader version 0.80.xxxx or below AND a current ROM of 1.21.xxx.x or below - DOWNLOAD / MIRROR
Unzip the file you downloaded to a directory, then open a command prompt / terminal window at that directory.
Turn off your HTC Desire, then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box. Connect the phone to the computer.
In the command prompt/terminal window, enter either 'step1-windows.bat'(for windows), './step1-mac.sh'(for mac) or './step1-linux.sh'(for linux)
Navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select.
In the command prompt/terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate.
When this has completed, your device should be at the 'recovery'("green") screen. Select Wipe and then press Wipe data/factory reset
Once complete you should be back in the main menu. Now select the option Flash zip from sdcard and than choose rootedupdate.zip
Once back in the main menu, choose restart the phone - the rooting process is now finished
Root guide for users who have branded(locked) Desire
Before you start to root your branded(locked) Desire you need to know:
How to make GoldCard
GoldCard Tool v0.0.5
Requirements:
Latest HTC Sync software installed (www.htc.com)
Spare microSD card
Windows PC (Tested on Windows7 x64,Vista x86)
.Net Framework 2.0
Step by step instructions:
Format the microSD card to FAT32 format.
Put the microSD card in your device and boot it.
Launch GoldCard Tool (Right Click and run as Admin if needed)
Connect Android device to USB (USB Debugging must be enabled on the device)
Click 'Get CID' (If MMC1 fails try MMC0)
Click the link to open revskills.de, enter the CID number from Goldcard Tool and create your goldcard image, which will be e-mailed to you.
Enable USB Mass Storage on the device.
Click 'Refresh' and select your microSD card in the drop down menu.
Click 'Load GoldCard.img' and open the .img file you got by email.
Click 'Patch MMC'
You now have a goldcard!
[Notes]
HTC Sync is required for drivers only
Android SDK is not required
Guide to root with Tiny Core Linux
IMPORTANT - this tutorial will not work if you have installed 2.2 OTA update from HTC!
Download Tiny Core Linux Live CD
---- For a bootloader of 0.75.* or lower AND a current ROM of 1.15.* or lower Download
---- For a bootloader of 0.80.* or lower AND a current ROM of 1.21.* or lower Download
Burn the downloaded iso on CD/DVD
Boot your computer from that CD/DVD, once you booted it will ask you to press Enter or F2/F3 keys, you need to press Enter
Insert the goldcard into the phone.
Start the HTC Desire in bootloader by holding back and turning it on by the power button
Connect the USB cable to the phone and PC
Open a terminal by clicking the icon that looks like a monitor at the bottom on Tiny Core Linux and type the following commands:
Code:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/desire
sudo ./step1.sh
Wait until the phone restarts back into the white bootloader screen
Turn the phone off via the bootloader menu (or pull the battery and USB cable) and remove the goldcard. Put a non-goldcard SD into the phone or reformat the goldcard and put it into the phone. Put the phone back into bootloader mode (Press Power button and Back button).
In terminal type the following command:
Code:
sudo ./step2.sh
Once the phone has finished, you will see a screen with a green text. Use the optical tracker to navigate the menu to select Wipe and then press Wipe data/factory reset
Once complete you should be back in the main menu. Now select the option Flash zip from sdcard and than choose rootedupdate.zip
Once back in the main menu, choose restart the phone - the rooting process is now finished
Guide to root using Windows, MAC OS X and Linux
IMPORTANT - this tutorial will not work if you have installed 2.2 OTA update from HTC!
Download following items:
---- If you have a bootloader version 0.75.xxxx or below AND a current ROM of 1.15.xxx.x or below - DOWNLOAD / MIRROR
---- If you have a bootloader version 0.80.xxxx or below AND a current ROM of 1.21.xxx.x or below - DOWNLOAD / MIRROR
Unzip the file you downloaded to a directory, then open a command prompt / terminal window at that directory.
Turn off your HTC Desire, put GoldCard and then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box. Connect the phone to the computer.
In the command prompt/terminal window, enter either 'step1-windows.bat'(for windows), './step1-mac.sh'(for mac) or './step1-linux.sh'(for linux)
Turn the phone off via the bootloader menu (or pull the battery and USB cable) and remove the goldcard. Put a non-goldcard SD into the phone or reformat the goldcard and put it into the phone. Put the phone back into bootloader mode (Press Power button and Back button)
Navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select.
In the command prompt/terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate.
When this has completed, your device should be at the 'recovery'("green") screen. Select Wipe and then press Wipe data/factory reset
Once complete you should be back in the main menu. Now select the option Flash zip from sdcard and than choose rootedupdate.zip
Once back in the main menu, choose restart the phone - the rooting process is now finished
Guide how to unroot, flash ROM and updates
fake-flash
Fake-flash is only possible with root access, you need to be rooted to use it. Basically, its a way to have recovery running on the phone without using a PC (making it safer as you are less likely to brick using no USB cable to push files, instead, you push directly from your phone). You can use "ROM Manager" from the marketplace to do this. Simply place the downloaded test recovery image on the phone and the downloaded rom zip (renamed to update.zip) and flash using ROM Manager.
Preperation
Download the fake-flash update zip from one of the links below
Copy the update.zip to the root of your SD card (the name MUST remain as update.zip)
When you want to launch the recovery image
Turn on your device with 'volume down' pressed and select 'Recovery'
When the exclamation mark appears, press and hold 'volume up' then press 'power'
Select the second option, 'Apply sdcard:update.zip
That's it, ClockworkMod recovery should launch!
DOWNLOAD
How to flash ROM
Download this
Turn off Desire and then turn it on while holding back button to enter bootloader(white screen)
Once in "white screen" press power button again to enter bootloader
Connect Desire with PC
Press Volume Down and than Power to enter Recovery
Now the red triangle should show up, go to folder you downloaded file and press recovery-windows.bat, recovery-mac.sh or recovery-linux.sh depending on which OS you have
Now you are in recovery mode (green screen), press Wipe and than Wipe data/clear storage, than press optical tracker to confirm it
After that press Volume Down to go back to main menu in recovery
Navigate to Flash zip from sdcard using optical tracker, select .zip confirm it and wait until process finish, after that press Reboot system and unplug you Desire
Enjoy your new ROM
How to change boot animation
Download this
Copy bootanimation.zip to SD Card
Turn off Desire and then turn it on while holding back button to enter bootloader(white screen)
Once in "white screen" press power button again to enter bootloader
Connect Desire with PC
Press Volume Down and than Power to enter Recovery
Now the red triangle should show up, go to folder you downloaded file and press recovery-windows.bat, recovery-mac.sh or recovery-linux.sh depending on which OS you have
Navigate to Flash zip from sdcard using optical tracker, select .zip confirm it and wait until process finish, after that press Reboot system and unplug you Desire
Unplug your HTC and enjoy your new boot animation
Alternative method to install a custom boot animation (without Recovery Mode - by MasDroid)
You need to have HTC Sync and Android SDK installed (http://developer.android.com/sdk/index.html).
To get adb running on the Windows OS platform, for example, download & extract the Android SDK to the following path: %SystemDrive%\android-sdk-windows (e.g. C:\android-sdk-windows)
Turn on your phone and connect it to your PC via a USB port.
Place the downloaded bootanimation.zip into the same folder as the adb app (in the tools folder of the SDK).
Open command prompt and type cd C:\android-sdk-windows\tools, hit enter.
Type adb push bootanimation.zip /data/local, hit enter.
Reboot phone.
How to Unroot your HTC Desire to stock
If you Have A 0.75 Bootloader:
Generic RUU Download / Mirror #1
T-Mobile UK RUU Download
o2 UK RUU Download
3 UK RUU Download
If You Have A 0.80 Bootloader: Download
Other RUUs Avalible Here
You will need:
HTC Sync (For Drivers)
The Download Above
A Windows PC
A Goldcard (Not required for generic HTC Desires)
The Guide:
Make sure your goldcard is in your phone (If Required-if your phone is branded)
Turn your Desire on
Connect it to a Windows PC
Run the HTC RUU
Let it run
& YOUR DONE!
You can use it to return your phone for warranty purposes!
How to remove apps from ROM
You need to have root for this and Android SDK installed!
Link to detailed tutorial
Im using Paul's R4 rooting files at the location C:/users/veedubz/r4-desire-root in Windows 7 so point your Command prompt there first and im also assuming that you have a rooted Desire and can get into recovery mode
1. First get into recovery mode with the Green menu then close that command prompt and open a new one and cd to /r4-desire-root folder
2. You now need to mount the /system folder using the code below
Code:
adb-windows shell mount /system
3. Now you will need to get the list of installed apk files
Code:
adb-windows shell ls /system/app/
and the output should look like this:
Code:
AccountAndSyncSettings.apk HtcWeatherWallpaper.apk
ApplicationsProvider.apk Jbed.apk
Bluetooth.apk LiveWallpapers.apk
..... ......
HtcStreamPlayer.apk htcsettingwidgets.apk
HtcSyncwidget.apk restartapp.apk
HtcTwitter.apk teeter.apk
4. there are 2 methods of removal, they are
4a. Just delete the files
4b. Move to the sdcard
Use one of the following methods
4a. Now you have a list of the files you can chose the ones you want to remove , note that this part is case sensitive so com.htc.twitterwidget.apk is not the same as com.htc.TwitterWidget.apk, use the following code(example used is the Stocks app and widget):
Code:
adb-windows shell rm /system/app/Stock.apk
adb-windows shell rm /system/app/com.htc.StockWidget.apk
4b. Also case sensitive, to move the files to your sdcard(which aso removes from the device):
Code:
adb-windows shell mount /sdcard
adb-windows shell mkdir /sdcard/device_files
adb-windows mv /system/app/Stock.apk /sdcard/device-files
adb-windows mv /system/app/com.htc.StockWidget.apk /sdcard/device-files
The files will be moved to the new folder on your sdcard called /device-files, once there you can also backup to your pc for a bit of extra backup
5. Repeat Step 4. untill all the apk files that you want to remove are gone and to check that they are gone use
Code:
adb-windows shell ls /system/app/
Restoring your backed up files
Use the following code,
Code:
adb-windows shell mount /sdcard
adb-windows shell mv /sdcard/device-filesStock.apk /system/app/
adb-windows shell mv /sdcard/device-files/com.htc.StockWidget.apk /system/app/
How to remove apps from ROM
Read here
any one having trouble downloading the method5 for windowsfiles for hboot 0.8
the first link seems dead and the mirror downloads a corrupt file ??
...EDIT --- forgEt this post liknk 2 seems fine now THANKS !!! .. .... .....
OH and nice work
Thanks man for this guide.
It's more clear for me now =)
cheers - if i flash R5 rom,will this leave me with 121 rom or 115 rom? -I already running the 121 rom?
thanks
dread123 said:
cheers - if i flash R5 rom,will this leave me with 121 rom or 115 rom? -I already running the 121 rom?
thanks
Click to expand...
Click to collapse
You will have generic 1.15 ROM
Good job!!!
Appreciate this. Thank you.
Very good tutorial dude.
This is worth to be sticky!
ignore pls answered own question
Using Modaco's guide and I am stuck in step 2!
Isn't the Modaco Custom Rom for the Desire the same rom as the one for the N1 port? If that's the case it's not that good because I had a lot of issues with the N1 port 22.1 alpha.
Using Mac OS X
Asian Unlocked Desire
1.19.707.7
HBOOT 0.80
I am so far stuck in Step 2 after installing Step 1. Tried everything and it still won't work.
# In the terminal window, enter either 'step1-windows.bat', './step1-mac.sh' or './step1-linux.sh' as appropriate.
# When this step has completed, REMOVE THE GOLDCARD and either format it and replace, or replace with a different (non goldcard) microSD.
# Navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select.
# In the terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate.
# When this has completed, your device should be at the 'recovery' screen. Select the 'wipe' option, then select the option to apply an update zip from sdcard, and select 'rootedupdate.zip'. This will take a little while, so go make a nice cup of tea. When the flash has finished, reboot, and you are DONE!
After installing step 1, I proceeded to the recovery until the red triangle came out, entered step 2 and the error log shows :
./step2-mac.sh
Desire Root Step 2
Pushing required files to device...
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
device not found
Tried Unplugging the unit first then plugging it to the mac only when the red triangle shows up to no avail.
Please help!
Read somewhere that its an HTC Sync issue but I am using a mac
kingofthebraves said:
Using Modaco's guide and I am stuck in step 2!
Isn't the Modaco Custom Rom for the Desire the same rom as the one for the N1 port? If that's the case it's not that good because I had a lot of issues with the N1 port 22.1 alpha.
Using Mac OS X
Asian Unlocked Desire
1.19.707.7
HBOOT 0.80
I am so far stuck in Step 2 after installing Step 1. Tried everything and it still won't work.
# In the terminal window, enter either 'step1-windows.bat', './step1-mac.sh' or './step1-linux.sh' as appropriate.
# When this step has completed, REMOVE THE GOLDCARD and either format it and replace, or replace with a different (non goldcard) microSD.
# Navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select.
# In the terminal window, enter either 'step2-windows.bat', './step2-mac.sh' or './step2-linux.sh' as appropriate.
# When this has completed, your device should be at the 'recovery' screen. Select the 'wipe' option, then select the option to apply an update zip from sdcard, and select 'rootedupdate.zip'. This will take a little while, so go make a nice cup of tea. When the flash has finished, reboot, and you are DONE!
After installing step 1, I proceeded to the recovery until the red triangle came out, entered step 2 and the error log shows :
./step2-mac.sh
Desire Root Step 2
Pushing required files to device...
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
device not found
Tried Unplugging the unit first then plugging it to the mac only when the red triangle shows up to no avail.
Please help!
Read somewhere that its an HTC Sync issue but I am using a mac
Click to expand...
Click to collapse
have you installed HTC Sync?
Im running MAC OS X so no HTC sync
kingofthebraves said:
Im running MAC OS X so no HTC sync
Click to expand...
Click to collapse
I haven't tried rooting with MAC, I would suggest downloading Live CD it should be safe and easy
Thanks for the guide, looks much easier to do.
getting a
failed- remote :42 custom id check fail??
when running batch 1? anyone help pls? tried to carryon and batch 2 - usb cant be found -htc sync installed?
thank you very much
** Version 4.7 Updated October 2016 - Supports Android 4.0-7.0 **
SUMMARY:
Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices.
UPDATE: This tool was last updated on October 12th 2016. and confirmed working on Android 4.0-7.0 using WhatsApp version v2.16.304 (latest available).
IMPORTANT: If you wish to extract media files or WhatsApp databases from Google Drive backups then you need: WhatsApp Google Drive Extractor instead.
TUTORIAL:
BRANCH UPDATES:
v4.0 - Fixed issues with Android API 14-17 (4.0-4.2 Jelly Bean).
v4.1 - Added support for Android API 23 (6.0-6.0.1 Marshmallow).
v4.2 - Added support for specifying adb backup passwords.
v4.3 - Added PowerShell version as optional alternative to bat version.
v4.4 - Changed primary mirror for legacy apk.
v4.5 - Fixed issue pushing cipher key to emulated storage.
v4.6 - Updated primary mirror for legacy apk (again).
v4.7 - Added new sanity checks and support for Android API 24 (7.0 Nougat).
PREREQUISITES:
O/S: Windows Vista, Windows 7, Windows 8, Windows 10, Mac OS X or Linux
Java - If not installed: Download Java
ADB (Android Debug Bridge) Drivers
USB Debugging* must be enabled on the target device. Settings -> Developer Options -> (Debugging) USB debugging
Android device with Android 4.0 or higher. I.E. Ice Cream Sandwich, Jelly Bean, KitKat, Lollipop, Marshmallow or Nougat.
*= If you cannot find Developer Options then please go to: Settings -> About phone/device and tap the Build number multiple times.
INSTRUCTIONS:
Extract WhatsApp-Key-DB-Extractor-master.zip maintaining the directory structure.
Click on WhatsAppKeyDBExtract.bat (Windows) or WhatsAppKeyDBExtract.sh (Mac OS X / Linux).
Connect your device via USB, unlock your screen and wait for Full backup to appear.
Enter your backup password or leave blank (if none set) and tap on Back up my data.
Confirm backup password in your command console and then check the "extracted" folder.
TROUBLESHOOTING:
If you have never used USB Debugging before, you may also need to verify the fingerprint.
If you have set a default backup password in your Android settings, then this MUST be the
backup password that you provide when prompted to backup your data. Else it WILL fail!
Linux and Mac OS X users may need to set the script permissions as executable. Depending on the
adb permissions, you may also need to sudo ./WhatsAppKeyDBExtract.sh from your command console.
If you're having issues with WhatsAppKeyDBExtract.bat then right click WhatsAppKeyDBExtract.ps1
and select Run with PowerShell. You may have to enter "y" at first run for script execution policy.
If you get an error saying "AES encryption not allowed" then you need to update your Oracle Java
Cryptography Extension (JCE) to Unlimited Strength Jurisdiction Policy Files.
DOWNLOAD: WhatsApp-Key-DB-Extractor-master.zip
AUTHOR: TripCode
THANKS: dragomerlin for Android Backup Extractor and Abinash Bishoyi for being cool.
alternatives
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
droopyar said:
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
Click to expand...
Click to collapse
The only way to access private application files (such as a WhatsApp's cipher key) without root is the ADB method. You can backup some files on the device without a PC (APK's etc...), but there is currently no way to access private files and folders. All the "My Big Fat Backup" style apps and tools will either require root or ADB. Eclipse also utilizes ADB. Basically, device side backups of application data require root. There are no other alternatives to this. If there was, then Android would be too infeasible and insecure as a viable operating system. Physical access translates into only two solutions. 1.) The ability to root and 2.) The ability to utilize ADB (Eclipse, Bats, Exe's doing nothing more than calling a simple command line). Of course if you are aware of a 3rd method (disregarding the user interface) and is not based on root or ADB then please feel free to share.
Thanks for this tool!
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Thanks!!
Mia
PS I got JDK installed and still not working
MiaNet said:
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Click to expand...
Click to collapse
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
still showing this message attached
TripCode said:
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
Click to expand...
Click to collapse
Still showing the attached message
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Many thanks! I'll test when home and let you know.
Just to let know, the path command do not fix the prior version with Java check as I first thought this might be the problem.
Thanks!
Mia
Could even be use with ADB from phone to phone? without using the pc? Or I must install the app on the phone and do it offline?
I have find my way! Re-installed Java, manually clicked on java.exe stored in Java folder in Program files (or Program files (x86) ) I've clicked on Javacpl as well and enabled all options, not sure if this is necessary though.
I've then rerun the program without Java check (the Java check one is bugging now) and was able to do the back up.
Thanks!!
Best regards,
Melanie
Cannot tap button
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Permission denied
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Error
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
I, too am showing the same error.
Curwens said:
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Click to expand...
Click to collapse
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
kharloz_jc said:
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Click to expand...
Click to collapse
cardinalaa said:
I, too am showing the same error.
Click to expand...
Click to collapse
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
TripCode said:
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Click to expand...
Click to collapse
Hi, I am receiving the "Cannot find the path specified" error. I have tried both changing the script and also the other method, in environment variables. I am curious if this has anything to do with the fact that its an ATT phone (since no one can even root it yet)? No other apps can access my phone, either. I have USB debugging enabled and all prerequisite programs installed. Tried on 2 computers, win7 and win 8.1
I wonder if i it is an error on my part..?
TripCode said:
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
Click to expand...
Click to collapse
I have reviewed the "Extract" folder and there was the key. I have managed to decrypt it.
Thanks for the help and the tool!
PD: sorry for my bad English, I use translator is haha.
Nothing happens
Hi, first, thanks for this iniciative. A lot of people would apreciate this
I think I did everything as u said, but when I open the WhatsAppKeyExtract,bat and then conect my phone in debuggin mode to PC, nothing happens. Ive waited for 10 minutes and.. nothing happens. Keep showing the initial message: "Please connect your Android device..." and in my phone nothing happens too. Just show a messagem at the upper tab saying: "USB debbugin conected".
Theres any kind of setting to do futher in the debbug options?
Thanks
Update: I had do install de universal adb driver for my phone, and now it starts the download, but now im having problem with java... the messagem says "'java' isnt a recognizable command". I tried all solutions in this post and nothing.. I need heeeelp!
Solution to path problem
Is working perfect. For someone else that can happen the same thing as me. I have to fix something (i am spanish) about:
java is not recognized as an internal or external command, operable program or batch file
Here is the solution:
java .com/en/download/help/path.xml
Or here:
1. Right-Click My Computer and select Properties
2. Then Click The Advanced Tab
3. Then Click Environment Variables
4. Select Path In The Bottom Box and Click Edit
5. Find Where You installed Java (E.g "C:\Program Files\Java\bin)
Its different on each computer
6. Make Sure to add a semicolon after the word bin in the path to seperate it from the other important paths
7. If this doesnt work then you may have to reinstall Java and Try Again
Setting Path on Windows
For Windows XP:
1. Start -> Control Panel -> System -> Advanced
2. Click on Environment Variables, under System Variables, find PATH, and click on it.
3. In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
4. Close the window.
5. Reopen Command prompt window, and run your java code.
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
tzuyang said:
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
Click to expand...
Click to collapse
Have seen this error before (not related to bat file). You may need to revert to an earlier Java version.
TVPad 4 is fourth in a series of Android-based IPTV settop boxes targeting the worldwide Chinese communities at large, although it seems to work well as a basic Android TV box. Support for all its predecessors (TVPad 1-3) have been discontinued. This guide will only focus on TVPad 4, model M418. Also this device have been banned from US and upgrading it may "brick" it - more on this later.
The method I used below is gathered from various sources elsewhere but not much on rooting and ADB. This is a compilation of all the most important info in one place. I am not sure if its bootloader is locked or not, but the Android 4.4 kernel sources can be found at openlinux.amlogic.com.
Physical specs:
AmLogic S805 SoC: ARM Cortex-A5, quad-core 1.5Ghz, Mali450 graphics, 1080p H.265 support
~1GB RAM
microSD card slot
HDMI out
USB-A port
Hardware needed:
To fully complete the process you'll need:
Monitor/TV with HDMI port
USB hub
microSD card
USB drive (optional)
USB keyboard
USB mouse
The remote that came with your box
Files needed:
* TVPad 4 5.054 firmware + TWRP 2.8.1.0: https://tvpadtalk.ca/discussion/1071/downgrading-tvpad-4-to-5-054/p1
The TWRP seems to be the modified from the one for AmLogic k200. Only the one from above work; the one from TWRP themselves do not.
* TVPad 4 5.066 OTA update: http://www.phoneunlock.com/forum/viewtopic.php?f=5&t=590
If you have this box and are in the US, do NOT do 5.066 update; your box is going to be banned. Might as well go all out and repurpose it into a general purpose Android TV box; but for the rest of the world, this update directs your box to different servers where it's mostly business as usual. You should be able to go direct from 5.054 to 5.066 following this guide, despite what others say.
* Root zip: http://www.freak-tab.de/finless/s89_root_update.zip
* APK install hint file:
Create a file named batchinstall.banana with contents below:
Code:
directory=
checkapp=no
Preparation
1. Download the 5.054 firmware and unzip into root of your microSD card. You should have recovery.img and TWRP folder. They are the TWRP recovery and a 5.054 TWRP backup respectively. Devices boots from recovery.img on root of microSD card if detected.
2. NON-US ONLY: Download the 5.066 OTA update to microSD root.
3. Download root zip to microSD root.
4. Put batchinstall.banana and any APKs you want to install on your USB drive or microSD. There is a APK pack of 23 apps for Cantonese speakers or 29 apps for Manadarin speakers available out there, but I haven't bothered. I included an updated SuperSU, ES File Explorer (preferably an older version; I used 4.0.4.9; newer ones are heavily loaded with ads), VLC, Firefox, AdAway, Terminal Emulator (by Jack Palevich). The last 4 being open source should also be available from F-Droid. Substitutions can be made to taste but Terminal Emulator is required to enable ADB (see below).
Enter Recovery
You will need to use stock recovery for OTA update AND TWRP for 5.054 firmware and root.
1. Connect HDMI monitor and USB hub to device. Connect USB keyboard and mouse to the hub. Leave power disconnected.
2. Look for a hole on the underside. If you have one, stick an iPhone/iPad SIM ejector pin in it and feel for a button. If able, this is the recovery button and you may skip to step 6.
3. Pull off the 4 rubber feet on the bottom and remove 4 screws under them.
4. Pry around the seams and lift the bottom cover off.
5. You either have a recovery button on the PCB or an empty spot for it. If no button, you'll have to short the bottom two contacts where the button is supposed to be (with all ports on the top edge).
6. Insert microSD card into "TF" slot. IMPORTANT: Leave popped out to enter stock recovery; fully insert to enter TWRP.
7. Press and hold the recovery button (or short the contacts) while plugging it in. Keep it pressed (or contacts shorted) until the recovery or TWRP appears.
8. Operate stock recovery with keyboard and TWRP with mouse.
Re-flash 5.054 - Downgrade/Unbrick
People do this to recover from "use restricted" or some other server errors after this thing is sued out of the States. I have also used it to recover from a soft brick situation.
1. Fully insert microSD card. Enter TWRP.
2. Select Restore. Choose External SD for storage.
3. Select the only available package to restore.
4. Swipe to Restore.
5. When complete, do not reboot yet. Return to main menu and select Wipe. Swipe to Factory Reset.
6. US ONLY: Remain in TWRP and proceed to step 2 of rooting.
7. NON-US ONLY: Return to main menu and select Reboot, Recovery. Immediately after screen go blank, push the microSD card again to eject it. It will pop out half way. Leave it hanging there. Proceed to update 5.066 next.
Update to 5.066 - NON-US ONLY! New server and Play Store support.
1. Enter stock recovery.
2. Fully insert microSD card.
3. Select Apply update from EXT and press Enter.
4. Select your 5.066 update file and press Enter.
5. When update complete, unplug power. Proceed to rooting.
Rooting
This is too easy with TWRP.
1. Fully insert microSD card. Enter TWRP.
2. Select Install, then the root zip file. Swipe to install.
3. Reboot into system and proceed with initial setup.
Kingroot also works but leaves some very persistent crap and questionable apps on the system so I do not recommend rooting using it.
Sideload apps
Plug the USB drive with your apps and batchinstall.banana file into the device or hub. Batch installer will appear. Select Batch Install and check that all apps you are installing are there and checked, then select Install.
Enable ADB
TVPad 4 does not have a USB slave port so ADB is only through TCP/IP. Steps below assume you have adb working on your computer.
1. Connect a USB mouse if not already.
2. Move mouse to right half of top of screen then drag down. Click on the gear to enter regular Android Settings app.
3. Enable Developer Options - About Mediabox, click Build Number 7 times.
4. Enable USB Debugging in Developer Options.
5. Open Terminal Emulator (sideload it if you haven't already).
6. Type in the following:
Code:
$ su
(Grant root if prompted)
# setprop service.adb.tcp.port 5555
# mount -o remount,rw /system
(Make the same setprop change in /system/build.prop - uncomment or add the line)
# stop adbd
# start adbd
7. Find the IP address of your TVPad from its own over-simplified settings page.
8. Open a command prompt/terminal on your computer and do this:
Code:
> adb connect <TVPAD IP ADDRESS>
(Authorize your computer on the TVPad.)
> adb devices
(confirm its IP is listed and not "unauthorized")
> adb shell
$ su
(grant root if prompted)
#
(success!)
# chmod 660 /data/misc/adb/adb_keys
(Double check permissions the public key file of authorized ADB clients)
9. Reboot and check that the change stays.
You're done! Now you have full control of this little TV box even after its server go under for good.
Additional apps
Kodi 15.2 seems to work on this box. 16.1 is untested. 17.x will not work since it requires Lollipop. Download from kodi.tv.
If all you want out of TVPad is TVB programming, the official app TVBAnywhere works on this box. About US$100/yr subscription for its own original programming only. Oh and it doesn't serve the States either. Go figure.
The gapps framework added with 5.066 is very minimal and doesn't work for eg. maps. You'll need to get it from apkpure. Use version 11.0.38-030-155006848.
I'm still looking for a decent launcher.
Credits:
https://www.youtube.com/watch?v=6evvWebosnU
https://www.youtube.com/watch?v=ZtY_qdYzmPs
https://www.youtube.com/watch?v=W2heIbUdZVE
can we flash any other rom on TVPad 4 since we can install TWRP??
I rooted easily with kingroot apk. to get shell, I just used my laptop as proxy between wifi and lan, created a meterpreter reverse_tcp metaploit payload, connected back to my laptop, shell and then su...
3vilhomer said:
can we flash any other rom on TVPad 4 since we can install TWRP??
Click to expand...
Click to collapse
To be honest, I'm more interested in if we can get Lollipop on this thing, for that is required for Kodi 17.
For whatever reason I can't boot into the TWRP. I have all the recovery.img and TWRP folder located in the root directory of the SDcard and my SDcard is FAT32 formatted. What did I do wrong?
Suppport has been officially terminated for this box so, it will only be a normal TVbox.
I'm kinda wondering if the SoC supports at least lollipop. A custom rom would be cool to run Leanback apps with a few modifications
ya, is there anything we can do with this box now since most live tv apps doesnt work on it anymore
Do you know where I can grab the file for TVPAD1? I am not sure which model I have, is only written TVPAD on top and there is no 2S, Plus or anything else.
TvChina, a subsidiary pay TV app after TvPad 4 ceased operating on June 1st. TvPad, the parent company, together with its Blue TV etc, have gone bust due to lack of funds from global dwindling sales. Now that the box is useless, can someone upload a root file so we can wipe then reuse it for other purposes? Found a related message on Google but it's has been blocked. Thanks in advance. Wonder if someone can get hold of firmwares for UnBlock or evPad etc so we can tune this into other sites.
did anyone ever put a different android OS on this and got the IR blaster to work too??
3vilhomer said:
did anyone ever put a different android OS on this and got the IR blaster to work too??
Click to expand...
Click to collapse
They were able to upgrade to android lollipop here:
tvpad.ca/discussion/1993/tvpad4-upgrade-to-android-lollipop-5-1
The root file "s89_root_update.zip" link is not working anymore. Does anyone has a copy > please post it here.
Basic requirementsbut warning
Important: Please read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb. Setup instructions can be found here.
Enable USB debugging on your device.
Preparing for installationSamsung devices come with a unique boot mode called “Download mode”, which is very similar to “Fastboot mode” on some devices with unlocked bootloaders. Heimdall is a cross-platform, open-source tool for interfacing with Download mode on Samsung devices. The preferred method of installing a custom recovery is through Download Mode – rooting the stock firmware is neither necessary nor required.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Download and install the appropriate version of the Heimdall suitefor your machine’s OS
Windows: Extract the Heimdall suite zip and take note of the new directory containing heimdall.exe. You can verify Heimdall is functioning by opening a Command Prompt or PowerShell in that directory and running heimdall version.
If you receive an error, install the Microsoft Visual C++ 2015-2019 Redistributable Package (x86) on your computer.
Linux: Extract the Heimdall suite zip and take note of the new directory containing heimdall. Now copy heimdall into a directory in $PATH, a common one on most distros will be /usr/local/bin. For example cp heimdall /usr/local/bin. You can verify Heimdall is functioning by opening a Terminal and running heimdall version.
macOS: Mount the Heimdall suite DMG. Now drag heimdall down into the /usr/local/bin symlink provided in the DMG. You can verify Heimdall is functioning by opening a Terminal and running heimdall version.
info_outline
Note: These Heimdall suite distributions were built by LineageOS Developers Nolen Johnson (npjohnson) and Jan Altensen (Stricted), as the Heimdall suite executables distributed on the official Heimdall website were outdated and the repo mostly abandoned. Modifications were made to make it build and function on modern OSes.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Home + Power.
Now, click the button that the on screen instructions correlate to “Continue”, and insert the USB cable into the device.
For Windows user only: install the necessary drivers. A more complete set of instructions can be found in the Zadig user guide.
If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or Samsung Kies.
Run zadig.exe found in your extracted Heimdall directory.
info_outline
Note: For the interested, source and documentation for zadig.exe can be found here.
Choose Options » List all devices from the menu.
Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu.
Click Replace Driver, then selecting Install Driver from the drop down list built into the button.
If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select Install this driver anyway. You may receive two more prompts about security. Select the options that accept the warnings and allow you to carry on.
On your machine, open a Command Prompt or PowerShell (Windows) window, or Terminal (Linux or macOS) window, and type:
heimdall print-pit
If the device reboots that indicates that Heimdall is installed and working properly. If it does not, please refollow these instructions to verify steps weren’t missed, try a different USB cable, and a different USB port.
Installing a custom recovery using heimdall
Download the custom recovery.
check
Tip: Ensure you download the .img file and not the .tar or .tar.md5 versions.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Home + Power.
Now, click the button that the on screen instructions correlate to “Continue”, and insert the USB cable into the device.
On your machine, open a Command Prompt or PowerShell (Windows) window, or Terminal (Linux or macOS) window, and type:
heimdall flash --RECOVERY <recovery_filename>.img --no-reboot
check
Tip: The file may not be named identically to what stands in this command, so adjust accordingly. If the file is wrapped in a zip or tar file, extract the file first, because Heimdall is not going to do it for you.
A blue transfer bar will appear on the device showing the recovery image being flashed.
info_outline
Note: The device will continue to display Downloading... Do not turn off target!! even after the process is complete. but When the status message in the top left of the devices’s display reports that the process is complete, you may proceed.
Unplug the USB cable from your device.
Manually reboot into recovery, this may require pulling the device’s battery out and putting it back in, or if you have a non-removable battery, press the Volume Down + Power buttons for 8~10 seconds until the screen turns black & release the buttons immediatelywhen it does, then boot to recovery:
With the device powered off, hold Volume Up + Home + Power. but When the blue text appears, release the buttons.
info_outline
Note: Be sure to reboot into recovery immediately after installing the custom recovery. If you don’t the stock ROM will overwrite the custom recovery with the stock recovery, and you’ll need to flash it again.
Installing PixelExperience from recovery
Download the PixelExperience installation package that you would like to install or build the package yourself.
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Home + Power. When the blue text appears, release the buttons.
Now tap Wipe.
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Sideload the PixelExperience .zip package:
On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
Tip: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success/No error.
Once you have installed everything successfully, run ‘adb reboot’.
As a OnePlus 9 user who likes to root their phone mainly to allow Network Signal Guru to work (as well as a few other root things like AdAway) I had been trying to extract the boot.img the same way as I had done with a OnePlus 7T using Payload Dumper for Windows. However it looks like Payload Dumper has issues with extracting xx.img files (including boot.img) if the payload.bin file is bigger than 4.3 GB in size. So I've been looking to see if another method was possible that would work for our OnePlus 9 ROMs that are above this file size. As I use Linux Mint as my usual desktop OS & only fall back onto Windows for stuff that'll only run on that OS, I went to have a look to see if something could be done under Linux. Turns out there is an old thread elsewhere on XDA that almost nearly provides what is needed for this, and I thought I would gives details here that should work for the time of this post (March 2023).
This not only extracts the boot.img to patch in Magisk, but also extracts other xx.img files as well.
I'm using Linux Mint 21.1, but I'd assume that this will also work for similar Ubuntu builds or anything that is based on Debian.
Obligatory disclaimer: The following instructions I'm giving below have worked well for me several times in the past, however I am in no way responsible for screwing up or damaging your phone if you try and follow what I've written below. In extreme cases, a bad flash may require using the OnePlus MSM tool to completely reflash your phone. Back up anything important first before doing any of the following!
1. You will need to ensure that you have downloaded packages to be able to do adb & fastboot from the command line. You can check by running the following commands - if it's already installed with the latest versions, the terminal interface will let you know...
Code:
sudo apt install adb
Code:
sudo apt install fastboot
2. You will need to go to your software manager in LM21.1 and install both Python 3 & the Python Protobuf compiler. Just search for "Python 3" & "Protobuf-compiler" in the software manager and the first option for each search is what you should need - if they are not installed, install them.
3. Create a read/writable directory that will hold your ROM that you've just downloaded & other files that I'll mention soon. I just use a folder calls "ROM" in my Downloads folder (e.g. /home/lawhec/Downloads/ROM ), but you can choose wherever you want that suits you.
4. If you have not done so already, make sure you have the FULL package of your OnePlus 9 ROM downloaded. As of right now (March 2023) it seems the best way is to download the package using the Oxygen Updater app which is available on Google Play - more info available at oxygenupdater.com - just download the ROM to your phone and transfer it on to your computer into the folder you've created for it.
5. Download and save the following two Python scripts/files ("Right click" & "Save Link As") into the folder you have just created for your ROM (all credit to Gregory Cyxx at github.com/cyxx )...
https://raw.githubusercontent.com/c...payload/master/extract_android_ota_payload.py
https://raw.githubusercontent.com/cyxx/extract_android_ota_payload/master/update_metadata_pb2.py
6. Make sure in your file browser (Nemo in my case as it is the default for LM21.1 Cinammon, yours may differ) the window is open in the ROM folder that contains the two Python scripts above that you've just downloaded as well as a ROM package (ZIP file) you've downloaded (in my case from Oxygen Updater mentioned in step 3). Create a new folder for the extracted images to be written to - in my case I just call the folder "output" which is located at "/home/lawhec/Downloads/ROM/output" but again you can call it what you wish.
7. After you've created your output folder, in your ROM directory in the file manager window right-click on your mouse in a white or free space and select "Open in Terminal" - a command terminal will pop up defaulting to your directory.
8. In the command terminal, type the following command and press enter/return...
Code:
sudo python3 extract_android_ota_payload.py <<Your ROM.zip>> <<Your Output Directory>>
...for example, in my case the command would be either...
Code:
sudo python3 extract_android_ota_payload.py LE2113_11_F-75.zip output
...or for handiness you can type "sudo python3 extract_android_ota_payload.py " (remember to leave a space) and simply drag the ROM zip file to the command terminal, press space and then drag the output foler to the terminal line, which will look like in my case...
Code:
sudo python3 extract_android_ota_payload.py '/home/lawhec/Downloads/ROM/LE2113_11_F-75.zip' '/home/lawhec/Downloads/ROM/output'
...this will now run the python script you downloaded earlier that will begin extracting the ROM you've specified and will output all relevant xx.img files into your output folder, including the one we want, "boot.img" - there is no need to extract paylod.bin beforehand, the script will automatically do this for you. Once all xx.img files have been extracted the script will stop, depending on your computer this will take anything from 1-5 minutes, maybe longer on some very old or low spec'd computers - but just let it run its course. Once it is done you can then close the terminal window.
9. Now with the boot.img we've extracted, transfer this file on to your phone (the Downloads folder is usually a good choice). Now open Magisk and patch the boot.img file - once this has been completed, it'll generate a patched boot.img file named something like "magisk_patched-25200_12345.img" - copy and paste this patched boot image back on to your computer (into the folder you've been using will be fine here).
10. If your OnePlus 9 phone is connected to your computer via USB cable, disconnect it now. Then shutdown your phone into a power-off state then reboot it into fastboot mode - this can be done by holding down the volume up & down buttons, then holding down the power button and keep holding down all three buttons until you feel a vibration from your phone. Your OnePlus 9 should then boot into fastboot mode.
11. Now reconnect your OnePlus 9 to your computer via the USB cable and then open up a new display terminal (preferably by right-clicking in the file window of the directory where you saved your Magisk patched boot.img file). Enter the following...
Code:
fastboot devices
...you should then get a line featuring a block of numbers that should match the serial number that is displayed on your phone's display, followed by "fastboot", for example...
Code:
85f53405 fastboot
...if you get anything else, double check your connections at try again - if more than one device is displayed, disconnect the and try again to make sure that only one device is listed. It might also be the case that you don't have the proper drivers installed on your computer for your phone though in my case LM21.1 automatically recognises my phone, so I'm not of any direct help here I'm afraid for this, sorry.
12. Now you will be flashing your patched boot.img to your phone - this is where things can be a little nervous though as long as you do everything right nothing should really go wrong. Type the following into the command terminal, assuming you did so by opening a command terminal from the folder your Magisk Patched boot.img file is located...
Code:
fastboot flash boot <<Magisk Patched boot.img>>
...for example in my case the command line would be...
Code:
fastboot flash boot magisk_patched-25200_12345.img
...otherwise you will need to provide the location of where your patched boot.img is, so in this case...
Code:
fastboot flash boot '/home/lawhec/Downloads/ROM/magisk_patched-25200_12345.img'
...either way, your phone will now be in the process of getting its boot image replaced with the one patched by Magisk. This should take no more than a few seconds and that should be it done! You can then close the terminal window again.
13. Once you've patched the boot image, disconnect the phone from the USB cable to the computer and make sure that the screen on your mobile says "START" in green at the top, if it doesn't, use the volume keys to change this. Then just simply press the power button and your phone will now reboot, this can take a little bit longer than before as your phone's firmware has changed so give it time - (however if it takes longer than 10 minutes or so you might have a problem here) - once your home screen becomes available, give it a few seconds once you've entered before selecting the Magisk app. Once you've done this, Magisk should say that it is installed however to double check, use an app that requires root permissions either to work (e.g. Network Signal Guru) or to do additional things, like a simple root checker app that you can download from wherever you download your apps. If everything is good, then you've rooted your OnePlus 9!
Notes: This process will probably work for other firmware packages for various phones where the boot.img can be extracted to be patched by Magisk and then flashed via fastboot (assuming the bootloader is unlocked) which includes the OnePlus 7T's stock firmware, but I can give no guarantees for this. Once again, try at your own risk.
I would suggest to boot the magisk patched image and then doing a direct install from the app instead of flashing it directly. This way you can use the "Restore images" feature in the Magisk app that can be useful when doing incremental update.
Thank You for thinking of Us Linux Users !
Attempted to update to LOS 20 via ADB, and now my touch screen will not work. All the remedies here require a Windows system for the MSM tool, which I do not have...
barguybrady said:
Thank You for thinking of Us Linux Users !
Attempted to update to LOS 20 via ADB, and now my touch screen will not work. All the remedies here require a Windows system for the MSM tool, which I do not have...
Click to expand...
Click to collapse
You have a computer you can install windows on another partition it's not like you don't have the ability to use msm
stez827 said:
You have a computer you can install windows on another partition it's not like you don't have the ability to use msm
Click to expand...
Click to collapse
no comment
barguybrady said:
Yup.
Just gonna spend another 4 or 5 hours prepping a drive to somehow install windows just to fix a phone.
Maybe - No....
Click to expand...
Click to collapse
It does not take that long as a Linux user who has had to install for that exact reason it took maybe an hour or 2
lawhec said:
As a OnePlus 9 user who likes to root their phone mainly to allow Network Signal Guru to work (as well as a few other root things like AdAway) I had been trying to extract the boot.img the same way as I had done with a OnePlus 7T using Payload Dumper for Windows. However it looks like Payload Dumper has issues with extracting xx.img files (including boot.img) if the payload.bin file is bigger than 4.3 GB in size. So I've been looking to see if another method was possible that would work for our OnePlus 9 ROMs that are above this file size. As I use Linux Mint as my usual desktop OS & only fall back onto Windows for stuff that'll only run on that OS, I went to have a look to see if something could be done under Linux. Turns out there is an old thread elsewhere on XDA that almost nearly provides what is needed for this, and I thought I would gives details here that should work for the time of this post (March 2023).
This not only extracts the boot.img to patch in Magisk, but also extracts other xx.img files as well.
I'm using Linux Mint 21.1, but I'd assume that this will also work for similar Ubuntu builds or anything that is based on Debian.
Obligatory disclaimer: The following instructions I'm giving below have worked well for me several times in the past, however I am in no way responsible for screwing up or damaging your phone if you try and follow what I've written below. In extreme cases, a bad flash may require using the OnePlus MSM tool to completely reflash your phone. Back up anything important first before doing any of the following!
1. You will need to ensure that you have downloaded packages to be able to do adb & fastboot from the command line. You can check by running the following commands - if it's already installed with the latest versions, the terminal interface will let you know...
Code:
sudo apt install adb
Code:
sudo apt install fastboot
2. You will need to go to your software manager in LM21.1 and install both Python 3 & the Python Protobuf compiler. Just search for "Python 3" & "Protobuf-compiler" in the software manager and the first option for each search is what you should need - if they are not installed, install them.
3. Create a read/writable directory that will hold your ROM that you've just downloaded & other files that I'll mention soon. I just use a folder calls "ROM" in my Downloads folder (e.g. /home/lawhec/Downloads/ROM ), but you can choose wherever you want that suits you.
4. If you have not done so already, make sure you have the FULL package of your OnePlus 9 ROM downloaded. As of right now (March 2023) it seems the best way is to download the package using the Oxygen Updater app which is available on Google Play - more info available at oxygenupdater.com - just download the ROM to your phone and transfer it on to your computer into the folder you've created for it.
5. Download and save the following two Python scripts/files ("Right click" & "Save Link As") into the folder you have just created for your ROM (all credit to Gregory Cyxx at github.com/cyxx )...
https://raw.githubusercontent.com/c...payload/master/extract_android_ota_payload.py
https://raw.githubusercontent.com/cyxx/extract_android_ota_payload/master/update_metadata_pb2.py
6. Make sure in your file browser (Nemo in my case as it is the default for LM21.1 Cinammon, yours may differ) the window is open in the ROM folder that contains the two Python scripts above that you've just downloaded as well as a ROM package (ZIP file) you've downloaded (in my case from Oxygen Updater mentioned in step 3). Create a new folder for the extracted images to be written to - in my case I just call the folder "output" which is located at "/home/lawhec/Downloads/ROM/output" but again you can call it what you wish.
7. After you've created your output folder, in your ROM directory in the file manager window right-click on your mouse in a white or free space and select "Open in Terminal" - a command terminal will pop up defaulting to your directory.
8. In the command terminal, type the following command and press enter/return...
Code:
sudo python3 extract_android_ota_payload.py <<Your ROM.zip>> <<Your Output Directory>>
...for example, in my case the command would be either...
Code:
sudo python3 extract_android_ota_payload.py LE2113_11_F-75.zip output
...or for handiness you can type "sudo python3 extract_android_ota_payload.py " (remember to leave a space) and simply drag the ROM zip file to the command terminal, press space and then drag the output foler to the terminal line, which will look like in my case...
Code:
sudo python3 extract_android_ota_payload.py '/home/lawhec/Downloads/ROM/LE2113_11_F-75.zip' '/home/lawhec/Downloads/ROM/output'
...this will now run the python script you downloaded earlier that will begin extracting the ROM you've specified and will output all relevant xx.img files into your output folder, including the one we want, "boot.img" - there is no need to extract paylod.bin beforehand, the script will automatically do this for you. Once all xx.img files have been extracted the script will stop, depending on your computer this will take anything from 1-5 minutes, maybe longer on some very old or low spec'd computers - but just let it run its course. Once it is done you can then close the terminal window.
9. Now with the boot.img we've extracted, transfer this file on to your phone (the Downloads folder is usually a good choice). Now open Magisk and patch the boot.img file - once this has been completed, it'll generate a patched boot.img file named something like "magisk_patched-25200_12345.img" - copy and paste this patched boot image back on to your computer (into the folder you've been using will be fine here).
10. If your OnePlus 9 phone is connected to your computer via USB cable, disconnect it now. Then shutdown your phone into a power-off state then reboot it into fastboot mode - this can be done by holding down the volume up & down buttons, then holding down the power button and keep holding down all three buttons until you feel a vibration from your phone. Your OnePlus 9 should then boot into fastboot mode.
11. Now reconnect your OnePlus 9 to your computer via the USB cable and then open up a new display terminal (preferably by right-clicking in the file window of the directory where you saved your Magisk patched boot.img file). Enter the following...
Code:
fastboot devices
...you should then get a line featuring a block of numbers that should match the serial number that is displayed on your phone's display, followed by "fastboot", for example...
Code:
85f53405 fastboot
...if you get anything else, double check your connections at try again - if more than one device is displayed, disconnect the and try again to make sure that only one device is listed. It might also be the case that you don't have the proper drivers installed on your computer for your phone though in my case LM21.1 automatically recognises my phone, so I'm not of any direct help here I'm afraid for this, sorry.
12. Now you will be flashing your patched boot.img to your phone - this is where things can be a little nervous though as long as you do everything right nothing should really go wrong. Type the following into the command terminal, assuming you did so by opening a command terminal from the folder your Magisk Patched boot.img file is located...
Code:
fastboot flash boot <<Magisk Patched boot.img>>
...for example in my case the command line would be...
Code:
fastboot flash boot magisk_patched-25200_12345.img
...otherwise you will need to provide the location of where your patched boot.img is, so in this case...
Code:
fastboot flash boot '/home/lawhec/Downloads/ROM/magisk_patched-25200_12345.img'
...either way, your phone will now be in the process of getting its boot image replaced with the one patched by Magisk. This should take no more than a few seconds and that should be it done! You can then close the terminal window again.
13. Once you've patched the boot image, disconnect the phone from the USB cable to the computer and make sure that the screen on your mobile says "START" in green at the top, if it doesn't, use the volume keys to change this. Then just simply press the power button and your phone will now reboot, this can take a little bit longer than before as your phone's firmware has changed so give it time - (however if it takes longer than 10 minutes or so you might have a problem here) - once your home screen becomes available, give it a few seconds once you've entered before selecting the Magisk app. Once you've done this, Magisk should say that it is installed however to double check, use an app that requires root permissions either to work (e.g. Network Signal Guru) or to do additional things, like a simple root checker app that you can download from wherever you download your apps. If everything is good, then you've rooted your OnePlus 9!
Notes: This process will probably work for other firmware packages for various phones where the boot.img can be extracted to be patched by Magisk and then flashed via fastboot (assuming the bootloader is unlocked) which includes the OnePlus 7T's stock firmware, but I can give no guarantees for this. Once again, try at your own risk.
Click to expand...
Click to collapse
If Using the t-Mobile Variant - LE2117 - we are Unable to Install any OTA Updates with OxygenUpdater, and are promptly warned of this limitation upon install. Nevertheless, I forged ahead and,
Following this Method, I downloaded a LE2115_11_F.17.zip, and proceeded to use your helpful .py scripts to extract the boot.img file, and Flash it - promptly sending me to a Qualcomm CrashDump mode.
Having a chance to MSM back to "stock" LE2117 - 11.2.2.2 LE54CB, I am wondering if I should just let the t-Mobile Update, through "Settings >> System >> System update" to Update the Stock ( bloated !? ) OS with all that are available,
Then attempt to Extract a boot.img and Magisk patch it ?
Any Advice?
TIA