Towelroot pre-sticky thread - Sony Xperia Z Ultra

adfurgerson said:
Where is @polargirl when you need her ?
Click to expand...
Click to collapse
LordManhattan said:
LOL, I had the same thought. @polargirl, where are you?
Click to expand...
Click to collapse
This new method is exactly what I was posting about!!!
I never thought I'd be coming back but clicking the wrong link in my browser lead me back to the Z Ultra general page when I found this thread. I guess it's a good thing the most popular currency converter website's URL also begins with an x. http://www.xe.com/
I just briefly went over this so I am not quite ready yet but I will be happy to combine all this information and make a new sticky thread that combines this new method and another linked in this page.
My only questions for now is: What must be done to retain DRM keys and how does unrooting work with this new method? When I get answers to those questions and more time to read this and other recent related threads in detail and well analyzed, I will get to work on the new thread if you guys like.

---

I have GPe model so my opinion shouldn't count, here it is anyways. Unless you intend to keep the thread up to date it wouldn't be worth doing. As you can see things can change quite a bit in a rather short amount of time.

---

adfurgerson said:
I have GPe model so my opinion shouldn't count, here it is anyways. Unless you intend to keep the thread up to date it wouldn't be worth doing. As you can see things can change quite a bit in a rather short amount of time.
Click to expand...
Click to collapse
As long as I receive adequate support from tech people, I will maintain the thread. I will even make a GPe thread if the procedure becomes significantly different enough to justify one. It's probably better to make a separate one for GPe if even just one thing is different just do avoid misunderstanding instructions.
If someone else would rather do this, I wouldn't mind. Unfortunately, this method has been out for a week already and it doesn't look like anyone else is interested in volunteering to make that thread so I will. This is one contribution that I can make to this site.

---

polargirl said:
As long as I receive adequate support from tech people, I will maintain the thread. I will even make a GPe thread if the procedure becomes significantly different enough to justify one. It's probably better to make a separate one for GPe if even just one thing is different just do avoid misunderstanding instructions.
If someone else would rather do this, I wouldn't mind. Unfortunately, this method has been out for a week already and it doesn't look like anyone else is interested in volunteering to make that thread so I will. This is one contribution that I can make to this site.
Click to expand...
Click to collapse
Sounds great then, I wasn't trying to discourage you just putting my two cents where it doesn't belong. As for the GPe it doesn't require this kind of exploit. Thanks for taking the lead on this and look forward to seeing your guide.

---

We already have TOO many threads.
This method will only be easier the the old method untill the next andriod release from Sony, then we will be back to the downgrade dance. No point in making a thread that will become out of date. Yes @LordManhattan needs to update his thread, but we dont need another root thread by someone that doesn't come here often.
If you really want to help don't reinvent the wheel. PM Lordmanhattan with corrections to his well used thread.

---

adfurgerson said:
Sounds great then, I wasn't trying to discourage you just putting my two cents where it doesn't belong. As for the GPe it doesn't require this kind of exploit. Thanks for taking the lead on this and look forward to seeing your guide.
Click to expand...
Click to collapse
Thank you for the encouragement. It means a bit coming from a regular like yourself.
blueether said:
We already have TOO many threads.
This method will only be easier the the old method untill the next andriod release from Sony, then we will be back to the downgrade dance. No point in making a thread that will become out of date. Yes @LordManhattan needs to update his thread, but we dont need another root thread by someone that doesn't come here often.
If you really want to help don't reinvent the wheel. PM Lordmanhattan with corrections to his well used thread.
Click to expand...
Click to collapse
The problem with your suggestion is that the consumer version of the Z Ultra rooting wheel has neither been invented yet nor does LordManhattan seem interested in doing this. That consumer wheel is not even a rough prototype ATM. This was the source of argument the last time I was here. Even adfurgeson is being supportive of me doing this.
If Lord Manhattan decides to do this himself, I would be happy to abandon this project. The is he almost certainly won't but I will wait until he chimes in on this thread before doing anything.

---

