Related
Hi, i recently down grade my C6903 to 534 and successfully root (thx to XDA), when i try to update the 257 and it's gone. they change to 290 now and i dont want it since it will lose the right of root. Is there any method update to 257 beside flashtool?
if i use flashtool update to 257, will i still have my apps and personal stuff after update? because when i down grade to 534, flashtool wipe out everything in my phone even i make sure i didnt mark wipe out my stuff (and i didnt update at that moment):crying:. so i dont want to re-install my stuff again.
if i use flashtool update to 257, will the right of root still exist?
Please advice me how to get 257 update with most less effort (as long as i can keep my apps and personal stuff).
Anyone can help?
Sent from my C6903 using xda app-developers app
anyone can help ??
will527 said:
anyone can help ??
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2505796
Flashing won't delete your data. Make sure you've unticked data and app wipe in Flashtool before flashing. Always make a backup in case though!!
TagEHeuer said:
http://forum.xda-developers.com/showthread.php?t=2505796
Flashing won't delete your data. Make sure you've unticked data and app wipe in Flashtool before flashing. Always make a backup in case though!!
Click to expand...
Click to collapse
That won't work in his case, he already flashed and rooted 534 but he is getting OTA to 290 and not 257.
Only thing you can try is to flash 290 through OTA.
If you flash 257 without wiping data via Flashtool you'll preserve your data but lose root.
290 OTA probably won't keep your root but that's the only thing you can try...or to flash ROM from XDA
Sent from my Z1
If your phone's bootloader is unlock-able, then you can back TA partition, unlock bootloader, install recovery, flash Supersu.zip, flash kernel from FTF (Don't wipe anything, exclude everything but kernel), then restore TA partition from your backup.
This way you will have a fully rooted Xperia Z1 Android 4.2 14.1.G.2.257
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!
My phone has OS 290 need to downgrade to 257 to root but the file doesn't show up in flashtool i downgraded to 534 before but lost IMEI so went back to 290
Follow NUT's thread in Android Development section in order to root your Z1.
Sent from my C6903 using XDA Premium 4 mobile app
ryanraven said:
My phone has OS 290 need to downgrade to 257 to root but the file doesn't show up in flashtool i downgraded to 534 before but lost IMEI so went back to 290
Click to expand...
Click to collapse
Even I am facing this issue. The flashtool does not seem to recognize .257 at all. Not sure on the reason.
Gurus - Any idea on why the flash tool is not recognizing .257?
@livelyyoungman, @ryanraven Use the FTF .534 provided by NUT to avoid IMEI lost, then follow the instructions to upgrade to .290. Read carefully the thread.
Even I had lost the IMEI when I flashed wrong firmwares 534 rom.
you need to flash .534 based on your firmware c6902 or c6903 or whatever it is. Root your phone and then use nut tutorial to upgrade and keep the root.
Losing IMEI is not even a problem at all because when you will update to .290 or .136 it will be back so do not be worry about it.
matharuajay said:
Even I had lost the IMEI when I flashed wrong firmwares 534 rom.
you need to flash .534 based on your firmware c6902 or c6903 or whatever it is. Root your phone and then use nut tutorial to upgrade and keep the root.
Click to expand...
Click to collapse
I flashed the correct firmware. The one I used was C6902_14.1.G.1.534_Generic IN firmware that I downloaded from the link provided in this forum (MEGA link). Excluded "Baseband" as well. Still IMEI went missing
eclyptos said:
Losing IMEI is not even a problem at all because when you will update to .290 or .136 it will be back so do not be worry about it.
Click to expand...
Click to collapse
I was not worried on this, as I did read about the issues on downgrading and was fully aware that by flashing to the latest version I would be getting back the IMEI.
Now I have successfully downgraded to .534 as well - just flashed first the global .257 and then the generic IN version of .534. All is well now. Was able to root the phone as well. But now I am facing camera issues; may be a visit to the service center is what seems looming @ large.:crying:
livelyyoungman said:
But now I am facing camera issues; may be a visit to the service center is what seems looming @ large.:crying:
Click to expand...
Click to collapse
If you unlocked bootlader then with .534 or .257 the camera not working, update to .290 or .136 and your camera will be back again.
eclyptos said:
If you unlocked bootlader then with .534 or .257 the camera not working, update to .290 or .136 and your camera will be back again.
Click to expand...
Click to collapse
No I have not yet unlocked the BL. But I find the following issues when using the camera:
1. "Camera Not Available" message appears sometimes. It does disappear but upon taking photos after this message a BLUE hue is visible at the bottom of all the pictures I shoot. Only a reset restores the camera function properly.
2. The phone keeps rebooting at least once every day.
I was reading few of the other posts and find that these two could be related to HW malfunction. Hence wanted to visit the service center to figure out the process for replacing the phone. I have already visited the service guys early last week for these two issues. They flashed my mobile once again and returned back to me for checking. :crying:
A factry reset in needed after update. If you are not on latest FW then update.
eclyptos said:
A factry reset in needed after update. If you are not on latest FW then update.
Click to expand...
Click to collapse
Yes did that as well. But still it does re-appear. So just wanted to confirm if there is really any hardware issue with my piece.
livelyyoungman said:
Yes did that as well. But still it does re-appear. So just wanted to confirm if there is really any hardware issue with my piece.
Click to expand...
Click to collapse
Then something wrong. Call Sony to understand if you should sent it back.
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?