Related
We all know that running "adb shell" from the command line is pretty crap, and when using a latter busybox version which has coloring support it's ultimately crap. One workaround was usually to start a telnet server on the phone, and use putty to connect to that telnet server. Actually there is a more easier way to do that which also works for non rooted phones.
Actually the Android Debug Bridge has a terminal connection feature (roughly speaking), which will be enabled after you connect to the adb server in "0006shell:" mode. You can actually use the putty to connect to this interface always, by setting the following things:
- Turn off line discipline in settings
- Use RAW mode to connect to localhost:5037
- Enter "0012host:transport-usb" (without quotes)
- Enter "0006shell:" (without quotes)
Now you've got a full fledged connection to your device. The main drawback is that it's tedious to repeat the above all the time, so I've made some modifications to the putty binary that adds a new type of connection, called "Adb"
To use the enhanced putty (via USB):
- Select Adb from the connection type list
- Enter "transport-usb" in the host (or any other connection string, check the adb socket interface documentation if you need something else than connecting via usb)
- Enter 5037 as port, if it's not already set there.
- Connect and enjoy (you might also save this connection, so next time you only have to double-click on the settings)
To use this via wireless adb:
- Connect to wireless adb using a command shell: "adb connect IPORT" (substitute ip and port for the real values)
- Enter "transport-any" in the host
- Enter 5037 as port if it's not already set there
- Connect and enjoy
To use this via the android emulator:
- Enter "transport-local" in the host. Everything else is the same
If you have multiple devices (for example multiple devices connected to usb and/or wileressly)
- Enter "transport:serial-number" in the host, where you substitute "serial-number" with the serial of the device you get by using "adb devices". Everything else is the same.
DL and source: http://github.com/sztupy/adbputty/downloads
Thanks
Great job
Love to use putty.
If this do what your say it's good buy adb shell!!
i am using putty for a long time, and i just tried urs, it looks great but i failed to connect coz i'm connecting to 2 devices....
so how can i add the -s param to specify which phone i'm gonna connect?
thx
EDIT: wow!!! i removed one of my devices and connected to it now!! ctrl-U now works!!!! THANK YOU!!!
EDIT2: quick question. if i use a normal putty, where to type in 0012transport-usb and 0006shell: ? i typed them in the term but it closed after 0006shell
Thanks. It works, but any idea how to get the up and down arrow keys to work on Putty? They work on the windows adb shell.
ykk_five said:
i am using putty for a long time, and i just tried urs, it looks great but i failed to connect coz i'm connecting to 2 devices....
so how can i add the -s param to specify which phone i'm gonna connect?
thx
EDIT: wow!!! i removed one of my devices and connected to it now!! ctrl-U now works!!!! THANK YOU!!!
EDIT2: quick question. if i use a normal putty, where to type in 0012transport-usb and 0006shell: ? i typed them in the term but it closed after 0006shell
Click to expand...
Click to collapse
The complete specification is here: http://android.git.kernel.org/?p=pl...T;hb=f41986bbc79055a4feed7266cac5c1b540296daf
This is what you can use:
- transport-any (either usb or local emulator)
- transport-usb (the only usb device)
- transport-local (the only emulator)
- transport:SERIALNUMBER (the concrete device with the appropriate serial number)
so in your case you have to use the latter.
For the second question, you need to ensure that all of the things are present:
- You are using RAW mode (connecting to localhost:5037)
- Line discipline is on "Force OFF" (in the terminal settings dialog)
- You make some pause between writing the two commands
- You don't press enter/backspace or any other key while entering the commands (the easiest way is to write the commands in eg. notepad, copy them, and paste them into putty by pressing ****+RIGHT MOUSE BUTTON)
hardcore said:
Thanks. It works, but any idea how to get the up and down arrow keys to work on Putty? They work on the windows adb shell.
Click to expand...
Click to collapse
The up and down arrow keys were actually handled by cmd.exe, which is non existent in putty. Instead it's now the responsibility of the shell to do the hard work. The included sh in the phone's sotfware (toolbox sh) is mostly useless here, but if you have busybox installed, you might want to run "busybox sh" after connecting (some rooted phones have busybox's sh as default, on them it should work out of the box).
Busybox's sh can not only handle the up and down arrows, but other things like tab completion works too.
sztupy said:
The up and down arrow keys were actually handled by cmd.exe, which is non existent in putty. Instead it's now the responsibility of the shell to do the hard work. The included sh in the phone's sotfware (toolbox sh) is mostly useless here, but if you have busybox installed, you might want to run "busybox sh" after connecting (some rooted phones have busybox's sh as default, on them it should work out of the box).
Busybox's sh can not only handle the up and down arrows, but other things like tab completion works too.
Click to expand...
Click to collapse
Use the ash.
edit:
Btw, thank you for this adb-putty.
sztupy said:
The complete specification is here: http://android.git.kernel.org/?p=pl...T;hb=f41986bbc79055a4feed7266cac5c1b540296daf
This is what you can use:
- transport-any (either usb or local emulator)
- transport-usb (the only usb device)
- transport-local (the only emulator)
- transport:SERIALNUMBER (the concrete device with the appropriate serial number)
so in your case you have to use the latter.
For the second question, you need to ensure that all of the things are present:
- You are using RAW mode (connecting to localhost:5037)
- Line discipline is on "Force OFF" (in the terminal settings dialog)
- You make some pause between writing the two commands
- You don't press enter/backspace or any other key while entering the commands (the easiest way is to write the commands in eg. notepad, copy them, and paste them into putty by pressing ****+RIGHT MOUSE BUTTON)
Click to expand...
Click to collapse
thx for u reply, but all i got in the log:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2010.10.09 13:10:54 =~=~=~=~=~=~=~=~=~=~=~=
0012transport-usb
0006shell:
FAIL0012device offline (x)
with adb turned on and working
sztupy said:
The up and down arrow keys were actually handled by cmd.exe, which is non existent in putty. Instead it's now the responsibility of the shell to do the hard work. The included sh in the phone's sotfware (toolbox sh) is mostly useless here, but if you have busybox installed, you might want to run "busybox sh" after connecting (some rooted phones have busybox's sh as default, on them it should work out of the box).
Busybox's sh can not only handle the up and down arrows, but other things like tab completion works too.
Click to expand...
Click to collapse
Yes and it will be great if busybox can handle history like linux
ADB over wireless ?
Hi, thanks for your great work
I'm using ADB Wireless
The first step is to connect first with
Code:
adb.exe connect 192.168.6.14:5555
And then the standard procedure
Is it possible for you to include these two phases directly inside Putty ?
So we just have to enter the IP address of the phone and here we go
PS : to disconnect, we have to do
Code:
adb.exe disconnect 192.168.6.14:5555
but that's not an obligation
seems to be a windows/putty problem because adb shell works wonderful on ubuntu with the default shell ...
btw. you can also easily get a sshd (dropbear) running. then you can ssh onto the device over wifi ... i can provide the binary+explanation if anybody is interested.
I'm very interested in that !
Sent from my GT-I9000 using XDA App
virus found
mathieumeuh said:
I'm very interested in that !
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
here is the explanation how to set it up (cyanogenmod wiki):
http://wiki.cyanogenmod.com/index.php?title=Howto:_Connect_to_Device_with_SSH
basically you have to create the keys on your pc and copy them onto the device. then you can connect via key-auth. if you want dropbear to autostart @boot you could add it to playlogos1 ...
and here are the binary's you need (including the missing dropbear-keygen) and a bash binary:
http://www.multiupload.com/B0L9FDQHPB
bash is optional of course but it's very nice to have tab-completion and the other improvements bash offers over sh. to replace sh with bash do the following:
Code:
cp bash /system/bin/
chmod 0755 /system/bin/bash
mv /system/bin/sh /system/bin/sh_OLD
ln -s /system/bin/bash /system/bin/sh
the chmod is really important. i forgot it once and then was unable to get shell access even over adb. was a pain in the ass to fix it again
jodue said:
seems to be a windows/putty problem because adb shell works wonderful on ubuntu with the default shell ...
btw. you can also easily get a sshd (dropbear) running. then you can ssh onto the device over wifi ... i can provide the binary+explanation if anybody is interested.
Click to expand...
Click to collapse
You seem to miss the point of this development. First, your method is mentioned as one of the possible workarounds in the first post. Second you need to have some kind of telnet/ssh server running on the phone, which you don't need, if using adb.
Meanwhile you don't even need a rooted phone or busybox or anything to get this thing working.
The main problem with adb shell under windows, that it uses the standard cmd.exe to run, and uses the standard cmd.exe's "readline" support, which only supports the up and down keys for history (and even that it only supports that within one session).
Putty is mainly the only good (xterm compatible) terminal emulator for windows (msys's or cygwin's rxvt is good too, but "adb shell" was programmed in a way that makes it kinda useless under rxvt too). There are two ways to fix this. One is to make adb.exe more comptible with rxvt, the other is to skip adb.exe entirelly and communicate with the adb server without it. This project utilises the latter.
But what is the advantage compared to "normal" ABD
But what is the advantage compared to "normal" ADB ?
Thank you!
DirkStorck said:
But what is the advantage compared to "normal" ABD
Click to expand...
Click to collapse
It has a real xterm compatible terminal emulator. Is you use busybox >= 1.17.1 you've got coloring, tab completion, resize events, keyboard events (applicatios like vi is working), etc.
This is the reason I recommend a faulty device: without the problems with the SGS the developments would go much slower Thank you for this putty, i have it connecting to the bash. Color coding and keys work perfectly.
Thanks for this Sztupy!
I hated using windows cmd.exe to access a linux shell
This Thread is outdated!
I will update it soon!
Thanks for your understanding
Hello everybody,
as there is no sub-forum for the new nook simple touch (help to get one),
all information are split on several posts in the nook color forum.
I want to create a central thread which list all the knowledge and work that is already done.
The most solutions are NOT my work!
I will link to the post and add the author,
please thank them for their work.
Basics
Update
There is an update for the nook touch!
(not recommended for now)
Checkout the discussion: Nook STR update 1.0.1
Screen Refresh
To avoid ghosting you can easily refresh the screen by pressing the n button twice (open and close default launcher).
Hidden back "button"
You can easily go back by swiping in the middle of the topbar from right to left.
(You may need this in stock apps / settings, after getting root you get 2 buttons for menu and back on this area)
Hidden Browser
you can access a browser by typing in an url into the searchbox,
but the browser doesn't work well...
liliputing.com nook touch browser (no root)
Backup
Backup/Restore N2E by jocala
Windows HowTo is on the second post
Factory Reset / Recovery
[TOOL] nookRestore { Nook Touch - Factory restore | recovery } by ros87
B&N - nook Support
Rooting:
Please take the time and get a backup of your nook!
nookdevs.com NookTouch Rooting (linux, mac, windows)
JesusFreak of nookdevs make all this possible!
Here you can find his original guide.
TouchNooter (linux, mac, windows)
GabrialDestruir said:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox
Installs Button Savior
Installs Go Launcher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Gapps (Gmail, Market, Youtube, Others)
Click to expand...
Click to collapse
Root & Setup Script Kit (windows only)
xboxexpert said:
Full Superuser Access
Updates are permanently blocked!
Unknown sources Enabled (install non-Market applications)
adb debugging is active [mostly for developers]
Ability to replace the Authors ****ty pictures
Ability to remap the left buttons to Menu & Back
Market Installed & Working! Login to YouTube with your GMAIL!
Software Included:
AdFree (Block those nasty ad's) [Wi-Fi needed]
Button Savior (Displays Softkeys)
gTab simi Clock (really awesome clock for your desktop)
Kindle (read your Kindle books on Nook, lol) [Wi-Fi needed]
LauncherPro (default launcher instead of Nook base launcher)
Superuser (provides a list of applications that use superuser access)
Click to expand...
Click to collapse
Advanced:
(need root)
adb
WiFi
by default you can only use wifi to connect to your nook!
Please consider that anyone in your network can connect to your nook!
This is a serious security problem!
mycr0ft modified the uRamdisk to disable adb over wifi by default! (not tested)
Code:
adb connect [I]NOOK-IP[/I]
USB
xor_ uploaded a uramdisk with adb usb enabled
and traycold has found drivers for windows (thanks to cceerrtt)
xboxexpert modified the adb usb driver to work with the n2e. (not tested yet!)
[GUIDE] ADB Workshop and Guide for everyone
Remapping Hardware Buttons
n Button
[MOD+APP][11Oct11] Configurable "n", "reading now", "RecentDialog" + Activity Picker!
XorZone said:
Features of mod
* Will return stock android go to home by short press of "n" button and recent apps dialog on long press (Configurable)
* All B&N quicknav buttons configurable, it even loads apps icons (after reboot)
* Reading now" button configurable
* NOTE: Installation of the jars w/o conf will have stock B&N effect + recent apps
Features of application
* Implements Activity Picker, so any app (i.e. Launcher Pro) can use "Shourtcuts" dialog that B&N removed.
* Configuration UI for above mod
* (In future) Configuration UI for page buttons
Click to expand...
Click to collapse
Page-Turn Buttons
The main thread is from xboxexpert,
the user aruangra shows how to map the keys to volume up/down so you can use it for scrolling in some applications
Softbutton
Softbuttons can add little buttons to your user interface which simulate the normal android buttons (Home, Back, etc.),
Button Savior is working very well.
OMGWTF_BBQ modded it for the eInk Display.
Market & gapps
If you have already rooted and want to enable the market by yourself you can use the tutorial on nookdevs from the nook color. GabrialDestruir have tested this and confirmend its working.
Additionally i have written down some steps to activate it by using resources of the touchnooter script.
GabrialDestruir updated his script, i dont know if my tutorial still works
AFTER you get the market working you can
update the market and gapps
or, just update the market.
This will fix the market search too
Language / Locale Settings
If you live outside of the USA and managed to get a nook,
there are a few steps to customize the system to your locale / regional enviroment.
To change the system language and the keyboard you can look here:
customize language
Timezone and 24:00 Clock can be set on the default settings menu
(On first-start-setup you can only choose US-Timezones)
Landscape / Screen Rotation
[APP] Orientation Switch by XorZone
on LauncherPro you have to enable Auto-Rotation (thanks to densets)
AdHoc WiFi
If you want to connect to an AdHoc WiFi you can checkout a fix for the nook color:
[FIX] AdHoc Wifi support on the NC! thanks to markmc87 & jago25_98
Misc:
Wallpapers
OMGWTF_BBQ made some nice wallpapers
The Wallpaper from the Video by OMGWTF_BBQ
Michael.Rose made a pencil sketch of it
Videos
XDA-User OMGWTF_BBQ upload a Nook2 Root Tour on youtube
JesusFreak's proof his working root with Angry Birds on Nook Touch
The Nook Touch has a Web Browser - No Root Required!
Gizmo - Nook Simple Touch Reader
B&N The All-New NOOK Guided Tour
App info
✔ Kindle, Kobo, txtr, Aldiko, Moon+, FBReader
ryanpl write together a list of supported apps
OMGWTF_BBQ Root Tour Video
You can try all other apps for Android 2.1
NOT WORKING:
xda-developers (some threads shows a blank page)
Pulse News (crash after initial screen)
(version from nook color market is working)
Skype (freeze on login screen)
Tricorder (system freeze)
Hardware/Software specs
Icehawk78 posted some system information on request.
stock-kernel:
MystaWright said:
VERSION = 2 | PATCHLEVEL = 66 | SUBLEVEL = 29
(2.6.29-omap1)
Click to expand...
Click to collapse
Links:
New Nook 2 eInk Reader Announced! Available for Preorder
Nook Touch Root Guide is OUT.
[REQUEST] B&N Nook Simple Touch forum
[N2E] Nook 2nd Edition Touch - Root
[N2E] Nook 2nd Edition Touch - Development
[N2E] TouchNooter 1.6.24
[NST] Root/Market & Setup Script Kit
[N2E] Nook Touch - App Support for Hardware Buttons
[N2E] Recovery & Source for Nook Touch
[N2E] Nook Touch n-button mapping
[N2E] modified framework.jar
Backup/Restore N2E
[NC]/[N2E] Warning!
Nook STR update 1.0.1
[APP] Orientation Switch
[MOD+APP][11Oct11] Configurable "n", "reading now", "RecentDialog" + Activity Picker!
[TOOL] nookRestore { Nook Touch - Factory restore | recovery }
[N2E] Nook ADB over USB on linux.
Nook Touch kernel hacking
[FIX] AdHoc Wifi support on the NC!
[Q] [POLL] Do we need NST specific launcher? If Y - how should it look like?
nookdevs.com NookTouch Rooting
ReviewHorizon.com Root Guide
Mike Cane's xBlog - Nook Touch Rooting: June 27th News
IRC: #nookdevs @freenode
B&N All-New NOOK Porduct Website
B&N nook Support
THANKS TO ALL OF YOU!
If i forget something or got something wrong, please feel free to complete this thread!
... reserved ...
First
Sent from my SPH-D700 using XDA App
What's the consensus as to the best launcher to use...
I currently use ADW, which seems to work ok. Biggest complaint is I can't see the text on the settings menus...
I prefer a white backgounnd. So ADW seems to be an only option. I am using ADW EX.
updated the fist post,
thanks to DenisTheMenace for the info about adb usb drivers,
the mod/person who made this stickie,
and again all of you
Xhorder said:
What's the consensus as to the best launcher to use...
I currently use ADW, which seems to work ok. Biggest complaint is I can't see the text on the settings menus...
Click to expand...
Click to collapse
iam using ADW too,
i like it more than Go Launcher or LauncherPro
but when i tried them i recognized some empty settings menus too,
so i dont think its the launcher that shows the settings menus without text...
rev0l said:
so i dont think its the launcher that shows the settings menus without text...
Click to expand...
Click to collapse
It's not without test, the test is white on white background, that's why we don't see anything.
I got pulse to work, I used the pulse from the nook apps shop.
mkenney12 wrote me a pm.
he wants that everybody consider the consequences of using a rooted nook touch.
its definitely a point that everyone has to keep on mind!
rmkenney12 said:
Hi,
I'm not sure who to send this to in the xda-dev
community, but noticed that you were maintaining
the KB articles for the Nook Touch root. I tried
posting to the touchnooter dev thread, but I don't
have the requisite 10 messages, so I couldn't even
thank them.
I've been able to root my N2E with the
touchnooter root: the most recent 1.6.24. I'm
extremely happy with the results, but am having a
major concern that doesn't appear to be getting
proper coverage in that or other roots. (I initially
tried the noogie root with lesser results).
<Rant On>
IE, adb wireless/wifi access.
Nobody seems to be expounding on the fact that
it's an enormous freaking barn-door-size gaping
hole in the security of the N2E(or doing anything
to eliminate it). You yourself mention it in
passing in your KB article, but only give it a single
line.
Essentially, once these things are rooted, they
are -enormously- vulnerable if they are taken out
into the public, either at a Barnes&Noble store,
or at any other hotspot. All it takes is for a hacker
sitting there at that hotspot with a laptop, scanning
all of the IP's in that subnet for IP's that respond
to the adb port, and they can do a simple
#adb install MyFavBotController.apk
or somesuch thing. If adb pukes on them(IE, it's a
non-rooted Nook), then they just keep scanning.
Unless you're sharp and see the notification tab
popping up, you may never notice it. They can
install any freaking thing they want on your Nook.
Evetually you've got hundreds or thousands of
infected Nooks running bots, or some other fun
little thing(s) implanted on them.
Everybody seems to be incredibly happy about how
easy it makes their experimentation, and all of the
root developers seem to be focused on making sure
that adb wireless is enabled, either in the startup
scripting or even in the uRamdisk as with the
touchnooter root.
Sure, you can install the adbWireless app from the
market, and it will turn off adbWireless, but:
a) when you initially run the adbWireless app, it
doesn't even properly report that the adb wifi
function is on. It reports it as off, even though
it's actually still responding to adb connects.
So now you have to remember to turn it on,
and then back off. That does work(for a little
while).
b) it's not permanent with some roots, like the
touchnooter. I disable adb wifi with the
adbWireless app, it's off, and everything is nice
and safe? if I put my N2E through a power
cycle, guess what. It's been turned right back
on again. That's completely whacked.
1) For one thing, as an older person I may
forget to use adbWireless to keep turning
adb wifi off after power-cycles. Over and
over and over again.
2) Even if you remember, there's a window of
access during power-up that's about 30-60
seconds long before you'll be able to run
adbWireless to shut things down. A hacker
could do a lot of damage to your Nook in
that time.
3) I have heard rumors of Nooks turning
turning themselves back on after being
powered off. So now you could be in a
hotspot, your Nook could turn itself on in
your knapsack without you even knowing,
and the hacker sitting there has all the
time in the world to beat on your poor little
Nook.
It's BONEHEADED. adb Wifi should NOT EVER be
automatically turned on by the bootstrap. NEVER.
If developers of these roots want to make it easy for
the users or other devs using them, then simply
bundle the adbWireless application along with
SuperUser, Yahoo, and the other apk's they've
included in their root distro's.
Let the -users- decide when and where it's safe for
them to use adb Wifi. Devels are NOT doing them a
service by forcing adb Wifi on them, or encouraging
them to use it under dangerous circumstances.
</Rant Off>
Sorry, but I have a rooted Nook that I'd like to take
outside the confines of my home. Unfortunately,
I don't dare to now. So yah, I'm feeling cranky :-(
rev0l. -please- pass this on to any developers
you might have contacts with.
Thank you!
= Glucosaurus
Click to expand...
Click to collapse
i dont know if someone can disable the access over adb by default...
may you can use apps like tasker or automate it to disable wifi when your accesspoint is not in range or start the adbwifi app while connecting to a public wifi.
Xhorder said:
What's the consensus as to the best launcher to use...
I currently use ADW, which seems to work ok. Biggest complaint is I can't see the text on the settings menus...
Click to expand...
Click to collapse
I love Zeam.
I think that the best way to avoid the wireless adb security hole would be to enable adb over usb and disable adb wireless if it is possible.
I have read on irc someone (maybe JesusFreke) saying that we just have to do something like modifying adb or doing something else (I don't remember very well)
I'm also trying to find out how to adb with usb. In particular I'm looking to get my N2E to connect to my iPhone running MyWi 4.0. I've read that the nookdevs Ad-Hoc_WiFi wpa_supplicant file for the NC will work with the N2E, but I haven't found a way to connect with USB and I'm too scared to try it over wifi in case it goes wrong and I won't be able to connect with adb over wifi to fix it. Any help would be much appreciated.
Edit :
Managed to get ad-hoc wifi working by pushing the fixed wpa_supplicant.adhocfix file to the /system/bin/ folder with adb over wifi.
Then, I switched the wifi off on the N2E and opened terminal emulator and did the following :
Code:
su
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
mount
cd /system/bin
mv wpa_supplicant wpa_supplicant.old */make backup of original wpa_supplicant file/*
mv wpa_supplicant.adhocfix wpa_supplicant
chmod 755 /system/bin/wpa_supplicant
exit
I am now able to connect to my iPhone's MyWi hotspot.
For security when connecting to a public hotspot, I have installed the ttxapps wifi adb app from the android market and turned off adb over wifi, meaning I can toggle it on only when I wish to connect on my home network.
does anyone have system restore image?
another pm from a user that cant post
J.Harmon said:
I figured out how to get a full factory "re-image" of my nook touch.
I followed the instructions for the nook color here:
Method two: Set the Boot counter to 8 by typing
http://nookdevs.com/Flash_back_to_clean_stock_ROM
I rooted my nook touch using touchnooter. Loaded up the amazon app store and played around for a while. But I found after I rooted the nook that the nook store didn't work any more. So i wanted to get back to factory state. I then installed the wireless adb app. I logged in to my nook using my linux pc and followed the above directions. After the re-image you have to do a data reset by going in and restoring to factory settings in the nook itself.
As soon as I gave the reboot command it started the re-image as seen in this link:
https://lh3.googleusercontent.com/-p...2E_Restore.JPG
I'm sending you this message because I'm a "noob" and can't post in the developer forums. So if you wouldn't mind reposting for the others to use.
Click to expand...
Click to collapse
Was anybody else able to get to "Restoring Factory Image..." dialog?
It happened to me after 20+ resets, I was just searching for bricked N2E solution and kept on pressing the button... I would like to know how to replicate this again
i tried it with the 8 times boot failure method, it brings up the factroy reset screen, but it does not the reall factory reset, root and some other stuff were still n the nook after this "factory reset" don't know..
and don't tried (or even read) the method from the pm...
too busy at the moment :/
Inspired by rmkenney12 (and rev0l), I updated the uRamdisk file from TouchNooter 1.6.24 so that adb over wi-fi does not run at boot.
Disclaimer: Don't try this unless you know how to restore your nook in case it does not work.
To install the new uRamdisk:
Unzip the attached file somewhere, then...
Code:
adb connect <nook>
adb shell mkdir /cache/boot
adb shell mount -o rw -t vfat /dev/block/mmcblk0p1 /cache/boot
adb push <path>/uRamdisk /cache/boot
adb reboot
Cross your fingers and hope it works.
You will also want to download an app to turn adb on and off. Search market for 'wifi adb'.
P.S. Does anyone know specifically what needs to be changed in the uRamdisk to enable adb over usb?
This guide isn't working for me. It says that after you create a noogie sd card, just pop it in, start the nook and it will mount the 7 partitions....
What 7 partitions? They never show for me. When I start the nook with the card inside it mounts the "boot" partition which is 64.8 out of 74.7 megabytes.
That's it. That's all I see. Inside of this partition are the files that were contained in the noogie image.
ibex333 said:
This guide isn't working for me. It says that after you create a noogie sd card, just pop it in, start the nook and it will mount the 7 partitions....
What 7 partitions? They never show for me. When I start the nook with the card inside it mounts the "boot" partition which is 64.8 out of 74.7 megabytes.
That's it. That's all I see. Inside of this partition are the files that were contained in the noogie image.
Click to expand...
Click to collapse
wrong thread?
which guide do you mean?
anyway, i don't know if windows can recognize all partitions...
download a live cd linux and try again
Ok... This is on windows 7. I dont know how to use Linux.
I am trying to root the Nook STR and using the guide provided here. It just gets stuck at the rooted forever screen, and the rest is as described in previous post.
So, I have had an HTC Vision running CM7 and have been using it as JUST a wifi access point (no routing or DHCP provided by the Vision itself, just the WAP). I could tell you a very long and boring story about why I need it this way but here's the bottom line -- I'd like to know the actual command line (either through adb shell or terminal directly on the device) to configure and enable just the master mode access point functionality with encryption.
I found a starting point on Antoine Amarilli's blog - Android from the Command Line -- not allowed to post links yet or I would -- but two things:
1) it doesn't appear to cover encryption.
2) It requires getting and using an add'l binary (ultra_bcm_config) which is simple enough but slightly puzzling since obviously the phone can do all of this already with just what's in the CM7 ROM.
So I'd just like a little more understanding, control, and insight to be able to script the WAP setup myself instead of being beholden to the built-in tether toggle -- which occasionally fails to work though it's easily fixed with a reboot of the phone.
Guidance? Thanks!
TL.DR; Trying to root new Verizon Android flip-phone with Marshmallow 6.0.1, ARMv7. Firmware version: VN22010B. Seems to to be locked down.
Click to expand...
Click to collapse
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Why?
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
jfn0802 said:
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
Click to expand...
Click to collapse
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Same problem
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
i get the same error. did you find a solution? i would really appreciate it
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
MendilR said:
i get the same error. did you find a solution? i would really appreciate it
Click to expand...
Click to collapse
re: the certificate error for side loading apps...
Code:
adb shell settings put secure install_non_market_apps 1
turns off the unknown source block, but I'm still getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
Could the apk itself I'm trying to use have a bad certificate? Or is there another solution?
InfectedPackets said:
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Click to expand...
Click to collapse
Just curious - any success or updates. I can't seem to get past " INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
Click to expand...
Click to collapse
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
PAULC91316 said:
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
Click to expand...
Click to collapse
I'm still at the same place I was the other day when I posted this.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from
here.
Click to expand...
Click to collapse
InfectedPackets said:
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Click to expand...
Click to collapse
Can you please share with us the KDZ file?
Thanks!
anyone?
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Thanks for taking your time, to help me.
I will check if I can unlock the bootloader.
Thanks alot
r3w1NNNd said:
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Click to expand...
Click to collapse
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
effulgent.unicorn said:
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
Click to expand...
Click to collapse
my freinds are using it in Canada with videotron and everything works, without unlocking
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Isn't that what turning on the "install from unknown sources" option should do? I still get the Install Parse Failed after switching it on with ADB.
@98jbsz I've tried to uninstall without success. What way did you do it? And does it just leave a blank space in the menu screen?
[Less on topic, sorry again, but has anyone seen the LG Wine LTE? http://www.lg.com/us/cell-phones/lg-UN220-lg-wine
It's strikingly similar to our friend the Exalt LTE here, but it seems less carrier branded/available at US Cellular, so I'm wondering if that would make a difference?
Major differences Wine LTE has more 4G bands (2/4/5/12/25) versus Exalt (4/5/13), which kind of has me kicking myself, because travel and 4G was one of the reasons I bought the Exalt. Both have quadband GSM and WCDMA, but interestingly the Wine also has CDMA.
Beyond that, there are some more smaller differences I scavenged from their LG pages, Exalt has more bluetooth profiles, supports more music formats, has more GPS capabilities, wifi calling, and 1 more ringtone. Wine has more supported video formats, and an FM radio.
I'm curious about what/if the Wine would have for sms messaging (I doubt it'd have Verizon's message+) and instead of my Verizon app...]
98jbsz said:
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
Click to expand...
Click to collapse
Alright, I also managed to uninstall my verizon and verizon's cloud app using
Code:
adb shell and the pm uninstall -k --user 0
But the Verizon apps folder on the menu screen remains, although it's empty. Any ideas on how to remove it?
Then I tried to install an apk using
Code:
pm install
and it came back with [INSTALL_FAILED_INVALID_URI] which...is a different than [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES], but not better.
right, but when you first copy the APK to the phone, and then you install it, you will see the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] error. still not a solution
I'm trying to find information about a multimedia system i have installed in my Skoda, the sticker on the device says CNT100, which is manufactured by CarNeTek (device page - https://www.carnetek.com.tw/products_detail/15.htm, not sure if they are the manufactures or just a reseller).
The company which sell and install it locally are not willing to share any information about the device, and of course are not willing to unlock it (to install applications from the play store, tweak configuration, etc.).
On the device there are 6 dip switches (which i couldn't figure out what they control), and no visible button (to get into recovery), i can get to the play store, and install applications - but as soon the installation is completed - they get uninstalled (there is a list of application that are not automatically uninstalled).
The launcher looks like a custom local version, there is no way to get into the settings page and the notification bar cannot be clicked (or dragged down), if i click multiple times on the menu - i get a dialog for some configuration, where i'm prompt for password (the dialog has a random number on it - which i suspect is used to generate correct password).
is anyone familiar with this device? or can suggest a way to unlock it?
(attached images of the device and the boot screen)
Hey mrtowel!
Trying to figure out that as well.
You said "if i click multiple times on the menu"
Where is this menu? possible to send a photo of that?
I'm talking about an Israeli version
Seems to be customized by [email protected]
sorry but i was wrong describing the way to get to the password dialog, on the home screen - there is a weather widget, showing the weather on the left side and the clock on the right side, multiple taps on the weather allows you to reboot the device, while multiple taps on the clock gets you to the password dialog.
I made some progress with the device - still working on getting it unlocked completely, let me know if you want more details.
mrtowel said:
Seems to be customized by [email protected]
sorry but i was wrong describing the way to get to the password dialog, on the home screen - there is a weather widget, showing the weather on the left side and the clock on the right side, multiple taps on the weather allows you to reboot the device, while multiple taps on the clock gets you to the password dialog.
I made some progress with the device - still working on getting it unlocked completely, let me know if you want more details.
Click to expand...
Click to collapse
Hey!
Just found that new to me. Pushed 6 times on the clock of the weather widget and got a prompt for the password. I receive a 9 digit number with that.
Also found that if you do the same on the temperature indication, you'll be prompt for device restart.
So that's a progress.
Anyways, I will be happy to hear from you, what progress you have made on this.
Will send you a PM.
Did someone have any success?
Hello, i have a Toyota corolla 2016 with "android multimedia" that have only 2 apps without google play or any apps, the startup screen is like yours.
i wan to unlock the system, someone know how to do that?
gtrs36 said:
Hello, i have a Toyota corolla 2016 with "android multimedia" that have only 2 apps without google play or any apps, the startup screen is like yours.
i wan to unlock the system, someone know how to do that?
Click to expand...
Click to collapse
try to get to app store (in case it is installed) through one of the installed apps using the 'rate us' option, you can also try and push a play store link through bluetooth, if it works - the android system will launch the play store app, and you'll be able to setup your account.
Once you get to the play store - download and install Googel app (https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox&hl=en) this will let you ask google assistant to 'Open Display Settings' (in my case this option let me enable the drag down menu, where i could easily access the settings and other stuff).
hope that helps
?
Hey did you succeed?
please help
Hi
did any one of you had any success with getting into setting menu ?
i can get to google play...but as was posted before, everything i try to install immediately erase itself.....
does any one have the approved app list from ituran ?
i do believe that together we can crack this....
thanks
Thanks for the tips I've made it to download youtube! But how I can bypass the limit to install all apps from play store?
Also how can I cancel the restrictions of using apps during drive?
Thanks
Allon
Hey @mrtowel any change you can share some more details?
I tried connecting to the USB with my laptop to try doing some adb commands but it did not detect anything
I'm also wondering about the dip switch
and how to get the password bypass
Would really like to hear some more details if you can share please?
Just came here to see if can recall my steps from last time i played with the device (i kind of gave up, as it worked well with what there is, but recent update made it work really slow).
turns out there is a post on facebook (https://facebook.com/groups/gilcar/permalink/729881061134680/?comment_id=729883497801103), i'm going to try and build some utility to generate unlock codes (last time, i managed to get to an adb terminal, but i wasn't aware of the `pm hide` option to disable the installation blocker ****).
will post updates here if i get some progress
For anyone interested, attached the list of whitelisted apps. a jar to generate the code to enable tech mode and how i disabled the installation blocker
For the jar - you would need to get your device Wifi MAC address (see old post from 2019 on how to enable the navigation bar), which can be retrieved from the 'אודות' section. (run the jar by running 'java -jar codeGen_jar.jar 00:11:22:33:44:55' - replace the numbers with your device mac address)
Wifi must be enabled - before the next step
To get to the code, hit few clicks on the clock widget in the home screen would prompt you with a password (if the code generator matches your version of connect-it (if it isn't - see bypass admin mode workaround below), the codes would match), enter the unlock code (admin mode result from the codeGen output) and move to the apps section - you would see 'tech mode' application.
Wifi must be connected before the next step
On the tech mode application - you would have another code (tech mode result from the codeGen) enter it - and it would open a page to enable adb remote server (you must be connected to a wifi network to get it to work).
Connect to the adb using a remote shell from another device (or a laptop), to the specified IP on port 1917 (note that most mobile tethering options won't work due to networking limitations). If you don't have an accessible wifi network - see Wifi Workaround below
From adb, run the following:
to disable the application which blocks installations: pm hide com.ituran.installationblocker
Disable updates: pm hide com.ituran.systemupdateservice
Disable blocking applications while driving: pm hide com.ituran.driveusagemonitor
Tips:
While in admin mode, you can see all installed applications, and pin them to the start page of the home screen, recommend to pin Play Store app (as it is usually hidden)
Don't try to enable or enter 'Guest mode' (i tried it, and the device went into boot loop)
The codes generated are date sensitive, so either generate new ones if you won't use them in the same day, or change the device date.
Wifi Workaround : a workaround can be to install modified version of 'Remote ADB Shell' (attached) on the device, save it to your mobile phone, and push it to the device through bluetooth, this version is the same version as 'Remote ADB Shell' from the play store - only names 'Spotify' which will keep it installed on the device, after installation, run it and connect to 127.0.0.1 on port 1917 instead.
Bypass admin mode workaround : while Admin Mode enables you to view the hidden applications, in the above process, it mainly gives you the option to run the tech mode app. if the code for the admin mode isn't working for you, install 'Amaze file explorer' (attached - it was renamed to bypass the installation blocker) by pushing it through bluetooth.
You can find more details on this facebook post (not mine - but i used details from this thread to figure out how to disable the application from ADB)
Enjoy and drive safely.
mrtowel said:
For anyone interested, attached the list of whitelisted apps. a jar to generate the code to enable tech mode and how i disabled the installation blocker
For the jar - you would need to get your device Wifi MAC address (see old post from 2019 on how to enable the navigation bar), which can be retrieved from the 'אודות' section. (run the jar by running 'java -jar codeGen_jar.jar 00:11:22:33:44:55' - replace the numbers with your device mac address)
Wifi must be enabled - before the next step
To get to the code, hit few clicks on the clock widget in the home screen would prompt you with a password (if the code generator matches your version of connect-it (if it isn't - see bypass admin mode workaround below), the codes would match), enter the unlock code (admin mode result from the codeGen output) and move to the apps section - you would see 'tech mode' application.
Wifi must be connected before the next step
On the tech mode application - you would have another code (tech mode result from the codeGen) enter it - and it would open a page to enable adb remote server (you must be connected to a wifi network to get it to work).
Connect to the adb using a remote shell from another device (or a laptop), to the specified IP on port 1917 (note that most mobile tethering options won't work due to networking limitations). If you don't have an accessible wifi network - see Wifi Workaround below
From adb, run the following:
to disable the application which blocks installations: pm hide com.ituran.installationblocker
Disable updates: pm hide com.ituran.systemupdateservice
Disable blocking applications while driving: pm hide com.ituran.driveusagemonitor
Tips:
While in admin mode, you can see all installed applications, and pin them to the start page of the home screen, recommend to pin Play Store app (as it is usually hidden)
Don't try to enable or enter 'Guest mode' (i tried it, and the device went into boot loop)
The codes generated are date sensitive, so either generate new ones if you won't use them in the same day, or change the device date.
Wifi Workaround : a workaround can be to install modified version of 'Remote ADB Shell' (attached) on the device, save it to your mobile phone, and push it to the device through bluetooth, this version is the same version as 'Remote ADB Shell' from the play store - only names 'Spotify' which will keep it installed on the device, after installation, run it and connect to 127.0.0.1 on port 1917 instead.
Bypass admin mode workaround : while Admin Mode enables you to view the hidden applications, in the above process, it mainly gives you the option to run the tech mode app. if the code for the admin mode isn't working for you, install 'Amaze file explorer' (attached - it was renamed to bypass the installation blocker) by pushing it through bluetooth.
You can find more details on this facebook post (not mine - but i used details from this thread to figure out how to disable the application from ADB)
Enjoy and drive safely.
Click to expand...
Click to collapse
Does this method work with Hyundai, Mitsubishi, etc...?
Hi Mr.
mrtoweldo you have any videos explain the steps in post #13 I will be thankful if you provide me with for urgent case.
thank you dear for great job