yashsingh1/xdaforums huggingface dataset:
[Nexus One General] wang1404:
So I went doing go-karts with friends yesterday noon, everything went well until we had no control of the karts and started bumping into each other quite a lot. My baby was in left pocket. when i got out of the kart, the phone was bent slightly enough to crack the screen. :( :( :( :(

even with cracked screen, i could still unlock the phone lol and the notification ball was still blinking.

Had it for almost 2 years already. Power button is still holding up very good compared to others. Volume buttons show no sign of age. Screen is in perfect condition thanks to invisible shield.

Upgrading to Sensation now. wish i could get the prime but i have tmobile :(
[Nexus One General] bassmadrigal:
I've had both the AMOLED screen and the digitizer (the touchscreen) cracked on separate occasions. Both are replaceable and they aren't too expensive. I think HTC will do the AMOLED screen for just over $100, and they will do an advanced exchange with you. (Not sure on the cost of the digitizer, but I would expect it to be similar)
[Nexus One General] wang1404:
Thanks for the info man but it's time i have to give up my baby. The best 530 dollars investment ive made yet. I'm still deciding should i part it out or just leave it how it is :(
[Nexus One General] liam.lah:
I'd seriously wait for the Nexus prime, it should be coming out for t-mobile/atnt too.
[Nexus One General] wang1404:
are you for sure its coming to Tmo and At&t cuz every site i have read said Verizon is having the phone exclusively, which is the reason why they passed on the SGS II.

Though, I just ordered the Sensation. I can always sell that and get the prime when it's out anyways lol.
[Nexus One General] battlekry:
It is highly probable the next "Google experience phone" will wind up on Tmo and Att as well as Verizon. I can even see Sprint getting it. There is much conjecture to be had that Samsung will be unveiling two Ice cream sandwich based devices at CITA; the event that they postponed but will eventually happen later this month.
[Nexus One General] qreffie:
A GSM version of the phone already was approved by the FCC last week that had both the AT&T and T-Mobile bands with no CDMA antenna, so it'll likely be on all carriers at some point before the end of the year.
[Nexus One General] onesavior:
I miss my roller ball sigh
[Nexus One General] battlekry:
Yep, HTC implements notification alert protocols on their devices like very few manufacturers do...
[Nexus One General] maumaumau:
why disappointed?

you can easily replace it.
[Nexus One General] bmw83:
My advice. If you have the option 'change the screen.
[Android Q&A, Help & Troubleshooting] wasdf:
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 :confused:
[Android Q&A, Help & Troubleshooting] wasdf:
Still no one answer this.. :(
[Android Q&A, Help & Troubleshooting] Mr.Wrong:
Sorry, I cant help you. Just interested in the right answers.:)
[Android Q&A, Help & Troubleshooting] baseballfanz:
Not sure but if you can find a copy of Z4Root it might work on Froyo
[Android Q&A, Help & Troubleshooting] wasdf:
I have tried it before but it keep stucking at "attempting to apply root" :(
[Android Q&A, Help & Troubleshooting] wasdf:
I am here and still waiting for the answer..........
[Android Q&A, Help & Troubleshooting] wasdf:
Another 12 hours has just passed...
[Android Q&A, Help & Troubleshooting] wasdf:
Another 12 hours just passed......again :(
[Android Q&A, Help & Troubleshooting] Mr.Wrong:
Don't be so sad. I am here with you. :D
[Android Q&A, Help & Troubleshooting] wasdf:
Thanks :D

I just wonder if I post this in wrong section so no one is here:confused:
[Android Q&A, Help & Troubleshooting] Mr.Wrong:
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.
[Android Q&A, Help & Troubleshooting] wasdf:
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 :D
[Android Q&A, Help & Troubleshooting] wasdf:
few days passed, still try to pump this for hope :)
[Android Q&A, Help & Troubleshooting] wasdf:
still try to pump this for hope :)
[Android Q&A, Help & Troubleshooting] aleunghk:
I wonder ViewSonic vb730 is same as Creative ZiiO 7" tablet in view of their features and CPU. The guide at http://xdaforums.com/showthread.php?t=1010402 may also apply for ViewSonic vb730
[Android Q&A, Help & Troubleshooting] wasdf:
(pump thread and reply :D)

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! :)
[Android Q&A, Help & Troubleshooting] wasdf:
few days a pump:D
[Android Q&A, Help & Troubleshooting] eyowzitgoin:
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!
[Android Q&A, Help & Troubleshooting] cuplzz:
Try superoneclick 2.1.1 ,It may help you.
[Android Q&A, Help & Troubleshooting] eyowzitgoin:
Nope! That's the version I tried. Not going to work. :(
[Android Q&A, Help & Troubleshooting] wasdf:
Oh.. I also tried what you have all tried before :(

and yes.. I contact Zii before and they said they dont have any driver for the device and told me to turn off the usb debugging -,-

I also tried some "universal usb driver" but when I run adb devices there are no devices in list too...
[Android Q&A, Help & Troubleshooting] aleunghk:
I just tried the the procedures below and was able to establish ADB connection to my VB730 device.

- Get the google adb driver

- Download and install Google USB driver; then open file android_winusb.inf from the driver's directory and find sections

[Google.NTx86] (for 32-bit Windows) or

[Google.NTamd64] (for 64-bit Wndows).

At the end of the section, add the following lines:

; ZMS-80

%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102

%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01

- Restate your windows workstation.

- Turn on USB debugging mode on your VB730 then connect it into your computer

- Find the device in Device Manager and update driver using previously installed USB driver. The driver installation might take a while. Having completed the driver installation, there would be "Android Composite ADB Interface" under "Android Phone" shown on your Windows device list.

- Add following line to %HOME%/.android/adb_usb.ini:

0x2350

- Start ADB
[Android Q&A, Help & Troubleshooting] wasdf:
Thanks dude, but I dont understand the step in red..

add 0x2350 in adb_usb.ini?

Also have you tried to use SuperOneClick to root it? Thanks

EDIT (1):

I dont have adb_usb.ini in my %HOME%/.android/adb_usb.ini, so I have created one with the follow content, is it right?

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.

# USE 'android update adb' TO GENERATE.

# 1 USB VENDOR ID PER LINE.

0x2350

EDIT (2):

after creating the adb_usb, the adb connection is successed, now try superoneclick :D

D:\android-sdk_r15-windows\android-sdk-windows\platform-tools\adb.exe devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

000000023c5d43e002352d2000813b2? device

EDIT (3):

Superoneclick just done the "half of the work", it push busybox and chmod it but not yet rooted..

I am trying to figuring out why...

btw the log of SuperOneCick

Killing ADB Server...

* server not running *

OK

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

Running psneuter...

ROOTED

Pushing busybox...

2888 KB/s (1062992 bytes in 0.359s)

OK

chmod busybox...

OK

Getting mount path...

FAILED

Or anther exploit still the same result...

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

Pushing rageagainstthecage...

337 KB/s (5392 bytes in 0.015s)

OK

chmod rageagainstthecage...

OK

Running rageagainstthecage...

ROOTED

Pushing busybox...

4429 KB/s (1062992 bytes in 0.234s)

OK

chmod busybox...

OK

Getting mount path...

FAILED
[Android Q&A, Help & Troubleshooting] eyowzitgoin:
Got it! Thanks much! Finally... Now to root this thing. ^_^ Will report back when finished!
[Android Q&A, Help & Troubleshooting] eyowzitgoin:
I GOT IT!!!!

Took some work, but I finally cracked this sucker. :D

How to root the ViewSonic ViewBook 730:

Installing the driver was a pain to start with. After you get that, don't use SuperOneClick directly, it won't work. The files for the VB730 are not in normal places. You'll have to do it manually. I followed the guide from a couple of places.

Here's the steps:

download and install Google USB driver

open file android_winusb.inf from the driver's directory. Find section [Google.NTx86] (if you have 32-bit Windows) or [Google.NTamd64] (for 64-bit). At the end of the section, add the following lines:

; ZMS-08
%SingleAdbInterface% = USB_Install, USB\VID_2350&PID_0102
%CompositeAdbInterface% = USB_Install, USB\VID_2350&PID_0102&MI_01

find the device in Device Manager and update driver using previously installed USB driver

add folowing line to %HOME/.android/adb_usb.ini (note! %HOME% refers in windows to c:/users/<YOURUSERNAME> or C:\Documents and Settings\<YOURUSERNAME> in case anyone else can't figure this out):

0x2350

restart server

Pull out the su-v3, busybox, Superuser.apk, psneuter, and GingerBreak files from the SuperOneClick zip. Rename su-v3 to su, and place the files in your ADB Platform-tools directory (or wherever you run ADB from)

Open the command prompt and find your way to your folder with ADB (and other files you just moved)

Start the commands:

adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
adb shell

This should give you temporary root access. There should be a # symbol on the left. Next, you need to exit the shell and then do what SuperOneClick does and change a few things:

#exit
adb push su /sbin
adb push busybox /data/busybox/busybox
adb install Superuser.apk
adb shell
#chmod 4755 /sbin/su
#chmod 4755 /data/busybox/busybox
#exit
adb pull /system/ziilabs/init.rc

This file is the one causing a problem. You need to open it on your computer in a text editor (wordpad worked great for me), and find this line:

mount ext4 /dev/block/mmcblk_data1 /data nosuid nodev noatime nodiratime

And you'll want to change it to:

mount ext4 /dev/block/mmcblk_data1 /data nodev noatime nodiratime

Save your file and then push it back to the VB730:

adb push init.rc /system/ziilabs/init.rc

Then, type:

adb reboot

This will reboot your VB730 and you'll have root! :D

I followed the guide mainly from this thread:

linkerro

And this one:

stawonog

And the start of the actual rooting from an outside source (not sure this link is allowed) here.

As far as I know, this is the current only guide to rooting the VB730. Now time to have some fun! :)
[Android Q&A, Help & Troubleshooting] wasdf:
Thanks bro, I am going to try it right now :D

Finally this problem is solved after 18 bumping-thread-days..... lol

Just tested and..................... Yeah! :D

Thanks a lot!
[Android Q&A, Help & Troubleshooting] bobtran:
I followed the instructions exactly and was partialy successful...ADB connects and recognizes my VB730, Was able to get temp Root "#" , successfully pushed and chmod'd the busybox and Superuser, modified init.rc as described and pushed it back successfully, adb reboot sucessful......

Result......Titanium could not acquire root privileges.

Can't figure out what is wrong...Need some help somewhere.
[Android Q&A, Help & Troubleshooting] Theonew:
Have you tried updating superuser and it's binary?
[Android Q&A, Help & Troubleshooting] bobtran:
No I didn't...should have thought of that. I will try that.
[Android Q&A, Help & Troubleshooting] FredWorrell:
Same problem

The instructions were great, plenty of info. I'm having the same problem. I can get temp root, but lose root at reboot. Tried updating the binaries, but don't have root privileges. Any ideas? Thanks again for a great tutorial!
[Android Q&A, Help & Troubleshooting] bobtran:
Thanks...you saved me the work of going through the root process only to fail again.

I continue to have hope but not a rooted VB730.

By the way mine was purchased from TigerDirect just 1 week ago and runs Android 2.2.1, not sure this is relevant but all info is relevant when trying to figure out why my tablet will not root with these instructs while someone elses will.
[Android Q&A, Help & Troubleshooting] rex013090:
yeah i've been wanting to root and alsao flash my gt p1010 but it seems there aren't many infos about it either and i'm afraid to try the super oneclick it might brick my tab
[Android Q&A, Help & Troubleshooting] bobtran:
Got it - Root access for VB730

I think that I figured out the issue. I did two things different and now have, I believe, full root access (or a very close simulation).

1) Don't remove "nosuid", instead changed it to "suid". (maybe not needed).

2) Install su into /system/bin instead of /sbin.

Now install Superuser (if it is currently installed remove it and re-install).

All other instructions remain the same. (Do just the above if you have already performed the root process previously).

Before these changes:

1) Access "/data" directory Results: error, your phone is not rooted.

2) Install Root Explorer Results: No request for root access and no option to mount as RO or R/W.

3) Install Adfree Results: Fails, Phone must be rooted to install this product.

4) Superuser app Results: Superuser can't update its binary due to install location.

