GETTING YOUR ULTRA ROOTED AND
READY FOR FLASHING
This guide should in theory make your Ultra ready for flashing custom ROMs, and with that said...
...here comes the warning: Your warranty is now voided. I am not responsible for bricked
devices, or whatever you might end up with.
TABLE OF CONTENT
ROOT ALL THE THINGS
ROOTING .108
ROOTING .757
ROOTING .681
ROOTING .290/.136
ROOTING .532
ROOTING GPe
DOWNGRADING
BACKUP TA PARTITION
CHANGE CDA
UNLOCKING THE BOOTLOADER
INSTALLING RECOVERY AND TWRP
FLASHING A CUSTOM ROM
BACK TO STOCK
BOOTLOOP
MISSING IMEI
CREDITS
BACKUP YOUR TA PARTITION BEFORE YOU UNLOCK THE BOOTLOADER
IF YOU'RE NEW AROUND HERE AND YOU WANT TO ROOT .757, DOWNGRADE TO .532 AND ROOT, AND THEN BACKUP YOUR TA PARTITION. PROCEED TO UNLOCK YOUR BOOTLOADER, UPGRADE TO .757 AGAIN AND ROOT BY FOLLOWING THE SHORT GUIDE HERE.
ROOT ALL THE THINGS:
Thanks to @geohot, we're now able to root (almost) all the things, meaning there is now one tool for rooting. This tool doesn't touch the bootloader, so it also works on locked bootloaders. Be sure to backup your TA partition after you've rooted (in case you want to unlock the bootloader). You can find the tool here.
Note: This tool will not work on the GPe model.
ROOTING .108:
Go to this thread and follow the steps.
ROOTING .757:
Same procedure as with .681, so just go to this thread and follow the steps. Requires an unlocked bootloader.
ROOTING .681:
Rooting .681 (first KitKat build) is pretty straight forward and requires an unlocked bootloader.
After that, just flash the kernel and then SuperSU. You can download and follow the short guide here. The kernel includes Recovery.
ROOTING .290/.136:
.290
• Unlocked bootloader: Follow this thread.
• Locked bootloader: Follow this thread.
.136
• Unlocked bootloader: Follow this thread.
ROOTING .532:
• Use this tool to root
ROOTING GPe:
GPe OWNERS: DO NOT TRY TO FLASH FTFs OR OTHER "XPERIA" ROMs AND KERNELS.
YOU WILL BRICK YOUR DEVICE.
Go to this thread and follow the steps. Thanks to @blueether.
DOWNGRADING:
• Download and install Flashtool (if you're running Windows 8, follow this installation guide) (Jump down to "Part 2" of the guide)
• If you're having issues with driver installation, install this one.
If you have issues, or simply have no clue how to install ADB and Fastboot, install and run this.
• Download NUT's 532 firmware from here
• Flash it by following this short guide
BACKUP TA PARTITION:
The TA partition holds all your unique DRM keys, and X-Reality won't work without it (except if you're on .681 or later).
Once you lose it, you can't get it back, so back it up and upload it to your Dropbox or something. So how do you backup your TA partition?
• Download this tiny tool on your computer and run it.
Here's a video tutorial by @hamdogg
CHANGE CDA (OLD):
This step is no longer necessary.
• Install a file explorer from the Play Store. I recommend Solid Explorer or ES File Explorer.
• Navigate to /system and open build.prop
• Change your CDA to: C6833_1275-8026 (there are three different places this has to be changed.
Just take your time and try to find something that resembles the CDA code above.
• Next you'll want to find "ro.somc.customerid" and change it to 436
• Next you'll want to find "ro.semc.version.cust_revision" and change it to R11A
• Now reboot your device
• The OTA update should arrive now. If it doesn't, go to "Update Center" (app) and manually refresh.
• Update to 257
• The root app (i'm not sure what app it installs) might be gone, so just install
SuperSU from the Play Store if it's not in your app drawer anymore. Update binaries and choose "Normal".
UNLOCKING THE BOOTLOADER:
This may wipe your phone, so backup your stuff
• Go to Sony's dev site
• Request the unlock key and check your mail straight away. Email is quick these days.
• Open Flashtool on your computer (yes, the one you installed earlier)
• Click the "BLU" icon
• Follow the steps and enter your unlock key
INSTALLING RECOVERY AND TWRP:
• Just run this tool on your computer.
• Boot into Recovery (POWER + VOL UP)and take a NAND backup ASAP.
It'll "save your life" (or time) when you're soft bricking your Ultra.
FLASHING A CUSTOM ROM:
• Find a ROM
• Move the ROM (and gapps if it is required) to a folder on your Ultra and remember where you put them
• You'll see that you'll need to flash a "boot.img" before you flash anything, so download this
• Now go to this thread and download QuickIMG and follow the short guide
• Flash the boot.img
• Now unplug from the computer and enter Recovery by pressing the Power button.
Once you see the green LED, push and hold VOL UP. If you fail, just press and hold POWER + VOL UP until you
notice some rapid vibrations. Now try again.
• Once you're in Recovery it's the usual stuff. Flash the ROM and gapps and wipe data/cache/dalvik etc.
• Reboot
BACK TO STOCK:
So you have to send your Ultra to a service center and you want to get it back to 100% stock.
Be sure to be on a STOCK kernel before restoring the TA partition or re-locking the bootloader.
• Restore your TA partition using the tool from the "Backup TA Partition" part of this guide.
• If your bootloader hasn't been locked by the TA tool, use Flashtool and press the BLU button and choose "Relock".
• You may not be able to boot now if you're on a custom ROM, so fire up Flashtool again and flash a stock ROM.
BLINKING RED LED:
So, you locked it while on a custom kernel, and all you get now is a blinking red LED above your screen.
Simply unlock the bootloader in Flashtool again, and it'll work again.
You should now be back on stock, un-rooted and with TA and bootloader in place. If you're back on stock,
but the bootloader is still unlocked, get back to 532, root, lock the bootloader, and then flash a FTF in Flashtool again.
BOOTLOOP:
You've ended in a bootloop and you have no idea what to do. A bootloop is when the boot animation is looping, and you're stuck.
We'll start out easy and go harder as we go down the list.
• [SAFE] Boot into Recovery and wipe cache and go to "Advanced" and wipe Dalvik. Reboot and see if it boots now.
• [SAFE] Boot into Recovery and re-flash the ROM and see if that does the job
• [WIPE] Boot into Recovery and wipe data (this will wipe everything) and reboot
• [WIPE] Boot into Recovery and flash a different ROM (wipe data after flash) and reboot
• [LAST RESORT] Fire up Flashtool and flash a stock FTF and get a new hobby
MISSING IMEI:
You downgraded from 290 or later, didn't you? Well, you'll have to update again or flash [NUT]'s .532 build.
CREDITS:
- @herogjan - The mighty discoverer of the OTA root method
- @krabappel2548 - The Belgian Don (guides, ROMs etc.)
- @RyokoN - ROOT Wizard
- @hamdogg - Bootloader help
- @fastest83 - Achievement unlocked [1/168]
- @sfagundes - For the GPe root guide
- @hamdogg - For helping people and for the video(s)
- [FONT=Arial [user=3534362]@blueether[/user] - For helping an incredible amount of people around here[/FONT]
LordManhattan said:
............
DOWN THE ROAD:
"I want to go back! Back to stock!"
- Boot into Recovery and restore the NAND backup you made after you installed Recovery. If you didn't; "son, i am disappoint".
CREDITS:
- @herogjan - The mighty discoverer of the OTA root method
- @krabappel2548 - The Belgian Don (guides, ROMs etc.)
- @RyokoN - ROOT Wizard
- @LarryPage - Coffee
Click to expand...
Click to collapse
Maybe/sometime you will loose(?) the recovery after the backup restored. It happen to me at the latest back-to-stock from CM10.2.
I just need to get the recovery back with this:
http://forum.xda-developers.com/showthread.php?t=2426739
abuihsan said:
Maybe/sometime you will loose(?) the recovery after the backup restored. It happen to me at the latest back-to-stock from CM10.2.
I just need to get the recovery back with this:
http://forum.xda-developers.com/showthread.php?t=2426739
Click to expand...
Click to collapse
Shouldn't happen if your backup already has the right kernel with Recovery, but i've seen stranger things happen, so i'll add that if it happens, then just re-install Recovery. Thanks
LordManhattan said:
Shouldn't happen if your backup already has the right kernel with Recovery, but i've seen stranger things happen, so i'll add that if it happens, then just re-install Recovery. Thanks : )
Click to expand...
Click to collapse
Yes it strange as it only happen with my latest back-to-stock. my stock backup is with rooted .257 where as far as I know still don't have proper kernel+recovery like .526 or .532 has.
Bread guide will help me when I want to get gpe rom on my ultra.
Nice guide, where was it last week?
Would it be possible for you to add a "So you need so send your ZU back to Sony" section covering restoring the TA partition and relocking the bootloader?
LordManhattan said:
Shouldn't happen if your backup already has the right kernel with Recovery, but i've seen stranger things happen, so i'll add that if it happens, then just re-install Recovery. Thanks
Click to expand...
Click to collapse
abuihsan said:
Maybe/sometime you will loose(?) the recovery after the backup restored. It happen to me at the latest back-to-stock from CM10.2.
I just need to get the recovery back with this:
http://forum.xda-developers.com/showthread.php?t=2426739
Click to expand...
Click to collapse
abuihsan said:
Yes it strange as it only happen with my latest back-to-stock. my stock backup is with rooted .257 where as far as I know still don't have proper kernel+recovery like .526 or .532 has.
Click to expand...
Click to collapse
I have noticed when I restored my nand a couple times when I then try reboot it comes up about not installing stock recovery there's about 10 no's which if you click installs stock you need to click the one yes not install stock recovery....
Sent from my HTC One using Tapatalk
pTeronaut said:
Nice guide, where was it last week?
Would it be possible for you to add a "So you need so send your ZU back to Sony" section covering restoring the TA partition and relocking the bootloader?
Click to expand...
Click to collapse
Sure, but I'm busy right now so that has to wait.
Sent from my C6833 using Tapatalk
LordManhattan said:
Sure, but I'm busy right now so that has to wait.
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
requested sticky...
here is a video I made on how to backup TA partition. also discusses what to do to restore your TA partition..
youtube ID : 8TowVR7CNQQ
I'll do a more comprehensive video in 3 days I hope... but for the moment this should be fine.
feel free to shove that in the OP
PS... can't believe that I'm the only one thats said thanks so far... tick... tick... BOOM!
Alright, i can add the "going back to stock" part, but i have never relocked the bootloader and restored the TA, so i'm not sure in what order we should do it. Relocking the bootloader is easy. Just use the TA backup tool and restore your backup, and it will lock the bootloader again. But, here's my question. This requires root, so we can't do it when we've flashed the stock firmware using Flashtool since we'll lose root. So i guess if a person is running CM, he'll have to restore TA and also lock the bootloader while on CM, but this will cause a soft brick, but then he can just flash the stock TFT in Flashtool?
Any ideas? I'm asking because i don't want to write something that's not 100% right.
hamdogg said:
requested sticky...
here is a video I made on how to backup TA partition. also discusses what to do to restore your TA partition..
youtube ID : 8TowVR7CNQQ
I'll do a more comprehensive video in 3 days I hope... but for the moment this should be fine.
feel free to shove that in the OP
PS... can't believe that I'm the only one thats said thanks so far... tick... tick... BOOM!
Click to expand...
Click to collapse
@hamdogg Added! And thank you Btw, do you have any ideas regarding my relocking of the bootloader? Check my post above this one.
LordManhattan said:
Alright, i can add the "going back to stock" part, but i have never relocked the bootloader and restored the TA, so i'm not sure in what order we should do it. Relocking the bootloader is easy. Just use the TA backup tool and restore your backup, and it will lock the bootloader again. But, here's my question. This requires root, so we can't do it when we've flashed the stock firmware using Flashtool since we'll lose root. So i guess if a person is running CM, he'll have to restore TA and also lock the bootloader while on CM, but this will cause a soft brick, but then he can just flash the stock TFT in Flashtool?
Any ideas? I'm asking because i don't want to write something that's not 100% right.
Click to expand...
Click to collapse
I ever restored TA backup once but that was before I flash Cm at the first time.
When I back-to-stock by restoring nand, bootloader still unlocked.
I wondered if we have nandroid stock (with locked bootloader) , then we unlock, then we flash CM or other custom roms,
can we then just restore the nandroid stok (with locked boot loader) without any problem and we will have our TA partition back and relocked without restore the TA first?
LordManhattan said:
@hamdogg Added! And thank you Btw, do you have any ideas regarding my relocking of the bootloader? Check my post above this one.
Click to expand...
Click to collapse
When I sent mine in for repair I had to reroot first... But most people will be rooted.. so:
1)restored the TA partition,
2)locked the bootloader (checked after restoring the TA partition and it was still unlocked)
3)flashed a stock FTF.
Then it was completely stock.
Post this in the OP for locking bootloader
____________________________________________________________________________________________
Download the latest flashtool from:
http://ul.to/3kjpyj70 [v0.9.13.0]
Before you relock the bootloader you have to be on a stock kernel or else the device WILL NOT BOOT.
-We recommend that you will need to return to a Sony STOCK FTF if you are currently on a custom ROM-
Steps:
1) Download Flashtool. Start Flashtool and click on BLU button
2) You will be asked to connect device in flashmode
3) Once you connect the device, you'll be prompted to "Relock"
4) Click on it, and when prompted, disconnect your Ultra
Thanks, I'll add it to the guide in a couple of minutes
Sent from my C6833 using Tapatalk
LordManhattan said:
Thanks, I'll add it to the guide in a couple of minutes
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
there is a new flashtool driver version too. It probably wont matter... but you could add it into the FAQ section or something. For those having issues with flashtool...
v1.1 drivers for flashtool and xperia 2013 devices.
http://d-h.st/Wyk
Thank you very much! I've added it under downgrading, and I also added the ADB and Fastboot Windows installer for people that have trouble installing those manually.
Sent from my C6833 using Tapatalk
Oh me gawd. Information overload
WoW. Very Read. Total Information. Much Thanks. WoW.
{
"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"
}
Srsly thou. Great job
Sent from my Xperia Z Ultra using Tapatalk 4
LordManhattan said:
- You'll see that you'll need to flash a "boot.img" before you flash anything, so download this
- Now go to this thread and download QuickIMG and follow the short guide
- Flash the boot.img
Click to expand...
Click to collapse
I didn't need to do that. I was on stock Sony build 257 and had never flashed AOSP before. All I did was root the phone, update OTA, install recovery and just flash a ROM. Looks like Sony's official unlock is unlike HTC dev unlock and doesn't need a PC (fastboot) to flash ROMs.
ChillyChan said:
I didn't need to do that. I was on stock Sony build 257 and had never flashed AOSP before. All I did was root the phone, update OTA, install recovery and just flash a ROM. Looks like Sony's official unlock is unlike HTC and doesn't need a PC (fastboot) to flash ROMs.
Click to expand...
Click to collapse
Yeah, it seems like it's a hit or miss with the whole boot.img. First time i tried to flash Omni (coming from 257) it wouldn't flash if i didn't flash the boot.img first, but it worked just fine after flashing it, so it seems like people have different experiences and outcomes with the whole ROM flashing, and that's why i just included it so the people that uses this guide gets to the finish line. It's a "fail safe" way of doing it.
LordManhattan said:
Yeah, it seems like it's a hit or miss with the whole boot.img. First time i tried to flash Omni (coming from 257) it wouldn't flash if i didn't flash the boot.img first, but it worked just fine after flashing it, so it seems like people have different experiences and outcomes with the whole ROM flashing, and that's why i just included it so the people that uses this guide gets to the finish line. It's a "fail safe" way of doing it.
Click to expand...
Click to collapse
True that. It appears (as someone mentioned) there's a problem with Omni's install script. Other ROMs flash fine from stock without the need for fastboot.
Related
Hi!!
Just got your Xperia Z Ultra and start looking on how to root, unlock your bootloader and do everything you can for start playing with your phone with a maximum of security? You are at the good place!!
First of all, install PC Companion, you just need to plug your phone on the PC and follow instructions on your phone and PC.
To make things clear, I didn't do any of those tools and link the threads where they come from, so if you want to thanks devs do it there. I tried all of them without any problem and I do this thread for help people who know nothing about Sony Android devices or simply want to find everything in one place. They are fully working, so if things go wrong while following explanations this is bad luck, you did something wrong and/or forgot to do something. Neither I nor the Devs can be kept responsible for what you are doing on your device.
How to enter Flashmod and Fastboot mod
See Post #2
Root and TA Backup
See Post #3
New version of Vroot, now with superuser in english
Tutorial updated with step by step root process and screenshots
Youtube tutorials added, thanks to hamdogg
Unlock bootloader and Install Recovery
See Post #4
Step by step + screenshots coming soon
Youtube tutorials for how to flash CMW added, thanks to hamdogg
Flash or update a firmware from another country
See Post #5
Useful links
See Post #6
[B]How to enter Flashmod and Fastboot mod [/B]
Code:
Flashmod:
- Plug USB cable to your computer (not plug to your phone)
- Turn off your phone
- When phone fully off, press Volume down button and plug USB to your phone
- You are now on flashmod, you can release volume down button
{
"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"
}
Code:
Fastboot mod:
- Plug USB cable to your computer (not plug to your phone)
- Turn off your phone
- When phone fully off, press Volume up button and plug USB to your phone
- You are now on fastboot mod, you can release volume up button
Root and TA Backup
Mod edit - VRoot links and install guide removed
until such time as the validity of this software can be determined due to some security concerns regarding this application.
Youtube tutorial made by hamdogg
Thanks a lot hamdogg
First tool you need to know when you own a Sony Android device is Flashtool. I invite every owner wishing to root, unlock or mess with your phone to install this program and install Flashtoo-drivers.exe (directory: C:\Flashtool\Drivers\). This tool is a jewel, you can flash any factory firmware, unlock your bootloader and cherry on the cake, make a TA backup, that will backup all your TA partitions including locked bootloader with DRM keys. Keys those are necessary to enable X-Reality and bravia engine.
But to be able to do a TA backup you need first to root your Z Ultra.
- First of all you need to enable USB debugging, you will find it on /Settings/Developer options. For enable Developer options you need to go on /Settings/About phone/ and tap 8 times on Build number.
Mod edit - VRoot links and install guide removed
until such time as the validity of this software can be determined due to some security concerns regarding this application.
- OK, now SuperSu closed by itself and disappeared, no stress it's normal, just restart your phone.
- After full reboot, open supersu again, and it won't ask you for update binary anymore. Just close it.
- Download Titanium Backup Root and open it.
- Just be patient, promt for root access can take time, but it'll come.
Enjoy!!
I just updated from .526 to .532 and done this process and it was successful at the first try. If it doesn't work just try again. It work on any firmware version and country
All is thanks to @nickylou88 for this process.
And if you need more support you can look at this thread you have all information you need inside. The OP introduce another program, but VRoot is the less complicate to use and work as well.
Now you can make a TA backup following the instructions on this post.
Ok, now your phone is rooted, but more important you made a backup of your TA partition. It is important because if you soft brick your phone or wish to restore your bootloader to locked state if you unlocked it now you can.
I am not doing a TA backup tuto as the one on the original thread is more than complet
Here there is the other program that allow you to make a TA backup.
hamdogg provide us a really good Youtube tuto.
[B]Unlock bootloader and Install Recovery[/B]
Sony offer us a way to unlock our boot loader here but we have Flashtool, so why not use it instead? Easy and fast.
-Just click on “BLU” icon next to the flash icon
-Remember how to enter flashmod.
-Remember how to enter fastboot mod
-Click on Get Unlock Code then follow instructions on Sony website
-Enter the Code Sony sent on your email and let the program do.
When done boot your device you are unlocked.
Now it is time to flash Recovery. For do so you need to have adb and fastboot on your PC, all the information you need for install it and more can be find Here.
Another Youtube tuto from hamdogg
To flash recovery you need to put advanced stock kernel v5.img to “C:\SDK ANdroid\sdk\platform-tools\” then type :
Code:
fastboot flash boot C:\SDK ANdroid\sdk\platform-tools\advanced stock kernel v5.img
Reboot your phone to system a first time then turn it off.
To enter CMW:
-Turn on your phone as usually
-On Sony boot Screen look when the led turn purple push volume up
-Enjoy CMW
To enter TWRP:
-Turn on your phone as usually
-On Sony boot screen look when the led turn purple push volume down
-Enjoy TWRP
[B] Flash or update a firmware from another country [/B]
While looking on the forum it is possible for you to find someone posting the latest firmware, but when you plug your phone on your PC and look for update with PC Companion it tell you have the latest firmware. It simply because the firmware came out first on another country, you can simply wait for it to come in your country. If you don't want to wait you have 2 possibilities.
- Download the .ftf and flash it via Flashtool
Follow step by step this post
- Modify your CDA code on your build.prop but need to be rooted
Open build.prop with any explorer with root permission (I use root explorer) and modify the following values with the values you need:
Reboot your phone then plug it to your PC and update with PC Companion.
List of CDA
[B]Usefull links[/B]
Sony Drivers
Xperia™ Z Ultra C6833, C6806, C6843: Drivers
Xperia™ Z Ultra C6802 HSPA+: Drivers
White Papers
Xperia™ Z Ultra C6833: white paper
Xperia™ Z Ultra C6843: white paper
Xperia™ Z Ultra C6806: white paper
Xperia™ Z Ultra C6802: white paper
Sony programs
PC Companion: Link
SEUS (Sony Ericsson Update Service): Link
XDA threads
C6802 ftf compilation (HK, TW & CH): Link
Tips, Tricks, Guide Series: Link
FIX: Proximity Sensor: Link
Sony Xperia Z Ultra Gaming with videos: Link
[GUIDE] Ultra owners care and maintenance guide: Link
RELOCK BOOTLOADER INSTRUCTIONS Z Ultra C6802 : Link
Very good! many plus for including pictures!
From tapatalk with my Linux Device!
Excellent, thanks.
Edit: It seems Flashtool 0.9.11 doesn't support the XUltra out of the box for TA Backup. Trying to add the device defn file, but no success yet.
bASKOU said:
just in case
Click to expand...
Click to collapse
nice one @bASKOU... I was about to create this exact thread! This will be invaluable for the new Xperia owners out there... :good:
Thanks guys, happy you like it. I'll develop it more with more pictures soon. Restored my TA backup and need to unlock again soon. If you have some idea on which point can be develop I am open.
Sent from my C6802 using Tapatalk 4
Edit: It seems Flashtool 0.9.11 doesn't support the XUltra out of the box for TA Backup. Trying to add the device defn file, but no success yet.
Ok done-> go here and get http://forum.xda-developers.com/showthread.php?t=2428319 C680X.ftd file, rename to C680X.gz and uncompress. On a mac, go to flashtool application and show package contents. Copy C680X folder to devices folder.
Flashtool will then find the Ultra
scoobydu said:
Edit: It seems Flashtool 0.9.11 doesn't support the XUltra out of the box for TA Backup. Trying to add the device defn file, but no success yet.
Ok done-> go here and get http://forum.xda-developers.com/showthread.php?t=2428319 C680X.ftd file, rename to C680X.gz and uncompress. On a mac, go to flashtool application and show package contents. Copy C680X folder to devices folder.
Flashtool will then find the Ultra
Click to expand...
Click to collapse
Yes, this is it. Need to we'll read each thread I linked there is all details. If it is not well detailed on the original thread I did put detailed. Or maybe I should put a more detailed install process with screenshot. Tomorrow I'll work on it.
Sent from my C6802 using Tapatalk 4
we need youtube videos for guides as this is too awkward to get working
encryptioncsta said:
we need youtube videos for guides as this is too awkward to get working
Click to expand...
Click to collapse
Lol Sorry but I don't have anything for record. I do believe than screenshots are already more than enough. I'll make detailed, but not hold hands of people for do it.
Sent from my C6802 using Tapatalk 4
Root tutorial updated.
Sent from my C6802 using Tapatalk 4
thank you so much!!!
so , if we root using VRoot , we wont lose XReality/Bravia ??
SuperSU work with Locked BL right ?
Shafwan7 said:
thank you so much!!!
so , if we root using VRoot , we wont lose XReality/Bravia ??
SuperSU work with Locked BL right ?
Click to expand...
Click to collapse
YEs, you do not lose it. Nobody using this tool loosed it. It doesn't touch at your TA partitions. After rooting if you are really that much concerned about your DRM keys you can make a TA backup. SuperSU is an application so it doesn't require anything from the bootloader.
bASKOU said:
Lol Sorry but I don't have anything for record. I do believe than screenshots are already more than enough. I'll make detailed, but not hold hands of people for do it.
Sent from my C6802 using Tapatalk 4
Click to expand...
Click to collapse
my unboxing video is almost finished uploading...
- then will do one on:
- how to root
- backup TA partition...
- access to bootloader
- flashing firmware
I'll follow your methods, so then you can shove the videos on here, and hopefully that will be another form of visual help..
hamdogg said:
my unboxing video is almost finished uploading...
- then will do one on:
- how to root
- backup TA partition...
- access to bootloader
- flashing firmware
I'll follow your methods, so then you can shove the videos on here, and hopefully that will be another form of visual help..
Click to expand...
Click to collapse
Perfect! Looking forward to that. Thanks!
thanks for sharing this, very useful
Hey guys, I've rooted, installed CWM Recovery, Unlocked Bootloader, and installed CyanogenMod on another phone before.
The thing is, I've had this phone for about 6 months and wanted to do the same. However, after browsing through the forums, man are there a lot of scary sh*t going down. I would like the request the procedure to install CyanogenMod safely, without losing any Keys/IMEI/XReality/DRMkeys/Etcetera.
I dont know if the method given by FXP is supposed to be this straight forward, but I too like others, do not want to risk losing important stuff if it can be avoided (Keys/IMEI/XReality/DRMkeys/Etcetera).
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Frankly speaking, the forums is pretty much jumbled up, and the existing [Guide] Threads are either incomplete (Lacking important steps), or Unclear (Non-Specific steps).
Perhaps someone could do me a favour by using the template that I have below to help me, and possibly others, to install CM 10.2 on our beast of a phone.
Template:
1. Backup TA and DRMkeys and stuff: http://forum-xda-developers-com/backup
2. Root: http://forum-xda-developers-com/root
3. Recovery : http://forum-xda-developers-com/recovery
4: Unlock Bootloader: http://forum-xda-developers-com/ulbl
5: Install FXP's CM 10.2 :http://forum.xda-developers.com/showthread.php?t=2461286
Something like that would suffice I think, as long as no important steps are missing that would cause me to lose stuff unique to my phone, that cannot be recovered if I didn't back it up.
P.S. My version is 14.1.B.2.257
P.P.S. Thank you in advance.
1. Root
2. Backup TA (VERY IMPORTANT)
3. Install Recovery and unlock the bootloader, or the other way around. Both ways work.
4. Install ROM by following the "guide" that you quoted above.
Sent from my C6833 using Tapatalk
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Xenogenics said:
I'm on 14.1.B.2.257, I believe reverting to the previous version causes data to be lost unless you back it up right. *Sighs* How troublesome.
Click to expand...
Click to collapse
you will have to back up the data anyways. I think unlocking the bootloader does a factory reset, as well one is needed going from stock to CM if i unforget correctly
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
stiggy2012 said:
I am also wondering about this. I'm currently running firmware .257.
I understand that I need to back up the TA partition first (though I'm not exactly sure on what I will loose if I don't). I also understand that to do this I need to root the stock rom. I understand that in order to root, I'll need to first downgrade to an earlier firmware using flashtool. However, after that I'm not so sure what I need to do. As far as I can see, the only method of gaining root currently is to use vRoot, which is currently under investigation for IMEI mining.
How else can I root the device? I was thinking of maybe using the recovery for locked bootloaders here: http://forum.xda-developers.com/showthread.php?t=2426739
Following by flashing SuperSU from recovery as per usual.
Will this work, keeping the TA partition intact so that I can back it up before flashing CM? Assuming so, would I even need to downgrade from the .257 firmware at all?
Thanks,
Click to expand...
Click to collapse
OK, so looking into this further, you already need to have root to be able to flash the "CWM for locked bootloader" rocovery. So as far as I can see, the only way to get root in order to back up the TA partition is to give your IMEI to the Chinese via vRoot?
Thank god the stock rom is so good.
tommo123 said:
i have CWM now so can flash custom roms like i did on other phones right?
what does unlocking the bootloader give me? unless i'm wrong and i have to unlock to flash?
all i've done so far is do a backup is all. (did a TA backup a while back though)
Click to expand...
Click to collapse
You have to unlock the bootloader to flash custom ROMs. You can flash stock ROMs without unlocking it, but you have to unlock it if you want CM, PAC, PA etc.
Sent from my C6833 using Tapatalk
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
tommo123 said:
really, so what would happen if i tried to flash an aosp rom now? would the system partition essentially be read only?
sorry for the Qs but haven't had a locked bootloader since the htc desire (although the s-off for that one was to remap the partitions to allow more room for data) and the reasons for unlocking don't seem to be the same.
Click to expand...
Click to collapse
Nothing will happen if you try it now. You can easily unlock the bootloader by going to Sony's Dev site, request your key and use Flashtool to unlock it. It takes a couple of minutes once you have Flashtool and the drivers installed. It's also perfectly safe to unlock it and you will lose your warranty. BUT you can easily relock it again if something happens to your ZU and the warrenty will be back.
Remember to backup your TA before you unlock your bootloader. It contains a lot if device info and your unique DRM keys. Unlocking the bootloader will wipe the system partition, but you will still have root, photos, music etc. (But do a backup of those just in case).
Sent from my C6833 using Tapatalk
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
tommo123 said:
i think that's where i got confused with drivers - unlocking.
i have already done a backup of my TA part so that side of it is ok. i'll leave unlocking until there's a rom i want to try. possibly a complete 4.4 or something.
cheers LM
Click to expand...
Click to collapse
If you've already backed up your TA, it means that you have the drivers installed, so job done All you have to do is to install Flashtool and get your key from Sony (which you will get on your email straight away). Either way, just ask here if/when you want to unlock it so we can guide you through it (it's very easy though).
ran flashtool but gave me driver errors - missing. unable to install the drivers included (i guess due to windows 8 driver signing)
Just got my sony version - can say this phone is beast mode. There is a pending update to .257 and someone told me that if I update to this, i will be locked out of any ROMs, including any google edition ROM. Can anyone verify this or comment? I have NOT updated to .257 yet.
Thanks in advance.
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
LordManhattan said:
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
Click to expand...
Click to collapse
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
LxMxFxD said:
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
Click to expand...
Click to collapse
Correct. There are currently no way to root 257, so we have to root 532 and update through OTA to keep root on 257.
- Use this tool to root
- Install OTA Root Keeper from the Play Store
- Since you've already received the OTA, you don't need to change the CDA in build.prop (to force the OTA), so...
- Update to 257
- The root app (i'm not sure what app it installs) may be gone, so just install SuperSU from the Play Store if it's not in your app drawer.
And you're done...
... unless you also want to unlock the bootloader:
But let's not get ahead of ourselves. You really want to take a backup of your TA partition. It holds all your unique DRM keys, and X-Reality won't work without it. Once you lose it, you can't get it back, so back it up and upload it to your Dropbox or something. So how do you backup your TA partition?
- Download this tiny tool on your computer and run it.
Are you done? Great! Let's move on to the bootloader:
- Go to Sony's dev site
- Request the unlock key and check your mail.
- Install Flashtool on your computer (follow the guide)
- Click the "lightning" icon
- Follow the steps and enter your unlock key
This may wipe your phone, so backup your stuff
And you're done...
... unless you want to install Recovery and TWRP!
Installing Recovery and TWRP is easy. Just run this tool on your computer.
Now you're all set to flash custom ROMs and all that stuff
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Actually... You only need ADB and Fastboot. You can install this Windows installer which will do all the work for you. I'm sorry if you installed the entire SDK I should have included it in the guide.
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my C6833 using Tapatalk
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
techpal said:
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
Click to expand...
Click to collapse
Thank you very much.
I'm new to Sony flashing. Recently bought a XZU (6833) after learning about GPe release. I havent gotten it as yet but i've spent the last few days reading up on preparing for flashing AOSP roms. I'm still not 100% solid on the steps as information is all over the XZU section, not really organised too well. A lot of the information is out of date and there are many gaps that left me scratching my head...
As far as I can gather, these are the steps a new XZU non GPe edition owner should undergo if they would like to flash GPe roms(or any other)...please correct me if I am wrong.
1) Use flashtool 0.9 to flash older 532 firmware ftf file. (does not require root and can be done on a bone stock device non GPe device regardless of installed firmware version). Link here http://forum.xda-developers.com/showthread.php?t=2463701. Now I know Hong Kong version is ok. 532 is older than 257. 257 cannot be rooted directly hence the need to downgrade first.
2) Root using the Japanese rootkitZ Link: http://forum.xda-developers.com/showthread.php?t=2559009 (I assume this installs Superuser as there is a Superuser APK in the folder)
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
5) Unlock bootloader using Sony method. Link:http://unlockbootloader.sonymobile.com/
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Please can someone edit and/or add details where necessary.
---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------
LxMxFxD said:
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Click to expand...
Click to collapse
To what scripts are you referring? Can you help me by fleshing out my above post?
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
Click to expand...
Click to collapse
If you're not planning on keeping the stock ROM, and you want to jump straight to a custom ROM, then no, it's not necessary to install OTA Root Keeper.
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
Click to expand...
Click to collapse
You don't need to back it up, but it's recommended even if you're going to use custom ROMs. What if you're having some issues with your ZU, and you have to send it in for repairs? Sony will notice if the DRM keys aren't there and they'll then know that you've unlocked the bootloader.
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
Click to expand...
Click to collapse
No, this part isn't necessary if you don't want to.
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
Click to expand...
Click to collapse
Yes, run the bat-file and choose SuperSU in the terminal.
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Click to expand...
Click to collapse
Before you start flashing custom ROMs, make a NAND backup of the stock ROM. This way, if you want to go back, all you have to do is to flash a boot.img and restore it, and you'll end up exactly where you left off (with root).
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
1) How does one know when it is necessary to do any of the above.
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
3) How do you flash the boot.img files? Through cwm or the flashtool?
4) Some gapps come with recovery? Why is that necessary?
A million thanks.
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
LxMxFxD said:
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
Click to expand...
Click to collapse
I see you're being taken care of welcome dude, good choice of phone, it's a screamer!
Sent from my C6833 using XDA Premium 4 mobile app
CptAwesomeTT said:
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Click to expand...
Click to collapse
No problem. I quite enjoy this (yes, i'm weird)
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Click to expand...
Click to collapse
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
Click to expand...
Click to collapse
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
Click to expand...
Click to collapse
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
3) How do you flash the boot.img files? Through cwm or the flashtool?
Click to expand...
Click to collapse
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
4) Some gapps come with recovery? Why is that necessary?
Click to expand...
Click to collapse
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
LordManhattan said:
No problem. I quite enjoy this (yes, i'm weird)
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
Click to expand...
Click to collapse
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
CptAwesomeTT said:
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
Click to expand...
Click to collapse
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
LordManhattan said:
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
Click to expand...
Click to collapse
You've been so helpful. I think that's all my questions until I actually get the device in hand and start working on it. Thanks a mill.
atm the jap root method is the one I'd use. kingo might be safe and vroot might not be...
Use the one in the zip or download the v4 or v5 boot.img
v4 http://forum.xda-developers.com/showthread.php?t=2426739
v5 http://forum.xda-developers.com/showthread.php?t=2426736
if going to omni i would flash the revolution kernel http://forum.xda-developers.com/showthread.php?t=2548092
No problem!
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
Link to .532 is gone. Is there another?
Thanks!
I have a Sony Xperia Tablet Z, 64GB WiFi (SPG312) running stock 4.3, and I can not root this thing. I've tried several different methods to no avail. Does anyone on here know how to root this thing? I'm ultimately trying to install CM11.
Either go back to 4.2, root with Doom's Rootkit, then install a recovery, and install 4.3 already rooted, or unlock your bootloader, install CM kernel, use the recovery built in to install the SuperUser zip, then flash stock kernel again.
Sent from my SGP311 using Tapatalk
Felimenta97 said:
Either go back to 4.2, root with Doom's Rootkit, then install a recovery, and install 4.3 already rooted, or unlock your bootloader, install CM kernel, use the recovery built in to install the SuperUser zip, then flash stock kernel again.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
So unlock the bootloader? How do I go about that? And after that I can install CM right from there? That sounds like the one thing I haven't tried.
How do I go about doing that?
http://unlockbootloader.sonymobile.com
Follow that link. It's pretty easy. Just make sure you have all the tools in hand. Shouldn't take more than a hour to read everything and do the procedure, if you have everything ready.
It's mentioned there, but remember that it will void your warranty and, with Android 4.3 or lower, on stock ROMs, you will not have Bravia Engine working. Also, in any version, Music and Video Unlimited will not work anymore.
Another big tip: Go to the Xperia Z section (the phone one), and on the sub categories, can enter one called Cross Device Development, or something along those lines, and look for a thread with the name TA backup. If you do the long process, of going back and such, backup your keys. Should come in handy in the future.
Sent from my SGP311 using Tapatalk
Felimenta97 said:
http://unlockbootloader.sonymobile.com
Follow that link. It's pretty easy. Just make sure you have all the tools in hand. Shouldn't take more than a hour to read everything and do the procedure, if you have everything ready.
It's mentioned there, but remember that it will void your warranty and, with Android 4.3 or lower, on stock ROMs, you will not have Bravia Engine working. Also, in any version, Music and Video Unlimited will not work anymore.
Another big tip: Go to the Xperia Z section (the phone one), and on the sub categories, can enter one called Cross Device Development, or something along those lines, and look for a thread with the name TA backup. If you do the long process, of going back and such, backup your keys. Should come in handy in the future.
Sent from my SGP311 using Tapatalk
Click to expand...
Click to collapse
Emma does not work. I have tried to register for an account a several times with no luck.
Birkesuss said:
Emma does not work. I have tried to register for an account a several times with no luck.
Click to expand...
Click to collapse
You do not need Emma.
Sent from my SGP311 using Tapatalk
u need to download flashtool and find a 4.1.2 rom for your device...
then you can either use framaroot 1.91(gandalf exploit) or use doomlords root setup...
after that you can install phill'z recovery...
http://forum.xda-developers.com/showthread.php?t=928343 this link was very help full for my device sgp311 and i think its almost the same for your device only the rom and the stripped .ftf will be different...
unlocking your boatloader is not really applied to you,you only need it if you want to install custom roms...but before you do search a bit around to find hou you can backup your drm keys aka .ta partition.
Make sure you downgrade to 4.2 and root using http://nut.xperia-files.com/?dlid=V...jb3ZlcnkyLjcuMTIzLUJFVEEuaW5zdGFsbGVyLnppcA== option 3 then backup your TA partition before unlocking your bootloader, or theoretically you'll lose warranty
ok ok ok
So what steps do I take to install CM11?
Which method posted would get me there? You guys are saying a lot of different things here, have me a little confused
Hi anyone knows and tries this Kingo to root and unlock bootloader
http://www.kingoapp.com/sony-bootloader-unlock.htm
http://www.kingoapp.com/index.htm
thanks
Unlock bootloader > flash any cm10-11 kernel that has recovery built in > boot to recovery > flash SuperSU > flash 4.4.2 stock kernel back (from FTF)
So today I managed to root my Z2
Following advice from o0 Matt 0o in another thread, I downgraded from 4.4.4 to 4.42 using flashtool, then using the rootkitXperia_20140719 install.bat the phone is now rooted (for some reason it would not find adb even though running adb from a cmd prompt worked!)
Anyway, now I am on 4.4.2 with root, if I upgrade back to stock 4.4.4 rom will I lose the root?
EDIT: I have installed dual recovery, is there a pre packaged rooted rom for:
Android 4.4.4
23.0.1.A.0.167
United Kingdom - 3 - 1281-2574
Click to expand...
Click to collapse
Dont really want to create a rooted package myself, the steps can be confusing
Thanks!
Since you have dual recovery on 4.4.2 you can use the pre-rooted package by niaboc79 (can be found in the Android Development section) or any pre-rooted stock based ROM based on 4.4.4. It is all down to your preference.
I doubt there will be a 3 branded pre-rooted package either.
Actually you're right I should just get one of those roms which is not branded which would look better anyway
One last thing what is the steps to backup ta partition? At some point I will unlock bootloader but don't want to lose the dry keys
Cheers
Ned_Flanders said:
Actually you're right I should just get one of those roms which is not branded which would look better anyway
One last thing what is the steps to backup ta partition? At some point I will unlock bootloader but don't want to lose the dry keys
Cheers
Click to expand...
Click to collapse
In the Sony cross device development section there is the backup TA tool, simply use that. Also, make sure to upload your backup to a cloud service or something like that, in case your hard drive goes kaput and you need it to relock your bootloader.
Please remember that unlocking the bootloader wipes the internal SD card (not the user one). Also, restoring the TA backup relocks the bootloader so make sure you are on a stock ROM and kernel when you restore the backup.
gamer649 said:
In the Sony cross device development section there is the backup TA tool, simply use that. Also, make sure to upload your backup to a cloud service or something like that, in case your hard drive goes kaput and you need it to relock your bootloader.
Please remember that unlocking the bootloader wipes the internal SD card (not the user one). Also, restoring the TA backup relocks the bootloader so make sure you are on a stock ROM and kernel when you restore the backup.
Click to expand...
Click to collapse
Cool thanks for the tips :good: