Database Users

[Guide] All in one 'Namaste guide' to Bootloader unlocking, Rooting, Flashing & more.

[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..

[Guide] Step by Step from Stock N910V 6.0.1 to hsbadr's CyanogenMod 13.0

Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
IMPORTANT: Read the ENTIRE instructions set before starting, make sure you know what you are getting into. I have been as straight forward as possible with my instructions to assist noobs with the procedure.
Mission Statement
The purpose of this post is to combine the following 4 guides, in an easy to read manner to help people get from a stock Note 4 Version running 6.0.1 to a fully rooted Note 4 running CM13.0
Guides Referenced and Summarized:
[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V] http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
(no title, sub post #1403, describes going from CPD1 to Jasmine with CPF3 and Firmware/Kernel Patch) http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
[ROM] [6.0.1] [UNOFFICIAL] CyanogenMod 13.0 [Jul 24, 2016] http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I will use large chunks from some of these guides, skip some parts not necessary and/or extrapolate/modify on the instructions given within.
Thankx & Achnologments
Main Contributors (I plagiarized, quoted, or sourced)
Robots_Never_Die
hsbadr
Tech Support
BickNasty
Feel like I missed you, it wasn't intentional....PM me and I'll consider adding you, if I feel you actually contributed in some way or I copied your work.
Satisfied Customers (Did my method work for you? Post a reply and let us know, I'll add you to the list)
jwp1299 - 1 hour
Viper-Link
keviinese - 1.5 hours
pfcland - 1.5 hours
Required Apps (Google Play) All Free
Search for and install these apps
eMMC Brickbug Check (free)
Required Downloads (note on version numbers: version numbers I specify are ones available at the time I wrote this guide. For most tool grab the newest version, such as Odin/ADB)
NOTICE Total size of Downloads is approximately 7 GB, some of the links may be slow! Time required may vary due to your network speeds, and luck with speeds from file hosts. (expect several hours)
ADB – minimal_adb_fastboot_v1.4.0_setup.exe
Odin - newest version (3.12.3 at time of writing)
Kingroot - Grab latest stable version, only grab NewKingroot(XXXXX).apk
Samsung USB drivers (windows) - newest version
Bootloader Unlock - samsung_unlock_n4-fix
TWRP - twrp-3.0.2-0-trltevzw.tar.md5
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5
N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)
JasmineROM_v7.0_N910VVRU2CPF3.7z
N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z
Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)
UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)
Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)
XPosed is OPTIONAL, but there are a lot of rooted apps that use the XPosed framework to get more control over your phone. Such as hiding mock locations for example.
NOTE: Internet is REQUIRED for KingRoot to function (grants temporary root, so ADP commands can be executed to unlock bootloader), at one point WiFi will NOT function but internet is still required. So a valid SIM with internet is required (Verizon will definitely work, others might[/] work)
NOTE: The entire installation will take an estimated 1-2 hours. (Not including time spent downloading) All steps are MANDATORY, do not SKIP anything....You've been warned
Install eMMC Brickbug Check (free) on your phone, and RUN IT. Your CID MUST start with 15. If it doesn't I can't help you, and this guide is not for you.
Install the Samsung USB drivers on your windows PC
Backup your phone, if you don't know how.....google it...And learn how, you will want to backup frequently. Every time you get to a point you can boot up into Android, backup...it's safer for you...I will not remind you again, this is on your head.
Disable Encryption on your phone, both the SD card and Device
Disable Samsung Phone Lockout. YOU MUST DO THIS OR ELSE!!!! (Settings > Security > Reactivation Lock)
Do 2 factory resets on your phone, one after another (hold volume up, home button, power when starting to enter recovery mode where you can reset phone). Not required but if you don't, you'll spend an extra hour or two doing this because Kingroot will crash/fail more often.
Boot up your phone in Download Mode (hold volume down, home button, power)
Open Odin3, Click the AP button and select the file N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5, once it checks it, goto options and make sure the Re-Partition is NOT selected. Now click start to flash and downgrade to Android 5.1.1.
Turn on your phone, and let it boot up.
Skip everything possible when setting up your phone. Don't even put in a google account, not necessary
Goto Setings and set the following
Settings > Security > Reactivation Lock = Disabled (EXTREMELY IMPORTANT, VERIFY)
Settings > Security > Unkown Sources = Enabled
Settings > Developer Options > USB debugging = Enabled
Developer options are unlocked by going to Settings > About Phone. Find "Build Number", and start clicking it till you get a message that Developer Options have been unlocked (about 10 clicks I believe, never counted).
Settings > Developer Options > Verify App via USB = Enabled (should be by default, CHECK)
Settings > Lock Screen = None
Settings > Display > Turn off Display = 10 Minutes
Plug your phone into your computer via USB, copy the NewKingroot****.apk to your download directory (samsung-sm-N910V\Phone\Download)
Install ADB onto your Windows PC. Select an easy directory such as c:\ADB
Copy the following file directly into the ADB directory
samsung_unlock_n4-fix
Open up command line interface. Hold windows key & press R key for run, type in "cmd" press enter. Will open a terminal window for you. Type the following commands:
cd\
cd adb (or whatever you named your directory where you installed ADB)
adb devices
This should return a list of devices you have connected, something like:
Code:
List of devices attached
SerialNum device
If no devices are displayed, check you have the Samsung USB drivers installed properly.
Type the following command
adb push samsung_unlock_n4-fix /data/local/tmp/
Got an error? check your spelling (or copy/paste from me), check you put the file into the ADB directory (not just a link), your phone must be on and screen not locked and check you have usb debugging enabled.
BTW: Do NOT CLOSE the window unless I instruct you to!
Install Kingroot on your phone, which you previously moved into your downloads folder, you can find it via My Files app that comes with phone.
Now run KingRoot. Flip down to the bottom and click "Try It", it will run some quick test then give you a button to try to root your phone.
Wait...Wait...Do not worry if your phone restarts, it will go back into KingRoot automatically on reboot. Just sit back and wait, it may fail multiple times and you may have to re-run Kingroot. Just keep trying . Once it succeeds you must do the following IMMEDIATELY AND AS FAST AS POSSIBLE. Kingroot is HIGHLY UNSTABLE.
On the windows PC, back in the command window you left open. Start Typing.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
After the last command it may prompt you to type yes, do so immediately. it won't write on the screen but type yes anyway for it to continue. Once it's done it should automatically start to reboot your phone. Unplug it and pull the battery, wait 5 seconds, put battery back in and plug the phone back in.
This was the initial setup for unlocking your bootloader, you now have to run it AGAIN so turn your phone back on. Repeat steps 22-24, after the 2nd time PULL OUT YOUR SD CARD BEFORE TURNING ON YOUR PHONE
Congratulations you now have an unlocked bootloader, you can close the command window on your PC.
The SD card has a restore point for your phone prior to removing your bootlock. Save it if you want, or plug into your phone and format the 18mb partition you are able to. You must format it on a PC before you can use it again in a phone!!!! Will shut your phone off immediately if you put the SD in without formatting that 18mb partition.
Now reboot your phone into download mode (hold volume down, home and power buttons when turning on)
Open Odin App on your PC, Click the "AP" button and select the file twrp-3.0.2-0-trltevzw.tar.md5 (which you downloaded earlier). Once it does it's check, verify that re-partition is NOT selected in options. Now click start to flash twrp bootloader.
Your phone will restart, re-enter download mode. If you missed it pull cable/battery and try again.
Now extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin, same as you did with twrp. VERIFY THAT RE-PARTITION IS NOT SELECTED IN OPTIONS.
Boot up in recovery mode (hold volume up, home and power when turning on) (note: no longer TWRP since you flashed firmware, will look different again)
"Wipe data/factory reset ", then reboot your phone.
Now repeat steps 9-12 (NewKingRoot should still be in your downloads, but verify anyway) (NOTICE: wifi will NOT work with the CPD1 firmware, but Verizon internet should in case you need internet for some reason, wifi will restore later in guide - Other internet from other providers MIGHT work with proper APN settings)
Install a clean SD card into the phone.
Now repeat steps 15-25. This time you should only need to run the samsung_unlock_n4-fix file once to break your boot. This is what it typically says on successful bootloader unlock: (if you got this message, pull the battery, cable and SD card.)
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceeding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Now boot back into download mode
Flash TWRP via Odin again (I'm summarizing greatly now, as you should by now understand this kind of shorthand)
Ok, now boot up into TWRP recovery mode (vol up, home, power)
Navigate through TWRP menus to create a Backup. Click Backup Button, and swipe to create backup. (this is just so that it creates the directory structure on your phone)
Click the Reboot System button, skip all the setup you can again. (DO NOT INSTALL SUPERSU!!! will cause bootloop)
Extract the "JasmineROM_v7.0_N910VVRU2CPF3.7z" file it will create a directory called "JasmineROM_v7.0_N910VVRU2CPF3".
Plug USB into phone and to computer. Copy the JasmineROM_v7.0_N910VVRU2CPF3 folder into \Internal storage\TWRP\BACKUPS\Phone SN\
Reboot into TWRP recovery
Click the Restore button (DONT start the restore yet!!!), and check that your JasmineROM is listed as a recovery option. (don't recover YET) If it's not there you copied it into the wrong directy, try again before proceeding.
Go back to the main menu, Click the Wipe button. Click the 'Advanced Wipe' button, and wipe the following cache/dalvik/system/data
Go back to Restore (from 2 steps ago) and run the JasmineROM_v7.0_N910VVRU2CPF3 recovery, return to main menu afterwards
Go to wipe, and wipe the cache/dalvik only this time.
Reboot into download mode
Flash the N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z file via Odin
Reboot the system, this will take a LONG TIME. WAIT for it. (if reboot takes >10 min, pull battery and restart)
Once it boots up, skip all the setup again. Copy the CM13, Gapps and XPosed (both zip and apk) to your downloads. Don't unzip anything, not necessary.
Now reboot into recovery go to WIPE and do a factory reset by swiping.
Then goto Install (still in recovery) and install CM13, then Install Gapps.
Reboot your phone, this time you are setting up properly reboot will take a while to optimize your apps depending on Gapps version used. So do all your setup as you want your phone setup. Once that's done, restart the phone in recovery. (if reboot takes > 5 min, pull battery and restart)
Install via TWRP the XPossed.zip file.
Reboot your phone, once on. Navigate via My Files, to downloads and install XPosed.apk
CONGRATULATIONS. You now have a fully Unlocked, Rooted Note 4 Verizon with CryanogenMod 13.0 installed and XPosed Installed.
Suggested Apps
Kernel Auditor [ROOT], will allow you to adjust kernel settings. Such as CPU clock speeds and thermal throttling, if your phone is too hot.
Note: About ROOT[/], you will have root once you finish this guide. But it is disabled by default, you can enable root in developer options (no reboot required when changing). Unlock your developer options again, and scroll down you will see an option to enable/disable root. This allows you to keep turn off during normal use, and only enable it when you need to install an app that requires root. You can always just leave it on all the time, that is your choice.
Note: Some apps on Google PlayStore will become unavailable due to incompatibility (according to google, HA). Such as YouTube Music, you will no longer be able to install it through the store. But you can install it by using an APK site, such as APK Downloader. On this site you find the app you want on play.google.com, copy the HTTP link and put it into the APK Downloader and it will generate a direct download link to the APK file. Copy onto your phone and sideload (ie. install) through file explorer. I don't endorse them, they are just one of many places you can get APK files.
Change Log
7/28/2016
Another success story :good:
Added note about how root works in CM 13.0
Corrected Step 34
Minor text adjustments, for clarification
Made note that wifi doesn't work with CDP1 flash
Added note that you MUST HAVE a valid sim card with internet access for step 35! KingRoot requires internet to function, and Wifi will NOT WORK after flashing CPD1 firmware (incomparable drivers).
Added another note about internet at the top of the instructions, to make sure people are aware.
7/27/2016
Added Bicknasty to the Contributors list - helped resolve issues I had with CM 13.0 kernel & modem.
Added a note to downloads section regarding total size of files downloaded and expected time.
Re-wrote steps 40-48 to make it easier to understand. Adding some steps and explaining in more detail.
Added note at the top to read ALL the instructions once before starting
Added note with the estimated time to perform all the steps
Added note suggesting Kernel Auditor app, and made reference to the fact that some apps on playstore will NOT install from playstore. Suggested APK Downloader for apps not available from store
Added a Success Story Section
Added note on how to enable developer options

Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5

jwp1299 said:
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Click to expand...
Click to collapse
Probably, but that's the only one I know which is a free download that I'd trust.

JacekRing said:
Probably, but that's the only one I know which is a free download that I'd trust.
Click to expand...
Click to collapse
Alright, still works just a little long. Thanks so much for the guide, working great so far!

jwp1299 said:
Alright, still works just a little long. Thanks so much for the guide, working great so far!
Click to expand...
Click to collapse
How far are you now?
And let me know when you finish, critique my guide. If parts weren't clear enough let me know.
And finally if you run into any issues let me know.

Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!

Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
Yea I do appreciate the help Bicknasty. I'll add you to contributors list later as helping with cyanogen issues I was having.

Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
You know it wasn't so much that it annoyed me it's that there was no concrete guide telling me what to do. It's a thread here, a post there to do a specific thing but they aren't coordinated in a logical way for users to easily find.

Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?

jwp1299 said:
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
Click to expand...
Click to collapse
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.

JacekRing said:
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
Click to expand...
Click to collapse
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs

jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
Lol yea, didn't think to mention reading the whole thing first. To me that's a given I always read everything before starting. I'll add a note to read everything.
As to download time, well it is like what 12 gigs in total? Basically 4 full versions of the Android OS at 2 gigs reach plus all the extras.
I'll try to see if I can't explain the twrp recovery of Jasmine better. Only reason you need to do Jasmine is for the 6.0.1 device drivers (such as modem).

jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.

JacekRing said:
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
Click to expand...
Click to collapse
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.

jwp1299 said:
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
Click to expand...
Click to collapse
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?

JacekRing said:
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
Click to expand...
Click to collapse
Oh of course, go ahead and add me.
Also, if you do end up making a torrent, i'd be happy to help seed at least for a while. I have pretty good upload and no data caps or anything so it would probably help a bit (anything is faster than that 100 kbps that xda was giving)

You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)

I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol

Viper-Link said:
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
Click to expand...
Click to collapse
Not sure what to tell you viper as not enough info. Hope you figured it out...

pfcland said:
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Click to expand...
Click to collapse
Was this after the first time you inputted the adb commands our second? Make sure you pull the SD card after the second time, as it will cause reboots after the second time until you reformat the SD card on your PC. Size will be wrong on PC but size will fix when you reformat the SD card a second time on your phone.
Edit it creates like 20 partitions on the ad card when you do adb, it creates a backup of your phone os.

[GUIDE/TUTORIAL/HOWTO] HTC One M7 Stock to Android 11 / LineageOS 18.1

[GUIDE/TUTORIAL/HOWTO] HTC One M7 Stock to Android 11 / LineageOS 18.1
[GUIDE/TUTORIAL/HOWTO] HTC One M7 any version (m7, m7ul, m7spr, m7vzw) stock to Android 11 R / LineageOS 18.1
This detailed step-by-step guide helps you transform your HTC One M7 (any version) to a powerful one with Android 11.
Make sure you have the One M7 model, in Android, go to Settings > About phone and check the model.
CHANGELOG
v8. Upgrade to Android 11, improve readability, update pack
v7. Updated pack with MagiskManager 8.0.7 and Magisk 21.4
v6. Infos in case of Simlock
v5. Moved to Android 10 thanks to @tarkzim, updated pack with Magisk 20.4
v4. Moving to Android 9. I was wrong in v3 ;- Thx @tarkzim), good for all M7 versions
v3. Reverted back to Android 7.1. No stable ROM for Android 8 or 9 (and will never be)
v2. Tutorial updated for Android 8.1 Oreo, updated pack with TWRP 3.3.1-0
v1. Initial release
1) DOWNLOAD
- djibe HTC One M7 pack (44.3 Mo) v2 : http://bit.ly/djibe-onem7-v1
(includes HTC drivers, recovery TWRP 3.6.1_9-0 for all m7 by Xeno1, Magisk Root 23 adb & fastboot.exe).
Unzip the djibe folder from the zip on root folder of C: drive.
- ROM Unofficial Lineage OS 18.1 for M7: https://forum.xda-developers.com/t/rom-11-0-unofficial-m7-all-lineageos-18-1-stable.4454219/
Download latest build for M7 here: https://androidfilehost.com/?w=files&flid=334598&sort_by=date&sort_dir=DESC
+ BitGApps ARM 11 v1.4+: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Charge phone to 100 %
WARNING. This tutorial uses Microsoft Windows.
WARNING. Warranty is now void.
WARNING. Read carefully the sentences starting with ###.
2) BACKUP DATA AND INSTALL DRIVERS
Disable Antivirus.
Install drivers from my pack:
right click on HTCDriver.exe -> click on Run as administrator and continue the setup.
Then install HTC_BMP_USB_Driver_x64.msi (or *_x86 if you have a 32bits Windows edition).
### Install doesn't work ? Try these drivers for Win10 : https://htcusbdriver.com/download/htc-usb-driver-v4-02-0-001
Now go to my folder flash, and right click the adb 15seconds installer > Run as administrator.
During install, every time the command asks you a confirmation, enter Y and confirm with Enter.
Connect HTC One (while phone on) to PC, let drivers install.
In Windows explorer, HTC One should be available.
### If not make sure phone connection is in File transfer mode (see Android notifications).
Collect all personal photos, videos, etc ... and copy these on PC.
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Disconnect phone.
### If your phone is Simlocked/carrier locked/Network locked, don't go further.
Visit official website of your network carrier (or call their support) to retrieve your desimlock code.
Ask them for details on how to remove simlock.
How do I know my phone is simlocked ? When you insert a SIM card from another operator, network is not accessible.
Only a stock ROM can remove simlock.
To go back from custom ROM to stock in 1 zipfile flash, follow this tutorial: https://tcg96.github.io/m7gurureset
3) UNLOCK BOOTLOADER
In Android, go to Settings > About > Software information > More.
Tap 7 times on Build number. It unlocks Developer options.
Go back to the About menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Toggle on the USB debugging option.
Connect phone, a message appears on phone : Allow USB debugging?
check Always allow and confirm by tapping on OK.
Now, open a Windows command on my "flash" folder (hold Shift + right click on folder -> Open a windows command here).
### Then navigate to my flash folder (if it is on desktop) with this command :
Code:
cd /d C:\djibe\flash
Enter command :
Code:
adb devices
, confirm by pressing Enter.
Command returns :
Code:
List of devices attached
HT35****** device
### If no device is found, uninstall and reinstall properly the drivers while antivirus is off.
### Or start fresh on another PC.
Now type :
Code:
adb reboot bootloader
Authorize ADB commands on phone.
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Type :
Code:
fastboot devices
Command returns :
Code:
HT35**** fastboot
Type :
Code:
fastboot oem get_identifier_token
, confirm by pressing Enter.
Command returns multiple lines.
Select with your mouse all the lines from
Code:
<<<< Identifier Token Start >>>>
(included)
to the line
Code:
<<<<< Identifier token end >>>>>
(included).
Now on keyboard copy (Ctrl + C combo), then open Notepad.
In Notepad, paste those lines (Ctrl + V combo).
Now manually remove all the (bootloader) strings from each line.
Your notepad should now look like this :
<<<< Identifier Token Start >>>>
37A5DBF4FE5F0D9F4425E54AA91AFDBF
2A20E9C67C3BB4FAE60263F76BDEC6AC
847BF9FFB11DAEA4AB88AC8710435449
9BC12E93DF4C54FFE3D064C4C810C49A
2CDAF2E0CD3A164FED4A568CB0FD2AC6
C01AA991733D949C00987062D691DE91
8AA1C97CEBC3ACE83FECE75A1D03CE72
62414C7DC36A73AFCBF433E1EBE2EDC7
E272F73309632D3EF8C86E472B65E8EF
37E46B52FE3F94FC69D1854CA3DE6F48
C3E10001B233A70B1EAF35134F51FCC6
353E0CC98534E6E60A241A7063D0BE2F
A5B752E75C1C47E6F739BDBE67D024DA
3292A14278247557632639802722A86C
E61424F7666AE085AA9905096FEED1AD
5ECBBD867544E95ABDDA277690B8CB55
<<<<< Identifier Token End >>>>>
Now visit this website : https://www.htcdev.com/bootloader/
Register on the site. Confirm registration with your email.
In the select menu, chose HTC One (M7), click Begin unlock Bootloader button.
Agree to legal terms.
Next page, go to the bottom and click continue to step 5.
In the bottom of this page, in the lower textarea "My Device Identifier Token",
copy and paste the multiple lines you just edited (my example is just above).
Click Submit.
HTC tells you : Token Submitted Successfully.
Open your mailbox (associated to your HTC account).
Copy the Unlock_code.bin file attached to email in my "flash" folder you unzipped.
In Windows command, type :
Code:
fastboot flash unlocktoken Unlock_code.bin
, confirm with Enter.
Command should return :
Code:
unlock token check successfully
Back to phone, press Volume+ to select "Yes, unlock bootloader", then Power button to confirm flash.
Now wait while phone is going to Factory reset.
Don't let Android restart by holding both Power + Volume- to enter bootloader immediately.
FASTBOOT menu is overlined in red.
4) FLASH TWRP RECOVERY
Using the same Windows command prompt, enter :
Code:
fastboot devices
to make sure phone is still available.
Then
Code:
fastboot flash recovery twrp-3.6.1_9-0-m7univ.img
Command returns :
Code:
finished. total time: x.xxxxs
##€ If it fails, tries with a Windows Powershell shell.
Now on phone, press Volume- to select Bootloader, confirm with Power button.
You are back to the booloader screen (UNLOCKED is written on top line), press Volume- to navigate to RECOVERY, and confirm with Power button.
Phone reboots in TWRP recovery.
5) WIPE PARTITIONS
In TWRP, check Never show this screen and Swipe to Allow Modifications.
You land on TWRP Home screen.
Go to Wipe > Advanced wipe.
Select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to Wipe menu.
6) FLASH ROM, GAPPS AND ROOT (OPTIONNAL)
We first have to get our zips on the phone.
Still on TWRP Home screen, tap on Mount > deselect all partitions except Data, then connect phone to PC.
In Windows Explorer, you can see MTP Device, copy the zips of ROM, GApps, Magisk + Magisk Manager right in the Internal Storage folder.
Tap on Disable MTP once copy is finished.
Then back to Home screen, tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active)
then Add more Zips -> Magisk*.zip,
then Add more Zips -> bitgapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end (can be long).
When completed successfully, tap on Reboot.
Tap on Do not install when TWRP asks for the app install.
Wait during long first boot.
Setup Android.
7) You can use Backupyourmobile to restore data,
use GPS Status & Toolbox app to enhance GPS fix.
That's it.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, LineageOS team, tarkzim, zsoerenm, alray, ., Flyhalf205, icxj1, R1ghtC, gimmeitorilltell, All M7/MSM8960 contributors.