polargirl said:
Thank you for the encouragement. It means a bit coming from a regular like yourself.
The problem with your suggestion is that the consumer version of the Z Ultra rooting wheel has neither been invented yet nor does LordManhattan seem interested in doing this. That consumer wheel is not even a rough prototype ATM. This was the source of argument the last time I was here. Even adfurgeson is being supportive of me doing this.
If Lord Manhattan decides to do this himself, I would be happy to abandon this project. The is he almost certainly won't but I will wait until he chimes in on this thread before doing anything.
Click to expand...
Click to collapse
WTF is this then
Downgrade to gain root
Follow one of the Downgrade paths below to end up with a 14.1.B.1.532 firmware that is rootable while keeping your imei # intact and working cell/data
Downgrade path 1 (very easy):
Download needed files
Download C6833_14.1.B.1.532_NUT.ftf
Flashing using flashtool
Flash EVERYTHING in the above ftf by @[NUT]
Reboot
Flash EVERYTHING in this ftf, (use the defaults) it will do the downgrade below so you will end up on .532 with a working IMEI ready to root with bin4ry's tool
Click to expand...
Click to collapse
If someone cant follow that and then press option 0 in the tool mentioned then I give up on them and they wont beable to run the batch file needed in the towel root way

---

=blueether;53658502]WTF is this then
Click to expand...
Click to collapse
Something that needs work and become a sticky thread on it's own.
Downgrade to gain root
Follow one of the Downgrade paths below to end up with a 14.1.B.1.532 firmware that is rootable while keeping your imei # intact and working cell/data
Downgrade path 1 (very easy):
Download needed files <---- What needed files? Way too broad and vague. It sure would help to elaborate on this for newbies. Links would be ideal especially if the instruction(s) were also hyperlinks.
Download C6833_14.1.B.1.532_NUT.ftf <------- A link at the end of this instruction or even better, have the instruction as a hyperlink to the file.
Flashing using flashtool <----I presume you mean Nut's flashtool? Specification would help newbies not get off track.
Flash EVERYTHING in the above ftf by @[NUT] <---It appears to be a redundant instruction to the last one. I could be wrong which means clarity would have helped but if I am right, then the two steps could have been combined into one that reads: " Flash EVERYTHING using the NUT ftf tool."
Reboot < No editing needed unless reboot is different from regular reboot or some regular method(s) cannot be used.
Flash EVERYTHING in this ftf, (use the defaults) it will do the downgrade below so you will end up on .532 with a working IMEI ready to root with bin4ry's tool <---What ftf? Please clarify and link preferably making the clarity instruction(s) a hyperlink.
Click to expand...
Click to collapse
If someone cant follow that and then press option 0 in the tool mentioned then I give up on them and they wont beable to run the batch file needed in the towel root way
Click to expand...
Click to collapse

---

I give up. I truly do

---

