Develop Bugs

Rhobuntu: Ubuntu 9.04 and Debian (test) UPDATE [19/09/2010]

Important - Read First!
First of all you must know that everything you do is on your own risk. Your device was not designed to run GNU/Linux or Android and that's why you shouldn't expect everything to be perfectly safe. If you don't want any troubles then simply don't tamper with your phone. On the other hand, installing Rhobuntu is probably less dangerous than installing alternative ROM's, because it doesn't touch your ROM and runs completely from the SD card. If something goes wrong and the system would hang up, you always can remove the battery and boot into Windows Mobile. Still, we can't guarantee you anything and we won't be liable for any damage that might happen to your device. If you don't accept this, don't install Rhobuntu.
At the moment two problems are known to occur when using Rhobuntu. They are, however, not Rhobuntu specific and may also occur when using Android.
1- After booting back into WinMo, you can't install or run unsigned apps. This problem probably has something to do with the way haret kicks WinMo out of the RAM. It also seems to occur only in combination with the use of Exchange Server. The only known solution at the moment is Hard Reset. Some users also reported that it can be fixed by using Visual Studio 2008. Check out this threads:
o Not digitally signed with a Trusted certificate/ Activesync keeps UNINSTALLING!
o Program... is not digitally signed with trusted certificate. HELP!
2- Since we still have no proper battery charge indicator working, you might not notice that your battery is completely drained. Deep discharge is, however, not good for batteries and may in some cases even damage them. Here is a thread dealing with this problem when running Android
o Android killed my USB connection, please help
The majority of Rhobuntu users doesn't face these problems, but just in case, you've been warned.
WIKI http://wiki.xda-developers.com/index.php?pagename=RhodiumUbuntu
WEBSITE https://sites.google.com/site/rhobuntu/
This build by Walter79 and the Rhobuntu team:
Rhobuntu 9.04 19.09.2010
changelog:
- zimage update (Xandroid Build 16/09)
- sphone 0.04 (thanks AmiPro)
- 3G scripts update (thanks AmiPro)
- sound works partial (thanks to phhuson) !!! run /sdcard/ubuntu/playwav2 after boot !!!
- alsaplayer added
Download:
Link1: http://www.megaupload.com/?f=RWDJWUN0
Link2: http://rhobuntu.4shared.com
Debian Squeeze Test 19.09.2010
For more information please look at this post http://forum.xda-developers.com/showpost.php?p=8186181&postcount=1208
Download:
link1: http://www.4shared.com/dir/n-2ObqP_/pro2-debian.html
Old Build (27/06/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (13/05/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (14/04/2010)
*part one:http://rapidshare.com/files/375930803/Jaunty_14_04_2010.7z.001 MD5 77430e728bb17277e671cc55ae03161f and part two: http://rapidshare.com/files/375939439/Jaunty_14_04_2010.7z.002 MD5 523589000dcd5d1dcea668bbe51253af
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (11/04/2010)
* http://rs427.rapidshare.com/files/374730149/Jaunty_11_04_2010.7z
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (10/04/2010)
*http://rapidshare.com/files/374138895/Jaunty_10_04_2010.7z
*http://rhobuntu.4shared.com

Pretty cool idea, keep us posted!

Definitely an awesome idea, and one I had been thinking about myself since my original Touch Pro days. An embedded version of Linux should run great on these devices. Hopefully momentum will grow surrounding this.

thats very interesting. any pictures of this running? maybe things can be pulled from android.

THANKS!!!! downloading now!

tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.

aq3e said:
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
Click to expand...
Click to collapse
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?

Help!
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.

dicko99 said:
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
Click to expand...
Click to collapse
Wierd, my winmo works find, minus the calibration issue, it's brilliant, we need some linux Devs to look into this. as a windows user, i have no idea on what to do
Thanks (All we need now is win XP )
Badwolve1

I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.

dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
did you install anything recently, could try uninstalling it

dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
try installing SdkCerts.cab
http://forum.xda-developers.com/showthread.php?t=554240
the cab is included with the rhodium keymapper zip file. (keymapper app is worth installing as well )

sdkcerts won't install. It has the same problem as other cabs where it prompts to say the program is from an unknown publisher and when I tap Yes to continue it still fails with "Installation of SdkCerts.CAB was unsuccessful."

Tried booting it up on my Verizon TP2 and all it does is run haret and then freeze.

Thanks for putting this together, sebbo90. It boots nicely, and actually performs quite well on my Tilt2. I hope some of the developers take notice of this project and consider fixing the major usability issues like the front keys and the display calibration.

After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.

spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
How did you even get it to boot?
EDIT: Do you think it will not boot for me since you all are using GSM and i am using a CDMA phone? Some settings may need to be changed i guess. I have been messing around but no luck.

spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps

sebbo90 said:
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Click to expand...
Click to collapse
If the mtype needs to be changed, what should it be instead of the default 2292, forgive my ignorance.
EDIT: must be a fluke, it booted now, did not change a thing. Re-extracted the ubuntu rar and shoved it back on the SD and booted. Great Job. All we need now is calibration to get started.

sebbo90 said:
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
Click to expand...
Click to collapse
I got it working now. It was the directory structure I was using. I spent about 2 hours last night working on the calibration issue. If I could get that working it would be sweet. Tried a newer version of haret and tweaked the startup.txt a bit but the calibration still goes out of range.
On a brighter note, the calibration works fine when booting xdandroid with haret though it is a manual calibration there is hope anyway.

Bricked my phone while flashing NAND, possibly reversable. Need some help :)

Hey, xda-devs.
I need a bit of help. I was trying to flash Eclair 2.1 Polymod to NAND on my AT&T Tilt on T-Mobile's USA network. I was previously using Dutty's Diamond v1 and Myn's Warm Donut from haret.exe
Unfortunately, I was kind of stupid while flashing - I decided I was going to flash KAISIMG.nbh *before* I actually put the /andboot folder on there. (This was due to a lack of research on my part because I only looked at one how-to which omitted the /andboot step.)
"Well that's fine," I thought, "I'll just put the /andboot on there with the polymod inside and re-flash KAISIMG.nbh!" I did this, and it's still not working... which doesn't make alot of sense to me. My KAISIMG.nbh has no issue flashing, but when I restart the phone I get stuck at the first HTC splash with the planet & whatever.
I've tried multiple panels for the KAISIMG.nbh, I made sure nothing else was on the SD card, and I even tried a hard reset of my phone, still to no avail.
So tell me, xda-devs. Did I brick my phone? I don't think I did because it actually powers on and all that jazz, it just won't load the android install program.

dont think it is bricked
if you can get into the 3 colored bootloader screen it is not bricked. just flash wince rom and you should be able to use your phone again.
if you flashed an android nbh you should get the linux logo and see bunch of text scroll over your screen. it you hit the dpad you should get into the installer menu.
Maybe you didn't actually flash the nbh?
did you get into the tri colored bootloader screen and then did you hit power when prompted?
the android kaiser nbh normally doesn't have a splash screen, so your old wince splashscreen will remain.
hope this help, more details from your part would help us help you.

Hey, thanks for replying
Yes, I get the tri-color screen but I'm not getting the linux logo or anything of the sort. I'm getting the old splash screen that came with the phone. When I passed the tri-colored screen I get the prompt to press the power button, then it flashes KAISIMG.nbh, (Although it says something like "File - KAISIMG.nbh" and "OS - " then nothing after OS... dunno if that helps)
But I'm glad to know I didn't brick it!
I experimented with various KAISIMG.nbh files found here. I believe those are Android KAISIMGs although I don't know since I can't read them with my text editor.

It could be the problem I have once in a while on my Kaiser. Try removing the battery and hold down the power button. Put the battery back in and turn on your kaiser. You should start seeing the scrolling text.
As far as I know that's normal. Happens once in a while.

Dukenukemx said:
It could be the problem I have once in a while on my Kaiser. Try removing the battery and hold down the power button. Put the battery back in and turn on your kaiser. You should start seeing the scrolling text.
As far as I know that's normal. Happens once in a while.
Click to expand...
Click to collapse
Negative, no change... How long should I hold it down?

You're holding down the button to release any power left in your phone. Sometimes, it can be a hit or a miss.
If all else fails, invoke the loader by holding down power button + camera button, and then press the reset button with the stylus. Do this quickly when you turn on your phone, and you can problem load WM back onto your phone.
I think Android needs a custom HardSPl on Kaiser.

As far as the old splash screen is concerned, thats normal, flashing the nbh does not replace the splash screen, after flashing the nbh you usually have to pull the battery, wait a bit, then restart the phone, it takes a little time before the linux kernel boots the lcd panel, so at first it shows the splash screen for some time.
The screen will go weird briefly, followed by the scrolling text as linux kernel boots, watch for the 'hold dpad to enter installer' line, then press dpad centre button.
Don't worry about the need for a 'custom' HSPL, the hard-spl most of us use seems to work fine for majority of users, also although radio 1.71.09.01 is recommended, android will work fine with earlier radios, some even say it works better with some earlier radios, ( can't confirm this, since I seem to have no problems with anything radio related).
If you need to reflash WM, you can do this either using the bootloader in usb mode, or by putting a WM rom in SD renamed to kaisimg.nbh and flash by doing the power+camera method.

