• 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 said:
Im striking out
Click to expand...
Well, you wanted to occlude the tampered banner.

It's not as planned but it sounds like that's accomplished.

Besides - their techs have already seen it, logged it as broken (it was hosed before) and they have provided the replacement.

Not the way either of us wanted to go, but unless you want to try more stuff, it's meeting the objective for return.

Your call, let me know.
 
Your other alternative is try the RUU again, and this time go to recovery when asked.

EDIT - ok, understand.

Let me know if you change your mind or if you want to move on to rooting the other one.
 
adb
Now its showing a charging battery icon every restart instead of the white screen. I hope they just move it along back at the facility
 
HunterSeeker said:
adb
Now its showing a charging battery icon every restart instead of the white screen. I hope they just move it along back at the facility
Click to expand...
I'm sure they will.

The techs reported it broken and good for a replacement. They've already done the initial checks.

It's showing up in worse shape than before and if anything, confusing observables.

I don't think that they're going to waste a lot of time on it and I don't think that you have to worry about fraud.

The first techs had to have recognized exactly what state it was in when they authorized it.

You took it to them because you couldn't receive calls, even with their sim.

Everything else came later, including resurrecting the phone and still not being able to receive calls.

A running phone, on a well known rom, that just stops receiving calls and it's not the sim - is broken.

And the more I think about it, I frankly doubt that the right firmware update would have cured it - it simply would have allowed more updates.
 
If youre ever in command prompt type in adb devicees and watch what pops up. Maybe youve seen it beforre maybe not. Maybe yyou can use it idk.
 
I generally use Linux, sometimes a Mac and only rarely Windows, so I probably don't see the exact same message...

Unless you mean the security authorization, that's normal...
 
I get this -

Code: 
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
(serial number removed @ forum)    device

$ adb reboot recovery
$ adb devices
List of devices attached
(serial number removed @ forum)    recovery
 
EarlyMon said:
I get this -

Code: 
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
(serial number removed @ forum)    device

$ adb reboot recovery
$ adb devices
List of devices attached
(serial number removed @ forum)    recovery
Click to expand...

Yeah its windows. I can send screen shots if you want when I get back home.
 
HunterSeeker said:
Yeah its windows. I can send screen shots if you want when I get back home.
Click to expand...
Wait, I may have misread your intention -

You mean if you say -

adb devicees

Yeah, any command that it doesn't understand will give you the help text, as will -

adb help

It then shows the full command syntax.

Is that what you meant?

Yeah, if not, a screen shot would be great. :)
 
Oh then that must have been it because it pretty much goes through the abd command gamut. Ever since the fiasco with the first phone, Im leery about doing the same thing with this one. Im wondering if a lot of other AT&T M8 users have had the same dumb luck or if it was a fluke. Id really like to get rid of bloatware, get longer battery life, enjoy the hk feature, and enjoy the cool factor, but Ive already paid $600 for the first M8, and I doubt if theyll give me a third one. Maybe there's a place in the forum just FOR AT&T M8 users that have had success? If it werent for that damned straight to voicemails thing I wouldnt be so leery. What say you?
 
EarlyMon said:
Wait, I may have misread your intention -

You mean if you say -

adb devicees

Yeah, any command that it doesn't understand will give you the help text, as will -

adb help

It then shows the full command syntax.

Is that what you meant?

Yeah, if not, a screen shot would be great. :)
Click to expand...

Hey EarlyMon I have an idea.........how about creating a thread specifically for AT&T M8 users who have had total success and everything works? And in their posts give detailed steps as to how they got that success? Is there already such a thread? It seems like just a bunch of people trying for it but rarely achieving it. Maybe thats a dumb question and I just need to learn how to better navigate the site? I sure would like to try out your hk work. It just looks like a risky proposition.
 
The problems are that traffic is lower because the M9 is about to release, people rarely visit later to say they succeeded and it's not true that the AT&T version the hardest to root properly - the Verizon one is by a long shot, the AT&T is in second place.

During release, we had a lot of AT&T success.

Of the trouble threads that you see here for well over the last month, how many are - I rooted my phone following a guide from somewhere else and now there's a problem - vs - please help me get this right the first time?

I certainly wouldn't discourage you from starting such a thread, you can even make up a poll and cover as many combinations or as few as you like.

I'd like to know myself. :)

I'll be interested to see who or how many come back to share success stories.

There are a lot more of them than you might expect. :)
 
Please im dealing with the issue here, ive done all that you said but when i press enter on the commend prompt to send the code it says code cannot be send. i have the driver installed but my laptop is not able to read my phone please help!!
 
You must log in or register to reply here.
Back
Top Bottom