Amlogic Next8HD8G (NX008HD8G) Modified Recovery - Stock Rom & Flashable Root

[eedwards]

Rooting alone is not the answer. It also requires changing the fingerprint in the build.prop file to a different tablet with better app support. This means manually editing the file, using an app from the play store to switch the device fingerprint for you, or installing a custom ROM that already has a modified fingerprint.

Your mileage may vary with any of the above methods.

ShaunMT

Ugh...that's way over my head. I'll leave it the way it is.
...but thanks

[shaunmt]

Ugh...that's way over my head. I'll leave it the way it is.
...but thanks

My custom ROMs will include modified fingerprints for better app compatibility, if I ever get them finished...

ShaunMT

[SprayStupid]

Hey guys i've been watching this thread since you started it. I am new to rooting and tried it and failed. I do have the mod stock rom installed but couldn't get root. I stopped before I messed something up, but I am having the issues you posted about with wifi and sdcard mounting and I found that the tablet does start the wifi and sdcard but it takes awhile. I wiped the cache and such and tried to turn on wifi and it just reboots. What I did was let it sit after manually rebooting and wifi came on and the sdcard mounted. I don't know much when it comes to this type of hardware but it seems the processes "hang" at startup. not for sure though.

[shaunmt]

Hey guys i've been watching this thread since you started it. I am new to rooting and tried it and failed. I do have the mod stock rom installed but couldn't get root. I stopped before I messed something up, but I am having the issues you posted about with wifi and sdcard mounting and I found that the tablet does start the wifi and sdcard but it takes awhile. I wiped the cache and such and tried to turn on wifi and it just reboots. What I did was let it sit after manually rebooting and wifi came on and the sdcard mounted. I don't know much when it comes to this type of hardware but it seems the processes "hang" at startup. not for sure though.

I assume you are trying to flash my root package using my modified stock 3e recovery, is that correct?

Which ROM do you currently have installed?

Can you describe the "failure" you experienced? What happened? Was there an error message? If so, what was the error message?

I suspect most, if not all, of the WiFi and SD card mounting problems that some have reported were due to bad flash installs. I myself have experienced this when reflashing a ROM that was previously working just fine, with no previous issues. I had to reformat my external SD Card, redownload the ROM, wipe everything from recovery and then reflash again in order to resolve the issues when it happened to me.

ShaunMT

[SprayStupid]

When I turn on wifi it freezes then reboots. No error. I tried the stuff you had listed in mid september. I don't remember the error as I tried to do it several times and got no results. It could have been me doing something out of order not sure. I failed so hard before I started by not backing anything up to begin with.

[DashHyper]

Any chance to see this tablet withcyanogenmod? By the way you guys are amazing, I called this like a soft root. Right?!?

[shaunmt]

Any chance to see this tablet withcyanogenmod? By the way you guys are amazing, I called this like a soft root. Right?!?

I'm compiling a cyanogenmod build from source for the Next8HD8G as I type. It's still gonna be awhile before it's ready for release though. There are several challenges yet to overcome and I'm still learning as I go.

ShaunMT

[DashHyper]

I'm compiling a cyanogenmod build from source for the Next8HD8G as I type. It's still gonna be awhile before it's ready for release though. There are several challenges yet to overcome and I'm still learning as I go.

ShaunMT

Awsome ShaunMT, thnx

[randomkidsrule]

When I turn on wifi it freezes then reboots. No error. I tried the stuff you had listed in mid september. I don't remember the error as I tried to do it several times and got no results. It could have been me doing something out of order not sure. I failed so hard before I started by not backing anything up to begin with.

Happened to me once, just re-installed the mod stock rom.

[eegorr]

Looks like I just bricked my tablet running your modified stock 3e recovery and root package, Shaun. The uSD card was freshly formatted in my laptop and the uImage_recovery and Kyser_Root-signed.zip are the only files on the card.

The update appeared to run and complete just fine. Here is what was displayed on the screen:

-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installing Kyser Root
Mounting /system
Installing su
Setting Permissions
Creating Symlink
Unmounting System
Finished. Reboot Now

Install from sdcard complete.

The first time I rebooted after I updated from sdcard it got to the screen with the finger and the spinning caterpillar. After a bit, the caterpillar froze in its tracks! I rebooted again and it did the same thing. I ran the update again and now it is stuck at the second screen.

The S/N on this tablet indicates it was built in July (YFG0713XXXXXX). If that is a problem, you might want to make a note of this in your instructions.

My wife's identical tablet has the same build month, although it is quite a bit newer in terms of serial number. Here is the build info for her tablet:

Kernel version: 3.0.8-g1a280e6
Build number: JR003C.v009

Any ideas besides a trip to Walmart?

[shaunmt]

Looks like I just bricked my tablet running your modified stock 3e recovery and root package, Shaun. The uSD card was freshly formatted in my laptop and the uImage_recovery and Kyser_Root-signed.zip are the only files on the card.

The update appeared to run and complete just fine. Here is what was displayed on the screen:

-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installing Kyser Root
Mounting /system
Installing su
Setting Permissions
Creating Symlink
Unmounting System
Finished. Reboot Now

Install from sdcard complete.

The first time I rebooted after I updated from sdcard it got to the screen with the finger and the spinning caterpillar. After a bit, the caterpillar froze in its tracks! I rebooted again and it did the same thing. I ran the update again and now it is stuck at the second screen.

