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.
Hi there guys,
I have a locked bootloader on my Sony Z1, I have the dual recovery (at least, I did), I flashed something, just a different boot animation and afterwards the boot animation didn't work properly.
So I went back to recovery to restore the backup that I had made just before flashing the boot animation and it came up with an error half way through restoring the /System, and aborted.
After it aborted and exited recovery, on the way out it said "No Root Access Detected" and asked if I wanted to "Reroot" it, so I said yes.
Now when it boots, it just sits on the "Sony" screen, with no colour on the LED, or anything. Can't hold the buttons to go to recovery either.
Can't use the Sony Flashtool, because that requires an unlocked bootloader, and I can't use the Sony Software Companion, because that requires the phone to fully boot.
Is there anything that you guys can suggest?
Thanks in advance.
corydor13 said:
Hi there guys,
I have a locked bootloader on my Sony Z1, I have the dual recovery (at least, I did), I flashed something, just a different boot animation and afterwards the boot animation didn't work properly.
So I went back to recovery to restore the backup that I had made just before flashing the boot animation and it came up with an error half way through restoring the /System, and aborted.
After it aborted and exited recovery, on the way out it said "No Root Access Detected" and asked if I wanted to "Reroot" it, so I said yes.
Now when it boots, it just sits on the "Sony" screen, with no colour on the LED, or anything. Can't hold the buttons to go to recovery either.
Can't use the Sony Flashtool, because that requires an unlocked bootloader, and I can't use the Sony Software Companion, because that requires the phone to fully boot.
Is there anything that you guys can suggest?
Thanks in advance.
Click to expand...
Click to collapse
There are some issues with restoring backups on dual recovery, i think this is fixed with the latest version of dual-recovery(check that thread for updates). Do not use Sony flashtool, use the this flashtool http://forum.xda-developers.com/showthread.php?t=2439328 - read from Part 4 and you can download firmwares from here http://forum.xda-developers.com/showthread.php?t=2469191.
sofir786 said:
There are some issues with restoring backups on dual recovery, i think this is fixed with the latest version of dual-recovery(check that thread for updates). Do not use Sony flashtool, use the this flashtool http://forum.xda-developers.com/showthread.php?t=2439328 - read from Part 4 and you can download firmwares from here http://forum.xda-developers.com/showthread.php?t=2469191.
Click to expand...
Click to collapse
Thank you so much!
I am on 02 in the UK, and hate the fact it has the stupid 02 bubble up and down animations, so would it be fine if I used to Generic UK FTF?
and would there be any disadvantage to using this one over the 02 FTF?
also, on the first link you posted, it said to download the EXE for the application and I have done that, but it said to download the device files folder they have, and place that in the flashtool folder, but the device files link isn't there? So what do I have to do?
Place the FTF in the folder they specified, or?
(sorry if I seem a noob, come from using/flashing HTC's for years)
corydor13 said:
Thank you so much!
I am on 02 in the UK, and hate the fact it has the stupid 02 bubble up and down animations, so would it be fine if I used to Generic UK FTF?
and would there be any disadvantage to using this one over the 02 FTF?
also, on the first link you posted, it said to download the EXE for the application and I have done that, but it said to download the device files folder they have, and place that in the flashtool folder, but the device files link isn't there? So what do I have to do?
Place the FTF in the folder they specified, or?
(sorry if I seem a noob, come from using/flashing HTC's for years)
Click to expand...
Click to collapse
lol its okay, i used to have a htc one too but im a bit of a flash junkie but anyway. If you use a generic ftf it doesnt have all the O2 apps that get bundles along with the phone. Ignore the device files folder, you dont need it. you need to place the firmware in the "Firmwares" folder which is in the directory where flash tool was installed. Mine is here C:\Flashtool\Firmwares
sofir786 said:
lol its okay, i used to have a htc one too but im a bit of a flash junkie but anyway. If you use a generic ftf it doesnt have all the O2 apps that get bundles along with the phone. Ignore the device files folder, you dont need it. you need to place the firmware in the "Firmwares" folder which is in the directory where flash tool was installed. Mine is here C:\Flashtool\Firmwares
Click to expand...
Click to collapse
Ah ok then. Yeah, I have the HTC One too. Just chucked my SIM in that until I get the Z1 up again, lol.
Thanks a lot. I'll update when it's working again.
sofir786 said:
lol its okay, i used to have a htc one too but im a bit of a flash junkie but anyway. If you use a generic ftf it doesnt have all the O2 apps that get bundles along with the phone. Ignore the device files folder, you dont need it. you need to place the firmware in the "Firmwares" folder which is in the directory where flash tool was installed. Mine is here C:\Flashtool\Firmwares
Click to expand...
Click to collapse
Should I exclude any of the things that are options in the FlashTool?
corydor13 said:
Should I exclude any of the things that are options in the FlashTool?
Click to expand...
Click to collapse
Nah not really, you can untick data if you want so that doesnt get wiped but i would do a full wipe and leave everything as is when you flash.
sofir786 said:
Nah not really, you can untick data if you want so that doesnt get wiped but i would do a full wipe and leave everything as is when you flash.
Click to expand...
Click to collapse
Got it all back up and working. All the inbuilt apps updated and system updated to the newest version.
Just need to download all the apps I had, possibly think about rooting it and that tomorrow.
xD.
corydor13 said:
Got it all back up and working. All the inbuilt apps updated and system updated to the newest version.
Just need to download all the apps I had, possibly think about rooting it and that tomorrow.
xD.
Click to expand...
Click to collapse
ah great stuff. Just to let you know this firmware - 14.1.G.2.257 - is not currently rootable, thought id give you a heads up.
sofir786 said:
ah great stuff. Just to let you know this firmware - 14.1.G.2.257 - is not currently rootable, thought id give you a heads up.
Click to expand...
Click to collapse
The update that I just got on my phone says "14.1.G.1.534"
corydor13 said:
The update that I just got on my phone says "14.1.G.1.534"
Click to expand...
Click to collapse
your cool then, you dont have to worry, that version firmware is rootable
sofir786 said:
your cool then, you dont have to worry, that version firmware is rootable
Click to expand...
Click to collapse
Thank you.
I really am at a loss now.
There seems to be nothing that i am doing that is making it possible for me to get my phone rooted.
I am running 4.3 .290 on an unbranded c6903 and i have been trying for the last week to downgrade it to .534 so i can root the phone.
I have gone through the forum and have tried the recommended ways. I have downloaded all the correct ftf files. I have flashtool up to date.
I started with downgrading direct to .534 but the IMEI number just read 00000etc. I re-read the forum and saw that i should try and go to .557 before downgrading to .534. Same thing happened. No IMEI number. I then tried a different ftf file to no avail.
Today i saw someone say to use SUS but not to wipe Data. Tried it and the phone got stuck in a bootloop.
I am at a loss. I have never had a phone which was so difficult to root. I have rooted nearly all my android phones before the Z1 and i am confident with doing so.
I really like the phone and i will not be replacing it anytime soon. But has anyone got any ideas that can help me so i can get this phone rooted.
bernj175 said:
I really am at a loss now.
There seems to be nothing that i am doing that is making it possible for me to get my phone rooted.
I am running 4.3 .290 on an unbranded c6903 and i have been trying for the last week to downgrade it to .534 so i can root the phone.
I have gone through the forum and have tried the recommended ways. I have downloaded all the correct ftf files. I have flashtool up to date.
I started with downgrading direct to .534 but the IMEI number just read 00000etc. I re-read the forum and saw that i should try and go to .557 before downgrading to .534. Same thing happened. No IMEI number. I then tried a different ftf file to no avail.
Today i saw someone say to use SUS but not to wipe Data. Tried it and the phone got stuck in a bootloop.
I am at a loss. I have never had a phone which was so difficult to root. I have rooted nearly all my android phones before the Z1 and i am confident with doing so.
I really like the phone and i will not be replacing it anytime soon. But has anyone got any ideas that can help me so i can get this phone rooted.
Click to expand...
Click to collapse
To get your IMEI back you will need to update to .290 (once you get on .290 firmware your IMEI should reappear).Then you can either go through .257 to .534 or you can use a special .534 ftf made by [NUT] where no IMEI loss occurs. You can use my guide to guide you through the process:
Jumping directly to .534 it will lost IMEI. You can't or you use one posted by NUT.
shem2409 said:
To get your IMEI back you will need to update to .290 (once you get on .290 firmware your IMEI should reappear).Then you can either go through .257 to .534 or you can use a special .534 ftf made by [NUT] where no IMEI loss occurs. You can use my guide to guide you through the process:
Thanks for the reply.
Alas i have tried this method but i am unable to download the ftf made by NUT. It wont download. There is no seeders.
Click to expand...
Click to collapse
bernj175 said:
Alas i have tried this method but i am unable to download the ftf made by NUT. It wont download. There is no seeders.
Click to expand...
Click to collapse
HERE
This is the Video Tutorial poster by @shem2409, in the video tutorial check the links, Point 4), to download the FTF by NUT.
Thanks again.
I have downloaded it but when i extract the zip it comes up as ''sin file'' and not ftf files.
Tried to create a ftf bundle in flashtool but it won't flash. It comes up with ERROR.
Again i am at a loss
bernj175 said:
Thanks again.
I have downloaded it but when i extract the zip it comes up as ''sin file'' and not ftf files.
Tried to create a ftf bundle in flashtool but it won't flash. It comes up with ERROR.
Again i am at a loss
Click to expand...
Click to collapse
I don't know what you downloaded but I downloaded the file from the first link today, which shem2409 posted, and I have a classic FTF file, 767.8MB. Both links give me FTF extension file so check again what exactly you downloaded. Anyway if the file is correct rename the extension from .sin to .ftf and you are ready to flash.
Nope. I am not getting a classic ftf file. I am downloading the file. I am extracting the zip and it is giving me a breakdown of the files in sin format. No ftf file to be seen anywhere.
I have downloaded ftf files no issue apart from these ones.
I guess i am doing something wrong somewhere but i am now feeling like a noob as i cannot for the life of me figure out what the hell i am doing wrong.
I even tried to create an ftf file bundle using flashtool but to no avail.
Still at a loss. I am using WinRAR extract to by the way.
Do what I told you. Don't do what you think because you will mess up stuff and at the end you will brick you phone trying to flash some kind of file made by you. If you downloaded correctly from the Point 4) from the Video Tutorial and the size is 770MB then you have just to rename the file from .sin to .ftf, do you understand? Then try to make the process again via flashtool and all will be fine.
I would do but i do not have a ''file'' as such.... When i extract the zip. I have a complete breakdown of the file in sin format and it includes boot folder, META-INF folder and 14 different .sin files.
My understanding is that all together these will make a ftf file but i cant get them into that format. They are in one folder and when opened it gives me a complete breakdown of the file in sin format.
I cannot explain it more and i am unable to copy and paste on here what it is i am seeing.
I have never had this problems with any files before and i cannot figure out what i am doing wrong this time
bernj175 said:
I would do but i do not have a ''file'' as such.... When i extract the zip. I have a complete breakdown of the file in sin format and it includes boot folder, META-INF folder and 14 different .sin files.
My understanding is that all together these will make a ftf file but i cant get them into that format. They are in one folder and when opened it gives me a complete breakdown of the file in sin format.
I cannot explain it more and i am unable to copy and paste on here what it is i am seeing.
I have never had this problems with any files before and i cannot figure out what i am doing wrong this time
Click to expand...
Click to collapse
Ok, now I understand, you get files like on the pictures I posted, right?
Then rename the .zip file to .ftf. If you do not see the extensions on your PC like .txt, .doc, then go to Control Pannel > Folder Options > View and uncheck "Hide extensions for known file types" then Apply and go to rename the Zip file to .ftf and you are ready to flash.
eclyptos said:
Ok, now I understand, you get files like on the pictures I posted, right?
Then rename the .zip file to .ftf. If you do not see the extensions on your PC like .txt, .doc, then go to Control Pannel > Folder Options > View and uncheck "Hide extensions for known file types" then Apply and go to rename the Zip file to .ftf and you are ready to flash.
Click to expand...
Click to collapse
Thanks. Will do that and have another go.
Ok. Now got the phone rooted, backed up and updated to latest version.
Thanks again for the help. Now i can go get some sleep.:victory::victory::victory:
Can the firmware (.534) by NUT be used with C6902 model?
Thanks to anyone who is assisting me.
livelyyoungman said:
Can the firmware (.534) by NUT be used with C6902 model?
Thanks to anyone who is assisting me.
Click to expand...
Click to collapse
Not really, is for C6903 only and I will not recommend to cross over. BTW, to avoid the IMEI lost in the case to downgrade directly to .534 with other Firmware just exclude "Baseband" and all will be fine.
If you're planning to upgrade anyway you'll get your IMEI back, so just root it and upgrade.
Sent from my C6903 using xda app-developers app
eclyptos said:
Not really, is for C6903 only and I will not recommend to cross over. BTW, to avoid the IMEI lost in the case to downgrade directly to .534 with other Firmware just exclude "Baseband" and all will be fine.
Click to expand...
Click to collapse
Thanks for the post.
No that did not work for me. Downgrading to .534 excluding "Baseband" too resulted in loss of IMEI. Tried a few times and failed miserably. I feel I will have to downgrade to .257 before getting to .534 as this is the other suggestion to downgrade without loosing IMEI. But the issue I am facing is that the flash tool does not seem to recognize the .257 ftf file that I downloaded. Not sure why. So planning to download the Global .257 release and then try downgrading to .534 so as to get to rooted status.
MohammadAG said:
If you're planning to upgrade anyway you'll get your IMEI back, so just root it and upgrade.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
I would be upgrading to the latest firmware but need a rooted device. Rooting 4.3 without unlocking the BL is not possible. Hence want to take the round about way of getting this achieved.
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?
Just got my r1hd and want to root it, it is currently running 6.1 and wants to update to 7.4 .2 should I update before root?? Also does anyone have a guide on how to root it via a Mac?? Thanks
d3adbroke said:
Just got my r1hd and want to root it, it is currently running 6.1 and wants to update to 7.4 .2 should I update before root?? Also does anyone have a guide on how to root it via a Mac?? Thanks
Click to expand...
Click to collapse
Well Blu and Amazon have released that there are backdoors the firmware. They claim that the latest versions have closed those backdoors. So probably should not remain on 6.1.
But if you root now then use the Roms from the XDA forum you can also close those backdoors. And be ad free.
I know there are many pages to get caught up on. But if you browse at least the titles of the various threads, it is good place to start.
Now I do not know of a mac specific guide. The process of rooting uses sp flash tool. Then fastboot.
Many others have done it fine with mac, but did not make guides. I assume it is not that different.
mrmazak said:
Well Blu and Amazon have released that there are backdoors the firmware. They claim that the latest versions have closed those backdoors. So probably should not remain on 6.1.
But if you root now then use the Roms from the XDA forum you can also close those backdoors. And be ad free.
I know there are many pages to get caught up on. But if you browse at least the titles of the various threads, it is good place to start.
Now I do not know of a mac specific guide. The process of rooting uses sp flash tool. Then fastboot.
Many others have done it fine with mac, but did not make guides. I assume it is not that different.
Click to expand...
Click to collapse
I can't seems to find the MTK Drivers to install on the mac all the ones I find are EXE files for windows.
d3adbroke said:
I can't seems to find the MTK Drivers to install on the mac all the ones I find are EXE files for windows.
Click to expand...
Click to collapse
the auto installer that has the exe file also has folders with .inf (driver files). Is that helpful?
mrmazak said:
the auto installer that has the exe file also has folders with .inf (driver files). Is that helpful?
Click to expand...
Click to collapse
Okay I was able to get the driver but now when I try to run the dirtycow one click root .sh file it will not connect to device or put device in fastboot. I wish my PC wasn't broke
d3adbroke said:
Okay I was able to get the driver but now when I try to run the dirtycow one click root .sh file it will not connect to device or put device in fastboot. I wish my PC wasn't broke
Click to expand...
Click to collapse
you may have to read the .sh file and do the commands one by one manually
as long as adb is working in mac.
also if your on 6.1 you dont need to do it with the dirtycow method.
but it will need sp flashtool
mrmazak said:
you may have to read the .sh file and do the commands one by one manually
as long as adb is working in mac.
also if your on 6.1 you dont need to do it with the dirtycow method.
but it will need sp flashtool
Click to expand...
Click to collapse
Can't find so flashtool that works with Mac