Related
So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit
great guide good job
Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...
Updated adding unyaffsmbn tool... Thanks antdking!
Added Volume tweak for speaker to sound harder.
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:
Guys We have got Official Support From XDA Please Move This Thread To Our Device Section
Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183
Great Guide Man! Thanks a lot.
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!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse
There is a lot of discussion about the m8s here: http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
That thread involves different ROMs, returning to a locked bootloader and lots of other stuff. I found it hard to search through it and obtain the information I needed to root my device. Because of that I thought I would make this post. I hope it is of some use to people. Thanks to posters who helped me out on previous threads.
To root your device
You will need fastboot installed on your computer. On a linux machine this will probably be easiest by installing android-tools. On a windows machine you can install htc-fastboot linked to from the first post here: http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
- unlock your bootloader following instructions on htc-dev.com [you will have to register for an account]
- download twrp-recovery-2.8.6.0-m8s-qlul.img [linked to from this post http://forum.xda-developers.com/htc...c-one-m8s-t3114245/post62216780#post62216780]
- download the latest SuperSU beta [http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133]
- obtain a flashable version of busybox from here: http://forum.xda-developers.com/showthread.php?t=1929852 [I chose the Stericsson one]
- copy both SuperSU and busybox .zip folders to your phone
- From the folder on you have download twrp to on your computer execute the following command [on linux machine]
Code:
sudo fastboot boot twrp-recovery-2.8.6.0-m8s-qlul.img
- once in TWRP install SuperSU and then busybox
And that's it. You now have a rooted Stock rom .
Thank you wageslave. I also found the thread somewhat confusing and appreciate your summary here. I was wondering if you could answer me this: Since you "just" root and continue to use your stock rom, will your stuff still be on the phone after rooting (independently of your answer here, I'll do a backup).
2)
Thank you wageslave, this should be stickied.
Not to hijack, but I have a related question I've tried asking a few times but has gone unanswered. Given the limited internal storage on the M8S (16GB, but let's face it, it's actually 9GB), I've been trying to use Link2SD to link apps onto a 64GB MicroSD card.
After a successful root, I seem to be hitting a wall. Link2SD fails to mount the second partition (ext4) at boot, and even when a quick reboot fixes that problem, it fails again when I try to install apps to the external sd.
I presume this is mostly to dow ith not being able to S-Off, would this be correct?
If so, are there any other ways to get around this? I see someone mentioning on another thread that you need to disable System Write Protection, but I can't find a guide to doing this relating to the M8S.
I haven't yet installed BusyBox, I will this evening.
Thanks for any help and advice!
I was also pretty confused..
So you are saying that with your method I don't have to think about that RUU thing?
I can just use the twrp and flash it using cmd?
Hi, I'd love to use twrp on my M8s, however, the twrp link doesn't work for me (the ruu.lalleman site).
Is there anyone kind enough to make the img downloadable through something like Google drive or Dropbox? That'd be so cool, I've been searching for days to find a working custom recovery.
[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer
jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:
Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.
Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:
Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks
Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.
jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)
Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.
Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original
I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?
Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.
Congratulations @jen.magnolis
Well done