Rooting issues with Kingroot destktop - Verizon HTC One (M8)

Hello,
I was following this guide http://forum.xda-developers.com/showpost.php?p=61920423&postcount=3652, obtained root and could not install the superSU apk included nor could I obtain the binaries needed for the play store version of the superSU app.
After having more issues with the Kingroot app I decided to try the desktop version and around 50iss % it forced my phone into an unknown state (all physical buttons not working, screen permanently off). The phone was still connected to my computer and debugging was still on. Knowing that kingroot would need to use adb I tried to use the adb in the king root folder since the rsa keys would have already been accepted on the device, but it turns out the device was unauthorized and I could not get it to reboot through a shell.
Any suggestions other than letting the battery die and seeing what happens when I reboot?
Thanks

No need to wait for a battery drain. Holding power + volume up for many seconds will force a reboot. As soon as it turns off, if you switch to volume down it will boot into the bootloader but your timing has to be right for the volume down switch.

Related

Cannot boot after Supersu 2.82 binary

I'm in big trouble and need help.
This is a rooted Nexus 5 running stock 5.1.1 The SuperSu version was 2.79. Everytime I updated to the latest SuperSU (2.82) from Google play I would get boot problems - specifically that the reboot would "optimize" all apps each time making my reboot take about 30 minutes. I would recover by rebooting into twrp recovery and restoring a previous nandroid.
After waiting a week for the SuperSu developers to fix their problem I tried the update again. Same result. As the app optimizations restarted, I impatiently pressed and held the power button to restart the boot but into Recovery. The optimizations stopped, the display turned off but the phone did not reboot. All attempts to reboot by holding down the power button have since failed no matter how long I hold the button down, with or without the volume down lever.
So I have a phone that is dead and will not reboot. How do I get out of this problem? My laptop has adb installed but I don't know if that will connect with the phone powered off.
Please help. Thanks.
OK. After holding the power button down forever, the phone finally rebooted.
Phew! Don't know why it decided to do so, but glad it did! Maybe it was scared of your expertise.......

[Resolved] [HELP] Phone not reacting, power button broken

Hi,
I have a problem with my Motorola Moto G4. I bought it 2 months ago and unfortunately the power button broke and I am therefore not able to turn my phone on/off. That is in general not a problem since the device is still under warranty and I will get the phone repaired. The problem is that I want to backup my data, which I am not able to, before getting the device repaired since the workshop will reset the phone.
I am still able to unlock the phone but no apps or windows can be opened (taping on an app icon does not do anything). Dragging down the notification bar is possible and if connected via USB I can still see the status, unfortunately I am not able to change the setting from charging only to data connection. Since the power button is broken I am not able to reboot the device. I tried to use the adb tools to reboot but the device is not authorized and I would need to change that on the phone which I am not able to. Is there any way to reboot the phone or to access the data.
Any help would be really appreciated.
you might be able to try the commands for adb reboot recovery as the phone is booting up - iv never tried it but adb should be working after the moto splash screen (during the boot animation)
Im not sure if it needs authorisation during that stage but if you cant get into recovery and you cant change the usb connection/authorise adb then I cant see any other way to get the data off
TheFixItMan said:
you might be able to try the commands for adb reboot recovery as the phone is booting up - iv never tried it but adb should be working after the moto splash screen (during the boot animation)
Im not sure if it needs authorisation during that stage but if you cant get into recovery and you cant change the usb connection/authorise adb then I cant see any other way to get the data off
Click to expand...
Click to collapse
I am not really sure how to follow your advice since I am not able to shut down / reboot the phone (power button is not working).
Nem1c said:
I am not really sure how to follow your advice since I am not able to shut down / reboot the phone (power button is not working).
Click to expand...
Click to collapse
In that case I don't see how you can access anything if you have no adb & you can't select anything on the phone
TheFixItMan said:
In that case I don't see how you can access anything if you have no adb & you can't select anything on the phone
Click to expand...
Click to collapse
If I would drain the battery to "shut down" the phone, would there be a way to turn the phone on without the power button?
Nem1c said:
If I would drain the battery to "shut down" the phone, would there be a way to turn the phone on without the power button?
Click to expand...
Click to collapse
with older samsung devices you could use a usb jig to get into download mode without the power button (its a usb cable with some pins crossed you can buy them for only £1 off amazon/ebay)
even if it did work you would still need the power button to select the option to restart phone so the answer is nothing that I can think of
TheFixItMan said:
with older samsung devices you could use a usb jig to get into download mode without the power button (its a usb cable with some pins crossed you can buy them for only £1 off amazon/ebay)
even if it did work you would still need the power button to select the option to restart phone so the answer is nothing that I can think of
Click to expand...
Click to collapse
I found some mechanisms to get the phone turned on and I will try them out. I guess I have nothing to lose.
The interesting thing is that my phone is still receiving messages and news (I see them in the notification bar), so things like that are still working but unfortunately new "widows" can't be opened.
Thank you for your help.
I was able to get the phone rebooted and after the restart everything works as it should.
This is what I did:
Drain the battery (using the flash light), once the battery is flat connect the phone to the PC
Press and hold the volume down button until the Fastboot menu appears
Download ADB tools (the minimal version with adb and fastboot is sufficient)
Install the Motorola driver on the PC (I was not aware that I need this, since connecting the phone without the driver being installed and running adb device results in the device being shown)
run fastboot reboot

Bootloop after device got dipped in water -> Volume down button is messing around

