Database Develop

[Q] In what Heroic direction do I go?

Hi guys... I have a few questions for you about my Hero. Forgive me for not yet having the same level of knowledge that many of you guys have. I am certain that I can contribute in some way, as well. My phone details:
Firmware version: 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d
Build number: 1.56.651.2 CL5027
Software version: 1.56.651.2
Hardware version: 0002
1. I've read several stories where a number of phones were returned because they couldn't be updated when the new update was released. Is this an absolute fact, that it can't be updated, or is there an error in code somewhere that made it reject the update and there is a known workaround? The answer to this question obviously dictates my forward motion.
I have the typical problem apps, and am getting no joy from youtube. Presently, I'm surfing with good speeds, but market is non-existent.
I like having Sprint tv, when I'm having to sit and wait somewhere.
I have time today and tomorrow to get things ironed out, but will be extrmemly busy after that, like 20 hours a day studying. I'm hoping to get some direction that will give me complete functionality, but will require the least setup. I am quite computer savy, and repaired this phone, to this point, in a day or 2, without asking a single question of anyone. I traced down problems, and solved issues. Seen APN, and TCP errors (don't believe it completely, since I can authenticate on the web). Know that some issues are url problems, etc.
The following questions are based upon the answer to question number 1.
2. Can this phone be updated?
2a. If yes, What do you recommend... 2.1? What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction? (pancake??, superhero??)
2b. If no, What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction?
Before repairing the phone, I actually tried to update it from my computer, but it was rejected. I turned off my security software and tried again. I noticed that while using XP sp2, a windows program that was incorporated starting with sp2, DEP (data execution prevention) didn't like the actions that the update was taking, and arrested it very shortly after starting (yet the window cycled forever). I assume that many people wouldn't be this observative, and recognize that this was happening. It was halting an HTC file that utilized storage memory (similar to buffer overrun exploits - the reason DEP halted it), for temporary storage of the files to be used for the update. That file was as follows:
C:\Program Files\HTC\HTC Sync\Mobile Phone Monitor\FsyncServer.exe
And the way to prevent it from continuing to do so is:
1. Click Start
2. Select Control Panel
3. Select System
4. Click the Advanced tab
5. In the Performance region select Settings
6. Click the Data Execute tab in the dialog box that opens
7. Select Turn on DEP for all programs and services except for those I select
8. Click Add.
9. The open dialog box will open. Browse and select your application.
10. Click Open
11. Click Apply
12. Click Ok
I guess what I'm sort of suggesting, is that this might be why anyone ever had problems updating, with the exception that OTA also said there wasn't an update.
So, back to the original question. Is it true that some Heros can't be updated? I don't want to force something, and brick, if you know what I mean. I completed the setting that will allow it to go forward (listed above), but haven't tried to update since. I felt that I really needed to ask you guys first, before I made a mistake that I'd regret. Should I try again? Before I started working on the phone I did try OTA and it said there wasn't an update. Now I don't have that option anymore. After repairing the phone, I've lost updates. Am I stuck with 1.5? With my run of the mill phone desires (except that it be fully functional), should I keep 1.5?
I did see gmail 2.3 apk, but is that compatible with 1.5? This looks like is would solve the market issue, if I could use it.
I did read about gscript and addressing mms (although I'm sure that's very old news to you guys), but if in fact I can't update this phone, it might be one of my only alternatives. If that is my only choice, are their also additional scripts to address everything I need to fix (all the normal issues)?
Additionally, it seems that many apps register with the phone/user. So, when you are using a used phone, many apps are still registered as functional. Does flashing a new rom affect the OS and apps? Will I loose the already registered/functioning apps? With a complete upgrade, will I gain functionality of some key features, but lose all other previously enabled apps? In other words, will I gain update, and market, and lose sprint tv?
I have read a lot. With things the way they should be, I've not been able to quite determine what I need to do. With all this being said, How do I go forward and achieve a fully functioning phone? What is the best choice of path's to take for me?
Rooting? I have seen the one-click, and think I'd be correct in that I need something containing Sense UI. Forgive me for asking a stupid question... but the rom is only the menu accessibility, correct? Is there something straight out of the box setup, or do all roms contain configuration notes?
I'm satisfied with stock features, if they work, and adding other useful things like tethering. Since I'll be so busy, I'll have little time to do much else. But don't get me wrong. I have 10 PC's in my house, with only 2 people living here. I'd love to customize the crap out of it. It's just not going to happen any time soon, due to my brutal study schedule. So for now, I just want it to work like it should, on a B mvno.
Do I go north, south, east, or west????
Could someone chime in that can give me direction, based on everything I've stated. Your response is so graciously appreciated.
Cheers!

