So, I feel like I should preface this with the full realization that I am an idiot.
Now that that's out of the way, here's what happened.
This thing runs crazy slow, and I heard HTC Sense (Amongst other things) slows it down. So, I Unlocked the bootloader and rooted my CDMA Virgin Mobile One V using the steps here:
http://forum.xda-developers.com/showthread.php?t=1751004
Afterwards, I tried to flash a rom of CGM 10, which didn't work. When I attempted to boot into recovery mode both from ROM manager and from the bootloader, I got a phone with a red ?. I tried a few times, couldn't figure it out, so, I gave up on the roms.
Then I found out you can uninstall apps using titanium backup. I uninstalled an app related to sense. I'm not sure which one exactly. After this, my home button stopped working. Upon realization, I did a factory reset through the bootloader, thinking it would resolve the issue. Now, when I boot the phone, the htc screen shows, the VM screen shows, then it goes black. The indicator light is flashing like I have a notification, however. Additionally, when I received a message on facebook, my phone vibrated. My theroy is that the phone is working in the background, but just don't display anything on screen.
When I use vol down + power to attempt to load into the bootloader, the phone just turns on and displays the symptoms above. I don't know of another way to get into the boot loader so that I can attempt to flash an RUU. Am I totally screwed here?
Good news is that I have my old Optimus V as a backup, but the thing is ancient and I'd really prefer to get my One back up and running. If the one is a turtle, speed-wise, my Optimus is a gargoyle.
Oh, and for the record, *facepalm*.
Update: I plugged the phone in to charge, and the unlock ring came up. I am able to get into the settings and notifications from the top bar, but the home screen still won't come up. I still can't get into the bootloader, either.
thefaded said:
Update: I plugged the phone in to charge, and the unlock ring came up. I am able to get into the settings and notifications from the top bar, but the home screen still won't come up. I still can't get into the bootloader, either.
Click to expand...
Click to collapse
I guess ur best shot is to get new rom flashed or use some nandroid.
thefaded said:
Update: I plugged the phone in to charge, and the unlock ring came up. I am able to get into the settings and notifications from the top bar, but the home screen still won't come up. I still can't get into the bootloader, either.
Click to expand...
Click to collapse
Sounds like you removed the Sense launcher which displays your apps, wallpaper, etc. I would try flashing another rom
Sent from my One V using xda premium
Just reflash the ROM you were on WITHOUT full wipe
Related
I'm having a rather odd problem with my wife's Slide. She was running an older CM7 rom and was having a problem getting the screen to lock. When you press the power button, it would act as if it is going to lock, the screen would go black, but then it brought up the recent programs. Simple problem I though... I downloaded CM7 and got ready to flash it, but over time her SD card has had things deleted and I wasn't able to get to recovery. I loaded the esprimg.zip onto her card thinking that was all I needed to load, but that forced us back to a stock ROM. No worries there, she doesn't care if she has an unrooted stock phone, or CM6 or 7, and I guess I will never have to hear her say the rooted ROM is ruining her phone.
So, now we are stock and the problem still exists. The screen will not lock when using the power button, nor will it lock when it times out. I put the pattern lock on, and still it will not lock, although it will load the pattern lock screen. I've rebooted a couple of times to no avail, and the phone is as stock as can be, no bells or whistles, no strange apps, actually the only market app on the phone is Words with Friends. Has anyone run across this issue, or know of maybe a third party screen lock app that I could try?
Hi there, this is my first post, i didnt want it to be like this but i have come to you in desperation.
I was excited about 4 hours ago to realise my phone was getting an update saying it was going to imporve battery life etc..
Well i let it do its thing while it was downloading, i went to check after an hour or so and it said the software had been corrupted or something along those lines, either way it had to start the download again.
It was about bed time when this happened so i chucked it on the charger, fell asleep, woke up and it was doing something on a kind of screen i had never seen before, black screen, obviously showing that it is processing the update(i was a little tired from waking up) i think i remember taking its time maybe longer than it should have been.
I went back to sleep woke up about an hour ago from now and checked my phone and the screen would not turn on, i think the charger cable had fallen out from the phone because it is loose and does that some times.
So i placed the cord back in and it didnt seem to respond with the red led coming up for a while then all of a sudden it worked for some reason, but was flashing. i suspected this was because the battery had been sucked dry. So after a while the led stopped flashing and i pressed the power button, sure enough it powers up straight away to the HTC - quietly brilliant screen. And thats that, end of story. It's stuck on that screen WTF?
I have been through forums like these interested in changing ROMs and so on but it all seems so complicated i never even bothered, so obviously i am a noob, but i dont think there is any reason for this to happen other than sh*t luck.
Can anyone help us out?
Your better off sending for repair unless you want to start unlocking the bootloader etc.
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
masucu said:
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
Click to expand...
Click to collapse
mercccccccccccccccccccccccccccccccci
zezo_ddd said:
mercccccccccccccccccccccccccccccccci
Click to expand...
Click to collapse
Well did it work? before you say that long thanks
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
helter_skelter87 said:
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
Click to expand...
Click to collapse
If you wait a day or so, the RUU will be released for your region now that the OTA has been released.
You'll be able to fully reload your phone - this is all HTC do when you send it for repairs and you can do it in a lot less time.
At the moment, HTC may even reload the 2.17 software so you may still have the problem again when trying to load the OTA.
Thanks all for your interest.
I spoke with customer support and they told me exactly what i already had done, factory reset through hboot.
After that was a no go, he told me i have to send it back to the point of sale, so they can flash the software?
Where can i find this ruu once it has been released?
I'm pretty sure the updates all say to not have the phone plugged in when updating.
Sent from my HTC One X using xda app-developers app
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
dubbz84 said:
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
Click to expand...
Click to collapse
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
GiantJay said:
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
Click to expand...
Click to collapse
Well i just placed the battery back in, it started on it's own without my pressing anything again, and i've been timing the last 5 minutes. but it seems like it will stay a black screen indefinitely. unless i remove the back of the phone, or snap it back into place, or any kind of micro impact movements it seems, when I do that it vibrates like it's first being turned on, and shows the samsung screen, then the samsung galaxy s3 screen, then it will go black again.
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
topherk said:
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Not picking it up on adb.
dante32278 said:
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After the first odin flash i was thinking the same thing. But that's the thing, it won't stay on the download mode screen long enough for me to even try to flash anything else through odin. I'm also noticing when connected to the charger, if i make a slight impact against the phone with my palm, the screen will briefly show the battery icon as if the phone is charging when it is turned off, then the screen will go black again. When it is unplugged, is when it will show the samsung screen, then the samsung galaxy s3 screen, then go black again.
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
To me it sounds like maybe your power button is stuck "down"
If you didn't know, the power button has a fail safe reboot that happens after holding for about 10 seconds. So no matter what, if you phone is frozen or whatever, holding power more than 10s will cause it to reboot. That would also explain why its turning itself on as soon as you pop in the battery.
toolegit said:
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
Click to expand...
Click to collapse
not recently, and if it was ever dropped, it would be in it's case... But i had noticed that while it was in it's power glove case, sometimes i would have to use more than normal pressure on the power button to get the phone to respond. I was wondering if something was stuck, just haven't read anything like that happening to anyone, and when I used the jig the first time the screen stayed on.
Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem
If This has Already been Posted I'm Sorry, I couldn't Find anything that fit..
I have a Samsung Note 2 Unlocked on 4.1.2 stock. I have a recovery on it..
This is what is going on and I Really Could USE Some HELP..
I tried to download an App last week but it wouldn't download. Then Friday the App just started downloading. It was just a simple Pic App. Friday Night, My phone died, so I charged it about an hour or so and Tried to turn it on. When it comes up with the Samsung screen then All of a Sudden the word Samsung starts jumping up and down and gets lines through it. The phone boots on up but the screen Stay Black. The lights come on where the buttons are and it makes the sounds from my text messages and things like that.. It also makes the sound and vib when I Unlock the screen but Still can't see Anything.. I can put it into Download Mode and see the Screen Fine but when trying Recovery Mode or Anything like that then the screen goes back to moving with lines and looks like static y.
What can I do??
I've went through all the files on my phone and SD card though my computer and Removed that APP but it Still didn't help... I'm Not Sure but I was thinking I could use the Factory Image to redo it but I'm not sure how to go about it. Also Will I have to re unlock my phone and I would like to upgrade so do I Need to 1st put what was on my phone then upgrade from there or just use the new one??
THANK YOU for Any and All the Help..
I have now Tried to re load the Stock Software 4.1.2. It was Successful and after it rebooted then it did the same thing with the Samsung Note screen. Then it showed some lines and lights kind of like it was going to come up but Never did, Just went back to the BLACK Screen... PLEASE SOMEONE HELP! Is there a way to Wipe Clean and Start Fresh by using the Computer..
Thanks for Any Help...
All I can think of is use Odin to flash the latest factory Rom, and see if that fixes it.
Sent from my SGH-T889 using xda premium