Develop Bugs

Help please...screen stuck at logo

Hello
My phone's screen is stuck at opening htc logo. I never rooted it - shall I just flash it with standard stock rom? Would you please be so kind to point me in the right direction? Bless...
My kindest regards
Pete

Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.

Teichopsia said:
Try booting without the sd card.
How old is the phone? What happened / did you do (if such is the case) for it to get like that? Etc.....
Sent from a dream.
Click to expand...
Click to collapse
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...

phosphen said:
Tried that before without result...also did a factory reset but to no avail. Phone was just over a year old when it happened, got it from my insurance policy so it's possibly a refurbished one. I can't remember doing anything to cause this...
Click to expand...
Click to collapse
You Need to provide the Cid number and the Main Version. Do You know how to Get that?

glevitan said:
You Need to provide the Cid number and the Main Version. Do You know how to Get that?
Click to expand...
Click to collapse
Sorry, no idea...

phosphen said:
Sorry, no idea...
Click to expand...
Click to collapse
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain

How old is your phone? Isn't there still any warranty? If so you may try to contact your reseller, service provider or the manufacturer. If not glevitan may be your hero

glevitan said:
Ok, enable USB debugging, plug the phone to the PC and then open a CMD ON the PC and type adb reboot-bootloader and once in bootloader type fastboot getvar all. You Need to post the INFOcidnum and INFOmain
Click to expand...
Click to collapse
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos

phosphen said:
Sorry mate, I was offline for a whole day, just managed to get back on it
How can I enable USB debugging if I can get onto HBOOT menu only? Is it possible to switch it on from there? Saludos
Click to expand...
Click to collapse
Yes, from fastboot, plug the phone (You will see fastboot USB in red) type: fastboot getvar all

sounds like a boot loop?
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.

rdub504 said:
try removing the battery, once you have done that re boot into boot loader from there you should see an option for recovery.you may want to do a full wipe and re flash the rom.:silly: keep in mind the initial flash normally will take the longest,best to leave it be for a few minutes while the phone adjust to the new settings,that sometimes will seem like you may have an issue, but patience most times is all that is needed.hope this helps.
Click to expand...
Click to collapse
It's not rooted, so I don't think that will work.

bananagranola said:
It's not rooted, so I don't think that will work.
Click to expand...
Click to collapse
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.

rdub504 said:
excellent point,but if that's true what is he flashing?
rooted phone=flash capable non rooted =stock rom with no admin access. am i mistaken,if so slap me and call me susan,if not box that thing up and bring it back,and if that's not an option then warranty time.because that device is chap.
Click to expand...
Click to collapse
Hello susan
Sent from a dream.

Teichopsia said:
Hello susan
Sent from a dream.
Click to expand...
Click to collapse
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.

rdub504 said:
LOL,I guess i'm susan and my face now hurt.can you please elaborate a bit so i can also understand what i am missing.
Click to expand...
Click to collapse
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.

Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse

Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).

Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Sent from a dream.
Click to expand...
Click to collapse
rdub504 said:
Teichopsia said:
Well....
1- over a year old bought refurbished.
2- he never rooted. We could assume that it is s-off from the previous owner but all of us failed to ask that question making another assumption that he isn't s-off.
3- he did a factory reset which didn't work (whatever that means with an s-on device / with an s-off device it really messes things up).
4- glevitan is here. If he doesn't know how to fix it (and from the few active members that tend to lend a hand in these type of posts) there may be just a handful who could help out. Hence, the OP is in good hands.
5- when someone messes up their phone without knowing what happened nor how to fix it, you need to give more detailed instructions on how to get it done.
6- I'm guessing that the info glevitan asked for is to find the correct ruu for the member to flash and to get his phone back to working conditions. If that doesn't work, chances are it's a hardware problem.
Bullet point,impressive. now a refurb with s off would mean a root from a previous owner?
"S-ON, which means it blocks you from flashing radio images — the code that manages your data, Wi-Fi and GPS connections. Switching your phone to S-OFF lets you flash new radios. Rooting doesn’t require S-OFF, but many rooting tools will give you S-OFF in addition to root access" So hince my question if attempting to flash a rom ,it would be a safe bet he would be rooted,because without it he would have no admin access,recovery or superser access and would not be able to complete the flash process.a factory reset would normally on a stock rom not result in a loss of the entire stock rom but only a loss off data i.e contacts apps etc. and with these things in mind it would seem to be a safe to assume its a hardware issue or a rooted refurb phone from a previous owner in a bootloop becauce a factory reset there would wipe everything?
Click to expand...
Click to collapse
Cfhappy said:
Factory reset resets the phone to it's "as fabricated"-condition, wich means it wipes user data and cache on the phone. With or without root the procedure is the same and should usally not affect /system or /boot.
So we have to find out, if the phone is S-On/S-Off (phosphen, more information on the topic can be read for example here, second post).
Click to expand...
Click to collapse
Sorry guys, but before hijacking this thread maybe you can go and follow the discussion in the off topic thread. The idea here is to lend a hand to someone that is stuck and a noob and this for certain not helping him. Let's keep it clean....
BTW, the only solution in his case is to flash the OEM RUU or make a goldcard and flash an unbranded rom. With no s-off there´s no other way.
Click to expand...
Click to collapse

