Yesterday I reinstalled stock 7.1.2 from Google, recovery and everything. I was trying to get rid of the /supersu directory in my phone's root directory. I think I got rid of it, because I didn't see it using "adb shell" and listing all files in my root directory. I went ahead and reinstalled TWRP and booted to it, and the /supersu directory is back. This makes me think TWRP is creating that directory by itself, without asking. Can anyone confirm this? And is there anyway to make TWRP NOT create that directory, or is SuperSU integrated into TWRP?
Ok so, I just rebooted into TWRP again and the /supersu directory was there. I didn't delete it from TWRP, and rebooted into the ROM, and used "adb shell" to list the files in root, and /supersu is not there. So does TWRP temporarily create /supersu for some reason, then delete it before you exit?
Related
I'm trying to remove some preinstalled apps from /system/app folder. My phone is rooted.
When I'm trying this over adb it says that I only have Read permissions. What am I doing wrong?
Put the phone into recovery mode then do the adb commands.
You only have read access while booted. R/W access while in recovery.
Mh I tried this but I couldn't even open the shell, said something.sh is missing.
You mean the normal recovery and not Clockworkmod or something, right?
You have to put it in the custom recovery. Clockworkmod or whichever one you use.
Ah okay, thank you, I will try that.
Though I need to use the normal recovery.
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Eggcake said:
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Click to expand...
Click to collapse
Code:
mount /system
At the adb shell.
Oy, thanks now I finally got it
Remove worked, pull didn't (or it took >5min for a simple apk file and I aborted it too early).
I followed all the steps from the Wiki: (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD).
Now the problem is when I go to verify the root. On the Wiki, where it says run "su' in computer ADB shell, I get access denied. When I run "./gfree_verify" in computer ADB shell, I get
Error: Could not open modem device; /dev/****
Error: Verify could not initialize device
But in my apps on the G2 I see an icon for superuser permissions. So did the root take or not?
Thanks for any help, new to Android.
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
MacaronyMax said:
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
Click to expand...
Click to collapse
After typing Su in the terminal on the phone, I get a message pop that says either allow or deny. I click allow and it gives me root permission.
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Ganii said:
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Click to expand...
Click to collapse
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
boost3d23 said:
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
Click to expand...
Click to collapse
# sign means your rooted or have su access.
Go under manage and restore backups in rom manager, you should have a copy of the rom you just backed up. Unless you renamed the back up its probably a date.
Its ok to delete the files you pushed to data/local use a file manager like root explorer.
Sent from my HTC Vision using XDA App
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again. Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
Click to expand...
Click to collapse
You get "#" then it`s right,the app don`t ask you again about allow or deny!
About gfree-verify,I don`t know.Maybe something wrong with Script
or you have done something wrong with the commands!
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Click to expand...
Click to collapse
If you choose "Backup ROM" you phone boot into Recovery,then you have
to choose "backup/restore option to backup you current ROM.
Otherwise you don`t have a backup
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
boost3d23 said:
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
I use Root Explorer or SUFBS (Super User File Manager and Terminal).
boost3d23 said:
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
You should really have posted up in the existing thread about gfree on this, or otherwise in the Q&A forum
But anyway, yes, those file managers don't handle root. Well, ES does have an option to do so, but it doesn't work on the Vision. So you'll need a root-capable file manager, as joemm said.
On the backup, that sounds a bit odd, but you'll know that it's doing a backup because it'll take a while. You'll get a different screen where it shows you it's backup up the main phone partitions, and even which file is being backed up. When it's done, make sure you copy this backup somewhere else, like your PC (i.e. so you don't just have a single copy, in case something happens to it - e.g. corrupt SD card).
Thanks to everyone who provided insight. I had the same problem and was worried about bricking my phone, but this worked and I'm happily rooted!
Daughter installed an app named Smart App Protector on her Kindle Fire and forgot the password. The app prevents access to anything. Worked with Amazon and can't do anything that gets around it, they even deregistered it. Finally suggested going through Android Debugger Bridge. After researching, found this forum. Have searched for similar question. So,
1) Can ADB be used to remove that app and leave Kindle as it was?
2) If I need to reset to Stock, which set of instructions on this forum should I follow. Still downloading all of the Android SDK files and have downloaded Kindle Fire Utility 0.9.6, but haven't installed.
How familiar are you with adb and/or basic shell commands?
Complete novice
To use adb you must do so while booted into custom recovery since Amazon has disabled it.
Assuming you have custom recovery installed and you are rooted you need to search a few directories to find where the program and it's data are installed.
The directories (path to) are...
/data/app (for apks installed on internal memory)
/data/data (for app data stored on internal memory)
/system/app (for system apks, just in case)
/sdcard/android/data (for app data stored on sdcard)
You need to open a shell in adb
Code:
adb shell
...your prompt will change to a #. From here you'll need to know a couple commands.
Code:
ls
("ell ess" to list the files in a particular directory)
Code:
rm
(to remove or delete a particular file or directory)
First pick a directory and list the contents
Code:
ls /data/app
When you find the file or folder you want removed...
Code:
rm /data/app/problematic_file.apk
"Data" folders will only contain folders, not apks. Sometimes they are named kind of weird but if you look closely enough you can figure out the right one to delete.
If you are running 100% stock, you'll have to install custom recovery to go any further, even if you want to revert back to full stock.
thanks, but KFU status says ADB status is <offline> and boot status is <unknown>. Since I can't get past the 'enter password' screen on the Kindle, i can't change anything from it. From Windows Devices, it shows the Kindle as a Android ADB Interface, so the kfu must have loaded properly.
Make sure you're in recovery and reinstall your drivers if you have to.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
If you don't have access to recovery, you'll have to use fastboot to install it.
I've been searching my _ off for two days now to find a solution for my problem, but I can't find one working for me.
What I do have right now:
NO working ROM (I believe because of a failed atempt to revert to a backup in CWM)
Access to my bootloader (unlocked through HTCDev)
Access to my recovery (Which is the latest CWM)
Fastboot/adb working
Phone boots upon the HTC logo screen
NO ROM zipfile on the SD-Card (I accidentilly deleted that, I still hate myself for that)
I've managed to push to ROM file into both /data and /system, which (ofcourse) isn't usefull to flash from because they don't show up in CWM.
What I've tried:
Reverting to a Nandroid backup, I've 2 on the sdcard. Both don't pass the part where /system is being restored.
'asd shell' to push files, or mount the SD card, does not work. First I had the error saying '--exec /system/bin/sh failure: file or dir not found (2)'. I managed to push the sh file into system, (and I believe into /system/bin), and the error changed to '[...] No directory (20)'
asd push /sdcard/; doesn't work because /sdcard is read-only.
In CWM I can't mount as USB storage, is says something about a file which can't be found.
TWRP recovery doesn't work on my device, I can touch whatever I wan't, the only button responding is the power button, which causes a locked recovery, which I can't unlock. (You need to swipe for that, which my phone seems to ignore).
I've read almost every topic on XDA and whatever Google could give me, but most solutions somewhere relied on the asd shell, or pushing into the /sdcard, or simply assume I still can mount as USB storage.
Does anyone have any suggestions left on howto get a ROM into the /sdcard so I can flash it? I would be thanking you forever!
Thanks in advance!
No ADB shell, then adb push *filename* /sdcard?
Maybe sideload a ROM?
Sent from my GT-I9300 using Tapatalk 4 Beta
I can't push files to the /sdcard since it's an read-only directory.
I tried the sideload part, but instead of executing something, it shows me the help of adb.
Any clue how to fix my shell, or get a ROM on it?
Tried typing 'adb remount' a few times and trying again?
Also, you should update your CWM to latest version so you can mount sdcard
tomascus said:
Tried typing 'adb remount' a few times and trying again?
Also, you should update your CWM to latest version so you can mount sdcard
Click to expand...
Click to collapse
I tried using remount, but that is to remount the /system partition right? I can put the ZIP on the /system partition. But CWM can't install from there.
I'm using the last version of CWM, but it gives me an error about a file not being found, so I can't mound as USB Storage device.
I returned the phone, to the store. I pretty much gave up after another few hours of struggling.
Hey guys, I'm running the latest TWRP, and I was trying to push a SlimKat rom to my phone while in recovery cause I forgot to put it on there and wiped my previous rom. I used adb push Slim-toro-4.4.alpha.1.2-UNOFFICIAL-20131117-1152.Zip /sdcard/Download and it said it went through, but when I went to look for it to install, it still wasn't there. I rebooted recovery, still wasn't there. It shows up in the File Manager in TWRP, but not through the Install menu. Am I doing something wrong?
t1.8matt said:
Hey guys, I'm running the latest TWRP, and I was trying to push a SlimKat rom to my phone while in recovery cause I forgot to put it on there and wiped my previous rom. I used adb push Slim-toro-4.4.alpha.1.2-UNOFFICIAL-20131117-1152.Zip /sdcard/Download and it said it went through, but when I went to look for it to install, it still wasn't there. I rebooted recovery, still wasn't there. It shows up in the File Manager in TWRP, but not through the Install menu. Am I doing something wrong?
Click to expand...
Click to collapse
Push to /data/media/
Is that why it wasn't showing up? Cause after I restored a nandroid, all the pushes I did showed up when I looked in root explorer.
t1.8matt said:
Is that why it wasn't showing up? Cause after I restored a nandroid, all the pushes I did showed up when I looked in root explorer.
Click to expand...
Click to collapse
Just push it to /sdcard/ or /data/media/ or even /storage/sdcard0 on some roms.
a manta wrote this.
beekay201 said:
Just push it to /sdcard/ or /data/media/ or even /storage/sdcard0 on some roms.
a manta wrote this.
Click to expand...
Click to collapse
I did push it to /SD Card and it still wouldn't show up, even though it was actually there after I got a rom flashed. Next time I'll try /data/media. Thanks for your help.
Alright, had to bring this back up because I'm still having an issue with this. This time I tried pushing the rom to /data/media/0. The rom shows up in TWRP file manager, but I still can't get it to show up in the install menu. I've tried pushing to multiple locations, /data/media/, /sdcard, same results each time, shows up in the file manager but can't get it to show up when I go to install it. I'm guessing at this point it's a TWRP issue?