Database Info

The officially unofficial Tiamat Moray ROM Q&A Thread

This thread is an attempt to help out the Tiamat Developers by answering the frequently asked questions in one consolidated thread. This thread should also be helpful to those who either cannot use the search feature or are having a hard time figuring out the correct search terms to find what they are looking for. If you have suggestions or added questions/answers feel free to reply and I will update the OP.
NOTE: I am not a developer. All of the information in this thread is from other members who have helped me out or information I found in the XDA forums. I do not take credit for any of the great work that has been done on this ROM and I will point back to the original answer when possible. I am only trying to help lessen the burden on the developers so they can spend more time getting us the best features. Hopefully you find this helpful as well.
I've flashed this ROM and now I get update notifications. Should I accept the update? How do I stop these notifications?
No, you should never accept an OTA upgrade when using any custom ROM/Kernel. This could result in severe problems. Your best bet is to be patient and give the developers time to react. If the update is worthwhile I am sure they will roll it out pretty quickly.
To get rid of the notifications flash Mod pack 3 as noted here.
OK I made the mistake of accepting the OTA update and now my Xoom won't boot. What can I do?
okantomi said:
Can you make it reboot by pressing volume up and power at the same time and holding? If it reboots, wait about 3 seconds once you see the dual core logo and then tap volume down you shoud see android recovery, then tap up to choose it. I hope you did a nandroid backup. If not, you can try and get fastboot by tapping volume down sooner after it reboots.
Click to expand...
Click to collapse
From this thread.
With this ROM certain websites don't load correctly or I can't get to the mobile version of a site.
This ROM by default sets the User Agent String to "desktop". If you want to revert to the stock settings flash either Mod pack 1 or 2 depending which version of Moray you are running. Look here.
I flashed this ROM and now when I click links in email or my file explorer the screen just dims and nothing happens.
This is a bug in Android 3.2 and not specific to this ROM. To solve this, simply ensure auto-rotate is enabled and rotate the device from landscape to portrait and back to landscape. The app chooser window should appear allowing you to choose which app to open the selected file.
I just flashed this ROM and the speed is amazing, so I OC'd it to 1.7GHz cuz I want more and I am now stuck in a boot loop. This worked for others why not me?
The Xoom was only specified to run at 1.0 GHz, anything beyond that is a gift. Due to part-to-part variation not everyone's Xoom will be stable at the same speed. Yes some people are able to run at 1.7 GHz, but many cannot. For your specific Xoom try out the various speeds, but do NOT click "Set on Boot". This way if it crashes it will revert back to stock speed and you will be able to boot. Once you are satisfied with a speed then feel free to enable "Set on Boot". Before you do so I would suggest making a nandroid backup so you can restore just in case.
How do you get out of this boot-loop? The only way I know of is to boot into recovery and restore a nandroid backup if you have one or perform a full wipe if you do not.
I updated to the latest CWM and I cannot find the zip card or I get "get error: E:failed to mount /sdcard (No such file or directory)."
Latest is not always the best, for the Xoom you need to either use ClockworkMod 3.2.0.0 (R4C) or CMW Rogue Recovery v1.1.1
After flashing this ROM the Motorola icon gets distorted during boot up, is that a problem?
Basically it is not a problem. This kernel has a patch provided by NVidia which causes the distortion during boot. It does not cause any problems after it boots.
Is there a way to get the stock WiFi and Battery icons?
Yes
How do I boot into recovery without ADB or my PC attached?
There are a couple methods.
1) The latest Tiamat ROM includes this if you press and hold the power button. Just pick what you want and hit OK.
2) Download and install "Quick Boot" from the market. It gives you the above options as well as others when you run the app.
3) Turn the Xoom on, wait ~2 seconds after your see the Dual Core logo, then press the volume down key. In the upper left corner it should say "Android Recovery", then press the volume up key to select it.
How do I get started? Any good guides?
There are several guides that are pretty good. The best one I have found and personally used is here.
The Xoom Heaven thread found here is also a good place to start for all sorts of information.
If you have another question please feel free to post to this thread. If you are having a problem or have a question it is likely that someone else along the lines will have the same problem or question. I will continue to update this OP with the list of F.A.Q.s.

