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...
Related
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
Any ideas on how to fix my Xperia Ray? HELP..
Quick backstory - my Xperia Ray won't read my SIM card anymore. It doesn't even ask for my PIN number, it just boots as normal (after asking me to pick a language) but I have no connection to any network. I've tried using the SIM card in another phone and it works fine, therefore the problem is with the phone itself.
I'd recently had my phone network & bootloader unlocked by wotanserver using the test point method - because of this I thought the DRM keys would be fine (e.g. TrackId & Timescape still worked). However, when I was updating from GB .42 to .62 OTA (to flash a GB ROM) my phone bricked! (Does this mean the DRM keys weren't intact? Confused.)
So, I searched for a solution and ended up using s1tool to relock the bootloader. Then I used flashtool to flash a stock ICS ftf file. It seemed to work (the phone rebooted) but it was then I noticed that the SIM card wasn't being recognised. Also, in the Flashtool log I noticed that a blue line was there saying 'this file is ignored simlock.ta'.
Anyway, my real dilemma is - which of the Available Omnius Operations for the Xperia Ray (see link: http://www.omnius-server.com/phone?id=20… should I pick to fix this?
Backup TA
Flash
Identify
Live boot
Repair S1-boot
Restore TA
Revive phone after OTA flash
Unlock bootloader
Unlock network lock by certificate replacement
Repair S1boot? Restore TA? I really don't know. Would really. really appreciate someone's help - I need my phone back urgently!
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
XperienceD said:
Updating via OTA on an unlocked bootloader does lead to a bricked Phone, which just requires THIS to fix it.
Click to expand...
Click to collapse
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem. I was asking what fix in the Omnius list of options applied to my situation. Do I need to Repair S1-boot? Do I need to 'Restore TA?' I really don't know to be honest.
All I really need to know is what option from Omnius's list applies to my situation...
seamo123 said:
Hi, thanks for your reply! I'm not sure what you mean though - the link provided in the first post on that thread took me to a dodgy website to download a file called 'downloadmanager
_setup' All that did was install crap like 'Zoomdownloader' and other non-android related rubbish on my computer. So I'm not best pleased about that...
Click to expand...
Click to collapse
Just checked the link myself, as it didn't skip the ad and asked you to download something else instead, that should have rang alarm bells. This is what you should have downloaded - FlashTool_0.2.9.1_FOTAUnbrick
seamo123 said:
Anyhoo, my phone isn't really bricked - it works fine apart from the SIM problem.
Click to expand...
Click to collapse
Your Phone was bricked in the first place due to an OTA update, and should actually state in what ever thread you used to unlock not to use the OTA feature after doing so, the attachment normally fixes that, given that you've re-locked using S1Tool then you may have done more harm than good. If I knew what option to suggest I would have done so, so unless anyone else does then it's trial and error I'm afraid.
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
seamo123 said:
Is it too late for me to give the link you gave me a shot then? Or might it do more harm than good at this stage? Thanks for your help btw, I appreciate it.
Click to expand...
Click to collapse
You could try to unlock the boot loader again, flash stock ICS and kernel and try again to connect the sim card...
Or have you tried PC companion to fix your phone? Try this first!
But I can't promise anything, maybe you will end up in a bigger problem than now
Sent from my Nexus 7 running Android 4.2.1
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.
Since it looks like I can't unlock the boot loader on my model I am thinking about returning my tablet and getting a different model or looking into warranty options. In either case I would need to have unrooted the tablet. The problem is that nothing I try seems to work. A factory reset doesn't unroot it. SuperSU unroot option doesn't work. Universal Unroot Tool doesn't work either.
I was partially rooted with Towel Root and then fully Rooted with Easy Root. What are the steps I can take to reverse it?
Elliander said:
Since it looks like I can't unlock the boot loader on my model I am thinking about returning my tablet and getting a different model or looking into warranty options. In either case I would need to have unrooted the tablet. The problem is that nothing I try seems to work. A factory reset doesn't unroot it. SuperSU unroot option doesn't work. Universal Unroot Tool doesn't work either.
I was partially rooted with Towel Root and then fully Rooted with Easy Root. What are the steps I can take to reverse it?
Click to expand...
Click to collapse
Just flash your stock firmware via latest Flashtool or Sony pc Companion.
kulvertti said:
Just flash your stock firmware via latest Flashtool or Sony pc Companion.
Click to expand...
Click to collapse
Not possible. First of all, I am on stock firmware, and second of all the Sony PC Companion doesn't work with SGP561. It specifically tells me to use the "Verizon Software Update Tool", but Verizon refuses to tell me where this is because I am not a customer and none of the old versions I could find work. Since I couldn't use Sony PC Companion I couldn't create a TFT image to begin with and although I can use Flashtool I would need one of the stock firmware SGP561_17.1.D.0.417 that is also Verizon locked or it will fail, but since I can't create a TFT image with Sony PC Companion the likelihood of finding one that works is low. Hypothetically though if I could find that exact stock firmware I could flash it and everything would go back to normal. (Unbranded firmware fails, BTW, and since the bootloader can't be unlocked on my model custom firmware isn't possible either)
I called Sony to find out where the required Verizon Software is located and they said it will take a day or two for researching the problem. No one seems to know anything about it.
Elliander said:
Not possible. First of all, I am on stock firmware, and second of all the Sony PC Companion doesn't work with SGP561. It specifically tells me to use the "Verizon Software Update Tool", but Verizon refuses to tell me where this is because I am not a customer and none of the old versions I could find work. Since I couldn't use Sony PC Companion I couldn't create a TFT image to begin with and although I can use Flashtool I would need one of the stock firmware SGP561_17.1.D.0.417 that is also Verizon locked or it will fail, but since I can't create a TFT image with Sony PC Companion the likelihood of finding one that works is low. Hypothetically though if I could find that exact stock firmware I could flash it and everything would go back to normal. (Unbranded firmware fails, BTW, and since the bootloader can't be unlocked on my model custom firmware isn't possible either)
I called Sony to find out where the required Verizon Software is located and they said it will take a day or two for researching the problem. No one seems to know anything about it.
Click to expand...
Click to collapse
I could do it for you if you wish. Do you really want 417 ftf or newer 437 ftf file?
kulvertti said:
I could do it for you if you wish. Do you really want 417 ftf or newer 437 ftf file?
Click to expand...
Click to collapse
Before you go through that trouble wait a bit.
Since the Verizon tool I could find failed - rendering it half bricked waiting for a proper update - and since neither Sony nor Verizon knows anything about the tool I am required to use they are willing to accept the warranty service on it. I am fortunate that because the failed update wiped the data there is no evidence of it ever being rooted and since this model's boot loader can't be unlocked even if it is fried there is no evidence of me doing anything wrong with it. And it was Verizon's tool that did it, so it's an honest case.
Anyway, I sent them a screenshot from last night proving this tablet hasn't been unlocked and I am on the phone with Sony on hold to see if they would be willing to sell me an International version right now and then refund me when they receive it. Since I need it for college on the 25th (textbook replacement) and I have no problems paying upfront they seem to think it should be possible, but they are all sort of talking with each other about it to see if it really can be done. If they can I will be able to get rid of the Verizon mess permanently.
If not, getting that firmware update from you would be greatly appreciated. I'll edit this post when I know what's going to happen.
Elliander said:
Before you go through that trouble wait a bit.
Since the Verizon tool I could find failed - rendering it half bricked waiting for a proper update - and since neither Sony nor Verizon knows anything about the tool I am required to use they are willing to accept the warranty service on it. I am fortunate that because the failed update wiped the data there is no evidence of it ever being rooted and since this model's boot loader can't be unlocked even if it is fried there is no evidence of me doing anything wrong with it. And it was Verizon's tool that did it, so it's an honest case.
Anyway, I sent them a screenshot from last night proving this tablet hasn't been unlocked and I am on the phone with Sony on hold to see if they would be willing to sell me an International version right now and then refund me when they receive it. Since I need it for college on the 25th (textbook replacement) and I have no problems paying upfront they seem to think it should be possible, but they are all sort of talking with each other about it to see if it really can be done. If they can I will be able to get rid of the Verizon mess permanently.
If not, getting that firmware update from you would be greatly appreciated. I'll edit this post when I know what's going to happen.
Click to expand...
Click to collapse
Okey buddy. However I allready make ftf file for your but it is Verizon 417 stock. Let me know if you need Verizon 437 firmware.
Here is the link need it or not:
https://mega.co.nz/#!UJJEAR5B!tK7pQEeppCmTQKxSA0tEL5_W3A7o_q6dsn3FXh43LYA
kulvertti said:
Okey buddy. However I allready make ftf file for your but it is Verizon 417 stock. Let me know if you need Verizon 437 firmware.
Here is the link need it or not:
https://mega.co.nz/#!UJJEAR5B!tK7pQEeppCmTQKxSA0tEL5_W3A7o_q6dsn3FXh43LYA
Click to expand...
Click to collapse
Thanks. At the very least that will help the next person with a problem.
Sony was willing to sell me an SGP512 model and is going to process a refund for what I paid on the SGP561. That's a better solution anyway since I'm not on Verizon's network - especially since Verizon doesn't support it. I paid for expedited shipping so I will get it in 2 days and I won't need to deal with any Verizon apps. I paid for 3 year extended warranty as well which covers all damage so as long as I dont't mess with the boot loader I shouldn't have any problems with it.
To anyone else reading this: Avoid the factory unlocked SGP561! It's a nightmare!
kulvertti said:
Okey buddy. However I allready make ftf file for your but it is Verizon 417 stock. Let me know if you need Verizon 437 firmware.
Here is the link need it or not:
https://mega.co.nz/#!UJJEAR5B!tK7pQEeppCmTQKxSA0tEL5_W3A7o_q6dsn3FXh43LYA
Click to expand...
Click to collapse
I wanna return it to stock and unroot it how do i know if i need 417 or 437?
Hello. I just received an Xperia Z3 Compact tablet (SGP641) compact tablet that I bought used. It is unlocked. I don't know if that means it is rooted, as well, as I am new to this.
Anyhow, I tried to update the tablet through the device itself, but it says it is up to date at version 5.0. So, then I try to update it using the Xperia companion on my PC. When I try, it gives me an error message that reads: "Update failed. The device contains modified software that cannot be updated. Error code: UEGetPhoneInfoRootedDevice
UE_2003"
I have no idea what this means. Does this mean that I cannot update the tablet, at all? Can I "un-root" the tablet? Basically, what are my options at this point? I would just like to update to its latest Android version. The battery life is not what I was expecting. I mean, it drains over 20% in an hour. Is that normal? I am hoping an update might help this out a bit.
Thank you in advance for any and all help, advice and suggestions. I really don't know anything about this, so I really would appreciate all the help I can get.
Thanks!
Edit:
So, it turns out that the device has been rooted and the bootloader unlocked. The seller just conveniently forgot to mentioned this during the sales process. Very frustrating. What can I do?
No the battery drain is not normal. I did not get an update either, here in The Netherlands. So I flashed a stock German version instead and changed the language afterwards. You would need Flashtool for that. The Xperia Blog has a good tutorial for Flashtool, but I guess you can also find it on xda. If you flash a stock version you will be unrooted as well.
If you wish, you can also lock the bootloader again in Flashtool.
Since your bootloader had been unlocked your DRM keys are probably lost, resulting in lower quality photos at low light conditions.
M1chiel said:
No the battery drain is not normal. I did not get an update either, here in The Netherlands. So I flashed a stock German version instead and changed the language afterwards. You would need Flashtool for that. The Xperia Blog has a good tutorial for Flashtool, but I guess you can also find it on xda. If you flash a stock version you will be unrooted as well.
If you wish, you can also lock the bootloader again in Flashtool.
Since your bootloader had been unlocked your DRM keys are probably lost, resulting in lower quality photos at low light conditions.
Click to expand...
Click to collapse
Thank you very much for your reply!
I am concerned to read that about the battery. I am beginning to really feel that I go a lemon.
Could you possibly explain more about flashing to stock, please? I am going to search and check out what you recommended, I just thought in the mean time you (or some other helpful poster) could clue me in a bit more.
Do you know if I can use the Xperia companion tool to do a software repair? It is an option within the program. I am just wondering if that will re-lock it and allow me to update.
Thank you very much, again, for your help! I really appreciate it.
I am not sure if Xperia Companion still works with an unlocked bootloader. But you can always give it a try. Flashtool is a much more powerful tool as it allows you to choose the rom you prefer, even if it is a downgrade.
M1chiel said:
I am not sure if Xperia Companion still works with an unlocked bootloader. But you can always give it a try. Flashtool is a much more powerful tool as it allows you to choose the rom you prefer, even if it is a downgrade.
Click to expand...
Click to collapse
Do you if there is any way to tell what, if anything, is on the device...as far as custom ROMs, rooted, unlocked boot loader...etc?
In Settings -> About you can access diagnostics with some basic info. More advanced diagnostics can be accessed if you install a phone dialer (I tried Pixelphone Dialer) and dial *#*#service#*#*. In Service Tests -> Security you can find your bootloader status. If it is locked it says Marlin [Key OK][Active] and the same for the other items. In addition you can find lots of other info there.
M1chiel said:
In Settings -> About you can access diagnostics with some basic info. More advanced diagnostics can be accessed if you install a phone dialer (I tried Pixelphone Dialer) and dial *#*#service#*#*. In Service Tests -> Security you can find your bootloader status. If it is locked it says Marlin [Key OK][Active] and the same for the other items. In addition you can find lots of other info there.
Click to expand...
Click to collapse
Thank you very much for taking the time to respond and help.
Will I mess anything up if I go ahead and flash a stock version or try to relock it if, by chance, it is not locked, rooted or anything?
Nope, but make sure you flash a correct ftf for your model. I'd advise you to wipe data, cache and apps log in Flashtool to make sure you have a fresh start. Any Marshmallow stock rom would be ok.
M1chiel said:
Nope, but make sure you flash a correct ftf for your model.
Click to expand...
Click to collapse
I can find that just by searching for the model number (SGP641), correct?
Flashtool will recognize your model as well.
M1chiel said:
Flashtool will recognize your model as well.
Click to expand...
Click to collapse
Thank you so much. I am going to try and do it now. I will post my results, just in case someone else may be having the same issue.
M1chiel said:
Flashtool will recognize your model as well.
Click to expand...
Click to collapse
I am having a rough time finding out what to do. The only thing that I can see is the Taiwanese version, which is the model the SGP641 is, but I am confused about how to do it. Can I just flash it to the file that is on Xperia blog, or do I have to downgrade it first?
Edit:
So, it turns out that the device has been rooted and the bootloader unlocked. The seller just conveniently forgot to mentioned this during the sales process. Very frustrating. What can I do?
Well, as the Dutch philosopher Johan Cruyff said: every disadvantage has its advantage. It depends on what you want. If you want to stay rooted, you can flash a prerooted Marshmallow rom for your model from recovery. Usually you can enter recovery by pressing volume down or up during boot until the led changes color. Root is attractive because you can remove bloatware and install costumizations. If you do not want root you can flash a stock rom with Flashtool.
dude you want only to update marshmallow?if not,i can give u 2 options for a veeery stable and battery friendly tablet.