Hey folks,
unfortunatly I am not able to boot my device properly since it fell into the bath tub. It boots into the download mode and stops after 5% saying Software install failed! That's because there is no .IMG on the SD Card I guess. Not sure what to do, I searched for a stock rom .IMG and put it on SDCARD/dload and got a good feeling that, maybe, it'll boot normally after installing this "update". So it boots into download mode and the update process is working just fine, but after the update successfully ends with 100% it reboots and starts the procedure over and over again.
I tried different button combinations to avoid booting the download modus - without success. I tried to get adb access by connecting it to the computer but just got an unauthorizised device - I never enabled usb debugging -.-
But then, somehow, it booted into safety mode and I was able to enable developer options and usb debugging. And I found the reason for the download mode bootloop. It turns out that the volume buttons are messed up. Volume up is not responding and volume down seems to be pressed all the time or repeatingly pressed in really short terms. Since my device is not rooted I installed an apk that allows me to disable the hardware buttons without root. But I found no way to run this app in safety mode. Also I have no access to the system files to change the key bindings on my own. I hoped to find a way to force normal boot out of safety mode but just got it booting up into the download mode again.
And there I am, my device is booting into download mode and nothing else. I don't know if it was just a lucky moment that the device booted into safety mode or if i did some magic that worked. But i can't get it to do something else than booting the download mode right now.
Do you have any idea what I can do without opening the device to unplug the buttons physically or to root it? If neccessary I am willing to do so but it's not the way I'd like to do.
Regards
Schmunzelhummel

Rooting Help - Virgin Mobile Galaxy J3 - Volume up button unusable :(

Heya peoples, I have a problem and am hoping for some help in a work around.
I am trying to root my J3 but my volume up button does not work. I have adb installed, and the correct drivers for my phone. I can use adb command to reboot to the bootloader and it brings me to the Odin "downloading" screen. I can then use the program to install TWRP so I can root. Everything goes fine up until this point. After TWRP is installed there is a single massive problem I am hoping there is a work around for. My volume up button does not work. I can only reboot to recover using adb once the phone boots up, and I read that if you let that happen it overwrites TWRP with the stock recovery (which is what happens when I do this). I read that you have to reboot directly from the downloading screen into recovery using Vol up and home and power. But I can't do that since my Vol up doesn't work. When I am at the download screen after installing TWRP none of the adb commands work so I can't reboot directly to recovery to access TWRP the first time. I hope this all makes since, and I hope someone has some advice because as far as I can tell I can't continue passed this point without a working volume up button.
A little more info in case it matters. When using adb command prompt I have to type ".\adb" instead of "adb" as the tutorials say. When I do ".\adb devices" my device shows up as connected. After rebooting to the bootloader using adb, typing ".\fastboot devices" shows nothing is attached, and any command I try to put in results in "waiting on devices". Checking the device management at this point does not show any unknown usb devices (one guide I read said if fastboot wasn't recognizing to check to update drivers if something was showing as unknown usb".
Basically hoping there is some way of booting directly to recovery from bootloader without having to use the vol up key combination so I can access TWRP for the first time. Any help at all is appreciated. I realize having a working volume button would take all the headache out of this but unfortunately fixing it is not an option at the moment.
Edit: I have also unlocked the bootloader using the Crom Services app from samsung, and have developer options and usb debugging enable.
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
CopaseticDream said:
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
Click to expand...
Click to collapse
Can this device even be rooted? Doesn't virgin lock their devices?
In any case if you flash twrp to the boot partition (rename it to boot.img) it'll boot directly to twrp then just use twrp to flash to the recovery partition.
Reflash the stock boot.img back to the boot partition.

Unbricking HTC U12+

Hey guys - I hope you're doing well.
I recently got an HTC U12+, but wanted to try using a custom ROM due to all of the bloatware . Unfortunately I think I've ended up bricking my device. Here are some things I've since tried:
- Restoring to the backup I made beforehand in TWRP - restore works without any errors, but then just hangs at the boot screen
- Method 1 from this thread (https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664) - TWRP always says the zip files are corrupted for some reason
- Method 3 from that same thread - this actually worked before, but I tried installing a custom ROM again, somehow messed up again, and now this method no longer works as it just hangs at the "HTC" boot screen for eternity
- Both methods in this thread (https://www.theandroidsoul.com/how-to-install-htc-firmware-ruu-and-zip/) - the first one leads to a "failed remote 99 ru unknown fail terrible mishap" error, and for some reason my PC doesn't see my phone when I try the second despite being able to see it in file manager
- Probably many other methods that I've now forgotten
I know this is a whole lot of information, but I'm in desperate need of some help. I typically like to troubleshoot things myself, but I've been trying to fix this for quite some time now and could definitely use another set of (much more experienced) eyes. I greatly appreciate any help you guys can provide.
Thanks.
Flash RUU with SD card method
Download RUU from here(important:check your CID): https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
1. rename RUU to 2Q55IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode,
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU(this method erase all your data)
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
EDIT: So I was finally able to get into download mode by waiting until the phone done its 6 minute reboot and then holding power down until it vibrated once, then held volume up until it vibrated again, then let go of the power button, I was then able to choose recovery, download etc.
So I managed to get the file 2Q55IMG.zip to install, it said it installed 100% okay. The phone rebooted and now I'm stuck again just at the white HTC logo and Power by Android down the bottom of the screen.
This time the phone is not automatically rebooting itself and no key combinations will make it reboot. I've tried holding them all in certain combinations for periods of time, the phone will not reboot or turn off.
EDIT 2: So maybe I didn't wait long enough after installing the 2Q55IMG.zip file, I finally got the phone to reboot and now I've got a working phone again. happy days :laugh:
whowhatwhen said:
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
Click to expand...
Click to collapse
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
fabrizio b92 said:
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
Click to expand...
Click to collapse
Cheer mates, issue sorted. I just updated my comment in my post.
Not sure if I'm game enough again now to try and put LeeDrOiD and Magisk on it.

Categories

Resources