Just my 2 cents
Just my 2 cents if it can help
djibe89 said:
- a microSD card (FAT32 format). Copy the zips of ROM, GApps, addonsu and deviceid*.apk (both in my pack) on the root folder of microSD, then insert it in phone.
Click to expand...
Click to collapse
The M7 is not equipped with a mircoSD card slot, only a virtual /sdcard (symlink to /data/media/0) ... So they'll either have to adb sideload or adb push the files to internal memory which is pointless at this stage since it will be wiped during bootloader unlock. Or drag n drop the files using mtp from twrp once it's installed on the phone.
3 ) UNLOCK BOOTLOADER
[...]
Now wait while phone is going to Factory reset.
Setup Android again on next boot.
4 ) FLASH RECOVERY
Now re-enable USB debugging in Android.
Using the same Windows command prompt, type
Code:
adb reboot bootloader
again.
Click to expand...
Click to collapse
You could save a lot of time just force rebooting to bootloader (power + vol down) right after BL unlock/factory reset are completed so you don't have to setup the system you're going to wipe 2 steps later. USB debug anyway isn't required to fastboot flash recovery so it's not like booting back in system is mandatory before flashing recovery.
:good:

@alray : Thank you so much for help.
I'm lazy with baby waking up every night and did some awful copy-paste.
I correct all these right now.
Thanks.

