I just got this device, and I love it, so I don’t want to screw this up. I’ve spent the last 4 days researching how to do this, and I want some expertise before I jump in. I have tried to keep the noob questions to a minimum. Please be kind; this is my first time working with Android at all. What I’m trying to accomplish with rooting, because the XZU is so beautiful and big, is the ability to modify the DPI on the device to make it more like a tablet. I may even try Paranoid Android on it, but I will try that after just screwing with the DPI. I am going to lay out the steps I am going to take. Please let me know if the steps I am taking are wrong or if I’ve left out something important. Also, I’ve put my own questions in BOLD. Please answer those if possible.
As I noted, my device is a C6806, its bootloader is able to be unlocked, and I am currently running .757, having just upgraded yesterday. Here are the steps I am going to take:
1. Downgrade to .532 by flashing NUT’s .532 firmware, the .FTF file found here (http://forum.xda-developers.com/devdb/project/dl/?id=3442), with latest version of Flashtool (0.9.16.0). QUESTION: NUT’s FTF file is C6833_14.1.B.1.532_NUT.ftf. I assume the C6833 refers to that device number. But I have a C6806. Will flashing this FTF negatively affect my C6806 in any way? Will it be a problem at all? I assume it won’t be, but I want to make sure.
2. Root the device by using the instructions found here: http://forum.xda-developers.com/showthread.php?t=1886460.
3. I will then backup my TA Partition by following this guide: http://forum.xda-developers.com/showthread.php?t=2292598.
4. I will then unlock the bootloader by following the steps here: http://unlockbootloader.sonymobile.com/.
5. I will then upgrade to .757 following the instructions here: http://forum.xda-developers.com/showthread.php?t=2714511. QUESTION: I cannot find the .757 FTF at that link. I can find the .681 FTF at https://www.youtube.com/watch?v=uFSeSe8gQOY (which should use the same steps as .757). I could just upgrade to .681, but is there a place I can get a good .757 FTF to flash?
I should, at this point, have the latest (or near latest) build rooted. Am I correct in thinking this? If you see any problems, please let me know. If you have any other tips or tricks, please throw those in as well. Thank you. I really appreciate it.
4. You can take a "shortcut" by using Flashtool to unlock your bootloader after getting your unlock key from Sony. Just press the "BLU" button in Flashtool and enter your IMEI and unlock key.
5. That's the root kernel that you need to flash once you're on .757. You can find the .757 firmware here.
BUT BUT BUT, one thing before you start. This could quickly kill your rooting plans before you've even begun. Open the dialer and dial *#*#7378423#*#*, go to "Service Info" and then "Configuration". What does it say under "Rooting status"?
Spoiler: C6806s from Rogers are bootloader locked, and are impossible to unlock, so it gets much more complicated to root them while being on a newer firmware. It's also impossible to flash custom ROMs on them, so pray to something that you don't have an Ultra from Rogers
So if it says "No" under "Rooting status"... then you can't unlock your bootloader, and you should go to the bathroom and cry. On the bright side.. the other steps in your "guide" looks good, so good job and thank you for researching on your own.
LordManhattan said:
4. You can take a "shortcut" by using Flashtool to unlock your bootloader after getting your unlock key from Sony. Just press the "BLU" button in Flashtool and enter your IMEI and unlock key.
5. That's the root kernel that you need to flash once you're on .757. You can find the .757 firmware here.
BUT BUT BUT, one thing before you start. This could quickly kill your rooting plans before you've even begun. Open the dialer and dial *#*#7378423#*#*, go to "Service Info" and then "Configuration". What does it say under "Rooting status"?
Spoiler: C6806s from Rogers are bootloader locked, and are impossible to unlock, so it gets much more complicated to root them while being on a newer firmware. It's also impossible to flash custom ROMs on them, so pray to something that you don't have an Ultra from Rogers
So if it says "No" under "Rooting status"... then you can't unlock your bootloader, and you should go to the bathroom and cry. On the bright side.. the other steps in your "guide" looks good, so good job and thank you for researching on your own.
Click to expand...
Click to collapse
Thank you for the response! I have just gotten to Step 4 with a few snags in the process. The device is currently rooted with .532 and the TA partition is backed up. Sony just e-mailed me the unlock code. I am not on Rogers and I did confirm before starting this that the bootloader can be unlocked. So, luckily no Rogers. I bought the device directly from Sony.
As to the point you made on step 5, do I flash the firmware that you linked there with Flashtool and THEN flash the Kernel? I do both? I'm a little confused on that last step. Any guidance would be greatly appreciated.
And thanks for the encouragement. I think I might make a little guide to explain the little snags I ran into. They confused me for a while!=
Snarge said:
Thank you for the response! I have just gotten to Step 4 with a few snags in the process. The device is currently rooted with .532 and the TA partition is backed up. Sony just e-mailed me the unlock code. I am not on Rogers and I did confirm before starting this that the bootloader can be unlocked. So, luckily no Rogers. I bought the device directly from Sony.
As to the point you made on step 5, do I flash the firmware that you linked there with Flashtool and THEN flash the Kernel? I do both? I'm a little confused on that last step. Any guidance would be greatly appreciated.
And thanks for the encouragement. I think I might make a little guide to explain the little snags I ran into. They confused me for a while!=
Click to expand...
Click to collapse
yep you will need to flash both the FTF (in flash mode) and then the rootable kernel (in fastboot mode)
Related
Thx for your support help and patience to me, kind of new in this stuff, here is my question and I hope someone with absolutly real experience can answer.
Here is my reality, I have an Atrix with the new OTA update gingerbread, no UL BL, no root, no mod, clean...Can I still unlock the bootloader with the2dcourt guide in briefMobile? or I am stuck in the world of no mod forever? This is because I am tired of searching. someone guy s say you can, other say can´t (BriefMobile for example)...I really apreciate the help and a little guide just the names of treats or files I would search
I'm in the same boat, was waiting for the official update before making any mods, and I have to say, after a couple of hours on here this morning I'm a bit confused.
I got root fine (brief mobile's is solid for that) but now I'm trying to figure out the BL. Some posts say the OTA will hard brick if an SBF is flashed, others point to guides that use the SBF flash...
You can still unlock the BL with pudding and install CWM to flash custom rome. Use the preinstall method to root or use a pre-rooted custom rom.
DO NOT try to flash back to a stock froyo build or you will hard brick.
Incognitum said:
I'm in the same boat, was waiting for the official update before making any mods, and I have to say, after a couple of hours on here this morning I'm a bit confused.
I got root fine (brief mobile's is solid for that) but now I'm trying to figure out the BL. Some posts say the OTA will hard brick if an SBF is flashed, others point to guides that use the SBF flash...
Click to expand...
Click to collapse
You will only hard brick with the OTA if you attempt to flash back to 4.1.83 or earlier stock builds. You can use the fruity cake builds (as they have pudding in them) to go back if you had to.
From here on out you have to use pudding to unlock the boot loader to enable custom rom flashing. Just follow the pudding thread for more info on that.
You can't flash an older SBF file, that will cause you to brick. The SBF files you should avoid are pretty much all of them except Gingerbread, Unlock, and Radio SBF's.
You can unlock your device even though you've updated. But you're stuck with that bootloader forever, but you can always downgrade with a fruit cake I believe.
It all seems confusing at first, but you'll get the hang of it!
Sinful Animosity said:
It all seems confusing at first, but you'll get the hang of it!
Click to expand...
Click to collapse
Thanks for the vote of confidence! I had run several custom roms on my G1, but much less of that experience is proving to be helpful than I had hoped.
Thanks everyone for your speedy replies, I'll go give pudding a shot after breakfast.
if i flash pudding, just the unlock part and then fastboot the unlock....will i have to load a rom, or will gingerbread 2.34 still be there?
Okay, so the official pudding thread recommends beginners follow Brief Mobile's BL unlocking guide. I did, and got the message "oem unlock is not implemented". However, the 1st step in the guide is "If you’re on Gingerbread, skip to step 13". I am on GB from the OTA, but the guide was published a month ago, before the OTA update.
I'm guessing they said that because at the time it was published, you would need to have already done those steps to be on GB, so I may need to go back and follow through all the steps I skipped the first time. But if they had GB users skip steps because they would be harmful to GB phones, then that would be bad... Advice?
Incognitum said:
Okay, so the official pudding thread recommends beginners follow Brief Mobile's BL unlocking guide. I did, and got the message "oem unlock is not implemented". However, the 1st step in the guide is "If you’re on Gingerbread, skip to step 13". I am on GB from the OTA, but the guide was published a month ago, before the OTA update.
I'm guessing they said that because at the time it was published, you would need to have already done those steps to be on GB, so I may need to go back and follow through all the steps I skipped the first time. But if they had GB users skip steps because they would be harmful to GB phones, then that would be bad... Advice?
Click to expand...
Click to collapse
Go through the whole thing. If you soft brick, just run fastboot oem unlock again.
Thx for the help and quick response everybody, I will try to put all the step together and get the ULBL, xda always there indeed
fanhtc2 said:
Thx for the help and quick response everybody, I will try to put all the step together and get the ULBL, xda always there indeed
Click to expand...
Click to collapse
Thanks for opening this thread. I was gonna ask the same thing . Now I know what to do...I did OTA as well. Awesome that I can still unlock the bootloader.
Sent from my MB860 using XDA App
Step by step ULBL, Root for OTA GB
**I've been getting PMs for clarification: I didn't do a single mod to my phone before this morning. Stock ATT/Moto Atrix, installed stock ATT/Moto OTA GB update yesterday. Following these steps I am now BLUL and rooted.**
So here are all the steps needed to get a stock, OTA Gingerbread Atrix Unlocked and rooted:
1. Follow Brief Mobile's BL unlock guide here.
Things I found out that you may like to know:
-You will need to complete all steps *even the ones the guide says to skip*.
-When you enter your device unlock code, it is case sensitive; use caps-lock.
-The most recent SBF flash is in the XDA IHOP pudding thread, use this instead of the older file linked to in the Brief Mobile guide.
-When you are done, reboot will take a *long* time; just stay calm.
Edit: After 30 min on the dual core screen with the "unlocked" in the corner I pulled the battery... after reboot everything seems fine.
2. Follow Brief Mobile's guide to root here.
Thanks to brief mobile, and to the xda folks who held my hand through this whole thing the first time
Incognitum said:
So here are all the steps needed to get a stock, OTA Gingerbread Atrix Unlocked and rooted:
1. Follow Brief Mobile's BL unlock guide here.
Things I found out that you may like to know:
-You will need to complete all steps *even the ones the guide says to skip*.
-When you enter your device unlock code, it is case sensitive; use caps-lock.
-The most recent SBF flash is in the XDA IHOP pudding thread, use this instead of the older file linked to in the Brief Mobile guide.
-When you are done, reboot will take a *long* time; just stay calm.
2. Follow Brief Mobile's guide to root here.
Thanks to brief mobile, and to the xda folks who held my hand through this whole thing the first time
Click to expand...
Click to collapse
i love you. (no homo..not that theres anyway wrong with that)....THANKS!
defnow said:
i love you. (no homo..not that theres anyway wrong with that)....THANKS!
Click to expand...
Click to collapse
Hey, I appreciate it, and I'm glad to help! But honestly, I stopped at each step and asked the experts what to do, and then just wrote down in one post everything they told me.
I'm glad it's saving time for those coming behind me, but the real thanks belongs to the guys who helped me through it this morning; thanks again guys!
Hello all!
I am finally ready to unlock my prime after using it on stock for the last year.
I was wondering if the Asus Unlock Tool is still relevant as I cannot find it in their downloads on the Global Website and I see very little mention in the up to date user posts or stickies about unlocking the bootloader.
I have seen this firmware update notification for several months and as I have read around, it is imperative that I perform the Nvflash before updating to JB. In order to protect myself from bricking my device I will need to unlock the bootloader before Nvflash.
If anyone has further information which could help me with this task, I would greatly appreciate a push in the right direction.
I am running Android 4.0.3 with build IML74K.WW_epad-9.4.2.28-20120525
Thanks!
Or if anyone has recently unlocked their bootloader while on ICS, could point me in the direction of how you did it?
Kensh said:
Or if anyone has recently unlocked their bootloader while on ICS, could point me in the direction of how you did it?
Click to expand...
Click to collapse
It's been so long since I did it but you just need to do things one step at a time.
First of all run the unlock tool. Once you have the prime unlocked go to the nvflash website and grab the 2 zips you need and extract them both into one folder.
Now you just need to go thru the commands it tells you one at a time. It looks complicated but really there is only about 5 lines for you to cut and paste in.
Just remember that the first lot of files it creates will be on the primes sdcard and you need to pull them to the pc. The second lot it makes goes straight into the same folder on the pc as where you are running wheelie from.
P. S. It took me longer to write this than it does for me to do it lol
Greetings
I foolishly upgraded my tablet to the latest version (4.2.2) before rooting my device. I understand that 4.2.2 cannot be rooted at this time. If I am wrong, please let me know.
So....I downloaded EMMA, unlocked my tablet, installed EMMA and proceeded to (as I though) downgrade to 4.1.2, in order to root the tablet and then upgrade.
EMMA happily installed the downgrade and indicated it was successful. Upon restarting my tablet, I noticed that I still had 4.2.2. I tried to again install the downgrade, but no luck.
I did do a complete backup of my data, so after reinstalling my apps, I was able to restore data and get my tablet back to its original (4.2.2) state. Of course, I am sitting with an unlocked device. I did not see any way on EMMA to relock the bootloader.
Without overly trying the patience of those who have far more knowledge of these matters than I, here are a few questions:
-why didn't the downgrade take?
-given I have an unlocked device, is there an alternate method to downgrade, root, protect root, upgrade and relock device?
-if number 2 is not possible what is the easiest and quickest way to relock the bootloader.
-is rooting 4.2.2 a question of when or if?
I would like to thank you all for reading this and any help you have to offer.
Have a good day.
gderreck said:
Without overly trying the patience of those who have far more knowledge of these matters than I, here are a few questions:
-why didn't the downgrade take?
-given I have an unlocked device, is there an alternate method to downgrade, root, protect root, upgrade and relock device?
-if number 2 is not possible what is the easiest and quickest way to relock the bootloader.
-is rooting 4.2.2 a question of when or if?
I would like to thank you all for reading this and any help you have to offer.
Have a good day.
Click to expand...
Click to collapse
Emma does not downgrade. It only installs the latest ROM ("service") for your device. It wrongly shows you the previous version in the list of services available (.370 for example for my 311). If you view the ''service" details in the bottom of the right-hand panel in Emma, you will see it actually refers to the latest ROM, not the previous.
Also, as far as I know, you cannot re-lock your bootloader with Emma. You will have to use Flashtool - search these forums or Google it for a "how to". Why do you want to re-lock?
There is a way to get root on 4.2.2 if you have an unlocked bootloader, see here :
http://forum.xda-developers.com/showthread.php?t=2392092&page=24 , post #232. I have not tried this myself, so I can't say if it works.
A little tip for you - when asking a question here, please state your device version (311, 312 or 321).
gderreck said:
Greetings
I foolishly upgraded my tablet to the latest version (4.2.2) before rooting my device. I understand that 4.2.2 cannot be rooted at this time. If I am wrong, please let me know.
So....I downloaded EMMA, unlocked my tablet, installed EMMA and proceeded to (as I though) downgrade to 4.1.2, in order to root the tablet and then upgrade.
EMMA happily installed the downgrade and indicated it was successful. Upon restarting my tablet, I noticed that I still had 4.2.2. I tried to again install the downgrade, but no luck.
I did do a complete backup of my data, so after reinstalling my apps, I was able to restore data and get my tablet back to its original (4.2.2) state. Of course, I am sitting with an unlocked device. I did not see any way on EMMA to relock the bootloader.
Without overly trying the patience of those who have far more knowledge of these matters than I, here are a few questions:
-why didn't the downgrade take?
-given I have an unlocked device, is there an alternate method to downgrade, root, protect root, upgrade and relock device?
-if number 2 is not possible what is the easiest and quickest way to relock the bootloader.
-is rooting 4.2.2 a question of when or if?
I would like to thank you all for reading this and any help you have to offer.
Have a good day.
Click to expand...
Click to collapse
Have a look here for downgrade instructions:
http://forum.xda-developers.com/showthread.php?t=2427256
I've done it yesterday and am glad i got rid of that dreadful phablet UI.
Thank you both for your replies. Mode is SGP311. I bought it from Sony Canada. I'm not sure if that is significant. Would I be correct in guessing that the US firmware is different from the Canadian version?
Thanks
gderreck said:
Thank you both for your replies. Mode is SGP311. I bought it from Sony Canada. I'm not sure if that is significant. Would I be correct in guessing that the US firmware is different from the Canadian version?
Thanks
Click to expand...
Click to collapse
Take a look here:
"http://forum.xda-developers.com/showthread.php?t=2433466"
Given that you have a SGP311, you should be able to root stock 4.2.2 using this.
Hello everyone.
I had posted this in the Z forum, not realizing there was a Z Ultra forum. So I will just quote my previous post and add some info at the end:
Hello guys. New guy here with an Xperia Z Ultra phone.
I'm trying to load the Paranoid Android custom ROM.
Had a couple of questions:
1. I went thru Sony's instructions to unlock the bootloader. When I ran the fastboot -i 0x0fce oem unlock (e-mail code), the first error message I got was "FAILED - Remote - Command did not succeed". So I tried the exact command again, and then I got "FAILED - Remote: The device is already rooted".
I have searched high and low, and cannot seem to find any way to verify that the bootloader is now in fact unlocked.
2. Reading the instruction on how to install CWM/TWRP recovery menus, Every single list of instructions includes the following "This tutorial is only for Sony Xperia Z Ultra with 510 and 493 LTE firmware. Do not use it for any other carriers or variants"
Again, I have searched high and low to find a way to confirm what firmware version I have. All I know is I have the C6806 model, with the build number: 14.2.A.0.290
So can someone please help out a very confused guy here? I don't want to brick my phone by accident
So far it's still working ok
Click to expand...
Click to collapse
So far, after doing some major searching, I seem to have found that I currently have "290" Firmware, and that this Firmware is currently NOT able to be rooted. Is this correct?
Also, I still have not found a way to verify wether the boot loader actually did unlock or not. From what I have been able to read, it seems that if a proper boot loader was in fact, unlocked, it would have wiped all the data on my phone along with the SD card data.
So far, it seems everything on my phone is intact. So does this mean the boot loader unlock command failed for me? If so, why did I get the reply "this device is already rooted?"
I can't believe how difficult it is to root a damn Android phone! Jailbreaking an Apple device is 10 times easier!
First of all, it's usually pretty easy to root Android devices. In most cases it's only a simple click, but sony has done a good(?) job at fixing exploits, so it does it much harder for us.
Second, you can check if your bootloader is locked or unlocked by opening the dialer and insert *#*#7378423#*#*, go to "Service Info" and then "Configuration". If your bootloader is unlocked, it should say "Rooting status: Bootloader unlocked: Yes". It's easier to use Flashtool to unlock the bootloader if you're having issues using a terminal.
You'll find the rest here (including bootloader unlocking). If you need some help, ask in that thread.
If you aren't boot loader unlocked then "BACKUP TA PARTITION" from My Lord's guide @LordManhattan
Just incase you need to re-lock it for service
LordManhattan said:
First of all, it's usually pretty easy to root Android devices. In most cases it's only a simple click, but sony has done a good(?) job at fixing exploits, so it does it much harder for us.
Second, you can check if your bootloader is locked or unlocked by opening the dialer and insert *#*#7378423#*#*, go to "Service Info" and then "Configuration". If your bootloader is unlocked, it should say "Rooting status: Bootloader unlocked: Yes". It's easier to use Flashtool to unlock the bootloader if you're having issues using a terminal.
You'll find the rest here (including bootloader unlocking). If you need some help, ask in that thread.
Click to expand...
Click to collapse
First of all it' pretty damn complicated and unrewarding to root a Sony device. Not all android but Sony definately. We checked, bootloader is unlockable. We unlocked and relocked bootloader prevoiusly because there is no robust, easy-to-install ROM for ZU. But time to time we try to root it.
Now, the question is the same: what should we do to re-unlock the bootloader if anything is OK, but flashtool says "Command did not succeed" for the first time and "Device is already rooted" for subsequent times at unlocking?
Please write some advice about the question, not about TA backup and your success. Thx!
Champdor said:
First of all it' pretty damn complicated and unrewarding to root a Sony device. Not all android but Sony definately. We checked, bootloader is unlockable. We unlocked and relocked bootloader prevoiusly because there is no robust, easy-to-install ROM for ZU. But time to time we try to root it.
Now, the question is the same: what should we do to re-unlock the bootloader if anything is OK, but flashtool says "Command did not succeed" for the first time and "Device is already rooted" for subsequent times at unlocking?
Please write some advice about the question, not about TA backup and your success. Thx!
Click to expand...
Click to collapse
Oh, are we demanding help now?
Bootloader unlocking is a straight forward process. I've had a couple of strange errors in Flashtool while trying to unlock the bootloader, but just close Flashtool and try again. Also be sure to be on the latest version of Flashtool.
LordManhattan said:
Oh, are we demanding help now?
Bootloader unlocking is a straight forward process. I've had a couple of strange errors in Flashtool while trying to unlock the bootloader, but just close Flashtool and try again. Also be sure to be on the latest version of Flashtool.
Click to expand...
Click to collapse
No sir, not at all. I wrote please, no demanding. Well yes, I'm a bit picky because there were no answer and I usually find some on XDA. Besides I used custom roms on Samsung devices for years (SGS2, SGN, SGN2) and I was disapponted when I bought my XZU that there are very few roms and I couldn't use them (I managed with very hard work to go back to stock in 9 hours after unsuccesful flashing).
So there is some basic problem every time. Like trying to root but cannot re-unlock because of some mysterious errors with no solutions.
Enough of my problems, your answer is much appreciated, will try to re-unlock some time. Thx!
Champdor
Champdor said:
No sir, not at all. I wrote please, no demanding. Well yes, I'm a bit picky because there were no answer and I usually find some on XDA. Besides I used custom roms on Samsung devices for years (SGS2, SGN, SGN2) and I was disapponted when I bought my XZU that there are very few roms and I couldn't use them (I managed with very hard work to go back to stock in 9 hours after unsuccesful flashing).
So there is some basic problem every time. Like trying to root but cannot re-unlock because of some mysterious errors with no solutions.
Enough of my problems, your answer is much appreciated, will try to re-unlock some time. Thx!
Champdor
Click to expand...
Click to collapse
Oh, i get that. I came from Samsung myself, and this is my first Sony device ever, so I've had some issues myself. I've gotten the same error message(s) as you before, and i think i restarted Flashtool and rebooted my Ultra and it was back to normal again - i think, but it "fixed itself" after trying a couple of times, so don't give up. It's also important to always be on the latest version of Flashtool.
It would also help us if you could tell us what you're trying to achieve, so you don't end up spending 9 hours on something that takes 5 minutes
@Champdor
From what I can make out you have never managed root your phone or back up the TA. If the latter is true then there is very little point in relocking the bootloader.
Yes the process is a little harder than Samsung, but the last device I rooted was a ZTE, and that was even harder to root and flash from what I can remember (yes this is my first Sony device as well, and I will buy another...)
Take you time and read the stickies that we have written and all should go well. Don't be afraid to ask (intelligent) questions if you get stuck, and read some more
HELP!
i am in same situation as OP
in past, i unlocked the bootloader then i relocked.
now I like to re-unlock. but I get same errors (i.e. 'command did not suceed' or 'device is already rooted')
i check service menu and it says 'bootloader unlock allowed: yes' meaning its not unlocked yet.
i use latest flashtool and try to unlock but i get error
can any expert help!?
thanks for your help
corrado85 said:
HELP!
i am in same situation as OP
in past, i unlocked the bootloader then i relocked.
now I like to re-unlock. but I get same errors (i.e. 'command did not suceed' or 'device is already rooted')
i check service menu and it says 'bootloader unlock allowed: yes' meaning its not unlocked yet.
i use latest flashtool and try to unlock but i get error
can any expert help!?
thanks for your help
Click to expand...
Click to collapse
I have not had this error so have not tested this, but what happens if you flash a full FTF and wipe everything then try to unlock the BL?
And remember that you can take a backup of the unlocked BL (re member to name it as such) and just flash that to unlock again. Doing it this way you don't get the format that happens when using the unlock code.
I followed this post to downgrade, root, i use Backup TA v9.10 to backup DRM Keys, use Flashtool 0.9.14.0 to unlock Bootloader, then to flash other Rom's (stock and customs), came back to Stock Rom .681, relock the Bootloader with Flastool 0.9.15.0 flashed the last .757 and unlock the Bootloader again with no kind of problems using Flashtool 0.9.15.0....
blueether said:
I have not had this error so have not tested this, but what happens if you flash a full FTF and wipe everything then try to unlock the BL?
And remember that you can take a backup of the unlocked BL (re member to name it as such) and just flash that to unlock again. Doing it this way you don't get the format that happens when using the unlock code.
Click to expand...
Click to collapse
I just flashed C6802 .757 FW using flashtool, and i get same issue
is there a tutorial about backup of the unlocked BL? assuming you meant I have to have own device backup..
this is so confusing at the end :crying:
corrado85 said:
I just flashed C6802 .757 FW using flashtool, and i get same issue
Click to expand...
Click to collapse
I dont know what else to suggest other than rebooting every thing and reinstalling all the drivers
is there a tutorial about backup of the unlocked BL? assuming you meant I have to have own device backup..
this is so confusing at the end :crying:
Click to expand...
Click to collapse
You just back it up as you would for a locked BL. Just remember to make sure you name them well so you know which is the locked one and the unlocked one.
NEVER use a TA backup from another phone, you WILL HARD BRICK IT
Lc1975 said:
I followed this post to downgrade, root, i use Backup TA v9.10 to backup DRM Keys, use Flashtool 0.9.14.0 to unlock Bootloader, then to flash other Rom's (stock and customs), came back to Stock Rom .681, relock the Bootloader with Flastool 0.9.15.0 flashed the last .757 and unlock the Bootloader again with no kind of problems using Flashtool 0.9.15.0....
Click to expand...
Click to collapse
problem is i get message 'device already rooted' when i enter my bootloader key using flashtool as well
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
blueether said:
I dont know what else to suggest other than rebooting every thing and reinstalling all the drivers
You just back it up as you would for a locked BL. Just remember to make sure you name them well so you know which is the locked one and the unlocked one.
NEVER use a TA backup from another phone, you WILL HARD BRICK IT
Click to expand...
Click to collapse
ahh ok, in that case, i do not have a backed up unlocked bootloader rom
corrado85 said:
problem is i get message 'device already rooted' when i enter my bootloader key using flashtool as well
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
ahh ok, in that case, i do not have a backed up unlocked bootloader rom
Click to expand...
Click to collapse
Did you tried:
*#*#SERVICE#*#*
and confirm that the Bootloader is unlock?
Lc1975 said:
Did you tried:
*#*#SERVICE#*#*
and confirm that the Bootloader is unlock?
Click to expand...
Click to collapse
It states
Rooting status
Bootloader unlocked allowed:Yes
corrado85 said:
It states
Rooting status
Bootloader unlocked allowed:Yes
Click to expand...
Click to collapse
When you try to unlock the Bootloader.. What button or icon do you click?
The one who has the padlock or BLU?
Lc1975 said:
When you try to unlock the Bootloader.. What button or icon do you click?
The one who has the padlock or BLU?
Click to expand...
Click to collapse
I choose which states 'BLU'
actually I do get the option to click on padlock but i dont know what to do there
corrado85 said:
I choose which states 'BLU'
actually I do get the option to click on padlock but i dont know what to do there
Click to expand...
Click to collapse
The padlock is to root the device..
Sorry but i can't help you much more then this... I don't have much knowledge to go foward...
Try to start from scratch..
Downgrade...
Root...
Try to unlock the Bootloader
And update to the latest...
root didnt work
Hello , i want to root my phone z ultra 6833 .757 i watch this video youtube . com/watch?v=uFSeSe8gQOY
i unlock bootloader after this install 757.img by flashtool so i can open recovery but after this i didnt find the same file he run i try run supersu.zip but the phone havent rooted plz what the problem
I have a new xperia z ultra c6806
Read a lot but still confused. ( Not everybody is made equal )
I want to root and back up TA
1 - My understanding is for backing up TA, i need to be rooted. But for rooting I need to be unlocked. But unlocking will erase the TA information. Am I wrong.
2- If I unlock boatloader can I flash back to pure stock for either warranty or returning the device.
Thanks
C6806 eh?
- Open the dialer and dial *#*#7378423#*#*
- Go to Service Info -> Configuration and check what is says under "Rooting status". Does it say Yes or No?
If it says yes, go ahead and downgrade to 532 and root it using Bin4ry's root tool, backup your TA partition and then unlock the bootloader, update to 757 again and flash Jackie's kernel and flash SuperSU. You can find links and what not here.
LordManhattan said:
C6806 eh?
- Open the dialer and dial *#*#7378423#*#*
- Go to Service Info -> Configuration and check what is says under "Rooting status". Does it say Yes or No?
If it says yes, go ahead and downgrade to 532 and root it using Bin4ry's root tool, backup your TA partition and then unlock the bootloader, update to 757 again and flash Jackie's kernel and flash SuperSU. You can find links and what not here.
Click to expand...
Click to collapse
Thanks for the reply
It says " Bootloader unlock allowed: Yes
So I guess, I will follow what you are saying
One thing; don't panic when you're noticing that you're not getting any signal at all (cell, WiFi etc.). That's the way it is when you're downgrading the baseband past .290, but you're only going to be on 532 for a short period of time, so it's no big deal. You'll get your signal back once you're back on 757.
LordManhattan said:
One thing; don't panic when you're noticing that you're not getting any signal at all (cell, WiFi etc.). That's the way it is when you're downgrading the baseband past .290, but you're only going to be on 532 for a short period of time, so it's no big deal. You'll get your signal back once you're back on 757.
Click to expand...
Click to collapse
Got 532 installed and unlocked but now cant update to 757.... Pc companion is saying I am uptodate..
There seems to be no link to download 6806 757 firmware
Edit : oofff ... finally got everything working.. That was lot of work...
aalupatti said:
Got 532 installed and unlocked but now cant update to 757.... Pc companion is saying I am uptodate..
There seems to be no link to download 6806 757 firmware
Edit : oofff ... finally got everything working.. That was lot of work...
Click to expand...
Click to collapse
So you figured out that you had to use Flashtool? You backed up TA? And you managed to unlock the bootloader and root?
Don't worry, this is a one time thing. The boring stuff is the downgrading and backup of TA, so since you've backed it up, it's done. If you have to relock your bootloader and un-root for whatever reason and you want to root again, you don't have to do this again. You then have to unlock the bootloader and simply flash a kernel.
Sent from my C6833
LordManhattan said:
So you figured out that you had to use Flashtool? You backed up TA? And you managed to unlock the bootloader and root?
Don't worry, this is a one time thing. The boring stuff is the downgrading and backup of TA, so since you've backed it up, it's done. If you have to relock your bootloader and un-root for whatever reason and you want to root again, you don't have to do this again. You then have to unlock the bootloader and simply flash a kernel.
Sent from my C6833
Click to expand...
Click to collapse
My issue was downgrading and some driver issues with windows 8. All went well..
However now when I reboot I get this error " System UID's are inconsistent, you need to wipe your data partition or your device will be unstable"
But fixed that using twrp
I cant believe how good quality the phone hardware is.. Was using samsung for the last few years...
I am waiting for the next generation of z ultra and going to get that too.... Wish they introduce qi charging...