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

[eegorr]

I rooted it with ADB commands and it worked great, then I messed with a file setting dealing with the WIFI and it just hangs at the finger with the circle moving around. The date is 0413

Where did you find the root procedure? Do you have a link to the web page?

[eegorr]

This is exactly what happened to me, Shaun. Clearly, it is not an issue with the uSD card. Please remove the /system/app permissions change from your root script as it is not necessary and can only cause trouble!

I'm not going to attempt to root another tablet until I can verify this change has been made.

I just picked up another tablet from the same Walmart where I got the first two. They had some June built tablets but after looking through the boxes we found one with a manufacturing date in July. It actually has a lower serial number than either of the other two July built tablets I already have.

I'm not going to take any chances with this one. Please create a new script that does the following, and only the following:

1) copy su to /system/bin (not xbin, and no symbolic link)
2) set permissions on /system/bin/su the same as this (from my NEXT8P12):

-rwsr-sr-x root radio 85096 2013-01-03 23:10 su

THAT'S IT!

You don't have to make it public, just send me a link to it via PM and I'll try it on the new tablet right out of the box. If it works, I'll dump the files you need to create a ROM from it, assuming you can tell me what files you need and how to do it!

Thanks...

First edit:

HOLD THE PRESSES...

I got curious and looked around a bit on my wife's tablet which is July built with a firmware build date of June 21, 2013. It has not been rooted by any method.

Using terminal, the first thing I did was try to run su from the prompt. I got an error message: "not allowed to su".

That made me curious. I first looked in /system/bin, then I found su in /system/xbin:
-rwsr-sr-x root root 62872 2008-08-01 05:00 su

If this is a legit version of su, all we need to do is change the permissions on it so that it can be executed by any user.

Second edit:

You may remember that I used the init-pppd.sh exploit to root my NEXT8P12 tablets. Here is what was added to that script, which ran when I connected a cellular modem to the USB port:

mount -o rw,remount /system
cp /sdcard/su /system/bin/
cp /sdcard/Superuser.apk /system/app/
chmod 06755 /system/bin/su
chown root:root /system/bin/su

[stevemp]

HOLD THE PRESSES:

I got curious and looked around a bit on my wife's tablet which is July built with a firmware build date of June 21, 2013. It has not been rooted by any method.

Using terminal, the first thing I did was try to run su from the prompt. I got an error message: "not allowed to su".

That made me curious. I first looked in /system/bin, then I found su in /system/xbin:
-rwsr-sr-x root root 62872 2008-08-01 05:00 su

If this is a legit version of su, all we need to do is change the permissions on it so that it can be executed by any user.

You need superuser or SuperSu installed to give permissions to apps. The N0008HD8G comes rooted, all the kyser_root_signed does is replace the su with one that works with the superuser app. I used adb to rename the original su and pushed the new one to get the correst su installed. System app permissions should be 644 not 0755, 0644 but works either way. I have used Shaun's script to make a couple of custom roms that work fine. I always wipe data/factory reset, cache partition, and media, never had a bootloop. I use a 16 GB fat 32 sd-card, only issue is the mbr gets corrupted and has to be formatted. Other issue lately is the missing MAC address but that could be hw related. If it had a better speaker and screen it would be a really good tablet.

[randomkidsrule]

The 4/12/13 build that I posted today will probably fix that issue.

ShaunMT

OK, thanks! Will download!

[shaunmt]

You need superuser or SuperSu installed to give permissions to apps. The N0008HD8G comes rooted, all the kyser_root_signed does is replace the su with one that works with the superuser app. I used adb to rename the original su and pushed the new one to get the correst su installed. System app permissions should be 644 not 0755, 0644 but works either way. I have used Shaun's script to make a couple of custom roms that work fine. I always wipe data/factory reset, cache partition, and media, never had a bootloop. I use a 16 GB fat 32 sd-card, only issue is the mbr gets corrupted and has to be formatted. Other issue lately is the missing MAC address but that could be hw related. If it had a better speaker and screen it would be a really good tablet.

Actually no, you don't need Superuser or SuperSu to use su... The purpose of Superuser or SuperSu is to notify the user that an App wants su and provide an option to block it... otherwise all apps get unlimited access to su, assuming the permissions for su are set high enough to allow access...

directories in /system are set to 0755

all other files in /system are set to 0644

user and group id's are both set to 0 for everthing in /system

[shaunmt]

So after days and days of trying to get my tablet unbricked and trying to get it to read from the sd in bootloader I'm still not sucessful. Does anyone know how to load the rom from ADB or fastboot?

Check the ainol forums on slatedroid... they have some guides about recovering from various brick conditions...

Also, have you tried removing the SD card, booting to the stock internal recovery and wiping everything? I've had to do this with my tablet a few times recently... I'm starting fear I may have a bad block or two in my NAND...

[shaunmt]

This is exactly what happened to me, Shaun. Clearly, it is not an issue with the uSD card. Please remove the /system/app permissions change from your root script as it is not necessary and can only cause trouble!

I'm not going to attempt to root another tablet until I can verify this change has been made.

See his other posts... he was messing with parts of his system in ADB when he messed up his tablet.

I removed the /system/app permissions line from the install script for the kyser_root.zip package. It was originally to set permissions for Superuser.apk, but was no longer needed after I chose to remove Superuser.apk from the package.

All links for kyser_root.zip currently point to the new package.

ShaunMT

[shaunmt]

I just picked up another tablet from the same Walmart where I got the first two. They had some June built tablets but after looking through the boxes we found one with a manufacturing date in July. It actually has a lower serial number than either of the other two July built tablets I already have.

Glad you found one!

