Related
Hello everyone, I apologize in advance if I've posted this in the wrong section. Ok so here is my problem, I recently got Cyanogen 4.04 (Latest stable release) on my phone. I was gonna try out the overclock app from the App market but it doesn't let me open it because i'm not ROOT. I thought users are always ROOT in modded ROM, are they not? If not then what should I do to ROOT? I used the one click method for root at the begining (to install cyanogen) and Haykuro SPL Update. Thanks.
p.s I am a complete noob so please go slow.
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
NeoBlade said:
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
Click to expand...
Click to collapse
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
pooranimator said:
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
Click to expand...
Click to collapse
type su into the terminal emulator and see what is says. if you were able to flash a custom rom then your phone is rooted, you could've gotten a bad download.
Download Better Terminal from the Maket and as david mentioned, type in "su" then press enter to see if you have root access.
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
mikespy said:
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
Click to expand...
Click to collapse
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
B-man007 said:
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
Click to expand...
Click to collapse
Thanks for the help....
I actually did download better terminal and when i typed in su and hit enter. It went to the screen your talking about and since i had just installed SetCPU it asked if i wished to allow i clicked yes. So i asume i have rooted correctly and guess the "overclocking" program on the market might just not download on my phone correctly with the cyan 4.0.4.
Thanks
Thanks to all of you for your replies. I think I know what the problem was. The OverclockWidget is a Widget...duh silly me. I was trying to open it as a regular app and was failing. Added it as a widget on the first screen and now everything works. I have one quick unrelated question, while downloading the latest experimental release of Cyanogen I read at the bottom of the post in read that the users should not use any Apps2SD while using Cyaogen's latest release because the ROM does it by itself or something like that. What does that mean?
@mikespy- tap and hold for a sec on your screen and add the OverclockWidget widget on your screen then tap to open. That's how you open the OC util.
Enable USB Debugging and Run the batch file from the attached and follow onscreen Instructions.
75 downloads - no confirmation - files removed.
Doesn't seem to want to temp root my phone. Tried with and without restart numerous times. The phone is rooted, and adb is installed correctly (or at the very least it's always done what I've wanted it to) but the batch times out when checking for temporary root every time. Oh well it was worth a shot.
I think "usb debugging" is not enabled on your phone.
Go to settings, applications, developement and enable usb debugging.
i'm with Canadian Mobilicity ... i am using Bionix V (official Froyo) and its giving me almost instantaneous GPS fix...
Axura worked as well... but this one is damn fast....
What are the commands from the terminal?
This sound good.
Do I install via cwm?
Sent from my SGH-T959 using XDA App
a1jatt said:
I think "usb debugging" is not enabled on your phone.
Go to settings, applications, developement and enable usb debugging.
Click to expand...
Click to collapse
No, USB debugging definitely was on. I always make sure it is. Otherwise straight ADB wouldn't work properly like I mentioned it always has for me
Besides, it tells you in the notifications bar if it's on whenever you plug in, and it's definitely on.
Maybe later I'll open up the batch and try the commands by hand from ADB.
hussarfilms said:
This sound good.
Do I install via cwm?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No, just double click on the install file.
Deathsnapper said:
No, USB debugging definitely was on. I always make sure it is. Otherwise straight ADB wouldn't work properly like I mentioned it always has for me
Besides, it tells you in the notifications bar if it's on whenever you plug in, and it's definitely on.
Maybe later I'll open up the batch and try the commands by hand from ADB.
Click to expand...
Click to collapse
Maybe,
it gave me same error only when i had it disabled.
a1jatt said:
Maybe,
it gave me same error only when i had it disabled.
Click to expand...
Click to collapse
Going through and doing it by hand. Pushing the files now. The line:
"%adb% -d push %gps% /system/etc"
makes total sense, in that it's pushing the gps.conf file to the folder /system/etc
but the lines following it:
"%adb% -d push %f1% /system/csc/WND/system/CSCFiles.txt"
and so on, they seem to be trying to push the txt file to a txt file already on the device. The shell tells me that "/system/csc/WND/system/CSCFiles.txt" isn't a valid file or directory.
There don't seem to be any lines that make directories /system/csc/WND/system/{files}
Should I assume that's still the intended destination and not an error? Go ahead and put some mkdir lines into busy box?
EDIT: DONE. It rebooted, installed packages, etc. Formatted data and cache when it did, so booting was like first boot (took a while, showed the general 'new rom' screens, etc.) Checking GPS now/soon.
Does it work on Mobilicity?
good work！
It should fix gps on mobilicity, i will add apn settings for mobilicity later.
On mobili u dont have to do *#06# or *#272 , just run the file and reboot.
giving me an error too
Just wanna be clear
I run the prog
Let it do its thing- exit
Then reboot?
Sent from my SGH-T959 using XDA App
How do you get it to work for tmobile in usa?
Sent from my SGH-T959 using Tapatalk
sorry but what does this do? I'm on wind mobile
I'm also using a T-Mobile Galaxy Vibrant on the Wind Mobile network.. in Vancouver.
Does this simply change the settings to use something other than supl.google.com?
it doesnt work gives me an error
I'm going to hold off on this until the errors have been addressed.. seems like there is a bug in the script (maybe).
Subject largely says it all. ADB is running fine through terminal, but when I run the adb devices command, no results are returned. Trying to run the install script to get the market up and running.
Any help? And the old cliches ring true here "I've searched, and failed" for quite some time. The only similar result I've seen on here just wound up "working" for someone.
Cheers.
ADB wasn't recongnizing my Nook Color either so I downloaded the adbWireless app from the marketplace. Hope this helps!
ChickenGod said:
ADB wasn't recongnizing my Nook Color either so I downloaded the adbWireless app from the marketplace. Hope this helps!
Click to expand...
Click to collapse
Unfortunately until i have an adb connection, i cannot install the market, which is a shame considering i really enjoy the HC preview.
When had the same problem w nook color running CM7, somebody told me to put 0x2080 in .android/adb_usb.ini. it worked first time I tried. Next day, it did not. After I checked off Stay Awake (under Application,Development), it works since.
Well why dont you use the terminal that -should- be on the HCv4... you can use busybox to push and do other things...
What are you trying to do?
arrjaytea said:
Subject largely says it all. ADB is running fine through terminal, but when I run the adb devices command, no results are returned. Trying to run the install script to get the market up and running.
Any help? And the old cliches ring true here "I've searched, and failed" for quite some time. The only similar result I've seen on here just wound up "working" for someone.
Cheers.
Click to expand...
Click to collapse
Just use Auto-nooter and you'll get the market
ChickenGod said:
Well why dont you use the terminal that -should- be on the HCv4... you can use busybox to push and do other things...
What are you trying to do?
Click to expand...
Click to collapse
pdanders said:
Just use Auto-nooter and you'll get the market
Click to expand...
Click to collapse
I appreciate the attempts to help, guys - but I did think I made it somewhat clear in the OP that I was trying to load the market via the widely circulated ADB script. I don't know if busybox is an option - and Auto-nooter is definitely not.
Regardless, thanks again - and I did just decide to go with the flashable HcV4 as it included the market and gapps bundle. Now if only we can get that new fangled gmail up and running... though I know that's wishful thinking at the moment.
I had this exact same problem. No matter what I tried, I couldn't get ADB to work on my MacBook with HC v4. So I booted into Windows using parallel and that worked, so I have been using windows thus far to ADB into the Nook
First off ,I like to say hello. Since the "Sprint " tab been out, Im thinking second thoughts of what capacities it can do (not all good). Ive re-programmed it so many times and yes bricked it and resurrected it too :0. Close one
Id tried rom manager (sprint not supported), Put in another kernal just to get rom manager too worked but crashed system (cant win).
Anyway I found Roto backup instructions, no help here. What I have is:
the tab is connected to pc.
cmd prompt which goes to abd.exe
-all is good, this is where i get stuck
adb shell su -c"dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
The -c of the above code! it says it cant find it or sometimes denied access.
what is it looking for if anything or what folder should adb be in to make this work. Where should i be entering all this into (terminal on tab or pc)
I looked for at least a month (seemed like forever)trying to find some instructions that would help.
Thanks
I think it would he best to send a personal message to rotohammer for more clarifications regarding this.
Sent from my Galaxy Tab via Tapatalk Pro
So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?
Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse
alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again
laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...
I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).
Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.
Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX