Database Info

[ROOT] Zopo ZP950+ ver. 16GB - Androd 4.2.1

The following procedure has been tested by me only on ZP950 + 16GB model. Although the procedure is created generally for the MTK6589 processor and it has been already tested on other devices, could / should also work for other devices based on MTK quad-core processor.
!! Important !!
Success with this application void warranty on your device.
The procedure is based on exploits found by motochopper and the necessary files can be downloaded from here
The procedure works on both linux (run.sh) and Windows (run.bat).
Here are the steps to follow:
Download and unzip the package into a folder
Enable USB debugging on your device. Check that using the command adb devices your device is seen.
Open a DOS window (or in case of linux the unix shell) on the new extracted folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disconnect the device from the PC, run the run.bat command and press enter.
The program will wait for the device. Then connect your device to the PC
The program will upload the necessary programs, install the exploit and SuperSU.apk and after will launch the exploit to enable root permissions.
When the process is finished, press a button and the program will restart the phone
When the phone is rebooted you will have the root permission and SuperSU application installed.
At first launch of the program will ask you to perform an upgrade to a newer version.
To test whether the procedure for root works, connect the terminal to the PC and type the commands
Code:
adb shell
at the shell prompt given command
Code:
su
The SuperSU app will ask you whether to grant root permissions or not, and once accepted, the shell prompt will change from $ to #.
Tested on my zp950+ Build number 20130427-162946

Reserved for future use

Recovery
The recovery partition is only 6 mb so, some latest recovery don't fit in partition and cant'be installed.
(To be honest, there is a procedure that allow you to increase the recovery partition but you must shift all other partitions and reflash all, but is very dangerous and i am not sure about it).
Here there is an adapted version of CWM (6.0.3.0) that works with the default partion size.
PS: Your device must be rooted, and i am not resposabile of damage to your phone.
The steps are:
Downloa the recovery from here
Conncet the device to pc, open a shell (or dos) where you have downloaded the recovery and run this commands:
Code:
adb push cwm-6.0.3.0-zp950.img /sdcard/
adb shell
su
dd if=/sdcard/cwm-6.0.3.0-zp950.img of=/dev/recovery
This will copy the new recovery on your sdcard,
open a shell on your phone and get the root grants
flash (manually) the new recovery into recovery partition
After the operation ends, you can type
Code:
adb reboot recovery
to reboot the phone in recovery mode, on power off it and restart it pressing POWER_ON and VOLUME_UP together.
PS: here there is the default (stock) recovery for who wants to restore it.

Cannot find 'recovery.img'

Hi..I have Android L installed on my N5 and want to root it..so I have been following THIS guide, to install custom recovery and then I plan on rooting it using THIS thread..
While following the first guide to install TWRP..I am getting the following error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone please help me with this error..I tried the TAB to search for the recovery.img..but it did not work
if I hit Tab after 'fastboot flash' then I am not getting first 'recovery' option.
Not sure if this will help..here are the contents of the slimmed down android sdk I downloaded from first guide:

rockstar283 said:
Hi..I have Android L installed on my N5 and want to root it..so I have been following THIS guide, to install custom recovery and then I plan on rooting it using THIS thread..
While following the first guide to install TWRP..I am getting the following error
Can anyone please help me with this error..I tried the TAB to search for the recovery.img..but it did not work
if I hit Tab after 'fastboot flash' then I am not getting first 'recovery' option.
Not sure if this will help..here are the contents of the slimmed down android sdk I downloaded from first guide:
Click to expand...
Click to collapse
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.

GTI6speed said:
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.
Click to expand...
Click to collapse
was having the same problem and this actually fixed it, thank you sir

All, please have a read of my "adb and fastboot. What is it?" thread. It can be reached via the sticky roll up link in my signature.
You shouldn't need to put recover where you put it. My thread explains how to use it properly.
Sent from my Nexus 5 using Tapatalk

GTI6speed said:
Navigate to your platform tools folder in command prompt. The path you have specified in the screenshot is not where your recovery.img is located... so keep typing ''cd.. enter'' until you're back at C:\ in the window, then type cd android-sdk-windows and hit enter, then cd platform-tools, and it should be able to find the recovery image.
Click to expand...
Click to collapse
Thanks a lot mate..that did the trick..DUMB mistake

