Unfortunately, I don't have a backup of mmcblk0p5, but even if I try (out of desperation) to flash someone else's mmcblk0p5, ID doesn't change from zeros. I managed to run CM7 from external sdcard, but installing CM onto mmc doesn't seem to work.
Ubuntu Total Reflash from this forum flashed al successfully, but failed on recovering stage and since then it just bootloops to that point (boot -> factory reset fails -> reboot).
Now trying to flash stock ROM 1.4.0, but don't think it'll work. Any advice?
P.S. Now found something strange: mmcblkp7 (seventh partition is gone, and that seem to repeat after every recovery option I try).
Code:
Number Start (sector) End (sector) Size Code Name
1 256 511 128.0 KiB 8300 xloader
2 512 1023 256.0 KiB 8300 bootloader
3 1024 31743 15.0 MiB 8300 recovery
4 32768 65535 16.0 MiB 8300 boot
5 65536 163839 48.0 MiB 8300 rom
6 163840 262143 48.0 MiB 8300 bootdata
8 1019904 2273279 612.0 MiB 8300 system
9 2273280 3145727 426.0 MiB 8300 cache
10 3145728 5242879 1024.0 MiB 8300 media
11 5242880 30535639 12.1 GiB 8300 userdata
UPD.: Paste from parted's print after I create partition 7 (factory):
Code:
(parted) print
print
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
Your NT's factory installed device info (ProductID, manufactured data, etc.) and individual device data (serial no., MAC address, security encryption keys, etc.) are stored in p5 and p7, if you reformatted these two partitions all that info was wiped out and the individual device data can't be replaced with data from another NT. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more details.
digixmax said:
Your NT's factory installed device info (ProductID, manufactured data, etc.) and individual device data (serial no., MAC address, security encryption keys, etc.) are stored in p5 and p7, if you reformatted these two partitions all that info was wiped out and the individual device data can't be replaced with data from another NT. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more details.
Click to expand...
Click to collapse
Oh, that's unfortunate. I didn't wipe it by myself, it just suddenly got stuck after i got ~4% of battery charge the other day. Can I do something for it?
P.S. Or, if nothing can be done, what's the most simplistic/minimalistic yet full-[stock]-feature ROM for sdcard available? Disregarding Android verion.
digixmax said:
Your NT's factory installed device info (ProductID, manufactured data, etc.) and individual device data (serial no., MAC address, security encryption keys, etc.) are stored in p5 and p7, if you reformatted these two partitions all that info was wiped out and the individual device data can't be replaced with data from another NT. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more details.
Click to expand...
Click to collapse
Huh, seems like I did it. I even can't recall all the steps I performed, but it included just little more messing up with gdisk/parted, trying to wipe all data and caches through CWM and install CM10.1, but that failed as usually, so I just uploaded Veronica's mmcblk0p5 again, then I thought "wtf, let's give it another try" and applied Ubuntu Total Reflash procedure and it worked! All of a sudden, I have my factory-state Nook (saying nothing about case cracks and fractures ^_^).
So, now I'm going to share link to this post with all the people I think are relevant to this question and ask them: is that normal? Can I try to flash CM 10.1 now without *too much* risk of getting my dear brick again? Thanks in advance.
UPD: Checked ID, MAC and so on - seems to be different from 00...0, but I'm not sure whether it's still unique (i reckon that they are like Veronica's now).
UPD2: Installed CM 10.1 rather successfully. I guess, someone can add to FAQ that even with broken mmcblk0p5 one still could help himself.
Related
Hi .
I 'm going to use "dd" to write my pre backuped img to my nook tablet.
I connect my nook to my computer, and then boot my nook into cmw, using adb to check my partition table.
Code:
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4338MB ext4 userdata
and then ,I format them one by one. when i 'm just going to write the backuped partition img to the device with "dd" , my nook went to reboot.
The accident is that my nook reboot before i rewrite the img.
so , the nook can't boot. even the N screen won't show up,the screen is totally black,even the back light .
I 've tried insert a bootable sdcard and the screen won't light up either.
neither can't i connect my nook via adb.when i connect my nook to the computer ,and holding the power button ,i just can see a new device named "OMAP 4430".
I think maybe this is because that the bootloader is broken.
Do you think there's any way to access my nook and re write the img to the missing partition ?Or it's a totally brick?
Thanks for your help.
gpthimble said:
Hi .
I 'm going to use "dd" to write my pre backuped img to my nook tablet.
I connect my nook to my computer, and then boot my nook into cmw, using adb to check my partition table.
Code:
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4338MB ext4 userdata
and then ,I format them one by one. when i 'm just going to write the backuped partition img to the device with "dd" , my nook went to reboot.
The accident is that my nook reboot before i rewrite the img.
so , the nook can't boot. even the N screen won't show up,the screen is totally black,even the back light .
I 've tried insert a bootable sdcard and the screen won't light up either.
neither can't i connect my nook via adb.when i connect my nook to the computer ,and holding the power button ,i just can see a new device named "OMAP 4430".
I think maybe this is because that the bootloader is broken.
Do you think there's any way to access my nook and re write the img to the missing partition ?Or it's a totally brick?
Thanks for your help.
Click to expand...
Click to collapse
Check out this YouTube vid by raywaldo & see if it works for you, http://www.youtube.com/watch?v=ZIrgkjen8ro&feature=related. Hope this helps.
LMN8R said:
Check out this YouTube vid by raywaldo & see if it works for you, http://www.youtube.com/watch?v=ZIrgkjen8ro&feature=related. Hope this helps.
Click to expand...
Click to collapse
Thanks.
i've watched the video, and want to try it, but seems the download links in this viedo is unavailable .
as a result i 'll try this one.
http://forum.xda-developers.com/showthread.php?t=1470910&highlight=unbrick
because i see it says
This post can unbrick any Nook Tablet as long as there is no hardware damage.
This will also work if you've damaged the bootloaders or recovery partition.
Click to expand...
Click to collapse
I'll try and post the result back.
Please do let us know the status of this. Also share any further problems you have.
Sent from my PG06100 using xda premium
for the benefit of others
That should work for you. I just wanted to caution the 8GB NT owner's that the post referenced originated prior to the release of their tablets and isn't applicable.
I have an Nook Tablet 8GB working fine with MIUI. I tried to install stock rom and suddenly something "happened".
I installed an APK to flash cwm, and the nook stocks in a CWM bucle. Then lights went off.
I've tried everything but the nook won't boot. The nook stills alive because if I format a SD card in this way ( http://androidforums.com/nookcolor-...-twrp-2-1-1-bootable-sd-card-4-22-2012-a.html ) - yep, I know this is for Nook Color but still works - the nook starts in a CWM Recovery .
My first thought was ok, it's still alive. If I try do something with this recovery, it says that there is a problem mounting /system !
Then I tried to format a SDCard and install ALL the unbrick methods one by one but no one runs, no one boots. BUT If I try with the CWM SdCard of Nook colors will boot !
If I overwrite the SDCard of the Nook color with the files of the unbrick the Nook Tablet, works but show me a CWM Recovery (the same recovery with the same errores of the Nook Color's method )
I don't know what to do. I tried almost everything and the Nook doesn't boot.
Please, HELP !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ps: sorry for my bad english
Hi,
You cant use a recovery made for other system, it will format wrong partitions or something bad will happen if you try to flash anything from it.
We need your partition table to see what you have done to it so far.
demetris_I said:
Hi,
You cant use a recovery made for other system, it will format wrong partitions or something bad will happen if you try to flash anything from it.
We need your partition table to see what you have done to it so far.
Click to expand...
Click to collapse
How can I show you my partition table?
Regards
I'm wondering if I could enter in fastboot mode I'll be able to reformat and repartionate the eMMC and flash whatever ROM directly form *.img file, I guess.
Is possible enter in Fastboot mode in the nook?
Regards
Any ideas?
Nook Color CWM Card
Ok since you used the wrong recovery you need to got to this forum
http://forum.xda-developers.com/showthread.php?t=1640958
follow the instructions there and reply to me if you need any help It might not work because I don't own a Nook 8gb
P.S. I haven't hit my 10 post threshold so i cant post actual hyperlinks....yet
So uh, you sure you didn't get a defective? Or by chance, a Nook Color?
just make a cwm sd card recovery for NT and boot to it, if you cant and only NC boots then you are in the wrong forum
Ok, I tried again and .... nothing
It was a Nook Tablet refurbished, but worked great before I messed up.
If I can't solve the problem I'll sell the tablet on ebay for 100 $
BTW I remember I've installed this http://forum.xda-developers.com/showthread.php?t=1458630 before get bricked.
It got stuck into a recovery bucle and later,it simply went off
Can anyone with Nt8 try that link in op and report if it boots into cwm? Thanks
Sent from my SGH-T959 using xda app-developers app
rabanomen said:
Ok, I tried again and .... nothing
It was a Nook Tablet refurbished, but worked great before I messed up.
If I can't solve the problem I'll sell the tablet on ebay for 100 $
BTW I remember I've installed this http://forum.xda-developers.com/showthread.php?t=1458630 before get bricked.
It got stuck into a recovery bucle and later,it simply went off
Click to expand...
Click to collapse
the link you provide is cwm for 16gb NT only and is your problem. you need to flash a proper recovery for 8gb NT
good luck!
Ok, finally I understand what I did ... holly shiet
I've installed in the emmc by an error a recovery !!! -And I really don't know how-
So the nook appeared to be dead
Now the nook boots but get stock here :
What should I do now?
PS: If I try to boot in recovery mode I also get freeze
rabanomen said:
Ok, finally I understand what I did ... holly shiet
I've installed in the emmc by an error a recovery !!! -And I really don't know how-
So the nook appeared to be dead
Now the nook boots but get stock here :
What should I do now?
PS: If I try to boot in recovery mode I also get freeze
Click to expand...
Click to collapse
Here is a link with everything you may need about 8gb NT
good luck
Lars for tobdaryl
http://forum.xda-developers.com/showthread.php?t=1644862
God .... nothink works, again
I can't boot from the SD Card any image
Hello , did you try the CWM SDCARD from here
To see the partition table of your Nook tablet you need to run parted using ADB while in CWM.
Here is the output of my 16GB Nook tablet:
~ $ adb shell
* daemon not running. starting it now on port xxxx *
* daemon started succesfully *
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
More information you can find in here, that thread is about repartitioning but it also shows you how to use parted.
Enviame un PM para poderte ayudar en nuestro idoma.
~ Veronica
lavero.burgos said:
Hello , did you try the CWM SDCARD from here
To see the partition table of your Nook tablet you need to run parted using ADB while in CWM.
Here is the output of my 16GB Nook tablet:
~ $ adb shell
* daemon not running. starting it now on port xxxx *
* daemon started succesfully *
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
More information you can find in here, that thread is about repartitioning but it also shows you how to use parted.
Enviame un PM para poderte ayudar en nuestro idoma.
~ Veronica
Click to expand...
Click to collapse
I've sent you a PM. Regards
Ok, at the moment this is my situation :
1. Tried almost every SD Card boot methods. Didn't work
2. Emmc seems to be fine
3. ABD didn't recognize Nook in "loading" state.
4. I want to crash the nook with a hammer
:crying:
I don't know what to do.
I dont know about anyone else but the partition layout on the S3 LTE really bother's me it just wastes so much
has any work been done on seeing if resizing causes any problems
as im tempted to resize cache,system,hidden to pull back 1971mb of space wasted by samsung
then make a custom full odin package with the new partition sizes and flash
clearly i wouldnt be able to use standard samsung packages anymore and would have to make my own
which isnt a problem
All sizes are in true Megabyte/Gigabyte what is called Mib/Gib by people of late
to try and differentiate from the stupid ass rounding hd manufacturers started
TOMBSTONES = 256mb
CACHE = 1024mb
SYSTEM = 1536mb
HIDDEN = 560mb
Leaving 10.8GB for userdata
Im unsure what the tombstones dir is used for so i would be inclined to leave it
but cache can be dropped to 100mb if not using ota updates which i dont
system i could drop to 1024mb and be fine
i dont think hidden is used on the s3 lte
so i could pull back around 1971mb of wasted space
for userdatea with partitions like below
CACHE = 100mb
SYSTEM = 1024mb
HIDDEN = 1mb
Here's the current layout
Note it isnt even 16 fake GB
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB ext4 TOMBSTONES
12 432MB 1506MB 1074MB ext4 CACHE
13 1506MB 3116MB 1611MB ext4 SYSTEM
14 3116MB 3704MB 587MB ext4 HIDDEN
15 3704MB 3712MB 8389kB OTA
16 3712MB 15.8GB 12.0GB ext4 USERDATA
ShonkUK said:
I dont know about anyone else but the partition layout on the S3 LTE really bother's me it just wastes so much
has any work been done on seeing if resizing causes any problems
as im tempted to resize cache,system,hidden to pull back 1971mb of space wasted by samsung
then make a custom full odin package with the new partition sizes and flash
clearly i wouldnt be able to use standard samsung packages anymore and would have to make my own
which isnt a problem
All sizes are in true Megabyte/Gigabyte what is called Mib/Gib by people of late
to try and differentiate from the stupid ass rounding hd manufacturers started
TOMBSTONES = 256mb
CACHE = 1024mb
SYSTEM = 1536mb
HIDDEN = 560mb
Leaving 10.8GB for userdata
Im unsure what the tombstones dir is used for so i would be inclined to leave it
but cache can be dropped to 100mb if not using ota updates which i dont
system i could drop to 1024mb and be fine
i dont think hidden is used on the s3 lte
so i could pull back around 1971mb of wasted space
for userdatea with partitions like below
CACHE = 100mb
SYSTEM = 1024mb
HIDDEN = 1mb
Click to expand...
Click to collapse
You can do it with PIT Magic i did this before for S2 I'd like to do the same thing with s3 but i don't have the PIT file for the international version (My Phone )
I have a NOOK tablet 16GB that is somehow locked from modifying partitions
I have tried
the repart image , which has worked many times for me in the past
the AdamOutler Ubuntu Disk
formatting / wiping options in various versions of CWM and TWRP
fastboot erases
fastboot formats
dd'ing /zero to various partitions
parted
sgdisk
a zillion scripts
something at a low level is preventing modifications to the partitions
Im wasting far too much time on this , but I hate being beat (-:
I have a backup of rom and factory , and dd images of stock parttions so I am 100% comfortable with something that
will COMPLETELY ZAP the device
if I boot a known good CM10 image from SD card, it fails to boot , I was assuming if I could get a running android from the card, I'd have access to lots of tools... , but it just fails to tun CM10
any help appreciated.
Thanks
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
sagirfahmid3 said:
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
Click to expand...
Click to collapse
Thanks for responding, Yes, I have tried multiple ways to to zap the table and it doesnt stick.
sgdisk -Z, sgdisk -z parted,
no matter what I do the partitions remain untouched.
I reboot and it still boots into an old stock OS that has a FC shortly after startup, and the internal recovery (factory) , which I can not overwrite, gives the please restart and try again message.
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
mikeataol said:
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
Click to expand...
Click to collapse
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
sagirfahmid3 said:
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
Click to expand...
Click to collapse
Hi, no, I didnt forget to "write" after the "o"
/tmp # ./gdisk /dev/block/mmcblk0
./gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Command (? for help): o
o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
y
Command (? for help): w
w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
/tmp # q
/tmp #
after reboot
Command (? for help): p
p
Disk /dev/block/mmcblk0: 31105024 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): CE21388C-B927-4A5C-91CE-DBD1DE4AB3BC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535678
Partitions will be aligned on 256-sector boundaries
Total free space is 1285 sectors (642.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 256 511 128.0 KiB 8300 xloader
2 512 1023 256.0 KiB 8300 bootloader
3 1024 31743 15.0 MiB 8300 recovery
4 32768 65535 16.0 MiB 8300 boot
5 65536 163839 48.0 MiB 8300 rom
6 163840 262143 48.0 MiB 8300 bootdata
7 262144 1019903 370.0 MiB 8300 factory
8 1019904 2273279 612.0 MiB 8300 system
9 2273280 3145727 426.0 MiB 8300 cache
10 3145728 5242879 1024.0 MiB 8300 media
11 5242880 30535639 12.1 GiB 8300 userdata
Humm...wow, that's pretty crazy. Try writing zeroes to your emmc and then retrying.
# dd if=/dev/zero of=/dev/block/mmcblk0
I was running Chucktr's CM11 12.16 rom. Went to turn on phone, and got a black screen after the white HTC boot up screen. When I did get it to boot to the bootloader, the recovery did not work either. I got TWRP 2.8.0.1 installed, and can see from there, that there is problems mounting.
E: Primary block device /dev/block/mmcblk0p35 for mount point '/data' is not present!
E: Unable to recreate and-sec folder.
Updating partition details...
e: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
and so on.
Update 2/22/15: Results of parted
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
p
Error: Invalid partition table on /dev/block/mmcblk0 -- wrong signature 0.
Ignore/Cancel? i
i
i
Model: MMC KYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 132kB 131kB primary boot
2 132kB 394kB 262kB primary
3 394kB 33.5MB 33.1MB primary
4 33.5MB 15.8GB 15.7GB extended
5 33.5MB 33.6MB 16.4kB logical
6 33.6MB 33.8MB 262kB logical
7 33.8MB 54.8MB 20.9MB logical
8 54.8MB 55.0MB 262kB logical
9 55.0MB 56.1MB 1049kB logical
10 56.1MB 56.3MB 262kB logical
11 56.3MB 58.4MB 2097kB logical
12 58.4MB 59.5MB 1049kB logical
13 59.5MB 59.5MB 32.8kB logical
14 59.5MB 65.8MB 6291kB logical
15 65.8MB 66.8MB 1049kB logical
16 66.8MB 67.1MB 262kB logical
17 67.1MB 109MB 41.9MB logical
18 109MB 151MB 41.9MB logical fat16
19 151MB 159MB 8388kB logical
20 159MB 168MB 8387kB logical
21 168MB 201MB 33.6MB logical fat16
22 201MB 218MB 16.8MB logical
23 218MB 235MB 16.8MB logical
24 235MB 252MB 16.8MB logical
Any ideas on where to start with fixing this?
amgold said:
I was running Chucktr's CM11 12.16 rom. Went to turn on phone, and got a black screen after the white HTC boot up screen. When I did get it to boot to the bootloader, the recovery did not work either. I got TWRP 2.8.0.1 installed, and can see from there, that there is problems mounting.
E: Primary block device /dev/block/mmcblk0p35 for mount point '/data' is not present!
E: Unable to recreate and-sec folder.
Updating partition details...
e: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
and so on.
Update 2/22/15: Results of parted
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
p
Error: Invalid partition table on /dev/block/mmcblk0 -- wrong signature 0.
Ignore/Cancel? i
i
i
Model: MMC KYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 132kB 131kB primary boot
2 132kB 394kB 262kB primary
3 394kB 33.5MB 33.1MB primary
4 33.5MB 15.8GB 15.7GB extended
5 33.5MB 33.6MB 16.4kB logical
6 33.6MB 33.8MB 262kB logical
7 33.8MB 54.8MB 20.9MB logical
8 54.8MB 55.0MB 262kB logical
9 55.0MB 56.1MB 1049kB logical
10 56.1MB 56.3MB 262kB logical
11 56.3MB 58.4MB 2097kB logical
12 58.4MB 59.5MB 1049kB logical
13 59.5MB 59.5MB 32.8kB logical
14 59.5MB 65.8MB 6291kB logical
15 65.8MB 66.8MB 1049kB logical
16 66.8MB 67.1MB 262kB logical
17 67.1MB 109MB 41.9MB logical
18 109MB 151MB 41.9MB logical fat16
19 151MB 159MB 8388kB logical
20 159MB 168MB 8387kB logical
21 168MB 201MB 33.6MB logical fat16
22 201MB 218MB 16.8MB logical
23 218MB 235MB 16.8MB logical
24 235MB 252MB 16.8MB logical
Any ideas on where to start with fixing this?
Click to expand...
Click to collapse
Are you S-OFF? If you are, grab an RUU (a real RUU that is the EXE file that runs from Windows, not a flashable ZIP) and run it, reflash back to complete stock, and see if you can recovery that way, it is your best chance (sometimes this needs to be done twice)... If you are S-ON, well, you are probably screwed.
The real underlying issue here is WHY did the partition table get corrupted,the life of the flash memory in this device is less than expected by most people... a lot of Rez's die because of failure of the internal flash memory, I have seen several of them myself.
acejavelin said:
Are you S-OFF? If you are, grab an RUU (a real RUU that is the EXE file that runs from Windows, not a flashable ZIP) and run it, reflash back to complete stock, and see if you can recovery that way, it is your best chance (sometimes this needs to be done twice)... If you are S-ON, well, you are probably screwed.
The real underlying issue here is WHY did the partition table get corrupted,the life of the flash memory in this device is less than expected by most people... a lot of Rez's die because of failure of the internal flash memory, I have seen several of them myself.
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately I am S-ON. I've looked unsuccessfully for a way to S-OFF without running software but have not found anything. Starting to feel like I now own a paperweight.
amgold said:
Thanks for your reply. Unfortunately I am S-ON. I've looked unsuccessfully for a way to S-OFF without running software but have not found anything. Starting to feel like I now own a paperweight.
Click to expand...
Click to collapse
Your chances of recovery at this point are very slim then... S-off is not possible on a non-bootable device, you can try multiple recoveries (CWM, TWRP, Amon Ra) and multiple format/wipes and flashing different ZIP packages, once in a while it recovers itself, but without access to the partition table via S-Off the chances are extremely low.
As I said before, the flash RAM in this device seems to be reaching its life span limits for lots of people... Nothing you did, it's just reaching its limits of writes and starting to fail.
acejavelin said:
Your chances of recovery at this point are very slim then... S-off is not possible on a non-bootable device, you can try multiple recoveries (CWM, TWRP, Amon Ra) and multiple format/wipes and flashing different ZIP packages, once in a while it recovers itself, but without access to the partition table via S-Off the chances are extremely low.
As I said before, the flash RAM in this device seems to be reaching its life span limits for lots of people... Nothing you did, it's just reaching its limits of writes and starting to fail.
Click to expand...
Click to collapse
This has to do with normal phone operation, right? Not how many times you've flashed ROMs? Curious because I rarely flash ROMs so wondering if that would mean my phone might have a longer life. I would be fine with it for another couple years.
feralicious said:
This has to do with normal phone operation, right? Not how many times you've flashed ROMs? Curious because I rarely flash ROMs so wondering if that would mean my phone might have a longer life. I would be fine with it for another couple years.
Click to expand...
Click to collapse
Emmc (your phones flash RAM) has a finite number of writes, when it reaches that point there is nothing you can do. It has nothing to do with flashing ROMs, it happens to completely stock devices as well... Like any other product, there are good ones and bad ones, some last longer than others, just the way it is. You didn't cause it to happen, normal use did, it was just it's time.