CWM Recovery with UBIFS Support For Amlogic Nextbook Tablets (Support Thread)

[shaunmt]

CWM For the Next8HD8G-NXM8000NBD_WMN Has Been Released

I just updated the Download page with a download link for CWM for the Next8HD8G-NXM8000NBD_WMN.

Coming next will be the unbrick kits and updated stock based ROMs for both the Next8HD8G-NXM8000ND_WM and the Next8HD8G-NXM8000NBD_WMN, followed by CWM, unbrick kits and updated stock based ROMS for the Next7P12-8G. Watch for new threads.

ShaunMT

[pabeader]

Thank you for all your dedication to this project!

Do you think we will see custom roms from somebody, now that CWM has been perfected?

[locuraconsigueusted]

I just updated the Download page with a download link for CWM for the Next8HD8G-NXM8000NBD_WMN.

Coming next will be the unbrick kits and updated stock based ROMs for both the Next8HD8G-NXM8000ND_WM and the Next8HD8G-NXM8000NBD_WMN, followed by CWM, unbrick kits and updated stock based ROMS for the Next7P12-8G. Watch for new threads.

ShaunMT

This got mine to boot (into CWM) . Seems like it was a WMN.

Now all I need is to find someone with a WMN CWM backup they can send me (anyone?)

EDIT: For whatever reason, I went to "Fix Permissions" and it told me:


"E:cannot mount ubifs /dev/ubi0_0 to /system
E:cannot mount ubifs /dev/ubi0_0 to /data
Fixing Permissions...
Done!"

At times, it says "... ubi1_0 to /system"

This also happens with Backing up. I formatted the data partition and it fixed it for /data, but not for /system. This means it is a corrupt filesystem, correct?

Could this have been my problem (why it went into a boot loop)?

Thanks,
locuraconsigueusted

[pabeader]

oh no!

Apparently, I had the wrong version on my sd-card. I just tried to get a backup of my wife's RED NX and it wouldn't boot into CWM. Now it won't boot at all!!!
It gets to the girl with the headphones and that's it. I take it that it is now a brick and I'm waiting for the unbrick kits.

I am going to play dumb for now. Maybe we'll just exchange it for a new one. Depends on what she thinks when she gets up.

How soon do you think you'll have the unbrick kits ready?

[locuraconsigueusted]

Apparently, I had the wrong version on my sd-card. I just tried to get a backup of my wife's RED NX and it wouldn't boot into CWM. Now it won't boot at all!!!
It gets to the girl with the headphones and that's it. I take it that it is now a brick and I'm waiting for the unbrick kits.

I am going to play dumb for now. Maybe we'll just exchange it for a new one. Depends on what she thinks when she gets up.

How soon do you think you'll have the unbrick kits ready?

Same symptoms I have. I think mine is because of file system corruption (check previous post). Check if that is your problem by downloading the correct version and and attempting any of the things I mentioned doing.

Thanks,
locuraconsigueusted

[rbitting]

ShaunMT is the Man

I just updated the Download page with a download link for CWM for the Next8HD8G-NXM8000NBD_WMN.

Coming next will be the unbrick kits and updated stock based ROMs for both the Next8HD8G-NXM8000ND_WM and the Next8HD8G-NXM8000NBD_WMN, followed by CWM, unbrick kits and updated stock based ROMS for the Next7P12-8G. Watch for new threads.

ShaunMT

Thank you soooooo much! Now with CWM I love this cheap little Nextbook.
Cannot wait for the unbrick kits. Thank you ShaunMT!!!!!!!!!!!!!!!

[pabeader]

Same symptoms I have. I think mine is because of file system corruption (check previous post). Check if that is your problem by downloading the correct version and and attempting any of the things I mentioned doing.

Thanks,
locuraconsigueusted

What's weird is that all i did was try to boot the wrong CWM. didn't even try to load a different ROM.

[shaunmt]

Thank you for all your dedication to this project!

Do you think we will see custom roms from somebody, now that CWM has been perfected?

I'm still working on a CM10 port.

We aren't going to see a whole lot of customization with a custom kernel though, and I don't have time to learn kernel development right now.

ShaunMT

[shaunmt]

This got mine to boot (into CWM) . Seems like it was a WMN.

Now all I need is to find someone with a WMN CWM backup they can send me (anyone?)

EDIT: For whatever reason, I went to "Fix Permissions" and it told me:


"E:cannot mount ubifs /dev/ubi0_0 to /system
E:cannot mount ubifs /dev/ubi0_0 to /data
Fixing Permissions...
Done!"

At times, it says "... ubi1_0 to /system"

This also happens with Backing up. I formatted the data partition and it fixed it for /data, but not for /system. This means it is a corrupt filesystem, correct?

Could this have been my problem (why it went into a boot loop)?

Thanks,
locuraconsigueusted

Possibly... it's also possible you used the wrong one. Did you check your build.prop before choosing one?

Using the correct one, formatting /system and /data, then flashing the correct ROM should solve the problem.

I expect the new ROMs to be released within a week.

ShaunMT

[shaunmt]

Apparently, I had the wrong version on my sd-card. I just tried to get a backup of my wife's RED NX and it wouldn't boot into CWM. Now it won't boot at all!!!
It gets to the girl with the headphones and that's it. I take it that it is now a brick and I'm waiting for the unbrick kits.

I am going to play dumb for now. Maybe we'll just exchange it for a new one. Depends on what she thinks when she gets up.

How soon do you think you'll have the unbrick kits ready?

It is quite possible the RED models have new hardware... you are the first I know that has one.

Did you check your build.prop before choosing a CWM version?

Are you still able to boot to recovery? Either stock internal or external?

ShaunMT

[shaunmt]

What's weird is that all i did was try to boot the wrong CWM. didn't even try to load a different ROM.

Booting the wrong kernel seems to be enough to screw up the /system and /data partitions. The partition layout is hardcoded in the kernel. When you boot the wrong kernel, the partitions aren't mapped correctly and it trys to mount them incorrectly. This is why the correct versions have to be used.

ShaunMT

[pabeader]

I'm still working on a CM10 port.

We aren't going to see a whole lot of customization with a custom kernel though, and I don't have time to learn kernel development right now.

ShaunMT

CM10 would be just fine. Whatever you do will be great.

[shaunmt]

CM10 would be just fine. Whatever you do will be great.

I'm working on CM10, because I had to start the device trees to create CWM and this was the best base available with UBIFS patches already created. It continues to offer the least work to get something usable.

If I get it working completely, then it should be simple to use the same device tree for other ROMs like Paranoid Android or PACMAN. It should also be simple to start updating to newer Android versions, although we still need a new kernel before we can boot newer Android versions.

ShaunMT

[locuraconsigueusted]

I'm fairly sure mine is a WMN. It is stick in a bootloop so the only thing that makes me say this is that the WM build wouldn't boot, but the WMN one will. Maybe I should try booting the WM build again?

Sent from my Event using Tapatalk

[shaunmt]

I'm fairly sure mine is a WMN. It is stick in a bootloop so the only thing that makes me say this is that the WM build wouldn't boot, but the WMN one will. Maybe I should try booting the WM build again?

Sent from my Event using Tapatalk

If it will still boot to recovery, one or the other should work. If it won't boot to recovery, you will need an unbrick kit.

ShaunMT