Database Users

Borked my Hero

Hi guys,
I was a total idiot and manage to make my Hero into a whats essentially an expensive brick.
I got root going by booting from insecure boot.img. Then after verifying that it worked, playing around a bit, rebooting, i continued, with the pursuit of installing cyanogenmod.
So I dled and fastbooted from cm-hero-recovery.img (cm 1.4 + jF) (#android told me later that i wanted i wanted 32A, which wasnt specified it this image, but it worked). Did a nandroid backup that i managed to delete just afterwards (Boy, that was phucking selfownage). From there I pushed cyanogenmod-update-4.0.1.zip over to the sdcard and upgraded the device. It finished successfully.
When rebooting the device only comes up with what #android calls the first boot screen, only HERO with no android coming up in the O (i miss that cute little android). logcat says - waiting for device -. For the record, ive never come beyond this point now. Ive let it boot for 6 hours, its not that i didnt wait long enough.
With help from alankila (thanks mate) at #android i used his nandroid backups from a factory reset to flash cache boot userdata system, all of them. Ive also wiped before that. Everything went successfully, but to no avail. It still wont boot further than that first boot image; HERO without an android in the O. Logcat: waiting for device.
After that ive tried using some of the leaked Hero rom's, other custom roms (both same as before, successfull install, fails at boot), recovery image 32A (didnt work), CM 32A (same as before).
My default recovery image says:
HERO CVT SHIP S-ON
HBOOT-1.76.00004 (HERO1000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.04.25
Jul 3 2009, 15:22:21
I feel like I have tried everything except making a goldcard. Do anyone have an idea of what to do (other than return to seller and admit guilt)?
Thanks in advance,
Thinky

wow, sounds like you are in deep. i think the s**t would be way over my head by now so i cant help you much. Where did you get the phone from?

Sorry to hear that.
This is the reason I really don't want to mess about rooting and booting different ROM's unless I really have to.

joemax - you not debranded yours then? im thinking about doing it if I want to get hold of this update?

I'm a European, so they sell it here - got it at a regular cell phone store. I certainly am not going to attempt to go further than rooting it, before someone else has done it and documented it properly. its really hard to find good information on this device. Google search for Hero ROM will most likely leave you with lots of ROMs for Magic with a hero theme (rosie).

From what I read on the forum, it may be the case that we won't need too.
Loading the new official HTC firmware supplied (somewhere here hopefully) by a trusted source from the HTC website (it will use serial number / IMEI to check to see if the upgrade is valid on your handset) will effectively replace the Orange firmware.
Currently the only customisation that they have done is the start up Orange logo. As of yet there is no other customisation that I can see anywhere.
Internet access info is pulled from the SIM I am led to understand.
Best we wait to see how this all goes - being a bit proud of my Hero, I will let other braver more adventurous souls try it first

Joe,
Interesting, I think it might be best to wait for this new update from HTC and see if it will update our Orange Mobile Hero's, I would hope it would personally like you but time will tell.
If it doesn't then it's time to look at De branding. But as you say best to wait to get the update (if it actually materialises!) and then go from there
Rich

Come on guys, im without a phone here, please dont hijack my thread. Does anyone have any helpful advice?

Sorry Thinkpad...have you posted on Modaco?

No i did not. Thanks for the tip.

no probs;
http://android.modaco.com/category/409/htc-hero-hero-modaco-com/

thinkpadx86 said:
Hi guys,
I was a total idiot and manage to make my Hero into a whats essentially an expensive brick.
I got root going by booting from insecure boot.img. Then after verifying that it worked, playing around a bit, rebooting, i continued, with the pursuit of installing cyanogenmod.
So I dled and fastbooted from cm-hero-recovery.img (cm 1.4 + jF) (#android told me later that i wanted i wanted 32A, which wasnt specified it this image, but it worked). Did a nandroid backup that i managed to delete just afterwards (Boy, that was phucking selfownage). From there I pushed cyanogenmod-update-4.0.1.zip over to the sdcard and upgraded the device. It finished successfully.
When rebooting the device only comes up with what #android calls the first boot screen, only HERO with no android coming up in the O (i miss that cute little android). logcat says - waiting for device -. For the record, ive never come beyond this point now. Ive let it boot for 6 hours, its not that i didnt wait long enough.
With help from alankila (thanks mate) at #android i used his nandroid backups from a factory reset to flash cache boot userdata system, all of them. Ive also wiped before that. Everything went successfully, but to no avail. It still wont boot further than that first boot image; HERO without an android in the O. Logcat: waiting for device.
After that ive tried using some of the leaked Hero rom's, other custom roms (both same as before, successfull install, fails at boot), recovery image 32A (didnt work), CM 32A (same as before).
My default recovery image says:
HERO CVT SHIP S-ON
HBOOT-1.76.00004 (HERO1000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.04.25
Jul 3 2009, 15:22:21
I feel like I have tried everything except making a goldcard. Do anyone have an idea of what to do (other than return to seller and admit guilt)?
Thanks in advance,
Thinky
Click to expand...
Click to collapse
so far as i know, there are no custom roms out yet for htc hero.
did u try flashing the stock hero rom from this thread?
http://forum.xda-developers.com/showthread.php?t=547282

Is it a unlocked hero or a orange/t-mobile one? That firmware will probably only work on the original unlocked one. But its your best bet.
For Orange you'll need 1.76.61.3
and for t-mobile you'll need 1.76.110.6

SOLVED:
With help from packetlss over at madoca.com I fixed it.
Yesterday I tried flashing all the partitions with flash_image from adb shell. That didnt work.
Today packetlss ran RUU for me (since he was on a Windows computer, its a windows executable), and made a nandroid backup of it. Then he sent me the zip containing all the .img's and the nandroid.md5. I made a path on the phone, using adb shell, under /sdcard/ called
nandroid/HT97PL902664/CBDMRS12-20090820-1613
which equals
nandroid/Serial Number/I presume static-date-time
I pushed all the .img's over, along with the md5 checksum file.
Then I fastbooted cm-hero-recovery.img and selected the "Restore latest backup".
It worked. Thanks to packetlss. I promise not to be stupid in the future.
Thinky

Excellent, good news

I seem to have landed myself in the same situation, not exactly sure what to do.
Can anyone help me?

evertb said:
I seem to have landed myself in the same situation, not exactly sure what to do.
Can anyone help me?
Click to expand...
Click to collapse
This is a very old thread,... What is the problem with your phone pal?

Phone will not install PC36IMG.zip file, tried a couple sd cards, stuck on boot loop

My friend gave me his Evo to try to fix. It isn't rooted so S-on. I tried put a recovery file on to see if I can change the rom, but it just won't recognize it. Someone else posted a similar problem, but he got is to work. I tested the card and file and my evo asked if I wanted to update, but his phone will not work. It is stuck in boot loop. Not sure how he got stock on that. He doesn't mess with phones. There was an unbrick program I tried and it didn't seem to work, but I probably wasn't using it correctly since it kept changing the rom to the same rom from what I could tell.
It boots up sometimes to seem to work for a minute then boots again. I get the red triangle when I try to go into recovery. It probably doesn't have a recovery img since we haven't tried to root it.

ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.

ok
dzee206 said:
ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.
Click to expand...
Click to collapse
I can hold the power and down vol and go into bootloader. It goes through the zip file loading instructions and can't find the PC36IMG image and never asks if I want to update. I think I read a post where someone was told their bootloader is "locked".

if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..

ok
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
I believe it was version .79 or something like that. I'll check it when I get home.
As soon as he gets back from China I'll ask him what he did when started bootlooping. The phone might work for 30 seconds before going into reboot over and over so RUU might not work. But I can go into bootloader and into fastboot and was able to get a unbrick program to run and it seemed to be able to install another rom, but the rom it said it was installing was the same that was on the phone so maybe they needs S-off to function.

If you find your phone is rooted and can turn it on long enough to download an app from the market called Flash Image GUI, in the description it will say for the EVO 3d but it works on the og as well, you can also download off the devs xda thread just google (flash image GUI xda) and it should pop up, another thing make the file is on the root of your sd card and not in a sub folder. Good luck.
Sent from my PC36100 using xda premium

Oh and you can't flash custom roms with s on period, if it is on that's your problem there.
Sent from my PC36100 using xda premium

here it is
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
S-on
HBOOT-0.79.0000
MICROP-041f
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
Does this give any idea of what I can do.

Successful Root and Unlock HTC One M8 with VZW Lollipop

Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!

UPDATES?
i need this working bro, my m8 is pissing me off, king root wont work i followed all your instructions
also what version of kingroot did you have?
radiowavedev said:
Hey guys,
I have never posted a thread like this so please tell me if I have done anything wrong. I don't have enough time to write a proper guide but if someone wants to they are more then welcome. I take no credit for any of this information, I just took the risk and attempted an M7 root and unlock method on my M8. And it worked! But just a little differently. I followed the steps in this thread but with a few minor changes: http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Okay so basically instead of using the mobile app of Kingroot I used the desktop version and had a much higher success rate. Once I gained temporary root for the first time I ran sunshine and finished all of the compatibility tests. The phone will reboot and you will need to re-root. Once you've gained root again run sunshine. It'll only take a couple of minutes. It may crash. That's fine you should now be unlocked. This is as far as I have gotten do to time constraints and not knowing exactly what recovery to flash. If someone knows please let me know! As stated in the original thread this is super finicky but will work. Just have some patience.
Also, I didn't get official software status. In case that's a problem for anyone.
My Phone:
VZW HTC One M8 running lollipop 5.0.1
Ill try to clean this up when I get home from work but I just wanted it to be out there so everyone knows. I will remove this thread if someone posts a better one. Thanks!
Click to expand...
Click to collapse

I'll work on creating a step by step when I get home. I've just been really busy. It's just a lot of trial and error but it should work at some point. Keep a look out for my reply tonight.

xercurial said:
i need this working bro
Click to expand...
Click to collapse
Such a polite way of asking someone to go out of their way to help you or write a guide for you.

lol sorry about that man i did however end up rooting it , now im having trouble
redpoint73 said:
Such a polite way of asking someone to go out of their way to help you or write a guide for you.
Click to expand...
Click to collapse
i am having trouble iwth twrp

xercurial said:
i am having trouble iwth twrp
Click to expand...
Click to collapse
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?

twrp issues
redpoint73 said:
Is there a question you are intending to ask?
And you need to describe the "trouble" exactly and precisely.
What version TWRP?
Click to expand...
Click to collapse
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!

Alright, sorry that I lied about going home and typing up a step by step things are just hectic ya know? Anyways i'm here now so let me gather myself and get you some help. lol

xercurial said:
i have the one the ends with 7.0.1 i believe i cannot check right now, i am servicing it because i have to replace the jack and get a new housing which will take a coupe days to ship, i did however get root s off after trying for the longest time. my issue now is whenever i try to boot into the recovery, most of the time it will take me to stock or show the error triaangle which indicates there is none installed which there is (very frustrating) once in a blue moon however i will finally get into twrp and whenever i try to do a backup, it says failed or some kind of error. and EVERYTIME i try to reboot my system it would bootloop into recovery! and when that happens i would be forced to re install a rom and the whole proccess starts again. So i just stuck with the gpe rom basically and i tried to do a backup and the whole recovery issue just pissed me off so i just decided to to my hardware fix by replacing the frame and the headphone-charging port which ended up not being compatable with the verizon model so i had to re order (very frustrating) will probably by the at&t model at some point instead
anyways sorry for being rude earlier and thanks for your patience!
Click to expand...
Click to collapse
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure) then installed it through adb and it has been working flawlessly. I since installed ViperOne without any problems. The version of twrp I got was 2.8.7.0. Once you get your phone going again i'd suggest reinstalling twrp through adb.

xercurial said:
i have the one the ends with 7.0.1
Click to expand...
Click to collapse
As noted by the previous response, you should get the latest version of TWRP (2.8.7.0) if you are on Lollipop firmware. TWRP versions 2.7 are known to be problematic on LP.
---------- Post added at 11:32 AM ---------- Previous post was at 11:07 AM ----------
radiowavedev said:
If I remember correctly all I did was go to twrp's website and download the most recent version for the VZW M8 (I think it might have just been one for all versions not sure)
Click to expand...
Click to collapse
You're correct, TWRP for CDMA (Verizon, Sprint) and GSM versions (most other M8 versions) was merged some time ago.

Looking for help on Unlocking Bootloader and Running Resurrection Remixed on G-900V

Hi all,
I'm new to rooting and modifying my Verizon S5 - so I don't have the most technical knowledge of Android nor do I have a deep understanding of related jargon yet. Recently I was able to root my phone using jrkruse's method (http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370). I then wanted to flash a new ROM - Resurrection Remix MM in particular. Through some research this seemed the best to my needs.
I understood that to do so I needed to first unlock my bootlader. So to do so I followed GeTex's post at http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909. I followed Method 1. All was well until the step of installiong Bootloader_Unlock_Safestrap.apk to my phone. After doing that and installing safestrap again like the guide said, I went to reboot my phone into recovery mode, however, initially there was only a black screen. Then, a message told me that Safestrap was disabled and gave me the options of recovery or allowing to continue. Here is a photograph of the screen (found online, not my own imagehttp://img.wonderhowto.com/img/99/57/63530107864095/0/install-custom-recovery-new-rom-your-bootloader-locked-samsung-galaxy-s4.w1456.jpg) Tapping "recovery" brought me to Safestrap and tapping "continue" made the screen black again - no Samsung or Verizon load screen followed.
Thinking that maybe this was normal, and that I had to flash one of the safestrap bootloader unlocks, I flashed SafeStrap_PD1_Bootloader_Unlock_AIO.zip as the phone was in safestrap. After that, any way of starting up my phone showed me a small message in red at the top of my screen saying my kernel was bad or broken (sorry I don't know the message verbatim - I should, but it was a while ago and I was in a hurry to have a functioning phone ASAP for work and was immediately concerned with unbricking my phone rather) a warning sign (big triangle with a !) telling me to use VZW software repair.
If anyone can pick out specifically where I went wrong, that would be great. However, as I'm a noob and there's a lot of room for error, that may be easier said than done.
It would also be helpful if someone could tell me (or link me guides) how to set up Resurrection Remix (or any other great ROM you would recommend) on an S5 G-9000V.
Also, any general advice for a noobie looking to optimize his Android would be greatly appreciated.
Thanks! Love this community for how quickly and how well they help out people with troubles like this

Bumping this, looking for help.
Would love some tips, even if they're simple general direction on how to set up this rom.
Thanks all!

jd13 said:
Bumping this, looking for help.
Would love some tips, even if they're simple general direction on how to set up this rom.
Thanks all!
Click to expand...
Click to collapse
After you have unlocked your bootloader, you should just flash the new recovery (I use TWRP) using Odin software. Once TWRP recovery is installed, boot to TWRP recovery and flash RR RoM. Just follow the RR RoM thread and choose Verizon variance.
I don't use safestrap anymore once I were able to unlock my bootloader. Just make sure that your bootloader IS IN FACT UNLOCK, before you can flasH TWRP.

johnnybg00d said:
After you have unlocked your bootloader, you should just flash the new recovery (I use TWRP) using Odin software. Once TWRP recovery is installed, boot to TWRP recovery and flash RR RoM. Just follow the RR RoM thread and choose Verizon variance.
I don't use safestrap anymore once I were able to unlock my bootloader. Just make sure that your bootloader IS IN FACT UNLOCK, before you can flasH TWRP.
Click to expand...
Click to collapse
Thanks a lot for your help, but I just did some more research and found out that my eMMC was in fact Toshiba, while I had originally thought it was Samsung. Oh well! Guess I'll stick to TW based ROMs on my firmware. I was thinking of going with MOAR Lollipop.

Soft Brick - Sideload ADB OTA Signature Verification Fails

I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.

tcoursey said:
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
Click to expand...
Click to collapse
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

scrin378 said:
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Oh believe me my head hit the wall for sure! I got careless and wasn't thinking straight. No reason to lock the boot loader except it was on a list of steps to get back to stock..and I guess it was late! doh.
There are lot's of posts/videos I've seen that should allow what I'm trying to do with sideload adb but mine keeps getting a signature verification error. Each new full version of a release 7.0 8.0 etc..has the entire rom, images etc. So your suppose to be able to flash those even though they are OTA updates... *shrug*
It's a blur what I did exactly in some areas. I at one point may have tried to flash the set of Stock IMG files as well. But for sure now all I'm left with is a locked phone with who knows what on it! Stock recovery...some form of 7.0.0 that has NYC as letters...that I can find NOWHERE! on any official releases...
Prob trash, I really want that night back..lol.