Develop Bugs

[GUIDE][All-In-One]LG Optimus Me P350

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.

Root Telstra T-Hub 2 (Technicolor)

Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????

Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.

wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
BUMP

I have this Tablet as-well and having the same problem.
any ideas on the best way to root this thing?
wocko1 do you have any more details on how to got that far?
Thanks guys.
Rabs_1976 said:
Wanting to root my new Telstra T-Hub 2, made by Technicolor.
There appears to be no USB drivers available (nothing via Google)
There also appears to be no way to get into the Download Mode for connection to Odin. (again nothing on Google)
So these two points have left me a bit lost.
It is running Android (GB) 2.3.7
Any one have any ideas????
Click to expand...
Click to collapse

was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it

Madaz2 said:
was it released in any other countries as another device?
even if we got root on it what can we do for a custom ROM if noone can dev for it
Click to expand...
Click to collapse
We as owners/users of T-Hub 2 devices require sensible answers to important questions.
We need usb drivers for the T-Hub 2, either from Telstra or from Technicolor the manufacturer of the device so that we can attain " ROOT ACCESS" via a usb cable connection to a computer.
Unless we can get "ROOT ACCESS" we cannot move applications to an external SD card (32 GB in my case) or use Titanium Backup or certain Antivirus programs that require "ROOT ACCESS".
Please accept the undeniable fact that 1 Gigabyte of storage on the internal SD card is totally insufficient and pathetic, almost as pathetic as the fact that we are still stuck with "Gingerbread" which puts us three versions behind on Android which is now up to "JellyBean" v2.
The fact is, I believe the Android operating system running on the T-Hub 2 is, like all other versions of Android, based on the Linux kernel which is software using the GNU General Public License, which allows people to see, copy, use, and modify for their own needs.
If indeed I am correct in my assumption then Telstra/Technicolor could be in breach of a world standard which would mean that the proprietary blocks and gates that they have built to prevent access to the kernel on the T-Hub 2 are illegal.

Download Mode discovered...and more...
I thought this:
Hold "Volume-" and "Volume+" and "Power Button" boots into download mode. This is incorrect.
This gets you to recovery mode (which shows the Android robot fallen over).

Help!
wocko1 said:
I got ADB working on my T-Hub 2 by using the generic Google drivers, and edited the adb_usb.ini to just say 0x069B
So far I have problems rooting it.
Click to expand...
Click to collapse
Have been looking for the drivers everywhere, and so far none of them have worked. Even tried wireless adb to no avail. Also tried gingerbreak but still nothing. Sick of looking at the bloatware. Someone please help!

anyone had more success now that it has ICS 4.0.4

