Hello, anyone knows that how to change the screen after powering off? It always shows "NOOK" and I don't find any related picture in system files. Thank you.
You don't need to turn it right off, just tap the power button once and it'll show wallpapers
yohoc said:
Hello, anyone knows that how to change the screen after powering off? It always shows "NOOK" and I don't find any related picture in system files. Thank you.
Click to expand...
Click to collapse
The boot/charging images can be found on the loader partition (/dev/block/mmcblk0p1) (vfat)
They are all 800x600 pgm files
Code:
#ls -l *.pgm
-rwxrwxrwx root root 480038 2011-05-26 04:05 black.pgm
-rwxrwxrwx root root 480054 2011-09-04 15:58 booting.pgm
-rwxrwxrwx root root 480054 2011-09-04 15:58 charging0.pgm
-rwxrwxrwx root root 480054 2011-09-04 15:58 charging1.pgm
-rwxrwxrwx root root 480054 2011-09-04 15:58 charging2.pgm
-rwxrwxrwx root root 480054 2011-09-04 15:58 charging3.pgm
-rwxrwxrwx root root 480054 2011-09-04 15:58 dead.pgm
-rwxrwxrwx root root 480054 2011-05-26 04:05 pic.pgm
-rwxrwxrwx root root 480054 2011-05-26 04:05 white.pgm
The power off image is probably a little trickier as it's displayed after the Android shutdown sequence has been started. Chances are it's packed into a jar and displayed as part of the shutdown context or it's compiled into the kernel.
[Temporarily removed to sort out a few bugs]
haha.. Your image is funny.Thank you for reply,and hoping you can post the steps soon.
BTW,I can't find pgm files in /dev/block/mmcblk0p1...
Well, I ran into some issues with my custom resource file, so while the custom image did work it made some other resources go out of sync with the B&N apps.
I'll look into it a little later today just for the fun of it
You need to mount that partition:
Code:
mkdir /data/local/tmp/mnt
mount -o rw -t vfat /dev/block/mmcblk0p1 /data/local/tmp/mnt
ls -l /data/local/tmp/mnt
-rwxrwxrwx root root 160768 2011-09-23 11:55 u-boot.bin
-rwxrwxrwx root root 92707 2011-09-23 11:55 wvf.bin
-rwxrwxrwx root root 480054 2011-09-23 11:55 dead.pgm
-rwxrwxrwx root root 480054 2011-09-23 11:55 charging1.pgm
-rwxrwxrwx root root 27 2011-09-23 11:55 cfg.bin
-rwxrwxrwx root root 480054 2011-09-23 11:55 charging3.pgm
-rwxrwxrwx root root 243735 2011-09-23 11:55 romrestore.zip
-rwxrwxrwx root root 480054 2011-09-23 11:55 charging2.pgm
-rwxrwxrwx root root 1839824 2011-09-23 11:55 uImage
-rwxrwxrwx root root 185029 2011-09-04 18:25 uRamdisk
-rwxrwxrwx root root 480038 2011-05-26 04:05 black.pgm
-rwxrwxrwx root root 16004 2011-09-23 11:55 mlo
-rwxrwxrwx root root 20480 2011-09-23 11:55 flash_spl.bin
-rwxrwxrwx root root 480054 2011-05-26 04:05 white.pgm
-rwxrwxrwx root root 480054 2011-09-23 11:55 charging0.pgm
-rwxrwxrwx root root 480054 2011-09-23 11:55 booting.pgm
-rwxrwxrwx root root 1508577 2011-09-23 11:55 uRecRam
-rwxrwxrwx root root 1839824 2011-09-23 11:55 uRecImg
-rwxrwxrwx root root 480054 2011-05-26 04:05 pic.pgm
Edit:
Keep in mind this is your boot partition, proceed with caution!
Oh,I see.I succesfully find the pgm files with the command you post :"mount -o rw -t vfat /dev/block/mmcblk0p1 /data/local/tmp/mnt"
And as you say,the power off image is not there,if it's compiled into the kernel I think it may be difficult for me to modify it.
yohoc said:
Oh,I see.I succesfully find the pgm files with the command you post :"mount -o rw -t vfat /dev/block/mmcblk0p1 /data/local/tmp/mnt"
And as you say,the power off image is not there,if it's compiled into the kernel I think it may be difficult for me to modify it.
Click to expand...
Click to collapse
Edit: See my post below.
hi all,
i found a simple way to customize shutdown image.
I modified the class where the shutdown image is set. With my mod, if an image called "shutdown.png" is found within folder "screensavers" of Nook, this image is used; otherwise the default image is used.
To enable this mod, you just need to update framework.jar and reboot the Nook. Of course you need a rooted Nook.
WARNING: as usual, modifying system files you may risk to brick your Nook, unless you know what you are doing. You are strongly advised to make a full backup before proceeding. I don't take any responsibility if you decide to apply this mod.
WARNING-2: i extracted my framework.jar file directly from my Nook, that has firmware version 1.0. Therefore you should not proceed if yoour Nook has firmware 1.0.1 (possibly having a different firmware.jar; i'm not sure). If you want, i could apply the same mod also to 1.0.1, just let me know. Now it's also available the framework.jar for firmware version 1.0.1
USAGE:
download one of the attached framework.jar based on your firmware version
rename it framework.jar
(optional) make backup of current framework.jar, for future usage
Code:
adb pull /system/framework.jar original-framework.jar
remount system partition r/w
Code:
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
push the downloaded framework.jar file to Nook
Code:
adb push framework.jar /system/framework
change the permissions of framework.jar file
Code:
adb shell chmod 644 /system/framework/framework.jar
reboot your Nook
Code:
adb reboot
Now, you can put any image you want (of course, best results are obtained using 800x600 image, 256 colors) into "screensavers" folder of the drive unit of the Nook (i.e. the drive used to sideload books), renaming it "shutdown.png" (please use the correct case, being the Nook case sensitive): this image will be used as shutdown image. In case the image is not present, the default one will be used (cold_boot_screen.jpg, attached to this message as reference).
The same mechanism is valid for the image displayed when the Nook shut down automatically for low battery level: in this case, you should put an image called "shutdownLowBattery.png" into the folder "screensavers". In case the image is not present, the default one will be used (cold_battery_low_boot_screen.jpg, attached to this message as reference).
I also attach 2 nice images that could be used as shutdown image.
For developers: the only class modified in framework.jar is ShutdownThread.
Hope this is useful,
regards
Thanks traycold，I'll try it.
[DISCLAIMER]: I'm not responsible for whatever happens to your Nook2, what worked for me might not work so well for you.
Ok, with that out of the way, here's a simple way to theme your N2:
[NOTE]: Only tested on 1.0.1 rooted with noogie + uRamdisk (Not touchnootered!)
[Updated Note]: Do not attempt to do this with rootexplorer or similar tools, use adb only! - Thx dorino1
Code:
adb pull /system/framework/framework-res.apk
IMPORTANT: Make copy of this file and store it somewhere safe before doing anything else!
Open the apk with 7zip and replace whatever images you want in res\drawable-mdpi\ then close 7zip
Code:
adb shell
# mount -o remount,rw -t ext2 /dev/block/mmcblk0p5 /system
# exit
adb push framework-res.apk /system/framework/
adb reboot
That's it
If your N2 starts acting strange then just adb push that copy you made of framework-res.apk (you did remember to make a copy yes?)
[Updated Note]: If you do end up in a mess (bootloop, messed up graphics, etc) you can restore your Nook Touch with nookRestore
thanks，ros87 and traycold allso mentioned an easy way to modify it.
hi traycold,I have changed my power off image succesfully with your framework.jar.Can you apply the mod to 1.01? Some of my friends may need it,thank you~
yohoc said:
thanks，ros87 and traycold allso mentioned an easy way to modify it.
Click to expand...
Click to collapse
Well modifying classes in framework.jar is not really "easy", as it requires you to disassemble the classes.dex with baksmali and know your way around in the resulting format..
But ofc, when someone provide you with a prepatched package it's easy
With the framework-res method you can do this yourself and also change a load of other graphical elements of your Nook UI, see attached pic
yohoc said:
hi traycold,I have changed my power off image succesfully with your framework.jar.Can you apply the mod to 1.01? Some of my friends may need it,thank you~
Click to expand...
Click to collapse
done! you can find it here.
(i used the framework.jar extracted from the manual update zip of 1.0.1 available at B&N)
ros87 said:
Well modifying classes in framework.jar is not really "easy", as it requires you to disassemble the classes.dex with baksmali and know your way around in the resulting format..
But ofc, when someone provide you with a prepatched package it's easy
Click to expand...
Click to collapse
actaully, with my mod there is no really need to disassemble anything: you just update the framework.jar with the one that you can download on this thread (the same way you would do for file framework-res.apk following your method), and you're done. Then you just need to copy the shutdown image on a given folder of your Nook usb connected to your PC, as you would do for any sideloaded book.
Another advantage is that you don't need to pack and update framework-res.apk any time you want to change shutdown image (or revert to default).
On the other end, it's true that you can modify other graphical elements, with your method.
Regards
PS: on a different subject, an indeed really useful mod would be to allow landscape orientation on default epub reader; at the moment i'm working to a mod allowing custom fonts (but not yet sure it would be possible)
traycold said:
actaully, with my mod there is no really need to disassemble anything: you just update the framework.jar with the one that you can download on this thread
Click to expand...
Click to collapse
I wasn't trying to disrespect your work mate, and I did say it was easy when someone is providing the jar, but in the end it still requires someone skilled in the art (that would be you) to create it trough disassembling and patching
The framework-res method can be done by anyone with enough skills to use photoshop and 7zip.
traycold said:
PS: on a different subject, an indeed really useful mod would be to allow landscape orientation on default epub reader; at the moment i'm working to a mod allowing custom fonts (but not yet sure it would be possible)
Click to expand...
Click to collapse
I'm pretty sure you'd receive a lot of love if you came up with a mod for landscape
ros87 said:
I wasn't trying to disrespect your work mate, and I did say it was easy when someone is providing the jar, but in the end it still requires someone skilled in the art (that would be you) to create it trough disassembling and patching
The framework-res method can be done by anyone with enough skills to use photoshop and 7zip.
Click to expand...
Click to collapse
got your point!
Thanks for your work. Also I'm looking forward to using custom fonts,because I'm a Chinese user and using Chinese fonts is a little complicated now.It makes me replace the original fonts with Chinese fonts or modify CSS in epub files.
Could something like this lead to displaying the current book's cover as the screensaver?
madigan82 said:
Could something like this lead to displaying the current book's cover as the screensaver?
Click to expand...
Click to collapse
Give a look here!
Related
Hi Everyone,
I noticed to today that there are multiple application for 1-click root for some android phone like Droid X, Samaung Galaxy S, Nexus One, ...
Is there any application that roots the mentions phone can root Samsung Galaxy Spica GT-I5700 ?
Regards
Get Odin and the latest lk. Not as simple as one click, but it should not take more than five minutes.
Pr0fess0rX said:
Hi Everyone,
I noticed to today that there are multiple application for 1-click root for some android phone like Droid X, Samaung Galaxy S, Nexus One, ...
Is there any application that roots the mentions phone can root Samsung Galaxy Spica GT-I5700 ?
Regards
Click to expand...
Click to collapse
rooting with ODIN it's so easy, just input the file (kernel from samdroid v.LK2.08) and click start,
just one minutes your spica now is under root
Instructions
Sorry im a total noob. Can anyone link to descriptive instructions to root the Spica? I sooo scared..
i did it yesterday, not as hard as i though. just search "i5700 flashing" in youtube and you should find ~8min video.
2black0 said:
rooting with ODIN it's so easy, just input the file (kernel from samdroid v.LK2.08) and click start,
just one minutes your spica now is under root
Click to expand...
Click to collapse
Hi Friends, I found out an eassy way of rooting but before you start format your card with FAT32 and follow instructions as mentioned here -
http://www.addictivetips.com/mobile/root-samsung-galaxy-spica-i5700-with-leshaks-kernel/
Guys I did it already, With Odin is so wasy, I was just asking if there is a way more easier.
Thank you
Z4root is now available for spica.
z4root
z4 root working for spica go at this link
http://forum.xda-developers.com/showthread.php?t=833953
i have done it successfully both mode working temporary and permenant
z4root not work superuser...
Pr0fess0rX said:
Guys I did it already, With Odin is so wasy, I was just asking if there is a way more easier.
Thank you
Click to expand...
Click to collapse
Z4root is not a full root for spica or any other phone.
to get it follow these steps
Enjoy
Not fully one click but almost there
Install z4root 1.3.0.apk.
Install any terminal emulator apk.
Do the permanent root to get the superuser apk and su binaries installed.
(the permanent root does not work because the rfs filesystem used by the spica does not support the suid bit)
Then do a temporary root. (z4root creates a tmpfs filesystem which supports the suid bit).
Launch the terminal emulator.
Get root by typing su at the $ prompt. The superuser apk should ask for permissions. Allow the terminal.
The prompt should change to #.
Type dmesg > /sdcard/dmesg.txt
This should dump the boot logging output to dmesg.txt. Connect your phone to the PC or eject the sdcard and open dmesg.txt in any editor.
Search the log file for cannot find.
In my case it was
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
The important part is the "/system/etc" and the ".sh".
For some reason spica allows editing in the /system/etc directory which remains after reboots. Any edits to / do not remain after reboots.
If you dont have a cannot find error by init generated by a script in /system/etc then youre out of luck. The only way out is to run z4root and get a temporary root everytime (although it kind of makes the phone a bit unstable after the temporary root).
Then type
mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
(wonder why this works, cos my device shows /system mounted as /dev/stl6. anyways it works)
Change directory to the system folder by typing
cd /system/sbin
Create a symbolic link to /xbin/su in /system/sbin. Do this because typically in the path variable /system/sbin comes before /system/bin (where z4root dumps the su binary). The suid bit is not set after reboot in the /system/bin/su so it dosent work.
ln -s /xbin/su /system/sbin/su
Have script prepared on your PC with the following lines:
#!/system/bin/sh
mkdir /xbin
mount -t tmpfs -o size=100k tmpfs /xbin
cat /system/bin/su > /xbin/su
chmod 6755 /xbin/su
Save it to your sdcard as the missing sh. In my case it was install-recovery.sh.
Copy it from the sdcard to the /system/etc folder by typing
cat /sdcard/install-recovery.sh > /system/etc/install-recovery.sh
Thats it.
Reboot when your done.
On reboot init should read the init.rc file in /. Then it should execute install-recovery.sh. (Just make sure the install-recovery.sh or whatever script is marked as oneshot in the init.rc file)
install-recovery.sh should create a small tmpfs partiition, copy the su binary there and set the suid permissions creating a permanent root.
I try to root my spica with super one click, android sdk and no work but i find a way to update cupkake 1,5 to eclair 2.1 with odin and finaly i made it . Than i use lkmod 2.5 to root but i cant find the super user or any root explorer in the phone and i dont know if my phone is root-ed or not ... any idea...?
one click root is impossible on spica
the stock OS on spica i think it was android 2.1, the one click root kits (at least the few i tried) didnt work on androdi 2.1
As soon as i flashed a 2.2/2.3 rom i had no problem rooting using z4root for example.
Where I can find the PDA for odin...
murat1369 said:
z4root not work superuser...
Click to expand...
Click to collapse
where I can find PDA file for odin..
The cruz tablet has android 2.0, no market pre-installed. I'm attempting to load the market on to it by tracking down .apk files for the market (vending.apk?) I havent had any success with adb installing it. I can use adp for just about every thing else it seems. I'm very new at this thus far. Any suggestions?
Whenever i run adp install vending.apk i get an error failure [install_failed_older_sdk] any idea what this means? maybe the vending.psk is intended for newer versions of android? I've tried another vending.psk (supposidly for pre-froyo items and it gave me the error missing libraries)
Thoughts? Ideas? Thanks
your doing it wrong, first you have to have root, next you need to flash a gapps update. If you can't flash you can unzip the update and push the files to their right system directory using adb.
Sent from my HTC Vision using XDA App
my device is rooted, but I'm having a hard time finding the zip file on step 2 there, i have build eclair 2.0-r1.1
Interestingly enogh i still cant delete files or uninstall much, is this something related to CHMOD or similar?
(on second thought I access shell (#) through adb and i can delete at will. I'm learning quickly but still can't figure out the steps to throw the market on this thing. If anyone can help me with more of a step by step or point me somewhere, i would really like to add to the lackluster modding community for the cheap velocity
If i can just somehow package the marketplace in to a rom for this thing (i used to do roms for windows mobile) I think the device interest will grow
I actually made a bunch of progress the other night, ill share my progress tomorrow in detail but it went something like this:
boot with power and volume - (down)
then you can chmod the /etc/permissions. ( and other dies) - from what I could tell this was only way to change system partition to writable?
then you can copy xmls, jar, and install all. the apk's with adb
that's as far as I got, market would run, but never got any pages to show up or was able to login (if that was a feature in 2.0) I would be more interested in an upgrade to 2.1? (if that's even possible?)
Which market APK did you use?
I think? for a 2.1 we would have to take the source 2.1 and go from there, I have no clue how to do that or where to start but I would like to take a shot.
Ideas?
I am actually quite happy with what I have right now, I picked it up for 170 at best buy and have most of the apps I want (with the exception of angry birds ) The tablet has seemed to speed up as time has gone on and 2.1 would be great!
From the get go with this tablet you can adb shell and you get the # meaning rooted.
I used the Market APKs from some phone ROMs AOSP 2.4 release that I found on communityforum.com
Here are the steps (from my notes) that I used. Note the FAILED, but could be a good starting point for you: Keep in mind this is from my first 8 hours of trying to learn Android, my first ADB session, etc, I am NOT an expert at this, just dangerous given all the other information others have shared, most of this comes from other device/forums for people trying to install the android market. Got my starting point from a post that stated that to install Android Market you had to:
Install:
1) GoogleApps.apk
2) SetupWizard.apk
3) TalkProvider.apk
4) Vending.apk
5) GoogleCheckin.apk
6) gtalkservice.apk
and copy and locations below:
/system/etc/permissions/com.google.android.datamessaging.xml
/system/etc/permissions/com.google.android.gtalkservice.xml
/system/framework/com.google.android.gtalkservice.jar
/system/lib/libgtalk_jni.so
------------------------------------------------------------------
HERE IS AS FAR AS I GOT:
------------------------------------------------------------------
Power up and Vol - (together - not sure if this was necessary but for some reason I couldn't ADB SHELL in and make modifications originally - although it might have been a skill thing on my part)
ADB REMOUNT
ADB SHELL
CD /SYSTEM/ETC
ls -l shows: drwxr-xr-x root root 2010-12-15 15:40 permissions
chmod 775 permissions
ls -l shows: drwxrwxr-x root root 2010-12-15 15:40 permissions
exit
exit
adb push com.google.android.datamessaging.xml /system/etc/permissions
0 KB/s (829 bytes in 1.000s)
adb push com.google.android.gtalkservice.xml /system/etc/permissions
52 KB/s (832 bytes in 0.015s)
ADB SHELL
CD /system/etc/permissions
ls -l
-rw-r--r-- root root 1139 2010-11-05 15:38 required_hardware.xml
-rw-r--r-- root root 8188 2010-11-05 15:38 platform.xml
-rw-rw-rw- root root 829 2011-01-10 23:20 com.google.android.datamessaging.xml
-rw-rw-rw- root root 832 2011-01-10 23:20 com.google.android.gtalkservice.xml
cd ..
chmod 755 permissions
ls -l
drwxr-xr-x root root 2011-01-11 01:43 permissions
cd ..
ls -l
drwxr-xr-x root root 2010-12-15 15:41 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxr-xr-x root root 2010-12-15 15:40 framework
chmod 775 framework
chmod 775 lib
drwxrwxr-x root root 2010-12-15 15:41 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxrwxr-x root root 2010-12-15 15:40 framework
exit
adb push com.google.android.gtalkservice.jar /system/framework
1698 KB/s (27139 bytes in 0.015s)
adb push libgtalk_jni.so /system/lib
29 KB/s (9460 bytes in 0.312s)
ADB SHELL
cd /system/
chmod 755 lib
chmod 755 framework
drwxr-xr-x root root 2011-01-11 01:47 lib
drwxr-xr-x root root 2010-12-15 15:40 fonts
drwxr-xr-x root shell 2010-12-15 15:41 bin
drwxr-xr-x root root 2011-01-11 01:47 framework
exit
ADB INSTALL
SetupWizard.apk
GoogleApps.apk
TalkProvider.apk
REBOOT
vending.apk
gtalkservice.apk
GoogleCheckin.apk
GmailProvider.apk
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb install Gmail.apk
2472 KB/s (710975 bytes in 0.280s)
pkg: /data/local/tmp/Gmail.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
GoogleContactsSyncAdapter.apk (success)
GooglePartnerSetup.apk
GoogleSettingsProvider.apk
At some point during the APK install and a device reboot the devices comes to complete crap and you need to use the VelocityMicro.com Cruz firmware update.zip to 'restore' the device to it's original state - so I would suggest being careful with what I've done above because your likely to make your device extremely unstable. My GUESS is it's somewhere after the first three APK installs and the reboot (after the first reboot it comes back fine, all steps after that cause failure, reboot, GUI starts acting all funky, can't swipe to login, etc and it's done)
If I get a chance, I'll try to play with it some more tonight.
The Attached SUCCESS.ZIP contains the files from the AOSP2.4 download I used to get this far...
I cant seem to get mine in to the pre-boot enviornment
Anywho i did everything with the device on and completed. It seems stuck in a reboot loop, probably from the setup wizard i'm assuming? Have you tried not installing as many apk's? Maybe something is trying to run and causing it. Can it be done without the wizard?
I've created some scripts that install good apps that work well with the tablet thus far and a script that will auto-uninstall bloat shortcuts and programs that it ships with
If you take the update.zip from the velocitymicro.com website firmware update for the cruz, and load it (power and Vol +) it'll recover the system (can't say i didn't warn you!
It's something AFTER this step that screws it up.
ADB INSTALL
SetupWizard.apk
GoogleApps.apk
TalkProvider.apk
REBOOT
I found this today and am going to dig into it a bit more to play with it, to see if it leads somewhere:
http://www.slatedroid.com/velocity-...-vm-cruz-(testers-needed!)/msg63584/#msg63584
and this:
http://www.slatedroid.com/pandigita...ment/easy-market-hack-for-bpdn-e-reader-help/
might lead to something?
tried item at first link. the batch corrupted the rom and i had to run the update.zip again
yes i did have adb installed and set up. I've been trying something similar to this for a while, just the manual way
I was able to get some apps installed via the handango.com market. Select the T-mobile G1 and you can download/install gmail, google reader, gdocs, google apps, maps, etc but as of now none of them work.
discovered 'adb bugreport' which seems to show issues with installed app. just did a clean reinstall of update.zip and am going to start from scratch one app at a time to see if i can make any headway there instead of blindly installing a bunch of crap and hoping that it works.
when i enter
>adb shell
I keep getting "access denied"
any ideas what I may be doing wrong?
are you mounting the device first? 'adb remount' if you have multiple USB devices it maybe confused, make sure your mounting the right device.
tullywork said:
are you mounting the device first? 'adb remount' if you have multiple USB devices it maybe confused, make sure your mounting the right device.
Click to expand...
Click to collapse
My tablet is the only USB device attached to the pc. It is the T301
i get all the way to the android-sdk-windows\tools directory (there is more to the directory i just didn't type it all.
from there i try
>adb shell
>adb mount
>adb remount
and each time I get 'access denied'
I've been hoping activity would pick up for modding the Velocity Micro Cruz Tablet T100 series. Glad to see good old XDA has taken a bite as I've been following the Cruz Tablet on Slatedroid which recently split the Cruz into Reader and Tablet forums.
I've been playing with the Android SDK and ADB under Lubuntu Linux. http://www.slatedroid.com/index.php?topic=14771.0 I have a system.img that someone in the cloud created that has the Market but it doesn't have access to protected apps. I used a modified build.prop with a ro.build.fingeprint... for another device and can get a more complete Market with access to protected apps. From there I am able to install apps from the Market with the AVD and move them to Cruz Tablet for installation.
But I haven't had success connecting to the Cruz using ADB under Linux. I have not located the USB device id for the Cruz Tablet. The ADB devices command shows the AVD fine but the Cruz shows up with question marks. Windows and Macs just work but Linux requires a USD device ID. If anyone knows the ID for the Cruz Tablet T100 series please post.
:8
I think my tablet is going back to best buy tomorrow. 170 was a great deal but too many issues with it. I wasnt really impressed with the battery life and nothing over android 2.0 is a major bummer. I need my tether! RIP Cruz
Agreed. I actually returned mine last week. The biggest killer was no Android Market or Google Apps. Had it at LEAST had Google Apps, I would have kept it, shame because the look/feel/etc was nice and I thought it had promise, but limited Apps obviously made it a brick (to me). I kept my Viewsonic GTablet, lots more work on the black market for that device, so it suits my needs (although I'm not a huge fan of the long 10" form factor, something closer to 8 or 9 inch and a 4:3 ratio seems to be my personal preference, definitely looking forward to checking out the Xoom.
I think mine is going back as well. Lack of Market is a killer. I can't even use appslib.
I've been trying to fix my kindle fire for a while now. My ultimate problem is that my build.prop is not in my /system/ but I have been trying to push a replacement build.prop to that directory to no avail. It looks like I have superuser installed. Superuser.apk is in system/app/ and there are a few SU directories around my file system.
My problem is that even though I have SU in my file system, I am not getting the correct permissions when accessing the KF through adb. Whenever I type in su it says permission denied. Similarly, whenever I try to change the permissions for /system/ I am denied as well. Whenever I type in su, it says "segementation fault".
It seems to me that there are three possibilities:
1. I somehow have the superuser files in place but the SU program itself is not installed.
2. SU is installed but because I can't fully boot up my KF, I can't give ADB Root access through SU because I can't pull up the "allow access" dialog box.
3. Something stupd like I"m trying the wrong commands.
Maybe your kindle auto updated and broke root? But if you've already updated and re-rooted I'm not sure what the issue would be.
Sent from my Nexus S 4G using XDA App
hmmm...I think a main thing I need to know for sure before I continue is if my phone is even rooted for sure. I have the superuser.apk in system/app. I don't have anything in data/local. I have a SU directory in a couple places. Is there any way for ADB to recognize if a phone is rooted (perhaps if the file system is set up a current way?) without having access to root priveledges itself?
Same here, BurritoRoot, I've tried this on both Linux/Mac, but either way, I can never get su to work so my Kindle can be r/w.
Maybe try
adb shell
$su
If $ changes to # you have root.
When installing su check the file permissions on the directory as well.
Sent from my Kindle Fire using Tapatalk
just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w
b63 said:
just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w
Click to expand...
Click to collapse
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.
Jessical said:
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.
Click to expand...
Click to collapse
that command only remounts the system partition r/w - not permanent !
but after issuing the comand:
you can copy files, change permission or whatever
you can also run kfu to permantly root with superuser
Fixxxxxxxxxx!
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue
taseedorf said:
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue
Click to expand...
Click to collapse
It just stalls at:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
downloading 'boot.img'...
Then nothing.
Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory
taseedorf said:
Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory
Click to expand...
Click to collapse
How would I do that? I downloaded twrp-blaze-2.0.0RC0.img
I have used the terminal in the past, even compiled stuff like Chrome OS, but I don't know anything except the stuff that people put in the instructions...
Where is the boot.img itself coming from?
hey guys I removed some systemapps and now I cant install the new row update. can some one please upload a titanium backup
thanks
titanium backup won't work for system apps. you will need a system dump. which apps do you need? i have a dump but i won't upload the whole dump cause its about 1 gb.
ok. thanks for the quick reply. im not sure but it sholud only be the music app. it would be great if you could upload it.
just unpack it and copy both files into the /system/app folder with i.e. rootexplorer etc.
here i uploaded nearly the whole dump:
System Dump
i am the same don't know how to do now.
---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------
@bananenlarry
I delete some app after root,then I unroot for some reason.
I can't not get root again,and also can not update OTA2 because missing APP.
waht can I do now?
@feskey
how did you unroot? did you delete superuser.apk from /system/app? then download Superuser from market again. because the su file from /system/xbin/ should still be there.
@bananenlarry
Unroot by following command.Su was clean up.
Instructions
1. Follow instructions to set up ADB.
2-Run "adb shell" from a command prompt.
3-In the ADB shell, type the following commands:
su
(this will cause a prompt to come up on the phone asking you to grant root permissions, accept this)
Then, back in ADB shell:
mount -o rw,remount /dev/block/system /system
rm /system/app/Superuser.apk
rm /system/xbin/su
rm /system/bin/su
omg you really unrooted your device thought you just deleted the superuser.apk. i don't know exactly how the root exploit works but as i know it uses a lenovo app to do so. if you also deleted that app, root isn't possible in your case. you will have to wait until there will be another method for rooting.
Hi! I don't know how it happened, I was customizing the screen buttons behaviour in ReLaunch settings and was very careful doing it. And it worked fine. But now I can't access ReLaunch settings menu when I tap on it, the screen flashes and goes back to previous screen(Relaunch file manager). The same thing happens when I tap on TestCenterService app; It was working fine before; don't know how to fix this; if someone could help please?
Use ADB and do a logcat.
That will tell you what is screwed up.
ReLaunch Settings menu disabled
Dexnet said:
... I can't access ReLaunch settings menu when I tap on it, the screen flashes and goes back to previous screen(Relaunch file manager). The same thing happens when I tap on TestCenterService app; It was working fine before...
Click to expand...
Click to collapse
Hi, I have the very same problem as mentioned: "Can't access ReLunch settings and TestCenterService". I tried a couple of things to fix it: e.g. I reinstalled ReLaunch v.1.3.8 and Nook Touch Mod Manager v.0.4.0 , I reset the button's functions to default, nothing helped...
Following Renate's advice, I used ADB and did a logcat. Unfortunately, I have no idea what is the reason. I would appreciate it very much to get some more help to understand what could happen and how to cure ReLaunch of my nook Simple Touch.... I attached the created logcat, and its alphabetically ordered version, too (logcat.7z).
Best regards, Balint.
(Budapest, Hungary)
Sorry, I don't see any unhandled intents or exceptions in your logcat.
It seems to mean that the problem is completely internal to the application.
I have no experience with this application.
ReLaunch Settings missing
Renate NST said:
Sorry, I don't see any unhandled intents or exceptions in your logcat.
It seems to mean that the problem is completely internal to the application.
I have no experience with this application.
Click to expand...
Click to collapse
Thank you very much for answernig so quick.
One more info, that yesterday I installed ADW.Launcher, and it has a Settings menu icon (I was happy).
However it neither works! Instead it returns a message, that no Settings apk is available in this device...
Have a nice week, best regards, Balint
bjuh said:
no Settings apk is available in this device...
Click to expand...
Click to collapse
Oh, well that is simple enough.
Do you see the Settings icon in the "application drawer"?
Does it do anything?
Can you ADB shell in and see:
Code:
# ls -l /system/app/Set*
-rw-rw-rw- root root 2084682 2012-12-22 13:04 Settings.apk
-rw-rw-rw- root root 39973 2012-12-22 13:04 SettingsProvider.apk
(Your dates, sizes and permissions could be different but you should see both.)
still nook settings...
Hi,
thank you again for your message.
I am still needed a little more help.
In the "application drawer" I do not have a Settings icon, instead on the ADW Config palette there is one. If I tap on it, it returns:
"Application is not installed on your phone"
All the files in my app dir have same rights like these:
-rw-r--r-- root root 1620660 2008-08-01 14:00 Settings.apk
-rw-r--r-- root root 34031 2008-08-01 14:00 SettingsProvider.apk
I tried to change, however I couldn't:
# pwd
/system/app
# chmod 666 Settings.apk
chmod 666 Settings.apk
Unable to chmod Settings.apk: Read-only file system
# cd ..
cd ..
# pwd
pwd
/system
# ls -l
ls -l
drwxr-xr-x root root 2000-01-01 05:39 lost+found
drwxr-xr-x root root 2000-01-01 05:39 etc
-rw-r--r-- root root 1248494 2008-08-01 14:00 recovery-from-boot.p
drwxr-xr-x root root 2014-07-04 00:44 app
drwxr-xr-x root root 2000-01-01 05:39 assets
drwxr-xr-x root shell 2014-07-04 00:25 bin
-rw-r--r-- root root 2279 2014-07-04 00:44 build.prop
...
(You might see, I am not a Lx expert, although I have some practice in C, LabVIEW, etc.)
Best regards, Balint
/system is normally mounted read-only
To modify anything you will have to remount it.
ADW "Settings" button does this:
Code:
I/ActivityManager( 1055): Starting activity: Intent { act=android.settings.SETTINGS flg=0x10200000 c
mp=com.android.settings/.Settings }
If you can't see Settings in the drawer then something is screwed up.
You should run a logcat and see what exactly the error is.
You can also try:
Code:
C:\>adb shell am start -n com.android.settings/.Settings
Nook settings
Renate NST said:
/system is normally mounted read-only
To modify anything you will have to remount it.
ADW "Settings" button does this:
Code:
I/ActivityManager( 1055): Starting activity: Intent { act=android.settings.SETTINGS flg=0x10200000 c
mp=com.android.settings/.Settings }
If you can't see Settings in the drawer then something is screwed up.
You should run a logcat and see what exactly the error is.
You can also try:
Code:
C:\>adb shell am start -n com.android.settings/.Settings
Click to expand...
Click to collapse
Dear Renate, thanks for all your help. Finally, I gave up fixing my Nook's system.
I re-installed my backed up system then rerouted it. Now everything works again normally.
Best regards, Balint (from Budapest, Hungary)
bjuh said:
Dear Renate, thanks for all your help. Finally, I gave up fixing my Nook's system.
I re-installed my backed up system then rerouted it. Now everything works again normally.
Best regards, Balint (from Budapest, Hungary)
Click to expand...
Click to collapse
I wonder what actually happened.