Additional Q&As
After installing this ROM I am having issues with the market not finding all of my apps or apps are giving errors when trying to install them.
See this post for one possible solution.

One more for good measure...

HuckFinn, I think you have covered most of the hot issues. Great job!

Stickied. Thanks for posting this, and Solarnz for giving me the heads up to do so.

Sorry for the newb question, but what's "root"?

Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
oh kitty, you funny!

Psychokitty said:
Sorry for the newb question, but what's "root"?
Click to expand...
Click to collapse
It's what you pull your hair out by when something is not working properly!!

darn you... I earned 1/2 my posts responding to the "why does my screen dim" question... now I'll have nothing to say!

i performed a factory reset from the os-> settings and once again performed a wipe/factory reset from the cwm recovery but still can't get back to the initial setup screen (where you enter your google a/c, etc)
any idea?
Thanks!!

Here is one..
Why does Market show up in USD even though my locale is set to UK, my language is English British along with my keyboard layout?

Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?

madamimadam said:
Ive had boot loops twice. Both times i could get into recovery but could not get backup to restore . kept getting cant read /sdcard. also cant reinstall update .zip becuase the sd card wont mount. I have only gotten back in by letting it sit powered off for a bit.
any ideas?
should i adb a stock image and start again?
should i flash a different recovery?
Click to expand...
Click to collapse
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.

okantomi said:
What version of recovery is installed now? If you have the version that doesn't recognize your external sdcard you should certainly flash a compatible recovery version through fastboot.
Click to expand...
Click to collapse
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you

madamimadam said:
Is there a way to check version without booting into recovery? Which version would you suggest?
And thank you
Click to expand...
Click to collapse
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads

LPHS said:
There are only two recoveries compatible..
you will find them in the Xoom Android Developmet Board in the sticky threads
Click to expand...
Click to collapse
OR here:http://forum.xda-developers.com/showthread.php?t=1209341

Links to both of these recoveries are also in the first post of this thread.

HuckFinn said:
Links to both of these recoveries are also in the first post of this thread.
Click to expand...
Click to collapse
Guess I should have read the thread before posting here, sorry for being a troll.

I tried this ROM on my 4G Xoom, but it left me without 4G or 3G (wifi only). Any way to get this working, or do I have to wait for an update?
I did try activating the network in settings, but it never connected even half an hour.

Thanks to steps mentioned by user 'LordDeath' in another thread and a bit of experimenting with a rooted 4G Xoom and a friends 3G Xoom running Moray, there seems to be a remedy for those who are having issues with the market compatibility issues as well as missing apps. I did not activate until attempting to sign in to the market and had missing apps and compatibility issues. I simply did a full wipe & reset and made sure the full activation went through in set up then let it automatically start restoring. I took a peek in the market after a a minute and all my apps were back with no compatibility issues. Here is a copy of his original post and mine but the last step was not needed for me.
Originally Posted by LordDeath
Something more about the market:
After I restored my backup of the official 3.1 ROM I still had some issues. On http://market.android.com I still saw that my Xoom is not compatible with some apps. The market app on the device did show these apps but upon installing I got the error message: "Fehler beim Verarbeiten des Kaufs". Translated into English it means "Error while processing the purchase". It was a free app, btw.
To solve this issue I did the following:
1. Wipe data/factory reset
2. Active the device during the wizard on the first boot with my Google account
3. Restore the nandroid backup of the official 3.1 ROM
Therefore it seems that the market servers check your device-compatibility only during the activation process at the first startup.
----------------------------------------------------------------------------
"This fixed everything for my friend running Moray and even corrected the issues on my 4G Xoom..."
I should add that though this fixes the issue, if you change your pixel density you may run into similar issues but can correct it by setting it back to 160 before going into the market.

[DEV & CWM Recovery for Pantech Crossover]

Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it

