Hello, I have a 64 GB HTC One M9u, S-OFF with CID: HTC__001.
EDIT:
It seems that even after my sd card flash the phone still does reboot randomly (perhaps I am being silly and we can say that it is crashing), I just had it occour to me after using it for a while. I have no idea why this persists, maybe it's a faulty battery instead? I was unable to change the title, but decided to keep the thread. Any help about this behaviour is greatly appreciated.
When I was reverting to stock, here is what I did:
1. I used ARUWizard to flash 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip
2. Then I did a OTA upgrade to latest 3.* firmware
3. after that I got a OTA to latest 4.* firmware
What happened then was that my device kept rebooting/crashing constantly even with the smallest of things happening like when I tried to setup the Play-account or used the music app, this occoured as weird to me.
There is only some quirks I noticed that seems odd:
The HTC Sense menus did not come in black with blue icons if activates as they did in normal stock, but they were instead black with red if activated, which seems suspicious. The background came out as hills one with the blue skies, while the one that was supposed to be there is the blue one with the yellow arrow (>)
So far I have proceeded to install RUU again, I did this by using the sd card method (since 4.* supports exFAT) I first put 0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip on the sdcard, then after this was flashed I did another HTC update (maybe just some HTC apps update) I am now on 4.28.401.3 CL869604.
I want to know if possibly there is a corruption on my phone that causes the phone to crash and to crash and rebootconstantly for no apparent reason? The crash can be me just watching a YouTube video and nothing more.
I also want to check if the eMMC or the RAM is working as they should, because perhaps this mistake happened due to the eMMC corruption, but I do not know how this can be done with Android, if you know how please tell me
Here is an update to whom it may be of interest. I bought this device S-Off with a custom ROM used, so I am considering giving it back to this person for being faulty.
But then here is something interesting, it appears it has been modified from Asian firmware to EU firmware, when I checked the IMEI online I got the following information: DEF00,w/o SIM Lock,HIMA#UHL_64G-C9#ASIA
It appears it is set to HTC__001 incorrectly, any ideas for what will be the corred CID and/or firmware for the smartphone? Maybe the incorrect firmware is causing this crash, and a fix will be just to revert to the Asian firmware.
Related
Hello,
Everything started when I did OTA update to Froyo...
My Desire reboot randomly when I use Nav, Maps, Browser, etc...
I tried to downgrade the HBOOT to 0.80 with a PB99IMG.zip package in order to get a clean place to do again the update.
The OTA update did not available after that...
So, I root it with Unrevoked, put a 2.2 official Froyo from Modaco with associated radio rom, install all my usual applications (Task killer, Reminder, Calendar, etc...) and try to use my phone again... with random reboots again
I made a swip of all that I could, re-install official Froyo ROM with radio, without anny application... and then, try it again... with random reboots !!!
Sometimes, it reboot in loop and then stay on the first HTC screen.
The back of the handset is hot when it reboot (but was more hot without any problem before, when I was under Android 2.1 and Nav activated).
The phone is not branded... and I use it with Bouygues Telecom.
I not use my gel case since I had the problem, as I though it could be an overheat issue.
And I have already read other topics about Froyo and reboots but not find something that could help me
Anybody could help me ?
i have the same issue. The only way to fix it is to underclock the cpu or open the back cover and blow at the bottom on the phone where the cpu is located.'
Or you can always return it to htc service (remember to flash original rom,radio and hboot and unroot)
The issue is that the phone got very hot and actually burned some stuff in there making a shortcircuit, before my phone could withstand over 50'C, Now it reboots at 40'C. I seriously think the phone has been fried!
I have exactly same problem.. it's very annoying!!! Anybody can help??
Maybe some app do it?
First it happened only in browser on some websites (after debrand + FROYO). I suspected Flash plugin.
But then it starts happened randomly everywhere - when reading PDF, use Navigation...
Even if i downgrade with PB99IMG_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed_txt.zip and then receive new OTA 2.10.405...
bug is still there!
I've used several custom roms like MIUI and RCMIX, but have always kept a backup of the phone's original software. Although these roms are great, they do have minor problems and the updates intended to fix them cause more minor problems...
anyway, Now that the official HTC DHD 2.3 update is live, I have gone back to the my backup of the original 2.2, and succesfully (by the look of it) downloaded the update. The phone reboots and only goes to a screen of the android logo with a yellow Exclaimation mark (!). I left it for half an hour til it was clear nothing was happening. Took battery out and it booted back into 2.2 without any problem.
I've tried undoing a lot of what was needed to get custom roms in the first place, but it hasn't been any good. (Unrooted, and used jkoljo's radio tool for an S-ON and Stock CID)
It's a generic DHD on T-mobile contract, but bought from Carphone Warehouse.
I've seen other posts about this, but I'm pretty sure they were in the wrong place and thus went ignored
Hi,
Have a look at this thread your not the only one having this problem - me too
http://forum.xda-developers.com/showthread.php?t=1081923&page=2
lendafender said:
I've used several custom roms like MIUI and RCMIX, but have always kept a backup of the phone's original software. Although these roms are great, they do have minor problems and the updates intended to fix them cause more minor problems...
anyway, Now that the official HTC DHD 2.3 update is live, I have gone back to the my backup of the original 2.2, and succesfully (by the look of it) downloaded the update. The phone reboots and only goes to a screen of the android logo with a yellow Exclaimation mark (!). I left it for half an hour til it was clear nothing was happening. Took battery out and it booted back into 2.2 without any problem.
I've tried undoing a lot of what was needed to get custom roms in the first place, but it hasn't been any good. (Unrooted, and used jkoljo's radio tool for an S-ON and Stock CID)
It's a generic DHD on T-mobile contract, but bought from Carphone Warehouse.
I've seen other posts about this, but I'm pretty sure they were in the wrong place and thus went ignored
Click to expand...
Click to collapse
+1 like @ericsson...also you can try this thread for solve it if you haven´t or loosed the recovery CWM...READ all posts
http://forum.xda-developers.com/showthread.php?t=1081595
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
Gonna try my best to give as much information as I can to make it easier for anyone good enough to try and help me with this. So I have an HTC One M9, from Sprint right here in the good old US of A, and it was working fine until I got the OTA Marshmallow update. At that point, apps started crashing like crazy (even after all were updated) and the status bar at the top of the screen and navigation buttons at the bottom would randomly disappear for several seconds after pressing the volume buttons, even after wiping the cache for both the system as well as the individual apps in question.
"No problem," I thought, "I'll just root it and install a custom ROM like I have with all my Android phones in the past." So I did that and tried Android Revolution, ICE, and ViperOne (all the latest versions), and every one of them had the same issues with programs crashing, the volume buttons messing up the screen, and so on. Actually, I couldn't even get through the setup wizards for any of them because those kept crashing too, and I had to use TWRP to rename the HTCSetupWizard.apk just to get to the home screen. Once there, my home button was inoperable, and no notifications or usual buttons like WiFi, Bluetooth, etc appeared when I pulled down on the status bar (which I discovered is what Android does if you don't complete the setup wizard).
At this point, I thought, "Well, maybe it's just a problem where my phone doesn't like Marshmallow for some reason. Let me try downgrading to Lollipop and see what happens." So I got the latest Lollipop versions for each of the aforementioned Custom ROMs, and they all ran smooth as silk, which tells me it's not an issue with faulty or damaged hardware. Only problem was that mobile data wouldn't work, on either LTE or CDMA settings.
I tried changing network modes, popping my SIM card in and out and rebooting in various combinations, but none of it worked. I couldn't even get into APN settings since the phone couldn't seem to detect my SIM card and had the APN menu greyed out. I thought I might have somehow damaged the SIM card with all the time I spent screwing around with the phone, but just to see what happened, I flashed a Marshmallow ROM back onto the phone and, sure enough, LTE service was right back.
I did some more research and saw that the issue may lay in the fact that the firmware (which is currently OS version 3.41.651.4) is not usable for Lollipop OS versions, and since my phone is S-ON (and I'm really not interested in spending $25 to S-OFF it), I'm not able to downgrade the firmware or, I assume, the radio firmware (if that's something you can even do separately from the "regular" firmware. Currently version [email protected]).
At this point, I'm really not sure what to do, and could use some guidance. I feel like my options basically boil down to the following:
1)Find a way to make Marshmallow ROMs more stable, possibly by reinstalling the firmware or some other method someone here might know that I don't,
2)S-OFF my phone, downgrade my firmware to something Lollipop can work with, and try a Lollipop-era ROM (not ideal), or
3)Go back to stock and hope Sprint pushes down an update my phone can use.
After going through all that, does anyone reading this have a recommendation for which of these options would be best (and how to go about them), or possibly offer other ideas I haven't come up with during the week and a half I've been researching and trying to fix it myself? I'm not hellbent on any particular option, I just want my phone to work (all of it) without constant crashes and glitches. Thank you to anyone who read all that and is still moved to offer help!
If you can run lollipop based roms you'd be on Lollipop firmware.
If you're going to mess around with aftermarket software you need s-off. If you don't s-off then you are risking unrecoverable bricks.
Sent from my HTC One M9 using Tapatalk
Okay, so if I'm on Lollipop firmware, would it stand to reason that that's why I'm having trouble running Marshmallow ROMs, including the stock ROM from Sprint? If so, what's the best (and safest) way to update it?
Hi everyone,
Yesterday night my battery unexpectedly drained out (maybe automatic update but cant be sure).
Since then, all of my apps, especially sense home and Chrome, keep crashing ("Unforunatley, <app> has stopped" message) .
steps I've tried:
- Resetting the device
- Disabling all but the essential processes
- Running on safe mode
- Factory Reset (Twice!)
- Wiping cash
- Using RUU EXE (obviously didnt fit my device as its all US RUUs in HTC.com)
Also, after wiping the device, im getting the Software Update prompt for Sense & a patch (fixes a bug in prep for the new software version 4.28.401.3) but both fail during installation.
Even in the rare occasion where i can move on to the 4.28.401.3 installation, the device reaches 25% and then gets to the red exclamation mark (followed by a hard reboot).
Device specs & info:
HTC M9 (unbranded) bought in the middle east
Android version 6.0
Sense Ver 7.0
Software ver : 3.35.401.32
Baseband : U11440792_97
S-On, locked, didnt change anything in that area.
Please help, I have resorted to using an old iphone I had lying around in the house, it doesnt get much worse than that :crying:a
Please read the ReadMe thread and try the correct RUU for your phone. You might want to take a look at the FAQ and get some information about the dead nand issue, as well, since you might be suffering from it.
However, it's impossible that your phone offers you an update to 4.28.401.3 if you're really running 3.35.401.32, at the moment, since OTAs are incremental and you would need to update to 4.14.401.7, first.