Related
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?
just a refresher to help those trying to read the dozens of new pages credit goes to david279, Gregalous and others
MMS FIX - WORKS
cd C:\android-sdk-windows\tools
adb shell
cd /data/data/com*telephony/databases
sqlite3 telephony.db
update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; *input your phone number example 13303214294 dont forget the'*
adb reboot
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
3D GALLERY INSTALL - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push Gallery3D.apk /system/app
adb reboot
REOCCURRING SIGN-IN FAILURE - DOESN'T WORK
install google voice 0.2
MARKET NOT SHOWING INSTALLED APPS - WORKS FOR MANY (may fix failing sign-in error at boot)
cd C:\android-sdk-windows\tools
adb pull /system/build.prop .
used wordpad (don't use MS notepad) to edit build.prop with the following:
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD79/22607:user/release-keys
ro.cdma.home.operator.numeric = 310120 (note 310120, not 310012)
ro.cdma.home.operator.alpha = Sprint
ro.com.google.clientidbase=android-sprint
adb remount
adb push build.prop /system/
clear market cache
adb reboot
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
I did not mean for the original title to be dirogitory i simply ment to make it as clear as posible it fixes many problems that we have had in that rom i dont want somone applying it to another 2.1 rom that it doesnt work for and coming back and saying ruler why wernt you more clear...
this was all posted (in one post) by rank78 i reposted so i could make a wiki page out of it (the fix finds were descovered by multilple people if you want your name up here pm me and il put it up)
these problems are more-so in all 2.X roms, the way your title is is like your bashing, but thanks anyway
lv2bll said:
these problems are more-so in all 2.X roms, the way your title is is like your bashing, but thanks anyway
Click to expand...
Click to collapse
x2 but thanks for the effort.
Great info, but can you edit the title of the post? It seems a bit harsh to flipz. All these guys deserve the utmost respect for doing these ROMs and not asking for much from us.
Just my 2 cents, thanks again.
wow people are sensitive. he's not bashing flipz...
rank78 also posted the links to the files needed for these fixes, i think it would be a good idea to post them on the first post of this topic
Great
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Kykiskly said:
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Click to expand...
Click to collapse
Tried the MMS fix on Darch's 2.1 ROM... no luck.
link to the post with files needed to fix. i pm'ed flip to add these to the first post.
http://forum.xda-developers.com/showpost.php?p=5799963&postcount=1908
rank78 said:
link to the post with files needed to fix. i pm'ed flip to add these to the first post.
http://forum.xda-developers.com/showpost.php?p=5799963&postcount=1908
Click to expand...
Click to collapse
Thanks Rank- How do I get the 11 MDN number from my phone?
Kykiskly said:
Thanks Rank- How do I get the 11 MDN number from my phone?
Click to expand...
Click to collapse
its just 1, area code, phone number = 11
Kykiskly said:
Thanks Rank- How do I get the 11 MDN number from my phone?
Click to expand...
Click to collapse
I believe it is your phone number 1-234-567-8901 that is 11
Kykiskly said:
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Click to expand...
Click to collapse
fyi the quickboot fix is for the program quickboot that wasn't functioning after flashing the rom.
the reboot file is zipped in my post
rank78 said:
fyi the quickboot fix is for the program quickboot that wasn't functioning after flashing the rom.
the reboot file is zipped in my post
Click to expand...
Click to collapse
Many thanks, but I was able to push the file to the destination. About the MMS, i did as instructed, still didn't help at all. I am not able to mms pics out either.
I am on Darchdroid V1 2.1
You guys probably know a lot more about this than I do, but shouldn't the MMS link be:
http://mms.sprintpcs.com/servlets/MMS?X-SPRINT-MDN="Your MSID Number" ?
on my hero, i just put in:
http: //mms.sprintpcs.com/servlets/MMS
and it worked.
rulermon said:
just a refresher to help those trying to read the dozens of new pages credit goes to david279, Gregalous and others
MMS FIX - WORKS
cd C:\android-sdk-windows\tools
adb shell
cd /data/data/com*telephony/databases
sqlite3 telephony.db
update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; *input your phone number example 13303214294 dont forget the'*
adb reboot
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
3D GALLERY INSTALL - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push Gallery3D.apk /system/app
adb reboot
REOCCURRING SIGN-IN FAILURE - DOESN'T WORK
install google voice 0.2
MARKET NOT SHOWING INSTALLED APPS - WORKS FOR MANY (may fix failing sign-in error at boot)
cd C:\android-sdk-windows\tools
adb pull /system/build.prop .
used wordpad (don't use MS notepad) to edit build.prop with the following:
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD79/22607:user/release-keys
ro.cdma.home.operator.numeric = 310120 (note 310120, not 310012)
ro.cdma.home.operator.alpha = Sprint
ro.com.google.clientidbase=android-sprint
adb remount
adb push build.prop /system/
clear market cache
adb reboot
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
I did not mean for the original title to be dirogitory i simply ment to make it as clear as posible it fixes many problems that we have had in that rom i dont want somone applying it to another 2.1 rom that it doesnt work for and coming back and saying ruler why wernt you more clear...
this was all posted (in one post) by rank78 i reposted so i could make a wiki page out of it (the fix finds were descovered by multilple people if you want your name up here pm me and il put it up)
Click to expand...
Click to collapse
There still needs to be appropriate quit and .quit statements added in to get out of sqlite3 and shell.
ripleys said:
You guys probably know a lot more about this than I do, but shouldn't the MMS link be:
http://mms.sprintpcs.com/servlets/MMS?X-SPRINT-MDN="Your MSID Number" ?
on my hero, i just put in:
http: //mms.sprintpcs.com/servlets/MMS
and it worked.
Click to expand...
Click to collapse
What do you mean by "http: //mms.sprintpcs.com/servlets/MMS"? Didn't you complete the sentence with the MDN=-----------------?
Kykiskly said:
What do you mean by "http: //mms.sprintpcs.com/servlets/MMS"? Didn't you complete the sentence with the MDN=-----------------?
Click to expand...
Click to collapse
No, supposedly both work. The MDN version works all the time and the MMS version works some of the time.
Mistamike17 said:
No, supposedly both work. The MDN version works all the time and the MMS version works some of the time.
Click to expand...
Click to collapse
Ok but after that statement, what goes after, cuz since we are in the sqlite3 telephony.db, we cant adb reboot from there. What is the command to close/save the statement. I tried .quit, exit, adb reboot and no success.
how do we know that by doing the above statements the change took effect?
1) update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=1+area code + cell #' where name='Production'; *1+area code + cell '*
2)http: //mms.sprintpcs.com/servlets/MMS
This also worked on Souffle!!! Thanks guys!
Code:
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
This is copied from the Droid2 section and is said to work on the X for those of us that didnt move SU b4 updating to 2.2 or those that lost root for whatever reason.
Cool How to root the Droid 2
All credit goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.
Attached Files
File Type: rar Droid2Root.rar (954.1 KB, 733 views)
Last edited by karnovaran; Yesterday at 01:58 PM.. Reason: Clarity
Reply With Quote
Hello all...
This worked on my DX that I upgraded to 2.2 just fine. The root pw isn't given anywhere in the instructions as it is in the 2.1 manual root steps.
Any thoughts on the root pw so that I can SSH to the device after rooting?
This method worked for me after thru much trial and error I was able to update to Froyo only to discover I lost root. Did not want to roll back to 2.1 and start over. Thanks so much to everyone who came up with root process and to those who discovered it worked on the DX.
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Tried uninstalling and reinstalling everything, the one click roots say it can't find my droid X and going through your instructions adb can't find my device ether. I kinda been having a problem with doubletwist where it doesn't recognize my device properly, could that be related?
I don't know why, but after typing ./rageagainstthecage-arm5.bin it showed the text talking about donations, etc went right back to the $ prompt, and never booted me out of shell. I waited 15 minutes at the $ prompt before Ctrl-break'ing out of shell and trying to relogin. noticed adb is repsonding sluggish. Maybe it's still working? Anyone else having this problem?
Edit: I retried the ./rageagainstthecage-arm5.bin command after rebooting the phone and it worked this time. And I'm rooted! Wireless Tether for Root app works perfectly!
Also I notice when I say PC mode the little debugger icon then doesn't show up like it does in USB mode or charge mode. could this be why the device isn't showing up?
Ok so I manage to get everything good up until the point where I should be looking for a # instead of a $ for terminal. I've done the rage and waited till it kicked me out and went back in and got the same result.
The way that I got through my problems is I set the droid x to USB charge only mode (PC mode there was no debugging and every time I plugged it in, it wouldn't take the ADB driver it wanted a MB810 or something driver)
I know I set the permissions right, and it does run (shows up a little message about donating and in a min or so kicks me out, anything else I can try?
Thanks for the help.
mavermc said:
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Click to expand...
Click to collapse
You need to turn off USB debugging first time you connect DX to PC and let the drivers install. After the drivers install, turn on USB debugging and let the driver installation complete again. Then go in terminal (also make sure you change directory to where the adb application is) and type in "adb devices". If your device does not show up, change USB connection method to Windows Media Sync mode on DX and try again.
I hope that helps because that is the limit of my knowledge on the subject.
No reboot, battery pull, then reboot = weird!
Okay, so after I rooted my DX, I went to reboot it (powered off then back on) and it got stuck on the M screen. So I pulled the battery, reinserted it, and then powered on again. It rebooted fine. So...why the battery pull?? Anyone??
So i rooted using this method, (finally got it to work, just used it in usb charge mode on a XP machine) Now my phone seems to drop battery like crazy, all I've changed besides the root is install set cpu (and set some profiles to lower the clock with screen off and low battery and hi temp) installed battery life widget and a little white widget that shows what the current clock speed is. oh and wifi teather, any idea why my battery just sucks now? and things like battery info (to show whats using the battery) force closes on me after root, anyone else with these problems?
read-only what? help!!
is it ppossible to do this from the device?
Will this root work on ota froyo upgrade that we will have in a few days?
Sent from my DROIDX using XDA App
Like many have said it works perfectly if you disable the USB Debugging...install all drivers again and then put it in "Charge Mode"
I finally have my phone rooted...Now I know why my Deodex didnt wanna work. Thanks to all for releasing this and ending my headache
Hi all.
Give a try to my version of the instructions. This is kind of like the holy grail of rooting the Droid 2 at the moment. Much clearer! More info! Enjoy!
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
dscottjr81 said:
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
Click to expand...
Click to collapse
One thing I found was after it ran and returned to a cursor, I closed the cmd window and relaunched it and had no issues. Before I restarted I did switch to Charge only w/ USB debug active.
It wouldn't work at all for me until I put the contents of the Droid2Root.rar in my /tools folder. The adb commands would not work as soon as I "cd c:/Droid2Root", but the adb commands would work in the /tools folder. So I just put the contents of the Droid2Root.rar in my /tools folder and it worked just fine. O yea I'm on the OTA 2.2 (2.3.15) that came out today. I also did it under "Charge Only" with debugging.
So I take it that the One-Click root will not work withfroyo 2.2 update????
i continuously get the money sign even after it kicks me out from the ./rage step and i kill-server then adb shell.
its still there even after 3 attempts at the ./rage step what should i do? it just wont (#) prompt me
Hello,
I have on my WF puzzlewildfire, but I would like to lighten up by removing all the applications built into the rom and I do not use. How simple?
thank you
didiersl said:
Hello,
I have on my WF puzzlewildfire, but I would like to lighten up by removing all the applications built into the rom and I do not use. How simple?
thank you
Click to expand...
Click to collapse
I have used "adb shell" to get into the phone shell and remove a few apps.
First, evaluate what you are going to gain by doing this...
If you still want to remove some apps:
1. Connect your phone through USB with USB debugging enabled and charge only option
2. To get write access to 'system' partition: adb remount
3. Get shell access to phone: adb shell
4. Go to apps folder: cd /system/app
5. rm -r TheAppYouDoNotWant.apk
Important:
- Backup your apps on your PC before deleting them from your phone by doing:
(after #1 from above)
Got to a folder on your PC using the system shell (cmd or bash or ...)
adb pull /system/app/* .
- Make sure you do not delete something another app is dependent on!
this light sensor is really pissing me off , is there any way to shut it off , i'v found a way that is telling me to chmod 777 the patch file after installing it manually but idon't know what chmod 777 is and how to do this please help me
Is stock eclair there isn't a GUI option to disable it.
About chmod 777, I haven't done it yet... but I guess you have to adb shell something.
To know how to use those commands, just have a click on the search button...
maveloth said:
Is stock eclair there isn't a GUI option to disable it.
About chmod 777, I haven't done it yet... but I guess you have to adb shell something.
To know how to use those commands, just have a click on the search button...
Click to expand...
Click to collapse
i searched and found nothing please help it's pissing me off for real !! se u suck i bought this phone because of it's design but their software update service sux !
I have found what you were looking for [just search in devs forum].
Here it is an explaining link:
http://forum.xda-developers.com/showthread.php?t=888232
maveloth said:
I have found what you were looking for [just search in devs forum].
Here it is an explaining link:
http://forum.xda-developers.com/showthread.php?t=888232
Click to expand...
Click to collapse
thanks i found this thread before but i can't apply this method because i don't know how to chmod777 the file so i can't get this to work ? can you try it and then tell me how to exactly do it please , thanks again m8
First thing, you have to learn how to adb shell.
But you have to make everything ok before using it.
So, let's see how it has to be done..
Download the .zip file posted on the other thread [linked above].
Using root explorer, just copy and paste the content of the .zip file under the /etc/ path of the phone.
After you have done this, let's adb shell.
1. Download this file: http://db.tt/cq44S4v
2. Extract the adb.zip file to C:\adb [there will be a folder named "adb" within the C:\ path, with 3 files within it].
3. On your phone, click Settings > Applications > Development, and make sure USB Debugging is on.
4. Plug your phone into your computer via USB cable [it needs to be on]. It should say installing drivers if your phone is plugged for the first time and you are using Windows.
4.1 You'd better install the drivers which comes with X8 software [PC Companion], or just google for them.
5. After it installs the drivers, go to the Start menu and type "cmd" into the search bar to open the command prompt.
6. Type the following into the command prompt window [hitting enter at the end of every line]:
Code:
cd\
cd adb
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
After all this procedure, you can finally "chmod" your files.
Always from the CMD, type this:
Code:
adb shell
You should see a "#" on the left. That's good.
Now enter the path with the file to chmod:
Code:
cd /etc
Then finally chmod it:
Code:
su chmod 777 hw_config.sh
You're done.
Hope this helps.
maveloth said:
First thing, you have to learn how to adb shell.
But you have to make everything ok before using it.
So, let's see how it has to be done..
Download the .zip file posted on the other thread [linked above].
Using root explorer, just copy and paste the content of the .zip file under the /etc/ path of the phone.
After you have done this, let's adb shell.
1. Download this file: http://db.tt/cq44S4v
2. Extract the adb.zip file to C:\adb [there will be a folder named "adb" within the C:\ path, with 3 files within it].
3. On your phone, click Settings > Applications > Development, and make sure USB Debugging is on.
4. Plug your phone into your computer via USB cable [it needs to be on]. It should say installing drivers if your phone is plugged for the first time and you are using Windows.
4.1 You'd better install the drivers which comes with X8 software [PC Companion], or just google for them.
5. After it installs the drivers, go to the Start menu and type "cmd" into the search bar to open the command prompt.
6. Type the following into the command prompt window [hitting enter at the end of every line]:
Code:
cd\
cd adb
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
After all this procedure, you can finally "chmod" your files.
Always from the CMD, type this:
Code:
adb shell
You should see a "#" on the left. That's good.
Now enter the path with the file to chmod:
Code:
cd /etc
Then finally chmod it:
Code:
su chmod 777 hw_config.sh
You're done.
Hope this helps.
Click to expand...
Click to collapse
lol it's freaking hard , thanks for your help m8 i appreciate it is there any easier way?
Have you tried installing Spare Parts from the market. I know it has light sensor tweak option plus has tons of other useful tweaks and monitors.
Sent from my I7500 using Tapatalk
Master Darko said:
Have you tried installing Spare Parts from the market. I know it has light sensor tweak option plus has tons of other useful tweaks and monitors.
Sent from my I7500 using Tapatalk
Click to expand...
Click to collapse
tried it still no use , the sensor is still working !!