NEXT7D12F

[900supersport]

I think astro is a file manager. Let's see if we can get esfileexplorer onto your tab. If I upload a copy to my gdrive will you be able to get it onto the tab and then install?

[jwjensen]

I think astro is a file manager. Let's see if we can get esfileexplorer onto your tab. If I upload a copy to my gdrive will you be able to get it onto the tab and then install?

One way to find out. I can look for it on the web somewhere, too. It's not on the SlideMe market.

EDIT: nvm.. I found it on slideme.

EDIT2: Ok, downloaded and installed ES File Explorer.

[900supersport]

open esfileexplorer and press settings at the bottom. Now scroll through until you find root settings, open this and check the four options.

I've also sent you a PM

[jwjensen]

open esfileexplorer and press settings at the bottom. Now scroll through until you find root settings, open this and check the four options.

I've also sent you a PM

Done, and responded.

[900supersport]

Ok sounds as though we have root if you could select all 4 options. I'll upload a second ROM kit in an hour or so.

[900supersport]

here's the second ROM kit, hopefully this is close to complete.

ROM=> Next7D12F_ICS Beta2 ROM (345 Meg)

https://docs.google.com/open?id=0B7_2GD_rqEZsS1B2OGQ0ZlBCQms

Please do not overwrite the earlier ROM kit as we may need that yet, download and unzip to a different loctation.

Instructions

• Put the tab into flash mode and connect to the PC
• Start the flash tool, it should recognise the TAB
• Erase IDB
• Flash
• The tab should boot into touch based recovery mode, it may take a minute or two
• select reboot
• The tab should now boot. On first boot the NAND may not be formatted properly, if so simple press the notification and select format.

In the event of any problems please describe as fully as possible (did the tab boot to recovery, did the boot animation display etc).

Possible solutions

Issue, tab does not enter recovery or recovery does not work.

• go to the 900supersportROM folder
• rename recovery.img recovery.img.900ss
• rename recovery.img.orig recovery img
• do a full flash as above

Issue recovery went ok but tab will not boot

• rename boot.img boot.img.900ss
• rename boot.img.orig boot.img
• do a full flash as above

If this fails revert back to the earlier ROM kit and let me know how you got on.

[jwjensen]

Beta2 ROM

Followed instructions with the below results:

• Flash successful.
• Tab booted into recovery.
• Selected reboot.
  • Splash screen 1 (Same as stock: an Abraham Lincoln quote about reading; this screen also displayed on Beta1 ROM before Splashscreen2.)
  • Splash screen 2 (Same as stock: the word 'Nextbook' with a lady enjoying her headphones on a sunny day; this screen also displayed on Beta1 ROM after Splashscreen1 and before cool animated freaktab supersport splashscreen); this is also the same screen that hung on the "blank" system.img I tried before from post 61.)
    • During this reboot process, the PC noted that it could not recognize the device, then recognized, then could not recognize, then stopped. (All notification dialogues on the PC).
    • No other screens other than the stock screens mentioned above were displayed, i.e. no fancy freaktab supersport splashscreens.
    
    
  
  
• Waited about 5 minutes.
  • Read post 81 again.
  
  
• Followed "Recovery went ok, but tab will not boot" solution.
• Flash successful
• Tab booted into recovery.
• Selected reboot.
  • Went to Splash screen 1.
  • Went to Splash screen 2.
  • PC did not recognize tab. (Notification dialogue)
  • Tab hung.
  
  
• Read post 81 again.
• Flashed to earlier ROM kit featured in post 68 with success.

What's next?

[900supersport]

Re: NEXT7D12F

With the latest ROM kit rename system.IMG system.img.900ss
Copy the working system.img from the old ROM kit into the new ROM kit and do a full flash. Tell me it this works.

[jwjensen]

With the latest ROM kit rename system.IMG system.img.900ss
Copy the working system.img from the old ROM kit into the new ROM kit and do a full flash. Tell me it this works.

Shall I undo this first?:

• rename boot.img boot.img.900ss
• rename boot.img.orig boot.img

[900supersport]

Re: NEXT7D12F

Yes, may as well I was going to do that next but worst case if we have an issue we can rename again and reflash.

[jwjensen]

Ok,

Flashed with the system.img from Beta1, and everything else from original Beta2.

Went to recovery, chose reboot system, splashscreens same as before, hung on Splash2. PC tried to install drivers, but failed.

[900supersport]

Re: NEXT7D12F

Swap the boot.img and try again

[jwjensen]

Swap the boot.img and try again

Results:

• Splashscreen1
• Recovery, chose reboot system.
• Splashscreen1.
• Splashscreen2.
  • PC tried to install driver.
  • PC failed.
  
  
• Tab hung on Splashcreen2.

[900supersport]

Re: NEXT7D12F

Can you swap the two recovery images from the second ROM kit and reflash.

[jwjensen]

Can you swap the two recovery images from the second ROM kit and reflash.

Done.

Using:

• system.img from Beta1
• boot.img (orig)
• recovery.img (orig)

Results:

• Splashscreen1
• No recovery, instead had a quick android load about formatting or something (sorry went by too fast)
• Splashscreen1.
• Splashscreen2.
  • PC tried to install driver.
  • PC failed.
  
  
• Tab hung on Splashcreen2.