I am playing with my old xv6800..
anything I flash to it gets stuck in the splash screen.
I can flash back to stock vz and all is well.
I have tried several different roms but all seem to stay on initial splash screen.
I am running a 6.5 rom on my regular xv6800 and am experimenting on old phone to find the best one for me. I have had other flashes on this phone, it just started sticking lately..
Thanks
Jerry
FOund problem..
Bad radio flash...
Can't wait for Verizon to release Omnia 2
Related
Hey I got a mogul I was trying to convert it to a cricket one using dcd 3.0.1 rom for cricket. Phone had already had latest sprint rom so i unlocked it I thought and loaded up dcd's rom. Rom was acting funny kept rebooting so in my attempts to fix I went from phone rebooting to just getting stuck at htc screen with dreaded no radio. So i thought try to flash 3.27 radio after reset phone is just dead just a black screen. Bootloader mode wont work. Can connect phone to computer and will connect as htc pid interface but screen is black will not boot. All i can get is a red light when i first plug it up but then goes out after so long somebody help me. thank you. Not a rookie but made a rookie mistake.
http://forum.ppcgeeks.com/showthread.php?t=20882
Hello, I have an unrooted Hero from Orange (Spain) that enters in a boot loop. I have tryed everything to restore it but with no success. In the hboot menu it says "touch panel-fail" and even if I flash again the original rom from the hboot, it still gets in a boot loop.
First of all I will explain my case.
I had the Hero rooted, with custom roms etc, but when I bought a Nexus One, I gave my Hero to my brother. In September he told me that the official 2.1 had arrived to the Hero, so he wanted it instead of a custom rom, so I just proceeded to do so. I created a GoldCard, installed the 1.5 RUU of WWE, made the two OTAs and all OK. The last week (I think) he received a new small OTA, he updated successfully. My brother went to sleep with the Hero almost charged, but when he woke up, the Hero was off. Then, when he turned it on, and after a while (15mins or so) the Hero finally boot up, but the touchscreen wasn`t working and using it with the trackball the Hero was always prompting FC of android.process.acore (every 2 seconds more or less).
After watching that, I installed the official 1.5 of Orange hoping that it will fix it, but no way. Now it gets stuck in a loop while booting after the Orange bootscreen.
I tryed again to flash the WWE version, but with my old GoldCard doesn't seem to work (incorrect cid) and not being able to boot it up, I cannot create a new GoldCard or even root it.
I have tryed a lot of fastboot comands but I can do just little things because for the most useful things I need root.
Other thing that might be good to know is that when I plug the power to the Hero nothing happens, the led is not turning on, and I don't know how much battery I still have. Thank goodness that the battery was full before I moved the Hero to this infernal boot loop.
Please I will be so thankful if anyone can help me or just giving me any clue about how can I fix this.
I had the same problem on a refurbished hero I had. It had touchpanel fail in hboot and was in a constant loop.
I managed to get it to boot into android once by installing the ruu while in fastboot mode, however the touchscreen did not work and when I rebooted the phone it went back to the loop.
I sent the phone back for a replacement. If u check my previous threads ull see the thread icreated. In it I said that it had worked as that was when it finally booted but before I realised the sgreen didn't work
Sent from my HTC Hero using XDA App
Thank you for your reply, I will check your posts when I arrive home this evening.
hi.
I had the same problem and solve it by flashing this rom (goldcard needed)
http://shipped-roms.com/shipped/Her...io_63.18.55.06P_6.35.15.11_release_signed.exe
I have an international version of the Samsung GS2 that i am using on At&t. A few weeks ago i noticed that my phone would suddenly turn off while in my pocket or just left alone. Then, one time i tried turning on the phone and saw that the phone got stuck on the boot animation screen with blue markings all around it. I took out the battery and put it back in a few times and was finally able to get the phone to work.
Today, the same thing happened. The phone turned off i tried to restart it and it got stuck on the boot animation screen (Galaxy S logo). It has these blue markings around it and it can't get past it. The phone isn't rooted and i have not tampered with the system files. I've only updated it once, from 2.3.3 to 2.3.4. I tried factory resetting it but nothing changed and its still has the same problem.
I have a suspicion that it might be caused by the fact that i've dropped the phone a few times. What do you guys think could be the problem and what are my choices in getting it fixed? Would flashing a stock rom help fix the problem?
I would suggest flashing the Stock Rom Through Odin as i once has an issue with massive yellow streaks kind of like what you are getting after a flash before.
I went ahead and flashed a few roms from http://forum.xda-developers.com/showthread.php?t=1075278. The flashing worked fine but it still can't get past the bootup screen and the blue marks are still there.
Would calling Samsung and asking for support get me anywhere?
How long did you wait after flashing the rom? The worst way you could have messed up is by choosing the wrong files in Odin. Did u check that again?
Sent from my GT-I9100 using xda premium
I flashed the rom and rebooted and saw that it was still the same. Does it matter which rom i chose? I tried two or three different roms from the thread. I though they were all stock roms...
I managed to break my original HD2 a while ago and I've only just decided to replace it. I have another main phone but I loved that I could pretty much do anything with my old HD2. I had a bit of experience with installing cooked ROMs before moving on to installing Android and WP7 on it.
As I had a bit of experience with playing about with software recovery/updates, I decided to buy a phone that was described as "booting to a white screen" off ebay. I thought it would be a fun little hobby to get it working again.
My first few steps would be to get it to stock and start playing with it from scratch.
I booted into the bootloader and tried to flash a stock ROM but it kept freezing at 0%.
I've since managed to change the SPL version from 2.08 HSPL (I could get the phone to boot into MAGDLR 1.13, so they must've been playing with WP7 or Android NAND) to 3.03.
I downloaded and installed the stock 3.14 T-Mobile UK ROM, but it won't boot past the white screen with the HTC logo. If I pull the battery out to turn it off and try to turn it on again, then it gets stuck at a blank white screen with no HTC logo at all. I'm very confused and would like some help if possible. Thanks in advance.
Good day! So I have an SGH-I757M locked to bell thats been sitting in my closet for quite a while now. when I pulled it out and turned it on it would splash to SAMSUNG and then the model number ( i later found out that was the beginning splash screen) and then stall out completely. I hooked it up to ODIN and used a version of the stock bell rom found on XDA and after it loaded up I could get to the beginning of the rom, but it would become glitchy and freeze.
I figured that I could now through a custom rom on it since I had gotten past the splash screen. having put the latest CWM Philz touch i started trying to customize the phone. I had to put a new modem set on there because the one one there was a gingerbread one and the roms wouldnt take. now when I put a rom on there i feel the phone vibrate when I turn it on but its a black screen. I can still get to download mode and CWM no problem. kinda at a loss here.