And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA

Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?

crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.

Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?

Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus

Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.

stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.

Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.

Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.

Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse

Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk

Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.

stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk

Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2

anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware

Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?

formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.

formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2

Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA

[Q] My Asus TF300T is on stock Android 4.0.3, what to do next?

The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!

What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app

This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...

Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD

Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.

It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app

Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596

pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?

Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89

Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.

opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.

Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:

pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...

Easy guide to twrp and 2nd bootloader

Hello all!
Do you want TWRP, a 2nd bootloader, and custom roms at your fingertips for your Kindle Fire HD? Well you have come to the right place! Over the past months, through trial and error, I've managed a full-proof, easy method to unlock the Kindle Fire HD's true potential. While this is aimed at 7" devices, it should work no problem on the 8.9 either - however you will have to use your head. These instructions are geared towards the 7", and you will have to realize what changes to this blueprint you personally will need to make with the 8.9.
!WARNING! WHILE THIS HAS WORKED FOR ME ON MULTIPLE DEVICES, YOU MUST FOLLOW THE DIRECTIONS CAREFULLY. I PERSONALLY SUGGEST YOU FIRST BUY A SkOrPn FACTORY CABLE IN CASE ANYTHING GOES WRONG. (Although using this guide, it almost certainly will not. Still, those cables come in handy!! :good: ​
Also, I would like to point everyone to seokhun's thread on this matter, which came before my own: http://forum.xda-developers.com/showthread.php?t=2271909
BIG thanks to LinearEquation for helping maintain this thread. Trust any advice he gives; it WILL help! :thumbup:
Although our posts on this process are essentially similar, he goes far more in depth on the process, and has an excellent troubleshooting section if something here goes wrong for you and I cannot respond to your question soon enough (although if done right, that won't happen )
Ok. Lets begin!
Step One: Download Kindle Fire First Aide, an amazing tool which is only getting better: http://forum.xda-developers.com/showthread.php?t=2096888
This is probably the most work-intensive step, although once you have it you'll be glad you do. You are to follow the directions on this thread and install the necessary files, and adb drivers. This is necessary for your KFHD7 to communicate with your computer properly. When finished, make sure your Kindle has ADB enabled under its device settings.
lets see if you're ready for step 2. Plug your kindle in and check your device manager. If your kindle fire shows up as "android adb interface" then you sir/ madam are ready. If not, please use the Kindle Fire First Aide (hereafter referred to as KFFA) thread to find out where you went wrong. The answer you seek will be there, I promise you.
Step Two: BACK UP ANY FILES/FOLDERS/MOVIES/ETC YOU WANT TO KEEP. STEP THREE WILL WIPE YOUR DEVICE!
Step Three: Here, we are going to use KFFA to reset our device to 7.2.3. Make sure you have transferred any backups you have made to your computer. Run KFFA and select the option that reads "Reboot the Kindle into Fastboot Mode". At the time of this posting, there are two options to do this. Try the preferred option first, and if that doesn't work, try the alternative method. Alternatively, just plug your kindle in with a fastboot/factory cable to get it into fastboot. YOUR DEVICE MUST BE IN FASTBOOT MODE FOR THE NEXT STEP
Step Four: while in fastboot mode, in KFFA, use the option "COMPLETELY RESTORE THE KFHD7 7.2.3. This will take a while, and you will be prompted at certain points to continue. I usually chose not to wipe user data at the end, as for me at least it takes forever and shouldn't be necessary.
Step Five: While still in KFFA, Disable Amazon's OTA updates with the option provided. This is important - If an update sneaks by, you will have to start from scratch!
Once KFFA says it's finished, unplug your device and hold the power button to hard-reset it. Now boot it back on. Your kindle will now be stock 7.2.3, with google play and superuser installed, along with root permissions.
Step Six: Here we go! Download the provided FireFlash11.apk, kfhd7-Freedom-boot-7.3.0.img, and kfhd7-twrp 2.4.4.0-recovery.img to your computer. Connect your KFHD7, make sure you check "allow installations of unknown applications" on your kindle's options (they will have reset thanks to KFFA, don't forget), and go to either the amazon or google play marketplace and find a file browser you can use to navigate to your download folder. Find where you placed the FireFlash11.apk, open it, and install.
Step Seven: Almost there guys! Open up your new FireFlash app. The first thing you (should) notice is that there is a warning that you have the incorrect bootloader at this moment. Check the box that says "Flash kfhd7-u-boot-prod-7.2.3.bin. scroll to the bottom of the app, where it says "execute", and press "flash, install script". Exit the program and reboot your device.
Step Eight: Now that your kindle has rebooted, open up the FireFlash app again. This time, you should see no warnings at the bootloader. If for some reason you do, STOP and retrace your steps. If you see no warnings, we're ready to install the 2nd bootloader and TWRP!! While still in FireFlash, under "boot partition" it should say "not flashed". Click on the "not flashed", and navigate to the "kfhd7-Freedom-boot-7.3.0.img" that we downloaded earlier. Check the box next to "apply stack override".
Now, under "recovery partition", again select the "not flashed" box and navigate this time to the "kfhd7-twrp 2.4.4.0-recovery.img". Once in place, check the "disable recovery auto update" box to the right. Now scroll to the bottom, to where it says "execute", and tap "Flash, install script" just like we did before with the bootloader.
Thats it! Select "reboot into recovery" from the Fireflash app if you're still in it, and if you followed the instructions and put everything where it belongs, you should wind up in TWRP after your kindle reboot (dont worry if you see the blue kindle fire logo for a minute before it enters TWRP - it's completely normal. From here you can install custom roms, wipe your cache, and most importantly MAKE BACKUPS! :laugh:
ATM I am using Hashcode's CM10.1 with the 1.5 ghz kernal, with Nova Launcher Prime and LMT launcher. It's simply amazing the difference in both speed and functionality. Hopefully, this guide got you there and now you too can enjoy a fully unlocked Amazon Kindle Fire HD!
Here is a link to the page for Hashcode's CM10.1, If you want to give it a shot I highly recommend it!! http://forum.xda-developers.com/showthread.php?t=2245335
One last note. I want to make it clear that I have not personally developed any of these tools, I've just organized them for you. The real ones you want to be thanking if this works are the developers. Thanks Devs!! :good:
​

Can u make video on youtube doing this plz thanks
Sent from my Nexus 7 using Tapatalk 2

Unfortunately, I lack the recording equipment or I would do so and link it. however, I promise if you follow the instructions closely, there should be no issues. And if for some reason you run into trouble, just post the problem and I'll do my best to walk you it. I realize there are other guides out there, but in my opinion this is currently the easiest one to get you through it. Good luck friend
Sent from my cm10.1 KFJD

+1

I will finally be doing a video this weekend if no one beats me to it got Saturday off thx open system to for the written tut as I do not have a lot of free time
Sent from my Kindle Fire HD 7

How is this different from my tutorial? I see you included KFFA, but other than that, same method, and you lack the troubleshooting portion as well as only promoting Hashcode's CM10.1.

seokhun said:
How is this different from my tutorial? I see you included KFFA, but other than that, same method, and you lack the troubleshooting portion as well as only promoting Hashcode's CM10.1.
Click to expand...
Click to collapse
I wrote this tutorial as a newer method of achieving TWRP/2nd bootloader, as every OTA update amazon pushes out makes different root methods temporarily break/ ineffective, while this method SHOULD always remain consistent with the help of KFFA doing the rooting. However upon going back and looking over your thread again, I now realize there are quite a few similarities. I strived to simplify mine as much as possible, which is why I avoided the troubleshooting section and left explanations of the process to a minimum. As your guide is more in depth, I will edit my original post to include a link to yours as well should people want additional information/help. Please, don't look at this guide as an attempt to derail yours - rather as an attempt to simplify it even more. I apologize for not mentioning your thread in my original, that was an unfortunate oversight, and thank you for bringing it to my attention :good:

techdeisel said:
I will finally be doing a video this weekend if no one beats me to it got Saturday off thx open system to for the written tut as I do not have a lot of free time
Sent from my Kindle Fire HD 7
Click to expand...
Click to collapse
You're welcome! Good luck on the video, if you complete it and follow these steps to do so, feel free to post a link on here and I will include it in the main thread to help people who need the visual aid to really drive the idea home

Opensystem
Brilliant!!
Had a look at your guide and thought why not...checked with Chris of KFFA about rooting KFHD 7 with 7.4.3 update, he gave me the 'fakebackup' file. Rooted with KFFA....followed EXACTLY from your step 6 to 8 and ATM doing a TWRP backup.
Fantastic job mate.
One question though. If I am going to put another ROM to KFHD7, do I need to do a full wipe (cache, factory, delvik) everytime before a flash install?
regards
fs1023

fs1023 said:
Opensystem
Brilliant!!
Had a look at your guide and thought why not...checked with Chris of KFFA about rooting KFHD 7 with 7.4.3 update, he gave me the 'fakebackup' file. Rooted with KFFA....followed EXACTLY from your step 6 to 8 and ATM doing a TWRP backup.
Fantastic job mate.
One question though. If I am going to put another ROM to KFHD7, do I need to do a full wipe (cache, factory, delvik) everytime before a flash install?
regards
fs1023
Click to expand...
Click to collapse
Check the bottom of my thread in my signature for instructions on installing a new ROM.

fs1023 said:
Opensystem
Brilliant!!
Had a look at your guide and thought why not...checked with Chris of KFFA about rooting KFHD 7 with 7.4.3 update, he gave me the 'fakebackup' file. Rooted with KFFA....followed EXACTLY from your step 6 to 8 and ATM doing a TWRP backup.
Fantastic job mate.
One question though. If I am going to put another ROM to KFHD7, do I need to do a full wipe (cache, factory, delvik) everytime before a flash install?
regards
fs1023
Click to expand...
Click to collapse
I'm delighted to hear that my guide helped you! And sorry for not getting back to you sooner. Seokhun seems to have managed to point you in the right direction, but in case anyone else needs an answer (or of course, you still do ) you only need to fully wipe when going from one type of Rom to another (ie: from stock Amazon to cyanogenmod). This is known as a "clean flash". Otherwise, if say you are simply upgrading cyanogenmod or whatever Rom you're on to a new update, all you really need to do is a "dirty flash" - wipe delvik/cache and you're good to go!
More info on this can be found here http://forum.xda-developers.com/showthread.php?t=1882629
Cheers!
Sent from my Android Kindle Fire HD 7 Running Cyanogenmod 10.1

seokhun said:
Check the bottom of my thread in my signature for instructions on installing a new ROM.
Click to expand...
Click to collapse
And thank you seokhun, for taking such an active role in improving my thread
Sent from my Android Kindle Fire HD 7 Running Cyanogenmod 10.1

techdeisel said:
I will finally be doing a video this weekend if no one beats me to it got Saturday off thx open system to for the written tut as I do not have a lot of free time
Sent from my Kindle Fire HD 7
Click to expand...
Click to collapse
Did u make it dude
Sent from my SGH-T989 using Tapatalk 2

Just wanted to say thanks. I followed steps 6-8 on my wife's new Kindle and all is well and running smooth.

huskyjayboy said:
Just wanted to say thanks. I followed steps 6-8 on my wife's new Kindle and all is well and running smooth.
Click to expand...
Click to collapse
awesome glad to hear it!

Hashcode Stock OS Zips for 7" HD do not block OTA updates
Opensystem said:
awesome glad to hear it!
Click to expand...
Click to collapse
I thought I would post here my experience with the latest 7.4.6 Amazon update.
I placed the update on my HD7" and was able to update.
When I booted, 2nd Bootloader/LOG was gone.
I decided to try this again.
I rooted the tablet and used Fireflash to re-load 2ndbootloader using the 7.4.3 series of Hashcode files.
Once I was not able to boot up into the 7.4.6 OS because the 7.4.3 boot image is used for 2nd bootloader as I expected.
I had downloaded, the 7.4.3.zip stock OS to the sdcard originally so, it was still present locally.
I flashed the OS zip and I was back to 7.4.3.
I downloaded 7.4.6 again to the tablet and again was presented with the Bright update Kindle in "More+/Device/About".
After, the update, I was again without 2nd boot and unrooted.
Point though is the update should not occur if the zip OS was in fact blocking OTA updates.
Is the zip file supposed to have OTA blocked?
I used KFFA to block updates as a second test and once disabled with KFFA, the update is Grayed out and then once re-enabled with KFFA, the update is bright and does update.
I know a lot of people have complained about OTA happening even when blocked...
It looks like this Zip is not blocking.
I will try the LINUX rootplus to see if it blocks OTA...
Regards

galearned said:
I thought I would post here my experience with the latest 7.4.6 Amazon update.
I placed the update on my HD7" and was able to update.
When I booted, 2nd Bootloader/LOG was gone.
I decided to try this again.
I rooted the tablet and used Fireflash to re-load 2ndbootloader using the 7.4.3 series of Hashcode files.
Once I was not able to boot up into the 7.4.6 OS because the 7.4.3 boot image is used for 2nd bootloader as I expected.
I had downloaded, the 7.4.3.zip stock OS to the sdcard originally so, it was still present locally.
I flashed the OS zip and I was back to 7.4.3.
I downloaded 7.4.6 again to the tablet and again was presented with the Bright update Kindle in "More+/Device/About".
After, the update, I was again without 2nd boot and unrooted.
Point though is the update should not occur if the zip OS was in fact blocking OTA updates.
Is the zip file supposed to have OTA blocked?
I used KFFA to block updates as a second test and once disabled with KFFA, the update is Grayed out and then once re-enabled with KFFA, the update is bright and does update.
I know a lot of people have complained about OTA happening even when blocked...
It looks like this Zip is not blocking.
I will try the LINUX rootplus to see if it blocks OTA...
Regards
Click to expand...
Click to collapse
Well if you said that KFFA works, then why not keep that?
Sent from my Kindle Fire HD 7 using xda app-developers app

Hashcode Stock OS Zips for 7" HD do not block OTA updates
r3pwn said:
Well if you said that KFFA works, then why not keep that?
Sent from my Kindle Fire HD 7 using xda app-developers app
Click to expand...
Click to collapse
Yes: Of course, you would keep what works and in this case, KFFA works.
However a ton of people have used various other methods over the last year or two and KFFA is pretty new.
Lots of people have written in saying "why did I get an update when I am blocked?"
I was just offering a reason why.
You can find lots of pre-rooted ROMs on the forum that all say "Rooted, No ADs, and OTA blocked, Gapps, etc.".
The user takes that descriptor on faith and flashes the ROM thinking they have what they need.
In my case, I purposefully updated to 7.4.6 and needed a way to get back to an older version of Kindle OS.
I restored back to 7.3.0 then flashed Hashcode's, 7.4.3 ZIP OS.
It was there I realized I could then update to 7.4.6 which I should not have been able to do.
Just a point of information.
Another point or question is whether there is a difference between a true OTA update that takes place automatically and the case where the user downloads the update to the tablet and then selects "Update" in Device/about. I have always thought it might be nice to have an option where the OTA is blocked but, the user could still download and update manually. When the KFFA method is used to block OTA, both options are blocked.
Regards

galearned said:
Yes: Of course, you would keep what works and in this case, KFFA works.
However a ton of people have used various other methods over the last year or two and KFFA is pretty new.
Lots of people have written in saying "why did I get an update when I am blocked?"
I was just offering a reason why.
You can find lots of pre-rooted ROMs on the forum that all say "Rooted, No ADs, and OTA blocked, Gapps, etc.".
The user takes that descriptor on faith and flashes the ROM thinking they have what they need.
In my case, I purposefully updated to 7.4.6 and needed a way to get back to an older version of Kindle OS.
I restored back to 7.3.0 then flashed Hashcode's, 7.4.3 ZIP OS.
It was there I realized I could then update to 7.4.6 which I should not have been able to do.
Just a point of information.
Another point or question is whether there is a difference between a true OTA update that takes place automatically and the case where the user downloads the update to the tablet and then selects "Update" in Device/about. I have always thought it might be nice to have an option where the OTA is blocked but, the user could still download and update manually. When the KFFA method is used to block OTA, both options are blocked.
Regards
Click to expand...
Click to collapse
If you're trying to get a custom Rom, this thread is for you. If you wanted the newest Amazon update with working root, wrong thread
From the first step to the last, my guide can get you twrp and root and a set up for a new rom. No more, no less
Sent from my Android Kindle Fire HD 7 Running Cyanogenmod 10.1

galearned said:
I restored back to 7.3.0 then flashed Hashcode's, 7.4.3 ZIP OS.
It was there I realized I could then update to 7.4.6 which I should not have been able to do.
Click to expand...
Click to collapse
I don't think Hashcode removed the OTA Scripts. He may have, but I'm not sure.
Sent from my Amazon Kindle Fire HD using xda app-developers app

Nobis NB07 and DA-741QHD rooting and ROM thread

Tech Specs:
Processor Type: Quad-Core Cortex A9 Processor(When I turn on the tablet it says Allwinner A31?)
Processor Speed: 1.20 GHz
System Ram: 1 GB
Hard Drive Size: 8GB
Laptop Screen Size: 7 inch
Screen Type: Capacitive Touch Display
Battery Life: 4 hours
Battery Type: 2800mAh Lithium Ion
Network Connection: 802.11b/g/n Wireless LAN
Connector Type: 1 x HDMI, 1 x Headphone, 1 x MiniUSB 2.0
Operating System: Google Android
Accessories Included: AC Adapter,USB Cable
Operating System Version: Android 4.2 Jelly Bean
This thread is a continuation of some of the discussion that was from this thread: http://forum.xda-developers.com/showthread.php?t=2568427
While not at all high end tablets, it's always fun to see what can be squeezed out of them! As stated in the title, this thread will be regarding the following devices: Nobis NB07, Iview 774TPC, and DA-741QHD (which all appear to be the same hardware) rooting and ROMs. That should be pretty simple for now since, we currently have no ROMs and no proven root method. Some have reported success using the Kingoapp. If anyone is able to obtain root, we would like to ask that you make a copy of the firmware and upload it for those of us having trouble doing so. After doing so, we can modify it and hopefully get more our of the software.
You may also post information regarding tweaking the ROMs for these devices and other ways to make them more useful!

Warning: The following may have unforseen effects including breaking your tablet to the point of being unrepairable.
Option #1, Use KingoApp Some users have reported that this did not work for them, at least one user reported that it did.
Instructions per RawX:
For the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers. That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times. I've done this were for clients of mine but its pretty straight forward.
Click to expand...
Click to collapse
The working drivers for me were: VID_1f3a_PID_efe8
Please consider trying this first and give us some feedback. A word of warning though, there has been some discussion on XDA in the past that this may be malware though I'm not sure this was ever confirmed.
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Credits: As above to RawX
Congrats... You're rooted.

Mods
Currently, I've managed to get great battery life out of my tablet by installing kernel tuner and changing the settings as such:
Governor: Ondemand (default is fantasys)
Max: 1200 MHz (Default is 1200 MHz)
Min: 240 MHz (Default is 120 MHz, but I had trouble with usability at this setting and Ondemand)
I also recommend setting wifi to turn off when the screen is off and turn off autosync.
This seemed to give me a very useable system but with greatly improved battery life. Doing the above and a few other tweaks here and there have made my battery life so that it drains by about 1% overnight when not in use. I also seem to get better battery life while using the tablet. I haven't had any trouble playing games either.

neatojones said:
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Congrats... You're rooted.
Click to expand...
Click to collapse
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?

Hippie459MN said:
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?
Click to expand...
Click to collapse
Nope, still haven't gotten the camera working. We are missing some config files still. Do you need the camera drivers or the tablet drivers?
The camera drivers are : sp2518 and sp0838, though I also see a module being loaded called cam_detect
I don't recall where I got the adb usb drivers for the tablet, but it would probably be a good thing to mention in this thread so if you have them, let me know and I can add it to one of the top posts. If you're having trouble finding them, I'll remove my drivers and go back through the process to find them again.

Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.

Hippie459MN said:
Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.
Click to expand...
Click to collapse
OK. The drivers I used were probably: VID_1f3a_PID_efe8 (or something similar)
You can either google that or try downloading the firmware for TP718AQ here: http://www.agptek.com/forum/viewtopic.php?f=22&t=948
Remove all prior drivers for the tablet. Plug it in and tell Windows to use the drivers from the extracted file you download (Will extract to TP718AQ_Update_Firmware\USB Driver).
Sometimes I have to do a little dance with restarting the device and my computer to get it to recognize it.
As a last resort you could try this: http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/
Let me know if you have any problems.
Good Luck!

Ok, I officially give up trying to root this thing. Stupid windows will not install the drivers in both the links you provided and I cant get windows to even try to install anything after removing them then I got the android ADB drivers to install but still zero luck. All rooting apps fail. Hopefully someone will post the image of their rooted NB07. A few claim to have rooted it just fine but I cant win with this thing.
All I want is to be able to run link2sd and a few other apps that require root. This is officially the longest I have owned an un-rooted android device. lol

I'm the one that got the root working using kingo, so for the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers ( I would post a link but I don't have 10 posts yet on XDA)
That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times I've done this were for clients of mine but its pretty straight forward.

Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:

