Hi guys,
Just bought the z2 second handed and as I was checking service info, under firmware info I saw some kind of "maxim" under device. What does this mean? Can it be somehow customized to track my actions or whatsoever?
Koostis said:
Hi guys,
Just bought the z2 second handed and as I was checking service info, under firmware info I saw some kind of "maxim" under device. What does this mean? Can it be somehow customized to track my actions or whatsoever?
Click to expand...
Click to collapse
From what I can read on my phone, it is giving the service centre info on the chipset in the phone and the screen in it. I don't think it is anything to do with tracking. I bought mine brand new, unlocked by the way so I know mine isn't anything to do with carrier tracking.
just flash a stock firmware and it should change the info to the right info
I am on stock version, recycled with Sony companion. Was simply worried if the previous owner could have changed build.prop or customization in some way
What he's saying though is if you flash a stock firmware file (ftf file via Flashtool) it will erase everything from the previous owner, and give you a brand new fresh install, so there's no way that the previous owner would be able to track anything.
bdithug said:
What he's saying though is if you flash a stock firmware file (ftf file via Flashtool) it will erase everything from the previous owner, and give you a brand new fresh install, so there's no way that the previous owner would be able to track anything.
Click to expand...
Click to collapse
Wait, so repairing the phone with pc companion does not give you as clean install as flashing with flash tool does? I thought that both methods completely overwrite the OS
Koostis said:
Wait, so repairing the phone with pc companion does not give you as clean install as flashing with flash tool does? I thought that both methods completely overwrite the OS
Click to expand...
Click to collapse
Yeah, im also prefer flashtool for a clean and fresh installation.
Sent from my D6503
Koostis said:
Wait, so repairing the phone with pc companion does not give you as clean install as flashing with flash tool does? I thought that both methods completely overwrite the OS
Click to expand...
Click to collapse
To be honest, I'm not sure the exact differences between a software repair via pcc or flashing an ftf via Flashtool, but if you're really concerned, I'd do both. The two methods could very well do the exact same thing though.
I wrote to Sony and they said it's completely normal as the maxim thing is a name of some component. Seems to have been nothing but empty worries
Related
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
I tried to install a custom rom and followed the instructions from this thread. All works fine until I did a fatal mistake: Instead of flashing the nAa kernel as described, I accidently flashed X10 V1 BLRelock that was previously chosen. Now my phone is completely dead, not detected by Flashtool or SEUS, I can't get it into flashmode (pressing 'back' while connecting) even after removing battery several times for different lasting periods.
Is there any chance to recover the phone or am I supposed to buy a new one?
Akrisios said:
I tried to install a custom rom and followed the instructions from this thread. All works fine until I did a fatal mistake: Instead of flashing the nAa kernel as described, I accidently flashed X10 V1 BLRelock that was previously chosen. Now my phone is completely dead, not detected by Flashtool or SEUS, I can't get it into flashmode (pressing 'back' while connecting) even after removing battery several times for different lasting periods.
Is there any chance to recover the phone or am I supposed to buy a new one?
Click to expand...
Click to collapse
Having a repair-shop JTag it may be cheaper than buying a new phone...
Well, unbricking by JTAG might be cheaper, of course - but is this the only chance? Anything I can do?
Akrisios said:
Well, unbricking by JTAG might be cheaper, of course - but is this the only chance? Anything I can do?
Click to expand...
Click to collapse
It seems to happen a lot lately, that people flash the x10blrelock.ftf, and it always bricks their phone, don't think anyone has a home-solution for that yet.
SmG67 said:
It seems to happen a lot lately, that people flash the x10blrelock.ftf, and it always bricks their phone, don't think anyone has a home-solution for that yet.
Click to expand...
Click to collapse
Can the flash-tool be upgraded to test if a custom kernel is installed before someone try to flash the bootloader relock-ftf, and then simply deny to flash x10blrelock.ftf?
Emperor.dk said:
Can the flash-tool be upgraded to test if a custom kernel is installed before someone try to flash the bootloader relock-ftf, and then simply deny to flash x10blrelock.ftf?
Click to expand...
Click to collapse
Doesn't seem to matter whether you're on stock or custom kernel, the x10Blrelock just bricks the phones. If you need to relock the bootloader for some reason use S1Tool's Restore option.
The best advice i can give at this moment is to just remove the x10blrelock.ftf from the flashtool/firmwares sub-folder so it can't get flashed by accident.
SmG67 said:
Doesn't seem to matter whether you're on stock or custom kernel, the x10Blrelock just bricks the phones. If you need to relock the bootloader for some reason use S1Tool's Restore option.
The best advice i can give at this moment is to just remove the x10blrelock.ftf from the flashtool/firmwares sub-folder so it can't get flashed by accident.
Click to expand...
Click to collapse
we should have a sticky thread (locked for no replies) with a list of read-first-warnings/what-never-to-do for our minnies. not a loong guide, just a simple list. i think it would serve an important purpose and avoid a lot of bricks for first-time-flash-users.
even I managed to brick my X10MP first time I flashed a ROM. it was loooooong before bootloader-unlock was possible, so very easy to fix.
Well guys, today the postman brought my x10mini pro back from the jtag shop. They did a quite good job by jtagging it for installing an original firmware. The issue is: This one seems to be older than the one I once had. I tried to update the software via PC Companion but there is no higher version available.
For installing CM7-2.2.1 I need Firmware Latest 2.1.1.A.0.6 with Baseband: M76XX-TSNCJOLYM-53404015 - this I had before bricking it.
Now I only have 2.1.1.A.0.54. Where do I get the latest update if not from SE itself?
Akrisios said:
Well guys, today the postman brought my x10mini pro back from the jtag shop. They did a quite good job by jtagging it for installing an original firmware. The issue is: This one seems to be older than the one I once had. I tried to update the software via PC Companion but there is no higher version available.
For installing CM7-2.2.1 I need Firmware Latest 2.1.1.A.0.6 with Baseband: M76XX-TSNCJOLYM-53404015 - this I had before bricking it.
Now I only have 2.1.1.A.0.54. Where do I get the latest update if not from SE itself?
Click to expand...
Click to collapse
I think you *should* be ok as long as the baseband is the required version, but there are original firmwares available in the x10 mini pro development section. There is a kernel+baseband package here
( And don't forget to delete the x10blrelock.ftf package from the flashtool\firmwares subfolder )
SmG67 said:
And don't forget to delete the x10blrelock.ftf package from the flashtool\firmwares subfolder
Click to expand...
Click to collapse
This was the first thing I've done after bricking the device
I now installed your linked fw/baseband version, it states the correct baseband ending with ...15 now, but the build goes to 2.0.A.0.504
OK... I did it too... I hard bricked it... now I want to repair it myself, but I will need some help.
I bought these things:
...
Segger J-Link: http://www.segger.com/jlink_base.html
...
GPG Industries u20i resurrection cable: http://www.gsmsp.com/products/Servi...e_for_U20i__by_GPGindustries__1209_19715.html
...
The cable has a battery slot that has no pins (I guess they are not needed), but I soldered them out (just in case) so the battery fits and I can set it on top of the cable so it can power the phone with the J-Link plugged on if needed.
I have a problem finding the correct config files for the J-Link to reprogram the phone. I can't get it to recognize the phone. Maybe I'm doing something wrong in the whole procedure. I don't know... I would be glad if someone experienced with Segger J-Link could help me.
I was watching videos on YouTube about resurrecting the phone with a Riff Box... then I checked, the both boxes have same pin-outs... more the J-Link has a power pin plus, that the Riff box is missing.
X10 Mini totally dead bricked
Congrats!!! Happened to me too just now.
Let me know your progress will order cables but it might take a while for me to get them hence I´m in Brazil.
Question
Akrisios said:
Well, unbricking by JTAG might be cheaper, of course - but is this the only chance? Anything I can do?
Click to expand...
Click to collapse
i found this link :
http://forum.xda-developers.com/showthread.php?p=51706478
are this method work?
Akrisios said:
I tried to install a custom rom and followed the instructions from this thread. All works fine until I did a fatal mistake: Instead of flashing the nAa kernel as described, I accidently flashed X10 V1 BLRelock that was previously chosen. Now my phone is completely dead, not detected by Flashtool or SEUS, I can't get it into flashmode (pressing 'back' while connecting) even after removing battery several times for different lasting periods.
Is there any chance to recover the phone or am I supposed to buy a new one?
Click to expand...
Click to collapse
i m also facing the same problem any one has a solution pls reply
Priyesh512 said:
i m also facing the same problem any one has a solution pls reply
Click to expand...
Click to collapse
Try JTAG
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...
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.