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

[eegorr]

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

Okay, I'll give it a shot a little later today.

Meanwhile, if you see this post before I get to it, tell me what I need to do to dump the files you need to create ROM package.

[shaunmt]

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.


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


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


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. If there is a typo, it was there when the script was run! Where is it, anyway?


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?

The stock su can't be executed or updated by SuperSu because the permissions aren't set high enough.

I was mistaken... in fact I mixed things up a bit in some of my previous posts... I mistakenly advised more than once that my root package sets su to 0644 (which would not even work). I was thinking of my ROM package which sets system apks to 0644 (correctly). Su is set to 06755 (0= root owner, 6=group, 7 =read/write/execute for owner, 5=read/execute for group, 5=read/execute for everyone else.

There is no typo in your root script. It uses the same permissions for su as mine. (06755)

If you change the .zip file, you'll need to resign it again with google test keys to use it with the modified 3e recovery.

Alternatively, you could use Cydia Impactor to root instead.

ShaunMT

[shaunmt]

Okay, I'll give it a shot a little later today.

Meanwhile, if you see this post before I get to it, tell me what I need to do to dump the files you need to create ROM package.

The easiest way to get the system partition is to use Onandroid (Online Nandroid Backup) from the play store to create a backup. It grabs some of the other partitions as well, but not all of them.

The only way to get all of the others is to dd them. (You can't just DD system too because it is ubifs.)

Here is how use dd to dump partitions:

Do

          
cat proc/mtd

You should get output something like this:

          
dev:     size     erasesize     name 
mtd0: 00800000 00200000 "bootloader" 
mtd1: 00800000 00200000 "logo" 
mtd2: 00800000 00200000 "aml_logo" 
mtd3: 00800000 00200000 "recovery" 
mtd4: 00800000 00200000 "boot" 
mtd5: 20000000 00200000 "system" 
mtd6: 00800000 00200000 "cache" 
mtd7: 40000000 00200000 "userdata" 
mtd8: 18c00000 00200000 "NFTL_Part"

You need bootloader, logo, aml_logo, recovery, boot, and system for a full ROM.

Cache is user settings. Userdata is downloaded apps. System, cache and userdata can't be backed up properly using dd. Use Onandroid (Online Nandroid Backup) from the play store.

Don't mess with NFTL_Part!

Output file names should be as follows:

"bootloader" = bootloader.img
"logo" = logo.img
"aml_logo" = aml_logo.img
"recovery" = recovery.img
"boot" = boot.img

So your command lines for dumping should be in this format:

dd if=/dev/mtd/mtd# of=/sdcard/external_sdcard/ouputfilename

Check your mtd#'s on your device using cat proc/mtd and fill in the mtd#'s and output file #'s and enter the dd commands one line at a time.

If your cat proc/mtd output matches my device, then your lines would be:

dd if=/dev/mtd/mtd0 of=/sdcard/external_sdcard/bootloader.img 
dd if=/dev/mtd/mtd1 of=/sdcard/external_sdcard/logo.img 
dd if=/dev/mtd/mtd2 of=/sdcard/external_sdcard/aml_logo.img 
dd if=/dev/mtd/mtd3 of=/sdcard/external_sdcard/recovery.img 
dd if=/dev/mtd/mtd4 of=/sdcard/external_sdcard/boot.img

When done, copy the files and folders you dumped off your external sd card, zip them all up together in a single zip file, upload them and let me know where I can download them.

ShaunMT

[stevemp]

In what way would you consider it rooted?

Unfortunately, that's not all it does!

The stock rom has a su binary in the xbin directory. If you type adb shell then su then you have the # symbol for root. I pushed a new su to xbin and installed SuperSu from the market and it worked. I really haven't noticed any problems with the kyser_root_signed.zip, probably have flashed my tablet a dozen times at least. The only issue I have is with the wi-fi, no MAC address after flashing a rom (hw failing or software related )

[eegorr]

The easiest way to get the system partition is to use Onandroid (Online Nandroid Backup) from the play store to create a backup. It grabs some of the other partitions as well, but not all of them.

Installed, but what settings do I use for the backup? (backup type, backup mode)

The only way to get all of the others is to dd them. (You can't just DD system too because it is ubifs.)

Here is how use dd to dump partitions:

Do

          
cat proc/mtd

You should get output something like this:

          
dev:     size     erasesize     name 
mtd0: 00800000 00200000 "bootloader" 
mtd1: 00800000 00200000 "logo" 
mtd2: 00800000 00200000 "aml_logo" 
mtd3: 00800000 00200000 "recovery" 
mtd4: 00800000 00200000 "boot" 
mtd5: 20000000 00200000 "system" 
mtd6: 00800000 00200000 "cache" 
mtd7: 40000000 00200000 "userdata" 
mtd8: 18c00000 00200000 "NFTL_Part"

This one is almost identical, except for the sizes of the blocks:

dev:     size     erasesize     name 
mtd0: 01000000 00400000 "bootloader" 
mtd1: 00800000 00400000 "logo" 
mtd2: 00800000 00400000 "aml_logo" 
mtd3: 00800000 00400000 "recovery" 
mtd4: 00800000 00400000 "boot" 
mtd5: 20000000 00400000 "system" 
mtd6: 10000000 00400000 "cache" 
mtd7: 40000000 00400000 "userdata" 
mtd8: 18a800000 00400000 "NFTL_Part"

You need bootloader, logo, aml_logo, recovery, boot, and system for a full ROM.

Cache is user settings. Userdata is downloaded apps. System, cache and userdata can't be backed up properly using dd. Use Onandroid (Online Nandroid Backup) from the play store.

Don't mess with NFTL_Part!

Output file names should be as follows:

"bootloader" = bootloader.img
"logo" = logo.img
"aml_logo" = aml_logo.img
"recovery" = recovery.img
"boot" = boot.img

So your command lines for dumping should be in this format:

dd if=/dev/mtd/mtd# of=/sdcard/external_sdcard/ouputfilename

Check your mtd#'s on your device using cat proc/mtd and fill in the mtd#'s and output file #'s and enter the dd commands one line at a time.

If your cat proc/mtd output matches my device, then your lines would be:

dd if=/dev/mtd/mtd0 of=/sdcard/external_sdcard/bootloader.img 
dd if=/dev/mtd/mtd1 of=/sdcard/external_sdcard/logo.img 
dd if=/dev/mtd/mtd2 of=/sdcard/external_sdcard/aml_logo.img 
dd if=/dev/mtd/mtd3 of=/sdcard/external_sdcard/recovery.img 
dd if=/dev/mtd/mtd4 of=/sdcard/external_sdcard/boot.img

When done, copy the files and folders you dumped off your external sd card, zip them all up together in a single zip file, upload them and let me know where I can download them.

ShaunMT

I've got these five files dumped (with dd), now I'll try system.img via the app.

Edit: Okay, I tried a selective backup and selected only system, but nothing was created. The log file gets to the point where it is checking for required tools, then logs the following error:

Error: mkyaffs2image not found in path! Exiting...

What now?

Edit: I just found this:

http://forum.xda-developers.com/showpost.php?p=26122715&postcount=75

Was the file "mkyaffs2image" missing on your tablet, Shaun?

Edit: His fix aborts after it attempts to verify the update package. I'm going to try to copy the file manually via terminal.

Edit: No good, not even with ES Explorer. I can't copy this file to either /system/bin or /system/xbin - "permission denied".

[pimpmaster55307]

update

I got my tablet to see the files in the recovery mode, turns out I had a bad SD card I went and bought a new one and it went right to it. But now when it goes to install after verifying update package it says installation aborted. Any reason it would say this for?

[shaunmt]

I got my tablet to see the files in the recovery mode, turns out I had a bad SD card I went and bought a new one and it went right to it. But now when it goes to install after verifying update package it says installation aborted. Any reason it would say this for?

If it failed signature validation, you're in the stock internal recovery instead of the modified recovery on your SD card.

It it didn't say signature validation failed, then your files are corrupted and you need to download them again.

ShaunMT

[pimpmaster55307]

If it failed signature validation, you're in the stock internal recovery instead of the modified recovery on your SD card.

It it didn't say signature validation failed, then your files are corrupted and you need to download them again.

ShaunMT

Yeah it just says instaallation aborted and nothing else after that. I'm redownloading them again now.

[pimpmaster55307]

If it failed signature validation, you're in the stock internal recovery instead of the modified recovery on your SD card.

It it didn't say signature validation failed, then your files are corrupted and you need to download them again.

ShaunMT

Thanks for all your help. My tablet is up and going again.

[shaunmt]

Thanks for all your help. My tablet is up and going again.

Glad to hear it!

[eegorr]

Glad to hear it!

Shaun, please see my post above: http://www.freaktab.com/showthread.p...l=1#post107793

I have all of the image files you asked for except the system image dumped, zipped up, and ready to upload.

Since my last edit, I saw your post to someone else and downloaded the file again, this time directly to the uSD card. Using your recovery with Ameer's fixtool.zip file, I still get the following:

-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.

Is this a problem with the zip file or is it related to the Google test keys you used with your recovery.

Edit: I just found the instructions for onandroid (in first post of previously mentioned xda-developers thread). Running onandroid v9.10 from the Terminal command line (after executing su) I get the following error: "BusyBox version less than 1.20 found.z", then "Exiting...".

Apparently, the version of BusyBox that comes pre-installed on this tablet is v1.16 (2012-03-08).

Edit: I used JRummy Busybox installer to update Busybox to v1.20.2. Now I get past the Busybox error, but I am getting the mkyaffs2image error again!

FINAL EDIT: I found OBackup on Google Play, but, of course, my device is not compatible. So I sideloaded the latest apk (v1.35) and IT WORKED!!!!

Shaun, check your PM for a link to two zip files on my Google Drive.

[shaunmt]

Installed, but what settings do I use for the backup? (backup type, backup mode)


This one is almost identical, except for the sizes of the blocks:

dev:     size     erasesize     name 
mtd0: 01000000 00400000 "bootloader" 
mtd1: 00800000 00400000 "logo" 
mtd2: 00800000 00400000 "aml_logo" 
mtd3: 00800000 00400000 "recovery" 
mtd4: 00800000 00400000 "boot" 
mtd5: 20000000 00400000 "system" 
mtd6: 10000000 00400000 "cache" 
mtd7: 40000000 00400000 "userdata" 
mtd8: 18a800000 00400000 "NFTL_Part"

I've got these five files dumped (with dd), now I'll try system.img via the app.

Edit: Okay, I tried a selective backup and selected only system, but nothing was created. The log file gets to the point where it is checking for required tools, then logs the following error:

Error: mkyaffs2image not found in path! Exiting...

What now?

Edit: I just found this:

http://forum.xda-developers.com/showpost.php?p=26122715&postcount=75

Was the file "mkyaffs2image" missing on your tablet, Shaun?

Edit: His fix aborts after it attempts to verify the update package. I'm going to try to copy the file manually via terminal.

Edit: No good, not even with ES Explorer. I can't copy this file to either /system/bin or /system/xbin - "permission denied".

I think you figured out how to use Onandroid... the system partition should backup as a .tar file...

I don't think mkyaffs2image is necessary...

ShaunMT

[shaunmt]

Shaun, please see my post above: http://www.freaktab.com/showthread.p...l=1#post107793

I have all of the image files you asked for except the system image dumped, zipped up, and ready to upload.

Since my last edit, I saw your post to someone else and downloaded the file again, this time directly to the uSD card. Using your recovery with Ameer's fixtool.zip file, I still get the following:

-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.

Is this a problem with the zip file or is it related to the Google test keys you used with your recovery.

Edit: I just found the instructions for onandroid (in first post of previously mentioned xda-developers thread). Running onandroid v9.10 from the Terminal command line (after executing su) I get the following error: "BusyBox version less than 1.20 found.z", then "Exiting...".

Apparently, the version of BusyBox that comes pre-installed on this tablet is v1.16 (2012-03-08).

Edit: I used JRummy Busybox installer to update Busybox to v1.20.2. Now I get past the Busybox error, but I am getting the mkyaffs2image error again!

FINAL EDIT: I found OBackup on Google Play, but, of course, my device is not compatible. So I sideloaded the latest apk (v1.35) and IT WORKED!!!!

Shaun, check your PM for a link to two zip files on my Google Drive.

I'm not sure what Ameer's fixtool.zip is, but it probably uses busybox in it's installer-script and our modified recovery does not contain a full busybox install.

It sounds like you got everything figured out though. I'll have to recheck the name of the app I use and edit my instructions...

ShaunMT

[eegorr]

I think you figured out how to use Onandroid... the system partition should backup as a .tar file...

I don't think mkyaffs2image is necessary...

ShaunMT

Maybe not, but Onandroid would not run without it, neither from app level nor from the command line. Orange Backup uses the Onandroid script and it worked fine.

[thebiggboss180]

I think you figured out how to use Onandroid... the system partition should backup as a .tar file...

I don't think mkyaffs2image is necessary...

ShaunMT

onandroid app needed to install the mkyaffs2image for me and let the app use it s own busybox

Thanks for clearing that up! It's been awhile since I installed it...

ShaunMT