Database Info

[Q] engHboot Comet

Hey all, So I'm working on a T-mobile comet for the time being while I'm stuck with it. One of the things that I've noticed doesn't seem to exist is the Hboot menu. I've had it on every droid I've ever owned, but this one does not happen to be an HTC, so I'm not sure if maybe that's the reason why.
http://cloud.addictivetips.com/wp-content/uploads/2010/12/s-off.jpg
Is a picture of the menu I'm talking about and I'm just wondering. Is there a way to flash this on the comet?
I don't really see it as being essential to have as I could always just adb reboot recovery, but it'd be nice to have the option if I'm at work or something tinkering and something goes awry. Thanks

morgan5814 said:
Hey all, So I'm working on a T-mobile comet for the time being while I'm stuck with it. One of the things that I've noticed doesn't seem to exist is the Hboot menu. I've had it on every droid I've ever owned, but this one does not happen to be an HTC, so I'm not sure if maybe that's the reason why.
http://cloud.addictivetips.com/wp-content/uploads/2010/12/s-off.jpg
Is a picture of the menu I'm talking about and I'm just wondering. Is there a way to flash this on the comet?
I don't really see it as being essential to have as I could always just adb reboot recovery, but it'd be nice to have the option if I'm at work or something tinkering and something goes awry. Thanks
Click to expand...
Click to collapse
HBoot is an HTC-specific protocol/bootloader. That's why it's not on your Comet. What you mean to refer to, in general, is the bootloader screen. I'm not sure what the button combination is for your device, but a quick Google query should get you the answer

Product F(RED) said:
HBoot is an HTC-specific protocol/bootloader. That's why it's not on your Comet. What you mean to refer to, in general, is the bootloader screen. I'm not sure what the button combination is for your device, but a quick Google query should get you the answer
Click to expand...
Click to collapse
I thought that would probably be the answer. adb reboot recovery still stands as an alternative, just gotta be cautious if I'm toying around and not around a PC (Or not toy around at all. Ha! Yeah right) I did look up some on the bootloader for the comet. It's actually a frozen t-mobile startup screen. Why they would have that as a bootloader I haven't the slightest. Very inefficient and very confusing when attempting to reach a real bootloader at first. Plus side is it's a Comet, so if I break it. Well. Like I said; It's a Comet, Still in the process of debating wether to replace the digitizer and upper portion of my Glacier or just buy a new phone. (Digitizer strand ripped on the Glacier some so not really functional and the power and volume buttons are essentially shot. More effective to just buy a new phone, but I love my Glacier lol)

DO NOT download the 4.4.4 update in the UK

:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.

Moto G will not power up
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
Source: https://forums.motorola.com/posts/3d5eadc25d

Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked
Click to expand...
Click to collapse
If the bootloader has mysteriously become unlocked, then clearly you did modify the phone and they are entitled to decline a refund. This is made perfectly clear when the procedure to unlock is executed.

That's why you should be careful of anything you do with the phone once the bootloader is unlocked.

Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: http://fsfe.org/freesoftware/legal/flashingdevices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners

TechMinerUK said:
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: ht tp:// f sfe.org/f reesoftw are/legal/flash ingdev ices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners
Click to expand...
Click to collapse
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:

Broken_motoG said:
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
No problem, I checked on it before I installed CM on my Moto G last week
Hope I could help and good luck with the phone

Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?

startersorders said:
Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?
Click to expand...
Click to collapse
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion

OP needs to establish if he has simply not encountered the ''Moto G won't turn on' issue. I included instructions above. It could all be just bad timing.

Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.

dethrat said:
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.
Click to expand...
Click to collapse
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.

neu - smurph said:
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.
Click to expand...
Click to collapse
It depends, my friend who has a Moto G update to 4.4.4 lost all functionality of his apps and his clock stopped working. It just depends as his phone wasn't rooted with no bootloader unlock

TechMinerUK said:
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion
Click to expand...
Click to collapse
Of course a bricked phone is useless, but something obviously went wrong with the OP's phone, and its probably a coincidence that it happened while updating. It's the absurdity of the comments "DO NOT download the 4.4.4 update" and "4.4.4 is a downgrade" that got me to post, because its pretty clear that many people have updated without any issue.
Not besmirching the OP's problem, and like I said, I wish him well in getting his phone working.
Also, depending how old the phone is and where you bought it from, isn't it an option just to return it to the seller for an exchange. Just tell them it stopped working and you want a replacement phone?

[Q] Power Button instant pressed

Hey Guys, today my N5 suddenly switched off and since then it refuses to boot further than the bootloader. I got it to boot one time (it turned off some seconds later) and it seems to be the Power button (when unlocking the screen it asks me if I want to turn off the phone). I still have warranty so I want to send it back to Google. My problem is that the device is unlocked. Is there any way to lock the bootloader before sending it back? I bought it from the German Play store, does anybody have experience about reclaiming unlocked phones there?
Thank you in advance!