I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.

saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
Because you are a senior member you know where to download everything.
But everyone is not like you.
So I tried to compile a ready-to-go pack for the newcomers, like I did for many devices by know.
This allows noobs to profit from custom ROMs and don't keep it esoteric.
Like you say, many downloads are just hacks, so I tried to bundle lowest size safe files.

saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
For the official LOS ROM, tell LOS to store official builds. As they don't do it anymore, we must rely on personnal builds.
A lot of guides out there ? Made extensive search for cracking this phone, never found a step by step one.
Five year old device ? Still so good once unleashed. Custom ROMs are for these devices isn't it ?

@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .

.:B:. said:
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
Click to expand...
Click to collapse
Thanks for your explanations.

Any trouble following this tutorial guys ? How to enhence it ?

802D device supported?

M.Z.F said:
802D device supported?
Click to expand...
Click to collapse
Hi, no idea, does your model has another model name/code ?

djibe89 said:
Hi, no idea, does your model has another model name/code ?
Click to expand...
Click to collapse
Model name & code like?
PRI Version= 4.22_001
PRL Version = 10012

Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you

I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg

Rafay106 said:
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Click to expand...
Click to collapse
All the custom roms mentioned above are NOT for your phone variant.There were almost no development for the 802 branch at the peak of it's popularity and I didn't see anything new for this variant in the past 2 years or so. I wouldn't expect a 7.1 roms for this variant...
Maybe you'll have better luck searching on Asian forums

