Hello,
I have an old HTC Hero (GSM) with a very old VillainROM on it, I haven't touched the phone for years. I now wanted to update with this ICS ROM (or potentially another one), however, I was unsure where to start, e.g. update my bootloader or whatever.
I tried copying the linked ROMs zipfile to the SD card, booting into my loader, wipe everything, and then "Install from zip". However, that fails while verifying the zip package.
I then also tried the newest official CM7 nightly for the hero, and that didn't produce above verify error.
Should I update my bootloader or something, or is just the ROM I tried broken? (for other people in that thread it seems to work).
What recovery do you use (CWM, AmonRA)?
Maybe you should try a newer one from here:
http://forum.xda-developers.com/showthread.php?t=1797626
derproblembaer said:
What recovery do you use (CWM, AmonRA)?
Maybe you should try a newer one from here:
http://forum.xda-developers.com/showthread.php?t=1797626
Click to expand...
Click to collapse
@derproblembaer Thanks for getting back to me! Just to close this, the phone wasn't really usable anymore, the touch was not working or acting weird on half the screen.
Elador said:
@derproblembaer Thanks for getting back to me! Just to close this, the phone wasn't really usable anymore, the touch was not working or acting weird on half the screen.
Click to expand...
Click to collapse
Yes exactly, why in the world does this happen? My friends HTC hero also, most of the times the bottom half of the phone does not work (touch). Thought a ROM problem so Flashed different ROM's and still the problem remains. He bought a new phone but he still has it, we could still try and see if we can do anything about that phone.
What can we use it for?
driverless said:
Yes exactly, why in the world does this happen? My friends HTC hero also, most of the times the bottom half of the phone does not work (touch). Thought a ROM problem so Flashed different ROM's and still the problem remains. He bought a new phone but he still has it, we could still try and see if we can do anything about that phone.
What can we use it for?
Click to expand...
Click to collapse
That's interesting! I assumed it was because I haven't been cleaning the screen for years and it was sticky etc., and even after proper cleaning it didn't work anymore. So I thought it was me and I should've taken more care And also, I mean it's really old.
However, maybe it's a Hero problem after all. And after thinking about it, it's not that old - it's from summer 2009 which makes is 5 years old. Hmm.
I had the same problem few years ago... two times with the same phone.
Related
Hey guys, I just followed to flashing guide for my touch pro, and installed EnergyROM on to it. The HSPL and flash and everything seemed to go fine, but now im on
http://forum.xda-developers.com/showthread.php?t=508084
Step 3
4. Once the phone reboots, go through Windows Mobile setup and let it finish.
My phone has been sitting at "PLease wait, phone starting up" for like 8 minutes.
This doesn't seem normal. . .should i be concerned?
Is your TouchPro CDMA or GSM? Sounds like you got the ROM to boot. Might just be taking a while. If it takes longer than 15 minutes, then reset the bugger. If something is indeed hosed with the ROM and it won't boot, just hold Volume Down and Power while hitting the reset button on the bottom, and you'll be back at the bootloader.
Cyfun said:
Is your TouchPro CDMA or GSM? Sounds like you got the ROM to boot. Might just be taking a while. If it takes longer than 15 minutes, then reset the bugger. If something is indeed hosed with the ROM and it won't boot, just hold Volume Down and Power while hitting the reset button on the bottom, and you'll be back at the bootloader.
Click to expand...
Click to collapse
It's verizon, so i assume it would be CDMA.
Alright, ill wait it out and give the reset a try if nothing happens. thanks
Curiously, if i end up being back at the bootloader, where should i procede?
actually i did the same installed a new rom and now it is stuck in start up , where it shows (touch Pro) stays lite for about a min or so then the whole phone reset. it seem to take the whole rom , because it said congrads installation is complete. now i cant do anything , like even install a different rom. i am wondering if i need to install a rom now via mini sd , or is there a master reset? and how am i going to install rom via mini sd
yellowz24 said:
actually i did the same installed a new rom and now it is stuck in start up , where it shows (touch Pro) stays lite for about a min or so then the whole phone reset. it seem to take the whole rom , because it said congrads installation is complete. now i cant do anything , like even install a different rom. i am wondering if i need to install a rom now via mini sd , or is there a master reset? and how am i going to install rom via mini sd
Click to expand...
Click to collapse
Like Cyfun said, hold Vol-Down/Power and Soft reset into bootloader. Plug the phone into USB and at the bottom serial should change to USB. Then flash away.
Otherwise, take a SD-micro and put your .nbh in the root folder, and rename it to RAPHIMG.nbh and reset into bootloader
holy crap that was fast, thanks , i am going to try it now
actually that worked, awesome!!!! i use to have a rom that was mighty rom (reborn) does anyone have the link for it , it seem to work the best on my phone!!
Sorry, never been a big fan of Mighty ROM. If you want something really Fast and Stable, I suggest Calkulins ROMs. Here is a link to the most recent release.
http://www.mediafire.com/file/tzmgjytkzm3/Calkulin's Touch Pro 23506 ROM v4.2.7z
I personally use NRG roms (due to them being updated so frequently). These however tend to be slightly buggy, and need many mods to suite individual needs.
Well once in bootloader mode i was able to get NFSFAN's rom installed with absolutely no issues.
So what did I do? Redownload a different version of energy rom and try it again. No luck there, the same thing happened. I think maybe energy rom just hates my phone. So I reflashed with NFSFAN's rom and i might just leave it with this. I dunno how much of a difference a noob flasher like myself will see between the two.
xmilkmanx said:
Well once in bootloader mode i was able to get NFSFAN's rom installed with absolutely no issues.
So what did I do? Redownload a different version of energy rom and try it again. No luck there, the same thing happened. I think maybe energy rom just hates my phone. So I reflashed with NFSFAN's rom and i might just leave it with this. I dunno how much of a difference a noob flasher like myself will see between the two.
Click to expand...
Click to collapse
EnergyROM has problems with Verizon phones.
SiqMawsh said:
EnergyROM has problems with Verizon phones.
Click to expand...
Click to collapse
wow that would have been good for NRG to mention in one of his posts... jeez.
antjc80 said:
Like Cyfun said, hold Vol-Down/Power and Soft reset into bootloader. Plug the phone into USB and at the bottom serial should change to USB. Then flash away.
Otherwise, take a SD-micro and put your .nbh in the root folder, and rename it to RAPHIMG.nbh and reset into bootloader
Click to expand...
Click to collapse
this post saved my butt guys. was having the exact same problem but didn't know how to reset to bootloader, thought my phone was bricked...
Ive never been able to get Energy to boot up on my Sprint TP. Tried flash dancing, etc, gets stuck on touch pro screen. Ended up using another ROM. Anecdotal of course
Me too...
That same thing happened to me, I've tried a few other energy ROMs but they've all been too buggy for me. I think he ported his GSM ROM over to CDMA because when I tried sending a text it asked for a SIM card.
I like psyki and I'm running Twisted NewSense right now...there are more CDMA ROM's over at ppcgeeks dot com
Maestro Nobones said:
wow that would have been good for NRG to mention in one of his posts... jeez.
Click to expand...
Click to collapse
why? the verizon touch pro is seriously gimped..MOST roms will barely run on them. the guys cook the roms according to how they like them, and likely theyre not on verizon if its not working. just flash a bunch of different roms till you find one that works, and i also have read that most verion touch pros seem to run better with pagepool at 6 so i suggest you try that..good luck with it, but remember that the guys that cook these dont owe any explanation if the dont want to. were getting state of the art roms (built for new phones) on our out-of-date touch pros for free.
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
weati said:
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
Click to expand...
Click to collapse
Are you following the instructions as stated in the op?
Sent from my SGH-I777 running AOKP
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
No
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Phalanx7621 said:
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
Click to expand...
Click to collapse
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
And because this phone isn't other phones, you can't use rom manager with it. It's a nono. And there is a sticky about it. And many threads. And posts. Warning about it.
thanks
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Butchr said:
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
Click to expand...
Click to collapse
weati said:
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Click to expand...
Click to collapse
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
mattdm said:
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
Click to expand...
Click to collapse
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
1. Kies generally only works with stock unrooted phones. Use Odin instead.
2. The phone has no "inability to take a new rom" if you do it the right way.
3. Apparently you don't know pretty well what you're doing.
4. The i9100 works exactly the same way as the i777, and if you try to use Rom Manager on it, you'll end up with the same result: a phone that won't boot.
5. AT&T will unlock an i777 for you if you ask them.
6. Just read the damn stickies, particularly this one and this one.
This thread is full of win.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
You resolved the problem by buying the unbranded version of the exact same phone?
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
So u paid 70 dollars to unlock a phone. Great hope it was worth it. Because like others have said they are identical.
Sent from my SGH-I777 running AOKP
to make a long story short I had to go back to stock after something happened when I tried to flash the new Carbon ROM. Anyway, the screen works and the buttons, but touch is gone. Not sure what to do .. don't have root, don't have CMW, can't navigate.
Any ideas?
You can run recovery (CWM) from sd card, on any OS.
About touch screen, have you run the 10 touch firmware at any time from a cm10 or newer ROM?
Sent with my Dinc4G
You know, I didn't even think of that... I'm so used to just installing it after a reflash. As far as the 10 touch mod, I believe I did that quite a while ago, but I have wiped/reflashed quite a few times since then. Would that still affect the system?
Yeah, as far as I know re-installing the stock ROM does not flash you back to 2-touch; you'd have to do that if you want to use stock ROM again. However, there's no need if you plan to go straight back to Carbon (or any other full android ROM that supports 10-touch) via a bootable SD card.
I am planning on running carbon, but I was trying to get back to a stock state because it was hanging at the carbon logo and no matter what I tried, it didn't work. I figured that starting from scratch would work... I didn't count on losing touch lok
criscross79 said:
I am planning on running carbon, but I was trying to get back to a stock state because it was hanging at the carbon logo and no matter what I tried, it didn't work. I figured that starting from scratch would work... I didn't count on losing touch lok
Click to expand...
Click to collapse
All you really need to do is flash a cm10/cm10.1 based ROM - they all have the 10 touch firmware app pre-installed. Then just run the app to go back to 2 touch. You can then go back to stock no problem.
Look around though, I think Succulent has a newer SD CWM file, you may have some issues flashing CM10/CM10.1 with an older version of CWM.
Good Luck
Same issue
Man my nook tablet was running great. but a few days ago my daughter was playing with it and I have no idea if she pushed the touch app on purpose. I have a feeling she did. Now its not working, it just stays on locked screen. Someone help.
centenj said:
Man my nook tablet was running great. but a few days ago my daughter was playing with it and I have no idea if she pushed the touch app on purpose. I have a feeling she did. Now its not working, it just stays on locked screen. Someone help.
Click to expand...
Click to collapse
If your NT is running a recent CM10.x build it should work with either 2-touch or multi-touch. So your problem might not be Touch-FW related. But if you suspect it is, as @DavDoc suggested above, burn one of Succulent's CM10 SD image to SDcard, boot that SDcard then use the Touch FW Flasher app to flash back to 2-touch.
Oh No
Well I guess its not the problem. I did a complete factory reset and still the problem exsist. I rooted it again and flashed cm7 with the gapps and still the same problem. I guess it decided to really give up. Any suggestions anyone.
centenj said:
Well I guess its not the problem. I did a complete factory reset and still the problem exsist. I rooted it again and flashed cm7 with the gapps and still the same problem. I guess it decided to really give up. Any suggestions anyone.
Click to expand...
Click to collapse
Were you running CM10 when this happened? Have you tried burning the CM10 card suggested and run it? I suspect there is a hardware error, but I just want confirmation that you actually have tried what's already suggested. CM7 will not work woth multitouch. You need to try CM10 if you haven't!
right
Yeah when this happened I was running CM10. I haven't tried the SD card method but I'll do it when I get home. Any place where I can find a CM10version in SD.
centenj said:
Yeah when this happened I was running CM10. I haven't tried the SD card method but I'll do it when I get home. Any place where I can find a CM10version in SD.
Click to expand...
Click to collapse
It's worth a try, but if you were running CM10 when it happened it probably won't help. But it's worth a try anyway!
try reflashing a compatible kernel. it should do the trick
Kernel?
rafiur said:
try reflashing a compatible kernel. it should do the trick
Click to expand...
Click to collapse
Hey where can I find that.
centenj said:
Hey where can I find that.
Click to expand...
Click to collapse
http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/.
Weird
OK something weird is going on. I returned back to stock and the touch was not working. So I Rooted it and flashed CM7 and it still didnt work. So I went to CWM and flashed CM10.2 and still didnt work. I gave up and left the nook off for a while. I turned it back on and it started working. WTF. The next day I turned it on from sleep mode and it didnt work again. I did the same procedure the next day and it did the same thing. Someone help!
DavDoc said:
You can run recovery (CWM) from sd card, on any OS.
About touch screen, have you run the 10 touch firmware at any time from a cm10 or newer ROM?
Sent with my Dinc4G
Click to expand...
Click to collapse
exactly what i was thinking , did this myself , even made a post about it last week , stock doesnt support it so it ends up non responsive ,
but from your last post , that sounds like it was working then not working then working and not working , it might be a hardware failure ....
if its out of warranty crack it open , inspect the cables to the screen under a microscope
Do you have problem with whole touch screen or a part. I have unresponsive problem of touch screen on the top then bottom until it happened with whole touch screen.
That's hardware problem. My friend has the same. Nook Table has low quality touch screen, so after 1 years or more, the touch screen becomming unresponsive!
The best solution is replace touch screen with new one but I recommend you change from Nook Table to another like Nexus 7
HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
dorianshehu said:
HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
Click to expand...
Click to collapse
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
es0tericcha0s said:
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
Click to expand...
Click to collapse
Thanks es0tericcha0s,
i did restore from the same firmware just after doing a factory reset. Because of the big file size of the restore the process stopped in the middle ( the phone was hot in fact ) and after reboot no touch working. Even after changed the screen still the same.
I did a full RUU.exe but no success and now after doing a lot of things on it, the phone does not mount /sdcard when in CWM recovery mode.
I dont know what to try any more first to fix the mount of sdcard and then try something else.
Please advice .
Thanks
BR
That's not good. Sounds like when the phone got hot and failed to restore that something might have happened to the motherboard. I seem to remember that some HTCs of that generation had touchscreen issues due to something shorting out, but can't seem to find the thread anymore. Sorry. Might be time to save for an upgrade. At least something that gets LTE...
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.