Related
Hi people!
Can you look into this boot.img? After editing it with kitchen to support init.d scripts, ecc. I get a new JB boot.img that have 4.4mb, is this normal?
If yes, it can be used with 1.24 hboot, right?
LINK: http://d-h.st/1Uz
If someone can give me some info about this kernel I will really appreciate this.
xpirt
xpirt said:
Hi people!
Can you look into this boot.img? After editing it with kitchen to support init.d scripts, ecc. I get a new JB boot.img that have 4.4mb, is this normal?
If yes, it can be used with 1.24 hboot, right?
LINK: http://d-h.st/1Uz
If someone can give me some info about this kernel I will really appreciate this.
xpirt
Click to expand...
Click to collapse
Hmm... What did you modify? Im sure you removed something to make it that small And I think you should have modified it using ubuntu (well thats the only way that I know to be able to modify a kernel and I don't use kitchen that much too ) correct me if Im wrong hehe maybe it should work though That would be awesome hurrah for not wating for the OTA LOL
4.4mb is not small... the actual size of JB boot.img is 4423 KB (4.31MB).
The Android Manual said:
Hmm... What did you modify? Im sure you removed something to make it that small And I think you should have modified it using ubuntu (well thats the only way that I know to be able to modify a kernel and I don't use kitchen that much too ) correct me if Im wrong hehe maybe it should work though That would be awesome hurrah for not wating for the OTA LOL
Click to expand...
Click to collapse
So.. Cygwin is a collection of tools which provide a Linux look and feel environment for Windows, so yes we can edit kernel on windows.
But I didn't edit manually nothing so far. Kitchen extracted automatically kernel & ramdisk to add init.d support and than it repacked it but the final kernel is only 4.4mb.
This is what I did and what I got
xpirt
ckpv5 said:
4.4mb is not small... the actual size of JB boot.img is 4423 KB (4.31MB).
Click to expand...
Click to collapse
For me is 15.9 mb
Did they not update hboot to make larger partitions like /boot?
xpirt
xpirt said:
......the final kernel is only 4.4mb.
This is what I did and what I got
xpirt
Click to expand...
Click to collapse
And that's a correct size... so what actually your problem is ?
---------- Post added at 12:22 AM ---------- Previous post was at 12:18 AM ----------
xpirt said:
For me is 15.9 mb
Did they not update hboot to make larger partitions like /boot?
xpirt
Click to expand...
Click to collapse
From where you got 15.9 mb ? a Nandroid backup ?
Get it from the OTA zip .. someone uploaded that somewhere before
xpirt said:
Hi people!
Can you look into this boot.img? After editing it with kitchen to support init.d scripts, ecc. I get a new JB boot.img that have 4.4mb, is this normal?
If yes, it can be used with 1.24 hboot, right?
LINK: http://d-h.st/1Uz
If someone can give me some info about this kernel I will really appreciate this.
xpirt
Click to expand...
Click to collapse
It's the correct size of jb kernel. Just the recovery generate bigger with the backup. But it's need to be less then 4mb for 1.24 hboot. But if you really want to try the jb rom, there is a way. You forgot that we have two boot partiton.
1. Install the jb rom with recovery and do a factory reset.
2. Reboot too bootloader
3. Flash jb kernel to recovery partition: fastboot flash recovery boot.img
4. Reboot to recovery will boot to the jb rom.
atis112 said:
It's the correct size of jb kernel. Just the recovery generate bigger with the backup. But it's need to be less then 4mb for 1.24 hboot. But if you really want to try the jb rom, there is a way. You forgot that we have two boot partiton.
1. Install the jb rom with recovery and do a factory reset.
2. Reboot too bootloader
3. Flash jb kernel to recovery partition: fastboot flash recovery boot.img
4. Reboot to recovery will boot to the jb rom.
Click to expand...
Click to collapse
I understand hehehe..
So kitchen remove recovery's backup extra stuff from kernel, also.
But what about two kernel partitions? There is not only one (/boot)?
Thanks,
xpirt
xpirt said:
I understand hehehe..
So kitchen remove recovery's backup extra stuff from kernel, also.
But what about two kernel partitions? There is not only one (/boot)?
Thanks,
xpirt
Click to expand...
Click to collapse
No. The recovery is the second boot partition If you flash the JB kernel to recovery partition you can boot to jb.
atis112 said:
No. The recovery is the second boot partition If you flash the JB kernel to recovery partition you can boot to jb.
Click to expand...
Click to collapse
But no more custom recovery, right?
xpirt
xpirt said:
But no more custom recovery, right?
xpirt
Click to expand...
Click to collapse
Yes.
atis112 said:
Yes.
Click to expand...
Click to collapse
Hehe.. Thanks for info.
But an uncertain, now.. If you go into bootloader->recovery.. It boots JB??
xpirt
xpirt said:
Hehe.. Thanks for info.
But an uncertain, now.. If you go into bootloader->recovery.. It boots JB??
xpirt
Click to expand...
Click to collapse
Yes. But you need to "reboot to recovery" every time when you want to reboot your phone.
atis112 said:
Yes. But you need to "reboot to recovery" every time when you want to reboot your phone.
Click to expand...
Click to collapse
Ah.. you're right
It can be used the same thing for recovery?
I will not be surprised if yes.. xD
xpirt
xpirt said:
Ah.. you're right
It can be used the same thing for recovery?
I will not be surprised if yes.. xD
xpirt
Click to expand...
Click to collapse
I don't know what do you mean now!!??
atis112 said:
I don't know what do you mean now!!??
Click to expand...
Click to collapse
If you use: fastboot flash boot recovery.img... xD
xpirt
xpirt said:
If you use: fastboot flash boot recovery.img... xD
xpirt
Click to expand...
Click to collapse
recovery image is bigger than boot partition, so no
@atis112,
The thing you mentioned, nice trick. I'm thinking of testing JB using that method. Seems safe enough to me.
So is there a JB ROM or backup which i can flash??? What i see is this:
1. Flash your modified recovery,
2. Restore the JB NAND backup from someone.
3. Install the kernel to recovery partition, reboot to recovery from fastboot and just wait.
Is that right???
Regards
atis112 said:
recovery image is bigger than boot partition, so no
Click to expand...
Click to collapse
Ah, you're right I forgot
Thank you atis!
xpirt
neXus PRIME said:
@atis112,
The thing you mentioned, nice trick. I'm thinking of testing JB using that method. Seems safe enough to me.
So is there a JB ROM or backup which i can flash??? What i see is this:
1. Flash your modified recovery,
2. Restore the JB NAND backup from someone.
3. Install the kernel to recovery partition, reboot to recovery from fastboot and just wait.
Is that right???
Regards
Click to expand...
Click to collapse
Just a bit correction: Use one of your ics recoverys! (You have the old partition table) And i think better if we made an installable zip from jb rom. And so:
Flash jb rom from your recovery
Wipe data and cache
Reboot to bootloader
Flash kernel to recovery partition
Reboot to recovery from bootloader
Enjoy the official jb rom
I think it's the only safe way to use JB without OTA update. You can reflash a recovery and go back to ics when you want.
I have seen that since the update notification for Jelly Bean has arrived, Many people (Including me) have been asking for a Tutorial to root the Jelly Bean updated HTC Desire X (HTC DX for short). In this tutorial I would like to mention the steps to root Android Jelly Bean (JB) on HTC DX.
UPDATE: Tutorial with Screenshots here : HTC Desire X Root
This was what had worked for me when I recently rooted by HTC Desire X with Jelly Bean Update, So I hope it works for you too. I am assuming you have just installed the OTA Update and are now sitting with a Stock Jelly Bean on your device.
Summary:
1. Unlock Bootloader (if not already unlocked).
2. Install Jelly Bean compatible Custom Recovery.
3. Flash Super User and Install Busy Box.
4. Enjoy.
Steps.
1. Unlocking Bootloader.
There is a fully explained thread on unlocking bootloader and rooting android ICS put up by user nlooooo, Follow that thread and unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2076675
2. Install Jelly Bean compatible Custom Recovery.
Once you update via OTA for the JB Update, Your HBoot becomes JB Hboot instead of the old ICS Hboot so you need a JB Hboot compatible Custom Recovery to flash the Super User and Root.
Our fellow user atis112 fixed the recovery by neXus PRIME to make it work with JB. So you need to download the JB Custom Recovery from the attachment and put it in your C Drive, So the file location would be C:\recovery.img
2.1] Download JB Recovery.img from here : http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 OR You can use the TWRP Recovery Image made by Yasir. Download from here : http://d-h.st/tSc
2.2] Once you put it in C Drive you need to connect your HTC Mobile to PC and Install HTC JB Drivers, You can install the drivers from here : http://forum.xda-developers.com/showthread.php?t=2222501. Make sure you have installed the Drivers correctly.
2.3] Open your Android SDK (Download it from here if not already) and Go to the \sdk\platform-tools folder. If on Windows 7, Keep the Shift Key pressed + Right click on an empty place in the platform-tools folder > Open Command Window here.
2.4] Type in the following command and see if your device is detected.
adb devices
Click to expand...
Click to collapse
After it is detected, Type the following command.
adb reboot bootloader
Click to expand...
Click to collapse
Once you are in the bootloader, Type the following command.
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
followed by
fastboot reboot-bootloader
Click to expand...
Click to collapse
and
fastboot erase cache
Click to expand...
Click to collapse
2.5] Now you have installed your custom recovery. Now Reboot your Phone.
3. Install SuperUser and Busybox.
3.1] Once again connect your HTC to PC, Download the attached SuperUser.zip and copy it to your SD Card.
3.2] Open the command prompt again as said earlier by going to platform-tools folder and using the adb devices command to check if the phone is detected.
3.3] Once it is connected, Type the following command.
adb reboot recovery
Click to expand...
Click to collapse
3.4] Now you are in the recovery, Use the Volume Up and Down keys to navigate it (Use the power button to select an option).
Navigate to Install Flashable Zip. (This should be the first option and already selected.)
Press Power Button once.
Select "Choose Zip from internal SD-Card" or "external SD-Card" accordingly as to where you put the Superuser.zip.
Press Power Button once.
Scroll and select the Superuser.zip using the Volume Keys.
Press Power Button once.
Then you have flashed your Zip successfully and you are rooted.
Go back to the Main screen using the "Go back" option. Select the "Reboot System Now".
Once you are in the HTC Main screen > Go to App Drawer > Google Play Store > Search for Busy Box and Install it.
That is it, You are now on Jelly Bean and Successfully Rooted.
To Check If You Are Rooted.
1. Open Playstore and search for an app named "Terminal Emulator".
2. Install it.
3. Open it and type in su and execute it.
4. You will get a prompt from Superuser to allow or deny > Allow it.
If you get that prompt, You are successfully rooted.
I hope I have provided credits to all the users whose threads I have mentioned. If not please let me know.
Thanks for reading this.
Or you can refer to my TWRP for JB. Its much better than the fixed neXusRecovery.
Hey, I didn't check that.. Can you give a link to the recovery?
Droid.Anoop said:
Hey, I didn't check that.. Can you give a link to the recovery?
Click to expand...
Click to collapse
Here: http://d-h.st/tSc
xpirt
xpirt said:
Here: http://d-h.st/tSc
xpirt
Click to expand...
Click to collapse
Done. Added it to the post. Thanks Yasir and Xpirt
Droid.Anoop said:
Done. Added it to the post. Thanks Yasir and Xpirt
Click to expand...
Click to collapse
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
neXus PRIME said:
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
Click to expand...
Click to collapse
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Both my recoveries are touch enabled.
1. TWRP (JB)
2. neXusRecovery. (discontinued for updates)
I'm not really a fan of buttons.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
xpirt said:
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
Click to expand...
Click to collapse
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Droid.Anoop said:
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Click to expand...
Click to collapse
I think ckpv5 found a way. Just think.
xpirt
xpirt said:
I think ckpv5 found a way. Just think.
xpirt
Click to expand...
Click to collapse
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Droid.Anoop said:
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Click to expand...
Click to collapse
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
xpirt said:
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
Click to expand...
Click to collapse
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
neXus PRIME said:
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
Click to expand...
Click to collapse
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Droid.Anoop said:
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Click to expand...
Click to collapse
Look at flar2's thread but use the files from ckpv5's ROM, but first ask him for permission.
xpirt
root JB without flashing custom recovery?
Hi!
I haven't flashed TWRP v2.5.0.0 but only boot the phone into this custom recovery, which is working perfectly. (I want to keep the stock recovery.)
I can install and use the Aroma File Manager (TWRP with Aroma File Manager did not work.)
I can mount the system partition and change / delete files.
However, with a reboot, all my changes will be undone.
Before installing Aroma File Manager for the first time, I installed SuperSu1.34.zip. No error. I installed Aroma File Manager right after it, and I think it said "rooted".
Using TWRP's SuperSu does not work (no error message, but system reboots, and it says it's not rooted.)
My question: can I root my phone while only booting into a non-stock recovery or do I have to flash TWRP and then root the phone?
Would I see the system apps e.g., after mounting /system, even if the phone was not rooted?
I am new to JB, I had 2.3.7 before, which I could root without flashing a custom recovery.
I am not sure if I have to flash the custom recovery because of the s-off problem with HTC devices?
If I flash a custom recovery and root the device, can I flash the stock recovery afterwards without loosing root again?
Would you recommend using SuperSu or Superuser? Which version?
I don't think I need busybox.
I only want to delete bloatware and change the battery symbol.
Thanks for your help!
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On. But after you rooted using a custom recovery you can flash the stock recovery again without loosing root. But keep in mind that you won't be able to change system partition. Also, you can't flash zips which aren't signed by HTC.
Sent from my HTC Desire X using xda premium
dansou901 said:
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On.
Click to expand...
Click to collapse
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
mary-lou said:
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
Click to expand...
Click to collapse
How do you boot into a custom recovery without flashing it first? It has to be on recovery partition to work correctly.
Hello
Here is attached link to TWRP 2.8.7.0 for Qualcomm's version of 64bit htc_a51ul and htc_a51tuhl. Not sure if it will work with htc_a51dtul (dual sim version for India/Asia) but if someone want to test, please do.
To flash phone, use below fastboot as HTC was change version for 64bit bootloader, so if You use Linux on Your PC, get My version, put together with recovery.img in same folder, restart phone into bootloader and execute:
Code:
chmod 755 fastboot
Code:
./fastboot flash recovery recovery.img
NOTE that dot and slash are IMPORTANT. If You skip it, will not use My fastboot but other which probably not work and You will get error flashing.
If You are on windows, please use latest version of fastboot for windows.
As usual, TRWP sources are on Omnirom github, device sources are on My github.
NOTE THAT YOU NEED TO HAVE 64bit BOOTLOADER (Lollipop installed on device)
Happy rooting
CAUTION: I am not responsible if You delete and/or brick Your device!!!
DOWNLOAD
EDIT1: attach removed due to bug inside. Will attach new one asap fix bug and recompile.
EDIT2: attach attached back
RESERVED
Screenshoots
Thank you fergy!
I will test a51_dtul!
Working
HTC Desire 820 cihazımdan Tapatalk kullanılarak gönderildi
Works great. Thank You!
Now i can backup to ext. sdcard and restore from ext. sdcard. Big evolution.
@fergy:
Great work.
No adb. Is it disabled in the build?
tomal said:
@fergy:
Great work.
No adb. Is it disabled in the build?
Click to expand...
Click to collapse
No adb? Hmm... Wasnt disable it...try to unpack and check please as i am not home atm.
Htc_a51dtul test is normal, but still the same problem, choose to "reboot to recovery" will be Repeated restart to recovery!
kinghunki said:
Htc_a51dtul test is normal, but still the same problem, choose to "reboot to recovery" will be Repeated restart to recovery!
Click to expand...
Click to collapse
I prefer to disable "reboot to recovery" (until there is a fix). It will save many user.
tomal said:
I prefer to disable "reboot to recovery" (until there is a fix). It will save many user.
Click to expand...
Click to collapse
Yes That's what I think!
I think the cause of the problem may be HBOOT!
@fergy,I added the Chinese language
Hi, where I can find 64bit sources?
@kinghunki Can you provide me original english xml? I want to translate it into polish
en.xml
Skorupa123 said:
Hi, where I can find 64bit sources?
@kinghunki Can you provide me original english xml? I want to translate it into polish
Click to expand...
Click to collapse
Here are en.xml
Skorupa123 said:
Hi, where I can find 64bit sources?
@kinghunki Can you provide me original english xml? I want to translate it into polish
Click to expand...
Click to collapse
No 64bit sources. HTC push OTA's but not release sources on htcdev.com, what is very unusual as GPL say that they MUST to release sources. Nevermind, We can handle that part soon with reverse engineering.
Only what is, let say, close to a51 Qualcomm hardware is sources for Desire 826 (a52) but with lots of changes and patches.
Thank You, tested on A51_UL EU. Works great!
kinghunki said:
Htc_a51dtul test is normal, but still the same problem, choose to "reboot to recovery" will be Repeated restart to recovery!
Click to expand...
Click to collapse
Ya, thank You for that, but I think that here is not problem with device but with twrp.
I can fix that problem but I am not maintainer of omnirom, so not My or Your problem.
If anyone have a time and wish, can participate in omnirom gerrit
Qoneek said:
Thank You, tested on A51_UL EU. Works great!
Click to expand...
Click to collapse
can you please tell if it solves the recovery problem as mentioned here? this problem is driving me crazy...
erany1 said:
can you please tell if it solves the recovery problem as mentioned here? this problem is driving me crazy...
Click to expand...
Click to collapse
What problem You have with recovery? This replace original HTC recovery and You can root, change OS etc..
fergy said:
Hello
Here is attached link to TWRP 2.8.7.0 for Qualcomm's version of 64bit htc_a51ul and htc_a51tuhl. Not sure if it will work with htc_a51dtul (dual sim version for India/Asia) but if someone want to test, please do.
To flash phone, use below fastboot as HTC was change version for 64bit bootloader, so if You use Linux on Your PC, get My version, put together with recovery.img in same folder, restart phone into bootloader and execute:
Code:
chmod 755 fastboot
Code:
./fastboot flash recovery recovery.img
NOTE that dot and slash are IMPORTANT. If You skip it, will not use My fastboot but other which probably not work and You will get error flashing.
If You are on windows, please use latest version of fastboot for windows.
As usual, TRWP sources are on Omnirom github, device sources are on My github.
NOTE THAT YOU NEED TO HAVE 64bit BOOTLOADER (Lollipop installed on device)
Happy rooting
CAUTION: I am not responsible if You delete and/or brick Your device!!!
DOWNLOAD
EDIT1: attach removed due to bug inside. Will attach new one asap fix bug and recompile.
EDIT2: attach attached back
Click to expand...
Click to collapse
Hello.
I tried once to change my stock recovery img but I ended up with a non compatible one and it has been impossible to find a good one.
I can only use my PC and ADB to flash one.
I'm using windows 10 and this model htc_a51tuhl. I have ADB and everything installed.
When i try to flash the recovery you posted: CMD "fastboot flash recovery recovery.img", it says "invalid sparse file format". I assume that the file is too big, but why?
Isn't it supposed to work? or it's only for linux users? Can someone inlight me please.
I'm struggling to find a working recovery to root my phone and so if someone share a working one for me, that would be very very nice.
Hi someone can give MI guide to root my xperia z5c android 5.1.1 E5823 firmware 32.0.a.6.200 please? Tank to the helpers
N22121991 said:
Hi someone can give MI guide to root my xperia z5c android 5.1.1 E5823 firmware 32.0.a.6.200 please? Tank to the helpers
Click to expand...
Click to collapse
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
hello
Thanks
Does it work with encrypted device ?
Bear in mind that if you unlock bootloader, your camera will worsen, you will lose image enhancements like x reality and your warranty will be void. Etc. Etc. So you might want to hold off on root. Just letting you know, that is
Sadman Khan said:
Bear in mind that if you unlock bootloader, your camera will worsen, you will lose image enhancements like x reality and your warranty will be void. Etc. Etc. So you might want to hold off on root. Just letting you know, that is
Click to expand...
Click to collapse
i don't totally agree because what i did,well,unlock device's bootloader & everything blah blah blah..but camera seems to be just fine.but of course,you'd definitely can see the difference..now since drm restore for our devices is already available however,it indeed restored the functions and the bravia engine & all(except the drm key itself),i noticed that my rooting status has changed from "unlock bootloader allowed: yes" to unlock bootloader allowed: no"!also,even if says so,my phone still has twrp installed,rooted & a custom kernel..all seems to be working as i so far observed..just that rooting status thing changed..kinda wierd,though!
Arturiuz! said:
i don't totally agree because what i did,well,unlock device's bootloader & everything blah blah blah..but camera seems to be just fine.but of course,you'd definitely can see the difference..now since drm restore for our devices is already available however,it indeed restored the functions and the bravia engine & all(except the drm key itself),i noticed that my rooting status has changed from "unlock bootloader allowed: yes" to unlock bootloader allowed: no"!also,even if says so,my phone still has twrp installed,rooted & a custom kernel..all seems to be working as i so far observed..just that rooting status thing changed..kinda wierd,though!
Click to expand...
Click to collapse
Mine says the same "unlock bootloader allowed: no" but root and everything works fine, and the camera definitely improved although its still crap in my opinion. Have a couple of before and after shots if someone is interested.
Radeon1337 said:
Mine says the same "unlock bootloader allowed: no" but root and everything works fine, and the camera definitely improved although its still crap in my opinion. Have a couple of before and after shots if someone is interested.
Click to expand...
Click to collapse
wait!let me correct myself a little(this is really weird!)..my drm keys are restored,to wc as far as i am knowledgable of,that shouldnt be the case after unlocking the BL..
*apologies here!im still trying to figure out how to insert a screenshot as a proof!i'm just using my phone atm..peace!
Arturiuz! said:
wait!let me correct myself a little(this is really weird!)..my drm keys are restored,to wc as far as i am knowledgable of,that shouldnt be the case after unlocking the BL..
*apologies here!im still trying to figure out how to insert a screenshot as a proof!i'm just using my phone atm..peace!
Click to expand...
Click to collapse
got it!here's for the screenshot before i unlocked my device..then drm keys lost..then when flashed the drmrestore.zip,consecutively..
MystereT said:
hello
Thanks
Does it work with encrypted device ?
Click to expand...
Click to collapse
Did you ever take the plunge with encryption? TWRP supposedly supports encryption, but want to make sure I have a way to a working phone if encryption doesn't work.
Don't remember if I can undo encryption via twrp, or at that point is it just prudent to flashtool it back to a clean image if not? My understanding is really just need to get a kernel on there that will boot, and provide the rest of the system with or without encryption.
Ready to pull the trigger on this to root and try with my encryption, but think I'll pull down a clean version of .200 firmware for the z5c first...
Yesterday there is a way to get Z5/Z5C/Z5P Rec & Root
and revive DRM & BE2 & Camera noise reduction by one-click (need unlocked BL),
I'm afraid to try...
Works like a charm
I can confirm drm-restore patch works like a charm and everything (camera noise reduction etc.)
iMaeGoo said:
Yesterday there is a way to get Z5/Z5C/Z5P Rec & Root
and revive DRM & BE2 & Camera noise reduction by one-click (need unlocked BL),
I'm afraid to try...
Click to expand...
Click to collapse
TheEndHK said:
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
Click to expand...
Click to collapse
hi Bro! is there any trouble if i flash (obviously via fastboot) only the recovery over the stock kernel firmware .200?? or is mandatory flash kernel and recovery?
thanks!
acabreram said:
hi Bro! is there any trouble if i flash (obviously via fastboot) only the recovery over the stock kernel firmware .200?? or is mandatory flash kernel and recovery?
thanks!
Click to expand...
Click to collapse
Stock kernel will get a bootloop if you rooted. The current build of Z5c kernel got dm-verity, when it detect your /system has changed like flashed flashablesu.zip to attempt to root probably it will not boot. You need a custom insecure kernel to root.
TheEndHK said:
Stock kernel will get a bootloop if you rooted. The current build of Z5c kernel got dm-verity, when it detect your /system has changed like flashed flashablesu.zip to attempt to root probably it will not boot. You need a custom insecure kernel to root.
Click to expand...
Click to collapse
ok Bro thanks!! there is not custom kernel of firmware .200 yet right?
acabreram said:
ok Bro thanks!! there is not custom kernel of firmware .200 yet right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64849573&postcount=2
plz read it clearly
can someone share stock E5823 fw .200 kernel, I need it to test this method
Help
TheEndHK said:
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
Click to expand...
Click to collapse
Hello, tks by the step by step u did... Sorry by my poor english, i am braziliam and need little help here.
1 - My z5c already is unlocked;
2 - I download the zombie kernel like u said (ok, get the boot.img file);
3 - I try to download the recovery, but when open the 7zip on windows cannot unzip the recovery.img file;
4 - Try to download this one (TWRP for Z5C) and ok, i get the recovery.img file from this (this is the same recovery file ???).
So the questoin is:
I can flash this files above (boot and recovery) on my z5c - E5823 - 32.0.A.6.200 ????
And why not flash the boot.img from the recovery zip file ??? Whats the diference ???
Regards and tks again !!!
puiatmp said:
Hello, tks by the step by step u did... Sorry by my poor english, i am braziliam and need little help here.
1 - My z5c already is unlocked;
2 - I download the zombie kernel like u said (ok, get the boot.img file);
3 - I try to download the recovery, but when open the 7zip on windows cannot unzip the recovery.img file;
4 - Try to download this one (TWRP for Z5C) and ok, i get the recovery.img file from this (this is the same recovery file ???).
So the questoin is:
I can flash this files above (boot and recovery) on my z5c - E5823 - 32.0.A.6.200 ????
And why not flash the boot.img from the recovery zip file ??? Whats the diference ???
Regards and tks again !!!
Click to expand...
Click to collapse
because it's only meant to be flashed in/by fastboot mode through command prompt or cmd.flashing it using recovery won't install those img's..not unless those were re/packed that could also be flashed through recovery..i've tried it but gave me error. & it's better that way installing it through command prompt/fastboot mode.
Arturiuz! said:
because it's only meant to be flashed in/by fastboot mode through command prompt or cmd.flashing it using recovery won't install those img's..not unless those were re/packed that could also be flashed through recovery..i've tried it but gave me error. & it's better that way installing it through command prompt/fastboot mode.
Click to expand...
Click to collapse
hey friend, tks for response.
I know we need to use fastboot to flash this files and i know how to do this.
I only wanna know if the files are compatible with my model and version device.
puiatmp said:
hey friend, tks for response.
I know we need to use fastboot to flash this files and i know how to do this.
I only wanna know if the files are compatible with my model and version device.
Click to expand...
Click to collapse
yes! it's(actually)for E5823 devices to be specific & as per OP(even as i have checked the links)..it even worked on mine wc is E5803! might want try it out first & see for yourself!
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?