Related
Assuming the mount points are handled by some sort of config file, can anyone tell me what the android equivalent of the linux /etc/fstab is and where it is located?
I do believe I found it.
Instead of /etc/fstab, its /etc/vold.fstab
Backing up my ROM and going to edit to see if this changes the mount point of my sd cards.
SD Card & EMMC handling is done by /system/etc/vold.fstab
/system, /data, /cache, /osh and /pds are handled on the init scripts (/init.*.rc, they're inside the ramdisk/boot.img)
Can anyone tell me how to correct mount sd card (with 2 partitiions) by means of vold.fstab?
[email protected]:/dev/block # ls
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p2
nanda
nandb
nandc
nandd
nande
nandf
nandg
nandh
nandi
platform
ram0
ram1
vold
Click to expand...
Click to collapse
Hi.
I was trying to flash my ROM to CyanogenMod today, however it didn't go through... my phone went into a bootloop and I tried to restore the backup I made through the RomManager. Now it's giving me the unable to mount /cache/ error.
I still have access to the RomManager and adb, however I was wondering if it was possible to fix my phone or at least turn S ON from OFF. If there is no solution to this issue, I want to try to return the phone to T-Mobile to get a new one, but I don't want to keep S-OFF...
Are there any solutions? Thanks.
http://forum.xda-developers.com/showthread.php?t=1448441
read the whole thread...
hoffmas said:
http://forum.xda-developers.com/showthread.php?t=1448441
read the whole thread...
Click to expand...
Click to collapse
Unfortunately, I tried following what the OP did and it was not working. fdisk kept returning an error stating that it could not read the partitions.
ViaTheStars said:
Unfortunately, I tried following what the OP did and it was not working. fdisk kept returning an error stating that it could not read the partitions.
Click to expand...
Click to collapse
If you pull the SD card, navigate to /dev/block/, and run ls whats the output it gives you? Then if you could put your SD card back in and do the same thing and post that too I might be able to help you do the same thing I did.
CollegeBound1987 said:
If you pull the SD card, navigate to /dev/block/, and run ls whats the output it gives you? Then if you could put your SD card back in and do the same thing and post that too I might be able to help you do the same thing I did.
Click to expand...
Click to collapse
Code:
loop0 loop6 mmcblk0p12 mmcblk0p18 mmcblk0p23 mmcblk0p3 mmcblk0p
9
loop1 loop7 mmcblk0p13 mmcblk0p19 mmcblk0p24 mmcblk0p4 platform
loop2 mmcblk0 mmcblk0p14 mmcblk0p2 mmcblk0p25 mmcblk0p5
loop3 mmcblk0p1 mmcblk0p15 mmcblk0p20 mmcblk0p26 mmcblk0p6
loop4 mmcblk0p10 mmcblk0p16 mmcblk0p21 mmcblk0p27 mmcblk0p7
loop5 mmcblk0p11 mmcblk0p17 mmcblk0p22 mmcblk0p28 mmcblk0p8
ViaTheStars said:
Code:
loop0 loop6 mmcblk0p12 mmcblk0p18 mmcblk0p23 mmcblk0p3 mmcblk0p
9
loop1 loop7 mmcblk0p13 mmcblk0p19 mmcblk0p24 mmcblk0p4 platform
loop2 mmcblk0 mmcblk0p14 mmcblk0p2 mmcblk0p25 mmcblk0p5
loop3 mmcblk0p1 mmcblk0p15 mmcblk0p20 mmcblk0p26 mmcblk0p6
loop4 mmcblk0p10 mmcblk0p16 mmcblk0p21 mmcblk0p27 mmcblk0p7
loop5 mmcblk0p11 mmcblk0p17 mmcblk0p22 mmcblk0p28 mmcblk0p8
Click to expand...
Click to collapse
yea see mine didnt look like that until after i recreated the partition tables
before i did that all i had listed there was
loop0 loop2 loop4 loop6 platform
loop1 loop3 loop5 loop7
If clockworkmod can mount your SD card i would try going to sdb shell and running these three commands
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
then install a new rom from your SD Card
I figure if the phone is already bricked you have nothing to lose
You may also want to try running 'busybox fdisk -l mmcblk0' in sdb shell putting the results here.
CollegeBound1987 said:
yea see mine didnt look like that until after i recreated the partition tables
before i did that all i had listed there was
loop0 loop2 loop4 loop6 platform
loop1 loop3 loop5 loop7
If clockworkmod can mount your SD card i would try going to sdb shell and running these three commands
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
then install a new rom from your SD Card
I figure if the phone is already bricked you have nothing to lose
You may also want to try running 'busybox fdisk -l mmcblk0' in sdb shell putting the results here.
Click to expand...
Click to collapse
Code:
/dev/block # fdisk -l mmcblk0
fdisk -l mmcblk0
fdisk: can't open 'mmcblk0': I/O error
/dev/block #
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,
Quite a strange thing happened to my Galaxy S3 (GT-I9300) tonight, I woke up and saw it stuck on Samsung logo. Tried the usual stuff, removed battery, changed battery, etc. No results. I then tried to reboot in recovery to wipe cache and dalvik and eventually reinstall omniRom. But then that's what I found (see picture). I tried to install stock from odin but I got a failed too. I read a lot about corrupted partition table but before trying to mess with that I'd like to hear dome opinions first. Tried to mount from adb shell but nothing. See attached recovery.log contents.
I tried to run
Code:
#parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
Code:
cd /dev/block
/dev/block # ls
ls
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
The strange thing is that I was doing absolutely nothing with the phone. Is it possible the sd is physically damaged?
Thank you anyone for your help:good:
Patit
HW problem?
maybe I ran into a hardware problem....:crying:
forums.whirlpool.net.au/archive/200176
It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?
wonderfulme said:
It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?
Click to expand...
Click to collapse
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.
matshias said:
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.
Click to expand...
Click to collapse
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.
matshias said:
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.
Click to expand...
Click to collapse
There was indeed an option for "OEM unlock" in dev settings which I somehow missed. Works as intended now.
So here's the output of fastboot:
Code:
F:\AndroidSDK\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.054s]
finished. total time: 0.054s
Guess we're out of luck here?
I also did an "adb shell" and /proc/partitions as well as /system/build.prop are readable, "mount" works, however I have no idea where the kernel is stored. There's a "/firmware" dir but it's unaccessible, I'm thinking maybe that's where:
Code:
2|TB-8704X:/ $ uname -a
Linux localhost 3.18.31-perf-g40dd5c6-dirty #1 SMP PREEMPT Fri Jul 7 02:02:41 CST 2017 aarch64
TB-8704X:/ $ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
TB-8704X:/ $ ls -ld firmware
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
TB-8704X:/ $ cd firmware
/system/bin/sh: cd: /firmware: Permission denied
Also, FWIW, here's a list of files/dirs in / in case I missed something of note. I'm not really comfortable with Android internals.
Code:
130|TB-8704X:/ $ ls -l
total 4232
dr-xr-xr-x 61 root root 0 1970-03-08 03:34 acct
drwxr-xr-x 2 root root 40 1970-01-01 03:00 bt_firmware
drwxrwx--- 7 system cache 4096 2017-08-10 16:42 cache
lrwxrwxrwx 1 root root 13 1970-01-01 03:00 charger -> /sbin/healthd
drwxr-xr-x 2 root root 0 1970-03-08 03:34 config
lrwxrwxrwx 1 root root 17 1970-01-01 03:00 d -> /sys/kernel/debug
drwxrwx--x 43 system system 4096 1970-03-08 03:34 data
-rw-r--r-- 1 root root 995 1970-01-01 03:00 default.prop
drwxr-xr-x 15 root root 3500 1970-03-08 03:34 dev
drwxr-xr-x 3 root root 4096 1970-01-01 03:00 dsp
lrwxrwxrwx 1 root root 11 1970-01-01 03:00 etc -> /system/etc
-rw-r--r-- 1 root root 186677 1970-01-01 03:00 file_contexts.bin
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
-rw-r----- 1 root root 1578 1970-01-01 03:00 fstab.qcom
-rwxr-x--- 1 root root 1246704 1970-01-01 03:00 init
-rwxr-x--- 1 root root 1846 1970-01-01 03:00 init.carrier.rc
-rwxr-x--- 1 root root 3295 1970-01-01 03:00 init.class_main.sh
-rwxr-x--- 1 root root 1156 1970-01-01 03:00 init.environ.rc
-rwxr-x--- 1 root root 1730 1970-01-01 03:00 init.mdm.sh
-rwxr-x--- 1 root root 29161 1970-01-01 03:00 init.msm.usb.configfs.rc
-rwxr-x--- 1 root root 7054 1970-01-01 03:00 init.qcom.class_core.sh
-rwxr-x--- 1 root root 12035 1970-01-01 03:00 init.qcom.early_boot.sh
-rwxr-x--- 1 root root 3775 1970-01-01 03:00 init.qcom.factory.rc
-rwxr-x--- 1 root root 37960 1970-01-01 03:00 init.qcom.rc
-rwxr-x--- 1 root root 2029 1970-01-01 03:00 init.qcom.sensors.sh
-rwxr-x--- 1 root root 12173 1970-01-01 03:00 init.qcom.sh
-rwxr-x--- 1 root root 2962 1970-01-01 03:00 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 97623 1970-01-01 03:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 10950 1970-01-01 03:00 init.qcom.usb.sh
-rwxr-x--- 1 root root 26676 1970-01-01 03:00 init.rc
-rwxr-x--- 1 root root 9584 1970-01-01 03:00 init.target.rc
-rwxr-x--- 1 root root 12058 1970-01-01 03:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5715 1970-01-01 03:00 init.usb.rc
-rwxr-x--- 1 root root 411 1970-01-01 03:00 init.zygote32.rc
-rwxr-x--- 1 root root 684 1970-01-01 03:00 init.zygote64_32.rc
drwxr-xr-x 10 root system 220 1970-03-08 03:34 mnt
drwxr-xr-x 2 root root 40 1970-01-01 03:00 oem
drwxrwx--x 13 root system 4096 1970-01-01 03:00 persist
dr-xr-xr-x 518 root root 0 1970-01-01 03:00 proc
-rw-r--r-- 1 root root 11549 1970-01-01 03:00 property_contexts
drwxr-xr-x 3 root root 60 1970-01-01 03:00 res
drwx------ 2 root root 40 2017-07-06 21:00 root
drwxr-x--- 2 root root 160 1970-01-01 03:00 sbin
lrwxrwxrwx 1 root root 21 1970-01-01 03:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 1957 1970-01-01 03:00 seapp_contexts
-rw-r--r-- 1 root root 90 1970-01-01 03:00 selinux_version
-rw-r--r-- 1 root root 285602 1970-01-01 03:00 sepolicy
-rw-r--r-- 1 root root 17999 1970-01-01 03:00 service_contexts
drwxr-xr-x 4 root root 80 2017-08-12 15:57 storage
dr-xr-xr-x 16 root root 0 1970-03-08 03:34 sys
drwxr-xr-x 21 root root 4096 1970-01-01 03:00 system
lrwxrwxrwx 1 root root 16 1970-03-08 03:34 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 14131 1970-01-01 03:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 4857 1970-01-01 03:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-01-01 03:00 vendor -> /system/vendor
-rw-r--r-- 1 root root 524 1970-01-01 03:00 verity_key
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.
That's quite sad.
Just got it and been playing with it for a couple days now. Device itself seems to be fine, but not having root is PITA.
wonderfulme said:
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.
Click to expand...
Click to collapse
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)
matshias said:
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)
Click to expand...
Click to collapse
Here's the output for the TB-8704X LTE version.
Mount points:
Code:
TB-8704X:/ $ mount
rootfs on / type rootfs (ro,seclabel,size=1705664k,nr_inodes=426416)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1811380k,nr_inodes=452845,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/dm-0 on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/bootdevice/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/dsp on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/modem on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/dm-1 on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Partitions:
Code:
TB-8704X:/etc $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.6G 4.7M 1.6G 1% /
tmpfs 1.7G 652K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/dm-0 3.6G 3.2G 336M 91% /system
/dev/block/bootdevice/by-name/cache 248M 744K 242M 1% /cache
/dev/block/bootdevice/by-name/persist 27M 512K 26M 2% /persist
/dev/block/bootdevice/by-name/dsp 12M 4.9M 6.4M 44% /dsp
/dev/block/bootdevice/by-name/modem 84M 74M 10M 88% /firmware
tmpfs 1.7G 0 1.7G 0% /storage
/dev/block/dm-1 52G 14G 38G 27% /data
/dev/fuse 52G 14G 38G 27% /storage/emulated
TB-8704X:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 61071360 mmcblk0
179 1 86016 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 32 mmcblk0p15
179 16 32 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 16 mmcblk0p18
179 19 15360 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 3984588 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 512 mmcblk0p29
179 30 32 mmcblk0p30
179 31 262144 mmcblk0p31
259 0 32 mmcblk0p32
259 1 512 mmcblk0p33
259 2 1024 mmcblk0p34
259 3 32768 mmcblk0p35
259 4 512 mmcblk0p36
259 5 4096 mmcblk0p37
259 6 128 mmcblk0p38
259 7 128 mmcblk0p39
259 8 256 mmcblk0p40
259 9 256 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 256 mmcblk0p45
259 14 256 mmcblk0p46
259 15 256 mmcblk0p47
259 16 8 mmcblk0p48
259 17 65536 mmcblk0p49
259 18 204800 mmcblk0p50
259 19 55492071 mmcblk0p51
179 32 4096 mmcblk0rpmb
253 0 3922408 dm-0
253 1 55492055 dm-1
/system/build.prop, just in case: https://pastebin.com/raw/jQn9N8nc
Kindly let me know if I missed anything.
Also, that Russian site lists the model number as TB-8704X_S000026_170707_ROW_QFIL, while my version of build.prop contains TB-8704X_S000026_170707_ROW (withot the "QFIL"). I'm not entirely up to date on Lenovo's naming conventions, but could that possibly suggest a slightly different model or should we disregard it altogether?
Edit: Nevermind, QFIL seems to be the name of the Qualcomm firmware update software.
Thanks!
I also hope that rooting or later a LineageOS will be available. I bought my one from Amazon in Germany 64GB/4GB/WiFi and it has following build number TB-8704F_S000024_170706_ROW. I came from Nexus 7 (2012).
Bought mine via Lenovo in the UK for £280 and loving it. I've been looking for a decent 8" tablet which wasn't stupidly expensive and this ticks all the boxes.
4GB /64GB + SD card
1920x1080 screen
Good audio with those front facing speakers
Decent battery life so far
Would love to be able to root and install Lineage as I use on my OPO as well, that would be perfect.
Love it so much I've ordered one for my old man as well.
wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
I have the tab 4 8" and you can unlock the boooader know developer mode.
Anonwatch said:
I have the tab 4 8" and you can unlock the boooader know developer mode.
Click to expand...
Click to collapse
Already figured as much. You might want to take a look at matshias's thread at https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
He's got TWRP working on both 8 and 10+.
Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?
Vicky khan said:
Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?
Click to expand...
Click to collapse
Wrong thread for your device - but install an ad-blocker
Many thanks for your great work. Everything has worked as described and I am super happy with this new tablet, replacing my Nexus 7.
I am surprised that there is so little activity around the Tab 4 here on XDA, but I am confident that once people understand that this is a really cool tablet and practically the only one with modern specs that comes close to the N7, there will be Custom ROMs and more. It's a beautiful piece of hardware and even without Custom ROM, the Lenovo Android is surprisingly lean and without bloatware (except for Microsoft Office).
Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:
Just had my memory card (128GB Samsung Pro) 'eaten' by my tablet - while on holiday with no computer access and it had my videos and music on it.
I've seen reports of this on other sites as well, and am fuming right now as this is an almighty ****-up if it's a regular occurrence, makes the tablet basically useless to me.
Edit: Took the card out of the tablet and stuck it in my Honor 9, no errors and all files work perfectly. Put it back in the Lenovo, so corrupt and won't let me do anything other than format it. Bloody Lenovo
jimmy19742 said:
Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:
Click to expand...
Click to collapse
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!
magoo5289 said:
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!
Click to expand...
Click to collapse
Yup 8504X not 8704X!
I saw this but am skeptical by nature and don't read Russian.
http://proshivkis.ru/?p=lenovo-tab-4-8-plus-wifi-lineageos-14-1