polargirl said:
The problem with your suggestion is that the consumer version of the Z Ultra rooting wheel has neither been invented yet nor does LordManhattan seem interested in doing this. That consumer wheel is not even a rough prototype ATM. This was the source of argument the last time I was here. Even adfurgeson is being supportive of me doing this.
If Lord Manhattan decides to do this himself, I would be happy to abandon this project. The is he almost certainly won't but I will wait until he chimes in on this thread before doing anything.
Click to expand...
Click to collapse
polargirl, I think you're forgetting one thing. This is a developer site. The guides which exist are already simple enough for non-developers/non-hobbyists people to understand. For example, the instructions which you and blueether 'discussed' right now. Here is the proper quote (with formatting) (which you should have done in the first place, @blueether :silly
1.Download needed files
Download C6833_14.1.B.1.532_NUT.ftf
2.Flashing using flashtool
Flash EVERYTHING in the above ftf by @[NUT]
3.Reboot
Flash EVERYTHING in this ftf, (use the defaults) it will do the downgrade below so you will end up on .532 with a working IMEI ready to root with bin4ry's tool
http://forum.xda-developers.com/devd...ct/dl/?id=3442
You will end up with a device that thinks it is a C6833 but when you flash 4.3 or newer (.290 or .136) just use the one for your real model and the model number will be restored.
Click to expand...
Click to collapse
The above method will get you a rooted .532 system. Then simply follow this thread to get .757 rooted(it even has a video link).
Now don't ask how will a new user know that he/she is supposed to downgrade to .532 first, because it is written quite clearly in @LordManhattan 's thread:
http://forum.xda-developers.com/showthread.php?t=2569904 (see the big red letters ?)
And while we're at it, his thread is concise and useful. A new user can follow his thread's instructions and end up with what he wants. Your standards of a non-prototype guide are too high. These guys are not getting paid to do it. They don't have to make it beautiful, they just have to make it functional. The only thing needed to understand these guides is the ability to follow instructions. The guides are good enough.
Few more things, polargirl.
Now we have a flood of new users who are asking not "How can I do this myself?" but more like "Give me the quick fix" without caring to understand the process. See if you read the threads then you get to experience the learning process, you see how the issues were investigated and confirmed. Then you get to watch the different attempts at resolution and learn why some failed while others worked. That is called Development.
The NooB backlash is coming from users who have walked in the development shoes and is directed mainly at those who don't care for the journey but just want the end result or destination.
As a Development Forum we are just as much (if not more) about the journey. I've read so many comments like "I don't have time to read all of the threads" or "I don't care how it works, just that it does". These very statements are contrary to the heart & soul of XDA-Devs and that is why the backlash is so strong.
Let me be very clear on this: IF YOU DON'T CARE ABOUT UNDERSTANDING THE JOURNEY THEN YOU PROBABLY SHOULDN'T BE HERE IN THE FIRST PLACE.
Click to expand...
Click to collapse
Each and new user, who gets a new device, will be 'lost' - without fail. You get 'un-lost' by searching, searching and more searching. So if you want to make a guide, you first have to understand what goes on behind it. If you're not willing to spend that time, then please don't attempt to make the guide. (And if you think you're spending too much time on it, remember - it takes 6 months to make a Rolls-Royce and only 13 hours to make a Toyota.) and how will you understand ? By searching...
How programmers think:
Im curious about "X"....
Im going to search for "X" where i think im going to find it
I found it! I like it,
Hmm what is this in here? What is "Y"??
Im going to search for "Y"
NO!?! I ll ask a buddy programmer....
He told me "Z" just... "Z"
Im going to search for "Z"
OH!! that makes sense!!!!
Im going to use that!
See a common trend? Search, learn, search, ask, search, learn, search, ask , search.
In programming this leads to the thinking, "Why type something again if its already been typed? - I can copy and paste!!!"
Similarly:
In forums and helping others it leads to thinking: "Why type something that has already been typed? - If you search "X", you find something that has already been typed and i dont have to copy and paste it or find it for you!!!. " Search this word.....
Closing
As said above its not out of being rude or elitist, its a way of thinking.
-That way of thinking is a part of programming, and leaning anything in that world, you have to learn the way of thinking. >
-Part of the learning to think that way is getting fed up and saying "Im just going to find out myself!!" >
-Then, by the time you learn how to find anything you want to know on your own, you have an epiphany and realize they were telling you "exactly what you needed to hear". They were the Oracle and you are Neo. The Matrix has you, and it was all about the journey!
Click to expand...
Click to collapse
So please, this is a humble request to you. If you want to write this guide, be prepared to invest your time. If you want to make a better all-in-one rooting guide, please do it. I do hope it is better than LordManhattan's guide. But do not expect us to agree that what's functional is not even a rough prototype.
As for "support from the tech people" -
We will help, but again -
If you ask a trivial question, you'll get the usual one word answer. If you ask something non-trivial that cannot be explained by a simple search, you may even end up getting page-long answers.
I hope that puts an end to this stupid fighting we've been participating in. Please pardon me if you feel that I've been going off on tangents.
---------- Post added at 04:29 PM ---------- Previous post was at 04:21 PM ----------
polargirl said:
My only questions for now is: What must be done to retain DRM keys and how does unrooting work with this new method?
Click to expand...
Click to collapse
1.) http://forum.xda-developers.com/showthread.php?t=2784900
2.) try reflashing the stock kernel using flashtool (?)

---

warfareonly said:
I do hope it is better than LordManhattan's guide.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's true though. I haven't updated my thread in awhile now. It's A LOT of work, and you must always know what's what and how to do it. If Polargirl can't even follow a regular rooting guide that noobs have followed for ages, I highly doubt she can make AND maintain a thread like that. She should probably just READ like the rest of us have done.
This is my first and last post in this thread since I'm not throwing away my time on this stupid thing - again.
Sent from my C6833_GPe using Tapatalk

---

Whatever happens, can we all agree on one thing please.. Towelroot was definitely named after Towelie.. (smile, we're all having fun here lol)
Sent from my C6833 using Tapatalk