• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root M8 flashed firmware in cmd, now stuck in HBOOT

HunterSeeker

HunterSeeker

Well-Known Member
This is my first post so I will try to do it as good as I can. I wanted to get away from all the undeletable bloat ware to give my battery more life so I flashed over to the Revo HD ver 34 something. It worked great and I used it for about a week and a half. All the while incoming calls were straight to voicemail. I didnt realize this til a few days passed. So I set about to find a solution. Spent a few hours on with at&t, even went to their service center and tried a new sim. Same result. She put a demo sim in to check the hdwe. and it was fine, able to receive calls normally. So they (att) said they would try to figure out if it was in their system and get back to me. That ship sailed. I joined xda dev forum and was advised to try firmware. And/or a stock rom. Well I thought I had the right firmware matched to my cid number 001. Shoulda been 401 firmware right? Well that's what I surmised anyway given the rom I was using was put up by the same guy. I searched how to flash firmware, downloaded, and renamed it firmware.zip like the guy on youtube and another forum said. First mistake right there. I tried several times and over and over cmd said cannot load. Reason? It was already a .zip file. So the guy on youtube that says "rename it firmware.zip" should have said make it simple and rename it firmware. I saw another forum member gnashing his teeth about this same thing, explaining the commands to some poor guy who was having the same problem I was with failure to load. What messed it up is cmd saw the file as firmware.zip.zip and got twitterpated. I figured that out on my own. Backed off the .zip on the firmware file in fastboot and bingo firmware flashed. BUT IT WAS NOT THE RIGHT ONE FOR ME!!!!!

So my phone slept on the floor on life support and stayed home from work today too. I was afraid to leave it all night without being on a charger because its mostly white screen and that's gotta drain a battery. I took pics of all I can get it to do, and of what my fastboot folder looks like to give as much info as I can. Also, one of my boys just bought an M8 on ebay. It"ll be here shortly. Was thinking it might give a transfusion. I'll finish up with this. I was up very late last night searching for answers and came across a forum post where one man was helping another get through a tough patch. The man helping sounds like a superhero the way he handles his words and calmly and with great resolve, gets the sick phones messed up by boneheads like me, up and running agaiin DSC05373.JPG
DSC05374.JPG
. Very intelligent and tech savvy. Well that man is here. And that's why I joined, because if anyone can bring my M8 back from its zombie state it is HIM! You KNOW who I mean........ Earlymon! King of the M8 Army!DSC05371.JPG DSC05372.JPG Sorry about the scattered pics. HELLLLLLP!!!!!!DSC05373.JPG
 
HunterSeeker said:
This is my first post so I will try to do it as good as I can. I wanted to get away from all the undeletable bloat ware to give my battery more life so I flashed over to the Revo HD ver 34 something. It worked great and I used it for about a week and a half. All the while incoming calls were straight to voicemail. I didnt realize this til a few days passed. So I set about to find a solution. Spent a few hours on with at&t, even went to their service center and tried a new sim. Same result. She put a demo sim in to check the hdwe. and it was fine, able to receive calls normally. So they (att) said they would try to figure out if it was in their system and get back to me. That ship sailed. I joined xda dev forum and was advised to try firmware. And/or a stock rom. Well I thought I had the right firmware matched to my cid number 001. Shoulda been 401 firmware right? Well that's what I surmised anyway given the rom I was using was put up by the same guy. I searched how to flash firmware, downloaded, and renamed it firmware.zip like the guy on youtube and another forum said. First mistake right there. I tried several times and over and over cmd said cannot load. Reason? It was already a .zip file. So the guy on youtube that says "rename it firmware.zip" should have said make it simple and rename it firmware. I saw another forum member gnashing his teeth about this same thing, explaining the commands to some poor guy who was having the same problem I was with failure to load. What messed it up is cmd saw the file as firmware.zip.zip and got twitterpated. I figured that out on my own. Backed off the .zip on the firmware file in fastboot and bingo firmware flashed. BUT IT WAS NOT THE RIGHT ONE FOR ME!!!!!

So my phone slept on the floor on life support and stayed home from work today too. I was afraid to leave it all night without being on a charger because its mostly white screen and that's gotta drain a battery. I took pics of all I can get it to do, and of what my fastboot folder looks like to give as much info as I can. Also, one of my boys just bought an M8 on ebay. It"ll be here shortly. Was thinking it might give a transfusion. I'll finish up with this. I was up very late last night searching for answers and came across a forum post where one man was helping another get through a tough patch. The man helping sounds like a superhero the way he handles his words and calmly and with great resolve, gets the sick phones messed up by boneheads like me, up and running agaiinView attachment 83538 View attachment 83539 . Very intelligent and tech savvy. Well that man is here. And that's why I joined, because if anyone can bring my M8 back from its zombie state it is HIM! You KNOW who I mean........ Earlymon! King of the M8 Army!View attachment 83536 View attachment 83537 Sorry about the scattered pics. HELLLLLLP!!!!!!View attachment 83538
Click to expand...

