Rooted an Alcatel ONE TOUCH Evolve 2 and downloaded root explorer. i ran out of space so deleted /system/bin and /system/xbin thinking they were filled with stuff like busybox that i had downloaded. i try to open a shell with adb and it doesn't work. So i restarted my phone and now it only went to the white start up screen and nothing els. i used a adb to reboot into recovery wich is still t-mobile stock and reset to factory it didn't work and now i can't use adb except for sideload and i can't find the right version of kitcat . please tell me how to remotely turn on usb debugging or how to flash it please.
Related
ok so today i tried to use a new boot animation zip and at first i tried to do it through an explorer but that didnt work as astro didnt let me paste the zip file so instead i went the adb route thought i didnt know how to use it.
i installed the files from here: http://sites.google.com/site/androidsamurai/Home/adb-for-dummies-1 and opened cmd, i used cd to get to the directory of my adb then i used adb devices to see if my phone was recognized which it was. then i used adb push bootanimation.zip /data/local and it said it copied since it gave me the speed stats, the file size and the time it took. i used astro to look inside the folder but it was empty. i then proceeded to do a few random things like remount and such and repush and the zip would just not appear in the /data/local folder. i then tried adb shell bootanimation just for kicks and it seemed to work, though i didnt know how to stop the animation besides closing my cmd. after that i tried to reboot and it got stuck at the bootanimation so then i used the 1.8.1 update and reinstalled it and i got past boot loop and for some reason the boot animation is the one i tried to install (the stock dell one that is in the themes forum) but the folder still doesnt exist in /data/local.
like i said im an adb noob, so please guide me through the entire proper way to push a bootanimation to my phone and to figure out where i pushed the previous to since it seems to be somewhere but i tried using astro search but cant find it. any help would be appreciated, thanks!
I'm not super talented at ADB either, but i believe that you should copy the boot animation zip into the same folder as ADB on your computer and then run this:
adb push bootanimation.zip /data/local
Also, there is a file manager called Root Explorer, you should use that instead of Astro because astro doesn't allow you to go into some of the system level directories (exactly what your dealing with in this case) but Root Explorer does. That's probably why you can't find what you flashed before.
Hope this helps
- pat
yeah apparently it seems that astro cant view some root files/folders
copy and paste with root explorer is easiest - like you though I am teaching myself how to use adb - get adb wireless btw - its cool if you dont have your cable to hand
Well guys i used a 1 click root to root my lg esteem from metropcs.
Worked perfect, than an update came and the phone become unrooted.
So i changed the permission of su in system/bin/su
It worked! my phone was un rooted again
Than this is my fault and the part iam stuck on -.-
I used root explorer and changed the permission of Su to match the other files.
I restarted and lost root! crap
Now whats even worse is, i cant use SU in adb shell any more
I just get the $ symbol everything i enter the su command under the adb shell and it wont give me root access to even changes the permissions back.
So now what i do, i cant use one click root anymore, and i cant get root with adb shell:
HELPPPPPPP
XD
I can see it is a real complicated situation and no doubt you messed up everthing. Maybe hard to find someone can help here. Give us the solution when you get it. Thanks.
I have heard of people using the lg recovery tool to recover bricked phones,
when it detects your phone isnt booting correctly it re flashes it.
But the problem is, my boots perfectly , so it just tells me my phone is up to date.
There has got to be a way to trick it some how....
Anyway off topic, how do i get my root back XD
Install root binary again.
Accidentally sent from my Google Nexus S using XDA Premium
You mean re install Su binary file to bin and xbin folders?
Or am i missing something?
ok i was able to change the permissions back on the system/bin/su file
Now things get werid,
I still cant run su command in adb shell as root
I checked the permissions of system/bin/su
i set chmod to 6755
Thats right isnt it?
The permissions DID CHANGES
so i dont get why root checker is telling me i dont have permission still......
I got it working i re installed binary 3.0.3 and i had root access again.
Than right after i set chmod to 6777 on /system/bin/su
i lost root again, what does this mean?
So I installed auto wipe then backed up and tested the app. It sure works... But then I realized that since I made the backup AFTER installing. Every time I restore it wipes. So I tried putting it into recovery and loaded up ADB but whenever I try to access /data/app to uninstall the APK I get this.
Code:
/sbin/sh: cd: can't cd to app
Any help is appreciated.
Oh and yes I am root and I'm running CWM 4.0.0.2
The problem:
I rooted my Samsung Galaxy Ace and went exploring the root directory with Root Explorer. I renamed the folder "apk" found in /data to "apk_old", thinking that if everything worked, I could just delete it as it contained a handful of stock apks as well as several apps installed from the market. At the time, I though apks were needed just for installation and that by deleting the folder I would save ~30MB of internal memory. Well, I turns out I was horribly wrong. Several stock apps, such as Youtube or Maps and all market apps that were installed in internal memory have stopped working. In the app drawer, their icons have turned into those default apk icons and their names into com.something.blabla. I was getting crashes every 1-2 minutes from those apps. The widgets on my home screen, such as Google search or Homework 4x2 have also stopped working.
What I've tried:
*renaming the folder back to "apk", obviously. That didn't work, it said something like "execution failed"
*making a copy of the folder - failed
*zipping the folder - failed
*thinking there was a problem with Root Explorer, I installed Total Commander and Solid Explorer hoping I could rename the folder back. Total Commander cannot open the /data folder, while Solid Explorer says the /data folder is empty
*"pulling" all of "/data" with ADB - 0 files pulled.
However, as I was trying to clean up my own mess, things changed a bit. At some point the crashes stopped and all of the "corrupt" apps have simply gone away from the app drawer. While I was unable to do anything with the "apk_old" folder in /data, something changed so that right now I can't even access /data anymore.
So yea, I have a bad feeling that somehow everything inside the /data folder has been wiped, though I sure hope I'm wrong. Anyone have anything to advise?
Oh, and I also noticed that Superuser is gone. I tried re-rooting my phone from this link, it worked the first time I rooted, but not now...
http://forum.xda-developers.com/showthread.php?t=1552792
I don't know exactly what you have in /data/apk I guess is the same I have in /data/app all the installed package.apk
Since your system is compromised I would avoid to use programs from it like Root Explorer to change anything, and for the other programs looks like they don't have root access.
I would try with plain adb: http://forum.xda-developers.com/showthread.php?t=2141817
Once you have your phone connected with adb shell you can go root:
Code:
$ su
to list files and directories in /data
Code:
# ls /data
and then to rename the folder
Code:
# mv /data/apk_old /data/apk
then reboot the phone
good luck
I'm assuming those # signs were suppose to be $'s?, Anyways, what I typed into adb:
1. adb shell
2. $ ls data
What I get:
opendir failed, Permission denied
Another atempt:
1. adb shell
2. $ su
What I get:
su, and after a long pause - Permission denied
eh? So, apparently I can't get root access, what now?
the dficua
Ha, made progress. I installed Superuser through adb and it gave me permission to access data and to rename apk_old back to apk. However, the folder has been wiped of all the apps. Luckily, I have a friend who also has a Galaxy Ace, I'll just copy the folder and paste it into /data, hopefully i'll bring back the default apps.
$ is the normal shell
# is root shell
I forgot to tell you to try that on recovery mode to prevent the calling of SuperUser to grant privilegs, su binary itself should be in /system/xbin
When you restore apps remember also to fix permissions, user and group, it should be something like this:
# chmod 0664 /data/apk/*.apk
# chown system:system /data/apk/*.apk
check the right values in your friend's phone.
Here's my situation...I had 2 rezounds...One perfectly OK, rooted and Titanium backed up, but my kids poured milk into it...yaay. The 2nd rezound which was my wife's seems to have something physically wrong with it where I can't connect to it with fastboot (but adb works ok when the phone is fully booted), which means I can't dev unlock it, or apply most of the root methods out there...
So I decided to try some other things...
I downloaded the Cydia Impactor...
Drop Su didn't work
but,
start telnetd as root on port 22 did work!
so I then went in and remounted /system as RW
and copied su to /system/bin and the Superuser.apk to /bin/apps.
I then performed a echo ro.kernel.qemu=1 >/data/local.prop.
Now when I reboot, I get the root shell if I adb in to my phone...
But, on the screen only the status bar at the top comes up and if I try to swipe down, I get
"Unfortunately, System UI has stopped".
After this, I went into adb shell and noticed the su was gone from /system/bin...So this time I pushed it to /system/xbin, changed to root owner and chmod'd it to 06755..I removed the local.prop since I think that was causing the problem with the launch screen.
After rebooting, the Rezound had deleteed the su again, but the launcher comes up OK.
So I'm thinking, maybe I need to name the su something else...nope that won't work.
I guess for now I can be happy I can get temp root...
1. Run Cydia Impactor and select start telnetd as root on port 22.
2. copy su to /system/xbin and chmod 06755 /system/xbin/su
3. Run Titanium backup, and allow SU access.
works until phone reboot when su is removed by something.
Any ideas for next steps anyone?
Thanks,
Scott