I have downloaded the relevant drivers and the unrooted device is recognized by Samsung Kies and various driver managers say that the drivers are up to date..
I have downloaded Odin 3.09 and unzipped it to a folder on the desktop. The folder contains Odin and and ini file.
I have downloaded what I believe to be the relevant tar.md5 file, called CF-Auto-Root-chagallwifi-chagallwifixx-smt8--.tar.md5, unzipped it and placed it in the Odin folder on the desktop.
I then run Odin and check that only the Auto-reboot and F.rest-Time are checked.
Using guidance found on this website I have pressed volume-down, home and power buttons and reached a screen showing several options none of which clearly states download-mode.
The instructions found here said press volume-down and then power.
This has taken me to a screen showing:
# Manual Mode #
-- Applying Multi-CSC.....
Applied the CSC code : XAR
Successfully applied the multi-CSC.
Now send the package you want to apply
to the device with "adb sideload <filename>....
When I connect the T800 to the laptop nothing happens!!!
Related
Ok I've tried following many guides but I cannot flash no matter what I do... I have Odin3 1.00 and I've tried the JH3 firmware... I've also tried the Oneclick JF6 firmware... each time it gets hung at "File Analysis". Is there something that I should have done beforehand that I'm missing here? The drivers are installed, Windows recognizes the devices... I've even tried with the SD card and SIM card out of the device and still no dice... This is what I do:
1.) Boot device holding Vol+ and Vol- (should I hold it until it boots or just start it and let go?)
2.) Once the device has the white triangle with an orange exclamation I then Open Odin3.
3.) I select the 512k PIT file.
4.) I then add the firmware file to the PDA and check the box.
5.) I then hit start...
After these steps nothing happens except "File Analysis".
Any ideas from anyone? I'm tearing my hear out because I really want to like this device and like android but if I can't address some of these issues then I can't really enjoy either...
-Michael
try a different USB port or even a different computer. It never works on my desktop where it always gets stuck at File Analysis, it works just fine on my laptop.
Try,
Start Odin, select pit and pda w/tar
Then start download mode on phone.
Then click Start on Odin.
itpromike said:
Ok I've tried following many guides but I cannot flash no matter what I do... I have Odin3 1.00 and I've tried the JH3 firmware... I've also tried the Oneclick JF6 firmware... each time it gets hung at "File Analysis". Is there something that I should have done beforehand that I'm missing here? The drivers are installed, Windows recognizes the devices... I've even tried with the SD card and SIM card out of the device and still no dice... This is what I do:
1.) Boot device holding Vol+ and Vol- (should I hold it until it boots or just start it and let go?)
2.) Once the device has the white triangle with an orange exclamation I then Open Odin3.
3.) I select the 512k PIT file.
4.) I then add the firmware file to the PDA and check the box.
5.) I then hit start...
After these steps nothing happens except "File Analysis".
Any ideas from anyone? I'm tearing my hear out because I really want to like this device and like android but if I can't address some of these issues then I can't really enjoy either...
-Michael
Click to expand...
Click to collapse
Turn on debugging on the phone, plug in the usb, open odin 3, open a command window and navigate it to your sdk/tools folder then type "adb reboot download" no quotes. Then pick your files in odin and start it. Make sure you put in that check mark on PDA as well. Hope it helps.
Clienterror said:
Turn on debugging on the phone, plug in the usb, open odin 3, open a command window and navigate it to your sdk/tools folder then type "adb reboot download" no quotes. Then pick your files in odin and start it. Make sure you put in that check mark on PDA as well. Hope it helps.
Click to expand...
Click to collapse
Where can I download a copy of the SDK from?
If you are getting into download mode don.t worry too much about the adb stuff. It does make it easier but if you are in download mode that isn.t your issue.
What version of windows are you using? On my win 7 64 bit machine it wouldn.t work until I ran it in compatibility mose for xp service pack 3. You may want to try that if you are on win 7.
Next time post it on the right section, this section is for development, not Q&A..theres a proper captivate section for that.
Rafyvitto
Thanks all for the suggestions I got it figured out.
I posted this in the Rooting thread, but figured it may be a more general questions other may have experienced.
I'm trying to root my GT-N8010 via the CM method. No matter what I do, Odin sits at "SetupConnection" and won't proceed. I tried:
- killing Kies via the task manager
- uninstalling Kies and using the SAMSUNG_USB_Driver_for_Mobile_Phones included in the OP link
- rebooting my PC
- using different USB ports on my PC
- running Odin as administrator
- moving Odin and the HighOnAndroidCWMRecoveryGTN8000.tar file to the root of my C-drive, to ensure there wasn't a folder path issue
When I boot my Note 10.1 to Odin Mode and plug it into my PC, Windows states the drivers were installed and my device is ready. I have no idea what else to try.
For reference, I'm running Windows 7 64-bit, fully up-to-date, and using the default Odin 1.85 that's included with the root package. I haven't tried a different PC, but I'd really prefer to do this on my home desktop.
Any other suggestions?
OK. Got it to work. Here's what I did:
- plugged the tablet into the first USB port on my motherboard (port 0)
- placed both the Odin folder and the HighOnAndroidCWMRecoveryGTN8000.tar file in a folder on the root of my C-drive, with a simple folder name ("root")
- when I ran Odin, I un-checked "Auto Reboot"
And that worked.
If you have PC follow these:
Try to download "kingo android" in your pc
Make sure you have the right drivers for your phone
then connect your device to pc via USB cable
open kingo android and start
If you dont have a pc and you have recovery mode in your device follow these:
search this: root (your device name) .zip file
and if you are successful put that zip file on root folder(the folder you see when you open your built-in file manager)
switch your phone to recovery mode
volume up, volume down, and menu button are the controls
navigate it to "apply update from sd card"
then choose your the zip file
If you dont have a pc and dont have a recovery mode follow these:
download "framaroot" "rootmaster" all apk
Hope it helps
Not working on mine - T310XXUBOD2
get lost
false advertising by OP
Hello. Has anyone rooted the Ulefone Power 6 yet? Im looking to have TWRP installed onto my new Power 6. My goal is to figure out a way to add user profiles, as it currently does not have them activated. I read online that you could edit the .prop to have any android activate the user profiles, but i cannot do this without my phone being rooted. Thanks in advance.
Start Here
Dvalin21 said:
Start Here
Click to expand...
Click to collapse
Sorry, This is for the original Ulefone Power, not the Power 6. Different phones. The instructions didn't lead me to anything useful. I have since update my phone to the latest firmware via the stock update app. I still haven't found a successful way to root the Power 6. There is this thread (https://www.getdroidtips.com/root-ulefone-power-6/), but the ADB commands to not work, and does not fastboot my phone to install the patched image. But either way, the instructions do not include a TWRP, so Im back to square one. HELP!
How to root Ulefone Power 6 (Build Power_6_SF1_V07) Updated 9/22/2019
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
Pre-Requirements:
Device battery charged up to 50%.
Developer Options enabled with OEM Unlocking and USB Debugging enabled
Remember to take a full backup of device data (Internal Storage, SMS), it will get formatted.
A Windows or Mac PC/Laptop is necessary to flash Magisk
A USB cable to connect your device with your PC
Download Links:
Download Minimal ADB Fastboot 1.4.3 (Portable). Extract it to your desktop.
It's best to give administrator privileges to the tools before you use them. To give them admin privileges:
Right click on adb.exe and select "Properties" at the bottom of the menu. Click on the "Compatability" Tab and check the "Run this program as an Administrator" box. Click on the "Apply" button and then the "OK" button to close the properties window.
Repeat the same process for the "cmd-here.exe" and the "fastboot.exe" files.
Ulefone USB Drivers. Extract it to your desktop and make sure you install the drivers.
MTK USB Drivers. Extract it to your desktop and make sure you install the drivers.
Latest Ulefone Power 6 Stock ROM. Or you could make a back up yourself. (latest rom as of 2/25/20 is GQ3081SF1_M860B1_Ulefone_20190921_V07(Non-EU) ).Extract it to your desktop.
MTK SP Multi Port Download Tool. This will be used to flash the most recent Ulefone rom on your device. Extract it to your desktop.
Download Magisk Manager
After downloading the Stock ROM (will be a .ZIP file), extract it to your PC.
Connect your device via USB cable
Find the "boot.img" file inside the Stock Rom folder you just extracted and copy only the "boot.img" file to your devices storage.
Copy Magisk Manager.apk to your devices storage
Using your device, install Magisk Manager
Open the Magisk Manager on your device.
Select "Install" from the first option next to "Magisk is not installed" and again select install.
Now, tap on "Select and Patch a File".
Go to your devices storage where you have copied the "boot.img" file earlier and select it.
Magisk will start patching the boot image.
Once the boot image is patched, Magisk will save the image on your "Download" folder located on your devices storage.
Locate the patched image (magisk_patched.img) and copy the "magisk_patched.img" to your PC. Make sure the patched image (magisk_patched.img) is inside the same folder as the extracted ADB and Fastboot tool folder on your desktop.
Open/run MTK SP Multi Port Download Tool
Click on File from the Menu located at the top right and select "Open Download Agent File"
Locate and select "MTK_ALLInOne_DA.bin", located in the same folder as the MTK SP Multi Port Download Tool folder.
Press the "Open buton" to select the file and close the window.
Now, click on the "Scatter File" button located at the top left.
Locate and select the XXXXXXXX_scatter.txt file located inside the extracted Ulefone Power 6 Stock Rom folder.
Press the "Open buton" to select the file and close the window.
Now, tick the "BootRom+PreLoader COM Sel All" check box located under the "scatter file" button.
Now, Click on the "Scan" button located at the bottom right.
Select Yes from the pop up window
Now, power off you device and disconnect your device from your PC by removing the USB cable from your device.
Now, reconnect the USB cable to your device while it is powered off.
MTK SP Multi Port Download Tool should detect your device and a green bar should appear confirming the connection with the words "Scan Success!" to the left of the green bar.
Press the "Stop all" button located at the bottom right
Disconnect and reconnect your device from your PC
Uncheck the "BootRom+PreLoader COM Sel All" box and check only the line with the green bar.
Click on the tiny "Start" button located to the right of the green bar.
You can confirm the flash was successful when the words "PASS" is visible to the right of the tiny "Start" & "Stop" buttons
Once the flashing is complete, you can close MTK SP Multi Port Download Tool and power on your device.
Configure your device to get to the home screen (skipping as many options as you can. You will have to format one more time) and enable Developer Options, OEM Unlocking and USB Debugging again.
Make sure your device is connected to your PC.
Now, you need to open up a command window (cmd window) inside the Minimal ADB Fastboot 1.4.3 (Portable) folder. To do this, open the "cmd-here.exe" file.
Next, enter the following command in the cmd window:
adb devices
(this command will confirm your device is connected to your PC via ADB )
Your device will show a pop up window asking for permission to connect via ADB. Click on the "Always Trust This Device" and Accept the connection
If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
adb reboot-bootloader
(This command will boot your device into fastboot/bootloader mode. It will turn off and the device will have a black lit screen)
Check that your device is connected to your pc by entering the following command:
fastboot devices
(this command will confirm your device is connected to your PC via fastboot/bootloader mode ) If successful, you should see the word "Device" to the right of your devices name on the list that the cmd window created.
Next, enter the following command:
fastboot flashing unlock
(if nothing happens, press the Volume up+ on your phone to start the unlocking of the bootloader)
(this will unlock your bootloader)
Next, enter the following command:
fastboot getvar unlocked
(this will confirm you have unlocked your bootloader. It will say "unlocked: yes")
Next, enter the following command:
fastboot flash boot magisk_patched.img
(This will replace your stock image with the patched image you created using Magisk Manager)
Next, enter the following command to reboot your phone:
fastboot reboot
Install magisk manager using your file manager. Make sure to follow directions when it asks you to give special permissions to install.
Open Magisk Manager and click on "OK" when it starts up and asks you for "additional setup".
Congratulations! Your device is rooted.
Extra notes:
If you come across a red watermark with the Chinese words and "Tee Keys" and/or "Google Keys" on the top right of your devices screen, this is how you fix it.
make sure your device is turned on and connected to your PC.
Open "cmd-here.exe" located in the Minimal ADB Fastboot 1.4.3 (Portable) folder.
Next, enter the following command:
adb shell pm uninstall -k --user 0 com.mediatek.factorymode
(This command will not do anything at the moment, but will remove the watermark after you reboot your device)
Next, enter the following command to reboot your device:
adb reboot
The watermark should be removed when your device restarts again.
ENJOY!
19Henry83 said:
OK. It was tough, but I finally found a way to root the Ulefone Power 6. I still haven't figured out a way to install TWRP, but that's because i have to build a custom recovery, and that's too advanced for me. So, anyone is welcomed to help out with building a custom recovery for TWRP. As for the root, This is what you will need:
. . . . .
. . . . . . . . . . .
. . . . . . . . . . . . . . .
ENJOY!
Click to expand...
Click to collapse
Thanks a heap for all these instructions, would not have been able to do this without them.
Just a few extra pieces of information for anyone else caryring out the above steps:
- If you your stock ROM doesn't have a file manager in order to open/execute the MagiskManager APK file then using Chrome to download the APK file will allow you to execute it.
- in the SP Multi Port Tool, after checking the line with the green bar and clicking start you'll notice the time in seconds counting next to the start button. At this point you may need to unplug your USB cable and replug it in order for the SP Multi Port Tool to detect the devices and actually start properly
- If the SP Multi Port Tool requires a checksum.ini file you can follow the instructions on the hovatek site (Google 'checksum.ini generatemediatek hovatek' I'm a new user so can't post links):
Note there is a download link for the CheckSum_Gen.zip file which will require you to register for an account on the hovatek website. You can create a junk/throw away account with a fake email as it doesn't require email confirmation. Also all of the files inside the CheckSum_Gen.zip folder need to be placed inside of the stock ROM folder where the scatter file is located.
- The watermark can only be removed after the MagiskManager carries out its additional setup and after root access is complete.
Still hoping to find a compatible TWRP recovery. If anyone builds one please let us know!
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
I Need help please ,, I need the TWRP Recovery, Tool / Utility for the Ulefone Power 6, I have looked for it in many web pages and I cannot find it, all the ones I find have the same name "3.3.1 Power 6" and not It works for me when I install them, I get the same recovery that I had when I try to enter
jiroscop said:
Hi, 19Henry83
I did try your method and it works great. I rooted my Power 6. The thing is I did this in hope to fix a freezing touchscreen issue. Touch screen frezzes and I need to lock/unlock my phone constantly to fix it. Now I'm convinced this is not a software issue and I will return the phone to the seller. So I wanted to get back to the original firmware. When I do that however there is still that red watermark and my IMEI is deleted. Is there any way to get back to the factory software and not have the red watermark, as I assume it will void my warranty.
Click to expand...
Click to collapse
Hello Jiroscop. I had the same problem and only noticed after i read your post. Now, a couple months later, i managed to use an IMEI changer to insert my IMEI found on my original box where my phone came in. It should have two IMEIs. I don't know if i can explain on this forum. Try researching it on your own and get back to me if you cannot find a way to fix your phone.
NOTE: you will need your original IMEI's, changing the IMEI's with anything other than the original ones will brick your phone.
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’.