[Solved] Partitioning KF stock ROM? - Kindle Fire General

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

Related

How to find /boot mount point?

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

Mount external microSD card as USB mass storage for tab 7.7 CM10 (working)

This tutorial only work for microsd card only ,
for internal no solution yet.
i found thread [APP][v1.5beta (+US)] SGS3 Easy UMS - Mount external microSD card as USB mass storage by Kopfgeldjaeger
1. download latest SGS3 Easy UMS.apk
{
"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"
}
2. install BusyBox market. then run the app. it will automatic organise your busybox
3. download userinit.shhttp://db.tt/eDYyoIEa
4. using root explorer paste userinit.sh in /data/local
5. reboot your phone.
6. plug the cable to your pc
6.run "SGS3 Easy ums" first press Mount card then press ums mode. ان شاءالله it should work . you will find drive later mount for your microsd card.
i wonder if it will work for stock ics... testing...
ahhh... pity its not working...
Try skip step 3 and 4 .
Sent from my GT-P6800 using xda app-developers app
edan1979 said:
i wonder if it will work for stock ics... testing...
ahhh... pity its not working...
Click to expand...
Click to collapse
First thing to do you need root your phone..then follow the tutorial.. for stock ics or cm9 you need to skip step 3 and 4.. try it
Sent from my GT-P6800 using xda app-developers app
just out of curiosity, why would you wanna of this?
s28 said:
just out of curiosity, why would you wanna of this?
Click to expand...
Click to collapse
More faster transfer rate, no more hang. Main thing is you can mount any pc any os eg; osx,ubuntu,.. without installing driver.
Sent from my GT-P6800 using xda app-developers app

Stuck at bootscreen

Okay, I am new to the rooting and modifying android devices.. I rooted my Nexus 7 using supersu and was making modifications with ROM toolbox pro. I changed the boot screen, the font, and the wireless icon(starting out small) well when I restarted my tablet it wouldn't get past the lboot screen that I set to.
When I went into recovery mode, I tried to recovery my old system but it giving me md5 missing.. so I'm kinda of stuck
is there a direct approach to the solution?
Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.
Hohokam337 said:
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.
Click to expand...
Click to collapse
Okay so wiping the data/factory reset didn't work, how do i go about flashing the google factory image?
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
http://forum.xda-developers.com/sho...Factory Image with fastboot / return to stock
Sent from my Galaxy Nexus using Tapatalk 2
Now i am running into this error with the command prompt..
{
"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"
}
Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb
mr_tris said:
Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb
Click to expand...
Click to collapse
Got it,
Thank you all for the help

[Q] ADB connection problem - Device Offline

This is weird. I never had this problem with my Galaxy S3.
I've enabled USB Debugging on the phone.
Even toggled it off, rebooted and turned it on again.
I've also rebooted my computer and even updated SDK Toolkit.
No change in problem though.
Every time I try to connect to my phone from ADB, it just tells me the device is offline (see attached pic).
Any ideas?
{
"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"
}
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
StolenVW said:
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I'm not getting any popup for that.
CZ Eddie said:
I'm not getting any popup for that.
Click to expand...
Click to collapse
Try this
http://www.wugfresh.com/faqs/how-to-fix-adb-device-is-listed-as-offline-on-android-4-2-2/
And if you do a Google search for
how to fix adb device offline
It comes up with other things to try
Sent from my A500 using Tapatalk HD
Thanks, I tried the info in that link but never got the pop-up asking for ADB permissions.
I did google prior to posting also. I listed in my OP what I tried (which is what my googling suggested).
I'm about to ODIN back to factory stock anyways. So I'll try again after that. Maybe I messed something up during all the bloatware removal I did yesterday.
Nope, a fresh ODIN install of stock ROM didn't help at all.
Guess I'll have to uninstall & reinstall Android Toolkit maybe.
EDIT:
Using Motochopper root tool, I finally got the popup. And made sure to select "always allow from this computer". I think that should fixit.
EDIT #2:
Nope, that didn't help at all. Still "offline".
EDIT #3:
Actually, using the ADB from Motochopper does work. It's just the ADB from my Android Toolkit that doesn't work.
Sounds like one in android tool kit is out of date
Try updating the android sdk
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Formatted storage when connected to PC

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

Categories

Resources