Related
I have the original Droid phone. Thus, to tether it to my CN I need to get the CN able to work with Ad-Hoc. I had come to the conclusion the only way to accomplish this was via the ADB shell. The problem is I cannot get ADB to work.
So, that being said, and before I bury another 4 or 5 hours into this, is there another way to get my CN working with my Droid?
Yes, you can do it on your nook using certain apps. I've done it with Root Explorer(paid app), which allows you to alter/replace/change permissions on any system file. Other file manager type programs might be able do this too, maybe even some free ones, but the only one I can verify is root explorer.
pfcwintergreen said:
Yes, you can do it on your nook using certain apps. I've done it with Root Explorer(paid app), which allows you to alter/replace/change permissions on any system file. Other file manager type programs might be able do this too, maybe even some free ones, but the only one I can verify is root explorer.
Click to expand...
Click to collapse
Do you mind posting instructions, or a link to how you did it? I have this exact same situation as the OP (Droid 1/NC).
"Easy Tether" for rooted Droid phones works perfectly for me. It's a Market download and free -- creates an infrastructure network the CN can see and use rooted or unrooted. Rooting your phone (if not already) is pretty quick and easy as compared to rooting the Nook. I have a Droid X.
I have both easy tether and root explorer. Easy tether will not work as it requires a cable connection.
Can you explain what i need to do with root explorer?
jtpryan said:
I have both easy tether and root explorer. Easy tether will not work as it requires a cable connection.
Can you explain what i need to do with root explorer?
Click to expand...
Click to collapse
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Thank you so much!!! Worked great!
Sent from my LogicPD Zoom2 using XDA App
racks11479 said:
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Click to expand...
Click to collapse
Hmmm, won't start wifi at all now. When I pasted the new file should the name be wpa_supplicant or wpa_supplicant.adhocfix? I used the former.
-Jim
Oops. My mistake. Too embarrasing to discuss ;+{
Anyway, all is well. Works the balls!
jtpryan said:
Oops. My mistake. Too embarrasing to discuss ;+{
Anyway, all is well. Works the balls!
Click to expand...
Click to collapse
No please discuss, we're all here to learn from your mistakes! j/k
Glad it worked out for you.
jtpryan said:
Oops. My mistake. Too embarrasing to discuss ;+{
Anyway, all is well. Works the balls!
Click to expand...
Click to collapse
Please explain so i dont make this mistake when i try this later.
Im having the same issue as OP. ill try this method when i get home.
racks11479 said:
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Click to expand...
Click to collapse
Clarify this step for me. Im confused at reading this.
You say to copy then rename original file, then paste. By original file do you mean the one on the sdcard and not the one being pasted?
Could i just pasti into system/bin , and then rename that file? Im just trying to clear this up?
Randomhero27 said:
Clarify this step for me. Im confused at reading this.
You say to copy then rename original file, then paste. By original file do you mean the one on the sdcard and not the one being pasted?
Could i just pasti into system/bin , and then rename that file? Im just trying to clear this up?
Click to expand...
Click to collapse
Yes. You could just paste then rename the wpa_supplicant.adhocfix to wpa_supplicant. I wanted you to renam the original file in your system/bin to wpa_supplicant.bak so you woul have a backup of the original just in case something goes wrong.
Sent from my "NookDroid" using XDA App
Ohhhhhh okay. Sorry if it seemed dumb. Im at work and without my Nc so im not able to see what is in there.
There's never a dumb question when you're learning something from it
Sent from my "NookDroid" using XDA App
racks11479 said:
Place the patched wpa_supplicant file from here http://forum.xda-developers.com/showthread.php?t=868354 somewhere on your sdcard.
Open Root Explorer and navigate to the file on the sdcard.
Copy the file.
Navigate to system/bin
Mount R/W
Rename your original wpa_supplicant file to wpa_supplicant.bak
Paste the new file. (make sure the name is as the original)
Reboot your nook.
Click to expand...
Click to collapse
went home and did this. THANKS!!!! Saw my IP4 MYWI network right away.
It works!! Thanks!
Under 1.1 I found that the ADHOC supplicant was so infuriatingly unstable it was almost unusable, and the lack of reconnect on wakeup was such a pain. this has been the major benefit of moving to Froyo for me - adhoc is seamless.
Hi Im almost done with it but I'm not sure how to rename the file. I'm using root explorer for some reason ADB is not pushing the file. I'm running 1.1 on my nc. I'm in root explorer and I got all the way to copy the file mount r/w and then i'm stuck.
Please help. I'm so close.
Hey bono quick ? when you use froyo is it on the sd card or is on the nook itself. I'm not sure how to get that far. I'm mad because I can't get these files right so that I can connect to my wireless tether through my phone. I'm so close. I finally got ADB to work but I can't push the files to the nook. I'm so lost right now.
Hi, I accidentally deleted the /system/bin/sh file from my system while messing around in the terminal after rooting my phone. Seeing how the shell is a pretty important part of the operating system, I kinda don't want to reboot the phone until I've replaced it. Therefore I wondered if any of you could just send me a copy of the shell on your system. I've got the Motorola Milestone UK model, with Android 2.1 Update 1.
are you running a custom ROM or just stock 2.1.1? you can always download a custom ROM update.zip made for the milestone 2.1.1 and unzip it, and just copy the /system/bin/sh file back onto your phone using root explorer or push using adb then make sure the proper permissions are set (i believe its 777)
i'm in the US and have the "Droid" so that's really all the help i can offer.
hope that helps
vuarnet said:
are you running a custom ROM or just stock 2.1.1? you can always download a custom ROM update.zip made for the milestone 2.1.1 and unzip it, and just copy the /system/bin/sh file back onto your phone using root explorer or push using adb then make sure the proper permissions are set (i believe its 777)
Click to expand...
Click to collapse
Thanks for the tip. Things seems to be working now
Great! Glad to hear it
Sent from my Droid using XDA App
adb shell, sqllite, build prop...Any other non-tech major people around here a little lost?
I'm rooted. I don't want the new update. I can follow directions but would be more comfortable if some basic instruction were written. Treat me like I'm 10.
It looks like the best way to do this is as follows:
"From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
"
Do I unzip the attached binary and paste that into the location or the .zip as a whole? What do I use as a terminal?
I've been flashing my DROID since day one but the NC development circle has been far from entry level user-friendly. Any help would be appreciated.
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
britoso said:
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
Click to expand...
Click to collapse
Progress. However...
I got SQLite on my PC. I found the devicemanager file on my NC, pasted it to my SD card for transfer over to my PC for editing. I trasnferred the file over to my PC for editing. I open SQLite but have no idea how to use it.
I just did this today using sqlite editor only!!! Its a GUI so it real simple to use.
1.Install the apk
2.reboot
3.go to extras and launch sqlite editor
4.allow it, give it the permision it needs
5.look for DeviceManagerService
6.click on devicemanager.db
7.click on registry
8.look for _id 7, name>>>> "com.bn.device.fota.mode"
9.scroll to the right and click and hold value field "auto", until a little pop up shows and select edit field
10. Change the value from auto to manual
11. Save
Done!!!
If you need the apk here is a link I just made
?d=LTSQDZ65 for megaupload (sure u guys can piece it together!)
Let me know if it helped anyone!
Yes, we totally need another thread on this. I must note that pushing the build.prop in my thread and my two Nook Colors have not updated. Dunno about this method or others. Caveat emptor!
This is exactly what I was looking for. Thank you. Very simple.
Sent from my NC using XDA App
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
tablo said:
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
Click to expand...
Click to collapse
In theory it should work for both, whether its a soft root mod or simply a bootable sd card that emulates froyo... It's a matter of just having root access and changing a registry setting on the device itself. Hope this shines some light! happy rooting ppl
Not noobie enough for me, sigh
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Droiddict said:
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Click to expand...
Click to collapse
If you read this >> http://forum.xda-developers.com/showthread.php?t=1007551
you will see that the sqlite method is used by many and is the simplest way too, again this is a GUI, so no shell command line... How can this be difficult??
Just follow my steps... it works
I have had nothing but problems with my rooted NOOK Color due to B&N auto updates. I followed your instructions and now I hope my problems are resolved and my NOOK Color will never update again.
Thank you
Hi, does anyone know the best way to unroot the dell streak. I used Superuser7 no problems, but need to go back. Is this possible without wiping/flashing a new rom?
Cheers
if you open up the superuser7 update zip you'll see what all it installs and where. Using a tool such as root explorer you can go to ~/xbin and /system/app and remove those files.
Assuming you're okay with CWR its just a matter of then rebooting.
If you really want to lock it down, you'll need to grab the dell recovery image from the wiki for your build and flash it with fastboot after cleaning up superuser.apk, busy box, etc.
So just to be clear
Do I have to delete:
-bash
-busybox
-profile
-su
in the xbin folder
and the apk file in /system/app (using root explorer) and then later flash the original dell recovery rom with fastboot from here: http://forum.xda-developers.com/wiki/Dell_Streak_7#Official
I just want to make sure I am doing it right, unfortunately I have to send mine in, it has an issue with the display (flickering in low brightness)
Hello guys, I'm here to show you how to fix it without repeatedly turning it on and off. (I provided the stock bluetooth for you guys, that don't have it)
This is only for LTE jem, sorry for any convenience. (For bluetooth.)
1. Download this https://www.dropbox.com/s/29pw4nm27pgl8aj/Bluetooth fix.rar?dl=0
2. Extract it.
3. Replace /System/etc/Bluetooth/bcm2076_20mhz.hcd with BCM2076_26MHZ.HCD
4. Replace /System/vendor/firmware/bcm2076_20mhz.hcd with bcm2076_20mhz.hcd (The one I provided for you)
Then tada! Bluetooth works, you can only connect to compatible devices it seems but bluetooth finally works.
Now onto how to fix amazon jem not being recognized, on your pc/laptop.
I'm going to be honest here, this will be very short lol.
So anyways, go to this link https://windows10skill.com/kindle-fire-not-recognized-on-windows-10/#2 and follow the steps provided. Method 2 helped me, so try that first if you want. (This can work on windows 7 too, I forgot where I found it at but you can try following it still.)
That's all I have, for now. I hope all of you guys get everything fixed! Please let me know if this was helpful for you, I would appreciate it.
This RAR file won't open
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
bapi28 said:
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
Click to expand...
Click to collapse
Oh my god, I'm so sorry I forgot to mention this is only for lte devices. Sorry!
Understood step 4. But on step 3 when it states replace a file with a file having a different name, does that mean 1) delete original file and put new file in that folder, or 2) rename new file to existing files name and copy over top of existing file replacing it?
Ok, answered my own question and figured it out.
I did not have such a file in the /System/etc/Bluetooth folder.
I renamed the 26mhz file to 20mhz and replaced (overwrote) the file in the /System/vendor/firmware folder.
It is working great finally after issues for the past few years. Awesome. Thanks.