I recently finally got a ROM to my HTC one successfully...I am on the Cyanogen mod.
However, like the ROM i istalled previously, my phone keeps rebooting randomly after a couple minutes or just a minute of being on and operating flawlessly.
any fix to this? Ive read around, i dont think this is the same as bootloop?
Also, my phone has no service or ability to activate my phone after, how to on that?
ONE THING:
I may/may not have (i did) accidentally flash a ROM designed for a GSM phone to my phone....COuld that have caused this problem???
Switchback802 said:
I recently finally got a ROM to my HTC one successfully...I am on the Cyanogen mod.
However, like the ROM i istalled previously, my phone keeps rebooting randomly after a couple minutes or just a minute of being on and operating flawlessly.
any fix to this? Ive read around, i dont think this is the same as bootloop?
Also, my phone has no service or ability to activate my phone after, how to on that?
ONE THING:
I may/may not have (i did) accidentally flash a ROM designed for a GSM phone to my phone....COuld that have caused this problem???
Click to expand...
Click to collapse
This could indeed be your problem
bigdaddy619 said:
This could indeed be your problem
Click to expand...
Click to collapse
so should i relock and reflash stock RUU and rom to it?
Edit: It works, it seems. service is back and it isnt rebooting (yet). Time to try reloading the correct ROMS
Related
Hey guys,
I upgraded my G1/Dream from an older cyanogen version, to the newer one 4.2.15.1
and now for some reason my phone keeps restarting Any reason why ?
Can you please tell me how to fix it?
I've taken battery out & Also 'green+home+red' . Same keeps happening.
It restarts when it wants, can be 2 minutes, 10, 30.. but lately ever 1 minute or so..
What can I do?
Bump
bump
Anyone?? please
I'd recommend a full wipe and reinstall of your desired rom from scratch. Sounds like kernel panics to me.
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Tone-E said:
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Click to expand...
Click to collapse
Why would you completely unroot and reroot? That's just too much work.
Wipe, and reflash. Also, a few apps have a problem with custom ROMs, try disabling apps that run in the background one by one until you find that your phone no longer reboots.
However, if you didn't wipe, I highly recommend that as the person before me said.
Hello, just today I've recieved my new google nexus one, after charging the battery for 2 hrs, i tried to start the nexus one, but when nexus animation starts it's converted into blue instead of coloured.
then my device reboot without touching anything,
it still doing like this 2-3 times then hang on the nexus coloured symbol.
after a while i tried to start again it was the same
another try, it worked and start android system , and after 4 minutes it restarted and doesn't boot the system again, just restarting
i don't know what's going wrong with it.
Please Hellllllp
i highly dought you animation turned blue on a new phone without the bootloader unlocked and a custom rom on it.
Actually, YES, my friend unlocked it and put an Arabic supported ROM, I tried to change the ROM to the original and still the same
Well seems like he has flashed Cyanogen for you too.. Try reflash it and se if that helps.
I tried to reflash the ROM, I have the same problem everytime,
janat83 said:
I tried to reflash the ROM, I have the same problem everytime,
Click to expand...
Click to collapse
Did you try to wipe first?
Redestwing said:
Did you try to wipe first?
Click to expand...
Click to collapse
yes, I've tried that as well, nothing changed
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...
Hi guys, as a lot of people now confirmed to me that it solved their problems complete when they switched to the GPE Firmware i think it is a good thing to write all that in a little own thread so not every user has to spam for the same bugs in all Android N Rom Threads.
First of all, YOU NEED TO HAVE S-OFF to flash Firmware files!!!
Using the GPE Firmware can solve the following bugs (thats no guarantee there can still be bugs in the Rom+Kernel):
-In Call Sound problems
-Camera Problems
-Mobile data problems
-wifi problems
-battery problems
Those bugs where already existing when the first Android 6 (M) Roms came to our M7 and with Android 7 (N) its still the same. But, those bugs are mostly present while using a Custom Rom on a Sense Firmware and they are nearly complete gone when you use the GPE Firmware.
Thanks to the Slim Jim Guy we have everything we need already here in the Forum. And please be that nice just give him a thanks for his thread as it helps us all a lot. Here is his Post and here is the direct download of his complete prepared Firmware without recovery and boot img GPE Firmware Download. It will delete nothing from your device, just changes the Firmware.
This Firmware is complete different to the one from HTC and is newer because Google provided much longer official updates for the m7 GPE than HTC did for the usual version.
Changed OP for complete Firmware file from Slim Jim Guy (thanks to maciclazar for this information)
just a little bump as a reminder haha
So if I understood right, it's better to have gpe firmware if I have a nougat ROM even if my phone is not GPE?
JustElisha said:
So if I understood right, it's better to have gpe firmware if I have a nougat ROM even if my phone is not GPE?
Click to expand...
Click to collapse
You can flash the GPE Firmware on any device thats not from a provider with CDMA radio like Verizon devices.
saturday_night said:
You can flash the GPE Firmware on any device thats not from a provider with CDMA radio like Verizon devices.
Click to expand...
Click to collapse
I just have to flash it in twrp or S-OFF is required?
JustElisha said:
I just have to flash it in twrp or S-OFF is required?
Click to expand...
Click to collapse
Like written in OP "First of all, YOU NEED TO HAVE S-OFF to flash Firmware files!!!"
@saturday_night I was using that firmware from Santod040's thread for months until I realised it was not full firmware.
The full GPE firmware is located in this post by Slim Jim Guy. It is full firmware containing hboot, radio and everything else and will turn you phone in full GPE device and the best thing is it fixes random reboots on nougat and marshmallow roms.
Edit: Never mind. Found the answer I was looking for.
maciclazar said:
@saturday_night I was using that firmware from Santod040's thread for months until I realised it was not full firmware.
The full GPE firmware is located in this post by Slim Jim Guy. It is full firmware containing hboot, radio and everything else and will turn you phone in full GPE device and the best thing is it fixes random reboots on nougat and marshmallow roms.
Click to expand...
Click to collapse
Exactly, link of post #1 is the black hboot 1.54 only
Would this work for Android N ROMs with the international variant? Running Xenon 7.1 ATM.
Not sure what's wrong. I've flashed GPE firmware, got a new battery, still phone does this awful thing Could be mainboard problem? How can I test motherboard?
Thanks
umbyka said:
Not sure what's wrong. I've flashed GPE firmware, got a new battery, still phone does this awful thing Could be mainboard problem? How can I test motherboard?
Thanks
Click to expand...
Click to collapse
What ROM are you using right now, how did you get S-OFF?
Yesterday I've turned back to stock GPE 5.1, hoping that it's a ROM problem, but still my phone shuts down by itself, even at 90%. S-OFF I gained a few years ago, in 2014 I think. Rumrunner if I remember right.
@umbyka are you able to completely drain the battery to zero, then, without powering the phone back on, connect it to a charger and let it charge to 100%?
93zx7 said:
@umbyka are you able to completely drain the battery to zero, then, without powering the phone back on, connect it to a charger and let it charge to 100%?
Click to expand...
Click to collapse
Yes, I'm able. So..I did turn back to 5.1 GPE, full stock, seems that, with this ROM, everything is normal. Didn't mention, that with all N ROMs the phone went so hot, that it was almost burning, but with 5.1 GPE it doesn't. I did this HTC said battery calibration, with both volume buttons + power button for 2 minutes also. Hopefully it's not a mainboard issue after all...
umbyka said:
Yes, I'm able. So..I did turn back to 5.1 GPE, full stock, seems that, with this ROM, everything is normal. Didn't mention, that with all N ROMs the phone went so hot, that it was almost burning, but with 5.1 GPE it doesn't. I did this HTC said battery calibration, with both volume buttons + power button for 2 minutes also. Hopefully it's not a mainboard issue after all...
Click to expand...
Click to collapse
How's the camera performance? How often does the purple hue come?
zeeBomb said:
How's the camera performance? How often does the purple hue come?
Click to expand...
Click to collapse
This is a hardware problem and not software related. When HTC made the first OTA Updates the device became too hot during the update process so that some camera modules got a little damage which caused this purple pictures. If it wasnt repaired under guarantee the only way for you to get this fixed is replace the camera module.
saturday_night said:
This is a hardware problem and not software related. When HTC made the first OTA Updates the device became too hot during the update process so that some camera modules got a little damage which caused this purple pictures. If it wasnt repaired under guarantee the only way for you to get this fixed is replace the camera module.
Click to expand...
Click to collapse
right...but what exactly would the camera fix be if i flash gpe?
So, I haven't been around for a while now, but I'll share with you the problems I have :
Even with GPE ROM phone shuts itself down sometimes even at 70% battery, sometimes it lasts till 20%. When it shuts down itself, turning it back on seems to get a problem. Normally it should get back on with all my settings saved, I mean background, ringtones, etc., but it starts with a message : Android is optimising apps..., and when it boots up finally, everything is gone. I mean background, ringtones, passwords. So, anybody has a clue what's going on?
umbyka said:
So, I haven't been around for a while now, but I'll share with you the problems I have :
Even with GPE ROM phone shuts itself down sometimes even at 70% battery, sometimes it lasts till 20%. When it shuts down itself, turning it back on seems to get a problem. Normally it should get back on with all my settings saved, I mean background, ringtones, etc., but it starts with a message : Android is optimising apps..., and when it boots up finally, everything is gone. I mean background, ringtones, passwords. So, anybody has a clue what's going on?
Click to expand...
Click to collapse
Did you clean flash everything including firmware? If yes, that sounds like a hardware damage
Hello guys,
Currently I run Android Revolution HD 93.0 by mike1986
HTC Sense Version: 6.0
Android Version 5.0.2
Recently dunno what happened, but my phone randomly stucks in the boot screen with the HTC logo and I need to restart it like 10 times till it runs properly again.
My question is, how do I install a new custom ROM when I already have this one ? Do I need to return to a stock ROM or something till I can flash a new one or ? I have no clue. Thanks in advance.
Btw. If any of you can help me find what causes this problem my phone to stuck in the boot screen I'll be more than happy.
I can't remember which app did this, but I remember receiving the notification on my phone to chose how to install the new update for this app, and there were 2 options
- Normal install
-Install through Recovery (recommended) and I think I clicked the Normal install option and since then the phone stucks randomly in the boot screen.
Neonskull said:
Hello guys,
Currently I run Android Revolution HD 93.0 by mike1986
HTC Sense Version: 6.0
Android Version 5.0.2
Recently dunno what happened, but my phone randomly stucks in the boot screen with the HTC logo and I need to restart it like 10 times till it runs properly again.
My question is, how do I install a new custom ROM when I already have this one ? Do I need to return to a stock ROM or something till I can flash a new one or ? I have no clue. Thanks in advance.
Btw. If any of you can help me find what causes this problem my phone to stuck in the boot screen I'll be more than happy.
I can't remember which app did this, but I remember receiving the notification on my phone to chose how to install the new update for this app, and there were 2 options
- Normal install
-Install through Recovery (recommended) and I think I clicked the Normal install option and since then the phone stucks randomly in the boot screen.
Click to expand...
Click to collapse
Do you know how to flash a ROM? Sorry for the question, but reading your post, I get the feeling that you're in the dark about flashing stuff. And that app that caused your issue i SuperSU.
donkeykong1 said:
Do you know how to flash a ROM? Sorry for the question, but reading your post, I get the feeling that you're in the dark about flashing stuff. And that app that caused your issue i SuperSU.
Click to expand...
Click to collapse
Yeah I've done it many times in the past on my old HTC Desire and now on HTC One by following step by step guides. However I totally lost interest in these custom ROMs and etc. in the past year and basically forgot everything, but when there's something urgent I always come back here to ask for help
However I think I fixed the stuck in boot screen issue by upgrading my TWRP to the latest version, no idea ... but now whenever I start the phone it turns on normally and there are absolutely no problems.
Neonskull said:
Yeah I've done it many times in the past on my old HTC Desire and now on HTC One by following step by step guides. However I totally lost interest in these custom ROMs and etc. in the past year and basically forgot everything, but when there's something urgent I always come back here to ask for help
However I think I fixed the stuck in boot screen issue by upgrading my TWRP to the latest version, no idea ... but now whenever I start the phone it turns on normally and there are absolutely no problems.
Click to expand...
Click to collapse
Great to hear that! [emoji106]