Umm well I'm not sure why you're having problems with any update, someone who's far more experienced can maybe tell you but as far as roms I think it depends on whether you like sense or wanna go froyo. Cyanogen mod 6.1 stable (2.2) is nice & highly customizable however there's also AOSP roms (2.2) that some people feel is quicker than cyanogen however they aren't as customizable as cyanogen, in addition there are tons of GREAT themes for both. Also we've had a ton of work on an odex AOSP gingerbread rom (2.3) not yet stable but works good for most & on that note a great themer also put together a themed AOSP gingerbread rom (2.3) that looks good & about stability I'm not so sure on but I would recommend those roms. Although with these roms YES you will lose sprint apps like TV & vvm etc. However people have posted these apks in the theme thread section to work on roms like cyanogen & AOSP. If you do like sense roms there's a couple that are still live in the development section like nfinite & nfx I believe. Hope some of that info helps

Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?

inkblots said:
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
Click to expand...
Click to collapse
Sort of. I can't remember which version I was at when I rooted but I remember I downgraded to do it. But if you go in the development section you will find a thread that shows & gives you what you need to root. So you should root. Then flash a recovery image such as clockwork mod or amon ra. When I rooted I used the recovery from the downloadable app (Rom manager) in the market & that one was clockdwork mod. It's worked great for me so I've been using it ever since. Then backup whatever you are running currently. Then flash whatever rom you want. I'm about to see if I can link you to a root thread then once you do so I can give you a dl link to cm 6.1 stable. Will you be able to root on 1.5?? I don't completely know...
Edit: Ok this is the way I rooted mine, hopefully this will work for you
http://theunlockr.com/2010/09/27/how-to-root-the-htc-hero-androot-method/

Problem when initially installing Android on HP Touchpad

Late last night I went to fix a touchpad that was handed to me, was told that the Android install was started, but had messed up. If I fixed it I could keep the touchpad.
So, i wandered over here and followed RolandDeschain79's how to install android thread, using the novacom,exe route with ACMEUninstaller2 and ACMEInstaller5. After running both of these (and placing the Cyanogen9 Mod on the tablet... i followed the instructions to the T). I got Android to run on it. BUT there was a problem! I got a bunch of notices @ initial startup, (Like 3). I don't remember what the other 2 were, but the biggest problem was the android keyboard would not function. Thinking that it would fix it, I went ahead and re-did what I had already done, running ACMEUninstaller2 and ACMEInstaller5. When I was in the middle of doing this the battery died (wish the stupid thing would just feed off power from my PC when it's plugged into it but apparently not). Now, I'm stuck in a bootloop (i think).
what does it do?:
The WEBOS boot screen, the little circle w/ HP in it? It just sits there. Sat there the entire time it was plugged in, didn't show me it was charging or anything. When I force it to shut off (hold power button and home key) it'll sit there 4 10 seconds or so, then turn itself right back on. I CAN GET INTO RECOVERY MODE however.
What I have done since then:
1. left it sit on the charger for about 7 hours... should be fully charged I hope.
2. Re-ran ACMEUninstaller2
3. Re-ran ACMEInstaller5
my thoughts were that if I can get an older ROM to work on it, I can upgrade to the most current from there.
HELP!!!!
Any ideas would be appreciated. This is the first tablet I've messed with, actually the first tablet I've owned and I'd really like to fix it...
Thanks in advance!

The easiest and most simple means of installing Android is with TP Toolbox. Follow the advice and instructions in the developers forum, you will have to do some reading to understand what you are doing.
I also am listing a link that I think is clear on the install:http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
As for the ROMS, there are a number to choose from. I have jcsullins installed on several TP's as well as pac-man ROM on another. Please take your time to read and decide.
Also, using toolbox will require that you use the naming convention for gapps as outlined in the toolbox thread.

Thank you. I followed the instructions on that site and the touchpad is working excellent.... Minus one glitch thus far: the camera works on boot, but as soon as you go to take a photo the whole screen digitizes and the touchpad loses connectivity with the camera. Is there an easy fix for this?

What ROM are you using? Also, which gapps did you install? Please be as specific as possible.

The ROM I am using is cyanogen 11 and I downloaded the gapps from the same page. The tablet upgraded itself last night and after that everything works great. It said something like upgrading apps, and reinstalled all the apps I had put on it. I'm playing with it as much as possible, making sure it acts like it should.
Thanks 4 all the help thus far

more issues
okay guys I am using invisiblek's cyanogen 11 and gapps... still have an issue with the camera I randomly acting up. it will work and then it won't. I have no clue where to even start with this. the build is from June of 2014. I do have an update available, I don't know if that will fix it but I do not have my laptop available at this current moment, so I cannot try it. Any ideas?

Are you reading the posts in the forum thread for that particular ROM? Other people using it may have encountered and fixed the issue.
I would invite you to read information about the various ROMS in the developer section as issues such as you are describing are
usually addressed and fixes or work arounds are presented.
I do not use the particular ROM you have installed but run other ROMS on several touchpads and do not have the problem you describe.

like an idiot I have not read the other threads regarding this particular CyanogenMod... I will look into them.
Thank you.

OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.

Greasemonkey50701 said:
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Click to expand...
Click to collapse
You can't bypass moboot, and what you're proposing is going to ultimately cause you problems. But if you must, the easiest way to do what you want is to reduce the moboot timeout so that it goes directly to boot quickly. Create (if it's not already there) or edit (if it is) a file named moboot.timeout and put the number of seconds you want moboot to wait before booting CM. You can do that with a root browser like ROM ToolBox lite, or you can do a terminal session and type in:
Code:
su
mount -o remount,rw /boot
cd /boot
echo "1" >/boot/moboot.timeout # will set timeout to 1 sec (defaults to 5)
sync

What problems would this cause? Call me stupid (and I am sometimes) but i really don't forsee any problems caused by doing this...

I think Shumash already answered your question.
You need moboot to boot into Android.
Android is Linux based and Linux requires the use of a bootloader.
The best you can do is to shorten the time out before it boots.
In spite of the best advice given to you...it is your touchpad and you are free to do what you choose.
Even if that means borking it for good.

OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.

Greasemonkey50701 said:
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Click to expand...
Click to collapse
You were clear enough, but seem to have some misunderstanding of what the sequence is. On boot, moboot times for a default 5 seconds and then automatically boots into Android, unless you screw with it by touching buttons or making selections. If you want it to do that faster, change the timeout as I suggested. You do not need to take anything off of it, and in fact, doing so will cause you grief eventually. If you take CWM off, and want to update your ROM, create a nandroid backup, clear the caches, or do any other low level stuff, you won't be able to. If it's booting into CWM (which you haven't said it does yet), then the moboot.default file has been changed. It should contain the word "CyanogenMod" (w/o the quotes) to boot directly to CM/Android. Use a root browser to edit or recreate it.

Touchpad Toolbox, past and present...

Hi All,
I've been putting this off long enough, but seeing as I won't see any updates for this device that are non-DM compiled... Thought it's about time I bit the bullet... and used Touchpad Toolbox
So, pre-questions before I go ahead and do it....
1) Going over to DM format, would I still be able to do my TRIPLE BOOT (of WebOS, Android and Ubuntu native)
2) Can I still flash non-DM roms to a DM formatted Tablet?
3) Can I return it back to fully stock
--- there are other questions, but currently distracted at work....
But just curious about those features if I upgraded the volume/partition layouts...??
Thanks, Lister

