Sony XPERIA Z3 D6616
Instructions for root
* zxz0O0's original instructions
* GhostRaiderMX's detailed instructions
* Video instructions
Intro
First, thanks to Pyres for a great Z3 bounty thread. This thread is specifically for gaining root on the D6616 (T-Mobile US) variant of the Sony Z3. The method proposed by user zxz0O0 works for many variants of this device, but the D6616 is excluded because the exploit has already been patched in the earliest available firmware for the device.
The goal
The bounty's fulfillment requires obtaining root access in order to be able to backup the TA partition, where the DRM keys for the aforementioned technologies are stored. Once we have a backup for our TA partition, we can unlock the bootloader with the official Sony tool and then restore the DRM keys. In the event of hardware failure, we will be able to restore to stock the phone and to have no warranty issue.
Claiming requirements
In order to claim this bounty, you will need to fulfill each and every one of this points:
1. Be the first person to create or find a method to obtain root access in the latest available software release on the aforementioned devices, without neither unlocking the bootloader nor compromising (or affecting) the TA partition in any way that could prevent a correct and successful backup of it;
2. Give proof of point #1 by posting an adequate quantity of screenshots to illustrate it, together with step by step instructions, in a fashion such that everyone can follow them and reproduce the exploit;
3. Wait for at least 10% of pledgers (fastest quorum achieved between per capita and per pecunia criteria*) to give confirmation about the method functionality;
4. Claim your bounty via PM from pledgers.
*i.e. the fastest between 10% of the number of people and 10% of the amount of money pledged as bounty.
Payment will be processed between each member and the bounty collector via PM on an individual basis.
List of Pledges
1. tuzonghua - $50.00
2. ecnahc - $25.00
3. leonhks - $20.00
4. ubuntunerd - $20.00
5. macrosblackd - $25.00
6. kaikea - $25.00
7. HORiZUN - $50.00
8. thienbrand - $10.00
9. lvlonkey - $20.00
10. edwardlanti - $25.00
11. xtentual - $40.00
12. bishop9779 - $30.00
13. metalmilo12 - $20.00
14. imna357 - $10.00
15. ShermCraig - $20.00
16. Bling_Diggity - $10.00
17. TrunkleBob - $50.00
18. mrmizzo - $50.00
19. dia_naji - $20.00
20. dmdelgado - $20.00
21. steelsix - $15.00
Total Pledge: $555.00
Last updated: April 5, 2015, 12:53 UTC -5
Rules of this bounty thread
- Please note before making a post in the thread please refer to the below list to see if your post will be acceptable. If it is not part of this list, your post will be reported and you may risk getting an infraction as per forum moderators.
- Please note you may not make any specific restrictions or requirements that aren't listed in the OP. By making a post with your contribution price you are agreeing to paying out based on all terms listed in OP only and nowhere else.
- Please be advised that if Sony is to release an official method of rooting without unlocking the bootloader or restoring TA partitions lost by officially unlocking the bootloader (extremely unlikely but must be accounted for) prior to any member of XDA's submission, this bounty automatically becomes invalidated.
- Please do not PM a pledge, for it will not be counted.
List of Acceptable Posts:
- New bounty submission or increase of current bounty;
- Questions or assistance in development of a root, recovery, or bootloader unlock method;
- Questions and answers regarding bootloaders on this device;
- Questions and answers regarding the nature of lockdown on this device;
- Questions and answers regarding kernel and bootloader-related exploits;
- Any kind of updates about unfinished or still work-in-progress methods that would at the moment of posting be unfit for fulfilling the bounty;
- Bounty's fulfillment.
This will most likely be the exploit used to gain privileges:
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1474
After the Graphic Buffer is exploited, giefroot (made by zxzo0o) should run successfully, rooting the device.
Right now, a few developers are attempting to root the Note 4 with this method, and I think once they achieve it, we can port it to the D6616 and Z3v. Follow the Note 4 devs here: http://forum.xda-developers.com/note-4-att/general/galaxy-note-4-root-progress-t2961974/page22
I planned on looking for a way to exploit the Graphic Buffer and run giefroot with escalated privileges, but it doesn't look like I'll have the time.
You can find a copy of the D6603's /system/lib/libui.so here: https://dl.dropboxusercontent.com/u/24614808/libui.so
I can't imagine the D6616's libui.so being patched since this exploit was just found.
would like to pledge $25.
I will pledge $20
Hope someone finds out how to root it for this model
Really hate tmobile icon and blogware.... Stupid WiFi calling mess up my group texts
I got $20 on it !!!
I'd like to add $25 to the bounty.
Finally a thread dedicated to the D6616. Willing to pledge $25. Love this phone! Just need root.
Put me down for 50 USD. This phone sucks without root access.
Just register my new credit card, so i'm in for $10 ( im doing everything i can, so sorry ).
I'll put $20 on it.
I'll pledge $25
I'm In, But
But, remember Lollipop will be out in the next 10 to 15 days, then this bounty will no longer be needed. CF-Auto-Root package works for Lollipop.
@tdoyle hopefully lollipop will be out soon for this model, but unlike the unlock/international model of the z3, the US version is built sightly differently, knowing tmobile with a lock led bootloader. Tmobile will take there sweet @SS time making the updated. If Cf-auto-root works then the guy that fulfilled these requirements can have my money....
tdoyle10 said:
But, remember Lollipop will be out in the next 10 to 15 days, then this bounty will no longer be needed. CF-Auto-Root package works for Lollipop.
Click to expand...
Click to collapse
Source for 10-15 days? Maybe it's out there and I missed it, but the T-Mobile software update tracker has no mention of the Z3...
tdoyle10 said:
But, remember Lollipop will be out in the next 10 to 15 days, then this bounty will no longer be needed. CF-Auto-Root package works for Lollipop.
Click to expand...
Click to collapse
It works by unlocking bootloader, which is not possible on D6616.
I'll pledge $40
pledge
i will pledge 30
Thank you for this thread
Will pledge 20$, I hope someone finds the exploit soon.
Pledge $10 from me
imna357 said:
Pledge $10 from me
Click to expand...
Click to collapse
I'm in for $20 too - wish it could be more.
Related
Announcement:
I have sold my Galaxy S2 and will be getting my Galaxy Nexus on the 25th of January, 2011. As such, from that date onward, I will no longer update this thread. I will gladly copy and paste the template of this post to anyone who wants to continue doing this. If you wish to continue this thread, please PM me (do not post here). If no-one who is willing to continue this thread contacts me by the 25th, I will message the mods to close and unsticky this thread.
Please Read:
This is not the place to voice your opinions, nor is it the place to ask your questions. It is, however, a place to get the latest updates as they come in from the CM9 team.
My aim is to have one place to receive CM9 updates, instead of having to go through several websites / G+ accounts / Twitter accounts.
Disclaimer: I am in no way related to the CM9 team
Current Status:
[Last updated on 18/01/12]
New version out:
1) 2stage boot (now for real)
2) Cleaned up ramdisk / desamsungized
Current Release:
[Last updated on 25/12/11]
The team has released an experimental, unsupported build of CM9. XDA thread here, and the blog post here.
Known issues here.
People to follow:
Codeworkx
Blog: Link
G+: Link
Twitter: Link
Xplodwild
Twitter: Link
IRC
#CMSGS at freenode.net
If you have anyone else to add, please PM me and I'll add them as quickly as possible.
Latest Youtube Videos
[Last updated on 22/12/11]
Exclusive hands-on (pre)review by site Android Next, uploaded on December 22nd, 2011. Watch it here.
Uploaded by codeworkx on December 19th, 2011. Watch it here.
Uploaded by XplodWild on December 13th, 2011. Watch it here.
Frequently Asked Questions
[Last updated on 03/01/12]
Q: I downloaded the latest CM9 build, but [XXX] isn't working!
A: Search! Search the CM9 threads, search Google, but for the love of God - please first search for the answer! If you did, and could not find it, you have three options:
1) Read this, it might very well answer your question.
2) Check out the live support chat But search first.
3) Go here and ask your question. But search first. Did I mention you should search first? You should search first.
In any case, if your question or query is not directly related to development, please do NOT post in the development section!
Q: I can't connect my phone to my PC! What can I do?
A: This is a known issue. There are several ways you go around this - either by downloading to your PC a program called Droid Explorer, or by downloading any of the wi-fi file transfer apps on the market.
Q: When I start up the Superuser app, it crashes! What do I do?
A: Users are reporting success by searching for Superuser updater on the Market, installing it, and forcing an upgrade.
Q: I can't buy apps from my phone! What can I do?
A: This is a known bug. The only way to buy apps right now is through your home computer. Refunding is reported working on the phone, though.
Q: When I download a big app from the market, I get an error message! What can I do?
A: This is a known bug. Nothing can currently be done about it, unless you already downloaded the app and have it backed up. In that case, there is an advanced work around that you can find by searching the CM9 threads.
Q: I heard Codeworkx got a Galaxy Nexus, is he going to stop supporting the Galaxy SII?
A: Nope, not currently. Actually, it means he can use his Nexus for day to day use, and only focus on development on his GSII. This is in our favor.
Q: I found and downloaded an ICS ROM by Airbus360, I heard its better than CM9, is that true?
A: Apparently, Airbus360 simply took what the CM team has been building, added a few useless lines of code (read: they don't do anything), and claimed that its faster. He also pretty much claims to be doing most of the hard work when in fact, he isn't adding much of anything.
If you have anymore frequently asked questions to add, please PM me and I'll add them as quickly as possible.
Thanks
To all the devs who put in the time and effort to make our phones shine.
To Stylez and Conantroutman, for their continuous support in managing this thread.
To Matriak for keeping the community up to date while he could.
To everyone who post updates here while I am away.
Note: If any updates come through between 21:30 - 05:00 UTC, they will not be reflected here because I will most likely be sleeping
[REF] Galaxy SII CM9 Progress
Reserved...............
[REF] Galaxy SII CM9 Progress
Reserved.................
Thread cleaned.
Please do not post as thread is open to allow OP to keep updated posts will be removed.
Frankly, I’m a bit overwhelmed by much of the anger and resentment being shown to me on XDA for the manner in which I chose to stop supporting my GApps packages. My intentions were to make a clean break, NOT to “take my toys and go home”. I am very disturbed by the notion that there was any obligation for me to leave on anything but my own terms. That was also the driving force behind my decision early on not to accept or ask for donations.
From the very beginning, the major premise behind PA GApps was to provide current up-to-date GApps packages with customization features. I believed that leaving behind outdated work that would “live forever” (with my name on it) would be totally counter-productive to what we had set out to accomplish. This was the driving force in my decision to pull the packages when I closed my threads.
That said, as a gesture of good faith, I am posting links to the most recent builds of my GApps packages. I am also making available the OP posts from my threads in case anyone wishes to continue my work. With this, I am also hereby granting approval for anyone who may wish to continue my work here on XDA. My only caveat is that I will NOT be making myself available for assistance with any questions or problems you may encounter. I have turned off PM’s so I won’t be reachable, anyway.
The links below will remain active until March 31, 2015 and then, once again, they will be removed. That should provide sufficient time for interested persons to gather anything they may want for the future. Feel free to share the links or create your own mirrors.
4.4.4 GApps Packages
5.0.1 GApps Packages
5.1.0 GApps Packages
4.4.4 OP Posts
5.x OP Posts
Thank you for all your hard work and for posting these, goodluck with whatever you do next!
Thank you! I really apperciate all the work you have done for this community! :good:
Thread closed at OP request.
Hello there!
I've noticed the resources for us using the ZE500CL variant of the ZenFone 2 line of phones are few and far between, so I decided to make this list of methods I personally tested for rooting, unlocking the bootloader and temporarily flashing TWRP (tethered recovery).
I apologize in advance if I'm breaking any forum rules, but I'll make sure to credit everyone who's guides and files I'll be presenting here. I am only posting this to help fellow ZE500CL owners in finding all the necessary tools and methods for various things they need. None of the tools and guides below are my work, all credit goes to their original creators.
I'll update this when I test more things, so keep an eye on this post in the future
NEW: Untethered (permanent) TWRP! You can find it here: http://forum.xda-developers.com/zenfone2/general/guide-twrp-2-8-7-0-custom-recovery-t3328155
Root
Both methods worked for me, but I'd still recommend the second method in combination with temporary (tethered) TWRP in the last guide. Credit: @Chinaphonearena
Guide:
http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063/post60872347
Unlock Bootloader
Please note: Only do this is you're absolutely sure you know what you're doing. Your warranty will be void and you will not receive further OTA updates. There are also NO CUSTOM ROMS for this phone. I am not responsible for damage to your device.
So, we've finally officially got the Bootloader Unlock tool from ASUS. It was uploaded in the "Driver & Tools" section on the ASUS ZenFone 2 ZE500CL official page just yesterday (I've checked it two days ago, it wasn't there, so it was most likely yesterday). I've got the information from this ZenFone 2 ZE500CL ZenTalk Forum post. I tried it, and it worked perfectly!
You can download it from here:
ZenFone 2 (ZE500CL) - Support
Temporary (Tethered) TWRP
This works like a charm tethered, but I didn't try flashing it. When I find one that works, I'll update this post with new information. If any of you find one before me, please notify me This one was, after all, not built specifically for the ZE500CL. Credit: @TheSSJ
Guide:
http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532/post61076508
Xposed Framework
I've attempted this one, and it worked. Use the tethered TWRP to flash, and be sure your phone is rooted and has BusyBox installed. Credit: @ansebovi
Guide:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476
I hope this was helpful. Again, the only intention of this post was to help out fellow ZE500CL users, since it's hard to find necessary tools for this device.
Thanks to all the wonderful people of XDA for working on the projects and helping out in the forums!
Checklist of Things to Do w/ Axon 7
1. Unlock Bootloader - DONE
2. Flash TWRP - DONE
3. Get Root Access, along with Root apps - DONE
4. Flash Cyanogenmod 13.1 - PENDING
Who is interested in seeing Cyanogenmod 13.1 running on the ZTE Axon 7 as much as I am? If so, please post on this thread. Hopefully, the right people will check this out and get the ball rolling on this project.
Why don't you build it ? ?
We are never happy ... let the devs work ... on the other hand they have a life and bills to pay !
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app
like tupirujp says.
If you want your question answered just contact Cyanogen directly.
***Thread Cleaned*** (removed negative, counterproductive comments/quotes, for a fresh start)
Some concerned users brought this thread to the attention of Moderation staff.
A good practice is to have the dev needing the device (Unjustified Dev) set up their own donation link, express their desire to dev for the device, and put out a little description of the work they intend to do for that device (ie; unlock bootloader, Roms , Kernels, etc)...
Otherwise, third party donation links usually only raise suspicion, mistrust, and rarely accomplish the goal of helping the dev get a device.
I applaud those who want to support developers (they certainly deserve the support), let's make sure we do it in a way that isn't counterproductive to the goal or the donation process.
Thanks for your cooperation.
Well, in order to build a rom you need:
Device Tree
Kernel
Vendor/Proprietary files
We have versions of the first two already loaded on GitHub. It's a (hard) matter of someone figuring out what proprietary files we need and then going through the iterative testing to ensure all the hardware components are working. So, let the devs have time with the phone to see what they can figure out and we'll start seeing development.
Please Cyanogenmod come to this device..
Introducing Motorola Moto G22 (hawaiip) developer community, this is an initiative to bring testers under the same roof for the betterment of development for Hawaiip
I advise people with the device to come forth as testers, please take note that it is only with your support that development with flourish. Regardless of the number of developers, there's no point when there's no one to test.
Requirements to be added as a tester:
1. Must have the device with an unlocked bootloader.
2. Must be knowledgeable and experienced enough with custom ROMs flashing.
3. A reliable internet connection is recommended.
4. Access to a pc would be beneficial for obtaining logs, but isn't necessary.
5. Should be active. You will be removed if inactive for longer periods.
6. Should be loyal to the team. If found to be leaking builds or even mere screenshots, you will be removed.
{Mod edit} If you meet all the necessary requirements and are interested to volunteer as a tester. Answer this post
@kaike_ I've moved your thread out of
Miscellaneous Android Development
For ROMs, kernels, tools and scripts only (devices that do not have a forum on XDA)
forum.xda-developers.com
Please note the subtitle of that forum but also
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
It has been moved to
Android Software Development
Discussion about Android-specific software development
forum.xda-developers.com
Additionally, I've removed the link to Telegram! Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to this thread as it doesn't qualify as a development thread. Additional information is also available here:
Telegram Chat Channels - Way Forward
WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...
forum.xda-developers.com
Please refrain for sharing of social media references unless within your own development threads!
And as a friendly warning: Never ever edit something that a moderator has added or edited without prior approval of a moderator.
Thanks for your future cooperation.
Regards
Oswald Boelcke
Senior Moderator
Ok, sorry, I'm not common using XDA posts
im volunteer as a tester for the further devlopement for the moto g22 i have experience 1 year in flashing these custom rom and stuff and also a random guy named MACKEN has booted gsi on hawaiip
kaike_ said:
Introducing Motorola Moto G22 (hawaiip) developer community, this is an initiative to bring testers under the same roof for the betterment of development for Hawaiip
I advise people with the device to come forth as testers, please take note that it is only with your support that development with flourish. Regardless of the number of developers, there's no point when there's no one to test.
Requirements to be added as a tester:
1. Must have the device with an unlocked bootloader.
2. Must be knowledgeable and experienced enough with custom ROMs flashing.
3. A reliable internet connection is recommended.
4. Access to a pc would be beneficial for obtaining logs, but isn't necessary.
5. Should be active. You will be removed if inactive for longer periods.
6. Should be loyal to the team. If found to be leaking builds or even mere screenshots, you will be removed.
{Mod edit} If you meet all the necessary requirements and are interested to volunteer as a tester. Answer this post
Click to expand...
Click to collapse
Hi , i would like to be a tester , i dont have much knowledge in flashing (but i have some basic knowledge and i alr flashed roms on other devices) other than that , i have everything required , where should i contact you? Over discord or in this thread?
Hi. I would like to be a tester. I have many years of basic custom-rom flashing experience on three mobile phones. Can follow any instructions for debugging/taking debug-logs.
Why they don't add our device into the devices list? There's the G20 but not out G22
i would like to be a tester , I have many years flashing roms whit moto g22 have 1 year and ready for give help if it possible
I would love to. I've got a spare hawaiip i'm not using at the moment, and feel quite comfortable with the task as I used to cook my own roms.
kaike_ said:
Introducing Motorola Moto G22 (hawaiip) developer community, this is an initiative to bring testers under the same roof for the betterment of development for Hawaiip
I advise people with the device to come forth as testers, please take note that it is only with your support that development with flourish. Regardless of the number of developers, there's no point when there's no one to test.
Requirements to be added as a tester:
1. Must have the device with an unlocked bootloader.
2. Must be knowledgeable and experienced enough with custom ROMs flashing.
3. A reliable internet connection is recommended.
4. Access to a pc would be beneficial for obtaining logs, but isn't necessary.
5. Should be active. You will be removed if inactive for longer periods.
6. Should be loyal to the team. If found to be leaking builds or even mere screenshots, you will be removed.
{Mod edit} If you meet all the necessary requirements and are interested to volunteer as a tester. Answer this post
Click to expand...
Click to collapse
just one thing,will there be custom things? (custom roms and recoveries) cause thats what im searching for the G22.
Similarly here, i have flashing experience all the way back to the htc dream and have dome it man times before.
I would like to see a version of LoS for our device, preferably based on android 13 or newer depending on when it is made.