Related
So I posted a thread about how my 3G wasn't working, and it's still not working. So after talking with Sprint for about 2 hours yesterday, I'm getting a refurbished phone. They told me when I get the refurb, to send back the one I have now, which is rooted. So I need to completely unroot the phone I have now. Is there a tutorial online that will show me how to completely unroot my phone?
Thanks
EDIT: Will this do it? If I just run this file with my phone connected to the computer?
Yes, the RUU completely restores the phone back to factory, unrooted stock condition, just like if it were fresh out of the box.
chromiumleaf said:
Yes, the RUU completely restores the phone back to factory, unrooted stock condition, just like if it were fresh out of the box.
Click to expand...
Click to collapse
Nice, also, I saw what you posted in my other 3G thread. I'm gonna give that a shot. The update profile thing I tried a few times (a few times myself as well as with the Sprint rep), but I never tried the airplane mode. Thanks for the info.
EDIT: Thanks, but it didn't help..still the same thing. I don't get what could be wrong though, I literally tried everything. I even factory reset my phone twice, still no go..I wonder if it's a hardware error, I don't know what else it could be at this point.
Okay so I'm trying to flash the originial RUU that I posted in my OP, but for some reason, when I start it up, it says "Waiting for Bootloader..." and it does that for about a minute, and then an error comes up saying that the phone couldn't be updated and to try again.. I did it twice and I'm getting the same error. Does anyone know how to get past this?
spatel9114 said:
Okay so I'm trying to flash the originial RUU that I posted in my OP, but for some reason, when I start it up, it says "Waiting for Bootloader..." and it does that for about a minute, and then an error comes up saying that the phone couldn't be updated and to try again.. I did it twice and I'm getting the same error. Does anyone know how to get past this?
Click to expand...
Click to collapse
Make sure your battery is charged pretty well (at least past 50% or so). Turn off your phone and turn it back on. Does it get stuck at the black HTC screen? Or the white one?
If so, leave it this way, plug your USB into the phone and computer, then try re-running the RUU with the phone stuck like that. Sometimes this works for people who get these types of errors.
Also check out this thread, some of that may be helpful: http://forum.xda-developers.com/showthread.php?t=586258
This one is similar: http://forum.xda-developers.com/showthread.php?t=703602
chromiumleaf said:
Make sure your battery is charged pretty well (at least past 50% or so). Turn off your phone and turn it back on. Does it get stuck at the black HTC screen? Or the white one?
If so, leave it this way, plug your USB into the phone and computer, then try re-running the RUU with the phone stuck like that. Sometimes this works for people who get these types of errors.
Also check out this thread, some of that may be helpful: http://forum.xda-developers.com/showthread.php?t=586258
This one is similar: http://forum.xda-developers.com/showthread.php?t=703602
Click to expand...
Click to collapse
Wow, you are just helping out left and right today, aren't ya, lol
Thanks, the first post on the first link you posted did the trick, thanks again.
So this is my wifes phone and the only thing that has been done if the phone is rooted. If we power her phone off and try to power it up everything works fine. But if we power it off and leave it over night the phone will not reboot unless we pull the battery the next morning.
Anyone else have this issue with thier Thrill?
sneakyws6 said:
So this is my wifes phone and the only thing that has been done if the phone is rooted. If we power her phone off and try to power it up everything works fine. But if we power it off and leave it over night the phone will not reboot unless we pull the battery the next morning.
Anyone else have this issue with thier Thrill?
Click to expand...
Click to collapse
Its only happened to me once but that was cause the battery died at night. Forgot about it the next morning and tried to turn it on. Nothing. Plugged it in. Nothing. Had to pull the battery and then plug it back in and it finally booted. Not exactly the same situation, but hey, its happened
And thats the one and only time its happened to me.
It does this even with a fully charged battery. Makes me wonder if it is a bad root causing the issue.
Well has anyone else had this issue at all yet? I even re-rooted the phone and it is still doing it. I read somewhere that fixing permissions using CWM can have some negative effects on the Thrill, could this be the cause?
Anyone else have any suggestions what to do in order to fix this issue. As of right now the phone has to stay on all the time, otherwise you have to pull the battery to get the phone to boot.
sneakyws6 said:
Well has anyone else had this issue at all yet? I even re-rooted the phone and it is still doing it. I read somewhere that fixing permissions using CWM can have some negative effects on the Thrill, could this be the cause?
Anyone else have any suggestions what to do in order to fix this issue. As of right now the phone has to stay on all the time, otherwise you have to pull the battery to get the phone to boot.
Click to expand...
Click to collapse
I doubt fixing permissions would fix anything since it really only messes with apk/service permissions. Nothing of that sort would affect whether the phone powers on. Its more of a fix for force closes. Are you within your window to exchange it?
Sent from my LG-P925 using Tapatalk
Previously when I had CWM fix permissions I would have the phone randomly restart, but it would still boot up and everything.
CallMeAria said:
I doubt fixing permissions would fix anything since it really only messes with apk/service permissions. Nothing of that sort would affect whether the phone powers on. Its more of a fix for force closes. Are you within your window to exchange it?
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
Yes we are, that was my next thought was to exchange it for a new one and try again.
Hello everyone. Im having this really odd issue where the phone wont power off. I press and hold the power button down, and choose "POWER OFF" and it does the animation of powering off, then it goes dark....then in about 2-3 seconds it powers back on. Now i do have Fast Boot unchecked. Im also rooted and running the Dev edition of the HTC One. If i boot into recovery and choose the option to shutdown, it still reboots on its own. Very odd. Anyone care to help me out? Thanks
seems like cache error. try to clear cache in recovery.. if nothing happens .. clear data .. . yup then you will lose all data. but u will get into system atleast
jags_the1 said:
seems like cache error. try to clear cache in recovery.. if nothing happens .. clear data .. . yup then you will lose all data. but u will get into system atleast
Click to expand...
Click to collapse
I did all that as well. Same thing. I even wiped the phone and am now reverting back to stock to see if i can get it to power off correctly.
serialtoon said:
I did all that as well. Same thing. I even wiped the phone and am now reverting back to stock to see if i can get it to power off correctly.
Click to expand...
Click to collapse
Strange. Good luck. Does reverting back to stock mean you are running the RUU?
nugzo said:
Strange. Good luck. Does reverting back to stock mean you are running the RUU?
Click to expand...
Click to collapse
Yea. But im having a bit of an issue even with that. I consider myself a seasoned vet at this kind of stuff, but seem to be having a hard time with it. I tried to flash the RUU and it failed about 25% thru it, and now im at an HTC logo with exclamation signs on each corner. Kind of at a loss...but ill keep in screwing with it.
ok, so i reverted back to stock using the RUU and it STILL DOESNT TURN OFF!! I dont know what to do anymore. Faulty hardware? Kind of weird when everything else works fine.
serialtoon said:
ok, so i reverted back to stock using the RUU and it STILL DOESNT TURN OFF!! I dont know what to do anymore. Faulty hardware? Kind of weird when everything else works fine.
Click to expand...
Click to collapse
Nothng else you can do on your end. You've done it all. Tell them you installed the ruu and that didnt work. If its from a carrier, ATT, t-mobile.. Just take it to a corporate store, they should replace it. If its a Dev edition, gotta send it in. For me it wouldnt be much of an issue because i never turn my phones off.. But if you do turn them off, this is a major issue lol. They should replace it no problem.
nugzo said:
Nothng else you can do on your end. You've done it all. Tell them you installed the ruu and that didnt work. If its from a carrier, ATT, t-mobile.. Just take it to a corporate store, they should replace it. If its a Dev edition, gotta send it in. For me it wouldnt be much of an issue because i never turn my phones off.. But if you do turn them off, this is a major issue lol. They should replace it no problem.
Click to expand...
Click to collapse
Yea it is a developer edition phone. Ive done evrerything i can think of and i think i may need to send it in. What sucks is that i have already added my zagg on the back and added an SGP screen protector and i would hate to waste them. I also normally dont turn my phone off (if ever) but i dont want to end up with more hardware issues down the line. Im contemplating sending it back to HTC and ordering the Google edition when that is available..but im kind of happy with it as is. I have HTC on the phone now...lets see what they say. At this point im kind of curious as to why its doing this.
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
dlnas said:
Today while using my one that is rooted with trickdroid 8.0.0 turned off at around 40% randomly, The screen froze at the lockscreen and I when put it to charge the orange light did not appear. I cannot reboot into recovery from the phone nor from adb. When plugged in the computer it is read as QHUSB_DLOAD. Any advice on how to fix this?
Click to expand...
Click to collapse
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
iElvis said:
QHUSB_DLOAD usually means a hard-brick. Does it power on at all? You might try leaving it plugged in overnight, but I suspect your phone just died.
Click to expand...
Click to collapse
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
dlnas said:
It does not power on at all. My battery was at ~40%. Is it possible for the phone to just turn off like that at that percent?
Click to expand...
Click to collapse
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
iElvis said:
I haven't seen it on the One, but it was a real problem with the One XL. Phones would just drop to 0% charge and die for no apparent reason. Not pleased to this happening on the One.
Click to expand...
Click to collapse
Before it died. I unlocked the phone and the only thing I could do was pull the notification drawer down. It would not let me open any app or even the app drawer.
dude this sounds frightening
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
postfatal said:
Read the HTC Unbricking Project thread, the problem is HTC phone wide so I see no reason why the fix wouldn't also be. At the very least give that thread a read, you've got nothing to lose.
Click to expand...
Click to collapse
That fix is only for a couple of specific issues:
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
Click to expand...
Click to collapse
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
tousary shall
iElvis said:
That fix is only for a couple of specific issues:
People tried it on the One XL/Evita when this happened, and it didn't work, unfortunately. Note that the method requires the battery to be removed.
Click to expand...
Click to collapse
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Had the same problem after flashing the wrong recovery..
THis means it is hardbricked and unrecoverable..
You could ask here: http://forum.xda-developers.com/showthread.php?p=43750389#post43750389
Else send it in for repairs
dlnas said:
I've only had the phone for 2 months and it already bricked. It shouldn't be a problem explaining it to AT&T and getting a replacement right? I mean if I can't turn it on they can't turn it on.
Click to expand...
Click to collapse
It's a hardware fault, from everything I've seen, and HTC or AT&T should replace it. AT&T tends to be very easy about this. If the phone won't power on at all, they shouldn't give you a hard time.
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
jason504 said:
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
Click to expand...
Click to collapse
I am sure you tried factory reset already? I had a few in phones in the past do that. Usually was a bad battery. When did it all start? How old is phone? Any apps you install and it started doing this?
Leaning more towards you will need to ship in for a warranty with Samsung.
Nick216ohio said:
I am sure you tried factory reset already? I had a few in phones in the past do that. Usually was a bad battery. When did it all start? How old is phone? Any apps you install and it started doing this?
Leaning more towards you will need to ship in for a warranty with Samsung.
Click to expand...
Click to collapse
This is my 2nd phone the first one got screwed up with a update. I have had this one for about 4 months and it just started doing it about a month ago. Now it has done it 3 times this week. Once just now and it happens on the charger and off the charger. It has made me late waking up twice. I haven't done a phone restore yet and I haven't installed any new apps.
Sent from my SM-N950U using Tapatalk
jason504 said:
This is my 2nd phone the first one got screwed up with a update. I have had this one for about 4 months and it just started doing it about a month ago. Now it has done it 3 times this week. Once just now and it happens on the charger and off the charger. It has made me late waking up twice. I haven't done a phone restore yet and I haven't installed any new apps.
Click to expand...
Click to collapse
Sorry didn't read right tired ha. Black screen usually sign of bad screen. Got mixed up and thought it was restarting on it's on. If there was no apps that caused it. You didn't mess with any settings? Said your stock.
If none of the solutions others suggest soon don`t work. I'd go for a factory reset last resort. Worst case you will have to ship again to Samsung sadly
Nick216ohio said:
Sorry didn't read right tired ha. Black screen usually sign of bad screen. Got mixed up and thought it was restarting on it's on. If there was no apps that caused it. You didn't mess with any settings? Said your stock.
If none of the solutions others suggest soon don`t work. I'd go for a factory reset last resort. Worst case you will have to ship again to Samsung sadly
Click to expand...
Click to collapse
I see a lot of people having this problem. Not on here but online and it's not just the Note 8 it's the S8 too.
Sent from my SM-N950U using Tapatalk
jason504 said:
I see a lot of people having this problem. Not on here but online and it's not just the Note 8 it's the S8 too.
Click to expand...
Click to collapse
That's concerning. I take it most people with same situation as yours, shipped into sammy? Sucks you gotta go through this bs again maybe.
Just as suggestion, but if you use AOD try turning it off and and see if this fixes the problem.
I had this problem with Ironman ROM and turning off AOD fixed the problem.
How to Fix A Samsung Tablet with Black Screen
jason504 said:
At least once a week I go to use my phone and it will not turn on? I have to hit the power and volume down to reboot the phone. It's getting worse and worse does anyone know why this is happening. I tried to search I didn't see anything. I am on Att and stock.
Click to expand...
Click to collapse
Hi,
If you can't reboot your device to fix black screen problem, you can try FoneLab broken android phone data extraction to fix it.
Download and install the program on your computer, and then connect device to computer.
Then you can scan, select and recover data with a few clicks.
More details from fonelab and the post How to Recover Data from Android Phone That Won't Turn On or How to Fix A Samsung Tablet with Black Screen.