Yes, it can be rooted, but...
Hi,
Yes, much more progress. I've gained ADB root access using the restore method (i.e., restoring a backup which has been modified to install a file to a strange path, e.g,: ../../../system/bin/su), I recommend creating your own restore file rather than using one of the many out there and using it to install the necessary SU software to the appropriate locations.
If your device isn't detected by ADB, check that the device ID has been added to the ADB config file. The Thub2 ID is not recognised automatically. Also, when using fastboot remember to specify this ID or it won't find your THub.
The biggest issue with the THub2 is that Telstra have (in an oddly intelligent move) adopted SquashFS for the root file system; this is the FS used on things like linux liveCD's, and it's 100% RO (well, 99% RO . I have gotten around this in a number of ways. 1: I copied the SquashFS partition using DD to an Ext4 partition, then forced a dirty unmount of the SquashFS partiition chained to a mount of the new Ext4 partition to /system. RW access no problems, SU installs OK, but no persistence without forcing the dirty unmount each boot. 2: I copied the SquashFS partition to my ~ using DD, mounted and edited the partition, then re-flashed to the thub. worked much better, persistence across reboots, but dangerous and dodgy method that could risk many NANDs. 3: I cross-compiled a busybox containing UnionFS to Android.
Option 3 is by far the best option. UnionFS provides a transperent RW layer for SquashFS filesystems, writing the updates that couldn't be written to a RO system like squash to another partition (e.g., Ext4 on SD card). Mount a UnionFS system over /system to enable write access to the system. Maybe a better idea to mount it at /, but that raises other problems I couldn't be bothered dealing with.
I mentioned above that SquashFS is on 99% RO (in all my other experiences, it has been well and truly 100% RO, so this indicates something else a-going on that we should be able to use; I haven't looked into it yet.). For some reason, files installed to the Thub2 using the Restore method are persistent. Very useful, and should lead to a cleaner method.
So rooting so far:
Root with Restore method to install (1 & 2., SU bins, or 3., UnionFS Busybox)
Remount / as RW
-->Path 1 & 2
Dirty unmount /system && dirty unmount /system2 && mount /dev/block/etc.. NOTE: Once you dirty unmount /system, you will need to reference the location of the Ext4 partiition using the absolute (real) name of the device. You will also need to invoke busybox from a fully qualified path, eg. /data/local/tmp/busybox, as the internal /bin applications are no longer available (eg., mount).​
-->Path 3
No need to umount /system, just mount the UnionFS system over the top.​
Finally, for Paths 1 & 3...
Install Superuser application and be free!​
So to sum up; I have easily rooted the Thub2 to root over ADB using a number of methods, however the Restore method works 100% of the time. I have mounted an Ext4 system to /system in order to have RW, but this isn't persistent. I have re-flashed the SquashFS with modified content, and this works a treat, but is RO and dangerous to NAND. I have mounted a UnionFS system over the SquashFS system, and this seems to provide the best all round performance.
I also wrote a short and nasty .apk to mount the UFS system without terminal, so that's a go as well.
Have fun pulling it all apart; I don't read these message boards, so I probably won't se any questions. More than enough to get rooted though.

THub Drivers and ADB Access
THUB 2 DRIVER INSTALLATION AND ADB ACCESS
This method sets out how to install drivers for the THub 2 and access ADB (Android Debug Bridge).
Access to ADB is the usual way that you use to Root an Android device.
Please note that not all ADB versions work. If you download and try a root method, you may have to copy the ADB.exe and support files across so that the root method can at least have a chance of working.
INSTALLING GOOGLE UNIVERSAL ANDROID DRIVERS
1. Ensure that Debugging has been enabled – Settings  Developer options  USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar
3. Unzip the file and copy contents to a folder on the C: drive. I copied it to a folder I named THub
4. Plug the THub into your PC and it will try to find suitable drivers – some drivers may load and install but at least one will come up with “No driver found”
5. Open “Computer”
6. Click on “System properties”
7. Click on “Device Manager”
8. Under “Other devices” you will see T-Hub2 with an icon with a yellow exclamation mark.
9. Right-click the device and select "Update Driver"
10. Select "Browse my computer for driver software"
11. Select "Let me pick from a list of device drivers"
12. Click “Show All Devices”
13. Click “Have disk …”
14. Browse to where you put the extracted files
15. Select and open “Android_winusb.inf”
16. Select “Android Composite ADB Interface”
17. Click “Next” and then Click “Yes” (Ignore warning)
18. Wait until the software installs
19. You should now have Android Composite Interface” under the “Android Phone” listing
If you have problems, ensure Debugging is selected and try unplugging the THub and reconnecting it
ACCESSING ADB
1. Ensure that Debugging has been enabled – Settings  Developer options  USB debugging and make sure the box is checked
2. The following is for Windows 7, other versions will be similar, It also assumes that the file has been down loaded, unzipped and installed in a folder called THub on you C: drive
3. Connect the THub to your PC
4. Click in the “Start” icon, lower left icon on your PC Desktop
5. In the entry box type in “CMD” and push “Enter”
6. You will be at the “Command Prompt”
7. You need to navigate to the “THub” folder, the following are my entries, and yours should be similar.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Terry>cd .. and “Enter”
C:\Users>cd .. and “Enter”
C:\>
C:\>cd THub and “Enter”
C:\THub>
8. At the THub folder type in “ADB devices” and “Enter”
9. You should get an output similar to this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
01545CAB0B015004 device
C:\THub>
10. You now have ADB access
11. Try “adb shell” and “Enter” to enter ADB and then “ls” and “Enter” to get the THub Root folder listing
What next, I don’t know but at least we have ADB access?
I have been trying to copy system files to my SD card to have a look at them but have no success.
Does anyone know how?
Here is the site I uploaded the files to:
"You can fill in the missing bits"
xxx.mediafire.com/download/voku3wnuff5s2ef/THub.zip
NOTE: There is also a file called “UniversalAdbDriverSetup6.msi”.
I don’t know what it is for, but I installed it anyway. It MAY be necessary for the above method.

Firstly, I understand this is an old thread but quite a lot of us Australians have this THub 2 now because Telstra seem to basically be handing them out like shots at a party.
As far as I know this thing still has no root access. You can get into ADB with it without too much trouble.
But what I really want to know is how I can get root access with SuperSU so I can install something like AdAway to remove the seemingly ridiculous amount of advertisements that apps and etc. come with.
In addition to that, after installing just TWO small apps. It seems the device's internal memory is already full and it cannot install any more apps.. I need root access in order to run Apps2SD so I can move some apps to the SD card that I have purchased for it.
Does anyone, and I mean anyone have any ideas about how to root this thing? There has to be some Australian who has a rooted version with SuperSU running.
I tried 'towelroot' but the device just rebooted (meaning it failed) and then when I ran the .apk again it said that the device was unsupported.
It's one thing to be able to get access to the root partition (which is possible over ADB) but it's another to be able to run apps with root privileges.
For any information.
The specs are:
Manufacturer - Technicolor
Operating System - Ice Cream Sandwich 4.0.4
Processor - 1 GHz dual core
Screen - 7″ (1024 x 600 pixels)
Camera - 1.9 MP rear camera, 1.2 MP HD front camera
RAM - 1GB
Storage - 2 GB Internal with an expandable Micro SD card slot (1GB internal usable)
Battery - 6000 mAh (non-removable)
I know it's nothing amazing, but if I could root the device and change the DPI, remove advertisements and install a few hacks. I'd get so much more out of the device.
I picked it up in almost perfect condition second-hand off eBay for only $15. They're worth $360 AU brand-new.
If anyone has any information at all, please do post something. My apologies again for bumping a super old thread but otherwise I was going to just start my own.

Possible to restore system partition
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp

SwampCrack1210 said:
Hi Guys,
I done goofed.
I killed my T-Hub by flashing a corrupted system partition and now the device wont boot and only displays the Telstra logo at the boot loader. I do have a backup of my system partition however I cant work out how I would perform the restore. The boot loader will not allow an ADB connection so no luck there.
Im thinking JTAG may be my only option. I have experience with this on other devices but i cant find the JTAG terminals on this thing? I must have tapped about 60 different combinations of testpoints now and have only been able to get console out of the radio module which is obviously no good for talking to the kernel.
Any help would be greatly appreciated.
Cheers,
Swamp
Click to expand...
Click to collapse
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?

clearburn said:
I'm completely new to this. What ROM would i look for to install on the THUB if any? And if i could install it?
Click to expand...
Click to collapse
sorry but no one has developed a ROM for this device, there is no demand

Madaz2 said:
sorry but no one has developed a ROM for this device, there is no demand
Click to expand...
Click to collapse
Thanks. I thought there might have been a rom from the basic device that didn't have all of the Telstra stuff on it.
It is currently a brick

if you can root it then you could install Titanium backup and uninstall the bloatware off of it

Some moderate success
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.

I would be very interested in your progress as I have one of these but in default state it is only usable as a phone on the DECT base.....
Having some useful apps running off an SD card would help no end (like multimedia remote for my home theatre system)
Cheers,
Alex B
SwampCrack1210 said:
I have had some moderate advancements of late.
I can get temporary ADB root using the directory traversal exploit
.
While the above method gets you a root terminal session, as it screws with some settings the device is nearly unusable due to screen flicker and general lag. I guess the exploit breaks some settings. Does anyone know how to leave the exploit in place and restore the settings file to eliminate the flickering and lag?
I have been able to export the system partition, edit it (add su.bin and SuperUser.apk) then swap the system mount so the device uses my edited system partition as described by malleus. When I try to flash my partition the device reboots and is in a semi brick state (reboot loop, stuck on boot loader Telstra logo).
I was able to obtain the OTA update files by getting an old 2.3.7 device, rooting it then grabbing the OTA files using ADB once it had downloaded them. These OTA's can be flashed from an SD card (ext4 format) in 3e recovery. This was a good bit of progress as it means I can restore from a bricked state. If anyone needs them, the files I have are:
Product_4.0.4_3.38-FOTA
Product_4.0.4_3.48-FOTA
This is all new territory for me but i think I am getting close to achieving full, persistent root in 4.0.4.
Any help would be appreciated.
Click to expand...
Click to collapse

Has anyone made any progress on this?
I have two of these tablets that have sat unused since I got them from Telstra. I really just want to update it to at least 4.1, but there's no official release from Telstra for the T-Hub, and I don't think there will be. Are ports entirely unfeasible?
Do you think I could contact Technicolor? What should I say?
P.S. there is a recovery mode, because I've booted into it.
hxxp://imgur.com/O0uq4Uk

Collection of Guides and Tutorials for G9(Also, how to root and get custom rom)

Welcome
I wrote this post to help people get their Archos g9 tablet running custom roms. If you have any improvement ideas, please post them so I can make this better source of information.
List of content:
Post 1
What is recovery
What is SDE and how to install it
-Also SDE for 4.0.25
List of most commonly used roms
How to install custom roms
How to install offical rom
How to multiboot android 4.0 based roms
Installing 3G stick and Huawei modems support.
Post 2
Change symlinks/binds.
Installing ADB
Installing SuperCharger
Installing Chainfire3D
But why?
FAQ
Useful links
What is recovery​You can boot to recovery menu by holding volume- while booting your device. From recovery meny you can calibrate your touchscreen, wipe data and do this kind of stuff. Installing SDE creates new entry to recovery menu, called Special Developers Edition. There you can remove android kernel, flash new, export hdd and data. In recovery move up and down with volume + and -. Select by pressing power button
What is SDE and how to install it​SDE is shortened word from Special Developers Edition. After SDE is installed, your tablet is able to boot to official rom, recovery, and SDE rom. Most of the roms advice you to use "Remove android kernel" from SDE before you install kernel. When you remove your android kernel from there and install kernel from custom rom, your archos boots directly to custom rom. If you don't delete it, your device boots to official, but keeping volume - while booting gives you change to boot to SDE.
There are 3 guides how to install SDE. Official SDE watermarks your device for archos (there is no watermark on screen ), so they can detect you have installed SDE in some point. It stays even if you remove SDE. Official way is more safe. Also, it removes "only" software warranty. If your devices powerbutton, Usb-port or etc brokes, you can still send it to warranty. Link to official SDE install guide. Big thanks for Shano56.
Then there is unofficial, a bit more dangerous method. It doesn't watermark your device, but is more complicated. Guide tells that it's outdated, but it worked for me. I used official 4.0.4 version while installing. Link to the guide. Big thanks to Shano56.
4.0.25 Guide, by surdu_petru
surdu_petru said:
Hi !
I uninstalled SDE by mistake yesterday !
...so, you can enable (install) unofficially SDE following this path ( work 100% on firmware 4.0.25 ) :
On your tablet :
check on Settings-> Developer options -> USB debugging on !
connect USB cable ( PC to tablet )
On your PC :
> adb push 1 /data/local
> adb push 2 /data/local
> adb shell
$ chmod 0755 /data/local/*
$ ./data/local/1
$ exit
> adb reboot
> adb shell
$ ./data/local/2
$ exit
> adb reboot
> adb push zimage /data/local/tmp
> adb push initrd.cpio.lzma /data/local/tmp
> adb push abcbox /data/local/tmp
> adb shell chmod 755 /data/local/tmp/abcbox
> adb shell /data/local/tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
( now you have installed unofficially SDE ! )
Flash Root version or other Custom Rom :
> adb reboot
> adb shell rm /data/local.prop
> adb push archos.ext4(.update) /mnt/storage
Go to SDE -> ( check "Reboot" on power off menu , and after a while press & keep volume down until you see SDE menu !)
Go to Recovery System -> Developer Edition Menu -> Remove Android Kernel -> I Undestand -> OK -> Developer Edition Menu -> Flash Kernel & Initramfs -> copy here zImage and initramfs.cpio.lzo appropriate archos.ext4(.update) -> OK -> wait to boot !
Now you have Rot version installed !
Here you will find the necessary files : Enable_SDE.zip
Click to expand...
Click to collapse
List of most commonly used roms​These roms are most commonly used. Most of them are still being developed. I also included link to rooted official honeycomb, because some people have better touchscreen responsibility with it.
ParanoidAndroid 3
Cyanogenmod 10, 4.2 mockup
Cyanogenmod 10
AOKP ROM
[email protected]
Clean_Slim&Fast(Based on official 4.0.25!)
Ubuntu. This requires special kernel, which is compatible with official android 4.0.4Overclockable stock rom
Early CM9
Stock ICS rom with root & busybox
Stock honeycomb with root. (FYI, kernel requires renaming while installing)
How to install custom roms​Custom roms have different installing methods, but basic idea is same. You move image file with specified name to specified location.
When coming from stock rom or whengoing to stock rom:
CyanogenMod 10, AOKP, CyanogenMod 9
surdu_petru said:
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /mnt/storage ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
[email protected], Ubuntu, Root 4.0.7 Clean_Slim&Fast
surdu_petru said:
Install :
- copy archos.ext4.update(archos.ext4 in case of Clean_Slim&Fast) in /mnt/storage/ , you can use this command > adb push archos.ext4.update(remove .update if Clean_Slim&Fast) /mnt/storage/
- go to SDE -> Developer Edition Menu -> ( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- after everything was installed - please reboot your device !
Click to expand...
Click to collapse
Honeycomb
Install like Cyanogenmod and AOKP and others, but rename initramfs.cpio.gz to initramfs.cpio.lzo
How to install official rom​Download official 4.0.7 rom from here.
Now boot to recovery (hold volume- while booting) and choose update firmware.
Now there should be noew drive in your pc. Drop the downloaded firmware_archos_it4.aos to there and press ok in recovery. Keep usb plugged in while installing. It should take around 30 seconds to 2 minutes. Now choose ok again. your tablet should now reboot to stock rom.
4.0.24 Official is owrking on some devices, but because it won't work on all, i won't cover it here(yet)
How to multiboot android 4.0 based roms​Install modified initfram from this topic. Use the zimage from the rom you want to multiboot. AFAIK you can multiboot with following combos:
[email protected], Ubuntu (download newer kernel from later pages.), Root 4.0.7
and
AOKP, CyanogenMod 9.
You cant use [email protected] and AOKP because they do not use same kind of data. That means that after you have run first rom, the second will bootloop. That is also why it requires wiping data when changing from stock to aokp and vise versa.
Detailed:
Download dmenu-0.3a.zip, and extract initframfs to desktop. Then download [email protected] and stock 4.0.7 rooted. Extract Image files and zimage from either one of the roms. Now just instal like described in earlier section, while using initframfs from multiboot and kernel from other rom.
Installing 3G stick and Huawei modems support. ​
Trevd made a package to add 3G stick and extra Huawei modems work for AOKP and generally all ICS ROMs. This guy is awesome because he also made some Huawei modems work.
trevd said:
Hi surdu_petru and AOKP fans.
Great work as always, It's not a rom i'll ever use but It's the first time I've loaded an AOKP Rom, I like notification layout, I'll be having that away for my own personal rom Anyway I was more just passing through and noticed 3G was not working yet. As seen as though that seems to be my speciality and preoccupation/addiction for the last 9 months I thought I do something to remedy that situation for you.
Here's an hotfile link to download the update [ 3g-archos-aopk.7z ] this should contain everything you need to get the Archos 3G Dongle, just for ****s and giggles as a extra bonus i've also included the huawei support file as well :good:
Installation:
From a command prompt / bash terminal
Code:
7z x 3g-archos-aopk.7z
adb push 3g /
adb shell reboot_into sde
extracting the 3g-archos-aopk.7z will give youu a 3g directory in you current directory, we then push the contents of the 3g directory to the root direcotry on the device. This operation is recursive.
Have Fun!
What follows is a detailed explanation of what files and modifications are required to add 3G support.
Archos 3G Stick
The changes / additions to add this functionality breaks down like this ; The following required binary's were on the device already:
** /lib/modules/hso.ko is insmod'd by the device specific init file /etc/init/init..rc
Code:
/lib/modules/hso.ko[B]**[/B]
/usr/bin/usb_modeswitch
/system/lib/libtcl-ril.so
/system/bin/rild
/system/bin/pppd
/system/xbin/chat
/etc/ppp/init_pppd_datakey
/etc/ppp/ip-up-datakey
/etc/ppp/ip-down-datakey
/etc/ppp/peers/datakey
/etc/chatscripts/datakey_start
/etc/chatscripts/datakey_stop
/etc/usb_modeswitch/1bbb_f000
The following required services were already defined in the device specific init.rc's located in /etc/init/init..rc ,
*** switch_ms_3g defined by /etc/init/init.archos.rc
Code:
service service switch_ms_to_3g[B]***[/B]
service pppd_secrets
service pppd_datakey
service ril-daemon
So what's missing? you may ask as this pretty much is everything that is needed by the Archos 3G Stick.
Standard Archos Roms use the UsbKeyManager.apk system service to start the switch_ms_to_3g and ril-daemon service's. I replace that with my own ueventd handling native service and add an additional to configuration file keep everything clean
Code:
/system/bin/hotplugd
/init.dongle.rc
I've added the following line to the top of the /init.rc
Code:
import init.dongle.rc
All that is left to do now is enable mobile networks on the rom. I used apktool to decompile the /system/framework/framework-res.apk and change the following values
res/values/bools.xml
Code:
true
true
res/values/arrays.xml
Code:
wifi,1,1,1,-1,true
mobile,0,0,0,-1,true
mobile_mms,2,0,2,60000,true
mobile_supl,3,0,2,60000,true
mobile_hipri,5,0,3,60000,true
mobile_fota,10,0,2,60000,true
mobile_ims,11,0,2,60000,true
mobile_cbs,12,0,2,60000,true
wifi_p2p,13,1,0,-1,true
"1,1"
"0,1"
"7,1"
"9,1"
res/values/strings.xml
Code:
ppp1
Huawei Support
The extend this functionality further I added the following files
Code:
/etc/ppp/init_pppd_gprs
/etc/ppp/ip-up-gprs
/etc/ppp/ip-down-gprs
/etc/ppp/peers/gprs
/etc/chatscripts/gprs_start
/etc/chatscripts/gprs_stop
/etc/usb_modeswitch/ [ numerous configurations files ]
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
We also need to chmod 6755 /system/bin/pppd but that is handled/checked in the /init.dongle.rc so there is no need to do that manually
Click to expand...
Click to collapse

Change symlinks/binds​Trevd wrote guide to let people know how to change binds. That way you can move large folders, like Gameloft games and navigator files to ExternalSD, saving InternalSD space.
trevd said:
If you after freeing up space, it is still possible with a bit of hacking voodoo . There are 2 ways I know of in fact.
METHOD 1 - SDCARD SERVICE
you can point the /storage ( /mnt/storage in reality ) to any directory you like. I've currently got mine pointing to an multi partitioned external 32gb sdcard. :0 all you need to do is change the sdcard service in the /etc/init/init.A101S.rc,
Currently it mounts /data/media to /mnt/storage, if you have an external sdcard card handy, try this as a quick and dirty test
From a terminal emulator or adb shell run the following commands
Code:
stop sdcard ;
sdcard /mnt/sdcard 1000 1015 &
ls /storage
You will now see that the external sdcard can be access through /storage. to kill the test run
Code:
pkill -9 sdcard
start sdcard
Everything should be back to normal. As I mentioned to make a more permanent change edit the following line in the /etc/init/init.A101S.rc
Code:
service sdcard /system/bin/sdcard /data/media 1000 1015
METHOD 2 - MOUNT BIND
The other, perhaps more straight forward method uses the bind argument on the mount to command to "mount an already visible filesystem elsewhere" .
In the example I'll bind the external sdcard to a directory in the internal storage
use the terminal emulator or adb once again to execute the following commands
Code:
mkdir /storage/sdcard
mount --bind /mnt/sdcard /storage/sdcard
To make this more parmanent, I would probably create a wrapper shell script for the sdcard service to make sure it all gets started together, that's just my preference, As we say in trade ( or maybe it's a saying i've just made up :silly: ) ; "there's more than one way to mount a file system!"
In Summary: I would go with method 2 as this effectively achieves the desired effect off "symlinking" an external directory in the /storage
Cheers
Click to expand...
Click to collapse
Installing ADB​ADB comes from word android development bridge, and it allows you to debug, move files and get shell access to your tablet.
Archos said:
First make sure you are running the latest ARCHOS firmware. Connecting by this method will give you user shell privileges. Learn more to know how to use ADB on Windows, Mac or Linux operating system:
Go to the Android SDK page and download the latest SDK for your operating system.
For Windows users only: Install the Archos ADB USB Driver for Windows. The driver is available at the ARCHOS support ftp (ftp://support.archos.com). Instructions how to install the driver are available at USB Driver for Windows site on Android Developers.
Add Archos vendor ID (0x0e79) to adb_usb.ini in .android folder in your home directory:
Windows: echo 0x0e79 >> "%USERPROFILE%\.android\adb_usb.ini"
Macos: echo "0x0e79" >> ~/.android/adb_usb.ini
Linux: echo "0x0e79" >> ~/.android/adb_usb.ini
For Linux users only: You need to add a udev rule if ADB only works as root:
Create a file /etc/udev/rules.d/51-android.rules that contains the following lines:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
Make the rule known to udev with the following command:
udevadm control --reload-rules (or udevcontrol reload_rules on older systems)
Click to expand...
Click to collapse
Running adb from anywhere
steviewevie said:
We need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)
Click to expand...
Click to collapse
sources:Archos, steviewevie
Installing Supercharger​Supercharger is a multiscript which makes the tablet work much better. Its created by Zeppelinrox, and its official topic is here. We are using also script manager in this guide. That way we can make MinFrees and OOM apply.
In this guide we'll use Apex launcher which is moved to /system/app for our default launcher.
We are also using adb to configure and run Supercharger.
Because stock launcher is odexed and i am not writing how to deodex, we are not using it.
First make sure apex is your default launcher. This can be tested by pressing home button in homescreen.
If it show mini previews of your homescreens, apex is your default launcher.
Now lets begin:
go to here and download newest file. At
the time of writing, it is Update 9_RC11_test6. Move it to your adb folder.
Then open commandline. This can be opened with windowskey + R and writing cmd. Navigate
to adb folder using cd command. I have made adb to run from anywhere, so i just navigate to the downloaded file.
Now use command "adb push v6* /mnt/sdcard" then use command "adb shell". Now you should have
shell access to your tablet. Now do following
su
cd /mnt/sdcard
sh V6* /remember capital V)
Supercharger script should open now. After presentation, script should print after telling your busybox version
"com.anddoes.launcher is the home launcher!" Now continue install. Supercharger will tell you everything you need to know.
So just follow the instructions. After choosing kernel tweak, you get bunch of permission denieds.
We can't help them, so lets just continue.I recommend on using all the tweaks that you can,
but it is your choise do you want to use or not. After all the selections are selected and your in
driver panel, choose number 32. It'll reboot your tablet and wipe dalvik. When the tablet has booted, lets run supercharger script again.
So write these again:
su
cd /mnt/sdcard
sh V6_Super*
After getting to drivers panel, you notice that minfrees are not in effect, and neither is OOM Grouping Fix BUT if they are, you can ignore this step..
Install script manager from market and open it. Give it root permissions and navigate to /system/etc/init.d
press SS99SuperCharger to open its settings. Now press the Su button and then Boot button.
Now press save, and then click it's name which appers to right. Then press back button and reboot.
Now Minfrees should work, and OOM too.
Now you can run 22 if you want to try it. Supercharger is now fully working.
Installing Chainfire3D​
Chainfire said:
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Click to expand...
Click to collapse
It is very useful for running gameloft games and other games too. I recommend buying it. There are some plugin for it, but i'm not going to tell you about it now.Play store link.
After downloading it, open it and choose "Chainfire3D Driver" and from there "install". Then confirm it and tablet should reboot. Now reopen it and choose "Default opengl setting". From there you can tweak 3D performance if some games lag. Also, if you install plugin, there you can apply them. I personally use "reduce texture quality".
But why?​
This section is to point few reason why to follow these guides. Lets begin:
SDE
Well, you should install this if you want to customize your tablet. If your happy with your tablet running stock, you don't need this, or any other guides.
Custom roms/kernels
Custom roms allow you to use root, they make your tablet faster and add extra functionality. This "functionality" includes: Overclock, run init.d scripts, enable both cores with all governors, root and themes. The benefits are not limited to these, but I could name this quickly. If you wan't to try something which is close to stock, but still has root and some custom functionalities, i would recommend deodexed 4.0.7, or [email protected]
Install official roms
These roms do not require SDE, but will not include root or anything fun . Updating your official rom has many benefits. They include fixes and boost your tablets performance.
Multiboot
Multibooting allows you to have 2 or more roms, which you can choose which to boot on startup. I would recommend this if you want to test functions with root, but still have "backup plan" if testing rom renders unbootable.
3G support
Basicly this allowes some extra huawei 3G sticks to work. There is no list of working stick, you just have to try and hope.
Change symlinks/binds
These allow you to "move" eg. gameloft games to external sd, and allow you to acces your externalsd via internalsd folder.. That way your gamedata does not eat the valuable internalsd space.
ADB
You need this to transfer rom to your tablet. It is also required when you sent logcat reports to help remove bugs.
SuperCharger
This makes your tablet work more fluid. I personally install supercharger to all my android devices. It removes need for task killer, and makes the device work better. Everyone has different results, and it costs only time to install, so i would recommend installing it.
Chainfire3D
This tool allows you to play games made for other GPUs and it can tweak application graphics. You can make the game look worse, but run better or adjust the grphics for a bit higher, so the game looks nicer.
FAQ[/CENTER]
These questions and answers are collected from various sources.
surdu_petru said:
How to activate second core for all govenors in surdu_petrus roms?
To activate the second core, you need the following steps :
- copy /system/S1tweak in /system/etc/init.d/ or ( > adb shell ; # cp /system/S1tweak /system/etc/init.d ; # exit )
- open No-frills CPU Control :
- choose the desired Governor ( but not hotplug ) !
- choose the desired frequency , but not overclocked ! ( when the device will boot - will open with the selected frequency , so please choose max. frequency = your max. stock frequency )
- check "Apply on boot"
- check "Applay"
- check allow if superuser asked permission
- reboot your device !
- Now , both core will be used in any selected Governor ( other than hotplug ! ).
Click to expand...
Click to collapse
What modems does Trevds mod support?
trevd said:
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
Click to expand...
Click to collapse
Shano56 said:
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
Click to expand...
Click to collapse
[/quote]
Useful links​Some link i consider useful are here:
G9 101 16GB 1.5GHz Teardown! (Lots of Images)
XBMC for android
Want faster GPS? Follow this guide

3th just i remember something to add. Comment and give me some feedback. It helps me to make this topic useful for beginners, and for those who seek info.

I meant to edit first post... well, this works as 4th reserved then.

Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:

trevd said:
Hi there!
You have been busy! Thanks for kind words, Just an heads up really, you might want to update your post as I deleted the usb-modem-binary-redist github repo yesterday as it was a bit too clever for it's own good and I think a bit of abuse/misuse of the concept branching! Just because you can, doesn't always mean you should LOL, with that in mind I'd probably advise against linking to my github repos as they don't stay static for very long. I generally leave the hotfile links up "forever" so link away with them.
The Information and files included in the new AOKP post about 3G Dongles should be good across all ICS roms. Finally allow me to throw out this mini guide I wrote a while back which explains an "app-free" method of freeing up space, I noticed there been a bit of discussion about it, Using an app just seem like overkill, but that's just me I suppose.
Anyway good work. :good:
Click to expand...
Click to collapse
Thanks for the feedback.
I removed the part which had github link, and modified the AOKP section to tell it works with all ICS ROMs.
I'll included your mini guide. I might even have some use for it myself...
Sent from my GT-I9100 using xda app-developers app

help me for multi boot ubuntu ics bleuv03
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.

muti642 said:
hello I want to know is it possible to bleuv03 ics and multi boot with ubuntu and it is possible that what zImage and iniframts I should use.
desoler for my english I'm french and I go through a translator thank you.
Click to expand...
Click to collapse
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app

julle131 said:
Download zimage, initfram and Ubuntu image from
http://forum.xda-developers.com/showthread.php?p=26000199
There is a high chance that touchscreen will not work if you have 101 G9 model in Ubuntu. You can still use USB OTG devices like mouse normally.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?

muti642 said:
thank you for answered. j've already managed to install ubuntu and I had no problem touch by cons I Can not get a dual boot ubuntu and bleuv03 ics. I shall therefore understands the multi boot flash I then I put two images but in the memory of the tablet and then I flash the kernel you gave me quote above and I should be able to boot on 2 rom and bleuv03 ubuntu?
Click to expand...
Click to collapse
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit

THX
julle131 said:
Download the this kernel https://docs.google.com/file/d/0BxgjsI4pMALheHZoVUdIYnVTN28/edit
It can dualboot [email protected] v03. If the ubuntu does not boot after flashing it, download this ubuntu image:
https://docs.google.com/file/d/0BxgjsI4pMALhVl9kek9SSFpKb2M/edit
Click to expand...
Click to collapse
Thank you thanks you it works well, I do not use the right kernel or the good image of ubuntu. ps: the touchscreen does not work but using the OTG is perfect.
thank you again julie :good:

sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!

solrakk6 said:
sorry for ignorance but for root i need to have adb sdk for do this steps??
"- copy archos.ext4.update to /mnt/storage/ , you can use this command > adb push archos.ext4.update /mnt/storage/
- go to SDE -> Developer Edition Menu ->( Remove Android Kernel if available ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to reboot .....
- the first boot may be longer ! "
If my archos is untoot how i use this comand? with adb sdk ?!
Click to expand...
Click to collapse
Yes, you must use adb. I assume your "untoot" means unrooted. You use cd command to navigate to your adb folder and from there to platform-tools. Also drop archos.ext4.update to there. Then use the adb command to move the file. Moving file to that location does not require root.
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.

hondacity said:
Hi Surdu,
I tried to update after SDE install and then accidentally dont know what happened have lost android on my tablet G9 101 HD. I cant see my hd on pc and is not booting but only can see the rom image which appears on boot without animation. How can I transfer the update archos.ext4 into Internal Storage without seeing the drive on PC win 7. I have made mistake in steps may be.
Please help.
Click to expand...
Click to collapse
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
julle131 said:
Go to the recovery menu, choose update firmware. When it prompts you to connect tablet to pc, cobbect it, but to different usb port than last time. That should cause the pc to reinstall usb drivers for the tablet.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.

hondacity said:
Thanks, for so fast reply Dear...
I did the same as you advised and a drive with name ending with "REC" with a capacity of 299 MB appeared. I tried to copy the Surdu's Deoedex update but it has more weight in MBS about 390. So it could not. I tried original Archos ROM with weight of 186 MB and it copied. Started update but returned with an error "Update failed: (221)".....
Please advise.
Note: I also tried in SDE menu to export data drive and got a drive 1.48 GB which I formated from win 7 and succeded in copying Stock and Surdu's ROMs one by one but always failed to get android and it always say failed update. Still get unanimated Archos logo on startup with no further bootup.
Click to expand...
Click to collapse
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
http://update.archos.com/9/gen9/gen9_4.0.26/firmware_archos_it4.aos
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
julle131 said:
Okay... So you have sde installed? Good. First, let's get the official firmware working. Download the latest official ROM from archos:
Drop this to the 300mb partition called REC. Then press power and let it install.
Now follow the install guide o. The ROM you want to install
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,

hondacity said:
Thanks Julle..But Now I understand that official ROM is not installing because of unofficial kernel flash I have already installed and had flushed original one. I think if I get original kernel then I can arrive to original Android ICS which you have mentioned. Please advise if you have any address of original kernel for "firmware_archos_it4.aos".
THANKS and Best Regards...
Further to my above thread...I found the stock kernel and flashed it but still after installing kernel and then original firmware, its giving same error of update failed (221).
Please advise if any remedy you prefer.
Regards...
Hi Julle,
Sorry too many threads from me but very much annoyed but sure thanks Dear for your kind help.
On export of HDD from "Repair system" menu...>>>> A drive appeared in PC but not opening as it says " Insert disk into drive". I think it is the problem which is preventing from installing the AOS file to run Android.
Please advise.
Regards,
Click to expand...
Click to collapse
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app

Archos G9 101 HD
julle131 said:
To install the update I linked, you shouldn't need any kernel changes. Removing kernel from SDE removes the official kernel, but that does not prevent installing official update. Also installing custom kernel will not prevent installing official rom.
I just do not understand why you get the 221 error as most of the people get it when that have incorrect file there or already have newer stock ROM installed. It is possible that your windows format broke it, because windows formats it to wrong format. You should never format any other than sdcards in windows. You could try the format system in recovery and choosing reformat device. After that install the official update I linked.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks again Dear,
I applied same as you say but ending on same 221 error. Any thoughts please.
Best regards.:crying:

Rooting Every Spreadtrum SC6820/SC8810 phones ! (1.5)

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

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

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

Are the sc8810 and sp8810 the same processors?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Custom Firmwares
Reserved

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

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

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

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

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

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

Thank you!

GEN 11 ?

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

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

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

OK Archos 53 also ...

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

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

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

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

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

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