Related
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.
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
ZB2016 said:
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
Click to expand...
Click to collapse
Restoring the backup is the only solution it seems.
Yes ... hmmm ... backup ... that was what I intended to do that morning when the BAMMMM happened. I really had a bad start with the 7X ...
So in case someone has a backup of a clean or nearly clean system partition, please send me a PN. Tnx in advance!
Normal make a Backup in Twrp before modify the System Partition.
Make not an Official Ota Update with Rooted and Twrp installed Rom
Its not the phones mistake that you mess up and wakeup and take the phone for a spin in half sleep
and bamm, i really dont know what that meant. i would say go to the honor care center and get it to them to work.
the procedure which i know of is tough and things like bamm happening might worsen things like TWRP not starting at all.
i have seen people bricking their phones but its never the phones fault.
i would never recommend doing a "BAMM" thing doing and flashing all the stuff randomly cz i dont think magisk is supported fully yet to our phone and you flashed it without asking anyone.
the other russian forums are flashing chinese stock firmware which is the only original firmware available, but the task to change the settings to work for other variant is a huge stock which i gave link to a few people but for you i wont recommend that cz obviously your situation is totally different so go to the honor center and explain them and they would help you.
good luck! next time verify and be careful before flashing anything at random cause its not the phones fault.
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
ZB2016 said:
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
Click to expand...
Click to collapse
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
sid21 said:
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
Click to expand...
Click to collapse
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
ZB2016 said:
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
Click to expand...
Click to collapse
I am in contact with the user who posted the article and tested it himself and requested a proper one in english language but he is busy so it hasnt proceeded.. But soon he ll be free to write one up for me so i will post it on XDA..
I'm in a very similar boat. The Magisk v15 update bricked my L24. I had another one available and have made back ups through twrp to restore on the bricked one. It actually boots, but all I get is a black screen with the menu, home, and back buttons now. Holding power gives me the options to restart and power off. Hope they release the stock rom soon, or custom roms be available soon.
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Sudeep Duhoon said:
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Click to expand...
Click to collapse
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Back to life ... at least about 80%. Rooting leads to corrupt system partition (unable to boot afterwards) and bootloader can only be reached while a USB cable is connected (unusual behaviour). Nevertheless ... got it running. SID ... you are my hero of the day. Will PM you regarding comments for your thread.
ZB2016 said:
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
Click to expand...
Click to collapse
i think i have to write a guide now. this was the first but more can come soon enough. may be today i'll write a guide to backup your phone (all 48 partitions) and then root so you always have all the necessary files to restore it back to life.
sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Plz give link of custom rom for honor 7x
dhananjay 007 said:
Plz give link of custom rom for honor 7x
Click to expand...
Click to collapse
Who made custom rom for the phone?
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I have honor 7x.
dhananjay 007 said:
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
I have honor 7x.
Click to expand...
Click to collapse
So why are you even asking me for a custom rom?
If you know no one has made yet
UPDATE ... got it back to life, at least partly. The only thing is, that constantly the android adaptions of Huawei is making it unnecessary complex or is stopping progress at all. This is the log of my actual tasks. Key to progress was the unlocking of the system fs, which has some inconsistencies in the file system. In general, it gives me a 7X, that boots and I can install apps via HiSuite. Nevertheless I have no idea how to deal with Gapps. If I install opengapps, I will not be able to register an account - just hangs for a long period and then comes back (are there any logs written on the device to analyze a bit deeper?). Gapps without an account maks no sense. So I tried it without opengapps but with installing play services via HiSuite, granting rights, rebooting twice, installing Playstore, granting rights, rebooting twice, but starting Playstore after this procedure just tells me, that gms has to be installed (which in fact is already).
Any hint?
- prep like described by SID21 including HiSuite-Installation
- optional: download Nova Launcher, Firefox and Total Commander from "apkmirror.com"
- boot into TWRP
- mount system r/w
- format data
- wipe all partitions besides external SD
- mount vendor
- install image VENDOR.IMG
- reboot to bootloader- USB-connect to PC
- kill HiSuite in case it comes up
- Start MultiTools
- Click on "Unbrick" in upper list
- enter Path to prepared folder in grey field
- Validate: at least 4 checked boxes
- Click on Box labeled "Unbrick"
- Validate messages: "Completed", "All images are flashed successfully"
- Click "Recovery" in upper list
- in frame labeled "Flash custom Recovery/eRecovery":
- Click Button labelde "Select image" and navigate to file twrp_Honor_7x.img and select
- Click button "Flash Recovery"
- in Popup window select "Restart from fastboot" and unplug the phone from USB- Stop Multitools
- Wait for first restart, phone comes up
- Adapt phone settings:
- Security & Privacy/Additional Settings:
- set "Unknown sources"
- set "Allow HiSuite to use HDB" - About phone:
- Click 7 times in a row on "Build number" to activate developer options - Developer options:
- Activate "USB debugging"
- optional: Activate "Allow ADB debugging in charge only mode" - WiFi:
- connect to your WiFi network- USB-connect phone
- Phone popup: set "Allow access to device data?" to "Yes, allow access"
- Phone popup: set "Allow connection in HDB mode?" to "Yes, allow access"
- Phone popup: set "Allow USB debugging?" to "Ok"
- PC HiSuite Popup to inform about installation of services to manage device
- optional: PC HiSuite Apps:
- Install a proper Launcher (e.g. Nova Launcher) and make it the default launcher
- Install a proper file manager (e.g. Total Commander)
- install a browser (e.g. firefox)
- Download opengapps from opengapps.org and save to sd card- USB-disconnect phone
- Restart phone into TWRP
- do not get access to system partition
- Mount: Validate: system is not mounted at all
- Advanced/Terminal:
- enter "ls -l /dev/block/platform/hi_mci.0/by-name/system"
- validate: the filesystem points to /dev/block/mmcblk0p44
- ONLY DO THE FOLLOWING IF YOU KNOW WHAT YOU ARE DOING!!!
- enter "resize2fs /dev/block/mmcblk0p44"
- Validate Message: The Filesystem is now 1200128 blocks long.
- enter "e2fsck /dev/block/mmcblk0p44"
- Validate message: system clean, ... - Mount:
- check "system"
- uncheck "Mount system partition read-only" and swype in next screen to get access to system
- check "system" - Install:
- Select storage: Micro SDCard
- install SuperSU (I've chosen 2.82)
- Wipe Cache/Dalvik - Reboot:
- reboot to system
- do not install TWRP app- Reboot takes long time
- During boot animation another reboot occurs
- Boot animations gets finalized, phones comes up normally
I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?
sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance
Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom
Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??
Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.
I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know
hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks
Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.
ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..
Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.
WARNING: You can't downgrade anymore once you flashed U4/S4 March update !
https://samfrew.com/model/SM-A805F/
SM-A8050
SM-A805F
SM-A805N you can't unlock bootloader on this variant! (R1Q_KOR_SINGLE.pit)
You will need:
-Odin v3.14.1
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
-Galaxy A80 Latest USB Driver
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
You want to download latest firmware directly from server? (fast download)
Samfirm 0.4.1 or Frija 1.4.2
https://samfirmtool.com/samfirm-v0-4-1
https://github.com/wssyncmldm/frija/releases
Frija not working ? install both vcredist_x00 for your device !
(Check your windows settings to know which version to install).
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
-https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
-https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-A805F) and your CSC : (mine is LUX).
(All CSC's and models on Samfrew: https://samfrew.com/model/SM-A805F/).
-Download and extract SM-A805XX_1_00000000000000_xxxxxxxxxx_fac.zip
On your device:
If you want to unlock bootloader:
-Go to Settings then to About phone and find your build number.
-Tap on your build number 6 times until you see “You’re now a developer”.
-Go in Developer options > enable OEM unlocking.
-Connect the device to your PC.
-Power off your device with POWER and volume DOWN and directly hold volume UP and DOWN together!
-Device will boot in DOWNLOAD MODE.
-Long press volume UP to unlock the bootloader. This will wipe your data and automatically reboot your device!
If you dont want to unlock bootloader:.
-Download and extract Odin and open it as administrator.
Still in DOWNLOAD MODE:
-Click on BL and select BL_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on AP and select AP_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
-Click on CP and select CP_A805FXXXU4AXXX_CP14483800_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on START and wait for installation, when done you can unplug your device.
ROOTYour KNOX status will be tripped if you follow this tutorial...What's knox ? : https://www.google.com/search?q=samsung+knox+explained
-Download the latest stock firmware for your Samsung Galaxy A80 with Samfirm/Frija app (faster) or Samfrew/Sammobile website (way slower).
https://samfrew.com/model/SM-A805F/
-Extract the SM-A805XX_1_EXAMPLE_0000000000_fac.zip file with 7zip or any other unzipper.
-Copy the (AP_A805XXXXU1XXXX_CL00000000_QB00000000_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5) file and transfer it to your internal storage.
-Download and install Magisk Manager APK https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
-Open Magisk Manager and go to Install > Install > Select and Patch a file.
-Navigate through the storage and select the extracted AP file.
The firmware will be patched and will be found in Internal Storage/Download/magisk_patched.tar.
-Transfer the patched file to your PC.
-Turn OFF your device and boot into DOWNLOAD MODE.
-In Odin, click on AP and select the patched tar file, Uncheck “Auto Reboot” and click on Install.
The tool will flash Magisk V20 on your Samsung Galaxy A80.
To boot in recovery or boot the system with Magisk installed:
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
My storage was reduced from 128gb to 32gb after doing this. Is there a fix?
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
haanz85 said:
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
Click to expand...
Click to collapse
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Nazato said:
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Click to expand...
Click to collapse
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Could you please be more detailed in this steps?? I got this problems too. plz help.
hosheaxu said:
Could you please be more detailed in this steps?? I got this problems too. plz help.
Click to expand...
Click to collapse
read carefully every step bro. after flashing magisk patched then setup phone from beginning without setup google acount just skip, then check again by activating developer menu & usb debugging on. at the end reset from about menu..then phone's should reboot, after that install magisk manager then follow until finished process. & now after reboot u already got rooted beloved phone . congrats
haanz85 said:
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Click to expand...
Click to collapse
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Nazato said:
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Click to expand...
Click to collapse
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
haanz85 said:
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
Click to expand...
Click to collapse
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Nazato said:
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
yeah it's possible for sensitive pricing from first launching. in my country first launching price going around $705 then after few month until approaching new device release info to be released in February. on new years then the price going down until just left $549,50 then i decided to bought it :victory:
maybe many people's thinking like me, wait & see before grab this phone's :laugh:
Nazato said:
I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
tin2404 said:
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
Click to expand...
Click to collapse
but what about this device? are u still make exception from regular ongoing development.. until now there's no famous developer that saw it for builds known roms out there although this doll already succesfully rooted, but none of them build us twrp with fully support & maybe one or two working cust roms
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
BK said:
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
Click to expand...
Click to collapse
Is This only for france devices?
android 10
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
uae.coool said:
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
Click to expand...
Click to collapse
go right ahead I'm rooted on Android 10 right now just follow the instructions again
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
uae.coool said:
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
Click to expand...
Click to collapse
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Nazato said:
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Click to expand...
Click to collapse
ok thanks will try it now
other things is losing the memory showing 32gb after the root and when wipe no root ???
and one more things please how to install TWRP i tried many time but stack in the samaung logo ???
thanks again
Hi All!!
This thread will now contain pre rooted Odin files for F926B users to flash and update
Before you start, download "420rom_F926B_BVA9_Odin_EUY.zip" from HERE
THIS IS FOR F926B ONLY
The process requires knowledge of basic adb and YOU MUST HAVE ADB INSTALLED BEFORE TRYING THIS
This will no longer wipe data but it is advisable to backup first anyway - i wont be responsible for any data lost that could have been backed up
PROCESS to update from rooted a11 or a12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP mount menu disable MTP
5 - ONLY IF YOU DONT HAVE A MAGISK.ZIP ON INTERNAL STORAGE copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer)
6 - go to the TWRP flash menu and you should see the app-debug.zip, flash it to root your A12 device - this needs to be done everytime TWRP is flashed in Odin it seems
7 - reboot to system from TWRP power menu
You will boot rooted, updated and with intact data if all the steps above are followed correctly
------------------------------------------------------------------------------------------------------------------
PROCESS IF COMING FROM STOCK A12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC (please ensure dev settings are enabled and that you have unlocked bootloader and checked "Oem unlock" is faded out under dev settings)
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP wipe menu and format device (type yes and press enter) - then reboot TWRP
5 - when TWRP has rebooted, go to the mounts menu and disable MTP -> this will allow us to send app-debug.zip (magisk) to your sdcard
6 - copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working
7 - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer) - go to the TWRP flash menu and you should see this app-debug.zip, flash it to root your A12 device
8 - as stated previously, i have disabled encryption therefore we just need to boot STRAIGHT to SYSTEM from the TWRP POWER MENU
9 -When phone reboots, set up as normal and you should now see a magisk stub in the app drawer meaning you are rooted
PLEASE NOTE THAT THE MAGISK PATCHED AP FILE IS UPLOADING AND WILL BE AVAILABLE IN A FEW HOURS
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
ok my teammate has built a tested and working AP file to use in the guide above - this will be up very shortly
mine was fine however my internet connection is not lol
Ok guys - sorry for the muck about!! the patched AP file is now live in the first post - therefore you can go ahead and root!
Follow the steps carefully, please also read and make sure you have everything prepared before you start
Had a couple of peeps join my telegram chat asking about OEM option being missing.
Please note that this guide only covers the WWE F926B at the moment (US models have a locked bootloader afaik)
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
JazonX said:
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
Click to expand...
Click to collapse
At the moment there is sadly no camera til the bootloader is relocked. Hopefully a fix is found soon
exocetdj said:
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
Click to expand...
Click to collapse
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
Hi mate have you managed to access it yet? if not ill try sort links out
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
try this alternative link
If not ill ask my teammate to mirror to Mega
exocetdj said:
Hi mate have you managed to access it yet? if not ill try sort links out
Click to expand...
Click to collapse
Yeah, after an hour or so it let me in again, and didn’t fail this time. :O)
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
ultramag69 said:
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
Click to expand...
Click to collapse
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
exocetdj said:
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
Click to expand...
Click to collapse
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
ultramag69 said:
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
Click to expand...
Click to collapse
So from my understanding, Knox was actually designed for dual rom booting, as a way to keep the original firmware in tact and safe, but also be able to flash a custom rom for dual boot. But investors, carriers, and the like decided they weren't happy with that and saw that it could also be used to lock the device down to make everything more secure for their intents. After like 4 iterations where Samsung kept being pushed, it became what it is today.
I'm assuming they thought if they just impliment everything that a person would root for, that it would make people OK with it, but of course not the case. In the end, just like any other major corporation, they let money push them around
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
As soon as you flash any custom binary then your software is classed as custom and will not boot at all with a locked bootloader. It would soft brick requiring a stock odin flash to revive device most likely
dirtybudha said:
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
Click to expand...
Click to collapse
You can remove and/or disable bloat with adb commands for now. There is a thread about it somewhere in our forum
Samkey apparently now supports f926b but I'm getting unsupported firmware errors on AUG8 and AUHF. I really want to get rid of this three bloat