Hi,
I'm struggling with battery drain on Oreo but it's not the case right now.
The problem is that I've successfully unlocked the bootloader and rooted my HTC 10 then flashed latest LeeDrOiD but the drain is still present. So I decided to try downgrade my phone to Nougat...
First of all, my device is S-ON, CID HTC__034.
I was following tutorials from this forum but I wasn't able to flash Nougat RUU (because of not using htc_fastboot, which I discovered later) even after flashing hosd. After reboot, my LeeDrOiD started (just like after factory reset) and everything was OK. Then, I tried with Marshmallow RUU (got same result) and with htc_fastboot (different error, still no downgrade, boot to LeeDrOiD). Suprisingly I was asked to enter PIN to decrypt my phone. I couldn't do that, because it shouldn't be set. After some attempts I've formatted my HTC and then flashed LeeDrOiD.
After all this operation my home button stopped working... That was the moment I decided to restore my stock Oreo backup.
Although my home button is still not working I thought that maybe I'll try to downgrade from stock but I'm not able to get into rebootRUU.
I've run out of ideas.
I can access download, bootloader and recovery mode but after typing fastboot oem rebootRUU my phone boots to system.
Is there anything I can do to bring at least my home button working?
Thanks in advance.
Related
I have serious problems with my phone that I could really use some help with as at the moment I'm completely screwed - I've already spent hours reading forums but have yet to find advice that will help. Here's whats happened:
I have an A8181 HTC Desire, and I took an OTA update yesterday that bricked my wifi. At this point I thought it would be easiest to root my phone, and after checking that my hboot version was 0.93, I read advice that said to downgrade this to 0.83, which I duly did.
Now, my phone is stuck in a bootloader loop - I get the 3 androids on skatebooards with FASTBOOT in red, and I can choose from:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I select bootloader I then get:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I can access recovery and apply update.zip roms successfully (I've only tried official HTC 2.2 roms as the phone isnt rooted), but after doing so it just goes back to the bootloader loop.
If I select FASTBOOT then I'm just back at the first screen.
I've tried clearing cache and factory reset aswell, but I still can't get past this 2 screen loop.
It's like the bootloader just can't load whatever rom is installed.
Because the phone isn't booting up, I can't use adb or any other pc tools as the device is not detected on my pc - although it does show up in device manager on windows.
I'm close to sending this back to try a warrantly claim, although I'm worried that by trying to fix this I may have invalidated this.
I'd really appreciate any help or advice as to how I can get out of this and get my stock 2.2 back.
Cheers
If your computer using windows, have you installed hboot drivers?
If you have those installed your pc should detect the phone.
unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
You shouldn't have had to downgrade your bootloader. If you can, go back to the newer.
The wifi issue, was widespread on desires, I had it also after a "pushed" update from HTC (european model, unlocked). I downloaded a stock 2.29 froyo. Had to make a gold card also. Took several tries, wipe cache, but eventually successful.
Then, I rooted, and went to CyanogenMod7 rom with clockwork recovery.
Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
When you flash a new kernel, all you have to do is place modules zip in phone storage, put phone in bootloader, connect to computer, flash boot.img, go into recovery and flash modules. If you don't flash boot.img, the phone won't boot. Try going into bootloader by pressing volume down and power at the same time and holding it, flash viper boot.img via fastboot kit, full wipe and reflash rom. I've messed up a few times but this has always worked for me.
Beyazid said:
Hi guys I´m going to go mad because of flashing a new kernel on my HTC One X.
At first the infos:
Unlocked at HTCDev
Had the CWM 5.8.40 Recovery (HAD!)
Faux Kernel 7m (didn´t work at the first time but after a reflash everything was ok)
Viper X 2.7.1 Custom Rom (UC+UV)
SoundEnhancer Mod 18
At first: I´m more like a silent reader and I´m trying to learn as much as possible so I´m not an expert.
Today I tried to flash the newer Faux Kernel 10m on my One X but forgot to erase the cache afterwards. It got stuck at the HTC One Logo
So like at the 7m Kernel I retried but this time it got stuck again at the HTC One Logo.
I read the Disaster Recovery Tutorial Thread and tried the fast and easy things but they didn´t work eitther.
I accepted the fact that I had to recover the phone with my backup which was from the stock rom with nothing on it.
After restoring the boot gif changed to the original one but it still got stuck at the HTC One Logo. This time I erased the cache.
After that I had to use a RUU but I just took the newest one because I didn´t get the idea how to match the cid with the RUU-numbers.
I did as it was written here in Method 2. But I didn´t see the Notification: "FAILED (remote : (00000006))".
I relocked the phone and it restarted but now it´s in the bootloop and doesn´t get detected neither by the RUU exe nor by the cmd. So I can´t get back to the recovery and can´t get detected by the RUU.
How can I fix my phone to end this misery?
I hope someone can wirte a step-by-step guide so everybody who has the same problem can solve it.
Greetings
Beyazid
Click to expand...
Click to collapse
there are infinite posts about how to fix this and tutorials too if you use the search button, anyways
1- why using faux 7m when there is already 10m ?
2- hold power+vol dwn
3- go to recovery (hboot not fastboot)
4- go to mounts and storage, mount storage usb
5- copy to your sd all the files excluding the boot.img from faux
6- flash rom then modules then type in cmd "adb reboot-bootloader" (without quotes),
7- choose fastboot in bootloader then flash boot.img and erase cache
@VCek: I flashed this before the Versions 10 and 11 came out
Thanks for the infos. I´ll use them the next time. But now I can´t reach the bootloader anymore because I locked the phone with "fastboot oem lock" and because of that I can´t do anything but go to the fastboot mode. The recovery is locked or in other words: I can´t use the CWM Recovery anymore.
If I click the recovery mode this happens: vvvvvv(dot)vidup(dot)de/v/l1vVH/ (make a dot instead of the word "dot" and change the V´s to W´s, I´m not allowed to post outside links right now)
The next step should be the unlocking I guess. Right? But how can I do that?
Edit: I was able to unlock the phone again so it should be easier from now on but your steps didn´t work for me. I reflashed the Viper X Rom and reflahed the Kernel without the boot.img in it. But I didn´t get the point which boot.img I should flash. Both of them or just the Rom boot.img?
Edit2: After a long day I was able to solve the Problem with the right RUU. After all it was easier than I thought and I should have done that at the beginning
A week or so after upgrading from Pacman v15 to v15.3 I began having my phone drop into roaming for a really long time. I restarted my phone to see if it would fix the issue, and I got a bootloop, nothing past the white HTC screen I had issues flashing to fastboot, so I got a new unlocktoken and now I can flash. At least... it will send, write, and "okay" me on it, but then nothing will work. I will "successfully" flash a recovery (i've tried twrp and cwm) and then when I try and get into them through bootloader it just sends me on the same old bootloop.
Please help... I guess I should flash an RUU but I've never done that before, and I'm curious as to whether or not this will even work since nothing else is "taking."
UPDATE... DL'ed the RUU and followed directions of...
flashing recovery_signed.img
fastboot oem lock
then running RUU in fastboot usb.
Everything SEEMED to take fine, and then when I go to reboot I get a loop again. grr...
Hi, recently I converted my international HTC One M9 to Developer Edition so that I could receive the Marshmallow OTA. This worked and I had everything setup, but whenever I booted the phone I was shown a red warning text. After surfing the internet for a while, I found a file to flash through ADB that should fix the problem. The file stated that it was for the Developer Edition, so compatibility should have been fine. Unfortunately, the first time I flashed it, it said error, please flush immediately and so I flashed it again. The second time it took much longer and then said it had been a success. However, when I went to reboot, it went straight to bootloader, and from there I can access download and recovery, but rebooting only takes me back to the bootloader. I have tried the hard reset key combo to wipe the cache and also 'fastboot erase cache' but it is still stuck.
My CID and MID is BS_US001 and 0PJA11000.
Software status: Official.
Unlocked and S-OFF.
Any help would be greatly appreciated as this is my daily driver and I need it online soon . I will probably try a factory reset and if that doesn't work maybe RUU it again
-----------------------------------------------------------------------------------------------
Just tried a factory reset and it went straight to bootloader so I have now started to RUU it again using 0PJAIMG in the SD Card. Fingers crossed :/
i did flash dev ed 2.11 and then OTA all way to Dev 3.35.617.12 MM, i will try on the afternoon to root with twrp 2.8.7.1beta and SUperSU 2.65.
just flash 3.35.617.12-Firmware-noredtext-aboot-only.zip if you are right now on this firmware , you will get the msg (90 pre-update FAIL) do not worry about this MSG as this is actually a success msg . all you have to do after that is to just use this command (fastboot reboot) . all done your m9 device will reboot into normal mode with no red text warning.
Regarding to title, I was trying to flash a custom rom on my Honor 7X but apparently with the crazy amount of idk twrp recoveries and failed flashes, the phone (totally empty with both system and data) decides to factory reset lowlevel after i try to fastboot oem relock bootloader and it stays stuck at 99%. Any troubleshooting tips would be great.
Well, am experiencing similar problems.
I was on rooted Stock, when I got a System update available prompt.
I uninstalled Magisk, Flashed stock recovery and did a Factory reset from the Stock recovery.
It booted up, but there was no Keyboard installed. I think, I had uninstalled the pre-installed one when I was rooted.
I couldn't get past the Setup Wizard, as the FRP was Locked and there was no way of typing the password.
I tried to flash the system.img from fastboot but it gave me 'Remote: command not allowed' error. (Even for flashing recovery)
I google'd a bit and ended up on a solution as to relock the bootloader, Turn on OEM Unlocking and lock the bootloader again.
I relocked the bootloader, it did a 'Low-level factory reset' and now the phone is even bootloop. (it boots into eRecovery from the Honor/Huawei logo)
I tried the 'Download latest version and recovery' from eRecovery. It's giving me 'Package verification failed' error.
'dload' method never worked for me, and it is still the same.
Any solution/suggestion?
Bootloader relock with empty system is a definite hard brick.
I think you may need to ues dload method and flash a service rom to get back up and running.
dload says software install failed, any ideas? @mrmazak
apparently now its back to usual after leaving it stuck at 99% overnight until the battery dies out, could go back to fastboot and stuff
How far did it get? Stop and fail at 5% happens when update not found or not correct update.app.
Of it loads higher that 5% then fails , that's probably not gonna be able to fix it.
We have only found 2 service roms. Both are bnd-l21c432 one is Nougat one is Oreo. Both have been used on other versions of honor 7x. But after it runs you need to run hurupdater or hwota with correct model / region fullOTA.