Develop Bugs

Guide to upgrading Universal with MaUpgradeUt_noID.exe

How to update your rom to the latest I-mate version (with push email) and Radio 1.09.0 using the MaUpgradeUt_noID.exe method
1 – download the file “Universal_Upgrade_v1.30.68_radio_1.09.0.zip” from the ftp site (see bottom of post for details)
2 - double click the file and allow it to unpack into a folder
3 – right click on the active sync icon in your tasks tray on you pc (at the stage you should NOT have you universal plugged in)
4 – select connection setting then untick “allow USB connections”
5 – Now take your Universal and take out the SIM and MEMORY CARD
6 – Press light + power + reset with the phone on, this will place the universal into bootloader mode
7 – Connect your Universal via the USB cable to your computer directly i.e. not though a USB hub
8 – Now double click on the program called “MaUpgradeUt_noID.exe” (found in to folder from step 1) this will start the upgrade process, the first stage takes about 3 to 5 minutes to complete, you will then be presented with a screen showing a “Imate Jam” and some information about what you are upgrading to, don’t be worried if this screen does not show you the version numbers you have at present that is normal.
9 – Now continue with the process by clicking upgrade/next
10 – After sometime (about 20 minutes) you should be at the end screen tell you to unplug and reset you “jam” So now unplug your universal and reset it and that’s all there is to it!
Note that during the upgrade process you can follow the progress by also looking at your universal screen with a light source as the backlight will be off.
I hope this post helps someone as looking around the forum Im amazed by the amount of people asking “how do I upgrade my rom” or “I only get a “country id error” when trying to update”
The “Universal_Upgrade_v1.30.68_radio_1.09.0.zip” file can be found here
ftp://xda:[email protected]/Uploads/Universal/Universal_Upgrade_v1.30.68_radio_1.09.0.zip
This file contains the latest imate beta rom v1.30.68 and the latest radio 1.09.0 plus all the tools you need
Oh and if anyone thinks Ive missed something out please post and let me know!

File as been moved its now at :-
ftp://xda:[email protected]/Universal_Upgrade_v1.30.68_radio_1.09.0.zip
This file contains everything need to upgrade your universal

Thanks rat - very cool of you to post up a guide. How Nb is it to remove your SIM?

wamatt said:
Thanks rat - very cool of you to post up a guide. How Nb is it to remove your SIM?
Click to expand...
Click to collapse
No sure I understand the question however Ive updated before now with the sim card in however lots of people report that its important to remove both the memory & sim cards so Ive included it because its better to be safe than sorry

Thanks I'll play it sorry :/..

BTW do you have to use this NOID method if you have an IMATE too?

wamatt said:
BTW do you have to use this NOID method if you have an IMATE too?
Click to expand...
Click to collapse
No you should be ok using the orginal package, however this way will still work

I installed the ROM but after the installation is finished and I reset the device I only get a blank screen.

Piesang said:
I installed the ROM but after the installation is finished and I reset the device I only get a blank screen.
Click to expand...
Click to collapse
Blank screen but do you have the USB or SERIAL written on the Screen?
Rat didn't mention in his post but it comes out in the last screen that it is supposed to be a HARD RESET which will bring about a menu where you have to press 0 (Zero) to ahrd reset the device. hope this helps

Yip, sorry, That's correct. I get the screen that says I have to press 0 to reset or X to exit.
If I press 0 the screen goes blank and stays like that.
I've installed the previous ROM now and it is working perfectly. It's just the new ROM on this page doesn't want to work on my Jasjar.

Piesang said:
Yip, sorry, That's correct. I get the screen that says I have to press 0 to reset or X to exit.
If I press 0 the screen goes blank and stays like that.
I've installed the previous ROM now and it is working perfectly. It's just the new ROM on this page doesn't want to work on my Jasjar.
Click to expand...
Click to collapse
I downloaded it straight from the first post and it installed flawlessly...
Have you tried installing it from bootloader mode instead of direct update? And without SD card in the PDA? This might work.
BTW, I have returned to the older ROM.... advantages don't outweigh the disadvantages.
My phone keeps on hanging (for the 1st time ever after 5 months use and different ROMs) on the screen where it shows whose calling. I havent answered the call yet but it stops ringing. When i open the PDA it has ANSWER on the left softkey and pressing this doesn't do anything. Will wait for the release..
It is a lot faster thought (the test ROM)

