Hi guys,
I've been having a few issues with my phone - thought it was due to some custom roms i was using,,,,,butmaybe not....
Recenty the phone has been rebooting on its own, at random times. The most recent one happened in the night, and now the phone is completly dead. I can not even get the bootloader screen.
Any one got any ideas, i guess it needs to go away, but would like to clear the personal info and work stuff off it. Guess i should also put stock rom back on.
Anyone had this before? could the bootloader (olinex 1.14) be currupt?
Advice would be welcome.....
update
after leaving the battery out for a long time, the phone boots, but crashes before finnishing and then wont start again.
I'm worried that if i send this back they could see that i have a non htc rom installed. Anyone had any experince wth this?
Having the same issue. Flashed Duttys ROM, then it starts. But same thing with L26. Think its the HSPL 1.56?
Which Bootload do you usw?
Frank
Did you have these issues with the stock ROM? When did the problem start - was it after flashing to a custom ROM? Have you reset twice after flashing the ROM?
Eventually my Phone completely died. I sent the device away for repair - HTC replaced the main board. When i got it back, the phone worked ok for 3 hours and then started to reboot again. Sent it back a second time, the main board was replaced, and the FPC connector was re-seated. Phone has been ok for 1 week now.
Suggest that you re-flash to the stock ROM and SPL. See if it still has the problem - if so, send it back to HTC. Here in the UK the turn-around was 6 days from notifying them of the issue to receiving the phone back.
It will not charge, turn on, connect to pc even while using power+back button.
It's around a month old, i flash it 2 times with Floyo v0.20 using xrecovery. it has been dropped about 4 times... i attempted to install something which corrupted the os. It then crashed and i removed the battery then attempted to turn back on and it turned on a few times but i was unable to access xrecovery pushing back over and over again. I then attempted to flash using my pc and it came up with some errors and now the phone will not even turn on. I used the X10FlashTool thread that is compatible with the x8. Is the phone completely dead or is there a way to recover it.
Thanks in advance.
NOTE: These errors on the flash program wasn't while it was flashing. It was while it was trying to connect... I don't think the software killed it.
Sorry m8 to here this I have done the same and my motherboard cook it self I hope it not the same for ur phone if so you need a new board m8
my civic
I hope not too, i guess your most likely right .
Try eBay for a bricked phone so it nice and cheap and look online on how 2 replace the screen it show u how to get the motherboard out so u can replace it with the bricked phone.PS I have seen the x8 going for a 5pound becouse it was brick I got the bird a bricked x8 for 20pound
my civic
Hopefully one goes on there soon since i couldn't find any... the phone is on contract so i might be able to get it replaced since i haven't had it that long and really i've done nothing to kill it.
Try to recover it using PC Companion or SEUS
I hope it helps... Good luck bro!
I'm not sure that will work since my pc doesn't even detect it's there.. i don't eve get the sony ericsson screen when i try and turn it on.
If you want to reinstall firmware with SEUS or with FlashTool you don't need to turn phone on. Try to look here maybe this will help you:
http://forum.xda-developers.com/showthread.php?p=12442257#post12442257
I've attempted this also, it doesn't detect the phone. I will give it another attempt in a moment... FINGERS CROSSED. Other wise i will try and get a replacement.
Update: I'm now sending it away for repair, i've tried everything i can find to repair it... It's obviously completely DEAD!
m8 try holding back key(the on on the right )and plug in the usb in at the same time seus should find it just did it 2 my old phone to try and help u
sooooo hold back button and plug in your usb while holding the back key untill phone driver install just done it less than ten min ago ( my old phone didnt turn on no se logo or anything i think this is the same as you and it may help you ps it take a bit of time like 2min to start but it work back to factory 2.1
Okay i will give this a try, Hopefully it recognizes that it's plugged in if i wait.
Mine doesn't even light up when plugged in to the charger or pc.
This didn't work either, i think it's completely dead since it does nothing at all.
I'm sending it away for repair, will they know i used a custom filmware though it's dead?
erm... maybe use pc companion?
I have the same problem. I got my phone back from repair (mainboard was changed) and decided to install the floyo v0.25 ROM. Installed it succesfully, but then my phone freeze and I took the battery out, same as he did also. After that my phone was dead, the SE logo wont appear. I tried to repair it with SEUS, but It didnt change anything.
Flashtool didnt work for some reason, said that I should turn my phone on and enable something..
I installed that rom just before mine broke...
i will stick with 0.20
so 0.25 is bricking everyones phones. Good to know ._.
If I manage to fix my phone somehow I will stay on original firmware. Thanks to the 0.25 developer
One thing ive seen you all state that made it go kaboom more or less is that you remove the battery, also i belive it isnt the FW you put in since im using 0.25 without any hickups or any bugs at all (well battery icon <60% but its fixable).
So don't blame the developer, you put this in with full knowledge it could brick your phone.
Try and think about what you did and what went wrong, because i seriously doubt that you did it 100% like you should, Backup org ROM->Restore 0.25 ROM-> wipe cache->factory reset->reboot into 0.25.
Also on a side note, dont be afraid to root and put in custom ROM, learn something from it instead. every "negative" experience is GOOD experience since you learn what NOT to do then
Best of luck to you all in the future and may the custom ROM gods be with ya !
Mine is partly dead...
Hi all,
A few days ago installed the newer floyo v0.25. For a day or 2,donno how long,but till my battery flatted out completely,did not have any probs with the rom.Than after recharge,think it was not a full recharge,turned on and left it on till next morning. Still everything ok,started music app and could not turn off music (pause) as the touchscreen didnt respond. Nothing helped yet so far to get it working properly.Did a restore,full wipe did a Seus update back to stock Eclair. Now at this point lemme mention that I`ve made service tests and everything was in mint order Yes the touchscreen too.(!) Started to be happy,could do a few things like making calls,navigating within menu,then it just went back to its sad state.Cannot even unlock the screen,as there is no reaction whatsover...No matter which backup am restoring,all of them reproducing the error. Now 2 things I`ve learned so far.
1.) when I installed (restored from xRecovery) floyo v0.25, did an advance restore and restored system only,as it was mentioned in other post,its possible,because I am upgrading from floyo v0.20
2.) did not make a full wipe AFTER restored custom rom.
I donno if these 2 mistakes lead me where I am now,just hoping I need not a new motherboard or dont have any hardware issue.
Sorry for the long post,hopefully someone can learn from it,also could help me to move forward,as am still working on it to make the touchscreen back in properly.
I also had the music issue and touchscreen not responding. After removing the battery and rebooting it worked at first, but then the phone froze and didnt want to reboot after I removed the battery the second time.
There is really no sollution to fix the problem?
So that filmware killed it , thing is my phone was only just over a month old...
I've sent it away for repair will they know i used a custom filmware on the phone?
Since it's dead really they shouldn't be able to find out.
Hello all,
This is yet another bootloop story, although I haven't found anything quite like it yet, hence the idea to post it here for reference and in case some of you have interesting ideas to explore...
This is gonna be a bit long, but TL;DR: After my phone got "spontaneously" stuck into a bootloop, I find that only the stock 4.2.2 rom works, and no other.
So, tuesday I get back home with an empty battery and a Nexus 4 (running latest OTA) that has switched itself of after a day of somehow intense usage. No worries, I plug the AC adapter, let it charge for a bit and switch it back on. Booting seems a bit long, but I have to take care of a few home chores so I let it do its thing before coming back to it a few hours later. Only to find it still displaying the animated nexus logo. After a few switch off/switch on cycles, I understand its pretty stuck and I need to be more radical about it. So I enter the bootloader menu, and OEM unlock the phone (I had never needed to do that) hoping the full wipe associated with that will clear things up.
Well, it didn't. So I guess I'll need to flash a stock rom, and so I do. Since 4.4 is available on Google's stock roms page I try that, the animated logo changes but the end result is the same. So I try again with the latest JB (4.3) and still the same result. I get more than a bit frustrated but it's late and I need some sleep.
The next day, I call Google's warranty desk in France. They tell me that since the phone fell a few month ago, they cannot take it under the warranty program, and so I have to ask LG. Knowing there's no reasoning that will get me past the clerk that answered the phone I hang up after saying I'll get back to them via snail mail. Which I'll probably do soon, because I'm very disappointed with the way that warranty desk works.
Once at work, everytime I have a few spare minutes, I try to reflash with a new tool just in case it does more than automate what I did manually (nexus root toolkit being the one I tried most). It doesn't change a thing and my phone is still a nice animated paperweight.
I don't know why I ended up trying that, but I finally tried flashing the original 4.2.2 rom, and lo and behold, my phone finally got to the SIM code screen ! Everything worked nice after that, so once back at home, I go for the offered OTA upgrade to 4.3. Well, guess what, back to paperweight. Before reflashing 4.2.2, I took the time to flash CWM and activate adb by modifying /system/build.prop in the 4.3 image. This showed a recurrent problem with "system_server" segfaulting at launch (and it might have been caused by hal_sensors_get_list not returning anything, I have no clue). Trying the same on 4.4 yielded the same result.
Back to 4.2.2 and everything works fine, but I get nagged by the OTA notification, and more than that I'm wondering if there's any hope I might understand and fix the problem with my phone.
So, ladies and gentlemen, any clue that would help me is very welcome !
I plan to try a CM rom this week-end to see if it has the same problems as the stock one, but I have little confidence it doesn't. My guess is I have a hardware problem that's non-critical except it triggers a bug in 4.3+...
Thanks for reading !
--
Alain Perry
Same case, mi phone is totally stock and stuck on logo
KRT16S: no luck
I only had the time to try KRT16S this week-end, and this latest update doesn't change a thing. Same symptoms. So I guess I'm stuck on JB 4.2 for the coming week...
Hello.
I guess I am done with my S4(i9500). Too many strange problems since past one week.
So, I was on Halycon ROM and one fine morning, phone restarted and all apps started optimizing again. Ok no issues.
But now I noticed, whenever I restarted, 2-3 apps optimized everytime.
So did a clean flash and installed Cri5.
Now restored some apps and then 1 app optimizes on boot now. Is there a way to log which app is causing the problem?
There's one issue. Another issue is phone restarts randomly when gets up too hot and gets stuck on S4 boot screen. Have to remove battery and restart to boot it up..
Another issue is that the phone isn't being recognized by my PC. Tried Kies. Tried everything. I don't get the MTP menu when I connect the power cable.
Oh, and another issue, I guess my SD card is infected with a virus. Any recommended free antivirus for android?
Thanks if you could help me with one of the aforementioned problems.
Regards
Sounds like you need to flash back to stock in order to rid yourself of the software issues. If the issues are present on a stock ROM, it could be a hardware problem.
Hi!
So i've recently had some issues with my Samsung galaxy s8+
With the introduction of the new Pie Beta update i thought it would be cool to try it out!
I had to downgrade my firmware and so i did via ODIN.
This failed initially duo to a bad cable, i quickly replaced with OEM one.
Alright! We are able to boot into the OS, i stuck my SD card in the phone and updated its firmware succesfully.
HOWEVER; My phone would reboot once in a while out of nowhere and i figured i was on a Beta that might cause issues
started removing all of my apps in hopes it would help. Unfortunately in either safe mode OR clean factory wipe.. I was still running into reboots.
Alright ok, eventho no one on the forum complained about reboots.. I'll take my loss and i'll just flash back to stock..
However; it seems like the phone just freezes up now in everything!
Freezes up in Download mode; Freezes up during boot of new OS
i was able to reflash via ODIN by the way it just wont let me load into the OS. I've tried different ROMS
I can't wrap my head around it!
Should i just take my loss and buy a pixel 3 ? i was hoping to extend my contract with the new Samsung Galaxy S10+ but i can't do without a phone for a month.
Thank you in advance!
UPDATE:
I've succesfully been able to load into the OS at the moment. Let's see how long this lasts!
Aaand about 6 Minutes later i get a reboot
Yeaaah, it's dead.. After rebooting more and more frequent
It doesn't turn on anymore.
GG