Related
Before I begin, Mods, PLEASE pin this. I (when I was a noob) had absolute difficulty installing ROMs. This is very noob-friendly, fixes Status 7 errors, and is easy to follow.
Alright friends and future flashers. I used to have difficulty installing ROMs. Now that I know how (after going through numerous tutorials), I'd like to make it easy for ALL of you. Enjoy your Custom ROM!
Before beginning, you need Android's SDK,Flashtool and The latest Official firmware.
If ever your phone needs to install drivers, let it install, don't unplug the phone or whatever.
And, battery at least 30%. Mine does it at even 20% without issues, but just to be safe.
Step 1: Revert to Stock
You don't need to downgrade. After flashing the latest stock kernel, I have flashed every single GB and ICS ROM in existence without issues, so you don't need to flash a specific one. But, latest one tends to be more stable. Here's what you do:
Get the latest Global ftf for your phone. Then, flash it using Flashtool. I won't go into specifics, but PM me if needed
By Now, you should have a stock EVERYTHING. Boot up the phone, run through the whole set up process. Once you are done, you need to get your IMEI number. Do this by following the steps here.
In the end, you should have the bootloader unlocked. If you come up with something like bootloader already unlocked, then you are good to go. Now onto......
Step 2: Preparing your Flash.
Download the ROM of your choice. I'd recommend FXP's Unofficial CyanogenMod9 as it has the best stability and no ICS Multitouch issues. If it is GB, any ROM will do. Most of them are stable.
Now, in the case of CyanogenMod, they often come with their own custom Kernel. It is in the zip file, known as boot.img, and you simply extract it to your platform-tools folder in the android-sdk folder you downloaded to unlock the bootloader. This is also true for some MIUI ROMs I've come across. Read their forum posts for more info on which kernel to use.
Copy the ZIP file to your sdcard. It does not have to be the root of SDcard, anywhere will do.
By the end, your Custom ROM's ZIP file will be in your SDCard, and the kernel file (a.k.a. boot.img or whatever_the _kernel_name_is.img) will be here:
32bit Windows: C:/Program Files/Android/android-sdk/platform-tools
64bit Windows: C:/Program Files(x86)/Android/android-sdk/platform-tools
Now we can
Step 3: Flash your Custom ROM
In the folder above (depending on OS version) press Shift+RightClick. Options will show up. Select "Open Command Prompt Here". A Command Prompt will open (duh).
Turn off your phone. Wait 10 seconds. While plugging in your phone, press the Menu button (the Right button). The LED Indicator should turn blue. This shows your in fastboot mode. If it starts to boot, rip out the battery and try again. DON'T STOP PRESSING UNTIL IT TURNS BLUE.
Now, type EXACTLY AS FOLLOWS, ONE AT A TIME. Just type in the lines with the "-" before it, but don't put in the "-" when typing it. The line underneath in brackets is an explanation, so you understand what is happening.
-fastboot devices
(This is actually a quick test I do to see if my phone is connected in flash mode or not. If nothing happens, it is not in flash mode or the drivers are installing)
-fastboot flash boot boot.img
(This is telling fastboot to FLASH the BOOT partition of your phone with the file specified. If you are using a different kernel, simply replace boot.img with the name of the kernel, ending with .img and wait for it to finish. Won't take long)
-fastboot reboot
(This causes the phone to reboot)
Now, while it is starting up, keep repeatedly pressing the Volume Down button until you are in ClockWorkMod Recovery (Assuming you are using it. CWM is the most popular and most kernels use it) Then, If you choose to, make a backup. I personally don't, as it is not too big an issue and I never revert to an old ROM anyway.
After that, choose Factory Reset. This will remove ALL data in your phone except your Stock ROM. Then, Clear Cache. You might've noticed it already did that when you Factory Reset, but this is for safety. Finally, in advanced, Wipe Dalvik-Cache and Wipe Battery Stats. I do this all the time for safety.
Now, the fun bit. GO to Install ZIP from SDCard. Select Choose ZIP, find your ROMs ZIP file, and install. It might take awhile, but not too long. Just be patient. When it finishes, flash anything else the ROMs forum post says to flash (Gapps, Patch, etc) and select Reboot Phone.
Step 4: Done!
Your phone will start up. First time is always slow, but this WILL WORK. Congratulations. You now have a Custom ROM
If you get a Status 7 error while flashing a ROM, reboot recovery and wipe everything again. If that doesn't work, flash official firmware and try again.
Credits to:
-Google: Providing Android SDK and Gapps
-Androxyde: Flashtool
-Madfysh: List of Official ICS ROMs
FXP: Creating CyanagonMod9
-And YOU!
P.S.: If you're confused, or feel this could use something extra PM me.
And uh, if it needs to be moved, please do so. Thanks!
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
PLEASE Don't spoil the mood man!!
This is a development section where even Noob Devs know how to flash a Custom Rom!! PLeaseee Pleaseeee ... Move it
Alright man. How would I move it? Cause, I only RECENTLY started being active on the forums.
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Reck1993 said:
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Click to expand...
Click to collapse
Okay. I will add an easy rooting instructions to it.
kormatoes said:
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Click to expand...
Click to collapse
Thanks kormatoes. Could you gimme some of the unnecessary/dodgy parts?
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Madfysh said:
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Click to expand...
Click to collapse
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
lalit387 said:
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
Click to expand...
Click to collapse
As it is, I am attempting to code a batch file to automatically run the entire flashing process, including kernel and ROM. Having a small issue where it does not wipe dalvik and cache. It also doesn't flash the custom ROM
There are so many topics on how to root, flash and install the X10, but they're all pretty old and most of them are based on Sony PC Companion, that, as far as I know, isn't available for Linux.
I am guessing that people who are upgrading their X10s to the newest FeraLab versions can do the entire procedure in the blink of an eye. So can you please help me make a quick checklist of the required steps? I'll dig on my own for all the details required by each step.
I just need a "structure" to follow. Let's say a "broader view".
A few days ago I've received an X10i with Android 2.3.3. running on it.
It hasn't been rooted.
How can I check if the bootloader is locked or not?
Note: I've no data to backup on the phone. It's all in its factory default settings with no content on it.
I've downloaded and I'm currently running the latest version of Flashtool on Arch Linux (64bit). It works.
I've also download FeraLab Kernel v28-beta4.
Then I've FeraLab Firmware v40. I couldn't get the latest version (v40.2) since the uploaded.net link doesn't work, at least not for me.
Now, this is what I came up to after reading the most recent threads that I've found here.
Please correct me if I am wrong.
1) Should I click on the "Flash device" icon (top left) and then "flash" the .ftf file of the FeraKernel?
2) Should I "push .ko files to /system/lib/modules/" and restart?
3) Now should I install the v40 ROM using the same procedure of step 1)?
4) In order to do that I think I've to follow FeraVolt steps, right?
-> Boot-up to CWM6 Recovery & just straightly install ROM following AROMA installation wizard.
-> After installation, boot your phone, pass setup wizard and wait 2 minutes. Reboot again.
-> On second boot wait not less than 2 minutes again & reboot.
-> Done. Do a reboot after you've configured your phone. Hit 'Thanks' button and rate this thread if you like my work or consider donating me to let me to have a good dinner.
Am I about to follow the right steps? Or am I doing something wrong?
What about rooting the phone and unlocking the bootloader?
Thanks for helping a n00b!
First, download both the rom and kernel. Put the rom on your sd-card and the kernel (.ftf) inside the firmware folder in flashtool.
Root the phone, then flash the kernel, and from the recovery instal the new rom (don't forget to make a backup first).
Hope this clears it up a bit.
Sent from my KIS PLUS using Tapatalk 2
So I've been reading these forums for the last 3 or 4 hours and I seem to be in an endless loop. I'm hoping people can help me untangle this mess, and perhaps I can write this up for others to enjoy.
I just picked up a HDX 7" with 13.3.0.5 on it. I dont care about the stock software, my ultimate goal is to get CM12.1 running on it.
So I see this ROM is available...
http://forum.xda-developers.com/kin...ent/rom-cm-12-unofficial-apollo-thor-t3050199
So from previous ROMing I know I need to get TWRP installed to get that running. So I find this post...
http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
However, first step is to unlock the bootloader... so I find this...
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
That says the first step is to install the "vulnerable" 13.3.2.3 firmware. Ok great...
http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
That first step there is to install TWRP :/ Seems we have an infinite loop here. Can anyone explain the proper procedure for going from stock 13.3.0.5 to CM12.1 using these procedures?
TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.
derpadoodle said:
TWRP can be installed on your current firmware, its just recommended that you use 3.2.3.2 as a base since it's the most up to date exploitable firmware. You can update without TWRP if needed, just place the Amazon update bin in the root of your internal storage and check for updates with WiFi disabled.
Click to expand...
Click to collapse
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).
Davey126 said:
@insodus - I agree with derpadoodle and have puzzled over the conflicting guidance myself. I can also confirm flashing the latest TWRP on 13.3.0.x is fine followed by the 3.2.3 bootloader (only) upgrade. You can then proceed with unlocking your bootloader and installing CM12. Gab a nandroid or two along the way just in case (best done from within TWRP).
You will obviously need to root your current firmware before proceeding. Don't forget to block OTA if you plan to enable wifi anytime before dumping stock. Also note a few things still aren't 100% in CM12; CM11 might be a better short-term choice and can be installed on with a locked bootloader (unlocking is still recommended).
Click to expand...
Click to collapse
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image
insodus said:
Ok, so if I dont care about the amazon firmware because I want CM only... I still should update to 13.3.2.3 before unlocking?
Click to expand...
Click to collapse
The 13.3.2.3 bootloader update is quick and easy. This code remains on your device even with other roms. So yeah, you should apply the update.
insodus said:
1- Root it (any preferable method? towelroot?)
2- Install TWRP
3- Update the bootloader to 13.3.2.3
4- Unlock bootloader
5- Flash cm image
Click to expand...
Click to collapse
My preference is HDX toolkit as it avoids wifi, installs SuperSU and has other handy options. However, it is a tethered solution which can be a PiTA. Towelroot should work fine too; I have used both.
Although it involves little risk bootloader unlocking is not for the faint of heart. You can always flash CM11 after step #3 and play with that while researching the bootloader unlock procedure. A recent tutorial by travanx captures most of the steps in one post. You'll want to start about halfway down.
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
rajdude said:
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
Click to expand...
Click to collapse
The only reason to use that guide is to backup ta keys for whatever reason you'd want to do that.
If you're after root on stock ROM the single easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. Solid marshmallow with root goodies. Xpower has everything and is deodexed and ready for xposed framework.
just a little more clarification please?
civicsr2cool said:
.....easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. ......
Click to expand...
Click to collapse
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
rajdude said:
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
Click to expand...
Click to collapse
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
still a little confused
civicsr2cool said:
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
Click to expand...
Click to collapse
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my day job). In Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
rajdude said:
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my d Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
Click to expand...
Click to collapse
Android is Linux, to gain root in the ROM you have on your phone currently all you need is an unlocked bootloader to run SU, but then you'll be left with a phone that still needs a customized kernel to keep root and a DRM fix for the camera. Xpower 3.0 is that package.
You could really benefit from reading more. Google up on dm-verity and Sony Ric, and fastboot/adb for a little better understanding of what you're getting into without a pre compiled ROM. Messing around with any Android you'll have the majority of the same steps, unlock bootloader with fastboot, flash Supersu, customized kernel.. Etc
Why use a stable compiled ROM?
Let me list down and explain to you why it's best to use a stable compiled ROM. But first you need to understand these few things before you decide to unlock your bootloader and root.
Before Sony Z models kicked in, every rooted Sony device are still able to retain all the features that came together with the phone before it was rooted. When Sony introduce the first Z model, they start to create these things called DRM keys. DRM keys are unique algorithm (i guess i should put it that way) which is attached to every phone the same way an IMEI number is attached to every phone. In short, my DRM keys cannot be used on your phone and vice versa.
DRM key: It's a unique algorithm that holds all the unique features that an unrooted Sony phone boast such as camera quality, X-reality, High Res Audio etc etc.
The moment you unlock your bootloader, that's the moment your DRM keys will be lost. But don't panic, the wonderful devs on XDA have prepared a tool to backup your TA partition (a partition that contains your DRM key) for your own convenience if you want to relock your bootloader.
Then recently Sony/Android come up with new features called Sony RIC and dm-verity. (You may Google what these are all about but to my understanding it is placing limitations to people who root their phones to meddle around with the system settings of thier phone)
With all these "hurdles", it have taken some time for devs here to find a work around and like every fairytale ending, they manage to find a way.
Now you're wondering if you can actually root without flashing another rom. Good news for you: you can! There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting.
.. But ask yourself what's the point of going through the hassle of rooting and your phone is not tweaked for performance or for theming purposes?
That's when people flash roms and in Z5 compact's case, XPower is the best rom there is. It gives you all the performance tweak you need to make your phone lag free, it has a lite version that removes all the unnecessary system apps you can't delete without root, it gives you an option to add themes and framework from Xperia X with all those work around in place.
For your second question: why is there a need to install TWRP?
TWRP is a recovery tool which is a need for all rooted phone. It's also a tool for you to backup and restore your current rom so that you can rollback to the last working configuration if your phone went into a bootloop etc. Plus i believe all these guides require you to actually use TWRP to flash the SuperSU to successfully root your phone.
I hope this explains your doubts.
Thanks a lot but...
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
I think this is a pretty great thread rajdude. It's getting people to spell out a lot of information to noobs like us that it seems most posters have taken for granted over time.
I'm a complete novice at all of this. Sort of gleaning information as I go along, but I used this guide: http://twigstechtips.blogspot.hk/2016/04/sony-z5-compact-root-without-losing-ta.html?m=0
Along with this guide: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
The first guide is pretty basic step-by-step instructions. It unfortunately occasionally kind of skips over a couple very small things (that will be clear as you go along), or occasionally words things in such a way that might not be completely intuitive, but maybe that's cause I need things explained to me like I'm five sometimes. Any time I might have had a question about something in the the first guide, I went to the other and found the answer. It didn't take me long to get the gist of the whole thing though, and overall, it wasn't as scary as I thought it was going to be. It'd be fantastic if someone created a video walkthrough, but so far as I know, no one has done that yet.
The guide will help you back up your TA Partition where your DRM keys are stored, unlock your bootloader, root your device, and then restore your DRM keys. In order to do this you need to downgrade to Lollipop (if you're not already on it), and then upgrade back up to Marshmallow. It will also install TWRP (which I had no clue was installed until I went into "recovery mode" by pressing UP when I saw the LED flash yellow during boot). There may be an easier way to go about this whole process, but this is the process I used.
Before jumping into anything, I'd hold off until you heard more from firdyRAY or someone more experienced. They may look at the guide I linked and be horrified.
And yeah, I haven't installed xpower yet for the same reasons you haven't. Sounds like there's even an xpower 4.0 that was released recently, but still seems kinda buggy. Being rooted with stock I've been able to give Greenify access to root. Install Adaway (which was worth getting root to begin with). Install sound/music mods like DiVA-X, Viper4Android and Dolby Atmos. Install Titanium Backup. And make a few other minor tweaks (that I've since reversed). I still don't know much about custom ROMs and all that jazz, so I'm holding off until I get more understanding. I'd love to install the xpower ROM (when the bugs are worked out), and maybe some sort of sound ROM. I also need to get more understanding on some of the other vernacular like what exactly a "dirty flash" is.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
Click to expand...
Click to collapse
sony ric is a layer of security for sony roms so that they can protect nfc and fingerprint stuff. samsung and htc have there own variants as well.
yes lol the big red lettering is there to make you read, although hes not far off on the melting your phone part, the s810 is ridiculously hot.
the xpower thread doesnt not include the drm backup instructions because: 1) you need bootloader unlocked to flash it. and 2) because it includes the drm fix in it so you dont have to backup your ta keys.
the fingerprint sensor bug is on any bootloader unlocked phone, the hardware fails after x amount of hours and requires a reboot to work again. xpower is a stock rom, the only thing different is its pre-rooted, de-bloated, and deodexed for xposed to work. we have a separate thread for the fingerprint sensor bug and its been solved.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
Click to expand...
Click to collapse
Sony RIC main function is to disable /system write even you got root permission(you still able to do /system write but after a reboot will restore to original). There is a workaround but very trouble, TWRP recovery file manager can bypass Sony RIC(it works in the old day for me, not sure about now). BTW, all 3rd kernel should be disabled RIC nowadays. For any regular computer, there is no hardware or software lock to prevent you gain root access in linux but there are many such trouble stuffs in the android world... lol
I'm running XPower 3.0 Full as a daily driver since June and been very happy. Battery life, stability and speed is good.
Please note, that you MAY lose your warranty when you lose your DRM keys. That's why I didn't unlocked my phone before there was a way to backup TA partition. Now I'm after warranty repair, and before it I was able to fully restore stock ROM with DRM and all features fully functional. In my country, there is only one Sony approved repair center and they check DRM keys before repairing anything - even if it's mechanical fault.
When I had Z1c in KitKat days, it didn't had dm-verity and Sony RIC. It was possible to gain permanent root with bootloader locked, so I was happily using stock ROM and kernel. In Z5c case, first thing I tried was to do the same and it was possible (just backup TA, unlock bootloader, and flash TWRP with patched kernel (dm-verity and Sony RIC disabled) to begin with), but going XPower way was much more confident - I didn't had to think about removing every bloat app. I just flashed lite version in June and I'm using it till this day without any problems at all
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
michuroztocz said:
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
Click to expand...
Click to collapse
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
flopower1996 said:
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
Click to expand...
Click to collapse
That's just what I wrote - just put it in another words
Please read the whole post and answer all (if possible) of my questions, I don't mind if you give me links, I'll read myself. Just don't answer with 2 words that don't mean anything to me.
I want to get into rooting, custom kernals, etc but I really don't know where to start reading from. Anything I came across seems not detailed enough. My end goals are:
- To get enough info so I don't brick my phone or even if I do, I want to know how to fix it.
- Install a custoim kernel, so I can get battery life simillar to this guy.
- Get magisk working, so I can get AUX lenses on gcam working too.
In the past I have installed custom roms on my old LG G2 and everything was so simple, rooting was 1 click and installed TWRP too. Then just flashing roms, gapps, etc, but at the moment I feel my knowledge/experience is like I've never seen a computer or phone in my life.
1. First, where do I start from? Here? It doesn't say if I should have an unlocked bootloader, but other guides require that. I'm kinda confused.
2. If I need to unlock it, I read that it wipes everything, how do I backup without TWRP? Speaking of which, do I need it since there is no official one. Can I do a pre-root backup with OP switch and then restore from it after I've rooted and/or unlocked bootloader?
3. What's the deal with patched boot images, in what situation would I need one?
4. I've just updated to OOS 10.0.8.HD01BA. Does that make me unable to root with method from 1 because its so new or it doesn't matter? I've read somewhere that with OTA you lose magisk/twrp, is there a way to prevent that or I'll just have to do 1 again. Do OTAs return me back to stock kernel?
5. The guy above is using this kernel. It's supposed to be working on 7T Pro too. Has anytone tried it? If so how is it?
6. What about blu_spark kernel, is it good? Also I don't really get what the warning message mean :
"Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark."
How do I reflash stock rom? Also there is no official TWRP, so I guess it's better to not use this one or there is another way to install?
7. Speaking of which, what's the deal with FKM? What should I know about it?
8. If I root with 1, can I then install arter97's kernel with FKM?
9. How do I go back to stock kernel/rom/etc/lock bootloader in case I need warranty?
10. Is there anything that's recommended to read/know?
UndeadG2 said:
Please read the whole post and answer all (if possible) of my questions, I don't mind if you give me links, I'll read myself. Just don't answer with 2 words that don't mean anything to me.
I want to get into rooting, custom kernals, etc but I really don't know where to start reading from. Anything I came across seems not detailed enough. My end goals are:
- To get enough info so I don't brick my phone or even if I do, I want to know how to fix it.
- Install a custoim kernel, so I can get battery life simillar to this guy.
- Get magisk working, so I can get AUX lenses on gcam working too.
In the past I have installed custom roms on my old LG G2 and everything was so simple, rooting was 1 click and installed TWRP too. Then just flashing roms, gapps, etc, but at the moment I feel my knowledge/experience is like I've never seen a computer or phone in my life.
1. First, where do I start from? Here? It doesn't say if I should have an unlocked bootloader, but other guides require that. I'm kinda confused.
2. If I need to unlock it, I read that it wipes everything, how do I backup without TWRP? Speaking of which, do I need it since there is no official one. Can I do a pre-root backup with OP switch and then restore from it after I've rooted and/or unlocked bootloader?
3. What's the deal with patched boot images, in what situation would I need one?
4. I've just updated to OOS 10.0.8.HD01BA. Does that make me unable to root with method from 1 because its so new or it doesn't matter? I've read somewhere that with OTA you lose magisk/twrp, is there a way to prevent that or I'll just have to do 1 again. Do OTAs return me back to stock kernel?
5. The guy above is using this kernel. It's supposed to be working on 7T Pro too. Has anytone tried it? If so how is it?
6. What about blu_spark kernel, is it good? Also I don't really get what the warning message mean :
"Reflash ROM -> flash TWRP --> reboot to recovery --> flash Magisk if you want (default, no plugins/modules) -> flash blu_spark."
How do I reflash stock rom? Also there is no official TWRP, so I guess it's better to not use this one or there is another way to install?
7. Speaking of which, what's the deal with FKM? What should I know about it?
8. If I root with 1, can I then install arter97's kernel with FKM?
9. How do I go back to stock kernel/rom/etc/lock bootloader in case I need warranty?
10. Is there anything that's recommended to read/know?
Click to expand...
Click to collapse
1. Unlocked Bootloader is always required.
2. Yes it wipes everything, OnePlus switch works fine for backup and restore
3. Since there is no TWRP you'll need one to root.
4. Not necessarily. You can just grab whatever patched boot image (preferably for BA), fastboot boot it to see if it works, if it does then do direct install in Magisk Manager. You can maintain root after an update following this
https://topjohnwu.github.io/Magisk/ota.html , and yes, it'll bring you back to stock kernel.
5. ?
6 &7. You can do ahead and try different kernels however I recommend arter97.
Since there is no TWRP you'll need FKM to flash the kernel.
8. Yes.
9. Rooting doesn't really void warranty, but I'd use MSMTOOL to get back to 100% stock.
For stock kernel you can flash stock (or patched) boot image depending wether you want stock or stock root.
To get back to stock ROM, either use MSMTOOL or fastboot ROM, you can find both in guides section.
10. Guides section for fastboot ROM and msmtool.
For AUX module.
https://www.celsoazevedo.com/files/android/p/gcam-oneplus-7-t-pro/
Since there is no TWRP it can be tricky to get out of bootloop if you install a rogue module.
Use this then;
https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677