Related
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...
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.
Hey peeps,
Am totally new to android as I have only just binned my iphone contact and got a Ultra, the issue am having, I am reading and reading and getting nowhere fast
I would like to root my phone but I seem to be getting stuck in an endless loop which I don't know how to break!
Phone is brand new, no contacts, nothing, I just want to do the following, which I would have thought would be in this order,
Backup the TA (As I have read and read that this will save the DRM keys, which once lost are gone)
Now, I read to backup the TA, I need to root, to root I need to unlock bootloader, to unlockboot loader you have to root all of which then I read is warnings that you can lose the DRM's
Arrrghhhh
I have the flashtool installed
Am on .757
My bootloader is locked but unless the .757 update changed it I was able to unlock it but everything I have tried and read doesn't work
I have my unlock key as well, and I have vague idea's what I want to do but there are so many threads and everything seems to loop back to to root, you need unlock, to unlock you need root to flash you need root lol am going crazy.
Am not sure why am struggling so much with following the guides but I guess it's cause I have zero experience with doing this.
any help would be greatly appreciated
Yeah, I'm not surprised by this at all; and welcome! You have to downgrade to 532 using Flashtool, then root, and then backup the TA partition. You're free to upgrade to 757 again after that, unlock your bootloader and root 757.
Sent from my Z Ultra
Thanks for that info mate, so far that's made more sense than searching all of these posts
Am thinking about two steps in this guide to downgrade
http://forum.xda-developers.com/showthread.php?t=2593918
First one seems very simple, but second one seems to flash them back to solid stock from the look of it.
Once downgraded,
I thought you require bootloader unlocked before you can root, and from what I read you need root to unlock/backup, or have I missed something?
(hopefully will be back to 532 shortly after files finish downloading.
LordManhattan said:
Yeah, I'm not surprised by this at all; and welcome! You have to downgrade to 532 using Flashtool, then root, and then backup the TA partition. You're free to upgrade to 757 again after that, unlock your bootloader and root 757.
Sent from my Z Ultra
Click to expand...
Click to collapse
OrangeMagicGod said:
Thanks for that info mate, so far that's made more sense than searching all of these posts
Am thinking about two steps in this guide to downgrade
http://forum.xda-developers.com/showthread.php?t=2593918
First one seems very simple, but second one seems to flash them back to solid stock from the look of it.
Once downgraded,
I thought you require bootloader unlocked before you can root, and from what I read you need root to unlock/backup, or have I missed something?
(hopefully will be back to 532 shortly after files finish downloading.
Click to expand...
Click to collapse
Hey mate, yesterday i had successfully root my XZU with locked bootloader and no backup TA or else, because I'm not yet decided to unlock.
Currently your device is locked or unlocked bootloader?.
Perhaps i could help you.
Currently mines locked.
Speederoff said:
Hey mate, yesterday i had successfully root my XZU with locked bootloader and no backup TA or else, because I'm not yet decided to unlock.
Currently your device is locked or unlocked bootloader?.
Perhaps i could help you.
Click to expand...
Click to collapse
OrangeMagicGod said:
Currently mines locked.
Click to expand...
Click to collapse
Just do as has been said a thousand times...
Downgrade to .532 - see my downgrade thread
Root using either [NUT]'s dual recovery or bin4ries tool - see thread in step above or LordManhattans guide
Backup the TA - see LordManhattons guide
Upgrade to latest FTF
Unlock bootloader
Root using jackies099's kernel
...
After hours of reading and searching around and trying to follow what LordManhattan said.
I have the phone down to 523.
I now have the bootloader unlocked
Just not sure on the rooting of the phone..
With Flashtool can I simple press the Lock key and root it that way? I don't know the difference between Superuser or SuperSU
Or do I have to do it another way?
I have looked at a number of rooting options and am unsure what to do, one way the links on the guide didn't work others are little confusing!
OrangeMagicGod said:
After hours of reading and searching around and trying to follow what LordManhattan said.
I have the phone down to 523.
I now have the bootloader unlocked
Just not sure on the rooting of the phone..
With Flashtool can I simple press the Lock key and root it that way? I don't know the difference between Superuser or SuperSU
Or do I have to do it another way?
I have looked at a number of rooting options and am unsure what to do, one way the links on the guide didn't work others are little confusing!
Click to expand...
Click to collapse
The order you have done it in is just wrong, so wrong... But what's done is done
Now that the bootloader is unlocked just flash a 757 FTF and install jackie099's kernel http://forum.xda-developers.com/showthread.php?t=2714511 and then flash SuperSu from recovery
Did you just skip backing up TA partition? Because if you did, that just defeats the purpose of downgrading
Sent from my C6802 using XDA Premium 4 mobile app
Morning peeps,
No atm I stopped at unlocking the bootloader after the downgrade, I have tried to run the Backup-TA-9.10 app but it fails on detecting Root cause obviously mines not rooted.
So regarding backup am not sure what am supposed to do, as all threads seem to point to that you require root to backup o.0
blueether I have read so many threads my eyes feel like they are going to bleed, like my original post stated, it seems to be a loop I was getting stuck in.
I cant backup without root from all the threads comments
I cant root without backup for safety and bootloader unlocked, and to unlock bootloader it seemed I had to be a specific version namely 532 to unlock.
So I have got somewhere, instead of pulling my hair out going no where
I hope the way I have moved forward doesn't or hasn't caused any possible lose of keys etc, so the question is, how do I backup before trying the next step of root?
Read post 6 above, follow all the steps in tat order
Sent from CarbonROM on my Z-Ultra
Blue I was going to use the Binary link but cant figure out how to download it, it mentions in the post to ask members for a working link if you have difficulty.
Do you have one by chance?
Thanks!
blueether said:
Read post 6 above, follow all the steps in tat order
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
OrangeMagicGod said:
Blue I was going to use the Binary link but cant figure out how to download it, it mentions in the post to ask members for a working link if you have difficulty.
Do you have one by chance?
Thanks!
Click to expand...
Click to collapse
Hey dude, what's going on? .. have you successfully root yet?
Which step is you dont understand to ROOT? .
Done the downgrade!
2.Root using either [NUT]'s dual recovery or bin4ries tool - see thread in step above or LordManhattans guide
Its the above, gone to Bin4ries post, the links don't seem to download for me? so cant get the tool to do the root
3.Backup the TA - see LordManhattons guide - should be able to do that, its working to the point of seeing it's not rooted, so not worried about that part!
4.Upgrade to latest FTF
5.Unlock bootloader - Already done by mistake thinking it was done easiler :S
6.Root using jackies099's kernel
7....
The thing I have noticed as well atm which am slightly worried about, is my sim card says invalid atm, hoping that changes when it's all finished
Speederoff said:
Hey dude, what's going on? .. have you successfully root yet?
Which step is you dont understand to ROOT? .
Click to expand...
Click to collapse
OrangeMagicGod said:
Done the downgrade!
2.Root using either [NUT]'s dual recovery or bin4ries tool - see thread in step above or LordManhattans guide
Its the above, gone to Bin4ries post, the links don't seem to download for me? so cant get the tool to do the root
3.Backup the TA - see LordManhattons guide - should be able to do that, its working to the point of seeing it's not rooted, so not worried about that part!
4.Upgrade to latest FTF
5.Unlock bootloader - Already done by mistake thinking it was done easiler :S
6.Root using jackies099's kernel
7....
The thing I have noticed as well atm which am slightly worried about, is my sim card says invalid atm, hoping that changes when it's all finished
Click to expand...
Click to collapse
Lol, you shouldn't unlock bootloader =.=" if you only required ROOT =.=".
if you worried, flash stock rom and redo to root?
Well am confused and lost atm.
Point 2 and Point 6 to me, are they not the same thing?
Trying to carry out Point 2, I cant get any of the software it seems as I cant get the links to work
So atm I have a phone working but telling me my sim is "invalid card - no service" currently
Any help for links to the Nuts, or Binary software would be grateful
Speederoff said:
Lol, you shouldn't unlock bootloader =.=" if you only required ROOT =.=".
if you worried, flash stock rom and redo to root?
Click to expand...
Click to collapse
OrangeMagicGod said:
Well am confused and lost atm.
Point 2 and Point 6 to me, are they not the same thing?
Trying to carry out Point 2, I cant get any of the software it seems as I cant get the links to work
So atm I have a phone working but telling me my sim is "invalid card - no service" currently
Any help for links to the Nuts, or Binary software would be grateful
Click to expand...
Click to collapse
the sim/imei problem shouldn't have happened if you followed my guide, but dont worry, it will come back after step 4
for step to use http://nut.xperia-files.com/?dlid=WlUtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjEyMy1CRVRBLmluc3RhbGxlci56aXA= from http://forum.xda-developers.com/showthread.php?t=2647492 and follow the instructions in post 2
Step 2 is only so we can get a backup of the TA so that it is safe to unlock the bootloader
Step 4 when you update to the latest FTF you will lose root
Step 5 will allow you to get root any time you want without having to do the downgrade dance
Step 6 is needed because the stock kernel wont keep write access to the system. This step also re-installs recovery so that you can flash the superSU update binary
Hi Blue,
Feel like am getting my self further and further into the **** with this
I was able to find bin4ries tool after searching on the net for awhile, and used that as advised, which has worked and didn't seem to be a problem, the SU appeared etc.
I then did the Backup which again has gone fine.
I updated what I thought was the latest TFT C6833_14.1.b.2.257_euro-lte.ftf from one of the links but looking at the phones version am still showing 532
That's the stage am at with still the sim/imei issue
I have downloaded the link you have provided for the lockeddualrecovery looking at it, I get options to
1. installation on ROM rooted with SuperSU
2. "" "" " with SUperUser
3. installation on unrooted ROM
4. exit
at this stage am not sure what to do, as I thought getting all the other steps completed now would have solved this.
Think am starting to regretting trying this and feeling like a total tool!
blueether said:
the sim/imei problem shouldn't have happened if you followed my guide, but dont worry, it will come back after step 4
for step to use http://nut.xperia-files.com/?dlid=WlUtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjEyMy1CRVRBLmluc3RhbGxlci56aXA= from http://forum.xda-developers.com/showthread.php?t=2647492 and follow the instructions in post 2
Step 2 is only so we can get a backup of the TA so that it is safe to unlock the bootloader
Step 4 when you update to the latest FTF you will lose root
Step 5 will allow you to get root any time you want without having to do the downgrade dance
Step 6 is needed because the stock kernel wont keep write access to the system. This step also re-installs recovery so that you can flash the superSU update binary
Click to expand...
Click to collapse
OrangeMagicGod said:
Hi Blue,
Feel like am getting my self further and further into the **** with this
I was able to find bin4ries tool after searching on the net for awhile, and used that as advised, which has worked and didn't seem to be a problem, the SU appeared etc.
I then did the Backup which again has gone fine.
I updated what I thought was the latest TFT C6833_14.1.b.2.257_euro-lte.ftf from one of the links but looking at the phones version am still showing 532
That's the stage am at with still the sim/imei issue
I have downloaded the link you have provided for the lockeddualrecovery looking at it, I get options to
1. installation on ROM rooted with SuperSU
2. "" "" " with SUperUser
3. installation on unrooted ROM
4. exit
at this stage am not sure what to do, as I thought getting all the other steps completed now would have solved this.
Think am starting to regretting trying this and feeling like a total tool!
Click to expand...
Click to collapse
OK so you are past step 3 now and you have a rooted phone with a backed up TA partition.
Step 4
You will want to flash https://docs.google.com/uc?id=0B51NBUj0yr7FNmtzWlhrT2JaOU0&export=download with the lates flashtool from https://unrestrict.li/flashtool instructions are in LordManhattan's guide I think
Step 5
Unlock the bootloader - see LordManhattan's guide again
Step 6
Follow the steps in this thread http://forum.xda-developers.com/showthread.php?t=2714511
Hi Mate,
So do I need to user the lockeddualrecovery still (going to assume not)
The link for the google doc doesn't work am getting an error trying to access it
I have the latest Flashtool installed and ready
blueether said:
OK so you are past step 3 now and you have a rooted phone with a backed up TA partition.
Step 4
You will want to flash https://docs.google.com/uc?id=0B51NBUj0yr7FNmtzWlhrT2JaOU0&export=download with the lates flashtool from https://unrestrict.li/flashtool instructions are in LordManhattan's guide I think
Step 5
Unlock the bootloader - see LordManhattan's guide again
Step 6
Follow the steps in this thread http://forum.xda-developers.com/showthread.php?t=2714511
Click to expand...
Click to collapse
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)
hi
i own a Z2 (d6503)
-bootloader unlocked (everything else is custom) i had rooted it previously but i think i lost the root access while updating the firmware to 4.4.4 using EMma
my problems
1. Google services are not working over wifi, but there is no problem with mobile data.
i have tried clear cache method already, factory reset, date/time thing. Sometimes few retries make playstore work.
2. Phone isn't turning on in recovery mode. neither manually (with buttons) nor with quickboot or PC
everywhere i found the same method: turn off, power on and wait for led to light up then press either of the volume buttons repeatedly. But the led doesnt light up
3. I have lost my DRM keys while unlocking the bootloader. (no TA backup). my bad.
what did i looose other than xreality engine? can it be recovered? how?
4. How can i root the new version of firmware android 4.4.4 (23.0.1.A0.167)
Please help
i am familiar with rooting and know a little more than an average user. But at the end of the day i am a noob too.
1. no idea, sounds weird that it works over data but not WiFi.
2. If your running stock rom then you don't have recovery installed hence you can't access it.
3. AFAIK The play station remote won't work, there is no way to recover DRM keys they are device specific so your out of luck.
4. Downgrade to .314 and flash a pre-rooted zip, there is currently no known exploit for 4.4.4 so no direct root method.
Although you have discouraged me completely, thanks anyway.
Can you explain the pre root zip thing? Shouldnt I just wait for the new rooting method to come up?
Sent from my D6503 using XDA Free mobile app
Absarock1 said:
hi
i own a Z2 (d6503)
-bootloader unlocked (everything else is custom) i had rooted it previously but i think i lost the root access while updating the firmware to 4.4.4 using EMma
my problems
1. Google services are not working over wifi, but there is no problem with mobile data.
i have tried clear cache method already, factory reset, date/time thing. Sometimes few retries make playstore work.
2. Phone isn't turning on in recovery mode. neither manually (with buttons) nor with quickboot or PC
everywhere i found the same method: turn off, power on and wait for led to light up then press either of the volume buttons repeatedly. But the led doesnt light up
3. I have lost my DRM keys while unlocking the bootloader. (no TA backup). my bad.
what did i looose other than xreality engine? can it be recovered? how?
4. How can i root the new version of firmware android 4.4.4 (23.0.1.A0.167)
Please help
i am familiar with rooting and know a little more than an average user. But at the end of the day i am a noob too.
Click to expand...
Click to collapse
Once rooted, you can recover most features flashing this : DRM FUNTION RESTORATION FOR UB
Absarock1 said:
Although you have discouraged me completely, thanks anyway.
Can you explain the pre root zip thing? Shouldnt I just wait for the new rooting method to come up?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
AFAIK devs aren't putting a huge amount of effort into finding a new root exploit, why bother when achieving root through downgrade and flashing pre-rooted is fairly trivial.
The pre-rooted zips are just that stock .167 roms that have been pre-rooted, they can be flashed over earlier fw without data loss.
So where can i get one?
ghostofcain said:
AFAIK devs aren't putting a huge amount of effort into finding a new root exploit, why bother when achieving root through downgrade and flashing pre-rooted is fairly trivial.
The pre-rooted zips are just that stock .167 roms that have been pre-rooted, they can be flashed over earlier fw without data loss.
Click to expand...
Click to collapse
[/CODE][/CODE]
oh damn! In my first post i made a mistake i meant to say (everything is stock) but wrote custom instead.
terribly sorry
Where can i get one of these roms u just mentioned?
Even if i get it, how do i flash it? I dont have a custom recovery installed and if there is a stock recovery i cant enter it.
can u elaborate the procedure i mentioned below?
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the boot.img to the folder containing fastboot binary
flash the boot.img using fastboot:
Code:
fastboot flash boot boot.img
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
THAnks
thanks man. 3/4 of my problems are solved now. 1 is going to be solved soon hopefully.