In case someone is still using this for Xposed, etc., here is a new build with the latest r79 security patches
https://www.androidfilehost.com/?fid=817550096634756906
https://www.androidfilehost.com/?fid=817550096634756906
[ROM] [6.0 and 5.1] nAOSProm for Xperia S
- Thread starter mickybart
- Start date
-
- Tags
- development
is there a way to go back to stock after using this rom? I want to sell the phone to a second hand shop but they only accept phones with stock firmware.
I've tried with flashtool from mac and windows and both fail when reading info from the phone
I've tried with flashtool from mac and windows and both fail when reading info from the phone
nageswarswain
Senior Member
If you read my previous message, I clearly said I tried with flashtool and official ftf. Anyway, I moved this matter to the Q&A thread
Hi there, I just updated from nAOSProm-5.1-b27 to nAOSProm-6.0-b13, but I am having a huge problem... I had to repartition the phone in order to update, I backed everything up but it looks like Android's MTP did not copy all the folders I asked him... So I only have 3 pictures in my DCIM/Camera folder, instead of hundreds... Is there any way on Earth to get my files back ? If I revert back the partitions and restore old TWRP backup, will I be able to use tools like Undelete to find my deleted files ? I do not want to touch anything to do not overwrite data, please help me 
Thank you very much, I knew I couldn't trust MTP...
Thank you very much, I knew I couldn't trust MTP...
Try with undelete or any other tool. There was a thread on Galaxy Nexus' forum about how to get a full copy of the memory to perform this kind of operationz
Enviado desde mi Redmi 3S mediante Tapatalk
Enviado desde mi Redmi 3S mediante Tapatalk
Do I need to do it with former partitions state ? And can you help me to find this thread ? I know I can make a backup with dd, but I have no idea how to do next...
Thank you for your quick reply !
Edit : I am trying to make a disk image of /dev/block/mmcblk0, I will try to mount it and try to restore the old sdcard partition with testdisk, but I don't think I will be able to browse my /dev/block/mmcblk0p15 partition
Thank you for your quick reply !
Edit : I am trying to make a disk image of /dev/block/mmcblk0, I will try to mount it and try to restore the old sdcard partition with testdisk, but I don't think I will be able to browse my /dev/block/mmcblk0p15 partition
Last edited:
I'd do it as it is right now. https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705 that's the thread i was talking about. Use testdisk on a linux system, that's your best chance to save your files
Enviado desde mi Redmi 3S mediante Tapatalk
Enviado desde mi Redmi 3S mediante Tapatalk
:crying:
So far, I have found these threads :
https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705
https://dflund.se/~jokke/androidfilerecovery/
In fact, I don't know if any program can revert back the merge of
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
to
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Last edited:
I made this 30gb backup of mmcblk0, hopefully I ran fdisk -l before and after repartitioning so I know the beginning and the end of each partition, the old 27gb /sdcard partition wasn't full at all (around 5gb only) and the actual /data partition only have nAOSP on it, with only a few apps so I think I have chances to recover some data, only some things might be overwritten... Now I will try to mount the backup and revert the changes, to make the mmcblk0p15 partition (with fdisk or gparted I think) and to use some data recovering tools... The guide doesn't explain how to restore the old partition table, I hope I am doing it the right way !
(Sorry for double post, I thought it would merge the two posts automatically)
EDIT : I managed to get some data back (the most important pictures) using photorec on the dd image I made. I still have a copy of this file in case I find a better solution but I think I am giving up for now ! Thanks to skyleth !
(Sorry for double post, I thought it would merge the two posts automatically)
EDIT : I managed to get some data back (the most important pictures) using photorec on the dd image I made. I still have a copy of this file in case I find a better solution but I think I am giving up for now ! Thanks to skyleth !
Last edited:
i have 0MB if try to format or convert data it fail :crying: what do i do now??
*in adb shell /dev/block/mmcblk0p15 was c Win95 FAT32 (LBA) insted of 83 Linux but is it a problem?
Last edited:
You ****ed something up with repartitioning. /data dev block simply isn't there.
Putting aside the right thread to post would be its one, you could post the partition table parted prints, for starters.
@mickybart could first post advertise punchup b14? There's simply none otherwise
It actually worked now.. the weird thing is that i couldn't change the /data file system from F2FS to EXT 2 EXT 3 EXT 4 or exFAT only FAT worked but i kinda gave up after the first 3 trys.. changed now back to F2FS and was able to mount, flash and start ROM :angel:
Last edited:
Also posted another build after that
https://forum.xda-developers.com/xperia-s/s-development/rom-naosprom-xperia-s-t2958516/post71566596
I did something wrong when I tried to repartition the device. When i start the mobile I get that 27.94 of 29.72 is used and it says that the system takes 27.72 GB. I think that what I did is I deleted some partitions and then I recreated some the wrong way.
Could someone explain what the right partitions should be so I can create them correctly (if it's possible I'd prefer the commands).
PS: I tried to install nAOSP 7.x but i don't think it's any different
Thanks in advance
Could someone explain what the right partitions should be so I can create them correctly (if it's possible I'd prefer the commands).
PS: I tried to install nAOSP 7.x but i don't think it's any different
Thanks in advance
nageswarswain
Senior Member
I did something wrong when I tried to repartition the device. When i start the mobile I get that 27.94 of 29.72 is used and it says that the system takes 27.72 GB. I think that what I did is I deleted some partitions and then I recreated some the wrong way.
Could someone explain what the right partitions should be so I can create them correctly (if it's possible I'd prefer the commands).
PS: I tried to install nAOSP 7.x but i don't think it's any different
Thanks in advance
Have you restarted the phone after the pic you given above ? iF YOU could still use your mobile then you are lucky... just flash official stock rom then start the whole thing again...
Yeah, i managed to start it (that way I could see how much of the storage is used). The only problem was that it coulndn't see my SIM card. So flash official rom and then repartition? what way would you recommend?
nageswarswain
Senior Member
If you want you can follow the whole re partition procedure from where now.but the best way is always starting from stock...be careful on the next time.Dont touch the partitions except 14 and 15 n you will be ok...Take time read carefully and proceed..Best of luck
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
245nAOSP ROM 5.1 and 6.0 for Xperia S
The purpose of this rom is to provide a rom not so far of the AOSP with some cool features (nAOSP means "near AOSP").
As I'm using some external works to do this rom, I first want to thanks the community and specially billchen1977,ViPER4Android Team ,Cyanogenmod Team , FXP Team
nAOSP 6.0 Marshmallow Changelog (features, issues, etc)
b14
IMPORTANT: temporary removed due to an annoying undetected bug !
- android-6.0.1_r70 (October security fixes)
- Kernel: security fixes (from nAOSP 7.0)
- 2D: Support 60 fps + managed by the GPU to reduce CPU load (improve global responsivness)
Previous versions
nAOSP 5.1 Lollipop Changelog (features, issues, etc)
b30
- android-5.1.1_r36
- Support /sdcard legacy path (fix issue with some apps like ES File Explorer)
- Hw Keys: launch Camera application with Camera key can be configured to Disabled, Long press only or default
Previous versions
Download
Release available under :
https://www.androidfilehost.com/?w=files&flid=49217
Overclocking
Overclocked kernel are tested on my own device BUT I won't be responsible for any damages on yours
Please don't enable mpdecision on OC kernel and b20+ version except if you know what you are doing.
Since b20 kernels are merged so the overclocking is available in the default kernel. By default the ROM will use stock frequencies.
Thermanager
By default if the device is too hot it will reduce the screen brightness and CPU clock. When the device will be cool enough it will restore brightness and CPU clock but at 1.5Ghz only.
If you want to force thermanager to restore the clock to a specific value defined by an external overclocking tool, you can edit /system/etc/thermanager.xml.
See http://forum.xda-developers.com/showpost.php?p=62419397&postcount=2465
ViPER4Android
All credits go to ViPER520 and the amazing works.
You should read detail and go to thanks developers.
xda : http://forum.xda-developers.com/showthread.php?t=2191223
website: http://vipersaudio.com/blog/?page_id=31
Layers
Themes are supported with Layers Manager.
This is not a CM Theme Engine so you can just use Layers themes.
Howto flash
6.0 and 5.1 procedure
(OLD) 5.1: Read and thanks UlvarinPL
Translation help
6.0 translation files
Known issues
6.0
Source
nAOSP 5.1
nAOSP 5.1 noemulated
nAOSP 6.0
Release
Kernel: 3.4.0
Android: 5.1.1 and 6.0.1
Thanks
- billchen1977
- ViPER4Android Team
- Cyanogenmod Team
- FXP Team
- TWRP Team
- All the community around Android
FAQ54nAOSP 6.0/5.1 Ultimate Flashing Procedure
So regarding the numbers of comments I will assume that I have not well explain how to flash the ROM, Gapps, Xposed, SuperSU etc...
Why it is more complicated than before ?
This is not the fault of devs but due mainly to security enforcement (new Android permissions system, new Selinux rules, new dm-verity on some devices to check that /system is not modified...).
So due to that :
- New SuperSU comes with a System and System-less installation
- OpenGapps need to be flashed with the ROM before the FIRST boot of the ROM.
- Some patches need to be integrated on AOSP.
. Ask Google.)
Infortunately if we don't respect a STRICT flashing method it will fail. So let's go to explain that again
GApps Flashing
For nAOSP 6.0
How to flash Gapps is explained into the Flashing section below but you need to know that on nAOSP 6.0 since b12,
you need to DON'T flash PackageInstallerGoogle.
To do it the ROM include a file into /persist/gapps-config.txt that exclude this package to be installed by Gapps.
If you already have a file gapps-config.txt somewhere it will probably override the file provided with the ROM so you need to add on your custom file the input 'PackageInstallerGoogle'.
The reason is to don't remove the AOSP PackageInstaller that permit to manager Superuser permissions since 6.0 b12.
Flashing
If you WANT to flash nAOSP 5.1 before b29 or noemulated versions
I suppose that you have not changed partitions on your device. If this is not the case revert to partition layout with a separate /data (p14) and /sdcard (p15).
Go to 'Manual procedure' section below.
If you DON'T come from nAOSP 6.0 or 5.1-b29+ and want to install last nAOSP version (except noemulated)
You will have to repartition your device if it is not yet done. DON'T ask a solution without re-partitionning. You want the last Android version, you need to evolve with Google decision.
PLEASE READ CAREFULLY. This is not a complex procedure but you have to repartition the device if not yet done and to backup your data prior.
Backup:
We will format /data and /sdcard so you need to take backup and put it outside of the phone.
Use your current TWRP to backup your ROM (system/boot/data) into /sdcard
Once done, backup on your computer the /sdcard content (use a file browser with mtp or adb pull)
Recovery/TWRP:
Extract recovery.img from the Zip file
(Alternative to below procedure if you already have TWRP: start TWRP/Install/Select image/Select Boot/Reboot)
Enter the device into fastboot mode
flash the recovery.img into boot partition like a boot image (fastboot flash boot recovery.img)
restart the device (fastboot reboot)
You should be on the recovery (it can be a little bit long to start the first time)
Repartitionning:
Go to Mount on TWRP gui (uncheck system, data, cache etc)
Connect on the recovery with "adb shell"
fdisk -l /dev/block/mmcblk0
Copy the output of the command to a file with your backup. It will permit you to revert if needed and to help you if you have an issue (read carefully and you will not have)
Interesting parts are those in bold :
/dev/block/mmcblk0p14 42945 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
It can be not exactly the same values for you depending the size of your /data (p14) and /sdcard (p15)
so here we go (don't forget the section backup. this procedure will erase your data)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-954240, default 769): 42945
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240): (just press enter if the default value is the good one)
Using default value 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table (You can have an error message about old table used. This is because you have not un mount every partitions before. This is not a problem, just continue to read the procedure)
Once repartitioning done, do NOT do anything else and just reboot the device (to be sure that the partition table is take into account by the kernel)
Now we will convert /data and /cache to F2FS.
Ext4 is not supported anymore on nAOSP 6.0 (Ext4 is still supported on 5.1 but you should migrate to F2FS). You don't need to take care about the 16384 byte to reserve for encryption. TWRP will do it for you.
Into TWRP:
Wipe
Advanced Wipe
select Data
Repair or Change File system
Change File System
F2FS
Swipe to Change
Press Home and do the same procedure to convert Cache partition to F2FS
Once done, again, do NOT do anything else and just reboot the device (required by TWRP)
If you still see 0MB or a wrong size for data after the reboot, try to format data (Wipe/Format Data). In the worst case, convert data to ext4 and convert back to f2fs will do the job
Upload the ROM/Gapps/SuperSU...
Upload the ROM/Gapps and every zip that you want to flash into /sdcard (/data/media/). Use "adb push" for example.
Congratulation
If everything is fine you should be able to mount /cache and /data and to see a big /data volume arround 28 GiB.
Later you will be able to restore your data (Pictures, Music, ...) if you want.
Do not restore TWRP folder because previous TWRP backup are not compatible with the new partition layout.
Now please follow the Manual procedure of this post just below
If you come from OneOfaKind or pure Marshmallow or another ROM than nAOSP
Don't asume that it will work to flash nAOSP if you already are in an similar system on another ROM.
Why ? At least selinux enforced can be your nightmare if you don't flash the ROM correctly.
So re-read from top and proceed with one of the 2 options.
Manual procedure
TWRP ?
The only supported TWRP version is the one included into nAOSP zip files. Please stop to flash something else it will not work correctly. Anyway the FOTA will be flashed automatically with last versions. (previous recovery version should be able to flash a new ROM except in some cases that will be mentionned. With block flashing used, it's now avoid a lot of incompatibility issues but in the doubt please follow the procedure below to have the last supported recovery)
You are not sure about which TWRP version you have ?
Ok we will flash it before starting the update:
- Extract recovery.img from the Zip file
- (Alternative to below procedure: start TWRP/Install/Select image/Select Boot/Reboot)
- Enter the device into fastboot mode
- flash the recovery.img into boot partition like a boot image (fastboot flash boot recovery.img)
- restart the device (fastboot reboot)
- You should be on the recovery (it can be a little bit long to start the first time)
So we can flash now ?!
- Start into recovery
- Backup system/data/boot
- Install ROM zip
- Install GApps zip (except if you DON'T want to install it BUT you will not be able to install it later without flashing the ROM again and without wipe cache/dalvik. see https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0)
- Wipe cache/dalvik
- Reboot
I want Xposed
Flash it no issue reported with it. Be aware that Xposed is only tested with SuperSU installed but there is no issue reported with the embedded Superuser.
I want SuperSU
Donwload the last stable version 2.65. Please don't use the BETA one.
SuperSU comes with 2 differents installation mode : system-less and system. We need on nAOSP to install it in SYSTEM mode.
Infortunatly, SuperSU thinks that it needs to be installed into systemless mode but this is wrong.
So to flash SuperSU 2.65 you need to:
- Mount /system
- Create a file /system/.supersu and put inside SYSTEMLESS=false (don't need to do it with last nAOSP versions)
- Flash SuperSU (You will see system mode displayed during the flashing. If you see system-less that means that you have a mistake on /system/.supersu or /system is not mounted)
I don't want to lose my theme files
Since nAOSP 6.0-b06 and 5.1-b29 you will not lost them. If you want to clean flash without theme restoration, you will have to wipe /system before.
Can I flash ROM + Gapps + SuperSU + Xposed + ... together ?
In fact yes you can flash everything together in one shot but if you are not really familiar with the flashing process divide it in multiple steps to understand what can be wrong. (Note that on my side I'm only testing ROM+Gapps)
If you want to flash everything I suggest you to do it like that :
- Install ROM zip
- Install GApps (Only if you want it. Don't forget restriction mentionned)
- Install SuperSU (Only if you want it. Don't forget the /system/.supersu)
- Install Xposed
- Wipe cache/dalvik
- Reboot
ROM Updater
Are you still reading ? Hope so
Now you are able to flash correctly everything manually. It's not so complicated but ok it is not so simple.
So I propose you an alternative based on ROM Updater.
- Start the ROM (at least nAOSP 6.0-b05-f01 and 5.1-b29 versions)
- Go to Settings/About/Updates
- Enable backup before update (if you want an automatic backup. You should do it !)
- Select Post update
Post Update (before 6.0-b07)
Now you should have a dialog box (Post update) that ask you to enter some text.
Before doing anything you need to know that TWRP use OpenRecoveryScript to permit some automation. Documentation is available at http://wiki.rootzwiki.com/OpenRecoveryScript
I will assume that you want to install Gapps, SuperSU and Xposed. Be free to remove what you don't want. So enter in the field this content :
install /data/media/0/gapps.zip
mount system (SuperSU doesn't mount /system but try to read variables from /system/.supersu)
install /data/media/0/supersu.zip (Don't forget the /system/.supersu)
install /data/media/0/xposed.zip
(of course you will have to change the path of your files to valid ones. Don't forget copy/paste possibility of your explorer to help you. The root path should be common if you have uploaded files on your own/primary android user: /data/media/0/)
Post Update (since 6.0-b07 and 5.1-b29)
Before doing anything you need to know that TWRP use OpenRecoveryScript to permit some automation. Documentation is available at http://wiki.rootzwiki.com/OpenRecoveryScript
I will assume that you want to install Gapps, SuperSU and Xposed. Be free to remove what you don't want:
Select + / select Gapps.zip / OK
Select + / select SuperSU.zip / In the before field put 'mount system' / OK (SuperSU doesn't mount /system but try to read variables from /system/.supersu)
Select + / select Xposed.zip / OK
If you need to add extra commands, use the additional script feature that will display a DialogBox.
That's it
Hope it will be easier for everyone now46nAOSP ROM 6.0 b01 released
This is the first version of nAOSP with Android 6.0.1_r3
The target for this first version is to have pretty much the same user experience for those who come from nAOSP 5.1 b28.
My works is based on @billchen1977 one so big thanks again to him !
Please read carefully this post and specially the flashing procedure !
Release changelog :
- kernel: Wake Gesture support (double tap, sweep). Touchscreen power managed by proximity sensor when screen off
- kernel: governor SMARTMAX by default. OC supported.
- Selinux: Fully supported and configured but will stay in permissive mode for this first release. You can Enforce it safetly and report denied in case of issue (adb shell dmesg | grep denied). Thanks for your help
- TWRP: Support new partition layout and encryption footer length. /data/media will be preserved and used for backup/restore (recovery.img on the OTA zip file)
- WakeUp: Permit to control wake gesture (Settings/nAOSProm/WakeUp)
- ViPER4Android: Sound FX managed by ViPER4Android
- Email: Patched to bypass Exchange Security Policy (No Pin code etc)
- Browser, Music and Gallery2: AOSP version replaced by CyanogenMod version
- Dialer: Materialized Icon added
- Quick Search: Removed. Be free to use another application like Google Search provided with GApps
- GApps: Patch to avoid force close due to permissions (you need to flash the ROM + OpenGapps in one shot and to reboot directly after that)
- Double Tap to Sleep on the status bar
- Minfree setting supported
- Volume/Camera Keys can control track (next/previous/stop) when screen off and music is playing
- Doze: Support adaptive brightness (Ambient Display)
- Notification during Doze: Invert color for dark theme supported (avoid a black text on black background)
- Menu/Home Keys: By default press Menu will launch App switcher and long press on Menu will trigger Menu. Long press on Home will launch Search Engine. This is the modern layout but you can use the old one too
- Power Key: Include Reboot menu (Normal, Soft, Recovery and Bootloader)
- Quick Setting: Can be pull down directly with one finger on the 1/3 right of the Status bar
- Recent Applications : Close all applications button on the right bottom
- Lightbar: Support adaptive brightness, On during 5sec, On/Off with the screen or Off, Notification
- Settings: nAOSProm section that permit you to configure the ROM, to start WakeUp, Layers Manager and SuperSU if available.
- Battery: Menu include the Fast Charge option (Fast charge will be always disabled after a reboot)
- KSM: Kernel Same-page merging disabled by default. (See Settings/nAOSProm)
- Signature Spoofing: Permit an application to fake his signature mainly for Microg/NoGapps (disable by default)
- Adaptive Brightness: Speed up transition when you go to a brighter environment (~1.5s).
- Busybox include
- Partition Layout: /data and /sdcard merged. F2FS is the only filesystem supported for /cache and /data now
Known issues
Encryption
So Encryption is working but don't use it for now because GSM radio will not be able to start correctly and TWRP will not be able to mount /data. You can try just for fun. The flashing procedure take care to prepare the device for a possible encryption in the futur but will not encrypt the device. (go into Settings/Security/Encrypt. Don't forget to set a PIN/passphrase/schema before)
Battery doesn't charge when the device is off on a sector charger
Don't panic if your device hasn't any power and can't start when you press Power button. It is not dead (It happens to me during my test).
So simply connect your phone in usb to a computer. The led should be red/orange. Keep it like this. After few minutes the device will start and you will see the Sony logo. If it display a battery on screen, you can press power button to start the device. Once done, go in airplane mode and wait to have around 10%. Of course you can enable fast charge and plug the device quickly to an adapted charger (1A).
Where is Superuser ?
The ROM doesn't come with any Superuser application. I recommand to use SuperSU (tested beta 2.52 but the stable 2.46 is reported to be fine). I will integrate SuperSU in a next release to avoid this extra step.
Flashing Procedure
PLEASE READ CAREFULLY. This is not a complex procedure but you have to repartition the device if not yet done and to backup your data prior.
Backup:
We will format /data and /sdcard so you need to take backup and put it outside of the phone.
Use your current TWRP to backup your ROM (system/boot/data) into /sdcard
Once done, backup on your computer the /sdcard content (use a file browser with mtp or adb pull)
Recovery/TWRP:
Extract recovery.img from the Zip file
Enter the device into fastboot mode
flash the recovery.img into boot partition like a boot image (fastboot flash boot recovery.img)
restart the device (fastboot reboot)
You should be on the recovery (it can be a little bit long to start the first time)
Repartitionning:
Go to Mount on TWRP gui (uncheck system, data, cache)
Connect on the recovery with "adb shell"
fdisk -l /dev/block/mmcblk0
Copy the output of the command to a file with your backup. It will permit you to revert if needed and to help you if you have an issue (read carefully and you will not have)
Interesting parts are those in bold :
/dev/block/mmcblk0p14 42945 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
It can be not exactly the same values for you depending the size of your /data (p14) and /sdcard (p15)
so here we go (don't forget the section backup. this procedure will erase your data)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-14): 14
Command (m for help): n
First cylinder (769-954240, default 769): 42945
Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240): (just press enter if the default value is the good one)
Using default value 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
Once repartitioning done, do NOT do anything else and just reboot the device (to be sure that the partition table is take into account by the kernel)
Now we will convert /data and /cache to F2FS.
Ext4 is not supported anymore on nAOSProm. You don't need to take care about the 16384 byte to reserve for encryption. TWRP will do it for you.
Into TWRP:
Wipe
Advanced Wipe
select Data
Repair or Change File system
Change File System
F2FS
Swipe to Change
Press Home and do the same procedure to convert Cache partition to F2FS
Once done, again, do NOT do anything else and just reboot the device (required by TWRP)
If you still see 0MB for data after the reboot, try to format data (Wipe/Advanced Wipe/Select Data/Format)
Congratulation, if everything is fine you should be able to mount /cache and /data and to see a big /data volume arround 28 GiB.
FOTA recovery:
Now it is time to put the new recovery into the FOTA partition
Upload the recovery.img into your phone (adb push recovery.img /sdcard/). Yes /sdcard is a symlink somewhere to /data/media
Flash the recovery.img to the fota partition as usual (dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11)
Upload the ROM/Gapps/SuperSU...
Upload the ROM/Gapps and every zip that you want to flash into /sdcard (/data/media/). Use "adb push" for example.
Flash the ROM and GApps
You can now flash the ROM as usual
If you want GApps, please flash Gapps just after the ROM and once done, don't flash anything else and restart the phone. You should be able to configure Gapps without force close. The first boot can be a little bit longer due to application compilation as usual.
Don't restore GApps with TB. I'm only testing OpenGApps micro.
Once everything is working fine, just reboot into the recovery and flash what else you need (SuperSU, Xposed...)
In fact SueprSU and Xposed can be flashed with ROM + Gapps in the same process. If this is the first time that you flash this ROM I suggest you to keep 2 steps and to be sure that ROM + Gapps is working.
Restore your own data
You can restore your /sdcard data (Pictures, Music, ...) if you want.
Do not restore TWRP folder because previous TWRP backup are not compatible with the new partition layout.
Congratulation
That's it
...more to come41
Installing lolipop rom from stock or 4.xx:Plz Can Someone Give me Step By Step Guide For This Noob I wanna Install This Rom
Hope XDA Will Help
1. Unlock bootloader, gain root privileges on current rom! - It's a must have! bootloader unlock bootloader unlock v2
Root
2. Flash TWRP 2.8.7.0 into FOTAkernel. (put recovery.img on sd and type
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11 in terminal emulator (app from google play)) (OR use TWRP Manager/Rashr app on phone - you can find it on google play, - easier way TWRP on googleplay) recovery
3. Reboot phone, copy rom and proper gapps on phone. (dont forget this step or you will have to start from stock rom again) OpenGapps
4. Install Rashr app and flash the kernel (boot.img - from the rom .zip/or rom source or any other suporting android 5.x/doomkernel etc). (easiest way for me, way easier than playing with bootloader itself) (it can flash TWRP as well but i prefer TWRP manager)
5. Reboot phone and keep clicking up volume key during restart, to start TWRP.
6. Wipe everything except sdcard.
6.5 - optional step - migrate all partitions on phone except sdcard to f2fs. (wipe menu in TWRP, theres an option for that, Do it one by one) (there is thread about it on 1st page Xperia S Android Development) here and here is ext4 vs f2fs test
7. Into TWRP, unmount every partitions except the sdcard.
8. Flash the ROM.
9. Wipe cache/dalvik.
10. Flash gapps. (U can combine steps from 8 to 11 by selecting rom and gapps at once in TWRP install menu, but you dont have to do this)
11. Wipe cache/dalvik.
12. Reboot and wait 1-30 minutes. (depends of luck, i have never waited more than 5 minutes but some ppl here had to wait like a half hour till it ends booting, so dont be scared! just wait)
13. Enjoy rom.
Updating rom from 5.xxx to 5.xxx next version, new beta etc.
1. Copy rom and proper gapps on phone. OpenGapps
2. Reboot phone and keep clicking up volume key during restart to start TWRP.
3. Wipe everything except sdcard. ( = clean install)
3.5 Wipe cache/dalvik. ( = dirty install)
3.7 Wipe everything except sdcard and data. I](To save your previously installed apps. I call it "half dirty") [/I]
Choose one of these three, dirty works fine ok 90% times. Sometimes after dirty flash you may encouter bugs or errors (luck dependent?) So always before cryin a river on forum make sure you did a clean flash, if bug still exist than u can report it here
4. Unmount every partitions except the sdcard.
5. Flash the ROM.
6. Wipe cache/dalvik.
7. Flash gapps.
8. Wipe cache/dalvik.
9. Reboot and wait 1-30 minutes.
10. Enjoy rom.
Hope it helped. Next time use search or please pin my post somewhere because it's way easier to install this way than by following OP instructions. No offense @mickybart
But your description is not easy to understand to common non xda maniac users. And i have to say its hard to find any allinone guide here to do/read about most common things needed to change rom. Well I remember how hard it was for me when i started playing with custom 4.1.2 roms.
Cheers!
PS. After "few" edits I dont know what more can i say here, so feel free to correct my mistakes or add new points
PS2. And to all newbies I strongly suggest to read all guides I have linked here before you start doing anything.
Read all, than start to follow step by step instruction so you wont get stuck somewhere.
PS3. English is not my native language, I apologize for any mistakes I did. (correct me if they are terrible - I'll edit them)
PS4. Most important one? If you've bricked your phone please don't blame me for that. It's like "youknowhat", it happens
There are many ways to fix it. Tutorial how to repair bricked phone.Don't be scared to fail, but if you stick to tut you 99% wont.
