Let me start off by saying I DO know what I am doing when it comes to rooting and Odin. And yes I have searched and found nothing.
With that out of the way, for some reason when I go to root my tab, Odin recognizes it and everything goes smoothly until I click on PDA and try to locate the recovery file to flash cwm. I am running Widows 8 consumer preview and have had no other problems with it thus far except for finding the file. Any ideas? It doesn't matter how I extract the file, my comp will not find the file so I cannot achieve root.
UPDATE: So apparently you cannot use Odin from the Windows 8 Consumer Preview because it does not play nice with Windows Explorer to locate the recovery .tar file to flash CWM. All is well though, I used another laptop running Windows 7 and everything is good and now I can proceed with Flashing CM9
What file are you extracting?
Also to help you further what guide are you following?
I suggest the one in my signature by S0ckM0nk3y.
Edit: I figure you can't find this 'recovery.tar.md5" file. Which you want to use with Odin.
I also just noticed you were using Win 8 So I'm out of my comfort zone trying to help much.
Sorry for the interruption of your post.
no apology necessary, I appreciate any help I can get or any suggestions. I am going to try on a friends computer that is on Windows 7 and see if odin will be able to see the file that way, if not, i guess i am SOL. Here's hopin'
It's just my thinking but don't you tell the program you unzip with "where" to unzip to?
If so, can't you just remember that "place" when Odin pops up with a box to select a file and use "that place" you told it to unzip to?
Again sorry if I'm way off here, as I don't know what you are using to unzip the files. Just seems strange to me.
I do know that's exactly how it works in Win 7 with just about any prog you choose to unzip with you can tell it where so it's easy to find it from Odin.
In any case. Best of luck.
Yeah that is normally how it works with unzipping the file and then locating iit normally, and thats what I was doing, however Odin apparnetly does bot play nice with Windows 8 explorer when it comes to locating files. I just finished rooting the tab, but I had to do it from a windows 7 laptop instead of my windows 8. Whatever, i am happy and I appreciate you taking the time to throw something out there. I guess now I should update the first post as solved....sort of
Related
When I try to reinstall the firmware it will not work. I get a message update failed: (1). This is done in the recovery section. I have put the latest firmware in, but nothing happens other then the error message. When I turn on the Archos it just goes straight to the Archos A70S Recovery screen. I have totally reformatted the device several times. Any thoughts on this board? Thanks.
Aaron
Try to format the device and then install the firmware, also, make sure to have the right firmware so the archos stock .aos file and not the SDE firmware .aos file
have you tried redownloading the archos firmware again? maybe the download got corrupted?
Also try running the repair tools under recovery: specifically Check Disk?
do you have a (1) at the end of the aos file? "sdqsqdfkqsdomij(1).aos" like Firefox do, i had the same error like that
Thanks...but I think I have tried it all...no luck
Try using a different browser, like IE to download it.
I've got the same thing going on. Was trying to re-partition the app space and something didn't work for the 4th time. So I removed Android and the SDE and now I can't get it to boot. My problem is that I was running windows, not sure what you were using, and I changed the recovery location's format. So every time I go to load the file the archos will format the partition then windows says it will not read and formats the partition... I move the file and try to start the reload only to fail.
I'm going to run ADB hopefully tomorrow. I hardly know what I'm doing, but don't really care if I break it! Just playing around but if anyone has any ideas let me know!
If you removed sde and android, there is nothing to boot from.
You then have to go into the recovery, format the device from there and then restore the orginal Android by transfering the aos file from arcos.
Yeah, I might have done that 10 times. That is when the archos reformats itself to something and then windows can't read the drive.
After you have transfered the AOS File to the device and it installs the Archos Android
it reformats the device to something?
I think that the archos is formatting to ext3 but windows can't read it, so windows then formats to whatever and I move the file, then hit ok on archos and you get failed message.
I know that AOS files work because I have already used them once.
If any of you guys give up on trying to get life into your bricked gen8 devices, then shoot me a message... I might be interested in buying the device from you.
Have you tried tried to fully charge it before installing? I had that same problem and it got fixed by fully charging the device first.
Full charge and plugged in as we speak.
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Ha! 393 posts and your only kind of a ****? Thanks!
All kidding aside It's not easy to describe whats going on, and I wasn't trying to hijack this thread but I think the original poster is way gone. I was only trying to say I had the same problem and was going to try a few things to get it working again, but this was only yesterday and I have not had luck. I never really even asked for help but appreciate everyones input.
So... Let me start again!
Archos 101.
Long ago I had Urik Droid 1.0 installed but it had since been removed. Before I messed everything up i had the latest Archos update and rooted. I was trying to create a large partition for apps and had just edited the init.rc and rebooted. Somewhere here I messed up! Boot loops start and I'm into recovery.
Recovery shows everything normal, but I'm unable to update archos via AOS file. So I totally reformat and remove SDE in an attempt to just start fresh. This is not the case and I figured it wouldn't be.
As I described before, using windows, in archos recovery this is what is displayed.
Archos A101IT Recovery
Would you like to recover system?
NO
REBOOT
UPDATE FIRMWARE
REPAIR SYSTEM
FORMAT SYSTEM
If you select updated firmware the archos will reformat to ext3. It then says USB connection: Press OK to disconnect. Windows then says that it is unable to use the disk and asks to re-format. I did, because I don't think I can do anything else, moved the AOS file over and hit ok. Update failed (1).
So today I installed linux in an attempt to move ext3 to ext3. I did get the file transfered and my archos even said plug into dc power. I did and waited... Update Failed (206). Not sure what this one is!
And that's really all I know. I can't even get the last thing I described to come up again. But I have all week on vacation.
And lastly I would like to thank you for the help
And I just got the AOS to install! Formated repair to Vfat, used repair option and moved AOS into archos. For whatever reason this time it worked. Rebooted and android just started up. Don't know if everything works yet but we will see!
Funny, you do the mistake and call others names.
fzelle said:
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Click to expand...
Click to collapse
Let me make this clear...
I was kidding. Take a deep breath, relax and please try to help someone else if that is what you are on here to do.
I'm pretty sure what you said to me was worst then my little joke. It was hardly clever and I'm ok with it as it did make me laugh a little.
I didn't ask for your help.
I didn't need your help
You didn't help.
And I'm ok with it even if you are not.
I'm going fishing now. Good day everyone.
No, it was exactly what you needed, as before my message you didn't tell us what was happening on your side.
Please read what you have posted before and check yourself if you would be able to get any sence from that.
It is funny how some people handle kritik.
I have been able to get the update tool software to flash the kdz file and I over right the bin in the process.
The phone flashes fine. But, after flashing I still have no root at all. I'm following every step by step instruction.
dismantlehands said:
I'm so happy that the Lelus Root method works. But, not for me. I have no other machine to use this method on that does not run windows 8.
When I attempt to put the phone in Software update mode when trying to flash the kdz file, windows 8 crashes because of driver issues. Has anyone else had this issue? Or could maybe point me in the right direction into fixing this so i can obtain root for my L9? :highfive: Team work guys, team work. *self five*
Click to expand...
Click to collapse
Works perfect on Windows 8. Mine too and one more user confirmed it before me.
Not even this, Since 5000+ years for hair growing medicine also, they always said "RESULTS MAY VARY" lolz
hey, listen! lol
cmahendra said:
Works perfect on Windows 8. Mine too and one more user confirmed it before me.
Not even this, Since 5000+ years for hair growing medicine also, they always said "RESULTS MAY VARY" lolz
Click to expand...
Click to collapse
Just sent you a pm asking about this issue. Sorry for not having any patience.
since that is the case, im even more confused now than ever.
I have tried uninstalling drivers and everything, still crashes. Fresh install is not an option seeing I have no way to backup my data.
dismantlehands said:
Just sent you a pm asking about this issue. Sorry for not having any patience.
since that is the case, im even more confused now than ever.
I have tried uninstalling drivers and everything, still crashes. Fresh install is not an option seeing I have no way to backup my data.
Click to expand...
Click to collapse
Not sure the situation of your window 8 and no one can help you without proper details, but my friend, in my humble opinion your title "[Q] Lelus root method crashes windows 8" is sort of misleading and may be scaring people from using Lelus method. It sounds like you are telling people that "Lelus root method crashes windows 8, so dont use it."
Make it "[Q] Please help! Why Lelus root method is not working on my windows 8?" to be more precise.
Are sure your clicking the network test flash button? Do not click the start button right under the kdz browser folder thing. There should be a button on the lower right hand. Also run the prgram in compatibility as administrator.
Virusbetax said:
Are sure your clicking the network test flash button? Do not click the start button right under the kdz browser folder thing. There should be a button on the lower right hand. Also run the program in compatibility as administrator.
Click to expand...
Click to collapse
+1 good point. You are talking about this http://forum.xda-developers.com/showpost.php?p=38914794&postcount=117
Virusbetax said:
Are sure your clicking the network test flash button? Do not click the start button right under the kdz browser folder thing. There should be a button on the lower right hand. Also run the prgram in compatibility as administrator.
Click to expand...
Click to collapse
My laptop crashes right after it tries to detect the L9 running in SW mode. So, I do not even get as far as the program it self.
I appreciate the input Virusbetax.
dismantlehands said:
My laptop crashes right after it tries to detect the L9 running in SW mode. So, I do not even get as far as the program it self.
I appreciate the input Virusbetax.
Click to expand...
Click to collapse
my win8 laptop has a few runtime errors during the flashing process itself, and I have to reboot afterwards, but never something as bad as this. you may be experiencing other problems not related to this phone.
may not be the BEST solution but you could always download tinyXP and virutalbox and try everything in a virtual machine..........
Yea there also virtual xp you can use. I believe is from windows website. Try with cousins or friends computer? Maybe theres will work.
Re: [Q] Lelus root method crashes windows 8
Have you tried other cables? Have you used the other usb ports on your system? Have you checked device manager on your laptop to see if there are other devices with errors? Have you gone to your manufactures Web site to see if there are new drivers or an updated bios?
Sent from my LG-P769 using xda premium
psychoace said:
Have you tried other cables? Have you used the other usb ports on your system? Have you checked device manager on your laptop to see if there are other devices with errors? Have you gone to your manufactures Web site to see if there are new drivers or an updated bios?
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
Switching it from the usb 3.0 port to the 2.0 port worked. I successfully got the phone in s/w mode to run with the software update tool. After the tool finishes my phone reboots. Still no root..... I am following every step....
Its all Security and Compatibility issue. Yesterday, I have done some changes in my Root Guide.
======================
2) Download Root_and_Flash_Guide_byCMahendra(date).zip file (attached with this post) and extract in your C-Drive.
Now you will get three folders named "C:\RootLelus" and "C:\RootFlash" and "C:\shttps"
If these folders need any permissions you should provide in folder security section by adding user "everyone" or "<yourname>" and give full access. (example video) This is Optional and should be done if you have permission errors while flashing. Do it for all three folders.
==================
Also run EXE files with WindowsXP compatibility mode and Run As Administrator, if any trouble. In fact I never did this. Just a suggested workaround.
STILL NOTHING IS GUARANTEED AND MAY NOT WORK FOR YOU.
Do some trial and error and you tell us.:good:
cmahendra said:
Its all Security and Compatibility issue. Yesterday, I have done some changes in my Root Guide.
======================
2) Download Root_and_Flash_Guide_byCMahendra(date).zip file (attached with this post) and extract in your C-Drive.
Now you will get three folders named "C:\RootLelus" and "C:\RootFlash" and "C:\shttps"
If these folders need any permissions you should provide in folder security section by adding user "everyone" or "<yourname>" and give full access. (example video) This is Optional and should be done if you have permission errors while flashing. Do it for all three folders.
==================
Also run EXE files with WindowsXP compatibility mode and Run As Administrator, if any trouble. In fact I never did this. Just a suggested workaround.
STILL NOTHING IS GUARANTEED AND MAY NOT WORK FOR YOU.
Do some trial and error and you tell us.:good:
Click to expand...
Click to collapse
The 7th try i had to run every single exe in administrator mode. So, for me. His updated method did indeed work for me. Thanks dude.
dismantlehands said:
The 7th try i had to run every single exe in administrator mode. So, for me. His updated method did indeed work for me. Thanks dude.
Click to expand...
Click to collapse
Glad it helped.
Hello,
It's been awhile since I messed with my phones so excuse the noobish question/dilemma here.
I lost(deleted) a video file that I thought I had backed up already....it did not. File recovery apps aren't doing the job so I want to try one of the more robust (I think) PC versions of a file recovery program on my S4.
Problem is, I can't make my phone appear as a drive on my computer like I swear I used to.....I don't know if it's Windows10 or what but it comes up as a "Portable Device" and my file recovery programs won't pick that up as an option to scan....ANY IDEAS folks???
Any guidance would be much appreciated!
Holy moly, no one???
Hi all, feeling somewhat frustrated, as all the posts I can find for P9000 require Windows to flash updated ROMs, Im looking to install 0315 (Ive got 0304 but need the Native FP API installed) but I run Mac and Linux so trying to figure out how to install the zip file? Anyone got any help?
Have a look here:
http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802
I did have a go on my laptop running arch linux but got an error with the scatter file so ended up doing it on a windows machine. However I have since seen this post on the Elephone forums:
Open the scatter in a editor and check the first bytes.
Ift there is anything before the "###" just delete and try again.
Click to expand...
Click to collapse
here is the thread:
http://bbs.elephone.hk/thread-9967-1-1.html#.VwaEa6QrKUk
Good luck
UPDATE: solved. ( https://forum.xda-developers.com/showpost.php?p=72427580&postcount=5 )
First off, I should say that I really don't know what I'm doing. I'm learning as I go along.
I bought this phone under the impression that flashing to a non-US firmware is the easiest thing in the world. Now a few weeks have passed and I still haven't been able to do it. Having a Mac was confusing at first, trying to figure out how to tweak the directions. Then this file script error, which seems to have popped up as a problem for everyone.
So, from what I can tell, I need to go download my desired firmware from XperiFirm. Then I need to go into the Flashtool folders, find the Devices folder, find the folder for F53XX (X Compact), copy the .fsc, and add it to the firmware I downloaded. Then I create the bundle in Flashtool, and flash the phone.
That's my first issue. I need to know from someone who knows about this whether or not I've got that right.
Now the second issue.
I've done those things. Because I don't really know what I'm doing, I haven't felt like risking the phone. (Even without the fingerprint scanner, I do really like this phone quite a bit. But typing the password is annoying as hell, and I don't quite feel my phone is secure with the other options, such as facial recognition.) After doing the steps I listed, I ran a simulation. It seems to have gone well. But, unfortunately, I don't know what any of it means. You can find the transcript of the simulation here: https://forum.xda-developers.com/showpost.php?p=72371001&postcount=7
My concern, overall, is that the .fsc file is labelled 34, whereas the firmware is 34.2. Does this matter? Does the transcript look ok? Should I go ahead and flash the phone?
Thanks in advance for helping an interloper who has no clue about any of this.
i think you just need to use that 34.fsc anf go for it.
here's why:
I was poking around the creator of flashtools update log here:
https://github.com/Androxyde/devices/commits/master
goto the commits for Jan 22 on Xperia X Fsc (F5321). (https://github.com/Androxyde/devices/commit/7bd7d4060c2777a8061daef3e738ecc075ee8f0c )
Inside read how he renames 34.2.xx.fsc to 34.fsc. I think its a typo and should have been 34.2.fsc.
Here's why:
I went to the one below on master page which is for my Xperia X (F5121), notice he changed 34.2.xx.fsc to 34.2.fsc (https://github.com/Androxyde/devices/commit/f52bbaeb1d5be96b01e49b5e579aefc6d5a3c9df)
I used 34.2 already to go to UK 34.2.A.2.47 and then again on CE1 34.2.A.2.69. Worked fine both times...
Just go for it man. Flash da phone!
Haven't read your log, because like you, it won't say much to me.
What I know however is this:
- Yesterday I flashed my brand new Xc that came with 34.2.A.0.311 directly to UK 34.2.A.2.69.
- I was prompted to use 34.fsc had no 34.2 or other option, just 34.
- Works like a charm.
The issue I DID HAVE was when I downloaded the firmware first and then installed FlashTool, that I didn't get the .FSC message at first. I had to uninstall everything (on WIN 10) including deleting all the folders left after installation, to get a clean slate (for Xperi and FlashTool). I hope this helps, although I can't really tell you how to delete left overs from macOS.
After doing this I got the holy .FSC message and went on to flash.
Good luck.
You do not need to add anything manually! Flashtool should ask you to include the 34.fsc file into the .ftf automatically when it creates it after closing xperifirm when the firmware bits have been downloaded. You can add it manually to the .ftf file after flashtool created it, but there is no need to. Because even if its missing from the .ftf file, flashtool should pick it up again automatically from the installation folder and use it. If you do not get the message to include/use it, you need to reinstall the latest version of flashtool (deleting all folders first) as said above.
Oh and the creation of the .ftf first starts when you close xperifirm after download! flashtool will then then put the .ftf together and its in this step it should prompt you to include 34.fsc to the ftf. The .ftf is just a masked zip file btw.
thegumptiontrap said:
So, from what I can tell, I need to go download my desired firmware from XperiFirm. Then I need to go into the Flashtool folders, find the Devices folder, find the folder for F53XX (X Compact), copy the .fsc, and add it to the firmware I downloaded. Then I create the bundle in Flashtool, and flash the phone.
Click to expand...
Click to collapse
Update:
I finally went ahead and did exactly the steps outlined above, and it worked. I used the 34.fsc from the F53XX folder, in the Devices folder.
If anyone on a Mac is trying to do this, know that it worked perfectly for me. For me. I'm no expert. I don't know what I'm doing. I just know that it worked.
If you're on a Mac you'll need to download XperiFirm separately from Flashtool, download a program called Mono, and open XperiFirm in Terminal by typing (without quotes) "mono /XperiFirm.exe". I believe you'll need to do this as the root user. You should also know that for some odd reason it seems that all programs need to be closed and XperiFirm needs to be clicked on and the only program running while the files download and unpack. A user on Reddit helped me with this when I failed to get the firmwares to unpack successfully multiple times.
You also, as far as I know, need to delete the fwinfo.xml file from the bundle before creating the bundle in Flashtool. This video tells you what you need to do overall, minus the newer issues that I dealt with: https://www.youtube.com/watch?v=gKKRznRWWso&feature=youtu.be
Reading through this thread here, and my thread on Reddit, should give anyone using a Mac a good idea of what you need to do at each step. And, probably, the likely problems you'll face when attempting it. The Reddit thread: https://www.reddit.com/r/SonyXperia/comments/6bp1vy/xperifirm_problems_on_applemac/
tl;dr: (but, seriously, do go ahead and read everything before attempting this)
Download Flashtool. Download Mono. Download XperiFirm. Open mono by typing mono /XperiFirm.exe in Terminal while signed in as root user. Download your desired firmware. (I went with Customized UK.) Go into Terminal and change the setting so that you can see all program files. (You can see how to do this in the linked Reddit thread.) go to users/(your username)/flashtool/devices/F53XX and copy the 34.fsc file. Put the copy in your recently downloaded firmware file. Delete the fwinfo.xml file. Follow the rest of the directions in the youtube video linked to above.
And remember that I don't know what I'm doing, learned all of this while doing it, and made sure to do it within my return window. It worked for me, but that doesn't mean it will work for you.
thegumptiontrap said:
Update:
I finally went ahead and did exactly the steps outlined above, and it worked. I used the 34.fsc from the F53XX folder, in the Devices folder.
If anyone on a Mac is trying to do this, know that it worked perfectly for me. For me. I'm no expert. I don't know what I'm doing. I just know that it worked.
If you're on a Mac you'll need to download XperiFirm separately from Flashtool, download a program called Mono, and open XperiFirm in Terminal by typing (without quotes) "mono /XperiFirm.exe". I believe you'll need to do this as the root user. You should also know that for some odd reason it seems that all programs need to be closed and XperiFirm needs to be clicked on and the only program running while the files download and unpack. A user on Reddit helped me with this when I failed to get the firmwares to unpack successfully multiple times.
You also, as far as I know, need to delete the fwinfo.xml file from the bundle before creating the bundle in Flashtool. This video tells you what you need to do overall, minus the newer issues that I dealt with: https://www.youtube.com/watch?v=gKKRznRWWso&feature=youtu.be
Reading through this thread here, and my thread on Reddit, should give anyone using a Mac a good idea of what you need to do at each step. And, probably, the likely problems you'll face when attempting it. The Reddit thread: https://www.reddit.com/r/SonyXperia/comments/6bp1vy/xperifirm_problems_on_applemac/
tl;dr: (but, seriously, do go ahead and read everything before attempting this)
Download Flashtool. Download Mono. Download XperiFirm. Open mono by typing mono /XperiFirm.exe in Terminal while signed in as root user. Download your desired firmware. (I went with Customized UK.) Go into Terminal and change the setting so that you can see all program files. (You can see how to do this in the linked Reddit thread.) go to users/(your username)/flashtool/devices/F53XX and copy the 34.fsc file. Put the copy in your recently downloaded firmware file. Delete the fwinfo.xml file. Follow the rest of the directions in the youtube video linked to above.
And remember that I don't know what I'm doing, learned all of this while doing it, and made sure to do it within my return window. It worked for me, but that doesn't mean it will work for you.
Click to expand...
Click to collapse
concrats you only learn by doing and sometimes failing , flashtool is basically 'idiot' proof. You do not need to delete fwinfo.xml file, flashtool will filter it and any dangerous .ta files out from flashing.
But I do see things are different on mac. Odd that you cant start xperifirm from inside flashtool. When did it create the actual .ftf then? When you closed xperifirm? If that's the case I see the problem with flashtool not propting you to include 34.fsc. But if flashtool compiles it and puts it in the */.flashtool/firmwares folder there should be no need to copy it manually it should prompt you, and as said if missing at flash time it should also automatically pick it up from the users/(your username)/flashtool/devices/F53XX folder since flashtool already knows the model of your phone when you connect it. everything should be pretty much automatically (yes/no prompt) with no need to copy or delete any files.. that was only needed many flashtool versions ago.
---------- Post added at 19:06 ---------- Previous post was at 18:30 ----------
Reading up on mono for mac I have a feeling why you needed it for xperifirm. thanks for sharing the info!
realtuxen said:
concrats you only learn by doing and sometimes failing , flashtool is basically 'idiot' proof. You do not need to delete fwinfo.xml file, flashtool will filter it and any dangerous .ta files out from flashing.
But I do see things are different on mac. Odd that you cant start xperifirm from inside flashtool. When did it create the actual .ftf then? When you closed xperifirm? If that's the case I see the problem with flashtool not propting you to include 34.fsc. But if flashtool compiles it and puts it in the */.flashtool/firmwares folder there should be no need to copy it manually it should prompt you, and as said if missing at flash time it should also automatically pick it up from the users/(your username)/flashtool/devices/F53XX folder since flashtool already knows the model of your phone when you connect it. everything should be pretty much automatically (yes/no prompt) with no need to copy or delete any files.. that was only needed many flashtool versions ago.
---------- Post added at 19:06 ---------- Previous post was at 18:30 ----------
Reading up on mono for mac I have a feeling why you needed it for xperifirm. thanks for sharing the info!
Click to expand...
Click to collapse
From what I was able to find, through a lot of Googling, Flashtool runs quite a bit differently on an Apple/Mac. I was never prompted at all, and I wasn't able to find any settings or preferences menu inside of Flashtool. That YouTube video I linked to shows pretty clearly the issue with XperiFirm. That's one video I was glad I found early on, as I kept getting some kind of error message each time I tried to open XperiFirm in Flashtool. With regard to the deletion of the .xml file, I got that from the video. He explains how to download the firmware separately and then create the bundle in Flashtool. He instructs you to delete fwinfo.xml. I honestly have no idea if it matters or not. I just deleted per those instructions. I do know that I attempted the flash many times before manually copying that .fsc, and it failed each time with a no file script error. There was never any prompt or option to add it.
Mono, from what I know, is just a program that allows you to run certain Windows executable files on a Mac. XperiFirm seems only to be available as a .exe.
thegumptiontrap said:
From what I was able to find, through a lot of Googling, Flashtool runs quite a bit differently on an Apple/Mac. I was never prompted at all, and I wasn't able to find any settings or preferences menu inside of Flashtool. That YouTube video I linked to shows pretty clearly the issue with XperiFirm. That's one video I was glad I found early on, as I kept getting some kind of error message each time I tried to open XperiFirm in Flashtool. With regard to the deletion of the .xml file, I got that from the video. He explains how to download the firmware separately and then create the bundle in Flashtool. He instructs you to delete fwinfo.xml. I honestly have no idea if it matters or not. I just deleted per those instructions. I do know that I attempted the flash many times before manually copying that .fsc, and it failed each time with a no file script error. There was never any prompt or option to add it.
Mono, from what I know, is just a program that allows you to run certain Windows executable files on a Mac. XperiFirm seems only to be available as a .exe.
Click to expand...
Click to collapse
Ok. Still flashtool should use the 34.ftf you copied from the devices folder at flash time if missing, but surely I'm not to say what it did And ofcause it's neater to have it included in the ftf. I'm almost certain you do not need to remove fwinfo.xml it's old remisants from earlier versions of flashtool some also still say to delete certain .ta files because they are harmful. That's not needed either as; yes they are included in the ftf firmware file and are potentially harmful. But flashtool will filter them out at flash to be safe, that is what it uses 34.fsc for and why it refuses to flash without it (to be safe).
I understand why you deleted fwinfo.xml if uncertain and included 34.fsc if you never got prompted even at flash., you kinda need to then. heh
And yeah since xperifirm is in visualbasic and apparently not included as *nix native, you need mono. I honestly thought flashtool included a more friendly solution in the package.
Edit: thanks again its always nice when people include how they got it working.
realtuxen said:
Edit: thanks again its always nice when people include how they got it working.
Click to expand...
Click to collapse
No problem. I wan't even really arguing anything before. Just stating the steps I went through and what I found along the way. I have a slightly better understanding of how this all works now, but I'm still barely comprehending any of it. I just hope my trial and error here will be able to help a few people trying to get this sorted out on a Mac. And even then, a lot of the info came from the person who was helping me in that Reddit thread.
thegumptiontrap said:
No problem. I wan't even really arguing anything before. Just stating the steps I went through and what I found along the way. I have a slightly better understanding of how this all works now, but I'm still barely comprehending any of it. I just hope my trial and error here will be able to help a few people trying to get this sorted out on a Mac. And even then, a lot of the info came from the person who was helping me in that Reddit thread.
Click to expand...
Click to collapse
Me niether I am not trying to dictate anything as I have never even used flashtool on a mac. I was also only trying to explain how flashtool usually work in relation to xperifirm which could not be applied. And also how flashtool works and why it needs a fsc script to filter out potentially dangerous files such as simlocks etc. from the firmware package.
Some time ago we needed to make sure we deleted or excluded certian files manually along with fwinfo.xml, since we do not need thst anymore, I think it filters fwinfo.xml out to by the fsc script. flashtool is pretty safe to use now that it also uses fsc scripts and refuses to flash if it is missing (it's my understanding they are provided to flash as precise/safe as sonys update tool would do it)
I myself remember how confused and nervous I was using flashtool the first time years ago lol I also used reading and trial and error. And I also remember my first bad flash, it almost gave me a heart attack lol. But then again by trial and error and reading again I also found out it was not very hard to recover.
I am sure other people can use your guide, and I personally also learnt something. After all sharing info is what the forum is supposed to be about. Hehe
It's not always good to do forum talk while on public transportation on a phone, at least not if you are old and not comfortable using it for such things, or watching youtube without headphones because it is not appropriate.
Just came back here re-reading your first post and on again and I do see that I was in my own head and over complicated some things rather than go to the point of what you actually asked, as you were right on the money in the very first post, if flashtool does not prompt you to include or use a .fsc script you can add it maually. And I could also have told you that 34.fsc is good since I used it to update may security patch. Sorry man, I feel all bad now. Though you did it sorted after getting tired of listening to 'how things are supposed to work'