Develop Bugs

Help - HTC TouchPro2 Sprint - Side volume up/down buttons no longer working

Anyone ever have the volume up/down buttons on the side of the phone stop functioning correctly?
Looks like the buttons themselves still work (they now scroll up/down on pages instead of adjusting volume up/down). Any suggestions?
I'm running Energy Rom sense 2.5, cookie hometab 1.6 and HDwalls with cookie patch.
Thanks

Didy ou install the keyboard fix after installing the energy ROM?

Thanks for the response. No - was not aware of one. I can check out the energy thread for it.
Odd though because this just happened yesterday (volume sidebar was working fine before then) and ive been running the rom for like two weeks now. Only new thing I did yesterday was install transparent tabs, a cookie tab fix and new wallpaper thru HD Wall.
Matt

stenuine said:
Thanks for the response. No - was not aware of one. I can check out the energy thread for it.
Odd though because this just happened yesterday (volume sidebar was working fine before then) and ive been running the rom for like two weeks now. Only new thing I did yesterday was install transparent tabs, a cookie tab fix and new wallpaper thru HD Wall.
Matt
Click to expand...
Click to collapse
I know there are reg edits available in cab form that change the vol up/down buttons into up/down scroll buttons. Nothing in your list would be likely to include that, but it's possible...that's the only thing I can think of that would change their behavior like that.

Thanks. I might just look to isolate those two areas and try to set back. I also have that zoombar app (to use for other purposes) but dont think that would affect it, plus I didnt have the problem until days after i installed.
Tried soft/hard reset as well with no avail.
sirphunkee said:
I know there are reg edits available in cab form that change the vol up/down buttons into up/down scroll buttons. Nothing in your list would be likely to include that, but it's possible...that's the only thing I can think of that would change their behavior like that.
Click to expand...
Click to collapse

stenuine said:
Thanks. I might just look to isolate those two areas and try to set back. I also have that zoombar app (to use for other purposes) but dont think that would affect it, plus I didnt have the problem until days after i installed.
Tried soft/hard reset as well with no avail.
Click to expand...
Click to collapse
I'm guessing you mean just a soft-reset (rebooting)..? A hard-reset is where you wipe the memory clean putting everything in the OS back to stock settings (or back to the fresh version of a custom ROM, if you've flashed one on to your device). If you've hard-reset and this problem still persisted, then you can pretty much rule out software as a cause...
Yes, my approach would be to just start uninstalling stuff in reverse order, soft-resetting and testing after each item removed.

Yep - definitely meant soft reset. I'll try your advice. Thanks so much.
sirphunkee said:
I'm guessing you mean just a soft-reset (rebooting)..? A hard-reset is where you wipe the memory clean putting everything in the OS back to stock settings (or back to the fresh version of a custom ROM, if you've flashed one on to your device). If you've hard-reset and this problem still persisted, then you can pretty much rule out software as a cause...
Yes, my approach would be to just start uninstalling stuff in reverse order, soft-resetting and testing after each item removed.
Click to expand...
Click to collapse

stenuine said:
Yep - definitely meant soft reset. I'll try your advice. Thanks so much.
Click to expand...
Click to collapse
No problem! Good luck, and let us know what you find

Hi SirPhunk
Deleted everything that I'd installed since the problem occured and still no luck :-/. Buttons on side of phone still scrolling up/down, instead of adjusting volume.
I also tried the Sprint keyboard fix for Energy roms, but no luck there as well. Any other ideas? Do you happen to know if theres a way to search for the value in my registry?
Thanks again