zenity said:
As far as the old splash screen is concerned, thats normal, flashing the nbh does not replace the splash screen, after flashing the nbh you usually have to pull the battery, wait a bit, then restart the phone, it takes a little time before the linux kernel boots the lcd panel, so at first it shows the splash screen for some time.
The screen will go weird briefly, followed by the scrolling text as linux kernel boots, watch for the 'hold dpad to enter installer' line, then press dpad centre button.
Don't worry about the need for a 'custom' HSPL, the hard-spl most of us use seems to work fine for majority of users, also although radio 1.71.09.01 is recommended, android will work fine with earlier radios, some even say it works better with some earlier radios, ( can't confirm this, since I seem to have no problems with anything radio related).
If you need to reflash WM, you can do this either using the bootloader in usb mode, or by putting a WM rom in SD renamed to kaisimg.nbh and flash by doing the power+camera method.
Click to expand...
Click to collapse
Yeah, that's the problem - I've flashed the .nbh, then taken the battery out for 10+minutes (including the method mentioned above of draining the power) but the screen never changes from the first splash page. I never get the scrolling text.
EDIT: I have a theory that maybe I should try the Panel 1 kaisimg.nbh instead of Panel 2 but since I don't have a computer that has a micro-SD slot it's a pain in the ass getting files on/off of there so I'll have to try it later. I'm also going to try with another built (Probably Myn's) to see if that works.

I got myself a cheap sd card reader and microsd adapter, makes life so much easier, however if you don't have access to one at the moment, just remove any sd in the phone, disable activesync, put the phone in bootloader, connect to usb cable, flash a WM rom, ( try a Stock HTC one from the wiki pages, this wipes everything, os,bootsplash,radio and gets rid of any traces of any custom roms).
And try running from SD to identify your panel type, etc, saves some time when flashing nand if you don't have to guess

[Q] No connection in Android with new build

Android was working perfectly ok with a 3G connection, but the new build isn't connecting. Any help? I didn't see anything in the FAQ.
I uninstalled the CAB from WinMo and deleted excess files off the microsd card.
Any idea on what's going on?

AVakil said:
Android was working perfectly ok with a 3G connection, but the new build isn't connecting. Any help? I didn't see anything in the FAQ.
I uninstalled the CAB from WinMo and deleted excess files off the microsd card.
Any idea on what's going on?
Click to expand...
Click to collapse
Is the force cdma option enabled in your startup? This only applies if you are on a CDMA carrier, obviously.
Also, don't use MGJDroidUtil... it has been known to screw up the startup.txt, I thought they were updating it tho... Haven't heard anything about it so just stay away from it...

Thanks for the tip regarding not using the launcher. I have noticed that startup.txt getting corrupted.
The force CDMA is enabled in my startup. I am on Sprint.

same....
I have the same problem. Force CDMA is checked. The BLAZN and default releases were my first attempt at this when audio support was added. Both of those tested and worked as expected. So that's two of us so far.
BTW I told myself I'd donate once some great minds got audio working. Is it best to donate on the main page or to any other specific party?

lip008 said:
I have the same problem. Force CDMA is checked. The BLAZN and default releases were my first attempt at this when audio support was added. Both of those tested and worked as expected. So that's two of us so far.
BTW I told myself I'd donate once some great minds got audio working. Is it best to donate on the main page or to any other specific party?
Click to expand...
Click to collapse
AVakil said:
Thanks for the tip regarding not using the launcher. I have noticed that startup.txt getting corrupted.
The force CDMA is enabled in my startup. I am on Sprint.
Click to expand...
Click to collapse
To both of you... you may want to format & start over. lip008, you said "force cdma is checked" - that sounds like you're using MGJDroidUtil, because the startup.txt is a text file... you have to make sure the force cdma command is in the cmdline section.
Oh and for donations, I'd say the general XDAndroid Donation page is sufficient

I'm on GSM (T-Mobile), and I had the same issue (not the BLAZN build, the regular one)

Ok, how about APN settings? sukru, others, have you checked those?
Honestly I haven't had to add the APN manually for several builds, but maybe there's a regression in the new build.
As always, make sure your rootfs, zImage/modules are up to date.

Heres the solution if you are on sprint
Boot into windows mobile and connect to pc so you can access the files in the andboot folder on your sd card. .
or (the purpose of this is so you can edit your STARTUP.TXT using notepad)
You can take out your SD CARD and put it in a card reader and do this too.. as long as you are in windows mobile..
DO NOT DO THIS IN ANDROID..
Once you get access to the SD CARD files.. go into the ANDBOOT folder..
locate STARTUP.TXT and edit it with notepad
locate the long line of commands that starts with "Set cmdline"....
read the entire line and somewhere in the middle you will find a part that says..
force_cdma=0 (remove this part only)
and make sure you have this at the end.... htc_hw.force_cdma=1
NEXT: SAVE YOUR FILE.. AND HERES THE IMPORTANT PART..
***** BOOT WITH HARET.EXE***** NOT WITH THE MGJDroidUtil program...
THIS WORKED FOR ME.. and if any of the mods here want to add to this.. please feel free to clarify..

In lamens terms... On cdma network sprint only
THERE IS A CORRUPT ENTRY IN THE STARTUP.TXT that needs to be removed..
EDIT this entry using notepad while not booted up in android.
the entry needs to be removed mentioned above..
DO NOT USE: MGJDroidUtil to start android.. USE FILE EXPLORER.. AND start
HARET.EXE..
hope this helps..
MINE READS AS FOLLOWS:
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 rel_path=andboot hw3d.force=1 physkeyboard=rhod400 htc_hw.force_cdma=1 "

lancevs, I appreciate then enthusiasm, but I don't think that would have any effect on GSM guys.
However, using MGJDroidUtil can still screw up anybody's startup.txt, regardless of the type of phone/radio... so he is correct in that fact:
DON'T USE MGJDROIDUTIL.EXE!!!!
Edit - didn't even think about it but sukru - do you have this force_cdma statement set to 1? For us CDMA guys it's required, but it probably will break you GSM guys if it is enabled... So check that out.

Yes for clarification
MY POST SAYS " FOR SPRINT USERS ONLY" at the TITLE...
GSM users, this does not apply..
I am on sprint and spent a good part of yesterday trying to figure out why i had no service.. I am on SPRINT which is a CDMA network..

arrrghhh said:
lancevs, I appreciate then enthusiasm, but I don't think that would have any effect on GSM guys.
However, using MGJDroidUtil can still screw up anybody's startup.txt, regardless of the type of phone/radio... so he is correct in that fact:
DON'T USE MGJDROIDUTIL.EXE!!!!
Edit - didn't even think about it but sukru - do you have this force_cdma statement set to 1? For us CDMA guys it's required, but it probably will break you GSM guys if it is enabled... So check that out.
Click to expand...
Click to collapse
Will check again tonight. Android was getting better each time, then it suddenly went down for me.

Hey guys. I had been running an early August (pre sound) release of Blazn, and everything had been fine. Today I decided to upgrade to get sound and 3D support, and every time I boot into Android it shows no signal, and shows I'm in airplane mode, and it will not let me turn the radio on.
I'm using a Sprint TP2, and I followed the instructions for earlier in the thread, but still no go.
Here's the line from my config file:
Code:
lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 hw3d.force=1 physkeyboard=rhod400 htc_hw.force_cdma=1
Is there something wrong in it? I am launching Haret directly from TotalCommander File Explorer. Same problem if I use the config/startup utility.
Also, to install the latest version, I deleted the andboot and android folders on my SD card, then installed via cab.

That line looks correct, perhaps you should post your entire startup.txt.
Or just start with a clean build - wipe everything Android related and do a fresh install. The new startup utility is pretty slick, just be sure you check force cdma in the advanced section.

Seems to be random. About 30% of the time it will work, the other 70% of the time "no service" and no way to turn on the radio.

shawndoc said:
Seems to be random. About 30% of the time it will work, the other 70% of the time "no service" and no way to turn on the radio.
Click to expand...
Click to collapse
Well, perhaps you shouldn't use the update utility at all. It has been updated so it shouldn't corrupt the startup.txt, but I had issues with it... so personally I prefer to just use haret & modify the startup.txt manually.

I am launching Haret directly, see OG post.

shawndoc said:
I am launching Haret directly, see OG post.
Click to expand...
Click to collapse
Start with a clean build. Don't touch the startup utility, because you said you had previously. It's been known to corrupt the startup.txt, even these new builds I had my startup.txt go to 0 bytes.

hi I am having the same problems cant get android to connect with sprint on the tp2. I am no expert but have become very good at using windows mobile as a user not a developer so all i know is i downloaded a cab file that was haret version 9 28 it came with a little icon labeled android project when i launch it i get to a screen that lets me make some advanced setting and check for updates before and choose my phone model. It says aka sovereinty at the bottom. I have tried to boot without forcing cdma and it does not connect and when i choose force cdma it seems likes its kinda connecting but keeps getting a error message and then i force close and it automatically tries again. If i boot wiithout force cdma the i can connect via wifi but that works but seems to also disconnect after a few minutes, though that is not my concern for now. I tried with the sim and without. and have updated twice so i am know on 10 4. anybody that get help would be appreciated. I love my tp2 with windows mobile but am curuios to play with android being that sprint wont let me unless i change my plan and make me pay double. not interested because my tp2 works great now and has everything i need.
thanks

[Q] Who provides a professional service to upgrade my Kaiser

Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry

I don't think there is a company that provides such a service especially if we take in to account that kaiser/tilt is a 3 year old device and the android port is not official. There are plenty of topics in the forum describing how to replace winmo with Android. You don't have to be a hacker to run Android on your phone. Just read the stickies and you wil be able to flash ityourself in no time

There are phone dealers out there (in the USA anyway), that will do this for a fee on the Kaiser, but trust me, with what has gone into the development of this, almost anyone can do it. Save yourself the money and try it yourself. The worst I've heard about is a mis-flashed phone needing some master reset.

The question is who?
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.

Henrykjr said:
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Click to expand...
Click to collapse
Listen HenrykJR there are about dozens of android builds on this forum + many different versions of two kernels, not all of those will work correctly for you. You might experience different issues with one setup but the other will work correctly for you. So even if there was a company that could flash it for you, you might end up with an unstable device. Also how could a company gain knowledge on flashing android builds to a phone that was originally shipped with windows mobile??? You seem to be looking for Nessy....in woods.
Your best bet now is to find someone in the forums to help you flash your device....maybe even use skype to show you how to do it. It really isn't that hard.

Hehe, i don´t think you´ll find a Company that will do it for you. Maybe you find some guys that do it for Money (me to ). But if you spend a little time with reading through this forum you could do it yourself and save the money.
Preparing:
1.) You need a SD card (mandatory for android on Kaiser). And you need a Google Mail Account for syncing your contacts etc. and access the android market.
2.) You have to "unlock" your Phone (with HSPL/HardSPL). Only after that you are able to flash things (Cusom WinMo ROMs, Radio, Android) to your Kaiser. So read through this guide and follow step 1-4.
3.) Now you have an unlocked phone an you should be able to flash everything. And the first thing you flash should be the latest "radio". The "radio" for Kaiser is similar to the BIOS for your PC. Like the subsystem and responsible for GSM chipset etc... So look & read in this Radio-Thread, download the latest Radio (it is 1.71.09.01) an follow the guide "Flashing Radio from microSD"
4.) Now your Phone is up-to-date and ready for flashing Android (or WinMo custom roms). YOU NEVER HAVE TO DO THE STEPS 1-3 AGAIN! Your Phone is now completely prepared!
Flashing Android:
For Android on Kaiser you always need 2 Parts. The Kernel (this part initialize the hardware so its similar to "driver" on PC) and the Built (the Android OS itself). But Both should work together so you´ll may find in some kernel suggestions in Built-threads because not ever kernel work with every built. For your beginning i whould suggest you some things:
First the kernel:
DZO is the most popular (the father of android on Kaiser) Kernel-Developer for Kaiser. So go to his repository and download "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh". Because Vouge and kaiser have almost the same hardware we all could use this kernel. But everyone have to modify this kernel to make phone related optimizations. You can do thy by hand (not recommended for you) or with a tool called "Atools". This tool is writthen in "Python" so mac and linux user could use it too. But you need to install Python. But that is all described in the Atools thread. Read through it and follow the guide.
Modifing Kernel:
We will only modify the madatory things. Not more at the moment...
So run Atools, klick on the "folder" Button and load the "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh".
Device: "Kaiser" should be checked
Resolution: 240x320 should be checked (native resolution of Kaiser display). Everything else will give blurry optic.
Version: "Froyo" should be checked, because we will flash a Froyo built (thats android 2.2). If you want to flash an older built like a Donut one (1.6) you have to modify & flash your kernel again.
Panel Type: Try "auto" or "1" first. But if you have a fuzzy screen or artifacts you have to try out which paneltype fits best for your device. HTC has built in 3 different displays in the Kaiser and the only way to find out which one is builtin is trial & error.
Keymap: Depends on which hardware keyboard layout you have. Here in Germeny i have to use "qwertz".
We leave the other options as they are an klick on the "Disk" button to save our modificated kernel now. it save it as "KAISIMG.nbh".
Now we need the Built:
I suggest "Fat Free Froyo" at the moment. Fast, stable, an looks good. So go to this thread and download "ODEX DOWNLOAD RLS5 ALL LANG-ODEX" on the bottom of the post.
then unzip/unrar this file...
Flashing your first Android:
1.) You should have a fat32 formatted SD card
2.) put the Kernel (the modified KAISIMG.nbh) to the root of SD card
3.) Create a folder named "andboot" on SD card
4.) Put the unzipped file (androidinstall.tar or .tgz) in the folder "andboot"
5.) Remove SIMcard and any cables from phone and put the SD card in your phone. Battery should be 50% carged or more...
6.) go to bootloader-mode (press and hold camera button and powerbutton). the KAISIMG should be loaded and it will show you "press powerbutton to update" or something similar. Do that... Now a progressbar will appear. When it is at 100% wait a few seconds an then pull the battery. Wait 10 seconds an insert it again. Voila! You flashed your first android kernel!
7.) Now we have to install android itself. So Power on the phone. In the moment when you see small white text on black background you have to press and hold the d-pad button. This one in the middle. Now you get in the install menu.
8.) Leave the options "System on nand" and "DATA on nand" as it is. Navigate to "install system" an press dpad. It ask "format system" and "format data". Both "YES". after this procedure you enter the menu again. navigate to "quit".
9.) Yeah! The first Bootup of Android! The first bootup takes longer as the following ones because now the system prepares for bootup and do a lot of optimisations. Even if you enter the lockscreen you should give it 10 minutes time to finish this optimization process in backround.
10.) Finish! You have flashed your first android completely! Now you can play around and make your settings. Remember: You have to sign in to your google account befor you can access the market or syncronize your contacts etc.!
Sounds more complicated as it is. Try it!
And if you´ll dig in deeper in this stuff you have to read here! Especially the Stickies/Refs/Tutorials! We´ve all done that!
have fun!

