Help a noob?
AT&T Aria -- HTC Liberty/Intruder
ROM install (Liberty R12, CyanogenMod 6., ...) always fails on the first symlink command in the update-script. Since these are working for many others, I must be doing something wrong.
unrevoked3 run and installed (and rooted)
ClockworkMod Recovery v2.5.0.1 installed and working
do factory reset/data wipe, cache wipe and dalvik cache wipe every attempt
nandroid backup to sdram done, and restored, several times
this must be a FAQ?
advice? recommendations? pointers?
MTD partition sizes:
~ # cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00420000 00020000 "recovery"
mtd2: 002c0000 00020000 "boot"
mtd3: 0f000000 00020000 "system"
mtd4: 02800000 00020000 "cache"
mtd5: 0b920000 00020000 "userdata"
Default ATT 2.1update1 filesystem sizes:
# /data/busybox/df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 146.1M 0 146.1M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 240.0M 187.1M 52.9M 78% /system
/dev/block/mtdblock5 185.1M 35.5M 149.6M 19% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
/dev/block//vold/179:1
1.8G 1.2G 677.3M 64% /sdcard
thanks.
ROM update -- continued...
Looks like the /system partition runs out of space.
Probably because the format step of the update script fails. From /tmp/recovery.log immediately after the install fails:
...
Opening update package...
I:Update file path: /sdcard/liberated_aria_R012_signed.zip
Installing update...
I:Trying update-binary.
I:Trying update-script.
Iarsed META-INF/com/google/android/update-script
calling command show_progress
calling command format
Formatting SYSTEM:...
mtd: erase failure at 0x00000000
mtd: erase failure at 0x00020000
mtd: erase failure at 0x00040000
...
mtd: erase failure at 0x06c60000
mtd: erase failure at 0x06c80000
mtd: not erasing bad block at 0x06ca0000
mtd: erase failure at 0x06cc0000
mtd: erase failure at 0x06ce0000
...
mtd: erase failure at 0x0efc0000
mtd: erase failure at 0x0efe0000
calling command run_program
E:Can't run /tmp/run_program_binary
(No such file or directory)
calling command delete
Deleting files...
calling command delete_recursive
Deleting files...
W:Can't delete /system/xbin
(Directory not empty)
calling command copy_dir
Copying files...
minzip: Error writing 32768 bytes from zip file from 0xbeec8814: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/app/AccountAndSyncSettings.apk"
calling command symlink
E:Can't symlink /system/bin/bugreport
E:Failure at line 8:
symlink dumpstate SYSTEM:bin/bugreport
Installation aborted.
Read something about unlocking the NAND flash, but have no context. Also something about PC36IMG.zip, but again, no context.
Help a noob?
ROM update -- cont'd some more
More on the saga...
So I thought WTF do I have to lose, so from an adb shell (as root), did the old dreaded "rm -rf /system", which it did. Not recommended for your own, personal phone that you paid for, BTW.
Then tried to install liberated aria R012. It failed on the second command in the update-script. Uh oh.
Oh well. Time for a nandroid restore. Started restore from my last good backup and it just sat there, hung on restoring "resource". Uh oh again.
Popped out the battery, booted to recovery. thought WTF, maybe I finally really bricked it this time. Tried installing aria_shipped_rooted_signed.zip and it installed. It also booted successfully, needed settings set, but ran cell, WiFi. life good, or at least better.
So. Any idea if the brute force "rm -rf /system" deleted a hidden lock file or lock device, or ATT firmware that was preventing the ROM image update-scripts from running (specifically from wiping /system during the install)?
Or does "rooting" using unrevoked3 on the vanilla ATT Aria image not unprotect everything? (like NAND updating?)
FWIW, also tried installing VirtuousROM3.0, which installed, but didn't boot -- infinite loop refreshing the first HTC splash screen.
And liberated_aria_R012_signed.zip installed and ran successfully, including cell, wifi, yadda yadda. Running now.
Next step is to try installing CyanogenMod 6.0.... update.
I'll brick this thing yet...
It's a loner phone for development after all.
Having a huge issue with this myself right now. It's a shame this topic never gets resolved in any forum on the internet. Trust me i have looked. i am going to try to the command in adb.
i've never had this issue when flashing roms to my aria. sounds like a headache to deal with though.
Related
Since I've got DropBear and SSH on my Hero (MCR 3.2) I thought I'd try to remove APK-files via SSH, instead of using the USB-connection. I've successfully managed to connect to my phone, both via PuTTY and ConnectBot, but whenever I try to remove something from /system I get a message saying it's a read-only file system. What am I doing wrong? I should be able to perform what I've described above, right?
jeans2 said:
Since I've got DropBear and SSH on my Hero (MCR 3.2) I thought I'd try to remove APK-files via SSH, instead of using the USB-connection. I've successfully managed to connect to my phone, both via PuTTY and ConnectBot, but whenever I try to remove something from /system I get a message saying it's a read-only file system. What am I doing wrong? I should be able to perform what I've described above, right?
Click to expand...
Click to collapse
remount /system as rw
jeans2 said:
Since I've got DropBear and SSH on my Hero (MCR 3.2) I thought I'd try to remove APK-files via SSH, instead of using the USB-connection. I've successfully managed to connect to my phone, both via PuTTY and ConnectBot, but whenever I try to remove something from /system I get a message saying it's a read-only file system. What am I doing wrong? I should be able to perform what I've described above, right?
Click to expand...
Click to collapse
/system is by default read only, even for root.
Execute this in shell to remount it as read/write
mount -o remount,rw /dev/block/mtdblock3 /system
Eddie1506 said:
/system is by default read only, even for root.
Execute this in shell to remount it as read/write
mount -o remount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I'm guessing that line is similar to "adb remount"?
Is it something I have to execute each time I wan't to make changes in the /system-folder?
Yes, you can execute it through adb with "adb shell ...". I guess you have to execute it after reboot, I'm not really sure.
/system will stay mounted read/write until you reboot or remount to read only, however I'd always either reboot or remount it read only as soon as I was finished making changes, to be safe & avoid any accidental modifications/deletions. Also, yes, adb remount is just a quicker way to execute the same (or very similar) command.
cauli said:
/system will stay mounted read/write until you reboot or remount to read only, however I'd always either reboot or remount it read only as soon as I was finished making changes, to be safe & avoid any accidental modifications/deletions. Also, yes, adb remount is just a quicker way to execute the same (or very similar) command.
Click to expand...
Click to collapse
Okay, so mount -o rw /dev/block/mtdblock3 /system for mount and remount -o rw /dev/block/mtdblock3 /system for remount, right?
Btw, what does mtdblock3 contain?
jeans2 said:
Okay, so mount -o rw /dev/block/mtdblock3 /system for mount and remount -o rw /dev/block/mtdblock3 /system for remount, right?
Btw, what does mtdblock3 contain?
Click to expand...
Click to collapse
Last question first: /system System contains most of the operating system.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
&
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
to mount system read/write & read-only respectively. You might not need the '-t yaffs2' option which tells it what format the partition is, as it should auto detect the type, however the above should be most reliable.
cauli said:
Last question first: /system System contains most of the operating system.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
&
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
to mount system read/write & read-only respectively. You might not need the '-t yaffs2' option which tells it what format the partition is, as it should auto detect the type, however the above should be most reliable.
Click to expand...
Click to collapse
Okay, but what are the differences between the above and executing mount -o remount,rw (-t yaffs2) /system and mount -o remount,ro (-t yaffs2) /system, leaving the /dev/block/mtdblock3-part out?
remount isn't a command of itself (if you're using adb, adb remount is, so perhaps this is the source of that misapprehension) so that line above simply wouldn't do anything.
As to missing out the /dev/block/mtdblock3, aiui, in this case the mount command will attempt to infer the block device associated with the given mount point (ie with /system). Usually I think it relies on a config file /etc/fstab to do this, but that is often not present in Android ROMs (it seems to be absent from MCR 3.2 for one). In this particular case it works because the remount option implies it must use the device currently mounted at that mount point.
Essentially, you can often keep the command simple by missing out various parts, but if you have any kind of problem with it executing it's worthwhile specifying everything in case that is the cause of your problem. HTH
fyi:
Code:
$ adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 0aa00000 00020000 "system"
mtd4: 08200000 00020000 "cache"
mtd5: 0a5c0000 00020000 "userdata"
cauli said:
remount isn't a command of itself (if you're using adb, adb remount is, so perhaps this is the source of that misapprehension) so that line above simply wouldn't do anything.
As to missing out the /dev/block/mtdblock3, aiui, in this case the mount command will attempt to infer the block device associated with the given mount point (ie with /system). Usually I think it relies on a config file /etc/fstab to do this, but that is often not present in Android ROMs (it seems to be absent from MCR 3.2 for one). In this particular case it works because the remount option implies it must use the device currently mounted at that mount point.
Essentially, you can often keep the command simple by missing out various parts, but if you have any kind of problem with it executing it's worthwhile specifying everything in case that is the cause of your problem. HTH
Click to expand...
Click to collapse
Ah, it was a typo. Should've been "mount" and not "remount", just as you pointed out.
Thank you for the explanation! And to you too, kendong2.
Manually set variables as shown below
NOTE: I have found out that the Atrix also uses the name Mapphone_cdma in place of Olympus in their code. Why I do not know... I have noticed that the log.txt generated by bootmanager after repackaging the boot.img says that it cannot find a file named init.olympus.rc BUT shows no error with init.Mapphone_cdma.rc
NOTE: So far only works with CM7 as being the Phone ROM. I tried other ROM's as the phone ROM and I get a lot of errors.. I think it might be because of the structure of the CM7..
Code:
Filesystem [B]Size[/B] Used Available Use% Mounted
tmpfs 439.6M 32.0K 439.6M 0% /dev
/dev/block/mmcblk0p15
[B]629.9M[/B] 16.5M 581.4M 3% [U]/cache[/U]
/dev/block/[B]mmcblk1p1 (Depends on the ROM, this is the setting for CM7)[/B]
10.7G 3.2G 7.5G 30% [U]/sdcard[/U]
/dev/block/mmcblk0p12
[B]309.9M [/B]249.5M 44.4M 85% [U]/system[/U]
/dev/block/mmcblk0p16
[B]2.0G[/B] 620.0M 1.3G 32% [U]/data[/U]
[COLOR="DarkOrange"]What phone do you have?[/COLOR]
[COLOR="DarkOrchid"]Current setting =[/COLOR] [B]Olympus[/B] [I](<--generates errors on CM7, May work with other phone ROM's)[/I] [U]or[/U]
[B]Mapphone_cdma[/B] [I](<--generates no errors on CM7)[/I]
[COLOR="DarkOrange"]What is your sdcardblock? [/COLOR]
[COLOR="DarkOrchid"]Current setting = [/COLOR]/dev/block/[B]mmcblk1p1[/B]
[COLOR="DarkOrange"]What is your system size in mb?[/COLOR]
[COLOR="DarkOrchid"]Current setting =[/COLOR] [B]309mb[/B]
[COLOR="DarkOrange"]What is your data's size in mb?[/COLOR]
[COLOR="DarkOrchid"]Current setting =[/COLOR] [B]2.0G = 2000mb[/B] [I](I put 500mb)[/I]
[COLOR="DarkOrange"]What is your cache size in mb?[/COLOR]
[COLOR="DarkOrchid"]Current setting =[/COLOR] [B]629mb[/B] [I](I put 250mb)[/I]
NOTE: if you have a smaller SDcard, let's say 4gb, the above inputs can be slightly modified if you receive "Low Disk Space" when trying to install a ROM.zip. The cache size can be reduced to as low as 200mb and the data size I would go as low as 500mb. The only one that should stay UN-modified is the System size..
Follow these steps to get a successful install/force close error galore!
Boot into CWM
Make a backup of your current ROM
Boot your phone back up
Use Root explore, File Manager or what ever File browser you'd like to use
copy the boot.img from /sdcard/clockworkmod/backup/nameofyourbackup
to /sdcard/BootManager/phoneRom (Thanks to hatefuel19 for his discovery. Fix found Here!)
Start BootManager and now select "Setup Phone ROM"
(Should say successful, If not go back to step 4)
Go to "install Zips", then select ROM of your choice.
Select "Wipe System", "Wipe Data", "Wipe Cache" and select "Sot1"
(Wait for install to complete..........................)
Download the file from down below named "BootManager-rom1-Atrix.zip"
place "BootManager-rom1-Atrix.zip" in the slot1 folder replacing the update.zip (<---delete)
(it is not necessary to rename "BootManager-rom1-Atrix" to "update" but you can if you want)
Now that you have replaced the file boot back into CWM
select "zip from sdcard"
select "install zip from sdcard"
select "external sdcard"
Navigate to BootManager
select "Rom1"
select "BootManager-rom1-Atrix.zip"
***At this point you will now have a successful install***
(This does not mean it will boot up successfully, you will still get errors no matter what ROM your using)
I have done some research and talked to the dev of init2winit and when it shows the block being busy or not available that is because it's mounted.. Doh!! lol I didn't even think of that..
If you choose to boot the phone up "as is" (meaning whatever ROM you are using) you will get stuck at the moto-boot screen or it will boot up into the ROM and everything will force close on you. To get it back to normal just go;
back into CWM
select "backup/restore"
select "advanced restore"
and all you have to restore is the boot.img
****About the two files uploaded****
"BootManager-rom1-Atrix (original).zip"
This is a modified update.zip by init2winit just for the Atrix. But this one is lacking one file that is crucial for the phone to recognize the install
"BootManager-rom1-Atrix.zip"
This file contains everything that "BootManager-rom1-Atrix (original).zip" has but I replaced the the update-binary located in the zip under \META-INF\com\google\android with one from the Alien #4 ROM because the update-binary has information sensitive to our phone (do not touch the updater-script it has information to keep the ROM from installing over your current Phone ROM)
***Question For a Dev***
I uploaded both the .txt files that are generated by bootmanager and recovery. at the bottom of the log.txt it says the following errors;
blocks
cp: can't stat '/data/local/tmp/system/lib/modules/ext2.ko': No such file or directory
cp: can't stat '/data/local/tmp/system/lib/modules/mbcache.ko': No such file or directory
sed: /data/local/tmp/boot.img-ramdisk/init.vivow_ct.rc: No such file or directory
sed: /data/local/tmp/boot.img-ramdisk/init.vivow_ct.rc: No such file or directory
sed: /data/local/tmp/boot.img-ramdisk/init.vivow_ct.rc: No such file or directory
What are these files and are they named something different on the Atrix?
That is a normal error, it is part of a script for another phone but will not hinder the install in anyway on ours.
Disclaimer: Neither I nor anyone else is responsible if you brick, break or blow up your Atrix. Everything that YOU do is at YOUR OWN RISK!!
STILL in the process of getting the Atrix supported with BootManager
All Credit goes to Init2Winit Applications for the creation of this Awesome APP!
I'm in the process of getting The Olympus (Atrix) supported.
Stay Tuned!!
Wow this would be so cool I would definitely use if enough roms were supported for our phones. I was gonna post about this earlier just to let other users know so glad you did and getting some extra news bout it on the Atrix
Sent from my MB860 using XDA Premium App
WooOoOOooOooOOoW
ClearFire said:
I'm in the process of getting The Olympus (Atrix) supported.
Stay Tuned!!
Click to expand...
Click to collapse
Nice. Would love to have this app. Thanks. Patiently waiting...
jzaslice said:
Wow this would be so cool I would definitely use if enough roms were supported for our phones. I was gonna post about this earlier just to let other users know so glad you did and getting some extra news bout it on the Atrix
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
It should work with any ROM with the new installer and edify scripts.
So in the meantime, does anyone know have a line on the Atrix' settings for manual setup?
Incognitum said:
So in the meantime, does anyone know have a line on the Atrix' settings for manual setup?
Click to expand...
Click to collapse
Yes, they outline the steps for the "How to" on manual setup but unfortunately I tried that already and it does not work. It's taking init2winit some time to get us support and I suppose that's because our phone is one hell-of-a beast to tame
EDIT: I copied the directions for manual set-up if you would like to give it a go!
Manual set-up
Found in /system/build.prop at the line ro.product.board = Product Board:
In adb shell while in recovery type mount and look for sdcardSdcard Block:
In adb shell while in recovery type df -h and look for system size System Size:
In adb shell while in recovery type df -h and look for data size Data Size:
In adb shell while in recovery type df -h and look for cache size Cache Size:
thanks for the info! I'm curious what rom you tried it on/with. I noticed this morning when I flashed CM7-PB2 that it moved the internal SDcard to mnt/emmc... I wonder if changing where the SD card mounts could break the operation of the program. were you using the internal SD, or an external SD? Sorry if it sounds like the Spanish inquisition, I'm just picking your brain so I can start trying different configurations; maybe with a little trial and error we can get it working...
Incognitum said:
thanks for the info! I'm curious what rom you tried it on/with. I noticed this morning when I flashed CM7-PB2 that it moved the internal SDcard to mnt/emmc... I wonder if changing where the SD card mounts could break the operation of the program. were you using the internal SD, or an external SD? Sorry if it sounds like the Spanish inquisition, I'm just picking your brain so I can start trying different configurations; maybe with a little trial and error we can get it working...
Click to expand...
Click to collapse
Well I tried using internal and external SD card on both Ninja SF ROM by samcripp and Alien #2 by Kennethpenn. I have not flashed CM7 as I am waiting for a more stable build. Let me know how it goes for you though
So from stock OTA GB unlocked and rooted here are my results:
Product Board = olympus
So far so good, but the adb shell from recovery didn't go so hot. Here are my commands and the output
C:\root>adb shell mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p15 on /cache type ext3 (rw,nodev,noatime,nodiratime,errors=co
ntinue,data=ordered)
Click to expand...
Click to collapse
No SDcard block. Maybe use dev/block?
C:\root>adb shell df -h
Filesystem Size Used Available Use% Mounted
tmpfs 408.1M 32.0K 408.0M 0% /dev
/dev/block/mmcblk0p15
629.9M 16.8M 613.1M 3% /cache
Click to expand...
Click to collapse
Which values become the system, data, and cache sizes?
Also, is it normal to have to reflash my recovery every time I want to use it? Right after flashing it works great, but any other time I get the android with the white triangle screen
Ok, while you are in recovery menu you MUST go down to the Mount and Storage option on the phone and then mount the individual paths because in recovery everything is unmounted except for the cache. Then you type in those commands and you will get the following results..
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p15 on /cache type ext3 (rw,nodev,noatime,nodiratime,errors=co
ntinue,data=ordered)
/dev/block/mmcblk0p18 on /sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=00
00,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixe
d,errors=remount-ro)
Filesystem Size Used Available Use% Mounted
tmpfs 439.6M 32.0K 439.6M 0% /dev
/dev/block/mmcblk0p15
629.9M 16.5M 581.4M 3% /cache
/dev/block/mmcblk0p18
10.7G 3.2G 7.5G 30% /sdcard
/dev/block/mmcblk0p12
309.9M 249.5M 44.4M 85% /system
/dev/block/mmcblk0p16
2.0G 620.0M 1.3G 32% /data
In adb shell while in recovery type mount and look for sdcard, Sdcard Block: mmcblk0p18
In adb shell while in recovery type df -h and look for system size, System Size: 309.9M
In adb shell while in recovery type df -h and look for data size, Data Size: 2.0G
In adb shell while in recovery type df -h and look for cache size, Cache Size: 629.9M
and as to your second question;
No, it is not normal to have to re-flash your recovery every time after the first use.
Not sure which recovery you are using but it should always be the latest version available.
here is the latest Recovery that can only be used (flashed) if your bootloader is unlocked!
Is this app still being worked on for atrix support by default or is it going to stay at a manual setup
sent from my Atrix via XDA premium
marko! said:
Is this app still being worked on for atrix support by default or is it going to stay at a manual setup
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
The support is still being worked on, a lot of bugs (I'm assuming) to be worked out. Unfortunately though the manual setup does not work and I have tried every which way possible to get it to work.
Like I said previously, our device is too beastly to be easily tamed
Glad to hear that. Yes we definitally have a beast.
sent from my Atrix via XDA premium
I am, however, going to flash CM7 pre-beta build #3 today and I will try bootmanager app then as the CM7 build has a different set-up as to were things are located (Manual Set-up that is). I will report back if it works
Fingers Crossed!
Unfortunately I am getting no luck with Bootmanager on CM7....
Sorry guys! But stay tuned as I'm sure we will have support very soon!
I was drooling over this app when my buddy with an Inc1 showed it to me. Having it on the atrix would be epic.
10tonhammr said:
I was drooling over this app when my buddy with an Inc1 showed it to me. Having it on the atrix would be epic.
Click to expand...
Click to collapse
Yea I installed it on my boys Evo4g and it is super clean! Though my only issue is that in order to install zips on the ROM's in bootmanager, is that you have to install them through bootmanager and sometimes could cause a boot-loop (soft-brick) so I do recommend, when we get it, to make a habit of doing backups
EDIT: the boot-loop doesn't happen every time, but has happened twice
Can some confirm if I understand correctly
As I understand internal GS2 memory is divided into several partitions:
/dev/block/mmcblk0p9 on /system type ext4
/dev/block/mmcblk0p7 on /cache type ext4
/dev/block/mmcblk0p1 on /efs type ext4
nil on /sys/kernel/debug type debugfs
/dev/block/mmcblk0p10 on /data type ext4
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs
/dev/block/vold/179:11 on /mnt/sdcard type vfat
So as I understand in CWM recovery:
format data formats dev/block/mmcblk0p10 on /data type ext4
format system formats /dev/block/mmcblk0p9 on /system type ext4
format cache formats /dev/block/mmcblk0p7 on /cache type ext4
wipe data / factory reset - on stock deletes everything from dir /data or just some files from dir /data
wipe cash - deletes all files from from /cache or just some files from dir /cache
wipe dalvik- deletes all files from from /data/dalvik-cache or just some files from dir /data/dalvik-cache
format /sdcard formats /dev/block/vold/179:11 on /mnt/sdcard type vfat ????
format /emmc formats what????
In what partition is bootloader?
In what partition is kernel?
In what partition is CWM recovery?
Where are located download mode (home+down+power) system/files?
From recent experience I understood that nandroid is not doing backup of all partitions. EFS partition is not backed up.
What else is not backed up and what partitions are backed up?
What partition is backed up in nandroid boot.img file?
Don't mess with them until you really know what you are doing
if bootloader gets messed up then its a brick
I really don't want to have problem and that's why I'm asking.
When you know simple basics it much safer to change ROM's
Well, if you'd search before asking questions, you'd have the information already.
Basically:
Code:
0 '/tmp' 'ramdisk' '(null)' '(null)' 0
1 '/efs' 'ext4' '/dev/block/mmcblk0p1' '(null)' 0
2 '/boot' 'emmc' '/dev/block/mmcblk0p2' '(null)' 0
3 '/recovery' 'emmc' '/dev/block/mmcblk0p6' '(null)' 0
4 '/cache' 'ext4' '/dev/block/mmcblk0p7' '(null)' 0
5 '/system' 'ext4' '/dev/block/mmcblk0p9' '(null)' 0
6 '/data' 'ext4' '/dev/block/mmcblk0p10' '(null)' -16384
7 '/preload' 'ext4' '/dev/block/mmcblk0p12' '(null)' 0
' 0 '/sdcard' 'vfat' '/dev/block/mmcblk1p1' '/dev/block/mmcblk1
9 '/sdcard1' 'vfat' '/dev/block/mmcblk0p11' '(null)' 0
Bootloader is in p2 and p3.
Kernel is in p5.
Recovery is inside the kernel.
Download mode (home+down+power) system/files is in initramfs (also kernel, basically).
Boot.img file contains the kernel if I remember correctly.
If you're concerned about partitions, back them all up with dd. However, be careful goes without saying
Sure I was looking, but short and simple answer couldn't find
Thanx
And additional questions:
So if /system (/dev/block/mmcblk0p9) is deleted, then phone still should be able to boot into download or recovery mode? (because Bootloader is in p2 and p3; Kernel is in p5.)
Can it be that in boot.img is packed p2, p3, p5 partitions?
/system comes with the ROM, so yes - you can delete it and still have recovery.
Why don't you extract the boot.img and see what's in it?
Sure I've tried to extract but..
In phone "Nandroid browser" can't open
In windows "unyaffs" says "broken image file"
In windows "DiskInternals Linux Reader" also not working
If you search you will find the post that shows how to extract on SGS2 and tools required .
jje
limmes said:
In what partition is bootloader?
In what partition is kernel?
In what partition is CWM recovery?boot.img file?
Click to expand...
Click to collapse
i always formats system and boot in cwm 4.x.x but since 5.x.x only system is present, meaning formating boot is good but is more dangerous for all users to access.
formating system solves many issues.
What is the boot process used on the Minix Neo x5/x7? And what are the formats/contents of each NAND (aka ROM) partitions?
Code:
misc /dev/block/mtdblock0 4194304
kernel /dev/block/mtdblock1 8388608
boot /dev/block/mtdblock2 16777216
recovery /dev/block/mtdblock3 16777216
backup /dev/block/mtdblock4 402653184
cache /dev/block/mtdblock5 134217728 - /cache 126M ext4
userdata /dev/block/mtdblock6 4294967296 - /data 3.9G ext4
kpanic /dev/block/mtdblock7 4194304
system /dev/block/mtdblock8 536870912 - /system 511M ext4
user /dev/block/mtdblock9 11010048000- /mnt/sdcard 10.2G
What is the boot process for the Minix Android sticks and boxes? I want to know so I can understand/manipulate the configuration. I know that people to make up new 'rom's for the systems know how to produce these '.img's, but I haven't seen it documented for those who want to get in on the act. I know how this is done on some other Linux installations, but want to know how Minix does it for their Android system.
I can see that the 'system', 'cache', 'userdata' and 'user' are normal linux filesystems that can been seen by mounting them. I assume 'boot' is some compressed bootloader code -- perhaps not the usual Android bootloader. 'kernel' is the, perhaps compressed, binary executable for the kernel that must be loaded and executed? 'recovery' seems to be uncompressed (ie you can see meaningful strings in it) -- I thought it might be a duplicate (backup) of 'boot', but its not. 'backup' seems to be uncompressed as well. No clue what 'misc' has.
I assume that on power up, some real ROM (R/O memory) loads (and decompresses?) some code from the 'boot' partition and that code loads the kernel and some root filesystem and starts things up. I know what the /init program in Android does (reading the /init.rc and other files) and mounting other file systems etc.
Can anyone share a link to the source code, or a replacement build for the NAND partition images (ie ROM .img) so I can see what it does?
System is the ROM. Misc stores all kinds of settings. As for the code.... Visit source.android.com
Sent from my Nexus 4 using Tapatalk
Hi,
I would like to know the android boot process too.
I need to replace the splash boot logo but i am not sure where to find it in the boot process
Couple months ago, I tried to flash Android 6.0 on my S2 i9100 but it only recognized the first partition (2gb ) but the rest 14gb no. [ Sure, I did wipe cache partition, dalvik cache, data ]
So, I did some format with adb shell ( I deleted FactoryFS, Data, UMS partitions and change the format type to Fat32) and copied to internal storage. When I install it ( it takes like 3-5 minutes) and get this error
|Warning: No file_contextsdetected filesysstem ext4 for /dev/block/mmcblk0p9
| mount: failed to mount /dev/block/mmcblk0p9 at /system: Device or resource busy
| detected filesystem ext4 for /dev/block/mmcblk0p9 It stuck here for a while
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r: system_file: s0 failed: Operation on not supported on transport endpoint
set_metadata_recursive: some changes failed
E: Error in /emmc/cm12.... (status 7)
Installation aborted
press any key to continue.
After that, I tried again with Odin, I used Stock PIT and 12gb PIT ver to install Rom, still get the error above. Even when I use Odin to flash new Rom, Odin get stopped working.
[ I have tried many versions of CWM, Philz, TWRP,... but still Can't mount /sdcard ]
So how can I fix this problem?
Thanks for reading and helping me. Also sorry for my bad English.