I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.

Teichopsia said:
I couldn't resist.
Maybe it's good practice for him to read through all to learn to discern right info from wrong.
Sent from a dream.
Click to expand...
Click to collapse
Yeah, that is right, but with the phone stuck in the splash I don´t think is a good time to think about learning. This experience will definitely be worth for him in the future. :victory:

Latest update MHC19J how to flash twrp

So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).

What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.

HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.

You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492

Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]

HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930

wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.

HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe

wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!

Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.

HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.

Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!

Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.

Constant crashing

Hi all,
My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.

It might be worth mentioning it boots into extreme power saving mode too.

Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?

redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
Click to expand...
Click to collapse
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.

carljames0603 said:
It is stock. Tried to root it but it didn't take.
Click to expand...
Click to collapse
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.
Always provide as many details as possible when asking for help and answering our questions.
carljames0603 said:
Don't know which version as it is stuck in a loop currently.
Click to expand...
Click to collapse
If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).
From there, tell us what OS number it says on the bootloader screen, near the top.
carljames0603 said:
It seems to me this is a hardware problem though.
Click to expand...
Click to collapse
What makes you think that? You haven't provided any details or evidence that would support the statement.
Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.

When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.
The OS is 3.28.605.4

carljames0603 said:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process.
Click to expand...
Click to collapse
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?

redpoint73 said:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
Click to expand...
Click to collapse
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked, and it stays there until I push it to reboot.

carljames0603 said:
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked.
Click to expand...
Click to collapse
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
carljames0603 said:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Click to expand...
Click to collapse
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.

redpoint73 said:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
Click to expand...
Click to collapse
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
did you read the post you quoted ?
redpoint73 said clearly what you need and where to find
you used a different RUU and it will not accepted by your device ( in red above )

carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app.
Click to expand...
Click to collapse
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
carljames0603 said:
(RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).

redpoint73 said:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
Click to expand...
Click to collapse
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.

carljames0603 said:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
Click to expand...
Click to collapse
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.
Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your posts is not the same as attacking a person (which you did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).
You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.

[REQUEST] AT&T LG K20 (LG-M255) root method

This is my 4th LG phone but this is giving me problems even unlocking the bootloader. Any help would be appreciated.

Is this of any help?
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248

Professor Woland said:
Is this of any help?
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248
Click to expand...
Click to collapse
I wish. At&t has the bootloader locked down. All the other steps will probably work. Twrp would have to be built for M255. Thanks for the response.

So, you don't have "allow device to be OEM unlocked" option in developer options?

Professor Woland said:
So, you don't have "allow device to be OEM unlocked" option in developer options?
Click to expand...
Click to collapse
I do. Tried enabling, but still trying to get a grip on it.
Update: still can't enter fastboot mode. It just reboots like normal.

Can't I run the oem unlock command while in download mode?

mikefeFe said:
Can't I run the oem unlock command while in download mode?
Click to expand...
Click to collapse
No.

pvineeth97 said:
No.
Click to expand...
Click to collapse
Any way you know to unlock bootloader?

mikefeFe said:
Any way you know to unlock bootloader?
Click to expand...
Click to collapse
Maybe bootloader patching might work. Will look into it later.

pvineeth97 said:
Maybe bootloader patching might work. Will look into it later.
Click to expand...
Click to collapse
I appreciate your help. If you need anything from my phone, just let me know.

Did you ever have any success unlocking the phone?
I am trying to do the same thing and running into the same problems.

please help us!
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
hope someone with a kind hearted intellectual brain will make this happen ? please help us damn it

jamers14 said:
Did you ever have any success unlocking the phone?
I am trying to do the same thing and running into the same problems.
Click to expand...
Click to collapse
Nothing yet. I am waiting to hear something from @pvineeth97 on the issue. I'll contact him and see where we stand. ?

mikefeFe said:
Nothing yet. I am waiting to hear something from @pvineeth97 on the issue. I'll contact him and see where we stand.
Click to expand...
Click to collapse
You guys have Android 7.0?

pvineeth97 said:
You guys have Android 7.0?
Click to expand...
Click to collapse
Yep & thank you MikeFefe!

Did anyone ever find a solution to this?