skovatov said:
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
Click to expand...
Click to collapse
Here you have answer:
https://forum.xda-developers.com/showthread.php?t=2522762
---------- Post added at 05:30 PM ---------- Previous post was at 05:20 PM ----------
Hi.
After installing Android 7.1 Google Pay stop working on my phone. I have torn on NFC communication but terminal don't read my card from app. I don't turn on access to root. Any aidia how to solve this issue?

I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.

Bazooka said:
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Click to expand...
Click to collapse
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?

alray said:
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
Click to expand...
Click to collapse
Thanks for that. I tried to go through it nice and slow making sure I understood each step. I got to where I needed to open a command window on the "flash" folder to which I must have powershell(?) installed as it gave me that option. After inputting 'adb devices' it listed a device but stated it was offline. This is where I am stuck as the steps after this do not work.

drivers win10
Hi, I have a basic ask. Do you know where to get Win 10 drivers? I can't run the installer HTCDriver_4.2.0.001 on my Windows 10 (version 1803).
It gives me the error: The driver installer is not supported for your operating system. Thanks for your help.

[HOW-TO]Android 8.1 for Z00VD/ZC500TG

Hello people of XDA,
as I promised here, here's a tutorial for getting Android Oreo 8.1 up and running to your device.
NOTE: I DID NOT MAKE THIS TUTORIAL! This is a translated guide from 4PDA by nik-kst. I've also rehosted some of the files on Google Drive so you won't have to register on 4PDA(hopefully).
Code:
[B]Your warranty is now void. [/B]
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Now that the disclaimer is dealt with, let's get on with this tutorial shall we?
First things first, we need to grab a bunch of things:
SP Flash Tool;
MediaTek VCOM Drivers;
The Stock Kernel(it will make sense to you soon!);
Scatter file for repartitioning, drop it inside the stock kernel folder(credit to fca.sjc);
ADB and Fastboot of your choice;
New recovery;
Oreo's Backup, drop it inside a MicroSD card or drop it once you have re-partitioned the device successfully;
Once you have everything setup and extracted, you're ready to go!
First, we gotta go ahead and install VCOM drivers - we won't be able to do anything to our phone without them.
If you're running Windows 8/10, make sure to disable Driver Signature Verification.
Go to Device Manager, click Action at the top and click Add legacy hardware. A new wizard window will appear.
Choose Install the hardware that I manually select from a list(Advanced);
In the next window, choose Show all devices and click Next, then click Have disk...
Then you will be prompted to direct to the driver install info, so click Browse...
Now go to the folder of drivers and select the Setup Information file that's fitting for your computer, x86 for 32-bit and x64 for 64-bit.
You should now find 5 new devices in the list, add them one by one by repeating steps 2 to 6 until you have all of them installed.
Windows might complain about unsigned drivers, just allow their installation and proceed.
If your ports list looks similar to the picture below, then you're set for the next step!
{
"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"
}
Next, we'll want to back up the NVRAM partition, because AFAIK, it keeps important unique data about your device such as WiFi, IMEI etc. data.
Note: You may want to take out your MicroSD card and SIM cards prior to this just in case. Also, might be the possible fix if readback for NVRAM fails(needs confirmation).
First, open up Flashtool.exe as admin and go to Readback tab;
Click on Add, a new item in the list will appear. You want to double-click on it, so that a Save File window would appear.
Save that file anywhere you want, name it whatever you like, for convenience I've named mine ROM_NVRAM.
Now, you'll want to find the address in the memory for NVRAM partition. To do this, open up the stock firmware(credit to fca.sjc) scatter file in a text editor(like Notepad++), and find line partition_name: nvram
In that paragraph, find two values: linear_start_addr and partition_size they should be 0x380000 and 0x500000 respectively.
Punch in those values into the Readback block start address window, so it should look something like this:
Now, click Read Back, it should gray out along with Add and Remove.
Now, turn off your device, pull out the battery for about 30 seconds, reinsert it and DO NOT TURN IT ON YET! With the Volume Down "-" button pressed, plug in your device into the USB port.
The NVRAM partition should've been read and you'll get a giant green tick sign when it's done.
Now that that's done, we can start repartitioning our device.
Make sure your SP FlashTool is running as admin, otherwise restart it as admin.
Open up the Download tab and in the line Scatter-loading File click Choose and navigate to the 8.1 scatter file, it should be named MT6580_Android_scatter_8.1.txt.
From the dropdown list, select Format All + Download.
Again, take out the battery for 30 seconds and put it back in WITHOUT turning it back on.
Now click Download, and with the Volume down "-" button held down, plug the device into your PC. There should be a bunch of colored progress bars at the bottom of the window.
Once it's done, you should get the giant tick pop-up, after which you can disconnect the device, and start it normally.
NOTE: it takes a while for the first launch, so give it some time!
Once it starts up into the first launch wizard, we can now restore the NVRAM.
In order to activate the memory writing function of SP FlashTool, re-start it with admin and press Ctrl + Alt + V, the window header should have (Advanced mode) now.
From the Window drop-down, select Write Memory, it should redirect you to a new tab named accordingly.
In the File Path field, browse to the ROM_NVRAM backup that you made earlier.
In the Begin Address (HEX) field, copy the linear_start_addr value off the scatter file.
The region should be left at EMMC_USER.
Now, click the Write memory button, turn off the device, re-insert the battery just like before, and connect the device with the Volume Down "-" button pressed.
It should begin the writing of the NVRAM and once it's done a giant tick pop-up will appear.
Now after that is done, boot into the OS, check that everything works, including IMEI and WiFi.
Also, during the setup wizard or later in the settings setup a screen lock with a pattern or a PIN or a password(credit to fca.sjc), because the partitions may remain encrypted and show 0mb(needs confirmation)
Now you'll want to unlock the bootloader and flash the TWRP recovery.
Now this is a standard recovery flash, but for a quick summary:
Enable Developer options;
Enable OEM unlocking;
Reboot into bootloader mode(I like to use ADB for adb reboot-bootloader);
Make sure your device is detected via fastboot devices, if not, google some drivers for ADB;
Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking.
Now, reboot the phone, it will take a while to reboot, DO NOT PANIC AND WAIT.
Now that we have bootloader unlocked, we can flash the TWRP:
Go into bootloader mode;
Confirm you are being detected again by fastboot devices;
Flash the recovery with fastboot flash recovery [twrp recovery name].img;
now, WITHOUT booting into system we boot into recovery and confirm it works.
Now that you've done all this, you propably want to run Oreo now, eh? Well, here's what we do now:
Note: make sure you have the Oreo's backup zip extracted at it's own folder inside your MicroSD card or inside the phone's internal storage by now(thanks @ZappaDong for letting me know)
From recovery, select Wipe > Advanced Wipe and select system and vendor, and wipe them. Logs may complain about not seeing vendor, ignore that message.
Then, we restore everything from the Oreo backup;
Finally, do a factory reset(aka wipe Data, Dalvik and cache);
And reboot!
Now, fingers crossed, you should be booting into a fully functional 8.1 Oreo! if you did, congratulations!
Please let me know if I've made any mistakes and/or this has worked for you.
All credits go to the awesome people at 4PDA, especially nik-kst(if you're reading this, you the real MVP!), below I've linked the sources I've written this guide from.
Nik-kst's guide to repartitioning the device for Oreo;
Nik-kst's post about the Stable Oreo ROM.

Reserved for possible FAQ in the future

@aurismat, Hey man it worked as expected ! However, I was a bit confused on the repartitioning part when selecting ''Format all+download'' option then clicking ''start'' will only give an error stating that the IMG file of ''vendor'' is missing. (I am using SP FLASH v5.1744)
But nevertheless, I tried the ''Download only'' option and lucky it worked as well. I just wanted to clarify should it be Format all +download or Download only? Or is there a missing corresponding IMG file for vendor ?

Hey @JustAnormalGuy,
It should've been Format All + Download.
Also I'm glad that my post has helped at least one person.
Thanks for pointing out this omitted detail though, I'll edit the post ASAP.

Thanks for the translation!
--- solved ---
I have tried it three times but never managed to back up the NVRAM partition.
Error: s_dl-get_fram_setting_fail (5054) see attached screenshot
-----------
I have used Win 10 on my Mac and it worked.
Now I am stuck at step "5. Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking."
this looks O.K. to me
----------------------------------
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 16.047s]
finished. total time: 16.047s
-----------------------------------
But now nothing happens after
-----------------------------------
> fastboot reboot
rebooting...
finished. total time: 0.000s
-----------------------------------
It's stuck in
[Fastboot Mode] <<==
=> FASTBOOT Moe ...
and nothing happens.
UPDATE
O.K. I have used the Power Button to switch it off and on again, there was a small Android for a few seconds and the phone rebooted the second time. Now I am waiting for it to finish booting.
UPDATE 2
TWRP is working now
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!

