hello I need your help, I have my htc one m8 like a brick and wifi for having no lights flashed a kernel modficado, this problem also happens to me with an eye htc desire, there some solution for unbirck cell? I tested with RUU and they tell me Error # 120 on the phone battery is below 30%, but the battery is charged to 100% pass this because I have Windows 10 ?, I read that Windows 10 gives problems with some RUU
someone help me?
My problem statement:
1. HTC One M8 is currently in boot loop. It boots approximately around 6 to 7 times and then enters to normal operation. This happens everytime i reboot.
2. WiFi is greyed. unable to "On" the Wifi. Still i can use my data through my SIM card.
I have also HTC Desire eye with the same problem and I can not return to factory, this seems a nightmare :/
trinidaddysan said:
My problem statement:
1. HTC One M8 is currently in boot loop. It boots approximately around 6 to 7 times and then enters to normal operation. This happens everytime i reboot.
2. WiFi is greyed. unable to "On" the Wifi. Still i can use my data through my SIM card.
Click to expand...
Click to collapse
Is the phone modified (unlocked bootloader) and did you try to flash a custom ROM? If so, what ROM and version number?
What hboot and radio numbers (shown on hboot screen).
trinidaddysan said:
hello I need your help, I have my htc one m8 like a brick and wifi for having no lights flashed a kernel modficado, this problem also happens to me with an eye htc desire, there some solution for unbirck cell? I tested with RUU and they tell me Error # 120 on the phone battery is below 30%, but the battery is charged to 100% pass this because I have Windows 10 ?, I read that Windows 10 gives problems with some RUU
Click to expand...
Click to collapse
Yes, Win10 can cause the RUU to fail. USB 3.0 is known to cause problem too (does your PC have it?).
One thing you can try, make sure you are using the latest 4.28.502.2 as opposed to 4.28.502.1
All AT&T RUUs are linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Reason I suggest this, I've seen at least a report or 2 of better luck with the latest RUUs (Stagefright fix released in August) as opposed to the previous Lollipop RUUs.
Otherwise, you may need to try a Win7 computer. Win8.1 may work too. But 7 seems to be the most reliable.
trinidaddysan said:
I have also HTC Desire eye with the same problem and I can not return to factory, this seems a nightmare :/
Click to expand...
Click to collapse
No idea about that phone. Suggested solutions for the M8 may or may not work on the Desire Eye.
I would advise against assuming the same fixes will work on different devices (may not work or even cause permanent damage), and seek specific help from other Desire Eye owners, if possible.
redpoint73 said:
Is the phone modified (unlocked bootloader) and did you try to flash a custom ROM? If so, what ROM and version number?
What hboot and radio numbers (shown on hboot screen).
Yes, Win10 can cause the RUU to fail. USB 3.0 is known to cause problem too (does your PC have it?).
One thing you can try, make sure you are using the latest 4.28.502.2 as opposed to 4.28.502.1
All AT&T RUUs are linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Reason I suggest this, I've seen at least a report or 2 of better luck with the latest RUUs (Stagefright fix released in August) as opposed to the previous Lollipop RUUs.
Otherwise, you may need to try a Win7 computer. Win8.1 may work too. But 7 seems to be the most reliable.
No idea about that phone. Suggested solutions for the M8 may or may not work on the Desire Eye.
I would advise against assuming the same fixes will work on different devices (may not work or even cause permanent damage), and seek specific help from other Desire Eye owners, if possible.
Click to expand...
Click to collapse
and this man could get a RUU to serve in Windows 10 and are working wonderfully, and also use the method in desire EYE, thank you very much for your provided information, you are a great contributor
Related
I am hoping someone can shed some light on a possible solution:
Generic UK Hero.
Clockwork ROM Manager installed and have backed up and successfully restored my standard Hero Rom.
I recently updated to the newest Radio rom and am hugely impressed with the signal improvements. So some aspects of what I am doing is working.
However I have tried. Vanilla, Chronos and Damage control and whenever I try to update when I get to the reboot stage the phone just sits there on the startup screen that says HERO. No little droid poking his head out, no shiny effect on the Hero logo, just the static logo. Latest update attempt has been sitting there or 12 minutes now.
I can pop the battery out and restore my original backed up settings no problem.
This has been tried while charging, while plugged into the USB and while not plugged into anything.
Any ideas ?
Thanks
Are you using a CDMA or GSM Hero? Vanilla could be either, but as far as i know, Chronos is for GSM only, and Damagecontrol is CDMA only.
Dont put the wrong type on the wrong handset.
CDMA or GSM ?
not sure what the difference is, I have a UK Hero that does 3G. I have tried UK specific (I think) roms (Vanillain) with exactly the same result. When rebooting after applying the zip update I just sits on the HERO screen.
hmmmm
Bit more info
I have been playing with fastboot/hboot and while it's a bit quick, hboot is reporting no image or wrong image aginst these (and more files)
HERODIAG.ZIP
HERODIA3.nmh
HERODIA2.nmh
etc. there's more of these.
This indicates I have loaded the wrong ROM image? Or have screwed up the (seemingly) simple process of flashing a rom.
Arse!
God I feel such an arse. Loading CDMA ROM Image on GSM Hero will not work.. Just loaded VillainRom 5.5 and it's working.
Mebbe not
A bit too impatient posting there. No Villain has the same problem.
Fastboot gives me
Fat32 INit ok
Open File Fail
Reboot Device?
wodswods said:
Fat32 INit ok
Open File Fail
Reboot Device?
Click to expand...
Click to collapse
Sorry i dont know what that means. the only thing I can suggest is to follow BTDAG's guide which is linked in my signature,.... Or wait to see if anyone can shed any light on the error you get?
Or look for a thread with support for that Clockwork ROM Manager?
Wait longer and get a logcat running to see what is happening.
I CANNOT believe this is a dead end . . as far as i have learnt from any "radio bricked" posts I have come across.
I am not a techie to start with but what could possibly be an unrecoverable damage unless the wrong radio flash impaired some hardware in the phone? This post, I hope, will also serve as an appeal to all the tech gurus out there saying "here's your nemesis . . radio brick"
I have an HD2 originally WWE ROM and then I decided to flash Dutty's after a radio (2.15) flash.
Then I was also able to run Android. Every thing was fine except for battery drain in Android so I said to myself "lets go back to winmo for a while".
aa aa . . not yet . .winmo was fine too except for some symptoms like sound failure, time sync failure, occasional hangs and so on which were fixed after a soft reset / restart.
Then .. one fine day (3 weeks from flash date) I woke up to a frozen phone. I tried restart/reset (soft and hard) nothing worked. I was always stuck in the white screen. I was still able to go to bootloader though.
Now the discovery of the nemesis. Tried the following proposed solutions
1. Flash Ship ROM from PC - The flashing would start and stay at 0% - ERROR 272 - Failed Connection - Recovery did not work either
2. Flash Ship Radio - Same error
3. SD card Flash ROM - Completed but the phone would go beyond the white screen
4. SD card flash Radio - Getting the infamous "Radio - Error" Update failed. Update terminated
5. Goldcard - Unfortunately I cannot even try it since the CID of the SD card can only be obtained via communication with my phone.
Now for the big question:
Whats going on???
Can I just wipe everything from my phone and start from scratch? like from command line so to speak . .?
This cannot be unless the phone can never ever be reused without changing a faulty hardware
Update: Solution
I had to delete this section since the information provided here was incorrect .. sorry . . still no solution
i am no expert..but just a suggestion
since you can enter bootloader...can i assume u have HSPL2?
if yes, you might want to do a Task 29.
then reflash a new rom.
dutty rom works fine with 2.15 radio
good luck
I see it's your first post here, you have to read very carefully and know what you are doing before flashing your device.
If you flashed your stock ROM thru SDCard method (a stock ROM is device specific), then your device should be in original state: stock SPL, stock Radio, stock BootScreen and stock OS (the 4 parts of a ROM).
So if it doesn't go beyond the white screen after that, you probably could send it back for repairs (if warrenty is not due).
But if you can enter the Bootloader, it's probably not bricked.
But if you can enter the Bootloader, it's probably not bricked.
Click to expand...
Click to collapse
sadly not quite correct. there are a few dozen references to the infamous radio update brick, where flashing seems to work, hspl'ing seems to work, but after restart nothing has changed.
The only suggestion i have to offer is finding another winmo phone (or pc/laptop sd card reader that is pci not usb based) and using that to create the goldcard, though even there i suspect it may not help.
If u can enter boodloader, make sure you see it's connected and see: USB at the bottom white part.
If this is what you see, i would set the stock rom back so everyrthing is back to normal.
Then read these forums good before you proceed.
Succes
Same thing happened to my phone, nothing will fix this, flashing a stock rom gives an error msg half way through , flashing custom rom also gives error. Factory reset, after resetting it gets stuck on htc screen.
weird, my radio is not working too, happened few days ago...
You could always try and remove the SD Card and then switch on into Bootloader Mode. Connect to the computer. Then run a Stock/branded ROM from HTC's website with your phone's serial number (this should at least guarentee that you are downloading the correct ROM).
Original post updated with solution
samsamuel said:
sadly not quite correct. there are a few dozen references to the infamous radio update brick, where flashing seems to work, hspl'ing seems to work, but after restart nothing has changed.
The only suggestion i have to offer is finding another winmo phone (or pc/laptop sd card reader that is pci not usb based) and using that to create the goldcard, though even there i suspect it may not help.
Click to expand...
Click to collapse
--- Tried goldcard method every which way possible.
fred_up said:
You could always try and remove the SD Card and then switch on into Bootloader Mode. Connect to the computer. Then run a Stock/branded ROM from HTC's website with your phone's serial number (this should at least guarentee that you are downloading the correct ROM).
Click to expand...
Click to collapse
-- Tried this as well with no avail....
htc hd 2 leo having problem
sir i have htc hd 2 leo and i was updating the softwere and then it stuck to 90 % and now i am having a screen with 3 colours ... my spl 0.64 version is not going to upgrade and i cant find file on internet working with this version, your already posted files are not working ...
please help me how i can i get rid off this problem and my phone work again ... tell me the whole procedue how to get radio and convert it on android ...
mairu834 said:
sir i have htc hd 2 leo and i was updating the softwere and then it stuck to 90 % and now i am having a screen with 3 colours ... my spl 0.64 version is not going to upgrade and i cant find file on internet working with this version, your already posted files are not working ...
please help me how i can i get rid off this problem and my phone work again ... tell me the whole procedue how to get radio and convert it on android ...
Click to expand...
Click to collapse
It's a prototype, notice the SPL 0.64
Flash stock rom back and then Radio 2.x
This way you can flash newer roms.
Notice you won't be able to install Android or WP7 cause of Prototype having diffrent hardware!
http://forum.xda-developers.com/showthread.php?p=7896583#post7896583
my devices keep restarting
i use it out side USA and not activated
in the stock rom resarting and same thing in the custom rom
every minite restating please help me
if you can, try an RUU for the phone...it will load the system back to it's original factory settings...if you're familiar with ADB make sure your device is recognizable thru there and try flashing the phone manually back to factory settings
i cant flash it my Hboot 1.50.0000
please any help
welcome to the club my friend... spoke with sprint today about this issue after they send me a new replacement phone for this issue and this new phone is doing the same thing still.. keeps rebooting and or shuting off requiring a battery pull to restart it. Sprint says they are aware of the problem and it is not a small issue affecting only a small number , its wide spead. they are awaiting a fit in a patch from HTC but there is no eta . they also suggested i monitor the HTC website for the fix
thanks i thought thats from my device only
please tel me if they fix it
any news? still same issu
Mine's not doing it that frequently, but it seems to be at the most inopportune moments!
My second Shooter (first one had a dead pixel) had the same issue and even though it wasn't often it was ANNOYING. I ended up having to swap it out for a new one and this one hasn't been giving me any sort of rebooting issues (once or twice when OCing; but that's expected). If it is software related flashing the RUU like someone else mentioned may help out; it'll set everything back to default straight from HTC.
If you're unlocked w/ the HTC method you'll have to relock first but then run this on your PC w/ the phone attached and follow the steps:
http://www.multiupload.com/09NOXKCUN0
^That's the latest RUU installer and should work for you.
Report back what happens; I'm curios about this myself since I never did an RUU reflash (was noobish in mind then) with my last device but if it fixes the issue it would make a LOT of people happy.
Peace.
lchupacabras said:
My second Shooter (first one had a dead pixel) had the same issue and even though it wasn't often it was ANNOYING. I ended up having to swap it out for a new one and this one hasn't been giving me any sort of rebooting issues (once or twice when OCing; but that's expected). If it is software related flashing the RUU like someone else mentioned may help out; it'll set everything back to default straight from HTC.
If you're unlocked w/ the HTC method you'll have to relock first but then run this on your PC w/ the phone attached and follow the steps:
http://www.multiupload.com/09NOXKCUN0
^That's the latest RUU installer and should work for you.
Report back what happens; I'm curios about this myself since I never did an RUU reflash (was noobish in mind then) with my last device but if it fixes the issue it would make a LOT of people happy.
Peace.
Click to expand...
Click to collapse
i need to flash rom from recovery mode
have another file for this
This is my third Android phone and fifth Android device. I've rooted all five and installed multiple ROMs and for the most part have not had too many problems.
I'm currently running Elegancia 5.3.0 on my AT&T One X+ and have a few issues that I'm tired of dealing with. I decided to flash the RUU to go back to stock and also to update to hboot 1.4 which is required for the Blackout ROM I was thinking about trying. The RUU cannot find my phone unless I connect while in the bootloader. Even then though, the RUU flash still fails. Since it cannot see my phone while it's running, I decided to check if ADB can see it. Nope. No luck at all. I have connected with ADB to my device many, many times... but it has been close to a year since the last time I did. I removed all HTC drivers and Sync from Add/Remove Programs, deleted my old version of the SDK and Java and followed LuckyThirteen's tutorial step-by-step.
My phone still shows up in Device Manager under PORTABLE DEVICES and I can't seem to make it connect any other way.
I've tried using every combination of search terms I can think of and have had no luck for the past 48 hours.
This is the same exact issue I am having! I am on hboot 1.35 however,and my phone won't even show up on device manager. I have done everything from factory reset, to trying other roms and back ups, to calling HTC, and still nothing. Good to see someone else has the same problem tho haha
Sent from my HTC One X+
Finally fixed my ADB problem using these steps.
Hi All,
I was trying to convert my ATT HTC One (Android 4.3; Hboot 1.55) to International version using the thread: [HOW TO] Convert AT&T/Rogers/T-Mobile HTC One to EU International One. (I had converted my old HTC One which I lost successfully using this thread in past.)
But when I got my new HTC One, I immediately OTA updated it to 4.3 and thus my HBoot also updated to 1.55. (I am a noob and didnt know it updated OTA will update to Hboot to 1.55 which is not compatible with revone to gain S-off. But anyways...)
So yesterday, I gained S-off using rumrunner. Had to root and install custom recovery to do that. Everything was fine until I gained S-off.
As I was S-off now, I decided to go ahead and start converting my Att HTC One to international version. So I started at Step # 4a of above mentioned thread.(I started at 4a bz steps before that are used to gain s-off using revone).
After I completed step 4a, and as menrioned in the thread, HTC One got stuck at 3/4 completed green status bar. And after that when I restarted my phone nothing is showing up. Screen is black and my computer gives me message that device connected could not be recognized. I never got the grey htc screen.
I cannot reboot into adb or recovery. if i hold the power button(10+ secs) phone vibrates. If I turn press the power button again the red led will turn on but screen is still black.
Please tell me i am not screwed and there is a way to fix this.
I really appreciate any kind of help.
You guys rock
P.S: I have searched the forum if someone has had same problem but couldnt find any, if you know any thread that already has solution to this please direct me to it.
striderr05 said:
Hi All,
I was trying to convert my ATT HTC One (Android 4.3; Hboot 1.55) to International version using the thread: [HOW TO] Convert AT&T/Rogers/T-Mobile HTC One to EU International One. (I had converted my old HTC One which I lost successfully using this thread in past.)
But when I got my new HTC One, I immediately OTA updated it to 4.3 and thus my HBoot also updated to 1.55. (I am a noob and didnt know it updated OTA will update to Hboot to 1.55 which is not compatible with revone to gain S-off. But anyways...)
So yesterday, I gained S-off using rumrunner. Had to root and install custom recovery to do that. Everything was fine until I gained S-off.
As I was S-off now, I decided to go ahead and start converting my Att HTC One to international version. So I started at Step # 4a of above mentioned thread.(I started at 4a bz steps before that are used to gain s-off using revone).
After I completed step 4a, and as menrioned in the thread, HTC One got stuck at 3/4 completed green status bar. And after that when I restarted my phone nothing is showing up. Screen is black and my computer gives me message that device connected could not be recognized. I never got the grey htc screen.
I cannot reboot into adb or recovery. if i hold the power button(10+ secs) phone vibrates. If I turn press the power button again the red led will turn on but screen is still black.
Please tell me i am not screwed and there is a way to fix this.
I really appreciate any kind of help.
You guys rock
P.S: I have searched the forum if someone has had same problem but couldnt find any, if you know any thread that already has solution to this please direct me to it.
Click to expand...
Click to collapse
Im having the same issue right not so far couldn't find a fix yet first time doing this and blamm black screen of death
x3reme85 said:
Im having the same issue right not so far couldn't find a fix yet first time doing this and blamm black screen of death
Click to expand...
Click to collapse
If your on a windows 8.1 PC what happen is the RUU downgraded your hboot and windows no longer can see the phone. Most likely your phone is not dead you just need a windows 7 PC to redo all the steps of running the RUU