• 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

You can restore the stock rooted nandroid you had, find the default settings location, and verify that everything works.

Is this happening on ARHD or Viper?
 
You can restore the stock rooted nandroid you had, find the default settings location, and verify that everything works.

Is this happening on ARHD or Viper?
Yeeeehaaaw! Figured it out! Thilly meeee! Where it says phone, right under carrier, , you put the name of your phone as it is in the phone itself, the way att shows its name. In my case, m8. Did that, saved, had my son call and bingo baby!
 
Last edited:
You can restore the stock rooted nandroid you had, find the default settings location, and verify that everything works.

Is this happening on ARHD or Viper?

On a final note, it worked once. So I went back into about phone, took THAT name, HTC One_M8, put it into APN field, saved exit ed. Rebooted, then had son call three times successfully. It could have been this same simple fix a phone ago with the ARHD Rom too, and I'll bet a dime to a dollar it was! But I digress.....
 
The good news....was able to receive calls......the bad news.....only for a short time. The demon is back. I reset apn settings to default.and prob still persists. On with art tech support.
 
Last edited:
1433181845336.jpg

1433181858966.jpg

1433181873225.jpg

(old screen shots but still...)

And then just write down the hboot version as it appears in the bootloader.
 
Have to do some running around, just got home, last night check engine light came on on Mercedes e320. Hope its a simple one. Been nursing it along as its got almost 275,000 miles on it. The phone worked a few times today, usually fight after a reboot. Then a few minutes later they go to vm. Strange. I think its on the money after doing default settings in APN. Itll come.. Just gotta keep at it. Wish someone else had the same problem and the fix! Otherwise maybe its just my karma. (JK) Not a believer of that, sorry.
 
Just driving by :)p) but wondering if viewing the logcat or kernel log might reveal something relevant to your issue, HS.

c:\> adb logcat > m8-logcat.txt

c:\> adb shell
$ su
# cat /proc/kmsg > /sdcard/m8-kernelmsgs.txt

If you can fire-up two Windows Command Prompt (DOS) windows at the same time (i.e., one for each of the above) and try to make calls, re-create the issue, etc. you might be able to catch something relevant or that pops-out during the misbehaving time...(I have no idea what you'd look for, but you might know it when you see it).

Dunno :).

Best of luck!
 
Just driving by :)p) but wondering if viewing the logcat or kernel log might reveal something relevant to your issue, HS.


If you can fire-up two Windows Command Prompt (DOS) windows at the same time (i.e., one for each of the above) and try to make calls, re-create the issue, etc. you might be able to catch something relevant or that pops-out during the misbehaving time...(I have no idea what you'd look for, but you might know it when you see it).

Dunno :).

Best of luck!

Check out "SysLog"

https://play.google.com/store/apps/details?id=com.tortel.syslog

That's the ticket for logs. ;) :)
 
Call AT&T customer service - request that they push a tower list update to your phone.

On Sprint phones we can control it through main settings, update, PRL update. Pretty sure that GSM operators call it something besides PRL, but either way - it's a tower list.

See also -

http://www.ehow.com/how_8240423_update-att-roaming-capabilities.html

If you can get calls in after dialing - and this comes and goes like from last night to this morning - it could easily be a tower / roaming connection issue that was invisible to you running stock.
 
I'll certainly give.that a shot. Kinda did that today with att customer service. I was at work. But yeah, when I get a chance I will try again.
 
Call AT&T customer service - request that they push a tower list update to your phone.

On Sprint phones we can control it through main settings, update, PRL update. Pretty sure that GSM operators call it something besides PRL, but either way - it's a tower list.

See also -

http://www.ehow.com/how_8240423_update-att-roaming-capabilities.html

If you can get calls in after dialing - and this comes and goes like from last night to this morning - it could easily be a tower / roaming connection issue that was invisible to you running stock.
Well then! Yesterday I got three texts from att saying my issue has been resolved. This am I had three coworkers try to call. Straight to vm. Sooooo I tinkered with apn settings again. This time under carrier I put tracphone. Saved, restarted, tried from my shop line, and it rang thru. Then a coworker, it rang thru, another coworker, it rang thru. Went back into settings and it shows ATT instead of tracphone. I'm going to keep checking it and see if it holds throughout the day. Maybe it just needed to be toggled off of att in carrier setting. Who the heck knows, but I'll take it! I'd post my # up here to take a test call from you but that's probably against the rules. Anyway, have a fine day! To be continued........
 
Back
Top Bottom