[Recovery] [Stable] TWRP 3.0.2-2 For XOLO BLACK

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello fellow BLACK owners, I know that HIVE has not got an update for a long time and is full of bugs but today I present you guys TWRP 3.0.2-2 for XOLO BLACK
CHANGELOG
Code:
TWRP 3.0.2-2:
Changed mount points.
TWRP 3.0.2-1:
Fixed a mount issue.
----
What works?
Everything, as far as I've tested it, everything works fine
----
Any bugs?
I haven't found any! If you do, please report.
----
How to flash?
Make sure you have unlocked your bootloader, guide can be found here.
Download, install and open Minimal ADB and Fastboot.
Execute adb reboot bootloader and your device will reboot into fastboot mode with the XOLO logo showing up. To ensure that your device is connected execute fastboot devices command and your device should be listed.
Download TWRP 3.0.2-2 for BLACK and then place it inside the Minimal ADB and Fastboot folder which could be found at C:\Program Files (x86)\Minimal ADB and Fastboot
Now execute fastboot boot twrp-3.0.2-2-black.img (If you don't want to flash the recovery and want to test it out before you do) and the device will temporarily boot into recovery mode.
If you want the recovery image to be flashed to your device then execute fastboot flash recovery twrp-3.0.2-2-black.img
Now, to reboot normally, execute fastboot reboot
How to reboot into TWRP recovery?
When your device is booted up normally, you can go to recovery mode via adb reboot recovery command or using third party apps which offer reboot options.
When your device is powered off, you can reboot to recovery by pressing both volume keys at the same time + power key.
----
CONTRIBUTORS
Me
lj50036 (Huge contribution, thank you!)
----
SOURCE
https://github.com/lj50036/android_device_xolo_black
----
NOTE: The tutorial part was a bit copied from here, sorry, I'm a bit lazy hehehe.

MINE!!!

lj50036 said:
MINE!!!
Click to expand...
Click to collapse

Bootloop Ulefone armor 6

Hello everyone, I have a big problem with my device, it happens that the system started to fail and after that it turned off, when I turned on it stayed in a bootloop and I can only access the fastboot, the question is that my device does not have the OEM and I never did any modifications so it doesn't have recovery either.
So far I have tried to install for fastboot the boot.img and system.img from the original firmware but I get the error "remote: not allowed in locked state" because the bootloader is locked
Any recommendation?

Reflash original Stock ROM by means of ADB Sideload method

jwoegerbauer said:
Reflash original Stock ROM by means of ADB Sideload method
Click to expand...
Click to collapse
but I can't use recovery and it doesn't have TWRP installed either.
The truth is that I am quite new to this subject but it would help me a lot if you guide me through that process.
In addition, the stock rom offered by ulefone is in .tar.gz format

Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...

jwoegerbauer said:
Both Stock Recovery and TWRP aren't needed to perform an ADB Sideload: both mentioned recoveries internally simply make use of this method.
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
You at any time can convert a tar.gz archive to a zip archive. GIYF ...
Click to expand...
Click to collapse
How about, I was trying to access with ADB, however when I put adb devices, the device does not appear, perhaps because I did not have the USB debugging before the bootloop, I was trying with different commands and nothing happens, but it does appear in the device manager. I'm sure I have the correct drivers because I tried another device with USB debugging enabled and it works fine.
Attached image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It should be obvious to you that ADB can't work as expected if USB debug option isn't got enabled on Android.

how can the bootloop be solved if only fastboot is available?
And the manufacturer flashing tool doesn't recognize the phone?
I cannot reflash the phone.

[Root Guide] Shanling M3X DAP

SAFTY INFORMATION: Whatever you do, its on your own responsibility. Your warranty might be void and there is the risk of bricking your device!​
So this is what I did:
Tools
Magisk-v25.2.apk
Latest M3X Firmware
ADB Tools
EDL.py
Click to expand...
Click to collapse
Extract the boot.img from M3X Firmware V1.62- Do not open, just copy.zip
Copy the Magisk-v25.2.apk and boot.img to your Shanling M3X
Install the Magisk-v25.2.apk
In Magisk press "Install" in the upper right corner
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On "Method" select "Select and Patch a File" and choose your boot.img then press "Let's Go"
Spoiler
When Magisk is done, you can close the App and transfer the patched boot.img to your PC.
On your M3X, activate Developer Mode. Settings > About device > Tap multiple times on the Build number
In Developer Options, activate USB debugging
On your PC extract the platform-tools.zip and install EDL.py
Plug the M3X into your computer with a good USB cable. You may be promted to allow USB debugging on the M3X - check "Always allow from this computer" and OK
Open a Command/Terminal window and navigate to your platform-tools folder
Use following command
Code:
adb reboot edl
the display of your M3X will now turn black
In the Command/Terminal window navigate to your EDL.py installation
From now on you could brick your device, please advance only if you know what you are doing!
I would highly recommend to do a backup of everything with the commands mentioned on the EDL Github site​
14. Use following command to dump your stock boot.img
Code:
edl r boot boot.img
the stock boot.img will appear in your EDL folder, move to a safe space.
15. Now copy your Magisk patched boot.img into the EDL folder and run following command:
Code:
edl w boot boot.img
16. When EDL is done, you can disconnect your M3X. You might need to hold the powerbutton for 20-30 seconds until it leaves edl mode and starts booting.
17. Congratulations! You rooted your M3X
Further information: There seems to be a undocumented method using the tool "QFIL" but I dont know anything about it. Might ne worth a try.
Have fun

Thanks for this tutorial. Can you drop some screen shots and an overview of what you're able to change now that you're rooted.
I've been thinking of getting a HiBy R6. But it being on Android 9 is annoying. My guess is if I can get it rooted, that it's possible to update to a newer version of Android.

Hi, I’m trying to root my M3 Ultra with this method but I’m facing a problem.
On windows when trying to enter « edl r boot boot.img » it says me that « r » is not a command…
Any help would be really appreciated please
Thanks in advance for replying