Hi guys, Total Noob here.
I've been reading through the forums over the last week and am still at a total loss. Despite trying numerous things, nothing I've tried has worked.. If anything, I'm afraid I've made things worse.
The back story: The NC we have is a newer one purchased *just* over a year ago, given to my 10yr old daughter as a bday gift. It's never been rooted or modded in anyway whatsoever. Two weeks ago while she was playing a game on it, it locked up, and wouldn't power off. We let it sit for a couple of days for the battery to drain. After that, the battery wouldn't charge, the NC would not boot and the cable indicator stayed orange. So I purchased, and replaced the battery. I let it sit overnight after replacing the battery, and we got a green light. On boot up, it would hang at the 'N Screen', and do nothing more.
I tried running the NC recovery, but that only resulted in an "INSTALL FAILED" error message, and that was the last sign of life to have been seen coming out of the NC.
At this point, it will only boot off the SD card, (currently using an 8gb with CWR 6.0.1.2), I no longer get even the 'N screen' anymore. I've tried leapinlars partitioning and formatting .zips, I've tried every stock image I could find, but the result is always the same. No partitions are mounted, and nothing but errors are generated.
I've tried connecting through ADB, but 'ADB DEVICES" only returns:
Code:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
...and nothing more.
Since this NC is for my daughters use, I'm really not interested in rooting or opening up android for her, I'd really like it to be nothing more than stock, but at this point I'd be grateful just to see some sign of life come out of this thing. All help would be greatly appreciated.
I hope I've provided enough info, anybody have a clue whats going on here?
Some other screen grabs from adb:
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # ls -l
ls -l
drwxr-xr-x 2 root root 0 Jan 9 05:40 boot
drwxr-xr-x 2 root root 0 Jan 9 05:40 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 9 05:40 datadata
-rw-r--r-- 1 root root 2553 Jan 1 1970 default.prop
drwxr-xr-x 10 root root 2440 Jan 9 05:40 dev
drwxr-xr-x 2 root root 0 Jan 9 05:40 emmc
drwxr-xr-x 2 root root 0 Jan 9 05:40 etc
-rwxr-x--- 1 root root 98756 Jan 1 1970 init
-rwxr-x--- 1 root root 1415 Jan 1 1970 init.rc
dr-xr-xr-x 64 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwxrwxrwx 2 root root 0 Jan 9 05:40 rom
drwx------ 2 root root 0 Sep 21 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 9 05:40 sd-ext
drwxr-xr-x 2 root root 0 Jan 9 05:40 sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 9 05:40 tmp
-rw-r--r-- 1 root root 32 Jan 1 1970 ueventd.encore.rc
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 3825 Jan 1 1970 ueventd.rc
~ #
and
Code:
fdisk -l
returns nothing except for the command 'fdisk -l' being echoed back to the screen.
Even though I can boot with CWM; when booting CWM, it displays the following error messages
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When trying to install "NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip", I get:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a while
Done. YOU MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
Then, rebooting and installing "NookColor-emmc-format-partitions-5-6-7-8.zip" generates the following output instantly, with absolutely no delay when the formatting should be occuring:
Code:
-- Installing: /sdcard/NookColor-emmc-format-partitions-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Reformatting /system, /data, /cache, and /media
Reformatting /system (0p5)
This may take some time, please be patient
Reformatting /data (0p6)
This may take some time, please be patient
Reformatting /cache (0p7)
This may take some time, please be patient
Reformatting /media (0p8)
This may take some time, please be patient
Done.
Install from sdcard complete.
Trying "NookColor-emmc-repair-partition-2.zip", ends with:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partition-2.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if not found will return error message and repair will be aborted.
assert failed: mount("ext2", "EMMC", "/dev/block/mmcblk0p3", "/factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
and then after not making progress with those; trying "NookColor-emmc-stockrecovery-CWM6012asAlt.zip" returns:
Code:
-- Installing: /sdcard/NookColor-emmc-stockrecovery-CWM6012asAlt.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Installing Stock Recovery to EMMC with CWM 6.0.1.2 as Alternate
-----------------------------------------
Done
Install from sdcard complete.
, ...with still no recovery process being possible.
MaGoober said:
Some other screen grabs from adb:
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # ls -l
ls -l
drwxr-xr-x 2 root root 0 Jan 9 05:40 boot
drwxr-xr-x 2 root root 0 Jan 9 05:40 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 9 05:40 datadata
-rw-r--r-- 1 root root 2553 Jan 1 1970 default.prop
drwxr-xr-x 10 root root 2440 Jan 9 05:40 dev
drwxr-xr-x 2 root root 0 Jan 9 05:40 emmc
drwxr-xr-x 2 root root 0 Jan 9 05:40 etc
-rwxr-x--- 1 root root 98756 Jan 1 1970 init
-rwxr-x--- 1 root root 1415 Jan 1 1970 init.rc
dr-xr-xr-x 64 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwxrwxrwx 2 root root 0 Jan 9 05:40 rom
drwx------ 2 root root 0 Sep 21 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 9 05:40 sd-ext
drwxr-xr-x 2 root root 0 Jan 9 05:40 sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 9 05:40 tmp
-rw-r--r-- 1 root root 32 Jan 1 1970 ueventd.encore.rc
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 3825 Jan 1 1970 ueventd.rc
~ #
and
Code:
fdisk -l
returns nothing except for the command 'fdisk -l' being echoed back to the screen.
Even though I can boot with CWM; when booting CWM, it displays the following error messages
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When trying to install "NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip", I get:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a while
Done. YOU MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
Then, rebooting and installing "NookColor-emmc-format-partitions-5-6-7-8.zip" generates the following output instantly, with absolutely no delay when the formatting should be occuring:
Code:
-- Installing: /sdcard/NookColor-emmc-format-partitions-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Reformatting /system, /data, /cache, and /media
Reformatting /system (0p5)
This may take some time, please be patient
Reformatting /data (0p6)
This may take some time, please be patient
Reformatting /cache (0p7)
This may take some time, please be patient
Reformatting /media (0p8)
This may take some time, please be patient
Done.
Install from sdcard complete.
Trying "NookColor-emmc-repair-partition-2.zip", ends with:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partition-2.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if not found will return error message and repair will be aborted.
assert failed: mount("ext2", "EMMC", "/dev/block/mmcblk0p3", "/factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
and then after not making progress with those; trying "NookColor-emmc-stockrecovery-CWM6012asAlt.zip" returns:
Code:
-- Installing: /sdcard/NookColor-emmc-stockrecovery-CWM6012asAlt.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Installing Stock Recovery to EMMC with CWM 6.0.1.2 as Alternate
-----------------------------------------
Done
Install from sdcard complete.
, ...with still no recovery process being possible.
Click to expand...
Click to collapse
You need to type
fdisk -l /dev/block/mmcblk0
in ADB. That will show you the partition structure of emmc. I suspect your cylinder/head/sector count is messed up. That is why my zips appear to work, but do not.
Report here the output of the command.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
You need to type
fdisk -l /dev/block/mmcblk0
in ADB. That will show you the partition structure of emmc. I suspect your cylinder/head/sector count is messed up. That is why my zips appear to work, but do not.
Report here the output of the command.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Thanks for the suggestion leapinlar, I assumed fdisk -l would show all disk info by default if a specific disk wasnt specified. For some reason when I plugged the NC into the USB port today, My Win7 box did not recognize it or want to reload the drivers the same way it did last night, and I was unable to connect to the NC through ADB.
I will try to figure out that later on, or try to use ADB through my Fedora box when I get a chance. In the meantime, I once again tried your repair-partions.zip and copied CWM's error log, which is pasted below. Hopefully this gives some insight:
Starting recovery on Sun Jan 9 18:13:58 2000
framebuffer: fd 4 (1024 x 600)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p8 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.larry.20121021.181637
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Oct 21 18:17:05 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=larry
ro.build.host=larry-HP-Pavilion-dm4-Ubuntu
ro.build.tags=test-keys
ro.product.model=NookColor
ro.product.brand=bn
ro.product.name=encore
ro.product.device=encore
ro.product.board=encore
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=bn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
ro.build.product=encore
ro.build.description=encore-user 4.0.4 IMM76D 228551 release-keys
ro.build.fingerprint=bn/bn_encore/encore:4.0.4/IMM76D/228551:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=encore
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=30
ro.additionalmounts=/mnt/emmc;/mnt/usbdisk
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
ro.pm.awake_on_usb=1
ro.cwm.forbid_format=/boot
ro.sf.hwrotation=270
ro.emmc=1
com.ti.omap_compat=true
ro.magic.optimization=ZOMG
ro.com.android.dateformat=MM-dd-yyyy
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
alsa.mixer.playback.master=default
alsa.mixer.capture.master=Analog
ro.opengles.version=131072
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=(link removed)
ro.url.legal.android_privacy=(link removed)
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9-20121022-UNOFFICIAL-encore
ro.modversion=9-20121022-UNOFFICIAL-encore
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=encore
ro.revision=5
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
I:Update location: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a whileabout to run program [/tmp/repartition.sh] with 1 args
Archive: /tmp/boot.zip
inflating: boot.img
144522+0 records in
144522+0 records out
73995264 bytes (70.6MB) copied, 1.259857 seconds, 56.0MB/s
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 236032.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): No partition is defined yet!
Command (m for help): 4: unknown command
Command Action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Partition number (1-4): script result was [Done. You MUST REBOOT TO RELOAD THE PARTITION TABLE]
Done. You MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblk0p8
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
Click to expand...
Click to collapse
leapinlar said:
You need to type
fdisk -l /dev/block/mmcblk0
....
Click to expand...
Click to collapse
Okay, got adb working again. Here's the result:
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #
Well now, isnt that special?
So that got me curious and I took a look/see in the /dev/block folder:
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6
/dev/block # ls -l
ls -l
brw------- 1 root root 7, 0 Jan 9 18:13 loop0
brw------- 1 root root 7, 1 Jan 9 18:13 loop1
brw------- 1 root root 7, 2 Jan 9 18:13 loop2
brw------- 1 root root 7, 3 Jan 9 18:13 loop3
brw------- 1 root root 7, 4 Jan 9 18:13 loop4
brw------- 1 root root 7, 5 Jan 9 18:13 loop5
brw------- 1 root root 7, 6 Jan 9 18:13 loop6
brw------- 1 root root 7, 7 Jan 9 18:13 loop7
brw------- 1 root root 179, 0 Jan 9 18:13 mmcblk0
-rw-rw-rw- 1 root root 73995264 Jan 9 18:14 mmcblk0p1
drwxr-xr-x 4 root root 80 Jan 9 18:13 platform
brw------- 1 root root 1, 0 Jan 9 18:13 ram0
brw------- 1 root root 1, 1 Jan 9 18:13 ram1
brw------- 1 root root 1, 10 Jan 9 18:13 ram10
brw------- 1 root root 1, 11 Jan 9 18:13 ram11
brw------- 1 root root 1, 12 Jan 9 18:13 ram12
brw------- 1 root root 1, 13 Jan 9 18:13 ram13
brw------- 1 root root 1, 14 Jan 9 18:13 ram14
brw------- 1 root root 1, 15 Jan 9 18:13 ram15
brw------- 1 root root 1, 2 Jan 9 18:13 ram2
brw------- 1 root root 1, 3 Jan 9 18:13 ram3
brw------- 1 root root 1, 4 Jan 9 18:13 ram4
brw------- 1 root root 1, 5 Jan 9 18:13 ram5
brw------- 1 root root 1, 6 Jan 9 18:13 ram6
brw------- 1 root root 1, 7 Jan 9 18:13 ram7
brw------- 1 root root 1, 8 Jan 9 18:13 ram8
brw------- 1 root root 1, 9 Jan 9 18:13 ram9
/dev/block # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
/dev/block # fdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
Disk /dev/block/mmcblk0p1: 73 MB, 73995264 bytes
255 heads, 63 sectors/track, 8 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block #
Strange, today when I opened adb, it appears that some of the entries in /dev/block have changed. mmcblk0p1 is gone and replaced with mmcblk1p1.
Yesterday I saw this
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6
This is what I see today:
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram0 ram12 ram2 ram6
loop1 loop5 mmcblk1 ram1 ram13 ram3 ram7
loop2 loop6 mmcblk1p1 ram10 ram14 ram4 ram8
loop3 loop7 platform ram11 ram15 ram5 ram9
/dev/block #
If my understanding is correct (and it's usually not) the "P1" indicates that this is "partition one" on the "mmcblock one" device. (or 'disk'). I'm further assuming that of the two devices shown (mmcblk0, and mmcblk1) one of them is my 8gb microsd card, and the other is the NC's internal 8gb memory. Which makes me wonder why yesterday's "ls" did not show both devices. Also makes me wonder what the 'p1' partition is, which disk it's really on, and why it appears to have moved.
I took a look at the geometries of the disks and the partition using fdisk again, I dont know what I should be looking for here, and dont know whats relevant and what isn't. I can see I have two disks of slightly different sizes, and a mystery partition of some sort that doesnt seem like it should fit on either of the two disks.
Code:
/dev/block # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
/dev/block # fdisk -l /dev/block/mmcblk1
fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
255 heads, 63 sectors/track, 966 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 1 38 305203+ b Win95 FAT32
/dev/block # fdisk -l /dev/block/mmcblk1p1
fdisk -l /dev/block/mmcblk1p1
Disk /dev/block/mmcblk1p1: 312 MB, 312528384 bytes
4 heads, 16 sectors/track, 9537 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block #
Ok. I feel real stupid, obviously the mmcblk1 device is the sdcard and the p1 partition on it is the fat32 partition on it. Still leaves me wondering what happened to the geometry on the internal memory. CHS looks way off. shouldn't it be more like that of my sdcard?
*** Second Update***
I'm pulling my hair out here. I tried to correct the CHS values...no love there, even after rebooting it remains unchanged.
Code:
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
After trying to fix the geometry several times, and failing. I said Eff this, and tried living with the incorrect values and creating the partitions anyway. I keep getting fdisk: short write, when creating partition 8.
Anway....from start to finish here - notice the # of cylinders as I progress.
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4):
Value is out of range
Partition number (1-4): 1
1
First cylinder (1-940, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-940, default 940): 9
9
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4): 2
2
First cylinder (10-940, default 10):
Using default value 10
Last cylinder or +size or +sizeM or +sizeK (10-940, default 940): 18
18
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4): 3
3
First cylinder (19-940, default 19):
Using default value 19
Last cylinder or +size or +sizeM or +sizeK (19-940, default 940): 56
56
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
e
e
Selected partition 4
First cylinder (57-940, default 57):
Using default value 57
Last cylinder or +size or +sizeM or +sizeK (57-940, default 940):
Using default value 940
Command (m for help): n
n
First cylinder (57-940, default 57):
Using default value 57
Last cylinder or +size or +sizeM or +sizeK (57-940, default 940): 114
114
Command (m for help): n
n
First cylinder (115-940, default 115):
Using default value 115
Last cylinder or +size or +sizeM or +sizeK (115-940, default 940): 236
236
Command (m for help): n
n
First cylinder (237-940, default 237):
Using default value 237
Last cylinder or +size or +sizeM or +sizeK (237-940, default 940): 281
281
Command (m for help):
at this point, I'll stop and review the changes before I commit (w) them to disk...
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
255 heads, 63 sectors/track, 940 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 83 Linux
/dev/block/mmcblk0p2 10 18 72292+ 83 Linux
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 940 7100730 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
Okay, Now the number of cylinders originally being reported was 236032, I specified 965 using the -C switch, and somehow ended up with a value of 940 - still leaving the geometry out of whack. Before I go any further I will commit and (w) the pending partition table here ...
Code:
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
255 heads, 63 sectors/track, 940 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 83 Linux
/dev/block/mmcblk0p2 10 18 72292+ 83 Linux
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 940 7100730 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
~ #
So it appears my partition table has been written successfully. I just need to create partition 8. ... before I do that, I will reboot the NC to make sure the partition table is persistent...
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
...and that's a big fat fail.
At this point, It looks like my only option to ever use this NC again, is to have a stand alone bootable sd card. If anybody has a suggestion, please throw it my way.
Do either of these things indicate anything of importance that could potentially be of help?
1) 'adb devices' lists the Device ID as "RECOVERY"
2) The internal memory seems to be in a 'read only' mode of some sort.
The last time this NC did power up under its own free will, was when the stock recovery was being attempted - and crashed.
MaGoober said:
Do either of these things indicate anything of importance that could potentially be of help?
1) 'adb devices' lists the Device ID as "RECOVERY"
2) The internal memory seems to be in a 'read only' mode of some sort.
The last time this NC did power up under its own free will, was when the stock recovery was being attempted - and crashed.
Click to expand...
Click to collapse
Your CHS (cylinder, head, sector) settings are wrong. It should be 255 heads, 63 sectors/track and 965 cylinders. You need to run fdisk CHS to fix it. You need to type the following command in ADB shell.
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Then do an
fdisk -l /dev/block/mmcblk0
to see what you get.
If the CHS is right you can do my 145678 repair and format. I don't know if the p2 repair will work though. If not, I may be able to help.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Your CHS (cylinder, head, sector) settings are wrong. It should be 255 heads, 63 sectors/track and 965 cylinders. You need to run fdisk CHS to fix it. You need to type the following command in ADB shell.
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Then do an
fdisk -l /dev/block/mmcblk0
to see what you get.
If the CHS is right you can do my 145678 repair and format. I don't know if the p2 repair will work though. If not, I may be able to help.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Here's the result - as before, it just doesn't 'stick'.
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #
Thanks for your help, I really do appreciate it.
I may be crazy here, but what are the odds my NC does not have the same emmc chip? This thing sure acts like its fallen victim to the 'brick bug'. I cant seem to write anything at all, Tried creating new partitions with parted, no go. Even tried overwriting the mbr with dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1 and it didnt even touch it.
MaGoober said:
I may be crazy here, but what are the odds my NC does not have the same emmc chip? This thing sure acts like its fallen victim to the 'brick bug'. I cant seem to write anything at all, Tried creating new partitions with parted, no go. Even tried overwriting the mbr with dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1 and it didnt even touch it.
Click to expand...
Click to collapse
I have had SD chips that became ready only by some mysterious means. It is possible that your emmc has done the same. In fact, one other user said that happened to his emmc.
Sent from my Galaxy Tab 2 using XDA Premium
Alrighty then, I confirmed this much at least:
with
Code:
dmesg | grep mmc0
The emmc chip in my NC is the Samsung M8G2FA, which is prone to the "Brick Bug", and from the little I've read on it so far, the bug is brought on merely by wiping the cache partitions clean. I got me some more reading up to do...
Today, I called BN tech support for the second time in a week, after visiting the local store to see if anybody there could offer up assistance. Long story short, because our NC was just out of warranty (by three weeks) they did offer to exchange it with a 'certified pre-owned' . When that comes in, the very first thing I'm going to do is see what memory chip it has in it, Evidently just trying to do a 'hard reset' and run the stock recovery bricks the M8G2FA EMMC. However, I still don't know what caused our NC to lock up in the first place. I guess at this point, that's moot.
leapinlar, I've read through many of your posts, although I couldn't fix my problems, you were instrumental in keeping me sane. ... well, depending on how loosely you define sane,
Hi,
The past week i've been busy in flashing flyme/twrp/ubuntu and all went very well, but i find the experience a little limited until now. Especially when reading about all the ppl who bricked their device or are stuck one way or another with locked bootloaders, missing recovery's etc.
I found that the bootloader unlock status is kept in the /private partition, wether manipulating this partition in order to unlock the device is possible, i dont know.
So in order to up the experience for all i need your help
I've been mapping out the partition layout on my Chinese Meizu Pro5 64gb (converted to global/intl now), but one device only gets you so far. There are differences between the Flyme/Ubuntu devices, the Flyme devices U/A/I and the TWRP recovery (lets all thank faust93) does not work for everyone (it does for me).
For anyone that has access to 'sgdisk' (you successfully installed TWRP or have an Ubuntu edition) i need a layout of your partitions: (your personal info/guid is excluded (-v GUID) from this)
# sgdisk --print /dev/block/sda | grep -v GUID >/sdcard/partition_layout.txt
We have the following devices:
1. G [M576_intl_official] Global 32gb
2. G [M576_intl_official] Global 64gb
3. U: [M576_unicom_custom] Unicom 32gb
4. U: [M576_unicom_custom] Unicom 64gb
5. A: [M576_mobile_public] Mobile Public 32gb
6. A: [M576_mobile_public] Mobile Public 64gb
7. I: [M576_intl_official] Ubuntu Meizu 32gb
8. I: [M576_intl_official] Ubuntu Meizu 64gb
TWRP 3: fstab table (work in progress)
Code:
/private emmc /dev/block/sda1 flags=display="Private";backup=1 # meizu imei/esn/wifi/bluetooth/serial/lock/unlock
/proinfo emmc /dev/block/sda2 # meizu firmware/machine_type/region_id unicom(U)/chicom(A)/intl(G)
#/misc emmc /dev/block/sda3 # empty 0x00
/param emmc /dev/block/sda21 # u-boot active stats
/efs ext4 /dev/block/sda22 flags=display="EFS";backup=1
#/pnv emmc /dev/block/sda23 # empty 0x00
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/recovery ext4 /dev/block/sda27 flags=display="Recovery";backup=1
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
#/rstinfo emmc /dev/block/sda29 # kernel log
#/mnv ext4 /dev/block/sda30 # nv_protected
#/reserved1 emmc /dev/block/sda31 # empty 0x00
#/reserved2 emmc /dev/block/sda32 # empty 0x00
#/reserved3 emmc /dev/block/sda33 # empty 0x00
/system ext4 /dev/block/sda41 flags=display="System"
#/custom ext4 /dev/block/sda42 # preload: adds applications to system on first install/factory reset
/cache ext4 /dev/block/sda43 flags=display="Cache";backup=1
/sdcard ext4 /dev/block/sda44 flags=display="Internal Storage";storage;settingsstorage
#/u-boot emmc /dev/block/sdb # u-boot bootloader
#- emmc /dev/block/sdc # empty 0x00 ( ?? could be used as backup bootloader for Android 7.0 nougat ??)
/external_sd vfat /dev/block/mmcblk0p1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat ?? flags=display="USB-OTG";storage;wipeingui;removable
*** BRICK WARNING: the bootloader expects >> ldfw << and >>dtb<< ***
*** Make sure ldfw and dtb are flashed, i did not dare to try without ***
*** Also make sure that bootloader and ldfw are from the flyme_5.6.1.19_daily ***
Code:
bootloader: u-boot bootloader
ldfw : u-boot load firmware (TrustZone driver?, can someone verify)
dtb : u-boot device tree blob/binary, to pass to linux kernel
.
Switching from android-to-ubuntu or ubuntu-to-android
requires the following partitions to be flashed:
Code:
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
/system ext4 /dev/block/sda41 flags=display="System"
.
My partition table
Code:
Meizu Pro 5 64gb Unicom Edition
Disk /dev/block/sda: 15267840 sectors, 58.2 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15267834
Partitions will be aligned on 64-sector boundaries
Total free space is 11386 sectors (44.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 1279 1024.0 KiB 0700 private
2 1280 1343 256.0 KiB 0700 proinfo
3 1344 1407 256.0 KiB 0700 misc
21 2048 3071 4.0 MiB 0700 param
22 3072 5119 8.0 MiB 0700 efs
23 5120 5631 2.0 MiB 0700 pnv
24 5632 6655 4.0 MiB 0700 ldfw
25 6656 7679 4.0 MiB 0700 dtb
26 7680 13823 24.0 MiB 0700 bootimg
27 13824 22015 32.0 MiB 0700 recovery
28 22016 30207 32.0 MiB 0700 bootlogo
29 30208 35327 20.0 MiB 0700 rstinfo
30 35328 40447 20.0 MiB 0700 mnv
31 40448 45567 20.0 MiB 0700 reserved1
32 45568 50687 20.0 MiB 0700 reserved2
33 50688 55807 20.0 MiB 0700 reserved3
41 65536 720895 2.5 GiB 0700 system
42 720896 851967 512.0 MiB 0700 custom
43 851968 983039 512.0 MiB 0700 cache
44 983040 15267834 54.5 GiB 0700 userdata
If you find any errors or have contributions, post in the thread or pm me.
Awesome
Wow, what a wasteland ... anyone still here .... here .... here .... ..... .... **dustball** ..... **crickets**
Anyways, i found the partition tables lurking in the bootloader,
they are pretty much the same for all the devices:
The 32gb and 64gb editions are the same, partition 44 userdata is just a leftover partition.
The only difference between Android and Ubuntu is partition 43,
maybe Wimpy can shed some light on this
Code:
< index=43,name=cache,size=[B]512MiB[/B],uuid=${uuid_cache};
---
> index=43,name=cache,size=[B]700MiB[/B],uuid=${uuid_cache};
Android partition table
Code:
index=1,name=private,size=1MiB,start=0x400000,uuid=${uuid_private};
index=2,name=proinfo,size=256KiB,uuid=${uuid_proinfo};
index=3,name=misc,size=256KiB,uuid=${uuid_misc};
index=21,name=param,size=4MiB,start=0x800000,uuid=${uuid_param};
index=22,name=efs,size=8MiB,uuid=${uuid_efs};
index=23,name=pnv,size=2MiB,uuid=${uuid_pnv};
index=24,name=ldfw,size=4MiB,uuid=${uuid_ldfw};
index=25,name=dtb,size=4MiB,uuid=${uuid_dtb};
index=26,name=bootimg,size=24MiB,uuid=${uuid_bootimg};
index=27,name=recovery,size=32MiB,uuid=${uuid_recovery};
index=28,name=bootlogo,size=32MiB,uuid=${uuid_bootlogo};
index=29,name=rstinfo,size=20MiB,uuid=${uuid_rstinfo};
index=30,name=mnv,size=20MiB,uuid=${uuid_mnv};
index=31,name=reserved1,size=20MiB,uuid=${uuid_reserved1};
index=32,name=reserved2,size=20MiB,uuid=${uuid_reserved2};
index=33,name=reserved3,size=20MiB,uuid=${uuid_reserved3};
index=41,name=system,size=2560MiB,start=0x10000000,uuid=${uuid_system};
index=42,name=custom,size=512MiB,uuid=${uuid_custom};
[B]index=43,name=cache,size=512MiB,uuid=${uuid_cache};[/B]
index=44,name=userdata,size=0,uuid=${uuid_userdata};
Ubuntu partition table
Code:
index=1,name=private,size=1MiB,start=0x400000,uuid=${uuid_private};
index=2,name=proinfo,size=256KiB,uuid=${uuid_proinfo};
index=3,name=misc,size=256KiB,uuid=${uuid_misc};
index=21,name=param,size=4MiB,start=0x800000,uuid=${uuid_param};
index=22,name=efs,size=8MiB,uuid=${uuid_efs};
index=23,name=pnv,size=2MiB,uuid=${uuid_pnv};
index=24,name=ldfw,size=4MiB,uuid=${uuid_ldfw};
index=25,name=dtb,size=4MiB,uuid=${uuid_dtb};
index=26,name=bootimg,size=24MiB,uuid=${uuid_bootimg};
index=27,name=recovery,size=32MiB,uuid=${uuid_recovery};
index=28,name=bootlogo,size=32MiB,uuid=${uuid_bootlogo};
index=29,name=rstinfo,size=20MiB,uuid=${uuid_rstinfo};
index=30,name=mnv,size=20MiB,uuid=${uuid_mnv};
index=31,name=reserved1,size=20MiB,uuid=${uuid_reserved1};
index=32,name=reserved2,size=20MiB,uuid=${uuid_reserved2};
index=33,name=reserved3,size=20MiB,uuid=${uuid_reserved3};
index=41,name=system,size=2560MiB,start=0x10000000,uuid=${uuid_system};
index=42,name=custom,size=512MiB,uuid=${uuid_custom};
[B]index=43,name=cache,size=700MiB,uuid=${uuid_cache};[/B]
index=44,name=userdata,size=0,uuid=${uuid_userdata};
I installed ubuntu on a android Meizu Pro 5 and now, when I try to change channels to rc-proposed using system-image-cli I find that the 512MB cache partition is not enough. So I guess that is the reason the Ubuntu version has a 700MB cache partition. That (/dev/sda43) is the place where the files for an upgrade are downloaded and then installed from the recovery mode.
st0rm77 said:
Hi,
The past week i've been busy in flashing flyme/twrp/ubuntu and all went very well, but i find the experience a little limited until now. Especially when reading about all the ppl who bricked their device or are stuck one way or another with locked bootloaders, missing recovery's etc.
I found that the bootloader unlock status is kept in the /private partition, wether manipulating this partition in order to unlock the device is possible, i dont know.
So in order to up the experience for all i need your help
I've been mapping out the partition layout on my Chinese Meizu Pro5 64gb (converted to global/intl now), but one device only gets you so far. There are differences between the Flyme/Ubuntu devices, the Flyme devices U/A/I and the TWRP recovery (lets all thank faust93) does not work for everyone (it does for me).
For anyone that has access to 'sgdisk' (you successfully installed TWRP or have an Ubuntu edition) i need a layout of your partitions: (your personal info/guid is excluded (-v GUID) from this)
# sgdisk --print /dev/block/sda | grep -v GUID >/sdcard/partition_layout.txt
We have the following devices:
1. G [M576_intl_official] Global 32gb
2. G [M576_intl_official] Global 64gb
3. U: [M576_unicom_custom] Unicom 32gb
4. U: [M576_unicom_custom] Unicom 64gb
5. A: [M576_mobile_public] Mobile Public 32gb
6. A: [M576_mobile_public] Mobile Public 64gb
7. I: [M576_intl_official] Ubuntu Meizu 32gb
8. I: [M576_intl_official] Ubuntu Meizu 64gb
TWRP 3: fstab table (work in progress)
Code:
/private emmc /dev/block/sda1 flags=display="Private";backup=1 # meizu imei/esn/wifi/bluetooth/serial/lock/unlock
/proinfo emmc /dev/block/sda2 # meizu firmware/machine_type/region_id unicom(U)/chicom(A)/intl(G)
#/misc emmc /dev/block/sda3 # empty 0x00
/param emmc /dev/block/sda21 # u-boot active stats
/efs ext4 /dev/block/sda22 flags=display="EFS";backup=1
#/pnv emmc /dev/block/sda23 # empty 0x00
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/recovery ext4 /dev/block/sda27 flags=display="Recovery";backup=1
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
#/rstinfo emmc /dev/block/sda29 # kernel log
#/mnv ext4 /dev/block/sda30 # nv_protected
#/reserved1 emmc /dev/block/sda31 # empty 0x00
#/reserved2 emmc /dev/block/sda32 # empty 0x00
#/reserved3 emmc /dev/block/sda33 # empty 0x00
/system ext4 /dev/block/sda41 flags=display="System"
#/custom ext4 /dev/block/sda42 # preload: adds applications to system on first install/factory reset
/cache ext4 /dev/block/sda43 flags=display="Cache";backup=1
/sdcard ext4 /dev/block/sda44 flags=display="Internal Storage";storage;settingsstorage
#/u-boot emmc /dev/block/sdb # u-boot bootloader
#- emmc /dev/block/sdc # empty 0x00 ( ?? could be used as backup bootloader for Android 7.0 nougat ??)
/external_sd vfat /dev/block/mmcblk0p1 flags=display="Micro SDcard";storage;wipeingui;removable
/usb-otg vfat ?? flags=display="USB-OTG";storage;wipeingui;removable
*** BRICK WARNING: the bootloader expects >> ldfw << and >>dtb<< ***
*** Make sure ldfw and dtb are flashed, i did not dare to try without ***
*** Also make sure that bootloader and ldfw are from the flyme_5.6.1.19_daily ***
Code:
bootloader: u-boot bootloader
ldfw : u-boot load firmware (TrustZone driver?, can someone verify)
dtb : u-boot device tree blob/binary, to pass to linux kernel
.
Switching from android-to-ubuntu or ubuntu-to-android
requires the following partitions to be flashed:
Code:
/ldfw emmc /dev/block/sda24 flags=display="Firmware";backup=1
/dtb emmc /dev/block/sda25 flags=display="Device Tree";backup=1
/bootimg emmc /dev/block/sda26 flags=display="Boot"
/bootlogo emmc /dev/block/sda28 flags=display="Bootlogo";backup=1
/system ext4 /dev/block/sda41 flags=display="System"
.
My partition table
Code:
Meizu Pro 5 64gb Unicom Edition
Disk /dev/block/sda: 15267840 sectors, 58.2 GiB
Logical sector size: 4096 bytes
Disk identifier (GUID):
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15267834
Partitions will be aligned on 64-sector boundaries
Total free space is 11386 sectors (44.5 MiB)
Number Start (sector) End (sector) Size Code Name
1 1024 1279 1024.0 KiB 0700 private
2 1280 1343 256.0 KiB 0700 proinfo
3 1344 1407 256.0 KiB 0700 misc
21 2048 3071 4.0 MiB 0700 param
22 3072 5119 8.0 MiB 0700 efs
23 5120 5631 2.0 MiB 0700 pnv
24 5632 6655 4.0 MiB 0700 ldfw
25 6656 7679 4.0 MiB 0700 dtb
26 7680 13823 24.0 MiB 0700 bootimg
27 13824 22015 32.0 MiB 0700 recovery
28 22016 30207 32.0 MiB 0700 bootlogo
29 30208 35327 20.0 MiB 0700 rstinfo
30 35328 40447 20.0 MiB 0700 mnv
31 40448 45567 20.0 MiB 0700 reserved1
32 45568 50687 20.0 MiB 0700 reserved2
33 50688 55807 20.0 MiB 0700 reserved3
41 65536 720895 2.5 GiB 0700 system
42 720896 851967 512.0 MiB 0700 custom
43 851968 983039 512.0 MiB 0700 cache
44 983040 15267834 54.5 GiB 0700 userdata
If you find any errors or have contributions, post in the thread or pm me.
Awesome
Click to expand...
Click to collapse
Hi, I have lost my partitions due to the latest update of Magisk.
PYCON told me that I could redefine my partitions yet I haven't got a clue about how to do this.
I have a chinese version 32 Gb Pro 5 by the way.
This guy here has the same problem : https://forum.xda-developers.com/meizu-pro-5/help/provide-images-partitions-t3639336
Could somebody help us please ?
I'm trying to fix my messed up partition table in my Meizu 5 PRO for Ubuntu Touch installation.
Using ADB and fdisk I've managed to get this print out:
Code:
~ # fdisk /dev/block/sda
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/sda: 122142720 sectors, 1984M
Logical sector size: 4096
Disk identifier (GUID): 00042021-0408-4601-9dcc-a8c51255994f
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 15267834
Number Start (sector) End (sector) Size Code Name
1 1024 1279 1024K 0700 private
2 1280 1343 256K 0700 proinfo
3 1344 1407 256K 0700 misc
21 2048 3071 4096K 0700 param
22 3072 5119 8192K 0700 efs
23 5120 5631 2048K 0700 pnv
24 5632 6655 4096K 0700 ldfw
25 6656 7679 4096K 0700 dtb
26 7680 13823 24.0M 0700 bootimg
27 13824 22015 32.0M 0700 recovery
28 22016 30207 32.0M 0700 bootlogo
29 30208 35327 20.0M 0700 rstinfo
30 35328 40447 20.0M 0700 mnv
31 40448 45567 20.0M 0700 reserved1
32 45568 50687 20.0M 0700 reserved2
33 50688 55807 20.0M 0700 reserved3
41 65536 720895 2560M 0700 system
42 720896 851967 512M 0700 custom
43 851968 15267834 [B]54.9G 0700 cache[/B]
44 55808 65535 [B]38.0M 0700 userdata[/B]
I bolded partitions in question. Cache is taking up all the storage whereas "userdata" gets only 38MB. I need to resize "userdata" partition to take up most of the storage and leave about 2 GB for cache. I noticed cache partition is formatted in ext4 and "userdata" is vfat.
option "d" selects partition 1 for some reason.
after running
Code:
disk /dev/block/sda43
(which is the partition with 60GB) I get:
Code:
Command (m for help): p
Disk /dev/block/sda43: 59.0 GB, 59047391232 bytes
64 heads, 32 sectors/track, 7038 cylinders
Units = cylinders of 2048 * 4096 = 8388608 bytes
Device Boot Start End Blocks Id System
Someone more experienced, can you guide me ? I don't wanna mess it up more than it is.
Thank you in advance.
Update:
Have learned that the best tool for resizing a filesystem is resize2fs thus I ran:
Code:
~ # resize2fs /dev/block/sda43 1G
However even after resizing the filesystem to 1GB I still get:
Code:
43 851968 15267834 [B]54.9G 0700 cache[/B]
Shouldn't it be reading 1GB now ???
Oh boy. Maybe parts of this guide could help you:
https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-how-to-upgrade-to-ubuntu-touch-t4021397
You *need* the correct fdisk version for this, as stated in the guide.
Do not just copy the bold parts. Sectors for your current table are below the next code box):
Code:
Command (m for help): d
Partition number (1-3,21-33,43,44, default 44): 43
Partition 43 has been deleted
Command (m for help): d
Partition number (1-3,21-33,44, default 44): 44
Partition 44 has been deleted.
Command (m for help): n
Partition number (4-20,34-40,43-128, default 4): 43
First sector (6-15267834, default 1769472): [B]1769472[/B]
Last sector, +sectors or +size{K,M,G,T,P} (1769472-15267834, default 15267834): [B]2293775[/B]
Created a new partition 43 of type 'Linux filesystem' and of size 2 GiB.
Command (m for help): n
Partition number (4-20,34-40,44-128, default 4): 44
First sector (6-15267834, default 2294016): [B]2293776[/B]
Last sector, +sectors or +size{K,M,G,T,P} (2293776-15267834, default 15267834): [B]15267824[/B]
Created a new partition 44 of type 'Linux filesystem' and of size 49.5 GiB.
When creating partition 43 sector should be first 851969 - last 1376271 for 2GB cache
and for partition 44 first 1376272 - last 15267824 to assign the remaining space to userdata.
Next change the partition types to "Microsoft basic data"
Code:
Command (m for help): t
Partition number (1-3,21-33,41-44, default 44): 43
Partition type (type L to list all types): 11
Changed type of partition 'Linux filesystem' to 'Microsoft basic data'.
Command (m for help): t
Partition number (1-3,21-33,41-44, default 44): 44
Partition type (type L to list all types): 11
Changed type of partition 'Linux filesystem' to 'Microsoft basic data'.
Check again with "p", if the types are correct. If not, search correct type number with "t" and "L" and try again.
Afterwards, you need to continue to give the partitions names:
Code:
Command (m for help): x
Expert command (m for help): n
Partition number (1-3,21-33,41-44, default 44): 43
New name: cache
Partition number (1-3,21-33,41-44, default 44): 44
New name: userdata
Expert command (m for help): r
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
If the table has been successfully altered, you can now continue to install the filesystem:
Code:
~ # mke2fs -t ext4 -m 0 /dev/block/sda43
~ # mke2fs -t ext4 -m 0 /dev/block/sda44
This should fix your current dilemma. Its a lengthy guide and if you actually want the most recent ubuntu touch you might as well do it completely, resizing your system partition too. In that case ignore above changes.