Hi all,
Got a Rogers HTC one off of craigslist a few months ago which was already flashed to stock 4.3... worked great. Just yesterday I got a prompt on my phone asking me if I wanted to update to 4.4. "Sure, it cant be too hard?" I thought. Maybe its that I'm novice, but it didn't end up looking so simple. Soon the device asked me if I wanted to continue, saying this is not reversible so I said yes, then another message, I said yes again.. the device then turned off, then back on and there was a black screen with white letters and a loading bar.. when it finished i think it asked me another question about backing up the ruu or something like that and I said no... the phone turned off and tried to reboot, first the white with HTC quietly brilliant, then the google logo for half a second and then right to a light plue pixelated screen with little lines in it.. every time I hold the power button to turn off it turns back on and same thing. Is this whats called a boot loop? Did I do something wrong? At one point I tried turning off and then holding power and volume buttons to get into bootloader and it worked.. I didn't really know what to do so I just told it to reboot and it did but with same blue screen. I've been reading a lot of threads on here but I didn't see anything quite like this. Sorry for the long post. I'd really appreciate it if someone would help me out here.
Thank you.
Related
I did a search for this issue, and I cant find a solution mentioned anywhere on this sire, or any other for that matter.
I just got my new HTC Magic 32A, and decided to root it. The reason I wanted to do this was simply to be able to access the pay applications, as Rogers in Canada blocks it.
I did the root following the 'theunlockr.com' procedure, using the flashrec-1.1.3-20091107-2.apk and recovery.RAv1.2.3H.
I typed in the following text into the empty box during the process " /sdcard/recovery-RAv1.2.3H.img ".
I tried loading few custom ROMs, but it refused each time, citing an error (different errors, as I recall).
The new ROM wasnt a big deal, so I decided to simply turn on the phone. The phone it stuck on the 'Rogers' logo, and after a while it turns into android letters on a black screen. Basically I am left without a phone, after spending pretty much everything I had on it.
At this point, all I want to do is revert it back to the original state and forget about it all. I tried doing the hard reset, to no avail. Tried doing the procedure with the sappimg.nbh file, but it turned out it only works for the mytouch in the states. The only other procedure they have on the website is through loading some sort of a file onto the phone, but I can't do that as the phone doesnt turn on! Kind of sucks, especially with Christmas coming up soon.
Guys, I am totally stuck and help would be really appreaciated.
Thanks to everyone in advance.
Bump.
Someone please help....
I am able to get into the phone by pressing "power + volume down" as well as "power plus home".
Is the phone dead?
Will giving you an spl and radio versions help? How do I get these numbers?
I am willing to up the ante, as I will donate $40 to the first person who fixes my phone, if possible.
Phone fixed.
Hey Com,
I got some problems with my u20i x10 Mini Pro. It was stuck in some boot loop like 1 month ago and I tried to reflash it with SEUS and this flaher App thing thousands of times. I did not have a little bit of success so i gave it up 3 weeks ago. Since then i had my phone laying under my desk without the battery. Today I decided to try it again and, GOD KNOWS WHY, it started up normally. So i finished the startup wizard and everything worked fine. Then i rooted it with superoneclick (my phone had A.0.6 FW), rebooted and everything worked just fine. Then I wanted to sign in to my wireless network and for some reason it did not work, but whatever. After like half an hour my phone started lagging really hard and suddenly the screen went black. I tried to push all the buttons and the screen went bright for a very little while and went black again. And this point it was like it was turned off. So i tried to turn it on and, guess what, its stuck in a boot loop! YAY! Now my phone is lying in front of me and all i can see is the only white SONY ERICSSON logo.
Seriously what has happened? Anyone knows how to fix that?
Thanks in advance, Martin.
UPDATE:
Now I am facing a new problem. My device turns "on", I can see the white SE logo, then the screen goes black but for some odd reason the touchscreen is reacting at the lower left and right parts of the screen. I can even dial a number (i hear the beeps) when I press twice at the lower left corner and then tapping at the display. But well, i guess thats not how the phone should work. So did any one also face this problem? Do you have a solution for that?
Anyway, Thanks in advance.
Kind Regards, Martin.
thing is..
Your posting skills are zero..
Using profanity is one thing, but using it in the topic? Surely a 99% ignore from most members!
Id go back and edit your posting if you are actually capable of using better language!
Nochances,
Wow, you must be one big loser, your first post is to criticise someone the way the lay out a question script.
nochances said:
thing is..
Your posting skills are zero..
Using profanity is one thing, but using it in the topic? Surely a 99% ignore from most members!
Id go back and edit your posting if you are actually capable of using better language!
Click to expand...
Click to collapse
I'm sorry if i offended you in any way but at the time posting this i was really stressed out. And i apologize for my bad English, I'm not a native English speaker since I'm from Austria.
Have a nice Day, Martin.
Hi, ive been lurking on the xda forums for months, and have succesfully roooted and run darky rom on my galaxy s. then i got a wildfire s second hand.
Now i decided to try for s-off and a custom cwm rom. downloaded all the files read everything i could, and have managed to brick it i think.
Result if i press power or volume down + power i get a flickering screen, it flashes grey for 2 sec, black 2 sec. there is a faint red glow to the right of the front htc logo...where i thought the camera was lol.
i was trying to use the htcdev.com route. downloaded :
PG7610000_Marvel_hboot_1.09.0099_2.13.401.3_0210_R.exe
and tried but it said i needed an earlier rom before i could update.
2.13.401.3 to be exact so i downloaded:
RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe
which was hard to find and a pain to download...i ran this, it found my phone, gave me the usaul warnings, check battery etc, everything set so i told it go ahead, it ran for bout 7 or 8 minutes my phone went to a black screen with htc, did a progress bar then it said finished on the pc. left it for a few more minutes to be sure, then powered on my htc. screen starts flicking grey and white...
ive tried removing the battery, cant get into hboot, get no logos, no vibration, nothing.
sdcard has been removed and sim card.
usb cable inserted charges then goes to flickering screen. pc does not detect any android device connected...
this was bout 2 hours ago. searched all the forums i know, googled, found one post similiar but no1 really helped him just told him to take back for warranty...
i live in south africa, dont know of any cellphone shops that can help me, please say its not a lost cause...
before attempting this my hboot was:
0.90.000
radio 7.46.35.08
s-on
.........anything else you need to know just ask....oh was running the htc sync drivers with sync not running on a windows xp sp3 32bit...
any help HUGELY appreciated, sorry for the long post....
i would ask this in the htc wildfire s general section, people over there no this phone in and out and could help you out quick hope this helps good luck!
thx
thx ill move it there now, sori for posting wrong area
its fine to post here! im no moderator haha but you would probably get better help in the wildfire s forum
Hello All,
I have a Motorola Atrix 4G running Dark Side rom. It has been working great for me and loving my phone. This morning it gave me a Wi-Fi error and after a few minutes rebooted. So first I did a complete reflash of the rom but nothing changed. Then I downloaded the Nottach rom and followed all instructions. Once phone booted up everything looked fine until i clicked on Wi Fi... it gave me a error I clicked it again and phone rebooted.
Does anyone have any ideas. Please keep in mind i am kind of a newbie to this so if you can keep it simple when explaining I would greatly appreciate it.
And most of all I want to THANK anyone who takes the time to help me.
THANK YOU
Does bt make it reboot as well? If so, hate to say it, but sounds like your wifi/bt chip died. All around the forums are people with this problem and lots of them say our atrix is known for this to happen. Hopefully that's not the case for you and someone will come along with more help.
If BT is blue tooth, i just clicked on it and it never turns on, but does not make the phone reboot. So the phone is trash i take it?
Okie_Bama said:
If BT is blue tooth, i just clicked on it and it never turns on, but does not make the phone reboot. So the phone is trash i take it?
Click to expand...
Click to collapse
If it doesn't turn on, that's bad news. Time to see about a warranty replacement and hope its not one that motorola has blocked the unlocking of the bootloader. Bad luck man.
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk