ShaunMT's TWRP Recovery For The Nextbook NX785QC8G-NXM865FD_WMDE (Support Thread)

[shaunmt]

The tablet in question is indeed an international model, sold in Iceland.

That increases the odds that it is actually the same hardware, with a different model number.

The package advertizes it as a Nextbook8, with NX785QC8G as the
model number, and it says eFun and Nextbook all over the package in
several places. So...same Brand, different market. Maybe the NX stands
for the american market while EB refers to the european one? It's
manufactured in March 1015, SerialNr is YF03150****

eFun is the North American (U.S.) marketing division of Yifang Digital that distributes Nextbook branded products.

I believe the NX is short for Nextbook, but I suppose it could be a code for North America.

I have no idea what EB stands for, but you could be correct about it standing for European something.

I have also noticed that they sometimes add letters to the product names/numbers to indicate special builds for exclusive retailers such as WM for Wal Mart.

I had the same problem with slightly varying hardware back with my old
Next8HD8G last year in august or september, you actually did help me
recover from a softbrick, and TWRP was working on THAT tab without
problems even despite of the different hardware IDs.

yeah, that was one of the messiest models they ever made. Numerous different hardware and software versions.

I think the recovery was actually compatible with most, if not all of them, but some models required different hardware drivers for the screen or wifi.

I do in fact have two identical NX785QC8G tablets of this type available
now, so even if I softbrick one of them, recovery should be possible using
the rom taken from the other.

That's always a plus!

I've rooted both of them with KingoRoot earlier today, so there's that,
it's a first step in the right direction.

Adding xPosed and a third party launcher are good next steps.

There isn't much to be gained from my ROM other than my splash screens, full ADB access and init.d support.

Few people need full ADB access except developers. Most don't need init.d scripting support either, and it can be added in other ways anyhow.

Next I will first poke the thing with the nandroid backup tool, then read
up on the rockchip tools and learn how to use those for a backup. That's
something for Saturday and Sunday.