5) Terminal emulator Results: su attempt in terminal emulator fails (no root access).

After these changes:

1) Access "/data" directory Results: Successful access

2) Install Root Explorer Results: Request for access, granted, appears in Superuser, option to mount directories as RO or R/W and ability to change access level.

3) Install Adfree Results: Installation successful, appears in Superuser, App runs and updates.

4) Superuser app Results: Superuser app can successfully update it binary

5) Terminal Emulator Results: su command returns the # prompt (root access granted)

I checked with root checker and it states no root access but I suspect that it can only tell root if the directories are in the normal/expected places

instead of the customized version we have on this device. However....can't seem to find a version of ROM Manager/clockworkmod that works with this

device as any attempt to run a backup using ROM Manager/Clockworkmod results in a factory reset/restore to stock (unrooted) and also disables the stock recovery which starts but

then the screen appears disabled.

I am beginning to suspect that we are dealing with a locked boot loader. I wonder if the Creative ZiiO 7" (which is this same device with a white case) has an unlocked boot loader based on the postings found on the web about the device, including a review that stated that clockworkmod for ZiiO 7" is available (it is and I have it but it again results in a factory reset/restore to stock (unrooted)).

Thanks Viewsonic, once again you go out of your way to shaft the customer (just like you have with the Gtab).
[Android Q&A, Help & Troubleshooting] evanova:
(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!
[Android Q&A, Help & Troubleshooting] bobtran:
First you must install ADB: http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/

Next follow these instructions for setting up ADB (Yes the Gtab istructions work) but then follow the instructions from page 1 of these instructions to get ADB to see your VB730/ZiiO 7": http://xdaforums.com/showthread.php?t=902860

This is how I have done it and my pc can see both Gtab and VB730...best of luck and keep us posted.
[Android Q&A, Help & Troubleshooting] wasdf:
Thanks for the guide but I tried to change nosuid to suid and /system/bin but still can't get perm. root. (and Yes, I have temp root now)

btw I dont understand how perm. root work but I know temp root is running a exploit to get root permission, can someone explain it? (just for my interest :D )
[Android Q&A, Help & Troubleshooting] bobtran:
I'm not sure what you have or have not done/accomplished....If you changed "nosuid" in the init.rc you would have used ADB to "pull" init.rc from the tablet to your pc....use "wordpad" or some other text editor and find/change nosuid to suid, then ADB push "init.rc back to the location you pulled it from, etc.

Second did you push su to /system/bin....if yes did you chmod the permissions afterwards......if yes did you......

Well, you get my point, can you give us a little bit more info....hard to guess what you have done/not done, results of each step, etc.

How do you know that you don't have root.....have you attempted to install/run a program that requires root priviledges such as Root Explorer or Titanium backup?

We can only help if you give us a little more data than simply "it didn't work".
[Android Q&A, Help & Troubleshooting] wasdf:
oh sorry, it is my fault, I should give in details...

I get temp root by running psneuter, now I have symbol # at "adb shell" if I dont reboot the devices.

after that I tried to push su to sbin first..

C:\FOLDER>adb push su /sbin
548 KB/s (26324 bytes in 0.046s)

C:\FOLDER>adb push busybox /data/busybox/busybox
841 KB/s (1062992 bytes in 1.234s)

C:\FOLDER>adb install Superuser.apk
877 KB/s (196521 bytes in 0.218s)
pkg: /data/local/tmp/Superuser.apk
Success

C:\FOLDER>adb shell
# chmod 4755 /sbin/su
chmod 4755 /sbin/su
# chmod 4755 /data/busybox/busybox
chmod 4755 /data/busybox/busybox
# exit
exit

Then I adb pull /system/ziilabs/init.rc, edit with Notepad++, change it from nosuid to suid, adb push init.rc /system/ziilabs/init.rc

to ensure that the init.rc has been edited and pushed properly, I open it with R.E. on the device

To prove that I still dont have root access:

1. I can't mount write in R.E.

2. superuser is not prompting me when the apps need root access

3. I can't use ti backup, it said I dont have root access

4. After rebooting the device, "adb shell" show $ instead of #

Any idea? Thanks.

edit: I also tried to edit "mmcblk_cache1 /cache no suid nodev noatime" but still not working
[Android Q&A, Help & Troubleshooting] bobtran:
I can see the problem (I think)....

You are pushing su to "/sbin", but you should be pushing to "/system/bin"

(see my post above where you got the modified info).

I also changed cashe1 to suid instead of nosuid.

Then:

After you push su to correct place, ("chmod 4755 /system/bin/su"), then unistall Superuser from the tablet and re-install it using ADB install command ( "ADB install Superuser.apk")....if you don't uninstall it then you will get an error about it already being installed. You should then get the root access prompt to allow root to programs requiring it after you reboot your tablet.... ("adb reboot")....

In my case four programs I use requiring root access:

1) Root Explorer (I am unable to remount directories as R/O after root process, however, everything is R/W access which works for granting root access to other programs)

2) Titanium backup

3) AdFree (will not istall unless tablet is rooted)

4) Terminal emulator (type su at the $ prompt returns request for root access the first time and then prompt changes to #, does not request root access after the first time but still gets root prompt #).

these all work and Terminal emulator works as root with the su command.
[Android Q&A, Help & Troubleshooting] azrael293:
one-click?

Has anyone gotten further along for a one-click beta? Not to sound lazy, but I am horrible at working with code, try as I might and never seem to even get temp-root.

If anyone has gotten something going and needs testers, I am willing to test the one-click on my VB730 as the stock ROM and lack of main google apps is definitely a ruining experience for this tablet.