Related
Hey,
in latest firmware there is a update to S1Boot (to Version R10A21). I think most users who DONT USE PCC/SEUS will not have the update because Flashtool does not decrypt it correctly.
I packed it up into German Firmware, so if you are interested you can flash this Firmware and then just reflash ANY OTHER Firmware if you dont want to stay on German one. After S1Boot got updated it will stay updated no matter what Firmware you flash afterwards, becasue normally it is not included.
File can be downloaded here from my Firmware collection, directlink to Xperia T folder:
http://ul.to/f/2fvm79
Regards
Thanks for that. Do you know what's changed?
I just checked my version and it s R10A118
Sent from my Xperia T using XDA Premium
This is a small appreciation for all the effort you put in XPERIA devices.
Thank you Andreas,
Confirmation Number: 30X20729LD1118121
PS: I have some FTFs if you want me to upload them.
Check it out: http://forum.android.com.pl/f664/oprogramowanie-dla-sony-xperiaa-t-228936/
made by me
and here:
http://forum.android.com.pl/f664/oprogramowanie-dla-sony-xperiaa-tl-231457/
http://forum.android.com.pl/f664/oprogramowanie-dla-sony-xperiaa-tx-231469/
made by me
and this:
http://forum.android.com.pl/f562/oprogramowanie-dla-sony-xperiaa-s-231330/
http://forum.android.com.pl/f562/oprogramowanie-dla-sony-xperiaa-sl-226461/
made by me
http://forum.android.com.pl/f308/oprogramowanie-dla-sony-ericsson-xperiaa-arc-s-147007/
made by me
Hi Binary, Can I confirm that I can backup my current stock rom (7.0.A.3.195) using CWM recovery (advanced kernel v4), then flash this for S1 update, then (correct me if I am wrong please!) re-flash kernel and then restore rom via CWM: resulting in being back to my current rom but with S1 Boot update.
Also just check that I should use "Generic DE (S1Boot-Update).ftf" - is this the one you refer to in the OP.?
Thanks for your patience
I updated via PCCompanion and my boot is
R10A118
WHich "latest" version did you get the new boot from? And what is new in it?
Mine is R10A121 and it was flashed with Flashtool.
ludwikjonkisz said:
Check it out: http://forum.android.com.pl/f664/oprogramowanie-dla-sony-xperiaa-t-228936/
made by me
and here:
http://forum.android.com.pl/f664/oprogramowanie-dla-sony-xperiaa-tl-231457/
http://forum.android.com.pl/f664/oprogramowanie-dla-sony-xperiaa-tx-231469/
made by me
and this:
http://forum.android.com.pl/f562/oprogramowanie-dla-sony-xperiaa-s-231330/
http://forum.android.com.pl/f562/oprogramowanie-dla-sony-xperiaa-sl-226461/
made by me
http://forum.android.com.pl/f308/oprogramowanie-dla-sony-ericsson-xperiaa-arc-s-147007/
made by me
Click to expand...
Click to collapse
You included S1Boot Update too ?
[email protected] said:
Hi Binary, Can I confirm that I can backup my current stock rom (7.0.A.3.195) using CWM recovery (advanced kernel v4), then flash this for S1 update, then (correct me if I am wrong please!) re-flash kernel and then restore rom via CWM: resulting in being back to my current rom but with S1 Boot update.
Also just check that I should use "Generic DE (S1Boot-Update).ftf" - is this the one you refer to in the OP.?
Thanks for your patience
Click to expand...
Click to collapse
Yep should work
gregbradley said:
I updated via PCCompanion and my boot is
R10A118
WHich "latest" version did you get the new boot from? And what is new in it?
Click to expand...
Click to collapse
It is included inside the SEUS files for the 195 Version, but "problem" is that we need to update Flashtool so that it decrypts the File correctly. For now we only added the "alternate" decryption for Loader, now S1Boot seems to be updated too Which is quite good, maybe they add features in future like button for recovery
smardu said:
Mine is R10A121 and it was flashed with Flashtool.
Click to expand...
Click to collapse
Cool :good:
Regards
Seansmit17 said:
Thanks for that. Do you know what's changed?
I just checked my version and it s R10A118
Sent from my Xperia T using XDA Premium
Click to expand...
Click to collapse
Really no idea
Halim2k said:
This is a small appreciation for all the effort you put in XPERIA devices.
Thank you Andreas,
Confirmation Number: 30X20729LD1118121
PS: I have some FTFs if you want me to upload them.
Click to expand...
Click to collapse
Many many many many thanks Sure i would upload yours too if you like, but somehow i have to get them
Regards
Bin4ry said:
It is included inside the SEUS files for the 195 Version, but "problem" is that we need to update Flashtool so that it decrypts the File correctly.
Click to expand...
Click to collapse
Stage, I flagged 195 via official method not flash tool, so why did I not have the update?
now S1Boot seems to be updated too Which is quite good, maybe they add features in future like button for recovery
Regards
Click to expand...
Click to collapse
That's fantastic, really miss the option to reboot or reboot into recovery
Sent from my LT30p using xda premium
gregbradley said:
Stage, I flagged 195 via official method not flash tool, so why did I not have the update?
That's fantastic, really miss the option to reboot or reboot into recovery
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
If you got it from PCC i dont know why you did not get it. Hope you did not understood me wrong. It is NOT implemented yet. I just hope that they WILL update is later on, with this possibility to update the S1Boot it would be possible from technical way
Regards
Bin4ry said:
If you got it from PCC i dont know why you did not get it. Hope you did not understood me wrong. It is NOT implemented yet. I just hope that they WILL update is later on, with this possibility to update the S1Boot it would be possible from technical way
Regards
Click to expand...
Click to collapse
Yes, I understand that, Can you check this firmware. Its the .ftf I made from my PCCompanion update. I dont know where to look to check the boot.
But i do get an update when i connect to pccompanion, allthough it gives me the same FW number, i thought that was strange but maybe its the new boot.
gregbradley said:
Yes, I understand that, Can you check this firmware. Its the .ftf I made from my PCCompanion update. I dont know where to look to check the boot.
But i do get an update when i connect to pccompanion, allthough it gives me the same FW number, i thought that was strange but maybe its the new boot.
Click to expand...
Click to collapse
Do your PCC Files are 3 or 4 Files? If your firmware includes the S1Boot update then it should be 4 Files!!
IT CAN BE that the branding firmwares does NOT include the S1Boot update, maybe that is the reason
Regards
Bin4ry said:
Do your PCC Files are 3 or 4 Files? If your firmware includes the S1Boot update then it should be 4 Files!!
IT CAN BE that the branding firmwares does NOT include the S1Boot update, maybe that is the reason
Regards
Click to expand...
Click to collapse
ok, I only used 3 largest files. The rest were all really small files. I will download again and make a new branded one...that way we will know if branded versions have the new boot.
I will get too it after I have eaten.
EDIT
Weird,
PCCompanion says my current version is 7.0.A.1.303, whilst my phone says I am on 7.0.A.3.195....lets see what happens
EDIT
Looks like i am getting 4 files, 3 downloaded already and still the big one to go....
gregbradley said:
ok, I only used 3 largest files. The rest were all really small files. I will download again and make a new branded one...that way we will know if branded versions have the new boot.
I will get too it after I have eaten.
EDIT
Weird,
PCCompanion says my current version is 7.0.A.1.303, whilst my phone says I am on 7.0.A.3.195....lets see what happens
Click to expand...
Click to collapse
Hehe.
The S1Boot is a FILE_XXXXXXX file with approx 330kb. But as i said Flashtool cannot decrypt now, it needs manual decryption.
Regards
Bin4ry said:
Hehe.
The S1Boot is a FILE_XXXXXXX file with approx 330kb. But as i said Flashtool cannot decrypt now, it needs manual decryption.
Regards
Click to expand...
Click to collapse
Check my second edit above, i do get that file now.
But guess what, (Like a noob) i forgot i cant use pccompanion anymore because of unlocked bootloader..D'oh
Anyway, any chance of instructions on how to manually decrypt it (Probably nothing simple) or if I send you the files can you incoorporate them into my .ftf so I can flash it?
I canthen also add a branded vodafobe version with the new boot to the ftf list.
Cheers
I need help to find out whish version S1Boot my lt30p has.
I tried to find the postet version numbers in the phone settings, I searched google, I installed SEUS .........
Nothing, I have no idea where you have the version numbers from.
harowa said:
I need help to find out whish version S1Boot my lt30p has.
I tried to find the postet version numbers in the phone settings, I searched google, I installed SEUS .........
Nothing, I have no idea where you have the version numbers from.
Click to expand...
Click to collapse
goto your dial pad and dial
*#*#7378423#*#*
then goto
service info>software info>
S1 Boot version is the third line down
OK, tutorial for those who want to update to the latest S1 boot.
You can check your s1 boot version by doing this
goto your dial pad and dial
*#*#7378423#*#*
then goto
service info>software info>
S1 Boot version is the third line down
Click to expand...
Click to collapse
Difficulty
Easy
Time taken
I did it in less than 10 minutes
1. Download one of the .ftf's from the OP that have the s1 boot update in title.
2. make a backup of your current rom
3. Download, install and set up flashtool. (Link in the all in one thread)
4. Drag and drop the .ftf into the open window of flashtool.
5. Tick all the boxes that say exclude except the one that says exclude uncategorized Check the attached image
6. Flash the .ftf following flashtool instructions
7. Reboot phone and check your s1 boot version, it should now be updated
8. Reboot into recovery and restore your backup.
9. You are now on the latest s1 boot with the same rom you had before.
EDIT
Alternative Method.
Flash this LT30_7.0.A.3.195_Generic DE (S1Boot-ONLY).ftf - 725.46 KB
(N.B. It is reported to relock your bootloader, just unlock it again if thats the case, info taken from this post)
I just removed all the unnecassary files from one of the .ftf's provided by Bin4ry
gregbradley said:
goto your dial pad and dial
#*#*7378423#*#*
then goto
service info>software info>
S1 Boot version is the third line down
Click to expand...
Click to collapse
*#*#7378423#*#*
is what you mean.
Here it is. Got my buddies c6606 us T-Mobile. Rooted fine, recovery went fine, but rom flash boot loops. And the best part is I cant get into recovery. So im stuck with fastboot, which gives me the same errors everytime, or flashmode with flashtool which I can put 100 fw's in the firmware folder and only a.1.253 shows up. Really need a.2.66 or 166 but I download them , place them in firmware folder with others and they're not there. My S3 is a dream compared to this. Takes me back to my HTC days! Anyway, I know its something small, its on .253 with some random rom asking for .66 or .67. Please, I'll pay. This is tying up my J-Tag repairs and other devices. Please, someone. I'll try whatever.
P.S. locked bootloader, apparently not unlockable.
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.
DrKrFfXx said:
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.[/QUOTE
Can I get that from that PC Companion that installed with this device?
Click to expand...
Click to collapse
jtford said:
DrKrFfXx said:
Just flash to stock with Sony Update Service. And try again.
It is pretty hard to wreck a locked bootleader device.[/QUOTE
Can I get that from that PC Companion that installed with this device?
Click to expand...
Click to collapse
I think it works the same, the tool got renamed after Sony dropped the Ericcsson last name.
Click to expand...
Click to collapse
DrKrFfXx said:
jtford said:
I think it works the same, the tool got renamed after Sony dropped the Ericcsson last name.
Click to expand...
Click to collapse
Just tried it and thought it was going to go but then gave an error saying "no software for this device". It says I need the fw x.xx.x.166 but I haven't been able to find the download for it. I hate little crap that kicks my but. If I could just get a recovery on it or a boot.img to flash I feel i'd be in the clear. I know its something small.
Click to expand...
Click to collapse
jtford said:
DrKrFfXx said:
Just tried it and thought it was going to go but then gave an error saying "no software for this device". It says I need the fw x.xx.x.166 but I haven't been able to find the download for it. I hate little crap that kicks my but. If I could just get a recovery on it or a boot.img to flash I feel i'd be in the clear. I know its something small.
Click to expand...
Click to collapse
I knew it would be something small. Just Googled Official Sony Xperia Firmware and took me to a site with all the firmware (stock) you could ever need. It actually showed up in flashtool after moving to firmware folder and vioala! Rerooted, flashed recovery, flashed new Xistenz (I think that's how its spelled) and its running like a champ. Customer (my buddy) is happy. PM me if your ever in the same boat and ill help you through it. This was my first Sony device to do and it was a good learning experience. Adding it to my repertoire!
Click to expand...
Click to collapse
jtford said:
jtford said:
I knew it would be something small. Just Googled Official Sony Xperia Firmware and took me to a site with all the firmware (stock) you could ever need. It actually showed up in flashtool after moving to firmware folder and vioala! Rerooted, flashed recovery, flashed new Xistenz (I think that's how its spelled) and its running like a champ. Customer (my buddy) is happy. PM me if your ever in the same boat and ill help you through it. This was my first Sony device to do and it was a good learning experience. Adding it to my repertoire!
Click to expand...
Click to collapse
Weird. SUS or Companion should provide you with the latest stock firm without having the need to look for it.
Glad you could solve it. Xperia family has some great tools to toy around.
Click to expand...
Click to collapse
DrKrFfXx said:
jtford said:
Weird. SUS or Companion should provide you with the latest stock firm without having the need to look for it.
Glad you could solve it. Xperia family has some great tools to toy around.
Click to expand...
Click to collapse
Thanks. I was suprised with the errors using SUS. The device has a lot more potential to be exploited I think.
Click to expand...
Click to collapse
Sorry i got a message to you too late.
one thing: if you flashed over a different firmware, like for a 6603 or 6602 the sony software often says there is no update for your device because it sees it as a different phone.
The firmwares that you are placing in the /firmware folder are. Ftf files, and around 700mb? You can find firmware for download that comes in a different format, but flashtool wont see them.
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
tinodevoe said:
Hi folks, I have an Xperia Z and its still stuck at 4.1.2
It's a prototype model, I've used the phone now for months and its been working great despite the lack of updates but I'm hoping it can have the latest software like the rest of the phones out there.
The bottom of the phone has C6606 written on it but the image on the screen shows C6616. Any suggestions would be appreciated.
Click to expand...
Click to collapse
can you take a screenshot of the 6616 screen? and can you go to the firmware by customization thread and follow the instructions? what is your cust.# ?
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
I think you can flash c6606 Software without problems... Maybe even of C6603 via Flashtool.
tinodevoe said:
Thanks for the reply. l've PM'd you a link to the screen shot since I can't post any links on the forum yet. I'll check out the customization thread.
Click to expand...
Click to collapse
OK, that is really very strange. You could try to contact DoomLord or Apollo89, they have knowledge of such things.
Are you rooted? Can you do a CWM Backup? I suggest having a full backup before flashing another rom. So in case you need it, you can flash it back.
I am not sure if you have the same kernel as the rest of us. If you can not do a CWM backup, and are not rooted, you need to find a way to extract the file "boot.img" from the phone. This is the kernel, which you can easily flash back. But for this operation, a bootloader unlock will most probably be necessary.
If you can get no help from Doom or Apollo and can not extract boot.img, you might need to flash hoping for luck, or stay on the firmware you have.
Disclaimer: I might be much too paranoid, after all your phone seems to have the same hardware as the normal one, and a flash of a 10.4.B.0.569 ROM should be no problem. I just don't want to be the one that did not warn you and be responsable for a broken phone...
===============================================================
EDIT: Just had a look at the thread, C6616 is bell Canada, if you had found that, you could have reported back and told us that you solved the problem.
===============================================================
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
tinodevoe said:
thanks for the advice. I still haven't tried anything with the phone. I've unlocked and flashed the firmware on my old Galaxy Nexus which for some reason also never updated (bought directly from Bell) but this one trying to read through all the information I'm having some trouble deciding on which method to use and where to really start.
If someone has a simple tutorial on flashing these phones please do share, otherwise I might just leave it as is and by the latest Nexus when this phone's done.
Click to expand...
Click to collapse
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
N1k0la89 said:
Here is the link where its all explained http://forum.xda-developers.com/showthread.php?t=2275632
Also there is this video http://www.youtube.com/watch?v=j8EQmufr0lw
You need to download latest flashtool and latest firmware FTF for your model and follow instructions, really not hard, hardest part is to w8 untill all that downloads from internet
Click to expand...
Click to collapse
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
tinodevoe said:
sorry to sound dumb, but I can't figure out which firmware to select for my phone. Can someone please recommend a link for the correct file to flash this with? Also does it matter which generic firmware I use? I don't want to get the Bell firmware and end up with all the bloatware they have on there. I'd prefer as close to a clean firmware as possible so I can start getting the latest updates onto this phone.
Click to expand...
Click to collapse
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
akisg said:
I think all Generic firmwares have the same "bloatware" app in common and all carrier branded firmwares have their carrier specific apps, so just choose a generic firmware and then remove all unuseful bloatware apps (if you go root).
Click to expand...
Click to collapse
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
tinodevoe said:
I finally just tried one method, following the guide here; http://forum.xda-developers.com/showthread.php?t=2240614
I installed flashtool and installed the stock Bell software, http://forum.xda-developers.com/showthread.php?t=2390178
It looked like everything went fine and when checking system updates it showed 4.3 was finally available!
but then after it downloaded the file I tried to install and it just gave me an error message :crying:
So what would be the next step for me?
Click to expand...
Click to collapse
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
akisg said:
Any info about that error??
Why not flash to 4.3 directly with flashtool or to 4.2 and then upgrade to 4.3?
Also try a fresh install by wiping data (if you have already a backup of them of course) it maybe helps..
Click to expand...
Click to collapse
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
tinodevoe said:
I've tried a couple times now to update that system update, its 10.4.B.0.569, once it starts to install it goes to the robot install logo at the startup for a second then starts the phone right away without doing the full install. The message on screen is simply "could not install".
i'll try a factory reset then directly to 4.3. I'm assuming I can use the same method as before or do I need to look into rooting the phone now?
Click to expand...
Click to collapse
As soon you are installing a stock rom, you don't have to worry about root.
But if you wanna root, your only choice is to flash a 4.2 rom, root it with a method of your choice and then upgrade to a prerooted 4.3.
Can someone please point me in the right direction to a FW that works with my phone? the only one that I seem to be able to use with flashtool is this one here which is 4.1.2. http://forum.xda-developers.com/showthread.php?t=2390178
however it won't let me update the system!
I'm guessing that I need a C6616 firmware to make this work, but I also tried this one, http://forum.xda-developers.com/showthread.php?t=2612159 and I get an error in flashtools, in red writing 'ERROR - error flashing. Aborted'.
I've been searching on here and all the other firmwares are 6603 which I tried a couple and again errors in flashtools.
trying again with that 4.1.2 its flashing it but its not the firmware I need!
ok, finally got one of them to work! I'm not sure what it was but I downloaded a bunch of firmwares until one of them finally updated me to 4.3.
thanks for all the help!
I didnt backup before flashing, and now have false firmware, no sim signal, no wifi, battery heats as hell, and so on and so on...
I opened my Sony Xperia T LT30p- and found the original customization number and all that.
Its: "1266-6442 LT30p/Mobile Phone/Telekom.de DE (Germany)/Black"
So if anyone can help me to post here or a clue to find that firmware, he would be the God for me !
so please HELP..
Stock firmware can be found here:
http://forum.xda-developers.com/showthread.php?t=2648320
[FTF] STOCK FIRMWARES for Xperia T,TL,V,TX
Sent from my LT30p using XDA Free mobile app
Mad Marty said:
Stock firmware can be found here:
http://forum.xda-developers.com/showthread.php?t=2648320
[FTF] STOCK FIRMWARES for Xperia T,TL,V,TX
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
Yeah thanks dude But my original firmware is not there :/
And i figured out, i cant flash any previos firmware versions, just the 4.3.
When i boot, the sony and xperia logo comes, and then that animation, and blocks there, and the phone restarts, and doing this all over again..
Just the 4.3, boots normal and all that, but i dont want that 4.3, want a previous version :/
bosnianboss9 said:
Yeah thanks dude But my original firmware is not there :/
And i figured out, i cant flash any previos firmware versions, just the 4.3.
When i boot, the sony and xperia logo comes, and then that animation, and blocks there, and the phone restarts, and doing this all over again..
Just the 4.3, boots normal and all that, but i dont want that 4.3, want a previous version :/
Click to expand...
Click to collapse
This is quite strange
1) Locked or unlocked bootloader?
2) Have you ever flashed a custom kernel?
3) Have you ever flashed a custom rom?
4) What's your original firmware customization number? EDIT: I've just seen that's 1266-6442... is this your ORIGINAL firmware? Where do you live? In Germany?
5) Rooted? CWM?
istux said:
This is quite strange
1) Locked or unlocked bootloader?
2) Have you ever flashed a custom kernel?
3) Have you ever flashed a custom rom?
4) What's your original firmware customization number? EDIT: I've just seen that's 1266-6442... is this your ORIGINAL firmware? Where do you live? In Germany?
5) Rooted? CWM?
Click to expand...
Click to collapse
I can have locked or unlocked, thats not the problem.
Custom kernel, roms, rooting CWM and so on, i never did that, just flashing with flashtool :S
and yeah 1266-6442 is the original customization number, and i live in belgium, but 20 minutes away from Germany.
bosnianboss9 said:
I can have locked or unlocked, thats not the problem.
Custom kernel, roms, rooting CWM and so on, i never did that, just flashing with flashtool :S
and yeah 1266-6442 is the original customization number, and i live in belgium, but 20 minutes away from Germany.
Click to expand...
Click to collapse
Ok, yes, I know how it works...
I just asked about the bootloader status, because sometimes some people mess with bootloader, kernel, flash from recovery, flash with Flashtool... and so on... WITHOUT the understanding of what they're doing... and come here complaining... do you know what I mean?
OK, now, I know how to help you.
1)
There's a method to download and install the original firmware directly from Sony.
But you need to be rooted. So, are you rooted?
2)
Your customization number is wrong.
1266-6442 doesn't exist.
That's maybe the number of your model, but it's not related with the firmware.
The right number for Telekom Germany is 1265-9144
The customization number is inside your software and can be found pressing *#*#7378423#*#*, inside Service info --> Sofware info --> Customization Version.
Give me that number please, so I can understand what's the software working now on you device.
3)
You said "I didnt backup before flashing, and now have false firmware, no sim signal, no wifi, battery heats as hell, and so on and so on.."
Ok, please, explain better what you did.
Have you flashed what kind of rom? Via recovery?
istux said:
Ok, yes, I know how it works...
I just asked about the bootloader status, because sometimes some people mess with bootloader, kernel, flash from recovery, flash with Flashtool... and so on... WITHOUT the understanding of what they're doing... and come here complaining... do you know what I mean?
OK, now, I know how to help you.
1)
There's a method to download and install the original firmware directly from Sony.
But you need to be rooted. So, are you rooted?
2)
Your customization number is wrong.
1266-6442 doesn't exist.
That's maybe the number of your model, but it's not related with the firmware.
The right number for Telekom Germany is 1265-9144
The customization number is inside your software and can be found pressing *#*#7378423#*#*, inside Service info --> Sofware info --> Customization Version.
Give me that number please, so I can understand what's the software working now on you device.
3)
You said "I didnt backup before flashing, and now have false firmware, no sim signal, no wifi, battery heats as hell, and so on and so on.."
Ok, please, explain better what you did.
Have you flashed what kind of rom? Via recovery?
Click to expand...
Click to collapse
Haha yeah i know what u mean, but thats not me
1) As i sad, i just did flashing firmware, whats easy, but rooting, roms, kernel and so on, i dont have a clue how to do this and WHAT it is at all :S
2)http://forum.xda-developers.com/showthread.php?t=2145364&page=4, here i saw it the 1266-6442 telekom germany DE, and i thought thats it, but u may be sure right.
And i currently have 1265-1620_R1J, flashed it yesterday just so, its CE Region i thing, 4.3 version, build .295.
3)Yeah, i first had the original Firmware on my phone, had the 4.2.2 version, and then the official software came for my phone and the T-Mobile provider i think.
And then, the 4.3 is just S**t, as i sad it, just problems, and i just want the previous version, because it worked perfect.
so i just was flashing all the other firmwares, especially the 4.3, from all the other regions, i thought maybe they will work better, but nope.
And when i try to flash previous versions/firmware, it just comes to the animation, after the sony and xperia logo, and restarts over and over again :/
And no, no roms, or recovery, i didnt do anything of all that, just flashing firmware with flashtool.
P.S. Thanks for trying to help me dude !
bosnianboss9 said:
Haha yeah i know what u mean, but thats not me
1) As i sad, i just did flashing firmware, whats easy, but rooting, roms, kernel and so on, i dont have a clue how to do this and WHAT it is at all :S
2)http://forum.xda-developers.com/showthread.php?t=2145364&page=4, here i saw it the 1266-6442 telekom germany DE, and i thought thats it, but u may be sure right.
And i currently have 1265-1620_R1J, flashed it yesterday just so, its CE Region i thing, 4.3 version, build .295.
3)Yeah, i first had the original Firmware on my phone, had the 4.2.2 version, and then the official software came for my phone and the T-Mobile provider i think.
And then, the 4.3 is just S**t, as i sad it, just problems, and i just want the previous version, because it worked perfect.
so i just was flashing all the other firmwares, especially the 4.3, from all the other regions, i thought maybe they will work better, but nope.
And when i try to flash previous versions/firmware, it just comes to the animation, after the sony and xperia logo, and restarts over and over again :/
And no, no roms, or recovery, i didnt do anything of all that, just flashing firmware with flashtool.
P.S. Thanks for trying to help me dude !
Click to expand...
Click to collapse
im reading you post and i get more confused because two things its impossible your xperia t had 4.2.2 because we jump ditectly from 4.1.2 to 4.3 and you put one thread for tx what is really your phone xperia t or tx?
Enviado do meu Nexus 10 através de Tapatalk
quintas84 said:
im reading you post and i get more confused because two things its impossible your xperia t had 4.2.2 because we jump ditectly from 4.1.2 to 4.3 and you put one thread for tx what is really your phone xperia t or tx?
Enviado do meu Nexus 10 através de Tapatalk
Click to expand...
Click to collapse
Ouh sorry my bad, 4.1.2 it was, and yeah, i know of course what phone i have dude Sony Xperia T lt30p
bosnianboss9 said:
Haha yeah i know what u mean, but thats not me
1) As i sad, i just did flashing firmware, whats easy, but rooting, roms, kernel and so on, i dont have a clue how to do this and WHAT it is at all :S
2)http://forum.xda-developers.com/showthread.php?t=2145364&page=4, here i saw it the 1266-6442 telekom germany DE, and i thought thats it, but u may be sure right.
And i currently have 1265-1620_R1J, flashed it yesterday just so, its CE Region i thing, 4.3 version, build .295.
3)Yeah, i first had the original Firmware on my phone, had the 4.2.2 version, and then the official software came for my phone and the T-Mobile provider i think.
And then, the 4.3 is just S**t, as i sad it, just problems, and i just want the previous version, because it worked perfect.
so i just was flashing all the other firmwares, especially the 4.3, from all the other regions, i thought maybe they will work better, but nope.
And when i try to flash previous versions/firmware, it just comes to the animation, after the sony and xperia logo, and restarts over and over again :/
And no, no roms, or recovery, i didnt do anything of all that, just flashing firmware with flashtool.
P.S. Thanks for trying to help me dude !
Click to expand...
Click to collapse
Ok, now I've understood what's your situation.
It seems that when you flashed 4.1.2 firmwares, the process was not compete for some reason.
The list from which you get that number, is about all kind of xperia T... and is different from the firmware list.
The problem is that you lost your previous original number, maybe it was 1265-9144... and you can resume it only with root and a little bit of experience... and actually I'm not sure you would be able to handle this kind of hacking stuff.
Anyway I'm quite sure that 4.1.2 from CE is perfect for your needs.
Try this one with Flashtool: http://forum.xda-developers.com/showpost.php?p=42393403&postcount=29
This firmware is perfect for any european country: I tested many times and is one of the best.
But before flashing, recharge your battery to the maximum. And be sure that the flashing process is complete and without errors.
Just try and let me know...
istux said:
Ok, now I've understood what's your situation.
It seems that when you flashed 4.1.2 firmwares, the process was not compete for some reason.
The list from which you get that number, is about all kind of xperia T... and is different from the firmware list.
The problem is that you lost your previous original number, maybe it was 1265-9144... and you can resume it only with root and a little bit of experience... and actually I'm not sure you would be able to handle this kind of hacking stuff.
Anyway I'm quite sure that 4.1.2 from CE is perfect for your needs.
Try this one with Flashtool: http://forum.xda-developers.com/showpost.php?p=42393403&postcount=29
This firmware is perfect for any european country: I tested many times and is one of the best.
But before flashing, recharge your battery to the maximum. And be sure that the flashing process is complete and without errors.
Just try and let me know...
Click to expand...
Click to collapse
Well Im downloading it now, in 5 minutes the download is done, and flash it then and i will report.
When it doesnt work, i must do that root or what u think should work.
With a bit of instructions and so on, i could do it, im a "Computer/Technic Freak" anyway
bosnianboss9 said:
Well Im downloading it now, in 5 minutes the download is done, and flash it then and i will report.
When it doesnt work, i must do that root or what u think should work.
With a bit of instructions and so on, i could do it, im a "Computer/Technic Freak" anyway
Click to expand...
Click to collapse
Damn, didint work. I had 50 % Battery, thats not the problem, the flashing process went good without any errors, and again, it comes past sony and xperia logo, and then by the animation, it blocks and restarts and do it all again..
I think i must do that root and so on :/
bosnianboss9 said:
Damn, didint work. I had 50 % Battery, thats not the problem, the flashing process went good without any errors, and again, it comes past sony and xperia logo, and then by the animation, it blocks and restarts and do it all again..
I think i must do that root and so on :/
Click to expand...
Click to collapse
This kind of issue is called "bootloop".
When it happens, try to push "power button" + "volume up" together.
The phone will turn off.
Turn on again and if there's bootloop again, repeat the procedure on and on and on.
Try many times...
istux said:
This kind of issue is called "bootloop".
When it happens, try to push "power button" + "volume up" together.
The phone will turn off.
Turn on again and if there's bootloop again, repeat the procedure on and on and on.
Try many times...
Click to expand...
Click to collapse
Well i did it, many times, didnt help.. And tried the soft and hardreset at least, didnt work either.. But im asking, why does this bootloop dont appear by any 4.3 version ?
Can i check somehow, is my phone rooted ?
Well, the other method wirh rooting and so on, must be done i think..
bosnianboss9 said:
Well i did it, many times, didnt help.. And tried the soft and hardreset at least, didnt work either.. But im asking, why does this bootloop dont appear by any 4.3 version ?
Can i check somehow, is my phone rooted ?
Well, the other method wirh rooting and so on, must be done i think..
Click to expand...
Click to collapse
I can't answer to the first question.
You are the first with this weird problem and I'm beginning to think that something is broken inside your phone.
Bootloops are usual when something is wrong with kernel or system, but if you say that flashing went good and this appears only with 4.1.2 , I really don't know why.
You are not rooted because you've never done before and anyway every time you format the system (flashing with Flashtool or via recovery) you lose root.
So you are not rooted for sure.
The problem now is becoming bigger, because there's no way to root a 4.3 firmware directly.
But... guess what? You have to root 4.1.2 before and then install a 4.3 already rooted. :crying:
The only way for you to root 4.3 directly is to unlock your bootloader, but this means that you lose warranty and DRM keys (that are needed to let work some functions like Bravia Engine).
Actually you could save your warranty and DRM keys with a special backup (called TA backup), but.... guess what? You need to be rooted!!!! :crying:
The second way is to try to install 4.0.4 ice cream and root it. It could work.
I give you this link https://docs.google.com/file/d/0B55PDGQqCzReV2dFSjFSNnlLLVk/preview?pli=1
It's 4.0.4 italian version...
Try this... and if it doesn't work, the only way is to unlock your bootloader losing warranty and drm keys, sorry...
istux said:
I can't answer to the first question.
You are the first with this weird problem and I'm beginning to think that something is broken inside your phone.
Bootloops are usual when something is wrong with kernel or system, but if you say that flashing went good and this appears only with 4.1.2 , I really don't know why.
You are not rooted because you've never done before and anyway every time you format the system (flashing with Flashtool or via recovery) you lose root.
So you are not rooted for sure.
The problem now is becoming bigger, because there's no way to root a 4.3 firmware directly.
But... guess what? You have to root 4.1.2 before and then install a 4.3 already rooted. :crying:
The only way for you to root 4.3 directly is to unlock your bootloader, but this means that you lose warranty and DRM keys (that are needed to let work some functions like Bravia Engine).
Actually you could save your warranty and DRM keys with a special backup (called TA backup), but.... guess what? You need to be rooted!!!! :crying:
The second way is to try to install 4.0.4 ice cream and root it. It could work.
I give you this link https://docs.google.com/file/d/0B55PDGQqCzReV2dFSjFSNnlLLVk/preview?pli=1
It's 4.0.4 italian version...
Try this... and if it doesn't work, the only way is to unlock your bootloader losing warranty and drm keys, sorry...
Click to expand...
Click to collapse
Dude, i s*it on the warrany and so on, i just want my phone to get goind and work !
So i will unlock the bootloader, and what should i do next ?
bosnianboss9 said:
Dude, i s*it on the warrany and so on, i just want my phone to get goind and work !
So i will unlock the bootloader, and what should i do next ?
Click to expand...
Click to collapse
LOL :cyclops: as you wish...
1) Flash 4.3 with Flashtool
2) Unlock your bootloader on Sony official site following all the instructions: http://unlockbootloader.sonymobile.com/instructions
3) Once it's unlocked, open Flashtool and re-flash 4.1.2 CE that I gave you and you tried before: http://forum.xda-developers.com/showpost.php?p=42393403&postcount=29
4) Don't turn on. Download Doomkernel here: http://d-h.st/4kK
Unpack the .elf file inside the zip
5) Open Flashtool. Connect the phone to PC keeping pushed the volume-up button. Now the phone is in fastboot mode. Click on the lightning symbol, select fastbootmode, select kernel to flash, select the .elf file extracted before, done.
6) Unplug the phone. Turn on and you will see the doomkernel logo... and now I hope that you finally enter into 4.1.2 firmware without bootloop.
7) To root: you need to copy this file http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip to the internal memory.
Turn off. Turn on pushing volume-down repeatedly, now you enter into recovery, now install the supersu zip and reboot.
istux said:
LOL :cyclops: as you wish...
1) Flash 4.3 with Flashtool
2) Unlock your bootloader on Sony official site following all the instructions: http://unlockbootloader.sonymobile.com/instructions
3) Once it's unlocked, open Flashtool and re-flash 4.1.2 CE that I gave you and you tried before: http://forum.xda-developers.com/showpost.php?p=42393403&postcount=29
4) Don't turn on. Download Doomkernel here: http://d-h.st/4kK
Unpack the .elf file inside the zip
5) Open Flashtool. Connect the phone to PC keeping pushed the volume-up button. Now the phone is in fastboot mode. Click on the lightning symbol, select fastbootmode, select kernel to flash, select the .elf file extracted before, done.
6) Unplug the phone. Turn on and you will see the doomkernel logo... and now I hope that you finally enter into 4.1.2 firmware without bootloop.
7) To root: you need to copy this file http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip to the internal memory.
Turn off. Turn on pushing volume-down repeatedly, now you enter into recovery, now install the supersu zip and reboot.
Click to expand...
Click to collapse
DAAAAAMN ! -.- :/ DommKernel logo is there, xperia logo, animation, and blocks again, restarts all the time.. I'm really desperate...
Now you have 4.1.2 with the doomkernel and the root, which is the perfect combination to do anything on your device.
If it's working, you can leave the phone in this situation.
Instead if you really want to go back to the original firmware, go here: http://forum.xda-developers.com/showthread.php?t=2334653
Follow the part A using this custom number 1265-9144 (t-mobile Germany). Remember you need root for this process!
Relock the bootloader http://forum.xda-developers.com/showthread.php?t=1924221
Plug to Sony PC Companion and Sony will re-install your original firmware.
My advice is to leave the phone unlocked and rooted with CE firmware
---------- Post added at 07:04 PM ---------- Previous post was at 06:59 PM ----------
bosnianboss9 said:
DAAAAAMN ! -.- :/ DommKernel logo is there, xperia logo, animation, and blocks again, restarts all the time.. I'm really desperate...
Click to expand...
Click to collapse
Damn.
Reflash 4.3 with Flashtool.
Download this Doomkernel: http://doomlord.xperia-files.com/download.php?dlid=VC1Eb29NS2VybmVsLXYwOQ==
Be aware: don't use the old doomkernel, but this one (v.09) that is specific for 4.3
Flash the elf file, as you did before.
Now you have doomkernel logo and you can enter into 4.3.
Now root it as I suggested in the previous posts (turn off, turn on pushing vol-down, flash suspersu zip, reboot).
Try.
istux said:
Now you have 4.1.2 with the doomkernel and the root, which is the perfect combination to do anything on your device.
If it's working, you can leave the phone in this situation.
Instead if you really want to go back to the original firmware, go here: http://forum.xda-developers.com/showthread.php?t=2334653
Follow the part A using this custom number 1265-9144 (t-mobile Germany). Remember you need root for this process!
Relock the bootloader http://forum.xda-developers.com/showthread.php?t=1924221
Plug to Sony PC Companion and Sony will re-install your original firmware.
My advice is to leave the phone unlocked and rooted with CE firmware
Click to expand...
Click to collapse
Well dude im a bit confused now
The recovery mode is working too ( volume down pressing repeadetly", "Team recovery..." didnt catch up the rest of the name, but cant boot into the phone as i said.
Soo, what should i do now? You are my one and only HOPE !!
Hi all,
I havnt flashed a device since the first android ROMS for the HTC HD2, so that gives you an idea of how rusty I am, so please bare with me. I've been reading and searching for hours and my eyes feel like they are bleeding so I'm typing this plea for help whle I atill have some vision.
I ve got a c6903 z1 running the latest 5.1.1 update. stock kernel etc, locked bootloader.
I was on 5.02 rooted and now want to root 5.1.1
After lots of reading I realise that I need to downgrade to 4.4.4 kitkat, then root then install dual recovery, then installl a pre rooted 5.1.1... FIRSTLY - Does this sound right? are these the right steps to root 5.1.1?
Secondly, It took me a while finding Generic .108 ftf files but now I've found a few (through the ftf 'mega thread') and dont know which one I need... the options are:
C6903_14.4.A.0.108_1276-7939_R3C Generic MY.ftf 1060174KB
C6903_14.4.A.0.108_Customized KR.ftf 948416KB
C6903_14.4.A.0.108_Customized UK.ftf 1034553KB
C6903_14.4.A.0.108_Generic-MEA_1277-2880_R5C.ftf 1010011KB
C6903_14.4.A.0.108_Generic FR 1276-5833_R5C.ftf 1019704KB
C6903_14.4.A.0.108_Generic IT 1276-0557.ftf 1050780KB
C6903_14.4.A.0.108_Generic RU 1276-7743.ftf 973615KB
C6903_14.4.A.0.108_Generic_SG_1276-7937_R3C.ftf 1048335KB
Will any of these work considering I'm not staying on 4.4.4?
I assumed I could safely use the 'UK' file from the above list but then got paranoid I might brick my z1 by flashing a Ukranian ROM lol.
I've now got 'the fear' and am afraid I might **** this whole process up and brick my device.
which reminds me, one last thing... Ive downloaded the official SONY Flashtool (ver. 0.9.19.8).. is this the right tool for the job? I seem to remember reading that the official flashtool only works on unlocked bootloaders, but I've read so much im confused as hell at this point.
Sorry for the long post,
Any help would be greatly appreciated.
Correct. There is no direct root for 5.1.1 currently. You could also downgrade to 5.0.2 instead, it doesn't really make a difference between that and 4.4.
It doesn't really matter what your interim ROM is as long as you do a clean flash when updating to 5.1.1 again.
Flashtool is the correct tool to be using. It has a utility called XperiFirm built it. You can use that to get any FTF that's publically available so that you don't have to depend on FTF threads.
The only way to have rooted 5.1.1 is with a pre-rooted zip, so you'll have to use PRFCreator to create that zip if there isn't one already posted for the specific variant you want to use.
thesweeney80 said:
Hi all,
I havnt flashed a device since the first android ROMS for the HTC HD2, so that gives you an idea of how rusty I am, so please bare with me. I've been reading and searching for hours and my eyes feel like they are bleeding so I'm typing this plea for help whle I atill have some vision.
I ve got a c6903 z1 running the latest 5.1.1 update. stock kernel etc, locked bootloader.
I was on 5.02 rooted and now want to root 5.1.1
After lots of reading I realise that I need to downgrade to 4.4.4 kitkat, then root then install dual recovery, then installl a pre rooted 5.1.1... FIRSTLY - Does this sound right? are these the right steps to root 5.1.1?
Secondly, It took me a while finding Generic .108 ftf files but now I've found a few (through the ftf 'mega thread') and dont know which one I need... the options are:
C6903_14.4.A.0.108_1276-7939_R3C Generic MY.ftf 1060174KB
C6903_14.4.A.0.108_Customized KR.ftf 948416KB
C6903_14.4.A.0.108_Customized UK.ftf 1034553KB
C6903_14.4.A.0.108_Generic-MEA_1277-2880_R5C.ftf 1010011KB
C6903_14.4.A.0.108_Generic FR 1276-5833_R5C.ftf 1019704KB
C6903_14.4.A.0.108_Generic IT 1276-0557.ftf 1050780KB
C6903_14.4.A.0.108_Generic RU 1276-7743.ftf 973615KB
C6903_14.4.A.0.108_Generic_SG_1276-7937_R3C.ftf 1048335KB
Will any of these work considering I'm not staying on 4.4.4?
I assumed I could safely use the 'UK' file from the above list but then got paranoid I might brick my z1 by flashing a Ukranian ROM lol.
I've now got 'the fear' and am afraid I might **** this whole process up and brick my device.
which reminds me, one last thing... Ive downloaded the official SONY Flashtool (ver. 0.9.19.8).. is this the right tool for the job? I seem to remember reading that the official flashtool only works on unlocked bootloaders, but I've read so much im confused as hell at this point.
Sorry for the long post,
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hey there! Welcome to the Z1 community
All you have to do is make sure you flash the ftf specific to your device. As long as it says C6903 in the ftf, you're good to go. all these locations are just country specific customizations with some apps and stuff. I'd say you can just flash the SG ftf for a mostly bloat free system.
In addition, you can't use the SONY flashtool (EMMA) unless you have an unlocked bootloader. I'd recommend you use flashtool (just google it) which lets you flash on both lock and unlocked bootloaders. Once you flash KK, use one of the rooting programs (Turn on USB debugging, and connect it to your computer, run the application and go through the steps. Let me know if you need help on what method of root to use.)
Once rooted, you should have a recovery, which should let you flash a prerooted zip easily.
If you have an unlocked bootloader, just flash any custom kernel through fastboot, boot into its recovery By pressing vol up or down at boot logo) and flash the zip.
Final tip is, make sure you have the prerooted zip on your sd card before you flash a custom kernel, as not all can mount to the PC from the reovery and flashing an incompatible kernel (such as a 4.4.4 kernel on a 5.0 rom) won't let you boot into the ROM.
Feel free to ask if you have any doubts, come across any issues, or need any help at all.
SOURCE: I flashed a customized TW ftf on a Singapore bought C6902 which I'm using in India with no issues at all.
xasbo said:
Correct. There is no direct root for 5.1.1 currently. You could also downgrade to 5.0.2 instead, it doesn't really make a difference between that and 4.4.
It doesn't really matter what your interim ROM is as long as you do a clean flash when updating to 5.1.1 again.
Flashtool is the correct tool to be using. It has a utility called XperiFirm built it. You can use that to get any FTF that's publically available so that you don't have to depend on FTF threads.
The only way to have rooted 5.1.1 is with a pre-rooted zip, so you'll have to use PRFCreator to create that zip if there isn't one already posted for the specific variant you want to use.
Click to expand...
Click to collapse
Thanks for the quick reply mate. Sounds good, I might just go to 5.02 then as rooting that was fairly painless.
Ive already found a pre-rooted zip for stock 5.1.1 so I think I'm good to go on that one. Almost ready to dive in... thanks for clearing that up.
AnrgKrshn said:
Hey there! Welcome to the Z1 community
All you have to do is make sure you flash the ftf specific to your device. As long as it says C6903 in the ftf, you're good to go. all these locations are just country specific customizations with some apps and stuff. I'd say you can just flash the SG ftf for a mostly bloat free system.
In addition, you can't use the SONY flashtool (EMMA) unless you have an unlocked bootloader. I'd recommend you use flashtool (just google it) which lets you flash on both lock and unlocked bootloaders. Once you flash KK, use one of the rooting programs (Turn on USB debugging, and connect it to your computer, run the application and go through the steps. Let me know if you need help on what method of root to use.)
Once rooted, you should have a recovery, which should let you flash a prerooted zip easily.
If you have an unlocked bootloader, just flash any custom kernel through fastboot, boot into its recovery By pressing vol up or down at boot logo) and flash the zip.
Final tip is, make sure you have the prerooted zip on your sd card before you flash a custom kernel, as not all can mount to the PC from the reovery and flashing an incompatible kernel (such as a 4.4.4 kernel on a 5.0 rom) won't let you boot into the ROM.
Feel free to ask if you have any doubts, come across any issues, or need any help at all.
SOURCE: I flashed a customized TW ftf on a Singapore bought C6902 which I'm using in India with no issues at all.
Click to expand...
Click to collapse
Thanks for the in depth reply mate much appreciated. And thanks for the welcome, cheers
Ive got a locked bootloader so I'll check out that unnoficial flashtool, thanks.
Now here is where my confusion and lack of knowledge becomes another problem... You say that after rooting kitkat (using something like 'easy root tool'?) I "should have a recovery, which should let you flash a prerooted zip easily.".......
I was under the impression that after rooting kitkat I would have to install
'XZ Dual Recovery' to let me flash the pre-root zip.
Do I not have to install XZ dual recovery?
Thanks again for all your help... just trying to clear up the details before I start the whole process.
Cheers mate.
thesweeney80 said:
Thanks for the in depth reply mate much appreciated. And thanks for the welcome, cheers
Ive got a locked bootloader so I'll check out that unnoficial flashtool, thanks.
Now here is where my confusion and lack of knowledge becomes another problem... You say that after rooting kitkat (using something like 'easy root tool'?) I "should have a recovery, which should let you flash a prerooted zip easily.".......
I was under the impression that after rooting kitkat I would have to install
'XZ Dual Recovery' to let me flash the pre-root zip.
Do I not have to install XZ dual recovery?
Thanks again for all your help... just trying to clear up the details before I start the whole process.
Cheers mate.
Click to expand...
Click to collapse
Some root kits will install a custom recovery for you, but it's so easy to just install XZDR, that's what I always do. XZDR will actually give you multiple recoveries to choose from (but TWRP is generally considered the best), but it also has some nice addition features like RIC killer (which allows you to have full root vs partial root).
I should also clarify my previous statement - XperiFirm is great for getting *new* firmware.. but you will either need to back up copies of old firmware for future use, or seek them out in threads if you need them later.
xasbo said:
Some root kits will install a custom recovery for you, but it's so easy to just install XZDR, that's what I always do. XZDR will actually give you multiple recoveries to choose from (but TWRP is generally considered the best), but it also has some nice addition features like RIC killer (which allows you to have full root vs partial root).
I should also clarify my previous statement - XperiFirm is great for getting *new* firmware.. but you will either need to back up copies of old firmware for future use, or seek them out in threads if you need them later.
Click to expand...
Click to collapse
ahhh, now that makes sense (re: some root solutions including a recovery), thank you for clearing that up.
One final thing (before I dive in and at least get KK installed+rooted)...
If I have to start reading one more subject I think my head will explode lol so If you could just clear up one thing about RIC Killer....
I want full root, not partial - do I have to mess with RIC Killer or can I leave it alone?
On the guide I am trying to follow; someone said they ended up 'half rooted' - would that be because of RIC killer or user error when creating the pre-rooted zip?
just dont want to go through all this and end up only being half rooted haha, cheers.
edit: ok so after checking flashtool it seems I already have the right one (NOT SONY)... I have version 0.9.19.7 But there are two warnings (pasted below) on the flashtool thread.
Does the first warning simply mean 'Use the latest version'??
I have no clue about the second warning...do i just uncheck the uption regarding simlock.ta IF it is in the list of options when I flash kitkat? I have no clue if my ftf file includes simlock.ta.
Both warnings mention bricks and hard bricks so I'm taking them pretty seriously haha.
Any advice on these warnings would be great, thanks for your patience.
"WARNING : Since Xperia Z, sony added a new set of files I called bootbundle. Those files can be bundled from 0.9.13 and can be flashed from 0.9.13 only. To all those flashing devices from Z edition to all after Z, it is highly advised to use 0.9.13 and to be sure FTF you flash contain the bootbundle set. I've been reported of hard bricks because of missing such set of files from bundles.
I WANT TO GET YOUR ATTENTION ABOUT THE LATEST BRANCH 0.9.19. Without FSC, the tool will by default include simlock.ta if this file is present in the FTF. The result will be a bricked phone
As a workaround, until I release a patch, please please tick the exlude simlock.ta if you see it in the list.
0.9.19.6 fixes the simlock.ta issue. This file is by default excluded. Then it will not be flashed until you explicitely untick the exlcude simlock box. Do it at your own risk."
thesweeney80 said:
ahhh, now that makes sense (re: some root solutions including a recovery), thank you for clearing that up.
One final thing (before I dive in and at least get KK installed+rooted)...
If I have to start reading one more subject I think my head will explode lol so If you could just clear up one thing about RIC Killer....
I want full root, not partial - do I have to mess with RIC Killer or can I leave it alone?
On the guide I am trying to follow; someone said they ended up 'half rooted' - would that be because of RIC killer or user error when creating the pre-rooted zip?
just dont want to go through all this and end up only being half rooted haha, cheers.
Click to expand...
Click to collapse
Even if you don't have a RIC killer installed, most root stuff will work fine. On the Z1, the RIC will prevent you from doing specific things, most importantly mounting /system as writable, which is necessary for certain type of advanced modifications.
However, if you install XZDR, you'll get the custom recovery + the RIC killer. I would just do that.
edit: ok so after checking flashtool it seems I already have the right one (NOT SONY)... I have version 0.9.19.7 But there are two warnings (pasted below) on the flashtool thread.
Does the first warning simply mean 'Use the latest version'??
I have no clue about the second warning...do i just uncheck the uption regarding simlock.ta IF it is in the list of options when I flash kitkat? I have no clue if my ftf file includes simlock.ta.
Both warnings mention bricks and hard bricks so I'm taking them pretty seriously haha.
Any advice on these warnings would be great, thanks for your patience.
"WARNING : Since Xperia Z, sony added a new set of files I called bootbundle. Those files can be bundled from 0.9.13 and can be flashed from 0.9.13 only. To all those flashing devices from Z edition to all after Z, it is highly advised to use 0.9.13 and to be sure FTF you flash contain the bootbundle set. I've been reported of hard bricks because of missing such set of files from bundles.
I WANT TO GET YOUR ATTENTION ABOUT THE LATEST BRANCH 0.9.19. Without FSC, the tool will by default include simlock.ta if this file is present in the FTF. The result will be a bricked phone
As a workaround, until I release a patch, please please tick the exlude simlock.ta if you see it in the list.
0.9.19.6 fixes the simlock.ta issue. This file is by default excluded. Then it will not be flashed until you explicitely untick the exlcude simlock box. Do it at your own risk."
Click to expand...
Click to collapse
Correct, the warning is to just make sure you use a version later than 0.9.13; you're fine to use 0.9.19.7. It will tell you that .8 is out, but the change is not important to you. You don't need to do anything special regarding simlock.ta.
If you have an external SD card, copy everything you want to flash onto the phone before starting (5.1.1 prerooted, SuperSU, XZDR), so it's already there when you need it.
xasbo said:
Even if you don't have a RIC killer installed, most root stuff will work fine. On the Z1, the RIC will prevent you from doing specific things, most importantly mounting /system as writable, which is necessary for certain type of advanced modifications.
However, if you install XZDR, you'll get the custom recovery + the RIC killer. I would just do that.
Correct, the warning is to just make sure you use a version later than 0.9.13; you're fine to use 0.9.19.7. It will tell you that .8 is out, but the change is not important to you. You don't need to do anything special regarding simlock.ta.
If you have an external SD card, copy everything you want to flash onto the phone before starting (5.1.1 prerooted, SuperSU, XZDR), so it's already there when you need it.
Click to expand...
Click to collapse
THANKS.
So As long as I install XZDR I will have RIC killer and that will ensure a full root? thats great, cheers..
Thanks for clearing up the flashtool warnings too, very much appreciated.
As for your final tip about the SD card... do you mean copy everything to the SD card? or the phone? I'm ASSuming you mean the SD card as the phone memory will get wiped during flasshing if I clear everything? no?
Sorry mate I'm having a total brain-fart after everything Ive read, my comprehension skills are at an all time low lol. Tired.
Thanks again for all ya help mate, I'm just about ready to get this crap done... and then once Ive finished I know I'll be thinking 'wtf was all the panicking about? lol.
THANKS.
thesweeney80 said:
THANKS.
So As long as I install XZDR I will have RIC killer and that will ensure a full root? thats great, cheers..
Thanks for clearing up the flashtool warnings too, very much appreciated.
As for your final tip about the SD card... do you mean copy everything to the SD card? or the phone? I'm ASSuming you mean the SD card as the phone memory will get wiped during flasshing if I clear everything? no?
Sorry mate I'm having a total brain-fart after everything Ive read, my comprehension skills are at an all time low lol. Tired.
Thanks again for all ya help mate, I'm just about ready to get this crap done... and then once Ive finished I know I'll be thinking 'wtf was all the panicking about? lol.
THANKS.
Click to expand...
Click to collapse
Make sure you flash SuperSU and XZDR at the same time. If you do not, it will not work correctly (still only partial root). If you make your own pre-root ZIP, you can roll them into it and do it in one fell swoop.
Yeah. External SD card = not the phone. If you do a clean flash (which you should), you will be wiping the phone storage.
xasbo said:
Make sure you flash SuperSU and XZDR at the same time. If you do not, it will not work correctly (still only partial root). If you make your own pre-root ZIP, you can roll them into it and do it in one fell swoop.
Yeah. External SD card = not the phone. If you do a clean flash (which you should), you will be wiping the phone storage.
Click to expand...
Click to collapse
You're the man, man...THANKS. :highfive:
I'll check the pre-root zip I found and if it doesnt have Supersu included I'll make my own and include XZDR too - I like the idea of having things 'slipstreamed' into one flash - thanks for the tip.
Thanks a lot for all your help in calming all my little worries about this process,,, very much appreciated.
I'll do the whole lot tomorrow and report back... thanks again.
Suggestion - since you are re-learning and your goal at the moment is to have a rooted 5.1.1, I suggest you download and install Flashtool for windows. Go to http://www.flashtool.net/index.php. Now in Flashtool, your need to install the appropriate drivers for your device/s. Instructions searching (I'm doing my lunch while typing reply - lol). Then use XperiFirm which is integrated in Flashtool. It has its own icon, just click it so you can download a 5.0.2 FTF for yor region. Install that 5.0.2 FTF on your phone using Flashtool (Flash it Baby! Flash it!) Then you can root 5.0.2 with ease using Kingroot. Replace Kingroot with SuperSU. Then install NUT's Dual recovery. Then you can download any of the pre-rooted 5.1.1 FTFs XDA peeps are putting up under the General section and boom. You are now on 5.1.1. with root.
Deathschythe33 said:
Suggestion - since you are re-learning and your goal at the moment is to have a rooted 5.1.1, I suggest you download and install Flashtool for windows. Go to http://www.flashtool.net/index.php. Now in Flashtool, your need to install the appropriate drivers for your device/s. Instructions searching (I'm doing my lunch while typing reply - lol). Then use XperiFirm which is integrated in Flashtool. It has its own icon, just click it so you can download a 5.0.2 FTF for yor region. Install that 5.0.2 FTF on your phone using Flashtool (Flash it Baby! Flash it!) Then you can root 5.0.2 with ease using Kingroot. Replace Kingroot with SuperSU. Then install NUT's Dual recovery. Then you can download any of the pre-rooted 5.1.1 FTFs XDA peeps are putting up under the General section and boom. You are now on 5.1.1. with root.
Click to expand...
Click to collapse
cheers mate, I appreciate all the help I can get lol.
I decided to go with 5.0.2 instead of kitkat, but when I click on the .270 firmware links in xperifirm I get an error which says:
"Incomplete Firmware.
The following files are missing on the server:
fsp.zip.
Proceed with caution"
I clicked on the latest 5.1.1 firmwares and none of them give this error... so does the error simply mean that .270 is not the latest version? I couldnt find the answer in google. Are thes firmwares without fsp.zip safe to flash?
Thanks again.
edit: hmmm looks like i'll have to flash 4.4 instead.
When I try to download a .270 (5.0.2) firmware in xperifirm; it stops downloading after a few seconds and says a reuired file is missing
If I try to download one of the .368 firmwares it downloads ok
edit 2: F*ck my life... Not enough space on C: for unpacked ftf file (Small c partition on SSD) ... so unless there is a way for flashtool to flash from d:\...\firmware im screwed. I'll try compressing (NTFS) the c drive and hope thats enough
thesweeney80 said:
edit 2: F*ck my life... Not enough space on C: for unpacked ftf file (Small c partition on SSD) ... so unless there is a way for flashtool to flash from d:\...\firmware im screwed. I'll try compressing (NTFS) the c drive and hope thats enough
Click to expand...
Click to collapse
There is a solution, but it's slightly complicated. Proceed at your own risk, maybe do a little research to make sure you understand what I'm tell you to do.
1) Browse to C:\Users\<username>\. if you aren't already, show hidden files and folders.
2) Grab the .flashTool directory and move it onto a drive with sufficient free space (e.g., D:\.flashTool).
3) Go to Start and type cmd into the search field. When cmd.exe shows up, right-click and select Run As Administrator.
4) Change to the user directory ("cd C:\Users\<username>").
5) Make a junction point named .flashTool pointed to where ever you moved the folder (e.g., "mklink /j .flashTool D:\.flashTool").
This will make flashtool think that its settings/data folder is in the right place, when really it's just a fake folder linked somewhere else.
xasbo said:
There is a solution, but it's slightly complicated. Proceed at your own risk, maybe do a little research to make sure you understand what I'm tell you to do.
1) Browse to C:\Users\<username>\. if you aren't already, show hidden files and folders.
2) Grab the .flashTool directory and move it onto a drive with sufficient free space (e.g., D:\.flashTool).
3) Go to Start and type cmd into the search field. When cmd.exe shows up, right-click and select Run As Administrator.
4) Change to the user directory ("cd C:\Users\<username>").
5) Make a junction point named .flashTool pointed to where ever you moved the folder (e.g., "mklink /j .flashTool D:\.flashTool").
This will make flashtool think that its settings/data folder is in the right place, when really it's just a fake folder linked somewhere else.
Click to expand...
Click to collapse
Thanks again mate. Ive done that once before and forgotten all about it.
This time I just compressed c:\ with NTFS compression and it gained just enough space (F*ck you Winsxs).
But the above info will surely come in handy in future, so once again: Thanks! Tou've been a big help.
Just about to install XZDR and a pre-rooted 5.1.1 :fingers-crossed: Cheers mate :good:
thesweeney80 said:
Thanks again mate. Ive done that once before and forgotten all about it.
This time I just compressed c:\ with NTFS compression and it gained just enough space (F*ck you Winsxs).
But the above info will surely come in handy in future, so once again: Thanks! Tou've been a big help.
Just about to install XZDR and a pre-rooted 5.1.1 :fingers-crossed: Cheers mate :good:
Click to expand...
Click to collapse
What a way you went through.
As you already were on 5.0.2 and rooted you just had to install xzdr to your phone.
After that you could flash one of the Pre-Rooted zip files you need.
Sent from my C6903 using XDA Free mobile app
motorazrv3 said:
What a way you went through.
As you already were on 5.0.2 and rooted you just had to install xzdr to your phone.
After that you could flash one of the Pre-Rooted zip files you need.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
well I know that now dont I? :silly: haha
yeah I was on a kingrooted 5.02, and should have just installed XZDR etc but I upgraded to 5.1.1 ASSunming I could root it with kingroot again, big mistake.
If I had read about kingroot not working on 5.1.1 I could have saved 24hrs worth of headaches.
Oh well... all done now. Rooted on 5.1.1, busybox installed and all
Now begins the long process of re-installing and customizing all over again *yipee*
No doubt I will go through all this again in a few weeks when I decide to unlock the BL and install a customROM And kernel
THIS is why I spent a few years with a 'dumb' phone after my HD2... ohhh the joys of flashing.
BIG Thanks to evryone who helped me out on this especially Xasbo, Gamer4Life and Deathschythe33. CHEERS
:good: glad you got it sorted.
Please Xasbo help, I Have loop all the time
xasbo said:
:good: glad you got it sorted.
Click to expand...
Click to collapse
Please, kan you help, I flashed downgrading my C6903 from .386 to C6903_14.4.A.0.108_Stripped, and got loops. Then I Tried again with several firmwares.108 and .386 and got the same result Loop :crying::crying:
I flashed with C6903_14.4.A.108 Generic SG and everything went fine, I got this massage:"NFC Firmware updating" "Don´t turn off you device", and got loop. Oh my god???? What Iam doing wrong?
Any suggestion. Thank you
asswembler said:
Please, kan you help, I flashed downgrading my C6903 from .386 to C6903_14.4.A.0.108_Stripped, and got loops. Then I Tried again with several firmwares.108 and .386 and got the same result Loop :crying::crying:
I flashed with C6903_14.4.A.108 Generic SG and everything went fine, I got this massage:"NFC Firmware updating" "Don´t turn off you device", and got loop. Oh my god???? What Iam doing wrong?
Any suggestion. Thank you
Click to expand...
Click to collapse
Hmm. I've never seen that NFC message before. Did it look like that firmware update completed before the phone restarted?
Are you still able to flash anything to the phone? What are you trying to accomplish?