Thanks for the info. I'm not gonna bother upgrading now. I'll wait for a decent ROM later.
Thanks m8

umm - stupid question I know.....
But what does this actually DO??
I understand that this will upgrade the radio stack and thus produce better reception etc - but what else will it do??
If I have an Orange M5000 will I still be able to use it on Orange's network?? Do i need to fill in any settings? Do I need to make notes of certain stuff beforehand? If so - what settings?
I assume this will totally rewrite the registry and what programs are on teh device - or will it??
I suppose a lot of this information is available on the forum - but tracking it down can take a lot of time for someone who's not necessarily that 'au fait' with the working of the device.

Riceburner said:
umm - stupid question I know.....
But what does this actually DO??
I understand that this will upgrade the radio stack and thus produce better reception etc - but what else will it do??
If I have an Orange M5000 will I still be able to use it on Orange's network?? Do i need to fill in any settings? Do I need to make notes of certain stuff beforehand? If so - what settings?
I assume this will totally rewrite the registry and what programs are on teh device - or will it??
I suppose a lot of this information is available on the forum - but tracking it down can take a lot of time for someone who's not necessarily that 'au fait' with the working of the device.
Click to expand...
Click to collapse
I also have an orange M5000 which I would like to get off Orange to use my Vodafone SIM - would installing this new ROM be the way to go ?

not if your phone is simlocked (or network locked). new rom is only the software.

Yeah, sorry
Just reading the other thread on this - sorry , am a relative newby.
It looks like MachineGod and Buzz are on the case though - and with their track record........

I wanted to confirm that Ratcom's file he linked to is good (not corrupt) and his method for upgrade works. Nice work, Ratcom.

ratcom said:
File as been moved its now at :-
ftp://xda:[email protected]/Universal_Upgrade_v1.30.68_radio_1.09.0.zip
This file contains everything need to upgrade your universal
Click to expand...
Click to collapse
Hi ,
Can let me know the speed of the Os did u face any problems after upgrade.
E.g Apps, Hanging , Memmory leaks. Etc. Cheers

I had no problems what so ever with this rom, the speed of the os was breathtaking.

ratcom said:
I had no problems what so ever with this rom, the speed of the os was breathtaking.
Click to expand...
Click to collapse
Does this rom work on dopod 900?
Is this is final release?
Cheers,

sound?

hi there
i just managed to install android onto a HTC "Kaiser" TyTn2.
everything i need seems to work fine except sound and wifi.
i installed RLS15 from http://forum.xda-developers.com/showthread.php?t=759894
using KaiserCustomRUU.exe
now there seems to be no sound. i called a number, and i hear nothing at all. i tried pressing speaker, and same no sound. vibrates working though. i also tried pulling the vibrate tab but it didnt work. still no sound.
about wifi, i have a Ad-Hoc network from my computer (which i can connect to from my ipod touch 3g - iOS4), but even after turning Wifi on in settings, it just doesnt seem to see my network....
btw i got no "welcome to android" or set up or anything... i did hold the DPad
any help?

I'm not sure but try out another Radio http://forum.xda-developers.com/showthread.php?p=9807696#post9807696 <---- Here
Flash it with HARDSPL or just using CustomRUU when in the tri-color screen.
I could be wrong but that's what I'm guessing
Wi-Fi... Wich kernel did you use?
Try out http://forum.xda-developers.com/showthread.php?p=9807696#post9807696 Post 118
And use the Androidupdate I attached, It's the one from Liquid wich should fix the Wi-Fi
Let us know if it fixed it
(God i had to edit it a million times before i did it right )

