I've owned a Ticwatch 2 for about a year, and it was a great watch, but I decided to get an Android Wear watch, so I sold the Ticwatch 2 and bought a Ticwatch E Ice. I love the Ticwatch E, and I love Android Wear 2.0, but there are a few things I miss about the Ticwatch 2. I really liked most of the watch faces from Mobvoi that were available for the Ticwatch 2, and I was disappointed to see that only about 3 of those cool watch faces came with the Ticwatch E.
I have collected about 100 of the Ticwatch 2 watch faces and posted them here. You can install the watch faces on your Ticwatch E/S via ADB over wifi with a PC. I believe they would work on just about any Android Wear smartwatch.
Here is the link.
https://drive.google.com/open?id=1ifoZpsLFpCUZl1Vbo67avl4NsMpJzsKk
(I hope this isn't breaking any rules.)
EDIT: See post #9
please allow drive folder access.
Here is the updated link
https://drive.google.com/open?id=1ekIGahdY3hblziaW4y1bgf0ngz_aIgk7
Enjoy these awesome watch faces
ThankYou!!
easily install all these watchfaces
Copy and paste all these lines in a text file, change the name from .txt to .bat and then after connecting the watch with adb launch the file .bat
adb install -r "0dyssey_1.0.apk"
adb install -r "adhd Watch face_1.0.apk"
adb install -r "All-Round Flower_1.0.apk"
adb install -r "App Error_1.0.apk"
adb install -r "Armor_1.0.apk"
adb install -r "Aurora_1.0.apk"
adb install -r "auspiciouscloud_1.0.apk"
adb install -r "Black Eye_1.0.apk"
adb install -r "Black Gent_1.0.apk"
adb install -r "Black Steel_1.0.apk"
adb install -r "Blank_1.0.apk"
adb install -r "Blue Eye_1.0.apk"
adb install -r "Blue Light_1.1.apk"
adb install -r "Bohemia_1.0.apk"
adb install -r "Broken Screen_1.0.apk"
adb install -r "Business Time_1.0.apk"
adb install -r "Campus_1.0.apk"
adb install -r "Champagne Gold_1.0.apk"
adb install -r "ChrisTicmas_1.0.apk"
adb install -r "Classic Machine_1.0.apk"
adb install -r "Classic White_1.0.apk"
adb install -r "Coffee_0.apk"
adb install -r "Colorful Pedometer_1.1.apk"
adb install -r "Colorful_1.0.apk"
adb install -r "Cube_1.0.apk"
adb install -r "Dark Knight_1.0.apk"
adb install -r "Dawn_1.0.apk"
adb install -r "Digital Pro_1.0.apk"
adb install -r "Digital_1.0.apk"
adb install -r "Division_1.0.apk"
adb install -r "electric line_1.0.apk"
adb install -r "Electronic TimeZone_1.0.apk"
adb install -r "ElegantGold_1.0.apk"
adb install -r "Elegant_1.0.apk"
adb install -r "Elegent_1.0.apk"
adb install -r "Equation_1.1.apk"
adb install -r "Fashion_1.1.apk"
adb install -r "Film_1.0.apk"
adb install -r "Fish_1.0.apk"
adb install -r "Fluorescence_1.0.apk"
adb install -r "Flyer_1.1.apk"
adb install -r "Forged Gold Time_1.1.apk"
adb install -r "Forged Steel_1.0.apk"
adb install -r "Gem_1.0.apk"
adb install -r "Halloween Skull_1.0.apk"
adb install -r "Hot_1.0.apk"
adb install -r "Intelligent Drive_1.0.apk"
adb install -r "iron sodier_1.1.apk"
adb install -r "Iron Will_1.0.apk"
adb install -r "kingofglory_1.1.apk"
adb install -r "Leader_1.0.apk"
adb install -r "Legs_1.0.apk"
adb install -r "Light Planet_1.0.apk"
adb install -r "Light Shadow_1.0.apk"
adb install -r "Lion dance_1.0.apk"
adb install -r "Lucky New Year_1.1.apk"
adb install -r "Machinery _ Electronics_1.1.apk"
adb install -r "Magic Shadow_1.0.apk"
adb install -r "ManyChickens_1.2.apk"
adb install -r "Mechanical_1.0.apk"
adb install -r "Meteor_1.0.apk"
adb install -r "Mithril_1.0.apk"
adb install -r "Modern Classics_1.0.apk"
adb install -r "Move Fit_2.2.apk"
adb install -r "Music Band_1.5.apk"
adb install -r "Mutual affinity_1.0.apk"
adb install -r "Naturally_1.0.apk"
adb install -r "Neon dive_1.0.apk"
adb install -r "New Year Calligraphy_1.2.apk"
adb install -r "Nightlight_1.0.apk"
adb install -r "Orange Light_1.3.apk"
adb install -r "Paper Folding_1.0.apk"
adb install -r "Paradox_1.0.apk"
adb install -r "Pearl_1.0.apk"
adb install -r "Playboy_1.0.apk"
adb install -r "primetime_1.0.apk"
adb install -r "Quadrel_1.0.apk"
adb install -r "Rabbit_1.0.apk"
adb install -r "Retro Wave_1.2.apk"
adb install -r "Rome_1.0.apk"
adb install -r "Silent_1.0.apk"
adb install -r "Silver_1.0.apk"
adb install -r "Snowflakes_1.0.apk"
adb install -r "source.properties
adb install -r "Space Man_1.0.apk"
adb install -r "Speed_1.0.apk"
adb install -r "Spring Blessing_1.0.apk"
adb install -r "Starry Sky_1.0.apk"
adb install -r "Starry_1.0.apk"
adb install -r "StarWar_1.5.apk"
adb install -r "Star_1.0.apk"
adb install -r "Steel Moon_1.0.apk"
adb install -r "Style_1.2.apk"
adb install -r "suntooblack_1.0.apk"
adb install -r "Super Mario_1.0.apk"
adb install -r "systrace
adb install -r "Tank Battle_1.0.apk"
adb install -r "The Lantern Festival_1.0.apk"
adb install -r "Time Shuttle_1.1.apk"
adb install -r "Transit_1.0.apk"
adb install -r "Tree Planting_1.0.apk"
adb install -r "Twinkle_1.0.apk"
adb install -r "Walker_1.0.apk"
O **** god, it worked on amazfit pace, only stand by not working but i think its can be ported.
Thanks for the wonderful faces.
Flyer, Bluelight and Mechanical are my favorite as they show most info we need on the face.
There is a ghost rider face that I am looking for...any way to extract that apk?
Also are there any where subeye is customizable
anangphatak said:
Thanks for the wonderful faces.
Flyer, Bluelight and Mechanical are my favorite as they show most info we need on the face.
There is a ghost rider face that I am looking for...any way to extract that apk?
Also are there any where subeye is customizable
Click to expand...
Click to collapse
I don't have my TW2 anymore.
Here is the new new link:
https://drive.google.com/open?id=1RsTJzc0l10QUnP52oCtO0_xQ1XNQL0Wn
I was inspired by fsamoggia's good idea and I included a batch file and a linux script in the folder. Find the file named windows_faces.bat or linux_faces. I am new to writing scripts, but I think they will work. Let me know if they work properly, anyone. I also renamed the apk files to make them easier to deal with.
Thanks a lot @zillo:)
Super easy installation thank you @fsamoggia
Much nicer watch faces than any of the 3rd party apps. Much appreciated!
Help
I'm trying to figure out how to install these watchfaces into my Ticwatch S. Any assistance here would be appreciated.
thanks
The Real KC said:
I'm trying to figure out how to install these watchfaces into my Ticwatch S. Any assistance here would be appreciated.
thanks
Click to expand...
Click to collapse
You have to use ADB. Install ADB on your PC. Open a terminal. Connect your watch to your PC with ADB over wifi. Type the command
Code:
adb connect xxx.xxx.x.xx:5555
. Put your watch's IP instead of the x's. The commands to install the faces are in the script. There is a linux script (linux_faces) and a windows script (windows_faces.bat) in the folder with the faces. Download the faces/script files to your PC. Put them in a folder on your PC. make sure the script file is in the same folder as the faces. In terminal, cd to the folder with the faces. Run the script. If using Linux, make the file executable with the command
Code:
chmod +x /path/to/scriptfile
. Then execute it with the command
Code:
./linux_faces
. If using Windows, just double click on the .bat file, you might have to right click on it and "run as Administrator." Just make sure that in the terminal, you are in the directory with all of the files. There's about 100 faces, so it will take a while to install. I believe it should work. Let me know if it worked for you please.
Thanks
zillo:) said:
You have to use ADB. Install ADB on your PC. Open a terminal. Connect your watch to your PC with ADB over wifi. Type the command
Code:
adb connect xxx.xxx.x.xx:5555
. Put your watch's IP instead of the x's. The commands to install the faces are in the script. There is a linux script (linux_faces) and a windows script (windows_faces.bat) in the folder with the faces. Download the faces/script files to your PC. Put them in a folder on your PC. make sure the script file is in the same folder as the faces. In terminal, cd to the folder with the faces. Run the script. If using Linux, make the file executable with the command
Code:
chmod +x /path/to/scriptfile
. Then execute it with the command
Code:
./linux_faces
. If using Windows, just double click on the .bat file, you might have to right click on it and "run as Administrator." Just make sure that in the terminal, you are in the directory with all of the files. There's about 100 faces, so it will take a while to install. I believe it should work. Let me know if it worked for you please.
Click to expand...
Click to collapse
I appreciate your prompt response!! Unfortunately, that is a much more complex process than I am able to accomplish.
Hi, will these watchfaces work for Ticwatch S2 too? Please advise. Thanks.
I don't see why not. I think it will work on any Wear OS watch.
i try on ticwatch pro.
thx
some works fine
others looks like resolution are not right
Just tried it on my Ticwatch C2. The resolution is off, like it's magnified. Doesn't work.
Do these watch faces require ticsystem enabled? If not, can you recommend any other mods/3rd party apps, etc once I disable ticsystem? Any roms that compete with battery life with or without ticsystem running on them? Apologies if this is a general mobvoi thread and you dont have the watch. Noob here with a stock ticwatch e.
cheers
svntsvn said:
Do these watch faces require ticsystem enabled? If not, can you recommend any other mods/3rd party apps, etc once I disable ticsystem? Any roms that compete with battery life with or without ticsystem running on them? Apologies if this is a general mobvoi thread and you dont have the watch. Noob here with a stock ticwatch e.
cheers
Click to expand...
Click to collapse
I haven't tried disabling Ticsystem on my watch. I'm not sure if it has anything to do with it. The Ticwatch 2 watch faces worked on my Ticwatch E but not on my Ticwatch C2. A user said that it didn't work on the Ticwatch Pro, so it seems that it just won't work on newer Ticwatches. I haven't really tried to find a solution. As for ROMs, I've only used stock ROMs on my watches, so I can't comment on that. Too bad Mobvoi doesn't just make all their nice watch faces available for download on any watch.
I glanced over an article last night about them dropping a bunch a bunch of faces from their stable of watches on the play store. That's probably gone or else I'm sure you would have come across it by now.
Try the disable, I'm just a day in but it's supposed to help a bit. Certainly don't miss mobvoi bloat. Cheers
Related
I have a Verizon tab that was rooted. I updated to gingerbread which removed root. Is there a way to root now that I have gingerbread?
Thanks!
you may try SuperOneClick 2.2 with ZergRush...
Thanks. I'll give it a shot.
Soundchasr said:
Thanks. I'll give it a shot.
Click to expand...
Click to collapse
Did it work?
Haven't had a chance yet.
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
receptr said:
I tried it hangs on Step 7.. Does not root.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Telling me, I have gingerbread on mine and it does nothing but forceclose crap all over the place
Lakilaulea said:
I've had the same problem. I can't seem to find a method that works; this Tab isn't getting much attention at all anymore.
Click to expand...
Click to collapse
I was able to get mine rooted by using the kernel from Galaxy Cubed 3 ROM. Downloaded the whole ROM and flashed only the kernel in heimdall. Then I used adb to push the correct files to the system and fixed permissions and rebooted. Worked great.
UPDATE:
If people want to know the adb commands I used, here they are:
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "rm /system/xbin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell "cd /data/local/tmp/; rm *"
You can copy and paste these commands to a bat file and run it in a command prompt window. These were taken from a script used to root devices.
Here are links for the files you need. They are:
su
superuser.apk
busybox
They need to be placed in the same directory that you run the adb commands from.
SECOND UPDATE:
Rather than go through all this, go here:
http://forum.xda-developers.com/showthread.php?p=19678785
This is dsb9938's plain stock EI04 VZW ROM that is pre-rooted. Just flash in Heimdall and you are good to go. As long as you only wipe cache and dalvik, all your apps should stay intact.
Gingerbreak.apk should do the trick. Worked on my P1010
chris_toshiba said:
Gingerbreak.apk should do the trick. Worked on my P1010
Click to expand...
Click to collapse
It did not work on my VZW Tab. Someone said it is because it only works on 2.3.3 and older gingerbread and we have 2.3.5.
BTW, look at my earlier post (second update) to get a really easy way to have rooted stock 2.3.5 VZW Tab.
New possible root method on Thinkpad tablet forums, by OPDECIRKEL. He needs help testing it out.
look here and lets cross our fingers =D
http://www.thinkpadtabletforums.com...nt/yareftpt-yet-another-root-exploit-for-tpt/
opdecirkel released the exploit -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
***EDIT***
updated script worked!
-=HOLLYW00D=- said:
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
Click to expand...
Click to collapse
Not sure if it can help you, but try checking the TPT forum thread again, there has been some advances and troubleshooting going on
Moved To General
As the first post is just a link and contains no development, this has no place in this section
updated -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
Someone thinkpadtabletforum reported that it worked for him.
updated script worked for me! cwm installed fine as well!
I achieved root with the new method on OTA 2.5. Also installed CWM with no issues. Works great.
Sent from my PC36100 using Tapatalk
I can confirm it worked!
I had to update first because the "Disable Battery Discharge" option was not there. (I guess my Tablet stopped getting OTA updates since I was on ThinkPadTablet_A310_02_0024_0065_US... Also, you have to update one at a time, you can't go from 24_65 straight to 37_75. Also, I stopped at 39_86 since I was impatient.)
I like this once since we can see how it worked rather than blindly running some guys program (I never tried the first root.)
I can also confirm the new method to be working. Just rooted my 0089_WE TPT. Works like a charm
I am quoting the following post (i don't have privilege to post there): forum.xda-developers.com/showpost.php?p=23902281&postcount=64
daswahnsinn said:
I unrooted and then updated, now I can't root. I updated the SDK and made sure I have the proper drivers needed. So I take back my easy comment. I'll keep trying I might just manually push the files back.
Click to expand...
Click to collapse
How did it fail? At which stage and what error did you get?
Okay, I'll try and flash the oldest update zip, and it fails as it should, then I wipe the cache part, reboot, and I hit enter when I gets to the unlock screen then the CMD window closes.
EDIT: I spent a good hour or so combing through my PC and these forums and tried both methods a lot, and this one finally worked. It wouldn't let me get to the /cache/recovery/pwn/su part of the script. Thank you all for your support.
I have problems...
Hi all,
Apologizes for my english, too bad to discuss this kind of issues. Sorry in advance.
I had the "fantastic" idea to update the firmware some weeks ago, when I was SU. After this, I've lost most of capabilities!
I tried to follow the procedure, but I cannot reach 'root' in any case. I have version WE089. Downloaded US060, but there's only 065 for Western Europe. I got both, just in case..
Unfortunately, in the first step it failed I'm not able to update anything. The process crashes when is loading old firmware, either US060 or WE065.
I've realised that during the process I loose the USB link connection (when I reboot), and the system tries to install again and again the driver. If the TPT is running in recovery mode, it seems that is not connected via USB... If I have the tablet in "normal use", I see it through the Windows Desktop.
Other question: should I disconnect the Internet connection?
I guess other requirements are right (ADBD, debugging mode,...). It's really annoying, it took me a lot of hours and I haven't found any solution.
Can anybody help me? What I'm doing wrong?
Cheers!
jm
W7 64bits - TPT WE089
@jm
goto device manager. right click on Android device. reinstall device driver.
This worked for me in recovery when the device was not recognized.
Edit: look here: http://forum.xda-developers.com/showthread.php?t=1471106&page=2
What do you mean with loosing the connection? Is the adb driver installed correctly? Where did you get it from? Is it an genuine lenovo driver? If so, than you shouldn't worry!
Perhabs it's the MTP driver, that is missing when you boot into recovery? If it's the adb driver, than you should try jlove's method.
In addition I wanted to inform you, that the new method worked for me, too! Even with some complications... by this way, thanks again to opdecirkel!
Because the run.bat script did't worked correctly, I had to do it manually. So I put the "yareftpt" on C:\\, started cmd.exe, booted the TPT into recovery and changed the directory in cmd.exe with "cd.." to "cd yareftpt" ...followed the instructions with the update...
echo 4. Reboot in RECOVERY: (shutdown the tablet, then start it and press volume + few times until it starts in recovery)
echo 5. Go to apply update, select the update from the sdcard and try to apply it. It will fail, but that is OK.
echo 5. Then, go to 'WIPE CACHE PARTITION' and select it (navigate with volume buttons and select it with power button),
echo 6. When wipe cache complete, press (here) ^<ENTER^>.
and after that I copied the first line of the script into cmd and executed. I did it line after line, just to the next step. (dark green= copy line after line, paste and execute)
adb shell "/system/bin/mkdir /data/local/pwn"
adb shell "/system/bin/mkdir /data/local/pwn-bak"
adb shell "/system/bin/cat /system/etc/install-recovery.sh > /data/local/pwn-bak/install-recovery.sh.orig"
adb shell "/system/bin/mkdir /cache/recovery/pwn"
adb push su /cache/recovery/pwn
adb shell "/system/bin/rm /cache/recovery/log"
adb shell "/system/bin/ln -s /system/etc/install-recovery.sh /cache/recovery/log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -oremount,rw -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache/recovery\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chown root /cache/recovery/pwn/su\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 4777 /cache/recovery/pwn/su\" >> /tmp/recovery.log"
echo 7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete press (here) ^<ENTER^>
pause
some of commands might cause failures, but don't worry and just go on
adb shell "/system/bin/rm /cache/recovery/log"
echo 8. On the device, select REBOOT. When startup COMPLETE press (here) ^<ENTER^>
pause
adb push Superuser.apk /data/local/pwn/Superuser.apk
adb push busybox /data/local/pwn/busybox
adb push su /data/local/pwn/su
adb push pwn-in.sh /data/local/pwn/pwn-in.sh
adb shell "/system/bin/chmod 777 /data/local/pwn/pwn-in.sh"
echo Your PC command prompt appears next. Do the following things:
echo 1. adb shell
echo when '$' (adb shell) appear, do:
echo 2. /cache/recovery/pwn/su
echo when '#' appears. You are root. run the following:
echo 3. /data/local/pwn/pwn-in.sh
now you should try if you have su, even if you don't see in your app list..
download root checker, install, open and try it!
You should have root right now.
In my case, i had root, but no CWM!
So I had to install in manually, but with root it should't be a problem. you only have to download the correct cwm version:
http://forum.xda-developers.com/showpost.php?p=21916505&postcount=71
then I installed it with the Android Terminal Emulator app, because the cmd.exe method did't worked for me. You should just follow the instructions:
or you can copy img file on /data/local/ folder of your tablet (with a file manager with root permissions)
launch "Android Terminal Emulator" application
and tape the instructions
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/NameOfCWMFile.img of=/dev/block/mmcblk0p1
http://www.thinkpadtabletforums.com...nd-development/clockworkmod-recovery-for-tpt/
After a shutdown and reboot into recovery I had cwm! So I am able to do nandroid backups...
In this way, I would particularly like to thank to all devs that made the TPT root possible! Now i like my TPT 1000% more than before...e.g. no status-bar in lecture notes -> sooo great!!
I do get the following error maybe someone can help me out
[*]
[*]
[*]
/system/bin/mkdir: not found
/system/bin/mkdir: not found
cannot create /data/local/pwn-bak/install-recovery.sh.orig: directory nonexisten
t
/system/bin/mkdir: not found
699 KB/s (22364 bytes in 0.031s)
/system/bin/rm: not found
/system/bin/ln: not found
7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete
press (here) <ENTER>
Drücken Sie eine beliebige Taste . . .
it cant find the mkdir command very strange
I'm a little rusty, but are the / and \ facing the correct way? And are you in the correct directory? Not found usually means path is incorrect.
@rangercaptain
thats the commands from the root script. I didnt change them.
the commands are send over from adb shell and the tablet is in root directory i think.
When i go into shell and type in ls i get access denied error.
and you load the update zip and wiped cache before typing the commands, right? You have to do this every time you try to root...
Try to do it with another method. Don't do it directly trough adb shell...just type the shell commands in the cmd.exe
You just have to chance the directory in cmd, before executing the commands.
Then try not to input 'adb shell' before the shortened command, but the whole command as one line like:
adb shell "/system/bin/mkdir /data/local/pwn"
Perhabs it will work..?!?
@neos
yes i do the same procedure.
I also tried over cmd with adb shell "command" and also in shell.
Always the same error.
I looked into the system/bin directory and mkdir does have filesize of 0kb...
Looks like Root has been achieved as there is the following guide on AndroidGeeks.
I am not responsible if you try this, I am just passing along information.
How to root the Kindle Fire HD 7 by pushing SuperUser via ADB commands
1. Download the SU zip file from HERE.
2. Extract the contents from the SuperUser zip in a single folder on your desktop.
3. Go to the newly created folder and open the ‘system’ directory, then open ‘bin’ and copy the ‘SU’ file and paste it in the folder you’ll be working from. Then, open ‘system’ directory and then ‘app’ folder and copy the ‘SuperUser.apk’ file and paste it in the same folder as the ‘SU’ file.
4. Connect your Kindle Fire HD 7 tablet to your PC via the original USB cable. Open Settings app on your Kindle Fire HD 7 and then select ‘Security’ and now you need to enable the ‘adb’.
5. Go to the folder that contains the SU and the SuperUser apk files. Press and hold ‘shift’ key and at the same time right-click in the folder’s white space. Select ‘Open command window here’.
6. Now you will need to push the files by using the command lines below:
adb shell
rmdir /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
7. Your device will restart and the local temp file was removed and now you will have a false link to the whole data directory. After the device reboots you have to enter the following commands:
adb shell
echo ‘ro.kernel.quemu=1′ > /data/local.prop
exit
adb reboot
8. The Kindle Fire HD 7 will now reboot and you need to push the SU binary files. Enter the following commands:
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
9. A new restart will be applied and now you can push the SuperUser apk file. Enter this final command line:
adb install Superuser.apk
10. That is it. You’ve finally flashed the root on your Amazon Kindle Fire HD 7 tablet.
If you didn’t manage to flash this tutorial, then you should ask for more help in comments.
Have a question or issue ? Ask it here !
JaxDomino said:
Looks like Root has been achieved as there is the following guide on AndroidGeeks.
I am not responsible if you try this, I am just passing along information.
How to root the Kindle Fire HD 7 by pushing SuperUser via ADB commands
1. Download the SU zip file from HERE.
2. Extract the contents from the SuperUser zip in a single folder on your desktop.
3. Go to the newly created folder and open the ‘system’ directory, then open ‘bin’ and copy the ‘SU’ file and paste it in the folder you’ll be working from. Then, open ‘system’ directory and then ‘app’ folder and copy the ‘SuperUser.apk’ file and paste it in the same folder as the ‘SU’ file.
4. Connect your Kindle Fire HD 7 tablet to your PC via the original USB cable. Open Settings app on your Kindle Fire HD 7 and then select ‘Security’ and now you need to enable the ‘adb’.
5. Go to the folder that contains the SU and the SuperUser apk files. Press and hold ‘shift’ key and at the same time right-click in the folder’s white space. Select ‘Open command window here’.
6. Now you will need to push the files by using the command lines below:
adb shell
rmdir /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
7. Your device will restart and the local temp file was removed and now you will have a false link to the whole data directory. After the device reboots you have to enter the following commands:
adb shell
echo ‘ro.kernel.quemu=1′ > /data/local.prop
exit
adb reboot
8. The Kindle Fire HD 7 will now reboot and you need to push the SU binary files. Enter the following commands:
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
9. A new restart will be applied and now you can push the SuperUser apk file. Enter this final command line:
adb install Superuser.apk
10. That is it. You’ve finally flashed the root on your Amazon Kindle Fire HD 7 tablet.
If you didn’t manage to flash this tutorial, then you should ask for more help in comments.
Have a question or issue ? Ask it here !
Click to expand...
Click to collapse
thanks, but you realize this has been posted here twice with two different methods (manual and automated) right?
May as well add the link. This autmated way ensures that you won't mistype some lnyx command. (as they are so logical, and English-y) :silly:
http://forum.xda-developers.com/showthread.php?t=1893838
I used this method, and it worked for me.
ffs something always goes wrong
would appreciate help on the command prompt part
It took some doing, but after following the instructions in this link:
http://forum.xda-developers.com/showthread.php?t=2559915
I was finally able to root my Nook Glowlight. The instructions are kind of sprawled out and extremely unclear so I will sum up.
As always, you will need the ADB. In order to install the ADB, you need the Java Development Kit and the Android Studio (formerly known as the Android SDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://developer.android.com/sdk/installing/studio.html
How to obtain root via ADB: The ONLY way you can root is using Windows. I was successful on Windows 7 32 bit, but it may be possible on other versions.
step 1) install bootloader driver.
You need to grab the drivers from here (bnusbdrivers.zip):
http://forum.xda-developers.com/showpost.php?p=49665945&postcount=279&nocache=1&z=184593200683593
then, open the Device Manager (on Windows). Be ready to right click on the new device 'omap3660' that shows.
With the nook turned completely off, plug in a USB cable. you will have less than 3 seconds to right click the new omap3660 device that shows up in the system profiler.
If you were successful and you right clicked on it in time, manually install the Barnes & Noble USB driver (there are entries added to the generic Google drivers for both the TI Omap 3660 bootloader and the ADB device after you modify the uRamdisk later on)
***NOTE***
If you WEREN'T successful on your first try (took me THREE times to get to it in time), you aren't going to get another chance to install the drivers. At least not easily anyway, because after Windows tries to automatically install the drivers for the bootloader and fails, it will disregard the device any time it shows up after that. So, you are going to need to delete the registry entries that it created, which in my experience was easier said than done. Even admin access was not sufficient to make the necessary changes to the registry.
You will need to launch regedit.exe using another tool called psexec which is available here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
after you download the pstools package, copy those .exe files to C:\Windows\System32\ (in order to add them to $PATH in cmd.exe)
Then, once you've installed the pstools commands to C:\Windows\System32\, run cmd.exe as admin (right click it and select 'run as administrator') and then open regedit.exe with the following command
Code:
psexec -s -i -d regedit.exe
Then, once regedit is open you need to find the keys created by the Nook bootloader and delete them. The Nook bootloader's device ID is 0451:d00e
You are going to be looking in HKEY_LOCAL_MACHINE\Current Control Set\enum\usb\ for the keys with the bootloader's device IDs. There may also be keys generated in control set 001 and 002 as well. Delete all of those keys and then reboot your computer. Then with the nook power off completely, repeat the process from the first step. eventually you will be successful installing the bootloader driver.
Step 2) temporarily boot with uRamdisk-noogie
you need to download omaplink.exe from here:
http://www.temblast.com/android.htm
and you also need to download the four files which allow you to temporarily mount the boot partition; omap3_aboot.bin, u-boot-ng2-exp-v03.bin, uImage-ng2-130-stk and uRamdisk-noogie.
They are available here:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
download usbboot-ng2-images-noogie-v1.zip
The next part is easy.
Extract the .zip file and then fire up cmd.exe. cd into the directory of the newly extracted .zip
in the new working directory, enter the command
Code:
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Then, with the Nook powered all the way off and omaplink running, plug it in and a few seconds later, after the device boots up all the way, you will be looking at the contents of the boot partition instead of the internal storage like normal.
Step 3) Edit uRamdisk
you will need to download bootutil.exe from here
http://www.temblast.com/android.htm
copy bootutil.exe to C:\Windows\System32
with the boot partition mounted, copy uRamdisk to your computer and extract the files init.rc and default.prop, eg;
Code:
bootutil /x /v uRamdisk init.rc default.prop
then using notepad++ (available here: http://notepad-plus-plus.org/) edit the files as follows
default.prop
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
and
init.rc
comment out lines 375 and 392-399
(do this by adding a # to the beginning of the line)
uncomment line 215
(do this by deleting the # at the beginning of the line)
save both files and then repack them into uRamdisk
Code:
bootutil /r /v uRamdisk init.rc default.prop
copy uRamdisk back onto the Nook, eject the disk and power off the device. Reboot and you should be able to connect to ADB via WiFi
eg;
Code:
adb connect 192.168.0.10
replacing '10' with whatever IP your Nook is grabbing from your router.
Step 4) Full Root
at this point, you have root access via ADB only. You will not have root access in any apps like Root Explorer, Terminal, TiBackup, etc.
In order to finish PROPERLY rooting your Nook, you need to install 'su' to /system/bin/ and install the superuser.apk
Code:
adb connect 192.168.0.10
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
reboot your device one more time and then you will be fully rooted.
*** Note ***
this devices firmware seems to be a strange hybrid between donut and eclair, although it purports itself to be Android 2.1. The Superuser.apk and su binary came from an old Cyanogenmod 4.6 build in case anyone was wondering (Android Donut). The ones from Cyanogenmod 5 (Android Eclair) do not work. you will get the 'install failed older sdk' error.
installing busybox
I tired installing busybox by using the stericson busybox pro.apk. It would always freeze at 6.47%.
I figured out that if I grabbed an older version of the busybox binary and pushed it to /system/xbin manually and then chmodded it to the proper permissions, auto updates and proper symlinking work using the busybox app
Code:
adb shell mount -o remount, rw /system
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Then reboot, and run the busybox app to update and create symlinks.
enjoy!
installing nano and bash
Code:
adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/
and then in terminal emulator under 'Preferences' change the initial command to
Code:
export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;
and finally
Code:
adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit
nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
As far as remounting /system as ro, I would HIGHLY recommend just rebooting at this point, otherwise your nook might be stuck in a weird pseudo-rooted state. Probably won't cause any problems, but why risk it?
Thanks for clarifying the line number. I will make the appropriate edits to my instructions. I was working off the top of my head and couldn't remember what exact line the ADB over TCP config was, as I just used ctrl+w '5555' to find it myself.
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
darz said:
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
Click to expand...
Click to collapse
N00b-un-2 said:
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
Click to expand...
Click to collapse
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
darz said:
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
Click to expand...
Click to collapse
Sorry for the really noob question, I have rooted, wifi adb running and installed apps as per your instructions, but I can't seem to access any of it on the nook. How can I get access to the launcher I installed?
You mentioned pre-edited images, do any of those come with the apps I need to get access to a custom launcher?
Cheers,
Dariusz
==============
Updated: All sorted
==============
For some reason had some issues with ADW launcher, Launcher pro worked fine.
ps I think I made a mistake with the su step I suggested, if you run a one line shell command I don't think it keeps su privileges, so I believe you need to run commands within the shell as per below:
adb shell
mount -o remount, rw /system
/system/bin/su
mkdir -p /system/xbin
exit
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Noob
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
The above instructions from N00b-un-2 should work fine running a vm with parallels on your Mac.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
valentin1985 said:
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
Click to expand...
Click to collapse
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
darz said:
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
Click to expand...
Click to collapse
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
thenookieforlife3 said:
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
Click to expand...
Click to collapse
So far so good,but now what?
valentin1985 said:
So far so good,but now what?
Click to expand...
Click to collapse
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
thenookieforlife3 said:
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
Click to expand...
Click to collapse
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
valentin1985 said:
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
Click to expand...
Click to collapse
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
thenookieforlife3 said:
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
Click to expand...
Click to collapse
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
N00b-un-2 said:
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
Click to expand...
Click to collapse
Well, as I ONLY use Windows and Powershell ISE has a nice-enough layout for my purposes, I use it. That's why I gave a tip on it.
Actually on a lot of installs just typing adb in the command console won't work either unless it's got the path variable set up correctly, I find it easiest to just right click and choose run as administrator, no need for the path to be setup.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
FW 1.2.1
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
real-6 said:
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
Click to expand...
Click to collapse
This rooting procedure is for the new Nook GlowLight with firmware 1.3.1. Your device is a Nook Simple Touch with GlowLight, which can be rooted very easily using the rooting package here.
Running Kali linux shell in Redmi Note 3 by 'chroot'-ing into it after mounting on data/local/mnt folder. Also using VNC to access the LXDE Desktop GUI.
It will run within a virtual machine on your phone alongwith the Android as well.
Required Files-
(Phone must be rooted)
1. Kali 1.0(moto) Image
https://sourceforge.net/projects/li...ux/kalilinux.BASIC.ext4.20131012.zip/download
2. Kali script
https://drive.google.com/open?id=0B_Aq1GXA8aP4UWZOcVB6X1lJUjQ
3. Busybox Installer, Termial Emulator, VNC Viewer- Download from Play Store
Steps for installing for 1st time:
1. Download kalilinux.BASIC.ext4.20131012.zip and Kali script and place them in the root of internal sdcard.
2. Install "Busybox" from Playstore. Then open it and Install Busybox 1.25.1.
3. Install "Termial Emulator" and open it.
4. In "Termial Emulator", type and press enter each time as follow-
i) su
ii) mount -o rw,remount /dev/block/bootdevice/by-name/system /system
ii) cp /sdcard/kali /system/bin/kali
iv) chmod 755 /system/bin/kali
v) kali install
That's all. First time and one time set-up is done, now no need to repeat any step later.
Running and Stoping the linux ( after 1st time set-up):
1. To enter into Kali's shell, Open "Termial Emulator" anytime and type "su" and then "kali start". To Exit type "exit".
2. To enter into Kali's LXDE Desktop, in "Termial Emulator" type "su" and then "kali vnc".
Now minimize or exit "Termial" and open VNC viewer.
Then enter following fields to enter desktop
address-127.0.0.1
port-5901
pass-kalilinux
To stop vnc server, Open "Termial Emulator" anytime and type "su" and then "kali vncstop".
3. To uninstall or exit the shell and all services, Open "Termial Emulator" anytime and type "su" and then "kali stop".
NB. To fix old kali keyring
Run in kali shell (after st set-up)
i) rm -rf /var/lib/apt/lists
ii) apt-get update
iii) apt-get install kali-archive-keyring
Here is the video guide
I think this works on all smartphones (?)
Inviato dal mio SM-G935F utilizzando Tapatalk
Francesco0301 said:
I think this works on all smartphones (?)
Inviato dal mio SM-G935F utilizzando Tapatalk
Click to expand...
Click to collapse
Yes, for all. But remounting system command is different, may be not needed.
For remounting system as rw in redmi note 3
"mount -o rw,remount /dev/block/bootdevice/by-name/system /system"
So...is it possible to run airmon-ng or aircrack-ng to hack Wifi password on RN3?
We already have Kali nethunter ROM 😀
MyStyle0714 said:
So...is it possible to run airmon-ng or aircrack-ng to hack Wifi password on RN3?
Click to expand...
Click to collapse
Yes, but with external wifi dongle, not with inbuilt wifi..
Will upload video if I got dongle
Rishabh1x said:
We already have Kali nethunter ROM 😀
Click to expand...
Click to collapse
Yes, and that is better. But it can be run in any android version and anytime by a simple command. It is very simple and handy..
So...where to buy @
MyStyle0714 said:
So...where to buy @
Click to expand...
Click to collapse
one D-Link 150 mbps dongle supported monitor mode.
But I do not own it now.
Google the wifi chip which support monitor mode, then buy dongle.
Pleasee help
When i run kali install command it become like this. Help me. I'm noob in linux command.
Can that's file and step worked with redmi note 4?
We've to place Kali.zip or kali script in the root folder?
palbadi said:
Running Kali linux shell in Redmi Note 3 by 'chroot'-ing into it after mounting on data/local/mnt folder. Also using VNC to access the LXDE Desktop GUI.
It will run within a virtual machine on your phone alongwith the Android as well.
Required Files-
(Phone must be rooted)
1. Kali 1.0(moto) Image
https://sourceforge.net/projects/li...ux/kalilinux.BASIC.ext4.20131012.zip/download
2. Kali script
https://drive.google.com/open?id=0B_Aq1GXA8aP4UWZOcVB6X1lJUjQ
3. Busybox Installer, Termial Emulator, VNC Viewer- Download from Play Store
Steps for installing for 1st time:
1. Download kalilinux.BASIC.ext4.20131012.zip and Kali script and place them in the root of internal sdcard.
2. Install "Busybox" from Playstore. Then open it and Install Busybox 1.25.1.
3. Install "Termial Emulator" and open it.
4. In "Termial Emulator", type and press enter each time as follow-
i) su
ii) mount -o rw,remount /dev/block/bootdevice/by-name/system /system
ii) cp /sdcard/kali /system/bin/kali
iv) chmod 755 /system/bin/kali
v) kali install
That's all. First time and one time set-up is done, now no need to repeat any step later.
Running and Stoping the linux ( after 1st time set-up):
1. To enter into Kali's shell, Open "Termial Emulator" anytime and type "su" and then "kali start". To Exit type "exit".
2. To enter into Kali's LXDE Desktop, in "Termial Emulator" type "su" and then "kali vnc".
Now minimize or exit "Termial" and open VNC viewer.
Then enter following fields to enter desktop
address-127.0.0.1
port-5901
pass-kalilinux
To stop vnc server, Open "Termial Emulator" anytime and type "su" and then "kali vncstop".
3. To uninstall or exit the shell and all services, Open "Termial Emulator" anytime and type "su" and then "kali stop".
NB. To fix old kali keyring
Run in kali shell (after st set-up)
i) rm -rf /var/lib/apt/lists
ii) apt-get update
iii) apt-get install kali-archive-keyring
Here is the video guide
Click to expand...
Click to collapse
I don't understand where to copy those two files plz explain to me....
silentacker said:
I don't understand where to copy those two files plz explain to me....
Click to expand...
Click to collapse
Extract kali.rar file the copy these files "kali" and "kalilinux.BASIC.ext4.20131012.zip" into Sdcard/ root directory