I am trying to make a stock Rom with wireless tether. I have cooked successful time in the past, but this one isn't working. I am using the latest rooted stock ota Rom as a base and just adding wireless tether.
I have noticed the hboot is 0.93 which is different than what my other evo had. His maybe because of the new unrevoke for 2.2.
Any ideas?
Thanks, cody
Cant you just flash the stock rooted rom and install wireless tether?
bender1077 said:
Cant you just flash the stock rooted rom and install wireless tether?
Click to expand...
Click to collapse
i want to cook it into rom. i have a few people that are wanting it. would be nice to keep it there for when and if they hard reset.
if seems even when i do it as you discribed above, it installes wireless tether as ad hoc instead of as an access point. i think thats how its worded.
thanks, Cody
You could install to system by making a flashable zip of the app. If it gets written to system/app it will survive a full wipe.
bender1077 said:
You could install to system by making a flashable zip of the app. If it gets written to system/app it will survive a full wipe.
Click to expand...
Click to collapse
hmmm. how do i make the app a flashable zip? and how do i then make it install into the system/app?
i like this idea
thanks, Cody
I believe REGAW has made a zipmaker tool that would be able to accomplish this.
ALTERNATIVELY you can also push the apk to the /system/app/ folder via ADB, and should install automatically once pushed.
First place the APK in the TOOLS folder of the Android SDK.
CODE:
adb remount
adb push yourfilename.apk /system/app
Let me know if that works for you.
bender1077 said:
I believe REGAW has made a zipmaker tool that would be able to accomplish this.
ALTERNATIVELY you can also push the apk to the /system/app/ folder via ADB, and should install automatically once pushed.
First place the APK in the TOOLS folder of the Android SDK.
CODE:
adb remount
adb push yourfilename.apk /system/app
Let me know if that works for you.
Click to expand...
Click to collapse
lol. funny you post this. i am googleing how to push wireless tether apk with adb on a mac and found this thread. i have almost got it figured out. having fun learning.
Thanks for your help, Cody
ok, new to adb so please excuse me.
i am on a mac so it is....
./adb remount
./abd push wireless_tether_2_0_5-pre8.apk /system/app
it seemed as if the push went fine, but when i go to run the wireless tether on the device it gives me a force close.
so close
in the adb, do i need to remount a second time after i push?
do i need to exit when im done with adb before unpluging my device from the usb?
just thinking it was something silly i did wrong. i am a noob at adb
Ok! Now I'm out of my territory because I am VERY unfamiliar with Apple/Mac. Can anyone else be of any assistance?
adb is adb. don't let that bother you. the fact that i never used or seen adb it the bigger concern. i am going to push a few other apps and see it they work ok.
it seems as if either /system/apps wasn't the correct place to install wireless tether or something happened to it in the push process. this is the exact apk that i manually install on the phone after flash and it works.
hmmm, Cody
Related
Hi all,
I've recently flashed to MoDaCo 2.2 however I'm just assuming my device got rooted at the same time - but I don't know for sure.
What's the easiest way to verify it has been rooted?
Thanks!
1. use search forum or google..
2. adb shell su
thats it
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Breakthecycle2 said:
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Click to expand...
Click to collapse
Have you enabled USB debugging? Settings-Applications-Development
trice1921 said:
Have you enabled USB debugging? Settings-Applications-Development
Click to expand...
Click to collapse
Yup did that too...my other phones pick it up no issues.
I also get the exact same problem (i.e. Device not found) - I guess it is a hint that it isn't rooted maybe (although I assumed it was automatic with flashing MoDaCo 2.2)?
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
robboy said:
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Click to expand...
Click to collapse
OK I got a work around. You need to restore your PC to a point BEFORE you plug in your hero. I did this and now works great.
How I might undo root process?
I think that replace chmod 4755 permision to default in the "su" file, but I don't know how to
No need to do, but I'm intererested in the concept
There is a thread on how to unroot:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse
ZenorGR said:
There is a thread on how to unroot:
Click to expand...
Click to collapse
I'm sorry but could don't find ...Thanks!!!
its a sticky.. its really hard NOT to find it
edit: okay it WAS a sticky, but its also on the first site in this subforum.. so no problem to at least SEE it
I used to use "Root Explorer" on my hero to delete system apps before..doesn't seem to work anymore..
solution??
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
did you mount /system in rw mode? (it's ro by default)
U dont have write access to system partition in normal use if i read the tutorial right. U have to do it with an update.zip (editing the update script) or with adb both u have to do in recovery menu from modaco i think. Tell me if i am wrong.
Sry for my bad english
@cezarL yes I did
@xtcislove I wish u were wrong..seems like pain.. anyway to do it without a pc?
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Damn, you're right. Previously, I had deleted an .apk just to check if it's working, then reinstalled the app right away.
But I just tested now, it looks like after a reboot, the .apk magically reappears, and the application is running as usual
Click to expand...
Click to collapse
ye..I'm sure it has something to do with the root limitations Paul mentioned in his rooting guide. hope it'll be fixed soon.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Try this: Boot in recovery menu and try the following commands:
adb remount
adb shell rm /system/app/APP.apk
adb shell rm /data/app/APP.apk
where APP.apk is the filename of the apk with the .apk extention, remember case-sensitive!
for example:
adb remount
adb shell rm /system/app/FriendStream.apk
adb shell rm /system/app/FriendStream.odex
take a look before if your app has a odex or try this: (here u need only one command)
adb remount
adb shell rm /system/app/*FriendStream*
Good luck and have fun =)
Edit: Just find a topic =)
hxxp://android.modaco.com/content/htc-hero-hero-modaco-com/297207/removal-of-apps-via-adb/#entry1124362
(replace hxxp with http)
I'm trying to do these things in windows at the moment. No issues getting in the recovery with the windows scripts. But when I try to open a ADB Shell after I've gone to recovery I can't really do anything with it and the recovery hangs (not controllable with the track pad).
Anyone can tell me what I'm doing wrong?
You're not doing anything wrong, from what I've seen opening a new adb instance on Windows will kill the server created by the .bat file used for recovery... which means the connection to the device is lost. I haven't looked into it further, but it might be fixeable somehow.
Ah I see, so basicly you undo the patched recovery by opening a new session. It does work properly under Linux then? I run ubuntu on my netbook so It's not a big issue anyway. Thanks for the tip, gonna try under linux now!
I'm having the same problems as:
http://android.modaco.com/content/h...co-com/307401/removing-sys-apps/#entry1256015
I removed a load of HTC widgets but I get strange entries on the widget menu. Anyone know how to get rid of these?
Also, I removed Stocks (.apk and .odex), now I get a force close on 'Accounts & sync'. Anyone know how to remove Stocks properly?
Cheers.
After running the bat file to get into recovery, start a new cmd prompt in windows and use again adb-nilezon for shell commands instead of ordinary adb, and it wont be killed.
This has worked for me atleast
blackadder1000 said:
Anyone know how to remove Stocks properly?
Click to expand...
Click to collapse
The best, foolproof, failsafe way is to remove them from the rom before installing it... and remember that some services are still required, weather you use them or not.
But, if a system app is already installed you need to remove:
the apk from /system/app
the data from /data/data/appname
the cache from /cache/dalvik-cache
Do not remove Accounts & Sync...
Thanks for the answer.
I guess now is a good time to bake my own ROM!
blackadder1000 said:
Thanks for the answer.
I guess now is a good time to bake my own ROM!
Click to expand...
Click to collapse
Yep, that's what I do... see my sig...
I've searched to the best of my ability in these forums and cant seem to find an answer to my problem...
Ive been looking at a particular thread's information on how to replace my MMS file and default.xml in order to get my MMS functionality working on my Evo 4G flashed to Cricket. http://forum.xda-developers.com/showthread.php?t=793588
Ive installed the SDK, installed the USB driver package within, installed the repository for 2.3.3 (what my phone is running).
I uninstalled all drivers from my phone using USBDeview.
And STILL, after plugging my phone in while in recovery mode (Clockwork mod 2.3.3) my PC will not recognize it as ADB, only as an Android Phone.
I have everything i need setup to push the files to my phone and get back the functionality of my MMS, but I cant seem to figure otu how the heck to get my PC to see my hone as an ADB. Any suggestions?
Did you install the modified unrevoked usb drivers?
Use the original USB cable... had similar problem and that solved it...
Sent from my A500 using xda premium
"Did you install the modified unrevoked usb drivers?"
I don't know what that is... All tutorials I found instructed to just use the USB drivers provided byt he Google Repository built-in to the SDK. Would this solve my problem? If so, where can I find it?
And yes, I'm using the original USB cable.
Is there a way to push files to the /system directory without using ADB? I just want to put 2 files in my /system directory...
PhayzR said:
"Did you install the modified unrevoked usb drivers?"
I don't know what that is... All tutorials I found instructed to just use the USB drivers provided byt he Google Repository built-in to the SDK. Would this solve my problem? If so, where can I find it?
And yes, I'm using the original USB cable.
Is there a way to push files to the /system directory without using ADB? I just want to put 2 files in my /system directory...
Click to expand...
Click to collapse
Here > http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
And nope, because you'll need 'permission' to have r/w on the system directory.
PhayzR said:
I've searched to the best of my ability in these forums and cant seem to find an answer to my problem...
Ive been looking at a particular thread's information on how to replace my MMS file and default.xml in order to get my MMS functionality working on my Evo 4G flashed to Cricket. http://forum.xda-developers.com/showthread.php?t=793588
Ive installed the SDK, installed the USB driver package within, installed the repository for 2.3.3 (what my phone is running).
I uninstalled all drivers from my phone using USBDeview.
And STILL, after plugging my phone in while in recovery mode (Clockwork mod 2.3.3) my PC will not recognize it as ADB, only as an Android Phone.
I have everything i need setup to push the files to my phone and get back the functionality of my MMS, but I cant seem to figure otu how the heck to get my PC to see my hone as an ADB. Any suggestions?
Click to expand...
Click to collapse
teh roxxorz said:
And nope, because you'll need 'permission' to have r/w on the system directory.
Click to expand...
Click to collapse
If you can still mount your phone as a usb flash, or disk drive or even take the sd out use an adaptor and transfer the files to the sdcard, now you have 2 of many options but these I prefer
1) You can use Root explorer which I prefer this will give you the option to mount system read write rather easily, then you can just copy or move your files and drop them in where you need them
or
2) You can install terminal on your phone and manually transfer files using the commands
this one I am not positive which one is needed but they will work as long as you have root and busybox
# su
# busybox mount -o remount,rw /system -this will put your system directory into read/write
you may try leaving the busybox off if it doesnt work at first.at the prompt you can use either cp or mv for copy or move I would do copy
should look something like this.
#cp (source directory)/(file you wish to copy) /system/(destination of file add additional directories if needed)
Make note though this is all dependant on you having root and busybox installed. Otherwise this will not work but I would work on getting the usb drivers working.
Sounds funny but did you enable usb debugging in settings/applications?
Sent from my PC36100 using Tapatalk
Sure did. I ended up replacing the default.XML, apn.XML and mms.apk files, but still no luck... I tried using apn backup and restore to install the new apn but no luck there either. Aaaaand when I tried to restore deathsled's jiminy mod, it looks like it just defaults back to cm7 instead. Any idea how I can try running jiminy without deleting my cm7 incase it doesn't work out as planned?
Sent from my PC36100 using XDA App
Still no luck...
Turns out I can't do a full flash (which is apparently what I need to get my MMS and GPS on my Cricket Flashed Evo4G) using ES Explorer or Root explorer. I need to use ADB to do so, but I still can't get the drivers working...
Any ideas?
I rooted my kindle fire using kindle fire utility 0.9.6 (after the rooting superuser wasn't installed on my kindle), downloaded twrp, flashed hashcode jelly bean ROM from this link
http://forum.xda-developers.com/showthread.php?t=1766829
and then flashed Superuser-3.1.3-x86-signed.zip which I downloaded from this link
http://androidsu.com/superuser/
but superuser won't work, when I check the root explorer in ES file explorer it tells me that this feature can't work on ur phone
Please I'm really dying out here
Someone Help Pleeeeeeeeeeeeeeeeeease !!!!!
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
Click to expand...
Click to collapse
Thank you for replying so fast
how can I install su binary? and about the superuser.apk isn't that what i flashed into my device i have a superuser icon on my desktop but it just won't add any apps to its list.
Thanks again
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
soupmagnet said:
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
Click to expand...
Click to collapse
what do you mean by not that it matters at this point?
can't I just download the zip and flash it?
soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
Click to expand...
Click to collapse
Maybe you missed this
soupmagnet said:
Maybe you missed this
Click to expand...
Click to collapse
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Scarfacew said:
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Click to expand...
Click to collapse
I too used the KFU to supposedly root my KF, but when I tried to install Titanium Backup, it gave me the same error message saying that my phone did not have root privileges... I wonder if there is something not installing correctly when using KFU...
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
soupmagnet said:
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
Click to expand...
Click to collapse
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
{Edit} I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized after the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Scarfacew said:
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
Thanks in advance
Click to expand...
Click to collapse
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
soupmagnet said:
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
Click to expand...
Click to collapse
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized since I flashed the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
soupmagnet said:
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
Click to expand...
Click to collapse
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Scarfacew said:
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Click to expand...
Click to collapse
Ok, well try a different ROM. If the problem persists then we can try to think of something.
I flashed the Alien droid ROM it's working fine till now but I need to know how to install an arabic keyboard please
Thanks
Ok, I have a dumb question, but from where do you run the DOS commands from? (ie. what directory?)..
c:\KFU?
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
soupmagnet said:
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
Click to expand...
Click to collapse
Thanks. but not sure i understand.
Here is what I'm attempting to do.. using the root method described here: http://forum.xda-developers.com/showthread.php?t=1638452 under "Getting to fastboot mode" there are a series of command line examples that seem to start with adb.... (ex. adb shell chmod 755 /data/local/tmp/fbmode).
Under Rooting the stock software, the first step command line is "adb shell mount system"
my question is from where do I start (directory) so that when I enter these commands they work?
Or are you saying that I need to fun all these from the KFU directory? (or KFU/tools) or some other directory..
I appreciate the help and feedback..
:h my::
Wherever adb is...Right-click on that folder to find it's path so you can "cd" or change directories to it. Alternatively, you can Shift + Right-click on that folder and select something like "Open command window here".
Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!
Rhatfield25 said:
Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!
Click to expand...
Click to collapse
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk
SwoRNLeaDejZ said:
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk
Click to expand...
Click to collapse
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!
Rhatfield25 said:
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!
Click to expand...
Click to collapse
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.
SwoRNLeaDejZ said:
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.
Click to expand...
Click to collapse
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.
Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?
Rhatfield25 said:
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.
Click to expand...
Click to collapse
What about trying to use the terminal emulator in twrp?
Rhatfield25 said:
Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?
Click to expand...
Click to collapse
You need to fix the framework file before you can boot. Try running the permission command without su first.