go to 7.0 thread for information
go to 7.0 thread for information
nAOSP 6.0/5.1 Ultimate Flashing Procedure
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)
That's it
Hope it will be easier for everyone now
please, i need help, i was with pure AOSP marshmallow r2 and didn't have problems, but after i flashed the rom of NAOSP marshmallow b10 i lost my eMMC storage, i only have my 2 GB of internal memory, the other 28 GB doesn't exist, i flashed the b12, b13 versions and nothing, i don't know how to recover my eMMC Gbs of the LT26i, can anyone help me?
Hey guys finally i decide to repartition my device coz android 7 has already been landed here. recently Im on nAOSP 5.1 b28 version with recovery 3.0.2
what i m not getting is, do i need to extract boot n recovery image from nAOSP 6.0 b13 zip file or just recovery.img only coz m going to flash nASOP 6.0 b13. And in partition table of last cylinder our devs say if default value is ok then just press enter or do i have to put the default value no. m lil confuse . Lastly after changing F2fs sytem do i need recovery.img again to flash or simply can go as usual install procedure ROM,GApps,wipe cache..sorry for being noobs.
Sent from my Xperia S using XDA-Developers mobile app
nageswarswain; [SIZE=1 said:---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------[/SIZE]
[/COLOR]
Press enter for default value..
Don't need to flash recovery again if you already flashed to fota
yes enter means it will take the default valueThanks @nageswarswain buddy ..press enter mean no need to put value yes ? n abt kernel n recovery flash from zip.. do i need or not ?
Sent from my Xperia S using XDA-Developers mobile app
Ok buddy thanks for ur time ..☺☺lastly one thing i should uncheck all in mount twrp gui section..yes?yes enter means it will take the default value
dont need to flash kernel as it will be flashed while you flash rom.But you need to flash recovery.img to fota partition.The guide by mickybart is really easy so read it couple of times and ask if any doubts...
Ok buddy thanks for ur time ..☺☺lastly one thing i should uncheck all in mount twrp gui section..yes?
Sent from my Xperia S using XDA-Developers mobile app
Thanks @nageswarswain friend I ll let u know after Im done.[emoji4]
thank you very much, i followed the procedure and now i have my 28 Gb of eMMC again!! :good:
SafetyNet / root ...
I take a look and I disable everything on my device (root, adaway, unsecure apk install etc) but the device can't pass the SafetyNet check.
In fact custom ROM are not able to pass SafetyNet.
https://koz.io/inside-safetynet/
https://koz.io/inside-safetynet-2/
Unroot the device do not permit to use Android Pay for example.
So Google prefer to trust official ROM not updated since 3 years. So for now, we have no solution to pass those checks except to go back to stock ROM.
So for banking applications that are using SafetyNet, you need to go back on stock ROM and to modify the boot.img to support system less root with unroot support with magestik for example.
EDIT: After digging, seems that Android version not released on a device can't pass the test. There is an open bug about that on microg.
read (last comment if you want a sum-up and search strings #90): https://github.com/microg/android_packages_apps_GmsCore/issues/181
and: https://github.com/microg/android_packages_apps_GmsCore/issues/90
Hi @mickybart,
Thank you for the info, I read it all even though I'm no fully understand (I'm not programmer). FYI, Magisk does not support Sony device. If you go to Magisk thread here http://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382, under the "Currently Known Not Working Devices" he's looking for help to modify Sony boot.img. I think maybe you can help him.
I would like try microG, does this rom support signature spoofing?
Lastly, this is only for your information. I unroot my phone and remove xpose module, Safetynet test fail however I'm able to login to pokemon go apps. Im not sure is this a bug or the Safetynet feature might be different between apps.
Sorry if bad english
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