Missing tips:
- Put both scatter files inside the stock kernel folder before starting.
-I used the stock scatter file for the NVRAM backup then the 8.1 scatter only for the Formal all+Download step.
- When you first run the stock ROM, set up a pin or a password, otherwise you will have failed to mount data in twrp and data will show as 0mb due to its encryption.

@aurismat does that WW file includes the new vendor release?
In the vendor, a bug was detected, the camera with the auto flash turned on, did not turn on (rather, it turned on and off immediately), the flash when shooting video.
Now everything works as it should: yes2:
Fixed vendor: 07/07/2018
https://yadi.sk/d/DUGRYLnc3YtADV

I did everything according with this tutorial. Sadly my mobile network is not connecting idk why. I get an error saying Simprocessor and it doesnt connect on mobile network. It detects the networks but wont connect. Im going back to stock until someone can help me fix it.

@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
@fca.sjc:
First of all, thanks for pointing out my missing tips.
I'm not really sure if it includes the fixed vendor. I didn't really have any issues with the camera's flash, so they already included it(?)(again, needs confirmation).
For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
Thanks to both of you for pointing out these tips, I'll update the guide and credit you when I'll have more time. Cheers!

[*]For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
[/LIST]
Click to expand...
Click to collapse
After repartition, wifi, 3g and mobile signal works fine. I just cant flash twrp after unlocking bootloader otherwise i get a bootloop (unable to mount data and storage). So after i installed twrp and wiped/restore vendor and system, i reflashed stock recovery to acess android and then, restarted again to recovery. At this point, i did the write memory step again, using old vendor and the new vendor. None seem to work. I even backed up NVRAM using TWRP at first to make sure i did it right and tried to restore from there and it doesnt seem to be an IMEI issue. Maybe it has something to do with the frequency. Im on Brazil right now and idk
It does recognize my Sim card, my number, it downloads the data operators and etc but it doesnt connect to the mobile signal idk why. The bug starts at the restore step so it has something to do with this part.
I just test stuff but im pretty experienced at flashing and reflashing, etc. I guess only a dev can help and i actually went back to 7.1 UHANS rom, wich i got from 4pda.ru. Before using this rom, I was having a bluetooth audio stream bug and Ive tested like 4-5 roms, one for each kernel that was there. Lets see if someone can help me with this, cause i want oreo for better bluetooth audio stream.
Thanks for your help so far. I really apreciate it. This device is very good and we dont see many mods here on xda for it.

