For the last two days I have been trying this Ive been getting this error... EVERYTIME! I cant see that I am doing anything wrong in cmd. No clue what to do.
No luck with moonshine either
Also, installed Ubuntu, ran distiller... Nothing. It tells me to "run distiller again and READ" BTW, all radios were off when this happened
I'm not an expert by any means. But when you downloaded adb, did you download the sdk for android? If so, go to sdk manager and make sure you have all the options under tools installed. Secondly, did you rename it to revone.2.0? I used revone.DNA, and while it took me 24+ hours, and 100s of tries, I finally got it to go through. Just to confirm, so far you have pushed adb revone to the device via the adb push revone.2.0 /data/local/tmp, then adb shell, cd /data/local/tmp, chmod 755 revone.2.0? I have found that some people have gotten success from removing -P from the command.
---------- Post added at 06:42 AM ---------- Previous post was at 06:38 AM ----------
It may work easier if you move adb to a folder in C: and title the folder something like adb_android, and move the revone file in there as well. From there, you can go to the search bar, enter cmd.exe and it will bring you in directly at C:\ adb_android.
Why don't you post this as a reply to the revone thread? We don't need a new thread every single time someone runs into an issue s-offing their phone...
So Im not entirely sure how to open the sdk manager. I unzipped the adb folder (it was the ADT package), renamed it DNA and placed it under my C:\ drive. Also, I had downloaded the updated revone (revone-0.2) and just removed the dash and have tried removing and adding the -P with identical results.. I have also done many factory resets and still the same problem. From what it seems like, my problem would be with the sdk manager?
shobon said:
Why don't you post this as a reply to the revone thread? We don't need a new thread every single time someone runs into an issue s-offing their phone...
Click to expand...
Click to collapse
Im a new member and I'm not allowed to post in that section. Ive gone through darn near every page of that thread and it seems my problem was unique. Sorry for flooding the forum, I was just looking for some help.
jenniferstough said:
I'm not an expert by any means. But when you downloaded adb, did you download the sdk for android? If so, go to sdk manager and make sure you have all the options under tools installed. Secondly, did you rename it to revone.2.0? I used revone.DNA, and while it took me 24+ hours, and 100s of tries, I finally got it to go through. Just to confirm, so far you have pushed adb revone to the device via the adb push revone.2.0 /data/local/tmp, then adb shell, cd /data/local/tmp, chmod 755 revone.2.0? I have found that some people have gotten success from removing -P from the command.
---------- Post added at 06:42 AM ---------- Previous post was at 06:38 AM ----------
It may work easier if you move adb to a folder in C: and title the folder something like adb_android, and move the revone file in there as well. From there, you can go to the search bar, enter cmd.exe and it will bring you in directly at C:\ adb_android.
Click to expand...
Click to collapse
I installed java and got the sdk manager working, everything is installed and I still cant get it to work. ugh
SpacemanJake said:
I installed java and got the sdk manager working, everything is installed and I still cant get it to work. ugh
Click to expand...
Click to collapse
Tbh it took about my tenth time. I don't know why but if you don't want to switch to linux just keep trying
Sent from my HTC6435LVW using Tapatalk 2
SpacemanJake said:
For the last two days I have been trying this Ive been getting this error... EVERYTIME! I cant see that I am doing anything wrong in cmd. No clue what to do.
Click to expand...
Click to collapse
they released an updated zip... maybe try that. mine worked first time this morning no problems
i also cannot post a reply in the regular revone section.
when i download revone-0.2.1 it is not a .zip file...its just a file that cmd wont recognize when i try to push it to the device, it says its not a recognizable file. when i download revone, do i need to move the file to the same directory as adb and fastboot or what?
yes it needs to be in same folder as adb and fastboot
munchy_cool said:
yes it needs to be in same folder as adb and fastboot
Click to expand...
Click to collapse
do i need to change it to a .exe or anything?
nopes...
one last question (which probably should've been my first)...does the DNA already have to be unlocked and/or rooted to use revone? i thought i read that it needed to have an unlocked bootloader to use this.
Got it! Although revone did not work for me at all! I tried to install ubuntu but failed due to windows 8 issue. Downloaded MintLinux 64 bit, used LinuxLive USB Creator to put my .iso on thumb drive, and boot with usb hard disk. In Mint download the 32-bit libraries, download moonshine and run. Done! No adb needed in mintlinux, reboot pc without usb drive if you didnt want to install mint. worked flawlessly.
Related
Important Update on Dec 2, 2011: Please do not update to Vizio Update 1.5. This will remove the root as well as disable this hack. According to user felixand in this Post.
I decided to start a new thread.
For those who would like to root, please see the instructions in the first post of this thread. This works for me.
http://forum.xda-developers.com/showthread.php?p=18805532
### Please use V3 version: DooMLoRD_v3_ROOT-zergRush-busybox-su.zip ###
Edited to add: If the above DooMLoRD method does not work you can use SuperOneClick. SuperOneClick can be found here: SuperOneClick. Download it and expand it. You will also need to download DooMLoRD_v3_ROOT-zergRush-busybox-su.zip. Expand it as well. Copy the new zergRush binary from the files directory of DooMLord into the exploits directory of the SuperOneClick folder. Then run SuperOneClick to root. Thanks to those who tried this method. See post by marvin02 below.
ACKNOWLEDGEMENTS:
I am not the original developer. I just helped test it. Please thank the developer of zergRush who fixed this code on the Vizio. Post by Ch4lky here.
http://forum.xda-developers.com/showthread.php?p=19396835
For those interested in the original source code of this exploit it is here.
Source code: https://github.com/revolutionary/zergRush
Binary: https://github.com/revolutionary/zergRush/downloads
Edited: Info about Vizio update 1.5 on Dec 2, 2011.
so to read into what you are posting - we need to follow directions and use the http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
which is "DooMLoRD_v3_ROOT-zergRush-busybox-su.zip"
again, I am at work and can't download, but does above file contain the additional files called out in the script - namely busybox, su, and superuser.apk - if I were to guess from the filename, I would say yes...
to sum up:
place the 4 fileset(s) into a common directory under your adb setup - for consistency - we'll call this "files"
so we end up with
./files/zergRush
./files/busybox
./files/su
./files/Superuser.apk
is this about right?
Rich
Yes, that is correct.
okay - so the next step is the rewriting of the vold.fstab file to properly map the internal mount point and the external microSDHD card.
I remember seeing something on the Pandigital Novel forums that had suggestions on this topic...
Any ideas as to what the Vizio needs?
1) first so as not to break the current OS settings
2) then, to remap the mount point as needed so that software like APP2SD will behave correctly.
(looking forward to getting home tonight)
Rich
Wow, I was about ready to get rid of this thing. Will be giving this a go today and seeing about some dev support for roms and what not.
Kudos!
For me the doomlord script stuck waiting for the device.
I put the zergrush exploit into the exploits folder of SOC 2.2 (replace the one that is there) and it worked liked a charm.
Edit: SD Card mount point mod
If you are having issues rooting here is some troubleshooting:
To test your connection with adb:
After installing the drivers open a command prompt in the folder where the adb.exe is located at, make sure USB debugging is on and connect your VTAB to your computer.
Now type "adb devices" without the quotes and you should see:
D:\Android\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your serial number here device
If this does not work then adb is not connecting to your VTAB.
For me the version of adb that is packaged with the doom script does not connect, but the version packaged with SOC 2.2 does. I copied the zergRush exploit from doom's script to the exploit folder on SOC 2.2 and used SOC. I am on WinXP Pro.
If you are using 64 bit windows make sure you install the drivers as an admin and run the doom script or SOC 2.2 as an admin.
Now...
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Maybe now that it has root, XDA should create a subforum for it?
blackcog said:
Who feels like making a custom recovery?
I guess I'll start on CWM porting...
Click to expand...
Click to collapse
This is great. Please post your progress. That will be very helpful.
majorpay said:
Maybe now that it has root, XDA should create a subforum for it?
Click to expand...
Click to collapse
We have to request it here.
http://forum.xda-developers.com/showthread.php?t=1301121
rprr said:
This is great. Please post your progress. That will be very helpful.
Click to expand...
Click to collapse
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
May I ask how you are trying to dump the boot img?
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
sigeltek said:
Hey rprr, I just wanted to say I love you and offer you any females in my family for inpregnation.
Click to expand...
Click to collapse
Thanks, I showed that to my DW and she burst out laughing But, the real credit should go to the devs of zergRush and Ch4lky in particular. Please see my OP for the link to Ch4lky's post if you wish to "Thank" his post.
Same problem here.
The doomlord rooting kit did not work for me either. However, the superoneclick 2.2 with zergrush exploit copied into the exploit folder did work.
---------- Post added at 09:13 PM ---------- Previous post was at 08:52 PM ----------
Do get my device rooted runnning ADB under Vista (32-bit) I did the following:
1) First the Vizio provided ADB driver would not install. I instead did the following.
2) After making sure that any previous drivers were uninstalled from Device Manager including the Android Composite ADB driver. This driver would install for my VTAB successully but I was unable to communicate to the tablet using ADB. I deleted this driver and clicked on "delete the driver software". I also deleted the USB mass storage device and USB composit device.
3) I did a clean boot of the VTAB and then enabled the USB debugging.
4) I connected the VTAB to the USB port and this enabled "installing new hardware"
5) On my machine, I allowed it to search for the device driver and the key was to ensure that it would fail and close.
6) Go into control panel, device manager and you should now have other device named VTAB1008 with yellow highlight.
7) Right mouse click and select "update driver software"
8) then select "browse my computer for driver software"
9) then select "let me pick from a list of device drivers"
10) Select "ADB interface" and then select "Android Sooner ADB testing interface".
11) Once this driver was installed, I was successful in seeing the VTAB through ADB.
12) Install SuperOneClick version 2.2
13) Download the doomlord V3 toolkit and copy the zergrush file under the /files directory to the exploit directory under SuperOneClick (replacing the existing zergrush file)
14) Once this was done, SuperOneClick was successful
rprr said:
May I ask how you are trying to dump the boot img?
Click to expand...
Click to collapse
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
blackcog said:
As embarrassing as it is, I'm actually having a terrible time getting a proper dump of the boot img. It seems to be corrupt every time I pull it
Once I get that much, the rest is a breeze. Probably 20 minutes, tops.
Click to expand...
Click to collapse
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
blackcog said:
Actually, after several hours and a chat with a vizio tech, I've finally been able to diagnose it as a hardware malfunction.
On that note, my vtab has died. This is number two. I don't think I'll invest in a third. Sorry, guys.
Click to expand...
Click to collapse
Sorry about your VTAB. May I ask again how you were trying to extract the boot.img?
marvin02 said:
I do not now how to do what you are doing, but I found this guide. Don't know if it is helpful.
Click to expand...
Click to collapse
Thanks. I did try that but still cannot get to the boot.img.
anyone know anything about these tablets? It is a cheap brand from bestbuy, I was just wondering if anyway could help me to get the android market to run on it.. It is a custom Itomic branded rom, it only has swift market or something like that on it.. Also, the recovery is not a regular recovery. When I go into recovery it just shows Itomic on the screen and says recovery mode at the bottom.. Itomic BestBuy That is the link to bestbuy for specs on it..
TIA
Julian
Are you rooted? If you're not rooted then go here: HERE and pick up the latest SuperOneClick program to get you started. Once you're rooted you need to download the latest Android Market apk here: HERE. Put that file on the root of the sd card in your tablet and then use a file explorer such as Root Explorer to find the file. Once you know where the apk is located you can use an APK installer to install the file. Then viola! You now have the Android market on your new tablet.
Trust me when I say you want to avoid a resistive screen (no multitouch) and 256M RAM (slooooow) as I have a 10" tablet with those specs.
Its not mine, i would not buy one with those specs just for the reason of I am used to my evo, not the best phone, but I like the way it responds and I would want the same or better response from a tablet... This is actually my 10 year old cousins tab, and it did not come with the android market as stated above so I am trying to fix that... I am nervous to root it because it doesnt have a regular recovery so if something goes wrong I would not be able to fix it... So I am looking for a dev that has experience with this or a similar tab... If I knew linux programming Id be a dev but unfortunately I dont know and at this point in time I do not have the time to learn...
That one click root program won't hurt anything. I've rooted many tablets and phones with it and it works like a charm, no problem. Once you're rooted and get the market make sure you get rom manager and see if there are any flashable recoveries for the tablet.
Sent from my SkyRaider Bolt using Tapatalk
I also forgot to mention I cannot get adb drivers to work... I have dev on and it still wont recognize the android drivers.. It is not the micro usb but mini usb, I have tried multiple usbs but it still will not find the correct drivers...
I dug into this and just found the tab came rooted, all I had to do was mount the system as rw through adb and then manually changed su to the gb su.. I installed root explorer and rom manager but unfortunately there isnt a recovery for it... I saw on androidtablets.net that a guy is willing to port cwm to any tab for you but am nervous to try anything because it is my cousins... I think for now I will just install the market and be done..
Yeah that would be the best since it doesn't look like it's too widely supported. But cm would give it a smoother feel and be a little nicer, but do what you choose.
Sent from my SkyRaider Bolt using Tapatalk
alil2cul4u said:
I dug into this and just found the tab came rooted, all I had to do was mount the system as rw through adb and then manually changed su to the gb su.. I installed root explorer and rom manager but unfortunately there isnt a recovery for it... I saw on androidtablets.net that a guy is willing to port cwm to any tab for you but am nervous to try anything because it is my cousins... I think for now I will just install the market and be done..
Click to expand...
Click to collapse
I am new to this whole thing, but I just got an Itomic tablet and I am also trying to get the Android market to work. Im stucj though i cant for the life of me get an ADB to work. Ive tried everything I could think of but cant get it to work. What did you do to make it work?
Plewis831 said:
I am new to this whole thing, but I just got an Itomic tablet and I am also trying to get the Android market to work. Im stucj though i cant for the life of me get an ADB to work. Ive tried everything I could think of but cant get it to work. What did you do to make it work?
Click to expand...
Click to collapse
I did it on my laptop, I have windows 7 64 bit with the android sdk installed.. Sdk install guide I think that adb worked just with the sdk installed, because I didnt do anything special that I know of.. I was having trouble getting adb to work on vista where I just had the adb files not the full sdk.. I also have the sdk in my path (if that makes any difference?) I also have all the htc diag drivers and motorola diag drivers installed... If you cant figure it out, just let me know and Ill dig through everything and see if I cant figure out what drivers helped... Also, I didnt use the plug that came with it.. The one I used was much thicker than the one supplied, the one I used came with a card reader... also the su file i used is the latest one posted over at gooinside.me SU.zip To change it i went into adb and
Very often when you want to write files to a particular partition on ADP1, you will get a "Permission Denied" if the partition is mounted read-only.
To get around this, you need to mount the partition read-write. Typically this is done with /system partition
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts) quoted from: android-tricks.blogspot.com
Click to expand...
Click to collapse
mounted the system as read-write then changed the su found in /system/xbin... forgot to add you must extract the su found in the zip folder...
alil2cul4u said:
I did it on my laptop, I have windows 7 64 bit with the android sdk installed.. I think that adb worked just with the sdk installed, because I didnt do anything special that I know of.. I was having trouble getting adb to work on vista where I just had the adb files not the full sdk.. I also have the sdk in my path (if that makes any difference?) I also have all the htc diag drivers and motorola diag drivers installed... If you cant figure it out, just let me know and Ill dig through everything and see if I cant figure out what drivers helped... Also, I didnt use the plug that came with it.. The one I used was much thicker than the one supplied, the one I used came with a card reader... also the su file i used is the latest one posted over at gooinside.me To change it i went into adb and mounted the system as read-write then changed the su found in /system/xbin... forgot to add you must extract the su found in the zip folder...
Click to expand...
Click to collapse
thanks for your help! I got the ADB to work and was able to mount it as rw. But, like I said I am new to this and am still having some trouble. then you say you changed the su found in the /system/xbin what does that mean? how do I get to /system/xbin? Thanks again for your help
---------- Post added at 02:59 PM ---------- Previous post was at 02:41 PM ----------
alil2cul4u said:
I did it on my laptop, I have windows 7 64 bit with the android sdk installed.. I think that adb worked just with the sdk installed, because I didnt do anything special that I know of.. I was having trouble getting adb to work on vista where I just had the adb files not the full sdk.. I also have the sdk in my path (if that makes any difference?) I also have all the htc diag drivers and motorola diag drivers installed... If you cant figure it out, just let me know and Ill dig through everything and see if I cant figure out what drivers helped... Also, I didnt use the plug that came with it.. The one I used was much thicker than the one supplied, the one I used came with a card reader... also the su file i used is the latest one posted over at gooinside.me To change it i went into adb and mounted the system as read-write then changed the su found in /system/xbin... forgot to add you must extract the su found in the zip folder...
Click to expand...
Click to collapse
I was able to get the adb to work and remount it as rw. But like I said im new to this, and Im confused when you say you manually changed the su to the gb su. How do I access the /system/xbin folder? thanks again for you help.
---------- Post added at 03:16 PM ---------- Previous post was at 02:59 PM ----------
actually I figured it out once I got a root explorer. Im able to find the su file, but not really sure what, if anything Im supposed to change. Once thats taken care of , how to I download the android market? Do i just find an APK online for it? Or is therre another program or something I have to go through. Thanks again, im learning...
Sorry its taken so long to reply, when i say I changed the SU in /system/xbin, I opened windows cmd and ran "adb shell" "cd to /system/xbin" "rm ./su" then "exit" still in the cmd i adb pushed the su file that i extracted from this file su-2.3.1-efgh-bin-signed.zip (thanks to goo-inside.me) with "adb push C:\su /system/xbin" I then pushed superuser.apk to /system/app with "adb push C:\superuser.apk /system/app" then "adb reboot" and when it turns back on you are fully rooted. now download gapps from goo-inside.me then extract the system/app from the zip you need to install GoogleServicesFramework.apk OneTimeInitializer.zip SetupWizard.apk Talk.apk Gmail.apk Vending.apk with "adb push *.apk /system/app"
The world's first ereader with a color Mirasol display is finally on the market, but unfortunately it's running a severely locked-down Android by the Korean bookstore chain Kyobo. The Kyobo ui is entirely in Korean, the browser blocks downloads, and the reader app is crap. In other words, it's basically useless to anyone outside of Korea. A few enterprising Americans have imported them and been extremely disappointed. Will someone please take a look at this device and see if it can be rooted or if something else can be done to make it of use to the rest of us?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Nate over at The Digital Reader has a firmware update that supposedly contains all of the installed apps. He is asking for someone to try and hack it. He has a download link for the firmware at The Digital Reader.
I also posted this as a question here on XDA:
http://forum.xda-developers.com/showthread.php?t=1432283
it is rooted since some time already.
files and instructions are in the following archive, but since instructions are in korean, i'll do a writeup below.
(argh! spambot won't allow this link, so you'll have to piece it together...)
www<dot>4shared<dot>com/zip/aLwRc7ZG/mirasol_rooting.html
edit: needed files are also in an attachment below
the gist is that you need to flash the boot partition via fastboot, setup root and busybox, and then modify secure->install_non_market_apps in settings.db.
you will need to have adb and fastboot from the android sdk working on your computer. There are many posts about this elsewhere, so i won't go into the details.
also, i only print filename without path, just find the corresponding file in the mentioned archive and modify the commands accordingly.
flash the boot partition via fastboot
first get your kyobo into fastboot mode (with usb cable attached) by pressing volume-down at bootup. timing here can be a bit finicky, but easiest seems to be to shut it down completely and then press just after pressing power.
issue a 'fastboot devices' on computer, if successful it should give you the response '???????????? fastboot' or similar. if empty or hangs, try again by rebooting the kyobo by pressing power with volume-up held (you can go into fastboot immediately after reboot by volume-down as expected).
when positive response above, you can flash by
Code:
fastboot flash boot boot.img
and then reboot by
Code:
fastboot reboot
edit: simplified fastboot instructions, thanks to smb_gaiden, whose button-poking-fu is strong.
setup root and busybox
with boot partition flashed you now have adb access, so let's use it. let the device boot as normal, and then issue the following.
Code:
adb push busybox /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/fixsu.sh
adb shell ln -s /data/local/tmp/busybox /system/xbin/busybox
after this, install some apk's from the archive
Code:
adb install superuser.apk
adb install blackmart.apk
fix non-market apps setting
only thing left is to change a setting to allow non-market apps to be installed. if you don't care about your current settings (locale, etc), you can just push the settings.db from the archive like so:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
if you *do* care about your settings, you'll need to pull the settings.db, edit it in some sqlite db editor (set secure->install_non_market_apps to 1) and push the result.
that's it. all rooted. now you just need to install angry birds and yer' set ;-)
Adb doesn't seem to start properly on device
Hello.
I did succeed in flashing the bootloader via fastboot.
However when I boot device - I see adb on usb only for some initial seconds, and then it disappears.
For that matter my device already had December firmware on it.
Any ideas how to activate adb on device?
Thank you,
Leonid
it may be that persist.service.adb.enable is reset, stopping the adbd service. try flashing the attached boot image instead, see if that fixes it. it is the same as above, except that persist.service.adb.enable is ignored.
edit: i took a look at the december update, afaict it should pose no problem (very few changes in there).
Once these steps are done, how do you install google market?
Thanks.
edit: the original instructions were snafu, so i replaced them with something that should actually work.
getting android market running on the kyobo
needed files are in the attached archive.
install like so:
Code:
adb remount
adb push DrmProvider.apk /system/app
adb push MediaProvider.apk /system/app
adb push DownloadProvider.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
adb push init.qcom.post_boot.sh /system/etc
adb push fix-shared-user.sh /data/local/tmp
adb shell chmod 777 /data/local/tmp/fix-shared-user.sh
adb shell /data/local/tmp/fix-shared-user.sh
wait for the reboot, find market in the menu, and off you go (with downloads this time ;-)
if downloads still do not work after this, try re-executing the last line. android periodically writes to the file we are modifying, which might clobber our changes if unlucky.
I am thinking about buying one of these because I have seen it on sale for 50% discount. However, the general reviews aren't too encouraging, so will rooting make any difference to overall performance?
fatboy1976 said:
I have seen it on sale for 50% discount.
Click to expand...
Click to collapse
where is that?
throwaway4096 said:
you'll need GoogleServicesFramework.apk and Market-3.4.4.apk from the following links:
http://androidmarketu.googlecode.com/files/GoogleServicesFramework.apk
http://forum.xda-developers.com/showthread.php?t=1391565
install like so:
Code:
adb remount
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
find Market in the menu and off you go.
Click to expand...
Click to collapse
I'm finding the market force closes when downloading an app.
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
rooting for beginners
Some friends and i ordered the kyobo to solve our eye-problem (nystagm)
We still can´t figure out, how to root it.
Can you please give us some rooting instruktion vor beginners??
It would be so essential for us, as the kyobo is little worth without forgeign apps!
Thank you very much!
Joe
send2toonie said:
I'm finding the market force closes when downloading an app.
Click to expand...
Click to collapse
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
smb_gaiden said:
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
Click to expand...
Click to collapse
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware update on my kyobo, that is found on the web, as instructed from the SD card. Then I installed fastboot and adb on my computer (search for 'how to install fastboot and adb'), as I found instructions for that as well. To enter fastboot I kept Kyobos, volume down button for about 10 sec, when booting the device (kyobo connected to computer with USB) - nothing happens -> however on my computers command window (cmd), 'fastboot devices' command produces an answer with '? ..' as it should. The biggest issue I had was to get adb working. For this purpose I installed and removed a couple of USB drivers - I don't really know how I got it to work finally.
You can tell if you have succeeded installing a useful usb driver, if you enter the 'adb devices' command in the cmd window and it returns a device number. Then you are ready to go with the rest of the commands/instruction as seen in the insturction of this thread.
From the blackmart application I was able to install many useful applications - the Launcher application can replace the Kyobo "home" application, which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Hey Guys!
is there a way to root the kyobo via mikrosd?
thanks a lot
Joe
Hey Joe. I've seen you on this forum as well as The Digital Reader asking for help with the Kyobo rooting. I too am a beginner and I'm trying to build up the nerve to try it. Wish us both luck and I hope someone can share rooting-for-dummies with us.
@fatboy1976: rooting won't improve performance in itself. it makes the device better as you can install apps, but ofc the hardware is still the same.
@send2toonie: yes, sorry about that. it worked for me, but only thanks to other changes. it's hard to keep track :-/. i updated the original post with new instructions which should work properly.
@smb_gaiden: hah, excellent, i never tried that! original post updated.
@Joe84: it should be possible to root via microsd by creating an update.zip. i haven't gotten around to trying that yet, but maybe in future. for now this is as simple as it gets.
Kaarlos said:
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware ...(updated -see above..) .., which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Click to expand...
Click to collapse
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Kaarlos said:
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Click to expand...
Click to collapse
Hi,
Could you post the OS/processor version and driver name that got adb working for you. If you can also remember the keys pressed to put the Kyobo in the correct boot mode for adb, that would be nice too.
I have also managed to load apps on my Kyobo but that is without having su, Superuser, adb and Android Market working. The above info would be helpful in fixing that. Holding the volume down fir 10 seconds after pressing power on puts the Kyobo into fastboot mode. Adb requires a different mode and set of key presses. This is because there is a menu of boot options being displayed which can't be seen on the Mirasol screen. I suspect this is because of display settings within the boot.img but that is only a guess on my behalf.
VRoot Cleanup Tool - Easily replace VRoot with SuperSU
From your Windows PC
OK everyone, here's the deal. I did the VRoot the toher day on my phone and it worked great. The problem is that it can be tricky to get the old Chinese Superuser app and SU binaries updated to SuperSU. As a result I decided to put this tool together to help update the VRoot files to SuperSU, and get rid of the old VRoot ones. What this means is that you can now clean up the Chinese Super User app and completely install SuperSU with a single click, from your Windows PC.
How to use:
Download Root Cleanup from here: https://www.dropbox.com/s/sto74q58uq4r1bj/root_cleaner.zip
Extract it to a folder on your computer.
Open the new folder and double click the clean_root.bat file.
Follow the directions.
** You will want to make sure that USB debugging is on (which it should be from VROOT) and that VRoot is closed when you run this. **
Also note I only have one phone to test with, and it worked great on the one I have. Please let me know if you have any other issues and I will try my best to help. Also, as always, not responsible for problems . <3
Edit: I just got asked via PM if this is to be run after freezing VRoot, etc. So I wanted to add here in case anyone else wondered. With this tool you do not need to freeze VRoot, delete any files, etc. My script will literally take care of everything for you. So, run VRoot and the phone will reboot. You can immediately close VRoot on your computer and run this to completely replace VRoot with SuperSU, and remove VRoot files.
This is my first time writing something like this, but so far I have a lot of people who told me it works fine. Please let me know if you have issues and Ill do my best to help! I went ahead and created this thread at the request of some people who have had good success with this on the other thread here: http://forum.xda-developers.com/showthread.php?t=2511815&page=29
Update: V4 is up - this version makes sure that ADB is accessible. Thank you @k1mu for helping me with this!
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
fabrilas said:
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
Click to expand...
Click to collapse
My guess would be these lines:
adb shell "su -c 'rm /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm /dev/com.mgyun.shua.su.daemon'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su.daemon'"
The issue is that I cant remember if com.mgyun.shua.su and com.mgyun.shua.su.daemon are directories or files. If you could confirm for me which they are then I will be happy to fix my tool!
Thx
Angie
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Works also with Galaxy S4 Italy Gt-i9505 :good:
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
LilTechPrincess said:
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
Click to expand...
Click to collapse
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
ComputerBro2 said:
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
Click to expand...
Click to collapse
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
k1mu said:
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
Click to expand...
Click to collapse
Thank you very much for the help! Im still a newb! haha Anyhow, I updated my tool with your suggestion.
LilTechPrincess said:
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
Click to expand...
Click to collapse
No the adb won't start on my phone
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Bfitz26 said:
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No it freze on this
rm failed for /sdcard/install-recovery.sh, No such file or directory
when i disconnect the pone say not found for 4 or 5 times and finish
---------- Post added at 08:49 PM ---------- Previous post was at 08:28 PM ----------
I tri 3 times
try to wipe all data.
Next try is to reinstall last firmware update whit odin or it trip my knox 0x0 to 0x1 ?
MexyHKR said:
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Click to expand...
Click to collapse
Thats not a big deal. Basically, I removed the /sdcard/install-recovery.sh from the script earlier and forgot to not try and delete a file that doesnt exist... Ill fix that! haha That doesnt hurt anything at all. Sowwy!
Ok now im freeze on Cleaning Up Files....
Your link is down
Tomsgt said:
Your link is down
Click to expand...
Click to collapse
The link has 2 hh's in the http
eklipz3 said:
The link has 2 hh's in the http
Click to expand...
Click to collapse
thanks did notice that
Finaly dont work on my GS4
PDA: I9505XXUEMJ7
MODEM: I9505XXUEMJ7
CSC: I9505ITVEMJ8
Try 2 times after full wipe and emergency firmware restore.
Freeze on Cleaning etc...
Now need to go sleep 1:06AM in italy
Good night and sorry for bad speak
I speak like a fish trying to speak Russian
This thread has been deleted.
This thread has been deleted.
This thread has been deleted.
***** really really really reserved*****
Working w/ Root on a Mac (OSX Yosemite)
CONFIRMED: This works using AT&T (SM-R750A), OSX (Yosemite), VirtualBox and Windows XP. See this link for the driver setup I used on my Mac.
http://www.onebadkid.com/?p=6930
I also find that after factory reset, I still have root! Great job!
---
Also, I haven't been able to get the scripts to work in the virtual machine so I've just been "pushing" the files manually. I did open up the scripts to get the destinations for the various files, so thank you OP. Also, you have to have the Tizen Wearables SDK installed and then use SDB commands in the terminal.
Remember, when using SDB on a Mac, it's: ./sdb [command] (you have to use the "dot-slash")
./sdb devices (to show whether or not your device is connected)
./sdb root on
./sdb shell (puts you into the device's shell so you can navigate the device in a Darwin/Linux terminal)
./sdb push [/full path of the file you want to upload to the device] [/full path of the desination]
I usually open up three Darwin/Linux Terminals on my Mac. One to use to navigate my watch in shell, the other to run the ./sdb command (just like in Windows, you have to run SDB on the mac from within it's home location: "/Users/[you]/tizen-wearable-sdk/tools"), and a third to drop files into so I can quickly see their full file path/location.
"PWD" = print working directory so you can use that in the Darwin/Linux Terminal so you don't get lost.
I'm using Windows 8.1 (don't know if it matters) but after updating to this driver my PC no longer recognized my Gear S. Had to roll back to previous driver.
Ohhhhh!!!
ohh SO installing these and getting it ready for the rest
Edit: got rootfs.img odin'd in so now i wait lmao
Wondering
Good write up so far. I had already gotten root from the previous thread with horrible direcions. LoL After I got my replacement gear s (ALWAYS CHECK YOUR SIM COVER), I rooted it using the bad direction method again (luckily I already know how to do these things), but your directions are very clear cut and noob friendly. You're doing a huge favor to new comers who come looking to root their gear. Hopefully they don't brick them before they find this.
cipherswitch said:
Got any request for certain alarms, notification sounds or ringtones? Shoot me a PM and I will get through them as fast as I can and repost here.
No themes as of yet, but I will definitely be working on custom clock faces apart from everything else
Click to expand...
Click to collapse
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Do this
sdb root on
sdb shell
chmod +x /bin/setup-folder.sh
./bin/setup-folder.sh
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
cipherswitch said:
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
Click to expand...
Click to collapse
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
new rootfs uploaded as of 12/17/14 8:42 am est, I also updated the link in the writeup.
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Megaflop666 said:
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
Click to expand...
Click to collapse
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
You'll be fine!
You will be fine. I've been able to restore from this screen using stock.
Um actually..... its easier. Connect your gear, drop your content into the right folders (eg; ringtones, alerts and such) and run the update script. done and done.
ipstack said:
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Click to expand...
Click to collapse
sbrownla said:
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
Click to expand...
Click to collapse
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Megaflop666 said:
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Click to expand...
Click to collapse
Hm ... what was it doing when you tried to flash?!
I was working on changing some permissions, rebooted it and it never came back, don't even have recovery. From what tmo said, this has happened to other people on this watch