diazi said:
Did anyone ever find a solution to this?
Click to expand...
Click to collapse
Not as of yet. Sorry.

Hey all, just got this phone, I had originally "done some research" when I was at the att store, and found root instructions for the lg k20 PLUS (missed that plus part). So I bought the phone and now im finding out there's currently no root method, which means, as usual, I have to at least try. I warn you, I'm no fulltime dev, so don't get too excited, im the kind of guy that still needs plenty of help with this stuff, but I'm setting up a dev environment and digging in.
My question right now is, has anyone been able to access the bootloader? I read thru the k20plus root topic a bit and they say to use
#adb reboot bootloader#
or hold VOLDOWN and plug usb while powered off.
Nothing seems to bring me to a bootloader.
#adb reboot bootloader#
reboots the device and I assume it tries to boot the bootloader and fails, because windows chirps as if it's been disconnected, then my device proceeds to boot up normally.
Holding VOLDOWN and plugging the usb makes the phone show a splash screen momentarily and then switch to the powered off charging screen.
Has anybody been able to access the bootloader?
-BMFC

Still waiting here too. ??

What u mean with "bootloader" are fastboot.
To get into download-mode hold Vol+ & plug-in usb
Fastboot may for u arivable but u have to wipe ur recovery partition first.
Then reboot into recovery...but wait !
It's look like freeze..plug-in usb and hit on ur PC "fastboot device"
Welcome !

Root Issue -- won't reboot into recovery mode

Hi --
Old Galaxy Tab Pro 10.1 running kitkat. I am using CF Auto Root to root it via Odin and I get the "pass" in Odin but then it just reboots into the existing OS and Supersu is not on the device. The instructions I have been following say that you should try again but switching off the "auto reboot" in odin. I did that, but it just remains in download mode. The instructions said to take out the battery...which, not really an option for the tablet.
I believe I followed all other instructions: I have the correct CF Auto Root file for my build; I have the drivers from Samsung ...
Any advice is appreciated.

tojotojo said:
Hi --
Old Galaxy Tab Pro 10.1
Click to expand...
Click to collapse
Which one?
tojotojo said:
running kitkat......
Click to expand...
Click to collapse
So you want to keep that?
If not why don't you flash TWRP and Lineage?

bmwdroid said:
Which one?
So you want to keep that?
If not why don't you flash TWRP and Lineage?
Click to expand...
Click to collapse
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.

tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.

tojotojo said:
Hi, and thanks for the reply. Big picture is that I'd like to use the tablet but kitkat obviously is now not compatible with most apps. So really just any reliable way to root so that I can make use of up-to-date/current apps. I can research TWRP and Lineage -- I'm guessing there's a how-to on here somewhere.
Tablet version: SM-t520.
Click to expand...
Click to collapse
I see.
Imo it's necessary 1st of all to make sure it's on latest stock to have latest bootloader.
Flashing TWRP with Odin is extremly easy.
Here is a post/thread although written for S4 valid for most others as well.
Written a how-to myself as well but the english part is not as up-to-date as the german is.

tojotojo said:
And , obviously, terminology may be/probably is "off" here (newbie and all) ... but I believe there's a step before being able to flash TWRP and Lineage - whether that's "rooting" or "unlocking" or whatever. I'm basically still "stock" at this point.
Click to expand...
Click to collapse
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.

bmwdroid said:
No unlocking necessary with that old device.
Rooting means having SU or Magisk but flashing works without as well.
Click to expand...
Click to collapse
Great, will give this a shot later today. Appreciate the help!

Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options. Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.

tojotojo said:
Well, didn't get very far. My understanding is that you have to unlock the OEM bootloader under developer options...which, ... well, I don't have that option listed once I've accessed the developer options.
Click to expand...
Click to collapse
As I said: not on this old device
tojotojo said:
Tried a bunch of options -- factory reset, changed date/time to long ago .... used Smart Switch to check for updates (which one post said would prompt it to appear. Any options for getting this modded without the OEM bootloader unlock option? One post somewhere said that having the USB debugging option checked would work, but .... questionable.
Click to expand...
Click to collapse
Just use Odin to flash latest TWRP,
Reboot to that TWRP,
Wipe everything plus "Format Data"
Flash suiting ROM and test if it works
reboot to TWRP and flash Gapps fitting this ROM version (I prefer Bitgapps ARM)
Be happy

@tojotojo remember that Odin can only flash .tar and .tar.md5 files
TWRP.....img are to flash later in an old TWRP to get a newer one.

you need check off auto-reboot. it still in dload-mode, then press power to reboot and just as you see it starts boot press recovery-mode key combination to enter recovery. if you are slow, tab will load default system without ur root and recovery. i hope this help you.