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?
Related
This is for my curiosity and many other users who I know are wondering the same thing, I've searched for this, but can't really find anything that answers it to my satisfaction.
So I'm running 4.3, with build number .290
I want to root my phone, but I know I need to flash .534 back to my phone. As far as I know, THIS will stop my sim being recognised by the phone. Do I then need to ROOT the phone, and then flash .290 again for the sim to work again.
So which .290 flash will I use? Just the normal FTF file for .290?
Thank you, I'm an active contributor to the forum, but I like to be super sure about what I'm doing before I do it, and I gather many other users do. The reason I'm asking in such detail is because my phone was rooted before, I updated (by mistake) to 4.3 and then flashed back to .290 where it stopped my sim working. Took me a few hours to work out how to fix it, as the pccompanion wasn't working for me!
Thank you!
TagEHeuer said:
This is for my curiosity and many other users who I know are wondering the same thing, I've searched for this, but can't really find anything that answers it to my satisfaction.
So I'm running 4.3, with build number .290
I want to root my phone, but I know I need to flash .534 back to my phone. As far as I know, THIS will stop my sim being recognised by the phone. Do I then need to ROOT the phone, and then flash .290 again for the sim to work again.
So which .290 flash will I use? Just the normal FTF file for .290?
Thank you, I'm an active contributor to the forum, but I like to be super sure about what I'm doing before I do it, and I gather many other users do. The reason I'm asking in such detail is because my phone was rooted before, I updated (by mistake) to 4.3 and then flashed back to .290 where it stopped my sim working. Took me a few hours to work out how to fix it, as the pccompanion wasn't working for me!
Thank you!
Click to expand...
Click to collapse
why don't you unlock your 4.3 rom and flash a recovery to root it ? would be easier
AntiDroid said:
why don't you unlock your 4.3 rom and flash a recovery to root it ? would be easier
Click to expand...
Click to collapse
Not really used to that, new to all this. A guide somewhere?
Look here,
http://forum.xda-developers.com/showthread.php?p=48902196
sent from a Rooted & Unlocked Xperia Z1
TagEHeuer said:
Not really used to that, new to all this. A guide somewhere?
Click to expand...
Click to collapse
If you want to flash the firmware you have, follow this guide from part B to part C, then you will have a ftf copy of your current firmware.
About the root thing, downgrade to .257 then .534 so you don't have the IMEI and signal issues. Then root and OTA to .257 and then, if you get OTA update to .290 go for it, but some people said that you will only get partial root access.
So you will have to either flash a prerooted firmware or unlock bootloader and turn off Sony's RIC and then root the normal way.
To unlock bootloader, just follow the instructions here but don't forget to backup the TA partition using this guide.
Regards,
~J2C
Hi i would like to downgrade back to. 257 so i can gain root again. I was on honami rom. 257 and then updated to. 290 via update through TWRP recovery. Now, do i just wipe and flash. 534 ftf file and then root and then update to. 257 ota?
Any help will be appreciated as im not sure how to do it.
Regards
Yes, that should do it.
Regards,
~J2C
Just2Cause said:
Yes, that should do it.
Regards,
~J2C
Click to expand...
Click to collapse
I flashed 534 file and ive no sim detection? what do i do now?
dawudbhai said:
I flashed 534 file and ive no sim detection? what do i do now?
Click to expand...
Click to collapse
Flash 290, then 257, then 534. Root, then OTA to 257.
Just2Cause said:
Flash 290, then 257, then 534. Root, then OTA to 257.
Click to expand...
Click to collapse
Hi ive tried all these steps.. Its like its locked to work on 4.3 only. Anything lower the signal dont work im screwed lol.
Have you tried this method yourself mate?
Regards
dawudbhai said:
Hi ive tried all these steps.. Its like its locked to work on 4.3 only. Anything lower the signal dont work im screwed lol.
Have you tried this method yourself mate?
Regards
Click to expand...
Click to collapse
Your phone can be Simlocked to a network, but it cannot be locked to 4.3 rom only,
Flash the correct Country/Network FTF .534 version, using Flashtool Latest version 0.9.13.0
http://forum.xda-developers.com/showthread.php?t=2469191
http://www.flashtool.net/download.php
then Root using VRoot app, then install SuperSU from Playstore, (I've got the paid version so I can enable OTA Survival mode to maintain root)
then OTA Update to .257, you should than have a rooted .257 rom.
regards
dawudbhai said:
Hi ive tried all these steps.. Its like its locked to work on 4.3 only. Anything lower the signal dont work im screwed lol.
Have you tried this method yourself mate?
Regards
Click to expand...
Click to collapse
Yes, I have used that method when I lost my IMEI and SIM signal.
Just2Cause said:
Yes, I have used that method when I lost my IMEI and SIM signal.
Click to expand...
Click to collapse
Ok ive downloaded a new 534 rom central europe version so will try that as I had a different version from somewhere not on the ftf section pages.
So do i just flash and full wipe on 534? I dont exclude anything like baseband, kernel etc?
Regards.
dawudbhai said:
Ok ive downloaded a new 534 rom central europe version so will try that as I had a different version from somewhere not on the ftf section pages.
So do i just flash and full wipe on 534? I dont exclude anything like baseband, kernel etc?
Regards.
Click to expand...
Click to collapse
I have tried again and still there is no signal or imei? I dont know what im doing wrong?
dawudbhai said:
I have tried again and still there is no signal or imei? I dont know what im doing wrong?
Click to expand...
Click to collapse
Flash back to 290 (Android 4.3), then flash the 257 (Android 4.2 → not rootable), then flash the 534 (Android 4.2 → rootable), root and OTA to 257.
Regards,
~J2C
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!
Hi all.
Have run into a bit of trouble.
Tried to flash PAC Man rom (Unlocked bootloader, running rooted stock 4.4.2).
I did as instructions stated, went to flash ZIPS (including pac_honami-nightly-20140330.zip) from external SD card using TWRP, after wiping everything (except my external SD card).
Received an Error message stating 'Failed', in red. Something about system.
I did a reboot, now stuck on Sony logo and cannot access CWM or TWRP.
Would really appreciate any help. Arrrgh!
Thanks kindly.
--
EDIT: I assume I can flash another firmware using flashtool. Can I just re-flash NUT's rooted .681 firmware?
groperfish said:
Hi all.
EDIT: I assume I can flash another firmware using flashtool. Can I just re-flash NUT's rooted .681 firmware?
Click to expand...
Click to collapse
You can flash a stock firmware with flashtool and start over
groperfish said:
I did as instructions stated, went to flash ZIPS (including pac_honami-nightly-20140330.zip) from external SD card using TWRP, after wiping everything (except my external SD card).
Click to expand...
Click to collapse
Did you install the right kernel?
XperienceD said:
Did you install the right kernel?
Click to expand...
Click to collapse
Here I am showing my ignorance. I followed the instructions here (http://forum.xda-developers.com/showthread.php?t=2478003).
I assume the nightly .Zip I (tried) to flash was the kernel...(pac_honami-nightly-20140330.zip)?
The kernel should already be in the .zip so i don't think its a problem with the kernel. Just to make sure, check if there's a boot.img in the .zip file and are you on a c6902?
Ahki767 said:
The kernel should already be in the .zip so i don't think its a problem with the kernel. Just to make sure, check if there's a boot.img in the .zip file and are you on a c6902?
Click to expand...
Click to collapse
Thanks Ahki. There's a boot.img in the zip file and I am on a C6903.
Have managed to flash .534 ftf, now I need to get back my IMEI (I did backup TA previously).
Thanks for your help. Wish me luck!
EDIT: any tutorials on how to restore TA? I can't find anything. Head is swirling. :-|
groperfish said:
Thanks Ahki. There's a boot.img in the zip file and I am on a C6903.
Have managed to flash .534 ftf, now I need to get back my IMEI (I did backup TA previously).
Thanks for your help. Wish me luck!
Click to expand...
Click to collapse
Good luck man :good:
If you need anymore help, just ask
Ahki767 said:
The kernel should already be in the .zip so i don't think its a problem with the kernel.
Click to expand...
Click to collapse
If it's not flashed the kernel then it will be so would install it using fastboot to be sure.
XperienceD said:
If it's not flashed the kernel then it will be so would install it using fastboot to be sure.
Click to expand...
Click to collapse
Hi guys. Sorry for the likely inane questions.
Is there anyway to get my IMEI back without reverting to .534 root, then getting to .290 root? I cannot download the .534 NUT firmware in time (it says it will be 3 weeks to download the torrent and I really can't wait that long...)
Can I just install a pre-rooted .290 firmware, given that my bootloader is unlocked?
groperfish said:
Hi guys. Sorry for the likely inane questions.
Is there anyway to get my IMEI back without reverting to .534 root, then getting to .290 root? I cannot download the .534 NUT firmware in time (it says it will be 3 weeks to download the torrent and I really can't wait that long...)
Can I just install a pre-rooted .290 firmware, given that my bootloader is unlocked?
Click to expand...
Click to collapse
If I remember correctly, I think you have to downgrade to .534 to get IMEI back or to the previous version before you flashed the pac rom. Download the stocks ftf from here instead of nuts
Ahki767 said:
If I remember correctly, I think you have to downgrade to .534 to get IMEI back or to the previous version before you flashed the pac rom. Download the stocks ftf from here instead of nuts
Click to expand...
Click to collapse
I did flash (after PAC's went awry) to .534, stock. That was when the IMEI was lost.
I did read somewhere that a locally branded firmware might get back IMEI.. Giving a .237 Netherlands firmware a try....
I hope I haven't bricked this phone...
EDIT: worked. IMEI back after flashing local firmware.
Man that was stressful!
Thank you for help guys. Really appreciated.
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