The S/N on this tablet indicates it was built in July (YFG0713XXXXXX). If that is a problem, you might want to make a note of this in your instructions.

My wife's identical tablet has the same build month, although it is quite a bit newer in terms of serial number. Here is the build info for her tablet:

Kernel version: 3.0.8-g1a280e6
Build number: JR003C.v009

Any ideas besides a trip to Walmart?

The root package doesn't do anything but install su, set permissions and create a symlink to it. It shouldn't do much damage, even if the flash install went bad.


Fixing permissions would probably fix it, but the stock recovery doesn't offer this feature.

I would try wiping the cache first. If that doesn't fix it, I would flash the ROM then the root package again. If all else fails, Wal Mart has a 15 day return policy on electronics.

FYI, the build number in my ROM is the same, but the kernel version is 3.0.8-g4b66125.

ShaunMT

[eegorr]

The root package doesn't do anything but install su, set permissions and create a symlink to it. It shouldn't do much damage, even if the flash install went bad.


Fixing permissions would probably fix it, but the stock recovery doesn't offer this feature.

I would try wiping the cache first. If that doesn't fix it, I would flash the ROM then the root package again. If all else fails, Wal Mart has a 15 day return policy on electronics.

FYI, the build number in my ROM is the same, but the kernel version is 3.0.8-g4b66125.

ShaunMT

Yeah, I looked at the Root zip file before I installed it on my SD card so I know it doesn't do much - I don't understand it, either! Do you have to set any of the developer options before rooting? I hadn't changed any of them from stock yet.

I feel better knowing that your kernel version is the same as mine, but what about the build number? Is your ROM built from the dumps you made from your own NX0008HDHG? I guess you have installed it yourself and are running it now, right?

I can't do anything with it right now because the battery is charging. Since I couldn't find a RESET pinhole (is there one on this tablet?), I left it on (displaying the second splash screen) overnight to run the battery down, hoping that would do the same thing. It didn't help, of course!

What permissions would you fix? Can I do something through ADB if it's not booting?

I'll try wiping the cache partition first. What about the media partition?

Lastly, I'll wipe data/factory reset from the boot menu, and if that doesn't work, I'll try your ROM.

But I can't do anything for a while until the battery charges up. I'll check for your reply before I do anything and let you know how it goes.

If you think of anything else to try, please let me know.

[shaunmt]

Yeah, I looked at the Root zip file before I installed it on my SD card so I know it doesn't do much - I don't understand it, either! Do you have to set any of the developer options before rooting? I hadn't changed any of them from stock yet.

I don't think you need to change any of the developer options.

I feel better knowing that your kernel version is the same as mine, but what about the build number? Is your ROM built from the dumps you made from your own NX0008HDHG? I guess you have installed it yourself and are running it now, right?

Actually, my kernel version appears to be newer than yours and the build number was the same. Yes, the ROM is made from a dump of a working tablet and is currently running on my own NX008HD8G. I reflash it all the time to test things I've been working on.

I can't do anything with it right now because the battery is charging. Since I couldn't find a RESET pinhole (is there one on this tablet?), I left it on (displaying the second splash screen) overnight to run the battery down, hoping that would do the same thing. It didn't help, of course!

Mine doesn't appear to have a pin hole reset button either.

What permissions would you fix? Can I do something through ADB if it's not booting?

Nothing in particular. You could try adb shell fix_permissions . If it works, it will run a script that will reset all of the file permissions back to stock.

I'll try wiping the cache partition first. What about the media partition?

Wiping the media partition couldn't hurt.

Lastly, I'll wipe data/factory reset from the boot menu, and if that doesn't work, I'll try your ROM.

But I can't do anything for a while until the battery charges up. I'll check for your reply before I do anything and let you know how it goes.

That sounds like a good plan.

If you think of anything else to try, please let me know.

Will do.

[eegorr]

I don't think you need to change any of the developer options...

Okay, I waited long enough. Wiped all of the partitions and factory reset and no go.

So I just finished flashing your ROM. IT WORKED! I am back up and running.

I'm about to try to root it again since there appears to be nothing to lose.

One thing I thought of that might have caused an issue: does the bootloader support FAT32? I used a brand new, freshly formatted (FAT32) 8GB uSDHC card when I attempted root - just didn't think anything of it at the time since the tablet supports uSDHC cards. Could that be the problem?

To flash your ROM I used a brand new FAT formatted 2GB uSD card, and that worked fine. I'm going to do the root from the same card and I'll report back.

Note: the only confusion in the instructions for your ROM is that you refer to an "update.zip" file - it isn't necessary to change the name of the zip (SMT_Next8HD8G_Stock_Rom-signed) to "update.zip" (nor did you instruct anyone to do so) as long as the correct update is selected when updating.

Thanks for getting me going again.

[eegorr]

SUCCESS!!!

Rooted and verified with Terminal Emulator. I installed SuperSU instead of Superuser just because it has been updated a lot more recently. Which one do you use?

Any comment on FAT vs FAT32 at the bootloader level? Is this something I should have known?

BTW, I one casualty so fer - I can no longer load Google Keyboard because the latest version is "not compatible" with my tablet. There were several apps I was able to run on the NEXT8P12 that Google Play won't allow me to install. I was able to install some of them via apk files I downloaded.

Any progress on coming up with a fix for this?