If you want to go searching in your resgistry for it, PHM_Regedit and Total Commander can both search for specific keys...I would just try the string "volbutton" or even just "volb*", something like that.
Now, even though you didn't see the issue immediately when you installed it, I think there's still a possibility that the zoombar app could be the culprit....I would try uninstalling that too (if you haven't already) before you start doing the extra work.
EDIT: It also might be easiest to just install Rhodium Keyboard Controller (attached below) and use it to manually map them back to stock function (don't ask me why I didn't think of that in the first place ). In fact, if you do that, try uninstalling RKC right after doing that mapping, and I'll bet they return to their stock function after that even without the app being needed anymore.

Sir Phunk, Thank you for taking the time to investigate and the response, Sir Phunk. I went ahead and dloaded the cab to my storage card, but cant seem to find the files in order to run and edit the keys manually. Sorry if this is a stupid question - I'm still learning the ins n' outs. Maybe this will help me fully install programs that may be hanging around (even though I went to the "remove programs" section and deleted them).
Please advise if you have a chance. Again, my apologies as I am still learning. Thank you again.

stenuine said:
Sir Phunk, Thank you for taking the time to investigate and the response, Sir Phunk. I went ahead and dloaded the cab to my storage card, but cant seem to find the files in order to run and edit the keys manually. Sorry if this is a stupid question - I'm still learning the ins n' outs. Maybe this will help me fully install programs that may be hanging around (even though I went to the "remove programs" section and deleted them).
Please advise if you have a chance. Again, my apologies as I am still learning. Thank you again.
Click to expand...
Click to collapse
Will do...full instructions coming first thing in the morning

Hey stenuine, let's see if we can get this working for you...
First, I'm again guilty of not explaining things well enough (seriously), my apologies. That file I posted earlier is actually a .zip file, with 2 .cab files inside...it'll be easiest if you download it to your PC desktop, unzip the 2 files out of there, and then copy them over to the SD card.
[TIP: I would strongly recommend creating a "cabs" folder at the root-level of your storage card, and using that to retain any cabs that you run and know that work, even if you're not still using them at the moment. That way, you'll always have easy access to any of them, even through flashes and hard-resets]
The first file in that .zip is the sdkcerts cab, run that one first. It allows your phone to use many of the homebrewed apps and tweaks found here at xda. After that one's installed (do a soft-reset again if the install doesn't force that anyway, always a good habit), then you can just run the keyboard controller cab to install it. Once you have the app installed, the icon to run it is found in:
Settings -> All Settings -> System (it will say "Keyboard Config").
Once you get it installed ok, here's how to use it to get your key's mapped the way you want:
1. When you first open the app, you'll see what's in the first screenshot below(pretty much a blank screen).
2. Click "Menu" in the bottom right
3. Click "Add key" from the menu
4. You'll see the dialog in the 2nd screenshot below, go ahead and tap the volume-up button
5. Now you'll see what's in the 3rd screenshot below, the setup window. There's a lot of stuff there, but we'll only need some of it for this. First, in the "Key mode" drop-down list, choose "Direct key mapping"
6. Now you see what's in the 4th screenshot. Now what you need to do is click the "Key" dropdown list, and scroll all the way down to pick "117 F6-VOL UP"...if you did all that right, it should look like the 5th screenshot.
7. Click "Ok" in the bottom left of the screen. Now, you should be back to the very first screen you saw, but now with the mapping you just created (screenshot 6).
8. VERY IMPORTANT...at this point you must remember to hit "Update config" in the bottom left, or the work you just did won't have any effect. It'll confirm for you that it updated, and that's it! You just mapped one of the volume buttons
9. Now, follow steps 2-9 again, with the following exceptions:
Step 4 - tap the volume down button this time
Step 6 - pick "118 F7-VOL DOWN"
As long as you did all that, and hit "update config" after each one, you should now be able to close the app and have normal volume-button operation.
As you noticed there's a lot of versatility in this little app, so if that still doesn't work for you, there's other ways we can try...this is just the most direct and should work just fine.

Hey SirPhunk,
Thanks for your time and the very detailed breakdown. I was able to install the app and run it, but no luck re-assigning the buttons :-/. Tried re-assigning vol-up button to vol-up and vol-down button to vol-down, but no change. To test, I also re-assigned the "up" key on my flip-out keyboard to "volume-up" and still no dice. Made sure to save the registry after each change and tried with and w/o soft resets after the changes. The vol-up and vol-down buttons still just scroll up/down on the screen and up button on keybard still just scrolls up as well.
I saw what you meant about other functions for this program, just not sure which to try next in order to fix this issue. Thank you again.

bumping my post...

i just ended up doin a hard reset. My best guess is it could have been the zoombar scroller v2 app that screwed with the settings.

[n00b Guide] Your USA T-Mobile Defy: Rooting, Roms, and fixing 3G