Google does not require you to have a locked bootloader. Only LG does

and anyways, its very easy to lock a bootlooder, either type fastbboot oem lock via fastboot, or by an app if you still have root.

rootSU said:
Google does not require you to have a locked bootloader. Only LG does
Click to expand...
Click to collapse
I know the American Play Store doesn't require to be locked, thats why I asked for some experience from the German one.
simms22 said:
and anyways, its very easy to lock a bootlooder, either type fastbboot oem lock via fastboot, or by an app if you still have root.
Click to expand...
Click to collapse
So how do I lock the bootloader if the device shuts down like 3 seconds after showing the Google logo? The button seems not to be released, so the device always gets forced off. No matter where I am. Sorry if I didn't explain that clearly, for me it was obvious.

Its nothing to do with American or German or UK for me. Its to do with Google and I've already answered

rootSU said:
Its nothing to do with American or German or UK for me. Its to do with Google and I've already answered
Click to expand...
Click to collapse
Ok thank you. I simply asked to be shure.

System Update

Prompted to install a system update today. I hesitate as hopeful to obtain at least root if not bootloader unlock and don't want an update to stand in the way of that (eventual) process. Any thoughts on this 5/10/16 update from developers and any recommendation on whether it's harmless or perhaps that we should hold off... Thank you.

I would like to know the same
Sent from my VS987 using Tapatalk

Its harmless because its an official update.

I looked it up and it said it is to improve the interface for visual voice mail, some changes to how you can enter airplane mode so you won't do it by accident, and allow display of data from the active exchange server, whatever that is. Nothing about security, but I would be skeptical. You never know what they might sneak into the update. It didn't sound like any big improvements so I didn't take it.

igomoto said:
Prompted to install a system update today. I hesitate as hopeful to obtain at least root if not bootloader unlock and don't want an update to stand in the way of that (eventual) process. Any thoughts on this 5/10/16 update from developers and any recommendation on whether it's harmless or perhaps that we should hold off... Thank you.
Click to expand...
Click to collapse
There's no reason not to take it.
I bought my G5 with the idea that the phone will NEVER be rooted or have an unlocked bootloader. Why? Because LG doesn't sell as well as Samsung or HTC or... and therefore has fewer developers working on unlocking/rooting and it's a very new phone, most newer phones have figured out how to permanently lock the bootloader and prevent rooting.
I certainly hope I'm wrong about this but.... :crying:
My Thunderbolt, Galaxy S3, Galaxy S4, M8 were bootloader unlocked, rooted and running TWRP and custom ROMs within an hour of getting them home so I had to think long and hard about buying a phone that I believe will never be unlocked or rooted but LG has nothing as horrible as TouchWiz or Sense and Nova Launcher make the phone suit my needs.
FWIW, I took the update yesterday and will take all future updates.

igomoto said:
Prompted to install a system update today. I hesitate as hopeful to obtain at least root if not bootloader unlock and don't want an update to stand in the way of that (eventual) process. Any thoughts on this 5/10/16 update from developers and any recommendation on whether it's harmless or perhaps that we should hold off... Thank you.
Click to expand...
Click to collapse
Hopefully @autoprime can take a look at it for us sometime and let us know the rollback situation with the new update. Until he lets me know its safe, I generally stay away!

Coycaine said:
Hopefully @autoprime can take a look at it for us sometime and let us know the rollback situation with the new update. Until he lets me know its safe, I generally stay away!
Click to expand...
Click to collapse
12A KDZ is out.
You can download it HERE. And as always.. I try to add all KDZ's to http://bit.ly/lgkdzlist
12A does not pop a version fuse... so there should be no issues going back to 11A from 12A as far as I can tell. :good:

I experienced issues after the update that were not there prior to its installation. Double tap to wake became hit or miss, although double tap to sleep worked just fine. And the power button became glitchy as well. On several occasions I couldn't wake the phone with either method and attempted a long press of the power button in order to shut the phone down which would not work. All this after only having had the phone less than 24 hours. Needless to say it went back and a replacement was obtained.
Thus far no problems with the new device but I have yet to install the system update (12A) which has downloaded and is pestering me to run.

