Yesterday I reverted my phone back to stock (4.4.2) using the RUU that you execute from the pc. Everything was working fine, except my phone wouldn't detect the new OTA update still. So I decided to use the RUU for the new update (5.0.2) from htc's site. Now when I tried to use that RUU it would start as normal. I would hear the disconnect/reconnect tone on my computer as the phone switched into the black HTC screen and the program would say updating 1/6. However when it would reach the end of the 1st part of the update, I would hear the disconnect/reconnect tone again. The program then says updating 1/7 with the progress bar full and the phone screen just shows the black HTC screen. It never progresses past this.
So me being me decided to keep on trying and I did this http://forum.xda-developers.com/att-htc-one-m8/general/att-4-4-4-firmware-signed-encrypted-t3031703. So that install seem to go fine, except now my phone won't boot past the white "HTC powered by android" screen.
Here's what the hboot screen says:
Software status: Official
RELOCKED
M8_UL_CA PVT SHIP S-On
HBOOT- 3.19.0.0000
Radio- [email protected]
OpenDSP- v38.2.2-00542-M8974.0311
(This is in red text) OS- 4.28.502.1 (4.28.502.1)
eMMC-boot 2048MB
Mar 20 2015,3:01:11:0
Also the 4.4.2 RUU won't work anymore because I have the wrong version bootloader now. I'm usually pretty competent at these things (been rooting/ flashing roms on my phones for about 4 years now) but I've messed up here.
So how do I get this working again?
Update: I kept messing around with the RUU. Tried different usb ports. I also tried unplugging it when it got stuck at 1/7 and plugging it back into a different usb port, and that seems to have worked. It's currently updating 3/6 so it's definitely progressing now. So... this thread may be pointless now. Such a weird fix though....
Update2: Well that fixed it somehow and my phone is booting up normally. Sorry for making this thread then.. Mods can delete it.
rockr09 said:
Update2: Well that fixed it somehow and my phone is booting up normally. Sorry for making this thread then.. Mods can delete it.
Click to expand...
Click to collapse
Better to mark the thread title as SOLVED and leave it up; in case others encounter the same issue and are looking for a solution.
If you thought an issue worthy enough for a thread in the first place; its almost never the right thing to do to have it deleted (even after solved).
Related
Hey, I have a somewhat major issue. I'd absolutely LOVE to be referred to any thread that exists to solve my issue. I just feel my problem is so bifurcated that no one resolution I've found quite fits the needs of my idiocy.
5 Days ago I got the HTC ONE with the Sense UI. Needless to say, I wasn't a fan of being stuck with the Blinkfeed, and lack of 4.2, so I went over to the lighter side of Android and put the Google Play Edition on my HTC ONE (AT&T).
This went well! I was running the GPE and had a blast, but I decided I wanted to return the phone and get the black one. Problem is...I needed it to look as it did out of the box, all unadulterated and such.
I attempt to restore it, accidentally delete OS, accidentally screw myself out TWRP, ontop of having NO nandroid backups.
My phone will either A. Boot to the HTC loader screen with the red disclaimer at the bottom, or B. Boot into the HBOOT screen by holding Power / Down Volume where it says ***TAMPERED*** / ***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, etc. <-- Lol what?
Anyways, I'm stumped as to how I go about fixing this and loading stock AT&T sense. I've tried to ADB push command ROMS on, but instead when I type ADB push I get a long list of commands, rather than any kind of success / lag of loading the ROM as other guides have pointed out.
When I FASTBOOT USB nothing pops up mounted. Upon going to USB mounted items, the Android device is recognized as a CD-ROM, not as a mass media device. When I launch recovery it goes into the screen where the phone is displayed with a green arrow circle. I've tried the ADB push command (with and without caps) and nothing occurs, both at the regular HTC boot logo and the short-lived recovery screen, only to display a red triangle with an ! mark in it's center (indicating no recovery loaded, I'm guessing).
HTC device manager doesn't recognize the device either, and suggests it's locked. This is highly frustrating and I'm sure the resolution is simple, but the problem is finding the right one(s) and subsequent steps needed.
I appreciate any and all help.
Try following this see what happens.... https://www.youtube.com/watch?v=n_KBYx0xuAs&feature=youtube_gdata_player
Sent from my HTC One using xda premium
tylerdurdin said:
Try following this see what happens.... YOUTUBE
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It didn't work initially, I had tried that video a couple of days ago. I did however get it to work.
I was running Windows 8, so first I needed to install drivers for Windows 8, by deleting the HTC from Device Manager and disabling driver verification. Doing this made the phone recognize in RUU.exe
The next step was an error code 155, suggesting my RUU was for the wrong model. Seeing as how the device was unlocked, I had to change directory to my android sdk and type "fastboot oem lock"
This fixed the error code 155, and the rest is history. Back on stock AT&T Sense 5.
Thank you for the link, had you not suggest it (and me attempt it a second time) I would have completely written off the method.
Hi,
I'm new to this forum and I need help. I'm not an expert with the whole android rooting and stuff
Few weeks back I updated my rooted HTC one from ARHD 4.3 TO 4.4ARHD
After I updated my phone it took forever to boot up , I went back to the boot loader and saw that I have no os installed.
I rebooted my phone and was taken to the main screen and it was working fine .
But after this update my battery has been acting funny , whenever my phone dies I get this red blinking led and won't turn on so I always have to press the power button and volume down. It would start up after a dew try. This has never happened to me until I updated it.
And I my apps would randomly crash and my phone would lag and hang sometimes and it takes forver to charge .
This is what's on my boot loader:
Tempered
Unlocked
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPEN DSP-V31.120.274.0617
OS-
eMmc-boot 2048mb
Can some one help me? I'm thinking of sending it back to store where I got it and maybe they can fix this but before that I want to make sure that it can be fixed . I'm from Dubai .
Thanks in advance
Please help I'm going insane. I woke up a couple days ago to find my Desire 601(Virgin Mobile Canada) in a constant reboot loop. The OS (KitKat 4.4.2) almost loads up but then immediately goes black and the HTC logo comes up again. The logo never does its musical start-up that it normally does and occasionally I will see an error about an app (google+, podcast or some other) pop up for an instant before everything goes black. Any changes I manage to make in the 30-60 seconds of OS time don't stick and safemode reboots the same way.
I tried to do a factory wipe but the phone ignores the command before rebooting again. I can access the bootloader but it doesn't seem to work. I tried to clear the cache and wipe the phone from there but it just goes into the reboot cycle. I tried to unlock the bootloader but after I say ok to the terms the phone simple reboots... over and over.
I've tried a number of suggestions as to ways of doing an RUU or flashing another operating system but I keep coming up snake eyes. I thought I finally had it when I was playing in flashboot when I found the -w command but the developer mode of the phone needs to be on for that to work (apparently) and guess what... the phone ignores me turning that on... YAY.
Any and all suggestions will be appreciated, I'm at the end of my rope here. Oh and the best part is its like a week out of warranty... hows that for timing.
My Bootloader screen is as follows:
*LOCKED*
ZARA_UL PVT SHIP S-ON RL
HBOOT-2.22.000
RADIO-1.26.40e.00.14
OpenDSP-v18.2.0268.0925
OS-2.14.666.3
eMMC-boot 1024
Feb 26 2014, 12:32:11:0
Any tips would be appreciated. Really pisses me off this phone has done this, definitely not amused at all. Is there some way to format the phone and start from scratch if developer mode isn't enable and the phone is Locked/S-on?
Thanks.
Still no luck with the boot loop phone(still looking for suggestions tho) but I've started messing with an identical phone I have. I've unlocked it and rooted it with twrp/supersu. Now I'm looking for a compatible JellyBean rom (I hate KitKat so far) or maybe a Lollipop rom (haha). Can anyone explain to me if I need a desire 601 specific rom or can a stock (nexus maybe) rom work fine? I'm very new to this (shocking I know) so I'm not sure what's what. Will any WWE rom work on virgin mobile? I assume it will. I would prefer as close to a stock android as will possibly work with my phone as possible. Again any help is greatly appreciated.
Remove the battery then put it back in ur phone
listen this is my last resort, i did everything I possibly could before coming here. & I searched people I freaking searched and ive tried every method I came across that related to my issue specifically, where the users found resolution. That being said, NONE of them worked for me. So i am not going to detail everything ive tried in the last 120+ hours dedicated to this issue in the last 10 days, so please understand that if your solution is one that is commonly/easily found online, chances are ive tried/applied but to no avail. Now to my issue, my specs are provided on the attached pic, but its hboot 1.58.0 radio is 1.09.00.0108 S-On & relocked bootloader, it was rooted with S-off but I am not sure if it is still rooted after the many attempts to get this device up & running. So now what happened, this is an inactive device of mine & i havent had it long, its mint condition tho and worked fine when i got it originally. I have an evo 4g as well and thats the whole reason i wanted the 3d. Ok, so I unlocked the bootloader thru htcdev & I rooted the 3d with s-on of course cause i am on 1.58. But then 2 critical things happened. When i got the 3d it wouldnt charge fully. it would charge til a green light but the battery would never show anything over 85% and either way i was flashing a rom and the battery just died when it supposedly had well over 50%. oh & btw, the rom was cynmod V? but the zip file is called "wild-for-the-night", which I have since learned wouldnt have worked anyway. & Then all of sudden the 3d wouldnt charge or turn on, but the orange light would act a specific way that I found others experiencing all over the web, but none of their solutions worked for me and i spent alotta f-ing time with the batt issue, that is until the new batt i ordered arrived, & solved the issue entirely. either way from that point on it will only boot into fastboot/bootloader. no recovery no rom, its not happening. In fact when I plug it in to a pc or to charge it wont stay powered down, it boots str8 into fastboot & simply wont stay off while plugged in live. but it does show its charging while plugged in. anyway I relocked bootloader so I could run the ruu and thats just not happening either. the 3d is updated to 2.89.651.5. At one point I followed methods to downgrade hboot to get s-off & I flashed hboot 1.4 or 1.5 in my attempts to downgrade but I lost that page with the exact instructions i was following and I havent been able to find it again, and ontop of that I lost the files I had downloaded to a usb that has been formatted since.. But regardless, it still shows 1.58, I just thought it might be relevant that I did attempt to flash an earlier version but things clearly havent worked out for this device. Adb doesnt seem to be recognizing the evo 3d & wont even show up as a connected device. fastboot is recognizing the evo tho, however when I try to unlock the bootloader thru htcdev, now it gives me an error talking about the unlock code isnt long enough or somwething like that. I can take a screenshot of it if needed. I really just wanna get this device back to an oem/stock condition, & then be able to follow methods that ive since come across to root with s-off. Please Help
Hello all! I know this is an old issue and the phone that I have is as old as life it's self but I hope that I can find some help here! I know there are sever threads covering this issue but I have not found any that covers the ENITRE issue that I am having.
Okay, now for my problem....
Of course my phone died (battery). I put it on the charger and powered it up. The phone stuck on Sprint screen for several days. This is the second time this has happened. The first time I was unable to use recovery but I was able to do a factory reset. THIS TIME I am unable to do anything. On factory reset, the phone goes to green icon and then it turns into the red exclamation. Same thing with recovery. I have tried the wipe/factory reset...I get an error there "E:can't open /cache/recovery/command" and I get that on all options in Sys recovery menu. I have read several threads on using fastboot but I have learned that there is more to it that plugging in the USB and recovering the phone.
To help answer some of the questions here are the details on the HBoot menu:
****Locked****
Shooter XC Ship S-On RL
HBoot - 1.58.0000
Radio - 1.09.00.0108
OpenADSP - v02.6.0226.00.0217
eMMC-boot
The phone has never been rooted and everything is stock.
I have seen that it can be recovered through Hboot menu but I'm not deep into this side of things so I will need detailed instructions if possible. I have an HTC Evo 3d and my PC is Mac OSX.
Same problem
I was about to post about my problem, but yours is very similar and like any good forum go-er I checked to see if there were any recent problems like mine.
I am running
**locked** shooter s-on hboot v 1.58 eMMC -boot from may 17, 2012.
I have never rooted the device or tampered with it in any way. I thought about it, but got a newer phone.
I recently got into computer programming and wanted to see what can be done with this old tech with still relevant hardware.
after starting the device it got into the OS , took me to my homescreen like normal then failed horribly after 10 seconds, once i slid the ring up.
it then got stuck at HTC screen, so i tried the bootloader, which works, so i went for a factory recovery. get the red triangle, so i look into rooting.
turns out that if i hadnt checked usb debugging and unlocked already, i cant get in to do anything. is this a soft-brick hard-brick case?
i feel there is hope, but the lack of response to OP after this time leaves me disappointed. I've spent many hours trying to find a solution to this problem, but it is way beyond me.
i tried finding signed copies of PG86IMG.zip for hboot 1.58 to no avail, only option is RUU which won't find the phone on windows 10. drivers are out of date, perhaps.
Installing linux now to hopefully get access to that file system.
Would really appreciate the help, devs. this is a great device would be a shame that NOT tampering with it would leave me and OP with a brick.
thanks for reading and thanks in advance for consideration and advice.
dunno, maybe try this
http://forum.xda-developers.com/showthread.php?t=1653777
virgin evo 3d has no downloadable current ruu to flash, and you guys are s on which won't let you flash older ruu to reset your system. which makes it difficult to fix.