calls do definately go out. i called someone, i coudnt hear anything, and they called me back.

What do you mean by "Welcome To Android" ?

i read in some website that the first screen when booting android for the first time is Welcome to Android

Gaura Mohana said:
i read in some website that the first screen when booting android for the first time is Welcome to Android
Click to expand...
Click to collapse
In some builds, when you boot Android, it gives this kind of tutorial on how to use your phone (Wich has as title "Welcome to full android on Kaiser" for example), time and date settings and connect to Google account, It's possible that it isn't in the one you use
Don't worry about it, the welcome to android doesn't show when u press D-pad, the D-pad is to get into the menu when ur kernel is booting (the one with black background and white letters)
The menu is to install your system, make backups, clear dalvik and others

ok... but what do i do now about the sound? (and the wifi if posibble)

Gaura Mohana said:
ok... but what do i do now about the sound? (and the wifi if posibble)
Click to expand...
Click to collapse
Sound=New Radio
Wi-Fi is probably androidupdate
[SOUND]
Go to http://forum.xda-developers.com/showthread.php?t=393182
Scroll down until you see this: KAISER Radios These Radios were ripped from Kaiser WM6.1 ROMs.
Pick a radio and download it.
HARDSPL IS NEEDED FOR THE RADIO!
Extract the file and change the name from the NBH file to KAISIMG.NBH if the name is something else.
Copy KAISIMG.NBH onto the root of your sdcard and plug your sd card into the phone.
Hold down the camera button and turn the device on or reset it.
When you see a tri-colored screen, release the camera button.
When you see a blue text with something like RADIO (i guess) press the power button (just 1 little press, no long pressing)
The device will now update your RADIO, when finished just reset it.
Now reinstall your Android version by holding down the D-center button when asked, then selecting Install System and make it clear data.
[Wi-Fi]
Copy the androidupdate.tgz into your Andboot folder
Reboot the phone and press D-center button when asked
Choose the option to install update
Wait for it to finish and just press quit to boot Android

OMG DUDE!! thank you so much

Gaura Mohana said:
OMG DUDE!! thank you so much
Click to expand...
Click to collapse
no problem
hope it works

i just managed to put the KAIS_RADIO_ONLY_1.71.09.01.nbh (which i renamed to KAISIMG.NBH) and i put it on the root after a couple of hours figuring out how to make the phone show up in explorer
i tried starting exactly as you told me, but it boots directly to android - no tricolor. it worked fine before i installed android. so what do i do now?

Gaura Mohana said:
i just managed to put the KAIS_RADIO_ONLY_1.71.09.01.nbh (which i renamed to KAISIMG.NBH) and i put it on the root after a couple of hours figuring out how to make the phone show up in explorer
i tried starting exactly as you told me, but it boots directly to android - no tricolor. it worked fine before i installed android. so what do i do now?
Click to expand...
Click to collapse
I don't think there's another way, just, turn phone off, hold camera button in while pressing the power button once
Release the camera button after you see the colored screen
http://www.youtube.com/watch?v=bVMeZyuIMls
Doesn't show much more than I already said
Did you put hardspl on it anyways?

Thanks... What i managed to do was to simply get into the tricolors by holding power+home, then i connected to computer, and SPL'ed from CustomRUU. it worked, and sound is working. i tried your way but it woudnt detect my .NBH. thanks anyways
but where can i get a androidupdate.tar for the wifi for?
btw quick point, but my camera seems to work!!!! i remember reading that the camera WONT work on android. (it didnt work before installing the latest radio)

Thanks for the file. i just tried installing the liquid update from this post, and all i get is error under wifi (before wifi would turn on - but it kept on searching and found nothing). i did install a old update before this. could that have messed it up?
i also have a problem with USB mounting. I click turn on USB storage, and it works randomly. it works 1 time - doesnt work 10... replkuggin and stuff doesnt work. as in "Android Phone" is showing in Eject, but nothing is showing in explorer
EDIT
-----------------------
I just re-installed android and now installed the liquid update.
NOW wifi turns on, but it just scans (has been scanning for 5 minutes)
my ipod touch sees the network immediately.

