Related
I've had this phone since its launch, but I'm now encountering this strange problem.
While I can get into Download Mode without difficulty, I have an issue with connecting it to my PC. While it'll pick it up fine while the phone is in recovery or normal modes, DL mode causes it to give me this error, thus blocking Odin and my chances of returning it to stock.
I desperately need to flash my way out of this battery-draining and unstable OC/UV kernel, but Odin won't recognize it because Windows won't recognize it.
I am using Win7 x64 and WinXP x86, both with appropriate drivers and both not working and having the same issue.
CWM is similarly failing to work, producing a "failed to chown" something or other. Is my phone basically gone at this point?
My suggestion is to reinstall the drivers for the device and if cwm is not working right then use rom manager to install another version of it and if that doesn't work im pretty sure in the development section u can dl the update file with cwm on it
Sent from my SAMSUNG-SGH-I897 using XDA App
I've done the former, I'll try the latter after work today.
Sent from my SAMSUNG-SGH-I897 using XDA App
command symlink
calling command set_perm_recursive
E:Can't chown/mod /data/
(I/O error)
E:Failure at line 69:
set_perm_recursive 0 0 0777 0777 DATA:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/Perception-Build-8-non-oc-uv.zip
Here's my error message from CWM. This is after reinstalling both ROM Manager and CWM. This is preceded by a million "command symlink" commands, leading me to believe that something is failing to work here.
Aus_Azn said:
command symlink
calling command set_perm_recursive
E:Can't chown/mod /data/
(I/O error)
E:Failure at line 69:
set_perm_recursive 0 0 0777 0777 DATA:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/Perception-Build-8-non-oc-uv.zip
Here's my error message from CWM. This is after reinstalling both ROM Manager and CWM. This is preceded by a million "command symlink" commands, leading me to believe that something is failing to work here.
Click to expand...
Click to collapse
If ur trying to flash a new rom I've had this problem before the reason it isn't working is u need to flash back to stock first before u can install a new rom but it will work if u want to flash the same rom over the one u have something to do with the kernel I believe not quite sure but the way I've fixed that is to flash back to stock before flashing a new rom
Edit:::: or u need to disable lagfix by putting a file in ur root folder named disable-lagfix
Sent from my SAMSUNG-SGH-I897 using XDA App
okay thanks unhelpful guy
if you read his original post, he can't get his pc to recognize the phone in download mode. big problem.
same problem i've got.
Have your tried different usb ports. If you are using a pc try the port in the rear of your tower.
Are you using oem usb cord?
Have you tried running odin as administrator
Where did you get the drivers from
Sent from my SAMSUNG-SGH-I897 using XDA App
I've had this happen and I was pissed. No matter what I did, my computer would not see this phone and the phone was bricked with cognition. So I don't know exactly what I did BUT this comes close. Uninstall keys and go to control panel and unistall any samsung drivers. Restart computer. Install only the samsung drivers found on the samsung support page at the official samsung website. And then try putting it in download mode again. I seriously spent 7 hours on getting this to work. If this doesn't work.then you need to find the right drivers. I know there's like 3 different driver packages and kies that have the ring one, but some just completely mess you up. So.find the right one with the right drivers. Good luck! Oh and have patience, that's key.
Sent from my SAMSUNG-SGH-I897 using XDA App
Okay, I'll take your advice. I thought I tried every combination of installing and uninstalling until I nearly ripped my hair out. I tried patching the GPS and it totally boned all GPS functionality, so reverting to stock is apparently my only option... and my phone isn't recognized in download mode. So I guess a few more uninstalls and restarts and we'll see if I blow my brains out today...
Yeah. I just uninstalled Kies, Samsung Drivers, and Samsung New PC Studio. I rebooted twice, and then reinstalled the drivers (from the OP, which are identical to the ones on the Samsung site) and rebooted.
Guess what? No effing luck. Nothing shows up in Odin (remove battery, run odin, plug cable in, plug phone in, return battery and enter download mode) and my taskbar tells me that "A USB Device has malfunctioned and is not recognized."
What the HELL is going on? There are several people with this problem and nobody seems to have an answer that isn't "buhhh you have the wrong drivers."
I had this issue, used a different computer and it worked. I did have to try multiple drivers to get it to work though.
What usb jack are you using
Have you tried running ofin as administrator
Sent from my SAMSUNG-SGH-I897 using XDA App
CHECK OUT THIS POST FROM SteveVHT ON THE ANDROID FORMS:
Had this problem this past week.
You need to uninstall all Samsung software and drivers completely. Do this the normal way through Control Panel.
After that, you need to go into your registry and delete all Samsung folders.
You open up Regedit in Windows
Then go to HKEY CURRENT USER, Expand that (+), expand Software
and delete the Samsung folder
Do the same for HKEY LOCAL MACHINE
When you simply uninstall Samsung stuff, it leaves a bunch of junk in the registry of the computer even after uninstall.
Reboot the computer with no phone attached.
Download the Samsung update from Sprint
http://www6.sprint.com/downloads/samsung/executables/SamsungMoment_Update.exe
Install the updater. After its installed, right click the SWUpgrade and run as administrator....Follow all on screen instructions, and you should be good.
If you do not need the updater, then you can skip the software install and just download the drivers for the phone from the SDX forum. Just do a search.
But I suggest you do it this way, it was the only thing that worked for me...
Running Windows 7 Ultimate 64
Hope this helps
Steve
Click to expand...
Click to collapse
I'm trying it right now.
edited:It was for a Samsung MOMENT, but imagine a company flubbing two series of drivers the same way.
FFS
it's still not working
Same problem here. Windows 7 will not detect my phone in download mode. I have tried every set of drivers out there. Detects it in regular (mass storage), and USB debugging mode though.
jtdroid said:
Same problem here. Windows 7 will not detect my phone in download mode. I have tried every set of drivers out there. Detects it in regular (mass storage), and USB debugging mode though.
Click to expand...
Click to collapse
If you are using a pc, are you using the rar usb port
Sent from my SAMSUNG-SGH-I897 using XDA App
Tried all 4 ports on the back of my computer
delugeofspam said:
FFS
it's still not working
Click to expand...
Click to collapse
mcord11758 said:
If you are using a pc, are you using the rar usb port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe if you right click odin you can run as administrator. Some say this has helped
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't believe this to be a problem with Odin (even though I tried that method). Odin picks it up perfectly fine while in USB debugging mode. Windows simply will not pick it up when it enters download mode.
Any other mode Windows will "chime" when the phone is connected. Download mode doesn't do anything. No sound, chime, icon, nothing....
mcord11758 said:
I believe if you right click odin you can run as administrator. Some say this has helped
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Did you try deleting all drivers then going into download mode and letting windows install the drivers by itself?
Sent from my SAMSUNG-SGH-I897 using XDA App
goob1284 said:
Did you try deleting all drivers then going into download mode and letting windows install the drivers by itself?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
You know, this might be the only thing I haven't tried.
Here goes.
Edit:
Exactly the same megafail.
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
This guide is to enable USB charging on your Samsung Galaxy Tab.
Requirements:
- Any rooted ROM with Pershoot's kernel
- ScriptManager (free market app)
- USB Charging Script
Procedures
- Ensure you have a rooted rom/custom rom with pershoot's kernel like task650 and PhantomHacker's In Paris rom. Download and install ScriptManager from Android Market. Download the script using the link above and store it anywhere on your tab.
- Open script manager
- Navigate to wherever you stored the script and choose it. Tick run as root and run on boot. Press run.
- If it asks for superuser/root access, please allow it.
- you're done. Press home to exit. Reboot.
Note
Please read and follow all instructions and I am not responsible if anything goes wrong. this should not damage your battery. the reason why samsung disabled usb charging is not because they were worried it would damage the battery. it is because the tab charges very slowly over usb, so they didnt want people to leave a zero battery tablet charging overnight on their pc usb to wake up and find that its only charged 50%.
The common USB connections provide 5 volts DC and between 500mAh to 1,000mAh at most whereas the main power supply provides 12 volts DC and between 1200mAh to 2400mAh. Our Samsung Galaxy Tab needs about 2,000mAh for normal charging. This mod just lets you charge using that low voltage and current from the usb anyways. It is useful for someone like me who never lets the battery drain to zero and I am almost always next to a laptop so when I am watching tv or doing something else, it is always charging.
thanks to pershoot for his kernel, developers on this forum for their excellent roms.
thanks to Giblet-dono for his help and pointers in this thread
dpakrr said:
This guide is to enable USB charging on your Samsung Galaxy Tab. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
- Any ROM with Pershoot's kernel
- Samsung Mobile drivers (most of you should already have them)
- Latest Android SDK (download the zip file)
- ADB files
Procedure:
- Dont plug in your Galaxy Tab via USB yet. Make a nandroid backup just incase something goes wrong. (Boot into clockworkmod recovery -> backup and restore -> backup)
- Install the Samsung Mobile drivers
- Extract the contents of the sdk zip file onto your desktop. you should get a folder called android-sdk-windows.
- Open this folder and copy all its contents. Go to your C: drive and create a folder called androidsdk and paste the files into this folder.
- Extract the contents of the ADB files zip file you downloaded to C:\androidsdk\tools
- On your tablet, go to Settings->Applications->Development and enable USB debugging. Plug in your Galaxy Tab now.
- On your Windows computer, click on Start and type in cmd in the search bar and press enter.
- type the following and press enter after each line
cd\
cd androidsdk\tools
adb devices
- you should see a combinations of letters and numbers followed by the word device. this means that the adb can interact with your tablet.
- type in the following to enable usb charging (ensure that command prompt is still in the C:\androidsdk\tools folder). again press enter after each line.
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
exit
you should now be able to charge your tablet via usb.
thanks to pershoot for his kernel, developers on this forum for their excellent roms, and a whole bunch of online guides i looked up on how to access adb lol
Click to expand...
Click to collapse
Will this work on my viewsonic gtablet as well?
hi sorry. like i said in the "requirements", for this to work you need a kernel made by a developer called pershoot. i dont know if hes made any for the viewsonic tablets. please visit his website and see if he has kernels for viewonic tablets and if he has included the option to enable usb charging on them
thats amazing, will try it as soon as possible
SamerBerjawi said:
thats amazing, will try it as soon as possible
Click to expand...
Click to collapse
thanks. let me know how you go.
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
halmo20 said:
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hi thanks. If there's an easier way of ddoing this can you please tell us the steps. I did what you suggested but it says permission denied. Thanks
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does is on boot !
Goodluck!
Click to expand...
Click to collapse
Hi thanks. So did you jjust created a script with the following line -
echo 1 > /sys/class/power_supply/battery/force_usb_charging
OK figured it out thx
Work work work, thank you bro .
uomoto said:
Work work work, thank you bro .
Click to expand...
Click to collapse
Your welcome. Are you following the old instructions or the new ones? If you follow the new instructions the usb charging is always set to on even after you restart
Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Click to expand...
Click to collapse
Adding to an existing script works for me. Could not get it working for a new script. Must be missing something. Ironically I just made two cables up tonight with resistors as per other forums. Both hardware and software setups work well! Screw you Samsung
Oh and, THANK YOU for the tip. Go Blacks!
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
tallgrasshawk said:
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
Click to expand...
Click to collapse
Yep leave that line there. Press enter to go to the next line. Then type in
su
Press enter again. It should ask for superuser permission which requires root. Allow it root access. Now type in
echo 1 > /sys/class/power_supply/battery/force_usb_charging
And save it and follow the rest of the steps in OP
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
tallgrasshawk said:
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
Click to expand...
Click to collapse
Make sure of the following -
- your tablet is rooted
- you have busybox v1.18.2 or lower by downloading busybox installer from market
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
tallgrasshawk said:
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
Click to expand...
Click to collapse
Yep its supposed to just sit there. Once you have saved it, just press the back key and choose the file you created. Tick run as root and run on boot and click run. Again it won't do much and it will just show you a command prompt screen. Press home. It should work.
If its getting too complicated for you to follow, I just uploaded my script in the OP. just download it to your tab and run it using ScriptManager. Just tick run as root and run on boot and run it. Thats all. Dont need to type anything.
I tried it, it's working. Thanks for the mod
I'm curious about one thing regarding this mod.
Would it be possible that this can hurt the battery? I mean, what happends to the battery if it gets fed with a current and voltage that is not the current and voltage it was made for? Could that damage the cells?
I'm a computer engineering student but unfortunately we do not study much electronics, perhaps someone with deep electronics and/or chemical knowledge could write something about this? Would be awesome to know more on why/why not it can/can not harm the battery.
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.
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Xenther said:
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Click to expand...
Click to collapse
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
dray_jr said:
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
Click to expand...
Click to collapse
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Xenther said:
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Click to expand...
Click to collapse
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
Thanks again, so much, for all this! I'll go through all of these in about... two hours or so. I'll report back regardless of the outcome. You're awesome for this! :highfive:
No problem man hope it fixes your problem
Sent from my XT1056 using xda app-developers app
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
So, I've done everything in this list, and also added trying forums.motorola.com/posts/caa12135bd?commentId=725256#725256 out. I'm pretty much out of ideas, because everything I've searched showed pretty much everything you've suggested (and that I tried!) as suggestions
I appreciate the help, but so far (at this rate), I think I might just not have to root. This is super frustrating to me!
EDIT: Actually, I think I finally have something here! After hooking it up to another computer, installing the adk and everything, making sure all the drivers showed up as installed correctly and getting nothing I pretty much resided to giving up. I, for whatever reason, decided to try and run adb. After I did, and ran the start-server command, it gave me the window to accept my laptop's fingerprint! Finally on to follow the rest of the guides!
Thanks!!!
Second edit: So, proceeding to step 3 or so in RockMyMoto, I'm encountering another issue. When running Impactor and trying to run telnet on port 2222 or whatever that is, I get an error that says Signature Bugs unavailable. If I'm understanding correctly, I have to do everything in this guide to downgrade to 4.2.2 or whatever the version with the camera update is, because there isn't a root available for 4.4 without downgrading. But now I'm seeing that I somehow need to downgrade from 4.4 to the previous version in order to get Impactor/telnet working correctly?
I'm super lost now :C
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
dray_jr said:
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
Click to expand...
Click to collapse
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Xenther said:
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Click to expand...
Click to collapse
i wouldn't see why not but i am not sure
26344422579
dray_jr said:
i wouldn't see why not but i am not sure
Click to expand...
Click to collapse
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Xenther said:
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Click to expand...
Click to collapse
correct
dray_jr said:
correct
Click to expand...
Click to collapse
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Xenther said:
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Click to expand...
Click to collapse
everything looks fine bro just finish the last command and then run root checker you should be fine.
i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
i might downgrade just to run back threw it to see if i can figure it out and maybe put together a package for you that i know works. but i am on the sprint X
dray_jr said:
everything looks fine bro just finish the last command and then run root checker you should be fine. i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
Click to expand...
Click to collapse
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Xenther said:
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Click to expand...
Click to collapse
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Alright, I tossed the adb stuff on my flash drive, and I'm going to see if I can try this at work. I'll report back. You are going above and beyond to help me out, and it's just amazing. After my last community being the League of Legends community, I'm not used to this! :highfive:
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Running each of the commands works, until the last one. I get "can't create /sys/kernel/uevent_helper: Permission denied" error message
EDIT: I got it! Yeah!! :highfive: I found someone suggesting to take the phone back to 4.2.2 with this error message and redo SMM, and it stuck! Downloaded root checker, and I got a congrats result! Thanks so much, mate! You've been such a huge help; I was going to give up the first night before I even decided to post here!
I'm glad to hear you got it rooted finally if you have any other questions or need any ideas on what to do please feel free to pm me anytime
Sent from my XT1056 using xda app-developers app
i've got one for you... running windows 7, 32 bit. Eset AV-disabled.. have 4.2.2 rooted, but can't get moto-wp-nomo to successfully run...any ideas?