Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Dog909 said:
Hello all
A little bit of background info:
I have owned my Desire for over 2 years now & recently decided to s-off/root/flash (primarily to gain some memory space- the only real short coming of the Desire in my opinion).
I went from stock Gingerbread 2.3.7 to Cyanogenmod 7.1 & so have taken my first step into a larger world!
In that world I encountered problems - no signal, no gps, no bluetooth, radio flashing etc. - all of which I managed to find solutions for by reading the excellent resources of xda-developers.
So having collated the enormous & varying wealth of info & getting my Desire fully functional - I wanted to give something back.
It's not much (though I haven't seen it anywhere as a solution?), but it may help someone somewhere :fingers-crossed:
## If you just want to cut to the chase- the procedure that worked for me is at the end of the post! ##
About my phone:
Android version 2.3.7
Cyanogenmod version 7.1.0
Baseband Version 32.56.00.32u_5.17.05.23
Kernel Version 2.6.37.6-cyanogenmod-geb50077
As stated, gps & signal were fixed with a simple radio flash from 5..11.05.14 - 5.17.05.23
but bluetooth remained unable to connect. My 2 devices were in the list showing as 'Paired but not connected'
Clicking on them they would say 'connecting' but that process would end with no error or message & no connection made.
The only long press option on them was 'unpair' - so no option to delete & try again.
I then found a potential fix which is I assume is fairly well known BUT I could not get it to run:
SOLUTION (copied from external site)
I ran the Terminal app and entered
'su'
(App requests root permissions, grant them). Then I went to the device's bluetooth settings with
'cd /data/misc/bluetoothd'
(Note the 'd' at the end). There I found a directory named by the bluetooth chip's ID, in my case '38:E7:B8:45:21:a4'. I renamed this directory
'mv 3* hidden'
Turned bluetooth off and back on and could use bluetooth again.
Every time I ran the terminal I could get su to work, with permissions granted as confirmed in the toast message that would pop up- BUT whenever I typed 'cd /data/misc/bluetoothd' I only ever got 'Permission Denied'.
All the fix posts I read about this pointed towards root & su permissions not working correctly but mine certainly were. I had tried all the usual fixes of un-applying/re-applying SU permissions, root etc.
I also tried the same commands through adb, all with the same result.
It then occurred to me that the Terminal was only changing a folder property so I used 'ROM Toolbox Pro' -> 'Root Browser' to find the folder in question ('38:E7:B8:45:21:a4' in my case).
It became apparent that the path given in the 'fix' was incorrect (for my Desire GSM at least).
The folder I was looking for was actually in 'd/data/bluetoothd' - so the 'permission denied' error was because the path was incorrect, not that SU permissions were not granted!
Before I actually tried that correct path though- I noticed that to make files hidden the '.' (full stop) prefix is added to the start of the file or folder name.
I used Root Browser to long-press on the '38:E7:B8:45:21:a4' folder & then 'rename' from the menu - making the folder name '.38:E7:B8:45:21:a4' (note the full stop at the start.)
I then re-enabled bluetooth - this time noticing that both my paired devices were no longer there (this is good!). I made the Desire discoverable then did a scan...success!
Both my devices paired & connected exactly as they should. I now notice in Root Browser that the file structure has also changed with there being no 'bluetoothd' folder at all.
I also imagine that entering the correct folder path in terminal or adb would produce the same results, though I cannot confirm this as the procedure described had already worked for me.
So, long story short:
1. Make sure bluetooth is turned OFF then open Rom Toolbox Pro -> Root Browser (or any root browser with su permissions I guess?)
2. Navigate to the folder d/data/bluetoothd/38:E7:B8:45:21:a4 (#Note: your '38:E7:B8:45:21:a4' folder will probably be named differently)
3. Long press on the '38:E7:B8:45:21:a4' folder. (or whatever yours is called)
4. From the pop up menu - select 'Rename'
5. Add a full stop '.' at the beginning of the folder name Eg '.38:E7:B8:45:21:a4' (Keep the rest of the name as it was)
6. Turn on Bluetooth - in 'Bluetooth settings' make your device discoverable & note that if any paired devices were present, they should now be gone from the list.
7. Scan for bluetooth devices, obviously making sure they are also switched on & discoverable! (if it doesn't automatically)
8. Your devices should now show up, ask to pair, ask for pin numbers if needed & then connect automatically.
If this has been covered elsewhere please accept my apologies, & delete the post if it's deemed as clutter- I was merely trying to help
Click to expand...
Click to collapse
I can't find folder *data* in folder *d*. I have a separate folder *data*. There is a folder named *bluetooth* in folder *d*. It also didn't work for me.
Related
As many PDA2k users might have noticed by now, a file named BtTrayLog.txt found in the main directory on the device keeps expanding endlessly and thus eats every bit of memory you might have. There is no setting that you can change to solve this nor does deleting this file keeps it from popping back again.
I found a temporary solution and it has been working perfectly for the last few days. You can replicate my solution by following these steps:
1) Turn your Bluetooth on.
2) Start your "File Explorer" on your device and go to the main folder "My Device".
3) You will find a file named BtTrayLog.txt (when I first discovered this file it was 32 MB big!). Delete this file.
4) Close your File Explorer and wait for a few minutes.
5) Start your File Explorer again and you will find the same file again, although this time it should be very small (the smallest I could get it was 866 B only.)
6) Click and hold on it until the submenu appears and then select "Properties".
7) Check the "Read only" box and click "Ok".
Voila! The file will remain but its size will not change. The solution is a little primitive but it will spare you the effort of having to delete the file every couple of days. I list it here for the benefit of other users until CD fixes this issue in its upcoming ROM upgrade, whenever that may arrive.
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.
Hello,
I was given a Galaxy Wonder to repair, the problem is the kid who's phone it is, forgot the lock screen password/code nor did he have a google account on the device. And the best part, is he want's the data!
I would backup and flash the device, but adb commands requiring root privileges won't work directly - it complains that "adbd cannot run as root in production builds"...
I got ADB up and running and installed "su" (root privileges in shell).
I've tried many suggestions with changing and deleting entries in the "data/data/com.android.providers.settings/databases/settings.db" file on the device.
There are no more references left in the "system" or "secure" tables to any kind of "locking". According to many posts the lock screen should not be present after reboot or it should be anything random (or nothing).
Also, I've deleted the gesture and password files from /data/system/...
Nothing has worked to remove the screen lock. Please help.
~confuded
There is a special secret dial code for invoking an extended Engineering Mode on the Oneplus 3:
*#36446337#
This opens up the menue of this extended EM.
It worked. But I screwed it up, so I cannot invoke it any more
I know, shame on me and all that stuff, this was totally my fault, as I played around with the apk, copied (not moved) it to the Download folder and tried to install it like a normal app.
Did not work.
But now also invoking the original extended EM no longer works ([email protected]).
I'd like to kindly ask the real experts among you:
1. What is it I screwed up with my stupid attempts to install this apk?
2. Is there any way to restore the information the dialer needs for parsing this secret code - other than performing a factory reset?
Or which is the information that got lost or overwritten?
3. All files in
/system/app/EngineeringMode
/system/app/EngSpecialTest
appear to have been unaffected.
(But could anyone please share the proper contents of these two folders, in case the extended EM works properly for him?)
4. Is there any way of invoking the extended EM directly working around doing it with the secret dialer code given above? e.g. by modifying the apk - admittedly in a more sophisticated way I attempted ?
I hope my question comes in the proper forum, don't want to cross-post it.
Thanks in advance!
Please Post Files as attachment or Link...
Would you be kind enough to post these files or a link to them? Unsure, but suspect a permissions issue or incorrect location of said files. I think you can connect to computer (with debugging enabled, & allowing access & allowing the rsa prompt also). You will need a command line/terminal depending on your desktop /laptop os. . I would say that you can use adb devices, then adb shell and finally am then the package name. Not sure how to format the activity manager command. Mayb am start - n xxx or am start xxx. Perhaps forum or Google can help. I kno that typing just am from the adb shell will list all possible options.
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