Android Police: The Verizon G2 Is Configured To Show Root Status In The About Phone Menu, Make It Easier To Void Your Warranty. http://google.com/producer/s/CBIwo9qLrAI
Sent from my VS980 4G using Tapatalk 4
Only Verizon lol.
Sent from my LG-D800 using xda premium
I know right? Now if something is actually wrong with the phone this will void warranty.
Sent from my VS980 4G using Tapatalk 4
yeah, but by rooting, we'll probably be able to change that line to say unrooted
sgtmedeiros said:
I know right? Now if something is actually wrong with the phone this will void warranty.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
Does it stick after restoring with LG Flash Tool? I would like to believe any smart person sending in a phone for repair would return it to stock before.
I'm sure this will only be a problem for those silly enough to try and take it in for repair/return without restoring it to stock first. It's no different than the triangle thing on Samsung devices and can be undone.
But seriously: Screw Verizon. I will never have them as a carrier. Between their obnoxious logos all over the phone, persistent wifi notifications, slow updates, removal of features, and refusal to adopt phones that aren't Motorola in a timely manner, they will never have my business.
AT&T might not be much better, but at least they get all the latest phones and they don't go to nearly as great of lengths to remove features and put every piece of bloatware they can on the device before selling it to you.
Don't be fooled...
Att also recorders root. Just not obvious.
Edit: ment att not art
Sent from my LG-D800 using XDA Premium 4 mobile app
at first i was like, whos art?
then i realized. lol
wargreymon89 said:
Does it stick after restoring with LG Flash Tool? I would like to believe any smart person sending in a phone for repair would return it to stock before.
Click to expand...
Click to collapse
No, it goes back to "Unrooted".
To reset root status:
1. Unroot your phone.
2. Make "RCT_security" file on your computer with "forel.lee" string inside.Ex: echo|set /p="forel.lee">RCT_security
It should be exactly 9 bytes size
3. Push it to sdcard: adb push RCT_security /sdcard/RCT_security
4. Reboot the phone.
rct daemon would remove status files on boot.
Root is recorded on my Razr HD also.
No big deal. There are ways....
So just out of curiosity, does anyone else have a Verizon G2 that showed as being rooted in the "Rooting Status" in about phone before ever rooting it? I have two, one shows unrooted as expected, however the other shows as being rooted. As far as I can tell though, it's not actually rooted (no su binary installed, etc.)
MJS139115 said:
So just out of curiosity, does anyone else have a Verizon G2 that showed as being rooted in the "Rooting Status" in about phone before ever rooting it? I have two, one shows unrooted as expected, however the other shows as being rooted. As far as I can tell though, it's not actually rooted (no su binary installed, etc.)
Click to expand...
Click to collapse
Rooting it is not only su. It check many other files. But anyway try:
1. Make "RCT_security" file on your computer with "forel.lee" string inside.Ex: echo|set /p="forel.lee">RCT_security
It should be exactly 9 bytes size
2. Push it to sdcard: adb push RCT_security /sdcard/RCT_security
3. Reboot the phone.
And check it again.
ddv2005 said:
Rooting it is not only su. It check many other files. But anyway try:
1. Make "RCT_security" file on your computer with "forel.lee" string inside.Ex: echo|set /p="forel.lee">RCT_security
It should be exactly 9 bytes size
2. Push it to sdcard: adb push RCT_security /sdcard/RCT_security
3. Reboot the phone.
And check it again.
Click to expand...
Click to collapse
Well after doing this it now shows as unrooted. I still find it odd though that it would show as being rooted when it was brand new out of the box. Do you know more about how/what it is actually checking to determine whether or not the phone is rooted?
ddv2005 said:
To reset root status:
1. Unroot your phone.
2. Make "RCT_security" file on your computer with "forel.lee" string inside.Ex: echo|set /p="forel.lee">RCT_security
It should be exactly 9 bytes size
3. Push it to sdcard: adb push RCT_security /sdcard/RCT_security
4. Reboot the phone.
rct daemon would remove status files on boot.
Click to expand...
Click to collapse
Will this work on a rooted phone to make it appear at first glance to not be rooted? Also, does this fix the rooted branding that shows up in bootloader download mode? (Volume up then plug in USB cord to get to this screen)
Sent from my VS980 4G using Tapatalk 4
ddv2005 said:
Rooting it is not only su. It check many other files. But anyway try:
1. Make "RCT_security" file on your computer with "forel.lee" string inside.Ex: echo|set /p="forel.lee">RCT_security
It should be exactly 9 bytes size
2. Push it to sdcard: adb push RCT_security /sdcard/RCT_security
3. Reboot the phone.
And check it again.
Click to expand...
Click to collapse
This works for me, but is cleared after the next reboot.
EDIT: nope, you just have to remove /system/bin/su /system/xbin/su /system/app/Superuser.apk, and /system/bin/busybox if you installed it, and it works.
My s3 has had this "Device Status" to display either normal or modified since release pretty much. AFAIK, Sprint doesn't even look at that screen to determine a fix. Verizon might be different, though.
ddv2005 said:
Rooting it is not only su. It check many other files. But anyway try:
1. Make "RCT_security" file on your computer with "forel.lee" string inside.Ex: echo|set /p="forel.lee">RCT_security
It should be exactly 9 bytes size
2. Push it to sdcard: adb push RCT_security /sdcard/RCT_security
3. Reboot the phone.
And check it again.
Click to expand...
Click to collapse
Can you show some screen shots of this method of removing the "root" status. I would appreciate it.
ddv2005 said:
Rooting it is not only su. It check many other files. But anyway try:
1. Make "RCT_security" file on your computer with "forel.lee" string inside.Ex: echo|set /p="forel.lee">RCT_security
It should be exactly 9 bytes size
2. Push it to sdcard: adb push RCT_security /sdcard/RCT_security
3. Reboot the phone.
And check it again.
Click to expand...
Click to collapse
I'm not sure what you mean by these steps. Do you mean to make a notepad document named "RCT_security" and then type in the exact string:
echo|set /p="forel.lee">RCT_security
and just save it?
Then push it over ADB?
And since we are pushing to sdcard only, can't we just cut and paste it from our computer into the sdcard over MTP connection?
Han Solo 1 said:
Then push it over ADB?
And since we are pushing to sdcard only, can't we just cut and paste it from our computer into the sdcard over MTP connection?
Click to expand...
Click to collapse
Sure you can
Related
The Superboot root method boot.img for 2.3.2 is now live thanks to Paul over at Android @ MoDaCo.
"Superboot is a boot.img that when flashed, will root your device the first time you boot (installing su and the superuser APK). No need to flash the system partition, no need to use ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just flash the boot image using the instructions below and you're done!"
Using Superboot
- Download the zip file and extract
- Connect Nexus S via USB cable (with debugging enabled - Settings->Applications->Development->Check "USB Debuggging")
- Boot into bootloader mode - (Turn on while holding 'volume up')
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
*Again, All credit goes to Paul at Android @ MoDaCo*
Cool I'm rooted already but nice to see easier ways of doing it for the noobs. Appreciate the work.
Sent from my Nexus S using Tapatalk
Updated today to 2.3.2 and lost root. Used this and I'm back up and running ! Thank you!!!
Sent from my Nexus S using XDA App
2.3.2
can u do this being rooted or do you have to revert to stock
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
i think you would
fastboot
fastboot satus failinvalid command
finally regain root, thank you!!!
qreffie said:
For some reason this didn't work for me. I tried it twice but each time the phone rebooted I still didn't have root. Do I have to unlock fastboot?
Click to expand...
Click to collapse
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
dakiz71 said:
maybe a noob question: if I just root my Nexus S using this method (no custom rom installation), will I still be able to get OTA updates from google?
Click to expand...
Click to collapse
Yes. You may have to re-root after updates but your phone will prompt you when OTA updates are available just like normal.
Sent from my Nexus S using Tapatalk
annndrewww said:
Yes. These instructions assume you have already unlocked your bootloader.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Figures. The answer was staring me in the face the whole time. I think I even remember unlocking it last time I rooted this way. I guess I should just leave it permanently unlocked then so it doesn't keep wiping every time I go to root after an update.
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Am I the only one that did not lose root after the latest 2.3.2 update?
DarkAgent said:
Am I the only one that did not lose root after the latest 2.3.2 update?
Click to expand...
Click to collapse
I used the superboot method for 2.3.1 and also did not lose root in with the 2.3.2 update.
Sent from my Nexus S using Tapatalk
You shouldn't.
P
Windows 7
For me install-superboot-windows is waiting for device long without success :\
No matter ... i had to force my pc recognize Nexus once more
Thank you. This seems simple. I'm stuck with my XP recognizing my Nexus S USB Driver after installing SDK and Google USB Driver even after trying to "update" driver under Device Manager and redirect the directory to Google USB Driver? I'm very confused.
philbs17 said:
Hi,
I can't get it to work on my mac.
When I put the renamed as "superboot" folder on the desktop, I open the terminal and type in:
~/Desktop/superboot/chmod +x install-superboot-mac.sh./install-superboot-mac.sh
it doesn't find that path.
Could somebody help me as a noob?
Thank you!
Click to expand...
Click to collapse
Ok buddy heres what you need to do, on the MAC, this is how i do it.:
DL the .zip in the OP.
Extract it on you're desktop
Rename the Extracted file to Nexus (thats what I name it)
youre device needs to have the bootlader Unlocked.
Open Terminal and type
cd desktop
cd nexus
chmod +x install-superboot-mac.sh (press enter)
./install-superboot-mac.sh (press enter)
then you're done. hope this helps.
Let me know.
Simply amazing! Thanks for the breakdown.
I've updated my phone. Lost my root.
Here are the instructions that got me successfully back to STOCK ROM that is still rootable.
EDIT #2: USE AT YOUR OWN RISK!
Instructions:
1. Get the LGNPST Package with the GenericModels and Components Plug-In.
http://www.megaupload.com/?d=GQ0P3XM7
2. Get the driver for the phone and install it.
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
3. Get the Stock Rom TOT file and extract it.
http://forum.xda-developers.com/showthread.php?t=1120062
4. Get the DLL file specifically for the Revolution
http://forum.xda-developers.com/showpost.php?p=14850289&postcount=19
5. Extract the "LGNPST Store & Lab"
6. Install the following order:
a. LGNPSTv1.2_Store_Version.msi
b. LGNPST_v1.2_Lab_Version.msi
c. Components >> LGNPST_Components_Ver_5_0_12_0.msi
d. GenericModels >> LGNPST_GenericModels_Ver_5_0_10_0.msi
7. Run "Right_Click_Register_DLL.reg"
8. Make a new folder called "Models" in the program's directory
Default: "C:\LG Electronics\LGNPST\"
9. Grab the "VS910.dll" and put it in the "Models" folder.
10. Right Click "VS910.dll" and click on Install.
Note: DLL WILL NOT INSTALL UNLESS COMPONENTS AND GENERICMODELS PLUG-INS ARE INSTALLED!!!
a. Make sure you install it properly
b. REBOOT!!
11. Run "LGNPST"
12. Plug in your phone, use Internet Connection Mode,and enable USB Debugging.
13. Phone should pop up in the list
14. Select the phone and click on the Open folder button inside the .BIN query underneath the COM## details.
15. Since it wants a .bin file, you can open the .TOT file by typing "*.*" inside the File Name query and hitting Enter
16. Select "VS910ZV4_04.S4_04.P58008.R5.user.tot" and Click OK
17. Then click on Upgrade
18. Wait a few minutes
19. Voila
EDIT: To all users running 64bit versions of Windows, you guys may run into problems since I only tested this method under a 32bit environment of Windows 7. I will attempt to get my hands on a 64bit version of Windows 7 to test some more and make a instructional Youtube video to help out everyone soon.
EDIT #2: Been busy, Haven't got a chance to make a youtube video yet.
Nice post!
Sent from my Cubed VS910 4G.
I didn't need this as I didn't lose my root but just wanted to say thank you for taking the time and posting this. Lot of upset people
Sent from my VS910 4G using XDA App
Nice Post.. now if i get bored one late night I will have to try it!
hilong08 said:
I've updated my phone. Lost my root.
Here are the instructions that got me successfully back to STOCK ROM that is still rootable.
Instructions:
1. Get the LGNPST Package with the GenericModels and Components Plug-In.
http://www.megaupload.com/?d=GQ0P3XM7
2. Get the driver for the phone and install it.
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
3. Get the Stock Rom TOT file and extract it.
http://forum.xda-developers.com/showthread.php?t=1120062
4. Get the DLL file specifically for the Revolution
http://forum.xda-developers.com/showpost.php?p=14850289&postcount=19
5. Extract the "LGNPST Store & Lab"
6. Install the following order:
a. LGNPSTv1.2_Store_Version.msi
b. LGNPST_v1.2_Lab_Version.msi
c. Components >> LGNPST_Components_Ver_5_0_12_0.msi
d. GenericModels >> LGNPST_GenericModels_Ver_5_0_10_0.msi
7. Run "Right_Click_Register_DLL.reg"
8. Make a new folder called "Models" in the program's directory
Default: "C:\LG Electronics\LGNPST\"
9. Grab the "VS910.dll" and put it in the "Models" folder.
10. Right Click "VS910.dll" and click on Install.
Note: DLL WILL NOT INSTALL UNLESS COMPONENTS AND GENERICMODELS PLUG-INS ARE INSTALLED!!!
a. Make sure you install it properly
11. Run "LGNPST"
12. Plug in your phone, use Internet Connection Mode,and enable USB Debugging.
13. Phone should pop up in the list
14. Select the phone and click on the Open folder button inside the .BIN query underneath the COM## details.
15. Since it wants a .bin file, you can open the .TOT file by typing "*.*" inside the File Name query and hitting Enter
16. Select "VS910ZV4_04.S4_04.P58008.R5.user.tot" and Click OK
17. Then click on Upgrade
18. Wait a few minutes
19. Voila
Click to expand...
Click to collapse
I thought this process caused problems with 4G not working and other various problems mentioned in the firmware thread?????
Not sure but maybe after doing this and obtaining root you can flash over to decrap rom or revolt rom and maybe that would fix the issues? Just a thought
dexter35803 said:
I thought this process caused problems with 4G not working and other various problems mentioned in the firmware thread?????
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
i dont know much so probably anyone can answer this but will this wipe my phones memory or just act as an update?
squidder said:
Not sure but maybe after doing this and obtaining root you can flash over to decrap rom or revolt rom and maybe that would fix the issues? Just a thought
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
Somehow i dont think so usually a tot is a full bin file that writes everything including the radio if this tot messes that up or doesnt complete properly u can have problems potentually even a brick
bonnaru said:
i dont know much so probably anyone can answer this but will this wipe my phones memory or just act as an update?
Click to expand...
Click to collapse
When I downgraded, the data stayed intact. However, do a backup anyways.
dexter35803 said:
I thought this process caused problems with 4G not working and other various problems mentioned in the firmware thread?????
Click to expand...
Click to collapse
I believe the users that have a failed downgrade had a problem with the .TOT file being downloaded properly and they probably had the phone in CDMA mode only when the phone should be in LTE/CDMA mode.
But if anything, they may have unplugged the phone before the program finished because the phone looks like it's done being flashed but the flash program says it's 80-90% complete.
Make sure you DO NOT unplug the phone until the flash program say it's safe to do so.
A note to all. If you have the drivers installed form earlier. UNINSTALL THEM!
Then restart. Install Verizon's drivers when you first plug your phone in while in 'Mass Storage' and THEN install those drivers. I had some problems getting it to work but that fixed it a bunch. Also, if you are getting a 0x800 error while trying to install the DLL, open CMD with Admin privileges and then 'regsvr32.exe "C:\LG Electronics\LGNPST\Models\VS290.dll" and it should install correctly.' I would suggest rebooting after this then running the tool.
hilong08 said:
When I downgraded, the data stayed intact. However, do a backup anyways.
Click to expand...
Click to collapse
wiped my sms log and thats it. Thanks much!
my phone isnt showing up in LGNPST...
how can i fix this?
This worked great for me! Thanks for the post!
Sent from my VS910 4G using XDA Premium App
jackpot08 said:
my phone isnt showing up in LGNPST...
how can i fix this?
Click to expand...
Click to collapse
You can try to update the drivers.
Reboot.
Turn on LGNPST.
Plug the phone to a DIFFERENT USB port.
Make sure USB Debugging is switched on on the phone.
Wait for the phone to install.
Voila.
I think LGNPST may have a refresh problem but that is what repaired the issue for me.
This Method works and is the same way I recovered my last Revo. Not sure what may have caused the issues for that phone. Using this method on the new replacement has been successful and still no problems with the phone. Did a S1C and rooted successfully and installed CWM using ADB without a hitch. Then came decrap 1.1 Life is great.
Having problems installing "VS910.dll" file. I keep getting an error. Tried Crax0r's suggestion and no dice.
You have to unzip the directory. Once that is done then the option will appear. If you still need help tonight then you might find me on irc. Im sure i can help you there. Message me if you dont figure it out.
Yeah I had download Bitzipper Trial to unzip....but when I right click the vs910.dll file I get this error "The module"C:\LG Electronics\LGNPST\Models\VS910.dll" was loaded but the call to DllRegisterServer failed with error code 0x80020009"
Edit: Sorry, I get the error when I right click and get an option to register....not Install...as the instructions says.
omik47 said:
Yeah I had download Bitzipper Trial to unzip....but when I right click the vs910.dll file I get this error "The module"C:\LG Electronics\LGNPST\Models\VS910.dll" was loaded but the call to DllRegisterServer failed with error code 0x80020009"
Edit: Sorry, I get the error when I right click and get an option to register....not Install...as the instructions says.
Click to expand...
Click to collapse
crax0r said:
Also, if you are getting a 0x800 error while trying to install the DLL, open CMD with Admin privileges and then 'regsvr32.exe "C:\LG Electronics\LGNPST\Models\VS290.dll" and it should install correctly.' I would suggest rebooting after this then running the tool.
Click to expand...
Click to collapse
I'm using win7 x64bit and the registry key that adds the right click register option wont work for me either. The manual .dll registration worked though after a reboot.
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
Its stable & works 100%
I personally have not lost root with this method in over 48 hours.
Zero com.noshufou.android.su crashes.
Before Using!!
HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
Restart your phone!
Lastly, if you're getting com.noshufou.android.su force close errors
Uninstall superuser prior to running scripts.
If you Lose Root, all you have to do is open Terminal Emulator & type fixsu
No More Rebooting & running the exploit again for R/W on system to get Root back in place!
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal and type fixsu to get root back.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot.
Q. Can I push & remove items to system and will it work?
A. Yes, but all changes are reset on a reboot.
~~~~~~~~~
For Mac/Linux users
Once downloaded, extract vividtemproot.zip to your home/root folder.
(Typically named after your login, has a house icon in Finder's sidebar of places)
Open folder vividtemproot, double-click run_me_mac (or run_me_linux)
and thats is all!
Click here to download for Mac/Linux
(Updated 11/14 - 23:50)
~~~~~~~~~
For Windows Users
Once downloaded, extract where ever you please.
Double click _RUN_ME
and enjoy!
Click here to download for Windows
(Updated 11/14 - 23:50)
Link for Windows is the Mac file...
CharlieMurphyIVXX said:
Link for Windows is the Mac file...
Click to expand...
Click to collapse
Thank you :]
Fixed
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
thecubed said:
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
Click to expand...
Click to collapse
I haven't lost root in going on ~60 hours, as as a newbie here, you definitely know far more than I do!
As you'll see in the fixsu, I redundantly copy su from /vendor/bin
to /system/xbin/ from which I hardlink (as you'd know is virtually the same as bind mounting in this case) to /system/bin
I added the fixsu, as a last resort, in case the something would dissolve, but unless someone really fudges something up, the fixsu shouldn't be needed
As my programming teacher once told me: the code doesn't need to be pretty as long as it works.
And through that philosophy I've used a lot of redundancies, that may or may not need to be there,
but they'll definitely keep anyone from having any sort of issues using the scripts!
P.S. Thank you :]
Thanks, I'll try this out and report back.
Sent from my HTC PH39100 using xda premium
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
The device rebooted itself -- the "root" is lost
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
rinnycoop121 said:
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
Click to expand...
Click to collapse
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
drewdatrip said:
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
Click to expand...
Click to collapse
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
3f62011 said:
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
Click to expand...
Click to collapse
I don't own a Windows box, an had to write the Windows bat file
without giving it a test run for errors.
I'm sure I did mess up the syntax, an probably left some command that isn't windows relavent at the end of the script.
No worries, you've got root, and shouldn't loose it.
bjg222 said:
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
Click to expand...
Click to collapse
I tried to pipe all errors out to null, as I took a mash up of your code, my code, and and another guys code, and left a lot of "in case it exists" type of lines in the code, to make sure no one would have any issues.
Apparently I didn't pipe it all to null well enough
The mac/linux version you only see 'starting' and 'finished' haha
rpendrick said:
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
Click to expand...
Click to collapse
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
drewdatrip said:
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
rpendrick said:
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
Click to expand...
Click to collapse
Yes, works much better with something in the folder.
Scrog said:
Yes, works much better with something in the folder.
Click to expand...
Click to collapse
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I was able to update superuser, but titanium back up doesn't see either SD card.
drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Superuser crashes when it is the lastest versions.
Do a google search for superuser.apk 3.0
I thought I included it in the package, but perhaps, once again in a rush
fudged that up too...
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
The Magician Type 0 said:
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Has anyone try to format the entire phone, and then fast boot back?
Someone mentioned trying that, but I never heard the results.
Sent from my DROID4 using Tapatalk 2
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
It's almost like Motorola has us all figured out! This and the unrootable Atrix HD... I think we just have to get better. I'm sure there is a root check somewhere in nvram or something
Sent from my Nexus 7 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Whoa. I mean, it probably just writes a value somewhere we can't touch (yet?), but still.
repeated shell auto-granted permissions
fade_to_red said:
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
Click to expand...
Click to collapse
highlandsun said:
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Morlok8k said:
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
Click to expand...
Click to collapse
After doing this, here is what i did in a terminal emulator:
Code:
su
mount -o remount,rw /system
chmod 644 /system/bin/dumpstate
i had to do the "644" instead of "a-x" because i kept getting an error message "Bad mode 10|"
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file??
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file???
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
It's /system/bin/dumpstate not /sys/bin/dumpstate
removing execute permissions does not do anything.
Should I or shouldn't I?
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
supraket said:
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
Click to expand...
Click to collapse
I say.....
You should:
unlock tether, free apps, better phone, harder to replace if something goes wrong (worth it to me)
You shouldn't:
warranty risk, stock performance, easy replacement
je2854 said:
removing execute permissions does not do anything.
Click to expand...
Click to collapse
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
intellitek said:
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
Click to expand...
Click to collapse
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
je2854 said:
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
Click to expand...
Click to collapse
Okay, well, let's say, hypothetically-speaking, somebody was willing to experiment with this.
When exactly does this "rootchecker" run? I guess I'd need to rename/replace it before it runs, but after I've rooted. Or somehow before, although I believe that's currently not possible. I'll try and see if the bin is signed.. not sure how to check if it's actually verifying it on exec, though, without rooting.
EDIT: Nevermind, it looks like it's built into the boot and recovery .img files?
This is the place to discuss all things Hotspot Mod. Problems, confirmation of it working etc...
Please keep the dev section clean.
The HotspotMod Thread is http://forum.xda-developers.com/showthread.php?t=2256950
Below is a tutorial on how to add the WiFiHotspot button to the notification panel using the free sqlite Database Editor
Thanks to DJSmoove for his find and to wicked for his original work located here http://www.galaxys4forums.net/forum...d-add-wifi-toggle-your-verizon-galaxy-s4.html.
sqlite Database Editor Instructions
How To Add WiFiHotspot To The Notification Panel
Missing Hotspot Option In Settings
Those of you that have the Hotspot option missing in settings, use the instructions for adding the toggle. Only this time you are going to choose the secure table instead of system. Select * for everything or chameleon_tethereddata. If the value for chameleon_tethereddata is not 3 change it to 3. Reboot the phone and see if Hotspot is showing up now in settings.
If you can't edit the database on 4.3
If you can't edit the database on 4.3 download, install and run the TB Restore Fixer from playstore.
http://forum.xda-developers.com/attachment.php?attachmentid=2381599&d=1384013849
Works great on 3g and 4g for me. Actually tethering with it now.
Just pulled the two files out and pushed them manually to the system/framework folder.
qbking77 said:
Works great on 3g and 4g for me. Actually tethering with it now.
Just pulled the two files out and pushed them manually to the system/framework folder.
Click to expand...
Click to collapse
Thank you sir. Good to see you around.
The only thing I miss about my E4GT is 4g tethering. Since Cleveland will be WiMax only for a while that means my tethering for me. 3g sucks here also.
Sent from my SPH-L720 using xda premium
I am rooted. I do not have a custom recovery though. Can I flash through stock recovery? If not, where is a working custom recovery? I have read mixed reviews on them at this point.
The alpha cwm recovery works fine just is tricky to navigate.
There is an adb version but you really need to be comfortable using cwm anyway in case something goes wrong.
Has anyone tried it with Foxfi?
I am pretty comfortable but I was hoping I could skip it all together and flash through stock. Possible?
Sent from my SPH-L720 using xda app-developers app
tyler1037 said:
I am pretty comfortable but I was hoping I could skip it all together and flash through stock. Possible?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Not with stock recovery. If you want to ask crawrj for the adb version that would be the only way currently.
Ok. Thank you!
Sent from my SPH-L720 using xda app-developers app
Is there functionally any difference between the hotspot mod and the treve tether mod? Or do they function the same, just see what you like better? I am on rooted gb27 with comadose tweaks. Whoops, just noticed I was in the s4 section, I am on the sprint s2.
Sent from my SPH-D710 using xda app-developers app
qbking77 said:
Works great on 3g and 4g for me. Actually tethering with it now.
Just pulled the two files out and pushed them manually to the system/framework folder.
Click to expand...
Click to collapse
Thanks for the idea! Working great for me on 4g! Thanks crawrj!
See signature for results!
Can anyone give a detailed way on how to unlock the hotspot for 3g 4g?
Sortilege said:
Can anyone give a detailed way on how to unlock the hotspot for 3g 4g?
Click to expand...
Click to collapse
There are instructions in the Hotspot Mod download section. There are two options, one with custom recovery and one without. To use the one with custom recovery you need to download the custom recovery tar and flash it with Odin. Then follow the instructions to install. The other option already has detailed instructions.
Do you have a specific question that you need help with?
So does the Wireless Tether app not work with the S4?
enos said:
So does the Wireless Tether app not work with the S4?
Click to expand...
Click to collapse
Not sure. I always use the native hotspot. I find that it is faster and more reliable. I am also really anal and like to use the native options if at all possible.
help please?
lafester said:
Not with stock recovery. If you want to ask crawrj for the adb version that would be the only way currently.
Click to expand...
Click to collapse
Would it be possible for me to obtain the adb version? I have tried to no avail to install this mod. I desperately seek wifi tethering on my new S4.
jarnkar said:
Would it be possible for me to obtain the adb version? I have tried to no avail to install this mod. I desperately seek wifi tethering on my new S4.
Click to expand...
Click to collapse
Yeah it is in post two of the mod thread.
Ok, I thought it worked until I read "read-only filesystem":
Code:
C:\Chris\HotspotMod>installer.bat
Mounting system
mount: Operation not permitted
Check the phone and accept the RSA request
adb shell
Press any key to continue . . .
Backing up files
76 KB/s (313 bytes in 0.004s)
5928 KB/s (5312208 bytes in 0.875s)
Installing GS4 Hotspod Mod
failed to copy 'services.jar' to '/system/framework/services.jar': Read-only fil
e system
failed to copy 'services.odex' to '/system/framework/services.odex': Read-only f
ile system
Installation complete
Rebooting Phone
I ran it from CMD & tried running the bat. Running the bat directly never prompted me with the RSA. Running it from CMD, it did everything, include pulling the stock files as backup, even reboot the phone.
I've tried several different times, but couldn't get the RSA prompt.
EDIT: Still no prompt, but running it from the bat by double clicking the bat did reboot the phone this time. Othertimes it did not after hitting any key. I'm not sure it's related, but I can USB tether. I disabled my NIC & was still routing via my phone. Even verified the IP was not what my router DHCP is configured for.
LAYGO said:
Ok, I thought it worked until I read "read-only filesystem":
Code:
C:\Chris\HotspotMod>installer.bat
Mounting system
mount: Operation not permitted
Check the phone and accept the RSA request
adb shell
Press any key to continue . . .
Backing up files
76 KB/s (313 bytes in 0.004s)
5928 KB/s (5312208 bytes in 0.875s)
Installing GS4 Hotspod Mod
failed to copy 'services.jar' to '/system/framework/services.jar': Read-only fil
e system
failed to copy 'services.odex' to '/system/framework/services.odex': Read-only f
ile system
Installation complete
Rebooting Phone
I ran it from CMD & tried running the bat. Running the bat directly never prompted me with the RSA. Running it from CMD, it did everything, include pulling the stock files as backup, even reboot the phone.
I've tried several different times, but couldn't get the RSA prompt.
EDIT: Still no prompt, but running it from the bat by double clicking the bat did reboot the phone this time. Othertimes it did not after hitting any key. I'm not sure it's related, but I can USB tether. I disabled my NIC & was still routing via my phone. Even verified the IP was not what my router DHCP is configured for.
Click to expand...
Click to collapse
Operation not permitted means that you don't have adb insecure installed or setup.