hey guys.
i unlocked my bootloader using CID method, flashed twrp, and installed the NOS sense 5 rom (didnt root)
the problem is, the phone is stuck on htc quietly brilliant screen. no budge
i tried using adb push to push roms to my phone, and i tried adb sideload
(tried both twrp and cwm)
using RUU gives me error 155 (always exits on "updating signature")
i am able to get into everything (recovery, bootloader, etc) just cant boot
any suggestions? :crying:
EDIT: solved, just had to flash the boot.img from the rom and all was good
Related
hi.
i have never had problems with my hero before but suddenly i'm unable to flash anything on it. i have always been on the stock recovery with S-OFF and rooted.
i flashed VanillaEclair 6.2 a while back and had no problems.
yesterday when i tried to flash another rom, i got signature verification error. I thought i'd flash TWRP or CWMR to bypass the signature verification but when i tried to flash it, i got the same error.
i tried to flash the recovery through rom manager but it failed...even with adb!
frustrated, i thought to use the official rom RUU...i ran the RUU, it went halfway in flashing the rom and then gave error.
now i don't have any recovery and pressing 'home+power' leaves me at the HERO screen forever.
luckily i can still boot in android so my device is not bricked.
I have tried pushing the recovery via adb but even the fastboot doesn't work.
i tried starting from scratch to check for the bootloader lock. fastboot oem get_identifier_token returns an error.
phone is working fine but i don't like the rom and want to be able to flash via custom recovery.
please help!
much appreciated.
http://wiki.cyanogenmod.com/wiki/HTC_Hero_(GSM):_Full_Update_Guide Check the installing a custom recovery page, use the FLASH_IMAGE method
hi, i unlocked bootloader and flashed CWM Recovery, everything sounded fine on the command prompt window, but the CWM wasnt installed (the bootloader still says [ENRCU2]), i rebooted the bootloader, chose recovery, it just gives the HTC logo window n then shuts down..
i tried to flash CWM over n over again, but it still does the same problem.
help please!
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
clrsri2006 said:
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
Click to expand...
Click to collapse
UPDATE : The reboot to boot loader via power button + volume down works but it took about 2 mins of holding those buttons, which is unusually long time. So its not a brick As experienced developers say DO NOT PANIC, staying calm and read the forums thoroughly has helped.
I'm trying to see how I can fix the .zip install failures now.
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
clrsri2006 said:
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
Click to expand...
Click to collapse
UPDATE : After many attempts I could work it out by using guru reset .zip file (1.26.502.12). I did this before as well but was not able to get s-off previously. This time I asked to install superuser when resetting using guru reset file. I got the 1.26 one back with disabled touchscreen. Then I used rumrunners and got s-off and then used the ruu for 3.17.502.3 exe file to get the working on.
Now the bootloader just says unlocked but not tampered. I got the twrp recovery again as it was very handy for me.
I was able to get supercid. Now trying for ARHD 51.0.
After I got the RUU for 3.17.502.3 the only issue i noticed is that when phone boots up I just see HTC instead of "HTC quitely brilliant"
Hi All,
I have unlocked my HTC M8 eye with the help of HTCDev site and installed TWRP from playstore. I restarted the phone and went into Fastboot mode and using adb installed TWRP image file for this phone (v2.8.0.3), before it I have saved SuperSU zip file on my local storage. From TWRP in recovery mode I installed SuperSU everything goes good and its shows Success. When I reboot I shows "Your device does not seems to be rooted? Install SuperSu now?" When I gave install now it shows error msg "Failed to copy su binary in to /system/bin/". I tried re-flashing it and tried to install some other versions of SuperSU but none worked. After this phone goes re-booting and stuck in HTC logo screen till I use shortcut keys to enter recovery mode. In Fastboot mode my laptop was able to detect my phone from command prompt and also my internal storage.
I believe I can get back my phone on working. Please help me, I really need my phone back .
If you can still get into recovery, then you can install a custom rom and go that route. Keep in mind, if you are just HTCdev unlocked and you flash a custom rom, you will have to use fastboot to flash the boot.img.
If that doesn't work, then you should be able to find the RUU for your phone and restore it to stock and redo the custom recovery and root. For future reference, just flash the SuperSU zip. TWRP doesn't normally detect that correctly and trying it's method often makes things worse, as you experienced.
I tried installing Pixel Experience, but unforutantely i ended up in fastboot screen everytime, I tried fastbooting the stock rom using Mi Flash and it didnt work, it reboots the device and shows ''THE SYSTEM HAS BEEN DESTROYED'' the bootloader is unlocked, and can be unlocked using cmd, i can boot twrp, but thats about it... help????