Today I was digging DEEP DEEP into my kindle's files one last time and found two things of interest. A debugging filesystem (named dfs) and a debugging kernel (named dkernel). I decided to install the kernel for lulz and I unpacked the filesystem. The surprising part is that it's not even android! I am currently unable to do anything with these files besides basic stuff. If you are in desperate need of these files or just want to screw around, check them out at http://db.tt/aNINJAB9. Also, Amazon was kind enough to hide a screenshot in there!
I used Flashify to flash the debug kernel. I'm not sure if you can do it other ways due to it's size.
Amazon's Lovely Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Amazon Kindle Fire HD using xda app-developers app
The link says ninja. O.O Lol.
I will also be willing to help someone get the KFHD8.9" version if they are willing to pm me.
Sent from my Amazon Kindle Fire HD using xda app-developers app
DFS has been around since the first generation of KFs and is really of no use to the end user because all it does is test the hardware. There are dfs and dkernel partitions on each of the KFs.
On each of my original KFs, I removed those partitions and reclaimed ~200MB of unused storage space, plus another ~100MB by removing various other unused partitions. I'm sure you could do the same on the 2nd generation KFs, but I'm not sure of how the offsetted partitions will affect Hashcode's "stack" file, and I'm not quite brave enough to put it to the test...yet.
I've done some more digging and there are some references to the "/dfs" directory in various files I took from the dfs partition so if we got it mounted there and used the debugging kernel, we might be able to get the testing part up and running! But I think the dfs mount would need to persist through boot. And I take back what I said that it wasn't android. It needs to be mounted along with the system partition. I believe the original kf's were different.
Sent from my Amazon Kindle Fire HD using xda app-developers app
I must have misunderstood you. For some reason, I could have swore you said that you booted into it using fireflash. I guess I'm going crazy.
Anyway, if you had a bootloader that was capable of choosing the dkernel and dfs to boot, it would surely be functional. Of course, that's not really an option on the 2nd gen KFs.
soupmagnet said:
I must have misunderstood you. For some reason, I could have swore you said that you booted into it using fireflash. I guess I'm going crazy.
Anyway, if you had a bootloader that was capable of choosing the dkernel and dfs to boot, it would surely be functional. Of course, that's not really an option on the 2nd gen KFs.
Click to expand...
Click to collapse
I use the dkernel. It always runs at 1.2GHz and has some weird init.d scripts. I'm trying to figure out the dfs thing, though. Maybe tomorrow. Too tired tonight.
I included the dkernel in the zip file.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Disregard my previous post. The debugging kernel itself didn't enable the development init.d scripts. It was the "ello_guvna" command from the dfs. I didn't let the command run too long, so I think there might be more when you run the command.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Related
So are the no other ways to partition the KF internal storage without being on a custom ROM? Got hit with a message today, see image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Learned GNU and went old school.
Sent from my Kindle Fire using xda premium
xolanir said:
So are the no other ways to partition the KF internal storage without being on a custom ROM? Got hit with a message today, see image.View attachment 960608
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
no -- you cannot partition in any mode but recovery. So therefore you can either 1. do it with the recovery or 2. adb shell (in recovery) and use Parted
http://www.gnu.org/software/parted/manual/html_mono/parted.html
http://luv.asn.au/overheads/parted/index.html
except you would go..
adb shell
~ # parted dev/block/mmcblk0
which starts off the Parted program
and then ... I played around a bit.
Just bacl up your data and print your tables each step of the way so you know what you started off with....
androidcues said:
no -- you cannot partition in any mode but recovery. So therefore you can either 1. do it with the recovery or 2. adb shell (in recovery) and use Parted
http://www.gnu.org/software/parted/manual/html_mono/parted.html
http://luv.asn.au/overheads/parted/index.html
except you would go..
adb shell
~ # parted dev/block/mmcblk0
which starts off the Parted program
and then ... I played around a bit.
Just bacl up your data and print your tables each step of the way so you know what you started off with....
Click to expand...
Click to collapse
This looks to be a very difficult process in the hands of a noob. Gonna need to do more reading up before attempting. Thx for the tip.
Sent from my Kindle Fire using xda premium
xolanir said:
This looks to be a very difficult process in the hands of a noob. Gonna need to do more reading up before attempting. Thx for the tip.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I would not suggest playing with the internal storage of the kindle if you are not completely comfortable with adb and how partitioning works.
What ever happened with fireparted? Did the dev take it down cos of issues people are having with repartitioning the KF? As of now, are there no other alternative methods to get the work done? Thx
sent from my CommandCenter
Ok, so I know for the Nexus S the mount point for /boot is:
/dev/block/mtdblock2
But that's only from looking at BM's rom wiper tool. I tried running "mount" under terminal emulator, but it doesn't list the /boot mount point.
I'm hoping to find the mount point on a kindle fire is why I ask. The cyanogen fastboot wiki mentions that it's mtdblock2, but I don't know if this is the case for all android devices.
Any help is appreciated, thanks!
EDIT - spoke to one dev and he said that /boot and /system should never be wiped. Now I'm confused, maybe it's differences due to it being a different device?
Have you tried to ask the question in kindle fire forum?
Sent from my Nexus S 4G using xda premium
shabgard said:
Have you tried to ask the question in kindle fire forum?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
This question isn't really device specific. The reason I haven't asked it there just yet is because there are more devs floating around in the NS forums.
That and the community there is different. Every other thread is a "bricked" thread, where it seems that a lot of users have no idea what fastboot or adb is. =p
"df" doesn't list it for me, so i doubt it is. However, if you do a fresh boot and type in "dmesg" it'll tell you where it's located right up the top (at least on the Nexus S).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Damn it looks different on the KF:
I'm not sure if that's what I need. I don't know if boot partition 2 = /dev/block/mtdblock2.
Ahh, I'm a super newb at this too.
Thanks for the help though.
Never done (or needed to do) any work with locations like this, especially with android. Sorry i can't help further, but maybe someone else around here can shed some more light for you.
Harbb said:
"df" doesn't list it for me, so i doubt it is. However, if you do a fresh boot and type in "dmesg" it'll tell you where it's located right up the top (at least on the Nexus S).
Click to expand...
Click to collapse
/factory doesn't show with df either, although it shows on GN I think...
Sent from my ice cream powered Nexus S
mount won't show the boot partition, because it's not mounted to the file system afaik.
Try
Code:
cat /proc/mtd
On the NS, it is mtd2, aka /dev/mtd/mtd2.
Boot is where the kernel and ramdisk are stored. If you erase boot, your phone will not boot (go figure).
Then I'm confused, what does the format/ boot function in CWM actually wipe?
erikikaz said:
Then I'm confused, what does the format/ boot function in CWM actually wipe?
Click to expand...
Click to collapse
The kernel
Sent from my ice cream powered Nexus S
DarkhShadow said:
The kernel
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
OH! Shoot, so is there any way to manually wipe that?
the kernel is in the boot.img
This CWM script will reodex any custom ROM.
With BOOTCLASSPATH edit in dexo.sh it can work on any ROM and phone.
Reodexing gives some people perceivable speed up. And it frees data partition from system dalvik cache. So dalvik-cache rebuild is also accelerated.
I ran it with stock kernel (root injected). And had problems with running it on any custom kernel.
http://galaxytree.net/bravomail/universalOdex.zip
Also a good example of output from shell script into CWM console.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great to see new tweaks. For me, flashing this mod went well, but it put me in an endless boot loop. I'm using a Cappy with a Jelly Bean custom rom. I know it's supposed to be "universal", but maybe some ROMs are not compatible. Any suggestions? Hope I can get it to work.
Using the android sdk you will want to try DDMS.bat and see what spew you get while the phone boot loops.
Sounds similar to what I used for all my roms.
Here are some tips I've picked up along my dev experience:
1. Make sure you have at least 50+ mb space free in /system. Else it may not complete and your /system/app and /system/framework folders may not work properly, thus causing many android core processes to force close and rendering your device unusable. If this happens, wipe, reinstall the rom, and delete more things using Root Explorer from /system. Such as unnecessary ringtones/notification sounds in /system/media and unnecessary system apps like *WallpaperChoosers.apk, stock launchers if you aren't using them, and other stuff you don't need. If you aren't sure what it is, don't delete it because it might be important for the use of your phone.
2. Also, it doesn't work on some roms, I'm not exactly sure why. But make sure you read the script's logs to ensure there are no errors. If you are getting mounting errors, make sure your phones /system partition is mounted as r/w (root explorer can do this). If it still doesn't work, try rebooting into recovery and mounting /system in mounts and storage and then try running the script.
3. Just because your phone is now odexed doesn't mean its gonna be a ton faster. In my experience, I found it to be a slight improvement from the original. In most cases it was unnoticable, so don't expect too much.
Cheers!
Sent from my SGH-I897 using xda app-developers app
Holy cow amigo. You started a bunch of threads. A little credit to original author would have been nice if you took the work and revamped it. All credit cause you didn't.
Sharing is caring. But I suggest you put where you got the script, etc, as well as the original author.
edit. upon further review, i see that you did change some things, mainly removing the original header (which is absolutely lame) and made it work with CWM. Also, you set a static BOOTCLASSPATH - which defeats the purpose of this script!!
Let me check my pms and emails. Someone contacted me a long time ago asking me review to their changes. Maybe it was you lol.
Sent from my EVO using Tapatalk 2
Hi guys. I just connected the tablet to my PC to copy some files, my PC got stuck for a moment and the second time I connected it, I realized the Nexus 7 storage was completely formatted. The only folder left is "Android". No idea how this happened.
Do you have any suggestions how can I recover my files back? Please help me, I had some really important stuff there. :crying: Thanks
All files are there, just hidden and marked as over writeable. Google recover deleted items. Point whatever tool you find to the nexus and it should get them all back.
Sent from my HTC One using XDA Premium HD app
OllieArmageddon said:
All files are there, just hidden and marked as over writeable. Google recover deleted items. Point whatever tool you find to the nexus and it should get them all back.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
That is very optimistic! Could you tell me please how can I make Win7 recognize the device as a flash usb drive because this is how it recognizes it now (in the capture below) and recovery programs does not support such "drives". I have set is as MTP Media Device. Thank you, man!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you not mount it as USB in recovery? Not too sure as I have a stock N7.
Sent from my HTC One using XDA Premium HD app
I tried to boot into recovery mode but the screen says "No Command". Win 7 does not recognize the device either. Mine is stock, not rooted.
P.S. I am a complete rookie with android, you can PM if you prefer please.
Sn00ky said:
I tried to boot into recovery mode but the screen says "No Command". Win 7 does not recognize the device either. Mine is stock, not rooted.
P.S. I am a complete rookie with android, you can PM if you prefer please.
Click to expand...
Click to collapse
When you click on Nexus 7 what do you get on the computer screen?
Sent from my Nexus 7 using xda premium
You will not be able to mount USB via the stock recovery. You will need CWM or TWRP. When in the OS you only have the option for MTP mounting. I don't know of any way to mount mass storage in the OS.
Sent from my SPH-D710 using xda premium
Okay, so here's a quick recent ROM history of my G2 (VS980).
I was on SlimKat for a little while, then switched to build 2014/07/09 of CyanogenMod, and just now I updated CM to build 2014/07/16.
So I backed up my ROM and apps and whatnot in TWRP, then did the default wipe, then flashed the latest CM nightly + Gapps. When I rebooted into the ROM, everything was still there. All of my apps were still there. My processor settings were still there. My lockscreen was still there. It was as if I never wiped then flashed a new ROM.
I went into the settings and it says that it's still on build 2014/07/09.
So can somebody tell me what's going on?
(Here's a picture of TWRP after I flashed the ROM + Gapps. Sorry for the crappy quality. I had to take it with my 3DS camera, since that's the only other camera I had lying around.)
(TWRP version 2.6.3.3)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In case you can't read the text in the image, here's what it says (in order):
E: Unknown File System 'datamedia'
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Updating partition details
Simulating actions
Simulating actions
Updating partition details
Check in twrp under advanced options (i think) and make sure "simulate operations to test theming" or some thing very close to that is not checked.
Sent from my LG-D800 using XDA Premium 4 mobile app
helioXverse said:
Check in twrp under advanced options (i think) and make sure "simulate operations to test theming" or some thing very close to that is not checked.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, I'll try that. I've never had to do this before though, so just a bit confused. What does it even do anyways?
It basically runs commands with out actually changing anything so people who theme twrp can make sure the theme works 100%. I've checked it by mistake more than once when setting up recovery.
*Edit its actually under "settings". Its the last box on the list, on 2.7.0.0 anyway. I checked it just to test and get the same message as you. I hope this fixes the problem.
Sent from my LG-D800 using XDA Premium 4 mobile app
helioXverse said:
It basically runs commands with out actually changing anything so people who theme twrp can make sure the theme works 100%. I've checked it by mistake more than once when setting up recovery.
*Edit its actually under "settings". Its the last box on the list, on 2.7.0.0 anyway. I checked it just to test and get the same message as you. I hope this fixes the problem.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found it in v2.6.3.3, so it's all good. Thanks for the help, and I'll see if this fixes my problem.
EDIT: It did.