Related
I have spent days looking for threads so this neewb is about to break something. Well maybe not. I have my daughters Eris 2.1 and am trying to root it for her. I have tried several times with different methods. The issue is that I can get into recovery mode after every 1 click app but nothing I try will let me toggle to unzip to SD, or toggle to anything for that matter, volume wont do it and all track ball will do is let me select reboot. Man my DX was easy compared to the one click method.
HELP PLEASE,
If the trackball is having trouble scrolling, I'd install the trackball-optional custom recovery so you can use other buttons to scroll. There are instructions for doing this here:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
It sounds like you fall into "Scenario 2" which says you should follow the same method as "Scenario 1" to get rooted using the trackball-optional recovery.
I'll give it a shot, The help is much appreciated,
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
popfan said:
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
Click to expand...
Click to collapse
popfan,
I am not aware that any of the above links or files are missing... Can you point-out / tell me specifically which files you cannot access / download / link-to?
The root_part1 and root_part2 files are part of erisuser1's (bftb0's) Universal Root for Dummies! thread that I do reference in my AF thread, but these should still be up, active, and available.
So, I'm not sure if you are speaking about becoming rooted or installing a my trackball-optional custom recovery.
Let us know.
Cheers!
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
malloneem said:
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
Click to expand...
Click to collapse
LOL, sorry, didn't make/see the connection between your two posts .
Okay, let's try something new here...
Just a week or so ago, I re-packed jcase's 1-click rooting app to include my trackball-optional recovery image in lieu of the original recovery that his app includes.
So, let's have you re-root using the new 1-click app (all credit to jcase, both for his app and his threads both here http://forum.xda-developers.com/showthread.php?t=742228 and over at AF http://androidforums.com/eris-all-things-root/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html).
Since you've already used the 1-click app before, then all you'll have to do is grab my new "trackball-optional" version:
https://sites.google.com/site/scaryalienware/downloads/one-click-tbo.apk
MD5 sum: 15763b51cf707c027cc73bc117e1fc39
(the "tbo" in the name stands for "trackball optional" ).
Just follow the same process you did before while running the 1-click app and you should end-up with my trackball-optional recovery installed.
Let me know how it goes (you'll be the first besides me that I know of that has tried it; the user that I created it for to test has not yet responded, LOL).
Cheers!
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
popfan said:
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
Click to expand...
Click to collapse
Glad that jcase's repackaged app worked for you. I'll update my documentation to make this available to others.
Also, re. the above Megaupload link...it works just fine for me (from my PC and from my Droid X) and includes all of the aforementioned root_part1/2 files.
I think you've fallen prey to a truncated download, which is not uncommon with Megaupload in my experience. This is also why is important to double-check the file sizes and MD5 checksums of files that you download so that you know you got the whole-shebang; notice that erisuser1 did include the MD5 in his thread for this file:
- Download gscript.zip (MD5 92796a8c6e61e8f1ee36e315c0acae7d)
I've often found it helpful to use a different browser other than the stock browser (like Opera Mini) when doing downloads via my Eris since the stock browser does seem to have more issues (timeouts perhaps) than it should.
Cheers!
Thanks to all this tuff till you hooked us up but now on to nightmare 2
I downloaded CyanogenMod7.1.0 RC1 [2.3.5 GingerBread NIGHTLY]
from this thread http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Got it up but it has no market so I can not get to titanium, boot loader or anything... It says to flash google apps after the rom but now Im back to the trackball / volume key issue because it's all in titanium. ??? I did a factory reset and it came back up as the new ROM, ???
EDIT UPDATE!!!!
Sorry for the hassle all, the "green" start call button works as the down after the download.. All is well.. I think..
Again thanks to you all, If I hear of any good deals on an Eris I will know why.
You need to download GAPPS to your sdcard. That is why you don't have market.
http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Its just below link for the rom and save it to your sdcard. Go ahead boot into recovery and wipe data, daliv-cache, cache; Flash Rom again, then flash gapps and reboot.
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．．．．
Anyone know how to root a Sharp SH-02E (ICS 4.0.4)? Even a temporary root is fine, I only want to install a particular apk in /system/app.
Many thanks.
I am looking for the Sharp Aquos Zeta root also, not for me but for my friend
I'll subscribe here and repost if I find something somewhere else.
Try this
http://forum.xda-developers.com/showthread.php?t=1886460
:thumbup:
DPK
Sent from my Android Smartphone
dkmali said:
Try this
http://forum.xda-developers.com/showthread.php?t=1886460
:thumbup:
DPK
Sent from my Android Smartphone
Click to expand...
Click to collapse
Tried and failed.
There's a discussion on a Japanese BBS that I think is onto something. Unfortunately there's a stupid rule here that means I can't post a link to it. The page title is '【ROM焼き】docomo AQUOS PHONE ZETA SH-02E root1' and it should be the top result on Google for 'sh-02e root'. The fun starts at post 75.
If we can just get ROOT and Custom Recovery on this device - it simply becomes the most powerful and advanced communicator in the world.. However no root - no life..
Two things:
Any luck with a custom recovery yet?
And can anyone dump the kernel and stock rom?
Happy to give it a crack...
Sent from my SPH-L900 using Tapatalk 2
Updating Aquos Phone
jaseli said:
Tried and failed.
Click to expand...
Click to collapse
Did you manage to get update 01.00.05 anyhow flashed outside Japan?
http://www.nttdocomo.co.jp/support/utilization/product_update/list/sh02e/index.html
jauhien said:
Did you manage to get update 01.00.05 anyhow flashed outside Japan?
http://www.nttdocomo.co.jp/support/utilization/product_update/list/sh02e/index.html
Click to expand...
Click to collapse
it is currently impossible to upgrade this phone out of Japan.
i am still on 01.00.03
I have a sh203 and I would like to root my phone also
>_<
Arrgh, this is so frustrating. You look on the 2ch thread and you can see they've done it. Temp root, MIYABI permanent root, they've done it all. The instructions aren't too hard to follow but I cannot for the life of me find the password (キーワード) required to download the files from axfc.net. If I had those files I could root the phone and post a guide here in English. For goodness sake it's staring me right there in the face and there's not a thing I can do about it. And of course because this is XDA, I can't even post you a link to the thread. It's the same thread title as earlier. You want to start from post 542 onwards, if you want a try yourself.
WithLoveFromExIA said:
Arrgh, this is so frustrating. You look on the 2ch thread and you can see they've done it. Temp root, MIYABI permanent root, they've done it all. The instructions aren't too hard to follow but I cannot for the life of me find the password (キーワード) required to download the files from axfc.net. If I had those files I could root the phone and post a guide here in English. For goodness sake it's staring me right there in the face and there's not a thing I can do about it. And of course because this is XDA, I can't even post you a link to the thread. It's the same thread title as earlier. You want to start from post 542 onwards, if you want a try yourself.
Click to expand...
Click to collapse
yes , please guide me how to root the phone permantly , thanks a lot !!
OK I've made some progress. I've got a temporary root, and am three hex numbers away from a full root. You'll need
The Sharp USB drivers, that are on Sharp's developer site.
ADB, as usual
The guide itself, which I can't like to. Post 672 on the 2ch thread.
The extra files, likewise. Post 680.
.
It's well written and pretty straightforward. Only minimal use of Google Translate will be necessary.
In the guide you'll find three lines of the form
Code:
./acdbwritevalue <address> <value>
where <address> and <value> are hexadecimal numbers.
The problem is that the guide is written for build number 01.00.05, the latest one. Unfortunetely I'm stuck on 01.00.03, so while the <value> numbers are the same, the <address> numbers are differrent, and I need to find the right ones. If you're on 01.00.05 feel free to go through the guide and share your results. Alternatively, if you know how to force the phone to update without being in Japan on Docomo, please share that too.
WithLoveFromExIA said:
OK I've made some progress. I've got a temporary root, and am three hex numbers away from a full root. You'll need
The Sharp USB drivers, that are on Sharp's developer site.
ADB, as usual
The guide itself, which I can't like to. Post 672 on the 2ch thread.
The extra files, likewise. Post 680.
.
It's well written and pretty straightforward. Only minimal use of Google Translate will be necessary.
In the guide you'll find three lines of the form
Code:
./acdbwritevalue <address> <value>
where <address> and <value> are hexadecimal numbers.
The problem is that the guide is written for build number 01.00.05, the latest one. Unfortunetely I'm stuck on 01.00.03, so while the <value> numbers are the same, the <address> numbers are differrent, and I need to find the right ones. If you're on 01.00.05 feel free to go through the guide and share your results. Alternatively, if you know how to force the phone to update without being in Japan on Docomo, please share that too.
Click to expand...
Click to collapse
Although I haven't got SH02E, I have found some extra files, which was mentioned in the Japanese guide for root, expect Busybox, enjoy.
The best phone of 2013 on the worse company in the world
Tommi_Vercetti said:
Although I haven't got SH02E, I have found some extra files, which was mentioned in the Japanese guide for root, expect Busybox, enjoy.
Click to expand...
Click to collapse
Thanks a lot. Luckily I came to Japan for Vacation and was able to find someone else to lend me a Usim card to update. DoCoMo are worse than Motorola, Apple and ATT when it comes to restricting your phone. Hell, I can't even use the native FM function without DoCoMo. How can Sharp expect to come out of the hole of bankruptcy when doing this sort of business? Look at the crappy Samsung company. Awful phones that everyone buys because they decided to be "untied" to companies at the beginning and for that reason they owned the market.
If Japan is really serious into getting its technological market back, better start uncopying the USA practice of enslaving their phones and tablets to telecomunication companies.
It's a shame that the best phone right now, the Sharp Aquos Zeta Sh-02e, with its awesome new screen and specs, is going to the trash as if it was a failure, just because they don't make deals with companies outside Japan.
16MPixel CAMERA!!! IGZO ultra clear screen!!! Quad Core!! 2gb Ram!! all the specs of all the other phones plus like 30 that none of them have!! A total shame, Sharp!
Find it carefully and you will find a good guy have written a script for temp root, I used the script to have my SH-02E rooted.
And, as far as I can read the topic, the unlock file is for NAND crack and may write to recovery area.
I don't test that coz of warranty, the reason I want to root is to put some message backup back(something like LINE) and remote control (VNC server for example)
And, yes, you can find the temp root solution for both 1.0.4 and 1.0.5, but no 1.0.3, good luck!
Do you have some files for rooting sh02e 1.00.04
rotalume said:
Find it carefully and you will find a good guy have written a script for temp root, I used the script to have my SH-02E rooted.
And, as far as I can read the topic, the unlock file is for NAND crack and may write to recovery area.
I don't test that coz of warranty, the reason I want to root is to put some message backup back(something like LINE) and remote control (VNC server for example)
And, yes, you can find the temp root solution for both 1.0.4 and 1.0.5, but no 1.0.3, good luck!
Click to expand...
Click to collapse
Do you have some files for rooting sh02e 1.00.04, I think many guys here are needing the solution
Hi rotalume
thanks for the note... can i ask a favor? i really need some help to install the SH-02E driver in windows.
tried to download the file from sharp's web, but after executing the install exe file, a bundle of unreadable signs come out, and i check my device manager, there is not SH-02E USB handler or SH-02E modem. I just want to make use of Helium (backup) to extract / restore apps and data...
thank you for your help in advance.
P.S. I guess to get the temp root script pushed to SH-02E, this driver is essential as well.
thanks again
jaseli said:
Hi rotalume
thanks for the note... can i ask a favor? i really need some help to install the SH-02E driver in windows.
tried to download the file from sharp's web, but after executing the install exe file, a bundle of unreadable signs come out, and i check my device manager, there is not SH-02E USB handler or SH-02E modem. I just want to make use of Helium (backup) to extract / restore apps and data...
thank you for your help in advance.
P.S. I guess to get the temp root script pushed to SH-02E, this driver is essential as well.
thanks again
Click to expand...
Click to collapse
The one you've installed is not ADB Driver, check ADB driver at developer site(I'm to young to post a link )
File name will be given as this form : usb_driver_SHARP_r6.10.zip
Download and extract, then install the driver by device manager.
And, I've used Carbon before but in vain coz of ADB driver(the author had told me), I don't know if this issue has been solved.
For the files, sorry guys, I've found someone at other forums has used them for commercial purpose(it's a shame that ppl of my country is included), so the best I can give is to tell you the clue.
You can post your question and I will do my best, but no file will be provided atm.
Downloaded Sharp Aquos Zeta ADB drivers for SH-02E
rotalume said:
File name will be given as this form : usb_driver_SHARP_r6.10.zip
Click to expand...
Click to collapse
I was able to find and download that driver by just selecting the name you wrote and making a search on Googl. It was the very first result. thanks a lot. Although I would love the name of the script or the title of the page you downloaded it from.
Thanks a lot.
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!!
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...