While there are many how to threads on pretty much everything, theres not much going into deeper details. While ofc any of us wishing to learn has google and can find many answers, its just from here the the answers mean a little more. My fear is, my self included, is that there are many of us with misconceptions on some of the inner workings or just bad knowledge. Just to be clear this is to clear up exactly what some of the terms we hear and use actually mean as well as some of the practices.
For example
Regarding Odin
How many partitions exist on the internal memory, and what are there functions.
What exactly does the PIT file do.
What all does the TAR file contain (full package) and how does it write to the partitions.
What is the csc option?
What else should we know about odin?
Why has nobody removed the phone option for our purposes here?
Voodoo, exactly what partition is it changing and how is it actually converting.
Which cache is used for what and where is it stored?
Just some things off the top of my head that i don't have a complete understanding of and wish to learn more. Again for this thread at least i am looking for some details from people that actually do understand. There are many of us that can spew out answers to these and more that are just close to right without a full comprehension.
This is for learning and not just getting enough to get you through a problem as im sure many of us are guilty of
I found the same problem when I first got into Android but this is more a forum for developers who know what they are doing.
MattRussNC said:
How many partitions exist on the internal memory, and what are there functions.
What exactly does the PIT file do.
What all does the TAR file contain (full package) and how does it write to the partitions.
What is the csc option?
What else should we know about odin?
Why has nobody removed the phone option for our purposes here?
Click to expand...
Click to collapse
There are I think about 10-11 partitions on the internal storage. You have /system, /data, /cache, /dbdata, modem, bootloader, secondary bootloader, kernel, recovery, there is a partition dedicated for OTA updates, and another one as well, though I'm not sure what it is for. There may be more as well.
The PIT file is the partition information table, which tells Odin where each partition starts/ends.
The TAR file can contain any of a number of items for flashing, and they'll get flashed to the appropriate partitions based on their name.
factoryfs.rfs=/system
dbdata.rfs=/dbdata
cache.rfs=/cache
movinand.bin=/data
param.lfs=the .lfs partition, not sure exactly what it does
boot.bin=bootloader
sbl.bin=secondary bootloader
modem.bin=modem/radio/baseband
zImage=kernel
recovery.bin=recovery kernel
Adding a md5 sum to the tar file and renaming it to .tar.md5 allows for built in error correction.
Not sure what csc mode is, but I've never seen it used, so I'd avoid it.
Odin is a tool created by Samsung as far as I'm aware for flashing their phones. No one has the source, or knows exactly where the tool came from, so that is also likely why no one has removed the phone button, because you'd have to HEX edit the executable to remove it, and there is no telling what effects it may have, so it's better to just leave it alone.
MattRussNC said:
Voodoo, exactly what partition is it changing and how is it actually converting.
Click to expand...
Click to collapse
Voodoo converts the primary partitions of the phone, /system, /data, /cache, /dbdata. It converts by backing up the data to a file, reformatting the partition, then restoring the data from the file. If it didn't backup the data, it'd just be formatting the system.
MattRussNC said:
Which cache is used for what and where is it stored?
Click to expand...
Click to collapse
Cache is similar to a temporary storage area for files that are created and used frequently/semi-frequently. The files there aren't fully needed, but help speed up the system.
phonefiend said:
I found the same problem when I first got into Android but this is more a forum for developers who know what they are doing.
Click to expand...
Click to collapse
Well I do believe I would have to argue that most people that visit this forum knows what they are doing. While a great many here including myself that knows enough to get by, we would all be better off knowing more. Also since this is q&a forum I thought it would be a good place to ask and learn more then "how do root"
Sent from my SCH-I500 using XDA Premium App
Had no idea there was that many partitions. What was the reason that radios couldn't be flashed to the proper partition along with everything else? (as in why we always have to flash the modems on thee own)
Sent from my SCH-I500 using XDA Premium App
MattRussNC said:
Had no idea there was that many partitions. What was the reason that radios couldn't be flashed to the proper partition along with everything else? (as in why we always have to flash the modems on thee own)
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
No one is completely sure how to flash a full modem file via recovery, and it may not be possible without using stock recovery. The only tried and true method that is know for flashing full modem.bin files is Odin (and Heimdall), so that's why it's always a separate step.
MattRussNC said:
Well I do believe I would have to argue that most people that visit this forum knows what they are doing. While a great many here including myself that knows enough to get by, we would all be better off knowing more. Also since this is q&a forum I thought it would be a good place to ask and learn more then "how do root"
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
I think you misinterpreted my post. I'm just saying I also was looking for the same information you want but it didn't seem that the people in the know wanted to explain all the details you're looking for. It seems in your case someone at least tried to answer some of you questions, which is great.
phonefiend said:
I think you misinterpreted my post. I'm just saying I also was looking for the same information you want but it didn't seem that the people in the know wanted to explain all the details you're looking for. It seems in your case someone at least tried to answer some of you questions, which is great.
Click to expand...
Click to collapse
People are much more likely to answer questions when they're posted in the correct section. You also tend to get questions answered if you join IRC and ask things, but don't expect to get everything handed to you, there is likely to be some work/searching on your own part as well.
imnuts said:
People are much more likely to answer questions when they're posted in the correct section. You also tend to get questions answered if you join IRC and ask things, but don't expect to get everything handed to you, there is likely to be some work/searching on your own part as well.
Click to expand...
Click to collapse
Thank you for the answers to those first off. My apologies if i placed this in the wrong section, i thought this part was open for these types of questions.
Im sure irc is a great place to learn a great deal, however i fear asking in irc things that have been discussed many times. While searching will absolutely give you a very basic knowledge it is often repeated from those that don't fully understand it and may have it a little off. This isnt a cut at anybody as it should fall to the lower tiers to answer to the common issues that arise. However that kind of information is normally only good for solving a problem. For when there is no trouble and one wishes to know more about what they just did instead of how they did it, things fall short. Just about every member here can root, cwm flash, and odin but how many of us truly understand the process in detail. i know i dont, but i would like to. Thats what im looking for in this thread. Not how to do what we do, but whats taking place underneath.
Thanks again for the answers so far.
if this is in the wrong area and doesn't getting removed please let it fade.
imnuts said:
People are much more likely to answer questions when they're posted in the correct section. You also tend to get questions answered if you join IRC and ask things, but don't expect to get everything handed to you, there is likely to be some work/searching on your own part as well.
Click to expand...
Click to collapse
You're right about IRC being the place where questions may be answered. As far as searching, I can tell you a lot of the technical details aren't answered here.
MattRussNC said:
Thank you for the answers to those first off. My apologies if i placed this in the wrong section, i thought this part was open for these types of questions.
Click to expand...
Click to collapse
This is the proper place for questions. The problem is that many people will post their questions similar to this in the development forum, and that just gets the thread no where. And searching for technical info is difficult because usually you get flooded with useless stuff in your search.
imnuts said:
There are I think about 10-11 partitions on the internal storage. You have /system, /data, /cache, /dbdata, modem, bootloader, secondary bootloader, kernel, recovery, there is a partition dedicated for OTA updates, and another one as well, though I'm not sure what it is for. There may be more as well.
The PIT file is the partition information table, which tells Odin where each partition starts/ends.
The TAR file can contain any of a number of items for flashing, and they'll get flashed to the appropriate partitions based on their name.
factoryfs.rfs=/system
dbdata.rfs=/dbdata
cache.rfs=/cache
movinand.bin=/data
param.lfs=the .lfs partition, not sure exactly what it does
boot.bin=bootloader
sbl.bin=secondary bootloader
modem.bin=modem/radio/baseband
zImage=kernel
recovery.bin=recovery kernel
Adding a md5 sum to the tar file and renaming it to .tar.md5 allows for built in error correction.
Not sure what csc mode is, but I've never seen it used, so I'd avoid it.
Odin is a tool created by Samsung as far as I'm aware for flashing their phones. No one has the source, or knows exactly where the tool came from, so that is also likely why no one has removed the phone button, because you'd have to HEX edit the executable to remove it, and there is no telling what effects it may have, so it's better to just leave it alone.
Voodoo converts the primary partitions of the phone, /system, /data, /cache, /dbdata. It converts by backing up the data to a file, reformatting the partition, then restoring the data from the file. If it didn't backup the data, it'd just be formatting the system.
Cache is similar to a temporary storage area for files that are created and used frequently/semi-frequently. The files there aren't fully needed, but help speed up the system.
Click to expand...
Click to collapse
I was wondering some of those terms my self.
thanks for all the Great info,
One thing been bugging me lately. Most likely every one has experienced the need to either wipe the caches more then once or flash multiple times for success. How is it that wiping cache is not 100%. Why does flashing a rom more then once sometimes yield different results when done the exact same way?
i believe the phone button in odin is to flash radio/modem alone
which we unfortunately do not have (yet)
the phone button and other buttons are still there because the gsm ones, like the captivate and vibrant, are using it
jk0l said:
i believe the phone button in odin is to flash radio/modem alone
which we unfortunately do not have (yet)
the phone button and other buttons are still there because the gsm ones, like the captivate and vibrant, are using it
Click to expand...
Click to collapse
I've only flashed the modem/radio by itself in the PDA button like everything else. As far as I know, we only flash things for the Fascinate through the PDA button (except of course for the atlas v2.2 PIT file.) That includes ROMs bundled in an ODIN package, modems/radios, and recoveries.
jk0l said:
i believe the phone button in odin is to flash radio/modem alone
which we unfortunately do not have (yet)
the phone button and other buttons are still there because the gsm ones, like the captivate and vibrant, are using it
Click to expand...
Click to collapse
The phone button is for completely different devices, likely their regular, non-smartphone, devices. It is not meant for flashing anything for the Fascinate.
Could have found a better place i guess but this will do. Noticed we are still without a FAQ aside from the outdated one as well as the guide. I thought perhaps some discussion on what should be included in a FAQ was in order to fill the gap.
Simple basic guides are important and have there place, however as one can use links to more details there is no reason not to have a comprehensive guide.
Just a thought. Most of us know the basics of what root is and how to gain that access. Most of us also has no idea exactly how get root manually without following instructions either. So what i was hoping for in the next guide
Q= What is root ?
A= Super user access needed for apps that need more control over your device like titanium backup
For more information click here
Then give the full out dev definition including the details that require reading up to understand. For those that want to learn.
Q= How do i root ?
A= Flash this package in odin (and give the dl link as well as a odin guide link)
For more information click here
Have the full process laid out by what needs to be done in shell without giving the copy and paste instructions. For those that want to understand what they are doing more than just doing it.
Just thought it would be nice if our next guide could be useful to more then just beginners.
Related
It seems that there are a lot of ROMs out there that are doing some funky stuff from the edify scripting in CWM and providing a poor user experience. This overall hurts the entire custom NookColor community and puts a bad taste in peoples mouths.
This post is to point out best practices when creating CWM flashable zips in a consistant way allowing the user to upgrade and migrate between roms in a predictable way.
Rule #1: Don't touch /data!
There are many reasons why you don't want to touch /data but the most important is to allow the user to be able to upgrade your rom without completely wiping your data.
If you want to bundle in an applications (first of all... don't but if you reaally think it is necessary) put it in /system/app as a system app.
Rule #2: Don't overwrite /boot/uRecRam and /boot/uRecImg!
ROM and CWM should be separate. Users should be able to use your rom with CWM or even the stock recovery if they wish to. Allow the user to choose what version of CWM they want to run and allow them to upgrade it independently of your rom.
This allows you to not re-release roms every time a new version of CWM is released.
Exceptions to the rule are update zip that are intended to install CWM (which is ok) or zips that will restore the entire system to stock.
Rule #3 Learn edify
Edify scripting is quite powerful. It saddens me to open up the updater-script of a rom and see it extracting a script and then executing the script.
Don't store your roms as .tars and require a script to extract them to the right locations, you should be doing this all from edify scripts.
Rule #4: Only touch /system and /boot/uImage and /boot/uRamdisk
All other files should be off-limit! This goes back to rule #1 and rule #2. A rom should consits of a kernel, a ramdisk to boot the system and /system files for running the rom!
Rule #5: NEVER EVER EVER modify partitions or wipe the EMMC completely!
I cannot stress this one enough. Use stock partition scheme for your rom. It may seem like a "waste" to you but this is what will make all our roms compatible with each other!
Also the Nookcolor stores NVRAM type information on /dev/block/mmcblk0p2 and factory restore information and a backup of p2 on /dev/block/mmcblk0p3.
If you wipe these directories in your update.zip you WILL BRICK THE USERS NC! It may work for you but they can never return to stock. Their serial number and mac addresses will be lost!
Just don't even think about doing anything with the partition map or these partitions!
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
For the users I will list the ROM that are compatible with the list above and list ROMs that don't follow these rules.
ROMs that follow proper packaging
These rom have been built properly according to the rules in the OP. I highly recommend testing any of these out.
Cyanogenmod Nightlies
phiremod nook V5.2
Nookie Froyo 0.6.8
(Utility Update.zip) Nook Color SDcard and emmc swap
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
Avoid this rom if you are new to Android or the NookColor. I would call this rom an "Advanced user" rom and not for new members of the community who are unfamiliar with Android, Linux, or the NookColor
Click to expand...
Click to collapse
HC v4 eMMC 2nd ed. - Flashable ZIP
This rom packaging is the poster child for how to do it wrong. They overwrite your /data for app customization. It uses an external script and tar files for extraction and overwrites all of /boot!
AVOID THIS ROM PACKAGE!
Click to expand...
Click to collapse
This looks very wise and in accord with general programming principles.
In the same area of discussion, can you talk about whether or not to clear cache while doing this same update process.
In fact, some explanation of /cache and Dalvik Cache and Market Cache might help to alleviate confusion, especially in regards to specifically what they are, and when one should clear them.
Sure, a "cache" is a piece of data that is frequently used, and so put in a more accessible place, but in typical confusing fashion, that general term is being used in a specific way in Android.
Thanks !
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
If everyone used CW to right to EMMC, this would be easy. But users like myself are running ROMs from SD and are always looking for a way to easily update and flash mods or ubdate ROMs to SD. Yes I use ADB, and other methods, but often I am traveling and away from my office or studio were my PC's are.
Any ideas on CWM to keep things more unified as the op suggests and be able to write to bootable SD cards?
Thanks for starting the discussion.
12
Good explanation/write-up, nemith. Not being a dev, but a user, it helps me to better understand which ROMs to use on my NC. I really liked HC EMMC, but did not realize that it would make it so I could never return back to stock (losing my S/N and such).
Also concur with ADude about cache....a good explanation would be helpful here. I only clear the cache/Dalvik when installing a new kernel. Not sure if even necessary? And, I clear AFTER installing, not before, so not sure if I am even doing that in the correct order. Setting the record straight would go a long way for us non-devs.
Sorry, one more thing, it would be great to have a consistently updated bootable SD card with latest/greatest of CWR on it. I am still on 3.0.0.6 and I am not sure why??
Thanks!
~ Razir
Could have used this a few months ago.
Thank you.
Nemith, your thread is directed at devs. If you want to make sure people don't flash my HC v4 2nd edition, you might want to invite users to read this as well.
nemith said:
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
I would avoid dual booting roms if you can!
Click to expand...
Click to collapse
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
12paq said:
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
12
Click to expand...
Click to collapse
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
cromanorn said:
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
Click to expand...
Click to collapse
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
nemith said:
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
Click to expand...
Click to collapse
THANKS!!! I had the NC for about 4 days now and would hate to have messed it up in the long run. I have a Droid Incredible that has been flashed more times than I can remember. It would be nice if the warnings were incorporated into the OP of these roms. I read the entire thread before flashing and I may not have flashed if this warning was there. I like having the option of going back to Stock without repercussions.
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
nemith said:
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
Click to expand...
Click to collapse
Yup. That would be very nice.
The Nook having SD boot priority really makes it versatile for testing, and quite recoverable. It also satisfies a unique situation where many users have a family device with Nook magazines and children's books not available on the Nook app, so many like myself are booting experiments and daily runners from SD and keeping the wife happy. LOL.
cromanorn said:
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
Click to expand...
Click to collapse
If you go digging at nookdevs.com and on your own NC you should be able to figure out what is safe and what is not.
nemith said:
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
Click to expand...
Click to collapse
the ironic thing is CM Roms don't fully follow Rule #3 since they have multiple scripts that run inside their packages during rom installation.
I'm not sure you are correct in saying that if you flash one of the HC emmc roms you can not revert back to stock. I know for a fact I have done both the dual boot, and HC emmc roms and reverted back to stock multiple times after doing so
I'm not saying you are wrong but I don't think i did anything to "advanced" to get back.
Quoted:
(I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?)
I had it installed and got back to stock no problem... i'm not sure what he is talking about.... i could be wrong though...
It was dualbooted CM7 and HC
went back to stock, registered with BN and all was well.
nooted it and then install HC on emmc
reverted back to stock to set up the ubuntu on NC
got bored of that and am back on HC on emmc
I went back to stock after both as well. Has anyone not been able to after using one of those two roms? I work at b&n and I had to spend time with the stock since they wanted me on the nook counter. I've been back and forth between all the roms more times then I can count.
Sent from my NookColor using Tapatalk
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
[Edit] It was the SD card's fault. It seemingly worked fine in the laptop and it mounted fine in CW Recovery, but as soon as I used a different SD card I could flash zips again.
So, now I'm playing with phiremod v6 and loving the Nook again.
I believe I just bricked my Nook through use of the dual boot script.
I can only boot from SD into CW but not a single zip can be applied to the internal storage. Not even the "reverse dual boot" zip will run. They all error out.
I believe this is due to unexpected partitioning.
I even formatted boot, system and cache and still it will not restore any Roms.
So now I'm hoping to access the Nook through USB and repartition the internal storage manually. But before I do that, I need to learn about ADB and what the correct settings are.
jlt220 said:
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
Click to expand...
Click to collapse
I don't think Nemith was saying that the existing dual boot installer is going to prevent you from returning to stock. He singled it out as a "ROM" that modifies the partition table, which can be a dangerous thing to do. There is information stored in the /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3 partitions that is specific to each device and required by the B&N software. This information can't be rebuilt easily if lost.
The dual boot install and removal tools (in their current versions) appear to leave these partitions in tact. They are modifying the partition table though, so they're not recommended for novice users. You were able to install and uninstall it with no problems, so you're clearly not one .
The other point is that future versions of the dual boot (doubtful since it has a good dev) or other similar style "ROMs" may not be so careful with your 0p2 and 0p3 partitions.
I'm sure there is an article or thread somewhere that outlines things like what is stored to the 2gb miniSD, what goes on the 16gb, if there is a built in memory chip and what is on that.
If anybody can point to one, I would be very appreciative.
I'd also like a link to a definitive explanation of what happens during the different types of recoveries. What is the difference between using zip files and pkg files, for example. How come some zip updates only make small changes but others can completely rewrite the phone and brick it?
What does it take to do the equivalent of formatting your computer and starting completely over with a fresh phone? I mean cleaning everything out.
What is it about this phone that a full nandroid backup will successfully bring back the phone one day and fail miserably the next?
I want to really understand this phone, because I am not going back to a smaller screen so it looks like I'm stuck with it for a while because there just doesn't appear to be a mad rush of manufacturers releasing 5 inch phones.
mid_life_crisis said:
I'm sure there is an article or thread somewhere that outlines things like what is stored to the 2gb miniSD, what goes on the 16gb, if there is a built in memory chip and what is on that.
If anybody can point to one, I would be very appreciative.
I'd also like a link to a definitive explanation of what happens during the different types of recoveries. What is the difference between using zip files and pkg files, for example. How come some zip updates only make small changes but others can completely rewrite the phone and brick it?
What does it take to do the equivalent of formatting your computer and starting completely over with a fresh phone? I mean cleaning everything out.
What is it about this phone that a full nandroid backup will successfully bring back the phone one day and fail miserably the next?
I want to really understand this phone, because I am not going back to a smaller screen so it looks like I'm stuck with it for a while because there just doesn't appear to be a mad rush of manufacturers releasing 5 inch phones.
Click to expand...
Click to collapse
There are many out there, too many to list as a matter of fact... if you just use the Search function you will find all your answers. I hate to sound rude but this is just the type of thing the search is meant for. There are several guides that outline all you want to know, but I point them out to you, you won't be any the wiser by just clicking on them. The jargon you have to go through to get to the meat of your questions will teach you everything you need to know along the way.
I've tried searching. The problem is choosing words that get usable results without also getting a ton of useless ones to wade through.
mid_life_crisis said:
I'm sure there is an article or thread somewhere that outlines things like what is stored to the 2gb miniSD, what goes on the 16gb, if there is a built in memory chip and what is on that.
Click to expand...
Click to collapse
There is no single article where you can get all of this info. Best general resource is the XDA Wiki on the Streak.
For more info on the workings of the inner SD Card see this thread at MoDaCo.
mid_life_crisis said:
I'd also like a link to a definitive explanation of what happens during the different types of recoveries. What is the difference between using zip files and pkg files, for example. How come some zip updates only make small changes but others can completely rewrite the phone and brick it?
Click to expand...
Click to collapse
The stock recovery will install .pkg files (update.pkg or OTA upgrades). These are a full replacement for the software on your phone. When installing as an update.pkg file it is best to use the recovery for the version you are installing.
When installing an OTA update the recovery that preceded the one you are installing should work if your are 'upgrading' to a ROM from the same region, the checks that are done during an OTA update will prevent a phone from one region using an OTA update from another region. The advantage to using the OTA update process is that you retain your apps and settings. OTA updates are done by downloading the file to your phone and then tapping the DL notification in the notification bar.
A custom recovery (use StreakMod recovery) will write .zip files. These files can be a theme like a new notification bar or a ROM like StreakDroid or SimpleStreak. Custom recoveries are able to write a subset of the phones software. Most custom ROMS are not a full replacement for the the phones software, which is why they may include directions to flash a certain baseband or other additional files.
mid_life_crisis said:
What does it take to do the equivalent of formatting your computer and starting completely over with a fresh phone? I mean cleaning everything out.
Click to expand...
Click to collapse
Installing a stock rom with a stock recovery from recovery mode will do this. Since a stock ROM is the whole software package this will also make sure that the baseband and amss.nbn files are all in sync (same version). Doing this or a factory reset formats the internal SD Card.
mid_life_crisis said:
What is it about this phone that a full nandroid backup will successfully bring back the phone one day and fail miserably the next?
I want to really understand this phone, because I am not going back to a smaller screen so it looks like I'm stuck with it for a while because there just doesn't appear to be a mad rush of manufacturers releasing 5 inch phones.
Click to expand...
Click to collapse
I have never had a nandroid backup fail. I use StreakMod recovery.
If you check out the links in my signature you may find more answers.
Posts like that last make me really pissed off that I can only click "Thanks" once per post.
Modding your Streak - where to start expands on my answer posted here.
Ok, I've gotten the pure stock ICS and installed it. Now, something I have noticed is that no matter what I do, I can never get all of the files in my phones directory be completely stock. There are some that files left over from applications and such. I would just go "willy nilly" deleting everything i thought didn't belong in there except that the last time I did that I hard bricked my Captivate. I love my Note and don't want to hurt it!!! Any advice or screen shots of a truly stock file setup would be greatly appreciated. Thanks. :cyclops:
condork464 said:
Ok, I've gotten the pure stock ICS and installed it. Now, something I have noticed is that no matter what I do, I can never get all of the files in my phones directory be completely stock. There are some that files left over from applications and such. I would just go "willy nilly" deleting everything i thought didn't belong in there except that the last time I did that I hard bricked my Captivate. I love my Note and don't want to hurt it!!! Any advice or screen shots of a truly stock file setup would be greatly appreciated. Thanks. :cyclops:
Click to expand...
Click to collapse
I dont understand your question or post. You want to keep your ICS completely Stock? Wouldn't be completely Stock if dont install any apps?
Or you referring to removing all the bloatware? Then you need to be Rooted, and then use a non stock app>Tibu to remove your bloatware?
But to be rooted there are measures to take to get Rooted.
clarification
what i am asking is when you go to applications then my files what does stock setup look like. i install and uninstall so much crap all the time and everything seems to leave folders and files behind. From time to time i'd like to just clear everything thing out that i don't need. In order to do that safely, however, i have to know what i DO need so i don't brick another phone. thanks.
the best way to remove the unwanted items on the internal SD, is to format the emmc in recovery (CWM)
this will "wipe" the internal space of the device, and repopulate only the specific device information pertaining to the rom on reboot.
but i caution you.......(please read this) !!
Although the risk is low, you can possibly delete items that you should not have. I.E.
data that you should back up prior to removal. photo's, documents, data from specific system apps etc.
But i've done this at least a dozen times since owning my note, as it strips all garbage left over from previous roms etc.
Again, you do this at your own risk, and i assume no liability from "your" choice to wipe the emmc partition, or any other partition on your device.
long story short, format emmc from recovery, and your internal storage will be "empty" as in nothing left. then on reboot, the device rom will re-populate the bare minimum file structure to run. So back up anything/everything you want to keep, and place it on PC...then it can be moved back if needed.
Now i dont know your skill level, or your root status etc. so if you are not rooted yet...see the "note everything" thread at the top of the general section. It is the best guide i've ever seen. and it will guide you through any process you want to use. with the exception of the one i just gave you...LOL
this method is no joke...and you "must" be sure that you understand what you are doing, and how to recover the device if something goes wrong.
good luck, and be careful !!!....g
Outstanding Sir! Thank you very much. Worked wonderfully. It's amazing how the little things can really brighten your day.
condork464 said:
Outstanding Sir! Thank you very much. Worked wonderfully. It's amazing how the little things can really brighten your day.
Click to expand...
Click to collapse
done already ?
Nice !...........:highfive:
Glad to have helped you......g
P.S.
If you dont mind, could you edit your thread title to include the word "SOLVED" ??
It helps users find answers faster, and keeps the sections clean..
Thanks !!....g
gregsarg said:
done already ?
Nice !...........:highfive:
Glad to have helped you......g
P.S.
If you dont mind, could you edit your thread title to include the word "SOLVED" ??
It helps users find answers faster, and keeps the sections clean..
Thanks !!....g
Click to expand...
Click to collapse
:good::good::good::good:
I am a noob and I am not a developer or even really great at programming or PC's in general.
I've managed to mess up my phone and have been looking all over the web for how to fix it and I am at a loss.
I decided to register and ask for help. Please be patient and understanding if I ask a lot of questions or don't understand things you accept as basic, understood or common. I looked through existing threads for help and couldn't find the answer I needed. Many thanks in advance for the help. Readers digest of the issue below.
Samsung Galaxy S 4G. T-Mobile. T959V5B5-Custom.
I tried the non-mandatory firmware update from T-mobile and it wrecked the functionality of my phone. I tried to go back with a couple new Rom versions and think I more or less ended up with three roms installed on my internal storage which has given me basically no space which was never an issue for me before. I have used a disk viewer to verify there is unmounted data that is taking up space but I can't figure out how to get to it through the phone or my pc to delete it. I assume if I do this that the empty space will be absorbed and fix the internal storage issue.
Again, thank you for taking the time to read and respond. I love my phone and just want it working right again.
JBMFT said:
I am a noob and I am not a developer or even really great at programming or PC's in general.
I've managed to mess up my phone and have been looking all over the web for how to fix it and I am at a loss.
I decided to register and ask for help. Please be patient and understanding if I ask a lot of questions or don't understand things you accept as basic, understood or common. I looked through existing threads for help and couldn't find the answer I needed. Many thanks in advance for the help. Readers digest of the issue below.
Samsung Galaxy S 4G. T-Mobile. T959V5B5-Custom.
I tried the non-mandatory firmware update from T-mobile and it wrecked the functionality of my phone. I tried to go back with a couple new Rom versions and think I more or less ended up with three roms installed on my internal storage which has given me basically no space which was never an issue for me before. I have used a disk viewer to verify there is unmounted data that is taking up space but I can't figure out how to get to it through the phone or my pc to delete it. I assume if I do this that the empty space will be absorbed and fix the internal storage issue.
Again, thank you for taking the time to read and respond. I love my phone and just want it working right again.
Click to expand...
Click to collapse
The course of action I would recommend at this point is using a tool called Odin to re-flash the stock ROM to your phone. I would recommend taking a look at this guide for the step-by-step procedure on how to do this. Let me know if you still have questions .
shimp208 said:
The course of action I would recommend at this point is using a tool called Odin to re-flash the stock ROM to your phone. I would recommend taking a look at this guide for the step-by-step procedure on how to do this. Let me know if you still have questions .
Click to expand...
Click to collapse
Hey! Big thanks for the reply. Here come the questions...
I used Odin to put the other OS versions on the phone so I am familiar with the software though its been several months. I also still have the ROM that I flashed to phone. I am curious though that if it didn't wipe the previous partitions last time, what would keep it from doing the same thing this time and really messing me up? Or did I click or not click something in Odin or use the wrong option and doing it differently this time would fix the problem?
I located the files on the phone and have verified they are not mounted and looked at their size using DiskInfo. They are located at "/dev/block". Do you know what this is or why they are there? I can delete them using ES File Explorer with SuperUser. Is it ok to delete these and would I get the benefit of increased storage by doing so? I played around with moving them to the SD card and didn't see an increase in my internal storage but was afraid that a reboot after doing to might be bad.
Can you tell I am a little gun shy?
Here are the names of the files, the set starting with t starts at 0 and goes to 12 and the other 1 to 12.
tsfr0-tfsr12
bml1-bml12
Thanks again!
JBMFT said:
Hey! Big thanks for the reply. Here come the questions...
I used Odin to put the other OS versions on the phone so I am familiar with the software though its been several months. I also still have the ROM that I flashed to phone. I am curious though that if it didn't wipe the previous partitions last time, what would keep it from doing the same thing this time and really messing me up? Or did I click or not click something in Odin or use the wrong option and doing it differently this time would fix the problem?
I located the files on the phone and have verified they are not mounted and looked at their size using DiskInfo. They are located at "/dev/block". Do you know what this is or why they are there? I can delete them using ES File Explorer with SuperUser. Is it ok to delete these and would I get the benefit of increased storage by doing so? I played around with moving them to the SD card and didn't see an increase in my internal storage but was afraid that a reboot after doing to might be bad.
Can you tell I am a little gun shy?
Here are the names of the files, the set starting with t starts at 0 and goes to 12 and the other 1 to 12.
tsfr0-tfsr12
bml1-bml12
Thanks again!
Click to expand...
Click to collapse
Using Odin to re-flash the stock ROM will automatically setup the right configuration for. Do Not delete the files in /dev/block these are critical to the phones operation and part of the phones normal partitioning and operation as previously stated deleting these will cause a lot of problems if you delete them. If you really want to free up some internal storage space I would recommend deleting the carrier pre-installed bloatware, before you delete any bloatware makesure to backup the apps you deleted with Titanium Backup or a similar backup or flash Clockworkmod Recovery or Team Win Recovery Project and make a Nandroid Backup which is a complete backup of your phone. And don't worry about being gun shy we are all beginners at some point the only real way to become an expert if practice, practice, practice .
So I am working on the Heimdall One-Click.
Handshaking with loke, got no response. FML.
Help.
Edited: Apparently a low battery is not your friend...
after a little reading around on the net I tried a different one and BAM.
Back to stock. We'll see how this goes.
Being rooted with superuser had me spoiled...so much bloatware.
I have a Samsung Galaxy S2 i9100 running Android 4.1.2. It is currently rooted using Chainfire method but no CWM installed.
I have questions about PIT file usage. I have searched the forum on the topic and have seen all the warnings that using PIT files can lead to bricking your phone and should not be done unless you know what you are doing. The only reason that I had been considering repartitioning was that I was running out of application space and wanted to increase the application partition from 2GB to 5GB.
I came across an article that had a link (http://forum.xda-developers.com/showthread.php?t=2538947) to various sizes PIT files for the Galaxy SII and a procedure on how to do the repartition. I have not tried this procedure since I spent considerable time researching any problems associated with doing a repartition. However, I still have not been able to find the answer to my questions, hence this post.
My questions are as follows:
(1) When doing a repartition using a PIT file, do you have to flash the rom (stock rom or custom) at the same time via odin? Or can you just
do a repartition, and factory reset? The procedure suggests flashing the rom, but I have seen posts that suggests that they just did the
repartition no ROM flash.
(2) After partitioning with the PIT file and decide to flash a custom rom at a later date, will I need to provide the same pit file at the time of
installing the new rom? I know some ROMs already have a PIT file included. The concern that I have is the new ROM may not find the
new repartition mount points – based on some posts that I have seen.
I have not made any decisions with regard to doing the repartition. After getting the answers to the above questions and any other insights that people care to provide, I will then decide on how to proceed.
Thanks.
So you want to expand the space destined to the SO.
You don't need to do that.
Read the korean's S2 thread; is that what you want?
Sent from the little guy
gastonw said:
So you want to expand the space destined to the SO.
You don't need to do that.
Read the korean's S2 thread; is that what you want?
Sent from the little guy
Click to expand...
Click to collapse
I guess I should add some additional information, I have already removed unused apps, cleaned up apps/system cache, removed system logs, cleared cache via recovery, and cleared the davilik cache (system recovery and titanium backup). I am still on the borderline - I can barely update any of the installed apps as I am getting the insufficient space error.
I took a look for the korean's s2 thread but no luck - I used the search function and looked at all posts by korean* - I assumed that korean is the userid. Maybe I missed something, perhaps you can post the link or provide a bit more detail so I can find the thread.
Thanks,
By korean I meant the korean version of the SII.
We've got a couple of threads that solve the storage issue you're experiencing, "issue" rather.
Anyhow, check them out.
And believe me, you don't need to re partition your device (PIT)
BTW, are you having trouble with apps or you're just checking the "storage" toggle?
If so, don't worry about it.
Sent from the little guy
gastonw said:
By korean I meant the korean version of the SII.
We've got a couple of threads that solve the storage issue you're experiencing, "issue" rather.
Anyhow, check them out.
And believe me, you don't need to re partition your device (PIT)
BTW, are you having trouble with apps or you're just checking the "storage" toggle?
If so, don't worry about it.
Sent from the little guy
Click to expand...
Click to collapse
Thanks gastonw, For clarification, my SII is the international version I9100 not the Korean version.
To answer your question, I am having trouble installing/updating apps. I am getting the error insufficient space available.
I get this error when updating apps and it has reached the point where even if I uninstall the app and try and install the same updated app I get insufficient space available.
I have searched for the Korean SII in the Q & A forum and from what I can gather, they are talking about turning the Korean version of the phone into the i9100 which does involve some repartition to the current i9100 PIT. Maybe I am looking at the wrong threads because I missed the reference to the storage problem.
Thanks.
mpcp27 said:
Thanks gaston, Currently still looking through the threads.
To answer your question, I am having trouble installing/updating apps. I am getting the error insufficient space available.
I get this error when updating apps and it has reached the point where even if I uninstall the app and try and install the same updated app I get insufficient space available.
Click to expand...
Click to collapse
Try installing romnuke script and flash another rom.
Only if u have gti9100
Sent from my GT-I9100 using Tapatalk 2
corruptionfreeindia said:
Try installing romnuke script and flash another rom.
Only if u have gti9100
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reference to the romnuke script. Will definitely put that in the arsenal of tools when required. However, I haven't reached the stage of flashing another rom just as yet. I am currently on I9100 Samsung stock rom but rooted. Figured I would deal with the space problem first before moving onto flashing roms at a later date.
Try clearing out them log folders.See what is freed up.
theunderling said:
Try clearing out them log folders.See what is freed up.
Click to expand...
Click to collapse
Yes, I tried all of that before considering the PIT solution.
In any event, I think I have found the answer to my questions from drilling down all the way into the original thread that I found. The answers I believe are as follows:
(a) You do need to flash a stock/custom rom when doing flashing the PIT file
(b) Based on the fact that other people have flashed other custom ROMs after flashing the PIT file, I suspect there isnt any problem flashing any other roms with the new PIT structure.