Develop Bugs

Rooting Every Spreadtrum SC6820/SC8810 phones ! (1.5)

Hello,
In this thread I will teach you every method I had to use to root any Spreadtrum devices, Starting with the riskless ones to the reckless ones.
I have to warn you that the last root method (using ResearchDownload to load a modified system.img) may be dangerous ! (because of possible partition table changes)
The others methods are pretty safe, don't be afraid by them if you do exactly what I wrote.
Theses processors are also named SP6820 and SP8810, it's exactly the same processor, it's just some misnaming from Chinese sellers.
Theses methods do work on the newest Spreadtrum CPUs, like the SC7710 (the 3G WCDMA model), and the more powerful SC8825/SC6825 (dual core).
Why buying a Spreadtrum based phone ?
They are really cheap, and they work amazingly well ! They can play some games and emulators very well, that's unexpected for such low end devices (50$ or less)
They usually only have 256MB of RAM but despite that, they still runs well ! (I tested a lot of games and some 3D games are working flawlessly, pretty amazing) - I discovered that they are using zram (or other swap methods) to provide more RAM by compressing it when needed. That's pretty neat and really helps with such a small amount of RAM !
They are very good as a portable multimedia device, to read mails, browsing the web, play some games, mp3, videos.
As a 2G phone they are competent, but the 2G modem is not as good as the one in MTK processors. (It takes longer to load something in the same conditions)
Boot very fast, and have decent battery life. (3-4 hours of video out of a 1200 mAh battery - 5-6 hours out of a 1800 mAh)
Why you should not ?
Not true anymore, but they were extremely difficult to root in some cases.
They don't seem to be well tested ... You can have a microphone so quiet nobody will be able to ear you. But it's easy to fix as you can see here: http://forum.xda-developers.com/showthread.php?p=38731407
They don't have any form of usable 3G support. (except the SC7710 who have WCDMA 850/2100 compatibility)
They usually have only 256MB of RAM again. So that can be a problem when you are, for example, using Opera Mobile Classic with more than 3 tabs. And make the transition between apps longer.
SC6820 and SC8810 model are all using Android 2.x, even if some are marketed as Android 4.0 phone (very big and blatant lie !)
They usually use android 2.3, but some are only Android 2.2 phones ! (The fake Android 4.0.3 for instance is usually only android 2.2)
SC6825 and SC8825 seems to only have a (real this time) Android 4.0.3 firmware. 4.1 are better is often advertised, but it's again ... lies ... Android 4.0 is not really suitable for phones with only 256 MB of RAM, so SC6825/8825 phones are pretty rough on the edges. Using more than one tab on the default web browser is asking for troubles for example.
They all use the MocorDroid Firmware. It's some kind of fork of Android that use NON-Standards and sometime buggy Launchers and they often use alternative keyboards like Go Keyboard which is kind of a bad choice considering the RAM and ROM constraints on theses devices ...
The only difference between the SC6820 and the SC8810 is the support for the Chinese form of 3G.
If you don't live in china, that means this two processors are essentially the same. (Don't trust sellers, the 8810 is NOT WCDMA "3G" compatible)
Some phones with the fake Android 4.0.3 based on 2.3.5 will brick themselves nearly 2 months after you first used it. It's a really weird behavior of this early Spreadtrum firmware. So if you have this firmware, just do whatever it takes to root it, make a backup and install CWM as soon as possible to be able to recover from this possible breakage. It's only a problem with a fraction of Spreadtrum phones, but you will be very happy if you have installed CWM before encountering it ^^ (applicable only if you bought one in 2012)
A lot of fakery in the Spreadtrum scene. For example fake MTK6515/MTK6572 phones that are in fact just SC6820/SC6825 phones with a firmware modified to lie its processor ID to populars android benchmarking tools like Antutu Benchmark.
If you are searching for a 512MB RAM phone, you'd better go for an MTK(6575/6572 or better) Phone. As you will never find a real 512MB Spreadtrum phone in the jungle of lies you are looking at ...
On all model with 2.3.5 based firmware (SC6820 and SC8810 essentially), you can have a lot of problems with the SIM card detection on some sim cards. For example I can't call somebody with mine, but I can answer a call or send/receive SMS ... Very weird bug ...
This bug seems to be related on the type a sim card you have. With some their is no problem at all.
I can confirm that it's working flawlessly on SC6825 and 8825 based phones with the real 4.0.3 based firmware.
Why rooting it ?
Because a lot of them come with a lot of sh*tty softwares, including the bad launcher and keyboard.
Because they can come with a "Virus" that can send SMS messages to china (so you have to pay for unwanted international SMS cost)
I myself have this Virus on one of my phones, as of now, I haven't noticed anything unusual. Just the useless, unkillable com.android.caivs.app process eating 15 MB of RAM doing nothing. (It is a significant waste of ram on such devices)
(As of now I only seen this malware on Feiteng devices - You can share your experience with this thing down bellow)
More about CAIVS here: http://web.archive.org/web/20110812021151/http://www.cseed.cn/chinese/news/portfolio2.htm
That virus was on most of the earliest Spreadtrum phones but don't seem to be a worry nowadays. But I haven't tried any new Feiteng devices. They were so poor in quality that I will never buy feiteng again so find it by yourselves if you feel adventurous xD
How-to do that ?!
If you are lucky you will be able to root your phone by traditional means.
If you are not, you can root them by manually adding the root utilities to the ROM.
I will describe every methods that you should try in order of difficulty and risks.
Before doing any of that, go to the android setting -> applications -> Development -> Check USB Debugging.
Universal Root utilities
Theses methods are safe, and the second one is, as of now, working on every Spreadtrum phones flawlessly !
1.1 - Z4Root
Just try z4root !
http://forum.xda-developers.com/showthread.php?t=833953
z4root is a little tool to root Android 2.2 and sometime work on 2.3
It's known to work on devices with the fake Android 4.0.3 based on 2.2 and MocorDroid 2.2.2
It may work on more of them, just try, there is no risks at all.
Make sure you have at least 50 MB of available space on the /data partition before trying this. (not the SDCard, the Applications Space)
Try a temporary root to see if it works, then you can do the permanent root.
You will maybe have to try it 2 or 3 times before it works.
Even if it doesn't work, reboot the phone after this. Because it can eat your battery while running in the backgroung if it fails.
1.2 - vRoot
vRoot is a chinese tool to root many devices !
It's proved to work very well with Spreadtrum (and MTK) devices. I used it successfully on a lot of Spreadtrum devices, even the most recent ones (SC8825).
You only need a Windows Computer (I personally use it on Windows 7 32bits).
Then download it from here: http://www.mgyun.com/en/getvroot
Install it and then open it.
As of now you only need to plug your USB cable to your computer, and then click on the Root button. (you don't need to do anything else, don't touch your phone)
Once it's done and the phone rebooted you will be rooted !
The root app is some kind of custom chinese one, but it's working properly.
Don't try to replace it with SuperSU as SuperSU don't seem to work properly on Spreadtrum devices.
If you want to understand what the root app is saying, try to set the language on your device to English.
2 - Custom Firmware Flash
Please never use any custom firmware available in .pac file format ! Or at least, don't use them before doing a full backup of your current firmware !
Feiteng A7100 (only if you have the mt6515_c910_ht_en_4.0_v01 rom/firmware on it !!! If not, don't touch it, you will end up with a brick ! Or screen reversed, or other strange bugs): http://forum.xda-developers.com/showthread.php?t=2149396
If you have a Feiteng A7100 I really recommend NOT TO USE this rom ! Why ? Because it only works on a fraction of A7100, newer releases of the same phone don't use the same firmware. With this tutorial here, you can root your A7100 easily and way safer. Please go to "4-" on this tutorial to know how to root your A7100.
If you append to find some others Custom roms for spreadtrum devices, or are making one, please send me a PM, I will link them here.
3 - Fastboot to the rescue !
If every fast, simple and secure methods are not working, then this will be difficult my friend !
3.1 - Find Fasboot
First, let check if we have fastboot in your phone !
Fastboot is a little tool inside the bootloader. It's here to help you flash the firmware.
Not every Spreatrum phones have it, so let's check if you are lucky !
You can access it by powering on the phone up while holding a key.
First power off your phone.
Then hold some button like volume+
while pressing this button, press and hold down the power button.
Keep holding the two buttons until the screen light up.
You should now have something on your screen. Maybe a system diagnostic tool (a menu with a set of system tests, that's totally useless) or maybe the recovery mode (a screen with a warning sign, and now your phone is stuck here until you pull out the battery) or, and that means victory, a screen that says "Fastboot".
If you are not on fastboot, but are on the Recovery or the System Test, turn the phone off again and try another button press at boot time exactly like I said before.
This time, try the Home button if you have one, or the Volume-.
You should also try buttons combinations. Like volume up and down at the same time. Home + vol Up, etc and maybe the 3 at the same time ...
(if you just boot as if nothing was pressed, you maybe have to unplug the battery, wait for a while and put it back before powering the phone on. Theses things are also not working when the usb/charging cable is plugged in - if some keys combinations are not doing anything, it's perfectly fine, it means they don't trigger any hidden boot mode)
If nothing bring fastboot up, you have to use the Spreadtrum Debug tool "ResearchDownload" ...
So Skip to "4-" ! ^^
3.2 - Install the drivers
If you append to find Fastboot, we will have to install the PC part of it !
Like every android phone, you have to install adb and his drivers to access the Android Debug Bridge.
You can find them and learn how they work here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
On Ubuntu or Debian Linux you just have to install them that way:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
You also have to install the phone drivers if you are using Windows:
ADB Drivers: http://www.mediafire.com/download.php?c5nf3rlhxmxhu4x
Debug Drivers: http://www.mediafire.com/download.php?2tyg0k2xp3ejgyg
Mirror: http://www.mediafire.com/?o9km8vl287ev24j
Then you will have to tell adb what phone to use. By that I mean adding the PCI ID to a text file to tell adb that this peripheral is compatible.
The Spreadtrum PCI ID is 0x1782
add this line to "Your user directory/.android/adb_usb.ini"
Code:
0x1782
3.3 - Using fastboot to load CWM (Clockwork Mod)
CWM work on some of theses Spreadtrum devices, most of the time, the screen is reversed, but it works !
On some phone, you will be presented with a blank screen, but CWM will work ... That will just be very difficult to navigate ... (don't bother and use another method if you append to be in this boat)
Here are the recovery images available for Spreadtrum device to my knowledge:
* http://www.mediafire.com/download.php?u6uyignmdcpillt - extracted from a random SC6820 that I don't remember
* http://www.mediafire.com/download.php?bosnfcq9n65mtc5 - i9270+
* http://www.mediafire.com/download.php?xem49dy5dh99ml0 - 5830, S5830, Q5830, Q206 and GT-N9300 (maybe more)
* http://www.mediafire.com/download.php?adfwq6b5268qb58 - S9300 (SC6820A S3 Clone)
* http://www.mediafire.com/download.php?y2f7aaan4b00l1m - Feiteng GT-A7100 and probably more Feiteng devices.
* http://www.mediafire.com/download.php?lg7m6v49efzpnjk - 6500-TV or S560
* http://www.mediafire.com/download.php?6xn977jjsuusjan - N9300 (I9300 Clone)
* http://www.mediafire.com/download.php?d68wc334qn47tdd - S930 or N8820
If your device is not listed or the one for your device doesn't work, try them all, even if your phone is SC6820 and the recovery was made for SC8810, if none are working, we will have to flash the entire system partition, which is a lot more difficult and dangerous ...
Flashing CWM to the phone:
Linux Only: Initialize ADB:
Code:
sudo adb kill-server
sudo adb start-server
Boot your phone in fastboot mode.
Be sure your device shows up:
Code:
fastboot devices
if your device show up, it's time to flash
Code:
fastboot flash recovery recovery.img
It's flashed ! Let's reboot now.
Code:
fastboot reboot
Start on CWM, if it works, you can start to root the phone !
Download this patch: http://www.mediafire.com/download.php?131nsw87afzwb5v
Put it on the root of your SD Card.
Now you will have to boot on CWM, he is on the same key combination than the old useless recovery was. (Most of the time Volume- and Power)
You can also try this command with adb:
Code:
adb reboot recovery
Now it's the perfect time to do a full backup of your firmware with CWM, so please do so, that can come in handy. (please go to the end of this tutorial after rooting your phone to know how to make a FULL backup. CWM will only make a partial one.)
choose apply update.zip
Choose the file you have put on your sd card before
Apply it then reboot.
This update.zip have pushed everything needed to root your phone in the right place, you should be rooted now !
If you have an error like:"Can't mount /sdcard" you may have to try with another SD Card and be sure your SD Card if formated as Fat32.
3.4 - Using Fastboot to load a modified system partition image
Please follow the instructions down bellow on how to "5 - Create a rooted system partition image"
When you have done your Rooted system partition image, flash it like that:
Code:
sudo fastboot devices
#if your device show up, it's time to flash
Code:
sudo fastboot flash system system.img
#It's flashed ... Now let's reboot with all the apprehension of the world
Code:
sudo fastboot reboot
If it boots (should boot), you will be up and rooting !
4 - Spreadtrum ResearchDownload tool to the rescue !
First, if you have fastboot, use fastboot ! It's simple, more reliable, faster. It's bottomline better !
If you don't have fastboot or can't figure out how to bring him up on your phone despite trying for about an hour. This tool will most likely work.
First, you should use Windows XP 32bits. Even real XP or in virtualbox.
It might work on windows 7 32 bits and 64 bits but you will have to tweak the system to allow installation of non signed devices drivers ...
ResearchDownload work as this:
First you start the Channelserver - This thing is here to make a bridge between the tools and the driver.
Then you start ResearchDownload.
Now you can make a full firmware flash (you should not !! It's a terrible idea !) or flash a single partition. But to do that, unfortunately, you should have a compatible set of fdl files.
Finding them on google is impossible, you have to extract them from your full firmware .pac file.
If you can't find your firmware on the Internet, you will have to try every single one you can find from others firmwares. I gathered all the fdl files I could find in a single package, so it won't be that difficult.
It's highly probable that you will find one that will work with your phone. This thing have to boot the phone and flash the Nand Flash chip. I'm pretty sure there is not a lot of different ways to do this on a single processor.
I really don't know the risks of using a wrong fdl set. But we haven't seen any risks at all yet. Some will work on your phone, others will just do nothing. You will just have to try every single one until one work.
I named the folders with the names of the phones I know working with theses. So it will be easier to find the good one. (A7100, 6500-TV, 5830, Q206 and S930 users will feel very lucky ^^)
4.1 - Learn how ResearchDownload Work
First you have to install the drivers, you can find them here:
ADB Drivers: http://www.mediafire.com/download.php?c5nf3rlhxmxhu4x
Debug Drivers: http://www.mediafire.com/download.php?2tyg0k2xp3ejgyg
Then you have to plug your phone to your computer with your micro usb cable. Your phone have to be powered on.
Be sure every pieces of hardware are detected and installed correctly.
As you can see, this phone is not just detected as an ADB device, or as a mass storage device.
It actually have an internal serial port to usb adapter !
In other words that means this processor provide a way to flash his nand very easily even if it is fully bricked. It's a rare and pretty good feature you don't see that often. In fact, most of the time you have to solder a real serial port yourself on the phone motherboard, then have to use a Serial to USB adapter to have this level of access to the hardware.
So yes, back to tutorial.
Now you will have to unplug your phone and turn it off.
You have to download the debug tools, you can download them here: http://www.mediafire.com/download.php?rngukh111vqfr8h
First you have to start the channel server, you will have to disable your firewall for this app, it's because this tool use a network protocol to communicate with the other tools.
Then open ResearchDownload.
ResearchDownload is a weird flashing utility, it can open a .pac firmware file and can make a .pac out of .img files. You also can flash .img files and that's what we will do. But unfortunately it can't make a full backup ... So be careful !
The cog logo is here to let you open a .pac file. We don't need that as we probably don't have it.
The "two cogs logo" let you configure the flash utility.
Click on this to bring a new window.
On the download settings window, click on select product then choose your type of phone. (SC8810 or SC6820, it doesn't really matters if you take the wrong one out of those two.)
Then uncheck "Select All Files" as you don't have any of theses.
You can see FDL1 and FDL2 are still checked, and you don't have those files ...
As they are needed to start the Flash utility, we will have to find them.
I came across only 3 different FDL1 files, but for theses FDL1 it seems every phone have his own FDL2.
You will have to find the ones that work for you.
Here is an archive of nearly every FDLs available: http://www.mediafire.com/download.php?c6q2gxobccv32oj
Choose one FDL1, and one FDL2 located in the same folder. (you can choose a File with a right click on the FileName blank space in front of FDL1)
Click on OK.
Then click on the "Play button" saying start download.
It may show some warning, it's not a problem.
Now, press Volume Down on your phone, then you have to plug it on the USB Port, still holding the button.
You can release the button when the flash begins.
You may have to press an other button than Volume-. Some phones are reported to use the Home Button instead.
You may also have to remove, wait a while, and reinsert the battery before holding volume- or after the flashing procedure to be able to start the phone.
If ResearchDownload shows you an error or timeout, try another set of FDLs Files. Keep trying until you find one pair that work !
If it works the flashing process should start right away. Just a millisecond after Windows have detected and initialized the device when you plugged it.
When you have the right FDLs, you can go to the next step, flashing something useful ^^ (we haven't flashed anything as of now, just been searching for a compatible flashing bios)
If your working FDLs folder does not have the name of your phone, please tell me what phone you have and what FDLs you used so I can rename them.
4.2 - Using ResearchDownload to load CWM (Clockwork Mod)
Do exactly as said before, but check the "Recovery" checkbox on Download Settings. and choose one of theses CWM images:
* http://www.mediafire.com/download.php?y2f7aaan4b00l1m - Feiteng GT-A7100 and probably more Feiteng devices.
* http://www.mediafire.com/download.php?lg7m6v49efzpnjk - 6500-TV or S560
* http://www.mediafire.com/download.php?6xn977jjsuusjan - N9300 (I9300 Clone)
* http://www.mediafire.com/download.php?d68wc334qn47tdd - S930 or N8820
* http://www.mediafire.com/download.php?xem49dy5dh99ml0 - 5830, S5830, Q5830, Q206 and GT-N9300 (maybe more)
* http://www.mediafire.com/download.php?bdl1qr7orsj4ebr - extracted from a random SC6820 that I don't remember
* http://www.mediafire.com/download.php?6g1t6057p6c8wpt - i9720+
* http://www.mediafire.com/download.php?adfwq6b5268qb58 - S9300 (SC6820A S3 Clone)
When you flashed one successfully, try to boot on recovery (Usually by holding Volume- while holding the power button until the screen light up).
If your device is not listed or the one for your device doesn't work, try them all, even if your phone is SC6820 and the recovery was made for SC8810, if none are working, we will have to flash the entire system partition, which is a lot more difficult and dangerous ...
Download this patch: http://www.mediafire.com/download.php?131nsw87afzwb5v
Put it on the root of your SD Card.
Now you will have to boot on CWM, remember, he is on the same key combination than the old useless recovery was.
You can also try this command with adb:
Code:
adb reboot recovery
Now it's the perfect time to do a full backup of your firmware with CWM, so please do so, that can come in handy. (please go to the end of this tutorial after rooting your phone to know how to make a FULL backup. CWM will only make a partial one.)
choose apply update.zip
Choose the file you have put on your sd card before
Apply it then reboot.
This update.zip have pushed everything needed to root your phone in the right place, you should be rooted now !
If you have an error like:"Can't mount /sdcard" you may have to try with another SD Card and be sure your SD Card if formated as Fat32.
4.3 - Using ResearchDownload to load a modified system partition image
Now we are in deep **** ! This can be tedious ... You will need to drink a lot of coffee, then you will probably pull your hair off, but it's possible to root every single Spreadtrum devices this way !
Please follow the instructions down bellow on how to "5 - Create a rooted system partition image"
When you have done your Rooted system partition image, reboot on Windows, then flash it like that:
Do exactly as said on the paragraph on how ResearchDownload works, but check the "System" checkbox on Download Settings, and choose your modified system.img file to flash it on the device.
As it is still not tested at all, you will have to pray some kind of Spreadtrum God and hope it will be successful ...
The first boot after the flash can be very VERY long. It's perfectly normal.
After the flash is done, please make a full backup (see bellow how you can do that), so I can make a Clockwork recovery partition working with your phone.
You may need to flush your data partition with CWM to avoid some crazy bugs after the flash. You will have theses bugs because of the partitions realignment that might occurs as a result of using a slightly different FDL set as the manufacturer.
Don't even try to do a factory settings reset before installing CWM, as I don't know what monster can lie ahead if you do a factory reset without any working recovery installed
(If your phone doesn't boot after the flash, it is possible to flush the data and cache partition with ResearchDownload. I will explain it, if needed !)
5 - Create a rooted system partition image
Please always try the CWM method first ! There is no risks at all to destroy your phone if the recovery is not working. Here we are making a new system image to flash on the system partition, this partition contain the Android operating system. I will try to explain everything as good as I can, but if you make a mistake, if you don't read my warnings, you can brick your phone very easily !
That will be difficult ... And you will have to use a Linux computer, or Linux in Virtualbox, or in a Live CD, basically you will need Linux somewhere on your computer ^^
Why ? Because we will have to preserve unix permissions on an extracted tar archive ! Trust me, you will probably brick your phone if you do that on windows ...
#Install ADB
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
#Configure ADB
Code:
mkdir ~/.android
Code:
echo 0x1782 > ~/.android/adb_usb.ini
#Start the ADB server
Code:
sudo adb kill-server
sudo adb start-server
#Just let's check just in case if your device is already rooted
Code:
adb shell su -c id
Possible answers:
uid = 0 (root) gid = 0 (root) - your phone is already rooted ! (if you haven't noticed it, it's because superuser.apk is not installed, so just push it and install it via ADB and you are rooted !)
SU: Permission denied - You are not rooted ... Good luck then !
#Now we will backup the system partition !
Code:
adb shell tar -cf /mnt/sdcard/system.tar system
Please pay attention to the errors !
There will be missing files, and we will have to add theses by ourselves after the backup to pretend to have a full backup.
Here is the archive for the known missing files: http://www.mediafire.com/download.php?fm1z5ujc75bg268
If you have more than theses:
Code:
tar: can not open 'system/etc/dbus.conf': Permission denied
tar: can not open 'system/etc/bluetooth/audio.conf': Permission denied
tar: can not open 'system/etc/bluetooth/auto_pairing.conf': Permission denied
tar: can not open 'system/etc/bluetooth/input.conf': Permission denied
tar: can not open 'system/etc/bluetooth/main.conf': Permission denied
tar: system/lost+found: Permission denied
tar: Error exit delayed from previous errors
Then you should just give up, or tell me so I can send you the missing files.
Note: Lost+found is not important, it's just a folder automatically created by Linux to collect any corrupt files.
#Now we will pull this nearly full backup to our computer. Please keep it preciously somewhere secure.
Code:
adb pull /mnt/sdcard/system.tar
#Warning, theses next steps have to be made ONLY on Linux on an ext2/3/4 partition ! Please never attempts to do this on Windows or On Linux on a FAT32 partition.
#untar the archive
Code:
sudo tar -xvpf system.tar
#now we will restore the files we have not been able to backup.
#Download this archive if you haven't done this before: http://www.mediafire.com/download.php?fm1z5ujc75bg268
#Then extract it on the same folder as you extracted your system.tar file with this command:
Code:
sudo tar -xvpf btdbus.tar
#Now it's time to add the root utilities, you can download them from here: http://www.mediafire.com/download.php?v69nm172heos17o
Code:
sudo tar -xvpf root.tar
sudo cp Superuser.apk system/app/Superuser.apk
sudo install -m 06755 su system/xbin/su
#Now we will get rid of this virus ! (the file name can be something else. Like caivs.apk, or some random numbers at the end)
Code:
sudo rm system/app/eyuSales_20121116.apk
#And now you will have to make a flashable system image with this tool, included in the root.tar archive
Code:
sudo ./mkyaffs system system.img
#Now you can reboot your phone in fastboot or use researchdownload to flash your new System image.
6 - Do a full nand backup
Here is how to do a full nand backup of your beloved Spreadtrum: http://forum.xda-developers.com/showthread.php?p=39270468
7 - Don't forget to remove to caivs Virus
When you are rooted, you can remove the Virus or any preinstalled apps using Link2SD.
I suggest you to remove everything you have preinstalled if it is available on the Google Play Store (except the keyboard or the launcher !!!). For example if you have an old version of ES File Explorer on your phone preventing you from updating it, you can remove it safely, then install the updated version from the the Play Store.
Never try to remove something that you don't know what it is !
For the Launcher or keyboard. You can remove them only if you installed a new one on the System partition and tested it successfully !
-----
I want to thanks every peoples at http://forum.china-iphone.ru and Yekdall for being one of the first to type something in English about spreadtrum firmware modding !

Data missing?
First of all, thanks a lot for tutorial! Unluckily there is missing the data that i should copy back into the tar and then the img-file. Could you upload the btdbus.tar and the root.tar?
Thanks again, have a nice day!

keulepeter said:
First of all, thanks a lot for tutorial! Unluckily there is missing the data that i should copy back into the tar and then the img-file. Could you upload the btdbus.tar and the root.tar?
Thanks again, have a nice day!
Click to expand...
Click to collapse
I'm uploading them right now ^^
By the way, what phone are you rooting ? I will try to make a "compatibility list", so I need the model number, and the brand name if any.
Good luck !
EDIT: I added the missing links

Are the sc8810 and sp8810 the same processors?

lynnox said:
Are the sc8810 and sp8810 the same processors?
Click to expand...
Click to collapse
Yes exactly the same, just a different way to name it.

ElectronikHeart said:
3 recovery images are available for Spreadtrum device to my knowledge:
1 http://www.mediafire.com/download.php?u6uyignmdcpillt
2 http://www.mediafire.com/download.php?bosnfcq9n65mtc5
3 http://www.mediafire.com/download.php?xem49dy5dh99ml0
Try them all, if none are working, we will have to do that the other way ...
Download this patch: """"""Link missing as of now, I have to upload it"""""""
Put it on the root of your SD Card.
Now you will have to boot on CWM, he is on the same key combination than the old useless recovery was.
choose apply a update.zip
Choose the file you have put on your sd card before
Apply it then reboot.
This update.zip have pushed everything needed to root your phone in the right place, you should be rooted now !
Click to expand...
Click to collapse
patch pls. (update.zip)
I'll try to load CWM even though at the moment I can only get into recovery. I have the exact same model as H_Bler's which is why I've been focusing more on his thread. From your description on how to access fastboot, I assume that it's the diagnostic mode when UpVol + Pwr is pressed. I never saw anything that said fastboot. The only thing unusual when I was going through the menus was I always got an error when I try the 4th or 5th option. Unfortunately, I can't really try it again because I can't access it anymore. That goes without saying the I can't work with IMG files as well.
5 - Spreadtrum ResearchDownload tool to the rescue !
Now we are in deep **** ! This is not tested as of now ... So come help me ! You will need to drink a lot of coffee, then you will probably pull your hair off, but we will know if it's possible to root every single Spreadtrum devices !
5.1 - Using ResearchDownload to load CWM (Clockwork Mod)
5.2 - Using ResearchDownload to load a modified system partition image
Click to expand...
Click to collapse
Something to look forward too.
I want to thanks every peoples at http://forum.china-iphone.ru and Yekdall for being one of the first to type something in English about spreadtrum firmware modding !
Click to expand...
Click to collapse
I've also been going here. I even tried 3 of the ROMs but I always get the verification failed message. I know it might be too much, but exact links for the thread would really be much appreciated (to be honest, I can't even remember exactly where I got the ROMs. All I remember is that the thread had a lot of collapsible trees.
ElectronikHeart said:
I'm uploading them right now ^^
By the way, what phone are you rooting ? I will try to make a "compatibility list", so I need the model number, and the brand name if any.
Good luck !
EDIT: I added the missing links
Click to expand...
Click to collapse
If and when I get my phone fixed/replaced. I'll try your method first. =P

jvrey5 said:
[Lot of things ...]
Click to expand...
Click to collapse
Well the thing you have when you push up and power is the system test menu. It's located on the android system partition. It's not fastboot.
Fastboot should be something that says "Fastboot" in red letter, or something else unusual.
If you have not fastboot you should use Spreadtrum Researchdownload to flash your phone, I will write the tutorial about it soon.
I really can't link you the thread on the russian forum, first because it will probably confuse you, and also because it's spread everywhere on so many threads it's unbelievable ... That's why I'm doing this centralization work for you ^^
I will post a list of ROMS for recovery purpose. Your phone seem to be bricked. I don't know how you've done it (I really want to know what you phone is and how you've bricked it, that will help me to write the warnings necessary to avoid such cases).
I have 14 roms for Spreadtrum devices, maybe one will work for your phone.
I just want to know what your phone is ^^ Please tell the name of your phone on your posts everyone and if you know how to find it, the exact name of your firmware.
PS: I will upload the patch soon, I'm just searching for a file hosting service that will keep it up and not erasing it 2 hours after I uploaded it ^^
EDIT: Link to the update.zip for rooting you device via CWM added.

Tutorial updated: Spreadtrum debug tools method added.
It may now be possible to root even Spreadtrum devices without Fastboot mode available.
Please feel free to tell me if it works !

ElectronikHeart said:
Tutorial updated: Spreadtrum debug tools method added.
It may now be possible to root even Spreadtrum devices without Fastboot mode available.
Please feel free to tell me if it works !
Click to expand...
Click to collapse
need help

Question
Dear Spreadtrum Master!
Please, can you help me with this problem:
I have a Star I8160 phone with Spreadtrum 6820 and 256 MB ROM. It seems, that everything is working fine, the ROM and the phone is fast, and cool. But when i try to use the phone as a phone, i talk to the phone, and the others just only hearing pieces of my sentences. Sometimes the phone is very-very silent, i need to shout for the others to hear. I thought, that this is a microphone problem, so i replaced the microphone. But nothing changed. I had 2 phones from this type, and both produces the same fault, so i think maybe the problem will be with the ROM. What do you think, is it possible? If so, can i replace my normal rom, which is DM_BASE_12A_w12.43 (sc6820_modem) 11-02-2012?

question
Hi ElectronikHeart, i need help
I have a feiteng a7100, and i flash a rom with ResearchDownload.exe, in the flash operations tab i choose the option to erase all flash. Now i have a brick phone. Do you have a copy of nv.bin? Do you know how to recover from it? how can i reflash nand?
thanks

gtxphoenix said:
Dear Spreadtrum Master!
But when i try to use the phone as a phone, i talk to the phone, and the others just only hearing pieces of my sentences. Sometimes the phone is very-very silent, i need to shout for the others to hear. I thought, that this is a microphone problem, so i replaced the microphone. But nothing changed. I had 2 phones from this type, and both produces the same fault,
Click to expand...
Click to collapse
The Master hasn't been in the past few days so I'll try to answer your issue as best I can.
Usually, the phones are designed for a specific region/country. It's possible that your ROM was built for a different one. How sure are you that the ROM which you are replacing it with will work for you? (I assume that you have a backup and you know how to load ROMs) Also, you might want to try editing the build.prop it increase/maximize reception.
To be honest, this is actually a complicated approach. From what you said, it seems that you've made other troubleshooting steps on your own. Since you really did not mention all of them I'm basing my response on what you said.
Let's try to stick to the basics first. Why did you replace the microphone in the first place? If the same issue happens with 2 other phones from this type, I don't think the mic is the problem. Also, does this mean that you can hear them fine, but they have a hard time hearing you? Have you tried using the stock sound recorder on your phone? Is it also choppy? Have you tried using Skype? You don't really have to call anyone, you just need to make a test call.
When using the device as a phone (eg. making calls, sending SMS, MMS, or connecting to the internet using EDGE or 3G), you're actually relying mostly on your carrier/service provider. How many signal bars do you get? The easiest way to test signal related issues would be by using a different SIM or using a different phone. (When you try a different phone, I suggest using a GSM one - the ones that can only make calls or do SMS.) It's highly possible that there's already something wrong with your SIM.
---------- Post added at 01:17 AM ---------- Previous post was at 01:08 AM ----------
jmss said:
Hi ElectronikHeart, i need help
I have a feiteng a7100, and i flash a rom with ResearchDownload.exe, in the flash operations tab i choose the option to erase all flash. Now i have a brick phone. Do you have a copy of nv.bin? Do you know how to recover from it? how can i reflash nand?
thanks
Click to expand...
Click to collapse
ElectronikHeart hasn't checked in the past few days, so I hope you don't mind me butting in.
When you say brick, does it mean that you don't even have recovery mode? If you don't, try to see if you can put CWM. Once successful, you can try to use the A7100 ROM if your original one was a mt6515_c910_ht_en_4.0_v01 rom using the update.zip

jvrey5 said:
The Master hasn't been in the past few days so I'll try to answer your issue as best I can.
Usually, the phones are designed for a specific region/country. It's possible that your ROM was built for a different one. How sure are you that the ROM which you are replacing it with will work for you? (I assume that you have a backup and you know how to load ROMs) Also, you might want to try editing the build.prop it increase/maximize reception.
To be honest, this is actually a complicated approach. From what you said, it seems that you've made other troubleshooting steps on your own. Since you really did not mention all of them I'm basing my response on what you said.
Let's try to stick to the basics first. Why did you replace the microphone in the first place? If the same issue happens with 2 other phones from this type, I don't think the mic is the problem. Also, does this mean that you can hear them fine, but they have a hard time hearing you? Have you tried using the stock sound recorder on your phone? Is it also choppy? Have you tried using Skype? You don't really have to call anyone, you just need to make a test call.
When using the device as a phone (eg. making calls, sending SMS, MMS, or connecting to the internet using EDGE or 3G), you're actually relying mostly on your carrier/service provider. How many signal bars do you get? The easiest way to test signal related issues would be by using a different SIM or using a different phone. (When you try a different phone, I suggest using a GSM one - the ones that can only make calls or do SMS.) It's highly possible that there's already something wrong with your SIM.
---------- Post added at 01:17 AM ---------- Previous post was at 01:08 AM ----------
ElectronikHeart hasn't checked in the past few days, so I hope you don't mind me butting in.
When you say brick, does it mean that you don't even have recovery mode? If you don't, try to see if you can put CWM. Once successful, you can try to use the A7100 ROM if your original one was a mt6515_c910_ht_en_4.0_v01 rom using the update.zip
Click to expand...
Click to collapse
I dont have recovery mode, the phone doesnt turn on. I already try to put CWN but it doesnt work. I need nv.bin file for sc6820a for rewrite nand flash.

jmss said:
I dont have recovery mode, the phone doesnt turn on. I already try to put CWN but it doesnt work. I need nv.bin file for sc6820a for rewrite nand flash.
Click to expand...
Click to collapse
Now we really need the Master

gtxphoenix said:
Dear Spreadtrum Master!
Please, can you help me with this problem:
I have a Star I8160 phone with Spreadtrum 6820 and 256 MB ROM. It seems, that everything is working fine, the ROM and the phone is fast, and cool. But when i try to use the phone as a phone, i talk to the phone, and the others just only hearing pieces of my sentences. Sometimes the phone is very-very silent, i need to shout for the others to hear. I thought, that this is a microphone problem, so i replaced the microphone. But nothing changed. I had 2 phones from this type, and both produces the same fault, so i think maybe the problem will be with the ROM. What do you think, is it possible? If so, can i replace my normal rom, which is DM_BASE_12A_w12.43 (sc6820_modem) 11-02-2012?
Click to expand...
Click to collapse
Hi,
I had the same problem with one of mine. You just have to use a diagnostic tool from Spreadtrum and adjust the microphone amplification level. I will start a thread on that subject and link it there.
It seems to be a very common problem with Spreadtrum phones, but it is, most of the time, very easy to fix.
edit: here is the link: http://forum.xda-developers.com/showthread.php?p=38731407
WARNING: Don't ever flash if you don't have a working copy of the original firmware somewhere (a complete backup that you have tested your ability to flash back) The first step to do a complete backup, if the manufacturer don't want to send you the firmware, is to successfully root your firmware)
Don't flash if you have a microphone problem, nothing good will happen, this problem is not firmware related AT ALL.

jmss said:
Hi ElectronikHeart, i need help
I have a feiteng a7100, and i flash a rom with ResearchDownload.exe, in the flash operations tab i choose the option to erase all flash. Now i have a brick phone. Do you have a copy of nv.bin? Do you know how to recover from it? how can i reflash nand?
thanks
Click to expand...
Click to collapse
Oh god ! Why have you checked that option ^^
I may be able to dump my nv.bin file from the a7100 I just bought. (If I recall correctly, the nv.bin contain the imei so I will have to edit it to use your imei instead, imei are written in the battery compartment)
Can you try flashing it a second time entirely, It's possible that your uboot partition (what manage the early time boot operations), is not flashed properly.
Even without the nv partition you phone should be able to boot android, you will just not be able to use the phone as a phone. (make a call and everything)
Try with a better micro usb cable, Chinese ones can be very cheap and corrupt data on the way to the phone.
If your phone is still able to flash using ReasearchDownload that is.

Re: 4.5 - Do a full nand backup and help me make you a new CWM recovery
ElectronikHeart said:
4.5 - Do a full nand backup and help me make you a new CWM recovery
Please if you have rooted your phone using this method, and can't use the CWM method, that mean I can do a CWM that work on your device !
Now that you are rooted, you can make a full backup of your phone with ADB !
#open adb shell:
Code:
adb shell
Code:
I still have to explain this if someone needs it
Then send me you boot.img file and I will send you a recovery.img that you can flash to your recovery partition.
That will help new users to root a lot faster the same phone as you, and will make your life easier is you have to restore a backup.
Click to expand...
Click to collapse
>>>
I have also the same kind of chinese android phone, having a model # S930 with the same cpu chipset SP8810 (aka. samsung galaxy s3 clone), i've successfully rooted my chinese android phone, and installed some very usable apps like link2sd & titanium backup pro, i want also to have a full backup of my phone using your methods & ideas, can you help me? where can i find my boot.img so that you can make me my recovery image for my phone? my phone don't have any compatible clockworkmod recovery, but it have a native recovery mode option which work on an update.zip or fastboot....i hope you can help me make my phone recovery image with a rooted features... Thanks!

earl22online said:
where can i find my boot.img so that you can make me my recovery image for my phone?
Click to expand...
Click to collapse
So, you already have tested every recovery already posted ?
To make a backup of your boot.img, you will have to do a full backup manually using the Android shell. I will make a tutorial about this, and link it here.
It's pretty easy as you already rooted your phone.
When you have your backup I will, post a recovery.img file suitable to your phone.
Please keep an eye to this post. I will post the tutorial very soon.

ElectronikHeart said:
Oh god ! Why have you checked that option ^^
I may be able to dump my nv.bin file from the a7100 I just bought. (If I recall correctly, the nv.bin contain the imei so I will have to edit it to use your imei instead, imei are written in the battery compartment)
Can you try flashing it a second time entirely, It's possible that your uboot partition (what manage the early time boot operations), is not flashed properly.
Even without the nv partition you phone should be able to boot android, you will just not be able to use the phone as a phone. (make a call and everything)
Try with a better micro usb cable, Chinese ones can be very cheap and corrupt data on the way to the phone.
If your phone is still able to flash using ReasearchDownload that is.
Click to expand...
Click to collapse
I already try with tree micro usb cables. when i try to flash with researchDownload it failed at nvitem (after FDL2).
can you post a link to your nv.bin to test it ?

jmss said:
I already try with tree micro usb cables. when i try to flash with researchDownload it failed at nvitem (after FDL2).
can you post a link to your nv.bin to test it ?
Click to expand...
Click to collapse
I just bought my A7100, so you will need to wait 2 weeks for me to dump it. Maybe you should try asking to the guy who have made the rooted rom for the A7100 ?
I will, none the less, make a full backup of my phone as soon as I receive it.

[Root] [Rom] [Dev] [Recovery] Archos 50 Platinum Dev Topic (Gen11)

Tweeks:
Camera Tweek (You need busybox installed for this), or you can unpack the zip and apply the patch manually/setting the permission corectly.
It will improve the overall video recording quality, by increasing the size limit cap of the video (old setting 600 Kb vs new 1200 Kb)

Custom Firmwares
Reserved

Recovery
CWM WITH ACCESS AT THE SYS_BOOT PARTITION ======>>>>> Bigger chance in bricking your device if you sleep while you flash something.
CWM NON TOUCH / NO ACCESS TO SYS_BOOT
Way to flash:
Version 1)
- enable usb debugging
- install adb drivers
- use the command adb reboot bootloader
- use the command fastboot flash recovery recovery.img
Version 2)
- shut down the phone
- press the volume key minus and power key
- use the command fastboot flash recovery recovery.img
Do not forget to unpack the zip files.
Please have in mind that with the no_sys CWM, you cannot restore the phone to stock using an official update.

Unbricking
Copied from here
Here's a small tutorial for people who bricked their phone while formatting the sys_boot partition in CWM Recovery. When you format that partition, nothing works except a screen shows up saying "RESET FOR ENTRY QPST DOWNLOAD". This screen is also known as the Qualcomm Diagnostic Mode.
Requirements:
A linux distribution (Ubuntu)
sys_boot.img (https://docs.google.com/file/d/0BxJJu-wXKdltTE90SGtEMmFQZHM/edit)
Follow the steps to restore the sys_boot partition:
1. Connect your phone to a pc using the cable
2. Install the drivers if necessary:
https://dl.dropboxusercontent.com/u/17562266/USB Modem Driver.rar
3. Open your terminal
4. Type "lsblk" (without the quotes).
You should see a list, showing every connected disk and partition. Look for a partition with a size around 50M. This is the partition we need, so remember the corresponding name under the 'NAME' column. It can be "sdc", "sdd" or "sde" followed by a number.
5. Cd to the directory you placed sys_boot.img in
cd [filename]
6. Type "sudo dd if=/dev/NAME of=sys_boot.img bs=512
Replace NAME with the name you got from lsblk, and press enter.
The output should look something like this:
3959420000 bytes (3866621 KB) copied, [ time spent], [KB/s]
7. Remove the cable from your device, do a battery pull and try to boot your device
Normally, it should boot correctly. If you formatted the /system partition too, you have to get into recovery mode by holding the upper volume button while booting, until a red screen appears.
If you have any questions, or if this doesn't work for you – let me know in the comments.
Thanks a lot to Adonis K. and globula_neagra for the sys_boot image and pointing me in the right direction.
Credits to DieterHolvoet from arctablet for putting it together.

THX! Much appreciated!
I own this device since today and you Sir made me very happy with your cwm and ability to root.
---------- Post added at 08:19 PM ---------- Previous post was at 07:42 PM ----------
I can confirm. Touchversion of CWM does not work.
File for non-touch CWM seems the same as touch btw. Could you please fix the link? Thx!

Yes, the touch version doesn't work.
The no-touch no-sys version works fine.
Here is the link for the no-touch/no-sys version (taken from the arctablet forums): http://globula.arctablet.com/ARCHOS_50_PLAT/CWM_A50_Plat_NoTouch_No_SYS.img.zip
globula must have misstyped it

IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way

Nash123 said:
IN CWM I cannot mount the sdcard. So I can't install any Zip-Files this way
Click to expand...
Click to collapse
I will fix these issues tomorrow.

Thank you!

GEN 11 ?

cajl said:
GEN 11 ?
Click to expand...
Click to collapse
Yes the Archos 50/53 Platinum and Archos 80 Xenon are Generation 11

NO !
it will be announced at IFA and I would see in Berlin

cajl said:
NO !
it will be announced at IFA and I would see in Berlin
Click to expand...
Click to collapse
I could try to convince you that they are Gen11, but you will have to trust me, the update page does not lie.

OK Archos 53 also ...

Anyone know if it's possible to partition the internal memory and internal sdcard together? I'm getting really low in internal space intended for app installations (180mb left, getting insufficient space errors)

Updated the third post with a new touch cwm, test version, i don`t have a platinum to test it.
Adonis, i don`t think is possible, tough you can use directory binder
I need some help with some file from the Archos 50 Platinum, I want to test if the phone function works on Archos 80 Xenon (it should in theory as this is not the first tablet made by Archos/Arnova that has a crippled phone function, my 7C G3 is capable if doing/receiving phone calls)

Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.

Adonis K. said:
Hmmm, i see. In my previous phone the developers found a way to repartition the device and play around with them so we could balance the phone and internal memory to our advantage. Could really use the /storage/sdcard1 as part of my /data and /system partitions.
http://i.imgur.com/MJkdLS9.png
Never heard of directory binding, is it like symlinking?
I will test touch version in a few mins, gotta watch something first.
edit: Nope, touch still not working. Same results as the previous one.
Click to expand...
Click to collapse
Then it will be no touch for the moment, tough is strange, on the Archos 80 Xenon is working fine.
Not having the phone is a big impediment for me to test things, and I have the Xenon only till 28`th, so this is my main platform for testing for now (identical spec with the 50 Plat, even the partition layout is identical , that`s why i believe that the phone function should work)
I will do another try with the touch version from the Xenon in the next days, maybe with will work with that one.
Yes, the directory binding is the same as simlinking

Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.

Nash123 said:
Does anyone know a fix for the incompatability with older routers? (Non Wifi-N support).
Sorry for the OT btw.
Edit: Second question. How do I revert back to stock firmware or stock mode [without root and CWM-recovery]? I used the non_sys-version.
Edit2: Tomorrow I will flash original firmware. Hopefully the alterations will be gone.
Click to expand...
Click to collapse
I think you will need the sys_boot recovery for that, or the stock one, the non_sys boot will not allow you to flash stock firmware.

2016 version (new fingerprint scanner, combined sim/sd)

Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile

Nice! Can you provide a dump from /system and /boot maybe?

BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?

Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask

BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted

Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.

flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?

I will do
Edit: OK, see if there will be an answer.

Thank you flo1k!

I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?

ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)

FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising

Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished

FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?

Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....

FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.

The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.

I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work

These are great news!
"Which ones do you need?"
Probably all of them

Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!

One of the BEST things you can do to Moto Z Play XDA Community (Takes a while! ;) )

EDIT: THE DEVDB PROJECT HAS RISEN UP!
https://forum.xda-developers.com/moto-z-play/development/project-real-unbrick-hard-bricked-moto-t3927107
This is so easy to do, and can be sooo helpful if one day You will end with hard-brick.
If you have any questions send me a private message. :good:
Hey! My name is Jacob and I must tell you that there is one common problem with Moto Z Play - OTA after downgroading results in hardbrick :silly:
I have also bricked my device some days ago, since then I have gathered interesting info, probably all old and not so old blankflash files (these were used in the past to unbrick, but don't work now) and two tools, that allowed me to make proper rawprogram0, patch0 and gpt_main0.bin needed for making files, that will allow everyone to unbrick.
But this can be worth nothing without your help. Problem with unbricking, is that last OTA, updated chip security making unable to flash older chip firmware rendering all flashfiles useless. To make new one, I must get some files that are not present in the internet, but are present in ALL working phones. All I need is full mmcblk0 backup. If you want to help follow these easy-peasy instructions:
INFO: Procedure bellow excludes EFS, MODEMST1, MODEMST2, FSG, BACKUP partitions from backup. These are your phone specific partitions, that contain sensitive information like IMEI, serial numbers etc, but this guide shows how to avoid them while backing up so you don't have to worry about it
Prerequisites:
1. Your phone might be rooted (but doesn't have to be), definitelly should be working and not messed up too much.
2. You must have at least 32 GB micro sd card
3. Any ROM, even custom will be good, but if you have stock, you get +1 point
Steps:
1. If you have TWRP recovery, boot into it and go to step 2.
If you don't have, here is official one https://eu.dl.twrp.me/addison/ - rename it to "twrp.img" and boot to it with
Code:
fastboot boot twrp.img
2. Backup your /data partition and keep it in safe place
3. Format sdcard in ext4 (it is more robust and failsafe) or FAT32/exFAT (if you are on windows).[/URL]
4. Wipe /data on your phone and insert sdcard. Under "Mount" tab in TWRP, check box next to SD-CARD.
5. Open TWRP terminal emulator (It is in advamced tab), type "su" and run these command:
If you trust me that I won't do bad things with your IMEI:
Code:
dd if=/dev/block/mmcblk0 of=/[U][I]"Ext sd location here"[/I][/U]/Loader.img bs=4096
This just makes full-backup of your all partitions from Qualcomm chip.
OR
If you don't trust me:
Code:
dd if=/dev/block/mmcblk0p[B][COLOR="Red"]X[/COLOR][/B] of=/[B][COLOR="DeepSkyBlue"]Y[/COLOR][/B]/mmcblk0p[COLOR="Red"]X[/COLOR] bs=4096
Where X is number of partition from 1 to 54 BUT NOT: 27 (modemst1), 28 (modemst2), 29 (fsg)
and Y is location of your SD-CARD. This will only back up partitions without IMEI, and other phone-specific info.
6 Generated files will be HUGE (~27GB). Copy them to pc and upload to cloud. Maby https://mega.nz/ - probably only they have enough space for that file for free.
7 Post link here or send it to me via Private Message.
8 That's all! If you managed to get here, all comunity is grateful, :highfive: you will be included as biggest contribuor to the new thread I will make in near future!

If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive

Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help

Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
The only other way I know would be a USB C OTG adapter and a USB stick...

Artim_96 said:
If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive
Click to expand...
Click to collapse
Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
Thank you very much guys! You don't even know how much did you motivated me to continue research when I got your responses. If you will have any problem, ask me for advice - I will try to help. :highfive:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
In case of Camarda: ...
Code:
adb -d shell su -c busybox dd if=/dev/block/mmcblk0 bs=4096 > D:\mmc.bin
... should do the job, where "D:\mmc.bin" can be any other valid location on your pc.
To make this work, you must have root and busybox installed.

Bobernator said:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
Click to expand...
Click to collapse
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell

Artim_96 said:
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell
Click to expand...
Click to collapse
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, becouse of smaller size and auto merging archives

Bobernator said:
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, because of smaller size and auto merging archives
Click to expand...
Click to collapse
Would it help you to get /data too? It's my old phone, screen is quite damaged so there is nothing worth looking for on it. Plus it was completely wiped twice by flashing the firmware with flashfile and unlocking the bootloader again since flashing the firmware locked it.

Data partition is absolutely not needed, but thanks for asking!

zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?

Artim_96 said:
zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?
Click to expand...
Click to collapse
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?

Bobernator said:
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?
Click to expand...
Click to collapse
I just sent you the file, tell me if everything is ok

Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!

Bobernator said:
Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!
Click to expand...
Click to collapse
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.

Welcome again! My exams have just ended (I hope they went well) I am temporally at my uncle's house so I don't have access to files and info I've gathered, but I will return to home at friday and even Easter will not stop me, becouse I have decided to start DevXDA project!
Stay with me guys

Fulcano said:
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.
Click to expand...
Click to collapse
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.

Bobernator said:
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.
Click to expand...
Click to collapse
Thanks for the reply! Sorry, i've been quite busy with exams as well.
It's been a while since the phone is bricked, and i think fastboot was the wrong word. When it is plugged in it appears as a qualcomm device and the LED blinks, but other than that the phone does absolutely nothing. I remember being unable to unbrick it because of needing a `programmer.pem` file specific to the version of android that was installed.
The phone had an unlocked bootloader, twrp and supersu. It got stuck during an OEM update from 7.1.1 (i think) to 8.0.0. It was stuck for over four hours, I turned it off by force and then it never turned on again .
With regards to the Moto Z2 files, that's fantastic to hear. If there's anything else I can do to help, please say so. I've configured email alerts now so i'll get notified when you reply .
Thanks for the effort!

Question We need unbrick tool for Redmagic 6/6 pro

Hello everyone, I want to ask if there is any developer who can help us please, we need unbrick tool for Redmagic 6 and 6 pro ASAP because the RM support team doesn't answer our complaints or emails. Please help us

M5tha said:
Hello everyone, I want to ask if there is any developer who can help us please, we need unbrick tool for Redmagic 6 and 6 pro ASAP because the RM support team doesn't answer our complaints or emails. Please help us
Click to expand...
Click to collapse
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....

Nocturne Seigneur said:
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....
Click to expand...
Click to collapse
It’s like Cinderella turning into a pumpkin after midnight. Our devices went from being phones to paperweights overnight.
Someone get our fairy god mothers up in here to bipity bopity this crap back into a working state

Out of curiosity may I ask how did it get to this state? Also I was able to get myself out thru a combination of reflashing boot.img (i was on 4.12), unlocking and relocking bootloader, and factory resetting via recovery mode. Not in that order and each multiple times. Somehow it worked out. Possibly worth a try if you are just waiting anyways with not too much to lose?
I found that a locked bootloader is good at telling whether you didn't quite flash an img right. It kept telling me that things are corrupt and whatnot, and all of a sudden it booted.

So I'm pretty close to getting a working TWRP for this device. I have extracted a basic TWRP.img file and merged it with the boot image for the Red Magic 6. When I flashed it, the logo shows up but nothing happens.
When I have time this weekend, I'll mess around with it some more.
That way we can unbrick it with twrp and not have to worry about waiting for an unbrick tool.

Nocturne Seigneur said:
i've been waiting for my paperweight turn into a phone for a month now, i don't think it will be here any soon....
Click to expand...
Click to collapse
I didn't unlock my bootloader, so I can't do anything to unbric this **** device

M5tha said:
I didn't unlock my bootloader, so I can't do anything to unbric this **** device
Click to expand...
Click to collapse
I’m in the same boat but Nubia is having me send my phone back to them to check out.

Guys the unbrick tool is already in this forum: https://forum.xda-developers.com/t/unbrick-tool-edl-flash-switch-from-cn-to-eu.4284797/
Note if you are rooted before going to EDL mode (9008) you should backup EFS via QFIL QCOM tool as a few people lost their IMEIs - I think it's in EFS Explorer the tool is free just Google it. Then do an EFS backup and save where you can't lose it. Here's a guide just ignore the Lenovo part, but you must go into diag mode Qualcomm 901D which is (try dial code *#7678# first it worked on the Red Magic 5 series, probably puts you in diag mode still) otherwise: adb shell; su; setprop sys.usb.config diag,adb before QFIL will see it: https://forums.easy-firmware.com/showthread.php/29143-How-To-Restore-Backup-QCN-EFS-on-Qualcomm-devices-(Giuide)
You can also back up the partition if you are rooted via adb shell. From memory, enable dev options (click build # under system until it shows up), patch your boot.img with Magisk Manager (should be in the ROM zip file you downloaded, copy to phone), flash back to the phone with fastboot (it will be in Downloads/magisk_patched_xyz.img "xyz" changes names just depends on Magisk) command is just after reboot to fastboot: fastboot flash boot magisk_patched_xyz.img; reboot and you should be rooted. Then from ADB do an ADB shell (it will ask to trust the device connected) adb shell (on PC), su (will ask for root access, grant it), $ dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img and copy that to your PC. That's your persist partition in case it gets messed up you should be able to: $dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist that assumes you copied persist.img back to your /sdcard/ in internal memory.
If I messed up a step feel free to correct it, this is all from memory no PC in front of me on vacation...

mslezak said:
Guys the unbrick tool is already in this forum: https://forum.xda-developers.com/t/unbrick-tool-edl-flash-switch-from-cn-to-eu.4284797/
Note if you are rooted before going to EDL mode (9008) you should backup EFS via QFIL QCOM tool as a few people lost their IMEIs - I think it's in EFS Explorer the tool is free just Google it. Then do an EFS backup and save where you can't lose it. Here's a guide just ignore the Lenovo part, but you must go into diag mode Qualcomm 901D which is (try dial code *#7678# first it worked on the Red Magic 5 series, probably puts you in diag mode still) otherwise: adb shell; su; setprop sys.usb.config diag,adb before QFIL will see it: https://forums.easy-firmware.com/showthread.php/29143-How-To-Restore-Backup-QCN-EFS-on-Qualcomm-devices-(Giuide)
You can also back up the partition if you are rooted via adb shell. From memory, enable dev options (click build # under system until it shows up), patch your boot.img with Magisk Manager (should be in the ROM zip file you downloaded, copy to phone), flash back to the phone with fastboot (it will be in Downloads/magisk_patched_xyz.img "xyz" changes names just depends on Magisk) command is just after reboot to fastboot: fastboot flash boot magisk_patched_xyz.img; reboot and you should be rooted. Then from ADB do an ADB shell (it will ask to trust the device connected) adb shell (on PC), su (will ask for root access, grant it), $ dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img and copy that to your PC. That's your persist partition in case it gets messed up you should be able to: $dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist that assumes you copied persist.img back to your /sdcard/ in internal memory.
If I messed up a step feel free to correct it, this is all from memory no PC in front of me on vacation...
Click to expand...
Click to collapse
I locked the bootlooder the screen is black, the only way to connect to the device is on a PC "COM",
I tried this link but and the next steps but it doesn't work, I don't know what to do with the phone and still it doesn't work,
I think I need the firmware RED MAGIC 6 "NX669J_NON EU Common".
PLEASE HELP ME
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.

Good evening I found a guy who unlocked the phone for me at 150 dollars.
the phone quickly repaired without any problems so the problem is solved.

Marofyxx said:
I locked the bootlooder the screen is black, the only way to connect to the device is on a PC "COM",
I tried this link but and the next steps but it doesn't work, I don't know what to do with the phone and still it doesn't work,
I think I need the firmware RED MAGIC 6 "NX669J_NON EU Common".
PLEASE HELP ME
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
Click to expand...
Click to collapse
i tried running it and now the phone is on but no display . who can help me ?
my device is :
Model: NX669J-P
Red magic OS :V4.5
Build number : NX669J_CNCommon_V7.14
Adroid version :11
Hardware version : NX669J_V1AM
I will pay for the software for you if I have to . Hope your help!

Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar

manhdoan1601 said:
i tried running it and now the phone is on but no display . who can help me ?
my device is :
Model: NX669J-P
Red magic OS :V4.5
Build number : NX669J_CNCommon_V7.14
Adroid version :11
Hardware version : NX669J_V1AM
I will pay for the software for you if I have to . Hope your help!
Click to expand...
Click to collapse
Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar

guide

Marofyxx said:
Hello,
I can give you the email of the person who repaired my phone but it's expensive 150dollar
Click to expand...
Click to collapse
i can pay it 150 usd . give me email

Ok

hey guys..
can u pls share qcn or especially xqcn for NX669J..?