Henrykjr said:
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
Click to expand...
Click to collapse
Brother, You can do it yourself, I can assure you. Regarding any ambiguity, you can contact me through PM. (I can guide you complete on voice over skype / msn). Its a TIDEOUS job but EASY to do since there is no MEANS OF BRICKING your kaiser (unless you flash something else than what u have do to install android).
I am here to help you in this community. And you can do this thing yourself.
Your device is At&t Tilt. The bad thing about installing android is getting a RIGHT kernel that suits your LCD type and enables wifi in the android build u install. (maybe in 1st try, maybe takes almost 10 tries like it happened for me)

[NST/G] Update FW 1.2.2 UK (unofficial)

If anyone has an old UK device at the bottom of a drawer somewhere which they recollect has a non-English language dictionary from B&N on it, please contact me before trying this.
Spoiler: How I did it
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
The most important discovery was that the "UK ROM" was still there in the US FW 1.2.2 update. That is to say, if you copied over the splash screens from the UK 1.2.1 update and the Oxford dictionary, you had nearly everything that was different between the two. Except it didn't work. It looked different on boot, but was still the US version (you can tell by looking at Settings which are different in the two versions).
Eventually I took at look at the update script in the B&N zip and saw that it was checking build.prop before doing anything else. I compared that file on the UK 1.2.1 and US 1.2.2 zips and found the major difference was in localization. In two entries "GB" was used instead of "US". Was it that simple?
Yes!
Ah...but it refused to register. In fact, it refused to authenticate, so it never got to asking about your account. The final discovery was the result of a completely idle-brained attempt (because I was out of ideas). I had rooted an instance after skipping OOBE. In the launcher app drawer I saw the familiar junk, including DeviceRegistrator (anyone who has rooted an NST knows this app with the smiley-face icon). I've always thought it was just cyber-detritus, an early version or mock-up left by B&N developers. They were not very tidy, after all. But maybe intents of the app are used in the current registration process. Who knows? Anyway, I tapped on the icon and proceeded to successfully authenticate the device. That got my attention! Then I tried to register with my existing B&N account and password. BINGO! I could see my device on the B&N website under my account and I was able to "buy" a free book using the Shop app (you need a credit card on file with B&N to get even a free book).
So it works for me, in the US.
Because of the changes I made to the original US 1.2.2 update zip, the internal signature is broken, so it cannot be used as an auto-update zip. Hence the need for CWM.
To avoid the necessity to root (for those who would rather not), I removed the broken Lancher.apk in /system/app and replaced it with a simple launcher in the Gingerbread style that is able to run as a system app. So when the device gets to displaying "home", it asks how you want to do that. Initially, the Launcher app is selected so that you have access to an app drawer and the DeviceRegistrator app. After registration, a reboot will present the "home" option choice again. This time the "always" box can be ticked and the B&N "Home" app selected. The Launcher.apk will never be heard from again. Those who go on to root can remove it from /system/app if they wish.
Outstanding issue to be explored: dictionaries. There seems to be a capability for adding different language dictionaries. The User Guide refers to this also. I have not been successful in doing this and don't know whether there ever were any other dictionaries. Since this was not a US option, I'm guessing that the only hard-coded URLs for the dictionary downloads are to non-existent UK servers. I still haven't tracked down where those URLs are. The Nook app for Android is reputed to have the same capability, but when I installed it on one of my rooted tablets, it only had an English dictionary. The format of this db file seemed to be exactly the same as the Oxford dictionary on the UK ROM. I got a Spanish book from B&N and tried to look up a word from there. This gives an option to download a dictionary (as the user guide says) but the result just sends you to the Settings where the only dictionary visible is the default English. So maybe you have to be in another country? Anyway, I could not get the NST to recognize the English dictionary offloaded from the Nook app, despite the apparent structure similarity with the Oxford already onboard. Perhaps there is a database somewhere that would keep track of the dictionaries on the device if the download function were still working. I have not found it. Or, perhaps additional "downloaded" dictionaries have a special place to be (Edit: YES! They go into /data/media/B&N Downloads/Dictionary). Someone with a long memory who has experience with the UK ROM but is not primarily an English speaker might hold the key.
Spoiler: Q&A
--Is this the same thing as the Region Changer?
No. The region changer procedure gives you a device running US firmware (although it looks like B&N still knows it's a UK device based on the serial number and their own records--or they might be identifying its point of origin by the internet connection). This update zip will give you a true UK ROM: the different splash screens, the different settings options (including language) and the ability to enter letters with diacritical marks from the keyboard. It also features the Oxford dictionary. However, it will contact US B&N servers, not the non-existent UK ones.
--Do I need to have an existing B&N account?
I think so. The back door we are using to authenticate and register the device does not have an option for creating a new account.
--Should I deregister my device before doing this?
If you did a region change and are currently running registered US FW 1.2.2, I would recommend deregistering the device before converting to the UK ROM, just to avoid potential conflicts. You can use the same account to register the new ROM. If you have B&N content, it might even show up since it's the same account (mine did).
--Can I purchase books from B&N using the Shop app?
Maybe. I was able to "buy" a free book from B&N and have it appear on my device (note: to purchase even a free book you need to have a credit card on file for your B&N account). But, I am in the US. The B&N Terms of Service says that you have to use (or have on file) a credit card with a US address. There appear to be workarounds like purchasing a US-based cash card, etc. Seems like a lot of extra effort, but apparently some people have done it.
--I live in the US but this sounds interesting. Can I try it too?
Well, I did! The ROM is interesting in a number of ways. It really is a Western European variant, not just UK. German, English, French, Italian and Spanish are the available languages. If your primary language is not English but instead one of these, this might be an attraction. However, there is at least one unexpected consequence. Some external servers will be absolutely convinced you are outside the US. I found this out by trial-and-error when I could not get my Today's Comics app to work. When I changed the region to English (US), it began to work, so I guess the content was region-blocked. I jiggered the Settings app of the UK ROM slightly so it would display the English(US) option.
--I see "Chinese" among the languages! Can my NST display Chinese?
Well, no. Unfortunately the only way to get English(US) to display is to display all of the "development" languages. I tried to suppress "Chinese" but had no luck. There are Chinese characters in DroidSansFallback but the strings for the B&N system were never fully translated (maybe not at all). There is a lot that is translated (appears to be Taiwanese Chinese), probably left from the original phone ROM they used to make the NST OS. However, if you select Chinese any apps you may have installed that are correctly localized for Chinese will display appropriately.
How to do it
Note: I did this on a deregistered device. It does not matter whether your device is currently US FW 1.2.2 or a UK FW 1.2.1.
1. Prepare a CWM card (if you don't already have one, use one of the two sdcard versions). If you've never done this sort of thing before it's probably easiest to download the zip for the Nook Region Changer and follow the instructions there for making the sdcard (steps 1-3). You don't need the two update zips that are on the card, but it's still CWM. If you already have a Region Changer card, you can use it as-is.
2. Download a copy of my 1.2.2 UK update zip. Copy the update zip to the CWM card (the card should be in the card-reader slot of your PC, not in the Nook)
3. Power down your Nook.
4. Insert the CWM card into your Nook and power up. You'll see the logo and maybe the opening menu.
CWM is a little wobbly on the NST. Sometimes it seems to get stuck on a white screen after the logo. If that happens to you, press the lower right hardware button. That generally wakes it up.
Navigating in CWM involves using the upper left hardware button (go back to the previous menu), the two right hardware buttons (go up and down a menu) and the "n" button (do what is highlighted).
5. Move down to "backup and restore". Press "n".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6. The menu should show "backup" at the top. Press "n". This will backup your current configuration onto the sdcard.
7. At the conclusion of the backup you should be returned to the top of the menu.
8. Move down (or one step "up") to "advanced". Press "n".
9. Move down one step to "wipe dalvik cache". Press "n".
Then move way down (or a little up) to "yes". Press "n".
Here you may run into another CWM issue. At least for me, CWM has a tendency to freeze after any kind of wipe. If that happens to you, don't panic. If the buttons don't seem to be responsive, press and hold the power button. If the device does not reboot back into CWM, release the power button and press and hold again. Eventually the device will reboot, taking you to the top of the menu again.
10. From the top of the menu move down to "wipe data/factory reset". This option is just like the previous one, including the potential freeze. Do it.
11. From the top of the menu, move down to "install zip from sdcard". Press "n".
12. The top of the next menu says "choose zip from sdcard". Press "n".
13. Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
14. After the update is complete you need to return to the top of the menu where it says "reboot now" (if you are not already there). At that point, remove the CWM card from the device and press "n" to reboot.
15. Your Nook will boot into the UK ROM setup. You'll see the familiar multi-lingual splash screen, the marching dots, and finally come to a Language choice screen.
Select whichever language you prefer. You can change this later from Settings.
16. The next screen is the "Welcome" screen.
You are now going to execute a "skip OOBE". Since registration fails in the usual setup wizard, we will have to go in the back door, so to speak. At the "Welcome" screen, press and hold the upper right hardware button and swipe your finger across the top of the screen from left to right. You should see a "Factory" button appear in the upper left corner of the screen. Tap it.
17. Now you are on the Factory screen.
Again, press and hold the upper right hardware button and tap the screen in the lower right corner. You should see a "Skip OOBE" button appear on the screen. Tap it.
18. OK, so now you are faced with a choice which I have added to the ROM in order to finesse the registration issue without needing to root the device. There should be two options listed on the screen: Home (the B&N home screen) and Launcher (I added this). For now tap on "Home". The B&N home screen loads up with the infinite spinner in the lower half (no registration, no wi-fi, no data).
19. Press the "n" button and select "Settings". Set up a wi-fi connection and set the time zone and time display format. Leave wi-fi on. Use the power button to shut the device off.
20. Power up your Nook. When it has passed the marching dots it will ask you again whether you want "Home" or "Launcher". This time, choose "Launcher".
A simple Android launcher screen is displayed. All you care about is the app drawer, that little square of tiny squares in the center of the bottom of the screen. Tap it.
21. There is a bunch of stuff (mostly junk) in the app drawer. Resist the impulse to fool around there. Keep your eyes on the prize! Locate the DeviceRegistrator app (stupid smiley-face icon). Tap it. Check to be sure your wi-fi is on.
22. You need to do two things here.
First, register (authenticate) the device itself. That's the first button on the left in the first row. Tap that. If all is going well (and your wi-fi is on) you should get a confirmation alert. After that, type in your username (email) and password for your B&N account. There is no option here to create an account, so you need to have one already established for this to work. After you've typed in the information, tap on "Register User". You should get a confirmation alert. You can now turn off wi-fi. Press the "n" button and select "Settings". Check Device Info>About your NOOK. If everything went according to plan you should see that it is registered.
23. Shut down the Nook. Power up one more time. After the marching dots you are again faced with the choice of "Home" or "Launcher". Before you make your selection, tap on the little (empty) checkbox. This will make your next move permanent. Now tap on "Home".
You'll never hear from "Launcher" again. It will just languish in /system/app with all the other unused apps and your Nook is now registered and good to go!
If you want to root and further customize your Nook, select one of the updated NookManager packages. I strongly recommend using NookManager to make a backup of your device before rooting. The CWM backup you made at the beginning of this process is not a complete nandroid backup and you'd be better off with one before you make any more changes. If you are not interested in rooting, you may want to make another backup with the CWM card at this point and then put it away somewhere safe. Just in case.

I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!

ashh87 said:
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
Click to expand...
Click to collapse
Thanks a lot for the feedback. Now we know it was not just a one-time fluke for me. I'm glad it worked for you as well.

Also worked for me. After registering I used NookManager to root it, then installed the latuk kernel from this post with CWM and it's now UK 1.2.2 and external keyboard supporting. That's all I was looking for. Another thumbs up for the repeatability of your method. Thanks for the detailed instructions.
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?

markeq said:
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
Click to expand...
Click to collapse
Let's say--hypothetically, of course--that you did that. There are two ways around it.
1. If you rooted with the "traditional" or "stealth" versions of NookManager, you have ES File Explorer. You can use it to access the App Manager and remove the defaults from the "Launcher" (or "Home", or whatever). After doing this, a reboot will present you with the choices again. Screenshots for a likely sequence below.
2. A more general quick-and-dirty method that will work in any situation: install yet another launcher app. When you reboot, the activity picker will see a new option and give you your choices again. When you've got it right, just uninstall the additional launcher (which you never have to run for this method to work). Here's a link to another simple and relatively useless launcher that will fit the bill.

nmyshkin said:
Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
Click to expand...
Click to collapse
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
any ideas on what i could try different to get working ? otherwise im stuck on a de-registered 1.2.1uk so my only option might be to nuke all b&n and go custom ereader route (which is probably fine tbh)

A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?

Renate said:
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Click to expand...
Click to collapse
yeah it looks normal on my computer (im running popos although i cant see how that would change anything)

Well, you can always do it semi-manually, at least you'll get feedback.
Extract META-INF\com\google\android\update-binary
Go to TWRP and use ADB to push both the (original) zip and the (extracted) update-binary somewhere useful.
Use ADB (you do have a rooted prompt?)
Code:
# chmod 755 update-binary
# ./update-binary 2 1 whatever.zip
You'll get text out of this and maybe figure out what the problem is.

cyberboy666 said:
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
Click to expand...
Click to collapse
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, just in case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1

nmyshkin said:
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, jus tin case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
Click to expand...
Click to collapse
omg thanks ! yes i think issue was with CWM card - i flashed a new one from the link you gave and now it is working
and also thanks for the advice @Renate - i want to get set up/learn to send ADB anyway so this is helpful

Hmm, well, I didn't know that.
OTOH, you would have seen that you couldn't find an update-binary in that zip.

nmyshkin said:
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
Click to expand...
Click to collapse
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)

jewelie said:
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
Click to expand...
Click to collapse
I'm glad it worked for you. That's my reward
Unless your glowlight is not turning off completely, I can't think of any other factor on a stock system that would drain the battery fast, barring some unknown hardware issue.
Hopefully this sorts it out.

On top of the running an unregistered device, I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing. Other possibilities that have been suggested to me are corrupt books, and maybe having the WiFi off.
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Device is now on sleep with wifi off and no books after the fresh start. I also hacked the cover I was using to make sure it wasn't touching the screens or buttons. It's at 79% now, let's see what the percentage goes to over the next few days...
EDIT: BTW The reason I know it's not the battery itself is because I disassembled it and tested the battery through a few 0.5A charge & discharge cycles and gave it a week to see if there was any significant self discharge - madly, it still has almost the full 1500mAh capacity - impressive for a device that's been going for 10yrs now!

jewelie said:
I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing.
Click to expand...
Click to collapse
I think this has been debunked in the distant past although I can't put my finger on the particular post.
jewelie said:
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Click to expand...
Click to collapse
That part is interesting and the initial result is not surprising. Unfortunately CWM cannot do a thorough wipe unlike, say, TWRP. A factory re-image is the most thorough cleaning I'm aware of, followed by the deregister/erase, then with CWM bringing up the rear. The reason I didn't include a factory re-image at the beginning of the process is that I wanted to keep it simple and not scare away those averse to anything approaching root. The 8-failed-boot-attempts method for a factory re-image is tremendously tedious and involves close timing and dexterity. OTOH, a NookManager card can initiate the process with the push of one hardware button. But that means making yet another card and flirting with the whole root thing (not necessary to root just to do the factory re-image).
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.

@nmyshkin Thank you so much for the detailed guide.
I followed all the steps without any issue. I even got the freezing bug after clearing the Dalvik cache. But followed your steps, pressed on the power button twice and it restarted.
I used a 2Gb memory card and used the sd_2gb_clockwork-rc2.zip and I've written the image with WinImage 8.50.

nmyshkin said:
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
Click to expand...
Click to collapse
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?

jewelie said:
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
Click to expand...
Click to collapse
I'd say so, especially if you've been doing any reading at all.

nmyshkin said:
I'd say so, especially if you've been doing any reading at all.
Click to expand...
Click to collapse
Update: It's over a month later, battery is still on 26%. Touch wood, it's fixed. THANK YOU!