Related
Hi everyone.
I have just rooted my xperia x10a and in terminal after hitting whoami I get UID 0. I tried root explorer and it showed me the root directory with all the files and then I think I did something wrong. I went to terminal to try out some stuff and after using the command cd /data/app-private I can no longer see the root directory files. I don't know if that command and this are related issues but my knowledge is limited in this field. I have superuser installed and titanium backup works well and shows all my apps so I'm not sure what's up. Superuser shows that root explorer has UID 0 root access and I get the r/w option in root explorer but root directory shows up empty. Please someone clear this up for me. Any help at all is much appreciated.
Edit:
After digging some more it seems that root explorer does show me the contents of the data folder that astro can't see. I'm just confused as to why I can't see the contents of the root folder.
Thanks for your help.
Sent from my SO-01B using XDA App
theMaDHakkeR said:
Hi everyone.
I have just rooted my xperia x10a and in terminal after hitting whoami I get UID 0. I tried root explorer and it showed me the root directory with all the files and then I think I did something wrong. I went to terminal to try out some stuff and after using the command cd /data/app-private I can no longer see the root directory files. I don't know if that command and this are related issues but my knowledge is limited in this field. I have superuser installed and titanium backup works well and shows all my apps so I'm not sure what's up. Superuser shows that root explorer has UID 0 root access and I get the r/w option in root explorer but root directory shows up empty. Please someone clear this up for me. Any help at all is much appreciated.
Edit:
After digging some more it seems that root explorer does show me the contents of the data folder that astro can't see. I'm just confused as to why I can't see the contents of the root folder.
Thanks for your help.
Sent from my SO-01B using XDA App
Click to expand...
Click to collapse
I think that the 'root' folder has always been empty, even on my old rooted phone.
Thank you for clearing that up. I was almost certain it had something in there before but I'm not surprised if I'm wrong or simply didn't pay attention. Anyway thanks again for taking the time to reply.
Sent from my SO-01B using XDA App
theMaDHakkeR said:
Thank you for clearing that up. I was almost certain it had something in there before but I'm not surprised if I'm wrong or simply didn't pay attention. Anyway thanks again for taking the time to reply.
Sent from my SO-01B using XDA App
Click to expand...
Click to collapse
Also keep in mind that Astro is not working with root permissions. In reallity each application is working with it's own permissions that can be compared to a normal user, not superuser. Some applications request specifically superuser or root permissions which can only be granted on a rooted phone.
So basically a normal app won't use root and will therefore see less than an app that actually knows to and uses root.
Question: Is your Superuser app asking for permissions from apps? Mine isn't. On my old rooted Eris, if I ran an app such as Titanium Backup or Root Explorer, I would get a dialog which would ask if I wanted to grant that app root access. This dialog was via the Superuser app. I don't get that now. It seems like any/every app on my phone has su access.
I'm wondering if it's just me or if this is the way the current root exploit works.
DeezNotes said:
Question: Is your Superuser app asking for permissions from apps? Mine isn't. On my old rooted Eris, if I ran an app such as Titanium Backup or Root Explorer, I would get a dialog which would ask if I wanted to grant that app root access. This dialog was via the Superuser app. I don't get that now. It seems like any/every app on my phone has su access.
I'm wondering if it's just me or if this is the way the current root exploit works.
Click to expand...
Click to collapse
It's just you. Try running root explorer or a screen cap program, and verify that you have root access. You may want to use an updated Superuser.apk too, I know the one I'm using (2.3.6.1) asks, (unless I told it not too).
I'm using Superuser 2.3.6.1. When I run Titanium or Root Explorer, everything works without prompting. Now, I'm concerned.
UPDATE: I opened Superuser, went to settings, scrolled to the bottom and updated the su binary. Now, I get prompted when an app needs access. Problem is, when I reboot the su binary is reset. I think this is due to me using the joeykrim root procedure, which uses a version of su that is scripted to be put in place during the boot process. I'm going to take a look at his scripts and change them so I can keep the su binary installed by the Superuser.apk.
Thanks for the info.
Confirmed my issue was due to using the joeykrim method. I backed out his procedure and used Dirrk's method (posted here: http://forum.xda-developers.com/showthread.php?t=779238) and I get a proper Superuser prompt when an application needs access.
I also noticed another flaw in the joeykrim method. Since his procedure was developed for the Epic, he has some incorrect file names in some places.
If you notice in his instructions where he says use playlogos1 instead of playlogos, this is not updated in all of his steps.
To get your boot screen back, you have to change the last line of playlogos1 or playlogosnow (based on whether you did the lag fix or not)
The file that will not show your boot animation will look like this:
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogo-orig
To fix it, change the last line to read:
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
In summary, the playlogos1 file is used to execute other startup scripts. The original playlogos1 file has the boot animation in it. It must be referenced in one of the startup scripts. Since these instructions were used for the Epic, there's a slight typo which keeps the original playlogos1 file from being executed.
Thanks--I came to the forums looking for a solution to the fact that my boot animation was now missing. I tried making your changes but I still can't seem to recover it. Here are what my playlogo scripts look like, keeping in mind I have also installed the lag fix:
playlogos1
Code:
#!/system/bin/sh
sh /system/bin/userinit.sh
playlogosnow
playlogosnow
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
I'll also have a 3rd file called just playlogo (which was very long). Do you know what the issue is? Thanks so much for your help.
theicemonkey said:
Thanks--I came to the forums looking for a solution to the fact that my boot animation was now missing. I tried making your changes but I still can't seem to recover it. Here are what my playlogo scripts look like, keeping in mind I have also installed the lag fix:
playlogos1
Code:
#!/system/bin/sh
sh /system/bin/userinit.sh
playlogosnow
playlogosnow
Code:
#!/system/bin/sh
#joeykrim-SDX sdx-developers.com scripted
/system/bin/joeykrim-root.sh
/system/bin/playlogos1-orig
I'll also have a 3rd file called just playlogo (which was very long). Do you know what the issue is? Thanks so much for your help.
Click to expand...
Click to collapse
Judging by what your files look like, things should work. The original file is playlogos1. We never touch the playlogo file from what I can remember, so let's not do anything there.
What I would do is make sure the permissions are straight on all the files listed above (primarily playlogos1). They should be 755 (shown below):
Code:
# cd /system/bin
# ls -l playl*
-rwxr-xr-x root shell 10060 2010-08-12 04:30 playlogo
-rwxr-xr-x root root 106 2010-09-11 18:53 playlogos1
-rwxr-xr-x root root 177 2010-09-11 18:55 playlogos1-lagfix
-rwxr-xr-x root shell 14420 2010-08-12 12:30 playlogos1-orig
-rwxr-xr-x root shell 14204 2010-08-12 04:30 playlpm
#
If all else fails, you can always grab the original file from the system dump off of this link: http://forum.androidcentral.com/fascinate-roms-hacks/32839-fascinate-system-dump.html
DEAR GOD
Well, I'm an idiot.
I tried to take the playlogos1 file from the dump you showed me and copy it to my /system/bin file and, sure enough, I got the boot animation back. Problem is, I didn't think it through (that the edited playlogos1 file pointed to the rest of the modified boot sequence) and then the phone wouldn't boot. It would just loop the animations.
I booted into recovery, did a factory reset, and now I can get to the lockscreen and the very beginning of setup but TWLauncher force closes over and over and over and I'm unable to do anything except pull down the notification bar occasionally. I think this is because I moved some things (like bing, daily briefing, etc.) that TWLauncher wants at the outset, and it doesn't have them. I tried to bluetooth over LauncherPro and run it, but it fails at the last moment.
Does anyone know of a way to get to ADB Shell so that I can fix my mistake? Or if someone had an update.zip I could flash to get back to factory (with all of the system files in place), that would be super! Otherwise, it looks like I'm effed and will need to come up with a good story to tell Verizon...
theicemonkey said:
Well, I'm an idiot.
I tried to take the playlogos1 file from the dump you showed me and copy it to my /system/bin file and, sure enough, I got the boot animation back. Problem is, I didn't think it through (that the edited playlogos1 file pointed to the rest of the modified boot sequence) and then the phone wouldn't boot. It would just loop the animations.
I booted into recovery, did a factory reset, and now I can get to the lockscreen and the very beginning of setup but TWLauncher force closes over and over and over and I'm unable to do anything except pull down the notification bar occasionally. I think this is because I moved some things (like bing, daily briefing, etc.) that TWLauncher wants at the outset, and it doesn't have them. I tried to bluetooth over LauncherPro and run it, but it fails at the last moment.
Does anyone know of a way to get to ADB Shell so that I can fix my mistake? Or if someone had an update.zip I could flash to get back to factory (with all of the system files in place), that would be super! Otherwise, it looks like I'm effed and will need to come up with a good story to tell Verizon...
Click to expand...
Click to collapse
Sorry you're having issues. Bad news is, you can't flash any zip updates because we don't have a custom recovery re our phones yet. However, what you should be able to do is use adb to push the apps from /system/app from the system dump. That is.. if you can get adb to work? If it can work from recovery, that should save you.
Good luck.
Flashing is never 100% safe, use at your own risk.
Backup before flashing!
Make sure your battery is charged!
For US version (YP-GI1CB) use the ROMs from alice90's thread
You might want to use sha1sum or md5sums to check download integrity, and 7zip to unpack archives.
Archive password is: xda-devs
These ROMs can be flashed using Odin3. If you want to use Heimdall (v1.3.2 reported not working with SGP4.2, use v1.3.1) you will need to extract the .img files from the archives. Use stock ROMs if you want to revert back to original state.
/!\ These ROMs are for YP-GI1CW/XEF. If you have another YP-GI1CW model you need to backup your wifi files before flashing and restore them later. You can refer to Backup /system/etc/wifi or Flash kernel (not recommended) or read the procedure in the HOWTO below.
ROOTED ROM
Description: this is the stock ROM with only 1 file added, /system/bin/su which was taken from TinySU (Note: doesn't spawn any popup when giving root through Superuser.apk)
SHA1: 2e27472345a40a8bfd4cba7f13bc1846ceba2800
MD5: 73288ed29eb8c4711b34e682a39682f3
STOCK ROM
Description: stock ROM, flash this if you want to revert back to out-of-the-box state
SHA1: 70eb347c5d8c0c877e7d069d30ac54bd1673d41a
MD5: 71a9880e88e6f513b4e9665542cbeaa3
STOCK KERNEL
Description: don't flash this unless you really need it; your bootlogo will be forever replaced by SGS2 logo, and your device will be watermarked, which will void your warranty
SHA1: 1bc402d990963c973957ef71e80e1a6dede4d1ae
MD5: 5b6be70d941c31aadfdb8d4a11db2800
Greets: Rebellos alice90 Baruch6132 zaclimon Entropy512 baladev helicopter88 ChrisFR and all the people from #xda-devs that supported me
HOW TO USE
Before anything you will have to install Samsung drivers, either with Kies from Samsung website, or using zadig (recommended)
I. Backup /system
Many different YP-GI1CW models exist with different letters at the end; I dumped these ROMs using YP-GI1CW/XEF and hence, if you have the same model but different letters at the end, you will probably not be able to use wifi after flashing. The workaround for this is to backup your original wifi files before flashing, and restore them later. If you own the very same model (YP-GI1CW/XEF) this step may be skipped, but it's safe to do it anyway:
- download & install AndroidSDK. It's a huge package with many tools, such as ADB (there's probably a light, stand-alone ADB somewhere; post if you have some info about this)
- unplug device from USB then put your device in USB debugging mode (Settings > Applications > Development > USB Debugging) then re-plug device.
- change active directory to where you installed AndroidSDK or ADB, on a windows system I would press Win+R then type cmd to open a console, and then in the console:
Code:
cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"
- make sure your device is detected
Code:
adb devices
Should show your device serial number and status. If you don't see them, check if: you have the correct drivers / USB Debugging is enabled / USB cable properly connected
- backup your /system directory
Code:
mkdir sysbkup
cd sysbkup
..\adb pull /system
You will probably get some errors and that's normal, as you can't pull all files without root. Make sure the files are actually copied on your computer (with my device it's approx. 473MB).
- keep track of the original file permissions so you can restore them later
Code:
adb shell
$ ls -l /system/etc/wifi
-rw-r--r-- root root 274168 2012-03-17 10:05 firmware.bin
drwxr-xr-x root root 2012-03-17 10:05 softap
-rw-r--r-- root root 16295 2012-03-17 10:05 tiwlan.ini
-rw-r--r-- root root 16986 2012-03-17 10:05 tiwlan_cert.ini
-rw-r--r-- root root 883428 2012-03-17 10:05 tiwlan_drv.ko
-rw-r--r-- root root 16985 2012-03-17 10:05 tiwlan_plt.ini
-rw-r--r-- root root 1012 2012-03-17 10:05 wifi.conf
-rw-r--r-- root root 134 2012-03-17 10:05 wpa_supplicant.conf
$ ls -l /system/etc/wifi/softap
-rw-r--r-- root root 262356 2012-03-17 10:05 ap_firmware.bin
-rw-r--r-- root root 652 2012-03-17 10:05 hostapd.conf
-rw-r--r-- root root 954932 2012-03-17 10:05 tiap_drv.ko
-rw-r--r-- root root 22424 2012-03-17 10:05 tiwlan_ap.ini
Save what you see in some TXT file for later reference (will be needed in section III).
II. Flashing with Odin3 on Windows
1. Make sure the ROM you intend to flash was made exclusively for your device
2. Double-check (for Samsung Galaxy Player 4.2: open your device's cover, lift the battery; the model appears behind it)
3. Download & run Odin3 (tested v1.85 and v3.04 so far, both worked fine), click PDA and choose the .tar (or .tar.md5) file you want to flash (most likely, the "Rooted factoryfs" ROM).
4. Put your device in download-mode:
- unplug USB cable
- shut your device down (remove and reseat battery if its stuck somehow)
- press HOME (physical button bottom center), keep it pressed
- press VolumeDown, keep it pressed
- press Power, keep it pressed
- wait until the download-mode confirmation screen shows up
- release VolumeDown first, then the rest of buttons
- connect your PC to your device using USB cable
- press VolumeUp one to finally make your device turn into download-mode
=> this should make Odin3 react, and tell you "Added" in the bottom-left window, while adding something like <COM#> in the first box
Be careful: some user report having troubles with USB3 ports. I would recommend properly powered USB2 ports only. Avoid USB hubs, avoid USB1 and USB3.
5. Make sure to UNCHECK repartition. You can also uncheck the "F Reset Time" and "Auto reboot" but they're harmless. The only box that needs to be checked is PDA, along with the ROM file you're about to flash.
6. To flash your device, click start, the process should take less than 2 minutes.
If Odin3 stops at "Setup connection" this means the device has timed out (happened to me all the time); just retry and click "Start" faster after plugging USB
III. If Wifi doesn't work, restore wifi files saved in section I
Go to your ADB folder in console (refer to secion I), just under the directory containing backup
Code:
cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Copy the the files you need on /sdcard/
Code:
adb push sysbkup/etc/wifi /sdcard/wifibkup
Then open a shell on your device, replace wifi files and set permissions (Note: I use 644 and 755 because that's what I had in section I, you should replace them with the permissions you had)
Code:
adb shell
$ su
# mount -o remount,rw /system /system
# cd /sdcard/wifibkup
# for i in *; do dd if=$i of=/system/etc/wifi/$i; done
# cd softap
# for i in *; do dd if=$i of=/system/etc/wifi/softap/$i; done
# cd /system/etc/wifi
# chown root.root *
# chmod 644 *
# chmod 755 softap
# cd softap
# chown root.root *
# chmod 644 *
# sync
Reboot, and you're done!
bluk
[EDIT: the following method does only work on Android 4.0 and above, I keep it here for reference only]
Many solutions exist for backup, I read many times about Titanium backup doing excellent job as well as ClockworkMod but they both need root IIRC. BackMeUp claims to perform backups without root on Android 2.1 and more, no idea to which degree this is true.
Without root, it's possible to make backups using ADB (Android Debug Bridge) which basically is the swissknife for Android devices; it gives you a linux shell on your device, backup/restore ability and more.
1. Download & install AndroidSDK. It's a huge package with many tools (such as ADB); there's probably a stand-alone ADB somewhere if you don't want to go the AndroidSDK way.
2. Unplug device from USB then put your device in USB debugging mode (Settings > Applications > Development > USB Debugging) then re-plug device.
3. Now it's time to create a backup file which I will call C:\MyBackup for the sake of example.
- open a shell
press Win+R and type in cmd
- change active directory to where you installed AndroidSDK or ADB, on my system I type
Code:
cd "C:\Program Files (x86)\Android\android-sdk\platform-tools"
- at this point, if you need to CREATE backup file, type:
Code:
adb backup -apk -shared -all -f C:\MyBackup
- but instead, if you need to RESTORE a previously created backup, type:
Code:
adb restore C:\MyBackup
zebluk said:
Flashing is never 100% safe, use at your own risk.
Backup before flashing!
A version for US devices (YP-GI1CB) is about to be made, just be patient folks, should be a matter of days!
These ROMs can be flashed using Odin3. If you want to use Heimdall you will need to extract the .img files from the archives. Use stock ROMs if you want to revert back to original state.
Stock factoryfs
Stock kernel (the original logo will be lost, and your device will be watermarked)
Rooted factoryfs
The rooted ROM is minimal. It just adds /system/bin/su to the stock factoryfs and nothing more. That should be enough for anything tho
This version of su (TinySU) doesn't spawn any popup when giving root thru Superuser.apk, feel free to replace it with the version you like.
Greets: Rebellos alice90 Baruch6132 zaclimon Entropy512 helicopter88 ChrisFR and all the people from #xda-devs that supported me
Click to expand...
Click to collapse
Congrats on this!! Now the 4.2 users can finally get their players rooted.
zebluk said:
Flashing is never 100% safe, use at your own risk.
Backup before flashing!
For US version (YP-GI1CB) go HERE
These ROMs can be flashed using Odin3. If you want to use Heimdall you will need to extract the .img files from the archives. Use stock ROMs if you want to revert back to original state.
Stock factoryfs
Stock kernel (the original logo will be lost, and your device will be watermarked)
Rooted factoryfs
The rooted ROM is minimal. It just adds /system/bin/su to the stock factoryfs and nothing more. That should be enough for anything tho
This version of su (TinySU) doesn't spawn any popup when giving root thru Superuser.apk, feel free to replace it with the version you like.
Greets: Rebellos alice90 Baruch6132 zaclimon Entropy512 baladev helicopter88 ChrisFR and all the people from #xda-devs that supported me
Click to expand...
Click to collapse
Is there a step-by-step procedure to do this for complete noobs like me? I don't know how to backup and root since it is my first Android device and I just don't want to brick it if I miss a step. Thank you very much for this.
Would appreciate a full guide as well. Though it seems pretty straightforward, I wouldn't want to make an elementary mistake or one specific to this device.
Also, I'm curious whether full functionality will be present in translating over to a different launcher.
Thanks a ton for the great work to all involved (and great timing in getting it out a week after I got my hands on the 4.2)!
Sent from my YP-GI1 using xda premium
Ok, added a HOWTO for Windows users, I hope that helps.
@Consumers: I'm not sure what do you mean by "translating over to a different launcher", maybe you're talking about CWM? Anyway unless you hardbrick your device, you should be able to restore it to stock (even from the exclamation mark screen which is in fact another download-mode), just be safe and do backups when you're in doubt!
For now I don't plan on doing other updates. Now the stock ROM is dumped & rooted, I'll let the modders take it from here, if they feel like it
bluk
zebluk said:
Ok, added a HOWTO for Windows users, I hope that helps.
@Consumers: I'm not sure what do you mean by "translating over to a different launcher", maybe you're talking about CWM? Anyway unless you hardbrick your device, you should be able to restore it to stock (even from the exclamation mark screen which is in fact another download-mode), just be safe and do backups when you're in doubt!
For now I don't plan on doing other updates. Now the stock ROM is dumped & rooted, I'll let the modders take it from here, if they feel like it
bluk
Click to expand...
Click to collapse
Thanks for the how to. However, the link to the rooted factoryfs is down. Could you please reupload it? Maybe with another file hosting site like Mediafire or through torrent maybe? Thank you very much.
galaxyplayer4.2 said:
Thanks for the how to. However, the link to the rooted factoryfs is down. Could you please reupload it? Maybe with another file hosting site like Mediafire or through torrent maybe? Thank you very much.
Click to expand...
Click to collapse
Thanks for notifying me; reuploading
bluk
Odin seems to flash successfully, but after restarting, root-only programs like Root Browser and ROM Browser still say that it appears that I'm not rooted. I tried flashing twice, both with no problems, and still nothing. Any ideas?
EDIT: Never mind! SuperSU simply wasn't granting access or prompting me to grant access to the apps. Thank you very much for your work, zebluk! Very helpful guide too.
Consumers said:
Odin seems to flash successfully, but after restarting, root-only programs like Root Browser and ROM Browser still say that it appears that I'm not rooted. I tried flashing twice, both with no problems, and still nothing. Any ideas?
Click to expand...
Click to collapse
Install Superuser I didn't include it to keep changes minimal.
Make sure you have rooted device issuing "adb shell" at prompt, then type "su". If you see sharp sign "#" you have root.
bluk
EDIT: looks like you got it at the very same time I was answering enjoy
Hi guys, just a litte thing: the mentioned backup process (adb) doesnt work on Android 2.3.6. Think its 4.0 above ...
Nevertheless, great we got root now
joeblack_2k2 said:
Hi guys, just a litte thing: the mentioned backup process (adb) doesnt work on Android 2.3.6. Think its 4.0 above ...
Nevertheless, great we got root now
Click to expand...
Click to collapse
Thanks for pointing that out, unfortunately seems there are no decent ways of backing up unrooted on GB, I'll investigate when I have time.
bluk
Root, but no wifi =(
First I want to mention that you made a great job!!!!
I'm from germany but the shop sold me a US-Version device (yp-gi1CB). I flashed the CB rooted firmware but i have no wifi. then i flasehd the cw firmware, same problem. Hope there is a solution :/
thanks!
Nouri92 said:
First I want to mention that you made a great job!!!!
I'm from germany but the shop sold me a US-Version device (yp-gi1CB). I flashed the CB rooted firmware but i have no wifi. then i flasehd the cw firmware, same problem. Hope there is a solution :/
thanks!
Click to expand...
Click to collapse
yes i have the same problem i root my device and i have no wifi
Kendos007 said:
yes i have the same problem i root my device and i have no wifi
Click to expand...
Click to collapse
Look at this thread http://forum.xda-developers.com/showthread.php?t=1715461&page=50 untill now the simplest solution is to flash another kernel, but im waiting for a another solution you can read that thread, the problem begans 1 page before..(page 49)
As I posted before I had the same problem when rooting, no WLAN.
But I've got it working again.
Before rooting I did a backup op my /System dir. And because there is a problem with de wifi driver, I restored the files in /etc/wifi from my backup.
After a reboot everything worked fine.
I attached the wifi folder so you guys can restore it. Hope it helps.
If you need any help, let me know.
kiteman76 said:
As I posted before I had the same problem when rooting, no WLAN.
But I've got it working again.
Before rooting I did a backup op my /System dir. And because there is a problem with de wifi driver, I restored the files in /etc/wifi from my backup.
After a reboot everything worked fine.
I attached the wifi folder so you guys can restore it. Hope it helps.
If you need any help, let me know.
Click to expand...
Click to collapse
Thanks man I have wifi again
kiteman76 said:
As I posted before I had the same problem when rooting, no WLAN.
But I've got it working again.
Before rooting I did a backup op my /System dir. And because there is a problem with de wifi driver, I restored the files in /etc/wifi from my backup.
After a reboot everything worked fine.
I attached the wifi folder so you guys can restore it. Hope it helps.
If you need any help, let me know.
Click to expand...
Click to collapse
Hello~ I copied your wifi folder to system/etc/wifi.. and replaced it, but still don't have wifi after reboot. :crying: Any important process I missed?
lng325 said:
Hello~ I copied your wifi folder to system/etc/wifi.. and replaced it, but still don't have wifi after reboot. :crying: Any important process I missed?
Click to expand...
Click to collapse
Hey! Not sure about your device model, can you confirm it is YP-GI1CW ? Btw, the permissions for the wifi and wifi/softap files should be 644, and 755 for the softap directory. Here's my output:
Code:
# ls -l /system/etc/wifi
-rw-r--r-- root root 274168 2012-03-17 10:05 firmware.bin
drwxr-xr-x root root 2012-03-17 10:05 softap
-rw-r--r-- root root 16295 2012-03-17 10:05 tiwlan.ini
-rw-r--r-- root root 16986 2012-03-17 10:05 tiwlan_cert.ini
-rw-r--r-- root root 883428 2012-03-17 10:05 tiwlan_drv.ko
-rw-r--r-- root root 16985 2012-03-17 10:05 tiwlan_plt.ini
-rw-r--r-- root root 1012 2012-03-17 10:05 wifi.conf
-rw-r--r-- root root 134 2012-03-17 10:05 wpa_supplicant.conf
# ls -l /system/etc/wifi/softap
-rw-r--r-- root root 262356 2012-03-17 10:05 ap_firmware.bin
-rw-r--r-- root root 652 2012-03-17 10:05 hostapd.conf
-rw-r--r-- root root 954932 2012-03-17 10:05 tiap_drv.ko
-rw-r--r-- root root 22424 2012-03-17 10:05 tiwlan_ap.ini
Also, some report flashing the stock kernel solved the problem, but this has some drawbacks (logo lost, warranty voided, device watermarked).
If you solve your problem please report what worked for you
bluk
EDIT: just in case, here are the MD5s
Code:
4fc219f6c48380e5df3c4229d3dfec32 firmware.bin
7525a9d0f212cba5ef4ea78860a9285b tiwlan_cert.ini
4457eadff2e6a0e91c1778c794f2ee21 tiwlan_drv.ko
8bd66fa950e4ecff2b34b4063beb44ef tiwlan.ini
c5d6fcfc2ad06b81db3dc3a5f6e7d98c tiwlan_plt.ini
0db52ef0a3e4941874f7de054abd9fc9 wifi.conf
bbb0cc9dac7a8d03ea4d6d477e49a0ee wpa_supplicant.conf
0e82efa50d450915b200a93246190d08 softap/ap_firmware.bin
880f7954eeb2a01d49295f1bd45e8c31 softap/hostapd.conf
ccfcb7e4d27276b0e3791025b2990e26 softap/tiap_drv.ko
214b2320c13c2242db05c40dbe3944d5 softap/tiwlan_ap.ini
zebluk said:
Hey! Not sure about your device model, can you confirm it is YP-GI1CW ? Btw, the permissions for the wifi and wifi/softap files should be 644, and 755 for the softap directory. Here's my output:
Code:
# ls -l /system/etc/wifi
-rw-r--r-- root root 274168 2012-03-17 10:05 firmware.bin
drwxr-xr-x root root 2012-03-17 10:05 softap
-rw-r--r-- root root 16295 2012-03-17 10:05 tiwlan.ini
-rw-r--r-- root root 16986 2012-03-17 10:05 tiwlan_cert.ini
-rw-r--r-- root root 883428 2012-03-17 10:05 tiwlan_drv.ko
-rw-r--r-- root root 16985 2012-03-17 10:05 tiwlan_plt.ini
-rw-r--r-- root root 1012 2012-03-17 10:05 wifi.conf
-rw-r--r-- root root 134 2012-03-17 10:05 wpa_supplicant.conf
# ls -l /system/etc/wifi/softap
-rw-r--r-- root root 262356 2012-03-17 10:05 ap_firmware.bin
-rw-r--r-- root root 652 2012-03-17 10:05 hostapd.conf
-rw-r--r-- root root 954932 2012-03-17 10:05 tiap_drv.ko
-rw-r--r-- root root 22424 2012-03-17 10:05 tiwlan_ap.ini
Also, some report flashing the stock kernel solved the problem, but this has some drawbacks (logo lost, warranty voided, device watermarked).
If you solve your problem please report what worked for you
bluk
EDIT: just in case, here are the MD5s
Code:
4fc219f6c48380e5df3c4229d3dfec32 firmware.bin
7525a9d0f212cba5ef4ea78860a9285b tiwlan_cert.ini
4457eadff2e6a0e91c1778c794f2ee21 tiwlan_drv.ko
8bd66fa950e4ecff2b34b4063beb44ef tiwlan.ini
c5d6fcfc2ad06b81db3dc3a5f6e7d98c tiwlan_plt.ini
0db52ef0a3e4941874f7de054abd9fc9 wifi.conf
bbb0cc9dac7a8d03ea4d6d477e49a0ee wpa_supplicant.conf
0e82efa50d450915b200a93246190d08 softap/ap_firmware.bin
880f7954eeb2a01d49295f1bd45e8c31 softap/hostapd.conf
ccfcb7e4d27276b0e3791025b2990e26 softap/tiap_drv.ko
214b2320c13c2242db05c40dbe3944d5 softap/tiwlan_ap.ini
Click to expand...
Click to collapse
I sure my device is CW verison, I bought it in Hong [email protected]@ I try to change the permissions on files, still dont work. The only method for me is flash back to Hong Kong Stock Rom ( no root).
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
I finally got my wifi back!!! after I said, the only method is flash back the Hong Kong stock rom.. I suddenly think why I don't extract wifi folders from Hong Kong Stock Rom? So I do it and get work!!!!!!! thanks all ~~
Maybe drivers are different on different country although our versions are same( YP-GI1CW)?????.. btw, I found the details code of my device : YP-GI1CW/XSH<<?
My version is YP-GI1CW/XEF ... probably the cause of problem, I'll mention that in OP thanks; and good job fixing your wifi!
bluk
I was wondering if someone could help. I have followed all the instructions of this post http://forum.xda-developers.com/showthread.php?t=1886460 It says it is successful, but still do not have root access. Could someone tell me if they see something wrong?
Here is the log from Root Checker.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.98 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 91988 2012-11-20 09:39 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your C5155 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Fixed
Removed Super SU all is now ok.
I have been trying to root my Kyocera Rise I just got a week ago, and I am having this problem as well. However it seems that removing SuperSU isn't doing the trick. What was your method of going about this? I'm so lost without root access . I followed the tutorial to a T, multiple times, as other users have suggested, and I get nothing! Thanks for your time!
I had the same problem I went into stuff folder of binry and replaced supersu with su, re-ran it and root took 1st time
Sent from my Amazon Kindle Fire using Tapatalk 2
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Could not get v17 to work. I saw in the thread v3 was supposed to so I tried it and after a few attempts I got it.
Sent from my LG-VM670 using Tapatalk 2
any luck on 4.0.4?
the latest krise firmware version is 4.0.4.
In the thread the guy who reported rooting success didn't say his version num, so it could be outdated information.
I am on 4.0.4, was not aware of any other version for this phone
Sent from my Amazon Kindle Fire using Tapatalk 2
jimchee said:
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Click to expand...
Click to collapse
Could you please be more specific with your procedure?
sonic_knx said:
Could you please be more specific with your procedure?
Click to expand...
Click to collapse
Since you have a rooted copy now, could i borrow a backup or a copy of the system folder because I installed hp beats audio installer (do not do) and my audio drivers are messed up. It is really taking a long time to get a copy so I was hoping that you guys would have a good copy. I also have another guy with the same issue so please help us.
the actual problem and a slight fix...
The actual problem/glitch with supersu is when it tries to promt access for su it freezes the app. When I tried unistalling supersu and installing superuser. It did not work for me even with the proper uninstall procedure (going into super su settings and click uninstall and prepare for new su app. Then go to the play store search supersu, google still thinks installed so click uninstall from there then immediatly search and install superuser.) I even tried going into the root setup folder I downloaded and switched the su apk files to start the root fresh... and still nothing. I figured out its the problem with the app trying to promt you for su access (ether app) bcs when I went into the settings I changed it to automaticaly grant su (TO EVERY APP READ BOTTOM DISCLAIMER) instead of promting you to ask for su.
DISCLAIMER: I AM NOT RESPONSIBLE FOR A ROUGE APP TAKING ADVANTAGE OF YOUR PHONE WITH YOUR SU SET TO GRANT ACCESS TO ALL APPS INSTEAD OF PROMTING YOU FOR YOUR ACTION ON ACCESS.
root VM rise
I used this method to root my Rise it says hydro but works on rise too.
http://www.cricketusers.com/content/646-root-cricket-wireless-kyocera-hydro-tutorial.html
Greetings! My apologies if I've posted in the inappropriate forum. The 3rd gen Fire 7" HD doesn't seem to have a home as yet.
I have rooted and had a working ES Explorer app. I noticed there was an upgrade to what I was using and figured I'd install it. That was a mistake. The newer version (which I was attempting to install directly from the Amazon store) didn't install properly because of the presence of the older. The older no longer worked so I removed (or thought I did) the app. My thought...let's reinstall my old one the way I did before, remove it properly, then try to reinstall the newer version.
I had used Android Injector to get the original on. I try it now and get the following error:
Command issued:C:\Program Files\Android Injector\adb.exe install C:\Installs\Kindle\ES_FIL~1.APK
pkg: /data/local/tmp/ES_FIL~1.APK
Failure [INSTALL_FAILED_ALREADY_EXISTS]
2330 KB/s (2833758 bytes in 1.187s)
I figure fair enough. I'll just use ADB shell and remove it. But there is nothing to remove!
[email protected]:/ # cd data/local/tmp
cd data/local/tmp
[email protected]:/data/local/tmp # ls -l
ls -l
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Any ideas on what I can do? It doesn't seem possible remove a file that doesn't seem to exist. I haven't done much to the system as yet. I've thought about restoring to factory defaults. However, my concern with that is that I've renamed /system/etc/security/otacerts.zip to /system/etc/security/otacerts.zip.old (effort to prevent OTA) and I've disabled the ads by renaming /system/app/dtcp_apk-release-signed_62320010.apk to /system/app/dtcp_apk-release-signed_62320010.apk.old --- if I try to restore to defaults, what are the chances I brick it due to those renamed files?
Or, I could rename them back if someone would be kind enough to offer me the exact command(s) to use in ADB shell so that I can get those files back to a state of being read/write instead of read only as they seem to be now? I'm comfortable with cmd line type stuff. I just don't have a 100% grasp on the exact syntax for some things -- this being one of them.
Any assistance much appreciated!
Files/Directories not hidden
It occurred to me as I thought about this today some more that maybe the file was hidden. So I check:
[email protected]:/data/local/tmp # ls -la
ls -la
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Ok...kills that idea. I don't understand why I'm being told a file exists that I can't see in any way.
DigitalVortex said:
It occurred to me as I thought about this today some more that maybe the file was hidden. So I check:
[email protected]:/data/local/tmp # ls -la
ls -la
-rwxr-xr-x shell shell 89968 2013-11-26 19:35 exploit
-rwxr-xr-x shell shell 188 2013-11-25 00:35 rootme.sh
-rw-rw-rw- shell shell 104564 2013-11-25 00:33 su
[email protected]:/data/local/tmp #
Ok...kills that idea. I don't understand why I'm being told a file exists that I can't see in any way.
Click to expand...
Click to collapse
My 2 cents. Did you check and see if it exists in the /data/app dir where it is installed to by default. check there or /system/app if you installed as root.
Sent from my KFTHWI using xda app-developers app
cdub50 said:
My 2 cents. Did you check and see if it exists in the /data/app dir where it is installed to by default. check there or /system/app if you installed as root.
Click to expand...
Click to collapse
Suggestion appreciated. I checked both places and nothing found that remotely resembles es explorer. I used the -la switch as well to make sure I wasn't missing anything as a hidden file.
I'm fairly stumped at this point and really don't mind setting it back to defaults. My only concern in doing that is making sure I don't brick it given the file renames I mentioned in the original post. I remain open to thoughts/ideas/opinions.
One other thing to try is open the amazon app store and check the cloud storage to see if you can restore the app from there.
Sent from my KFTHWI using xda app-developers app
I tried that in the early stages of recognizing the issue. And I'm wondering if my renaming the file to /system/etc/security/otacerts.zip.old is messing things up in that realm. The newer version of ES Explorer had failed to complete its install and showed on my screen with a little red '!" in the lower right of the icon. I tried to reinstall from the cloud and it wouldn't complete. I then proceeded to remove it from the cloud. The fun part after that is that the app's icon still shows on the Kindle with that "!" on it. I tried to go back into the app store to re-download. It tells me I can't and refers me back to my cloud storage.
Alright, thinking "out loud" here. I suppose if that file is causing this commotion, if I rename it back, there's the potential of everything returning to normal. To rename it back, I can only do that through the adb shell right now. The file perms are read only and if I try to chmod it, I can't because of the dir perms (I think). Would I want to do something like chmod -R 777 system/etc/security/otacerts.zip.old rename and then same command with 644 to set it back? Directories are usually 755 from my recollection. That's why I'm just a little confused on what my syntax should be to rename that file from the command line. I know once I have write privilege I can just mv system/etc/security/otacerts.zip.old system/etc/security/otacerts.zip.
DigitalVortex said:
I tried that in the early stages of recognizing the issue. And I'm wondering if my renaming the file to /system/etc/security/otacerts.zip.old is messing things up in that realm. The newer version of ES Explorer had failed to complete its install and showed on my screen with a little red '!" in the lower right of the icon. I tried to reinstall from the cloud and it wouldn't complete. I then proceeded to remove it from the cloud. The fun part after that is that the app's icon still shows on the Kindle with that "!" on it. I tried to go back into the app store to re-download. It tells me I can't and refers me back to my cloud storage.
Alright, thinking "out loud" here. I suppose if that file is causing this commotion, if I rename it back, there's the potential of everything returning to normal. To rename it back, I can only do that through the adb shell right now. The file perms are read only and if I try to chmod it, I can't because of the dir perms (I think). Would I want to do something like chmod -R 777 system/etc/security/otacerts.zip.old rename and then same command with 644 to set it back? Directories are usually 755 from my recollection. That's why I'm just a little confused on what my syntax should be to rename that file from the command line. I know once I have write privilege I can just mv system/etc/security/otacerts.zip.old system/etc/security/otacerts.zip.
Click to expand...
Click to collapse
I don't think the cert is your issue as I had restored from a backup using safestrap and I had not backed up a game I had downloaded so I restored it from the cloud and I had moved otacert to another directory. Why not just try a different file manager?
Sent from my KFTHWI using xda app-developers app
[RESOLVED] Help: remove file that "doesn't exist" (KFSOWI)
That was a good idea. Trying something else doesn't mean I need to keep that...just a means to an end. So I did. I used that and renamed items to original. Rebooted. The weird stuff still existed - the "!" on the ES Explorer. I was just about to go for the restore when I noticed SYNC at the top of the list. I had never thought to try that. I sync'd the device. The "!" disappeared. I could download ES Explorer 3 from the cloud and this time it installed.
Lesson learned.
DigitalVortex said:
That was a good idea. Trying something else doesn't mean I need to keep that...just a means to an end. So I did. I used that and renamed items to original. Rebooted. The weird stuff still existed - the "!" on the ES Explorer. I was just about to go for the restore when I noticed SYNC at the top of the list. I had never thought to try that. I sync'd the device. The "!" disappeared. I could download ES Explorer 3 from the cloud and this time it installed.
Lesson learned.
Click to expand...
Click to collapse
Glad it's all working. I highly recommend using safestrap to do a backup in case you ever mess up you can restore. I have tested backup and restore and both work with safestrap. I had installed a .zip via twrp and was wedged and did a restore and everything is back to normal.
Sent from my KFTHWI using xda app-developers app
cdub50 said:
I highly recommend using safestrap to do a backup in case you ever mess up you can restore. I have tested backup and restore and both work with safestrap.
Click to expand...
Click to collapse
You're successfully using safestrap on the 3rd Gen Kindle Fire HD 7 then? Just making sure because the more stuff I read in here, the more differences I find between mine and my kids' 2nd Gen HD 7's. I found another example tonight....I have Lookout on their Kindles and it won't run on mine. Anyway, thanks again for the help!
DigitalVortex said:
You're successfully using safestrap on the 3rd Gen Kindle Fire HD 7 then? Just making sure because the more stuff I read in here, the more differences I find between mine and my kids' 2nd Gen HD 7's. I found another example tonight....I have Lookout on their Kindles and it won't run on mine. Anyway, thanks again for the help!
Click to expand...
Click to collapse
Using SafeStrap on Kindle Fire 7" HDX (Thor). Just waiting on a ROM to flash so I get rid of Fire OS not a big fan and I would rather have the google app store amazon app store just doesnt have much selection IMO.