HD PLus Partition Table restoration

[dbolack]

I've tried diving through google and the site looking for a solution to this. Between noise,missed hits, and age, I am not having any luck finding out if this is solvable.

I made the mistake last year of trying the fstrim fix on a model that was clearly a bad idea on - funny how I found all the "DON'T!" articles a year later despite being from before my search. . *ah well* I toyed with the fixes at the time but never had much luck and set it aside for a while.

Started looking again last night and was able to at least determine the Nook isn't dead. CWM comes up, I can hit it with ADB. fdisk doesn't seem to see anything ( which I'm guessing is expected but I'm unsure why ) so I'm uncertain how to restore. the partition tables.

I have an identical model I can clone if there are any sane processes for doing such, but i've been unable to ask search engines the right questions.

Can someone clarify if this is possible or if I'm "stuck" running off of an sd card from now on?

Thanks.

 

[leapinlar]

I've tried diving through google and the site looking for a solution to this. Between noise,missed hits, and age, I am not having any luck finding out if this is solvable.

I made the mistake last year of trying the fstrim fix on a model that was clearly a bad idea on - funny how I found all the "DON'T!" articles a year later despite being from before my search. . *ah well* I toyed with the fixes at the time but never had much luck and set it aside for a while.

Started looking again last night and was able to at least determine the Nook isn't dead. CWM comes up, I can hit it with ADB. fdisk doesn't seem to see anything ( which I'm guessing is expected but I'm unsure why ) so I'm uncertain how to restore. the partition tables.

I have an identical model I can clone if there are any sane processes for doing such, but i've been unable to ask search engines the right questions.

Can someone clarify if this is possible or if I'm "stuck" running off of an sd card from now on?

Thanks.

First, the HD/HD+ does not use a DOS based partition table so fdisk will not work. It has a different system, I think GPT, but not sure it is the right name.

But if you look at my HD+ stock tip thread linked in my signature, you will see I have an article about partition structure there. If you use TWRP on SD it has a terminal emulator that will let you run the routines for backing up and restoring the partitions.

But if you truly messed up with the fstrim fix your device has become read only and it is not fixable.

Sent from my SM-T707V using XDA Premium HD app

 

[dbolack]

First, the HD/HD+ does not use a DOS based partition table so fdisk will not work. It has a different system, I think GPT, but not sure it is the right name.

This is the provided, linuxy fdisk on the CWM image when I did a adb shell, not the host OS, which also isn't dos. Unless it's behaving in a way different than expected, it should detect the block devices even if it does not understand the partitioning table. Newer implementations of fdisk do speak gpt, but I rather doubt that's on the CWM image. I believe you are correct that it is a gpt table. I'll have to verify against my other device.

But if you look at my HD+ stock tip thread linked in my signature, you will see I have an article about partition structure there. If you use TWRP on SD it has a terminal emulator that will let you run the routines for backing up and restoring the partitions.

I'll have to give that a whirl. I hadn't spotted that particular bit.

But if you truly messed up with the fstrim fix your device has become read only and it is not fixable.

I'm not sure. If I run blkid I do see that the two partitions that CWM has a wipe/format seem to have file systems on them, but they are the only ones detected. This makes me think the partitions are borked in some very creative way and I either can't see the table to fix it with the tools I'm using or the tools I need aren't present on my image.

 

[digixmax]

I've tried diving through google and the site looking for a solution to this. Between noise,missed hits, and age, I am not having any luck finding out if this is solvable.

I made the mistake last year of trying the fstrim fix on a model that was clearly a bad idea on ...
...
Can someone clarify if this is possible or if I'm "stuck" running off of an sd card from now on?

If your EMMC is bricked due to "having run fstrim on a faulty EMMC chip", your only option is to run on SD a special "no-emmc" CM ROM such as the one posted at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.

 

[dbolack]

If your EMMC is bricked due to "having run fstrim on a faulty EMMC chip", your only option is to run on SD a special "no-emmc" CM ROM such as the one posted at....

Interestingly, using the link to the buggy EMMC Page at Cynogen ( sorry, newb can't link ) mine is not on the list of known offenders.