Database Users

[TELUS T959D FASCINATE][NOT ACTIVELY MAINTAINED-last updated 04.29.13]One Stop Shop

Hi and welcome Telus Fascinate T959D Users.
The purpose of this thread was to join a few T959D users together. When I flash a ROM I usually have at least 6 posts open on XDA - on different methods, kernels, etc. So I started collecting information and organizing it here. I have been updating based on feedback and adding more and different content especially when more users found us here.
Special thanks to everyone who has helped with this thread over the past few years - and special call outs to @Matt5606, @iwebsource, @finneginsfast, @moosehead11, @Dayfid, @karmatose, @bucknetbucky.
However, please note that we the contributors take no responsibilities for your phone or anything you do to it - this is simply a collection of helpful posts to get you started and continue having conversations - they are by no means offered as full proof guides, nor do they imply a warranty of any sort.
Now on the fun stuff, but first a simple FAQ.
Q. What is the T959D and what ROMs can I use on it?
The T959D is Telus' Galaxy S phone - known as a fascinate. What is confusing is this phone has almost nothing in common with the Verizon Fascinate - in fact flashing a fascinate ROM will brick your phone. Fortunately for us, our phone is VERY close to the International Version - the i9000 or galaxysmtd. Those are the ROMs we use on this phone.
Q. Is there a place where I can get files for my phone?
Yes - all through XDA you can use i9000 compatible ROMs, Kernels, modems. As well, we have a stock pile of files available to you - as you read the OPs you will find those and how to get them.
Q. Can I brick my phone?
Yes - but from my personal experience it is very hard to do this, and you can always get a USB jig that gets you to download mode (if you are soft bricked) - load one of the stock images and you are right as rain again.
A USB jig is a small piece of modded hardware that plugs into your USB port on your phone and forces it into download mode on start up - EVEN if it is SOFT BRICKED. A necessity for flashing. Lots of 'how tos' on how to create them out there if you have a spare cord, or just order one on EBay
http://www.ebay.com/sch/i.html?_nkw=usb+jig
For me, the place to use the most caution is using Odin - when placing files into the fields ensure they in the right place (measure twice, flash once ) as that is the biggest risk to flashing your phone. I think this is the greatest risk to hard bricking your phone which I am not sure you can recover from (I have only ever soft bricked my phone in which the USB jig saved my hide).
Q. I put on an ICS/JB ROM and now my IMEI is gone? What is that and how do I get it back?
Your IMEI is the unique identifier on your phone. The number is written down behind your battery - and that is what your phone should be displaying when you go to About Phone in Settings. Something happened with ICS/JB that it sometimes gets lost. To prevent that you need to back up your EFS folder.
1. You must be rooted.
2. You must have a file explorer that has root access (root explorer or ES File Explorer - although, if using ES ensure you have enabled root access and mounted /system in the preferences.
3. Find your /EFS/ folder at root (/).
4. Copy the EFS folder. Ensure you have ALL the files and ALL the subfolders (one will your IMEI). However, there can be hidden files in here, I would not worry so much about those, simply ensure you copy over the EFS folder itself - that should do it.
5. Move this to your removable SD card. Zip it, keep it on your PC, put in dropbox, ensure you have a copy for safe keeping.
And that is it - after flashing a new ROM, if you are missing your EFS or your IMEI number if wrong, just copy back the folder, reboot, and voila!
Q. GPS sucks.
Yes, yes it does. Do a search if you are adventurous there are hardware fixes. There's also faster fix in the play store and there are files here you can load as well - but its a known issue with the Galaxy S family of phones.
Q. What should I run on my phone?
Well, that is entirely up to you. The last official firmware you can get is 2.3.3. If you like very stable and do not need to have the latest, just a stable working phone with great battery - maybe try a good gingerbread ROM like Darky's or CM7.0 - Darky's will give you that Samsung feel (and still have the right firmware for the camera).
There are literally tons of options - go to the i9000 thread and see what the latest is. Most users here in this thread are on SlimICS, SlimBeam, CM10 or CM10.1. I have been running latest (nightlies) CM10.1 for some time combined with my favourite kernel Semaphore.
If you are going to flash a new JB ROM though, I suggest as your first flash stable CM 10.0 - this will be the base of your next ROM and many ROMs such as slim recommend you flash CM first just to set things up for yourself.
Q. So what now?
Read, read, and read. Go through this thread - go through threads of the ROMs you want to install - see what users are saying about it lately. And please - come to this thread and ask questions - we have a small but friendly and very helpful community - and remember if we help you, stay active on the thread so you can help someone else.
Cheers - and happy flashing

ICS/JB ROMS from Scratch (updated May 31 2013)
THANKS to @karmatose and @Dayfid for creating an ODIN flashable 2.3.3 - this means no more KIES (yes!) and creating a fresh stock ROM - here's the steps for this procedure... (Updated September 26, 2012)
Please note that the links below provided by Karma http://t959d.karmatose.org will work BUT you will need a username and password to download the files. Karma or myself can make the login and password available to you.
1. Download the KG2 package from here - http://t959d.karmatose.org/index.php/apps/files/download/Shared/stock_roms/T959TLKG2_Gingerbread.zip
2. Extract the archive to a folder on your PC using your archive app of choice. Mine is WinRAR.
3. Open Odin3 v1.7.exe (the one that is in the ZIP file)
4. Place the PDA, CSC and PHONE and PIT files in the proper boxes. Take absolute care to make sure you don't mix them up. Ensure that repartition is ticked 'on' in this case.
5. Put phone in download mode (vol down + power from off or download jig) and connect it to the PC
6. Click start and wait just under 3 minutes. The phone will restart and you should be back to stock 2.3.3
7. If your intention was to get to stock, you're done. If you want to go to ICS/JB and you *don't* have a backup of your EFS folder, go to step 8. If you do have a backup of your EFS folder, go to step 10.
8A. If you need to backup your EFS folder (HIGHLY RECOMMENDED), you need to root the phone. Flash the Speedmod kernel with ODIN (in the PDA field). The phone will reboot and get stuck in a boot loop at this point. Pull and replace the battery and place the phone in Recovery Mode by holding VOL+ and VOL- and pressing the power button. When the screen lights up, release the power button and continue to hold the volume rocker until you see CWM Recovery. Using the Vol+ and Vol- to navigate the menu, go to the Speedmod Advanced Options menu and press the power button to select it. Choose to root your phone.
8B. (Optional) Now that you have custom recovery, would not be a bad idea to make a nandroid backup of your phone. So go to backups, and create backup from the CWM Menu.
8C. Once that is complete, go back to the root menu and reboot the phone. Pull the battery out and put the phone back into download mode. Flash the stock 2.3.3 kernel back (also in the PDA field) in Odin. The phone should now be rooted. Let it boot. Hopefully you're greeted with a lock screen
9. Install ES Explorer from play (or APK), enable Root Settings in the settings menu then navigate up to root and copy your EFS folder to your EXTERNAL_SD card. Power down the phone, remove the SD card and copy this to your PC, Google Drive and some other backup source. Don't lose this folder.
10. Installing ICS / JB - Depending on what OS you want to go to, you're going to need to grab an appropriate kernel to do so. The best option seems to be Semaphore's i9000 kernels. If you're going to flash an ICS rom, grab the 1.3.0s .tar file. If you're going to JB, grab the 2.1.0s .tar file.
11. Download your ROM of choice. i9000 versions of SlimICS/SlimBean/CM9/CM10 work on the T959D. You will also need grab the .zip version of the Semaphore kernel (ICS / JB) you're using and a Modem of your choosing. KG3 works best for me, your mileage may vary. Place the ROM, .zip version of the Semaphore kernel you're using and the ES File Explorer APK on your internal SD card.
12. Open Odin again. Put the .tar'd Semaphore kernel file you just downloaded in the PDA field, ensure Re-Partition is UNCHECKED. Put your phone in download mode, connect it to the PC and click start. In a bit more than 10 seconds, your phone should reboot itself. Pull the battery out and replace it.
13. Put the phone in Recovery Mode by holding VOL+ and VOL- and pressing the power button. Release the power button as soon as the screen turns on but keep holding VOL+ and VOL- until CWM appears. Use the VOL+/- keys to navigate, PWR button to select. Go to "Install zip from sdcard", then "choose zip from internal sdcard".
14. Follow the directions to install your ROM. CM9/10 comes in one flashable .zip file whereas SlimICS/SlimBean comes in multiple files. Consult the documentation for your ROM to get specifics on how to install it. Note that if you are installing CM10, CM10.1, Slim 3.x + that the partition layout has changed. This means you will need to flash the ROM at least 3 times - once you will get an error 7, then flash again, and then again - after that you will have latest.
15. Once the ROM is done flashing, flash the Kernel .zip you placed on your External SD card the same way you flashed the ROMs. Then flash your modem .zip. Note that if you are using an 's' version of semaphore, and a non-patched ROM like CM (Slim is already patched) you will want to flash the big mem library patch which is attached below after flashing the kernel.
16. Go back to the CWM main menu and reboot the phone. You should boot into ICS / JB at this point with no issue. It might take a bit so be patient.
17. Verify your IMEI number. Hit the Menu button on your phone and select System Settings > About Phone > Status. Look at your IMEI. If there's a lot of 0's in it, you need to replace your EFS folder. Use Oi Explorer to access your External SD card and install the ES File Explorer APK. Enable *all* the Root options in the application settings and return to the file browser. Locate your EFS folder backup on your external SD (emmc), longpress on the folder and select "Copy To". Hit the navigate up button in the dialog box and select /. Press OK twice then reboot your phone. Your IMEI should be back to normal now.
18. Enjoy the fruits of your labour and customize the heck out of your new ICS / JB rom.
----
This is an alternate method from @bucknetbucky created this quick 'how to'. This will put you on stock GB and allow you to flash ICS from there.
Why start from GB? The bootloaders. When flashing from froyo you'll see lots of tips on pulling batteries and the first flash always not working - this won't happen from Gingerbread AND you'll get to keep the logo for the kernel for some added bling.
For those looking to flash from GB here is how to do it...
Get back to 2.3.3 stock
1 flash stock froyo via ODIN (tick repartition! - See the 'Essential Files' section above).
2 install samsung kies (should have this if you have this device- AND update it!)
3 update to GB using kies
Root your phone and back up EFS
Backing up EFS is vital. Essentially do this.
4. Download Super1click to root your phone and following the instructions (http://depositfiles.com/files/n0dcxce3t)
5 Install a file manager with root access and backup your efs folder by copying it to the internal sdcard then your computer (instructions in OP)
Note: this is one way to root your stock GB phone - you can also use the speedmod kernel (the version I use is older --- but works --- and is attached below) which has a root option under 'advanced' but has more steps. If you already have backed up your EFS though, you really do NOT need to do this step and skip to the steps below to flash your ICS ROM.
Finally INSTALL your ICS ROM
Now to flash the latest super duper ROMs from the super duper devs you will need to do the following...
1 copy glitch v14 kernel and the rom of your choice to your internal sdcard (The version linked below is the BEST version to accomplish this with)
http://www.box.com/s/tov06pvzkkqbmui6tcmi
2 flash via ODIN the speedmod kernel (gives you a custom recovery)
3 when it tries to boot pull the battery and then boot to recovery
4 flash the glitch kernel from recovery (again you are boot looping)
5 pull the battery and boot to glitch recovery and wipe data, clear cache and such then flash your ROM
6 copy your backed up EFS folder back to the phone to restore yout imei
Just some notes
Most ROMs will come with a compatible modem, however, if having modem issues - please see a few posts down on getting modems.
A complete list of ROMs for the I9000 by Android version can be found here (as well as kernels). Please note the update dates as that will indicate how much active support there is for the ROM.
http://forum.xda-developers.com/showthread.php?t=1837223

Gingerbread ROMs (Updated 03/11/2012)
In terms of loading GB ROMs I have had success with a few - namely Darky ROM (up to 10.4.2).
Credit to the original poster, but I always start with this how to on loading a ROM.
http://forum.xda-developers.com/showthread.php?t=923712
I do not execute every step, but essentially use it to get to stock along with the custom voodoo kernel which will give you root and custom recovery to load your custom ROM.

ROM and Kernel TWEAKS (Updated 08/28/2012)
GPS Tweak
This how to can you help you tweak GPS
http://forum.xda-developers.com/showthread.php?p=17081413
Note the multiple GPS.conf entries you can have for country (Canada) as well as region (North America).
Darky ROM tweak
When installing Darky ROM you will find the buttons for home and back no longer work. There is a simple fix for this as long as you have a root explorer (like ES File Explorer) and a text editor.
Open up /system/usr/keylayout/melfas_touchkey.kl in a text editor.
Make sure that your 'keys' look like this:
key 139 MENU
key 158 BACK
key 217 SEARCH
key 105 HOME
key 106 SEARCH
Keep VIRTUAL as part of the keys and you will still have vibration as well.
Alternatively (Thanks @finneginsfast !) you can flash 'keylayout.zip' attached below from recovery.

Flashables (Updated June 29 2013))
This is reserved for flashables such as modems and kernels.
Ultimate Kernel Cleaner
Before flashing a kernel, you should run a kernel cleaning script. Matt (THANKS @Matt5606) gave me this one - it handles cache cleaning, etc. See the attached file for ultimate kernel cleaning script.
Modems
Lots of modems out there, and get Perka's file store for a ready list (see recommended apps). My favourite for a long while has been the i9000UGKC1 modem - it has GB versions as well as ICS - just make sure you get the right one!
You can also download modems diredctly from Perkas Site (/Samsung/ICS_CM_Modems/850_Modems_CM) or the android app (available in Play). Ensure you get the right modems for your ROM or Android version.
For Gingerbread: /Samsung/I9000/Modem_850_Enabled
For ICS and JellyBean: /Samsung/ICS_CM_Modems/850_Modems_CM
@finneginsfast provided me with this graphical link to help give you an idea of what modems work where: http://soggycashew.weebly.com/modem-location-map.html
Gingerbread Kernels
Semaphore. Great kernel to run with DarkyROM.
http://forum.xda-developers.com/showthread.php?t=1112908
Glitch Kernel. Great kernel to run with CM7 or MIUI GB as its made for our model!!!
http://forum.xda-developers.com/showthread.php?t=1315400
ICS Kernels
I run Semaphore almost exclusively - definitely a favourite.
http://forum.xda-developers.com/showthread.php?t=1468795
Glitch has a specialized kernel for ICS as well, but I typically do not use it.
http://forum.xda-developers.com/showthread.php?t=1459475
JellyBean Kernels
Semaphore has a JellyBean kernel for 4.1.2 as well as 4.2.2 - its my go to kernel.
http://forum.xda-developers.com/showthread.php?t=1786220
Be sure to get the LMK app from XDA (search it) to ensure your launcher and keyboard do not die, and get Semaphore manager from the Play Store as well.

Recommend APPs (Updated 09/28/2012)
Launchers - ICS/JB
- APEX Launcher (free and paid, on Google Play)
- Nova Launcher (free and paid, on Google Play)
- Holo Launcher HD (free and paid, on Google Play)
Launchers - 2.x
- Launcher Pro (free and paid - better widgets with paid - Google Play)
- GO Launcher (totally free - lots of great supporting apps - Google Play)
- ADW (free and paid, Google Play)
- Holo Launcher (free and paid, Google Play)
Keyboards
- Swift Key X (trial and paid, Google Play)
- Swype (trial and paid, Google Play)
File Management & Files
- ES File Explorer (Free, has root explorer - Google Play)
- Perka's File Stash Free and Donate - excellent file resource for modems - Google Play)

Other Stuff
Essential Files
Before we get started wanted to make available some essential files. These are from my public dropbox folder, so I may switch it in time, but felt they should be here.
Need to get back to stock, then here is the Stock Telus Froyo 2.2. http://dl.dropbox.com/u/2069701/T959TLJL3.zip
Want stock with a CWM kernel on 2.2, then here is the VooDoo Kernel http://dl.dropbox.com/u/2069701/voodoo.advanced.v666.2-20110111-21.53.tar
Remember when flashing back to stock to tick the re-partition box, and place the files as follows:
- s1_odin_20100512.pit in "PIT"
- T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
- T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
- SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
Additionally, Karma has some core files he is posting as well (Thanks @karmatose !!!) and you can find those files at:
http://t959d.karmatose.org
To access the files, you will need a login. @karmatose or myself can make the login and password available to you.
Starting Fresh
Buck provided this a while back. This is recommended after many flashes and you want to start out fresh without lingering script files and other crap we're all guilty of installing/flashing
WARNING: This clears up EVERYTHING - even TB backuped programs - so if you want your TB backups, change your backup location to the REMOVABLE SD Card.
If you want to start fresh and i mean bare bones this is how i do it.
1. Remove the external sd card (the one you put in the phone)
2. Go into storage under settings and unmount then format the sd card (the partition the phone makes that you see if you do not have root)
3. Flash stock rom via odin and repartition ofcourse.
4. When you are done the phone will be like you just took it out of the box.
5. Backup the card you took out and format that. Leave it out.
6. Grab some beers and start flashing whatever you want (except the neighbors they dont like that)

Awesome thread, subscribed!
Sent from my GT-I9000 using XDA

Do I have to root my phone after installing GB . Or I can wait
And witch app is the better to backup the EFS folder

You need to root to back up your EFS... so for that. Then use root explorer or ES to copy that folder over to your SD and computer.
If you ES make sure turn on root explorer and mount /system.
Sent from my GT-I9000 using xda premium

In Odin witch slot (PDA,PHONE,CSC,BOOTLOADER) that i put the file speedmod-kernel-k16-11 . and the other one

Pda
Sent from my GT-I9000 using xda premium

there is no root option in the recovery mode after i put the speedmodkernel
nevermind lolll

I've been lookin at that procedure and you root through recovery with the speed mod kernel? I'm pretty sure you can root while on stock GB without all that hassle by just using SuperOneClick.
Sent from my GT-I9000 using XDA

Thx a lot JP for this thread!!!! . I m now part of the ICS community . Only one thing my IMEI number inst the same was its written under my battery . I copy back the EFS folder tho . Does it change something ???
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Matt5606 said:
I've been lookin at that procedure and you root through recovery with the speed mod kernel? I'm pretty sure you can root while on stock GB without all that hassle by just using SuperOneClick.
Sent from my GT-I9000 using XDA
Click to expand...
Click to collapse
I finally found it but thx for the feedback

If you remembered to copy your efs folder before the flash, just copy the original folder back into your phone replacing the old files and reboot. You should have your number back.
Sent from my GT-I9000 using XDA

Yeppers
Sent from my GT-I9000 using xda premium

So get yourself the semaphore kernel and nova launcher and you are all set
Sent from my GT-I9000 using xda premium

it did not change my IMEI numbers?? .what is that kernel do (Semaphore) and how to install it odin??

jpmccarthy said:
Darky ROM tweak
When installing Darky ROM you will find the buttons for home and back no longer work. There is a simple fix for this as long as you have a root explorer (like ES File Explorer) and a text editor.
Open up /system/usr/keylayout/melfas_touchkey.kl in a text editor.
Make sure that your 'keys' look like this:
key 139 MENU
key 158 BACK
key 217 SEARCH
key 105 HOME
key 106 SEARCH
Keep VIRTUAL as part of the keys and you will still have vibration as well.
Click to expand...
Click to collapse
Or you can install this zip from recovery, I think it's the same fix or at least it's what I've been using for a while.

[4.4.2] Root, Deodex, Bootloader Unlock/ Relock, Roms Kernels list, Themes, Mods

=Brief Introduction=​This thread will consist of information about Rooting, Flashtool, Bootloader, Kernel and Roms.
Xda have been helping me a lot, so I have decided to start with the most basic way to help since I have no idea on software development. Hope everything is correct, if anything is wrong please leave a comment below.
Also, I BELIEVE the ADMIN would most probably lock this thread up again. I initially did not intend to repost another thread, however @eclyptos had me convinced to repost this for the sake of newbies, since it will be locked but not deleted.
If you support me, give me more thanks, and maybe post some posts below to help to convince the admin not to lock this.
Thanks.
=Part 1 Rooting the latest KitKat 4.4.2 Firmware=
For Locked Bootloaders
Required files: ​
14.1.G.1.534 FTF file
Link: http://forum.xda-developers.com/show....php?t=2469191
(You many choose anyone you wish, for it will be overwritten after that)
Move file to C:\Flashtool\firmwares or wherever you installed flashtool to.
Root Many Android by Bin4ry
Link: http://uploaded.net/file/d2w6dl7r
Latest Flashtool
Link: http://www.flashtool.net/download.php
(Please make sure you use v9.15 and above)
Note: Please make sure fastboot and flashtool drivers are installed.
Help on installation on windows 8: http://forum.xda-developers.com/show....php?t=2095087
Dual Recovery
Link: http://forum.xda-developers.com/show....php?t=2647487
( Choose the latest version, read instructions on the site.)
14.2.A.0.290 Flashable files (C690X_14.2.A.0.290.flashable.zip and C690X_14.2.A.0.290_Stripped.ftf )
Link: http://forum.xda-developers.com/show....php?t=2572988
Note: Please transfer zip file to external sd card
Move ftf file to C:\Flashtool\firmwares or wherever you installed flashtool to.
14.3.A.0.681 Flashable files (C690X_14.3.A.0.681.flashable.zip and C690X_14.3.A.0.681_Stripped.ftf)
Link: http://forum.xda-developers.com/show....php?t=2687443
Note: Please transfer zip file to external sd card
Move ftf file to C:\Flashtool\firmwares or wherever you installed flashtool to.
Lets Get Started:​
1. Make sure phone is charged to at least 50%
2. Enable USB Debugging on your phone and switch to MSC mode
How to: Setting >About Phone>Tap Build Number a few times > Go back > Enter developer options > Enable usb debugging
Setting >Xperia Connectivity> USB Connectivity> MSC mode
3. Back up all apps or app data you wish to keep (contacts, applications, messages and photos that are in your internal storage)
How to: Use Helium from Play Store to backup app data or any other apps, make sure backup is saved to cloud or external sd card
5. Flash 14.G.1.534 Firmware.
How to: Power off device.
Hold Volume Down button
Plug in USB cable to computer and phone
Open flashtool and click lightning.
CHoose flashmode.
Choose 14.1.G.1.534
And FLASH!
6. Root it
How to: Turn device on
Enable USB Debugging
Open Root with Bin4ry file and run 'Run Me' file
Connect phone to pc
Select 0 (xperia root by .......)
7. Install dual recovery
How to: Open dual recovery file and open 'Install' file
Choose option 1
Grant Superuser permissions when requested
Phone will reboot.
8. Install 14.2.A.0.290 Flashable zip
HOw to: power off Phone
POwer on phone
When phone vibrates press volume down
It will then enter recovery mode
Wipe ( enter Wipe > Advanced WIpe > Tick Everything but external sd card and Otg)
After wipe, press back and slide factory reset
Install zip ( press install and find file)
It will take a few minutes
Do not press reboot system, press back key until first page and then click reboot key.
Select power off.
9. INstall Stripped FTF 14.2.A.0.290
How to: Hold Volume DOwn button
Plug in usb cable to computer and phone
Open flashtool and click lightning.
CHoose flashmode.
Choose 14.2.A.0.290 Generic NCB
And FLASH!
10. Power on
11. Install 14.3.A.0.681 Flashable zip
HOw to: power off Phone
POwer on phone
When phone vibrates press volume down
It will then enter recovery mode
Wipe ( enter Wipe > Advanced WIpe > Tick Everything but external sd card and Otg)
After wipe, press back and slide factory reset
Install zip ( press install and find file)
It will take a few minutes
Do not press reboot system, press back key until first page and then click reboot key.
Select power off.
12. . INstall Stripped FTF 14.3.A.0.681
How to: Hold Volume DOwn button
Plug in usb cable to computer and phone
Open flashtool and click lightning.
CHoose flashmode.
Choose 14.2.A.0.290 Generic NCB
13. Reboot and you are done!
Unlocked Boot loader​
Required Files:​
14.3.A.0.681
Link: http://forum.xda-developers.com/show....php?t=2469191
Move file to C:\Flashtool\firmwares or wherever you installed flashtool to.
DoomKernel v10 or up ( or any other 4.4 kernel)/XZDR Kernel
Link: http://forum.xda-developers.com/show....php?t=2448613
Unzip file.
SuperSu flashable zip
Link:http://forum.xda-developers.com/show....php?t=1538053
Transfer to external SD card
Latest Flashtool
Link: http://www.flashtool.net/download.php
(Please make sure you use v9.15 and above)
Note: Please make sure fastboot and flashtool drivers are installed.
Help on installation on windows 8: http://forum.xda-developers.com/show....php?t=2095087
Lets Get started:​
1. Make sure phone is charged to at least 50%
2. Enable USB Debugging on your phone and switch to MSC mode
How to: Setting >About Phone>Tap Build Number a few times > Go back > Enter developer options > Enable usb debugging
Setting >Xperia Connectivity> USB Connectivity> MSC mode
3. Back up all apps or app data you wish to keep (contacts, applications, messages and photos that are in your internal storage)
How to: Use Helium from Play Store to backup app data or any other apps, make sure backup is saved to cloud or external sd card
4. Flash 14.3.A.0.681 Firmware.
How to: Power off device.
Hold Volume Down button
Plug in USB cable to computer and phone
Open flashtool and click lightning.
Choose 14.3.A.0.681
And FLASH!
5. Power on. Test if everything is working well, camera and others.
6. Fastboot DooMKernel
How to: Power off device.
Hold Volume Up button
Plug in USB cable to computer and phone
Open flashtool and click lightning.
Choose Fastboot
Choose Boot.img that was in the unzipped file
And FLASH!
7. Reboot and let phone start
8. Install root.
How to: Power off
POwer on phone
When phone vibrates press volume down
It will then enter recovery mode.
Install SuperSu file that was downloaded.
9. Reboot and you are READY!!
=Part 2: Deodexing=
Firstly, what is deodex?​
From @philo64:
Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming.
The advantage of .odex file is the faster load time of the app and were supposed to quickly build the dalvik cache, removing them would mean longer initial boot times.
And finally rooting need not necessarily mean your device is deodexed, rather that almost all stock ROMs are odexed to some extent, and usually most custom ROMs are deodexed for easy theming.
For a casual user, the main implication is in theming possibilities. Themes for android come in APKs too, and if you want to modify any of those, you should always choose a dedoexed custom ROM.
In summary to install custom themes, install certain mods, you would need to have a deodexed phone. To check if your phone is deodexed, you can check at system/app/Phone.apk ===>where you will find this together with it ===> system/app/Phone.odex
Locked & Unlocked Bootloader
Required files:​
FLASHABLE deodex zip
Link: http://forum.xda-developers.com/showthread.php?t=2690160
Note: Download the file which matches your phones model number. Please transfer this file to somewhere in your phone.
Requirements​
Recovery is required for flashing.
Lets get started:​
Flash the file
How to: Power off
POwer on phone
When phone vibrates press volume down
It will then enter recovery mode.
Install Deodex file that was downloaded.
Done! As simple as that!
=Part 3 :Unlocking Bootloader=​
What does unlocking the bootloader do?
Unlocking the boot loader allows you to put custom ROMs on your device. Also, it allows you to install custom kernels that could potentially improve the performance, battery life and others. However, unlocking the bootloader can potentially brick your device if you do stupid things like cross flashing and others. So be warned, I am not really clear about the warranty status, do it at your own risks. Most probably nothing will happen.
:laugh:
Before unlocking bootloader, please backup TA just for precautions.
To backup TA, please use computer application: backup TA and run it.
Details and download can be found here: http://forum.xda-developers.com/showthread.php?t=2292598
Requirements and Warnings for unlocking bootloader
​
What you need to do:​
Backup all data. All data on the phone will be deleted, whole phone will be formatted. I do not know about the external sd card as I have never tried it, you could take it out as a precaution.
Backup Ta with backup Ta
What you would need:​
IMEI Number
How to: Enter *#06# in dialer and copy the imei number out
An email
Fastboot package
Link: http://doomlord.xperia-files.com/download.php?dlid=YWRiX2Zhc3Rib290
Xperia drivers
Link: http://forum.xda-developers.com/showthread.php?t=2635830
PC and usb cable
Lets get STARTED!​
1. Go to http://unlockbootloader.sonymobile.com/unlocking-boot-loader
2. Read Everything.
3. Go through all process, there will be many prompts, just click Accept/ Proceed
4. Finally you will reach a 'Create unlock boot loader key request' Page. Enter your Name Imei Number and Email.
5.Go to your email and you would most probably recieve an email about bootloader unlocking. If you dont, patiently wait.
6. You will recieve and unlock key, KEEP THIS KEY SAFELY. ( what i do is screenshot the email and save the pic in google drive.:good: )
7.Extract fastboot_with_Android_USB_file.rar and open fastboot folder
8. Enter fastboot mode
How to:
Power down ur phone and keeping the Volume Up button pressed connect the USB cable to PC this will make the phone enter FASTBOOT mode.
9.Hold SHIFT and right click on the background of the folder
10.Select 'Open command window here'
11.Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
12.In the cmd windows type in fastboot.exe -i 0x0fce getvar version
13.If a value is returned (it will return 0.5), it means the phone is correctly connected
14.Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
=Part 4:Roms List (Updated as of 5th of April)=​
1.RomAur v6.3 [ LB-UB ] - KK4.4.2- c690x - 14.3.A.0.681 - FAST-STABLE - AROMA - ONLINE [Last updated: 04/04 ]
Link: http://forum.xda-developers.com/showthread.php?t=2481248
2.iHackers v3.0 [Last Update: 02/04]
Link: http://forum.xda-developers.com/showthread.php?t=2539008
3.[LB&UB] C690X ★ monxDIFIED ★ Honam1Z™ (KK) FULL-ROOT on LB [v05-01][07/04] AROMA [Last updated: 07/04]
Link: http://forum.xda-developers.com/showthread.php?t=2463675
4. [UB/LB] [][][]14.3.A.0.681KitSlimV2.1[][][] [OD/DOD] [FullRoot] [Last updated: 31/03]
Link: http://forum.xda-developers.com/showthread.php?t=2693142
5. [LB&UB]CriskeloROM v4.0[AROMA][Stable][FULL ROOT] [Last updated: 28/03]
Link: http://forum.xda-developers.com/showthread.php?t=2560068
6. Pure Stock v1.1 [Xperia Z1] [Last updated: 12-21]
Link: http://forum.xda-developers.com/showthread.php?t=2579270
7. [DragonSphere Team][Unlock Bootloader]Cyanofire[AOSP][KitKat] [Last updated :24/03]
Link: http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=2699803
2. DooMKernel (v11)[20140401]
Link: http://forum.xda-developers.com/showthread.php?t=2448613
3. [KERNEL][CM-based] Pimped Kernel (F2FS|SoundControl|DT2Wake|CPU & GPU OC|Color Control|Voltage|FastCharge|Intelliplug...)
Link: http://forum.xda-developers.com/showthread.php?t=2660679

Hmm, the mods will not take kindly to this
You have already had a similar thread to this locked
http://forum.xda-developers.com/showthread.php?t=2704741
I suspect they may do the same here.
EDIT
Also, although none of your instructions are dangerous you do include several unnecessary steps.

LOL....I am guilty.....

HotKillerZzz said:
I BELIEVE the ADMIN would most probably lock this thread up again.
Click to expand...
Click to collapse
As with the prior thread,
This thread is a duplicate of information already found in these forums.
We expect all members to follow the XDA rules.
Rule #1 SEARCH BEFORE POSTING
If you are able to find the information and learn how to use it, then others will also.
Having multiple thread for the same thing only makes it harder for user to search for the correct information.
If there are errors in the current information then post in that thread how to correct it.
The current sticky info thread has been updated by the OP thru February 2014.
Any further posts like this will not be taken so lightly.
Please re-read the XDA RULES
thread closed

[Tool] [Unmaintained] dd Flasher (v2.0 beta)

Due to new security measures added on recent Android versions (mainly dm-verity), using dd Flasher on newer devices or recent firmwares (Marshmallow, Nougat, etc) will certainly result in a bootloop. dd Flasher probably still works if you have a unlocked bootloader and a modified kernel disabling dm-verity, but due lack of free time and other priorities, this tool is currently unmaintained.
Introduction
This tool is a new version of Nicki Root (originally released for Xperia M), but now compatible with almost any device. The purpose of dd Flasher is keeping root access in any firmware version assuming your device already have an exploitable firmware...
How it works?
Sony updates are packed in .sin files, generally stored in FTF packages. Using FlashTool, you can get an image of the system partition (system.ext4) of the latest firmware available, which is sideloaded into your device by dd Flasher. Next, it'll mount the update image (system.ext4) in a loop device, place SuperSU binaries (and when needed, disable RIC protection) and after that, stop all running processes and "flash" the modified image back into your device by using dd binary.
After dd Flasher finishes its work, all you need to do is rebooting your device into flash mode in order to flash the rest of the FTF file (excluding system partition, of course) with FlashTool. In the end, your device will be running the latest available firmware with full root access, making dd Flasher extremely useful for devices with locked bootloader that have exploitable firmwares but lack recoveries or other means to get root access.
Requirements
• Your device must already have root access. You can downgrade to an older firmware and root it with some known exploit, if needed. Also, if you don't have root access, dd Flasher won't work at all.
• You will need FlashTool and an FTF file of the firmware version you want to upgrade your device to.
• Your device should have enough free space to store system partition image of the update temporarily (around 1.5-2.5GB, depending of the device/firmware). At the moment you can store the image either on its Internal Storage or in external SD Card (when possible). USB OTG support is planned too.
• If pushing system image to SD Card, make sure your phone is connected in MTP mode (in Mass Storage mode only Internal Storage is accessible and dd Flasher will fail)
Instructions
Getting system partition image: FTF files are just ordinary .zip files with lots of .sin files inside, format commonly used by Sony in their firmwares for Xperia devices. We are interested in system.sin (it's the one with the partition image), to use it with dd Flasher, so:
• Open the FTF file with WinRAR or 7-Zip (or any other program compatible with .zip files);
• Extract system.sin somewhere you have easy access;
• Open FlashTool and go to Tools => SIN editor;
• A new window will open. Locate system.sin we extracted before, click in "Extract Data" and wait until FlashTool finishes extracting it
• If everything went well, now you should have a system.ext4 file in the same place you extracted system.sin before (you can already delete system.sin -- we won't need it anymore).
Using dd Flasher: now that we got our system partition image, we can move on to dd Flasher:
• If you didn't already have extracted dd Flasher somewhere, do it now (DUH!). Make sure FlashTool isn't running as well -- it's known to interfere with ADB interface;
• Move system.ext4 extracted previously to the same folder you've extracted dd Flasher (where dd_flasher.bat/dd_flasher.sh is located);
• Open dd_flasher.bat (or start dd_flasher.sh from a Terminal if you're on Linux) and follow the instructions. After selecting a storage device, dd Flasher will do its work;
• Please note some steps take a while to complete (mainly pushing the system image and flashing it), your device will look like it's dead and won't respond but don't worry, it's normal (on compatible devices the notification LED will pulse in different colors to indicate the the script is running);
• If everything went well, dd Flasher will notify you (and your notification light will be green, if compatible). After that, you'll need to power cycle the device, disconnect the USB cable and pull your battery off (if your battery is non-removable, use the Off/Reset microswitch). Wait some seconds and put your battery back but don't turn your device on yet.
Flashing the remaining with FlashTool: at this stage, your device have the latest firmware from the FTF you used and full root access but still have old versions of kernel, baseband, etc., so, trying to start your device now will probably result in a boot loop or something like that, so, let's finish it:
• Open FlashTool again and flash the FTF you used to extract system.ext4 in flash mode, however, make sure you've excluded SYSTEM, if you forget to do so, everything the tool did will be lost and you'll need to restart from the beginning;
• After flashing ends, disconnect the USB cable and start your phone. The first boot may take several minutes but if everything went well you should be now running the latest firmware, with full root access!
Compatibility
This tool uses an internal database to automatically set up everything needed in the officially supported devices, with at the moment are:
• Xperia E series (C1504, C1505, C1604, C1605)
• Xperia E3 series (D2202, D2203, D2206, D2212, D2243)
• Xperia M series (C1904, C1905, C2004, C2005)
What to do if my device isn't officially supported? dd Flasher also comes with a "default" config which is automatically selected when used in a unknown device. It should work by default in any Xperia (and may even work in devices from other brands), but if dd Flasher still refuses to work, PM me your device model and firmware version, I'll try to support it
FAQ
Soon
Credits
Although I wrote this script from scratch, it uses some pieces of code written originally by @zxz0O0, @[NUT] and @Chainfire, so, credits to them. I would like to thank also everyone who helped directly or indirectly in the conception of the original Nicki Root script, which became what we know today as dd Flasher
Changelog
Soon
Download
All currently released versions available in downloads tab.
XDA:DevDB Information
dd Flasher, Tool/Utility for the OEM Cross Device Development
Contributors
mbc07
Version Information
Status: Beta
Current Beta Version: 2.0
Beta Release Date: 2015-03-19
Created 2015-03-19
Last Updated 2015-03-19

Awesome!
Incredible!
Thanks for sharing this with the community.

Nice
Thanks for everything

Amazing
Thank you so much!

Who try it with android 5.0.2 of z2,z3,z3c,??? And is is full root, isn't it????

nhoc_huhu said:
Who try it with android 5.0.2 of z2,z3,z3c,??? And is is full root, isn't it????
Click to expand...
Click to collapse
Not ready yet =/
The current SuperSU package included in this beta version is unlikely to work in Lollipop -- I was working into that but it didn't made it into this beta. I'll try to get it ready for the stable version...

Error: can't stat '/data/local/tmp/ddFlasher/system/bin/sh':
Hallo,
i tried this on a xperia m (C1905) and get this error:
---------------------------------------------------
Initializing ADB [DONE]
Waiting for device [DONE]
Waiting root access [DONE]
Preparing script [DONE]
Pushing system image [DONE]
Stopping device [DONE]
Mounting system image [DONE]
Installing packages...
- SuperSU v2.46 (SELinux) cp: can't stat '/data/local/tmp/ddFlasher/system/bin/sh': No such file or directory
[DONE]
- Disable RIC (RAM Disk) [DONE]
Saving changes [DONE]
Flashing image [DONE]
System partition updated.
Reboot your phone into flash mode to finish.
NOTE: device won't respond in current state, that's
normal, pull your battery or use Off/Reset switch.
Press any key to exit...
--------------------------------------------
I used C1905_15.4.A.1.9_CE.ftf for the system.sin.
rootchecker says everything is fine but "folderMount", for example, dosnt work, it does a "hard" restart without request.... the screen went black and then reboots.
Before the rooting i also had 15.4.A.1.9 on the phone.
for "prerooting" i used towlroot v3
Could someone please help me with this.
I like to get more space for apps on the xperia m. with something like folderMount or swapinternal 2 external SD and i really tried a lot rooting technics and rootfixer and so on but nothing works.
its really frustrating.
kind regards
Oliver

olliD said:
rootchecker says everything is fine but "folderMount", for example, dosnt work, it does a "hard" restart without request.... the screen went black and then reboots.
Click to expand...
Click to collapse
You have partial root access, that's why the device reboots. I added that in to-do list, should be fixed in the stable release of dd Flasher. Since you have Xperia M, it's much easier and quicker to root it with TowelRoot and then applying the root fixer (there's a tutorial in Xperia M forums). In the meantime, if TowelRoot still fails, you can try again with the old Nicki Root, although old and not supported anymore, they should still work, at least with Xperia M...

What is the difference with the prfcreator tool?.cheers

juanpirulo said:
What is the difference with the prfcreator tool?.cheers
Click to expand...
Click to collapse
PRF Creator generates a flashable ZIP, you'll need a recovery to use it, differing from dd Flasher that archive this through ADB bridge, so, it works even if there's no recovery for your device...

Hi mbc07,
thanks for the reply.
I did this (with TowelRoot and then applying the root fixer (there's a tutorial in Xperia M forums).) several times. I have 2 Versions of the rootfixer on my pc in the moment, tried both but dosent work. I also looked for the tutorial you mentioned, but i didnt find it, sorry.
Could you please link to the tutorial or the correct rootfixer.
I just saw that i dont tell you that i have a locked bootloader, just for info.
kind regards
Oliver

Try this tutorial @olliD...

Got SuperSU v2.46 (SELinux) cp: can't stat '/data/local/tmp/ddFlasher/system/bin/sh': No such file or directory
and some related errors

[Guide] How to root Z5C - the new, less painful way (using dirtycow exploit)

Why yet another guide? Why should you follow this guide?
This is more of a future reference for myself, but might be beneficial to some other people, hence why I decided to post it.
Thanks to the "dirty cow" exploit (CVE-2016-5195), we now have a more simple way of backing up the TA partition compared to existing guides, which all relied on another exploit that involved downgrading the firmware, thus making the whole process a bit more complicated.
Unfortunately, as you can probably tell, it's still not a painless ordeal, just "less" painful. But hey, at least you have a choice.
To keep this step-by-step walkthrough guide simple and straightforward, I am focusing on just the steps and skipping the explanations.
Let's get started!
Prerequisites
Important: Your phone must be vulnerable to the "dirty cow" exploit, any firmware version with security patch level 2016-12-01 or earlier should work, such as 32.2.A.5.11. Basically, any MM or LP firmware.
Currently there is no way of backing up the TA partition on Android 7.0 Nougat firmware, you will need to downgrade to MM or earlier firmware first.
Remember to backup all your data before you downgrade, since a downgrade is akin to a factory reset. Downgrade instructions:
Follow Step 0, skip Step 1 and 2
In Step 3, download a MM or LP version firmware. For the sake of simplicity, I suggest you download the one labeled Storefront.
Follow Step 4 and 5
Done, your phone is now downgraded, skip the remaining steps. Continue with the guide as usual from Step 1
Note: If the DRM keys are irrelevant to you (TA partition already backed up/restored/lost) and would just like to root, then you can root using this guide on all firmware versions including Android 7.0 Nougat without downgrading. In this case, you can skip Step 1 and Step 7. Depending on your situation, you can also skip other parts of this guide, such as Step 2 if your bootloader is already unlocked, or in Step 5 don't wipe anything (leave all boxes unchecked) to retain your apps and data for a firmware upgrade.
Computer setup with correct drivers and adb/fastboot connection ability.
Enable USB debugging on the phone:
Settings > About phone > Tap multiple times on Build number until Developer options is enabled
Settings > Developer options > USB debugging > Toggle ON
XperiFirm for downloading official Sony firmware directly from Sony's servers
Flashtool for flashing firmware
Battery preferably more than 80% remaining, loss of power while flashing can brick your phone
Step 0 - Backup your phone (optional)
Move all your data to your SD card using the native tool: Settings > Storage > Transfer data to SD card
Use Sony's Backup & restore app to make a backup: Settings > Backup & reset > Xperia Backup & restore > More > Manual backup > Select SD card > Select content to backup
Personally, I choose everything except apps, they can be re-downloaded from the Play Store at any time, plus they take a long time to backup and restore not to mention eats up free space
Step 1 - Backup the TA partition
Download this wonderful TA Backup tool, unzip to desired location
With the phone powered on, connect the USB cable to the computer, then plug the micro USB end to the phone
Open command prompt (Start > Run > cmd), navigate to the directory where you unzipped the TA Backup tool
Run the following command:
Code:
backupTA
The tool will run and if successful, you should see at the bottom the words "TA Successfully pulled to TA_E5823.img".
TA_E5823.img is the TA partition image file, actual filename will be longer and differ for everyone so to keep it simple we'll just refer to it as TA_E5823.img in this guide.
Please check that the file is 2,097,152 bytes. If not or file is missing, then the backup has failed.
If it fails, just run the tool again a few times, or try rebooting your phone then rerun the tool. If you just can't get it to work, seek help from the tool thread.
Step 2 - Unlock the boot loader
Visit Sony's website and follow the instructions carefully
Important: Pay attention to the warnings. No, really, unlocking the boot loader will wipe your DRM keys (hence the need to back them up in Step 1) and trigger a factory reset, erasing everything on your phone.
After you've successfully unlocked the boot loader, unplug your phone and leave it powered off
Step 3 - Download stock firmware
Run XperiFirm, locate the correct Xperia Z5 Compact version of your phone (E5803/E5823) and download the firmware of your choice.
General recommendation is to download the "Customized" version that's available for your country.
Step 4 - Create a FTF file from the firmware
Open Flashtool
Tools > Bundle > Create
Select source file > Locate the folder where you saved the firmware from XperiFirm in step 3 > You should see your device name appear automatically in Device and the folder list below populated
Branding > The same as Operator in XperiFirm, e.g. Customized AU
Version > The version you downloaded, e.g. 32.2.A.5.11
Hint: Both Branding and Version information is in the folder name
In folder list, select the first item, hold SHIFT and select the last item so that all items are highlighted, then click the "- >" button > The folder list should now be empty, and the Firmware content field populated
Click Create, if successful you will see "Bundle creation finished"
Note: The FTF file is saved to %userprofile%\.flashTool\firmwares by default
Step 5 - Flash the FTF file
Click the lightning symbol in Flashtool > Flashmode
Source folder should be pre-selected to the default location mentioned above and "Sony Xperia Z5 Compact" listed in Firmwares
Expand all the arrows and select the version number
Under Wipe/Sin check all options (APPS_LOG, DIAG, SSD, USERDATA), leave all other options unchecked
Click Flash, wait for an instruction prompt to pop up
Plug the USB cable to your computer if it isn't already plugged
Turn off your phone if it isn't powered off, hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Flashtool will begin flashing the firmware automatically. It can take a long time, 10~15 minutes is normal, wait until completed
Unplug your phone and do not power it on yet
Step 6 - Patch the kernel
Download this awesome rootkernel tool, unzip to desired location.
Extract the kernel image file kernel.sin from the FTF file using any file compression program such as 7zip, WinZip, WinRAR, etc.
Open Flashtool > Tools > Sin Editor > Sin file > Locate the kernel you just extracted > Click Extract data. You should now have a file named kernel.elf in the same folder
Copy kernel.elf to the rootkernel folder
Download the latest stable version of the SuperSU ZIP file and copy the entire ZIP file to the rootkernel folder. Do NOT unzip it!
Rename the SuperSU ZIP file name so that it starts with SuperSU (case sensitive) instead of UPDATE-SuperSU, e.g. SuperSU-v2.79-20161211114519.zip
Note: if you're patching Nougat firmware, you may want to use phh's superuser instead of SuperSU due to potential battery drain. See rootkernel thread for more info. If you use phh's superuser, you will need to install the apk from the Play store after Step 8.
(optional) Download the latest Xposed framework ZIP file and copy it to the rootkernel folder. Do NOT unzip it!
Note: this only works with rootkernel v5.0 or later, if you're using an earlier version of the rootkernel tool, skip this and skip Step 9
At time of this edit (2017/2/22), Xposed does not support Android 7.0 (Nougat), so if you're trying to patch a Nougat kernel, do not include xposed. You can check the official Xposed thread for latest announcements to see if it's supported
Open command prompt and navigate to the rootkernel directory
Enter the following command:
Code:
rootkernel kernel.elf boot.img
You will be prompted to make a series of choices, including whether you want to install SuperSU and Xposed. Type Y for all of them.
If you didn't see the prompt for SuperSU (required) or Xposed (optional), check the filename of the ZIP files. Remember they're case sensitive.
You should now have a boot.img file in the rootkernel folder, that is your rooted kernel
Step 7 - Flash the DRM keys (one-time procedure)
tobias.waldvogel (rootkernel developer) said:
Flashing this file with flashtool will write your device key to an alternative unit, from where the drmfix library will pick it up.
This is a one-time task. It will survive a complete reset of the phone or Android system upgrade.
Click to expand...
Click to collapse
Copy the TA backup file TA_E5823.img from Step 1 to the rootkernel folder, then enter the following command in command prompt:
Code:
flash_dk TA_E5823.img DK.ftf
This will create a DK.ftf file in the rootkernel folder
Open Flashtool > Click the lightning symbol > Flashmode > Source folder > Locate the rootkernel folder
"Sony Xperia Z5 Compact" should appear under Firmwares, expand the arrows until you see DeviceKey and 1.0. Select 1.0, click Flash and wait for an instruction prompt to pop up
Hold the VOLUME DOWN button while connecting the micro USB end to your phone. Keep the VOL DOWN button held until the prompt disappears, which indicates that Flashtool has detected it and is correctly in flashmode.
Wait until operation is completed, then unplug the cable from your phone. Do not power on yet
Step 8 - Flash the kernel
Hold the VOLUME UP button and plug in the micro USB cable. Wait until the LED indicator turns blue, then release the VOL UP button.
Enter the following command in command prompt to flash the rooted kernel:
Code:
fastboot flash boot boot.img
After completion, congratulations, you've successfully rooted your phone!
Now you can turn on your phone, the first boot will take a very long time to initialize, don't worry.
If you see the boot animation for more than 30 minutes, then it's time to worry. First try again from Step 6, and if you still can't complete boot, go up a step starting from Step 5. If that still fails, start over from Step 3.
Step 9 - Finish installation of Xposed (optional)
In Step 6, if you chose to include the Xposed ZIP file, which means you want to install Xposed, then there's one more step to complete the installation.
Download the unofficial Material Design Xposed Installer.
Currently, this is the only Xposed Installer that works with the systemless Xposed integration method used by the rootkernel tool. Using the official Xposed Installer will not work.
Go to Settings > Security > Unknown sources > Toggle ON
Copy the Xposed Installer apk to your phone and install it.
Done!
Personal list of xposed modules to install for self reference. This is in no way a recommendation list, your preferences will vary.
Amplify
Android Phone Vibrator
App Locale
BootManager
Disable Low Battery Notifications
DynamicAlarmIcon 2
HideBatteryLowAlert
Keep Trash (broken at the moment)
Lockscreen Album Art Remover
MinMinGuard
NeoPowerMenu
NoHeadsetNotification
Ringer and Notification Volume Unlink
RootCloak
Use USB for Marshmallow V 1.2
XperiaFMwoHS
Xposed Torch: Physical keys
Youtube AdAway
Bonus - How to unroot/fully restore DRM/return to 100% factory state

Thank you for taking the time to write this guide!

best guide for root, thanks!

Fantastic guide, Thank you very much for that!
I had trouble getting the latest version of flashtool (09231) to work (mac and PC). It froze when I was trying to create the new bundle.
After downloading the older version (09186) it worked without problems.
However, currently I am stuck at step 6, running cmd 'rootkernel kernel.elf boot.img':
I get the message:
Code:
Rootkernel V5.11
- Unpacking kernel
error: Android boot magic not found
Unknown boot image format
Aborting
UPDATE:
I found the reason for the img file creation failure.
I was not patient enough in copying the kernel.elf file over. While the flashtool says file with size X created it was still compiling and only a minute later or so finished writing the file. In other words, I copied over the 'unfinished' kernel.elf and that's what caused the issue.
Trying to boot now
Thanks again for this nice guide!
Cheers,
Malcolm

Hey Malcolm, did you manage to complete the process successfully?

good news
thanks for your help. very good tutorial, realy made easy to understand
successfully rooted my nougat z5c with this,
you the best thanks

brokich said:
Hey Malcolm, did you manage to complete the process successfully?
Click to expand...
Click to collapse
Hi Brokich,
Unfortunately not (yet).
After finishing step 7 my device is stuck at the bootloader
I've tried now several times re-flashing (steps 5-7) but unfortunately no luck yet...Will try to repeat the whole procedure over the next days again.

I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..

Hello guys
On step 5 i get this error
5/031/2017 13:31:03 - INFO - Device connected in flash mode
05/031/2017 13:31:28 - INFO - Selected Bundle for Sony Xperia Z5 Compact(E5823). FW release : 1298-5497_32.2.A.5.11_R13C. Customization : Customized UK
05/031/2017 13:31:28 - INFO - Preparing files for flashing
05/033/2017 13:33:12 - INFO - Please connect your device into flashmode.
05/033/2017 13:33:13 - INFO - Opening device for R/W
05/033/2017 13:33:14 - INFO - Start Flashing
05/033/2017 13:33:14 - INFO - Processing loader.sin
05/033/2017 13:33:14 - INFO - Checking header
05/033/2017 13:33:14 - ERROR - Processing of loader.sin finished with errors.
05/033/2017 13:33:14 - INFO - Ending flash session
05/033/2017 13:33:14 - ERROR - null
05/033/2017 13:33:14 - ERROR - Error flashing. Aborted
05/033/2017 13:33:14 - INFO - Device connected in flash mode
Any idea why ?

notabene said:
I am getting problem with flashing kernel :
FAILED (remote: Command not allowed) my bootloader status was unknown at first, then I got unlock code at sony website, then it said my bootloader is unlocked, followed your tutorial and now I not able to flash kernel..
Click to expand...
Click to collapse
Did you backup your TA-partition before the bootloader status was unknown?

zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
Yes, why?
---------- Post added at 01:13 PM ---------- Previous post was at 12:49 PM ----------
zegovernator said:
Did you backup your TA-partition before the bootloader status was unknown?
Click to expand...
Click to collapse
I was able to flash FTF file. But not the kernel.

notabene said:
yes.
Click to expand...
Click to collapse
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.

zegovernator said:
Okay. It sounds like you wiped your TA partition. On which firmware did you backup your TA? Lollipop using Iovy.root or Marshmallow using this guide? I experienced the same problem once. I recovered my TA partition via Iovy.root. (because back then the only possibility was to downgrade to LP and then backup/restore TA).
Check if the service menue states:
[Bootloader unlock allowed:no] and [Remote Lock State: Locked]
If so, restore TA.
Click to expand...
Click to collapse
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Bootloader unlock allowed : yes
Remote Lock state : UnLockd
Checked DRM all OK

notabene said:
This guide, latest firmware 32.2.A.5.11.
Currently my phone stucked at after boot in TM logo.
Trying to repair via PC Companion
Phone booted. Will check if bootloader is really unlocked.
Click to expand...
Click to collapse
Flash a .tft from the MM version your backed up your TA image from. When flashing, ensure to tick everything under wipe except TA Misc.

Well finally was able to do all the steps, but phone wont boot. Stucked in Sony logo, led is yellow and then power off..

Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm

Need to use phone tomorrow, how can i revert to stock for a while since I cannot do it throught Xperia companion?
---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------
Malcolm143 said:
Yeah, same here.
Tried now multiple times but it always gets stuck at the xperia screen with orange/yellow LED
One thing that I noticed was "ERROR - root : this bundle is not valid" when I start to create the bundle. Straight after locating the custom firmware that I dowloaded with Xperifirm the message comes up in the log. Thought that this is not an issue though, or is it?
Cheers,
Malcolm
Click to expand...
Click to collapse
Did you use customized firmware? I did not, i used Tmobile CZ
Now with bootloader unlocked even PC Companion doesnt work..
So the problem is after flashing custom kernel with rootkernel+DRM fix.
So after hours of trying from step 5 with different settings for kernel, I ended up with stock rom flashed via flashtool..
tried to flash back DRM keys from Dirty cow TA Backup, using this command flash_dk TA_E5823.img DK.ftf but when rebooted in service menu drm keys are still gone..
EDIT:
Seems like there is more users with same issue with Z5C and latest rootkernel
https://forum.xda-developers.com/xp...matic-repack-stock-kernel-dm-t3301605/page200

Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.

mhaha said:
Hmm, I never ran into the stuck at boot problem, and I just successfully flashed a new phone on the same day I posted the guide. That said, I was using v5.0 of the rootkernel tool, not the latest v5.11. The rootkernel developer mentioned that there's battery drain problems with v5.11, so I decided to use the older v5.0 that helped me root two Z5C's several times in the past. Try patching the kernel again using v5.0 and see if that fixes it.
Note that v5.0 only supports up to firmware version 32.A.0.253 out of the box, you will need to make the following modification to support up to 32.2.A.5.11:
Download and unzip rootkernel v5.11 and v5.0.
Open folder \rootkernel_v5.11_Windows_Linux\Android\twrp_common_kmodules
Copy and overwrite all 7 sub-folders (folder names look like 3.10.49-perf-g83fc9bc etc.) to \rootkernel_v5.0_Windows_Linux\Android\twrp_common_kmodules
Then patch the kernel using v5.0 tool.
Click to expand...
Click to collapse
Thanks, will try in the evening.

Just to know, if I'm upgrading from previous firmware version, do I have to do all steps or I can start from step 4 (flashing ftf file)?

trying to bring my brothers A500 to life in 2019

Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn

Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?

Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.

Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.

Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.