Hi guys, I am having a problem in my xt890, even with no modifications.
The thing is, it got stuck on the red logo, so I flashed the original rom again and it was alright, but then again in a few weeks the same problem happened and I did it again and again. It's the fourth time now, and the phone was fully stock, no modifications at all.
In this last time I unblocked the bootloader and installed CM11 to see if that works, but I'm afraid that the problem is in the hardware.
Does anybody knows what causes this? Is there any way to fix it?
Thank you
Related
Hello everyone, today I'm facing a strange problem
I was playing with my razr I (really good phone btw, which is rooted and UNLOCKED) and I had a random reboot and from that moment I can't do anything,
WHen I turn on my phone, the green light flashs and the screen says : Service Required Code Corrupt
I am not able to boot into fastboot, my PC doesn't recognize the phone either
I'm stuck ^^
SO if you have an idea i'm open
Thanks
What firmware was installed before your phone had bricked?
I was on jelly bean 4.1.2 stock french carrier
Try this. It can help.
http://forum.xda-developers.com/showthread.php?t=2184877
U1138 said:
Try this. It can help.
http://forum.xda-developers.com/showthread.php?t=2184877
Click to expand...
Click to collapse
Nop already tested, doesn't do anything but thanks
If I don't manage to repair my phone until tomorrow morning, I will go to my carreer shop and protest ^^
Hay guys I have exactly the same problem
nikitagu said:
Hay guys I have exactly the same problem
Click to expand...
Click to collapse
How does it happen for you ?
the update of ICS on JB
It seems like we are stucked on a weird brick......
Sent From My SlimBeaned Nexus S
yes, fully strange
metalmoot said:
Hello everyone, today I'm facing a strange problem
I was playing with my razr I (really good phone btw, which is rooted and UNLOCKED) and I had a random reboot and from that moment I can't do anything,
WHen I turn on my phone, the green light flashs and the screen says : Service Required Code Corrupt
I am not able to boot into fastboot, my PC doesn't recognize the phone either
I'm stuck ^^
SO if you have an idea i'm open
Thanks
Click to expand...
Click to collapse
i have the same problem
nothing?
I think your boot loader just got corrupted. Take your phone to a tecnical assistant. Your carrier won't do anything for you since you've an unlocked bootloader.
It will be just a waste of time.
I have the same "Service Required Code Corrupt" error after I tried to restore from a Nandroid Backup...
ohhh...
that sucks!!
Solution please
I have no
please you guys are the best to find a solution (
yes please
Me too, successfully downgraded JB to ICS, all was ok, made nandroid backup and boom.
Hi guys,
I've been looking around a bit but unfortunately I did not find any solution to my problem
Well, I'm a newbie and I got my desire c last december.
Basically since I got it, I've been flashing loads of different roms and never had a problem with it.
Yesterday, I wanted to try the cm10 and I started having difficulties: I got a bootloop after flashing it.
I said "no problems", I tried to reflash it and got the same..then I decided to change rom.
When I changed I had no problems at all..well till I decided to turn off the phone.
Here is the situation I'm stuck now: no matter which rom I decide to flash I always report the same problem, when I turn off the phone I'm never able to turn it on again (when I turn it on I can see the htc logo and only a black screen after)
how can I resolve that? Please I need some help
ilikemyhtc said:
Hi guys,
I've been looking around a bit but unfortunately I did not find any solution to my problem
Well, I'm a newbie and I got my desire c last december.
Basically since I got it, I've been flashing loads of different roms and never had a problem with it.
Yesterday, I wanted to try the cm10 and I started having difficulties: I got a bootloop after flashing it.
I said "no problems", I tried to reflash it and got the same..then I decided to change rom.
When I changed I had no problems at all..well till I decided to turn off the phone.
Here is the situation I'm stuck now: no matter which rom I decide to flash I always report the same problem, when I turn off the phone I'm never able to turn it on again (when I turn it on I can see the htc logo and only a black screen after)
how can I resolve that? Please I need some help
Click to expand...
Click to collapse
I'll suppose you tried clean flashing. Check which kernel you are using.
You need to use CM10 kernel for CM10 and Sense for the Sense roms.
If its the correct kernel, try a lower clock frequency.
If you havent tried clean flashing:
Dirty flashing can cause a lot of errors so i suggest that you perform a clean flash.
If you get this error again, you should try to post a logcat using adb. There are guides on how to do that all over the web.
I hope i helped, and if there are any further questions, ask away :3
ommicsiy conduted
thanks for the answer!
well actually I did a clean flash..
and it can't be a matter of kernel since I tried different roms with different kernels and the problem is the same..
tomorrow after work I'll try the logat and post it
since I was not able to do it trough adb (-waiting for the device- for about 30 mins..)
I flashed again a rom and used catlog.
here is the outcome!
Hey guys,
First off, I am a complete noob with all this tech stuff. But I felt a little adventurous and wanted to root my One V.
I managed to unlock the bootloader and also root my phone. Phone was working perfectly fine after this. So next I tried installing some custom ROM to change the GUI. I clearly must have done something wrong because my phone is now stuck at the boot screen. I did a google search and stumbled across a page which said I have to go into Recovery mode and Back up or something. I followed the instructions and I'm still facing the same problem. It just won't go past the boot screen. I have no clue what to do next. Now I'm wondering why I even tried to do all this.
What do I do next? Please keep in mind that I'm an utter noob.
So here's my story: my phone was JellyBean. I didn't tinker with it, didn't root, just used some launchers. It upgraded to KitKat. I kept using it, even though I liked JellyBean better. Then one month ago it froze and stopped responding even to physical buttons. I managed to restart it, but it wouldn't go past the intel logo. Somehow I got it to go past it and give me like two seconds on before it would freeze and become unresponsive again, so I got to enter safe mode (all following instructions on the internet, which buttons to hold to manage to get into safe mode). Once in safe mode, I deleted every app that had been recently updated or installed, one at a time, trying to turn my phone on each time, until I finally deleted facebook (that enourmous blue monstrosity taking all that internal space), and the phone seemed normal. I re-installed the other apps I had uninstalled, then one day later, it froze again. Now it wouldn't go past the intel logo. Only then I gave up and used RSDLite to re-install the firmware - BUT! The firmware I managed to find was JB, but I had been wanting to downgrade for some time, anyway, so I unlocked the bootloader and flashed JellyBean. And it worked. I was proud. Then one month later, today, it froze again. I can do the same procedure, and lose all my data again, but I fear the problem will remain unsolved and it will freeze/crash/explode one month from now. Can someone help me figure out what my problem is, or give an alternate solution to try?
TL;DR:
my razr i was stuck on the intel logo screen, I unlocked the bootloader and flashed JB, it worked, one month later it is now stuck on the WARNING BOOTLOADER UNLOCKED screen. Please help thank you.
Hey. First time posting i think. I got a sm t-719 that was infinitely restarting. I tried changing everything software wise. Original Samsung Android and custom rims but nothing worked. Now i got TWRP bootloader on it that works. Should i replace the whole motherboard or what now? Thanks
i'm in the same predicament as you. Seems its all over the web,
but nobody really knows how to fix it.