aurismat said:
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
Click to expand...
Click to collapse
Thanks again!
I am using Windows 10 (bootcamp on the iMac) now and I have read the description in the 'old' [ROOT/TWRP] thread but used the files you have provided.
TWRP is working now, but I got an error that the ZIP file on the SD card was corrupted. Maybe I have damaged it when copying it to the SD card under OS X.
I am just redownloading it with Windows 10 and give it another try. (Yandex is very slow now, about 60 KB/s)
------------------------------------------------------------------
UPDATE
I have downloaded "WW_Phone-user_810_O11019_1528478718_release.zip" again, put in on the SD card, booted into Recovery, wiped system and vendor and chose "Install" , selected the "WW_Phone-user_810_O11019_1528478718_release.zip" file.
But I still get an error message.
Installing zip file '/external_SD/WW ... release.zip'
Checking for digest file
Skipping Digest Check: no Digest file found
[IN RED]Invailid zip file format!
Error installing zip file '/ 'external_SD/WW ... release.zip' [/IN RED]
Updating partion details...
...done
I have just copied the zip file from the download folder to the SD card - have I missed anything?

ZappaDong said:
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Click to expand...
Click to collapse
Yup that one

@ZappaDong, yeah I kind of forgot to mention again - you should've extracted the .zip in which the backup came in. It's a backup, not an installation zip.
It needs to be extracted into its own folder inside the MicroSD card, so that then it could be used by TWRP to recover the partitions.
Thanks for pointing this out to me though, gonna edit it ASAP.

@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is better to use PC restore tools since it writes directly to the nvram unlike apks like Chamelephon which (according to what I know) writes only to nvdata.
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 in with sim 2. I forgot the explanation on it but it helps.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.

JustAnormalGuy said:
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is the best IMEI restore tool since it writes directly to the nvram. (Meaning it retains even after wipes to data, system etc. via twrp)
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 with sim 2. I forgot the logic on how that helps but I've seen it as a solution as the phone rereads the sims.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
Click to expand...
Click to collapse
Thanks for your help bro. I did check the IMEI while i was on this oreo rom. It seem to be ok. Number was there but i did not check if it was the right number. I might check it when i try to flash again. Probably later today when i'm home.
The problem wasnt just data connection, it was the connection itself. I couldnt call or receive SMS to activate whatsapp, for example. Like i said previously, those features were ok after repartitioning (on stock repartitioned). After the restore step, i did check all network options, including data, network mode, network connections available,etc. I'll follow your tutorial to restore the IMEI if the numbers are different then. I'll remember to take some screenshots next time so you guys can help me figure out what the problem is. Thanks again

aurismat said:
@ZappaDongIt's a backup, not an installation zip.
Click to expand...
Click to collapse
Yes, that did the trick. The installation went through and everything seems to work now.
Thank you again for your patience.

I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?

Ricardo Flowers said:
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Click to expand...
Click to collapse
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.

aurismat said:
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
Click to expand...
Click to collapse
Can you do a tutorial? I did not quite understand how it installs. Sorry, google translate does not help.

Deleted

2020 Guide for rooting Xperia Play, tips and resources

This is a guide for rooting and customizing the Xperia Play from out of the box. fma965’s Megathread Guides is a more in depth step-by-step tutorial that you might want to look at instead. However, some people might still run into issues because overtime links are dead and it's difficult to find the right files to do certain things. These are the methods that work for me. I also have useful files and minor tips that hopefully make the job easier.
Link to all the useful files I've collected for the Xperia Play.​​(There are no downloadable paid apps.)
Post #1 Instructions for beginners, no bootloader unlocking required
Post #2 Instructions for advance users, bootloader unlocking is required
Post #3 Tips​
Why root?
The biggest problem with the Play is there’s only 400mb of internal storage space, much of the space is taken up by bloatware. Out of the box, there is not even enough free space to update Google Playstore and Google Play services to the latest version. So it’s a good idea to root the device in order to delete the system installed bloatware. While it's possible to move apps to the SDcard, some apps simply load faster from the internal storage. I recommend to not sign into your Google account on this phone and not let Google Playstore and Play services update themselves. This is because they take up too much space and are resource hungry which affect the phone’s performance. This phone is very old and have very poor to zero compatibility with modern apps and websites, it is better and safer to use it for offline gaming and media playback only.
To Unlock the bootloader or not?
It is not required to unlock the bootloader to root and install ClockworkMod Recovery for this device. Unlocking the bootloader is redundant unless you are an advance user and intend to install custom roms and kernels. If you only want to root the phone, delete bloatware so the phone run smoother, and have more space to install games, then it is not required. Therefore, my instructions below will be for rooting without the need to unlock bootloader.
Instructions for beginners, rooting​1. Installing fastboot and flashmode drivers
2. Flash stock firmware using Flashtool
3. Rooting
4. Optional: Installing ClockwordMod
1. Installing fastboot and flashmode drivers
These drivers are required for fastboot and flashmode to work, in order to root or flash the phone. This step is absolutely crucial for everything else to work.
First, reboot your Windows computer into “Disable driver signature enforcement” mode because these drivers are unsigned and will not install otherwise.
This is “F8” on bootup for Windows 7, and “Advanced startup” for Windows 8 and 10 (Hold SHIFT while pressing Restart -> Troubleshoot -> Advanced options -> Startup settings -> restart).
For more information, check this guide, or search the web for "install unsigned drivers". Also the program "Driver Signature Enforcement Overrider" may be useful.
Now to install the drivers:
Download and install the program Flashtool version 0.9.24.4. Download this version specifically, newer version have issues with this device!
Then run C:\flashtool\flashtool-drivers.exe.
Only select these four choices during the installation to reduce driver conflicts:
Flashmode Drivers
Fastboot Drivers
Common drivers Moga and Zeus Board
Sony Ericsson Xperia arc, Xperia neo, Xperia PLAY, etc
{
"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"
}
In the past I have selected all the drivers in the list to install and it created a lot of issues.
For reference, later in this guide when you'll connect the Xperia Play to your computer under various modes (adb debugging, fastboot, flashmode), this is what you should see in the Windows Device Manager:
2. Flash stock firmware using Flashtool
Flashtool allows flashing factory firmware to return Sony phones to stock. Flashing an older firmware version on the Play allow easier rooting, which is the main purpose of this step. However, you can skip this step and try rooting the phone in Step #3 first, if that doesn’t work, use this step to flash to an older firmware, and then try rooting again.
Recommended rootable firmware for R800i / R800a GSM: "R800i_4.0.2.A.0.58_Enhanced.ftf"
Recommended rootable firmware for R800x Verizon: "R800x_3.0.1.E.0.88_Verizon.ftf"
(Make sure to download the correct ftf file for your device, R800i is for unlocked and AT&T devices, R800x is for Verizon.)
*DO NOT connect the Xperia Play to your PC yet until the steps say so.*
-Download the ftf file and put it somewhere easy to find like your desktop.
-Make sure the phone is turned off and not connected to the computer.
-Launch the Flashtool program.
-Click the “lightning” shaped icon on Flashtool’s menu.
-Select “Flashmode”, select Ok.
-On the “Firmware Selector” menu, select the “Source folder” where the ftf file is located.
-If you check the USERDATA box, it will wipe all your user data, this is recommended to prevent compatibility issues.
-Select “Flash”, the “Wait for Flashmode” window appear.
-While holding the BACK button on the phone, connect the phone to your computer (via microUSB cable)
-The Power button should glow green and the flashing will begin.
-After the flashing is done indicated by Flashtool, unplug and reboot the phone.
Hint: If you gets the errors:
ERROR - Not a sin file
ERROR - Error flashing. Aborted
Try a different Flashtool version. I get this error with the later versions of Flashtool, but version 0.9.24.4 works.
3. Rooting
-Enable USB Debugging on the phone.
Located in: Settings -> Applications -> Development -> USB debugging
-Set the phone to "MSC” mode, not MTP mode.
Located in: Settings -> Sony Ericsson -> Connectivity -> USB connection mode
-Connect the phone to your computer and launch Flashtool program
-In Flashtool, select “My R800" -> Root -> force ZergRush”
It will then give you the option to choose Superuser or SuperSU. I recommend choosing SuperSU, but either works:
-Superuser: usually requires the phone to reboot twice to root successfully.
-SuperSU: usually require only one reboot. After the phone rebooted, run SuperSU app on the phone. It will ask to install the binary via CWM or Normal. Select Normal.
Hint: If you select the option "Full unroot" inside SuperSU, it will successfully unroot the phone. However, afterward if you try to use Flashtool to root again, it may not work.
4. Optional: Installing ClockworkMod
After the phone has been rooted, install the "CWM Installer 5" app (credit to "nobodyAtall") which let you install ClockworkMod Recovery. ClockworkMod is not needed, but it is useful for backing up the image of the phone in case you need to restore it at a later time because you screwed up.
Note: In case booting into CWM from the app doesn’t work. While phone is turning on, when white Sony Ericsson logo appears, keeps tapping Vol Down button. Taps, not holding, you don't have to do it very fast.
To navigate CWM screen: Use Vol Up & Down to navigate. BACK to go back. HOME for Okay/Select.
"Back menu button is disabled." WTF?
While in CWM, if you press Vol Up + Vol Down together at once, it will toggle between enabling and disabling the back button.