Disclaimer: I make no warranties expressed or implied. This information is provided for research and educational purposes only. By reading this post, you agree not to hold me, my estate, my heirs, or my dog responsible for anything ever and waive all of your rights to legal action against said parties forever in perpetuity. Amen.
Note: this guide covers Android 2.1 (Eclair). Various builds of Android 2.2 (Froyo) are available in the forum. You should NOT use my guide if you are installing a build of Android 2.2 (Froyo). Currently I am running the Jboogie Froyo Rom, Orange DeBlur v4, which is great and (in my opinion) the best Froyo Rom out there for USA T-Mobile. Froyo is not much faster than Eclair in terms of benchmarks, but the apps are better, especially if you need the Android email app for connecting to an exchange server.
Now, on to the guide:
Goal: starting with a fresh-out-of-the-box Defy from T-Mobile USA, root the phone, install a non-US (or other) Rom, and recover your 3G capabilities.
Why: non-US Roms have much less bloatware from T-mo and Motorola, and allow you to install JIT/Deodex if you want
0) Oh noes! You've got to sign up for a Motoblur account just to use your phone! Create a throwaway email address at any of the webmail providers (gmail, yahoo etc.) and then go through the motions on the phone to set it up and get to the main home screen. Editorial note: wtf!!!
1) Get root access to your phone. Following Sorensiim's excellent guide, download the Z4Root app, which allows you to root (and unroot) your Defy. (thanks to Sorensiim for hosting!)
>> n00b notes:
First, go to Settings -> Applications and check "Unknown Sources" so you can run the Z4Root app.
Also go to Settings -> Applications -> Development and check "USB Debugging" so you can connect to your phone from your computer later.
Then open your phone's browser, navigate to this page, and download the app directly to your phone.
Install the app from your "Downloads" folder (accessible inside your Browser)
Run the Z4Root app on your phone, hit the "root" button and wait for it to work its magic.
This is what you will see if you run Z4Root after you reboot from rooting:
{
"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"
}
2) Install recovery so that you can make a backup of your operating system to your SD card before you do anything else - that way you can go back to the stock T-mobile OS if you need to.
Following Sorensiim's excellent guide, and many thanks to tenfar who put it together for us, just go here to download the Recovery App. (thanks to Sorensiim for hosting!)
>> n00b notes:
Just like before, visit this page on your phone's browser. Click the link to download the recover app, and once it's done, install it.
Allow the app to have root access, and check the box to always allow.
Once you are in the System Recovery program, click "Install Recovery System"; it will let you know when it's successfully installed (see image below):
3) Make a backup by opening the System Recovery app, and then press the "Recovery Boot" button. Back it up! Once again, details here, big thanks to tenfar!
>> n00b notes:
Once you have booted into recovery, you'll see the black/green screen shown below.
Use the volume buttons to navigate the menu and the power button to select an option.
Go to "Backup and Restore", and then "Backup".
If you need to restore later, just do the same thing except hit "Restore" and then select the one you want.
4) Flash a different ROM! Now here's where it get's a little more tricky. First, you'll want to follow Higgsy's Debranding Guide closely. I won't repeat his excellent guide, but here are my comments on the steps in the guide:
>> n00b notes:
Technically this step is optional - you can still weed out the bloatware and overclock while keeping your stock USA ROM. However, you will miss out on being able to install JIT/Deodex and having other features of non-USA roms, such as tethering.
Step 1: I used the consumer drivers package - Motorola 4.8.0 Driver with MotoConnect - since I am using 64 bit Windows 7. You can also use the developer drivers that Higgsy links to in his guide (available here).
Step 2: I used the JRDNEM_U3_2.34.1 firmware from central Europe, since you don't have to deal with Motoblur that way. You don't have to use this Rom of course, there are a bunch of different options, but I wanted to stick with a "real" Rom from Motorola as a starting point. Note that a firmware version is not the same as an Android version - i.e. v2.34.1 is NOT android 2.3, it is still anroid 2.1. Confusing, I know. Other Rom options include custom Roms that people put together and list in the XDA Developers forum. If you want to use one of those, you would follow their instructions for installing that particular custom Rom.
Step 3: In case the RSD Lite download link in the guide doesn't work, you can also get it from Megaupload the password for the site and the rar file is 'alabama'.
Step 7: Before booting the phone into the bootloader, you may want to clear out your data manually (aka "wipe your phone"). Go back into the System Recovery app, go to "Recovery Boot", and then when you're back on the black screen, select "Wipe DATA/Factory reset", "Wipe CACHE Partition" and then also go to "Advanced" and then select "Wipe Dalvik Cache". Then hold down the power button to turn off your phone. You won't be able to boot your phone after this, except by holding down the volume up + power on buttons together to get into the bootloader, so I would make 100% sure you have the drivers and RSD Lite installed and working!
Step 8: I would recommend waiting until it says "PASS" on the right side of the RSD Lite window before closing the program (this is after the "PLEASE START PHONE MANUALLY" phase is completed).
You should now have a working phone, with EDGE connectivity (little "E" in your status bar at the top) but no 3G or H icons. What, no 3G? We'll fix that next.
5) Re-root your phone and reinstall System Recovery following steps 1 and 2 above.
6) Install JIT/Deodexed: Optional step if you flashed either the 2.21 or 2.34 ROM. If you want to make your phone a bit faster, this is for you. Higgsy's guide is here if you want to do this!
>> n00b notes:
Update: on my third time flashing the phone, I was able to get JIT/Deodexed working fine. I think my failure the first time may have been due to my old SIM card, which I replaced because I was having problems reading the card and sending text messages (couldn't update the SMSC number).
Originally, I couldn't get the JIT/Deodexed package to work on my USA phone after installing the 2.34.1 firmware (too many 'untoward things happening' like Higgsy warned about), so I just skipped it the second time I flashed the 2.34.1 firmware.
The process of installing the packages is super easy, although you may want to make a backup before you start just in case. You can never have too many backups, because you can always transfer them to your computer if your SD card gets full. They are stored on your SD card under /goapkrev/backup/
The performance improvements are substantial - see graphs below.
Obviously you must get the package that matches the version of the ROM you installed. If you didn't flash a new ROM and still have the stock USA one, you are out of luck.
7) Make another backup! Now you want to backup your freshly-installed (and possibly JIT/Deodexed) Non-US Rom. Your first backup was the USA T-mobile Rom. You'll want to make this backup in case you eff something up in one of the next couple steps and want to go back to a fresh Non-US install and try-again.
Following the instructions in Step 3 above, load the System Recovery app, Recovery Reboot, and make a backup. Then reboot your phone!
8) Install ADB and/or Android SDK on your computer - there is a great guide on the Cyanogen Mod Wiki here. Just go slow, and follow the instructions. Once you can do "adb devices" and see your phone, you're good to proceed onward.
>> n00b notes:
To open a Command Prompt in Windows, go to "start" -> "run" and type "cmd" in the box or just go to "start" -> "all programs" -> "accessories" -> "command prompt").
Note that if you have 64-bit windows, you'll still need to install the regular 32-bit Java Development Kit (JDK), not the 64-bit version.
When you're editing your "path" environment variables in windows, note that you can't have spaces before or after semicolons. This is what my full path looks like (and iTunes works now - it didn't when I accidentally left a space after QTSystem\;
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;[B]%SystemRoot%;C:\Program Files (x86)\Android\android-sdk-windows\platform-tools;C:\Program Files (x86)\Android\android-sdk-windows\tools[/B]
9) Fix 3G
*** NOTE: This step only applies to USA phones. If you're not in the USA, your 3G probably works fine.
Download HandlerExploit's 3G fix from the 2.21 UK ROM or my 3G fix from the 6.19 US ROM. Thanks to HandlerExploit for figuring this out for us.
>> n00b notes:
There's not much difference between the two 3G fixes, except that each one will display different info in the "About Phone" section (either v2.21 or v6.19). For example, if you use my fix, "About Phone" will tell you that you have "Build number: JORDN_U3_6.19.0" installed - this is a side affect of the patch. For HandlerExploit's fix, "About Phone" will report v.2.21 GB
You may want to write down what Rom you actually installed if you think you might forget (for example, my phone actually has "JRDNEM_U3_2.34.1" even though it reports 6.19.0 in "About Phone")
If you downloaded HandlerExploit's 3gFix, you can choose to follow his instructions or the ones below, which are basically the same as what is in his, except you enter the commands line-by-line instead of running them through a script. I prefer line by line because I like to know what I'm doing. Both methods should work fine.
If you are unfamiliar with basic command prompt commands (cd dir ls etc.) please see my reply later in this thread
Once you download the zip file, extract it somewhere, like your desktop.
Alright, time to get some ADB skills. Plug your phone in via USB and open a command prompt. First we connect to the phone by typing this, each command followed by the "Enter" key:
Code:
adb shell
Then you want to run some commands as a super user so type:
Code:
su
Quick! Look at your phone, and tell it to always allow superuser access. You only have to do this once.
You should have a "#" command prompt now (instead of a "$" like before) indicating that you are working as a superuser (#=superuser). Now some more commands to enter. (n00b tip: you can copy and paste each line into the command prompt by copying the line from this guide and right clicking "paste" on the command prompt window)
Code:
mount -o remount,rw -t ext3 /dev/block/mmsblk1p21 /system
chmod 0777 /system/etc/motorola/bp_nvm_default
chmod 0777 /system/etc/motorola
chmod 0777 /system/etc
chmod 0777 /system/app
chmod 0777 /system/lib
chmod 0777 /system/lib/modules
chmod 0777 /system
exit
exit
So now we have set CHMOD Permissions for some folders on your phone, and then quit the adb shell. Now we've got to push some files to the phone:
Navigate to the folder where you extracted the files from the 3g fix you downloaded above, for example, type:
Code:
cd c:\users\administrator\desktop\3gfix\
then enter:
Code:
adb push system /system
This will copy all the files in the subfolder "system" to your phone's "/system" folder, overwriting them (which is why we made a backup earlier). Then enter:
Code:
adb reboot
to reboot your phone. You should have 3G connectivity now - note that it may take up to a minute or so for it to appear the first time, and you may not see the icon at all if you have WiFi enabled (so disable it in your settings to test it out).
If it still doesn't work, try going to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Access Point Names" -> (settings button of four squares) -> "Reset to default". Also make sure the APN name is highlighted with a green dot. You may also have to go to "Settings" -> "Wireless & Networks" -> "Mobile Networks" -> "Operator Selection" -> "Select Automatically"
This is what the 3G icon looks like of course:
10) The phone is yours. You can:
Install some apps: Titanium Backup & Launcher Pro for example.
Weed out the bloatware, overclock, and scale: see Sorensiim's awesome guide here. I highly recommend doing this, just bumping up to 1000mhz overclock makes the phone's performance much more snappy. If you overclock, you should definitely use Sorensiim's scaling method and his scaling files -- it makes a very noticeable improvement in battery life.
Benchmark your phone: with Quadrant Standard Edition, available in the app market
Play Angry Birds all day: :-D
Here is my phone benchmarked, with no overclocking, no bloatware removal, no JIT/Deodex packages, just the stock JRDNEM_U3_2.34.1 firmware (note that the phone with the US Rom straight out of the box benchmarks a little higher at 987. I'm not sure why this is.):
Here it is after overclocking to 1000mhz and my own customized bloat removal (not as much as most people, i use some of the default apps), also still no JIT/Deodex. Obviously you can get it to go faster if you want to overclock more, install JIT/Deodex, and remove more bloat:
Edit: These are the apps I disabled for the second benchmark (renaming them using Sorensiim's guide )
AdService.apk
ArcPhotoworkshop.apk
ArcVideoEditorLite.apk
esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.apk
FBAndroid-1.3.2.apk
Fota.apk
hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.apk
Kindle-1.0.2-OEM-SingleSign.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MySpace.apk
Protips.apk
Quickoffice_BasicViewer_2.0.52.apk
revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk
truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.apk
WeatherWidget.apk
Here is what I got to after JIT/Deodexed was installed on 2.34 - same apps removed, same overclock at 1000mhz. Removing VisualizationWallpapers.apk and YouTube.apk got me to 1308.

Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Sent from my MB525 using XDA App

Passa91 said:
Wow, great guide! I might try this later.. I do have a question though, if we've already set up our phones on a stock rom, can Titanum Backup or the recovery backup our apps and settings and then restore them to our new deblured ROM?
Click to expand...
Click to collapse
Yes, you would do that with Titanium Backup. System Recovery is for making entire images. It's easier to replace things piece-by-piece with Titanium Backup.

Thanks for this...along with handler's tips on SA I got it working.

Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...

heglen said:
Although I´m not an US user (hence got working 3G) I´m still on the 2.34.1 ROM, and I still use som of the default apps.
Just wondering though: which ones did you remove? I´m not going to get into ADB, but I was thinking of removing some of ´em with TB.
Slightly OT - can you safely remove Swype? There´s no swedish language support for that, and I´ve gotten used to TouchPal anyway...
Click to expand...
Click to collapse
Sure you can remove Swype, theres still the standard android keyboard installed as well. Check out scandinavian keyboard from the market too

I had a big problem in step #8, installing ADB. No matter what I tried, the command "adb devices" would not work. But I was able to solve it by following this:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
You have to download the ADB files from
http://www.megaupload.com/?d=RTEY0Q97
and put them into your
Android\android-sdk-windows\tools
directory. Word is, they were taken out by Google for whatever reason in the R08 version, and must be restored in order for ADB to work.
After I extracted the files into the Tools folder, and used the 'adb devices' command, it worked like a charm!

Quick noob question.
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo? Currently as I have the stock firmware/ROM it does not let me connect to neither 3G nor Edge. I've tried my SIM with Nokia N900 and 3G works fine, since the T-mo network doesn't recognize it as a smart phone. Please let me know if de-bluring/debranding my Defy will solve this problem for me.
Thanks in advance.

nvvass said:
If I install a custom ROM on my Defy following this guide and then restore the T-mo US 3G connectivity - will I be able to use the "Web2 go" unlimited plan without being detected and blocked by T-mo?
Click to expand...
Click to collapse
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.

rob-t said:
Why did you buy an android smartphone if you don't have a plan for it? Can't help ya.
Click to expand...
Click to collapse
I do have a plan. Many friends' Nexuses work fine with the same plan. I know a guy with a Nokia N900 and it works in 3G even with his grandfathered T-zone for $4.99. Why pay more? You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Thanks.

nvvass said:
You didn't answer my question though - can you give a specific answer? As in "will work" or "won't work".
Click to expand...
Click to collapse
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.

Wifi Calling?
Great tutorial for us noobs! Thanks! How does this affect wifi calling?

rob-t said:
Seeing as how I never had even heard of web2go before your post, I really have no idea. I'm not entirely sure I know what T-zone and web2go even /are/.
If you follow the instructions above and you still can't use your web2go thing, you can always roll back to your first backup and then use Z4root to unroot your phone, effectively returning it to 'stock' condition.
Click to expand...
Click to collapse
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.

bcrawf68 said:
Great tutorial for us noobs! Thanks! How does this affect wifi calling?
Click to expand...
Click to collapse
WiFi calling seems to work fine for me.
nvvass said:
Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan.
Click to expand...
Click to collapse
Ah OK thanks for the explanation. I currently use T-mobile but I don't really know much about their offerings. I would try the 2.21 or 2.34 firmware and then apply the UK 3G fix made by HandlerExploit, instead of the USA 3G fix I made from the US firmware.
Only one way to really find out though...

Excellent!
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.

cloogshizer said:
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
Thanks, yes, I updated the guide accordingly. 3G fixing should only be necessary in the USA.

nvvass said:
I'm sorry I assumed you're familiar with T-mo US, but thanks for responding anyway. Basically, web2go is an unlimited data plan for $10, that T-mo used to provide for "dumb" phones. T-zones was it's previous version (before 3G times) priced at $4.99 and was offered for all phones other than BBs. I remember getting a Dash (T-mo branded HTC Excalibur), witch was one of the first phones T-mo started to call "smart", and was able to get full Inet access with my T-zones just by tweaking some APN settings on the phone. In fact I (and many others) was able to get that without any data plan for awhile, before T-mo caught up with it and started blocking it. Of course it was too slow for browsing (EDGE/GPRS), but you could get your e-mails pretty easily and search stuff when in a pinch. Speaking of that - anybody remember when texting was free? Anywho, at some point in time T-mo started blocking smart phones from accessing data services on a "dumb" data plan - apparently by adding a piece of code to the FW of all T-mo branded phones, that allows their network to recognize the phone as "smart" and then block access if a "dumb" plan is used. Now, if you use a non-T-mo branded phone (even the same model that has a T-mo version) the network is not able to figure the type of phone and lets you access regardless of data plan. So, I hope this long explanation helps you understand where I was coming from with my original question. Obviously, when you flash the Defy with a non-T-mo ROM you get rid of the piece of code that makes the phone identifiable, but then when you copy part of the original ROM to restore 3G functionality, does that part contain the ID code also, I was wondering. At any rate, if you're not familiar/don't use T-mo you wouldn't know, I understand, I guess I'll have to go through the steps and figure it out for myself. Thanks anyway.
Click to expand...
Click to collapse
cloogshizer said:
Steps 1-8 of your guide are also very helpful for non-US Defy users!
3G fixing, however, is probably not required on European Defys and I would not recommend following steps 9 et seq for those devices. Please correct me if I'm wrong here.
Click to expand...
Click to collapse
first of all.. thank's for the great tutorial man..!!
second of all, I got this T-mobile defy from my uncle and I used it in Indonesia.. It's true what nvvass said, that the T-mo firmware constantly tries to connect with the "smart phone" data plan.. which caused me to unable to connect to my local provider data connection.. after I flashed the defy with the central-europe de-blur firmware, Voila..!! I got 3G connection directly..!! without any settings at all..
hope this helps for anyone using US T-mobile defy outsite of US.. cheers mate..

if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?

Jt612 said:
if i have no reception (the signal bars have a red circle with a line through it on top) will this kind of 3g fix but relevant to australia fix the issue?
Click to expand...
Click to collapse
where did you get the phone from? if it from US and still locked with T-mobile, than it would refuse to connect with local provider.. you need unlock code..

i bought it in australia its an australian phone... works fine when i restore my backup of australian software but i would like to use the 2.34.1

[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)

[Q] Tried to update, now unuseable

So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.

Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)

Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.

I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.

EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?

Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.

In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!

Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.

EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.

UK 1.2.0 Glow ONLY TFU Software Upgrade

After much debate I have decided to make my work public as a lot of people seem to want these features!
THIS IS AN ALPHA SOFTWARE! EXPECT BUGS!
THEREFORE IF YOU INSTALL, ITS YOUR CHOICE. I TAKE NO RESPONSIBILITY IF THINGS GO DOWN THE PAN!
To get this working well, I need you guys! The testers - the community!
TFU ROM UPGRADE PACK ALPHA 3
What is it?
This software pack will supply your STOCK UK nook with software 1.2.0 with the following features:
ROOT
BUSYBOX
ADB
A clean nook friendly interface
A custom kernel (Thanks guevor http://forum.xda-developers.com/showthread.php?t=1906507)
Multitouch
Browser, Email, PDF, News Feed, Lots of tools
A custom built video mod to improve multitouch speed, refresh rates, delay and general display performance
MORE (but I cant remember)
Follow this guide to backup your nook and find out everything you need to know about the process. Please do this BEFORE any other tinkering! Make sure you know what you are doing!
http://forum.xda-developers.com/showthread.php?t=1961835
How to Install
Make a CWM SD card:
http://forum.xda-developers.com/showthread.php?t=1360994
Flash my zip:
http://dl.dropbox.com/u/13673492/TFU_ALPHA3.zip
Reboot:
You now have everything you need to get started!
BUGS:
Cant install apps unless you use ADB or drop them into /data/app and install.
If some of the preinstalled apps don't work follow this procedure:
-Open nook color tools and disable/enable allow non-market apps.
-Use file explorer to browse to /data/app and click on and install the broken app.
If you need help with ADB or want a different way to root check out my other post here!
http://forum.xda-developers.com/showthread.php?t=1961835
If you find a bug let me know please!

RESERVED

Hi Loney,
Installed just now and all seems well so far - well done!
John

I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.

Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks

stelph said:
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
Click to expand...
Click to collapse
You are spot on. I didn't want to cause problems for people. Is your firmware 1.2.0? its firmware differences which are most likely to cause a problem. If you have a good backup, give it a go. If it works great. If not, you could try sending me your framework.jar file and I can try and find out what the differences are. Good luck!

roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks for posting this. Very useful for people who aren't familiar with the nook. I will mention your name and this post when I update my guide with this information.

Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.

roustabout said:
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
Click to expand...
Click to collapse
This is great news. Everyone will benefit from some constancy across all devices.

Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!

stelph said:
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
Click to expand...
Click to collapse
In my next update you will be able to customise the launcher as you like. The fact that you cant is a bug that can be fixed by clearing the launcher data using the included titanium backup program.

Since i'm back from the hell of the "bricked nook", now i can come back to test your mod with more understanding.
It seems that if we change the language to all but english, the installation of the mod is doomed to a blank launcher. (that was the case for registering the nook i have to do it in english).
I reflash my nook after setting it in english and that correctly installs everything (not Opera but that's easy to recover it).
may be a note for foreigners who try to install this mod is to be aware of keeping the nook in shakespeare's mother tongue.
would you mind integrating in your future version the manga reader "perfect viewer"? fastmode.apk is also a request but now i understand that is not so easy.
thanks for your contribution. :highfive:

I'll report my experience using this technique. A few days ago, I purchased a US Nook Simple Touch (non-glow) which came with software v.1.0. I made a backup using the method referenced in the OP. I then upgraded to software v.1.2 via the manual (USB mode) method shown at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/ . I made another backup. I verified both backups using the SD card method as suggested by roustabout. Everything looked good.
I followed the OP instructions and was successful in installing TFU_ALPHA3.zip with CWM.
Upon reboot of the NST, I saw a dialog chooser asking me to select either the standard Nook software or Launcher7. I first tried Launcher7 and was greeted with a large gray "n" background. Nothing else. The only button that had functionality was the "n" button which brought up the "home" menu at the bottom of the screen. This got me back to the standard Nook software. So at least the reader still worked.
I rebooted and tried Launcher7 again, just to be sure. Still nothing but the large gray "n" background. No apps.
I restored my v.1.2 backup without any problems, and am now back to a "stock" NST. All good.
So while the TFU_ALPHA3.zip installation proceeded without incident, I didn't see any apps that I could run from Launcher7. I guess I'll have to try a different technique.

it seems like the same problem i said in my previous topic. did you set your language to anything but english?
i had the launcher7 without anything loaded. I had to set the language in english then reinstall the TFUAlpha3 to make it work correctly.
hope it helps.

jjinkou2 said:
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
Click to expand...
Click to collapse
I have the US version of the NST. I couldn't find any way to change the language in the settings.

fastmode is working but we have to set it manually. i read this here http://forum.xda-developers.com/showthread.php?t=1241419, and i tested it.
Code:
adb shell
# cd /sys/class/graphics/fb0/
# echo -n 1 > fmode
# echo -n 0 > pgflip_refresh
since no-refresh and fastmode are autoexclusive i set pgflip_refresh to 0.
values are lost when the nook reboots.

New version coming soon. Lets start a list of requests guys. And if anyone has tested custom graphics settings, what works for you?

Loney,
Things that aren't working for me:
* Launcher 7 settings can't be altered (changes don't "save")
* apk installs are hitty-missy. Sometimes moving an apk into /data/apps and rebooting will work, other times I need to install it again by clicking on it in a file explorer.
* Fast mode app does nothing (but we knew that...)
Other than that, all is cool. I have also installed the patched .jars from the "mod manager" thread and they work alongside your changes.
Well done for your efforts on our behalf. Shout if you want anything specific testing - I'm confident that I can recover from "bricking"!
John

loney01843 said:
New version coming soon. Lets start a list of requests guys.
Click to expand...
Click to collapse
I haven't tried this yet, but when I do I would imagine access to google markets would be needed.

A follow-up on my experience which may (or may not) help getting this to work with the US NST (non-glow). Yesterday, I decided to give GlowNooter (http://forum.xda-developers.com/showthread.php?t=1675706) a try. Suspecting that it wouldn't work out-of-the-box, I deleted /system/framework/framework.jar from the glownooter.zip file. Installation of the .zip succeeded, and I was able to run ADW Launcher. I added my account to YouTube, attempted to sync in GMail, rebooted, and installed the PART-2-END.zip. Then I tried to open up Market, but kept getting connection errors. I also tried the Browser app, but was unable to enter text into Google's search page. So I guess there is stuff in glownooter's framework.jar file that is needed for everything to work. I didn't try too much more.
Anyway, I reverted to the stock NST 1.2 software for now. But I am happy to help with testing new firmware since I'm pretty confident about restoring to stock software.