Hello,
my old Nook sometimes has faulty change page buttons, when i press them it's like they are constantly pressed and changes a lot of pages before it stops.
So I would like to disable them software side so that I can only use the touch screen (which works fine).
is it possible?
Also I have no way in settings to change the time, is it possible to do that maybe using terminal?
Thanks!
borzowsky said:
Hello,
my old Nook sometimes has faulty change page buttons, when i press them it's like they are constantly pressed and changes a lot of pages before it stops.
So I would like to disable them software side so that I can only use the touch screen (which works fine).
is it possible?
Also I have no way in settings to change the time, is it possible to do that maybe using terminal?
Thanks!
Click to expand...
Click to collapse
Which Nook model is this, exactly?
Hi sorry, it's the Nook Simple Touch (not the glowlight one, but the one without backlit)!
Thank you very much.
borzowsky said:
Hi sorry, it's the Nook Simple Touch (not the glowlight one, but the one without backlit)!
Thank you very much.
Click to expand...
Click to collapse
Alright, good.
To completely disable the four hard keys, all you have to do is navigate to /system/usr/keylayout using ES Fike Explorer (or something else), long-press on TWL4030_Keypad.kl, and change its permissions from rw- r-- r-- to --- rwx r-x. Then, after you reboot, your hard keys will not function anymore.
If for some reason you end up wanting your hard keys back, just change the permissions back to their original state.
Hope this helps!
ИΘΘK¡€ said:
Alright, good.
To completely disable the four hard keys, all you have to do is navigate to /system/usr/keylayout using ES Fike Explorer (or something else), long-press on TWL4030_Keypad.kl, and change its permissions from rw- r-- r-- to --- rwx r-x. Then, after you reboot, your hard keys will not function anymore.
If for some reason you end up wanting your hard keys back, just change the permissions back to their original state.
Hope this helps!
Click to expand...
Click to collapse
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
borzowsky said:
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
Click to expand...
Click to collapse
It probably is - I'm researching it right now. While you wait, though, here's the command for setting the time/date through ADB:
Code:
adb shell date -s YYYYMMDD.HHmmss
...in which "Y" is year, "M" is month, "D", is day, "H" is hour, "m" is minute, and "s" is second.
---------- Post added at 10:56 ---------- Previous post was at 10:45 ----------
borzowsky said:
Hi, sure it helps!
Just a question, is it possible to change it in ADB with terminal? I have my nook very stock and I like it this way, I just rooted it years ago to put on the UK firmware (that inclues italian language).
Thank you very much!
Click to expand...
Click to collapse
Alright, I got it.
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
Then, a reboot will finalize the change, which can be done either straight from your Nook, or using this ADB command:
Code:
adb reboot
ok one last thing and I won't bother you no more!
to revert to working buttons, what is the corrisponding command to this one?
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
is the power button and the "N" button continue to work if i do the change, right?
That changes only the change page buttons, right?
borzowsky said:
ok one last thing and I won't bother you no more!
to revert to working buttons, what is the corrisponding command to this one?
Code:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
is the power button and the "N" button continue to work if i do the change, right?
That changes only the change page buttons, right?
Click to expand...
Click to collapse
To revert the page buttons to working order, use this command:
Code:
adb shell chmod 644 /system/usr/keylayout/TWL4030_Keypad.kl
And yes, this modification will only turn off the side page-turn buttons, and not the "n" and power buttons (those are controlled by a different file, gpio-keys.kl).
Ok I tried the clock trick and it works, but this command:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
says read-only file system, how can i fix this?
edit: ok i put this:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
in the shell, then quit the shell, gave the command and it didn't told me anything
then I did adb reboot and it rebooted, but the buttons to change page are still working.
borzowsky said:
Ok I tried the clock trick and it works, but this command:
adb shell chmod 075 /system/usr/keylayout/TWL4030_Keypad.kl
says read-only file system, how can i fix this?
edit: ok i put this:
Code:
mount -o rw,remount /dev/block/mmcblk0p5 /system
in the shell, then quit the shell, gave the command and it didn't told me anything
then I did adb reboot and it rebooted, but the buttons to change page are still working.
Click to expand...
Click to collapse
Hmm. Let me look into this.
ИΘΘK¡€ said:
Hmm. Let me look into this.
Click to expand...
Click to collapse
yeah sure, take your time!
you've been really helpful so far
Did you manage to find a way?
borzowsky said:
Did you manage to find a way?
Click to expand...
Click to collapse
Sorry for not getting back to you - been pretty busy lately. Here's what I'm tryng to figure out how to do:
I have discovered in the past that if a system file's permissions are not rw- r-- r--, or 644 in numerical value, the OS will not recognize the file as usable. What I am trying to do here is use the chmod command (change mode) to change the permissions of TWL4030_Keypad.kl to something other than the default setting so that it will not get used, therefore making the side keys unusable.
The problem is, I need to actually find a permission setting that does keep the system from seeing the file, and then I have to translate it into a numerical value for the chmod command to work. I know that --- rwx r-x works, but I don't know if I translated it right.
I'll post again when I get something usable.
---------- Post added at 10:41 ---------- Previous post was at 10:12 ----------
borzowsky said:
Did you manage to find a way?
Click to expand...
Click to collapse
Alright, I have a solution! Use this command in ADB (after mounting /system as read-write [adb shell mount -o rw,remount /dev/block/mmcblk0p5 /system]):
Code:
adb shell chmod 000 /system/usr/keylayout/TWL4030_Keypad.kl
Then, after a reboot, you will be good to go.
I'll try this as soon as I get home.
thank you for your efforts.
great it worked, thank you very much!
Related
just a refresher to help those trying to read the dozens of new pages credit goes to david279, Gregalous and others
MMS FIX - WORKS
cd C:\android-sdk-windows\tools
adb shell
cd /data/data/com*telephony/databases
sqlite3 telephony.db
update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; *input your phone number example 13303214294 dont forget the'*
adb reboot
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
3D GALLERY INSTALL - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push Gallery3D.apk /system/app
adb reboot
REOCCURRING SIGN-IN FAILURE - DOESN'T WORK
install google voice 0.2
MARKET NOT SHOWING INSTALLED APPS - WORKS FOR MANY (may fix failing sign-in error at boot)
cd C:\android-sdk-windows\tools
adb pull /system/build.prop .
used wordpad (don't use MS notepad) to edit build.prop with the following:
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD79/22607:user/release-keys
ro.cdma.home.operator.numeric = 310120 (note 310120, not 310012)
ro.cdma.home.operator.alpha = Sprint
ro.com.google.clientidbase=android-sprint
adb remount
adb push build.prop /system/
clear market cache
adb reboot
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
I did not mean for the original title to be dirogitory i simply ment to make it as clear as posible it fixes many problems that we have had in that rom i dont want somone applying it to another 2.1 rom that it doesnt work for and coming back and saying ruler why wernt you more clear...
this was all posted (in one post) by rank78 i reposted so i could make a wiki page out of it (the fix finds were descovered by multilple people if you want your name up here pm me and il put it up)
these problems are more-so in all 2.X roms, the way your title is is like your bashing, but thanks anyway
lv2bll said:
these problems are more-so in all 2.X roms, the way your title is is like your bashing, but thanks anyway
Click to expand...
Click to collapse
x2 but thanks for the effort.
Great info, but can you edit the title of the post? It seems a bit harsh to flipz. All these guys deserve the utmost respect for doing these ROMs and not asking for much from us.
Just my 2 cents, thanks again.
wow people are sensitive. he's not bashing flipz...
rank78 also posted the links to the files needed for these fixes, i think it would be a good idea to post them on the first post of this topic
Great
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Kykiskly said:
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Click to expand...
Click to collapse
Tried the MMS fix on Darch's 2.1 ROM... no luck.
link to the post with files needed to fix. i pm'ed flip to add these to the first post.
http://forum.xda-developers.com/showpost.php?p=5799963&postcount=1908
rank78 said:
link to the post with files needed to fix. i pm'ed flip to add these to the first post.
http://forum.xda-developers.com/showpost.php?p=5799963&postcount=1908
Click to expand...
Click to collapse
Thanks Rank- How do I get the 11 MDN number from my phone?
Kykiskly said:
Thanks Rank- How do I get the 11 MDN number from my phone?
Click to expand...
Click to collapse
its just 1, area code, phone number = 11
Kykiskly said:
Thanks Rank- How do I get the 11 MDN number from my phone?
Click to expand...
Click to collapse
I believe it is your phone number 1-234-567-8901 that is 11
Kykiskly said:
Thanks Rolermon,
Quick question, would the MMS fix work for the 2.1 Darchdroid? Also, when you said step 5. update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; -----------are we to changing the MDN=************ for something on our end, or do we leave it as it is?
Edit---------Another question on the QUICKBOOT FIX - WORKS--------
Where do I find the reboot file that I need to push to /system/bin?
Click to expand...
Click to collapse
fyi the quickboot fix is for the program quickboot that wasn't functioning after flashing the rom.
the reboot file is zipped in my post
rank78 said:
fyi the quickboot fix is for the program quickboot that wasn't functioning after flashing the rom.
the reboot file is zipped in my post
Click to expand...
Click to collapse
Many thanks, but I was able to push the file to the destination. About the MMS, i did as instructed, still didn't help at all. I am not able to mms pics out either.
I am on Darchdroid V1 2.1
You guys probably know a lot more about this than I do, but shouldn't the MMS link be:
http://mms.sprintpcs.com/servlets/MMS?X-SPRINT-MDN="Your MSID Number" ?
on my hero, i just put in:
http: //mms.sprintpcs.com/servlets/MMS
and it worked.
rulermon said:
just a refresher to help those trying to read the dozens of new pages credit goes to david279, Gregalous and others
MMS FIX - WORKS
cd C:\android-sdk-windows\tools
adb shell
cd /data/data/com*telephony/databases
sqlite3 telephony.db
update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=YOUR11DIGITNUMBER' where name='Production'; *input your phone number example 13303214294 dont forget the'*
adb reboot
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
3D GALLERY INSTALL - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push Gallery3D.apk /system/app
adb reboot
REOCCURRING SIGN-IN FAILURE - DOESN'T WORK
install google voice 0.2
MARKET NOT SHOWING INSTALLED APPS - WORKS FOR MANY (may fix failing sign-in error at boot)
cd C:\android-sdk-windows\tools
adb pull /system/build.prop .
used wordpad (don't use MS notepad) to edit build.prop with the following:
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD79/22607:user/release-keys
ro.cdma.home.operator.numeric = 310120 (note 310120, not 310012)
ro.cdma.home.operator.alpha = Sprint
ro.com.google.clientidbase=android-sprint
adb remount
adb push build.prop /system/
clear market cache
adb reboot
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
I did not mean for the original title to be dirogitory i simply ment to make it as clear as posible it fixes many problems that we have had in that rom i dont want somone applying it to another 2.1 rom that it doesnt work for and coming back and saying ruler why wernt you more clear...
this was all posted (in one post) by rank78 i reposted so i could make a wiki page out of it (the fix finds were descovered by multilple people if you want your name up here pm me and il put it up)
Click to expand...
Click to collapse
There still needs to be appropriate quit and .quit statements added in to get out of sqlite3 and shell.
ripleys said:
You guys probably know a lot more about this than I do, but shouldn't the MMS link be:
http://mms.sprintpcs.com/servlets/MMS?X-SPRINT-MDN="Your MSID Number" ?
on my hero, i just put in:
http: //mms.sprintpcs.com/servlets/MMS
and it worked.
Click to expand...
Click to collapse
What do you mean by "http: //mms.sprintpcs.com/servlets/MMS"? Didn't you complete the sentence with the MDN=-----------------?
Kykiskly said:
What do you mean by "http: //mms.sprintpcs.com/servlets/MMS"? Didn't you complete the sentence with the MDN=-----------------?
Click to expand...
Click to collapse
No, supposedly both work. The MDN version works all the time and the MMS version works some of the time.
Mistamike17 said:
No, supposedly both work. The MDN version works all the time and the MMS version works some of the time.
Click to expand...
Click to collapse
Ok but after that statement, what goes after, cuz since we are in the sqlite3 telephony.db, we cant adb reboot from there. What is the command to close/save the statement. I tried .quit, exit, adb reboot and no success.
how do we know that by doing the above statements the change took effect?
1) update carriers set mmsc='http://mms.sprintpcs.com?X-MDN=1+area code + cell #' where name='Production'; *1+area code + cell '*
2)http: //mms.sprintpcs.com/servlets/MMS
This also worked on Souffle!!! Thanks guys!
Code:
QUICKBOOT FIX - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb push reboot /system/bin
adb shell
cd /system/bin/
ls **optional...I did this just so I could make sure the reboot file was there**
chmod 755 reboot
chmod 755 /system/bin/reboot
adb reboot
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
lakeside00 said:
Is it possible to change the lockscreen to the default android, i'm new to android nd still tryna get a hold of things. Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
you can remove the HtcLockScreen.apk from /system/app/ and it will default to the stock android one. Problem is that is suffers from the same fate as many others where the slder is up/down and the time is jummbeled on the left side.
Oh and of course to remove/rename the file in /system/app/ you must be rooted and in recovery mode.
I'm working on how to fix the screen. Flipz did it for android 2.0 but it isn't the same fix in 2.1. If I get more info I'll post back.
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
gmelchert said:
I tried to remove HtcLockScreen.apk via adb but I don't think we have system write access yet. even through adb. someone correct me if I'm wrong but I believe this is true.
Edit: As said above... you have to be in recovery. I stand corrected. don't listen to me!
edit #2: tried it in recovery... couldn't even remount. I don't think I did anything wrong...
Click to expand...
Click to collapse
LOL! love the step by step edits...
I have a script that makes it easy, it is just a modified version of Toast's. It cuts it down to one command input instead of three.
Any way here are the steps:
With phone on plug it into your computer. Open two command windows. Navigate one to the folder you have downloaded toasts recovery script to.
1) In the window that is at evo-recovery> type: adb reboot recovery
This boots you in to the stock recovery
2)in the same window type windows-recovery.bat (adjust for your OS)
This gets you into Amon-RA's recovery
3) Wait for the phone to get the new recovery screen. In the other command window type: adb shell mount -a
Step 3 can be adb remount or you can type adb shell then at the # type #mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system
Any way after that point you can exit adb shell back to the command prompt and push/pull anything to /system
unfortunately you can't see it right away and have to wait for reboot. Also this limits some of the apps that we can install because some will need to write to /system and cannot once rebooted.
I searched around and couldn't get a clear answer. I'm a noob at anything command prompt/terminal related.
I was screwing around with adb last night after figuring out that I can remove program .apks with the rm <com.whatever.program> command. I got a little trigger happy and removed things that I don't use, just to test it out. I made a nandroid backup before I started. The phone runs fine, but now the Market won't download anything. It just sits on the Starting download... screen.
One of the .apks I removed was GmailProvider.apk. Whether this is the problem or not, I'd like to reinstall it for practice. I can always nand restore later.
So my question is... How can I use adb push to reinstall an apk?
I tried:
Code:
adb push C:\GmailProvider.apk
adb install C:\GmailProvider.apk
adb install C:\GmailProvider.apk \system\app
And about every variation of the 3, in and out of the adb shell.
It didn't work, and I'm at a loss to do anything else. So does anyone have any suggestions?
You have to push it abs then give it permissions.
So after pushing the apk give it permissions by doing this.
Code:
Adb push C:/gmailprovider.apk /system/app/gmailprovider.apk
adb shell
Chmod 775 /system/nameofapp.apk
Exit
Adb reboot
Your phone needs to be rebooted so I added the adb reboot, but you can just turn it off and on like you would normally or use that command.hope it helps.
Sent from my Eris using XDA App
Code:
# Chmod 775 /system/GmailProvider.apk
Chmod: not found
What's Chmod do, anyway?
EDIT: Forgot to cd to the directory...lemme try again.
EDIT2: Same error.
Okay, I tried:
Code:
# install /system/app/GmailProvider.apk [-cdDsp]
With no errors. Lemme see if it worked.
EDIT: I can see it, but the Market still isn't downloading apps. Lemme try an actual program.
Raikalo said:
Code:
# Chmod 775 /system/GmailProvider.apk
Chmod: not found
What's Chmod do, anyway?
EDIT: Forgot to cd to the directory...lemme try again.
EDIT2: Same error.
Click to expand...
Click to collapse
Ok I see two things that might be wrong with what you did.
Try not capatalizing the first letter(Not sure if this is a big deal but better to make sure.) and fix your path, GmailProvider.apk should be in the system/app folder.
Code:
adb shell
chmod 775 /system/app/GmailProvider.apk
adb reboot
The chmod command (abbreviated from change mode) is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes
EDIt:
Raikalo said:
Okay, I tried:
Code:
# install /system/app/GmailProvider.apk [-cdDsp]
With no errors. Lemme see if it worked.
EDIT: I can see it, but the Market still isn't downloading apps. Lemme try an actual program.
Click to expand...
Click to collapse
Yea you might be able to see it but the app might not have the right permissions to be used. Therefore it might be the reason why you can't download apps from market.
Excellent.
Code:
adb push C:/GmailProvider.apk /system/app/GmailProvider.apk
adb shell
chmod 775 /system/app/GmailProvider.apk
adb reboot
Worked like a charm. The capitalization was required; it gave an error without it. I installed Gmail.apk again using the same method and ran the program, and it worked. Thanks!
EDIT: GASP! Market works.
You're a lifesaver. Well, ROMsaver. I guess this means that GmailProvider.apk and gtalkservice.apk can't be removed from the phone.
Raikalo said:
However, the Market still won't download. Hm.
Click to expand...
Click to collapse
I just want to take this moment to make a Public Service Announcement: Everyone please remember to do a Nandroid backup before making any changes to your /system area.
Raikalo said:
Excellent.
Code:
adb push C:/GmailProvider.apk /system/app/GmailProvider.apk
adb shell
chmod 775 /system/app/GmailProvider.apk
adb reboot
Worked like a charm. The capitalization was required; it gave an error without it. I installed Gmail.apk again using the same method and ran the program, and it worked. Thanks!
However, the Market still won't download. Hm.
Click to expand...
Click to collapse
Don't know what to tell ya, you can start adding back the apks you deleted or do that nand restore since you already know how to install back a system apk, so you learned what you wanted
EDIT: I see you got it to work so that's good news, but like Nestor pointed out always use nand backup before you do any changes to the system area, I've learned to do this the hard way lol.
It's a good reminder
Thanks a ton guys I'll nand backup in a few to have a better restore point.
Learning android-related things ftw!
Oh, one more thing.
I saw something about adding an Environmental Variable to windows that involved adb? Could someone explain that?
- Also, Mikey1022 has reminded me to add the "ADB" directory path as a system variable in windows...
To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista) then select Environment Variables.
Click "New" under System Variables and add the following:
Variable: adb
Value: C:\android-sdk-windows-1.1_r1\tools
Click to expand...
Click to collapse
There's an example. I tried this and it didn't do anything.
Raikalo said:
Oh, one more thing.
I saw something about adding an Environmental Variable to windows that involved adb? Could someone explain that?
There's an example. I tried this and it didn't do anything.
Click to expand...
Click to collapse
i think Thefuzz4.net explained this better
To make life easier, lets add a global path to the android SDK tools. Right-click My Computer > Properties,
click on Advanced, then click on Environment Variables.
Doubleclick on PATH, then at the end of the Variable value, add a semi colon ";" and then c:\AndroidSDK\tools
Doing The above ^^ will let you run adb from anywhere on your computer, like your desktop. You won't have to change to the directory and the run adb anymore, you can just run adb from anywhere on the command prompt. Its basically a little trick for us lazy people that hate having to "cd C:/android/tools" before running adb.
Does anyone know of a good resourse for adb and/or shell commands. Every time i try to goole it i just get links to different forums with just basic stuff, push, pull, ect. Id like to find something much more complete including chmod and the like
Sent from my Eris using XDA App
Thanks t2. Makes sense now. I hate CDing to the directory, so shortcuts are also ftw.
@above -- couldn't find a real resource so I resorted to asking specific questions on xda. if you find a resource lemme know.
ALSO -- chmod 775 /system/app/RandomProgram.apk.....what does the "775" do?
Raikalo said:
Thanks t2. Makes sense now. I hate CDing to the directory, so shortcuts are also ftw.
@above -- couldn't find a real resource so I resorted to asking specific questions on xda. if you find a resource lemme know.
ALSO -- chmod 775 /system/app/RandomProgram.apk.....what does the "775" do?
Click to expand...
Click to collapse
the different numbers are different permission settings. I forgot the other numbers, but their are others that set the applications for different permissions in the system. Someone correct me if I am mistaken though.
Finally found some explanation of chmod at catcode.com/teachmod/ . not sure if it directly applies to andriod, but seems to make sense to me now
Sent from my Eris using XDA App
wrong thread
I have replaced some fonts on the nook and everytime at some point, i get issue with it.. it does not boot anymore... and every time i need to do a factory reset, re-root. Is there steps/precautions i need to be aware when replacing fonts on the nook or adding apps in system/app??
I have an htc desire rooted and i have never had issues like that on it; i have replaced fonts, edited files like build.prop or key mapping, added/deleted/renamed apps in system/app and i never had a single issue... maybe the nook is different i don't know
To answer your question, no, it's not dangerous.
Linux doesn't care at all about fonts.
So if you have a problem with fonts, use ADB and logcat and actually figure out what the problem is.
Even with flashing dots, ADB and logcat (and dmesg) work.
Renate NST said:
To answer your question, no, it's not dangerous.
Linux doesn't care at all about fonts.
So if you have a problem with fonts, use ADB and logcat and actually figure out what the problem is.
Even with flashing dots, ADB and logcat (and dmesg) work.
Click to expand...
Click to collapse
adb does not detect the nook while it is booting... it only detects when it's booted or when i use cwm
Well, apparently you are bashing some non-font thing.
How are you copying over the font?
Are you using some wonderful "Insta-Mega-File-Masher-Omatic"?
Which font are you replacing?
Stick to basics.
Get your Nook working with 1.2.1 since that is where you should be.
Get ADB working.
Remount /system r/w, adb reboot, still working? Yup.
Remount /system r/w, adb push your font to /system/fonts/temp.ttf, adb reboot, still working? Yup.
Remount /system r/w, then:
Code:
stop
mv whatever.ttf old.ttf
mv temp.ttf whatever.ttf
reboot
Renate NST said:
Well, apparently you are bashing some non-font thing.
How are you copying over the font?
Are you using some wonderful "Insta-Mega-File-Masher-Omatic"?
Which font are you replacing?
Stick to basics.
Get your Nook working with 1.2.1 since that is where you should be.
Get ADB working.
Remount /system r/w, adb reboot, still working? Yup.
Remount /system r/w, adb push your font to /system/fonts/temp.ttf, adb reboot, still working? Yup.
Remount /system r/w, then:
Code:
stop
mv whatever.ttf old.ttf
mv temp.ttf whatever.ttf
reboot
Click to expand...
Click to collapse
I am replacing Caecilia, HelveticaNeue and Trebuchet.... i using adb push to replace the fonts .. i use these commands
adb shell
#su
#mount -o rw,remount /dev/block/mmcblk0p5 /system
adb push myfont.tff /system/fonts
adb reboot
sometimes, every fonts is replaced properly... and everything is alright.. sometimes, replacing the 3rd font and i reboot .. i gets locked.. sometimes it's the 2nd font, it's random.. or sometimes i push an app to system/app.. everything is alright... then i push the same app, it does not boot.. it's all random
how do you activate adb while booting... adb does not detect my nook while booting...
A comment; I have done some playing around with fonts over a year ago and if I recall correctly, the system needs fonts files with names Caecilia, HelveticaNeue and Trebuchet. You can rename other font files to have those names, but those names must exist.
Next, a question; Is it possible that the font files you are attempting to use are so big that they are filling up the file system?
Filling up the partition was one thing I thought of, but since /system is normally ro that didn't seem like it could affect anything.
Do a df and see what space you have left.
How big are the files?
If you are trying to make this do Chinese, just replace one file.
Linux doesn't use fonts.
Android only uses the Droid fonts.
Opera Mobile will use DroidSansFallback.ttf
ReaderRMSDK.apk uses the rest of the fonts.
Hello Everyone. I bricked my device and need the following files to fix that. Please, can someone with a rooted device provide this files?
Thanks much:
/system/framework/services.odex
/system/app/DownloadProvider.apk
/system/app/DownloadProvider.odex
/system/app/DownloadProviderUi.apk
/system/app/DownloadProviderUi.odex
Thanks again
MarcoJoo said:
Hello Everyone. I bricked my device and need the following files to fix that. Please, can someone with a rooted device provide this files?
Thanks much:
/system/framework/services.odex
/system/app/DownloadProvider.apk
/system/app/DownloadProvider.odex
/system/app/DownloadProviderUi.apk
/system/app/DownloadProviderUi.odex
Thanks again
Click to expand...
Click to collapse
hey don't feel bad I need boot img and system img to get my running again....or I just need to pop it in the microwave and call amazon and ask for a new one and start over
My Kindle is alive. If someone need this files too, they can be found in the Update.bin at Amazons website.
@crzyjoker13. Good luck with your device.
Here you go, pulled straight from the latest update...
It's just the files you requested, the file structure should be correct.
crzyjoker13 said:
hey don't feel bad I need boot img and system img to get my running again....or I just need to pop it in the microwave and call amazon and ask for a new one and start over
Click to expand...
Click to collapse
You can get them from Amazon's website. That's your best bet at this time.
really lost
NighthawkXL said:
Here you go, pulled straight from the latest update...
It's just the files you requested, the file structure should be correct.
Click to expand...
Click to collapse
ok this is a start but how do I get them to /system/app
crzyjoker13 said:
ok this is a start but how do I get them to /system/app
Click to expand...
Click to collapse
Your need to get the device to be picked up by ADB and then push the files if your not able to boot into the actual system itself. Your have to ask someone else for the commands... but here's a snippet for services.odex the rest the files should be similar pieces of commands.
Code:
adb shell
su
mount -o rw,remount /system
chmod 777 /system/framework
exit
exit
adb push services.odex /system/framework
adb reboot
step in the right direction
NighthawkXL said:
Your need to get the device to be picked up by ADB and then push the files if your not able to boot into the actual system itself. Your have to ask someone else for the commands... but here's a snippet for services.odex the rest the files should be similar pieces of commands.
Code:
adb shell
su
mount -o rw,remount /system
chmod 777 /system/framework
exit
exit
adb push services.odex /system/framework
adb reboot
Click to expand...
Click to collapse
well hey this is a step in the right direction but all I need now Is to gain read write acess to /system and system/app abd I should bea able to push the old files back...my problem lies in the fact that es explorer tried to update and it messed up so I went to remove and just install the new version at the same time I was following the directions to put play market on the dev so now I can download and I have no file explorer
or if anyone know how I can push and execute an apk to the kindle I would be happy
thanks in advance
crzyjoker13 said:
well hey this is a step in the right direction but all I need now Is to gain read write acess to /system and system/app abd I should bea able to push the old files back...my problem lies in the fact that es explorer tried to update and it messed up so I went to remove and just install the new version at the same time I was following the directions to put play market on the dev so now I can download and I have no file explorer
or if anyone know how I can push and execute an apk to the kindle I would be happy
thanks in advance
Click to expand...
Click to collapse
I was having the same problem as you are and was able to fix it by doing the following.
Download and extract the files NighthawkXL has provided.
From within the folder that you saved the files run command and do the following
adb shell
su
mount -o rw,remount /system
chmod 777 /system/framework
exit
exit
adb push services.odex /system/framework
adb push DownloadProvider.odex /system/framework
adb push DownloadProviderUi.odex /system/framework
exit
adb shell
su
mount -o rw,remount /system
chmod 777 /system/app
exit
exit
adb push DownloadProvider.apk /system/app
adb push DownloadProviderUi.apk /system/app
adb reboot
I think this will solve your problem with the downloads not working. Please keep in mind I have small amount of knowledge when it comes to rooting, but figured that it couldn't do more damage to it since it wasn't working.
LinearEquation said:
You can get them from Amazon's website. That's your best bet at this time.
Click to expand...
Click to collapse
can you provide a link to the system images please
thanks cant seem to find them
davethebrave14 said:
can you provide a link to the system images please
thanks cant seem to find them
Click to expand...
Click to collapse
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
Just downloaded .bin gonna check this out also. I didn't brick mine its usable but I screwed it up trying to take things off to get more memory and easier on battery. Runs ok now but I took off the system keyboard thinking the android keyboard file would be it the asop or whatever. So had to add Google keyboard which is better and the main navigation is gone with the back and menu key. ROFL. Using all in one gestures and omega status bar as a rig lmao.
adb install package.apk works fine after adb start-server with linux.
Theres app in 1 mobile market for moving .apk to /system/app folder.