Related
How to Root/Unroot Samsung Galaxy Note N7000 + CWM
This guide How to root galaxy note is divided in three part, according to running ROM
post #1 Root ICS/JB ROM
Post #2 Root Older GB ROM
post #3 Root access on Newer GB ROM
Click to expand...
Click to collapse
Rooting Note on JB/ICS ROM
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/showthread.php?t=1810954
So present options for rooting are - Here below 5 option to root Note, You can select any of one.
0.Root with apk (NO MORE WORKING ON LATEST ROM)
1A.Root with stock recovery including safe kernel
1B.Root with stock recovery
2. Using Odin (will raise counter)
3.Using Mobile Odin
NEW 17 Dec2012
0.Root with apkCredit goes to Chainfire, alephzain (This method won't replace kernel, so if you root with this method,I recommend to flash safe kernel)(NO MORE WORKING ON LATEST ROM)
1.Download latest from chainfire's original thread
2.Install application as routine apk installation and open it.
3.Open Exynos Abuse application from App drawer
4.Select Root device (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.It will ask SuperSU permission, Grant it See image)
6.Now your device is rooted, for security purpose you can disable Exploit.(see image)
Note : This may break camera, but unchecking disable exploit make it working again
7.Open SuperSU from app drawer and update binary (see image)
How to Unroot and make status Normal
Open Exynos Abuse app, uncheck disable explot and select Unroot device (see image)
Restart device and wait for 10 min. and then you can check status.
1.Rooting with stock recovery - Thanx to Entropy who direct this way,as well always looking for safety measures for us, Chainfire for creating great tool SuperSu (and many more), Phil3759 as files,scripts derived from his Thread and Linus Yang for Busybox.
You can have two choice to root device from recovery
1A.Root + safe kernel + advance recovery. [Recommended method]
Here this will not just root your device but also add safe kernel (patched for mmc erase cap command) so you can safely wipe your device. as well gives you advanced recovery with it you can flash flashable zip files, nandroid backup/restore and more.
All credit goes to Phil3759 for awesome work.
Visit this thread
http://forum.xda-developers.com/showthread.php?t=1901191
And download kernel in zip format according ROM you are having on device.
-Copy downloaded file to Ext SD card to root directory
-Reboot into recovery (vol up+Home+power)
-Select install(update) zip from ext SD card
-select '[your downloaded kerenel].zip' which you have copied to Ext card above
-Reboot device
Now you will have Root + safe kernel
1B.If you want just Root but not kernel, follow this
- Download Root_SuperSu 0.95
-Copy downloaded file to Ext SD card.
-Reboot into recovery (vol up+Home+power)
-Select install zip from ext SD card
-select 'root_SuperSU-*.zip' which you have copied to Ext card above
-Reboot device
-You can see superSU on appl drawer. open it and update.
-Now This will give you only SuperSU not busybox, though application which doesn't depends on system busybox will still works.e.g.Titanium Backup.
-To get full Root+busybox, Download Root_busybox *.zip
-Copy Root_busybox* only to Ext SD card
-Reboot into recovery, Select Install zip from Ext SD card. select Root_busybox* .zip and Flash.
-Done !
PS : If you can't see superSU after flashing above file(sometimes happen if there is too low space like in LQ3 ROM, then use this Root_superSU, followed by same above Root_busybox file.
Immediately after This I recommend to
1.Backup EFS
2.Flash any safe kernel with mobile Odin.
UnRoot :
Busybox uninstaller - Flash in recovery
Complete unroot (busybox+Superuser) - Flash in recovery
2. Short, easy - requires to reset counter
-Download Odin (.tar) version of custom kernel like Notecore, Speedmod, CF root kernel Or other any with same function. If newbies have confusion to select, here is one for example Notecore V12 std kernel. You can use this. But newer version can be found on link mentioned above.
-Flash it using PC odin for PDA tab.
-You will get exclamation mark and raised counter, which can be reset with Triangle Away
-First time opening triangle away application, it will ask to download file(flasher), let it complete. then choose to reset counter, it will restart in special recovery an finish job.
3. Long, No raised couter OR Exclamation mark
-Downgrade to Rootable GB ROM and Root it. OR Download This pre rooted GB ROM and flash using PC Odin
-Wipe cache, data and delvic cache from recovery
-Install Mobile Odin Pro
-Copy ICS ROM file in .tar (you want to flash) to Internal SD card (recommended, but you can have it on EXT too)
-Download Odin (.tar) version of custom kernel like Notecore, Speedmod, CF root kernel Or other any with same function. If newbies have confusion to select, here is one for example Notecore V12 std kernel. You can use this. But newer version can be found on link mentioned above.
-Open Mobile Odin Pro
-select open file
-Point to ROM file you have copied
(file name varies from image above, this is for demo purpose)
-All fiels will popup and feel automatically
-select kernel and point to custom kernel file you have copied
Tick 'Enable ever root' and 'Inject superuser(super SU) -(see image)
Flash.
Done!
First thing you should do after rooting is
-backup EFS folder ( you can use Ktool for that)
-to make some space (at least 15MB). You can safely remove google+, youtube and later install from market.
Now your device is full rooted, and use Titanium backup(or which you have used to backup) to restore
For Rooting on GB ROM, see post no 2 and 3.
How to Root/Unroot Older GB ROM + CWM
Rooting Older GB (Directly rootable) ROM
Now first thing someone newer like to know what is directly rootable and non rootable ROM
Directly rootable GB ROM is older release of ROM before Nov11, which can be root with zergrush exploit directly, without odin it (and so without exclamation mark and raising flash counter)
Which ROMs are directly rootable? and how do i know my ROM directly rootable or not?
Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is your kernel version)
If it is one of below mentioned then proceed otherwise follow post #3
These are directly rootable ROM
If ROM having one of these kernels, then it is directly Rootable.
KJ1/KJ4/KJ6/KJ7/KJ8/KJA
KK1/KK2/KK3/KK4/KK5/KK6/KK9/KKA
KL1
KL3(few of KL3 only is directly rootable e.g. Indian KL3. so in case your KL3 cudn't get root with zergrush you should consider it as non directly rootable )
Rooting Procedure
Here procedure divided in two part
Part 1. For whom who just want to root device (you will have option to move to part two anytime)
Part 2. For those who want to Root + CWM (advance clockworkmode recovery, to use upgrade ROM / Nandroid backup restore) - Recommended
Part 1 : - Credit goes to DooMLoRD for his zirgrush exploit
Download This
Before u begin:
Code:
(1) make sure u have installed adb drivers for ur device.
OR you can install kies, that will do the job.
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) Close kies SW completely, close if any antivrus SW running
Procedure for window:
-Extract file you have downloaded.
-Connect device to PC
-Execure Run Me from extracted file, and follow instruction on screen
Done. Device will be rebboted after successfull root.
On successful rooting, you can see working Superuser app in drawer.
Procedure for Max & Linux
Download This
- Extract on PC
- Confirm you have installed driver on PC (Kies will do it)
- Enable unknown sources in setting - application on device.
- Enable USB debugging in setting - application - development on device
- For Mac, double-click and run runmemac.sh. Or you might have to run it in terminal like this:
sh runmemac.sh
-For Linux, double-click and run runmelinux.sh. Or you might have to run it in terminal like this:
sh runmelinux.sh
Connect device N run script
Device should rebooted N you can confirm it by working superuser application on device.
Part 2. Credit goes to Chainfire
Which kernel You have?
(Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is kernel version)
Now download tool from below according kernel you have.
I have Kernel KJ1 - Download This– and Extract
I have Kernel KJ4 - Download This - and Extract
I Have Kernel KJ6/KJ7/KJ8 - Download this - and extract
I have Kernel KK1/KK2/KK3/KK4/KK5 - Download This - and Extract
I have Kernel KKA - Download This - and Extract
I have Kernel KK9 - Download This - and Extract
I have kernel KL3 - Download This - and Extract
I have Kernel KL1 - Download This - and Extract
Before u begin:
Code:
(1) make sure u have installed adb drivers for ur device.
OR you can install kies, that will do the job.
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) Close kies SW completely, close if any antivrus SW running
Procedure :
-Connect device to PC
-Execute "not-rooted-yet.bat" and follow the instructions.
-Device will reboot after successfull root, and you can see superuser and CWM application in drawer.
For those who have Root device earlier(with part 1) and want CWM
Download tool as mentioned in part two
-Connect device to PC
-Execute 'Already rooted.bat' from downloaded tool.
-Device will reboot after successfull pushing zImage, and you can see CWM application in drawer.
OR
If you are already Rooted, you can use Mobile Odin Pro to flash CWM
Unrooting
Download This
-Extract - Execute - Rum Me unroot.bat (same as mentioned in part1)
PS : Unrooting by above tool may leave some footprint, so if you want to do it for warranty purpose then best way is to flash stock ROM using PC Odin followed by wipe.
Get root access on Newer GB ROM (non rootable directly)
Get root access on Newer GB ROM (non rootable directly)
Here as name suggest non rootable directly ROMs. guide is not for How to root it, but better we can term it, How to get root access on such newer ROM.
As i said if you ROM not having kernel as mentioned in previous post (#2), you have to consider your ROM as non rootable.
Available option to get root access on such ROMs
1. Flash Pre rooted ROM
As name suggest flashing This ROM with PC odin, you will have ready made Root + CWM. This ROM was modified by ChainFire (All credit goes to him only). And you can flash it using PC Odin without getting exclamation mark/raise flash counter.
Download :
http://d-h.st/HJM
Mirror
Installation method is same as flashing other rootable ROM described here
After flashing you will have Root + CWM
PS: This is first ever GB ROM, and you may notice some screen issue if your Note is newer, dont worry for that once you upate to newer ROM, this issue will go. You can now update to any newer GB ROM with keeping your root intact, mentioned in option 2 below.
2. Update Newer GB ROM using Mobile Odin / CWM
If you are currently on Rooted GB ROM, you can update to any newer GB (non rootable) ROM using PC Odin OR CWM with keeping your root intact.
Here is description available How to use Mobile Odin OR CWM to update newer ROM
After updating to newer ROM, you can flash CF root kernel from here
according to newer ROM kernel. And Flash it using Mobile Odin OR CWM.
I have Kernel KL7 - Download
I have kernel KL8 - Download
I have kernel LA1 - Download
I Have Kernel LA3 - Download
I have kernel LA4 - Download
I have kernel LA6 - Download
I have Kernel LB1 -Download
I have Kernel LC1 - Download
i can confirm, it works whit gt-n7000, kernel and binary counter untouched..
dr.ketan said:
Easy Rooting Toolkit [v1.0](zergRush Exploit)
(WINDOWS ONLY)
Click to expand...
Click to collapse
Ok,and CWM, how install it???
This post is temporary backup while maintanance and not to be use for any procedure
JUST FOR BACKUP post
DONT USE ANYTHING FROM THIS POST
---------------------------------------------------------------------------------------------------------------
When No Any other method works to Root your device, use this
---------------------------------------------------------------------------------------------------------------
Note that, this will downgrade your ROM to KJ1, after that you can update it.
Download: https://rapidshare.com/files/369028110/SGN_XX_OXA_KJ1_FACTORYFS.zip Thanx to Chainfire for making it.
(special thanx to schiwa for providing premium a/c to host file)
Mirror : http://d-h.st/HJM (Thnx to Dev host for providing premium ac to XDA recognise contributor)
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (Vol down + Home + Power))
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done.
Now you have your device Rooted, Install Mobile Odin Pro n update your device to any new ROM with Mobile Odin
Root GB ROM
NEW
Download dr.Ketan's guide - How to Root & Update ROM on G-Note
Download , Extract n Hit Dr.Ketan's guide No need to enter inside folder.
--------------------------------------------------------------------------
Note : This won't be works on KL7/KL8/LA1 n newer. To gain Root access in such ROM, see post # 2 n 3 of this thread.
----------------------------------------------------------------------------------------------------------------------
Part 1 : Acknowledgement purpose (No need to download from this section)
Method 1 :
Easy Rooting Toolkit [v1.0](zergRush Exploit) with newest zergRush binary (16 Nov 2011) and newer superuser files
Watch Video Guide :
Unrooting
Rooting
video by cursed4Eva Root Unroot
Big Thanx to DooMLoRD Donate DooMLoRD
(WINDOWS ONLY)
WILL WORK ON BOTH LOCKED & UNLOCKED BOOTLOADER DEVICES!
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
Code:
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device.
OR you can install kies, that will do the job. Kies is [URL="http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=UNI_NL&CttFileID=4564828&CDCttType=SW&ModelType=N&ModelName=GT-N7000&VPath=SW/201110/20111010173222709/Kies_2.0.3.11082_152_2.exe"]here[/URL]
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
Tested & Reported to be working on the THESE devices
·
Code:
Sony Xperia X10 (GB firmware)
·Sony Xperia Arc (.42 firmware)
·Sony Xperia Arc S
·Sony Xperia Play [R800i/R800x]
·Sony Xperia Ray
·Sony Xperia Neo
·Sony Xperia Mini
·Sony Xperia Mini Pro
·Sony Xperia Pro
·Sony Xperia Active
·Samsung Galaxy S2 [GT-9100/GT-9100P]
·Samsung Galaxy S II for T-Mobile (SGH-T989)
·Samsung Galaxy S [i9000B]
·Samsung Galaxy GT5570
·Samsung Galaxy W [i8150]
·Samsung Galaxy Tab [P1000] (2.3.3 firmware), [P1000N]
·[COLOR=Red]Samsung Galaxy Note [N7000][/COLOR]
·Samsung Galaxy Player YP-G70 2.3.5 (GINGERBREAD.XXKPF)
·Samsung Nexus S [i9023] (2.3.6)
·Samsung Nexus S 4G 2.3.7
·Samsung Exhibit (SGH-T759)
·Motorola Milestone 3 [ME863 HK]
·Motorola XT860, Bell XT860
·Motorola Defy+
·Motorola Droid X sys ver 4.5.605 w/ gingerbread
·Nexus One (2.3.6 stock)
[ Credits ]
Credits go to all those involved in making this possible!
zergRush Binary from: Revolutionary - zergRush local root
Source:
Inspired from: http://forum.xda-developers.com/showthread.php?t=1319653
DooMLoRD_v4_ROOT-zergRush-busybox-su
--------------------UNROOTING TOOLS---------------
UNROOTING SCRIPT v1.0
so here is the unrooting script to be USED ONLY AND ONLY IF U HAVE USED Easy Rooting Toolkit FOR ROOTING
[ WARNING ]
if u have used any other way/solution for rooting then PLEASE DO NOT RUN THIS... you MIGHT END UP with damaged system...
(thats cause some ppl create symlinks for busybox in /system/bin/ which wipes out stock symlinks to /system/bin/toolbox and breaks/damages system)
[ DISCLAIMER ]
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
REMEMBER YOU ARE DOING THIS AT YOUR OWN RISK
now that the warning is clear (hopefully) lets get to unrooting
so here is the file.. (WINDOWS ONLY)
just download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME-UNROOT.bat"
read and follow the instructions on the screen!
Code:
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) unroot ur device using special script
(2) remove Busybox and assocaited symlinks
(3) remove SU files and assocaiated data
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
--------------------------------------------------------------
DooMLoRD_v1_UNROOTING.zip
---------------------------------------------------------------------------
Method 2: Root + CWM recovery
Souce : http://forum.xda-developers.com/showthread.php?t=1331784
Big Thanx to ChainFire - Donate chainFire
Here simplified Rooting and CWM recovery for Galaxy Note N7000
- Download Root package, see at end of post
- There are three folder
1. Initial CFroot flasher
2. Two other folder having zImage file , you need one only
Which file do I use ?
Listen closely, for I will say zis only once!
Go to Settings -> About phone -> Kernel Version. Note the string present there:
2.6.35.7-N7000XXKJ4-CL641703
What matters most (KJ4) in this case, is in bold. Try to find the matching file
e.g. CF-Root-SGN_XX_XEN_KJ4-v5.0-CWM4.zip)
so choose accordingly
- Place the zImage file accordingly in folder 1.initial CFroot flasher /zImage folder
- Start "already-rooted.bat" and follow the instructions If you are Rooted already
OR
- Start "not-rooted-yet.bat" and follow the instructions.
Note : Just below this, where you download actual flash programme, that includes initial CF root as well i have already placed zimage accordingly.
Click to expand...
Click to collapse
edit 16Nov11 Simplified
-----------------------------------------Forget all Above and follow simple Step below------------------------------
Part Two : Final Procedure
1. I want just Root- Download This
Now Execute RunMe – follow screen instruction
(Note : Who are on Linux look to End of this post)
New method edit 19Feb12
If you fail to Root with aove method, You can try this
Keep you mobile debugging on, connect to PC and use tool mention above
2. I Want ROOT + CWM
I will do with PC (all credits goes to Chainfire for making Cf root kernel)
Which kernel You have?
(Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is kernel version)
I have Kernel KJ1 - Download This– and Extract
I have Kernel KJ4 - Download This - and Extract
I Have Kernel KJ6/KJ7/KJ8 - Download this - and extract
I have Kernel KK1/KK2/KK3/KK4/KK5 - Download This - and Extract
I have Kernel KKA - Download This - and Extract
I have Kernel KK9 - Download This - and Extract
I have kernel KL3 - Download This - and Extract
I have Kernel KL1 - Download This - and Extract
Below mentioned are Non Rootable(to use for CWM only. You have to flash using Mobile odin), so you wont get Root from here, Read this thread, Post # 2 n 3
I have Kernel KL7 - Download
I have kernel KL8 - Download
I have kernel LA1 - Download
I Have Kernel LA3 - Download
I have kernel LA4 - Download
I have kernel LA6 - Download
I have Kernel LB1 -Download
I have Kernel LC1 - Download
NOW Ready to begin
I am Already Rooted - Execute "already-rooted.bat" and follow the instructions
I am Non-rooted - Execute "not-rooted-yet.bat" and follow the instructions.
OR
I will Go with Mobile Odin option (No PC needed)
After root with above mention method, Go to Market download this, Again Thnx to great ChainFire
https://market.android.com/details?...xLDEsImV1LmNoYWluZmlyZS5tb2JpbGVvZGluLnBybyJd
Now place CF root kernel to your Int/Ext memory, N flash with Mobile Odin Pro
Tip: Just to note that, who have to use root for application purpose e.g.Root explorer, titanium backup etc, they shud select 'I want just Root' option. these all application will work, as well stock recovery also will work like reset, wipe cache partition, wipe data
You shud only apply CWM, if really you are need to backup/restore firmware, regularly updating ROM, using ChainFire application(which need CF root)
---------------------------------------------------------------------------------------------------------------------
CF Root ICS ROM
N7000XXLPY - CF-Root-SGN_XX_OXA_LPY-v5.3-CWM5.zip
Extract till zImage N flash Kernel using Mobile Odin Pro
-----------------------------------------------------------------------------------------------------------------------
Now How I can revert back to Stock ROM/Unroot (In case of replacemet may i need)
I you have Just rooted only but not added CWM - Just Download this Extract - Execute - Rum Me unroot.bat
If You have Root + CWM - then first find out original stock kernel (zImage file)
Now place this file in zImage folder, n repeat procedure(Initial CFRoot Flasher), which you have done at time of pushing CWM by selecting I am rooted already
Now unroot with above said unrooting tool.
---------------------------------------------------------------------------------------------------------------
When No Any other method works to Root your device, use this
---------------------------------------------------------------------------------------------------------------
Note that, this will downgrade your ROM to KJ1, after that you can update it.
Download: https://rapidshare.com/files/369028110/SGN_XX_OXA_KJ1_FACTORYFS.zip Thanx to Chainfire for making it.
(special thanx to schiwa for providing premium a/c to host file)
Mirror : http://d-h.st/HJM (Thnx to Dev host for providing premium ac to XDA recognise contributor)
- Make sure your SGN is NOT connected to your computer
- Reboot your SGN into "download mode" (Vol Down + Home + Power)
- Start ODIN
- Click the PDA button, and select the "SGN_XX_OXA_KJ1_FACTORYFS.tar" file
- Connect the SGN to your computer
- Make sure "repartition" is NOT checked
- Click the START button
- Wait for the phone to reboot TWICE
- Done.
Now you have your device Rooted, Install Mobile Odin Pro n update your device to any new ROM with Mobile Odin
----------------------------------------------------------------
Root Note using Mac & Linux
---------------------------------------------------------------
Download This
- Extract on PC
- Confirm you have installed driver on PC (Kies will do it)
- Enable unknown sources in setting - application on device.
- Enable USB debugging in setting - application - development on device
- For Mac, double-click and run runmemac.sh. Or you might have to run it in terminal like this:
sh runmemac.sh
-For Linux, double-click and run runmelinux.sh. Or you might have to run it in terminal like this:
sh runmelinux.sh
Connect device N run script
Device should rebooted N you can confirm it by working superuser application on device.
Click to expand...
Click to collapse
dr.ketan can u explain it better please. I don't know how to do it
thanks in advance
refer this to install CWM with rom manager
http://www.addictivetips.com/mobile/how-to-install-clockwork-recovery-to-your-android-phone/
Edit : Rom manager not supporting Note
i already postet the same way some days ago here on the general note thread ----
http://forum.xda-developers.com/showthread.php?t=1326955
Where can I get the ADB drivers for the samsung note?
It's not in the Google USB driver package of their SDK Manager.
And do I need to load the drivers on the CDC Serial or the Samsung_Android device?
it isn't working for me...
c:\Temp\Samsung_Galaxy_Note\Root\zergRushAIO>runme
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- cleaning
--- pushing zergRush"
2250 KB/s (23052 bytes in 0.010s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Zerglings did not leave interesting stuff
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2611 KB/s (1075144 bytes in 0.402s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
ROM version KJ4. Any ideas? Tahnk you!
---------- Post added at 03:06 PM ---------- Previous post was at 02:58 PM ----------
Second attempt worked!
c:\Temp\Samsung_Galaxy_Note\Root\zergRushAIO>runme
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) install Busybox (1.18.4)
(3) install SU files (3.0.5)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
1875 KB/s (23052 bytes in 0.012s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x00030610
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d8
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40322cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25b15 0xafd395df
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2120 KB/s (1075144 bytes in 0.495s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.136 secs (7905470 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
2411 KB/s (22228 bytes in 0.009s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
2439 KB/s (762010 bytes in 0.305s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
If you have the Samsung Galaxy S2, then you are in the wrong forum.
You need to be here: http://forum.xda-developers.com/forumdisplay.php?f=1055
I have not updated my signature yet, yes I own a GN.
I'm in!
Hi there,
Me too, I can confirm that the described rooting method is working fine!
At start I did have an issue with the CDC something driver wanting to be installed, but that can be solved by installing the KIES software for the phone, that can be downloaded from the Samsung website.
Regards,
Worked like a charm.... thanks!
Worked like a charm.... thanks!
Thanks for the tip. The KIES software from Samsung had the ADB driver that was needed.
And it worked very well.
You can Download KIES Here
It feels like doing startcraft on my phone. Haha.
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
360 KB/s (23052 bytes in 0.062s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x00030610
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Overseer found a path ! 0x000309d0
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40322cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25b15 0xafd395df
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
1919 KB/s (1075144 bytes in 0.546s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes transferred in 0.123 secs (8741008 bytes/sec)
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
463 KB/s (22228 bytes in 0.046s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
2267 KB/s (762010 bytes in 0.328s)
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
I'm out!
Hi there,
Can confirm that unrooting works too.
Sadly I have to say that I must return my Note because the phone speaker went dead.
Regards,
Does it also SIM unlock the Galaxy Note?
ok for the root but i dont undestending for the CWM.
thanks
Plz who have successfully rooted, share your experience here.
have anybody installed ROM manager after ROOT?
Wifi tethering working ?
any error reported?
Tutorial includes stock firmware .ftf files for Flashtool!
Changelog:
22-08-2012 - Expanded to Xperia Arc section.
This tutorial has been created to help XDA members in order to modify their 2011 Xperia phone. This tutorial is originally made for Xperia Ray by hansip87, link to original topic forum.xda-developers.com/showthread.php?t=1426912.
Same tutorial in Xperia Mini & Mini Pro & Active section: http://forum.xda-developers.com/showthread.php?t=1568792
These tutorials can also work on other 2011 Xperia phones. Instructions will also work with ICS unless written otherwise, so read carefully!
All kinds of ideas/comments/critism are always welcome.
Everything you do is on your own responsibility. I am not responsible for any damage that you have made to your phone.
Tutorial includes:
Android Dictionary
Root the Phone(GB and ICS)
What to do after rooting(apps etc)
Installing stock firmware and downgrading
Install Busybox and CWM Recovery
Unbricking your phone(after OTA update)
Install Supercharger to optimize Memory and KAK to optimize Kernel
Edit build.prop for additional optimizations
Enable Dual Band and Burst Mode for Wifi
Unlocking bootloader
Installing custom kernel
Installing custom ROM
Relocking bootloader
Preparing for ICS
Overclock/Underclock/Undervolting guide
Downloads
Frequently Asked Questions(FAQ)
Yet to be added:
List of system apps and which can be removed - Gingerbread and ICS
Optimizing battery life
What will you need:
Stock ROM on your Xperia and USB cable
PC Companion installed on your computer (for base drivers)
FlashTool(Flashtool topic and download)
Enable "USB DEBUGGING" from Menu -> Settings -> Applications -> Development
Enable "UNKNOWN SOURCES" from Menu -> Settings -> Applications
Set Connectivity mode to MSC from Menu -> Sony Ericsson -> Connectivity -> USB Connection Mode
Root Explorer or any file manager that provides access to root (I personally used ES File Explorer)
1. Android Dictionary
ADB - Short for Android Debug Bridge. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
Android - Operating System for smartphones and tablets, based on Linux, built by Google, similar to Windows on PC.
AOSP - Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK - An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Baseband - System of a smartphone, that controls the cellular radio systems(GSM, 3G, HSDPA etc).
Bootloader - Controls the booting process, makes sure that you will access User Interface. These programs tell the Android device how to start up, and are critical to its functionality.
Build.prop - A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations.
BusyBox - Command line bridge, used to give commands to Android system. You will need app to send commands, it will use BusyBox to send the commands.
Brick - A phone, that you paid a lot for and now you can use it as brick, because it doesn't start up.
CWM/ClockworkMod Recovery - A specific program, that is used before booting to Android. Allows the user to make full backup of system and install custom ROMs, updates etc.
CM - Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
Dalvik Cache - The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
Deodexed - Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
Downgrade - A job, that you have to do, when you want to get from newer firmware to older firmware.
Factory Reset - This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card.
Fastboot - Command Line Tool to edit Android filesystem. Unlike flashmode, this allows flashing unsigned partition images.
FC - Short for FORCE CLOSE. See FORCE CLOSE.
Flashing - The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
Flashmode - Phone mode, where you can freely flash any firmware to your phone via WotanServer or Flashtool.
Force Close - When a program on the Android device becomes unstable, the DALVIK program will force it to terminate to prevent further system instability.
GB/Gingerbread - Android 2.3 version, codename Gingerbread, mostly used shortly as GB.
Governor - A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA - Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS/Ice Cream Sandwich - Android 4.0 version, codename Ice Cream Sandwich, mostly used shortly as ICS.
Kernel - Bridge between hardware and Android, used for hardware information exchange and control hardware parts(CPU etc).
Launcher - A program that launches programs in Android. Examples are Touchwiz (Samsung), Launcher Pro, ADW Launcher, and Go Launcher.
MD5 Checksum - A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
Nandroid Backup - A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
OTA/Over The Air - Updating your phone firmware directly from your phone via 3G or WiFi connection.
Overclocking - Setting the processor's clock speed to run faster than its default setting, i.e. 1200 MHz (1.2 GHz) vs 1000 MHz (1.0 GHz).
RAM - Random Access Memory, data storage area, where are currently in use apps and services. It is used, because it has really high data transfer rate compared to other possibilities(SDcard, hard disks etc).
ROM - Read Only Memory, data storage, where the data can only be read by system itself. It includes all data to start the Android. Many developers edit this ROM to change Android interface.
Root(ing) - Process, during which user gets access to Android system partition and files, giving the possibility to edit Android.
SEUS - Sony Ericsson Update Service, can be used in some cases to get back to newest stock firmware.
Undervolting - Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
WotanServer - A paid application, which can be used to flash any stock firmware version with kernel to your phone.
2a. Root your phone - Gingerbread – only firmware 4.0.2.A.58 or older
Currently ZergRush method by DoomLord is the simplest way to do it.
NOTE: If you have newer firmware(4.0.2.A.0.62 or 4.0.2.A.0.69), check tutorial 3 first to downgrade your firmware.
Download the attached file from here, extract it to a folder using any .zip manager, for example 7-Zip.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser app and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2b. Root your phone – ICS 4.1.A.0.562 ONLY
NOTE: Make sure you have Android 4.0.3 and 4.1.A.0.562 firmware! This might not work on Android 4.0.4!
Download the file from this post, extract it to a folder using any .zip manager, for example 7-Zip/WinRar.
Make sure all drivers are installed.
Make sure USB debugging(Menu\Settings\Developer Options\Development) and Unknown Sources(Menu\Settings\Security) is allowed in the settings.
Connect Phone to USB.
Execute "RUNME.bat" from the extracted folder.
Follow the instructions in the window.
The phone will be rebooted, after reboot you will have Superuser and Busybox and your phone is rooted!
Don't forget to thank DoomLord on the original link in the credits
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
2c. Root your phone – ICS 4.1.B.0.431 and newer
First update your phone to the newest firmware.
Use Flashtool to flash a ICS 4.0.3 stock firmware kernel to your phone.
Run the exploit created for 4.1.A.0.562 firmware, explained in previous tutorial.
Install back ONLY the newest kernel.
Now you can access system files on your Android. Some file manager apps will require you to set a ticker to get access to the root, ES File Explorer is one of them. What to do now? Read the next tutorial.
3. What to do after rooting?
Congratulations! You've rooted your Android phone. But...what now? Here is a list of what you can do:
Install Titanium Backup. It allows you to backup all system and user apps with all data that belongs to the app. Very useful when installing firmwares and wipe is required. Using this program, you can easily backup and restore lots of apps at once. Also includes some other functions, link to Play Store.
Edit your Android. In this tutorial are some modifications that can be done. Read the forum, explore different sections and look for more modifications(there are thousands of them!), that you can do. Watch out, make sure that it will work on your phone, else you might mess up something and need to reinstall the ROM.
Remove unneeded system apps to free up some space on the ROM. This [/B]topic, http://forum.xda-developers.com/showthread.php?t=1089470, includes info about APKs, that can be removed and what must stay.
4. Installing stock firmware and downgrading
In the newer firmware, the ZergRush exploit has been blocked. If you want to return to stock ROM or you want to get your phone rooted, you have to install (older) firmware to your phone, which can be done 2 ways:
Flashtool, you need to find correct files yourself.
WotanServer, you have to register a account. - Costs €1.99
Flashtool method
Download the correct firmware file for your phone at the bottom of the post.
Make sure Flashtool is installed.
Place downloaded firmware file(.ftf format) in Flashtool\firmwares(by default C:\Program Files\Flashtool) folder.
Start Flashtool.
Click the lightning button and choose Flashmode.
Firmware should appear there, if you have it in correct folder. Choose it.
Turn off your phone, connect USB cable to computer, then press Volume Down button and connect USB cable to your phone.
Flashtool should detect your phone and starts flashing. Follow the instructions.
When it says „Flashing completed“, unplug your phone and turn it on.
WotanServer method
Go to WotanServer.com, make an account and download the client.
Start the client.
It wants to find your phone. Turn off your phone, then connect USB cable to computer, press Volume Down button and connect USB cable to your phone.
WotanClient detects your phone automatically.
Click Advanced Settings and choose firmware (4.0.2.A.0.58 or older if you want to root).
For region, it isn’t a big deal, which one you choose, although picking own one is easier.
Next, enter your account details(e-mail address and password) and click Update. Make sure you have enough credit.
Click Next and it will download proper firmware files and automatically install them.
When it’s ready, unplug your phone and turn it on.
After that you can proceed with rooting your phone, which is explained in previous guide. Or just enjoy your recently installed stock ROM
5a. Installing ClockworkMod Recovery
NOTE: You must have stock and rooted phone!
NOTE: Most custom kernels already include Recovery.
What you need to do:
Go to this link: http://forum.xda-developers.com/showthread.php?t=1346190 and download SE Tweak Installer.
Connect your phone via USB cable.
Start SE Tweak Installer.
Pick CWM, which is for your phone.
Click Install and wait. When it is ready, CWM is installed.
There is one more solution to install Recovery.
Go to Android Market/Play Store.
Search for X-Parts.
Download the app to your phone and start it.
Follow the instructions to install the Recovery.
And enjoy having a recovery.
To enter the Recovery, turn off your phone, then turn it again, when Sony Ericsson logo appears, get ready. When screen gets brighter during Sony Ericsson logo, click Volume down button(I usually keep clicking it until I get into the recovery).
To move around in Recovery, use volume buttons to go up/down, Menu button to enter, Power button for back(in some cases, also back button works).
5b. Installing BusyBox
NOTE: Requires root.
NOTE: If you used zergRush method to root, BusyBox is automatically installed already and you can skip this.
Go into Play Store(Android Market) and search for BusyBox Installer.
Download it and start it.
Follow the instructions.
6. Turning the "brick" into a smartphone
If you had unlocked bootloader and did OTA(Over the Air) update, then you probably ended up with a dead phone, aka brick. Don't worry, it is not completely bricked, still can be saved!
Download UnbrickingXperia2011.zip file from this post below.
Unpack the .zip file and place the .ftf file in Flashtool\firmwares folder.
Open Flashtool.
Get your phone to flashmode, make sure it is turned off, press down Volume DOWN button and connect USB cable.
In Flashtool, click the lightning button, pick Flashmode and choose the Xperia_2011_FreeXperia_ALL.ftf file.
Let Flashtool finish.
Install stock firmware and kernel to your phone.
Remove USB cable from your phone and start your phone.
Try not to brick it again, less problems for you.
7a. Installing V6 Supercharger
Both can be used to improve the speed of your phone. Supercharger is meant to improve RAM, KAK is for kernel.
Install Script Manager.
Download Supercharger from this topic, http://forum.xda-developers.com/showthread.php?t=991276, make sure to download the "V6_Supercharger_for_Android-update8.sh.txt" file.
Place the file on root of your SDcard, that is the main folder on SDcard(where everything else is).
Open Script Manager, start the V6 Supercharger as normal. You can choose 0 as scrolling speed.
Pick the choice, that you like. I have used Agressive 1 personally(enter the number infront).
When done setup, just exit from the menu (no.17). The result file named 99Supercharger will be generated at /data/ (or in /system/etc/init.d/99Supercharger if you have init.d mod)
(If you use init.d mod, skip this) Open Script Manager, select the /data/99Supercharger.sh, and when the properties window pops up, tag it as "su" and "boot") The ScriptManager will load it at startup and as root, otherwise it will fail.
To test if the script is loaded or not, launch again the setup script(repeat step 4-5) You will find a text like "Launcher is.. xxxxxxx" if it is written as "weak", the script is not running yet. If it is "hard to kill" it is running correctly.
7b. Installing Kickass Kernelizer
This should improve your kernel, haven't tested myself yet.
Go to http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 and download the file.
Open it with Script Manager.
Follow the instructions.
Press I for Install.
(If you use init.d mod, skip this) Open ScriptManager, select the /data/98KickAssKernel.sh, when the properties window pops up, tag it as "su" and "boot") The Script Manager will load it at startup and as root, otherwise it will not work properly.
Reboot your phone.
To verify, run it again after reboot and when it offers Verify, choose it.
8. Editing build.prop to optimize your phone's system
Build.prop consists of quite a lot lines, which set up, how some phone functions work. To edit the file, you need root rights and a program to explore root(ES File Explorer, Root Explorer etc).
Making a NANDroid backup in Recovery first is a good idea, because if you make a mistake in build.prop file, and phone does not boot into Android, you can still restore it.
Start your Explorer app and go to directory \system
Open build.prop file with a text editor.
Go with your PC to this post: http://forum.xda-developers.com/showpost.php?p=16833651&postcount=1. There are also other tweaks, you can try if you want(you might need init.d script for your ROM for init.d tweaks).
Read the first part of the post, there are some build.prop tweaks, choose which ones you want.
Make modifications in your build.prop file, save it and restart your phone.
Changes should take effect, if you have made a mistake, edit the file again or restore the backup, depending on the situation.
Some more tweaks for build.prop, init.d etc:
http://forum.xda-developers.com/showthread.php?t=1289539
http://forum.xda-developers.com/showthread.php?t=1342241
9. Enabling WiFi Dual Band and Burst Mode
As the title already, this is to increase the internet speed for WiFi on your phone.
Personally, I didn't notice any difference in battery usage.
Open Root Explorer, go to \system\etc and open file named tiwlan.ini with Text Editor.
Edit these lines:
Code:
HT_Enable=0
BurstModeEnable = 0
WiFiAdhoc = 0
to
Code:
HT_Enable=1
BurstModeEnable = 1
WiFiAdhoc = 1
and
Code:
Single_Dual_Band_Solution = 0
to
Code:
Single_Dual_Band_Solution = 1
Reboot your phone.
10. Unlocking bootloader
Unlocked bootloader is needed for most custom ROMs and for ALL custom kernels. It allows the booting system to be changed.
This can be done via official way or via test point method. Official way also removes DRM keys, which cannot be restored at all.
WARNING: You will lose warranty with this!
THE OFFICIAL METHOD - You lose DRM!
Go to http://unlockbootloader.sonymobile.com.
Enter service menu, open keypad and enter *#*#7378423#*#*.
Service Info - Configuration, Bootloader Unlock Allowed: Yes/No. If it says Yes, continue. If it says No, do not continue, because it will not work.
On the website, click "Start Unlocking the bootloader".
In the text, there are instructions, what you need to do. Also there are drivers that are needed for this process. Follow the instructions.
Install the drivers, then click Continue.
Enter your IMEI, name and e-mail. Leave out the last number from the IMEI.
You get a code, leave the website open, you will need this code.
Turn off your phone, then connect USB cable to your PC, hold down Volume UP button and connect USB cable to your phone. Blue LED should light up.
You will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
Open command prompt, first enter this
Code:
cd C:\...\android-sdk\platform-tools
Replace C with the correct drive letter and ... with the path to the android-sdk folder. Next, enter this command
Code:
fastboot.exe -i 0x0fce oem unlock 0xKEY
Replace KEY with the key that you got from the website.
Bootloader is now unlocked.
THE TEST POINT METHOD
Go to this topic http://forum.xda-developers.com/showthread.php?t=1285285.
Follow the instructions to patch bootloader.
11. Installing custom kernel
Most custom ROMs will require a custom kernel, some of these include it already(CM, MIUI etc), other you need to find yourself(Hybrom). Installation is done via fastboot. First, you need to find a custom kernel, that will work on your phone. You can find these from Development section.
Make sure your bootloader is unlocked, enter service menu(*#*#7378423#*#*), Service Info, Configuration, if it says Bootloader unlocked: Yes, then it is unlocked.
Make sure fastboot drivers are installed. These should come with Android SDK.
Download the kernel you want. You will need a .img file, which is mostly inside a .zip file.
From the downloads section, download kernel installation package and extract the folder.
Place the .img file inside the folder. If it's name isn't boot.img yet, rename it to boot.img.
Place your phone in fastboot. Turn it off, connect USB cable to your computer, hold Volume UP button and then connect USB cable to your phone. Blue LED should light UP.
Double-click on the flash.cmd file. It will start fastboot automatically and install the kernel.
When finished, disconnect the cable and turn on your phone.
12. Installing custom ROM
Requirements: Unlocked bootloader, ROM .zip file downloaded.
Nothing difficult here.
Place the downloaded .zip file to the root of your SDcard.
Install the custom kernel, explained in previous tutorial.
Enter Recovery(while booting, when screen gets brighter, press Volume Down button until phone enters Recovery).
Make factory reset, wipe cache partition and clear Dalvik Cache(under Advanced).
NB! Do NOT make format /system, because some ROMs require files from system folder and installation will not finish if files are not available. Then you have to install stock ROM again.
Choose install zip from sdcard, pick the downloaded .zip file on your SDcard.
Wait for it to finish and reboot your phone.
13. Relocking bootloader
When you return to stock and/or need warranty back, you will need to relock bootloader. First install stock ROM and kernel and then relock bootloader, else you will have problems. Depending on the unlocking method, there are 2 ways to relock.
TEST POINT METHOD
Start S1 Tool and click Restore button. Should relock the bootloader automatically.
OFFICIAL METHOD
Will not work on test point method, because bootloader was patched there ant not unlocked.
Make sure you have Flashtool installed.
From the downloads section, download Xperia_Relock_Bootloader.zip file.
Extract the package, there is a .ftf file.
Flash the .ftf file with Flashtool.
Bootloader is locked again
14. Preparing for Ice Cream Sandwich update
ICS update is already released. You might want to know, what you need to do to get the update. Make sure, that you have
a working Xperia 2011 device
with stock ROM and stock kernel installed(if you install via PC Companion or SEUS)
and locked bootloader(if you install via PC Companion or SEUS).
Root access doesn't matter(according to current information), whether you have or not. It is lost after update anyway.
PC Companion and/or Update Service installed on your computer.
Drivers working for your phone.
Official update will only be available via PC Companion and Update Service. But you can also use Flashtool to install ICS.
15. Overclock/undervolt/underclock guide
Want to give your phone a small performance boost? Or save battery?
WARNING! The following is done fully under your own responsibility! Overclocking is a dangerous process and doing it without knowledge will end in FULL BRICK! Be careful with what you do and proceed only if you fully understand the process!
You need root, unlocked bootloader and custom kernel, that allows OC/UC/UV, installed.
Install app to edit the CPU, for example SetCPU, SetXperia, NoFrills CPU Control or another one.
Open the application on your phone.
CPU Frequency is the clock, how fast your CPU works. The faster it works, the more power it uses, more heat is generated, info is faster calculated.
CPU voltage is how much power the CPU receives. It can affect, how CPU works. Manufacturers set it to high enough for CPU to work properly. You can set it lower to save battery, however you might occur problems with your phone!
Search on internet for more information about overclocking to know more about it.
Do everything carefully, as a small mistake could result in serious problems(for example, FULL BRICK due to motherboard damage). Repairing can cost more than phone itself.
XX. Downloads
Stock firmwares, ftf file is inside the zip/7z archive(except PreRooted firmwares)
4.0.2.A.0.XX type - Android 2.3 Gingerbread
4.1.A.0.562 - Android 4.0.3 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
4.1.B.0.431 and 4.1.B.0.587 - Android 4.0.4 Ice Cream Sandwich - You will need 7-zip to extract the ftf file.
Xperia Mini (ST15i)
4.0.2.A.0.42 - http://www.mediafire.com/?uboo3lrdxnoeldn
4.0.2.A.0.62 - http://www.mediafire.com/?zad88cn2n78ashv
4.1.B.0.431 - http://www.mediafire.com/?wot47vumhstlc4h
Xperia Mini Pro (SK17i)
4.0.2.A.0.42 - http://www.mediafire.com/?hevz3x5w9pqt24q
PreRooted 4.0.2.A.0.69 - http://www.mediafire.com/?desy0bkka1b44g0 - Flashable zip
4.1.B.0.431 - http://www.mediafire.com/?j0bdx06zz5skvzt
Xperia Mini Pro (SK17a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?433tco785pj1y69 - Branded Mexico Telcel firmware
4.0.2.A.0.62 - http://www.mediafire.com/?zykznaar0yjxbp5
4.1.B.0.431 - http://www.mediafire.com/?9d2wcbfqly4lkf3
Xperia Active (ST17i)
4.0.2.A.0.42 - http://www.mediafire.com/?3zm7iss0sid94wr
4.1.B.0.431 - http://www.mediafire.com/?7hsrd2wmuqgmmq1
Xperia Active (ST17a) - "a" model
4.1.B.0.431 - http://www.mediafire.com/?yvjnt0qctun9t6j
Xperia Live with Walkman (WT19i)
4.0.2.A.0.42 - http://www.mediafire.com/?5ahb85ir7ni0i06
4.0.2.A.0.58 - http://www.mediafire.com/?4deeznrbldz886u
4.0.2.A.0.62 - http://www.mediafire.com/?ervpg54922b9c0p
4.1.B.0.431 - http://www.mediafire.com/?xklhl2uk1itk0ey
Xperia Live with Walkman (WT19a) - "a" model
4.0.2.A.0.58 - http://www.mediafire.com/?adigb2qgvpf0o1s
4.1.B.0.431 - http://www.mediafire.com/?4t3mm7dvm01v3mh
Xperia Ray (ST18i)
4.0.2.A.0.42 - http://www.mediafire.com/?0oi9t2m0z5p8a9y
4.1.A.0.562 - http://www.mediafire.com/?1lh84f1nyzoz883
4.1.B.0.431 - http://www.mediafire.com/?2j7i7rruqxnui3q
Xperia Arc (LT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?8aa5x52vc9dc25l
4.0.2.A.0.62 - http://www.mediafire.com/?0ann64yqnl4ei62
4.1.B.0.431 - http://www.mediafire.com/?pzr6phfd19xgbva
Xperia Arc S (LT18i)
4.0.2.A.0.42 - http://www.mediafire.com/?9mz2rhdouu6ggtk
4.0.2.A.0.62 - http://www.mediafire.com/?gn6y626km6nryi7
4.1.A.0.562 - http://www.mediafire.com/?9at03bbhdf72h3h
4.1.B.0.431 - http://www.mediafire.com/?20z5t5tg3dgbugz
Xperia Neo (MT15i)
4.0.2.A.0.42 - http://www.mediafire.com/?4qy6vd4ndbfy8wy
4.0.2.A.0.62 - http://www.mediafire.com/?4apn8hchshmqq07
4.1.B.0.431 - http://www.mediafire.com/?6i2ihiint7tfl79
Xperia Neo V (MT11i)
4.0.2.A.0.42 - http://www.mediafire.com/?8bwwe8m6c49vs4t
4.0.2.A.0.62 - http://www.mediafire.com/?elicesjb6aerb7i
4.1.A.0.562 - http://www.mediafire.com/?aao25nnf30rcs50
4.1.B.0.431 - http://www.mediafire.com/?84d4w462qdfk44a
Xperia Play (R800i)
4.0.2.A.0.42 - http://www.mediafire.com/?cne2yvrtcu3ccvn
Xperia Pro(MK16i)
4.1.B.0.431 - http://www.mediafire.com/?8jdu5dkhlm4psoc
Kernel Installation Package for Xperia phones - http://www.mediafire.com/?c0u0kf0ud5jvkhk
Unbricking Xperia 2011 Package - http://www.mediafire.com/?s166qsg8qaaxc43
Relocking Xperia Bootloader Package - http://www.mediafire.com/?1an09qoq5yq4b5y
XX. Frequently Asked Questions
Q. I just installed custom ROM, but phone is frozen at the logo!
A. Did you install custom kernel, which is confirmed to be working with that ROM? If you did everything correctly, it might take a while, because at first boot new caches are created.
Q. Flashtool won't install stock firmware, gives this-and-this error.
A. Make sure phone is in flashmode(turn off, hold down Volume DOWN, connect USB cable). If yes, make sure, that correct drivers are installed. If yes, post here with FULL log, and I will take a look.
CREDITS
http://forum.xda-developers.com/showthread.php?t=1093062 - Android dictionary
http://forum.xda-developers.com/showthread.php?p=18805532 – zergRush rooting method by DooMLoRD
http://forum.xda-developers.com/showthread.php?t=1346190 - SE Tweak Installer by quangnhut123
http://forum.xda-developers.com/showthread.php?t=1426912 - Original tutorial by hansip87
FreeXperia Team for the unbricking file
http://forum.xda-developers.com/showthread.php?t=991276 - V6 Supercharger
http://forum.xda-developers.com/showpost.php?p=22078137&postcount=7649 - Kickass Kernelizer by zeppelinrox
http://forum.xda-developers.com/showthread.php?t=1477440 - Stock firmware list for 2011 Xperia phones by benji.berg
http://forum.xda-developers.com/showthread.php?p=24882250 - DooMLoRD ICS Rooting method
http://www.xperiablog.net/2012/04/16/root-for-android-4-0-ics-xperia-update-now-available-guide/ - Original Xperia ICS rooting guide
http://forum.xda-developers.com/showthread.php?p=26914104#post26914104 - Android 4.0.4 rooting guide by puppet13th
All users, who gave me ideas for this topic.
All users, who have shared their stock firmwares.
Everyone else, who I may have forgotten.
Still needs to be edited in order to fit it for Arc/Arc S/Pro.
If you notice a bug or have an idea, let me know.
Also, critism is welcome.
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
Greetings.. I bought Xperia x F5121 ( 34.0.A.1.264) Android 6.0.1 (Prototype) online & found its prototype.Possible for me to root & flash custom rom.If theres a way,could anyone guide me .Thks in advance.I appreciate it.
My apologies admin.If i post wrong section pls delete it.
if the BOOTUNLOCK is allowed on your PROTOTYPE DEVICE then
short answer is : YES
dial *#*#7378423#*#* goto SERVICE INFO >> CONFIGURATIONS
HERE you will see alot of info, search for BOOTLOADER UNLOCK ALLOWED text and see what shows ,,, if NO then sorry! this device is locked by SONY and only they can unlock it
if BOOTLOADER UNLOCK ALLOWED has YES then MAGIC CAN BE DONE
IF YOU ARE NEW TO SONY WORLD then you must save XPERIA X DRM KEYS
since you are already on ANDROID 6 (YAY)
just enable USB DEBUGGING from DEVELOPER OPTIONS
and
download the UNIVERSAL (DIRTYCOW-BASED) TABACKUP SCRIPT ( DOWNLOAD FROM HERE ( REFERECE MASTER POST BY RAYMAN
uzip the script on desktop and RUN the .BAT file, it will ask permission on your mobile screen, ALLOW it and after few seconds, the SCRIPT will EXTRACT TA-xxx-xxxx-xxxx-date+timeStamp.IMG file (2mb in size) IN THE SAME FOLDER
you can run .bat mulitiple times! each time it will extact the same TA.img file with different file name , i ran it thrice
now you have your DRM KEYS FILE (SOME USERS SAYS ITS NOT NECESSARY BUT TRUST ME! IT IS! ) KEEP THIS TA.img file SAVED on cloud!
------------------------
UNLOCKING BOOTLOADER
SONY official handout unlocking keys for FREE at
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
follow the steps! select your device model from list, provide them your email, they will send you one time link , to generate BOOT UNLOCK KEY AGAINS YOUR "IMEI" NUMBER ( dial *#06# on your F5121 to obtain IMEI number) (its even given on configuration page, where you checked the bootulock status )
- flashtool (www.flashtool.net) can ALSO unlock xperia Bootloader! (install flashtool and then install drivers also ( c:\flashtool\drivers)
- clicking BLU while device is CONNECTED IN FASTBOOT MODE ( it will prompt you) and giving SONY's generated KEY will UNLOCK your F5121's bootloader! device will JERK, ANDROID BOT WILL APPEAR and ALL PARTITIONS (accpt system) will be FORMATED and you will loose all your data, accounts, details , DRM KEYS ... (make sure you take backup of your photos/videos/music)
--------------------------------------------------
NOW IF YOU WANA STAY ON 34.0.A1.264 and DONT wana UPGRADE to ANY OTHER BUILD came after this then
you need to do this
0. put magisk16.0.zip in sdcard (if you don't have sd card then UTG drive, flashdrive, etc)
1. unlock bootloader
2. flash TWRP (via fasboot
3. FLASH modified kernel ( the MASTER TOOL of SONY WORLD www.flashtool.net) (installing Xperia COMPANION + Google Minimal ADB & Fastboot.zip is M - U - S -T )
4. BOOT in to twrp, flash MAGISK16.0 from sdcard
and reboot device
the device will boot ROOTED 34.0.A.1.264
NOW IF YOU WANT TO UPGRADE TO NOUGAT FROM 34.0.A1.264 and ROOT IT THEN
-the recommended NOUGAT Stockrom version is 34.3.A.0.252 (releasedin dec2017)
1. download the .252 ftf file from xda post
https://forum.xda-developers.com/xperia-x/how-to/sonyx-f5121-downgrade-8-0-0-to-7-1-1-to-t3754986
2. flash it via flashtool / you need to see solid tutorial for that! please do research , flashing xperia is TRICKY
3. flash twrp
4. flash modified kernel
5 boot into twrp and flash MAGISK and REBOOT.
NOW IF YOU WANT TO UPGRADE TO OREO FROM 34.0.A1.264 and ROOT IT THEN
-for OREO the RECOMMENDED STOCKROM version is 34.4.A.2.97 (released in JULY2018)
1. you must download the latest stockrom
2. flash it
3 flash modified Kernel
4. boot in to twrp and
(a) flash the DRMFIX.zip
(b) Magisk16.0.zip
5. reboot
ALL KERNELS BY YEARS/BUILD WITH DRMFIX FILES ETC ARE GIVEN IN MY POST
https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
PLEASE READ THOROUGHLY !
I have tested all these kernels my self since I have F5122 however if anything goes wrong please note that XDA or any member is NOT responsible
try it on your own risk
Thks again for the fast reply.I'm choosing upgrading to Oreo. I download Germany o2 DE ( 34.4.A.2.97 /R2E ) & i'm using the latest flashtool v0.9.25.0 .I'm stuck at fsc script shown ( Those data are not in the FSC script and will be skipped. RESET-NON-SECURE-ADB. Do u want to continue? )i click no & close it. I download the fsc script 34.4fsc from your site & overwrite paste it on C:\Users\USERNAME\.flashTool\devices\F51XX .Once done,i reopen the flashtool & flash.Same problems occurs.i even restart my pc..No success..
jingaro said:
Thks again for the fast reply.I'm choosing upgrading to Oreo. I download Germany o2 DE ( 34.4.A.2.97 /R2E ) & i'm using the latest flashtool v0.9.25.0 .I'm stuck at fsc script shown ( Those data are not in the FSC script and will be skipped. RESET-NON-SECURE-ADB. Do u want to continue? )i click no & close it. I download the fsc script 34.4fsc from your site & overwrite paste it on C:\Users\USERNAME\.flashTool\devices\F51XX .Once done,i reopen the flashtool & flash.Same problems occurs.i even restart my pc..No success..
Click to expand...
Click to collapse
click yes and proceed
what about drmkeys extraction part?
have you done that
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.