Related
I have a Droid Eris but I made the fatal mistake of putting clockwork recovery on it :'( and now I can't do anything with it because of the following:
1.) Can't install PB00IMG.zip from HBOOT because: "Main version is Older!" (I've checked the md5sums and everything lines up)
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Feb 8 2010,00:08:56
2.) Clockworkrecovery 2.5.0.1 (I get the error message below)
3.) A bad deployment of GSB Gingerbread (2/18/2011) {Stays on Android skateboard screen and never does anything}
Is there anything I can do with this combination of stuff to get my phone booting into Android again?
Any help (even a "you're screwed" message) would be of help. Thanks guys
ttp://img834.imageshack.us/img834/8232/img20110221103304.jpg
KannedFarU said:
I have a Droid Eris but I made the fatal mistake of putting clockwork recovery on it :'( and now I can't do anything with it because of the following:
1.) Can't install PB00IMG.zip from HBOOT because: "Main version is Older!" (I've checked the md5sums and everything lines up)
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Feb 8 2010,00:08:56
2.) Clockworkrecovery 2.5.0.1 (I get the error message below)
3.) A bad deployment of GSB Gingerbread (2/18/2011) {Stays on Android skateboard screen and never does anything}
Is there anything I can do with this combination of stuff to get my phone booting into Android again?
Any help (even a "you're screwed" message) would be of help. Thanks guys
ttp://img834.imageshack.us/img834/8232/img20110221103304.jpg
Click to expand...
Click to collapse
Don't do anything further to your phone until you have answered a couple of questions. In the meantime, plug your phone onto the charger and keep it fully charged. The steps you take at this moment are extremely critical. In particular, I would recommend that you avoid attempting to flash a PB00IMG.ZIP file or run an RUU until you have investigated a few more things.
First, let's find out about your skills and resources:
Q1) Do you know how to use "adb" and the command line?
Q2) You are still able to boot into recovery, HBOOT, and Fastboot modes, right?
I'll post another entry in a minute or two - I want this to get up on the board ASAP.
OK, so here's the deal about that symlink error.
It can result from two different conditions - one of which is innocuous, and one of which is "near-death".
In the "near-death" case, flashing a PB00IMG.ZIP file or running an RUU sometimes results in a hard brick, so, for the moment you should avoid that.
So, if it is the "innocuous case", what happens is that you simply flashed a ROM file which was truncated or corrupted. The installer script performs a lot of "symlink" installations after files have been unpacked from the "system" area in the ROM file; if that fails so that the target of the symlink is not found, you get an error similar to what you see in your .jpg file.
(BTW, this is the exact reason that newbs are advised to stay away from Clockwork - it does not perform signing verification of ROM files to check that they are complete and uncorrupted. Amon_RA does this, so that it is impossible to flash a corrupted ROM using Amon_RA - but ClockworkMod does not provide you that protection).
The second cause is much more sinister - we have observed cases where something in Clockwork ends up causing the MTD driver in the kernel to mark a massive number of pages in flash memory as if they had fatal flaws - they can not be reclaimed by the standard erasure methods that the custom recoveries normally use. The net effect is that when you try and load a new ROM onto the phone (assuming that the ROM file is correct, complete, and uncorrupted), the installer runs out of space and the installation fails.
[SIZE=+2]We will need to be able to discriminate between those two cases to determine how to proceed next.[/SIZE]
The most direct way to detect this more critical problem is to boot into ClockworkMod recovery, create a shell on the phone using "adb", and then attempt to "mount" the /system mount point. It is possible that this will fail; but if it succeeds, you then erase everything in /system, and do a "df" command to look at available space on the phone, as in:
Code:
C:\WindozeSucks> [COLOR=green]adb shell[/COLOR]
# [COLOR=green]mount /system[/COLOR]
[COLOR=grey](If the above command fails, proceed no further)[/COLOR]
# [COLOR=green]cd /system[/COLOR]
# [COLOR=green]df -k /system[/COLOR]
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 174080 112128 61952 64% /system
# [COLOR=green]rm -rf /system/*[/COLOR]
# [COLOR=green]df -k /system[/COLOR]
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 174080 112128 61952 64% /system
# [COLOR=green]cd /[/COLOR]
# [COLOR=green]umount /system[/COLOR]
The example output of the "df -k" command above is from my phone where I did not erase the /system folder. Note that its total size is about 174,000 kB (roughly 170 MB). If you have a bunch of bad pages, your total size will be quite a bit smaller than this. Note also that it reports the "Use%". If you are showing 100% use when you first run the "df" command, this likely also indicates a problem of this nature.
When you actually erase all the files in the /system folder, the 2nd time you run the "df -k /system" command, you should see a very low total "Use%" - about 1%. Note that his erasure does not correct the problem - we are only trying to find out what state your phone is in at the moment.
2) If you are not familiar with using adb, there is an indirect route you can take, which is to determine if the ROM file on your SD card is corrupt or not.
Ahhh, ****, I forgot that ClockworkMod doesn't have a MS-USB mode
Again, boot into Amon_RA, connect to the PC, and then toggle "MS-USB toggle" from the Amon_RA menu. Then use a file explorer on the PC to find out the exact size of the ROM file on the SD card (down to the very last byte). If it is exactly the correct size, it is somewhat unlikely that this is a simple problem of a corrupted ROM file. If you know how to do it, compute the "MD5" signature of this ROM, and report both the exact total file size (in bytes) and the MD5 signature.
I'll provide more instructions after you respond.
bfb0
PS You didn't mention WHICH PB00IMG.ZIP file you were trying to flash, nor the exact version of GSB you used - I presume you mean the ROOT version/GSB v1.6, but you ought to clear that up to avoid any ambiguities.
I can post up a flashable zip that will allow you to replace your ClockworkMod recovery boot with Amon_RA, so don't get discouraged yet.
Such a thing is trivial to do - it's never been done so far on the Eris forum because the emphasis of rooting was on getting any custom recovery in place, rather than replacing a custom recovery with another custom recovery.
But, I think it is important to use non-destructive methods first to investigate as thoroughly as possible; because your current recovery boot is your lifeline to getting the phone back, we should avoid that until I've received some feedback from you.
bftb0
Nevermind.
bftb0 said:
Ahhh, ****, I forgot that ClockworkMod doesn't have a MS-USB mode
Click to expand...
Click to collapse
In ClockWork Mod Recovery it's under the Partitions menu, I think at the bottom of the list.
roirraW "edor" ehT said:
In ClockWork Mod Recovery it's under the Partitions menu, I think at the bottom of the list.
Click to expand...
Click to collapse
Thanks - I wasn't aware of that.
I have been using both Clockwork and Amon_RA - I think you saw the hack/trick I am using that allows me access either one I choose from a cold boot.
I tend to use Clockwork for Nandroid backup/restore (because it is far more complete), and Amon_RA for almost everything else. I want my installer to perform signing verification, dammit!
bftb0 said:
Thanks - I wasn't aware of that.
I have been using both Clockwork and Amon_RA - I think you saw the hack/trick I am using that allows me access either one I choose from a cold boot.
I tend to use Clockwork for Nandroid backup/restore (because it is far more complete), and Amon_RA for almost everything else. I want my installer to perform signing verification, dammit!
Click to expand...
Click to collapse
You're welcome!
Yes, actually even with ROM Manager installed I most often use QuickBoot or any other app/ROM's reboot to recovery option and then load ClockWork from there. Most of the time it seems actually less time consuming than bothering to load ROM Manager just to tell it the same thing. I don't keep any other zips in the root of the SD card besides FlashBack21 and 15, so the update.zip for ClockWork is always right there easily accessible without scrolling through a list.
And I won't lie, ClockWork Mod definitely has a different approach to the naming of it's menu options and organization, and even naming of those menu items, so it doesn't surprise me that you didn't know that the USB mount option did exist - in a weird place, if you ask me. Makes sense only in hindsight.
Something just rang a bell so I loaded ClockWork Mod re: signature verification. I would have brought this up a LONG time ago, but I honestly just didn't remember it until now, I swear.
ClockWork Mod DOES have signature verification, at least as a menu toggle.
In CWM's main menu, choose "install zip from sdcard". You'll see the third option in the list is "toggle signature verification". If I choose it now it then says at the very bottom of the recovery screen "Signature Check: Enabled". This setting doesn't stick between reboots (tested), although they could probably set it up so that it does by one of two methods:
1. Writing a settings file on the SD card which the recovery reads when loaded.
2. Actually modifying the update.zip as necessary to make this setting permanent until it's re-toggled.
I think where the confusion lies is that if you actually use ROM Manager the way that it's meant to when flashing a ROM, you'll never get the opportunity to see the menu option for signature verification as I believe that ROM Manager causes CWM to automatically reboot after the flash.
I rarely even enter ROM Manager as I mentioned above, so I guess that's how I got a little bit more familiar with the varying contents of the CWM menus. I never toggled sig verification on before except a very long time ago as a test to see what it did - but I just didn't ever think about it ever again after that.
I will probably toggle it on from now on, though.
I don't know what the "toggle script asserts" option below that is, though. Any idea so that I don't have to search?
Back to how I originally started this post. I was going to say that despite CWM not verifying the signature (by default - now that I know), I like the ability to organize my various flashable items in my favorite hierarchy of folders too much to revert back to Amon RA for typical flashing. Now that I know there's no reason to, I won't feel as lazy.
Also, I see now that in CWM v2.5.0.7 that they renamed the "partitions" menu to "mounts and storage". Still slightly confusing, but oh well.
Wasn't it speculated or more that Amon RA may not wipe Dalvik correctly when Cache To Cache is used? Did anyone come to any definitive conclusion regarding that?
roirraW "edor" ehT said:
Something just rang a bell so I loaded ClockWork Mod re: signature verification. I would have brought this up a LONG time ago, but I honestly just didn't remember it until now, I swear.
ClockWork Mod DOES have signature verification, at least as a menu toggle.
Click to expand...
Click to collapse
While I have seen this before myself, the one time that I tried to use it in Clockwork with a known-good .zip file it gave an error message. In other words, this passed Amon signature check, successfully installed on both recoveries, yet gave an error when I tried to set it.
Maybe I was reading the error message wrong, though.
Wasn't it speculated or more that Amon RA may not wipe Dalvik correctly when Cache To Cache is used? Did anyone come to any definitive conclusion regarding that?
Click to expand...
Click to collapse
I can't see how it wouldn't. Wiping Dalvik formats the /cache partition, and the /cache partition with cache2cache is holding both the system Dalvik cache (the one that you want to wipe when there has been a change in the Android system files) as well as the third party app cache (normally in /data.) It's definitely true, though, that Clockwork does a more thorough Nandroid backup and restore, as it backs up and restores /cache, the SD card's /.android_secure folder (where Froyo/GB store apps moved to SD) as well as ext partitions on the SD card (where 2.1 ROMs store apps2sd.)
At this point in time it's beginning to look like the OP did a "drive-by" posting, so I suppose it's Ok to continue with the OT discussion.
doogald said:
While I have seen this before myself, the one time that I tried to use it in Clockwork with a known-good .zip file it gave an error message. In other words, this passed Amon signature check, successfully installed on both recoveries, yet gave an error when I tried to set it.
Click to expand...
Click to collapse
Same experience here. From that I concluded that it doesn't work correctly.
I suppose it could be set up to reject the "test key" signature, as it really isn't a private key (cuz everybody has it), but that would make it useless for Eris dev ROMs.
doogald said:
While Wiping Dalvik formats the /cache partition
Click to expand...
Click to collapse
Eh?
That's counterintuitive. I thought Amon_RA only wipes /cache when you do a "wipe data/factory reset". Is clockwork different in this regard?
bftb0 said:
That's counterintuitive. I thought Amon_RA only wipes /cache when you do a "wipe data/factory reset". Is clockwork different in this regard?
Click to expand...
Click to collapse
I was actually talking about Amon's, and I am probably very wrong about that - I hadn't really checked. Still, all that cache2cache does is move /data/dalvik-cache to /cache/dalvik-cache and create a symlink so /data/dalvik-cache points to /cache/dalvik-cache, so any procedure that wipes /cache/dalvik-cache and even /data/dalvik-cache is going to wipe Dalvik just fine with cache2cache installed, right?
doogald said:
I was actually talking about Amon's, and I am probably very wrong about that - I hadn't really checked. Still, all that cache2cache does is move /data/dalvik-cache to /cache/dalvik-cache and create a symlink so /data/dalvik-cache points to /cache/dalvik-cache, so any procedure that wipes /cache/dalvik-cache and even /data/dalvik-cache is going to wipe Dalvik just fine with cache2cache installed, right?
Click to expand...
Click to collapse
Well, when Amon_RA is performing installs or Nandroids, it mounts the "data" and "system" partitions on the normal mount points, namely /data and /system, respectively.
So, yeah - if someone had cache2cache installed on their ROM, there would be a symlink
/data/dalvik-cache -> /cache/dalvik-cache
So if Amon_RA's strategy for "wiping dalvik cache" is to "mount /data and rm -rf /data/dalvik-cache", then yes - the folder at /cache/dalvik-cache would get wiped.
But if someone was NOT using cache2cache ( me! ), then the /cache/dalvik-cache folder, which normally contains entries for apps in /system/app (for Froyo and GB) would be preserved if you were "overflashing" a ROM, assuming that the dev did not place an explicit "format CACHE:" directive in his installer script.
When I am "overflashing" a ROM, I always look at the result with an adb shell to Amon_RA after everything is flashed, but before the first boot, and I manually remove /cache/dalvik-cache if it is there.
In that specific case (no use of cache2cache), there is no need to wipe the /data/dalvik-cache (because none of the apps in /data/app have changed), and a very good reason to wipe /cache/dalvik-cache (because many of the apps in /system/app could have changed).
Arguably, if someone is NOT using cache2cache, then a "wipe dalvik-cache" in Amon_RA wipes the wrong cache if the intent is to overflash a Froyo or Gingerbread ROM - because the /cache folder does not get wiped ... and that is precisely the location that you do want to wipe, because what is being replaced is the system apps.
I wonder how many rooters understand that subtlety.
And then, after that, I wonder if it is even necessary to worry about it - I thought that Android does a variety of signature checks on every boot, and if there is a mismatch between the .apk and the .dex, the .dex gets re-created automatically.... I think. (Ugh. I know how to check this experimentally, but it's a lot of work.)
doogald said:
While I have seen this before myself, the one time that I tried to use it in Clockwork with a known-good .zip file it gave an error message. In other words, this passed Amon signature check, successfully installed on both recoveries, yet gave an error when I tried to set it.
Maybe I was reading the error message wrong, though.
I can't see how it wouldn't. Wiping Dalvik formats the /cache partition, and the /cache partition with cache2cache is holding both the system Dalvik cache (the one that you want to wipe when there has been a change in the Android system files) as well as the third party app cache (normally in /data.) It's definitely true, though, that Clockwork does a more thorough Nandroid backup and restore, as it backs up and restores /cache, the SD card's /.android_secure folder (where Froyo/GB store apps moved to SD) as well as ext partitions on the SD card (where 2.1 ROMs store apps2sd.)
Click to expand...
Click to collapse
bftb0 said:
At this point in time it's beginning to look like the OP did a "drive-by" posting, so I suppose it's Ok to continue with the OT discussion.
Same experience here. From that I concluded that it doesn't work correctly.
I suppose it could be set up to reject the "test key" signature, as it really isn't a private key (cuz everybody has it), but that would make it useless for Eris dev ROMs.
Eh?
That's counterintuitive. I thought Amon_RA only wipes /cache when you do a "wipe data/factory reset". Is clockwork different in this regard?
Click to expand...
Click to collapse
It should also be noted that CWM wipes .android-secure (and /sd-ext, as well as Data and Cache) when you choose "wipe data/factory reset". Noticed this just now.
I wanted to test the signature verification since CWM had been updated recently for the Eris, at least with one ROM and it's associated files (GAPPS, zach.xtr's C2C). I flashed GSB v1.6 with verification turned on. It never reported any error flashing the zip. It did, however, claim that "gapps-gb-20110120-signed.zip" failed sig verification. I immediately flashed that zip via Amon RA and it flashed just fine.
zach.xtr's C2C passed CWM's sig verify, though.
I'm doing research to see if I can find any more information on this behavior.
bftb0 said:
Well, when Amon_RA is performing installs or Nandroids, it mounts the "data" and "system" partitions on the normal mount points, namely /data and /system, respectively.
So, yeah - if someone had cache2cache installed on their ROM, there would be a symlink
/data/dalvik-cache -> /cache/dalvik-cache
So if Amon_RA's strategy for "wiping dalvik cache" is to "mount /data and rm -rf /data/dalvik-cache", then yes - the folder at /cache/dalvik-cache would get wiped.
But if someone was NOT using cache2cache ( me! ), then the /cache/dalvik-cache folder, which normally contains entries for apps in /system/app (for Froyo and GB) would be preserved if you were "overflashing" a ROM, assuming that the dev did not place an explicit "format CACHE:" directive in his installer script.
When I am "overflashing" a ROM, I always look at the result with an adb shell to Amon_RA after everything is flashed, but before the first boot, and I manually remove /cache/dalvik-cache if it is there.
In that specific case (no use of cache2cache), there is no need to wipe the /data/dalvik-cache (because none of the apps in /data/app have changed), and a very good reason to wipe /cache/dalvik-cache (because many of the apps in /system/app could have changed).
Arguably, if someone is NOT using cache2cache, then a "wipe dalvik-cache" in Amon_RA wipes the wrong cache if the intent is to overflash a Froyo or Gingerbread ROM - because the /cache folder does not get wiped ... and that is precisely the location that you do want to wipe, because what is being replaced is the system apps.
I wonder how many rooters understand that subtlety.
And then, after that, I wonder if it is even necessary to worry about it - I thought that Android does a variety of signature checks on every boot, and if there is a mismatch between the .apk and the .dex, the .dex gets re-created automatically.... I think. (Ugh. I know how to check this experimentally, but it's a lot of work.)
Click to expand...
Click to collapse
I certainly didn't know this. Very interesting, thank you!
I Agree
roirraW "edor" ehT said:
It should also be noted that CWM wipes .android-secure (and /sd-ext, as well as Data and Cache) when you choose "wipe data/factory reset". Noticed this just now.
I wanted to test the signature verification since CWM had been updated recently for the Eris, at least with one ROM and it's associated files (GAPPS, zach.xtr's C2C). I flashed GSB v1.6 with verification turned on. It never reported any error flashing the zip. It did, however, claim that "gapps-gb-20110120-signed.zip" failed sig verification. I immediately flashed that zip via Amon RA and it flashed just fine.
zach.xtr's C2C passed CWM's sig verify, though.
I'm doing research to see if I can find any more information on this behavior.
I certainly didn't know this. Very interesting, thank you!
Click to expand...
Click to collapse
I agree yes, thank you!
A few weeks ago my SD card went bad on me. I have been using Gingershedbread as my ROM and see there are some updates, however, since I don't have an SD card, the "normal" method of loading the zip onto the SD card obviously won't work for me.
My question is: Is there a way to flash a ROM zip from a pc (windows) to my phone without an SD card? I know you can put the zip on the data partition, then use "recovery --update_package=DATA:rom.zip" (through adb), however, when trying to copy the rom I get a message saying that there is no space left.
As of now, the only thing I know of is to do a full wipe and factory reset, then push the ROM zip to my phone, but I don't necessarily want to do this every time.
I have also tried fastboot and using mkyaffs2image to create a system.img from the ROM's system folder in the zip file, but I am not doing something right.
I run "mkyaffs2image c:\rom\system\ c:\system.img"
then with my phone in fastboot, I "fastboot flash system c:\system.img"
and "fastboot flash boot c:\rom\boot.img".
I restart the phone in recovery mode, load gapps and xtrCache, but then it reboots, sits on black screen for a few seconds, then reboots into recovery.
I have tried erasing system and boot first, but that didn't seem to help.
I first tried just flashing system.img, but that didn't work.
Not sure what I am doing wrong. Is there a way to take a ROM zip and create a system.img and boot.img that can be flashed through fastboot without an SD card? OR, is it possible to flash a ROM zip without transferring the file to my phone first? Any help would be appreciated.
I don't think that there is an answer to your question which is both complete and also short.
So, here goes with the long answer.
First, a yaffs2 image file (e.g. system.img) is not compressed, so it is quite large - for things like the HTC factory/stock ROMs, it can be bigger than the cache partition. I don't know if the cache partition is actually used when you push things with fastboot, but experimentally, I have run into the problem that when attempting to do a
Code:
fastboot flash system my-yaffs2-system.img
fastboot gives you get an error about being out of room.
Second, and more importantly, the file modes (permissions) and user:group ownership of files in the /system mount point are extremely critical to proper operation of Android. If you have files sitting on a Windoze machine filesystem (either FAT32 or NTFS), all this information will be lost even before you create your "yaffs2" image file. (Not only that, but all symbolic links will be missing, too). This is why you observe that ROM files have instructions in their "update-script" (or "updater-script") command files for setting file & directory ownership, file permission modes, creating symlinks, et cetera.
Third - even if you use a linux OS to unpack yaffs2 images, and run as root when you are doing so, a lot of the "unyaffs" programs that are lying around do not even bother to extract things like user:group ownership or file modes - so you are basically screwed as soon as you unpack a yaffs2 image file on a PC, no matter whether it is Windows or Linux/Unix/OS-X.
Fourth, I am not sure that it is even a good idea in the first place to be "flashing" yaffs2 images. The "fastboot flash" command merely writes whatever you pass to it as a long linear blob of bytes, and there is no evidence to suggest that the yaffs formatting used in the archive is the same formatting used by the kernel. When "Nandroid" runs to restore a system.img or data.img file onto the phone, it does not write the image as a linear blob of bytes: it actually mounts the filesystem in question, cleans it up with a "rm -rf *" command, and then manually unpacks the yaffs2 image file into the mounted file system, one file at a time. (Fortunately in this case, it actually restores things like symlinks, file permissions, and file/directory user:group ownership information). This insures that the low-level yaffs2 formatting is *identical* to what the kernel expects, because it is the kernel that creates it.
There is a solution, but it is tedious enough that you really ought to ask the question, "Why don't I go out and buy a replacement SD card for 10 bucks instead of wasting a huge amount of time?"
Here's the solution:
You mount /system, clean it up manually, use adb to push the files recursively from wherever you have them stored on your PC, and then afterwards you run a custom (signed) installer .zip file which has been modified so that it only contains the "symlink" and permission-setting commands - you delete the "format" and "extract" commands from that command file, since you have manually put all the files into /system. Either that or you manually adjust the permissions and user:group ownership information by hand.
Obviously, since you don't have an /sdcard any longer, you will need to put this flashable, custom .zip file in /cache, and then create a one-line command file at /cache/recovery/command that points at the flashable .zip file in /cache. (This is the way the the OTAs work, and also how ROM Manager is able to customize the recovery when it boots).
Is this a lot of work? Yeah, you betcha.
It seems like running down to wally world to get a cheap SD card might be a little more fun.
Thanks for the info. I figured getting a new SD would be the best solution.
I knew about the symlink and file permission stuff and was trying to flash a system img then run a zip to ser that info., but couldn't get it to work. Sounds like using fastboot might be a bad idea.
For now I think I will just have to find a rom and stick with it for a while.
I am nearing an upgrade for a new phone and looking at the Thunderbolt, which comes with an SD so I don't want to buy one just yet.
Thanks for your help.
Sent from my ERIS GSBv2.1 using XDA App
kgunnIT said:
then run a zip to ser that info., but couldn't get it to work.
Click to expand...
Click to collapse
If you know how to sign ROMs, it's really not a hard hack to launch an installer of the type you mention.
And, now that I've just said that, I think I have another, simpler, idea.
But first:
[SIZE=+2]How To Launch a (smallish) .zip-based Flash That's Not On the SD Card.[/SIZE]
All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.
It literally is named "command", i.e.: /cache/recovery/command
... and it is a simple text file with as few as one line(s) in it.
Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:
--update_package=CACHE:filename.zip
So, if you are trying to get an installer to run without an SD card, you would:
1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.
After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so
.... wait for it .....
... wait for it ....
it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.
So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.
It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )
bftb0
bftb0 said:
If you know how to sign ROMs, it's really not a hard hack to launch an installer of the type you mention.
And, now that I've just said that, I think I have another, simpler, idea.
But first:
[SIZE=+2]How To Launch a (smallish) .zip-based Flash That's Not On the SD Card.[/SIZE]
All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.
It literally is named "command", i.e.: /cache/recovery/command
... and it is a simple text file with as few as one line(s) in it.
Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:
--update_package=CACHE:filename.zip
So, if you are trying to get an installer to run without an SD card, you would:
1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.
After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so
.... wait for it .....
... wait for it ....
it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.
So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.
It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )
bftb0
Click to expand...
Click to collapse
You always find the one thousand and ONETH way to skin a cat. Hehehehe...
Thankyou so much for this this alowed me to flash a rom on my phone which can't detect any sd cards and i stupidly wiped it before relising the sd card wasnt being detected!
sum_guy55 said:
Thankyou so much for this this alowed me to flash a rom on my phone which can't detect any sd cards and i stupidly wiped it before relising the sd card wasnt being detected!
Click to expand...
Click to collapse
very good, sum_guy55!
At least all that typing wasn' t in vain.
Out of curiosity, how big was the ROM file you used?
bftb0
Been meaning to post this:
Thanks for your posts roirraW "edor" ehT and bftb0 for posting this. I also was able to clear the cache and push the ROM and update.
However, I have xtrCMCache2cache on my phone, so the dalvik-cache was moved from /data/ to /cache/. After doing a wipe of dalvik-cache from Amon recovery, the folder in /cache/ was not emptied out. I went ahead and cleaned it manually, which freed up enough space to push the ROM.
Is this behavior expected using cache2cache and wiping dalvik-cache from recovery? I guess it would be since the dalvik-cache was moved.
Anyway, after clearing the dalvik folder, I was able to push GSBv2.4 to my phone, as well as gapps and xtrCMCache2cache, a total of almost 80 MB. Rebooted and all was well.
Thanks again for your help.
kgunnIT said:
Been meaning to post this:
Thanks for your posts roirraW "edor" ehT and bftb0 for posting this. I also was able to clear the cache and push the ROM and update.
However, I have xtrCMCache2cache on my phone, so the dalvik-cache was moved from /data/ to /cache/. After doing a wipe of dalvik-cache from Amon recovery, the folder in /cache/ was not emptied out. I went ahead and cleaned it manually, which freed up enough space to push the ROM.
Is this behavior expected using cache2cache and wiping dalvik-cache from recovery? I guess it would be since the dalvik-cache was moved.
Anyway, after clearing the dalvik folder, I was able to push GSBv2.4 to my phone, as well as gapps and xtrCMCache2cache, a total of almost 80 MB. Rebooted and all was well.
Thanks again for your help.
Click to expand...
Click to collapse
It was all bftb0. Interesting, I had once asked if cache was definitely wiped from Amon after it was moved. The consensus was that it should. I shall be anticipating some light shed on this.
Sent from my Gingerbread Eris via Tapatalk
Well, Amon_RA has no idea whether you are using cache2cache; I suppose we would need to look at the code to figure out how it behaves.
If it mounts /data and then does something like
rm -rf /data/dalvik-cache
there is a chance that the symbolic link is not followed, which would explain what kgunnIT observed.
Normally, if you are flashing a new ROM in a full-wipe fashion, the " wipe data/factory reset" menu option clears both /data and /cache, so in that case it is irrelevant that the "wipe dalvik-cache" is a no-op.
If you are overflashing, it's not obvious that you need to wipe the dalvik-cache... at least for the market apps normally stored in /data/app, although it seems like it would be a good idea to do so, as the system apps could be changing.
Note that even when cache2cache is not in use, the Amon_RA menu item "wipe dalvik-cache" never works as intended for froyo & gingerbread ROMs - the system apps have their dalvik-cache stored in /cache, and this never gets touched by Amon_RA with that menu operation.
BTW... for what it's worth, the ClockworkMod recoveryhas a menu entry for wiping only the cache.
bftb0
bftb0 said:
BTW... for what it's worth, the ClockworkMod recoveryhas a menu entry for wiping only the cache.
bftb0
Click to expand...
Click to collapse
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
kgunnIT said:
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
Click to expand...
Click to collapse
There is a version of Amon_RA (the trackball-optional version) that also allows you to format cache. You can find out more about it here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
That said, if you have ROM Manager, you can have Clockwork Recovery start as a stub within Amon_RA just from ROM Manager (the first option copies a file called update.zip to the root of your SD card, and the second, "Reboot into Recovery", starts Amon_RA with a script to flash update.zip, which starts Clockwork.) In fact, once update.zip is on the SD card, you can start Amon_RA as you always do, go to the Flash a zip from SD card menu, choose update .zip, and it will start Clockwork, if you want to do it that way. However, the drawback to this is that you can't go back to Amon_RA without shutting down the phone and then restarting in Recovery again, so I just find it easier to use the trackball-optional version of Amon_RA.
I think every person who has bricked their Eris while running Clockwork was running Clockwork Recovery as their main recovery image, and not in the way that I described in the last paragraph. (Though don't hold me to that ...)
kgunnIT said:
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
Click to expand...
Click to collapse
I've been using it through ROM Manager since last August or so, I use it all the time.
My HTC Desire VC (T328d) was rooted and running Android OS 4.0.3 (ics).
In recovery mode, I accidentally formatted /system folder (from internal phone memory).
This is because the recovery mode is all in chinese language and I did a huge mistake.
The phone cannot boot showing HTC logo screen and no boot sound.
I've downloaded the kernel for this device at htcdev.com and I don't know how to use it and what it is for.
Fortunately, I can enter recovery mode. My friend has the same device and his is not rooted yet. Maybe I can get some files from him.
Any solution, please?
Learn Chinese?
Flash a rom?
You should ask in a Desire forum tho
zeppelinrox said:
Learn Chinese?
Flash a rom?
You should ask in a Desire forum tho
Click to expand...
Click to collapse
I can't find the rom ... can u please help me?
There is no forum for my device. Only for Desire, Desire HD, Desire V ,.........
Looks like your best shot is to root your friends phone, do a nandroid backup, restore it to yours, then reset to factory defaults.
Don't forget to use V6 SuperCharger afterwards... lol
please tell me
zeppelinrox said:
Looks like your best shot is to root your friends phone, do a nandroid backup, restore it to yours, then reset to factory defaults.
Don't forget to use V6 SuperCharger afterwards... lol
Click to expand...
Click to collapse
Thanks for your advice. But, I don't know how to do nandroid backup. The instructions say that it is apk app. I can't even boot my phone and how can I use apk ? In addition, now I installed a recovery from china site (for Desire VC specifically) and it contains backup and restore function. Is it the same with Nandroid Backup or CWM ?
Can you instruct me in some steps, please ?
erizchen said:
Thanks for your advice. But, I don't know how to do nandroid backup. The instructions say that it is apk app. I can't even boot my phone and how can I use apk ? In addition, now I installed a recovery from china site (for Desire VC specifically) and it contains backup and restore function. Is it the same with Nandroid Backup or CWM ?
Can you instruct me in some steps, please ?
Click to expand...
Click to collapse
Yes, the backup option you see in recovery is Nandroid backup. Please be carefull in formatting system, it would wipe your ROM. Always take nandroid backup before you playing with other Rom.
Here you go,
1. Take nandroid backup of your friends ROM
2. Place the backup into your sd card( backup available in clockwork folder in ur friends mobile. Just copy the entire clockwork folder and paste in ur sd card. Now mount the sdcard in ur mobile)
3. Reboot in recovery.
4. Wipe cache and dalvik
5. Restore from nandroid.
Let me know this helps..
Cyb0rgz said:
Yes, the backup option you see in recovery is Nandroid backup. Please be carefull in formatting system, it would wipe your ROM. Always take nandroid backup before you playing with other Rom.
Here you go,
1. Take nandroid backup of your friends ROM
2. Place the backup into your sd card( backup available in clockwork folder in ur friends mobile. Just copy the entire clockwork folder and paste in ur sd card. Now mount the sdcard in ur mobile)
3. Reboot in recovery.
4. Wipe cache and dalvik
5. Restore from nandroid.
Let me know this helps..
Click to expand...
Click to collapse
What does "dalvik" mean ?
I've never heard of it. Can u explain me a little?
erizchen said:
What does "dalvik" mean ?
I've never heard of it. Can u explain me a little?
Click to expand...
Click to collapse
Dalvik is virtual machine that runs Android Apps on Android. Dalvik-cache is the cache area for Dalvik VM, it is created when the Dalvik VM optimizes your app for running.
Dalvik is the virtual machine that is used by Android. It is generally thought of as a java virtual machine, although this is not precisely correct. It uses an object model that is identical to java, and it's memory model is also nearly equivalent. But the
Accordingly, it uses a completely different bytecode than java. However, the Android SDK includes the dex tool to translate java bytecode to dalvik bytecode, which is why you are able to write Android applications in java.
When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application.
Cyb0rgz said:
Dalvik is virtual machine that runs Android Apps on Android. Dalvik-cache is the cache area for Dalvik VM, it is created when the Dalvik VM optimizes your app for running.
Dalvik is the virtual machine that is used by Android. It is generally thought of as a java virtual machine, although this is not precisely correct. It uses an object model that is identical to java, and it's memory model is also nearly equivalent. But the
Accordingly, it uses a completely different bytecode than java. However, the Android SDK includes the dex tool to translate java bytecode to dalvik bytecode, which is why you are able to write Android applications in java.
When you install an application on Android, it performs some modifications and optimizations on that application's dex file (the file that contains all the dalvik bytecode for the application). It then caches the resulting odex (optimized dex) file in the /data/dalvik-cache folder, so that it doesn't have to perform the optimization process every time it loads an application.
Click to expand...
Click to collapse
Thanks alot for your explanation.
But, I don't have any setting to clear dalvik. Anyway to do so?
These are in my list of recovery menu:
1 - Reboot the system
2 - Select Update
3 - Restore the factory
4 - Empty the cache
5 - Backup and recovery
6- Mount storage
7 - Advance
- Empty the battery status
- Reporting errors
- Keys test
- Card partition
- Permissions repair
8 - Shutdown
I wish to succeed with nandroid backup and restore method.
erizchen said:
Thanks alot for your explanation.
But, I don't have any setting to clear dalvik. Anyway to do so?
These are in my list of recovery menu:
1 - Reboot the system
2 - Select Update
3 - Restore the factory
4 - Empty the cache
5 - Backup and recovery
6- Mount storage
7 - Advance
- Empty the battery status
- Reporting errors
- Keys test
- Card partition
- Permissions repair
8 - Shutdown
I wish to succeed with nandroid backup and restore method.
Click to expand...
Click to collapse
Your recovery is not CWM recovery.
You must flash CWM recovery first. With CWM recovery, you can find "wipe delvik cache"
under Advance menu.
erizchen said:
I wish to succeed with nandroid backup and restore method.
Click to expand...
Click to collapse
It's easy. Just try to do all steps with patience. If you have any doubts, please do clear it. Don't assume anything just few mins of Googling will solve major issues..
I will help as much as I can to get things works well in your desire cheers
Cyb0rgz said:
It's easy. Just try to do all steps with patience. If you have any doubts, please do clear it. Don't assume anything just few mins of Googling will solve major issues..
I will help as much as I can to get things works well in your desire cheers
Click to expand...
Click to collapse
Millions of Thanks to you all ... I can do it successfully :victory:
I just backup my friend's ROM (which was updated by him).
And I restored all of his ROM.
My device is being well now ..... but still problem there are errors for wifi and bluetooth
I can't switch on wifi and bluetooth.
Below the "wifi" text, it shows "error".
:angel: :angel:
I've tried the ways from here and there , but it didn't work
Please help me with this again.
Am I a problem maker ?
erizchen said:
Millions of Thanks to you all ... I can do it successfully :victory:
I just backup my friend's ROM (which was updated by him).
And I restored all of his ROM.
My device is being well now ..... but still problem there are errors for wifi and bluetooth
I can't switch on wifi and bluetooth.
Below the "wifi" text, it shows "error".
:angel: :angel:
I've tried the ways from here and there , but it didn't work
Please help me with this again.
Am I a problem maker ?
Click to expand...
Click to collapse
Try all basic things, like clearing RAM, Booting your phone etc. If its not solved, try to flash the kernel via recovery. Please ensure that you are s-off for this. Even after flashing the kernel that issue persists, please check your radio (baseband) is latest. Else update the radio. I guess, flashing kernel will solve the issue.
Please let me know whether you are s-off and rooted.
Tips: its my personal advice to be s-off (your warranty voids)
Edit:
If you are HTC.dev unlocked and s-on then follow below steps to flash the kernel.
http://forum.xda-developers.com/showthread.php?t=1752270
Cyb0rgz said:
Try all basic things, like clearing RAM, Booting your phone etc. If its not solved, try to flash the kernel via recovery. Please ensure that you are s-off for this. Even after flashing the kernel that issue persists, please check your radio (baseband) is latest. Else update the radio. I guess, flashing kernel will solve the issue.
Please let me know whether you are s-off and rooted.
Tips: its my personal advice to be s-off (your warranty voids)
Edit:
If you are HTC.dev unlocked and s-on then follow below steps to flash the kernel.
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
My device is not s-off yet. I've just unlocked with htcdev. I searched s-off for this device but i can't find and don't know how to.
I have kernel downloaded from htc official web. Can i flash it with s-on ?
PRE REQUISITES:
1. ROOTED/UNLOCKED Phone.
2. HTC Sync Drivers (Install HTC Sync, it will install necessary drivers; Make sure HTC sync is not active; Just Exit from HTC Sync if its running)
3. Android SDK/Fast boot and Adb installed.
4. ES or ROOT Explorer (Available in google play)
*
<<PLEASE TAKE NANDROID BACKUP>>
1.* Follows Steps 1 to 5 from This thread, http://forum.xda-developers.com/showthread.php?t=1752270
2.* Extract the bcm4329.ko from the your kernel.zip
*
[ with Root Exploror or ES Explorer ]
1. touch Mount R/W
2. copy bcm4329.ko to /system/lib/modules
3. long press on the bcm4329.ko and select Permissions then check read, write for owner, read for group and read for others, click ok
4. long press again on the bcm4329.ko and select Change Owner, then pick 0-root for owner and pick 0-root for group, click ok
*
-----I am not responsible for any problems caused to your mobile-----
Cyb0rgz said:
PRE REQUISITES:
1. ROOTED/UNLOCKED Phone.
2. HTC Sync Drivers (Install HTC Sync, it will install necessary drivers; Make sure HTC sync is not active; Just Exit from HTC Sync if its running)
3. Android SDK/Fast boot and Adb installed.
4. ES or ROOT Explorer (Available in google play)
*
<<PLEASE TAKE NANDROID BACKUP>>
1.* Follows Steps 1 to 5 from This thread, http://forum.xda-developers.com/showthread.php?t=1752270
2.* Extract the bcm4329.ko from the your kernel.zip
*
[ with Root Exploror or ES Explorer ]
1. touch Mount R/W
2. copy bcm4329.ko to /system/lib/modules
3. long press on the bcm4329.ko and select Permissions then check read, write for owner, read for group and read for others, click ok
4. long press again on the bcm4329.ko and select Change Owner, then pick 0-root for owner and pick 0-root for group, click ok
*
-----I am not responsible for any problems caused to your mobile-----
Click to expand...
Click to collapse
From where do I have to find "boot.img" ?
I have only back up folder (ROM) from my friend's phone. And I just restored it (including boot.img) with CWM nandroid backup.
Is that the same with your instruction from step 1 to 5 ?
I can selectively restore "boot.img" with CWM nandroid recovery. Is that the same ?
In addition, the version of Kernel I downloaded is the same with my phone currently. I downloaded it from http://htcdev.com/devcenter/downloads
I got primodd-ics-crc-3.0.16-ead8920.zip file. When I extract it, I just found "bcm4329" folder under "primodd-ics-crc-3.0.16-ead8920/drivers/net/wireless" path. I can't find "bcm4329.ko"
Do you mean the driver in my system is not compatible with my phone after restore ?
erizchen said:
From where do I have to find "boot.img" ?
I have only back up folder (ROM) from my friend's phone. And I just restored it (including boot.img) with CWM nandroid backup.
Is that the same with your instruction from step 1 to 5 ?
I can selectively restore "boot.img" with CWM nandroid recovery. Is that the same ?
Click to expand...
Click to collapse
Boot.IMG is consists of kernel and ramdisk. They both necessary to start up the device, initializing the hardware, phone etc.
Since you are s-on, while placing the boot.img from nandroid, its not well placed. S-0N means, security on that doesn't allows to flash boot.img from nandroid.
I guess, every time you flash the via recovery boot.img is not placed in correct partition.
So, you have alternative method which allows to place the boot.img in correct path.That's why asked to do it via fastboot mode. Hope you understand.
In addition, the version of Kernel I downloaded is the same with my phone currently. I downloaded it from http://htcdev.com/devcenter/downloads
I got primodd-ics-crc-3.0.16-ead8920.zip file. When I extract it, I just found "bcm4329" folder under "primodd-ics-crc-3.0.16-ead8920/drivers/net/wireless" path. I can't find "bcm4329.ko"
Do you mean the driver in my system is not compatible with my phone after restore ?
Click to expand...
Click to collapse
Since you have problem only with WiFi and Bluetooth. You can skip fastboot method. bcm4329.ko is same as what you found in the kernel that you downloaded from HTC dev. (Just right click and check the file extension from your pc)
Your friends WiFi and Bluetooth are working fine. bcm4329.ko is responsible for WiFi and Bluetooth. Since you used recovery to restore nandroid, the bcm4329.ko is not placed in the system/lib/modules path. So manually you are placing it
To make it easier do the following
1. From your friends mobile, goto system/lib/modules copy bcm4329.ko file into your pc (use root file explorer)
2. Place that file in your sd card.
3. Then use root explorer and follow the steps mentioned in previous post.( 4 steps under root explorer)
Please let me know if this works.
PS: take nandroid before performing. No warranty for any tips provided. Please do search on google regarding kernel, android partition, bcm4329.ko etc.
Since I don't have pc, I can't help you more with respective links to other sites. Yes, It took much time to compose in my android touch screen.
Any shine on your WiFi / Bluetooth? Just curious to know about it..
Trying
Cyb0rgz said:
Any shine on your WiFi / Bluetooth? Just curious to know about it..
Click to expand...
Click to collapse
What does "shine" mean ?
My friend can't find "bcm4329.ko" such a file under /system/lib/modules
So, I'm trying to take matching the files under /system/lib/modules to know the missing files.
Any idea ?
My friend told me he has same files as mine in /system/lib/modules
These are the file list
bluetooth.ko
bnep.ko
btwilink.ko
cfg80211.ko
compat.ko
fm_drv.ko
hidp.ko
kineto_gan.ko
mac80211.ko
rfcomm.ko
wl12xx.ko
wl12xx_sdio.ko
He has only those files (not include "bcm4329.ko")
What should I do now ?
Hello,
I want to root my device with odin and chainfire. I know this basically leaves my recovery
untouched and modifies some system files so as to allow root apps to install themselves
in a way that they can run with root permssion.
1. I would like to know more about exactly what changes this kind of rooting does to the
device's file system.
2. I want to back up my ROM before this (not my data, just the program that factory
resets my device). That way, if I don't like something or something doesn't work I know
I can go back.
3. If once I root my device I install ClockworkMod as my recovery, does that mean my
old recovery is gone forever and I cannot get it back (not that I would probably need it
but just in case).
Can someone please help?
Thanks,
John Goche
johngoche99 said:
Hello,
I want to root my device with odin and chainfire. I know this basically leaves my recovery
untouched and modifies some system files so as to allow root apps to install themselves
in a way that they can run with root permssion.
1. I would like to know more about exactly what changes this kind of rooting does to the
device's file system.
2. I want to back up my ROM before this (not my data, just the program that factory
resets my device). That way, if I don't like something or something doesn't work I know
I can go back.
3. If once I root my device I install ClockworkMod as my recovery, does that mean my
old recovery is gone forever and I cannot get it back (not that I would probably need it
but just in case).
Can someone please help?
Thanks,
John Goche
Click to expand...
Click to collapse
1. It doesn't make any changes to the file system. Are you sure you're using the right term?
It tells you what it does here:
http://autoroot.chainfire.eu
2. You cannot back up your rom before rooting. You require a custom recovery to do this... unless the s3 toolbox does this??have a look. There is a nandroid over adb option
http://forum.xda-developers.com/showthread.php?t=1746680
Factory reset only manages /data I.e your stuff. It doesn't restore roms
3. The toolbox in 2. Can flash stock recovery
Sent from my GT-I9300 using Tapatalk 2
1. OK, so there's the ROM, and there's the filesystem. So it's not like in Unix where everything is a file.
I thought the ROM includes all the files which are part of the filesystem including /system/xbin and the
kernel. I thought the filesystem is part of the flashed ROM, not a separate thing.
2. I have adb installed. How do I do a nandroid over adb?
3. OK, so the default recovery just restores the /data partition.
johngoche99 said:
1. OK, so there's the ROM, and there's the filesystem. So it's not like in Unix where everything is a file.
I thought the ROM includes all the files which are part of the filesystem including /system/xbin and the
kernel. I thought the filesystem is part of the flashed ROM, not a separate thing.
2. I have adb installed. How do I do a nandroid over adb?
3. OK, so the default recovery just restores the /data partition.
Click to expand...
Click to collapse
1. File system = ext4, fat32, ntfs etc.
The ROM is a collection of files, within the /system partition and a kernel (boot.img). Of course there is a file system beneath this but its completely irrelevant to our discussions.
But cf auto root puts an app in /system/app and a binary in /system/bin. I suppose you're using "filesystem" in the way linux uses that to navigate to the /root of the OS.
2. Download the windows application I linked you to and follow the prompts to set up correctly. Then its a menu option
3. The stock recovery only WIPES the /data partition. It restores nothing
Sent from my GT-I9300 using Tapatalk 2
1. OK, the ROM is a collection of files. Now I'm in sync. So only two files are modified during the rooting process,
and app in /system/app (which does what?) and a binary in /system/bin (presumably a shell?).
2. Download the windows application I linked you to and follow the prompts to set up correctly. Then its a menu option
Where is the windows application you linked me. With all the clutter on the XDA pages I can hardly see it.
3. The stock recovery only WIPES the /data partition. It restores nothing
Thanks. Not sure why the data partition is not browsable with adb shell by default.
Thanks.
The su binary is the actual root. But you need a superuser app too. The app acts as a gatekeeper. When you run an app that requires root, superuser app opens and asks you if you want to allow or deny access to this app. Think of it as a level of protection
The link in my first post in my number 2. Answer is a specific thread for the windows application called unified toolbox. Just read all of post one. It tells you everything you need to know.
/data is protected because things that could otherwise be deleted can prevent android from booting up.
Not sure if you're familiar with Linux, but /data isn't quite the same as your home directory. That would be /sdcard. I suppose the Linux equivalent of /data would be /usr (although not really as despite their similarity, linux and android are not the same. Only really the kernel)
Sent from my GT-I9300 using Tapatalk 2
Hi folks,
Just wanting to understand Flash file behavior a little more, so several questions...
Question 1: Seeing that there are "SD" and "Internal EMMC" versions of flash files (recoveries, ROMs,etc), I'm wondering if they're specifically designed to write to SD or EMMC. Note, I didn't say "intended"... For example, if one were to flash a ZIP file, would it flash to its particular destination device no matter if I was booted from a Recovery located on SD or EMMC? Is it's destination "hard coded" into the ZIP? If so, does that mean it's impossible to accidentally flash a ZIP to EMMC if it was designed to go on SD, and vice versa?
Question 2 (well, question set #2): Do these flash files only add (or overwrite existing) files? If I created an extra (randomly named) file in a system partition and then flashed an entire ROM, would it erase the extra file?
TIA!
InUrKitchin said:
Hi folks,
Just wanting to understand Flash file behavior a little more, so several questions...
Question 1: Seeing that there are "SD" and "Internal EMMC" versions of flash files (recoveries, ROMs,etc), I'm wondering if they're specifically designed to write to SD or EMMC. Note, I didn't say "intended"... For example, if one were to flash a ZIP file, would it flash to its particular destination device no matter if I was booted from a Recovery located on SD or EMMC? Is it's destination "hard coded" into the ZIP? If so, does that mean it's impossible to accidentally flash a ZIP to EMMC if it was designed to go on SD, and vice versa?
Question 2 (well, question set #2): Do these flash files only add (or overwrite existing) files? If I created an extra (randomly named) file in a system partition and then flashed an entire ROM, would it erase the extra file?
TIA!
Click to expand...
Click to collapse
Answer 1: There are INT and SDC versions of the ROMs. The difference between them are different updater-scripts and vold.fstab files (you can get the SDC versions of the files from succulent's developer page on goo.im). If you flash any .zip file it won't do anything because recovery is reading for the ROM's files. ROM's without the SDC are flashing to the internal storage. Recovery can either be flashed on the internal or SD card. Either way, they do the same thing. So it is possible to flash the wrong .zip. If you flash an EMMC ROM and wanted the SD ROM it will flash to the EMMC.
Answer 2: Files do not automatically erase each other. If you upgrading from CM9 to CM10 you MUST wipe data/facotry reset, wipe cache, wipe dalvik cache. CM versions with different builds (ex. CM10.1 3/21/13 and CM10.1 5/21/13) don't need to be wiped because they are updates of the previous ROM. If you overwrite different versions problems will occur.
Let me see if I have this right.
Statement: Flashable ZIP files contain updater-scripts and vold.fstab files that determine where they will write to and (I'm assuming since you said 'scripts') other things that will occur during the flash. Accurate?
If the Statement is true about the scripts, then theoretically could the scripts in the ZIP flash wipe the data, cache, and dalvik cache automatically? Going down a slippery slope here, but taking this another step further (again if the scripts can do things like this) I assume there's a reason why they typically don't?
InUrKitchin said:
Let me see if I have this right.
Statement: Flashable ZIP files contain updater-scripts and vold.fstab files that determine where they will write to and (I'm assuming since you said 'scripts') other things that will occur during the flash. Accurate?
If the Statement is true about the scripts, then theoretically could the scripts in the ZIP flash wipe the data, cache, and dalvik cache automatically? Going down a slippery slope here, but taking this another step further (again if the scripts can do things like this) I assume there's a reason why they typically don't?
Click to expand...
Click to collapse
I'm far from an expert on knowing what the scripts do. I only know those two files change where the ROM will flash. I've tried making my own SDC versions of INT ROMs and have no luck. There may be something I'm missing, but I'm not sure.
When flashing newer builds of the same ROM you don't need to wipe data. I've never actually tried flashing a different ROM over another, I only know it's recommended to wipe data. Overwriting different ROMs is considered dirty flashing which can lead to a few problems with the ROM's behavior.
As I said before, I'm no expert. I learn from the things I've already done. Read up and learn about what you're trying to do and attempt it yourself. There's ways of recovering your Tablet if something wrong happens.
datallboy said:
...
Recovery can either be flashed on the internal or SD card. Either way, they do the same thing.
Click to expand...
Click to collapse
Emmc and SD Recovery are different versions and not interchangeable.
---------- Post added at 11:41 PM ---------- Previous post was at 11:18 PM ----------
InUrKitchin said:
Let me see if I have this right.
Statement: Flashable ZIP files contain updater-scripts and vold.fstab files that determine where they will write to and (I'm assuming since you said 'scripts') other things that will occur during the flash. Accurate?
Click to expand...
Click to collapse
Updater-scripts contains the action script for the installation.
Vold.fstab is one of the ROM system files and controls the mounting of storage partitions.
You can open both of these files with a text-editor (e.g., Windows Notepad) and take a peak to see what they do.
See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info on what parts of the NT get changed in Rooting & in Flashing a custom ROM.
If the Statement is true about the scripts, then theoretically could the scripts in the ZIP flash wipe the data, cache, and dalvik cache automatically? Going down a slippery slope here, but taking this another step further (again if the scripts can do things like this) I assume there's a reason why they typically don't?
Click to expand...
Click to collapse
The scripts don't wipe these partitions because it's not always necessary to wipe them. /data needs to get wiped only when switching between different ROMs or updating to a new ROM build based on a new Android release.
That makes sense. Thank you.