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'
Related
Hello.
This is my first post so first off I would like to say thank you to the members of XDA because I have been helped a great deal in the past by simply reading some of the posts on this forum.
That being said, I have a problem that I could not find the answer to after hours of searching.
I am trying to Debrand/Root my Rogers X10a using the Exploid method
forum.xda-developers.com/showthread.php?p=7490733#post7490733
After I enter my Device ID into the appropriate file, I ran RootX10a_v2.cmd as instructed. However, once I try to run step 1 i get the following message:
"unable to access jarfile X10flash.jar"
Ive tried connecting the phone in flash mode to different USB ports and using different Device IDs however nothing has worked.
Any ideas?
Any help will be greatly appreciated.
Thanks!
I have just the thing for you matey. I can't post a link sorry but google search for Universal Androot and download and install it on your phone.
It allows to you 1 click root or unroot your device without any fuss and should allow you to root it when 2.1 is released as it contains the superuser files for 1.5 / 1.6 and 2.0 - 2.2.
I am using it and it works brilliantly. Hope this helps
Sent from my rooted .26 x10i using the XDA app
Welcome to xda! the answer is in the forum but i can't remember where.
Set up the path to the sdk tools in your environment variables.
Cheers
Gav
Thanks for the responses.
steve- are you sure that the universal androot works with the x10? another concern is that i also wanted to debrand my phone to get rid of rogers bloatware so how would I solve that issue if I can't access the x10flash.jar?
gavriel- sorry. could you explain in a little more detail what you said? i don't quite understand what you mean.
Thanks!
The one click root seems simple enough.
My problem now is with debranding.
Ive tried the method where you switch the files in SEUS (ive also tried PC Companion) just before it installs onto your phone and that has not worked. It says every time that the installation has failed.
Does anyone have any other ideas as to how I can debrand my phone?
Thanks!
For sure. I may be wrong but ill explain it as I understand it.
Basically when your PC is trying to use a jar file it looks in a particular area. I'm not sure where it looks though. Obviously your jar file isn't in that directory or you wouldn't get that error. So, by adding it as an environment variable it will look in the directory u added for that file.
The environment variables is found somewhere in the system settings. I can't remember where. Once you have found it you should find the path to the jar you are trying to access. Copy that path and paste it and the end of the environment variables. Don't erase anything that's in there. If need be seperate that path from the one before with a ; (semicolon). Save it and try running the jar again. It should work.
Good luck and hopefully it helps.
bmalaklou said:
After I enter my Device ID into the appropriate file, I ran RootX10a_v2.cmd as instructed. However, once I try to run step 1 i get the following message:
"unable to access jarfile X10flash.jar"
Click to expand...
Click to collapse
It means that Java can't find the X10flash.jar file. Do you have that file in the same directory as DeviceID.txt? Also, do you have the latest version of 32-bit Java installed?
To solve my debranding problems I had to use the 32 bit update 20, not 21 (which is the latest) and you need the jdk and the jre, hope that helps
Sent from my X10a using XDA App
I'm a complete noob and I've searched the forums and can't find an answer to my questions. (I'm sure there's some answer in Japanese on a Japanese forum somewhere, but my Japanese is not up to that level.)
I have a Toshiba Regza IS04 from AU (in Japan).
Running Android 2.2.2
Baseband Version 5014.1907.39
Kernel Version 2.6.32.9-rel [email protected] #1
Build Number FFK300
I have been researching rooting on and off for months since I first got the phone and have decided I would like to root it. My reasons for rooting:
1. I want to get rid of all the apps that were pre-installed that I don't use.
2. I would like to have the latest version of Android 4.0 Ice Cream Sandwich. (I doubt that another authorized upgrade from au is ever going to happen, since the 2.1 to 2.2 upgrade.)
It seems from reading forums that there are special builds of an OS depending on the phone?
My questions:
1. What is the best way to backup my phone before rooting?
2. What would be the best rooting method for my phone (SuperOneClick?)?
3. How can I (or even can I) upgrade my Android to 4.0?
Thanks for any help!!
Sam
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Thank you so much for this response!
I have the same phone, and I've been wanting to root it for a long time. There were so many pre-installed applications that are just hogging room, especially since I can't read Japanese well enough (yet).
-T
I hope it works for you too!
I spent probably the equivalent of 2-3 days searching over the last few weeks, but couldn't find anything that I was comfortable with trying.
This morning, I finally got the nerve up to try superoneclick and was really disappointed when it wouldn't work. Then I started trying all kinds of methods, and about 8 hours later finally came across the method that worked!
It's probably the only thing frustrating sometimes about having a Japanese phone: lack of English support!
Now I'm just hoping I don't break it! I'm backing up all the apps with Titanium backup before I start deleting them one by one. I would hate to delete something that is crucial to the system and not be able to restore it. I'm also looking into other ways to backup the system.
One word of warning. Your au one market will not work unless you do one more step. It's mentioned in English in the readme file. I didn't bother because I never download from it anyway. (Although, I probably should just so I'll keep getting updates on some of the J apps that I do have.)
Deleted
Deleted
the rootkit d/l has been removed. anyone know where to get it?
The File
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
link die;
anyone help me another link for that file & help me root this device step by step?
Thanks
The post above dissolution said they had one, but good luck getting a reply. I'm emailed twice and nothing.
私はローボーボブ。 Haro！！
Latest rootkit for FFK300
Here is the latest rootkit,
IS04 root toolkit ver 4.0.1
http://www1.axfc.net/uploader/Ne/so/131631
DL key ; is04
And other informations;
- Custom kernel(overclock, compcache, +others)
http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=visit&cid=9&lid=47
- Custom kernel(CWM on ramdisk, ported from Xperia, modUI)
http://www.mediafire.com/?jkz5nek59y3hpaf (reported kernel unstable)
# FFK301 stock ROM update - (rootkit does not work, still can be rooted.)
http://spf.fmworld.net/sw_update/kddi/is04/update/
- scroll to bottom and click on blue rectangle.
# kernel source code
http://spf.fmworld.net/oss/is04f/index.html
- some files are missing, extract them from T-01C(DoCoMo).
http://www.fmworld.net/product/phone/sp/android/develop/t-01c_froyo_oss/
help! rooting regza inquiry..
[/COLOR]
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
hi!
I am a newbie here and like you all, I would also like to root my regza phone. Can someone give a working auto_rootkit because the link above is not working. I have searched it as well on the net but still all will lead me to dead hotfile link. Or someone could send me the file instead to my yahoo mail [email protected] tnx in advance
And also i have downloaded this rootkit instead from IS04 and downloaded. After dowloading, I click the adb file and it appears a command screen with commands running so fast. Next i did click the root file and there appeared a command screen with all sorts of command running so fast. My question is, i did not received any confirmation that the rooting process was succesfull. And also i have read to other forums that one thing you will notice that rooting was successfull is that 'superuser" will be automatically installed.
Please help me on this one. To be honest I started exploring this process since i have this phone and there are apps that i wanted to uninstall not unless i root the phone.
Thank you in advance
marvz,
Dissolution said:
I'm not sure if this is against the forum rules, but I have a copy of the zip file (well, a zipped up copy of the folder) from my computer. If you pm me, and I can send you it.
-T
Click to expand...
Click to collapse
hi there!
Can you send to my e-mail [email protected] the said file so that i could root my regza phone?
thank you for your help> ^_^
Question to get root on phone regza
samkk75 said:
To answer my own question, in case any one else wants to know:
Okay... it looks like I cannot post external links... until I post 8 times, which I don't really predict doing... so I'm going to try just removing the http at the beginning and see if it will go.
Superoneclick v2.2 does NOT work with this phone. It gets through "Rooting device... Step #7" but cannot remount.
Unrevoked does not work.
Z4root also does not work.
But I found a Japanese site with directions that did work! YES!!
hibari.2ch.net/test/read.cgi/smartphone/1320415141/
Somewhere in the page was the following information and link:
■auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
Some of the Japanese threads were saying something about the problem with superoneclick was that the is04 took too long to mount and so there was an error. At least, I think that's what it said. My Japanese is okay, but not always good enough for this type of stuff.
I hope this can help someone else.
Click to expand...
Click to collapse
Hi
I have this phone too. And I try to get root, you can send for me the link of you downloaded and explain for me how you made it.
Other question, I can use this phone to call in brasil?
Thank you.
:good:
My phone just had this phone and I'm trying to update it before rooting. It came with 2.1-update 1 OS version and I'm trying to update the phone to it's latest official 2.2.2.
I've downloaded the necessary 256mb file update but it didn't work. Even tried using the recovery but is still not working.
Based on my research about this phone, There's no way to update without the phone downloading the app from the official website, using the SIM and au logins.
We've lost the sim (UIM) card that came with the phone. So I guess its stuck on its current OS. I'm having trouble installing apks (Gingerbreak and even normal apps) as it always gives me the error "parsing error" or something.
Is there anyone could help?
EDIT:
I have successfully updated the phone from Android 2.1-update1 to Android 2.2.2.
Download all the necessary files here:
http://www.fmworld.net/product/phone/is04/
I have used the method of updating from the least upgrade and up to the latest. I have managed to download 3 separate files for the upgrade, namely:
IS04_RC2_RC3RE_DL.zip
IS04_RC_4.zip
IS04_TO_SP_FYRC_4.zip <- froyo update
I have extracted all the files on the sd card. make sure that the ".enc" file is found on the root of the SD Card and on the "prg" folder.
I have updated it using the recovery mode (power + volume up + camera button).
I am now currently trying to Root the device using Gingerbreak and seems that it's taking too long to root.
Also. I have able to root the 2.1-update OS using z4root.
help me
hi.. i didn't my phone plz send me ...................................................auto_rootkit_is04_v0.5+suhax
hotfile.com/dl/134084004/f59084e/auto_rootkit_is04_v0.5suhax.zip.html
thnxx.. in advance..
Root
I rooted mine with http://unlockroot.com/
root_toolkit_is04_v4.3.zip
www1[dot]axfc[dot]net
/uploader/Ne/so/135399
Password is "is04".
suhax
www[dot]4shared[dot]com
/zip/pHLT8kqe/suhax.html
Sent from my IS04 using xda premium
more detail please
samkk75 said:
.....
I downloaded the zip file and extracted it. I clicked on adb.exe first and then clicked on the auto_rootkit_is04 batch file. I just hit enter after each step. (It's in Japanese, but all it says is each step it is doing and then to hit any key.)
The first time I ran it, it did not work. The second time, I turned my phone off and on again before trying anything, and bingo: I had root!
.....
.....
I hope this can help someone else.
Click to expand...
Click to collapse
Thx so much for your posts.
I am so glad to finally find someone with the same phone, the same problem and intentions
I do, however, need more info:
Did you extract the files into any particular folder? You obviously hooked up in de-bug mode, but did you command prompt anything?
I tried your steps but get nothing to 'hit enter' on. I have also tried the other (different version) toolkit.
You can IM me or email or post or come around and root my phone yourself - I will sell you my car, house, wife...
... as you can tell I am a little frustrated ...
lets just IM/email for now
Thx in advance,
Kaz
---------- Post added at 12:34 PM ---------- Previous post was at 12:29 PM ----------
orgia82 said:
I rooted mine with http:!!unlockroot*com/
Click to expand...
Click to collapse
Didn't get to try it - was too tied down with all the additional ^%$&#$ I had to download to get to it.
help
as everyone can see that link isnt working anymore,so im here asking someone whos still have it to upload :fingers-crossed: again．．．．
I'm trying to root my phone using the Lelus method. As far as I know, I'm following the instructions to the letter. When I get to the actual flashing step, using the ICS T-mobile rom, I get the same "Scheduled Server Maintenance" error that Kevev reported in the guide thread on the development forum. Apparently, he was able to successfully flash, but I don't see any information there as to how he got around the error. I have tried repeatedly and always come up with the same result. Since I can't post yet in a development forum, I have to ask the question here. I must be doing something wrong, but I don't have a clue. I ask your indulgence, and would appreciate any help you can give me.
bearymore said:
I'm trying to root my phone using the Lelus method. As far as I know, I'm following the instructions to the letter. When I get to the actual flashing step, using the ICS T-mobile rom, I get the same "Scheduled Server Maintenance" error that Kevev reported in the guide thread on the development forum. Apparently, he was able to successfully flash, but I don't see any information there as to how he got around the error. I have tried repeatedly and always come up with the same result. Since I can't post yet in a development forum, I have to ask the question here. I must be doing something wrong, but I don't have a clue. I ask your indulgence, and would appreciate any help you can give me.
Click to expand...
Click to collapse
Do you have shttp in C:? C:/shttp/shttp.exe. It must be exatct this way. I have this problem too....
Rixx666 said:
Do you have shttp in C:? C:/shttp/shttp.exe. It must be exatct this way. I have this problem too....
Click to expand...
Click to collapse
I have it nested several directories deep. Did you get it to work when you put it in C? I'll give it a try.
bearymore said:
I have it nested several directories deep. Did you get it to work when you put it in C? I'll give it a try.
Click to expand...
Click to collapse
You get such hiccups if you dont follow the simple instruction first. Many people have habit to extract/save everything on desktop. C drive means C root location of C drive. And you must be logged in as "ADMINISTRATOR USER" on windows 7/8 to avoid access/permission issues.
cmahendra said:
You get such hiccups if you dont follow the simple instruction first. Many people have habit to extract/save everything on desktop. C drive means C root location of C drive. And you must be logged in as "ADMINISTRATOR USER" on windows 7/8 to avoid access/permission issues.
Click to expand...
Click to collapse
I'm used to Linux rather than Windows and when possible I put things in a user's home directory rather than the root directory. Since all that the instructions said was C drive, I interpreted that to mean anywhere on the C drive, not the root directory. Now that I put the program in the root directory, everything worked perfectly.
Thanks for your guide!
I just rooted my p769. I had a few hiccups.
Line 5a says optional, but really it's a necessary step if you've never done it once. If you've edited your HOSTS file and are running shttp, then it's not gonna be able to download/update what it needs to. Close shttp and rem out the lines in HOSTS until it updates, the continue as normal.
shttp has to be extracted in C:\
Mine ran from desktop but the 127.0.0.0:9002 test for the girls picture was file not found, look at shttp dialog window and you see it couldn't find the file because it wasn't where it expected it..
Also did you forget to right click and edit UpTestEX_mod2_marwin.exe compatibility tab if you're running win7/8 like it says to?
Once I set it all up according to the image in the thread and clicked "Normal web upgrade test" it gave me an error box. Saying to setup Tool > B2C Client Setup.
After that it was easy sailing. Well other than the fact that some of the KDZ/bin files were either missing, deleted or dropbox blocked the account for excessive use..
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
After trying for a few weeks now, I've still had no success. One idea has come to me though- installing a rom. Would downloading a custom ROM change my hosts file? Also, if so, could anyone recommend one that is similar to default android? One last idea that I've got at the moment is sonehow completely wiping the hard drive of the phone and reinstalling androud on it, though I have no idea whether that is even possible, and if so, how to do it. I would really appreciate some help here!
Thanks again,
Louis
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
J2270A said:
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
Click to expand...
Click to collapse
I'm not entirely sure I understand you here, but I'll try. What would unlocking the bootloader do to my phone? Would it enable r/w on the system folder? Also, what is a reflash of the system image? How would I do that?
I'll try these things if I can, but would still appreciate help.
Look around on http://wiki.cyanogenmod.org/w/Basic_concepts?
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
J2270A said:
Look around on [I can't post urls yet ]
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
Click to expand...
Click to collapse
Ok, so from what I can work out, cyanogen does not support my device. Would doing it for a similar device work? Are there any ROMs that support my device?
under the line, restoring the phone via the official ways actually just wipes the user data, not including the HOSTS file which is what I need to wipe. What I really need it is basically a ROM that completely wipes my phone and reinstalls some version of android.
Any other ideas?
While there may not be official support for a phone for a custom ROM, you may be able to find unofficial ports/versions if you search for it in the forums.
From what I know, a system reinstall via official methods wipes data and almost everything else, then downloads from its servers system files to be installed to the phone. At least, my phone was reverted to a stock ROM when I restored it after using a custom ROM. It may be different for some, but generally, this is what I think.
Important: only use a ROM made for your device model only, do not use the ones made for a similar phone, the small differences are no longer small in this case and will cause a system error(?)
Generally, once you have successfully unlocked boot loader using a method for your phone, the instructions afterwards are generally the same for all phones. You'll be able to get better answers in the threads specifically for your phone, so try to look for one and look for the already tried methods,
Here's one:
<You'll need to quote to copy link>
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Ish Takkar said:
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Click to expand...
Click to collapse
I have this problem with my S3 and I always delete the "hosts" file! I should find witch process make this file!!
Hello.
I was forced to reinstall firmware due to phone issues.
Now I'm again with root and TWRP.
Firmware is on nougat, version c900b300 but many files are missing.
In particular, themes cannot be applied even if I can download them.
I followed a procedure suggested for the Mate 8 but with no results.
Is someone able to help me?
I think this is not a post for q&a section.
Otherwise please move it.
Thanks.
Ah, even the ringtones folder is empty, but this is not a big issue...
Try these 2 methods
1 - https://forum.xda-developers.com/honor-6x/help/solved-huawei-gr5-2017-honor-6x-problem-t3606037
2 - https://forum.xda-developers.com/honor-6x/help/theme-issue-5-0-upgrade-t3579812/page2
First method pushed FM spk in data folder, I rebooted but no FM radio app shows up.
Regarding second method, Google drive file doesn't exist.
I hope to be able to install Oreo when available through TWRP.
Now I don't have the updater and I'm not receiving ota update from Huawei. Unfortunately I'm stuck with March security updates
Dammit, I'm out of ideas at the moment. Plus, i didn't knew that even updater was missing... You wanna try with an apk of mine extracted?
of course mate.
Now I'm more relaxed, as I understand that is better just playing with this phone. I'm not gonna put job related files anymore in, so if something happens, I can recover easily.
Baaaaaaaaad phone...
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Diamantes said:
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Click to expand...
Click to collapse
For Huawei bloatware it's surely a positive thing if you don't care, since that those results "well" radicated into system and aren't easy to remove. For all the rest, looks like you are on a firmware build that was created to another build, and so causes various incompatibilities... But it's the worst case that i saw, except bricking related cases maybe a rebranding to an other variant, with the flash of another firmware could solve at least the missing apps issue. Anyway, i uploaded the updater apk; after all i don't think it'll works sincerely neither making it a system app with apps or modules like systemizer, if all those issues are present already... But in the worst case here, you'll just get an install failure due to an apk version that doesn't match your first, initial build. Try for fun, i would say.
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
You can use apps like Link2SD, but if the file looks corrupt (had this problem too when i accidentally deleted compass app time ago) it means that doesn't matches your build number. You could try by installing a version that matches your actual build.
Diamantes said:
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
Click to expand...
Click to collapse
Yes, with dload method, you need to flash all files available in zip to get everything working, i tries this and everything worked for me without anything missing.
For flashing zip, yes it is PV files that can be flashed via Twrp
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Diamantes said:
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Click to expand...
Click to collapse
They are still getting it. Not sure how
Solution
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Will it work on honor 6x? The hw data is only for p9 ,isnt it?
starkeeper2018 said:
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Click to expand...
Click to collapse
Will it work on honor 6x..the hw data is showing only for honor p9 ,etc but not 6x