jamesava said:
Its harmless because its an official update.
Click to expand...
Click to collapse
Is this your first android phone or something? :laugh:
No, but seriously, Verizon sends out updates that f*ck things up all the time. Marshmallow ruined my G4 and lollipop ruined my S4. Plus, each update you take makes your chances of getting root that much slimmer, because if a dev has been working to root a phone for X amount of months, they've only been trying it with the software at the beginning of those X amount of months. A security patch could make root impossible until further dev work is done.
---------- Post added at 11:53 PM ---------- Previous post was at 11:53 PM ----------
rapperman said:
I experienced issues after the update that were not there prior to its installation. Double tap to wake became hit or miss, although double tap to sleep worked just fine. And the power button became glitchy as well. On several occasions I couldn't wake the phone with either method and attempted a long press of the power button in order to shut the phone down which would not work. All this after only having had the phone less than 24 hours. Needless to say it went back and a replacement was obtained.
Thus far no problems with the new device but I have yet to install the system update (12A) which has downloaded and is pestering me to run.
Click to expand...
Click to collapse
In regards to your power button issue, have you noticed that your phone is slower to wake when you have just locked it? If I shut my screen off and quickly flip it back on, there's a good 3+ second delay. Otherwise, doubletap to unlock and finger print to unlock are both pretty much instant if I count a good 2-3 "Mississippi"s ;P

ryanpm40 said:
In regards to your power button issue, have you noticed that your phone is slower to wake when you have just locked it? If I shut my screen off and quickly flip it back on, there's a good 3+ second delay. Otherwise, doubletap to unlock and finger print to unlock are both pretty much instant if I count a good 2-3 "Mississippi"s ;P
Click to expand...
Click to collapse
With this G5 I've not experienced the issue you've described, or any of the other issues that plagued the first one I purchased. I've even installed the 12A update which I believed were responsible for the "doubletap" issues. There's no doubt in my mind now that the first device was defective.
The only problem I am experiencing at this point is this nagging sensation that I should give the HTC 10 a comparative look before the end of my 14 day evaluation period lol.

Please Help Me!!
autoprime said:
12A KDZ is out.
You can download it HERE. And as always.. I try to add all KDZ's to http://bit.ly/lgkdzlist
12A does not pop a version fuse... so there should be no issues going back to 11A from 12A as far as I can tell. :good:
Click to expand...
Click to collapse
Hello Good Day,how can i install the kdz file????,im a noob in this and i cant find how to do it,i search and i found that i need the program Lg Up and others files,but i was unable to find the right ones......
can you guide me???,please....
My Cellphone is recognized as a Lg g4 by the program VZW Software Upgrade Assistant.......
and i tell this because it show me that is an update but is VS98624C.........:silly::silly::silly:

rapperman said:
I experienced issues after the update that were not there prior to its installation. Double tap to wake became hit or miss, although double tap to sleep worked just fine. And the power button became glitchy as well. On several occasions I couldn't wake the phone with either method and attempted a long press of the power button in order to shut the phone down which would not work. All this after only having had the phone less than 24 hours. Needless to say it went back and a replacement was obtained.
Thus far no problems with the new device but I have yet to install the system update (12A) which has downloaded and is pestering me to run.
Click to expand...
Click to collapse
I cleared the update by booting to the bootloader and wiping cache. It rebooted and then I cleared away the unsuccessful update message. Then using adb, I run the short command that @autoprime posted in his topic for all things LG G5. It hides the system update and I haven't got the prompt since.
Sent from my VS987 using Tapatalk

[Need for help] Is there any way to remove bootloader unlocked screen?

This question has bothered me for a long time. As you guys know, when the bootloader is unlocked, everytime when you boot the device, the warning screen will show up
That screen is quite annoying...
Therefore I use a lot of time searching on Google, many people said it is impossible to remove it...
However, I saw them successfully replaced it on Moto and LG V20 (V20 Guide XDA link)
or something like this V30 Discuss XDA thread
I think maybe we can use the HEX tool to replace the warning screen with original logo sceen...?
But unfortunately, I'm not a developer and still couldn't find out the solution...
Can anyone please help research in how to remove or replaced that annoying screen...? Really appreciate!

UP. I'm also interested to know if it's possible.

AFAIK, there's no way around it. Think of it as a badge of honor.

I hear there's meds that will take away the pain.

Hitting the resume button makes the warning screen go away quicker.

swieder711 said:
Hitting the resume button makes the warning screen go away quicker.
Click to expand...
Click to collapse
Yeah but that's still quite annoying... So I'm thinking if there's a way to get rid of that

MyStyle0714 said:
Yeah but that's still quite annoying... So I'm thinking if there's a way to get rid of that
Click to expand...
Click to collapse
First for a little background on unlocked bootloader warnings. It used to be that the actual graphics files for the initial splash screen were located in their own partition and after you unlocked the bootloader you could flash a new image to that partition of any correctly formated graphic file to display whatever you wanted. Starting with the original Pixels Google moved them into the bootloader itself and I am not aware of any Dev that has or is willing to experiment with altering the bootloader since any error in doing so will hard brick the phone.

Why does it bother you so much? Its not like you need to hide it from the FBI. You should be PROUD...