I'm not going to take any chances with this one. Please create a new script that does the following, and only the following:

1) copy su to /system/bin (not xbin, and no symbolic link)

This is not the standard way to install su on Android.

2) set permissions on /system/bin/su the same as this (from my NEXT8P12):

-rwsr-sr-x root radio 85096 2013-01-03 23:10 su

THAT'S IT!

You don't have to make it public, just send me a link to it via PM and I'll try it on the new tablet right out of the box. If it works, I'll dump the files you need to create a ROM from it, assuming you can tell me what files you need and how to do it!

Thanks...

The permissions set by my installer for the su binary are 0644, which is sufficient for full Root.

First edit:

HOLD THE PRESSES...

I got curious and looked around a bit on my wife's tablet which is July built with a firmware build date of June 21, 2013. It has not been rooted by any method.

Using terminal, the first thing I did was try to run su from the prompt. I got an error message: "not allowed to su".

That made me curious. I first looked in /system/bin, then I found su in /system/xbin:
-rwsr-sr-x root root 62872 2008-08-01 05:00 su

If this is a legit version of su, all we need to do is change the permissions on it so that it can be executed by any user.

I didn't realize the stock ROM included su at all... still keeping in it my root package for anyone who doesn't have it preinstalled. Superuser or Supersu will overwrite it with a newer version anyway. My root package is designed in way that should work on ANY Android device capable of flashing a package signed with Google test keys.

Second edit:

You may remember that I used the init-pppd.sh exploit to root my NEXT8P12 tablets. Here is what was added to that script, which ran when I connected a cellular modem to the USB port:

mount -o rw,remount /system
cp /sdcard/su /system/bin/
cp /sdcard/Superuser.apk /system/app/
chmod 06755 /system/bin/su
chown root:root /system/bin/su

Functional, although not the common way of installing it. Also, I think you may have a typo there in the permissions.

Feel free to take my files and modify them any way you like.

ShaunMT

[stevemp]

Actually no, you don't need Superuser or SuperSu to use su... The purpose of Superuser or SuperSu is to notify the user that an App wants su and provide an option to block it... otherwise all apps get unlimited access to su, assuming the permissions for su are set high enough to allow access...

directories in /system are set to 0755

all other files in /system are set to 0644

user and group id's are both set to 0 for everthing in /system

Thanks for the info about superuser, never tried using su without it. I have been setting permissions for apks in system/app to 644 for years, started compiling 7.2 for the Next3 and porting it to different rk2818 tablets. Also compiled cm-9, cm-10, cm-10.1, Paranoid Android, and AOKP for the Archos G9, not a newbie.

[shaunmt]

Thanks for the info about superuser, never tried using su without it. I have been setting permissions for apks in system/app to 644 for years, started compiling 7.2 for the Next3 and porting it to different rk2818 tablets. Also compiled cm-9, cm-10, cm-10.1, Paranoid Android, and AOKP for the Archos G9, not a newbie.

No problem... I didn't realize this until, I started installing su without superuser or supersu. I usually test it by typing su in terminal before installing SuperSu.apk.

Your permissions are correct, I was just confirming that I'm using the same and trying to clear up any confusion.

Now, if I could just get my current CWM build to boot instead of hanging and reverting to stock...

ShaunMT

[pimpmaster55307]

Check the ainol forums on slatedroid... they have some guides about recovering from various brick conditions...

Also, have you tried removing the SD card, booting to the stock internal recovery and wiping everything? I've had to do this with my tablet a few times recently... I'm starting fear I may have a bad block or two in my NAND...

Yeah I've tried that a few times and no luck sadly, I'll take a look around the other fourm you mentioned. Otherwish I may just use this tablet for target pratice. LOL

[pimpmaster55307]

How can I tell if my tablet it booting into the recovery that I put on my sd card. I suspect that I'm not and that might be the whole issue I"m having

[shaunmt]

How can I tell if my tablet it booting into the recovery that I put on my sd card. I suspect that I'm not and that might be the whole issue I"m having

It looks exactly the same as the stock internal recovery. If you try to flash one of my ROMs or my kyser_root.zip and get an error about failed signature verification, you're in stock recovery. If it passes signature verification, you're in the modified recovery on the SD card.

ShaunMT

[eegorr]

This is not the standard way to install su on Android.

LOL! Maybe not, but that's all we could come up with. I thought you were there almost a year ago when we were struggling to get those tablets rooted. They were locked up tight - Finless Bob finally gave up! I guess he didn't know about Google test keys. But someone else found that vulerability in init_pppd.sh and, after buying a modem and OTG cable, I used it to achieve root.

The permissions set by my installer for the su binary are 0644, which is sufficient for full Root.

Maybe so, but it's not necessary and it is just another opportunity for something to go wrong!

I didn't realize the stock ROM included su at all... still keeping in it my root package for anyone who doesn't have it preinstalled. Superuser or Supersu will overwrite it with a newer version anyway.

I didn't, either, but it is not executable from the Android Terminal app. And SuperSU was not able to update it, either.

Functional, although not the common way of installing it. Also, I think you may have a typo there in the permissions.

As I said, it was not our first choice. That text is copied and pasted from the modified init_pppd.sh script that allowed me to achieve root. Finless Bob told us what to put in there. If there is a typo, it was there when the script was originally run! Where is it, anyway?

Feel free to take my files and modify them any way you like.

I would, but I don't have the setup to do it and just changing the zip file would cause it to fail validation, right?

[eegorr]

The N0008HD8G comes rooted...

In what way would you consider it rooted?

all the kyser_root_signed does is replace the su with one that works with the superuser app.

Unfortunately, that's not all it does!