Gaura Mohana said:
Thanks for the file. i just tried installing the liquid update from this post, and all i get is error under wifi (before wifi would turn on - but it kept on searching and found nothing). i did install a old update before this. could that have messed it up?
i also have a problem with USB mounting. I click turn on USB storage, and it works randomly. it works 1 time - doesnt work 10... replkuggin and stuff doesnt work. as in "Android Phone" is showing in Eject, but nothing is showing in explorer
EDIT
-----------------------
I just re-installed android and now installed the liquid update.
NOW wifi turns on, but it just scans (has been scanning for 5 minutes)
my ipod touch sees the network immediately.
Click to expand...
Click to collapse
Hmm can you tell me wich kernel you are using? 2.6.32?
Did you use the guide on Atools to make your nbh files?
Guide: http://forum.xda-developers.com/showthread.php?t=783514
Gotta go take exam right now so I'll be looking for this afterwards.
And since it's 06:24 here in the morning, we have a bit of a time issue I think.

I actually dont know what version i have, but i got it from some post on this forum, and it was the latest, and i did use atools.
I found this post http://www.google.com/support/forum/p/android/thread?tid=3b250c94811ca5df&hl=en
I am trying to use a ad-hoc network too, and i dont have any other type of wifi to try.
thanks
good luck with the exams(s)
EDIT- i have 2.6.32.9

Gaura Mohana said:
I actually dont know what version i have, but i got it from some post on this forum, and it was the latest, and i did use atools.
I found this post http://www.google.com/support/forum/p/android/thread?tid=3b250c94811ca5df&hl=en
I am trying to use a ad-hoc network too, and i dont have any other type of wifi to try.
thanks
good luck with the exams(s)
EDIT- i have 2.6.32.9
Click to expand...
Click to collapse
It could be that it's not possible to connect to an ad-hoc network, I've got no idea about that.
Hope someone else will post here and answer that.
U should really try connecting with a normal Wi-Fi network
Go onto the street and look for appartments or houses with open networks just to test?

i live in a small town..... no one here has internet let alone wifi....

aww that's balls
got no idea on how to try it then

Storex Ezee'TAB901 root JB 4.1.1

hi,
After spending many time trying to root my storex tab 901 I bought in france (Already installed on 4.1.1 with google play), Iwas finnaly able to root it using adb and command line.
to do so:
- Download attached file
- Download from google SDK usb_adb_driver
- Go to your device parameters-> USB -> enable debbuging mode
- create a c:\root folder on your windows XP computer then Extract the zip file attached into it.
- Plugin your device to the computer, when prompted for driver, use google sdk USB_ADB_Driver
- When done, open a windows terminal command line
- type: c:
- type: cd \
- type: cd root
- type: cd rootkit
- type: go.cmd
If everything goes well, your tablet should reboot. you can try installing the free app from google store called "Root checker" to confirm your device is properly rooted.
Also, if you lost the original rom and live suite, here is the link to download the latest build from storex web site:
(I will post the link later when I find it)

JB 4.2.2
CAUTION: USE THIS ROM AS YOUR OWN RISK.......Be sure you have the official rom in case it is not working for you. It appears that even though you have the same tablet Reference, depending on when you buy it, hardware might be a bit different and most likely you will take the risk of having a unusable Touch screen or wifi...
I found out you can fully use your Ezee Tab 901 4.2.2
you can install rom from Manta MID 13.
You will be able to install the rom using Livesuite.
Gain:
- Android 4.2.2
- Root Access out of the box
- Play store installed.
Everything will be working
For the link type in google:
MID13 Android 4.2.2 Jelly Bean - Manta Multimedia Info
select google link called: manta.info.pl
select the link catshare or 4shared.
Start live suite 1.7, select the download img file, do a format when prompted. You done.
When the tablet restart, go to the parameter icon, and change language to French or english
Procedure on the Ezee tab 901 with livesuit:
- completly turn off the tablet, unplug cable
- start livesuite and select the downloaded image file
- keep the VOL- button pressed and plug the usb cable
- without releasing the VOL- button press the Power button 6 times.
- You should hear windows sound saying a USB device has been plugged
- if windows request it, install the driver from Livesuitefolder\usbdriver
- Livesuite should automatically start the flashing process.
- when prompted, "Format device" press YEs.
- When it s 100% you tablet should reboot.
Done.
Note: I did not invent anything, thanks to the good work of MANTA team members. I just found out this rom works on my tablet out of the box.

Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.