Hippie459MN said:
Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:
Click to expand...
Click to collapse
Thanks to the work of someone on another forum, I have now got TWRP working on our device and am hoping we will soon have a CM working on it as well. Check back in the near future for further details. Maybe if you can't have a rooted stock, we can get a fully functional CM.

I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.

Hippie459MN said:
I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.
Click to expand...
Click to collapse
On another site for now. Just PM's at the moment so not much to follow yet. But, all you'll need is the Phoenixsuit to install it, so you won't have to root your tab first. You'll have root on the new ROM. You'll have to have drivers fully working though. Once fully working I'll link to the site so people can get the files and hopefully we can get this guy some donations for his work.

Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.

Hippie459MN said:
Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.
Click to expand...
Click to collapse
Not sure about the camera yet. I have CM booting but no touch yet, so this will be the first task. I'll keep everyone posted.

Any word on getting things to work yet?

Currently, we have CM working with no touch screen/camera. I'm not sure what else all isn't working because I'm waiting on my OTG cable to come in for further testing to see what all is going to be required to get the touchscreen going. Right now, it appears we my be looking at compiling our own drivers which could take some time to do. I think we'll get it eventually, but it may take some time. If you don't need touchscreen or camera, it could be working right now.

Sorry for no updates for a while. My work has been delayed on this since I have a son who is sick and in the pediatric ICU. I'll get back to work when things calm down for me.

No worries man. Family first.

Just a question, Hippie...
On the original ROM, can you see your device in ADB? If you can, and type "adb shell" do you get root? If you have adb access but not root, can you try typing sh and see what happens?
Also, could you try loading the rootfromOTA.zip and see if you can get a printout of the error log if possible?
Also, I tried installing this from the recovery on a similar ROM and it acted like it failed. I went back into the ROM and used adb and was able to get root using vroot or kingo...I don't remember which. This may be worth a shot.
Interestingly, I have been looking for alternative ways to root and found this (but we need to find a way to get to the bootloader):http://whiteboard.ping.se/Android/Rooting
I think that the method to get to bootloader is to turn off the tablet, then hold down the back button while tapping the power button 5 times. But, I also googled and found a method for getting to fastboot from adb in android without root as well which may work.