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.
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.
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..
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...
Well that was an adventure. I inadvertently ended up with an upgrade to VS9854CA over-the-air which predictably killed my root and wiped my setup. Life sucked, but livable until the screen started doing the flashy fade to back lockup. Now I've got to do something - I really don't want a new phone, I like my LG G3 even if the carrier is basically Evil Corp.
First things first: I had to fix the screen. I noted that the newer ROM was making the phone hotter. That's a side effect of what is truly an improvement in responsiveness from my old old version. I also noted that it seemed to get better if I manipulated the covers. Loose part somewhere? Quick search on the forums turned up this thread: "[GUIDE] Fix Display Flickering, Overheat and Constant Rebooting" with thanks to @IngJulian_RVLX. Reading it showed a basic problem to be sure but wasn't an entire fix. It did give me the idea what was needed though. So I disassembled the phone and re-flowed the main chips with a heat gun (NOT a hair dryer - not hot enough, focused enough, and way too much airflow, and DEFINITELY NOT a toaster oven - this will fry other components), then cleaned the board. Using silicon pad I placed one on the top of the main chip on the "front" (faces the display when assembled and has the big shield on it), then another piece over that one the length of the metal shield. Then I put another piece of silicon pad on the chip on the back side under the smaller metal shield. Reassemble the phone. Power up. Okay, we're working again without the annoying flashy fading screen.
So now the problem is getting root and TWRP back. Again the search: "Root for LG G3 VS985 Android 6.0 47A". Thanks to @annoyingduck and @roirraW "edor" ehT. I found a 10B .tot file and flashed that successfully. Only one big problem - adb would not find the phone! Turns out the identifier pulled in a G3 device and not the VS985 device for which I had a debug stack. Not to worry, stump is an apk so I should be able to upload right? Nope, it's offline. Well the suggested alternative, kingroot.net, exists try that. Yup that worked - I'm now rooted and victimized by all the bloatware kingroot brings with it.
Rather than debloat the kingroot I figured it does no harm in the moment. So let's get TWRP back so I at least have a recovery. Of course the CodeFire team has what I need and TWRP is installable as an app now. The first time I rooted it was a manual load with dd - progress! Just search the Play Store for TWRP, load and go. Nice work guys!!!
Okay so how to get up to the latest version possible and still keep root? Because, hey as long as I'm in here why not? Searching I find this: "[Guide] [VS985] Flash Back To Stock - KDZ Method". Yup, once more @annoyingduck to the rescue - a repository of .KDZ files along with more helpful experience. I managed to find this thread as well: "[TOOL] KDZ and TOT Extractor" with thanks to @bullghost. Still not quite what I need yet. I found "VS985 47A - Stock Flashable Firmware" with thanks to @xdabbeb. That's the ticket! So flashed that (and the bootstack) and now I'm at least a marshmallow 6.0 version. Lost root, but kingroot was able to root (and bloat).
Now to get rid of kingroot and put on superSU instead. Search found this: "How to Remove/Replace Kingroot (KingUser) with SuperSu". There, that's better! After a reboot I have to manually remove the last vestiges of kingroot but SuperSU is happily running and the bloatware is gone. Now I can restore the phone to it's prior level of function. Play Store restored my apps, I did have to reconfigure my home screens, but I'm now back in business. What's more I've got an upgrade that I like.
Whoops! An OTA update flashes on my screen!!! NO!!!!! Okay, calm down. This took several searches to find so basically here's what I needed to do:
1. Delete the files in the /cache/fota directory - this allowed the OTA to fail without updating my phone.
2. Find the "System updates" in the application manager - there are two of them and you have to select 'system' in the drop down to see them. One of them can be disabled the other cannot.
3. Find /system/app/FOTA and rename the LGFOTA.apk file to LGFOTA.apk.bak
No, using hiddenmenu.apk or the ##PROGRAM985 or any other method does not work. Apparently Evil Corp. doesn't pay attention to this anymore and that's why I got the original update that killed me. Thanks to this post for the tips: "[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually" and h/t to @autoprime.
So now I've got some work to do, because there's some fun to be had. I've managed to get the VS985CA .KDZ and extracted it. I've got the .img files ready. Now I just have to add su and busybox to the system image under linux and then I can flash these files to the phone using FlashFire (again CodeFire team - what can I say, you guys rock). Time to make the chimichungas!
Moral of the story here is this:
I've been playing around with android phones and root since my HTC Incredible. Xda-Developers has always been a source of good information but it only works if you use it. I found the original hiddenmenu.apk and it was the forums that gave me the invocation command to bring it up - somewhere in the original VS985 root thread I'm there contributing that information. Do the searches and you can find the answers you need without being annoying. Also give it time - these people I've mentioned throughout this post (along with many more) are working as fast AND as carefully as they can to bring the best solutions possible to problems. But you do have to do your part, if you aren't going to put the time in to learn at least the basics by reading the forums than this isn't your rodeo. I'm no expert but I do know how to think, experiment, and I have some background in linux and have some familiarity with android application development so I could understand something of what this device is doing and how it's built. If you lack that and you're going to play here my best advice is to have a backup phone - 'cause you're going to brick yours a few times before you learn that these basics are required, even if you're not going to be a "cool ROM" developer. That's the dues you pay to play. The experienced folks will realize my mistakes made, as I do, in this post. That's because they are the experts and I am not. Did I get where I wanted to get? Yes. Was it elegant? No. But having paid the dues I never needed to ask. Just admit to myself that I needed to get smarter and dug in. Besides, it was kinda nice not to be bugged by the phone for a day.
Quick update to the above...
The task to kill is com.lge.lgdmsclient. It took ES Task manager to find it. I moved the offending apps off to quarantine on my SD card after setting them to disable in the ES Task manager and no more OTA updates.