samus64 said:
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
Click to expand...
Click to collapse
Hi,
did you try going into recovery mode and factory reset? (shutdown tabel completely and keep press on volume+key then press power button)
in the menu, using vol+/- scroll down to wipe factory reset and validate by pressing the power key.
Let me know how it goes.
btw, are you sure your tablet is a Ezee tab 901 and not 971?
Cheers

Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/

samus64 said:
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
Click to expand...
Click to collapse
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers

pierrottls31 said:
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
Click to expand...
Click to collapse
Yep the wifi switch is exactly what i've got on this storex. Thanks for your help anyway. Ho and by the way, I properly rooted it with you first tuto
Cheers.

Fast custom ROM 4.2.2 by TOxico for Ezee tab 901
Guys,
I manage to find a very fast and usable rom for our tablet: (THanks to Toxico.) this rom will change your life.
All information and download are in the thread here:
http://forum.xda-developers.com/show...php?p=42274265
It should basically work on any A13 device with livesuit (tested on my Ezee tab 901 and on my 704CET mem up)
This rom comes with no TS driver, but there is all explanation and download to install the needed driver.
note: you might loose the camera though. I encourage you to read the full thread before going further and flash your tablet.
If you want to know the driver used on your tablet, run a adb shell and type lsmod (You will have a list of loaded/used driver.)
Dont be scared, everything is written in the toxico's thread
My only advice, if you dont know how to use adb, do not try it, this is not that easy.
I hope this will help.
Best regards.
As usual do it at your own risk and even more: make sure you have the original rom... just in case

Tutorial for 971.
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.

MaedaKeiji said:
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
Click to expand...
Click to collapse
Hi, sorry i cant help you, it looks like the 971 is using a10 cpu, sôit can be different.
If you know what you are doing, u can try to backup your original firmware and test the solution i have provided from toxico in py post above. But there is no warranty it s going to work.
Any case, donnot forget google is your friend
Good luck

Unfornetly it seems google doens't like this tablet...
I'll see what I can do with some backups and all.
Thanks anyway!

[NST/NSTG][ROM] Tweaked Modded ROM Final [RETIRED][Jun23-2015]