Former TouchPad user with questions about coming back

So, I've heard about the recent Lollipop ROM for TouchPad, and this made me consider getting out my TouchPad. I'm curious though, if the guides and such account for having a comparatively ancient Android/recovery installed, from ICS - possibly even a beta. Do I just reflash those with little troubles, or something else? Do the modern ROMs co-exist with webOS? I might get a small nostalgia trip from seeing how much better webOS multitasks than Android.

ampharos said:
So, I've heard about the recent Lollipop ROM for TouchPad, and this made me consider getting out my TouchPad. I'm curious though, if the guides and such account for having a comparatively ancient Android/recovery installed, from ICS - possibly even a beta. Do I just reflash those with little troubles, or something else? Do the modern ROMs co-exist with webOS? I might get a small nostalgia trip from seeing how much better webOS multitasks than Android.
Click to expand...
Click to collapse
First, modern Roms can coexist with webOS, however at this point I don't how how useful webOS is anymore. You may want to give TPToolbox a try and wipe webOS altogether. You can find great tutorials for this online.
Nonetheless, if you choose to keep webOS, you can flash a newer recovery from your old recovery, which will allow you to install lollipop or marshmallow. This will coincide with webOS. Although, if you have trouble installing a new recovery through the old recovery, then you can install a new recovery through TPToolbox, and from thereon flash a new rom.

As a former WebOS user I found that I stopped using my TP after HP shut down the servers in March. For a phone I jumped to BlackBerry and enjoy it all but for a few missing appps. My TP just sat in the charger. So this week I downloaded jstoolbox and installed Lollipop on it. So far so good an I am actually using it again.
It isn't WebOS but it is being used again.

Bringing an old Nook HD+ back to life

Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben

benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Bumping my original post - can someone help please? Cheers, Ben

benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Hey, one question, are you able to boot into TWRP? If so, you can flash any rom. Also, here is the link for installing stock rom again if you want. https://forum.xda-developers.com/nook-hd/development/stock-nook-hd-nook-hd-2-2-1-2018-update-t3840163 I personally haven't tested it though.