Instructions for advance users, rooting using unlocked bootloader method
Note: If I remember correctly, the R800a (AT&T version of the Xperia Play) is not allowed to have it's bootloader unlocked. Therefore this step is only for the R800i and R800x models.
-Reboot your Windows computer into “Disable driver signature enforcement” mode because the drivers are unsigned and will not install otherwise. This is “F8” on bootup for Windows 7, and “Advanced startup” for Windows 8 and 10 (Hold SHIFT while pressing Restart -> Troubleshoot -> Advanced options -> Startup settings -> restart).
-Install the fastboot and flashmode drivers:
Download and install the program Flashtool version 0.9.24.4. (Download this version specifically because newer versions have issues with flashing this phone's firmwares.)
Then run C:\flashtool\flashtool-drivers.exe.
Only select these four choices during the installation to reduce driver conflicts:
Flashmode Drivers
Fastboot Drivers
Common drivers Moga and Zeus Board
Sony Ericsson Xperia arc, Xperia neo, Xperia PLAY, etc
-Unlock the bootloader
-Use fastboot mode to boot into CWM:
While the phone is off, connect it to the PC while holding the SEARCH button, wait for the power button to turn blue meaning you’re in fastboot mode.
-Boot into CWM with this command: fastboot boot recoveryPLAY.img
*Boot the image only, do not flash it.
*Link for the latest "Android SDK platform tools" which contains adb.exe and fastboot.exe.
-Wait about 20seconds for CWM to appear. From here you can root by flashing SuperSU.
*Note: For this CWM version, SEARCH is the Okay/Select button.
*Credit to FreeXperia team for the recoveryPLAY.img.

Tips​
Obligatory: The sim card slot
------------------------------
The sim slot for this phone have gold pins or "teeth" which acts as contact points. If you use a sim card adapter(s), as you try to remove them from the sim slot, the bottom edge of adapter will absolutely guaranteed to get stuck on the gold pins. If you try to pull harder, it will break the gold pins resulting in an broken sim slot. This does not matter if you use a new precisely cut adapter. Once it is stuck, the safest way to remove the jammed adapter is to remove the back casing of the phone (with a T6 Torx screwdriver) and use a precision tweezers to remove it, however, this is not easy either. One time I had to remove a broken piece of the adapter stuck inside the slot from the backside to not break the gold pins, not through the front.
The best way I found to get around this is to cut away the bottom edge of the adapter(s). See image below. This will make it a bit tricky to insert the sim card, but it's not too hard. As for removing, just pull it out slowly, the sim card should come out with the adapters (if not, tweezers).
Side note: Since AT&T already shut down their 2G network, only T-Mobile work on this phone, but they will also shut down their 2G at the end of 2020.
GPS issues
------------------------------
This phone by default have very poor GPS reception so you shouldn't expect it to work. If I remember correctly, a sim card has to be inserted for GPS to work on the GSM version of this phone. Verizon R800x don't have a simcard slot and doesn't have this issue.
Try flashing this agps.patch.sonye.build.v3.1 patch in ClockworkMod Recovery to see if it helps. I wouldn't get my hope up though, GPS has always been very shoddy with old Android devices.
Installing apk without a file explorer
------------------------------
If your phone don't have a file explorer installed out of the box, enable "USB Debugging" in the phone, then connect it to your PC. Use adb command to sideload apps from your PC: adb install appname.apk
Hint: If you drag an apk file from the File Explorer and drop it into the Command Prompt's window, it will automatically include the full path name for the apk file.
Android 2.3 Compatible apps
------------------------------
These are free apps I collected that are compatible with Android 2.3.
(There are no downloadable paid apps.)
Google Play Store and Play services (latest Android 2.3 compatible)
------------------------------
Google Play Store 6.2.02
Google Play services 10.0.84
Emulator recommendations
------------------------------
CPS2: Use CPSEmu.
MAME 0.139: Use MAME4droid(0139)-1.6.1-MULTI. This is the latest version of this emulator that works on the Xperia Play running Android 2.3 without crashing. Any newer version will crash. If you log into the Playstore and install the latest version, it will crash.
PSX: I find ePSXe combined with the opengl plugin gives best performance. Make sure to enable opengl plugin inside ePSXe's options.
SNES: I find SNES9x EX non-plus version (not the plus version from the Playstore) have better performance and plays smoother. Technically the emulation is supposed to be a little less accurate, but really it doesn’t matter.
Robert Broglia emulators: I have excellent results with the “.emu” emulators by Robert Broglia. The NEO.emu version 1.5.40 have poor laggy performance on the Play. The previous 1.5.37 ran very smooth, however it is a paid app and only the latest version is available anymore.
Bloatware apps to delete
------------------------------
These are apps I deleted from the /system/app folder to clear up space, but it is at your discretion to choose what to keep. You need a root capable file manager, such as Solid Explorer Classic.
Code:
AdobeFlashPlayer.apk
brucelee.apk
chinesetextniput.apk
com.sony.playstation.ncua94900_1.apk #Crash Bandicoot
com.sonyericsson.androidapp.storefront.apk
EventStreamPluginFacebook.apk
facebook.apk
fbcalendarsync.apk
FBIAppShare.apk
FBMediaDiscovery.apk
FBMusicLite.apk
FBNotificationPublisher.apk
FBSetupwizard.apk
fifa.apk
GenieWidget.apk
Gmail.apk
GoogleQuickSearchBox.apk
Maps.apk
officesuite.apk
playnowclientarvato.apk
PlayStationPocket.apk
PostViewer.apk
SEMCFacebookProxy.apk
Sims.apk
starbattalion.apk
Street.apk
Talk2.apk
VoiceSearch.apk
YouTube.apk
Also check these folders for more preloaded apps to delete: /etc/customization/applications or /system/etc/customization/applications
Free up the second MENU button.
------------------------------
This phone have two MENU hardware buttons. "keypad-zeus.kl" contains the binding for the phone's hardware buttons, located in folder /system/usr/keylayout/.
You can directly edit "keypad-zeus.kl" as a text file if you have a root capable file manager (Solid Explorer Classic). PS. It's probably a good idea to backup of this file first.
The original binding give this phone two Menu buttons.
key 226 MENU WAKE_DROPPED
key 139 MENU
“Key 226” is the small MENU button below the Down button. I changed it to SPACE instead:
key 226 SPACE WAKE_DROPPED
This frees up an extra button which is useful for emulators.
Reboot phone.
AC3 support for MX Player
------------------------------
This MX Player codec pack (mx_aio_1.7.32.rev1) is specifically compatible for ARMv7 devices running Android 2.3. Copy this zip file to phone’s SDcard and load it inside MX Player: Settings -> Decoder -> Custom codec
Turn off Repeat mode for stock Music app "SemcMusic.apk"
------------------------------
I like the stock Music app for this device, however, almost every firmware come with a version that cannot turn off repeat. I don't remember where I found this version from, but it allows turning off Repeat mode using the Menu options.
Using a root capable file manager (Solid Explorer Classic), download "SemcMusic.apk" and paste it into the folder “/system/app” overwriting the old file. (Simply sideloading will not work.)
Also make sure to fix the file’s permission back to 644:
Reboot phone.
Android 4 ICS?
------------------------------
You may have noticed that I have not mentioned Android 4 / ICS / CM9 in this guide. That's because I find the performance to be very very poor and not worth it. You can try flashing it if you wish, but you will lose much of the gaming performance.

Thank you for the 2020 updated guide and tutorial

Really appreciate you putting this up. Just pulled mine out of storage and thought there's no way I'd find up to date files and info for it.
Now I've just got to find a place that still sells flex cables for it.

Hi ! I have recently buy this device 9 years after the release and I'm in research of oldest version of the doomlord kernel.
Unfortunatly all links are dead and if someone can share a compilation pack of the kernels it could be awesome.
I'm specificaly interested in the early ones for gsm, like the v02/v03 linked in this post : https://forum.xda-developers.com/showpost.php?p=15805471&postcount=2
The one made for the firmware 3.0.1.A.0.145, someone can share it ?
BTW if your searching for the best rom for emulation, it's this one : https://sites.google.com/site/panicus/nerdery/attodrive
Download link : https://drive.google.com/open?id=1nNDy6cux_roYFqUDhksSmvVKnCE1eBRS

I had all those LuPuS and Doom Kernel images at one point, but deleted them overtime. Sorry. Try posting in the original kernel threads and see if someone still have the files.

I'm pretty sure i have some kernel images stored in my PC. Will look for it these days...
Now i remember the good times with the Sony Ericsson Xperia Play... Dreaming...
It was the first smartphone for my son, was a present from me - and he was the king in school, you know what i mean.
Now it's here, at home, repaired, built from 3 Xperia Plays, bought years ago at eBay....
Aaahhh, nostalgic....
Greetz,
0LDST4R

Great guide, I wished this guide was created back late last year when I got my first Xperia Play I had to follow a few guides and they were not noob friendly.
Thank you for your info about Google Play Store/Play Services and MAME fixed my long time issue!
For advance users, take a look at the following to increase your RAM memory size: [MOD] Increase RAM memory size(without swapper!) (good for gaming)
Also for the advance users, I use an app called Link2SD to add additional storage for installed apps, I created a 16GB 2nd partition on the SD CARD, which acts as extra storage, you can increase to whatever you like, and linked new installed app to this partition.
For you pirates, don't bother trying to find a hacked apk for this app, you wont find a working one. Small price to pay for the plus version to unlock the extra features but it is well worth it.
The above two will compliment the stock firmware, I got another Xperia Play, so one has stock FW and the other has XperiaPlay Z Final Ultimate Edition (4.0.4).
Added Notes:
I had issues with flashtool telling me "ERROR - Device connected in flash mode but driver is too old", after some soul searching, the issue was related to my USB3.0 port on my laptop, since I didn't have any USB2.0 ports, I did have a cheap generic USB2.0 4 port usb hub, I connected this and it fixed my issue.

Thank you great guide [emoji4] my phone is now rescued and boots up .
I am unable to root for some reason using the flashtool method .
It has been rooted before in the past . I also tried one click root but that's asking for payment , any ideas greatly appreciated .
Thanks .
Sent from my VOG-L29 using Tapatalk

Okay so I was successfully able to root my phone (got supersu installed) and I've been down a long rabbit hole of trying to understand how adb works. I figured out how to open my cmd prompt in the folder, but when i try to force install CWM using it, I get:
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
Performing Push Install
.\CWM_Installer_5.apk: 1 file pushed, 0 skipped. 175.2 MB/s (2257096 bytes in 0.012s)
adb: error: failed to read copy response
Sorry I'm new to this whole thing and trying desperately to learn... Any advice is appreciated.

Great Post!
As someone who recently picked this device up to preserve some history, as well as possibly use it as an emulation device for my wife at work, I really appreciate the depth of your post. I am not entirely familiar with rooting devices, and adb sideload, but I was able to follow your tutorial and find a nice device in the process.
---------- Post added at 10:48 PM ---------- Previous post was at 10:43 PM ----------
Kiri_The_Fox said:
Okay so I was successfully able to root my phone (got supersu installed) and I've been down a long rabbit hole of trying to understand how adb works. I figured out how to open my cmd prompt in the folder, but when i try to force install CWM using it, I get:
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
Performing Push Install
.\CWM_Installer_5.apk: 1 file pushed, 0 skipped. 175.2 MB/s (2257096 bytes in 0.012s)
adb: error: failed to read copy response
Sorry I'm new to this whole thing and trying desperately to learn... Any advice is appreciated.
Click to expand...
Click to collapse
I can say that I ran into that issue as well, and I don't know what I did that fixed it. I had a PC reboot, as well as a soft boot into CWM on the device. Once doing both of those things it seemed the adb server matched up and things went smoothly. I wish I had some knowledge of how to explain how it worked, I researched a lot about it and everything said it had to do with the version of the adb server running conflicting with the version of the android platform tools installed. Maybe this can help you as well, best of luck!

I have a question and hope anyone can help because I'm kinda tired of thinking lol.
-So, to root easily as shown here, you need to have firmware .58 or lower.
-You cannot root if you have firmware version .62 or higher.
-To install one of the best roms, which is JokaWild, you need firmware version .62.
-To be able to flash JokaWild, you need to have root (to install CWM).
-You can install a custom kernel through fastboot mode which among other things, would force root...
...but, to install a custom kernel, apparently, you need a rooted device.
*Basically, to install this room, you need to root a firmware which cannot be rooted.
So, am I missing something here or doing something wrong? I just can't figure this out.
EDIT. Figured it out. You need an unlocked bootloader.
No tutorial I've seen explains the difference between unlockABLE and unlockED bootloader, so I didn't even think about this.
First follow a tutorial on how to unlock a Sony bootloader and then everything will work.

pakrett-bm said:
BTW if your searching for the best rom for emulation, it's this one : https://sites.google.com/site/panicus/nerdery/attodrive
Download link : https://drive.google.com/open?id=1nNDy6cux_roYFqUDhksSmvVKnCE1eBRS
Click to expand...
Click to collapse
If you know of any way to get this thing working on the R800i model, then good. Otherwise it appears to be an R800x-only ROM.