This is a tweaked versions of the official UK 1.2.1 firmware (works with all devices, not just UK ones. Go to Settings > *Development > Locale Picker: to change local to United States).
Changes Made to nook_1_2_update.zip:
Busybox and init.d support.
Forced all rendering to be done on the GPU.
Chainfire3D drivers added.
Kick Ass Kernelizer
fixalign -ZipAlign & Fix Permissions on boot.
vac - Runs SQLite VACUUM & REINDEX to optimize databases
improved rendering of images and text.
OptiPNGed and Zipped all system apks.
Plus many improvements taken from this thread and many others.
To install:
Write CWM to a 2GB SD: http://forum.xda-developers.com/showthread.php?t=1360994
Download the modified nook_1_2_update.zip - 126 MB firmware and place it onto the SD you just wrote CWM to.
Place SD into NST and boot device.
Wipe all user data/factory reset and install nook_1_2_update.zip
Take out SD and boot device.
Setup Wifi and log into your B&N account.
Format SD and place what you ]want to enable onto it:
ReLaunch+Apps - This will replace the Home with ReLaunch and includes Cleanmaster, Calculator, Clearscreen, Email, ScreenRotator & Opera Mini.
EpubBrowser+Apps - This will replace the Home with EpubBrowser and includes Cleanmaster, Calculator, Clearscreen, Email, ES File Explorer, ScreenRotator & Opera Mini.
USB-Audio+FastMode+Host - This will enable USB Sound and USB Host + FastMode. Also enables ROOT/SU
SuperUser - Enables ROOT/SU.
Click to expand...
Click to collapse
Place SD into the NST and reboot the device
While booting push and hold the lower left and the lower right buttons until you see CWM
Now Install what Home you want to use. EpubBrowser or ReLaunch and any other modules.
Thats it!
Once everything is installed leave it for about 5 minutes to let the device optimize all the apps and get everything setup (it will probably reboot).
Bugs:
The B&N Welcome screen will flicker. Tap the power button to get rid of it.
Tip: To bring up the list of apps installed in EpubBrowser, swipe a clockwise circle starting at 10 O'clock.
Once everything has settled down open the NookColor Tools app and un-tick then tick Non-Market apps so you can side load apps.
To be able to download apks from the Play Store and side load them onto the Nook, use this site: http://apps.evozi.com/apk-downloader/
Remember the Nook is running Android 2.1 Éclair (API level 7), so any apps needing a newer version of Android won't load.
You can also grab this package of apps I put together that work with the NST:
http://forum.xda-developers.com/nook-touch/themes-apps/share-setup-t3143404
Here is a video of my personal setup:
What I enabled:
nook_1_2_update.zip - This is just an optimized version of the default UK ROM with init.d+Busybox.
EpubBrowser+Apps.zip - This will replace the Home with EpubBrowser and includes Cleanmaster, Calculator, Clearscreen, Email, ES File, ScreenRotator & Opera.
USB-Audio+FastMode+Host.zip - Also enables ROOT/SU - Install this after logging into your B&N account. If you install it before you won't be able to register with B&N.
If you have under 50% battery life the USB sound dongle will cut out. So make sure you have plenty of battery life.
Thanks to :
latuk for the Kernel.
NFHimself for the EpubBrowser home screen.
antsm for Extended power menu
ИΘΘK¡€ for AndroNook Settings

Awesome to see a new ROM. Double awesome to see that it adds color to our devices

2 pinguy1982
Thank you for this perfected ROM, will try it at some point later.
A question if I may: While booting push and hold the lower left and the lower right buttons until you see CWM - this means that you have to write the CWM image to SD card again, after formatting it? And then copy those two Nooter-zip files onto SD card with CWM image? Sorry if my questions looks silly here.

All download links are now up and working.

How compatible it's with NSTG and its glow functionality?
Good work, at least complete ROM for NST:]

Tarnak said:
How compatible it's with NSTG and its glow functionality?
Good work, at least complete ROM for NST:]
Click to expand...
Click to collapse
It's fully compatible with NST and NSTG

Have installed the ROM and nooter files, but my home screen continuously refreshes. Any idea why?
Also tried the separate replacement home file on top of the rooted ROM and it still keeps refreshing.
No books are shown in the 6 rectangular boxes.
Sent from my GT-I9300 using xda app-developers app

northender said:
Have installed the ROM and nooter files, but my home screen continuously refreshes. Any idea why?
Also tried the separate replacement home file on top of the rooted ROM and it still keeps refreshing.
No books are shown in the 6 rectangular boxes.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I had the same issue with the Home. What I did to fix it was to find out what book was having issues generating a thumbnail images and changed the cover to a different one using Calibre.
You could also manually add the thumbnail images yourself. You do this by coping the image from Calibre library and renaming it the same as the title of the book.
If you just can't get it to work then replace the Home with this: Home.zip - 553.42 KB
You just flash it within CWM.

just one question bro...how u managed to bring colors to our black and white nook simple touch? how u made this magic happen?:fingers-crossed: that means we can also read colorful comic strips on it now :laugh:

I wish I could figure this out myself, but I just don't know that much about android. :crying:
So here is my question.
I already have a NST and a NSTG rooted with NookManager. Is there anyway to just install this kernel and get the optimizations to run without going through the entire process above?

