Related
Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)
Just got my sony version - can say this phone is beast mode. There is a pending update to .257 and someone told me that if I update to this, i will be locked out of any ROMs, including any google edition ROM. Can anyone verify this or comment? I have NOT updated to .257 yet.
Thanks in advance.
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
LordManhattan said:
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
Click to expand...
Click to collapse
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
LxMxFxD said:
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
Click to expand...
Click to collapse
Correct. There are currently no way to root 257, so we have to root 532 and update through OTA to keep root on 257.
- Use this tool to root
- Install OTA Root Keeper from the Play Store
- Since you've already received the OTA, you don't need to change the CDA in build.prop (to force the OTA), so...
- Update to 257
- The root app (i'm not sure what app it installs) may be gone, so just install SuperSU from the Play Store if it's not in your app drawer.
And you're done...
... unless you also want to unlock the bootloader:
But let's not get ahead of ourselves. You really want to take a backup of your TA partition. It holds all your unique DRM keys, and X-Reality won't work without it. Once you lose it, you can't get it back, so back it up and upload it to your Dropbox or something. So how do you backup your TA partition?
- Download this tiny tool on your computer and run it.
Are you done? Great! Let's move on to the bootloader:
- Go to Sony's dev site
- Request the unlock key and check your mail.
- Install Flashtool on your computer (follow the guide)
- Click the "lightning" icon
- Follow the steps and enter your unlock key
This may wipe your phone, so backup your stuff
And you're done...
... unless you want to install Recovery and TWRP!
Installing Recovery and TWRP is easy. Just run this tool on your computer.
Now you're all set to flash custom ROMs and all that stuff
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Actually... You only need ADB and Fastboot. You can install this Windows installer which will do all the work for you. I'm sorry if you installed the entire SDK I should have included it in the guide.
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my C6833 using Tapatalk
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
techpal said:
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
Click to expand...
Click to collapse
Thank you very much.
I'm new to Sony flashing. Recently bought a XZU (6833) after learning about GPe release. I havent gotten it as yet but i've spent the last few days reading up on preparing for flashing AOSP roms. I'm still not 100% solid on the steps as information is all over the XZU section, not really organised too well. A lot of the information is out of date and there are many gaps that left me scratching my head...
As far as I can gather, these are the steps a new XZU non GPe edition owner should undergo if they would like to flash GPe roms(or any other)...please correct me if I am wrong.
1) Use flashtool 0.9 to flash older 532 firmware ftf file. (does not require root and can be done on a bone stock device non GPe device regardless of installed firmware version). Link here http://forum.xda-developers.com/showthread.php?t=2463701. Now I know Hong Kong version is ok. 532 is older than 257. 257 cannot be rooted directly hence the need to downgrade first.
2) Root using the Japanese rootkitZ Link: http://forum.xda-developers.com/showthread.php?t=2559009 (I assume this installs Superuser as there is a Superuser APK in the folder)
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
5) Unlock bootloader using Sony method. Link:http://unlockbootloader.sonymobile.com/
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Please can someone edit and/or add details where necessary.
---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------
LxMxFxD said:
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Click to expand...
Click to collapse
To what scripts are you referring? Can you help me by fleshing out my above post?
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
Click to expand...
Click to collapse
If you're not planning on keeping the stock ROM, and you want to jump straight to a custom ROM, then no, it's not necessary to install OTA Root Keeper.
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
Click to expand...
Click to collapse
You don't need to back it up, but it's recommended even if you're going to use custom ROMs. What if you're having some issues with your ZU, and you have to send it in for repairs? Sony will notice if the DRM keys aren't there and they'll then know that you've unlocked the bootloader.
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
Click to expand...
Click to collapse
No, this part isn't necessary if you don't want to.
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
Click to expand...
Click to collapse
Yes, run the bat-file and choose SuperSU in the terminal.
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Click to expand...
Click to collapse
Before you start flashing custom ROMs, make a NAND backup of the stock ROM. This way, if you want to go back, all you have to do is to flash a boot.img and restore it, and you'll end up exactly where you left off (with root).
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
1) How does one know when it is necessary to do any of the above.
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
3) How do you flash the boot.img files? Through cwm or the flashtool?
4) Some gapps come with recovery? Why is that necessary?
A million thanks.
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
LxMxFxD said:
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
Click to expand...
Click to collapse
I see you're being taken care of welcome dude, good choice of phone, it's a screamer!
Sent from my C6833 using XDA Premium 4 mobile app
CptAwesomeTT said:
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Click to expand...
Click to collapse
No problem. I quite enjoy this (yes, i'm weird)
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Click to expand...
Click to collapse
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
Click to expand...
Click to collapse
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
Click to expand...
Click to collapse
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
3) How do you flash the boot.img files? Through cwm or the flashtool?
Click to expand...
Click to collapse
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
4) Some gapps come with recovery? Why is that necessary?
Click to expand...
Click to collapse
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
LordManhattan said:
No problem. I quite enjoy this (yes, i'm weird)
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
Click to expand...
Click to collapse
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
CptAwesomeTT said:
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
Click to expand...
Click to collapse
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
LordManhattan said:
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
Click to expand...
Click to collapse
You've been so helpful. I think that's all my questions until I actually get the device in hand and start working on it. Thanks a mill.
atm the jap root method is the one I'd use. kingo might be safe and vroot might not be...
Use the one in the zip or download the v4 or v5 boot.img
v4 http://forum.xda-developers.com/showthread.php?t=2426739
v5 http://forum.xda-developers.com/showthread.php?t=2426736
if going to omni i would flash the revolution kernel http://forum.xda-developers.com/showthread.php?t=2548092
No problem!
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
Link to .532 is gone. Is there another?
Thanks!
Hey guys so I've been killing myself just trying to find ways to get my newly rooted xperia z2 phone to boot into recovery mode.
Essentially I followed this guide to the bone and successfully rooted my phone --> http://forum.xda-developers.com/xperia-z2/development/stock-d6502-23-1-0-726-complete-guide-t3085893
The big problem is whatever I do, no matter the selection of recovery apps(quickboot, twrp manager, etc.) I install I can never get back into recovery mode, my phone turns off and goes into normal bootup, even when I try to do manual recovery mode the light indicator on top doesn't show up and the phone ends up starting normally.
I have factory resetted my phone a couple of times to have a fresh start each time I try something new but nothing seems to work.
On top of that SDFix and it's other variants does not work on my phone, so I can't install any apps on my micro sdcard. I'm really at a loss for what to do here(been at it for 3 days now) so I'm seeking help.
I'm not sure what information to give but I'll try to give as much details as I can about my situation, I'm really desperate to have recovery and my sd card working normally as I am currently very limited with the stuff I want to do on my phone. :crying::crying:
Info:
Model Number: D6503
Android Version: 5.0.2
Kernel Version: 3.4.0-perf-g72984dd [email protected] #1
Build Number: 23.1.A.0.726
SuperSU Installed
Phone is factory reset and rooted.
No other mods & apps installed aside from pre-installed apps and SuperSU
I would very much appreciate it if someone can help me with this problem, thank you!! :cyclops::laugh:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
saedted said:
I can't access recovery mode either. Led light doesn't come on when I turn on the phone as well.
I was thinking abt rooting my phone but nvm now.
Click to expand...
Click to collapse
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
disenx34 said:
I think it doesn't matter whether your phone is rooted or not for you to be able to access recovery mode(not sure about this to be honest). I know rooting(and all this headache) is worth it for any android phone especially the xperia z2 which is why I'm hellbent on getting this fixed.
I wanna install cyanogen mod but those two things I've mentioned in my first post is really limiting what I can do with this phone sadly.
Click to expand...
Click to collapse
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
ptmaniac said:
Sony devices don't have recovery partition, either unlock your BL (and lose DRM keys) and flash a kernel with a built-in recovery , or keep your BL locked and install nut's dual recovery (you need a rooted system before installing).
All the info needed for both options is here on xda but i think you guys need to read a lot more before you start messing with your devices....
Click to expand...
Click to collapse
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
disenx34 said:
I already did everything I possibly could think of (i.e. unlocked bootloader through sony website, rooted, etc.) like I mentioned in the OP, I actually just recently discovered(like 15 minutes ago) that apparently there's this thing called Sony RIC and that's what's disabling me from installing anything on the system and limiting what I can do with my phone because everything(sd card + system folders) are read only and not write-able.
I found out from this thread (http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141/page3) that there's no updated version of 'Sony RIC KILLER' for lollipop version 5.0.2. so I guess I'm stuck. I tried installing TWRP recovery through TWRP manager on my phone and it wouldn't even get to the recovery mode.
I'm gonna keep trying other variants of dual recoveries till one successfully works, I'll also try your suggestion of flashing a kernel with a built-in recovery that's one area I haven't dabbled in yet, this is my first android device so I'm still figuring out where the red line is on everything. :laugh::good:
Click to expand...
Click to collapse
On stock rom / kernel only nut's dual recovery will work. IT will also disable sony ric for you in the process. check here: http://forum.xda-developers.com/showthread.php?t=2261606
On custom kernel you have to choose a kernel with the recovery you want and flash that (don't forget to unlock BL before or you'll end up with softbrick). Recovery managers won't work as there is no recovery partition on your device...
install latest version of nuts recovery for z2 and install it after finish phone well reboot into recovery
Then dont update busybox it well break recovery
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
francisci said:
Hi All,
I am looking for a tutorial that explains how to root the cellphone build under 32.2.a.0.305 running with Marshmallow. I haven't found any topic that state someone succeeded to root this one. Any chance someone can give me some guidance. On some other website it is mentionned that we cannot root it for the moment. So I was thinking maybe downgrade it and go back to Lollipop? But even for that I need some guidance.
Thanks in advance.
Cheers.
Click to expand...
Click to collapse
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
madshark2009 said:
Theres a perfectly detailed guide in general section , you should downgrade to lolipop so you can use the temp root tool to back up drm keys before unlocking the bootloader , but if you dont care about drm keys , you can in fact just skip to the boorloader unlock part and root. Its so simple , but i would suggest going through the whole proccess and back up your drm keys cuz once lost , forever lost so ... Yah
Click to expand...
Click to collapse
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
francisci said:
Hi Madshark
Thanks for your prompt reply. Appreciate it.
I'm at rookie level in terms or rooting smartphone, so I don't know even the basics. Can you send me the link of the "detailed guide" and also explain me what does the "drm keys" stand for?
Click to expand...
Click to collapse
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
madshark2009 said:
this is the link to the post that I used and followed its instructions to root my phone personally.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
if you lose DRM keys (and that happens when unlocking the bootloader) then some functions in the device will stop working like Bravia engine, Track ID, etc and on our z5 compact some say even stock camera stops from working, and when you lose those keys you can NEVER get them back because each device has its OWN TA partition that includes its OWN DRM keys and no other device has the same so thats why each and every one who owns an Xperia device must perform this TA backup in case they ever wanted to get back to stock (unroot and relock bootloader) they can restore these keys and functions to factory functionality. if you dont back them up and unlocked the boot loader then you will never get some functions to get back to working properly if you ever wanted to get back to stock and relock your boot loader!
However; there is some thing that is called DRM fix in certain roms that when you install these roms, you will not feel like you lost your functions because they already include a fix that behaves like the DRM keys.
still, losing your DRM keys will cause your device to lose its warranty and if you didnt back them up then you will never get it back even if you relocked your bootloader. so I personally backed them up because my device has a 2 year warranty and I dont want to waste them if any thing goes wrong I would restore them and send it to get fixed.
yet the only problem is warranty to me so if you have no warranty or dont care about it you can skip the back up process but yet again I dont like taking chances so just back them up its a 2 minute thing.
and I say again, all stock based roms in this Z5 compact forum have drm fix...
and to give you my personal opinion I dont like the Xperia z5 compact rooted because as I saw, there is so little roms and so little kernel variations and all the stable roms are based on stock MM firmware and CM roms arent fully stable yet , (they are but they have bugs that I hate having) and I only rooted so i can increase the volume of my phone speakers and headset and increase the strength of the torch but it all turns out to be that all sound mods have bugs and torch mod only work properly on any thing but STOCK ftf but any thing besides stock ftf isnt fully stable so I dont see any point in rooting this device I so regret buying it I should have checked how little the modifications are that can be made on it I owned Z2 and HTC devices in the past and boy! if I wanted to try different things every day for the past 2 years I wouldnt have finished by now there is sooo much to test and so much to try and to customize ...
the only rom that can be customized and can be enjoyed as much that we have is Kryptonian - the rom of awesomeness!
I hope I was helpful
Click to expand...
Click to collapse
Very helpful ! Thanks v much - I'll let you know if I succeed!
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
--jenana-- said:
Ok, 2 more things.
Probably the most important: warranty has nothing to do with DRM keys, unlocked bootloader or what more. Sony is not/never gonna repair smartphones when there're problems caused by custom ROM or kernel, they're not gonna fix a bootloop caused by a bad flashing procedure and so on. But it's not true that you're automatically losing warranty by unlocking bootloader or getting root access.
Next to that, you don't have to go through that process of backing up your own TA, if you don't want. It's much easier to root and flash a kernel with DRM keys patched. Procedure to root is really simple. Flash new rom, unlock bootloader, fastboot to flash compatible twrp , flash supersu, flash modded kernel, done. There're already quite some tutorials to guide you through this proces.
Click to expand...
Click to collapse
Yah well if the bootloader is unlocked and the system has modification on it , they have every right to refuse fixing it for you because its hard to prove that what bricked the device isnt some modification that you made... Unless they have a really good heart , i had a z2 before and it was rooted but the ftf on it was custom but was on it for like 7 months and all the mods were working properly untill all of the sudden it wont turn on so they told me that what i.did caused it but i didnt do anything wrong i know they lying but can u prove it!? No..
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
francisci said:
Hi guys,
How do I flash the boot.img using cmd and fastboot ?
Click to expand...
Click to collapse
first you gotta download ADB folder
you can find it here if im not wrong : http://forum.xda-developers.com/showthread.php?t=2588979
then place the adb folder in C:\
I think it automatically place it there when installing so no need to do that if so
2. go to cmd (start - type in CMD) and once it launches direct it to where the adb folder is "cd c:\adb" without the quotes of course
3. to flash boot type in "fastboot flash boot boot.img" without quotes and one space step between words only.
4. to flash recovert just type is "fastboot flash recovery "recovery name".img wihtout the quotes and copy recovery name exactly the way it is.
that it
keep in mind that any time you want to flash any thing , that thing must be inside the adb folder for example ,boot.img file must be there in the adb folder with all the other files when installing adb, and also recovery and every other thing you want to flash using fastboot.
hope this is helpful.
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
francisci said:
Hi madshark, thanks again for your help. I have been able to flash the boot img and then rename twrp into recovery and flash it as well.
Now I'm stuck the device cannot reboot so I cannot transfert the SuperSU files in to the device...
And when I type adb devices in cmd, it do not mention the device ! Seems that I'm facing an issue.
Click to expand...
Click to collapse
well youre new, mistakes like these happen Ive been there, sorry for the late reply XDA isnt giving me notification
any way, make sure after backup TA (which is on lolipop firmware) you gotta get back to original .305 firmware (MM) the process of you getting back to lolipop in the first place is so you can use Ivoyroot tool for temporary root so you can backup your TA partition, once that is done you must get back to .305 because you are flashing a kernel (boot.img) that is for build .305 I guess the guide guy didnt mention this?
second when I said copy recovery name as it is I meant what recovery name you have for example
fastboot flash recovery twrp-3.0.2-0-E5823-20160417.img
thats my recovery name the one that I downloaded, yours might say some thing else its OK I meant copy YOUR recovery name to CMD the way it is exactly in the ADB folder
and now your stuck, if your bootloader is already unlocked, just flash .305 firmware with flashtool the same way you flashed the lolipop firmware, once that is done, do the first boot settings and once device is launched into the software , just flash boot again
make sure you follow instructions to the POINT, so you gotta turn of your phone, press the volume up button keep it pressed while connecting your phone to the PC and flash boot and recovery and thats it
and after youre done with this process , then you turn on your phone connect it to your PC and place the superSU zip file in it and then go to recovery and flash it
adb isnt recognizing your device?
thats weird if you just connect your device nothing will happen, so you turn off your phone and press the volume up button and connect it, (thats how you enter fastboot mode) and if still doesnt recognize then do what I told you to do already and see what happens next
keep me updated and if its urgent just send me a PM because I dont see notification otherwise...
Thanks Madshark for your help, it has finally worked!
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Gdhgeorge1 said:
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Click to expand...
Click to collapse
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Horst the Animal said:
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
Click to expand...
Click to collapse
Thanks for replying! Yeah, I assumed that would be the case. But I found this post that says I can flash a "drmrestore" zip package so I can simulate that the keys are still there: https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
The thing is, in order to flash it, I need TWRP recovery, right? I have been unable to successfully install TWRP. Is there an easy way to install it?
Thanks again!
harry_turtle said:
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Click to expand...
Click to collapse
Thanks a lot for replying! If I find this post where I can create my own kernel, I will have to unlock the bootloader again and flash the new custom firmware using flashtool, right?
Also, will I have to downgrade to Lollipop, since Nougat is pretty new on Sony phones and there's no drm fix for that?
Thanks again!
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Will try!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
Thank you so, so much! I will try this and report back with my results!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
I apologize for replying with my report this late.
It turns out I re-locked my bootloader in the process when I flashed Android Nougat, since I had bricked it temporarily. To do the procedure you mentioned above, I need to have it un-locked, correct?
If that is the case, when I try to unlock the bootloader, I cannot access fastboot because whenever I press VOL UP key with adb, the light flashes blue and then red and then boots into the OS normally. Same with flashmode (the light turns green, and then red, finally booting into the OS).
Does anyone have a solution for this, please?
Thank you very much!
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
Thank you for your reply, Dean F.
OEM unlocking option and USB debugging were already enabled. It should have technically been working by now. Could it have something to do with some drivers I have to re-install?
It worked!!
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Gdhgeorge1 said:
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Click to expand...
Click to collapse
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Dean F said:
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Click to expand...
Click to collapse
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Gdhgeorge1 said:
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Click to expand...
Click to collapse
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Dean F said:
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Click to expand...
Click to collapse
Excellent, I see now, thanks!
Well, what I wanted before starting the entire process was a permanent root solution, one that would allow me to access features like Root Explorer on ES File Explorer, or extra features in Link2SD and such, when the opportunity arose. That is what I did with all my previous smartphones, even a Sony Z1 Compact, but this has been the hardest phone to root I've ever handled.
After all the trial and error I've faced, I will take your good advice and leave it as is for now. In the future, I will flash the rooted kernel when I need to use those functions, and use the androplus kernel you had sent me previously to get it back to normal.
Thank a bunch again for all your help, Dean F. You revived my phone, so to speak!
Cheers!