Related
Hi,
I rooted my x10 a week ago following the usual method step by step and everything went fine, phone was much faster than in 014, i had su apk installed...
The problem is that yesterday i tried barnacle for tether, and for my surprise, it said i have no root. I tried opening terminal and su command but nothing. I tried a method found in a topic to gain root, mount -o remount, rw.... and it gave me an error with the path this method uses....
Now i cant do the process again since i have no computer with me. Is there something i can do?
Thanks!!
Sent from my X10i using XDA App
Straf said:
Hi,
I rooted my x10 a week ago following the usual method step by step and everything went fine, phone was much faster than in 014, i had su apk installed...
The problem is that yesterday i tried barnacle for tether, and for my surprise, it said i have no root. I tried opening terminal and su command but nothing. I tried a method found in a topic to gain root, mount -o remount, rw.... and it gave me an error with the path this method uses....
Now i cant do the process again since i have no computer with me. Is there something i can do?
Thanks!!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Is Superuser installed?
If not, install it using this apk: http://dl.dropbox.com/u/5653599/Superuser.apk
Yes, it is installed, when i open it, shows nothing
Sent from my X10i using XDA App
Make sure step one is completed properly, and all steps are. I had same problem. Because effectively all you have done is install the apps without actually rooting. Start over, take your time and make sure all steps complete
Sent from my rooted x10a using XDA app
Happened to me using the "Newbies guide", so make sure you complete all the steps.
Mine is a froyo 2.2.1 device (ViewSonice VB730), I tried z4root, instant root, DPRoot, and many many many rooting apk but it is not working, some of them are FC or some of them are stucking in "attempting to apply root"
I tried to use SuperOneClick but since I can't find a suitable driver for it, so when I use "adb devices", the list is empty.
I also checked out about some article about how to manually root a devices with PC, seems I have to copy the necessary file first to /data then run the exploit. Since I dont have the driver, I tried to do it with Terminal Emulator and tried to grand access right of /data but failed.
cd /data/
$ ls
ls: can't open '.' : Permission denied
$ chmod 777/data
chmod: /data. Operation not permitted
What should I do
Still no one answer this..
Sorry, I cant help you. Just interested in the right answers.
Not sure but if you can find a copy of Z4Root it might work on Froyo
Sent from my Transformer TF101 using Tapatalk
baseballfanz said:
Not sure but if you can find a copy of Z4Root it might work on Froyo
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I have tried it before but it keep stucking at "attempting to apply root"
I am here and still waiting for the answer..........
Another 12 hours has just passed...
Another 12 hours just passed......again
Don't be so sad. I am here with you.
Mr.Wrong said:
Don't be so sad. I am here with you.
Click to expand...
Click to collapse
Thanks
I just wonder if I post this in wrong section so no one is here
Nooope, maybe just the ones who can answer it are happened to be falling in love with their ladies and cant spare time here. Why don't you try some ways of rooting the similar phones. There are so many people out there talking about rooting their devices everywhere, maybe you can try some. Next time I will copy for you.
Mr.Wrong said:
Nooope, maybe just the ones who can answer it are happened to be falling in love with their ladies and cant spare time here. Why don't you try some ways of rooting the similar phones. There are so many people out there talking about rooting their devices everywhere, maybe you can try some. Next time I will copy for you.
Click to expand...
Click to collapse
I tried almost any method before opening this thread.. like Superoneclikc, z4root or some similar ways or apps, but if you still have any recommendation for me, I will still try it and thanks
few days passed, still try to pump this for hope
still try to pump this for hope
I wonder ViewSonic vb730 is same as Creative ZiiO 7" tablet in view of their features and CPU. The guide at http://forum.xda-developers.com/showthread.php?t=1010402 may also apply for ViewSonic vb730
aleunghk said:
I wonder ViewSonic vb730 is same as Creative ZiiO 7" tablet in view of their features and CPU. The guide at http://forum.xda-developers.com/showthread.php?t=1010402 may also apply for ViewSonic vb730
Click to expand...
Click to collapse
(pump thread and reply )
I heard about this method before, but the main problem is I can't find the suitable driver for the device so I am not able to perform any action related to the adb.. can you tell me which one you have choosen which one for your Creative ZiiO 7"? Thanks a lot!
few days a pump
I'm going to say I have the same problem with the VB730. I wish to root this thing but can't seem to make it work (in spite of hours and hours of work). Programs I've tried:
Z4 Root
Universal Androot
Instant Root
SuperOneClick
I've also attempted to do it by hand. No dice. I have installed File Expert which allows me to see all the files including the system files, however, I cannot write to these files nor change them without at least temporary root access.
After looking around though, I think the problem seems to be the same as the Creative ZiiO tablet in that there is no driver available for the USB debugging and even once you get those files, the Android system files aren't in normal places so you'd have to figure out a workaround for it.
I tried following the guide here and I believe this would work but for the problem of the USB driver. I wrote to ViewSonic asking for a solution to get my USB Debugging to work but they have no idea what to do it seems. Or they just don't care enough to figure it out.
I tried using the PID, VID and MI for the ZiiO as per the guide (despite it being for a different vendor and product) which got the driver to install and recognize the VB730 as an Android device (when first installed, it came up with a bad parameter but I restarted the device, reinstalled the driver and the problem disappeared) but I am unsure where to make and put the adb_usb.ini file as there isn't a ".android" file located on the VB730 (there IS a ".android_secure" folder on the write-able portion though). So, when checking for devices through ADB I get a readout that says no devices are connected.
Anyone have any ideas on what else I (we) could try? Thanks both for the help already given and any still to come!
Try superoneclick 2.1.1 ,It may help you.
cuplzz said:
Try superoneclick 2.1.1 ,It may help you.
Click to expand...
Click to collapse
Nope! That's the version I tried. Not going to work.
Hello dév. I love you're work, you rock our geek world, but it seem to some Prime as a little difference to other, and we do not use your work as we whant :
- No OTA update possible
-The serial number on pref=> about is 'unknown'
-No root possible
For me, and please, someone can test to confirm my theory, root is impossible with standard methode on xda (forum.xda-developers.com/showthread.php?t=1426280)
on root, failed by error : cannot create /data/local.prop: permission denied
exemple : forum.xda-developers.com/showthread.php?t=1426280&page=12
It seem to OTA, unknow and no-root is seem to be a problem on local.prop (?)
I'm NOT developeur, just advanced user, i call any devellopeur to help us, my tablet is yours for test to solved this real fail from Asus. Thank
Sorry, but why should a Dev think about fixing some broken TF201, without an unlocked bootloader impossible anyways ... Only one who will solve this for you is your warranty at ASUS.
http://forum.xda-developers.com/showthread.php?t=1366437
Sent from my ADR6425LVW using XDA Premium.
Ok, I do more try to understand why some prime as this problem.
I try to root via TPSparkyRoot method :
adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
cannot create /data/local.prop: permission denied
adb shell ls /data/
opendir failed, Permission denied
Click to expand...
Click to collapse
But /data/local/ is ok:
adb shell ls /data/local/
busybox
installbusybox
installbusybox2
nachoroot.bin
sysro
sysrw
tmp
tmp.bak
unroot
unroot2
Click to expand...
Click to collapse
It seem that /data/ permision is the problem, right ?
Any help is welcome.
I also had this problem. I undid step 1, rebooted the tab, tried again, and it worked (somewhat inexplicably).
I think it had something to do with Asus Sync, which I installed to get the drivers. If you did too, try killing that on your computer, see if it works then.
Everblue said:
Ok, I do more try to understand why some prime as this problem.
I try to root via TPSparkyRoot method :
But /data/local/ is ok:
It seem that /data/ permision is the problem, right ?
Any help is welcome.
Click to expand...
Click to collapse
chinly43 said:
I also had this problem. I undid step 1, rebooted the tab, tried again, and it worked (somewhat inexplicably).
I think it had something to do with Asus Sync, which I installed to get the drivers. If you did too, try killing that on your computer, see if it works then.
Click to expand...
Click to collapse
Do you mean that you're prime no longer shows " unknown serial"?
Sent from my Transformer Prime TF201 using xda premium
Sorry, no, I just meant that the permission error was fixed that way on a prime that otherwise shouldn't have had a problem.
RichMD said:
Do you mean that you're prime no longer shows " unknown serial"?
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Hey all. i'm following the post here but i'm getting some errors. Looks like other people are getting them as well but I ahven't seen a viable solution yet.
Anyway, I've found the linux folder through terminal (/mnt/sdcard/linux), but get permission denied errors all over the place when i sh install.sh. I apparently can't access all the places on my phone when I connect it to my PC, so I can't move the folder to my phone even though through windows, that's where I "am" when I put it there.
Does anyone know how I can get this working? Or if there's another way to get Ubuntu on here?
Thanks
Bump
Check out our development dev only section for dev discussions. They are working on making it for our phone. That guide you linked won't work with any phone like they claim.
Sent from my SCH-I605 using xda app-developers app
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Android Cowboy said:
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
johnnydowngrief said:
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
Click to expand...
Click to collapse
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Android Cowboy said:
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Click to expand...
Click to collapse
Then maybe this. http://forum.xda-developers.com/showthread.php?t=1379875 But I'm just guessing here. I dont want to spam this thread. Maybe someone more experienced can help you.
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I will try that. If I could just push a new build.prop to overwrite the old one I put probably be okay. How did restore system files using ADB.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That didn't work for me, I've also trying factory resetting again multiple times through recovery, but no dice.
I got my fastboot cable working, and was able to get the device recognized as "Qualcomm USB modem converter"
I opened a thread about it, any help is appreciated!
Android Cowboy said:
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
Click to expand...
Click to collapse
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
GSLEON3 said:
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
Click to expand...
Click to collapse
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Android Cowboy said:
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Click to expand...
Click to collapse
Did you try either of these drivers:
http://www.4shared.com/rar/kRIFBtGe/qualcomm_hsusb_device_drivers.html
http://drivers.softpedia.com/progDo...dows-7-x64-Windows-8-x64-Download-179130.html
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Since you didn't factory reset, does it show up on adb devices at all while it's trying to boot ?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
So currently its not showing up on adb while its booting, but that's probably because I haven't updated adb in a while. I'm going to update when I get home from work and report back.
EDIT: So I update ADB, which isn't recognizing it, but oddly enough, my computer can see it even after the screen shuts off as an android device. My only guess then is I'm missing a driver or something. Any suggestions?
Android Cowboy said:
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
S_transform said:
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
Click to expand...
Click to collapse
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Android Cowboy said:
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Click to expand...
Click to collapse
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
S_transform said:
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
Click to expand...
Click to collapse
When you ADB shell, are you seeing a "#" which means you are rooted. I'm not the world's expert on ADB but this should help. Once you are shell and rooted you can just chmod 644 or 777 on /system and see if that works. http://gizbeat.com/2103/how-to-change-file-permissions-through-adb/