Related
Hi, I tried to update the system on my phone and when it did a reboot after updating and installing, it is freezing on the white/logo startup screen. how can i proceed...?
Remove the battery to turn the phone off, and when turning back on, hold down the power+volume up buttons. This will put your phone in hboot mode and allow you to reflash your ROM from there.
Good luck.
Sent from my Incredible S using xda premium
thanks. Yes i did make it to that step. now i need to flash the official rom for my model which is S710e, but i found so many links that i'm confused which one is the official...can i have some indication...
thanks in advance
If you flashed a custom rom and it is stuck in white screen with logo, your boot partition is messed up. But no worries you can fix it.
Extract the boot.img file out of your custom rom (zip-file).
download the SDK files
put the boot.img in the same folder as the files
Boot phone in fast boot
connect phone through usb with a computer
open command prompt on the pc an go to folder
use command fastboot flash boot boot.img
wait 2 secs
reboot
whole proces takes maybe 10 min, very easy to do.
no i did not flash a custom rom. i just did a system update which was prompted to me on the phone itself; when i did this it got stuck on reboot. then i did a factory reset but it was in vain.
at this point what i want is to have my phone back as it was in the beginning...so I wish to know how i can flash a stock rom so that it will become like brand new. thanks.
atlam83 said:
... I wish to know how i can flash a stock rom so that it will become like brand new. thanks.
Click to expand...
Click to collapse
First, you have to know what your mainver is:
Boot into fastboot, open a cmd window in windows and type this:
Code:
fastboot getvar mainver
This will give you your mainver (e.g. 2.12.708.4)
And go here: http://www.filefactory.com/f/e45d6fe3dcf51228/
You'll find shipped rom list. The filenames are in format like this: RUU_[name][mainver][radio_version]_signed.exe You must select ones with WWE prefixes (for multi-language support) and higher mainvers than yours! For example, if your mainver is 2.12.708.4, then you can select RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed (this one's mainver is 2.33.669.2) in the shipped rom list.
Once you've downloaded, you'll face another problem: Flashing.
Flashing is not a real problem but needs some trickies.
The question: Have you rooted your phone?
If yes, this thread is your flashlight to enlighten your way..
If no, you have to obtain a goldcard. A goldcard is a special microSD which prevents the phone to check cid (Customer ID) while trying to flash an original rom. If you haven't created a goldcard yet and cannot boot your phone properly, find another Android based phone and insert your microSD card into it. Then read this thread to create your gold card. Once you've created your goldcard, then it's so easy for you to flash your original rom. Follow the steps in the link above (explaining how to flash).
hth.
-R
i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.
atlam83 said:
i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.
Click to expand...
Click to collapse
Did you previously use Revolutionary to gain S-Off on your phone. If so by trying to install the OTA update, you now have a HBOOT ROM mismatch. The OTA update requires that the HTC HBOOT 2.00.0000 be installed, but the Revolutionary S-Off HBOOT prevented the OTA from overwriting the hboot, thus creating the situation you are in.
Follow steps 1 - 2c on this thread.
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
The find the OTA file on your SD card and extract the file firmware.zip.
Copy this to the root of your SD card and rename it PG32IMG.zip and then reboot into bootloader and it should reflash the correct HBOOT and you should be good to go.
Thanks very much tpbklake, I managed to solve my issue following the thread you indicated. its been 3 weeks since last i used my mobile. Send it to various ppl including HTC (which did not want to fix my mobile) and no one fixed it. have tried that thread and now its fine working again )
HTC freezing on thie logo startup screen
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(
Aniok said:
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(
Click to expand...
Click to collapse
All you need to do is go to the Development section and upgrade from Revolutionary HBOOT 6.13.1002 to BlackRose 2.02.0002. That will allow your phone to boot.
http://forum.xda-developers.com/showthread.php?t=1509236
Thanx
..
Sent from my GT-I9300 using xda premium
Please read and understand the guide and accompanying links in their entirety before beginning.XDA and I am not responsible for anything you do to your phone.
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
While trying to run an RUU to reset my phone, I kept running into an issue: "htc_fastboot.exe has stopped working". I could get my phone to restart, but the RUU would not run successfully. I searched this site and the internet for an answer, but could not find anything that worked for me. Also, a lot of people in Q&A tend to have issues getting the RUU to work. That's why I'm writing this guide. Hopefully someone who is having trouble will search and stumble across it. I tried everything I could find - Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update so the guide is written from that perspective.
Steps:
1. Make sure that your computer can see your phone when you boot into fastboot. It should say Fastboot in red that changes to Fastboot USB when plugged into your computer. There are guides that help with this, so I'm not going to go into much detail. Basically you install HTC Sync to your computer and then uninstall it but leave the drivers.
2. Get a copy of fastboot and ADB. The easiest way is to get the SDK from Google (tools only) as it also includes drivers, but you can get just fastboot and adb from here (I did not use this tool personally).
3. To verify that your phone and computer are talking, open a command prompt window (I always open as administrator) and go to the folder that contains fastboot. Type "fastboot devices" (no quotes) and it should list your phone. If it does not, something did not work right with steps 1 and 2.
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes).
5. Download the Full Firmware from RUU here. While you're there, get the RUU as well. Make sure to get the one that is not decrypted (first link). Copy both into the folder with fastboot.
6. Flash the firmware file using fastboot following the directions in the OP from where you got it. To summarize, rename the firmware zip file to firmware.zip. Then at a command prompt, type "fastboot oem rebootRUU". When the phone shows a black screen that says HTC, type "fastboot flash zip firmware.zip". The command prompt window will show a bunch of stuff as it does its thing. When you get back to the command prompt, it's finished. At this point, type "fastboot reboot-bootloader" to restart back into the (hopefully now stock) bootloader. Personally, I had to repeat the last command again because it failed the first time.
7. At this point, you should be in the stock hboot. It should say fastboot USB in red. Now time to RUU.
8. The current RUU is an exe so run the RUU you download before (if you have a zip file, unzip the RUU and run ARUWizard.exe). I personally ran it as an administrator just to make sure limited privileges didn't cause an issue. Read each screen and keep clicking next. Eventually it will do its thing. It takes about ten minutes and sometimes seems to be frozen. Have patience grasshopper.
And that's it. I'm now running pure stock (not for long I'm sure), still s-off. If you are s-on, you will have to unlock your bootloader again.
Good luck!
I'll be the first to troll post in this guide
Nice work brother.
I've noticed the newer RUU's (M7 and M8) require you to have the matching hboot to run correctly even if your device is s-off.
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
kushanson said:
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
Click to expand...
Click to collapse
You're welcome. Glad it helped. Also, thank you for the heads up about the RUU being an exe now. It was a zip file when I wrote the guide. I've fixed the guide to reflect the change.
Dude...
I was soft bricked for about an hour until I found this. It seems fairly obvious to me now, but for some reason I had thought that only flashing the full_firmware zip in fastboot would suffice. I guess the tiny file size (80MB unzipped???) should have tipped me off.
Regardless, I'm back up and running. Thanks, coal.
i am getting error bootloader signature failed how to fix please
rajnshubham said:
i am getting error bootloader signature failed how to fix please
Click to expand...
Click to collapse
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
coal686 said:
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
Good luck!
Click to expand...
Click to collapse
Thanks for your guided I was able to fix an old One that I had laying around, thanks again
coal686 said:
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
Click to expand...
Click to collapse
i think the problem was due to same hboot error. i get to know this thing few days back. anyway thanks coal686. now i updated with the ruu having hboot 1.56 and now i m on kitkat 4.4.2 stock. i can update now to higher ones. thanks buddy
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for using my guide!
The first step is to flash the "full firmware from RUU" (it's actually labelled that way in the OP of the linked post). It's only the firmware, not the full RUU. Then, follow that up with the .exe file which is the entire RUU. For some reason, the RUU wouldn't run for me without flashing the firmware first.
Since you are already on hboot 1.6, you probably don't have to flash the firmware first, but I'd do it just to be safe.
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
biker57 said:
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Just run it. Fastboot flash the firmware then just run the RUU exe.
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
cowboysgz said:
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
Click to expand...
Click to collapse
.
Thanks
Device not recognized
Whenever I plug in my device and go to fastboot, my computer tells me "USB Device not recognized". I've installed the drivers from HTC, I even went to Decide manager on my PC to see if the device appears at all. It shows on the top under "Android USB Device" and it's labeled "My HTC" but it has the error symbol on it, so o deviced to unistall the driver and install it manually. It said that I already had the correct driver.
The reason I'm trying to do all this is, back in 2013 I had put Viper ROM on my device, it worked great, I also installed cyanogen mod as well and that worked great, at the time I wanted to have the double tap to wake feature, so I installed a custom Kernel to allow that. When I had booted up my phone the HTC logo didn t go away, then the lock screen showed up, I unlocked my phone, the HTC logo was still there, then my home screen finally opened and some apps wouldn't open. Then it would restart, so I rebooted it and it would do the same thing, turn on, show the HTC, start then restart. I could go into recovery fine, Install updated version of rom, and the same problem persists
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
krakora said:
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
Click to expand...
Click to collapse
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
coal686 said:
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
Click to expand...
Click to collapse
Thanks so much Coal, that absolutely worked. The RUU exe runs for me, but getting 155 unknown error. Evidently its not the right RUU for my device. My bootloader is "relocked" already, S-on. So confusing. When I was following the directions on the guide, when flashing the firmware, I was getting the 12 missing signatures error also, I'm assuming its not reading it as an HTC signed firmware. Any ideas on my next direction? Best, Rich
in short, I have a playstore M7_UL that just won't switch to LTE after flashing a couple of lolipop based roms, I already tried messing around with the APN settings. stock roms such as this one (http://forum.xda-developers.com/showthread.php?t=2499452) will work properly with every single feature the phone should have if it was originally from T-Mobile, however I would Ideally like to update my phone to 12.
do you have any suggestions for this problem? or am I stuck with this 4.3 rom? I would like to thank you in advance for your time and consideration, and I wait eagerly for your response.
BNMotive said:
I've tried updating to several Lolipop roms, flashed 2 different radios as well as double checked APN settings and confirmed that my Sim card does support LTE however no luck, I've been having the issue of not being able to retain LTE support. only rom that worked completely was this one http://forum.xda-developers.com/showthread.php?t=2499452 the help would be greatly appreciated to resolve this nightmare.
my carrier is T-Mobile.
Click to expand...
Click to collapse
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
majmoz said:
That is a very old ROM, have you updated your system to the latest Sense 6 firmware? If not, then you might want to run the latest TMOUS RUU. When completed, check to see if you have LTE. My guess you will, then if you want you can try one of the Lollipop ROM.
Click to expand...
Click to collapse
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
BNMotive said:
this makes a ton of sense to me, so I decided to downloaded this RUU http://forum.xda-developers.com/htc-one-tmobile/general/ruu-t-mobile-htc-one-android-4-4-3-t2995420
I tried flashing it through my PC but I get this "Error [170] USB connection error" I read briefly over the code and there are some mentions of re-locking my phone, before I get deeper into this, do you have any suggestions for flashing the right RUU?
I really appreciate the help
Click to expand...
Click to collapse
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Utterly Clueless
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
BNMotive said:
Finding the "right" RUU was difficult but I got it "working" I flashed RUU: "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed" that had 4G, then I unlocked and rooted once more, unfortunately I am currently still stuck with CM12 in 3g/h+, so am I missing something? I thought that by flashing a stock Sense RUU and then updating to CM12 that would help me get what I needed for 4G, any advice is greatly appreciated.
Click to expand...
Click to collapse
if you have a read through the CM12 thread or use the search feature within the thread itself, you will find that 4G / LTE is currently a problem for most users and in all not working, seem's to be a problem with 11 and 12 at the moment.
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
BNMotive said:
tried installing the first one, I get Error [155] "The ROM update utility cannot update your android phone. please get the correct ROM update utility and try again."
is there a way to give detailed information of my phone's firmware status? would that help? I thank you for the help.
Click to expand...
Click to collapse
as you are s-on you will need to do the updates in order, therefore your next one you'll need will either be a 1.28.531.xx or 1.29.531.xx or even 2.24.531.xx, you need to do them in the correct order otherwise you'll just keep erroring out, easier to just s-off on your current firmware.
you cant jump from 1xxxxxx to 3xxxxxxx
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
BNMotive said:
Windows 8.1 proved to be a very bad choice to begin flashing old RUUs. USB drivers went rogue on me, so I decided to switch to an old beat up windows 7 system. worked like a charm, I was able to flash 1.2 and 3.2 things were looking up till tried 4.2, both windows 8.1 and 7 killed the installer, 7 says it is a USB error [171] while 8.1 says it is the wrong RUU. apparently I am not the only one with this issue, I'll see what I can find. I feel that thanks to your help guys I am getting real close, I can almost smell the sweet scent of fresh 4G lolipop brewing.
Click to expand...
Click to collapse
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
majmoz said:
Yes, if you are S-ON you need to re-lock your bootloader. You can use this command in bootloader/FASTBOOT USB:
Code:
fastboot oem lock
Your bootloader should say Relocked, leave the phone connected to the computer then run the RUU.
Click to expand...
Click to collapse
majmoz said:
I think you have a gross firmware - ROM mismatch. You are running version 1.XX firmware with a version 6.XX or 7.XX rom. You need to update your phone to at least version 6.XX and then see if CM12 will give you 4G. If you still have troubles with it in CM12 but not in the stock then it is CM12 that is the issue! These need to be done in order so that you don't brick your phone!!!
RUU 3.24.531.3
RUU 4.19.531.10
RUU 5.14.531.1
RUU 6.10.531.10
Click to expand...
Click to collapse
Seanie280672 said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone, recheck your drivers with the phone booted and plugged into the computer and also recheck your drivers with the phone in the bootloader and plugged into your PC, I think you might find when its in the bootloader you have "One" with a yellow exclamation mark in device manager, you will have to manually force the driver, right click and select update driver, you the manual installation instructions, don't let windows search anything itself, it will fail.
have you also tried to just run the updates from your phone, ie settings - about - software updates ?
Click to expand...
Click to collapse
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
BNMotive said:
after the first comment in this post yeah, I had installed a very early TMOUS RUU, from there it asked to be updated to Sense 6.0, I let it update and from there I flashed CM12 and I had no 4G. would something different happen if i try this again now that I flashed 1.2 and 3.2?
more info though, both computers do "update" the phone but get interrupted. regarding the "wrong" RUU error message from windows 8.1, it says "ERROR[158]: Image Error"
Click to expand...
Click to collapse
Im sure I read through here somewhere ages ago about users having problems with the 4xxxxx update, have a search through this forum for T-Mobile RUU, it was in the main RUU thread, and im sure someone fixed it too.
http://forum.xda-developers.com/htc-one-tmobile
I flashed a gsm rom on my sprint m7, which put it into a bootloop....
I tried the firmware fix , but ended up with signature failures.
I haven't been able to get the RUU.exe to run on my windows 8 machine.
Wondering if anyone can supply me with 5.05.651.02RUU flashable zip?
I've searched, and see a bunch of flashable firmwares, but non for 5.05.651.02.
Or maybe a solution to my ruu.exe problem? I've tried the guides supplied in this forum, but still can't get passed the installation screen.
Thank you !
Can u open the ruu at least to the first menu
phonegeekjr said:
Can u open the ruu at least to the first menu
Click to expand...
Click to collapse
No, just install wizard "loading" . when its done it either freezes the computer , or does nothing.
I have tried to open it using "compatibility" which tells me to use win 7. But no luck.
Looking for a way to just push it too the phone. Seems easiest.
Supertacomonkeyexplosion said:
No, just install wizard "loading" . when its done it either freezes the computer , or does nothing.
I have tried to open it using "compatibility" which tells me to use win 7. But no luck.
Looking for a way to just push it too the phone. Seems easiest.
Click to expand...
Click to collapse
Hmm can I have the link to where you got it. And out of curiosity why not upgrade to 6.16.651.2 which is lollipop
phonegeekjr said:
Hmm can I have the link to where you got it. And out of curiosity why not upgrade to 6.16.651.2 which is lollipop
Click to expand...
Click to collapse
I can use 6.16.651.2 flashableRUU ?
The phone is unusable right now, bootloops. I thought I had to be s-off to flash anything but the firmware that's present. Am I wrong?
My end game was to use the phone on at&t. I thought I could flash a gsm ROM to accomplish that.
Can I still s-off and sim unlock lollipop? Or at least s-off and downgrade?
Thanks for the help
I tried downloads from here:
[RUU][Firmware]Sprint HTC One | 6.16.651.2 | *Updated 2.10.15*
And I also tried the RUU from the official HTC website.
And I also tried the ripped "firmware only" from http://forum.xda-developers.com/showthread.php?t=2503646
There is an ruu in that thread that has a fastboot flashable zip. You might want to read through how to run it on your device. You shouldn't ever flash a gsm Rom to a Sprint phone. The mount points are different.
Solution: get a new computer.
Not sure what was going on but I could not get the ruu to run on windows 8.1. Drivers, adb,fastboot all working on the computer. I couldn't find the problem.
Dug up an old windows XP machine I have , worked in an instant.
No knowledge gained.
The RUU exe take a lot of RAM to run. please make sure you have no other programs running when running the exe. If you device is stuck in a boot loop try power the device down and into recovery mode. Then connect to terminal when the RUU ask to connect to the device. My guess is the the RUU is corrupt and try re-downloading the file. If all else fails relock the boot loader and try returning to stock.
Hello everyone
I have some trouble with returning to full stock. Yesterday I thought that I totally bricked my phone. Today it's working on UK Version from one of thread searched in this forum. I have RUU file for my version (i think so). When I'm try to follow steps from tutorials, it ends with fail
Now I have philz recovery, and stock rom UK version.
I started RUU on XP and follow the steps, when I am chosing update it doesn't find my phone.
Maybe it's the case that I have S-ON?
I'm not expert in this area, so please be patient.
Many thanks in advance.
Barti1XL said:
Hello everyone
I have some trouble with returning to full stock. Yesterday I thought that I totally bricked my phone. Today it's working on UK Version from one of thread searched in this forum. I have RUU file for my version (i think so). When I'm try to follow steps from tutorials, it ends with fail
Now I have philz recovery, and stock rom UK version.
I started RUU on XP and follow the steps, when I am chosing update it doesn't find my phone.
Maybe it's the case that I have S-ON?
I'm not expert in this area, so please be patient.
Many thanks in advance.
Click to expand...
Click to collapse
Being s-on doesn't mean anything you can still fix and return a phone to stock and if you already have the phone up and running just find out what your carriers APN is and input that info and you'll be able to get back online and make calls, texts etc.. If you want to S-Off for more control then visit The Root Ninja Sunshine S-Off HTC Desire 510
MrMike2182 said:
Being s-on doesn't mean anything you can still fix and return a phone to stock and if you already have the phone up and running just find out what your carriers APN is and input that info and you'll be able to get back online and make calls, texts etc.. If you want to S-Off for more control then visit *** The Root Ninja Sunshine S-Off HTC Desire 510[/URL]
Click to expand...
Click to collapse
Hi there,
I'm online now, I can make calls etc. But I just want to know, it's possible to return to full stock (I mean recovery, kernel and rom).
I tried to use RUU, but i doesn't work.
When I'm in bootloader I see :
*** Software status : modified ***
*** UNLOCKED ***
*** Security warning ***
When I'm running RUU, I see only option to update software, but on my phone is UK version, and RUU which I use is EU version.
Regards
Barti1XL said:
Hi there,
I'm online now, I can make calls etc. But I just want to know, it's possible to return to full stock (I mean recovery, kernel and rom).
I tried to use RUU, but i doesn't work.
When I'm in bootloader I see :
*** Software status : modified ***
*** UNLOCKED ***
*** Security warning ***
When I'm running RUU, I see only option to update software, but on my phone is UK version, and RUU which I use is EU version.
Regards
Click to expand...
Click to collapse
The EU version I posted works for your phone however i'd keep your phone the way it is because you will have to lock the boot again and reinstall a stock recovery to run the RUU which I can't seem to find(the stock recovery) for your phone and without it you cannot run any RUU.
MrMike2182 said:
The EU version I posted works for your phone however i'd keep your phone the way it is because you will have to lock the boot again and reinstall a stock recovery to run the RUU which I can't seem to find(the stock recovery) for your phone and without it you cannot run any RUU.
Click to expand...
Click to collapse
Actually, I found stock recovery for EU version (on polish forum, btw I'm from Poland). But I don't want to put in there, before I test it. So, please verify my steps.
1. Relock the bootloader. After that I see information which I posted in my previous post.
fastboot oem lock
fastboot reboot-bootloader
2. Reboot to bootloader, flash stock recovery.
fastboot flash recovery [name of my stock recovery]
fastboot reboot bootloader
3. Reboot to bootloader, run RUU.
After that I should have stock software. If I made somewhere any mistake, please tell me. If it will be okay, I'll upload a recovery, so the others will been able to do the same thing.
Regards
Barti1XL said:
Actually, I found stock recovery for EU version (on polish forum, btw I'm from Poland). But I don't want to put in there, before I test it. So, please verify my steps.
1. Relock the bootloader. After that I see information which I posted in my previous post.
fastboot oem lock
fastboot reboot-bootloader
2. Reboot to bootloader, flash stock recovery.
fastboot flash recovery [name of my stock recovery]
fastboot reboot bootloader
3. Reboot to bootloader, run RUU.
After that I should have stock software. If I made somewhere any mistake, please tell me. If it will be okay, I'll upload a recovery, so the others will been able to do the same thing.
Regards
Click to expand...
Click to collapse
Correct.
MrMike2182 said:
Correct.
Click to expand...
Click to collapse
Hi there, it's me again.
I finally get into RUU, and start STOCKing but it stops at step 2/8 (updating software - 100%). I wait 10,20,30 minutes and nothing...
I don't have any idea what I can do. I run XP on VM Oracle, because on 8.1 I was unable to start RUU.
Could you have access to any backup for Philz recovery?
Regards
Barti1XL said:
Hi there, it's me again.
I finally get into RUU, and start STOCKing but it stops at step 2/8 (updating software - 100%). I wait 10,20,30 minutes and nothing...
I don't have any idea what I can do. I run XP on VM Oracle, because on 8.1 I was unable to start RUU.
Could you have access to any backup for Philz recovery?
Regards
Click to expand...
Click to collapse
It's most likely stuck because your stock recovery is either not the correct one, or installed incorrectly. The RUU is known to stop there when it detects that the recovery partition has been modified and doesn't have the stock one on there... I also have no idea where to get you a stock recovery.img... I'm sure there is one around the net somewhere, if you search for it.
What do you exactly mean? I try to extract recovery from rom.zip from RUU temp folder but archive is incorrect or something like that. Later I'm going to extract it using unruu on Ubuntu 15.10.
Regards