Good luck with that. Make sure you get the latest version. (I don't know what the latest version is.)

The BIG step will be getting TWRP Recovery running on it. Even if
the resized partitions patch might not work, at least TWRP would be
VERY nice to have.

My TWRP will almost certainly work.

Just make sure you have a backup of the stock recovery and flash TWRP by itself. I would use either the Rockchip flash tools or a flash tool from the play store before trying my installer.

Then if it doesn't work perfectly, you can use either the rockchip flash tools to flash the stock recovery back, or boot into android and use a flash tool from the play store to flash the stock recovery back.

Also, be careful not to wipe the entire device or the parameter file using the Rockchip flash tool... that would be difficult to fix, though not impossible.

ShaunMT

P.S. When you get a backup, upload it somewhere and send me a link. I can take a look and try to compare it to my ROM and advise if I see any compatibility problems or not.

[Clyde]

Hi,

Made a backup of the stock firmware using AndroidTool v2.1. I'm leaving the stock firmware
up at http://kyr.mooo.com/%5CNX785QC8G for now.

I also unpacked your twrp update.img to get my hands on the recovery.img itself, then
flashed that one over the stock recovery again using AndroidTool v2.1.

Seems twrp is running now but is having problems mounting \sdcard, it keeps complaining
in bold red letters about that.

Best regards,
-Clyde

[shaunmt]

Hi,

Made a backup of the stock firmware using AndroidTool v2.1. I'm leaving the stock firmware
up at http://kyr.mooo.com/%5CNX785QC8G for now.

I also unpacked your twrp update.img to get my hands on the recovery.img itself, then
flashed that one over the stock recovery again using AndroidTool v2.1.

Seems twrp is running now but is having problems mounting \sdcard, it keeps complaining
in bold red letters about that.

Best regards,
-Clyde

Thanks, I will try to take a look at your backup sometime this weekend.

Sounds like your /sdcard either has a different mountpoint, or needs to be reformatted... If you were having problems with your internal /sdcard before installing TWRP, try reformatting it...

If your /sdcard was working correctly before you installed TWRP, then wait until I can take a look at your backup.

[Clyde]

Hi,

I'm suspecting it's a mountpoint issue, since there were no problems
with the internal /sdcard before installing TWRP. Also, the problem does
persist on both tablets. Identical hardware, so that was to be expected.

I've taken a screenie of the error messages TWRP gives, taken right
after booting into TWRP. It's up at http://imgur.com/vGECLZ4 in case
it helps.

The firmware image mentioned above was taken right after factory
reset, by the way. I'll leave that one up for download on my webserver
for a while.

Ohh, Factory Reset itself as done from within the tablet's 'Settings' menu
does not work with TWRP installed, only with the stock recovery. It's
prolly related to the \sdcard mounting problem.

I wish I could be more helpful with this. Learning as I go, though.

Best regards,
-Clyde

[shaunmt]

Hi,

I'm suspecting it's a mountpoint issue, since there were no problems
with the internal /sdcard before installing TWRP. Also, the problem does
persist on both tablets. Identical hardware, so that was to be expected.

I've taken a screenie of the error messages TWRP gives, taken right
after booting into TWRP. It's up at http://imgur.com/vGECLZ4 in case
it helps.

The firmware image mentioned above was taken right after factory
reset, by the way. I'll leave that one up for download on my webserver
for a while.

Ohh, Factory Reset itself as done from within the tablet's 'Settings' menu
does not work with TWRP installed, only with the stock recovery. It's
prolly related to the \sdcard mounting problem.

I wish I could be more helpful with this. Learning as I go, though.

Best regards,
-Clyde

The error message in your screenshot could be caused by either a bad mountpoint, or a partition that needs to be reformatted...

I agree with you though, it sounds like the mountpoint defined in the recovery doesn't match the mountpoint defined in the stock ROM.

Would you mind taking all those zip files and copying them into a folder and then zipping it all up together in a single file with your model and board name for me? That way I don't get them mixed up with any of my other files.

[Clyde]

Hi,

I've zipped up the individual partitions into one file. You can get it at

http://kyr.mooo.com/NX785QC8G/NX785QC8G_EBM865FD_rk30sdk.zip

Best regards,
-Clyde

[ken.taning]

Hi,

I've zipped up the individual partitions into one file. You can get it at
http://kyr.mooo.com/NX785QC8G/NX785Q...FD_rk30sdk.zip

Best regards,
-Clyde

hai im new to android so please pardon me of my innocence, we exactly have similar build.prop so i presumed if something goes wrong i should be able to restore my device using this firmware. my question is can i flash using stock recovery or using the windows rkflash tools(i dont know the exact name of the tools) or is there any other way? tnx

[Clyde]

Hi,

the firmware images were created with the RK Android Tools 2.1 you can download
at the link I've provided below. Create a folder 'Output' in the 'RK Rom Dumper & Flasher'
folder after extracting that package, unpack the firmware image there, and in the
'Flasher Tool' folder you will find the right tool to flash the firmware. Take note that
this does not include the 'user' or 'userdata' partition, and that you should check
and adapt the address offset for each partition before flashing. The correct
address offset for each partition can be found in your parameter.txt file. Do read
the exhaustive instructions file that comes with the flasher tools before you use
them. I will not be held responsible if you brick your tablet.

Best regards,
-Clyde

[Xprime]

Hello ShaunMT,

and thanks for the quick and comprehensive answer.

The tablet in question is indeed an international model, sold in Iceland.
The package advertizes it as a Nextbook8, with NX785QC8G as the
model number, and it says eFun and Nextbook all over the package in
several places. So...same Brand, different market. Maybe the NX stands
for the american market while EB refers to the european one? It's
manufactured in March 1015, SerialNr is YF03150****

I had the same problem with slightly varying hardware back with my old
Next8HD8G last year in august or september, you actually did help me
recover from a softbrick, and TWRP was working on THAT tab without
problems even despite of the different hardware IDs.

I do in fact have two identical NX785QC8G tablets of this type available
now, so even if I softbrick one of them, recovery should be possible using
the rom taken from the other.

I've rooted both of them with KingoRoot earlier today, so there's that,
it's a first step in the right direction.

Next I will first poke the thing with the nandroid backup tool, then read
up on the rockchip tools and learn how to use those for a backup. That's
something for Saturday and Sunday.

The BIG step will be getting TWRP Recovery running on it. Even if
the resized partitions patch might not work, at least TWRP would be
VERY nice to have.


Best regards,
-Clyde

Clyde


Clyde I have the same tablet.. same as the build.prop you have... and I'm using Shaun's TWRP and parameter patches everything works for me.. I'm just waiting for Shaun to release the 3gb version of the parameter patch.. but if you are asking if it would work.. answer is yes no fail.. I've done it so many times bro.

[Clyde]

Hi,

there seems to be SOMETHING different about our tablets,
XPrime. Encouraged by your post, I did look up your other
posts and did tried to flash the tab with the TWRP recovery
as you did in your step-by-step guide post.

I started out with a fresh factory reset tab, stock firmware.

I formatted a 32gb microSD, did copy the update.img from Shaun's
SMT-NX785QC8G-NXM865FD_WMDE-TWRP_rkimage.zip onto
the card, inserted it into the tablet, did boot into recovery with
VolumeUp+Power, then flashed the update.img from there.

The flash took much longer than expected, a good 5 minutes
at least.

Afterwards I could boot into TWRP, still getting the same
ext_sdcard not found type errors I always did before, BUT
flashing from the update.img did actually mess up my
parameter file and the tablet would not boot into Android
anymore.

At that point I recovered from the softbrick by flashing
with my stock image with AndroidTools and poked around
some with the contents of Shauns update.img. Seems
the parameter file included in the scripts there is
different from what my tablet uses.

For comparision: The parameter.txt used by my tab:

FIRMWARE_VER:1.0.0
MACHINE_MODEL:NX785QC8G
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00006000@0x00004000(kernel),0x00006000@0x0000a000( boot),0x00010000@0x00010000(recovery),0x00020000@0 x00020000(backup),0x00080000@0x00040000(cache),0x0 0002000@0x000C0000(metadata),0x00002000@0x000C2000 (kpanic),0x00200000@0x000C4000(system),-@0x002C4000(userdata)

And the parameter files from Shaun's TWRP update:
FIRMWARE_VER:2.0.8
MACHINE_MODEL:NX785QC8G
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00006000@0x00004000(kernel),0x00006000@0x0000a000( boot),0x00010000@0x00010000(recovery),0x00020000@0 x00020000(backup),0x00040000@0x00040000(cache),0x0 01FE000@0x00080000(userdata),0x00002000@0x0027E000 (metadata),0x00002000@0x00280000(kpanic),0x0030000 0@0x00282000(system),-@0x00582000(user)

Note how I seem to have no 'user' partition, and what is named 'user' in Shaun's file is 'userdata' for me. Also
the offsets are different.

Best regards
-Clyde

[shaunmt]

Hi,

there seems to be SOMETHING different about our tablets,
XPrime. Encouraged by your post, I did look up your other
posts and did tried to flash the tab with the TWRP recovery
as you did in your step-by-step guide post.

I started out with a fresh factory reset tab, stock firmware.

I formatted a 32gb microSD, did copy the update.img from Shaun's
SMT-NX785QC8G-NXM865FD_WMDE-TWRP_rkimage.zip onto
the card, inserted it into the tablet, did boot into recovery with
VolumeUp+Power, then flashed the update.img from there.

The flash took much longer than expected, a good 5 minutes
at least.

Afterwards I could boot into TWRP, still getting the same
ext_sdcard not found type errors I always did before, BUT
flashing from the update.img did actually mess up my
parameter file and the tablet would not boot into Android
anymore.

At that point I recovered from the softbrick by flashing
with my stock image with AndroidTools and poked around
some with the contents of Shauns update.img. Seems
the parameter file included in the scripts there is
different from what my tablet uses.

For comparision: The parameter.txt used by my tab:

FIRMWARE_VER:1.0.0
MACHINE_MODEL:NX785QC8G
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00006000@0x00004000(kernel),0x00006000@0x0000a000( boot),0x00010000@0x00010000(recovery),0x00020000@0 x00020000(backup),0x00080000@0x00040000(cache),0x0 0002000@0x000C0000(metadata),0x00002000@0x000C2000 (kpanic),0x00200000@0x000C4000(system),-@0x002C4000(userdata)

And the parameter files from Shaun's TWRP update:
FIRMWARE_VER:2.0.8
MACHINE_MODEL:NX785QC8G
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x 00006000@0x00004000(kernel),0x00006000@0x0000a000( boot),0x00010000@0x00010000(recovery),0x00020000@0 x00020000(backup),0x00040000@0x00040000(cache),0x0 01FE000@0x00080000(userdata),0x00002000@0x0027E000 (metadata),0x00002000@0x00280000(kpanic),0x0030000 0@0x00282000(system),-@0x00582000(user)

Note how I seem to have no 'user' partition, and what is named 'user' in Shaun's file is 'userdata' for me. Also
the offsets are different.

Best regards
-Clyde

That explains why it doesn't work perfectly for everyone.

Looks like you never got the official Nextbook update.

The backup and restore of your existing system most likely fails because of the parameter differences.

You should still be able to get everything installed using my files, you will just have to manually reformat the data, cache, and internal sd card before reflashing my ROM (and possible again after too) instead of your backup.

ShaunMT

[ankithmathew]

will the rom fix the partitioned internal storage and combine them?

[shaunmt]

will the rom fix the partitioned internal storage and combine them?

It won't combine them, but it should fix them and there are patches for different sizes.

[odarie]

hi i have a next8p12 tablet show red light pc recognize it but i can not load software i believe it brick the screen shows pitch blackhelp!!!!!!!!

[shaunmt]

hi i have a next8p12 tablet show red light pc recognize it but i can not load software i believe it brick the screen shows pitch blackhelp!!!!!!!!

How did the tablet end up in the current condition?

What were you (or are you) trying to install and how?