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
Related
Boot animation ICONIA A500
install with:
Code:
adb push bootanimation.zip /data/local
the default is well default for all android devices. people will need to make some bootanimations to flash.
Just do this: adb push bootanimation.zip /data/local/bootanimation.zip and setup a nice bootanim
i figured it out... just after i posted...got shnny bootanim now
good bootanimation here http://forum.xda-developers.com/showthread.php?t=991086
just have to remove the motorola logo...
I'm after a nice boot animation as well, currently I'm using the radio active Xoom boot animation. Unfortunately it displays Xoom. Although I'll have a look at photochopping it out and adding Iconia or something in there.
remade the retro bootanimation for our lovely a500
hope you guys like it
UPDATED first post
not bad man good job.
is there a tut i can read that explains the process of making a new boot screen/animation? does it require root? That link to the xoom version has a post that says it doesnt.
doesnt require root
The Animation is wrong... The Acer had 1024M DDR3 Ram
good to know. any chance of getting a fad writeup?
did anyone have the honeycpmb one??
that is many honeycomb on the screen
So whats the file structure for this? /data ? there's no /local folder in that and it wont let me make one... Sorry, noob.
EDIT***
Okay looks like I need adb (reading that xoom thread and others with the same question as mine) - ill figure it out.
EDIT 2***
Got it working Very cool Thor
What does adb mean?
Ha haah...awesome
Is it possible to save the stock boot ?
I don't get it - you people actually turn your device off? ;-)
I never see the boot animation because well... I never power my tablet off. Why wait so long for it to boot when I'm going to use it multiple times during a day anyway?
good work
what programs you have created the
would like to create one yourself
Crazy - A500 use DDR3 RAM
Can anyone modify this one to fit the Acer A500 specs?
http://forum.xda-developers.com/showthread.php?t=648555
{
"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"
}
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
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
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
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