So, just to set the stage, I'm not a developer, but I'm fairly practiced at using ADB, unlocking bootloaders, rooting and unrooting, and installing custom recoveries and ROMs - that is to say, I know what I'm doing. I recently bought an HTC One, and in preparation for wanting to sell my One X on ebay, I wanted to return it to completely stock and make sure OTA updates were working properly.
I started by relocking the bootloading and installing the 2.20.502.7 RUU (I have an AT&T One X). That went fine and booted up properly, but I wasn't seeing the OTA updates, so I thought maybe the stock recovery hadn't been installed properly, and when I tried to boot into the recovery I couldn't get the menu to show (the initial image appeared, but holding Vol Up+Down didn't do anything, just made the error image appear after several seconds). So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Getting stuck in a bootloop or something I know how to deal with, but the phone is completely unresponsive, holding the power button for any length of time seems to have no effect, hoping you guys might have some ideas.
FYI My phone was on bootloader 1.09 before flashing the RUU, 1.14 after.
Requested moving to the AT&T One X forums
TToivanen said:
Requested moving to the AT&T One X forums
Click to expand...
Click to collapse
Ugh....thought that's where I was, evidently didn't look at the forum close enough...
bikeracer4487 said:
So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Click to expand...
Click to collapse
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?
redpoint73 said:
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?
Click to expand...
Click to collapse
Link to site of download link: http://onexroot.com/one-x-unroot/how-to-unroot-rooted-htc-one-x/
Download link: http://downloadandroidrom.com/file/HTCOneX/unroot/OneXUnroot.zip
Connecting charger shows blinking red notification light. As a side note, the phone was at 96% battery when I was working on it and I left it plugged in overnight, just in case.
That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.
redpoint73 said:
That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.
Click to expand...
Click to collapse
Yeah...that was dumb...I realized what you were getting at as I was getting the link for you... That said, I WAS able to get it turn on just now by holding down the Vol Down button and power for 10 seconds...although, didn't actually do anything, letting go of those buttons and simultaneously unplugging it from the charger made it turn on...not sure which or both of those things were actually the cause though. But once I was booted in I tried booting into recovery with "adb reboot recovery" but that got me to the HTC logo screen with the developer warning but it hung there. Luckily, I was able to boot into the bootloader, but again, trying to get into the recovery made it hand at the "quietly brilliant" screen. Do you know if the stock RUU's are supposed to flash the stock recovery, or do have a link to AT&T's stock recovery? I'm having a hard time finding one labeled properly.
Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.
redpoint73 said:
Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.
Click to expand...
Click to collapse
Okay, I'll try that, I still have the 2.20 RUU. Good to know on the 3.18 since I am def SuperCID. Will being SuperCID affect my ability to install OTA updates?
bikeracer4487 said:
Will being SuperCID affect my ability to install OTA updates?
Click to expand...
Click to collapse
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.
redpoint73 said:
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.
Click to expand...
Click to collapse
Good idea. Found a thread for S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) but not sure how to restore AT&T CID.
EDIT: Frick, wish I had though to do this BEFORE installing RUU and unrooting the phone.
Related
Beware, I installed AT&T's latest OTA update today, but something went wrong because I just get a black "blank screen" after the htc splash screen.
Symptoms are like this:
Power on
Get "HTC Quietly Brilliant" splash screen
AT&T Music plays, but the screen is black, no animated ATT logo
A few seconds later, the screen is still black, but the power button toggles the backlight on and off
I tried swiping my unlock pattern on the black/blank screen to get the phone to do something like activate the camera so I could hear the autofocus motor, but nothing seems to be working.
I can reset the phone by holding the power button for 5 seconds, the softkey backlights flash at about 1Hz for a few seconds and it reboots
I can boot into hboot, fastboot, and recovery (sadly all stock) by holding VOL- and POWER
Some people in this forum are having the same issue:
Google: "androidcentral.com AT&T HOX Update!!"
(sorry, I hope linking to another forum is okay I did not see the same subject here)
So AT&T acknowledged their update bricked my phone and they are shipping me a new phone, BUT.......
MY REAL PROBLEM is I have several pictures from a recent trip and I haven't figured out a way to get them off the phone. I'm cursing the non-removable SD Card now!:silly:
Two ways out of this I can think of, but I don't know exactly how to execute (1) and I'm unsure about (2):
Mount the SD Card in the stock bootloader (impossible?)
Run one of the RUU updates in the hope of un-bungling whatever that OTA update did (will it overwrite my /sdcard dir?)
(1) I see I could do this if I had the twrp recovery, but I haven't gotten around to unlocking this phone yet. (2) Can anyone confirm if the 1.85 or 2.20 RUU erases the /sdcard dir? I called HTC support, the tech support person said they were "98% sure 2.20 RUU wouldn't erase the SD card" but I was hoping some one could state that from experience on either the 1.85 or 2.20 RUU.
2.20 RUU is found here, along with a warning it could "possibly" erase /sdcard:
www htc com/us/support/htc-one-x-att/software-updates
Any input greatly appreciated. If I can get out of this bind, perhaps it is good I did not complete 2.20 after what I was reading through here!
I had the exact same issue. If I recall correctly I lost all pictures I took after doing the RUU, but the RUU did fix it.
However, the RUU will update you to the newest (not unlockable version) and you will lose hboot.
jimmymood said:
Beware, I installed AT&T's latest OTA update today, but something went wrong because I just get a black "blank screen" after the htc splash screen.
Symptoms are like this:
Power on
Get "HTC Quietly Brilliant" splash screen
AT&T Music plays, but the screen is black, no animated ATT logo
A few seconds later, the screen is still black, but the power button toggles the backlight on and off
I tried swiping my unlock pattern on the black/blank screen to get the phone to do something like activate the camera so I could hear the autofocus motor, but nothing seems to be working.
I can reset the phone by holding the power button for 5 seconds, the softkey backlights flash at about 1Hz for a few seconds and it reboots
I can boot into hboot, fastboot, and recovery (sadly all stock) by holding VOL- and POWER
Some people in this forum are having the same issue:
Google: "androidcentral.com AT&T HOX Update!!"
(sorry, I hope linking to another forum is okay I did not see the same subject here)
So AT&T acknowledged their update bricked my phone and they are shipping me a new phone, BUT.......
MY REAL PROBLEM is I have several pictures from a recent trip and I haven't figured out a way to get them off the phone. I'm cursing the non-removable SD Card now!:silly:
Two ways out of this I can think of, but I don't know exactly how to execute (1) and I'm unsure about (2):
Mount the SD Card in the stock bootloader (impossible?)
Run one of the RUU updates in the hope of un-bungling whatever that OTA update did (will it overwrite my /sdcard dir?)
(1) I see I could do this if I had the twrp recovery, but I haven't gotten around to unlocking this phone yet. (2) Can anyone confirm if the 1.85 or 2.20 RUU erases the /sdcard dir? I called HTC support, the tech support person said they were "98% sure 2.20 RUU wouldn't erase the SD card" but I was hoping some one could state that from experience on either the 1.85 or 2.20 RUU.
2.20 RUU is found here, along with a warning it could "possibly" erase /sdcard:
www htc com/us/support/htc-one-x-att/software-updates
Any input greatly appreciated. If I can get out of this bind, perhaps it is good I did not complete 2.20 after what I was reading through here!
Click to expand...
Click to collapse
Did you have USB Debugging enabled in Developer Options?
Also, did you have a custom recovery installed?
rohan32 said:
Did you have USB Debugging enabled in Developer Options?
Also, did you have a custom recovery installed?
Click to expand...
Click to collapse
Negative on both. I was seriously hoping there was some magical incantation using fastboot or something to get the SD card mounted. If I only had debugging on, I might just be able to use adb but I'm not even sure anything is really alive behind that blank screen. Any options with the stock boot loader/recovery?
rutro said:
I had the exact same issue. If I recall correctly I lost all pictures I took after doing the RUU, but the RUU did fix it.
However, the RUU will update you to the newest (not unlockable. ersion) and you will lose hboot.
Click to expand...
Click to collapse
So 2.20 erases the /sdcard directory? I wonder if 1.85 RUU does the same?
I also saw it was possible to pull the partition images out of the RUU by copying them out of the windows temp folder. Any chance I could re write the system partition only and get the phone to boot up again?
Thanks for all the input so far.
rutro said:
I had the exact same issue. If I recall correctly I lost all pictures I took after doing the RUU, but the RUU did fix it.
However, the RUU will update you to the newest (not unlockable version) and you will lose hboot.
Click to expand...
Click to collapse
The OTA will also update the hboot. It looks like he already did the OTA so it wouldn't hurt to ruu.
OP, was your bootloader unlocked and cid changed prior to taking the OTA? If so, you might wanna try to ruu 2.20 because chances are you may get a replacement with 2.20 already installed and you won't be able to root or unlock. Maybe even try the 1.85 ruu. The OTA might not have taken. Either way I think those are your only options. I don't think you'll be able to get your pictures back. Although I could have sworn when I ruu'd before that it kept all my pictures. I backup all my pics to Dropbox now.
Sent from my One X using xda app-developers app
File corrupted!
I've downloaded the update 3 times, 4th in progress. I keep getting the message "Downloaded File Corrupted, do you want to download again?" anyone else experienced this?
The RUU does not wipe your sdcard. I've done the 1.85 RUU and 2.20 RUU multiple times. My sdcard has persisted through every RUU.
WOO HOO!
Well it was a majority vote for "doesn't wipe /sdcard", I ran the 2.20 RUU from HTC's support site. After about 10 minutes, not only does my phone work again, I still have all the contents in /sdcard and my pictures. :victory: I had the 1.85 RUU as well, but it came from some file sharing site and I'm sometimes weary of running stuff from those places.
In summary:
If the OTA update bricks your phone the RUU available on HTC's website (see my first post) will fix the problem and preserve the contents of /sdcard.
OR if the OTA update bricks your phone and you want a new one, call AT&T because they still don't know how to fix this problem.
Thanks for the help!
Michael95GT said:
I've downloaded the update 3 times, 4th in progress. I keep getting the message "Downloaded File Corrupted, do you want to download again?" anyone else experienced this?
Click to expand...
Click to collapse
Try the RUU package from HTC's website I mentioned in the first post. This will apply the same update the OTA does, but it resets the phone back to factory (except for the contents of /sdcard)
SkizzMcNizz said:
The OTA will also update the hboot. It looks like he already did the OTA so it wouldn't hurt to ruu.
OP, was your bootloader unlocked and cid changed prior to taking the OTA? If so, you might wanna try to ruu 2.20 because chances are you may get a replacement with 2.20 already installed and you won't be able to root or unlock. Maybe even try the 1.85 ruu. The OTA might not have taken. Either way I think those are your only options. I don't think you'll be able to get your pictures back. Although I could have sworn when I ruu'd before that it kept all my pictures. I backup all my pics to Dropbox now.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Glad you got your stuff back.
Sent from my One X using xda app-developers app
Hey
I just got a huge bootloop while attempting to flash new Venom Room to my HTC One X. http://forum.xda-developers.com/showthread.php?t=1868236
I cannot access the recovery.. After restart (power button+volume down) i can get to bootloader section, but when i try to get into recovery, the phone just restart and stop on the white htc screen.
I already tried to reinstall recovery. Installation was successful, but the problem persists..
Before i had Incert Coins room.
The phone is unlocked, new recovery is installed
Please, help
If you had Insert Coin working on your phone, you have an international (Tegra3) version of the One X. This forum (and the Venom ROM you linked) are for the Snapdragon S3 version. Completely different hardware.
If I'm correct, you flashed a ROM for the wrong phone. Try running the RUU for your phone, but if that doesn't work you may be screwed. Recovery partitions are not the same for the versions. The ROM overwrote the recovery partition of your phone.
You are right.. It WAS the wrong rom.. I have tegra3 processor and this rom comes from american section..
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Senbration said:
But - is the RUU reinstall only one thing what i can do? I heard its dangerous
Click to expand...
Click to collapse
RUU just returns your phone to the stock condition. Stock ROM and stock recovery. There should be nothing dangerous about it. Just use the right one for your version, carrier, etc. But the CID check should ensure that you don't run the wrong RUU (if RUU is for a different CID, the RUU will not run).
Only thing with RUU, is that it wipes all user data. That may be why you heard its "dangerous". But in the condition you are in, this is not even a consideration anymore.
RUU is not dangerous, and it may be your only hope at this point.
You will need to lock your bootloader before running the RUU.
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
I'm assuming you meant relocked bootloader and now has security warning relocked if this what you meant then you are fine flash the ruu
Sent from my Nocturnalized One XL using Forum Runner
Senbration said:
I've relocked bootloop. But now there is an information "RELOADED, Security Warning"
Will be safe to flash stock RUU now?
Click to expand...
Click to collapse
You mean relocked and not reloaded? If so, you should be good to run the RUU. Redpoint, sorry for highjacking your help session
Sent from my One X using xda premium
ohh, its Relocked.. Im just a bit nervous right now hoping it will unbrick this phone..
Just 3min to complete RUU download.
Do U guys think this stock RUU will rewrite the partitions back?
I've noticed another problem.
Cannot load RUU because the battery level is lower then 30%.
But when i plug the charger the light doesnt flash. It starts to flash when i switch on the phone.
Also cannot switch the phone with the power button. It restart all the time. Only can do that from bootloader command "power down". But when the phone is off the power light doesnt flash..
Does it mean that the battery is not charging at all? Because the light can flash only because the power is low..
The phone shut down completly now.. Does not charge the battery at all.. Power gone off and i cannot even turn on the phone..
Is there any solution how to make it charge?
Ok, the problem is that the wrong ROM i tried to install changed partition and also it seems it destroyed Recovery..
Without recovery the phone cannot charge while being in bootloader mode...
Is there any way to make phone charging when Recovery doesnt work and cannot be flashed?
Please help
Take the phone apart. I mean all the way spart and hardwire a charger to the phone/ battery. Its a pain but you can do it.
Ohh..
I found a treat http://forum.xda-developers.com/showthread.php?t=1658084
There is a way to charge battery by running the script, which makes phone reinstalling constantly. Each time it is reinstalled, the battery is charged a little bit more.
After mayby 40min i went up from 3686 V to 3720 V.
It seems that my only hope is to reinstall RUU. I tried to flash wrong ROM, from wrong model and as one user wrote above, it has rewritten my partition. Same time it destroyed recovery.. I cannot flash recovery now because the partition is rewritten...
And without working recovery i cannot charge the battery being in bootloader.. If i understand it all correctly.
I already tried to install RUU with 3710 V. It started to install, but stopped after few min with information that battery is too low..
So i think ill leave this script running for a whole night, and hope, in the morning battery will be charged just enough to install RUU eventually..
Uff
Okey, finally its fixed..
After 7 hours of constant reinstalling the phone by the script, the battery was loaded enough to finish RUU instalation process.. (battery went to about 3830mV power)
After oryginal RUU was installed, everything went fine.
Now i already re-unlocked the bootloader, re-rooted the phone and all works correctly.
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Amazingly impressive to me.
Thanks for following up with your success.
WR
Sent from a CleanRom-V OneX
THAT is AWESOME
Senbration said:
Thanks all people who helped. Mostly to redpoint73, who diagnosed the problem straight away and put me on the right track.
Click to expand...
Click to collapse
Your welcome, and no problem really. It was an easy problem to recognize, as I've seen it several times before on here.
Nice job getting the phone charged. Haven't seen that solution before.
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Sent from my HTC One X using Tapatalk 2
Senbration said:
Thanks people for not calling me a noob and not blaming for installing the wrong ROM. Even though it was a silly mistake..
Click to expand...
Click to collapse
Sh1T! Did I forget to do that???? I must have been in a good mood . . .
Heh it must have been so
Sent from my HTC One X using Tapatalk 2
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Should have read this first:
http://forum.xda-developers.com/showthread.php?t=2181929
Sent from my One X using Tapatalk 2
No, I don't have neither..
iElvis said:
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
the whole process took awhile for me, felt like it rebooted a few times also. about 20 minutes i think, you could of got in a hurry during the process and messed it up. does the phone detect? maybe u can reruu?
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
The LED does not come on, believe me I have tried keeping it on the charger all night, with no success.
redpoint73 said:
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
Click to expand...
Click to collapse
I tried this, and nothing happened.. I will head to my nearest AT&T store soon to get a replacement hopefully.. I guess its not all bad though, I have been enjoying my Lumia 920 with Windows phone 8, but I am missing my Android!
iElvis said:
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
Click to expand...
Click to collapse
hrrsncrawford14 said:
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Click to expand...
Click to collapse
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
nmupparaju said:
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
Click to expand...
Click to collapse
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I'm sure it's the same thing.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I did get supercid, unlocked bootloader installed cm10 relocked bootloader, ruu to 2.20 used for few days, used update tool from htc website to update to jellybean, after using the tool phone never booted back , dead (I guess brick)
When connected to windows pc qhusb_dload shows up
nmupparaju said:
When connected to windows pc qhusb_dload shows up
Click to expand...
Click to collapse
You've got a brick. Sorry. It's not clear why this is happening, but once you're in that mode, you're done.
I flashed twrp recovery from HOX interational version by mistake. Now the phone is stuck in bootloop. Tried to boot into bootloader by pressing vol down + power but that didnt work and i also tried to reboot via adb but that also threw me an error . I cant even turn off my phone it just keep rebooting.. Is there anyway i can revert this? Btw my phone is recognized by PC in disk manager though.
My phone is s-off and unlocked.
Any help would be appreciated.
Hold the volume down button while it's rebooting, do not let go, it should hopefully get to the bootloader. The next problem is that you could have borked the recovery partition by flashing the wrong recovery. Try to flash the right recovery, it might work. Otherwise you'll need to run an RUU.
Out of interest, how in the world did you manage to flash a recovery from the Endeavoru?
Sent from my Evita
rangers said:
I flashed twrp recovery from HOX interational version by mistake.
Click to expand...
Click to collapse
Be extremely careful to only flash mods from this forum section specific to the EVITA: http://forum.xda-developers.com/one-x-att
You can also use my Index thread (also EVITA specific): http://forum.xda-developers.com/showthread.php?t=1671237
Especially since you are s-off, you need to be extremely careful about what you flash (and you obviously were not) since all safety checks (such as device check) are disabled with S-off. Different devices have different partitions, and flashing a mod for another device could have easily messed up the hboot partition and bricked the phone.
The fact the phone still turns on is a good sign, and you can probably get it sorted at as timmaaa instructed in the previous response. But consider this a close call and don't make the same mistake again.
Thank you so much timmahy. Just pressing volume down worked and I flashed a RUU after. I was searching for "recovery for hox" on Google and I found one and it happened to be the international versions twrp recovery. This is my gfs phone and I really did not know about the whole evita and hox Tegra difference. Thanks a lot again
Sent from my Nexus 5 using xda premium
Cool, glad to help. Just make sure you only stay within our forum, the main page is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Sent from my Evita
rangers said:
I was searching for "recovery for hox" on Google and I found one and it happened to be the international versions twrp recovery. This is my gfs phone and I really did not know about the whole evita and hox Tegra difference.
Click to expand...
Click to collapse
Google is not your friend, when searching for phone mods. Stick to the proper XDA forum, and always do the proper research to be absolutely certain you are flashing the right thing. There are plenty of devices (not just the HOX) with different carrier versions, variants, etc. that can get you bricked if you flash the wrong version.
Hello everyone,
My gf is having an issue applying an OTA to her U11. It was bought off Amazon, and had some Chinese app on it when we got it.
Anyways, there's an update notification she can't get rid of, and when she tries to update it always fails...
I have a link to a folder with all the phone info and failed update screenshot. We even tried a hard reset then updating with the same outcome.
This is driving her nuts! If some could point me in the right direction I'd be very grateful. I searched OTA fail and came up with 0 results...
Photos: https://drive.google.com/folderview?id=1y8Cin-JD2kf9uZ0SWka4Kh4C-i1cTCtP
Have you booted the phone in recovery, to see what was on it? With the phone off, hold Vol up and power while it boots up. My guess is the recovery was replaced by the previous owner and they were flashing ROMs. Bet you find twrp or something
I get this: https://drive.google.com/file/d/1wlDtgNaZ24yWkm4MntVhX50FfUpmj-0R/view?usp=drivesdk
Any ideas?
Android_Guy said:
Any ideas?
Click to expand...
Click to collapse
Have you tried resetting your phone using a ruu that matches your type of phone ie mid/cid?
hammered58 said:
Have you tried resetting your phone using a ruu that matches your type of phone ie mid/cid?
Click to expand...
Click to collapse
This would be my next reconnection as well. Use the cable that came with the phone, hold power + vol down to start up in download mode, run their ruu.exe.
Sent from my 2PZC5 using Tapatalk
It seems like your system partition is corrupted or your unit has been refurbished. Maybe @5m4r7ph0n36uru can help you.
Hmm, so what do we have here .. seems to be a Japan U11 UHL edition.
There are some options. Either the ROM has been somehow corruptet, which could be solved by flashin the proper Japan RUU.This one's not on my spreadsheet I fear so you'd have to download it from easy firmware. Maybe you should even download latest RUU and flasdh it, to make sure you're on the current firmware. Second option would be to unlock the bootloader, download WWE/EMEA RUU, go temp S-OFF, change CID/MID to international ones HTC__034/2PZC10000 and flash the RUU you downloaded, and relock the bootloader. This would in one single step convert the device into an internatinal one
5m4r7ph0n36uru said:
Hmm, so what do we have here .. seems to be a Japan U11 UHL edition.
There are some options. Either the ROM has been somehow corruptet, which could be solved by flashin the proper Japan RUU.This one's not on my spreadsheet I fear so you'd have to download it from easy firmware. Maybe you should even download latest RUU and flasdh it, to make sure you're on the current firmware. Second option would be to unlock the bootloader, download WWE/EMEA RUU, go temp S-OFF, change CID/MID to international ones HTC__034/2PZC10000 and flash the RUU you downloaded, and relock the bootloader. This would in one single step convert the device into an internatinal one
Click to expand...
Click to collapse
Trying option one right now....hope it doesn't come down to the second one. I feel like its been forever since I messed with HTC phones and all the RUU, S-Off, etc that goes with them!
I appreciate your responses and keepong my fingers crossed. I'll let ya know if it works! :good:
Some cell phone repair places could unlock and set you up for international. Might be worth asking if you don't want to dive to deep
Sent from my 2PZC5 using Tapatalk