I was upgrading my radio last night and power went out in area. The device now freezes at blue imate logo page. Will not boot up. When I hard or soft reset it still stops at blue screen. Can not get into bootloader. XP says it does not recognize the device. ActiveSync does not connect.
Screen says "No GMS". D 1.30 .76 WWE. Just out of warranty. Any help would be appreciated.
cboy!!!
cboy77 said:
I was upgrading my radio last night and power went out in area. The device now freezes at blue imate logo page. Will not boot up. When I hard or soft reset it still stops at blue screen. Can not get into bootloader. XP says it does not recognize the device. ActiveSync does not connect.
Screen says "No GMS". D 1.30 .76 WWE. Just out of warranty. Any help would be appreciated.
cboy!!!
Click to expand...
Click to collapse
I have sent you a pm, that will correct your device. Please check your pm's...
Take care,
-Jwrightmcps
Jasjar Problems
Went in and restored the DOC to original layout. Have been trying to load Original OEM ROM (Jasjar WWE 1.30.76). Keep getting Country ID Error.
Any assistance would be appreciated.
Thanks in advance!!!!!!!!!!!!!!!
cboy77
Hi all i am new to all this i tried to load a newer rom on my Imate it had an error and froze did a reset and now it only comes to the 3 colour boot screen i have tried a hard reset but no luck and have downloaded the offical rom again i can get into the bootloader screen by pressing camera button and on and connect with the usb the thing is how do I load the rom the Program"RUU program" says u must have a active sync connection and it will not work in the bootloader it says usb in the left conner but active sync will not work is there any other program that doesnt use active sync to load the rom to my phone i have been reading the forum and seen similar problems all with the reply load wizardlove cant find the it all the links are broken or doesnt excest I need to get my phone running asap and if i send it in it will only be returned inn 6weeks they say I am from south africa and the guys here can be a lot of help coz the know nothing so if anybody can help me please it would be great thanks
Which is your device a G3 or G4 ? post the IPL/SPL...? of the phone to determine the version. As far as it gets to bootloaders (tricolor screen) you are safe,its just a bad flash,nothing to worry,you'll soon have it working fine.
Which rom were you trying to upgrade to ? and what exactly were you doing.First, is your phone SIM/CID unlocked,if you were trying to upgrade to a latest wm6 rom,its essential to have the phone CID unlocked
Secondly,while in bootloaders, Activesync doesn't work,you got to have a working OS on the phone to sync with activesync,but when in bootloaders and usb appears in the bottom of the screen,you can flash the rom.
Cheers!
K Jam hangs at blue screen
Hi to all,
I have a K jam more then 1 years old. Now It is giving some probem. There is no display but only light in the screen but I make call and recieve calls!.
First time when problem arised. I pressed 3 battons(2 left side and 1 up side)the screen will became perfect and when I remove the battery & reinserted, the problem arised again. When I asked some 2 to 3 mobile service mens, thay told that there is a problem with OS (By reinstalling the OS it will be repaired). I think probem is with the strip connect motherboard to the LCD, that could be cuted but service mens told no, it is problem with OS.
Where I can get the OS, WM5 is preinstalled in it.
Still it did not open the mobile. Please help me
Many Thanks for all
Srikanth.K
hellol i m facing the same problem when i start my imate k jam it does nt boot to windows n stopd on three color screen wht to do now help me plz to sort out
I feel your Pain! im in the same boat the three colour screen! all my Imate only gives
me IPL 2.16.0001 an SPL 2.16.0001 not even an OS
i downloaded wm6 from here and i followed some step of senior member of these site.now i have a problem.when i upgraded my mobile restart after booting and again restart so i am in serious problem.what can i do now.any help.
my imate k-jam ipl 1.01 and spl is 1.06
please help me
Hi,
My diamond was water damaged a while ago, I let it dry out for a couple of weeks and it did not work, I bought a new diamond and tried the battery in my old one and to my amazment it started up, well to the touch diamond screen anyway, it didn't display any red writing and the sreen stayed on but went black after that. I though the radio must have been gone so put it in the bootloader and tried to flash the same radio I had before 1.17, the white screen came up and all went fine but still the same problem!
I really need the data on my internal storage and so need to at least be able to read that. I don't care about it working forever thats why I bought another one as a doner!
Could someone please tell me what happened and how to fix it! Why does it not get past this?
Thanks.
Also I have hard reset it, reflashed the original ROM successfully, reflashed hardspl and reflashed the Stock SPL but it still does the same!
In case it helps the bootloader says:
DIAM100 MFG 64M
SPL-1.40.OliNex
MicroP-Diam (LED) v11
PSOC-Wrong Platform(v0x0)
What does that mean?
I guess the water just bricked your device,
you'd better throw it away i think
there's one posible solution, go to your phone's store and ask if they have some machine to acces the internal storage. (something like this has to be alive somewhere)
Goodluck
MK.
I don't think it's bricked because it goes into the bootloader just fine. However there is something wrong with the firmware. Bricked normaly means it doesn't turn on at all!
Please someone help, especially the last line on the bootloader sounds worrying!
I am also having this problem, but I have not had water damage. I ran outa main memory and it froze and now I am having this problem. Some one told me it maybe caused by a bloated rom? I donno what that means. Any help would be great!
try radio 1.13
Hi everybody!
First of all sorry for my not good english, but i think this is the best community for desire and android in general, so i decide to post here.
I was using a desire (NoBrand, PVT4 20000) with RCMixHD (s-off, CM7 partition table, latest radio 5.14)
I wanted to return to default ROM, so i downloaded the latest RUU, i begun the process but something goes wrong! while the installshield was flashing the system, the green bar process on the phone became red and the ruu installation has reported error in flashing, when i removed the usb cable, the phone goes in a similar hboot interface where there was something like a log of the flash, everything was "OK" except the flashing of /system.
I thought may be the cm7 partition table that haven't got space enough for the original rom? i believe that the ruu.exe also restore the partition table
Now when i power on my desire there is a triangle with a "!" and 4 "!" in the respective angle.
if i try to start ruu flashing again everything is the same.
HELP MEEE!
i retry flashing after pc reboot and everythis is ok!!!!
fiuuuuuuuuu
sorry for the useless thread but i got scared
hehe ca daca iti crapa zona de boot si dupa cum obs dupa user ca esti din c-ta ajungeai cu el pe la mine
Regards!
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
did you install xposed? Rooted? Any other modifications?
jollywhitefoot said:
did you install xposed? Rooted? Any other modifications?
Click to expand...
Click to collapse
Nothing, had it out of the box for about an hour.
Hugglester said:
Nothing, had it out of the box for about an hour.
Click to expand...
Click to collapse
return it then. something isn't right.
Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
Hi there.
Yes I have encountered this issue. But I'm not sure if I had it from the box or I got it after the update.
When I got this issue and my phone started boot looping, the only way I tried to recover from it is by hooking up the charger and I got it too boot up, it showed an error report and I sent the error report to HTC.
So the phone works normally after it boots, but is this software related? Should I wait for the next update or also replace my phone, it's so hard after setting up everything to again go through the annoying process of getting a replacement or a fix just to find that the issue still happens or is caused by the update.
UPDATE:
Ok so after testing and trying to recreate the issue I have discovered that when trying to do a normal restart or power off the phone while the phone is on battery this issue doesn't happen.
The last time it happened is when my phone battery drained and powered off then I hook it up to the charger and went to sleep, when I woke up I removed the phone from the charger and powered it on then the issue happened and the phone went into a boot loop, tried restarting with no luck then I figured I would plug in the charger again, then it booted up normally. (Unplugging the charger from the phone makes a weird metallic noise, so I checked my USB type c port and it wasn't lose or rattly). Anyways when the phone booted up it had 99% charge while I was certain it should have been full at 100%, I waited for it till it got to a 100% then unplugged it.
So I tried my best to cover how this issue happened to me, and if it happens I would get the error report thing that the phone had unexpected boot or something like that.
Could it be because I'm using adoptable storage?
Is it hardware or software related?
Could it be a corrupt file or something in the file system?
Or I just need to wait for the next update?
So my issue came right out of the box. I was trying to get everything transferred over from my old HTC device and about half way through downloading my apps the issue started for me. Tried similar steps to you as well with charging the phone and it was only off charger when I had the issue. I am returning the phone and getting a new one as of now. Not sure what else to do to fix it.
p1r8t3 said:
Hi there.
Yes I have encountered this issue. But I'm not sure if I had it from the box or I got it after the update.
When I got this issue and my phone started boot looping, the only way I tried to recover from it is by hooking up the charger and I got it too boot up, it showed an error report and I sent the error report to HTC.
So the phone works normally after it boots, but is this software related? Should I wait for the next update or also replace my phone, it's so hard after setting up everything to again go through the annoying process of getting a replacement or a fix just to find that the issue still happens or is caused by the update.
UPDATE:
Ok so after testing and trying to recreate the issue I have discovered that when trying to do a normal restart or power off the phone while the phone is on battery this issue doesn't happen.
The last time it happened is when my phone battery drained and powered off then I hook it up to the charger and went to sleep, when I woke up I removed the phone from the charger and powered it on then the issue happened and the phone went into a boot loop, tried restarting with no luck then I figured I would plug in the charger again, then it booted up normally. (Unplugging the charger from the phone makes a weird metallic noise, so I checked my USB type c port and it wasn't lose or rattly). Anyways when the phone booted up it had 99% charge while I was certain it should have been full at 100%, I waited for it till it got to a 100% then unplugged it.
So I tried my best to cover how this issue happened to me, and if it happens I would get the error report thing that the phone had unexpected boot or something like that.
Could it be because I'm using adoptable storage?
Is it hardware or software related?
Could it be a corrupt file or something in the file system?
Or I just need to wait for the next update?
Click to expand...
Click to collapse
Hugglester said:
So my issue came right out of the box. I was trying to get everything transferred over from my old HTC device and about half way through downloading my apps the issue started for me. Tried similar steps to you as well with charging the phone and it was only off charger when I had the issue. I am returning the phone and getting a new one as of now. Not sure what else to do to fix it.
Click to expand...
Click to collapse
Hi there, i think the newer update fixed the issue for me. Hope this helps.
Any news?
HTC One M9 cihazımdan Tapatalk kullanılarak gönderildi
same issue for me, just made an update and then got the bootloop.
even ****tory reset didnt help
any idea what to do.
phone never rooted
Your phones right out of the box and on the stock rom should be in perfect working order. If not, I would send it back for a replacement pronto. Don't wait for an update.
you guys got an external sdcard in the phone?
It's reported by a couple of users that the boot up process took a few cycles for them till it booted.
It was caused by a corrupted sdcard. Try to take the external sdcard out and see if the issue is fixed.
If yes, try to format it with the overwrite option in the "SDFormatter" program..if that does not help. get a new sdcard.
El mismo problema de bootloop después de actulizar
me ocurrió el mismo problema después de actualizar mi HTC 10, luego de actualizarlo al Android 7 llegó una nueva actualización luego de completada la descarga procedió a instalarse la actualización y aquí quedo el teléfono en bootloop por más de una hora, se soluciono el problema conectando el teléfono a cargar la batería después de pocos minutos el teléfono arranco correctamente. Al completar la descarga de esta ultima actualización el teléfono tenia más del 90% de carga aun así se generó este problema de bootloop.
I am experiencing the same problem. The phone has the latest update installed. (not rooted, bootloader locked).
Initially soft (backlit) keys weren't working, so i tried restarting and it never booted up as its stuck in boot loop. I cannot go to any recovery modes.
Its so disappointing ! I'm in India but I bought this phone from middle-east on December 2016 and I have to sent it back there for warranty claim which will not happen very soon.
Have anyone found a solution for this problem ??
jeraldsm said:
I am experiencing the same problem. The phone has the latest update installed. (not rooted, bootloader locked).
Initially soft (backlit) keys weren't working, so i tried restarting and it never booted up as its stuck in boot loop. I cannot go to any recovery modes.
Its so disappointing ! I'm in India but I bought this phone from middle-east on December 2016 and I have to sent it back there for warranty claim which will not happen very soon.
Have anyone found a solution for this problem ??
Click to expand...
Click to collapse
I had a similar issue....backlit keys stop responding, a few days later the phone ran out of battery during the night and I got the boot loop when I turned it on the morning after. I can just get into the bootloader (no normal boot, no recovery, no download mode). An purchased in the US but I am now in Argentina .
Same here
I had the same issue. I factory reset a couple of times. I even rooted and installed custom ROM. But it still would do it (though much less frequently). I ultimately exchanged it with a warranty phone with my carrier. Crossing my fingers that my phone will stop doing this.
Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
I have same promlem
I had the same problem... After the last update, it entered a BootLoop... It was pretty difficult to even shut down the phone! It got so hot I was afraid it's going to burn out its motherboard...
Mine is not rooted or anything of the sort...
Eventually I managed to shut it down...
Went to claim my warranty... They opened it up... Don't really know what they did... But before throwing it in the garbage... I tried one more time to power it up... And it worked !
I've stopped all the updates since and I never let it run out of battery.. It's clearly a software problem.
And it's not related to HTC only. Samsung has it too. I know for a fact that the S8 has it....
I am having the same problem , has anyone found a fix ?
I had the same problem with mine. Bought it used from Swappa and out of the box it would randomly reboot. I also noticed the phone was abnormally hot doing nothing on the lockscreen or homepage. The random reboots quickly escalated to bootloop. Unfortunately I had to return it. I think the phone during initial stages of booting up relies purely on internal battery power, regardless if it's plugged into AC power or not. So, when the internal battery is dead, in the sense that it can no longer provide sufficient power even at a fully charged state, then you get stuck in the eternal bootloop.
I believe the only fix is to replace the battery with a new cell. However, due to the complexity of the tear down, I literally could not find one shop that would be willing to do it. Otherwise, I would have sucked it up and paid to have a new battery put in.
j to the 4n said:
you guys got an external sdcard in the phone?
It's reported by a couple of users that the boot up process took a few cycles for them till it booted.
It was caused by a corrupted sdcard. Try to take the external sdcard out and see if the issue is fixed.
If yes, try to format it with the overwrite option in the "SDFormatter" program..if that does not help. get a new sdcard.
Click to expand...
Click to collapse
I've been encountering exactly this problem. Anywhere after 40% it'll just die and get stuck in a boot loop until I hook it up to a charger. If the boot loop happens multiple times before I manage to get to the charger, widgets stop working and I'll have to wipe the cache. Sometimes when the phone dies, it'll have said 20% or so before dying, but after hooking it up the charger it'll claim 2%.
So the battery or battery level sensor ain't great, that's a given. But 40% and dying? Something's wrong.
So after it completely died and refused to turn on again because it went through the boot loop until it just stopped trying, I decided to try this trick. I removed the SD card, tried everything to turn it on, finally getting it going by long-pressing volume down and power, went to recovery mode, rebooted the phone and it's working again. For now.
I'm not sure whether the SD card removal will fix the entire problem (or at least limit it to a ****ty battery) but I'll report back if that's the case. At least it got it to boot again, so thanks for at least giving me a strand of hope