I'm at work til 3 pst. If anyone can post some steps to take I will print em off and try em whin I get home. I think I was able to flash twrp img last night but not 100% sure it got in. I saw the post by the guy who had a similar problem and installed the minisdk. Opened cmd in the folder and tried twrp in thru .img. I also found a utility to flash in that would relock , unlock, or lock. It wouldnt load as I recall. Im probably trying to do too many things. I dont know. But its sure different not having my communicater on me. One thing I noticed when rebooting in HBOOT....it shows the screen with recovery in the list for a brief moment but it goes by. Cant get to it. But it seems to be there. I am confident that I will get through this somehow and keep on lovin this phone, but for now it's in a coma. If only the ROMs were put up with the firmwares that worked.... The 401 firmware was supposed to be for my phone but somebody posted that 401 was euro not US. He said US is 501. Geeeesh! Someone needs to make a CLEAR list of this so boneheads like me dont get tripped up. Im sure thats already been done. I just have not found it apparently.

I hope to get a firm grasp on this hobby as I have built and loaded many pc's and understand that hobby quite well. Could someone use the info I provided up above and help me get runnin again? I'll make it worth your while! Thanks!
 
Ok, my friend, I am on the case. :)

The bad news - I'm going to need time to digest all of this, and likely cannot respond until later tonight - and if you're not around, or I can't make it back, we can tackle it in the morning, yes?

Meanwhile -

Don't install any toolkits besides what you already have.

Leave the situation as-is so I have a good picture when we start together.

The pics you posted look great, thank you.

We can get you sorted.

We will get you sorted.

Don't panic. ;) :)
 
I may ask a question or two as I get the chance.

Like I say, I'm in and out tonight, so don't think I abandoned you - I'm not going to be here in real-time right away ok.

First question - you unlocked this yourself using HTCdev.com - yes or no?

Don't worry about the recovery being there or disappearing during boot up.

Don't panic.

Don't experiment - nothing personal, it's just the right way ok.

I don't see anything yet to panic about.
 
0P6B10000
cidnum: HTC__001
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__E11
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__J15
cidnum: HTC__016
cidnum: HTC__M27
cidnum: HTC__K18
cidnum: HTC__A48
cidnum: HTC__002
mainver: 1.54.401.10
btype:1
aareport:1
hbootpreupdate:12

I believe it was OP6BIMG that I used to flash firmware. I deduced that my cid was 001 and I thought that was the proper version to use. It was on 3-4-15 that I flashed the firmware. But I don't remember the links. I took it in last saturday to the att store in a mall, they took it in the back room and came out with it vibrating on black screen with red text. Then I took it to att service center. On the way there I had one of my kids hold all three buttonns down to see what would happen, and it stopeed vibrating. I think we even got it to power off. Att service center looked at it and decided to send me a new one. Got it today. Do you think I should worry about resetting the Relocked and software Modified banners in HBOOT? Or should we try reviving it? You're the expert.
 
At the moment I wouldn't try and do anything else. Good going if you managed to get a free replacement though. After whatever AT&Y did can you still get into boatloader? If so the phone can probably still be sorted out.

As you now know that file you downloaded isn't correct for your phone. The zip file and the cids listed are basically for unbranded European phones.

You need to dig up a RUU specific to AT&T and your firmware version. I'm not familiar with AT&T cid no., but sure EarlyMon will be along again.
 
Yes it can display boot loader still. As well as power down. I think there is still a good chance it can be reloaded but I don't know the web commands to do it nor do I know how or where to get the proper (reliable) RUU or .zip or .img to use on it. I was able to figure out the cid # and the other one that goes with it. I'm at work right now and not firing on all 12. Anyway I thought I had the right firmware but didn't. The Revolution HD Rom I loaded did work great but calls in went to voicemail. Ver 34 something.
 
i have a folder called M8 full on my desktop. i think i just copied the folder windows sees when you plug in usb. "open folder to view files"
 
maybe i did...theres an iso openrecovery-twrp-2.8.4.0-m8 in a folder with adb ...an RUU_M8_K444_SENSE60_ATT_MR_Cin...

the original unlock code....a SuperSU folder...a Data folder
 
Sprint wouldn't care - once their service makes a determination, that's the end of it.

AT&T could be the same way, but you never know.

So, unlike other versions, the AT&T RUUs (as well as the Euro ones we could try to fool) all require s-off.

Getting the bootloader markings changed - also requires s-off.

Latest TWRP, put in same folder as fastboot that you showed above.

http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.5.0-m8.img

EDIT - I see you have the 2.8.4 version - great - put that into the Android Fastboot folder.

When you first unlocked your bootloader, you got an unlock token file from HTC. Put that into your Android Fastboot folder.

If you don't have one, follow the procedure at http://HTCdev.com - then put it there from your email.

Put your phone into FASTBOOT USB mode as shown by the second picture in your first post. Open a command window to the fastboot folder.

If not sure how, in Windows Explorer, Program Files - shift+right click on Android Fastboot folder and choose to Open a command window here.

Then say:

fastboot flash unlocktoken Unlock_code.bin

If successful, your bootloader will be unlocked, so let's try to restore TWRP -

EDIT - see notes here -

fastboot flash recovery openrecovery-twrp-2.8.5.0-m8.img

EDIT - because 2.8.4 is just as good, if you moved that over, instead say -

fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.img

If successful, it will say some bytes (give or take 16k or so) and then OKAY.

From there, on your phone, use the volume keys to go up/down, choose HBOOT, tap power to select, then choose Recovery, tap power to select.

If not successful, no big deal yet - power off phone, power on while holding volume down, see if TWRP is available.

Let's stop there and please say if that works.
 
You must log in or register to reply here.
Back
Top Bottom