Does this include USB host?

bradpitcher said:
Does this include USB host?
Click to expand...
Click to collapse
Yes.

ashish2k4.dce said:
just one question bro...how u managed to bring colors to our black and white nook simple touch? how u made this magic happen?:fingers-crossed: that means we can also read colorful comic strips on it now :laugh:
Click to expand...
Click to collapse
Come on, people, are you serious - these are the screenshots, yes they are in color, but NST CAN ONLY show them in black and white.

Hi,
I have installed this room with Nook_Replacment_Home.zip not Nooter-partx.zip because I don't need Gapps.
But I don't find a way to view all the apps on the nook.
I only have the home screen with my book.
---------- Post added at 12:26 PM ---------- Previous post was at 12:10 PM ----------
tebra said:
Hi,
I have installed this room with Nook_Replacment_Home.zip not Nooter-partx.zip because I don't need Gapps.
But I don't find a way to view all the apps on the nook.
I only have the home screen with my book.
Click to expand...
Click to collapse
Solved:
To bring up the list of apps installed, swipe a clockwise circle starting at 10 O'clock. Touch an app to launch it, left or right swipe to go back to main screen.

Fastmode and norefresh are not working on this great ROM.

tebra said:
Fastmode and norefresh are not working on this great ROM.
Click to expand...
Click to collapse
Fastmode2 does work and is included with the ROM.

pinguy1982 said:
Fastmode2 does work and is included with the ROM.
Click to expand...
Click to collapse
Maybe in full version of your rom with Nooter-Partx and Gapps.
I have the light install without Nooter-part. If I install and start fastmode2 it don't do anything on my NST. Maybey the kernel is not the same or not rooted with the light version of this rom.

tebra said:
Maybe in full version of your rom with Nooter-Partx and Gapps.
I have the light install without Nooter-part. If I install and start fastmode2 it don't do anything on my NST. Maybey the kernel is not the same or not rooted with the light version of this rom.
Click to expand...
Click to collapse
Install Nooter-Part2 to get Fastmode working. It is a different kernel that enables Fastmode,.

pinguy1982 said:
Install Nooter-Part2 to get Fastmode working. It is a different kernel that enables Fastmode,.
Click to expand...
Click to collapse
Thanks, I will try tonight.
One more question:
I want to use my NST without uSD card. But UC Browser (and other apps) only see /sdcard and sub-directory as download destination. But I want to download to /media directory.
Any idea workaround?

People having issues the EpubBrowser Launcher read this: http://forum.xda-developers.com/showpost.php?p=50617346&postcount=29

[RECOVERY] TWRP 2.8.6.0 for Shield TV (all variants)

I was going to wait for this device to be added to devdb to make a release thread, but that's being delayed, if it'll ever happen. So, I'm making this thread as a placeholder. No big fancy text, just a known problem list and the release. If you're looking for this, you probably know what to do with it. Everything should work from flashing to backup and restore from all external media. If it doesn't, please report it.
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
SOURCE:
device (branch cm-12.1-mrom)
kernel
vendor
CURRENT RELEASE:
For Android M:
twrp-20160222-UNOFFICIAL-foster.img
Known Issue: This release does not work on 4K displays. It boots to a black screen. Please use a 1080p display for TWRP until this is fixed.
For Android L:
twrp-multirom-20151112-UNOFFICIAL-foster.img
OLD RELEASES:
twrp-multirom-20150630-UNOFFICIAL-foster.img
twrp-multirom-20150624-UNOFFICIAL-foster.img
twrp-multirom-20150613-UNOFFICIAL-foster.img

MultiRom will be a must have on this device.
I really appreciate your work, and reading the various thread on xda I found out that you're one of the best developers for Nvidia Shield devices.
Without people like you we would all be locked in a large digital cage.
Compliments

Thanks Steel01!

