Related
Had a problem with recovery going missing when i updated to 4.3, decided to downgrade back to 4.2 rom 534 and after the downgrade my IMEI reads a series of 0's obviously can't make any phone calls and have no signal at all.
Have tried to get the EE branded ftf but it wouldn't download, I didn't want to get another branded one so i went with an unlocked one, still can't get the EE ftf so can't revert back to my official branded rom, still haven't got recovery and by using an ftf i've lost root, so i'm kind of back to square one but with no imei lol, ahhh if i didn't laugh i'd cry.
Any ideas how to get it back up and running?
Cheers.
This may help i havent tried it myself as thats one of the few problems that my crappy Z1 haven't got .
http://forum.xda-developers.com/showpost.php?p=48597629&postcount=11
hope it helps.
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
This may help i havent tried it myself as thats one of the few problems that my crappy Z1 haven't got .
http://forum.xda-developers.com/showpost.php?p=48597629&postcount=11
hope it helps.
elander said:
This may help i havent tried it myself as thats one of the few problems that my crappy Z1 haven't got .
http://forum.xda-developers.com/showpost.php?p=48597629&postcount=11
hope it helps.
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
This may help i havent tried it myself as thats one of the few problems that my crappy Z1 haven't got .
http://forum.xda-developers.com/showpost.php?p=48597629&postcount=11
hope it helps.
Click to expand...
Click to collapse
Only just got home but i've sorted it now, basically i wasn't able to get the EE branded ftf from XDA as the link was down so i got the tmobile one as it's pretty much the closest one there is in the list.
Flashed that with flash tool and it came back, obviously lost root, so i've re rooted and now i'm upgrading all over again.
Will be staying on 4.2 until i've got a whole day to mess about with things, 4.3 isn't for me yet, at least until root is 100%
Cheers for the help all the same.
Problems occur if 4.3 is flashed using flashtool.
I solved it by reinstalling the software using SUS then flashing 4.2
Regards,
~J2C
Just2Cause said:
Problems occur if 4.3 is flashed using flashtool.
I solved it by reinstalling the software using SUS then flashing 4.2
Regards,
~J2C
Click to expand...
Click to collapse
SUS???...
Darkstylance said:
SUS???...
Click to expand...
Click to collapse
Sony Update Service.
Regards,
~J2C
Ok... Thanks...
I tried to reinstall with SUS 4.3, and then flash with flashtool, but I still departing imei all 0.
I'm desperate, please help me.:crying:
Thebox said:
I tried to reinstall with SUS 4.3, and then flash with flashtool, but I still departing imei all 0.
I'm desperate, please help me.:crying:
Click to expand...
Click to collapse
Flash from android 4.3 to 4.2 .257 then from 257 to 534, root then OTA to 257 and wait for a rooting solution for android 4.3.
Regards,
~J2C
Thebox said:
I tried to reinstall with SUS 4.3, and then flash with flashtool, but I still departing imei all 0.
I'm desperate, please help me.:crying:
Click to expand...
Click to collapse
Just grab the closest rom you initially started with and flash with flashtool, that's pretty much all i did.
Then root.
Install clock work mod or TWRP.
Then flash a rom from the development section like monx.
Just2Cause said:
Flash from android 4.3 to 4.2 .257 then from 257 to 534, root then OTA to 257 and wait for a rooting solution for android 4.3.
Regards,
~J2C
Click to expand...
Click to collapse
dladz said:
Just grab the closest rom you initially started with and flash with flashtool, that's pretty much all i did.
Then root.
Install clock work mod or TWRP.
Then flash a rom from the development section like monx.
Click to expand...
Click to collapse
Just get recover flash IMEI if the stock 290. And this version has no root, there is the problem.
I tried to flash the rom Monx but still all the same.
Thebox said:
Just get recover flash IMEI if the stock 290. And this version has no root, there is the problem.
I tried to flash the rom Monx but still all the same.
Click to expand...
Click to collapse
I assume you didn't understand what I mean, while using android 4.3, flash for the previous firmware 257 (the unrootable android 4.2) and then flash 534 (the rootable android 4.2) then root and OTA to 257 again, then from 257, if you get OTA to 4.3 then go for it, if you don't have OTA to 4.3, you'll have to wait.
Thebox said:
Just get recover flash IMEI if the stock 290. And this version has no root, there is the problem.
I tried to flash the rom Monx but still all the same.
Click to expand...
Click to collapse
In my personal instance i couldn't get recovery, nothing would work, I had to downgrade.
Just2Cause said:
I assume you didn't understand what I mean, while using android 4.3, flash for the previous firmware 257 (the unrootable android 4.2) and then flash 534 (the rootable android 4.2) then root and OTA to 257 again, then from 257, if you get OTA to 4.3 then go for it, if you don't have OTA to 4.3, you'll have to wait.
Click to expand...
Click to collapse
Just one leap back to the earliest rom is all thats needed to get your imei back, obviously not the easiest way but probably the safest.
dladz said:
Just one leap back to the earliest rom is all thats needed to get your imei back, obviously not the easiest way but probably the safest.
Click to expand...
Click to collapse
If you flash from 290 to 534 you will loose IMEI and service provider signal, if you flash back 290 you will get them back. so to prevent loosing IMEI and service provider signal, flash 257 then 534.
Just2Cause said:
If you flash from 290 to 534 you will loose IMEI and service provider signal, if you flash back 290 you will get them back. so to prevent loosing IMEI and service provider signal, flash 257 then 534.
Click to expand...
Click to collapse
Jeez i'll say again.
I downloaded the T-mobile FTF file as it was the closest to my EE phone when i got it, i was on 290 and without my IMEI, i flashed the FTF file via flashtool which is a 534FTF and my IMEI come back as soon as the phone came on, i was able to root and upgrade to monx's rom.
So what you're saying is untrue, if you pick the wrong FTF file then that may cause the IMEI to be lost again or not come back at all, but if you pick the one as i said before which corresponds with your phones original network or the closest thing to it then the imei will come back I know this as I did this a few days ago, i'm not going to argue about this and i'm not going to respond to anything else on this matter.
If theres another way to do it then fair enough, all I know is that doing it this way worked.
The imei gets lost if you wipe data when you are on 290 and flash 534 using flashtool
Sent from my C6903 using xda app-developers app
n3rrox said:
The imei gets lost if you wipe data when you are on 290 and flash 534 using flashtool
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
And if you don't wipe data you get stuck in a bootloop. (I tried it)
Just2Cause said:
I assume you didn't understand what I mean, while using android 4.3, flash for the previous firmware 257 (the unrootable android 4.2) and then flash 534 (the rootable android 4.2) then root and OTA to 257 again, then from 257, if you get OTA to 4.3 then go for it, if you don't have OTA to 4.3, you'll have to wait.
Click to expand...
Click to collapse
Ok, and where I can dowload the 257 versión for flashtool?
Thanks
Enviado desde mi C6903 mediante Tapatalk
Thebox said:
Ok, and where I can dowload the 257 versión for flashtool?
Thanks
Enviado desde mi C6903 mediante Tapatalk
Click to expand...
Click to collapse
You can find the link in the mega ftf collection thread, here
I have a c6902 in the USA on Tmobile. I used Pc companion to update to stock .290 firmware (Jellybean 4.3), lost root (and thought I was fine without it).
I read a thread about downgrading using FTF on flashtool and that your sim card won't work correctly? (I think that's what i read).
I just wanted to know is this correct or did I misread something?
I'm wanting to revert to the firmware before .290, looking at the FTF thread it looks like .257 is what i need, but Which of the three?
my software id is: C6902 R4B
C6902 14.1.G.2.257 Commercial/Journalist 1277-1348_R1A
C6902 14.1.G.2.257 Generic IN 1277-2364_R5A
C6902 14.1.G.2.257 Generic TH 1276-7160_R4A
Is there anything else I should know or do before downgrading? (aside from making a TA backup?)
I want to downgrade to gain full root again, and the minor annoyances I'm encountering will go away too (mainly sound output issues since upgrading; i.e lost the stock tones i was using for alarms and phone has been rebooted a few times to make notification/ringtones output {stock and custom})
Sorry for my noobishness, (cut my teeth on android using htc phones for the past 3-4 years, this Z1 is slightly foreign to me)
That is correct, you'll lose sim card detection like I did. I used the sony PC Companion to reset my phone (so I got sim detection back), then followed this guide:
http://techbeasts.com/2013/12/19/in...ng-latest-14-2-0-a-290-firmware-how-to-guide/
Took less than 20 minutes and was so easy.
Shroomster said:
I have a c6902 in the USA on Tmobile. I used Pc companion to update to stock .290 firmware (Jellybean 4.3), lost root (and thought I was fine without it).
I read a thread about downgrading using FTF on flashtool and that your sim card won't work correctly? (I think that's what i read).
I just wanted to know is this correct or did I misread something?
I'm wanting to revert to the firmware before .290, looking at the FTF thread it looks like .257 is what i need, but Which of the three?
my software id is: C6902 R4B
C6902 14.1.G.2.257 Commercial/Journalist 1277-1348_R1A
C6902 14.1.G.2.257 Generic IN 1277-2364_R5A
C6902 14.1.G.2.257 Generic TH 1276-7160_R4A
Is there anything else I should know or do before downgrading? (aside from making a TA backup?)
I want to downgrade to gain full root again, and the minor annoyances I'm encountering will go away too (mainly sound output issues since upgrading; i.e lost the stock tones i was using for alarms and phone has been rebooted a few times to make notification/ringtones output {stock and custom})
Sorry for my noobishness, (cut my teeth on android using htc phones for the past 3-4 years, this Z1 is slightly foreign to me)
Click to expand...
Click to collapse
On a C6906, I had no issues whatsoever downgrading from 290 to 257.
TagEHeuer said:
That is correct, you'll lose sim card detection like I did. I used the sony PC Companion to reset my phone (so I got sim detection back), then followed this guide:
http://techbeasts.com/2013/12/19/in...ng-latest-14-2-0-a-290-firmware-how-to-guide/
Took less than 20 minutes and was so easy.
Click to expand...
Click to collapse
So you downgraded, used pc companion to repair your problem while on .257, rooted, upgraded then rooted again?
Following that guide, I have a locked bootloader currently. If I unlock it on .290, do I lose any functionality or does the phone just factory reset?
sent from my rooted Xperia Z1
Shroomster said:
So you downgraded, used pc companion to repair your problem while on .257, rooted, upgraded then rooted again?
Following that guide, I have a locked bootloader currently. If I unlock it on .290, do I lose any functionality or does the phone just factory reset?
sent from my rooted Xperia Z1
Click to expand...
Click to collapse
I unlocked it on .290 and I didn't lose any functionality or it didn't factory reset (back up in case) http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
I used Sony to reset all my phone back to the latest firmware which was .290 (as I lost sim defextion), then just followed the guide I originally posted.I never downgraded.
Sent from my C6903 using Tapatalk
So what did you do to lose sim card operation?
sent from my rooted Xperia Z1
Shroomster said:
So what did you do to lose sim card operation?
sent from my rooted Xperia Z1
Click to expand...
Click to collapse
I tried flashing back to .534 from .290 after I upgraded to 4.3. It kept boot looping then bricked.
Simply, you have 2 solutions to downgrade without losing SIM signal.
1- Downgrade from 290 to 257, then from 257 to 534 (then root then OTA to 257 if you downgraded to root it).
2- When downgrading from 290 to 534, exclude "Baseband" in Flashtool and you'll be good to go.
Regards,
~J2C
The only problem I have is I can't find ftf in the ftf thread for my c6902 that matches my id
sent from my rooted Xperia Z1
Dial *#*#7378423#*#* then go to service info then software info and see what is your customization number and look for that number in the ftf thread.
If you want to go back to 257 for root, then you have 2 options:
1- flash 257, then 534, root and OTA to 257.
2- flash 534 and exclude baseband then, root and OTA to 257.
Regards,
~J2C
Just2Cause said:
Dial *#*#7378423#*#* then go to service info then software info and see what is your customization number and look for that number in the ftf thread.
If you want to go back to 257 for root, then you have 2 options:
1- flash 257, then 534, root and OTA to 257.
2- flash 534 and exclude baseband then, root and OTA to 257.
Regards,
~J2C
Click to expand...
Click to collapse
Yes, I read how to find my ID, and it is not listed in the ftf thread. C6902 R4B
sent from my rooted Xperia Z1
Shroomster said:
Yes, I read how to find my ID, and it is not listed in the ftf thread. C6902 R4B
sent from my rooted Xperia Z1
Click to expand...
Click to collapse
There are numbers before the "R4A", look for the numbers, not the R4A.
Just2Cause said:
There are numbers before the "R4A", look for the numbers, not the R4A.
Click to expand...
Click to collapse
Yes, and I'm not sure if the initials in the files stand for the region it is from.
there are three possible files for me to download for the c6902:
IN
TH
journal/commercial
No idea what the differences are.
By the way...unlocking the bootloader did wipe my phone/factory reset it. Oh well I was prepared none the less...
I just realized I didn't reset the usb debugging/dev options, which is why the fastboot isn't working damnit lol...
EDIT----got fastboot working, just can't get the recovery to work. I press up then down, blue light flashes then phone boots to home screen, not recovery.
EDIT---- apparently the key sequence is hold up then press down but keep holding up? can anyone confirm this for me?
Final EDIT-----GOT IT ALL WORKING.... thanks for the help everyone...
Welcome.
Hello,
I recently bricked my Z1 and just got it back from warranty repaired. It is a C6906 that they upgraded to 4.3 (.290) however it is branded to BELL and I wish to flash the unbranded generic so I don't have as much bloatware/fast updates.
Since I do not wish to brick the device again and go through this again and so I am looking for advice to do this in a way that is guaranteed. With flashtool if I flash "C6906 14.2.A.0.290 Generic CA 1276-7484_R2B" would I have any issues at all? Just load up Flashtool - select the ftf and just use the default settings and plug in the Z1 while holding down the volume button.
I used the latest Flashtool v0.9.13, connected to PC, let install windows the drivers, selected the Unbranded Stock ftf, wiped all data, appslog, cache, all the rest unchecked and I performed the flash. All fine and the phone working well. I don't know why you had problems or why you bricked the phone but there is no advice to give you because it's simply. So even if all it's clear no guarantee and it's up to you. I don't think is the FTF faulty.
eclyptos said:
I used the latest Flashtool v0.9.13, connected to PC, let install windows the drivers, selected the Unbranded Stock ftf, wiped all data, appslog, cache, all the rest unchecked and I performed the flash. All fine and the phone working well. I don't know why you had problems or why you bricked the phone but there is no advice to give you because it's simply. So even if all it's clear no guarantee and it's up to you. I don't think is the FTF faulty.
Click to expand...
Click to collapse
This is separate from how I bricked it (using custom rom), I did this previously with a older version and just not on .290 and I am wondering if there is any issues (IMEI etc) doing it .290 to .290, thats all. I just don't want to make a mistake.
magwart said:
This is separate from how I bricked it (using custom rom), I did this previously with a older version and just not on .290 and I am wondering if there is any issues (IMEI etc) doing it .290 to .290, thats all. I just don't want to make a mistake.
Click to expand...
Click to collapse
Ok, so you bricked the phone with custon rom, now I understand. In this case there is no any issues flashing .290 unbranded on .290 branded. IMEI is lost only when jumping .257 and downgrade directly to .534. It's more "safe" flash .290 on .290. Go flash now.
eclyptos said:
Ok, so you bricked the phone with custon rom, now I understand. In this case there is no any issues flashing .290 unbranded on .290 branded. IMEI is lost only when jumping .257 and downgrade directly to .534. It's more "safe" flash .290 on .290. Go flash now.
Click to expand...
Click to collapse
Thanks. I don't suppose there is any working root for 4.3 yet, is there for the C9606?
Edit: Successfully flashed. Thanks again.
magwart said:
Thanks. I don't suppose there is any working root for 4.3 yet, is there for the C9606?
Click to expand...
Click to collapse
No direct root, like Vroot or 360, for .290 at the moment, just a method to get full root for Locked Bootladers. To do that you have to downgrade, root, install recovery then update to .290 again, a bit longer to get root on your phone, sure this method working for C6902/3 but should work for C6906 too, just check.
Would I be able to go from 290 branded to the new 136 intended without issue? I already bricked one device trying to root and I'm just trying to make sure lol
akusokuzan said:
Would I be able to go from 290 branded to the new 136 intended without issue? I already bricked one device trying to root and I'm just trying to make sure lol
Click to expand...
Click to collapse
Probably because when you bricked your phone was the time when some issues was not discovered yet in do that, and this confirm the fact on the thread now is wrote "How not brick your phone" . BTW, the risk to brick the phone is in downgrading so if you want just to upgrade without Root this way should be more "safe" and you will be able to do it without any issue.
eclyptos said:
Probably because when you bricked your phone was the time when some issues was not discovered yet in do that, and this confirm the fact on the thread now is wrote "How not brick your phone" . BTW, the risk to brick the phone is in downgrading so if you want just to upgrade without Root this way should be more "safe" and you will be able to do it without any issue.
Click to expand...
Click to collapse
Lol yeah, when I was trying to update with root, it didn't go so hot. That thread wasn't stickied until after the debacle. Sounds good though, thanks!
My phone doesn't seem to receive any signal when flashing any firmwares othewr than .136
I was on the Monx rom for about 4 months but felt like restoring the phone back and trying something different. So I flashed a generic UK .534 firmware I had on my pc with flashtool as I still want root.. But once it was completed I received the fatal "Invalid Sim - No Service". I tried the original o2 sim in the phone which my Xperia used to be on before I unlocked it but still got the same error with no signal. I flashed it a few more times but it didn't make a difference. I thought it must have been something wrong with the ftf of the generic one so i downloaded the .257 generic uk ftf as you're able to root that too BUT same "invalid sim" popped up again. I tried restarting a few times, different sim cards and nothing works. I then found an o2 branded .136 on my computer which I must have made as a back up...I flashed it and it worked fine again with fulkl signalk and no invalid sim message. I thought maybe my handset will only work with o2 firmwares since only that ftf worked...i decided to download a .534 o2 ftf since as I mentioned i need root but same issue again!
I'm so frustrated since the ftf that root doesn't work on is fine. I have no idea why this issue is occurring
Sorry for the long read. Any help appreciated
that always happens
just flash any 534 FTF
root it
install the rom of your choice
it will be fine
gregbradley said:
that always happens
just flash any 534 FTF
root it
install the rom of your choice
it will be fine
Click to expand...
Click to collapse
Hi,
That's what I have been doing trying different .534 firmwares as mentioned but only .136 works
dreamville said:
Hi,
That's what I have been doing trying different .534 firmwares as mentioned but only .136 works
Click to expand...
Click to collapse
No, please follow what I said
flash a 534 FTF
root it
Then flash a pre rooted rom of your choice.
If choose to stay with 534 you will never get a signal.
Also remember that's a 4.2 version of android, we are now on 4.4
gregbradley said:
that always happens
just flash any 534 FTF
root it
install the rom of your choice
it will be fine
Click to expand...
Click to collapse
gregbradley said:
No, please follow what I said
flash a 534 FTF
root it
Then flash a pre rooted rom of your choice.
If choose to stay with 534 you will never get a signal.
Also remember that's a 4.2 version of android, we are now on 4.4
Click to expand...
Click to collapse
I love you :victory:
dreamville said:
I love you :victory:
Click to expand...
Click to collapse
no worries
I have rooted my Z1 many times without problem, first downgraded to .534, root with Bin4ry's root tool, then flash the .zip file from recovery and flash stripped .ftf with FlashTool.
By rooting this way I can keep my bootloader locked.
A couple of weeks ago I had to send my phone for repairs when the call speaker gave up and they changed the mainboard (new IMEI).
After this I can not downgrade to .534 anymore! It will stuck at a bootloop, with only the Sony logo showing. Downgrading to .257 (the version after .534) is no problem though.
I have tried many different .534 tft-files, including NUT's.
Any ideas? Could this new mainboard be incompatible with the oldest firmwares? Sounds unlikely to me.
Thanks!
dape16 said:
I have rooted my Z1 many times without problem, first downgraded to .534, root with Bin4ry's root tool, then flash the .zip file from recovery and flash stripped .ftf with FlashTool.
By rooting this way I can keep my bootloader locked.
A couple of weeks ago I had to send my phone for repairs when the call speaker gave up and they changed the mainboard (new IMEI).
After this I can not downgrade to .534 anymore! It will stuck at a bootloop, with only the Sony logo showing. Downgrading to .257 (the version after .534) is no problem though.
I have tried many different .534 tft-files, including NUT's.
Any ideas? Could this new mainboard be incompatible with the oldest firmwares? Sounds unlikely to me.
Thanks!
Click to expand...
Click to collapse
If it's incompatible with 534 then i'd be surprised, my guess is that it's a dodgy download and you should re-download the FTF file or an alternative and make sure it's the only thing that your computer is doing at the time, even check the MD5 checksum if it's available.
Are you flashing the full FTF file when downgrading and allowing for a wipe?
Only problem i've had when downgrading is losing the IMEI but after you've rooted , installed a custom recovery and installed a custom rom that'll come back anyway.
dladz said:
If it's incompatible with 534 then i'd be surprised, my guess is that it's a dodgy download and you should re-download the FTF file or an alternative and make sure it's the only thing that your computer is doing at the time, even check the MD5 checksum if it's available.
Are you flashing the full FTF file when downgrading and allowing for a wipe?
Only problem i've had when downgrading is losing the IMEI but after you've rooted , installed a custom recovery and installed a custom rom that'll come back anyway.
Click to expand...
Click to collapse
Thanks, yes I have tried with 5 different .534 ftf-files, all of them resulting in this bootloop. I am doing a full flash with wipe. Downgrading to .257 is working fine though, but then I cant root.
I am running out of ideas
dape16 said:
Thanks, yes I have tried with 5 different .534 ftf-files, all of them resulting in this bootloop. I am doing a full flash with wipe. Downgrading to .257 is working fine though, but then I cant root.
I am running out of ideas
Click to expand...
Click to collapse
Are you branded? What model is the phone C6903? C6902?
don't forget the obvious stones
dladz said:
Are you branded? What model is the phone C6903? C6902?
don't forget the obvious stones
Click to expand...
Click to collapse
It's not branded. No SIM-lock, Generic_NCB customization. C6903.
Now I have tried with older versions of FlashTool and I tried other USB-ports too, but no success. Newer firmwares then .534 flashes just fine.
dape16 said:
It's not branded. No SIM-lock, Generic_NCB customization. C6903.
Now I have tried with older versions of FlashTool and I tried other USB-ports too, but no success. Newer firmwares then .534 flashes just fine.
Click to expand...
Click to collapse
Which version of flashtool are you using currently? I've found that some firmwares just don't like the older flashtools.
What about different USB cables? Shouldn't make any difference but I thought I'd ask. I find it odd the way it'll work for newer but not older firmwares, perhaps someone else should chime in with an idea.
I'm all out, as this isn't something i've come across and everything i'd try myself i've told you.
dladz said:
Which version of flashtool are you using currently? I've found that some firmwares just don't like the older flashtools.
What about different USB cables? Shouldn't make any difference but I thought I'd ask. I find it odd the way it'll work for newer but not older firmwares, perhaps someone else should chime in with an idea.
I'm all out, as this isn't something i've come across and everything i'd try myself i've told you.
Click to expand...
Click to collapse
Thanks for your help.
Now I have tried with another computer and another USB-cable, and also tried to flash the older .526 and .518 firmwares. Tried FlashTool 0.9.1.6 and .5 and .4.
Same result.
Seems very strange that this new mainboard should not be compatible with these firmwares?
dape16 said:
Thanks for your help.
Now I have tried with another computer and another USB-cable, and also tried to flash the older .526 and .518 firmwares. Tried FlashTool 0.9.1.6 and .5 and .4.
Same result.
Seems very strange that this new mainboard should not be compatible with these firmwares?
Click to expand...
Click to collapse
It does seem strange and i'm pretty much out of ideas myself for you m8. Mad one that.
dladz said:
It does seem strange and i'm pretty much out of ideas myself for you m8. Mad one that.
Click to expand...
Click to collapse
Thanks anyway, I hope somebody else has an idea
dape16 said:
Thanks anyway, I hope somebody else has an idea
Click to expand...
Click to collapse
click thanks dude,
Hope you work it out
Just had a thought, can't you now root later firmwares?
dladz said:
click thanks dude,
Hope you work it out
Just had a thought, can't you now root later firmwares?
Click to expand...
Click to collapse
I dont think it is possible to root any firmware later then .534? Not without unlocking bootloader?
dape16 said:
I dont think it is possible to root any firmware later then .534? Not without unlocking bootloader?
Click to expand...
Click to collapse
yes it is, any 4.2 FW can be rooted
Its just that 534 can be done using [NUT]s installation of dual recovery
gregbradley said:
yes it is, any 4.2 FW can be rooted
Its just that 534 can be done using [NUT]s installation of dual recovery
Click to expand...
Click to collapse
Thanks, but I have tried both vroot and Bin4ry's root tool on .257. Didn't work. Is there any other method for rooting?
Edit: Sorry, didn't see the link in your signature, will try that.
dape16 said:
Thanks, but I have tried both vroot and Bin4ry's root tool on .257. Didn't work. Is there any other method for rooting?
Edit: Sorry, didn't see the link in your signature, will try that.
Click to expand...
Click to collapse
DO NOT USE VROOT!!!!
It send your IMEI number to an IP address in china..
I cant believe people still do not know this
gregbradley said:
DO NOT USE VROOT!!!!
It send your IMEI number to an IP address in china..
I cant believe people still do not know this
Click to expand...
Click to collapse
Well, I tried vroot because it is in the first posts in the "Ultimate Xperia Z1 Guide" sticky thread.
Since I have always used Bin4ry's tool, I guess I have not noticed any thread about vroot being dangerous.
gregbradley said:
yes it is, any 4.2 FW can be rooted
Its just that 534 can be done using [NUT]s installation of dual recovery
Click to expand...
Click to collapse
Right now I have .257 firmware flashed which is a 4.2.2.
I have tried to root with Bin4ry, vroot, Kingo, and [NUT]s recovery, but it is not possible.
Everywhere I look people say that it is a must to downgrade to .534 when rooting with a locked bootloader.
What have I missed?
Thanks,
257 was the first one that closed that exploit, you have to go back further.
I know you say 534 does not flash for you, but what error does flashtool give?
gregbradley said:
257 was the first one that closed that exploit, you have to go back further.
I know you say 534 does not flash for you, but what error does flashtool give?
Click to expand...
Click to collapse
Thank you, I misunderstood an thought .257 was rootable too.
No error in Flashtool, flashes fine but is stuck on bootloop with Sony logo.
Tried .518, .526 and .534
make sure you do not exclude any part of the FTF and wipe everything,
Can you get a log from the phone?
Make sure you backup and clean your sdcard (So there is no trace of recovery files on there)
gregbradley said:
make sure you do not exclude any part of the FTF and wipe everything,
Can you get a log from the phone?
Make sure you backup and clean your sdcard (So there is no trace of recovery files on there)
Click to expand...
Click to collapse
I have cleaned the internal sdcard and tried without external sdcard and simcard.
Don't think it is possible to get a log file from the phone while in bootloop?
If my new mainboard is incompatible with .534 and older, I guess other users would have the same problem?