Related
Do I have root?
First you install the unlock APK, unlock it...Install goo beta, Install Open-Script Recovery, reboot and ill have TRWP? and be able to install custom roms?
IM READY TO JUMP SHIP!
You have your recovery to install everything.....
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
It has its own recovery? or do i need to install one...
David522d said:
It has its own recovery? or do i need to install one...
Click to expand...
Click to collapse
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
also a video showing you how to flash a custom rom, with TWRP and goo manager, is there also
demandarin said:
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
Click to expand...
Click to collapse
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Anyone ?
I don't know about goo manager but I flashed cwm touch with fastboot (normal cwm didn't work and twrp wasn't out)
Sent from my sgs2 running cm9
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Yeah steps sound good. you could always flash a ROM that has root. I dont think you need root to install twrp. Double check though. post in twrp thread to make sure.
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
David522d said:
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
Click to expand...
Click to collapse
There is nothing that will work 100%, but its pretty close, maybe 98%? Anytime someone does anything with the bootloader, recovery rom, or OS rom, there is a chance for bricking: interuption in the write process, loss of power, corrupted dl (crc check should catch most of those). If your worried about bricking it, leave your TFP stock and await the OTA's - that way if it gets bricked by Asus then they are responsible and you havent nullified your warranty.
Unlocking the bootloader allows the use of non stock bootloaders/recoveries to be installed and used. From the new bootloader/recovery, you can install a rom that either has root, or not. You don't even have to change roms after unlocking. The 2 are independent.
Right -
Unlocking with the APK does not root or in any other way modify or prep the prime for what you're about to do. Depending on your stock ROM revision this is either very easy or a complete pain in the ass, I'll provide both versions:
For Stock ROM ending .15 or earlier -
* DO NOT RUN THE GOO IM.MANAGER FIRST. Follow these steps below.
* Download Sparky's APK to root - it's in the development forum for the TF Prime. Run it. This will get you root access on the system. It's automated and practically idiot proof, just follow the on screen instructions.
* If you're going the Team Win route, once rooted, load up the Goo.im manager, then follow the instructions as per a rooted installation for getting TW Recovery into place. This is pretty painless really and works automatically, approve the Superuser permissions as required. Once the recovery is in, you can reboot into it and then get with the flashy.
-----
If you're on the Stock ROM ending .21, you're going to have to do what I did. As you're already unlocked using the BLOB files to downgrade -will- result in a hard brick. SO!
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
Hope this helps.
This whole blob thing is new for me since i have always insta-rooted, and CWM'ed any android device i get; but from what I've gathered, it is used by ASUS to lowlevel write the os on locked systems, similar to the way nvflash dumps img's directly to the memory. Once your unlocked with the CWM or twrp, then you can no longer use blobs, just the rom zips. The recovery rom handles the unpacking and dumping of the kernel and OS into the appropriate partitions. Some roms are zipped with install scripts that wipe your cache, user space and dalvik - but its always a safe bet to do that anyways.
Nice writeup Hobbesian
Well, some blobs are fine, but generally they're strictly either Team Win Recovery or Clockwork mod recovery suites, and they need to be slipped in using fastboot (I believe ROM manager and GOO managers use their own scripts to handle installation) as a rough rule. The "big" BLOB files which Asus puts out are a guarantee to hardbrick an unlocked device (some days I wonder if it would kill Asus to offer a route to re-lock and re-stock a device on the proviso that if you brick it doing so you're still out of warranty).
That said - Virtuous Prime is definitely an excellent first step into Custom ROM tinkering, it gives you root and all the associated useful features, as well as the ability to start experimenting with more feature heavy ROM builds such as Cyanogen and AOKP Cornerstone. They're even nice enough to include a partially tweaked build.prop which saves you a lot of the work in modifying that.
I should point out my guide is relevant only if you already applied the unlock APK to your system, if you haven't done so, there's alternative routes including the downgrade blob option to get root without unlocking your device.
paddycr said:
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
Click to expand...
Click to collapse
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
David522d said:
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
Click to expand...
Click to collapse
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
EDIT: if you're in fastboot and you cannot get adb to recognize your prime you need to install the correct drivers for your pc/mac. Hobbesian describes how to do this a few posts above this. In his nice write up he also describes how to flash TWRP directly from fastboot. If you want TWRP, follow his instructions since you'll have less messing around to do.
paddycr said:
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
Click to expand...
Click to collapse
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
David522d said:
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
Click to expand...
Click to collapse
Yes, all of the roms will have root. Hit my thanks button if it works for you
paddycr said:
Yes, all of the roms will have root. Hit my thanks button if it works for you
Click to expand...
Click to collapse
Would it be easier to install CWM, then install TWR
David522d said:
Would it be easier to install CWM, then install TWR
Click to expand...
Click to collapse
I think both ways are the same. There's no correct answer to that. It depends on whether you would prefer to use CWM or TWRP.
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
kokorolove said:
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
Click to expand...
Click to collapse
You need to unlock to flash a custom kernel which would be needed by the cm12 to run. So first.
1.Backup drm keys
2.Unlock BL
3. Flash CM kernel via fastboot
4. Flash CM Rom via recovery.
Sent from my SGP621 using XDA Free mobile app
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Cyberratchet said:
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Click to expand...
Click to collapse
I guess you should just flash the kernel via fastboot after unlocking the bootloader, that would eliminate the need to flash a recovery. It's hitting 2 birds and one stone and besides CM uses a different kernel than stock so later you would really need to flash kernel.
Sent from my SGP621 using XDA Free mobile app
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
I'm also curious about this.
Right now, I'm trying to download the Flashtool program from Sony, but apparently, you need to "register" for it. Where did you guys download your Flashtool from?
Cyberratchet said:
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
Click to expand...
Click to collapse
Correct, make sure the kernel is compatible with CM
Sent from my SGP621 using XDA Free mobile app
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Cyberratchet said:
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Click to expand...
Click to collapse
I ran into the same problem usin the cm12 nightlies from 27th march 2015:
Sideloading would not work because the tablet is not recognized by the computer. I tried with Windows 7 and gentoo Linux.
Installing from the sd-card in recovery mode was also not possible due to a error of missing "/misc".
I solved the problem by manually choosing the driver in Windows 7. I booted the tablet into recovery. Choose update using adb as detailed in this post:
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534
Then I found the device in the windows device manager. Here I manually choose the adb driver that I installed earlier from the flashtool package. After that the device was correctly recognized by Windows and I could Sideloade the cm12 image.
Hey Guys,
as far as i could find out so far, you use TWRP to flash a Custom Rom from the Tablets Recovery Mode, this requires a rooted device, and to do this you flash a prerooted rom somehow, which includes TWRP already, which you then use to flash the rom you actually want on your device.
Another possibility was to flash a Kernel (with TWRP?) to get the same results...
Now I absolutely can´t find a tutorial for dummies, to do that, or find the required files.
After i found it kinda complicated to unlock the bootloader, since most of the tutorials didn´t even mention you need advanced mode and a special Google USB Driver from Sony´s Developer Page, to even get that working, i would really appreciate if someone could give me a step by step with links.
If a tutorial exists, pls give me a link as well, cause i looked the whole day yesterday, and found jack.
cheers
yes, you need to do all that. i just went through this yesterday and used this tutorial:
https://forum.xda-developers.com/showthread.php?t=2747676
once you are unlocked, follow the instructions for your rom, usually to flash the boot and recovery images with fastboot. two things to watch out for though, if you are using an oreo rom make sure your twrp version is 3.2 or better, secondly, if twrp give an error where it cant mount the partitions to wipe them use the change format option under wipe/advance to change to ext4 (which essentially re-formats the partition) and you should be good to flash the rom after that.
here is another tutorial to help get adb, fastboot, and the drivers up and going:
https://forum.xda-developers.com/showthread.php?t=2588979
answer yes to everything, i can't remember if i loaded in sony specific driver on top of that or not.
goodluck!
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
BootLoader needs to be Unlocked and of course Usual T&C's apply. Use at your own risk don't blame me if you brick your device or lose your valuable data etc etc.
So what's different about this ROM??
Ok so I have been working on this for quite sometime during the little free time I have.
The ROM is my own preferences only and it may not be to everyone's tastes so you're quite welcome to take it, leave it, add to it, strip it, mod it, etc, etc.
The ROM ditches the not so useful stuff of Sony's but retains what I consider the good stuff like Music Album and the Camera.
Where possible I have replaced the Sony stuff with Google's Stuff which receive regular updates and keep the Rom looking fresh.
The trick to this ROM was finding a good balance without breaking anything in the process which I think I have now achieved.
This is a list of the visible apps installed, there are quite a few none visible Sony & MediaTek apps still installed that relate to settings functions and some background stuff.
Google Apps:
Clock
Calculator
Contacts
Calendar
Chrome
Drive
Files
GMail
Hangouts
Maps
Messages
Phone
Photos
Play Store
Wallpapers
YouTube
Sony Apps:
Album (Please disable this in /settings/app It will constantly search for other apps I removed otherwise. Use the pre-installed Google Photos app instead)
Camera
Music
Radio
Swiftkey (Left this in because I like it)
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Flashing InstructionsThe ROM is packaged as a TWRP Backup containing system, oem, boot and recovery (TWRP)
First you will need to install this TWRP HERE which has oem partition support and others too.
1. Install the TWRP Recovery above.
2. Boot to the new TWRP and backup oem, system and boot then move it to a safe place off device or to and external sdcard. Same goes for anything you value like pictures, music, etc, etc
3. Once you have Backed Up everything FORMAT your /data partition using TWRP. Wipe > Format Data (type yes to confirm)
When that's done choose Wipe > Advanced Wipe and select Dalvik / ART Cache and Cache after that from the TWRP menu choose Reboot and select Recovery
4. When back in recovery swipe to allow then do a quick Backup of any small partition like boot or recovery. This will just create the folders on your clean data partition unless your default backup is external sdcard.
5. Now extract/unpack the downloaded ROM from HERE and move the folder SonyXA-Android-One to TWRP/BACKUPS/Sony_XA/
6. Once done go to TWRP Menu and choose Restore and select SonyXA-Android-One
7. Once done go to the Reboot Menu and Choose Power OFF
8. Wait a few Mins and power on normally.
First boot can take a while but if you see the boot animation start everything should be fine so go have a brew while you wait.
Play Services will want to Update so allow that then most apps will need to be updated to the latest version.
Arrange the app icons and widgets on your Home screen and choose a nice wallpaper or live wallpaper and your done.
Hopefully everything will be quick & smooth. :fingers-crossed:
The ROM is not pre rooted so Root in the usual way using Magisk
PS: Ensure you check your app permissions and Default APPS the Phone app is Not the Default one even though it's the only one installed so please choose it Manually along with any others that do not set by themselves.
Thanks
Some Screenshots
{
"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"
}
......
.....
.....
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
z4Android said:
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
Click to expand...
Click to collapse
Thanks. :good:
Be sure to let me know how you get on with it. :fingers-crossed:
I am not sure where you are from or which version of the XA you have but I am sure the ROM could be easily adapted for your own version.
All I would need would be a backup of your /oem & /boot partitions and the build.prop from your /system .
There is a modem config file in /oem which states telefonica uk I am unsure if this has any effect at all as I am sure I have flashed firmware from other European regions with no noticable effects.
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
z4Android said:
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
Click to expand...
Click to collapse
Hi, Your version should have no issues as it's identical to mine :good:
As for TWRP yes it does have issues with Unmounting /system for some reason
So if you mount /system from the Mount Menu TWRP or auto mount system you will not be able to Unmount mount it due to the "device or resource busy" error
If this happens you will need to ensure auto mounting is unselected and reboot to recovery from the Reboot menu.
I will look into the TWRP issue later to make things easier
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Bluesummerz said:
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Click to expand...
Click to collapse
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
bigrammy said:
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
Click to expand...
Click to collapse
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Bluesummerz said:
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Click to expand...
Click to collapse
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
bigrammy said:
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
Click to expand...
Click to collapse
And that is exactly why I like these forums, if you provide enough insight to a question, you'll get the full-spectrum answer, splendid!
And yes, confusing things is in my nature, also I might find it troublesome to know when I get like off topic here, so please stop me the moment, it would be better to switch to pm.
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
PS
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Bluesummerz said:
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Click to expand...
Click to collapse
Correct they are essentially a dd backup of the entire partition in question.
[Edit] To expand TWRP does not convert anything so if those partitions had the stock recovery & boot .elf format on them when the backup was performed they will still be .elf's which are not fastboot compatible. Those in my ROM have already been converted to .img format which is compatible with fastboot.
If you ever got stuck for some reason then you could simply use FlashTool to restore the Stock Recovery (fotakernel), Boot, OEM & System
Bluesummerz said:
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
Click to expand...
Click to collapse
Correct.
My Phone is restored using the F3111_33.3.A.1.97_1302-4476_R2B.ftf (FlashTool Firmware) and the ROM is based on this version.
Try to use a 33.3.A.1.97 if possible as I know that works.
Bluesummerz said:
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
Click to expand...
Click to collapse
Fastboot the recovery and the boot then You Simply need to follow the Flashing Instructions from step 2 in the first post from this point.
It is /data that gets wiped manually BTW (By The Way). TWRP will take care of the /system during it's restore tasks.
Bluesummerz said:
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
Click to expand...
Click to collapse
Yes providing you did everything correctly I see no reason why it would not work for you unless your device is a extra special Sony XA
Bluesummerz said:
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Click to expand...
Click to collapse
It stands for a Work In Progress.
The term work-in-progress (WIP) describes partially finished goods awaiting completion.
Does it has VOLTE support
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
altmash mirza said:
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
Click to expand...
Click to collapse
Not sure about VOLTE
If anyone did try this ROM nobody reported back
I guess this device is dead now as there seems to be very little activity which is a shame
drm fix working in case we use sony backups?
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
z4Android said:
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
Click to expand...
Click to collapse
Thanks for the feed back. :good:
Sorry no Oreo or Pie unless we fix the Ril issue on none Stock custom ROM's like the Lineage 14.1
bootlogo
bigrammy said:
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Click to expand...
Click to collapse
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Codetrr said:
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Click to expand...
Click to collapse
If your TWRP is not working you should fix this FIRST before doing anything else.
Warning: The logo partition is very important and as I said before it's part of the secure boot chain so if the logo does match the signature and or hash the ROM will boot loop or soft brick it did for me when I tried to change it so be very careful and make sure you can recover the phone with FlashTool.
To find partitions on Mediatek devices use this cmd.
Code:
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
This will give you a list of all partitions by-name and the actual dev block.
The logo partition is
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
So to flash the logo.img with dd you would copy the logo.img to your internal sdcard and use the following cmd.
Code:
dd if=/sdcard/logo.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
Sorry I cannot test your logo's because my wife use's this phone now as her everyday phone so she would not let me mess around with it now.
Akinimaginable said:
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Click to expand...
Click to collapse
The ROM is just stock ROM with most bloat ware removed and Google alternatives installed. I would recommend not to use the Sony "Album" app as it requires some other Sony apps which I removed and it continually looks for these apps. So just disable it in /settings/apps and use the pre-installed Google photos instead.
Also ensure you manually set the Phone app as the default dialer even though it's the only one or you will not be able to make or answer calls.
11 year girl! I would not worry they probably know more than we do at that age :laugh:
Yes it should be 100% compatible with a European Xperia XA F3111 ?
How to do this ?
I just rooted and flashed my old LG, and probably the by the "good" method. So if you have a link for the way to root and flash this phone, you'll make me very happy. I know that I have to go in adb flash TWRP as recovery, go in recovery by resetting the phone. Once this is done I have to wipe the phone, put the rom (and opengaps ?). And finally flash the rom. But previously I saw a lot of commands and warning so I'm a bit confused ?
Thanks for your attention ??
Hi,
I am trying to put lineage on my Redmi Note 9 Pro.
However, I am getting the following message when I open Magisk Manager.
Attestion Failed | basicIntegrity CHECK | ctsProfile NOT CHECK | evalType HARDWARE
I tried follow a tutorial on youtube to fix it, however I cannot Link it. It was with the app Terminal Emulator.
Is it still possible to install lineage? If yes, how? If now, can I still return to my phone as normal?
Kind regards,
Q
@Qurbey
It's not required to install Magisk before it comes to install a Custom ROM as Lineage OS. All what is needed is
that phone's boot-loader got suceesfully unlocked - that in most cases will void OEM's / Carrier's warranty -
obtaining a copy of a Custom Recovery like TWRP matching at 100% your phone
obtaining a copy of Lineage OS ROM that at 100% is matching your phone
having the ADB / Fastboot drivers matching your phone installed
jwoegerbauer said:
@Qurbey
It's not required to install Magisk before it comes to install a Custom ROM as Lineage OS. All what is needed is
that phone's boot-loader got suceesfully unlocked - that in most cases will void OEM's / Carrier's warranty -
obtaining a copy of a Custom Recovery like TWRP matching at 100% your phone
obtaining a copy of Lineage OS ROM that at 100% is matching your phone
having the ADB / Fastboot drivers matching your phone installed
Click to expand...
Click to collapse
Thanks jwoegerbauer.
The boot-loader is unlocked with miflash_unlock.exe
I used following tutorial and software to flash TWPR and Root. Should I have not rooted the phone and only flashed TWPR? I am getting lost in all the vocabulary.
https://www.youtube.com/watch?v=PSNe0WkmV6c&t=313s
I am planning to download this version of Lineage.
https://forum.xda-developers.com/redmi-note-8-pro/development/rom-lineageos-17-1-t4072137
Is there a tutorials you would recommend to execute this step? I prefer a video, since I am new to this.
Will I be able to install all software on this phone, or not any more because of my previous actions?
Qurbey said:
Thanks jwoegerbauer.
The boot-loader is unlocked with miflash_unlock.exe
I used following tutorial and software to flash TWPR and Root. Should I have not rooted the phone and only flashed TWPR? I am getting lost in all the vocabulary.
https://www.youtube.com/watch?v=PSNe0WkmV6c&t=313s
I am planning to download this version of Lineage.
https://forum.xda-developers.com/redmi-note-8-pro/development/rom-lineageos-17-1-t4072137
Is there a tutorials you would recommend to execute this step? I prefer a video, since I am new to this.
Will I be able to install all software on this phone, or not any more because of my previous actions?
Click to expand...
Click to collapse
As I can see you modded / hacked your phone in a way that is completely unnecessary in order to flash a Custom ROM.
To be honest, I can't tell you whether this Lineage OS is the correct one.
If a ROM gets flashed, then you're free to install any user-app of your choice on it.
jwoegerbauer said:
As I can see you modded / hacked your phone in a way that is completely unnecessary in order to flash a Custom ROM.
To be honest, I can't tell you whether this Lineage OS is the correct one.
If a ROM gets flashed, then you're free to install any user-app of your choice on it.
Click to expand...
Click to collapse
I have removed the app Terminal Emulator.
But now my phone is locked again. It is not bricked. However I cannot acces twpr recovery any more.
Should I unlock it again? Is that with the 168 hours waiting time agian or not?
Then flash Twrp, without rooting.
Install Lineage
Thanks.
@Qurbey
By installing TWRP you have deleted phone's Stock Recovery. Means now you can no longer flash the original Stock ROM in order to then re-start flashing Lineage OS. It was your decision.
Don't have the phone in question, hence can't help you any further.
jwoegerbauer said:
@Qurbey
By installing TWRP you have deleted phone's Stock Recovery. Means now you can no longer flash the original Stock ROM in order to then re-start flashing Lineage OS. It was your decision.
Don't have the phone in question, hence can't help you any further.
Click to expand...
Click to collapse
Thanks, jwoegerbauer.
That is unfortunate. There is no workaround this? Does this mean I am stuck with the xiaomi interface forever?
Would you advice to remove Magisk from the phone?
@Qurbey
My last 2 cents here ( I no longer participate this thread ):
Get rid off of all mods/hacks you made to phone's Android, will say restore phone's Stock ROM by means of MIUI Flash tool.
Then do NOT install TWRP, but simply boot into it - via FastBoot driver
Finally flash Lineage OS via TWRP
jwoegerbauer said:
@Qurbey
My last 2 cents here ( I no longer participate this thread ):
Get rid off of all mods/hacks you made to phone's Android, will say restore phone's Stock ROM by means of MIUI Flash tool.
Then do NOT install TWRP, but simply boot into it - via FastBoot driver
Finally flash Lineage OS via TWRP
Click to expand...
Click to collapse
Thanks for all the help.