Got my XZU last Saturday and decided today to keep it. Being long out of the Sony-world (last was an XS, now coming from a Find 5), I've got some questions. I'm also going to search for the infos, but I feel a single thread for "my stuff" makes it easier for me, so please be kind.
So, for the current state, here's the device's information.
- Sony Xperia Z Ultra (C6833), black
- running on Vodafone DE
- Android version 4.2.2
- Baseband version 8974-AAAAANAZQ-10220006-09
- Kernel 3.4.0-perf-gde8296d-02194-ga2561a5
- Build 14.1.B.1.510
- The device shows me an update to 14.2.A.1.136
Questions:
1) Do Sony's official updates only update Android + Sony Apps or are there also firmware updates included?
2) I want to root and install a custom ROM, should I start from the current build or should I upgrade to $something first?
3) I've read that KitKat is restricting SDcard usage for non-system apps. Do custom 4.4 ROMs work around this(,yet) or should I update to 4.3 max?
4) I probably won't use the camera much, if at all, still, most custom ROMs can't get the camera quality on a level the stock ROM has, so how bad is it on this device?
5) is the PowerCover CP12 available somewhere in the EU? It's "out of stock" in all big shops I looked at in .de,.at,.ch and the Twitter-Team wasn't really helpful. Ordering from outside the EU would be possible, but pretty much guaranteed to get stuck at the customs where the next office is ~50km away and doesn't have work-friendly times at all.
6) About screen protectors: a) can I apply them over the shatter shield and if so b) will input by pens or something still work on a decent level?
7) is there a prefered solution of recoveries on this device or does it not matter at all, if I'd choose CWM or TWRP(or is there something else entirely)?
8) are there known problems in general with custom ROMs regarding external hardware? I'd like to use my "SmartWireless Headset Pro", my "SmartWatch (1)" and TV-Out
That's it for now, thanks for any help
1) The 136 update is a firmware update (to Android 4.3), but they also push out updates for their Sony apps.
2) You have to update to at least 290 (Android 4.3) if you don't want to lose your IMEI when you flash a custom ROM. Also note that you'll lose your IMEI if you downgrade from 136/290 to anything older. There are no real reasons to downgrade though, but just keep that in mind. It's easily fixable, so it's not the end of the world if you do it.
3) Yes, there's a workaround to get SD card working on KitKat (you just have to replace one file)
4) The camera is still bad on custom ROMs. It might get better with official Sony KitKat.
5) I have no idea.
6) a) Yes. b) Yes.
7) We've got double recovery, meaning you'll get both CWR and TWRP when you flash recovery, so use the one you prefer. (Vol Up for CWR and Vol Down for TWRP)
8) I think the only known issue on 136 is that Bluetooth might be a little wonky, but i'm not sure, so be sure to read around here since there's a thread about it.
Thank you for that.
In regard to 1), I meant firmware updates of hardware, f.e. the Find5 received some updates regarding the touchscreen.
As for 2), so there's currently no reason not to install the latest official Sony update, meaning it's also rootable without too much hassle? What would be the consequences of a lost IMEI?
S.D.Richards said:
Thank you for that.
In regard to 1), I meant firmware updates of hardware, f.e. the Find5 received some updates regarding the touchscreen.
As for 2), so there's currently no reason not to install the latest official Sony update, meaning it's also rootable without too much hassle? What would be the consequences of a lost IMEI?
Click to expand...
Click to collapse
Bugfixes are included in firmware updates, so they don't release an update to fix one minor thing. The Find5 receives updates every two weeks, if i'm not mistaken?
There's really no reason to update to 136 (the newest) if you're going to flash a custom ROM. Rooting is fairly easy if your bootloader is unlocked, and it only takes a couple of minutes, but it's a little more complicated if your bootloader is locked. Luckily, you're on 510, meaning it's even easier to root, and once you've rooted 510, make a backup of your TA partition. It holds all of your unique DRM files that makes X-Reality work etc. You'll lose the TA partition when you unlock the bootloader, so that's why you have to make a backup of it before you unlock it. Once you've done that, update to 290, unlock the bootloader, root it and do whatever you'd like to do.
Thanks again.
Now rooting worked(+OTA keeper from the Playstore), so did creating the TA backup.
Having a glance over the custom ROMs available as of now, I think I'd like to stay on rooted stock until Omni (official) comes around.
So what would be the (better) procedure to get latest Sony ROM running? Use Sony's updater and hope OTA keeper works or unlock, install recovery and flash a pre-rooted FTF?
S.D.Richards said:
Thanks again.
Now rooting worked(+OTA keeper from the Playstore), so did creating the TA backup.
Having a glance over the custom ROMs available as of now, I think I'd like to stay on rooted stock until Omni (official) comes around.
So what would be the (better) procedure to get latest Sony ROM running? Use Sony's updater and hope OTA keeper works or unlock, install recovery and flash a pre-rooted FTF?
Click to expand...
Click to collapse
OTA Root Keeper doesn't work on 4.3, so you'll lose root no matter what you do. Are you still on 510, or have you updated to something else?
You have your TA partition backed up now (recommend you to upload it to your Drive or Dropbox), so you can unlock the bootloader without permanently losing the TA partition. It'll delete it when you unlock the bootloader, but you can easily restore it again in case you have to send it in for repairs. Rooting 290 and everything else becomes so much easier and faster the second your BL is unlocked, so head over to the General section and look for Jackie's root guide and see if that's something you might want to do...
...or you can simply stay with the firmware you're on now, granted it's not the most stable firmware version, but it'll save you a lot of time. Official KitKat is also scheduled for release this month, so you can:
A ) Stay on current firmware and wait for official Sony KitKat
B ) Go all out and flash a custom ROM
I'm currently running the GPe ROM, and I can highly recommend it. It's solid as a rock with no bugs.
Any questions?
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
OTA Root Keeper doesn't work on 4.3, so you'll lose root no matter what you do. Are you still on 510, or have you updated to something else?
Click to expand...
Click to collapse
Still on 510, bedtime was up and I don't wanted to do something stupid with a sleepy head.
You have your TA partition backed up now (recommend you to upload it to your Drive or Dropbox), so you can unlock the bootloader without permanently losing the TA partition.
Click to expand...
Click to collapse
Yes, did that and mirrored it over a few systems. BTW, if I'd ever go back to stock, would the TA-p get changed so I'd need to back it up again or does it stay the way it is over the phone's lifetime?
It'll delete it when you unlock the bootloader, but you can easily restore it again in case you have to send it in for repairs. Rooting 290 and everything else becomes so much easier and faster the second your BL is unlocked, so head over to the General section and look for Jackie's root guide and see if that's something you might want to do...
Click to expand...
Click to collapse
No problem, I had my Xperia S unlocked, so I now the procedure. Only question related to that: I read that for the Z1(?) there's a minimal version one should update to before unlocking the BL, if you don't camera stops working or something - so, is this also a problem on the ZU or has this already been fixed?
I'm currently running the GPe ROM, and I can highly recommend it. It's solid as a rock with no bugs.
Click to expand...
Click to collapse
I'll have a look at it, thanks.
S.D.Richards said:
.
Yes, did that and mirrored it over a few systems. BTW, if I'd ever go back to stock, would the TA-p get changed so I'd need to back it up again or does it stay the way it is over the phone's lifetime?
Click to expand...
Click to collapse
The TA partition is unique to your device, so you do it only once, so be sure to not lose it.
No problem, I had my Xperia S unlocked, so I now the procedure. Only question related to that: I read that for the Z1(?) there's a minimal version one should update to before unlocking the BL, if you don't camera stops working or something - so, is this also a problem on the ZU or has this already been fixed?
Click to expand...
Click to collapse
The ZU has never had any of the camera issues when we unlock the bootloader, so there's nothing to add here
Sent from my C6806_GPe using Tapatalk
So to be clear, when you're talking about the GPe ROM, you're meaning this one: http://forum.xda-developers.com/showthread.php?t=2608708 ?
So if I'd like to try this, I'd need to:
1. unlock bootloader
2. install recovery
3. take NAND backup
4. Flash .290 fw
5. flash this ROM
Correct?
S.D.Richards said:
So to be clear, when you're talking about the GPe ROM, you're meaning this one: http://forum.xda-developers.com/showthread.php?t=2608708 ?
So if I'd like to try this, I'd need to:
1. unlock bootloader
2. install recovery
3. take NAND backup
4. Flash .290 fw
5. flash this ROM
Correct?
Click to expand...
Click to collapse
The bootloader unlocking doesn't need to be the first step since you can flash Recovery on a locked bootloader. You can do everything except the ROM flashing on a locked bootloader. But yeah, that looks fine to me. Be sure to download the tweaked GPe version that includes Recovery and SD fix.
If you can't bother making a NAND:
- Unlock the bootloader
- Update to 290
- Flash boot.img (includes recovery)
- Boot into recovery and flash (VOL UP when LED lights up)
- Done.
Thanks again, could/would you link me to a .290 ftf for germany/europe/generic? The ones I found are either for other regions or the links seem to be down.
Here's 290 EU for the C6833.
https://mega.co.nz/#!VR4HyJia!PGxJXHOi8V-eJpWDnsJKShRPlhoYHR5DpFRkko6m0Nk
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
Here's 290 EU for the C6833.
https://mega.co.nz/#!VR4HyJia!PGxJXHOi8V-eJpWDnsJKShRPlhoYHR5DpFRkko6m0Nk
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Thanks, already found that link, but it gives me a "the file you are trying to download is no longer available"-error.
Already searched on Google, but couldn't find one, yet, or only for the other models.
Here's the Chilean 290 for C6833. It doesn't matter which one you use, and you're planning to flash the GPe, so just flash this one and get it done
Sent from my C6806_GPe using Tapatalk
Thank you very much for all your help, GPe is up and running smoothly now.
Apart from anything looking pretty huge, guessing different DPI settings compared to Sony's values, it's fine so far. One question though: under display settings it says X-Reality is on. Is that just cosmetics, since at no point I restored the TA-backup. If it's "fake", is it possible to restore TA and have it working or would that "trash" the system and restore should only be done in case of a stock re-install?
S.D.Richards said:
Thank you very much for all your help, GPe is up and running smoothly now.
Apart from anything looking pretty huge, guessing different DPI settings compared to Sony's values, it's fine so far. One question though: under display settings it says X-Reality is on. Is that just cosmetics, since at no point I restored the TA-backup. If it's "fake", is it possible to restore TA and have it working or would that "trash" the system and restore should only be done in case of a stock re-install?
Click to expand...
Click to collapse
just cosmetic and does nothing. If you restored the TA the GPe rom would fail to boot.
blueether said:
just cosmetic and does nothing. If you restored the TA the GPe rom would fail to boot.
Click to expand...
Click to collapse
Thanks for that quick answer, satisfied for now, so I can finally go to sleep
One last thing. Just change ro.sf.lcd_density=400 to 320 in build.prop to get the same sized UI like the Sony ROM. Unless you like 400.
Sent from my C6806_GPe using Tapatalk
LordManhattan said:
One last thing. Just change ro.sf.lcd_density=400 to 320 in build.prop to get the same sized UI like the Sony ROM. Unless you like 400.
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Perfect, just what I've been looking for, thanks.
Now to hope that the ZU also gets double tap to wake, than I'd be pretty happy.
S.D.Richards said:
Perfect, just what I've been looking for, thanks.
Now to hope that the ZU also gets double tap to wake, than I'd be pretty happy.
Click to expand...
Click to collapse
Yeah, the leaked footage from the Z2 KitKat build shows the option to use double tap to wake, so it looks like we'll get it. It's a kernel feature, so it'll work on mostly anything out there.
Related
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)
Hi, I have problems to regiister on my carriers network. My Z Ultra can see all available networks but refuses to connect toany of them. I tried several different ROMS without success. I also took out the SIMcard and put it into an old phone (no smartphone) and with that it connected instamntly. My carrier told me to wait but I´m reaklly fed up with waiting. Does anbybody have a clue what might be the issue here?
magnusaaa said:
Hi, I have problems to regiister on my carriers network. My Z Ultra can see all available networks but refuses to connect toany of them. I tried several different ROMS without success. I also took out the SIMcard and put it into an old phone (no smartphone) and with that it connected instamntly. My carrier told me to wait but I´m reaklly fed up with waiting. Does anbybody have a clue what might be the issue here?
Click to expand...
Click to collapse
Do you have an IMEI number?
Have
I bought this phone recently and i beleive tthat the imei number is on one of the receipts. However could you perhaps tell me a way of finding IMEI without hazzle..? I scarefully start to grasp that this might be an IMEI issue of which i have no clues or experience. I+m fammiliar with adb and rooting though. What is your advice?
magnusaaa said:
I bought this phone recently and i beleive tthat the imei number is on one of the receipts. However could you perhaps tell me a way of finding IMEI without hazzle..? I scarefully start to grasp that this might be an IMEI issue of which i have no clues or experience. I+m fammiliar with adb and rooting though. What is your advice?
Click to expand...
Click to collapse
Open the dialer and enter *#06#. A new window with a bunch of numbers should pop up. If it says "0" or "0000", your IMEI is gone, and we'll take it from there.
Note: Do not post your IMEI here.
Code Zero
OK you are right i surely mesed something up because all i get from that code is a hole bunch of zeros. Would be happy for rfurther advive.
yes
By the way, my platform is ubuntu. So I am familiar with some cli actions.
magnusaaa said:
OK you are right i surely mesed something up because all i get from that code is a hole bunch of zeros. Would be happy for rfurther advive.
Click to expand...
Click to collapse
I see, so i'm assuming that you've been on 290 and then downgraded to 257 or 532? If yes, that's why you've lost your IMEI. You can easily fix this by updating to 290 again, or flash NUT's 532 version in Flashtool.
LordManhattan said:
I see, so i'm assuming that you've been on 290 and then downgraded to 257 or 532? If yes, that's why you've lost your IMEI. You can easily fix this by updating to 290 again, or flash NUT's 532 version in Flashtool.
Click to expand...
Click to collapse
NUTS 532 sounds interesting. Does it have support for init.d and so on?
Can i flash cwm to boot after? My aim is to become on latest stock but rooted. Why? Is because i purchased a sony original miracast device and i would like that to work...
Suggest?
magnusaaa said:
NUTS 532 sounds interesting. Does it have support for init.d and so on?
Can i flash cwm to boot after? My aim is to become on latest stock but rooted. Why? Is because i purchased a sony original miracast device and i would like that to work...
Suggest?
Click to expand...
Click to collapse
Yup, it supports init.d.
It has dual-recovery installed as default, so you can either flash that one and stay fully rooted on 532 (with IMEI), or you can jump straight to 290, but then you'll have to flash it in Flashtool (so you get the latest baseband), and you'll have to root it yourself and install recovery.
Reason
LordManhattan said:
Yup, it supports init.d.
It has dual-recovery installed as default, so you can either flash that one and stay fully rooted on 532 (with IMEI), or you can jump straight to 290, but then you'll have to flash it in Flashtool (so you get the latest baseband), and you'll have to root it yourself and install recovery.
Click to expand...
Click to collapse
I beleive i messed it up while flasshing different roms and so son. But still my main goal right now is to be able to use ther miracast. Do you think it would work on the 532?
magnusaaa said:
I beleive i messed it up while flasshing different roms and so son. But still my main goal right now is to be able to use ther miracast. Do you think it would work on the 532?
Click to expand...
Click to collapse
I don't use Miracast, but i can't see why it shouldn't work? Does it require a special feature on Android 4.3?
Miracast
There has been several issues on miracast. Many people seeem to have failed to get it working. Maybe Sony has fixed that in Kitkat i dont knowe. But thge 532 is jellybean right?
LordManhattan said:
I don't use Miracast, but i can't see why it shouldn't work? Does it require a special feature on Android 4.3?
Click to expand...
Click to collapse
Ok i gather that you recommend that i flash the 532 ftf..? Using flashtool in flash mode? And where can i find that ftf?
magnusaaa said:
Ok i gather that you recommend that i flash the 532 ftf..? Using flashtool in flash mode? And where can i find that ftf?
Click to expand...
Click to collapse
The NUT 532 ROM is a Recovery file, so just flash it in recovery like you usually do, and you should in theory get your IMEI back. If not, flash a stock 290 FTF in Flashtool.
I have Miracast working on .136
It never worked on prior firmware - don't know if that was the tv's fault or the phone.
Sitting duck again
I tried flashing the NUT 532 and all seemed ok until i power the device up. I get thousands of force close to the system ui. Practically rendered my ZU useless. Does anybody recognize this issue? I tried a factory reset as my hands had to dance in order to reset it. Right now i dont know what fw oi am on but as i said the phone is uselesss.
magnusaaa said:
I tried flashing the NUT 532 and all seemed ok until i power the device up. I get thousands of force close to the system ui. Practically rendered my ZU useless. Does anybody recognize this issue? I tried a factory reset as my hands had to dance in order to reset it. Right now i dont know what fw oi am on but as i said the phone is uselesss.
Click to expand...
Click to collapse
Did you do a full wipe after flashing? If not, you should've done that. Also, no reason to panic. I understand why you might be, and i've been in much worse situations than this a couple of times, but it's nothing we can't solve. It takes some effort to hard brick a Sony. It just depends on how far you're willing to go to get it up and running. The easiest way would be to just flash 290 in Flashtool and be done with it. That way you'll have a fully funtional phone again with IMEI, and you can do the rooting later on when you have a system that's actually functioning correctly. Get your stress levels down again and root and what not when you have full control over your phone again
I'm in Norway btw, so since we're in the same time zone, i can help you out tomorrow after school/work if you need it.
LordManhattan said:
Did you do a full wipe after flashing? If not, you should've done that. Also, no reason to panic. I understand why you might be, and i've been in much worse situations than this a couple of times, but it's nothing we can't solve. It takes some effort to hard brick a Sony. It just depends on how far you're willing to go to get it up and running. The easiest way would be to just flash 290 in Flashtool and be done with it. That way you'll have a fully funtional phone again with IMEI, and you can do the rooting later on when you have a system that's actually functioning correctly. Get your stress levels down again and root and what not when you have full control over your phone again
I'm in Norway btw, so since we're in the same time zone, i can help you out tomorrow after school/work if you need it.
Click to expand...
Click to collapse
What I would do is do a flash of the FTF in my guide on downgrading the ZU/recoverinf the IMEI (parse be to [NUT]) http://forum.xda-developers.com/showthread.php?t=2593918
That should give you a clean stock sony .532 firmware ready to root. To root use Bin4ry's tool linked in LordManhatton's guide, then run through the steps in [NUT]'s .290 locked BL ROM thread and the his .136 locked BL thread. This has to be done in order if you are keeping a locked BL all the way through.
THNX
I am very thankful, for your guide and assistance. I am back on stock 532. Is it possible to flash another kernel/boot since this 532 sems to be without root and reovery. All tother things are back though. I cant find te thanks button. Where is that here on xda..?
Could i jjust write fastboot flash boot and then the actual boot.img? So that i can root it...
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)
I gave my XZU, which has an unlocked bootloader, is rooted, and is running 4.4.2 to my mother. I want to return the device to stock, as she has no need for root, and upgrade it to stock lollipop. The problem is, I rooted it a long time ago, I don't remember how I did it, and even then, I was stumbling through the process. There are many more guides about rooting than there are about unrooting, so I'm concerned that I may brick the phone or mess it up in some way. Here are the steps I found on XDA for returning to stock:
1. Make sure you have root
2. Backup any data/photos/etc on the phone
3. Restore your TA backup with the TA backup tool above
--------If you are on a custom kernel or ROM you ZU will not boot at this stage
4. Start flashtool and load a FTF
5. Start the flash and wait for the onscreen instructions to connect the ZU
6. Connect your ZU in flashmode
---------With the ZU powered off
---------Connect to PC while holding the volume down key
---------Flash will start
7. Wait for flash to complete
Is this the appropriate way to approach what I'm trying to do here? I am not running a custom kernel or ROM, I don't think. Certainly not a custom rom, though I'm not sure how kernels work anymore. But I'm pretty sure it's not custom. Just to be certain I am doing this properly, I want to write this out with the guide and see if it makes sense.
1. I do have root.
2. Done.
3. I have my TA partition saved as a .zip from when I originally rooted the phone. I'm not completely sure how I restore the partition. I am getting the Backup TA program from here: https://github.com/DevShaft/Backup-TA/releases. But I can't find actually how to restore it. After I do this, my bootloader is now relocked, and then I can just flash stock .ftf's? Is this correct?
4. I am downloading flashtool from here: http://www.flashtool.net/downloads.php and I am using this .ftf: [STOCK ROM] [FTF] Xperia Z Ultra (C6806) 14.3.A.0.681 "US Unbranded", which I am getting from here: http://forum.xda-developers.com/xpe...tf-depository-sony-firmware-releases-t2829387. I haven't used the flashtool since the original rooting I did, but I think I can figure it out.
5. Etc.
6. Etc.
7. Etc.
At this point, I should be back on stock, right? And then I could just update through Sony's PC Companion at this point, yes? I'm basically just looking for a "Yes, you're going in the right direction" or "Yes, this is how you would return the device to stock."
Thanks!
That is the most up to date instructions that I know of, sorry I can't answer about the TA restore. Just one suggestion would be to flash a lollipop ftf, rather than kitkat and trying to get it to upgrade. An even easier solution would be to leave it unlocked and flash this http://forum.xda-developers.com/xpe...llipop-5-0-2-c6806-14-5-0-242-rooted-t3082449 in recovery.
adfurgerson said:
That is the most up to date instructions that I know of, sorry I can't answer about the TA restore. Just one suggestion would be to flash a lollipop ftf, rather than kitkat and trying to get it to upgrade. An even easier solution would be to leave it unlocked and flash this http://forum.xda-developers.com/xpe...llipop-5-0-2-c6806-14-5-0-242-rooted-t3082449 in recovery.
Click to expand...
Click to collapse
I appreciate it. I think I'm going to try it now. I really want it on stock for any updates. It needs to stay as simple and as up-to-date as possible without as little effort as possible. Do you know where the stock lollipop .ftf's are?
Snarging said:
I appreciate it. I think I'm going to try it now. I really want it on stock for any updates. It needs to stay as simple and as up-to-date as possible without as little effort as possible. Do you know where the stock lollipop .ftf's are?
Click to expand...
Click to collapse
This tool might work.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
rajdude said:
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
Click to expand...
Click to collapse
The only reason to use that guide is to backup ta keys for whatever reason you'd want to do that.
If you're after root on stock ROM the single easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. Solid marshmallow with root goodies. Xpower has everything and is deodexed and ready for xposed framework.
just a little more clarification please?
civicsr2cool said:
.....easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. ......
Click to expand...
Click to collapse
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
rajdude said:
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
Click to expand...
Click to collapse
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
still a little confused
civicsr2cool said:
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
Click to expand...
Click to collapse
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my day job). In Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
rajdude said:
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my d Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
Click to expand...
Click to collapse
Android is Linux, to gain root in the ROM you have on your phone currently all you need is an unlocked bootloader to run SU, but then you'll be left with a phone that still needs a customized kernel to keep root and a DRM fix for the camera. Xpower 3.0 is that package.
You could really benefit from reading more. Google up on dm-verity and Sony Ric, and fastboot/adb for a little better understanding of what you're getting into without a pre compiled ROM. Messing around with any Android you'll have the majority of the same steps, unlock bootloader with fastboot, flash Supersu, customized kernel.. Etc
Why use a stable compiled ROM?
Let me list down and explain to you why it's best to use a stable compiled ROM. But first you need to understand these few things before you decide to unlock your bootloader and root.
Before Sony Z models kicked in, every rooted Sony device are still able to retain all the features that came together with the phone before it was rooted. When Sony introduce the first Z model, they start to create these things called DRM keys. DRM keys are unique algorithm (i guess i should put it that way) which is attached to every phone the same way an IMEI number is attached to every phone. In short, my DRM keys cannot be used on your phone and vice versa.
DRM key: It's a unique algorithm that holds all the unique features that an unrooted Sony phone boast such as camera quality, X-reality, High Res Audio etc etc.
The moment you unlock your bootloader, that's the moment your DRM keys will be lost. But don't panic, the wonderful devs on XDA have prepared a tool to backup your TA partition (a partition that contains your DRM key) for your own convenience if you want to relock your bootloader.
Then recently Sony/Android come up with new features called Sony RIC and dm-verity. (You may Google what these are all about but to my understanding it is placing limitations to people who root their phones to meddle around with the system settings of thier phone)
With all these "hurdles", it have taken some time for devs here to find a work around and like every fairytale ending, they manage to find a way.
Now you're wondering if you can actually root without flashing another rom. Good news for you: you can! There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting.
.. But ask yourself what's the point of going through the hassle of rooting and your phone is not tweaked for performance or for theming purposes?
That's when people flash roms and in Z5 compact's case, XPower is the best rom there is. It gives you all the performance tweak you need to make your phone lag free, it has a lite version that removes all the unnecessary system apps you can't delete without root, it gives you an option to add themes and framework from Xperia X with all those work around in place.
For your second question: why is there a need to install TWRP?
TWRP is a recovery tool which is a need for all rooted phone. It's also a tool for you to backup and restore your current rom so that you can rollback to the last working configuration if your phone went into a bootloop etc. Plus i believe all these guides require you to actually use TWRP to flash the SuperSU to successfully root your phone.
I hope this explains your doubts.
Thanks a lot but...
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
I think this is a pretty great thread rajdude. It's getting people to spell out a lot of information to noobs like us that it seems most posters have taken for granted over time.
I'm a complete novice at all of this. Sort of gleaning information as I go along, but I used this guide: http://twigstechtips.blogspot.hk/2016/04/sony-z5-compact-root-without-losing-ta.html?m=0
Along with this guide: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
The first guide is pretty basic step-by-step instructions. It unfortunately occasionally kind of skips over a couple very small things (that will be clear as you go along), or occasionally words things in such a way that might not be completely intuitive, but maybe that's cause I need things explained to me like I'm five sometimes. Any time I might have had a question about something in the the first guide, I went to the other and found the answer. It didn't take me long to get the gist of the whole thing though, and overall, it wasn't as scary as I thought it was going to be. It'd be fantastic if someone created a video walkthrough, but so far as I know, no one has done that yet.
The guide will help you back up your TA Partition where your DRM keys are stored, unlock your bootloader, root your device, and then restore your DRM keys. In order to do this you need to downgrade to Lollipop (if you're not already on it), and then upgrade back up to Marshmallow. It will also install TWRP (which I had no clue was installed until I went into "recovery mode" by pressing UP when I saw the LED flash yellow during boot). There may be an easier way to go about this whole process, but this is the process I used.
Before jumping into anything, I'd hold off until you heard more from firdyRAY or someone more experienced. They may look at the guide I linked and be horrified.
And yeah, I haven't installed xpower yet for the same reasons you haven't. Sounds like there's even an xpower 4.0 that was released recently, but still seems kinda buggy. Being rooted with stock I've been able to give Greenify access to root. Install Adaway (which was worth getting root to begin with). Install sound/music mods like DiVA-X, Viper4Android and Dolby Atmos. Install Titanium Backup. And make a few other minor tweaks (that I've since reversed). I still don't know much about custom ROMs and all that jazz, so I'm holding off until I get more understanding. I'd love to install the xpower ROM (when the bugs are worked out), and maybe some sort of sound ROM. I also need to get more understanding on some of the other vernacular like what exactly a "dirty flash" is.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
Click to expand...
Click to collapse
sony ric is a layer of security for sony roms so that they can protect nfc and fingerprint stuff. samsung and htc have there own variants as well.
yes lol the big red lettering is there to make you read, although hes not far off on the melting your phone part, the s810 is ridiculously hot.
the xpower thread doesnt not include the drm backup instructions because: 1) you need bootloader unlocked to flash it. and 2) because it includes the drm fix in it so you dont have to backup your ta keys.
the fingerprint sensor bug is on any bootloader unlocked phone, the hardware fails after x amount of hours and requires a reboot to work again. xpower is a stock rom, the only thing different is its pre-rooted, de-bloated, and deodexed for xposed to work. we have a separate thread for the fingerprint sensor bug and its been solved.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
Click to expand...
Click to collapse
Sony RIC main function is to disable /system write even you got root permission(you still able to do /system write but after a reboot will restore to original). There is a workaround but very trouble, TWRP recovery file manager can bypass Sony RIC(it works in the old day for me, not sure about now). BTW, all 3rd kernel should be disabled RIC nowadays. For any regular computer, there is no hardware or software lock to prevent you gain root access in linux but there are many such trouble stuffs in the android world... lol
I'm running XPower 3.0 Full as a daily driver since June and been very happy. Battery life, stability and speed is good.
Please note, that you MAY lose your warranty when you lose your DRM keys. That's why I didn't unlocked my phone before there was a way to backup TA partition. Now I'm after warranty repair, and before it I was able to fully restore stock ROM with DRM and all features fully functional. In my country, there is only one Sony approved repair center and they check DRM keys before repairing anything - even if it's mechanical fault.
When I had Z1c in KitKat days, it didn't had dm-verity and Sony RIC. It was possible to gain permanent root with bootloader locked, so I was happily using stock ROM and kernel. In Z5c case, first thing I tried was to do the same and it was possible (just backup TA, unlock bootloader, and flash TWRP with patched kernel (dm-verity and Sony RIC disabled) to begin with), but going XPower way was much more confident - I didn't had to think about removing every bloat app. I just flashed lite version in June and I'm using it till this day without any problems at all
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
michuroztocz said:
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
Click to expand...
Click to collapse
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
flopower1996 said:
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
Click to expand...
Click to collapse
That's just what I wrote - just put it in another words