Related
Taken from the inital forum thread
Posted in this forum so that it is correct forum
There is already a 'how to root' thread going, suggest you post there for help.
27/05/2011:
-------------------------
Modified the Iconia Tab GB's xml files to remove the need for portrait mode and change the name so not as to be confused with the original ginger break.
File attached.... signedGBIconiaTab1.20.apk (296.8 KB)
good luck
Older Details:
-------------------------
Root based on Chainfire's gingerbreak
Usual rules apply, if you break then best efforts but in the end it's was up to you to click 'root'
Thank you for your tools and time:
apkmanager; Daneshm90
apktool; brutall
Superuser honeycomb; j4mm3r
gingerbreak initial version ; Chainfire (Please review this for all the requirements)
The Android Exploid Crew for the exploit
Thanks you people for your help and input:
lou0611,dc13,maddler,nycbjr,seraphimserapis, it2steve, thor2002ro, rmgold & of course all of the team xda-developers
Special thanks to maddler for pointing us to the exploit
Chainfire for his apk version and work on gingerbreak
More Details
What we done to gain inital root:
turned on usb debugging & unknown sources
leave usb connected between tablet and pc
must have microsd card in the device (you may loose all the data on the card, read Chainfire thread)
split open chainfire's gingerbreak.apk with apktool
hex edited the gingerbrake.png change HONEY to HRI66 (see this link after reading the exploit)
added the updated su from xoom (thanks guys for coming to help me!)
recreated the apk with apktool
resigned with apkmanager
pushed to /data/local
launched apk install using oi file mananger entering the whole path to apk
set tablet in portrait mode and locked rotation
run the gingerbreak tool (it installs the root, updates SU and installed superuser.apk) waited about 4-5 tense minutes
confirmed root in terminal
install busybox
There are other method (which maybe easier) please check the 'How To Root An Acer Iconia A500' thread
Step by Step Root Guide [Long Method]
As with most instructions read completely before starting...
based off gingerbreak's instructions
usual rules apply, if you break then best efforts but in the end it's was up to you to click 'root'
Install Applications from market:
oi file manager
busybox installer (or Titaium Backup)
From your setting menu:
settings/applications
check Unknown Sources box
setting/Development
check USB Debugging
On the PC and Acer a500: Using ADB (I needed to download the usb driver from acer & sdk for adb):
(from the folder where the apk & adb is...)
connect your micro usb cable make sure usb debug comes up !
copy the apk to storage
On the Acer A500:
insert micro SD card if you have not done this yet
Rotate display to Portrait mode
Lock the screen its the little button under the VOL up/down (just incase)
Launch file manager
find and install <Gingerbreak>.apk (name will be different depending on version)
Install the application 'GingerBreak' (name will be different depending on version)
Return to apps menu
Find and launch 'Gingerbreak' [you must be in Portait or it will FC]
Select root device
Wait for it to reboot (2-10 mins, if you want monitor it with aLogcat or Logcat)
--- after reboot ---
Remove the rotate lock
Disconnect the usb cable
Uninstall Gingerbreak
Launch busybox app which will install busybox !
Install your root apps (my first are Titainum Backup and Cpu Master for me)
enjoy your Iconia a little bit more...
Regards and Best of Luck
Bugs? Troubleshooting?
Post any Bug for inital version
Issues
Hardcoded to HRI66
Features
Requires SD Card...
Why repost this method when the actual method is as simple as check debug, unknown sources, make sure sd is in slot, install app and run app?
Just asking. Thanks.
Reply
Probably for people like me that are new to rooting a device, detailed instructions can help others to understand and maximize success.
Placing the SD card in the slot was (for me) unclear per the original instructions, I just decided to try it since I was at a loss and it worked.
Details = Maximize Success & Minimize Failure
added new version of the Gingerbreak Mod, stops the FC if device is not portrait
monki-magic said:
added new version of the Gingerbreak Mod, stops the FC if device is not portrait
Click to expand...
Click to collapse
U.B.D.Man.....
a500 gingerbreak ??
I am trying to install gingerbreak 1.20. I am running android 3.2. it stays on the screen rooting this my taks a few minuter? I have let it run for hours and has not changed? Can anyone help me out
djbeach said:
I am trying to install gingerbreak 1.20. I am running android 3.2. it stays on the screen rooting this my taks a few minuter? I have let it run for hours and has not changed? Can anyone help me out
Click to expand...
Click to collapse
gingerbreak NOT WORKS on HC 3.2
HC 3.2
do you know of anyone coming out with a gingerbreak for honey comb 3.2?
djbeach said:
do you know of anyone coming out with a gingerbreak for honey comb 3.2?
Click to expand...
Click to collapse
I think no one for HC 3.2
You should revert to HC 3.0.1 and install a custom ROM HC 3.2 already rooted.
See other threads in this forum.
[Guide] All in one 'Namaste guide' to Bootloader unlocking, Rooting, Flashing & more.
So you got an Arc!!!! Congratulations on being an owner of this beauty with brains. It’s a great phone if you know how to make the most of it. Damn!!! That’s the problem. You don’t know what to do. Google led you to XDA Forums and you are lost in this techy - geeky world of Rooting, Modding and Unlocking. DON’T WORRY. Let’s go on an intellectual yet fun guide on WHAT TO DO WHEN YOU OWN A XPERIA ARC.
[Please push thanks and if possible donate to Lollylost100, Chainfire, kistigun, Androxyde, Bin4ry, constin, Blagus and many such genius’s at XDA without whom we may not be able to move even an inch with this guide].
Feel free to ask anything which you think is not clear to you, i'll be there to help. There is a thanks button on your screen waiting to be pressed & You can always donate to help me get a new phone .
Ques -What the hell is a bootloader?
According to Wikipedia – “When a computer (Your smartphone - Arc) is first powered on, it usually does not have an operating system in memory (ROM or RAM). The computer (phone) must execute a relatively small program stored in memory from which the operating system programs and data are loaded into RAM. The small program that starts this sequence of loading into RAM is known as a bootstrap loader, bootstrap or boot loader. This small boot loader program's only job is to load other data and programs which are then executed from RAM.”
Ques – Ok. So what is meant by unlocking the bootloader and why do I need it?
Every Android phone has a bootloader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer (Sony Ericsson – SE, in case of xperia arc) has their own version of bootloader specific for the hardware present in it’s environment. A bootloader is usually locked on an Android device because although it’s an open source OS, still the manufacturers (SE) want you to stick to their Android OS version specifically designed for the device. In order to apply this concept, SE lock the bootloader.
If you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone. [Source - [URL]http://www.addictivetips.com/[/URL]
Ques – Got it. But what on earth is a firmware and what is meant by installing a custom ROM (or whatever you call it)?
An operating system (OS) is a piece of software which provides environment for various applications (Yes, the ones you download and enjoy from Android market) to run. For instance, Windows 7/Vista/XP or Macintosh or Linux are nothing but OS’s. A firmware/ ROM is a term used for the operating systems designed for phones. A stock/generic firmware/ROM is an OS on your phone which is developed by Sony Ericsson and comes pre-loaded when you got your phone. A custom ROM is a modified firmware where modifications can vary from modifying the speed of firmware or making it look beautiful.
Ques – Ok. So quickly tell me how to unlock my Xperia Arc’s bootloader and install a beautiful Custom ROM.
Not so fast dear. I described a deal about bootloader and benefits of its unlocking but let’s get practical. There are disadvantages of unlocking the Xperia Arc’s bootloader.
1. Important – If you unlock your phone’s bootloader, you MAY void your warranty from Sony Ericsson.
2. You will loose the DRM keys present in your phone. DRM keys are (sort of) licence files which are required in order for SE’s custom developed apps like Track ID to work. In short you will loose Track ID and some other SE based apps.
3. You will not be able to update your phone by SE's official programs (SEUS and/or PC comapnion).
Ques - Ohh!! So this means that I should never unlock the bootloader of my ARC, what a waste of my smarty phone.
Looks like I’d scared you with this voiding the warranty stuff (sometimes I scare myself too, don’t worry...). We have so far discussed the disadvantages of unlocking the bootloader, let's look at some of the major advantages -
1. All the updates released by Sony Ericsson will be available to you within a few hours of their release irrespective of your country of purchase or country of usage of the phone.
2. You will be able to root your phone (read the questions below to know more about rooting) much faster than any other method available.
3. Few custom ROMs are in their final stages of testing. By unlocking the bootloader you will be able to run those ROMs on your Xperia Arc.
Ques – Hmm, so this means that once I unlock the bootloader of my Arc, I will never be able to run Track ID or update my phone using SEUS/PC companion.
Well, there is a catch. The catch is that you can Relock your bootloader anytime you want. All you need to do is to follow these steps –
1. Go to Blagus's post at http://forum.xda-developers.com/showthread.php?t=1134335 to download Xperia_Relock_Bootloader.ftf file.
2. Follow steps 2 to 7 of the question ("I am still not ready to unlock my bootloader. So guide me how to perform rooting on my locked Xperia Arc.") given below to flash the Xperia_Relock_bootloader.ftf file to your phone.
3. You should be on a relocked bootloader. To confirm, try to use repair function in pc companion or SEUS. If these official programs update/repair your phone, then you had successfully relocked your bootloader.
4. Thanks to itskapil for a video guide at [GUIDE] How To Re-lock Xperia Arc Boot Loader.
Ques – Woooo. Thank you for the information. But Vaibhav, if warranty gets void by unlocking the bootloader and we have a method of relocking the bootloader, then why are we worried about this?
You little genius. Look, I agree that you can relock the bootloader and unlock it as many times you want, but you should always keep in mind that –
1. Even if you will certainly revert back to your initially locked state and hence technically you are not voiding the warranty...,
2. still, you can’t get your DRM keys to work once they are gone .
So, in other words, you can relock your bootloader any number of times but you can’t get Track ID to ever work on your phone. So, if you don’t like Track ID or you can live with alternatives (Shazam works like a charm, why bother about Track ID?), unlocking the bootloader is a really good choice.
Ques – Who cares about Track ID or facebook ‘like button’, android market is full of alternatives. Can you please tell me how to unlock bootloader in little detail?
Sure. I will recommend you to follow this lollylost100’s awesome guide. There is a link to step by step video of unlocking the Arc by ItsKapil . Make sure you watch that too.
For those who got their phone by a carrier can't unlock their bootloader officially, by the above mentioned method. In that case, just follow any of these two guides -
1. Paid unlocking - Remote unlocking
2. Paid unlocking - Remote unlocking
Ques – Hmmm. Done unlocking the bootloader. But my gut feeling says this is not the end. Isn’t it vaibhavknockout?
Bingo. You are absolutely right. Now, rooting and modding and theming comes in picture. The real fun begins.
Ques – Can you brief me on rooting?
In tech world, you can access any file in two modes –
1. Either as a basic user who can just read the file but is not allowed to change it in any way, or
2. As an administrator/Root who can read, write and execute any file in the OS/firmware.
When you get a fresh copy of any OS (e.g. Windows, Mac, Linux etc.) or a firmware (e.g. Android 2.3.X aka Gingerbread on your phone), the OS treats you as a basic user. Rooting is a procedure which grants you the administrator/superuser/root/su permissions so that you can modify any file inside your Android OS. Afterall you should be the one to decide the ‘flavour’ of your gingerbread.
Ques – So this means that I can change system files by rooting. Big deal. What can I possibly do by changing the system files and can we discuss the disadvantages of rooting (and advantages – if any…).
Believe me rooting is a big deal. Here are THE things you can do if your phone is rooted –
1. You can remove bloatware. Bloatware are those crappy apps that comes pre – loaded inside your Xperia Arc (e.g. LetsGolf, Whatsapp, Timescape, postcard, playnow etc.) by SE or your carrier which can’t be uninstalled, which usually drains your battery most of the time and which make your phone slower and laggy.
2. You can get any SE official firmware. This means that if someone like me is having an Indian generic firmware and want to install a generic UK firmware, rooting will allow me to do so (totally officially via SEUS or PC companion). This also means that you can debrand your carrier locked phone to use sim free phone.
3. You can customize your statusbar, lockscreen, bootanimation, homescreen etc. if you are rooted.
Ques – Vaibhav I don’t want to unlock the bootloader (just don’t feel like) but I want to perform rooting on my Xperia Arc. Can I do that?
YES. You can do that. To summarize, you can have locked bootloader and still root your phone. The advantages of rooting is that you can mod your phone without worrying about unlocking the bootloader stuff. You can unroot your phone anytime you want. As far as disadvantages are concerned there is none.
Ques – WoW!!! So guide me how to perform rooting on Xperia Arc.
Note – It is always advised to back up your contacts and other data before trying out any of the following steps. Be ready to wipe your phone to get a clean better firmware. I repeat – IT IS ABSOLUTELY SAFE AND ADVANTAGEOUS TO ROOT YOUR PHONE.
There are two modes of rooting Xperia Arc depending upon whether your bootloader is locked or unlocked. Read next few questions for further details.
Ques – I am still not ready to unlock my bootloader. So guide me how to perform rooting on my locked Xperia Arc.
Don’t worry. XDA’s big brains have developed something called a FLASHTOOL. It will help you getting a rooted 2.3.4.
1. Go to Jozinek’s post on [ROM]Generic LT15i (Arc) 4.0.2.A.0.42 (1247-1041) (Android 2.3.4) and follow the link named ‘http://multiupload.com/xxxx’ to download official SE world firmware/ROM. Unzip the file and save the LT15i_4.0.2.A.0.42.ftf file in a folder.
2. Go to Androxyde’s post at http://forum.xda-developers.com/showthread.php?t=920746 and download the latest version (0.4.1.0) of flashtool.
3. Run the autoextractor in a folder.
4. Download LT15.rar file (attached to this post below) and copy "LT15.sin" to "loaders" folder in flashtool. You can skip this step safely.
5. Copy your “LT15i_4.0.2.A.0.42.ftf” in the "firmwares" folder.
6. Run X10Flashtool.exe (as administrator in case you are working on windows 7/Vista).
7. Follow steps in http://www.youtube.com/watch?v=Keo61Zffh5Q to flash the LT15i_4.0.2.A.0.42 firmware on your phone. The video asks you to download firmware and flashtool, keep in mind that you already did that in steps 1-6 above.
8. After flashing, restart phone and check your Android version, you will be on 2.3.4.
9. Now go to ‘settings’, ‘Applications’ and tap ‘Development’. Tap ‘Unknown sources’ and ‘USB debugging’ to tick on them.
10. Connect the phone (in running state) back to the computer in media transfer mode. Flashtool should detect your phone now. Press the root button on top left side of flashtool and wait(just a button tap and you are done) to root your phone on latest 2.3.4 firmware.
11. Similarly, install superuser and busybox via flashtool. The phone should now be running a rooted 2.3.4.
Ques – I have already unlocked the bootloader of my phone. How can I perform rooting on my Xperia Arc?
Congratulations. Now that you have unlocked the bootloader of your phone, you have opened a way for yourself into an awesomely wonderful world of modding your Xperia Arc. Before we move any further, let's review some techy-geeky concepts -
1. Partitions – Just like the human brain, a computer needs to store data for performing different functions. Again, a computer also has memory, similar to human brain. But unlike the human brain, a computer possesses two different sets of memories. One is relatively permanent and is called as ROM (Read only memory, should not be confused with android ROMs), the other is volatile and is referred to as RAM (Random access memory/ cache memory).
Our Xperia Arc (or any other smartphone for that matter – even iPhone ) also has two memory system. But unlike computers, smartphones have a single physical memory disk, since it is not feasible to have two different physical memory disks in a small portable device like our phone. To provide the two memory architecture, the single physical memory disk is PARTITIONED into two or more virtual disks. This is similar to the fact that although Asia (or any other continent) is a single continuous physical land surface (you need to ignore mountains and rivers ), virtual boundaries make different countries. These virtual memory disks are known as partitions.
2. Boot sector/boot partition (“/boot”)– When your phone (Arc) starts, the bootloader (you know what a bootloader is, right. What, you were sleeping!!) needs to start a boot program (known as a kernel) which further guides the rest of the system to start in sequence (the Sony Ericsson text that appears when you start your Arc is what you have as a kernel). This boot program is stored in a memory partition known as boot sector or boot partition.
3. Cache partition (“/cache”)– A cache partition (as discussed above) is a memory disk space which is volatile. This means that it stores programs temporarily onto it, until the program is executed. The moment a program is no longer needed, it is erased from cache and loaded back to a relatively permanent storage called system partition, where it stays (until user decides to erase it).
4. System partition (“/system”)– All the files and applications that are visible to you in your phone (including all the system files like settings, app drawer etc.) are stored on a disk partition known as system partition.
5. Data partition (“/data”)– Did you ever wondered as to why is it that when you save a setting or install an app, it remains as it is even when you turn off the phone? This happens because all of it is saved in the data partition of memory disk.
6. Recovery partition (“/recovery”)– Recovery is another boot program (kernel) that is added by a manufacture (Sony – Ericsson in our case) to perform restoration and damage control if something goes wrong in the system simply by booting into recovery and skipping the normal kernel boot. Recovery program is usually stored in a partition called recovery partition. Developers utilize this partition to boot their own custom recovery kernels to provide us much advanced functionalities like – Backup, Restore and Flashing to name few important ones. To read more about recoveries follow this.
7. Fastboot – Fastboot is a tool which is used to flash, erase, reboot or boot into a particular boot program (kernel). It is also used to unlock the bootloader. It is a part of Android debug bridge (ADB) supplied by google.
You must have downloaded and installed fastboot into a directory/folder when you had unlocked your bootloader. If you have an unlocked bootloader and you don't know how to install fastboot, watch this video by itskapil. You can download fastboot from a link given in lollylost100's guide.
If you are a MAC user and want to install fastboot follow this guide by im_bol2riz.
To root your phone, simply follow the previous question "I am still not ready to unlock my bootloader. So guide me how to perform rooting on my locked Xperia Arc." to root your unlocked ARC (Yes, the one click method is same for unlocked and locked bootloader phones!, beauty of flashtool!).
Alternatively, after you have downloaded and installed fastboot, just follow these steps to root your phone -
1. – Flash any desired stock ROM for Xperia Arc (download 2.3.4 update from link given in "1." of previous question - "I am still not ready to unlock my bootloader. So guide me how to perform rooting on my locked Xperia Arc.") using flashtool (read the question - "I am still not ready to unlock my bootloader. So guide me how to perform rooting on my locked Xperia Arc." to know how to flash a stock ROM using flashtool). This step is optional if you want to root your current stock ROM.
2. – Download attachments below titled recoveryARC.img and RootXperia.zip. Thanks to jlmcr87 and his post. Copy and paste the file recoveryARC.img to the fastboot folder (folder containing fastboot.exe). Also, transfer the file RootXperia.zip 'as it is' to your SD card.
3. - Open the fastboot folder. Right click on the folder background while pressing shift key on windows PC. Click "Open command window here".
4. - A black cmd window will open. Type in the following command - "fastboot.exe boot recoveryARC.img".
5. - Switch off your phone, connect to the USB cable while holding the menu button (rightmost of the three buttons on Arc). A blue led should light up (It is an indicator of entering in fastboot mode).
6. - Let the process run. Look at the cmd window. If it says the process is complete, remove the USB cable.
7. - On your phone, a menu should appear. This is Clockworkmod/ CWM recovery menu (more about this in later questions). Use volume down key to go to 'install zip from SD card' and enter by pressing camera button.
8. - Choose 'RootXperia.zip' where you've stored it on your SD card. Accept the prompt.
9. - Let the process run until it says that it installed the zip.
10. - Go back to the main menu by either pressing back button or entering into '+++Go Back+++'.
11. - Enter 'reboot system now'. When rebooted, you will have a rooted stock firmware.
Ques – Ok. So I am now rooted. Tell me how to remove bloatware from my phone.
Good. Now you are talking like a pro. Follow these steps to remove bloatware –
1. Download and install Root Explorer from android market. It’s a paid app worth buying.
2. Create backup folder on your memory card - Open Root Explorer, browse to the ‘sdcard’ directory. Press the button at the top so it is ‘Mounted as r/w’ (button will turn to Mount R/O). Create a backup folder on ‘sdcard’ (press menu button and tap “New Folder” icon). Name it anything you want, we have named ours ‘Backup’. This is the folder that we will move the unwanted apps to. By moving it to the memory card, the Android OS will not see them. The backup means that should anything go wrong you can easily move them back.
3. Go to the app directory - Using Root Explorer, browse to the app directory ‘system/app’. Here you will find a list of all of the apps installed, including all those unwanted ones too. The settings button brings up an option for ‘Multi-select’. This will be used to easily move multiple files.
4. Select apps to remove - The next job is to select which apps you want to remove. Go to Flo95's post [Tutorial] Remove Junk Apps + List (4.0.A.2.368, 4.0.1.A.0.283 & 4.0.2.A.0.42) and find the list of apps which are junk as per your phone's firmware version. You can also follow constin’s post at http://forum.xda-developers.com/showthread.php?t=1089470 and look under section "Safe to remove" for a list of apps which are safe to remove from xperia Arc.
5. Click on the settings button and hit ‘Multi-select’. Select all the apps listed under safe to remove files and then press ‘Move’.
6. Move unwanted apps to backup directory - Now using Root Explorer, browse to your backup folder on your memory card. Make sure the setting at the top is ‘Mounted as r/w’. Then click ‘Paste’. All of the chosen files will then be moved from ‘system/app’ to your memory card.
7. ENJOY YOUR EXTENDED BATTERY LIFE AND FASTER ARC!!!!
Ques – I am loving it……ok, guide me on what are the official SE firmwares and how can I change from one firmware to another?
Note - By following the procedure mentioned below, you can easily debrand your carrier sim locked phone, which means that you will remove any carrier logo, bloatware and other carrier imposed stuff (Except of course, the sim lock).
Well, SE releases its firmwares in different countries with slight differences in number of bloatwares. The one we used for rooting guide (in above mentioned question) is a global world firmware. For instance, for the Android 2.3.3 firmwares the UK o2 firmware is believed to contain least amount of bloatwares and is believed to be the fastest.
As mentioned in an earlier question on rooting, you can search for official firmwares in the XDA forums on Xperia Arc in the ROM.ftf format and flash them directly using Flashtool. A good place to start out is [INDEX]: Arc & Neo - full firmware guide! by Ambroos. Choose wisely.
If you don’t get your desired firmware, there is also a roundabout to this method for phone’s with locked bootloaders. Using Root Explorer (mentioned in previous question on removing bloatware), follow these steps –
1. Go to kistigun’s post at http://forum.xda-developers.com/showthread.php?t=1082368 and select your desired customization number (e.g. I chose United Kingdom Generic 1247-1073).
2. Open root explorer and go to \system and open the build.prop file in the text editor and change the following three lines:
*ro.product.name=LT15i_XXXX-XXXX
*ro.build.fingerprint=SEMC/LT15i_XXXX-XXXX/
*ro.semc.version.cust=XXXX-XXXX
Change the XXXX-XXXX into the customization number of your desired firmware (1247-1073 for my UK generic selection).
3. Press the menu button and save & exit. Reboot the phone.
4. If you are using pc companion, run it & on your computer and go to:
For windows XP users- C:\Documents and Settings\All Users\Application Data\Sony Ericsson\Update Engine\db\13740270\
Or For windows 7 users - C:\ProgramData\Sony Ericsson\Update Engine\db\13740270
5. And delete the blob_fs folder.
6. If you’re using SEUS, run it & on your computer go to:
C:\Program Files (x86)\Sony Ericsson\Update Service\db\13740270\
7. And delete the blob_fs folder.
8. Shut down your phone. Use SEUS for update or use the repair function in pc companion (You know how to use pc companion). Reboot and enjoy your new firmware.
[Source - [GUIDE]Easy way to brand/debrand or change firmware]
Ques – Hey, you said that if I unlock my bootloader, I would be able to try out different ROMs and stuff available for my Arc? How to do that?
Hold that for a minute. Let us first discuss some basic questions –
1. What is meant by flashing a kernel and recovery? – As previously explained, a kernel is a boot program that calls the rest of the system files in sequence when the phone starts. By default, when your phone starts, your bootloader looks for this program in boot partition. In a special case, bootloader can call a different special kernel known as recovery stored at a different place called recovery partition.
2. What the hell on earth is Clockworkmod? – Also known as clockwork and CWM, Clockworkmod recovery is one of the most widely used custom Android recoveries that is available for most mainstream Android devices (including our Xperia Arc). It allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery. ClockworkMod recovery has been developed by Koushik Dutta (also known as Koush) – the same guy who brought us the Android ROM Manager (I am proud to be an Indian ).
3. What is Cyanogenmod? – Also known as CM, Cyanogenmod is an aftermarket modification of android OS which includes all the basic functionalities of android (as released by Google) with many added functionalities like inbuilt theme chooser. Current release of Cyanogenmod is CM7 based on android 2.3.5.
4. What is FreeXperia? – Cyanogenmod is not available for all the android devices but a few. The Xperia range of handsets by Sony Ericsson is not supported officially by CM. FreeXperia or FXP in short is a joint venture started by a handful of genuises at XDA to provide CM7 to our Xperia devices.
5. What is meant by overclocking? – CPU of a computer or a smartphone processes a huge amount of information at very high rates. The rate of processing of information (speed of a computer or snappiness of a smartphone) is governed by its clock frequency. We all know that hardwares are fabricated with a maximum limit and a safe limit. Overclocking is to shoot up from a safer limit (clock frequency of CPU) to hardware's external maximum limit. It gives you faster hardware but mostly working more than it is designed to work, hence heating and damage risks. I personally don't like the idea of pushing hardwares too much.
6. What is this Doomkernel? – Doomkernel is a supersmart kernel which is designed for our Xperia Arc by doomlord (he is a member of XDA ). It has a lot of functionalities over stock kernel such as CWM recovery, overclocking, voltage change and many more.
Continued in third post
Wow, thank you for putting it together so nicely! Love you for that post. xD
I think I'll finally try to get root on my 2.3.3. over this weekend.
Continued from first post
Ques – If your lecture is over, may I know how to change ROMs on my Xperia Arc?
For locked bootloaders, you can’t use custom ROMs. Flashing stock ROMs by SE is already described in a previous question. For unlocked bootloaders, all you need to do is this –
1. – Flash any kernel having working recovery. I will recommend using the same kernel as provided in the thread of the custom ROM but Doomkernel works well for most of them. Download latest version of kernel.img from Doomlord’s post (http://forum.xda-developers.com/showthread.php?t=1172885) here and use fastboot as described in a previous question to flash kernel.img. Use this command – “fastboot.exe flash boot kernel.img”.
2. – If you want to flash FXP’s latest release of CM7, download the package from the original thread here. The package will contain a boot.img (recovery kernel) and a CM7.zip file. Flash boot.img using fastboot same as above.
3. – Custom ROMs are usually available as zip files. Just download the ROM.zip file and place it anywhere on your SD card.
4. – Turn off the phone and turn it on. While the first logo/text appears on screen, press down volume key several times until a recovery menu appears.
5. – Install update from SD card as described above in question – “I have already unlocked the bootloader of my phone. How can I perform rooting on my Xperia Arc?”. This time choose the ROM.zip that you have just placed on your SD card.
6. – Restart the phone when done and enjoy your new ROM.
7. – Remember, ideally you need to flash doomkernel or any other recovery kernel just once. Once it is there, you can directly go and download any ROM.zip from Xperia Arc’s development section and use same recovery to flash any ROM.
8. – Since most of the ROMs are in testing stages, it is recommended at the moment to use the specific instructions given in the respective threads of the ROMs.
Ques – Wow, look at that… I just installed a new FXP CM7 based ROM on my Arc and it looks awesome. I wish I could just take a complete backup of my current ROM before trying out something else?
You name it and we have it. CWM recovery also has a popular functionality of taking “Nandroid backups”. This means that if you backup your ROM in its current state, everything in your ROM (your apps, games levels, contacts and even messages) are saved in the form of a backup called Nandroid backup. You can take a backup of your stable favourite ROM, try out a newly released ROM and revert back anytime later to your previous ROM in EXACTLY the same state as it was at the time of backup. To take Nandroid backups, all you need to do is this –
1. – Flash a recovery kernel as explained in the question above.
2. – Go to ‘Backup and Restore’ in the recovery menu.
3. – Enter restore and accept when prompted.
4. – Once done, if you start your phone and check the SD card contents, your backup will be stored in CWM folder on your SD card.
To restore later, all you need to do is this –
1. – Enter the recovery menu.
2. – Enter ‘Backup and restore’, ‘restore’ and then choose the date when you have taken a backup.
3. – Restart when finished.
To be continued
I have 3.0.1.A.0.145 on my Arc
Is it ok to follow kistiguns guide even with 3.0.1.A.0.145?
regards
A space between sentences would make it much easier to read, like where you've numbered certain points.
Sent from my LT15i using XDA App
XperienceD said:
A space between sentences would make it much easier to read, like where you've numbered certain points.
Click to expand...
Click to collapse
Done.....thanks for the suggestion XperienceD.
hasse_e said:
I have 3.0.1.A.0.145 on my Arc
Is it ok to follow kistiguns guide even with 3.0.1.A.0.145?
regards
Click to expand...
Click to collapse
Gingerbreak used a loophole in gingerbread 2.3 to gain root access. Google removed the security loophole in android 2.3.4 while smart-asses at SE incorporated that in 2.3.3 update of Xperia Arc.
So, currently there is no straight way to directly root Android 2.3.3. Hence it is advised at the moment to flash back to 2.3.2 (using flashtool as mentioned in the guide above) and then root the phone. After that just update your phone OTA (over the air - again as mentioned in the Namaste guide above) to retain your root access with 2.3.3.
Its easy, just try it out and feel free to ask for any further help.
vaibhavknockout said:
2. ... Also, once you’ve unlocked your Arc’s bootloader, there is no way in hell you can lock it back.
Click to expand...
Click to collapse
Things are moving faster than your guide
http://forum.xda-developers.com/showthread.php?t=1134335
hush66 said:
Things are moving faster than your guide
http://forum.xda-developers.com/showthread.php?t=1134335
Click to expand...
Click to collapse
Lolz.....Totally agree with you, things here at XDA are unpredictable.....So finally we got a bootloader relocking method.....great news. Updated the guide with the same.
Thank you for the amendment.
vaibhavknockout said:
Gingerbreak used a loophole in gingerbread 2.3 to gain root access. Google removed the security loophole in android 2.3.4 while smart-asses at SE incorporated that in 2.3.3 update of Xperia Arc.
So, currently there is no straight way to directly root Android 2.3.3. Hence it is advised at the moment to flash back to 2.3.2 (using flashtool as mentioned in the guide above) and then root the phone. After that just update your phone OTA (over the air - again as mentioned in the Namaste guide above) to retain your root access with 2.3.3.
Its easy, just try it out and feel free to ask for any further help.
Click to expand...
Click to collapse
I was rooted in 2.3.2, but updated with Companion to 2.3.3
I will give it a try as you suggest
Thanx
vaibhavknockout said:
Done.....thanks for the suggestion XperienceD.
Click to expand...
Click to collapse
You're welcome, much better.
Wow man you are awesome.... Thanks....
Akhir indian hi indian ki madad kar sakta hai.....
Bhambya said:
Wow man you are awesome.... Thanks....
Akhir indian hi indian ki madad kar sakta hai.....
Click to expand...
Click to collapse
Sahi kaha dost......and u r always welcome.
dude i triead the superoneclick step..my FW is uk and flash it back to 184 uk and use super1clik for rooting,which one should i should use for the exploit psneuter or gingerbreak,,,after i did that OTA the phone but still not yet rooted what went wrong?what am i missing?
elnitrox said:
dude i triead the superoneclick step..my FW is uk and flash it back to 184 uk and use super1clik for rooting,which one should i should use for the exploit psneuter or gingerbreak,,,after i did that OTA the phone but still not yet rooted what went wrong?what am i missing?
Click to expand...
Click to collapse
Huh? You should be using GingerBreak and not SuperOneClick.
Yup ill be doing it tonight..hope things will go smoothly
elnitrox said:
dude i triead the superoneclick step..my FW is uk and flash it back to 184 uk and use super1clik for rooting,which one should i should use for the exploit psneuter or gingerbreak,,,after i did that OTA the phone but still not yet rooted what went wrong?what am i missing?
Click to expand...
Click to collapse
I am not sure whether superoneclick works for this exploit. What you need to do is to flash back to 184 UK, root using gingerbreak (as is also pointed out already by hush66) and then perform OTA. That's what is confirmed to work.
See you on rooted 2.3.3.
thank you my friend =) really nice topic =)
Hi vaibhavknockout,
i've 2.3.3, i used your guide to downgrade to 2.3.2 using flashtool then updated again using WiFi, but still i'm unable to remove system components! like the chinese keyboard!!
what's wrong? please help...
use titanium backup..backup and uninstall..
The Xperia X10 Rooting Toolkit also works flawlessy with the Samsung Galaxy Note and gives you full root access (tested by myself)
Just follow the instructions to root/unroot the device here
http://forum.xda-developers.com/showthread.php?t=1319653
Confirmed working!
Since the ice cream sandwich is not out yet, what is the advantage of rooting it now?
clubtech said:
Confirmed working!
Click to expand...
Click to collapse
You are using AT&T and have the note,from wish retailer you buy yours?
please excuse my trivial question, but rooting the Note with the instructions you provided is it possible to install any kind of apk file?
finanziere said:
please excuse my trivial question, but rooting the Note with the instructions you provided is it possible to install any kind of apk file?
Click to expand...
Click to collapse
You don't need to root to install apks.
wonsanim said:
You are using AT&T and have the note,from wish retailer you buy yours?
Click to expand...
Click to collapse
eBay...
10chars
clubtech said:
eBay...
10chars
Click to expand...
Click to collapse
Thanks
is a little expencive on ebay
schölli said:
The Xperia X10 Rooting Toolkit also works flawlessy with the Samsung Galaxy Note and gives you full root access (tested by myself)
Just follow the instructions to root/unroot the device here
http://forum.xda-developers.com/showthread.php?t=1319653
Click to expand...
Click to collapse
could somebody tell me if this root method increase the binary counter??
thanks..
kersh said:
You don't need to root to install apks.
Click to expand...
Click to collapse
thanks, but I mean the non official apps or those that are cracked.
is it possible to install these without rooting the device?
m_adnan said:
could somebody tell me if this root method increase the binary counter??
thanks..
Click to expand...
Click to collapse
It won't
Sent from my GT-N7000 using xda premium
Worked for me! It was even easier than rooting an HTC Evo 4G. This thread, or at least the thread referenced in the first post, should be stickied in the Development sub-forum.
I am a Noob and I can Root my Note!
I had experience rooting a Milestone 2 with SuperOneClick and an unbranded Android Tablet with Z4Root. (Thanks to developers of these!)
Unfortunately, both these methods did not work on the Galaxy Note so I came here and found this thread.
Unfortunately, ADB drivers was an issue with the zergRush Exploit on first run. The easiest way to get around this is to install PDANet on Windows and have it install the drivers for you. No need to complete the whole installation, just watch when it's finished installing USB drivers and then when prompted to continue, just cancel. Then re-run the zergRush Exploit and it should do its magic (Again thanks to the developers who work on these!)
While I'm able to freeze some apps with ROM Toolbox, I'm unable to change boot animation or the battery icon. Would appreciate if anyone could help with this!
Rooting hav no relation to install official/crckd version of apk.
Rooting needed for those application which are needed to access your system data e.g backup etc
when you need to install these kinds of application (weather off/unoff) you needs Root.
The optional unrooting package works also perfectly (just for info)...
i have sent back my Galaxy Note to amazon just to wait for the white version of the Note.
This method won't increase your binary counter, so root and unroot it as often as you like
Never either had any problem at all after rooting it, so this method is also stable and won't crash your device in any way or crash any applications...
Root confirmed working here, superuser.apk doesn't have permissions set properly but still works, easy to fix, updates fine from market.
Awesome - confirmed working. This needs to be stickied... other websites are promoting netchips CWN kernel method instead of this MUCH simplier way.
For you noobs with a clean system (that means me!), get the following files:
Note I run a 64 bit windows box, get the 32 bit variants if necessary.
You need:
1) Latest version of Kies
www.samsung.com/ca/kies/index.html
download file for me was: Kies_2.0.3.11082_152_4.exe
2) Java:
www.oracle.com/technetwork/java/javase/downloads/index.html
Click on jdk and download. File for me: jdk-7u1-windows-x64.exe
3) android sdk:
developer.android.com/sdk/index.html
My file was: installer_r15-windows.exe
4) zergrush root script
http://forum.xda-developers.com/showthread.php?t=1312859
grab the zip file in that page i.e.
DooMLoRD_v1_UNROOTING.zip
and unzip it to your windows box.
Install 1, 2, 3 in that order.
Find the SDK Manager program in your sdk install directory, double click it, and download/update 'Android SDK Platform Tools'.
Note you can't run the sdk manager program from the command prompt, or it'll complain that directories are being locked.
Now follow the instructions on the zergrush page, i.e. do the 'before you begin' stuff.
Go to the directory where you unzipped the doomlord zip file, run the runme script from a command prompt,and that's it.
To test, download terminal monitor, run it, and do a 'su' then 'id' and see if it says you are root or not.
Good luck!
- Frank
sir can i ask a question?
after i install the cwm and i will make a nandroid back up before rooting the phone.
if i restore the unrooted back up. Will i go back to became un root again and go back to out of the box state?
will this work with the Korean version of the Note? thanks in advance.
Is there a possibility for getting root and CWM recovery on this device? i have achieved to get into E3 Recovery, Bootloader mode, and some other test screen.. i posted pics and a description on how to do it. i would really like to get root on this device, i can can help anyone in all ways possible.. p.m. me.
Link to video is in a text file..
I wait for S2109 root too...
I want buy this devise, but without root its difficult use it...
I wait for S2109 root too...
you can find on support.lenovo.com Open Source Code:
fih_uboot_0618.tar.gz 10.7MB
kernel_s2109.tar 445MB
how to obtain these files
Hey how do I find the files u are talking about? Like a link?
nevermind got em
Maybe someone can start developing on the uboot.bin and the system image to obtain some root access
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
WOO!!!
polakko said:
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
Click to expand...
Click to collapse
Awesome! thank you so much! the CWM root worked perfectly. However, the driver from the SDK folder wasn't recognized so I just used the Lenovo ADB driver that came shipped with the device and that worked just fine. Took me about 20 minutes to complete - that includes resolving the driver issue.
Niiice
OK, so the CWM method worked great on my S2109. I had the 4.0.4 update.
Two things:
1) The Lenovo drivers are at Lenovo's support website. Just search for "adb interface driver"
2) In step 3 of el_fuego's instructions, he says "add following to both the [Google.NTx86] and [Google.NTamd64] sections:", add this instead:
Code:
;Lenovo S2109
%SingleBootLoaderInterface% = USB_Install, USB\VID_17EF&PID_748B&REV_0100
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&REV_0216&MI_02
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_748C&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_74CC&REV_0216
How easy is this root? I'm not really familiar with the process and don't want to brick the device, which I'm concerned about as I don't quite understand the directions.
Lenovo s2109 rooted
@Jittery Jim: Rooting following polakko's (or el_fuego's) guide is straightforward. I did it yesterday and found no problems, you should only consider luckyjay's post regarding the adb driver.
@all: As I imply above the rooting process was free of problems and I have successfully installed CWM. However, after rooting I've run into some other problems:
First:
I rooted before performing a Software update (i.e. I still have the original version 4.0.3). I was planning to make a backup of the system after CWM installation and then update to 4.0.4.
When I try to backup the system using CWM everything works fine until the step "Backing up data..." I get the following messages:
- No /sdcard/.android_secure found. Skipping backup of applications on external storage.
- Backing up cache...
- No sd-ext found. Skipping backup of sd-ext.
- Generating md5 sum...
- Backup complete!
After backing up, I find in the internal sd card 4 files (in total 500K) and a directory called "blobs" with several subdirectories. In total about 2000 files. Is that the backup?
Furthermore, when I try to update to 4.0.4 using CWM, I get the following:
- Finding update package...
- Opening update package...
- Installing update...
- Mount partition
- Verifying current system...
- assert failed: apply_patch_check("/system/app/Launcher2.apk", .....
- E:Error in /sdcard/update.zip
- (Status 7)
- Installation aborted.
If I try to update from the normal system (i.e. outside CWM), CWM stops the update upon reboot.
Any ideas of how to update to 4.0.4 after CWM has been installed?
Second:
I have installed Super Manager from the market. When I try to enable ROOT, I get a message telling that ROOT functions are nor supported in my device. As it could be expected, Superuser does not inform that there is an app trying to get root priviliges, and Super Manager does not appear listed in the superuser's app list.
Third:
It appears that in newer Android builds, it is not possible for third party apps (apps that were not preloaded on the device, but you manually installed or downloaded from Android Market / Google Play) to gain write access to the external SD card. This was not an issue on Android 2.x but it became a problem on Android 3.x.
The implications of this (at least in my cse) is that I can not create folders, copy files or move apps to the external sd card. That even happens with the preinstalled ES Explorer. The solution to this problem is easy if root access is available. One just needs to add the line <group gid="media_rw" /> within the WRITE_EXTERNAL_STORAGE section of the file /system/etc/permissions/platform.xml.
I have pulled the file platform.xml with adb and updated it accordingly. However, I can not push it back because the directory /system/etc/permissions is read only. Any ideas of how to circumvent this problem?
Cheers,
Pisuke
pisuke2012 said:
@Jittery Jim: Rooting following polakko's (or el_fuego's) guide is straightforward. I did it yesterday and found no problems, you should only consider luckyjay's post regarding the adb driver.
Click to expand...
Click to collapse
Thanks, I'll see about giving it a shot.
The main reason I am interested is I would like to install a mod of Jelly Bean on the thing, but now I am not sure there is a build that the tablet will support. Anyone know?
Jittery Jim said:
Thanks, I'll see about giving it a shot.
The main reason I am interested is I would like to install a mod of Jelly Bean on the thing, but now I am not sure there is a build that the tablet will support. Anyone know?
Click to expand...
Click to collapse
Well...Rooting seemed to go ok, but I got a little too ambitious and attempted to install a JB build that turns out wouldn't work. So I had to restore to factory as CWM wouldn't load my recent back-up. Not sure if I now need to re-root or not.
If there is no JB that will work on this I really have no point in rooting, I guess.
Jittery Jim said:
Well...Rooting seemed to go ok, but I got a little too ambitious and attempted to install a JB build that turns out wouldn't work. So I had to restore to factory as CWM wouldn't load my recent back-up. Not sure if I now need to re-root or not.
If there is no JB that will work on this I really have no point in rooting, I guess.
Click to expand...
Click to collapse
Well, one of the points of rooting would be being able to write the external SD card with apps which are not preinstalled. Or even move apps from internal to external SD card. The problem is that you need to modify the file platforms.xml (see my post above). Unfortunately, I haven't manage to do so yet. I can not remount the system directory with write permission.
Did the tab with JB boot at all? or you had to restore factory defaults with CWM?
Did you update to 4.0.4 before rooting?
Where did you found the JB mod? is there a project porting JB to the Medion s9215/ Lenovo S2109?
Cheers,
Pisuke
pisuke2012 said:
Well, one of the points of rooting would be being able to write the external SD card with apps which are not preinstalled. Or even move apps from internal to external SD card. The problem is that you need to modify the file platforms.xml (see my post above). Unfortunately, I haven't manage to do so yet. I can not remount the system directory with write permission.
Did the tab with JB boot at all? or you had to restore factory defaults with CWM?
Did you update to 4.0.4 before rooting?
Where did you found the JB mod? is there a project porting JB to the Medion s9215/ Lenovo S2109?
Cheers,
Pisuke
Click to expand...
Click to collapse
I was/am on 4.0.4 and was there before attempting root. Despite following the directions a root checker app continues to tell me I do not have root access.
The JB mod was a mistake on my part, not paying attention I grabbed one that was built for the Kindle Fire. I could not get it to install at all; not sure now if it was due to the mod or due to actually not having root.
Bricked my s2109
Jittery Jim said:
I was/am on 4.0.4 and was there before attempting root. Despite following the directions a root checker app continues to tell me I do not have root access.
The JB mod was a mistake on my part, not paying attention I grabbed one that was built for the Kindle Fire. I could not get it to install at all; not sure now if it was due to the mod or due to actually not having root.
Click to expand...
Click to collapse
Well, me like the previous people and Jittery Jim above, being too ambitius after rooting s2109 tried JB customs rom's. I did try to flash JB because I have installe CWM V.6.0.1.0 and did make a back up. I used that back-up to restore my ideatab s2109 and it worked fine!
Now after trying to flash JB, which failed :crying:, I can not make a succesfull nandroid back up using CWM . I tried advanced restore and I can restore succesfully : boot , system, cashe, sd-ext, but I can not restore data.
Now my S2109 just boot loop :crying:
Also, I did try the factory reset and it is not working. The same result as boot loop...
Any help available?:angel:
Jeje I have a reboot-loop too.
I've installed CWM and gained root access with this useful guide.
However, recently the s2109a tablet showed me a message about "Encryption Unsuccessful", and with a button to do a factory reset. The factory reset process fails everytime it starts.
I've read some guides regarding this problem, and in all of them mentions that I need the latest build of ICS for my device. Where can I find that build for the IdeaTab s2109? Or maybe we need to compile our own ICS?
At least CWM works, but I don't have a backup :S. Any help, too? Thank you in advance.
--
Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
luckyjay said:
OK, so the CWM method worked great on my S2109. I had the 4.0.4 update.
Two things:
1) The Lenovo drivers are at Lenovo's support website. Just search for "adb interface driver"
Click to expand...
Click to collapse
All I can find is the adb interface driver for the thinkpad tablet, is that the same as the ideapad?
Also, I downloaded the SDK tools but there wasn't an option for Android 4.04 , just 4.0 (API 14) and 4.03 (API 15). Will it go ahead and install the revision for 4.04? (I assume that I'm supposed to install the SDK tools on my Windows 7 Pro 64bit device, though the instructions just say to download them.)
Thanks.
---------- Post added at 02:55 AM ---------- Previous post was at 02:05 AM ----------
polakko said:
Hi, I own Medion Lifetab S9512, which is a branded version of the Lenovo S2109. I am not sure what Android version is the S2109 shipped with. If it is 4.0.3 you can root it using the method from http://forum.xda-developers.com/showthread.php?t=1439429, as the method is confirmed to work with S9512. The other possibility, which works also for 4.0.4 version is to use CWM recovery. I have compiled a provisional version for S9512 and it should work also for S2109. Installation instructions and the download links are available at German site (don't worry, my posts are in English, posted under the nick of el_fuego ): http://www.android-hilfe.de/medion-lifetab-s9512-forum/278439-clockworkmod.html
Click to expand...
Click to collapse
I downloaded the Android-SDK that was on their site and installed it, but I'll be darned if I can find the files that your instructions say to modify. There's no such directory anywhere on my system. I finally used the exe to install SDK tools thinking that would place the files in the appropriate place but there aren't any. Perhaps the instructions are for downloading the German version? Could you provide a link to the appropriate download site?
Update: I have now downloaded and installed the ADT package and have run the SDK installation standalone (not sure why I need to do both of these steps, but what the heck). I found the correct inf file and did the modifications. However, I did get an error when installing the adb driver so assume I have to install a different fdriver. I have a win7Pro x64 box and am trying to root an S2109 with Android 4.04 installed. I've set the developer tools to enable debugging mode when connected to usb. But is there another adb driver I should download? Is there a driver located on the device itself that might be more appropriate? Again, couldn't find a lenovo s2109 tabet driver, just the thinkpad tablet driver, and it's files don't look right.
Update2: Took a few educated guesses and it worked! I installed the thinkpad tablet adb files after modifying them, by just overwriting the files that were already there. Worked perfectly when it came time to define the drivers and after that it even identified the right device name (rather than Blaze). The rest of it went pretty smoothly. Thanks for updating the instructions on the German site, that was helpful.
Anyone Making progress with CM on S2109?
Or happen to know where there is an active forum discussing the S2109. I also have an HP touchpad running CM9 and it performs much better than my 2109. I'd really love to get CM working on the 2109.
Did this get uploaded?
Otamay said:
Jeje I have a reboot-loop too.
I've installed CWM and gained root access with this useful guide.
However, recently the s2109a tablet showed me a message about "Encryption Unsuccessful", and with a button to do a factory reset. The factory reset process fails everytime it starts.
I've read some guides regarding this problem, and in all of them mentions that I need the latest build of ICS for my device. Where can I find that build for the IdeaTab s2109? Or maybe we need to compile our own ICS?
At least CWM works, but I don't have a backup :S. Any help, too? Thank you in advance.
--
Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
Click to expand...
Click to collapse
I'm needing a clean copy of this. I bought a display unit that was monkeyed with and the rom is corrupt on it.
If you would be willing to share it with me please contact me at [email protected].
Thanks.
Has there been any work on getting a Jelly Bean Rom for this tablet? Would be nice if we could get CM10.2.
I am having the "Encryption Unsuccessful" message and cannot break through to a solution. I saw the post above where the user seems to have gotten past the error by formatting the data partition via ADB. Can someone tell me how that was done exactly? I am getting a device not found error when I try to use ADB (from the screen entitled (Encryption Unsuccessful) and I cannot for the of me (or google) figure out how to issue the mke2fs and tune2fs commands!
Thanks to anyone who can help!!!
<<<Nevermind, I solved the problem.
The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.
In short I will upload my IdeaTab s2109a /system and NANDROID backup.
Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
@HvdW Please check your PMs
Also, there is some inaccuracies in your advice and statements in the above guide.
Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.
SkyHigh76 said:
Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.
Click to expand...
Click to collapse
Yes you do. Once you unlock the bootloader DRM functionality is gone. So on a stock ROM with unlocked bootlader you will need the DRM fix in order to fix the DRM functionality. If you use a custom kernel with the DRM fix already incorporated into it then you do not need to add it again as you are already using it. In either case, it is needed though...
@HvdW
I tidied up your OP. The missing step 2 is down to you. The original posts did not have a step 2, it went from step 1 to step 3.
Nice, I will try this early January, after Christmas
Thank You!
HvdW said:
Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thank you! Excellent step by step baby guide. However <b><i>do</b></i> wish to point out to future people unlocking their bootloader that it is HIGHLY essential that you backup your TA before unlocking the bootloader.
What i did is: unlocked bootloader before i ever sow this post, installed custom stock based rom, red this post, backuped DRM, and DRM found and successfully backuped intact just like it was before unlocking on Z3Compact
OpenGapps 8.0 not working, you need 8.1.0 gapps.
Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?
vinc9876 said:
Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?
Click to expand...
Click to collapse
If u see blue led u are on fastboot.
Try adb fastboot comand after mast see same help comand, now try fastboot device.
Don't worry, take,it easy. GL
Maybe u are flashtool open, close flashtool.
yo7fb said:
Try adb fastboot comand after mast see same help comand.
Click to expand...
Click to collapse
I don't think I understand what you mean.
I think the bootloader is stuck somehow. Maybe something to do with the .291 ROM being incompatible with the bootloader? I'm pretty sure I should see the fastboot screen like so:
EDIT: Got it working!
Had to reinstall adb/fastboot drivers from the flashtool installation.
HvdW said:
Introduction
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.[/hide]
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.
Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.
jhalvico said:
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.
Click to expand...
Click to collapse
Hello.
I'm sadly in same situation as you are (or was). Did everything according to guide but it is 1.5 houre since it started booting.
Do any of you guys have tip what to do?
Btw: thanks for this guide
Edit:
So i managed to get it working by following steps from the Oreo rom page.
the battery on which version lives more?
probably google dialer?
uilino said:
Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.
Click to expand...
Click to collapse
Did you install google dialer? if so, go to
Settings--> Apps¬ifications -->Advanced-->Default apps --> Phone app --> Select "Phone"
Error 7/6 when I try to install ZIP File via TWRP
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?
Hovenzius said:
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?
Click to expand...
Click to collapse
hi, i have got the same problem and i found this solution : https://forum.xda-developers.com/showthread.php?t=2522762
Restore with Xperia Companion
HvdW said:
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Click to expand...
Click to collapse
First thank you for your great post!
I try to restore my data after a successful upgrade and after having saved them with Xperia Companion but I can't succeed to make it detect my phone, so I can't use restore function... Do you know how can I achieve that? Is there some apk to install on the phone in order to make Xperia Companion recognize my phone and make restore function work?
Thanks!
Hi guys,
I have successfully followed this step-by-step:
How-to: root, keep and backup DRM keys, etc. [KitKat/Lollipops/Marshmallow/etc.]
and I also have unlocked the BL.
So, my Z3c has
- DualRecovery installed
(Z3C-lockeddualrecoveryX.Y.Z-RELEASE.installer.zip)
- superSU
- pre-rooted D5803 23.5.A.1.291
- backed-up TA
- unlocked BL
My question:
Do I still need to install Twrp or could I just boot into DualRecovery and flash CARBON-CR-6.1 + gaps from internal storage of phone?
Btw, if it isn't already blatantly obvious, I'm a total noob and without all the fine tutorials wouldn’t have a clue what I was doing.
Thanks for reading.