I'm starting to slowly look at what I can disable in the kernel to shrink it down enough to fit in the recovery partition. Unfortunately, my first two ideas, network and sound, can't be unilaterally removed due to the android USB gadget (used for adb) depending on them. I've got it down to 26 MB, but iI dont know if it still boots. I'll try a few more things and hopefully have something working in the next couple days. I'm also hoping Tasssadar merges the 2.8.7.0 changes soon, the resize functionality will be useful (in testing I somehow shrunk my user data partition to 11 GB and had to reformat it get the full 4?? GB back).

Or it could be quicker than I thought. Todays test was successful. It's small enough to barely fit in the partition and appears to work correct. The link is in the OP. The next update to the multirom TWRP will probably make it too big again and I'll have to rip some more stuff out...

I want to install twrp recovery on my 16gb Shield, but i have no need for multirom. Is there an option to bypass the boot option or should I wait for a standard TWRP?
You didn't take much of a break before going back at it again. Thanks for your dedication!

Well, I'm not going back at it fully yet. Next week and a half will likely be pretty busy. I'm just doing a piece here and there.
This TWRP has multirom support, but does not require it or even set it up by default. In fact, to enable multirom, you have to install a separate zip (which I haven't released because it doesn't work). So no, you won't see any extra boot screens with this.
A standard TWRP build should be simple to make with the sources I've linked in the OP. I haven't released one here (or on any device I support) because I don't want to support it directly (basically, I'm supporting what I use myself). If no one else makes one, I might make a one time build for those that want it.

Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks

Remote controller fix
cdsn99 said:
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
cdsn99 said:
Hi Steel01, . Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy

Josti-Band said:
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Click to expand...
Click to collapse
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.

cdsn99 said:
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
Click to expand...
Click to collapse
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.

I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy[/QUOTE]
Josti-Band said:
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
Click to expand...
Click to collapse
Thank you, that makes better sense, I will try and load a rom and gapps and see how it goes. thanks again for the assistance

Steel01 said:
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Hi Steel01 , I have a logitech k400r wireless keyboard and mouse, it seemed to work ok, except was very laggy, had to wait for it a few seconds each time I went to move the mouse, and sometimes mouse would freeze.
Click to expand...
Click to collapse

I have edited and deleted the orginal text from this post,and moved it to it's own thread. I realized I was beginning to hijack steels thread, I couldn't find a way to just delete the whole post, sorry.

Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.

Steel01 said:
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Click to expand...
Click to collapse
What about the kexec-hardboot patch ? Do you have already tried it ?
The others binary for multirom execution are the same for all arm64 devices like the nexus 9 or we need a specific build for shield ? I never played with multirom stuff. There are specific problems to solve ? In case i can help you with experiments if you don't have much time.
P.S.
I tried your patch for the framework and all others new Nvidia binary + resigned private apk like blakepairing and others. But this year Nvidia added many others things to the framework. You can see by yourself with dex2jar.
It's a shame that for a stupid controller there are all this bloatware inside the firmware. Very bad behaviour, that a so big company not publish drivers for an hardware that we have bought. Fortunately we can use also better wireless controllers. But this fact really remove 10000 points from Nvidia as good company.

I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.

Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Already tried all. deodexed and resigned stock stuff, also used your framework patch and your (resigned) apks . not work in shield console. as i write above in shield console there are others proprietary things in the framework. Tested also with your wpa_supplicant and hostapd but the result does not change.
In any way i will retry
We can discuss in a separate thread. sorry for off-topic. can be useful also for others developers

This is very interesting, please continue with this work! Would be great to get the remote working on other ROMs.
Thanks!
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse

Steel01 said:
I
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Click to expand...
Click to collapse
I have a logitech K830 keyboard with trackpad and have exactly the same issue as you. I have to unplug and replug the usb receiver before it will work with the recovery.
The recovery itself is working great for me. I can access my external usb hd from the file manager, and I did a TWRP backup to the external usb drive last night :good: Ive sideloaded this app to boot straight into the recovery from the TV.. https://play.google.com/store/apps/details?id=gt.reboot.utility