Hi guys i knew the ins and out of my galaxy S3, but need help with my htc one
I know this is a big ask but having a real bad time trying to get this sorted, but need to get back to stock for new digitizer replacement.
i am running ARHD 11 with unlocked bootloader S-off, latest firmware. and twrp on my UK HTC_001
Is there a full guide to get me back to stock, as i have trawled through the forum and have about 10 tabs with various information but its getting to confusing as to what to do first with out bricking my phone.
i tried to do my stock nandroid backup first but that gave me no touchscreen function, not sure if that's because i have updated to the latest firmware, so had to flash ARHD back to get touchscreen function agian.
i then relocked the bootloader and that wiped my phone so had no system to boot into just cwm recovery. Tried to sideload rom but that didn't work adb error closed.
then i fastboot flash twrp, and then usb otg flashed arhd 11 from usb stick, working agian.
this is doing my head in, been at this for 3 days and getting nowhere
in what order do i go about this to get to full stock without bricking
need to be S-on
locked bootloader
revone locked not relocked
stock uk HTC_001 unbranded rom
unroot.
Big thanks in advance guys if you can help.
You should be able to install a 401 RUU and then
./revone -l
fastboot oem writesecureflag 3
thanks benpope, need a bit more of a guide dude,
not sure what RUU i need, my phone is uk unbranded htc_001
do i fastboot the RUU rom?
revone-l , is to turn relocked to locked i guess
thanks
Sent from my iPad using Tapatalk HD
I would gain S-off and unlock bootloader again then flash this RUU in fastboot
http://bugsylawson.com/files/file/1...13323127-1031113105-release-310878-signedexe/
RUU (ROM Update Utility)
Connect your device to the PC
Open/run the RUU and follow on screen instructions.
Set up your phone once it reboots then check for software update and you should get the 1.29.401.12 update.
When you have installed the update you can use revone to set S-on and lock your bootloader.
./revone -l
fastboot oem writesecureflag 3
This is what I did and it worked for me.
jake460 said:
Hi guys i knew the ins and out of my galaxy S3, but need help with my htc one
I know this is a big ask but having a real bad time trying to get this sorted, but need to get back to stock for new digitizer replacement.
i am running ARHD 11 with unlocked bootloader S-off, latest firmware. and twrp on my UK HTC_001
Is there a full guide to get me back to stock, as i have trawled through the forum and have about 10 tabs with various information but its getting to confusing as to what to do first with out bricking my phone.
i tried to do my stock nandroid backup first but that gave me no touchscreen function, not sure if that's because i have updated to the latest firmware, so had to flash ARHD back to get touchscreen function agian.
i then relocked the bootloader and that wiped my phone so had no system to boot into just cwm recovery. Tried to sideload rom but that didn't work adb error closed.
then i fastboot flash twrp, and then usb otg flashed arhd 11 from usb stick, working agian.
this is doing my head in, been at this for 3 days and getting nowhere
anks in advance guys if you can help.
Click to expand...
Click to collapse
If i were you i would write superCID from here http://forum.xda-developers.com/showthread.php?t=2317536. leave S-Off as it is and only lock the bootloader and then just flash the latest WWE RUU and you`re done. Unless you have a problem with your phone and need to turn it in for repair.
Cheers guys will give it a go in the morning, on nightshift at the mo
Sent from my HTC One using xda app-developers app
Getting stuck at RUU error 170 usb cable connection, must be a driver error.
Sent from my HTC One using xda app-developers app
Adb updated, htc drivers, HTC sync, pdanet installed but still getting RUU ERROR 170 usb cable not connected when trying to run Ruu Rom. Adb devices dosent see my device, it did 2 days ago.
No driver installs when I plug phone into pc in bootloader mode, pdanet used to pop up too, but dosent any more, reinstalled them all but still the same, even used cccleaner to fix registries.
Any advice on this one thanks.
Sent from my HTC One using xda app-developers app
jake460 said:
Adb updated, htc drivers, HTC sync, pdanet installed but still getting RUU ERROR 170 usb cable not connected when trying to run Ruu Rom. Adb devices dosent see my device, it did 2 days ago.
No driver installs when I plug phone into pc in bootloader mode, pdanet used to pop up too, but dosent any more, reinstalled them all but still the same, even used cccleaner to fix registries.
Any advice on this one thanks.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I have a zip you can flash which will fully hard brick your phone with no chance of HTC recovery if you need it, will probably result in a new phone and not just a new touchscreen.
MacHackz said:
I have a zip you can flash which will fully hard brick your phone with no chance of HTC recovery if you need it, will probably result in a new phone and not just a new touchscreen.
Click to expand...
Click to collapse
PM sent
Sent from my HTC One using xda app-developers app
Please send me that zip...I need to return my phone to htc
Sent from my HTC One using xda app-developers app
need latest WWE RUU exe, is it 1.29
anyone have a link, done search, but not sure which is latest.
cant run 1.28 RUU as gives me bootloader error which i think is due to upgrading to custom firmware.
thanks.
jake460 said:
need latest WWE RUU exe, is it 1.29
anyone have a link, done search, but not sure which is latest.
cant run 1.28 RUU as gives me bootloader error which i think is due to upgrading to custom firmware.
thanks.
Click to expand...
Click to collapse
If you have S-off you will not get the bootloader error.
Was s-off but trying to get to stock, long story but updated firmware few weeks back, now locked bootloader to do Ruu but some how got s-off and can't get s-on due to updated firmware or need updated revone
Sent from my HTC One using xda app-developers app
So is there a RUU WWE htc_001 1.29 that has the latest firmware that matches the custom firmware i updated to from mike86 firmware page.
Thanks
Sent from my HTC One using xda app-developers app
MacHackz said:
I have a zip you can flash which will fully hard brick your phone with no chance of HTC recovery if you need it, will probably result in a new phone and not just a new touchscreen.
Click to expand...
Click to collapse
Man, that's dark.
Is this confirmed? Has anybody flashed this, then sent their phone for warranty repair?
My phone, as far as I could tell was hard bricked (AOSP), but HTC was able to pull up my bootloader to tell me they were gonna need $200 to replace my main board.
It has been confirmed as it was initially flashed accidentally by someone. However, I won't be sharing the link as I feel it isn't morally right to do it
Related
Hey guys so another newb fail here, essentially I rooted my phone and installed a cmd rom and messed my phone up. Went through all the steps in trying to fix it, ruu etc but the ruu was out of date? Or my phone needed a different version. Anyway now my internal storage isn't mountable and I can't do anything. Very worried I ruined my phone! Does anyone have any advice?
A little more info would be helpful. Like what ROM exactly did you flash? Were you on the latest 1.31 RUU? Did you try flashing a 1.29 RUU?
babymatteo said:
A little more info would be helpful. Like what ROM exactly did you flash? Were you on the latest 1.31 RUU? Did you try flashing a 1.29 RUU?
Click to expand...
Click to collapse
It was this rom http://forum.xda-developers.com/showthread.php?t=2356654
once I installed that everything went wrong, but I found a way to reboot because I made a backup and it saved to my phone and then i installed them7spr-RootBox-JB-houstonn rom, that worked for a bit but I had no service at all. So I tried to do the RUU trick but didn't realize the numbers didn't match the 1.31 as it prompted (it was 4 in the morning and I was really worried so I tried everything) so that crashed and my bootlock was locked, I then unlocked it again and when I tried to turn it on it would just load the rootbox rom's loading screen then power off. But in short yes, I was on 1,31 and tried flashing to 1.29
Got a little update, so I downloaded http://forum.xda-developers.com/showthread.php?t=2368907 and went into cmd and typed in fastboot flash recovery boot.img and got it to start loading the rom but it crashes after about 2 minutes. I can't go into recovery mode anymore, I'm assuming the flash wiped it clean? No idea what to do next. Any insight would be amazing!
1. Never flash ROMS that aren't made for your phone. ARHD is made for GSM variants of the HTC One only. I believe ARHD was also available for CDMA in point in time, but not anymore
2. You can't go back to previous RUU's unless you have S-off
Have you tried to RUU to 1.31? Did you re-lock your bootloader first? If not, do that first and you should be fine.
babymatteo said:
1. Never flash ROMS that aren't made for your phone. ARHD is made for GSM variants of the HTC One only. I believe ARHD was also available for CDMA in point in time, but not anymore
2. You can't go back to previous RUU's unless you have S-off
Have you tried to RUU to 1.31? Did you re-lock your bootloader first? If not, do that first and you should be fine.
Click to expand...
Click to collapse
I haven't been able to find a 1.31 RUU, I relocked it but yeah. Just can't find the RUU
twozilla said:
I haven't been able to find a 1.31 RUU, I relocked it but yeah. Just can't find the RUU
Click to expand...
Click to collapse
I can help you when I get home from work
Update: Check PM
Sent from my HTCONE using xda app-developers app
Help too
bigdaddy619 said:
I can help you when I get home from work
Update: Check PM
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I can't seem to find the Sprint HTC ONE 1.31 RUU anywhere so I can use the program to fix my phone since I wiped the internal storage before pushing a rom to the device. OTG doesn't work. I have TWRP installed and I can get into fastboot, but adb isn't working at all. Any help??
srefsn said:
I can't seem to find the Sprint HTC ONE 1.31 RUU anywhere so I can use the program to fix my phone since I wiped the internal storage before pushing a rom to the device. OTG doesn't work. I have TWRP installed and I can get into fastboot, but adb isn't working at all. Any help??
Click to expand...
Click to collapse
Follow the guide posted here
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
srefsn said:
I can't seem to find the Sprint HTC ONE 1.31 RUU anywhere so I can use the program to fix my phone since I wiped the internal storage before pushing a rom to the device. OTG doesn't work. I have TWRP installed and I can get into fastboot, but adb isn't working at all. Any help??
Click to expand...
Click to collapse
Check PM
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
MacSkizzle said:
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
Click to expand...
Click to collapse
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I get s-off? All I can access is my bootloader.
jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded, extracted, and ran the correct soju but I get an error. It says to run rumrunner again and READ... I don't know what I did wrong. I did this with my phone in fastboot usb mode, is that right?
MacSkizzle said:
Can I get s-off? All I can access is my bootloader.
Click to expand...
Click to collapse
I'm pretty sure that's all you need. But I could be wrong.
TriBeard said:
I'm pretty sure that's all you need. But I could be wrong.
Click to expand...
Click to collapse
When I run the rumrunner program, I type 'Yes' twice then I get an error telling me to run rumrunner again and READ. What did I do wrong?
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
I'll try this tonight when I get home from work, thanks for the input.
ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
This didn't do it either. PLEASE SOMEONE HELP ME
I don't know if you can flash OMJ's firmware if your bootloader is set to "Relocked". I could be wrong but I think what you need to do is unlock it again first and install a recovery. Then flash OMJ's stock firmware from recovery. From there you can probably do the S-OFF process and RUU back to stock.
You do need to be able to boot into your ROM for S-OFF to work, as you start the S-OFF process while the phone is booted up and running.
MacSkizzle said:
This didn't do it either. PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
Look HERE
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
cristhefur said:
I have a rooted htc one m8 hk edition with S-On, I would like to install the new update that sprint rolled out so I was thinking about using the RUU from another thread here. My question is, since I have the HK edition can i install the RUU without S-Off? I noticed that SuperCID was required for the non hk version only and was not required for my version. Is this correct? Also will the RUU return me to 100% stock? I couldn't post this in the RUU thread itself due to being new to xda, sorry for the inconvenience. Thanks!
Click to expand...
Click to collapse
You can use the RUU with S-ON as long as it is not an older version than what is already on your phone - I believe you are probably talking about 1.54.654.9 right? Check the about settings on your phone to see if you have upgraded from that (1.54.654.13 or 1.54.654.15 or the 2.16 something).
If the phone version is newer, you will not be able to use the RUU without S-OFF. Since you actually have the HK version, you will not need to change your CID. Successfully running the RUU will flash all the major partions, radios, and more and will bring you completely back to stock. It will also wipe your data/media partition (internal SC card) so make sure you backup anything you need to keep.
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
cristhefur said:
Thank you so much for your response it was exactly what I needed. If I wanted to remove the tampered flag could I do it before flashing the RUU? Or will that get removed along with the root in the process? Thanks again!
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
The RUU will actually remove the TAMPERED banner because that flag is in mmcblk0p6, named "pg2fs", which is one of the images that the RUU overwrites. UNLOCKED, if you have it, will remain because that flag is mmcblk0p2, named "pg1fs" which does not get overwritten by the RUU. It can be removed by hex editing that block with an echo command http://forum.xda-developers.com/showthread.php?t=2708571
If you are already unlocked, rooted, and have version 1.54.654.9, I would highly suggest you run sunshine and get S-OFF before you run the RUU and update the OTAs; who knows if that exploit will be blocked in further updates.
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
cristhefur said:
I see, I'm running 1.54.654.15...can I still s-off with sunshine?
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Not sure since I did it on .9, but I would definitely try it - in fact, if you are on 15, the only way you will be able to run the .9 RUU is if you S-OFF.
Sunshine will not ask you to pay until it has run compatibility tests and verified that it can get S-OFF on your phone - so run it and if you see the message to pay, you are good to go. Having S-OFF just makes things SO much easier.
Just follow the directions on the sunshine site http://theroot.ninja/ and run it entirely from the phone; couldn't be easier. You will need to sideload the APK, easiest if you just run the command "adb install SunShine-latest.apk" after making sure Unknown Sources is checked in your phone settings.
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
cristhefur said:
Wait a sec, I thought you said I could use the RUU as long as it was of an older version than the one I currently had..so I was thinking about the .9 RUU since I am on .15... That actually wouldn't work? Sorry I'm a bit confused.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
It's the other way around - look a few posts up - there's a "not older than your phone's version" in front of that statement.
To be clear, the .9 RUU will not work on a .15 phone if you are S-ON, you must be S-OFF to do that. However, if you had a .15 RUU (which doesn't exist) it would work on a .9 phone.
Sorry about the confusion. That is just one of the benefits of being S-OFF (not to get sidetracked but my favorite benefit is being able to flash from hboot or fastboot rebootRUU with the bootloader locked)
Ah yes, I see that now- my mistake. I guess I'll s-off tomorrow afternoon then. Thank you very much for your help!
Sent from my 831C using XDA Free mobile app
It's encouraging that the Sunshine devs recently made fixes to deal with Sprint 4.4.3 M8 devices - that's version 2.16.654.4 which is higher than yours, so I think you have a good chance of success. Good luck!
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
I'm fairly certain that if you're S-on you can only run a RUU with the same software & firmware version that's installed on the phone. It was that way on the EVO LTE and I'm fairly certain that's how it is now.
Sent from my HTC M8
you may want to try http://firewater-soff.com/ first, if nogo, then sunshine
AarSyl said:
Are you sure that it wouldn't work on a phone that is already updated to a newer software?
I have been on the previous version (final 4.4.2 version), and I have certainly used the RUU to flash back to the .9 version. To my knowledge, the RUU should work regardless of which version that your phone is running. If you're S-On, you just have to be locked & using the stock recovery.
Click to expand...
Click to collapse
nope, you can't flash a older RUU if you're s-on
Oh ok...my apologies.
Is there a reason that my phone boots directly into the bootloader every time that I relock it?
I am unable to boot into anything after using fastboot oem lock, and it only loads the bootloader until I run the RUU (granted, this was before the latest update).
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
neudof said:
So I am S-On with a non-HK M8
I was on stock rooted 4.4.2 and I flashed the stock recovery and took the OTA
Now I am on 4.4.3 and still have SuperSU installed (not rooted)
Everything is working fine, but when I try to boot to recovery i get the red triangle with the !
Any suggestions?
Click to expand...
Click to collapse
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
PillowMetal said:
The red triangle is indicative of the stock recovery, which was updated with everything else when you did the OTA. Being S-ON with SuperSU means you must have been UNLOCKED at one point - if you are still are UNLOCKED, simply flash custom recovery back onto your device. If not UNLOCKED (if you relocked for the OTA, which is not necessary if S-OFF, not sure about S-ON), you will need to HTCDEV unlock again before flashing the custom recovery.
Click to expand...
Click to collapse
Is it possible to flash the recovery from SD card or do I need to use my computer?
neudof said:
Is it possible to flash the recovery from SD card or do I need to use my computer?
Click to expand...
Click to collapse
When you download say TWRP from their webiste, you get an image file (IMG) that is meant to be flashed using fastboot from your computer. But you can rename it to "recovery.img", place that in a zip file along with an android.txt file with specific contents onto your external SD Card, and then you can flash it from the bootloader (if you are S-OFF). The file has to be specifically named as well - e.g., the Sprint HTC One M8 is "0P6BIMG.zip".
If you don't have an external SD Card, you may also be able to flash from the bootloader using a powered USB-OTG cable (like we did on the M7). Again, this is only if you are S-OFF, otherwise you will have to fastboot flash the image from your computer because bootloader flashes with S-ON have to be signed.
One last method that doesn't require S-OFF, is to copy the image file anywhere on internal or external SD cards, then use the "dd" command to copy the image over your recovery block (specific numeric device block depending on phone) using either your computer or a terminal emulator on the phone.
So yeah, you have options.
Update: I achieved S-Off as suggested, locked my boot loader using an adb command from another thread then ran the HK .9 RUU. I went through the 3 updates then took the phone to sprint, had no problems at all. Thanks for your help guys. :thumbup:
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
jwalters1123 said:
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
Click to expand...
Click to collapse
You say the RUU failed...
Any error message?
As much info as you can give would be better.
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
jwalters1123 said:
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
Click to expand...
Click to collapse
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
BD619 said:
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
jwalters1123 said:
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
Click to expand...
Click to collapse
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
BD619 said:
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
Click to expand...
Click to collapse
ok so hboot version says 3.19.0.0000, i am on a usb 2.0 port, i am not sure how to paste my copied text from the cmd prompt into this box so i just pasted it to a .txt file and attached that and it has all the getvar all info. thanks for the help.
Everything is current according to the getvar...go ahead and remove it as it contains the imei #
The latest RUU should work.
Maybe try downloading Sync Manager to update the drivers or try a different PC/usb port.
Low and behold i was in a 3.0 port lmao... smh... so you just saved me beating my head against the wall for god knows how much longer, thanks for the help, the ruu is working fine now:fingers-crossed:
Hi guys I have acquired a Rogers M7 that powers on but then just sits at a blank screen after boot. I can access fastboot and als flashed twrp recovery, I m on OS version 7.17.631.7 lollipop I believe, it is S-ON , HBOOT 1.61, I unlocked the bootloader using the HTCDEV.
I have tried to getting it past the blank screen by using the latest RUU I could find, 4.19.631.9 but that did not work, I think cause the s-on will not allow a downgrade, I also tried using the One_All-In-One_Kit_v3.1 to side load a zip but same problem, fails verification. I have also tried a nandroid back by copying it to the internal memory but still not working.
Can anyone help me fix this phone so it can be usable again? or provide me with an RUU that will work.
Thanks
carlos1984 said:
Hi guys I have acquired a Rogers M7 that powers on but then just sits at a blank screen after boot. I can access fastboot and als flashed twrp recovery, I m on OS version 7.17.631.7 lollipop I believe, it is S-ON , HBOOT 1.61, I unlocked the bootloader using the HTCDEV.
I have tried to getting it past the blank screen by using the latest RUU I could find, 4.19.631.9 but that did not work, I think cause the s-on will not allow a downgrade, I also tried using the One_All-In-One_Kit_v3.1 to side load a zip but same problem, fails verification. I have also tried a nandroid back by copying it to the internal memory but still not working.
Can anyone help me fix this phone so it can be usable again? or provide me with an RUU that will work.
Thanks
Click to expand...
Click to collapse
Right, you can't downgrade when S-ON. Relock your bootloader and flash the 7.17.631.7 RUU
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I would also recommend that you stop using toolkits and learn to use adb and fastboot directly from a command window. These tools are not up-to-date and will most likely cause some issues.
thanks
alray said:
Right, you can't downgrade when S-ON. Relock your bootloader and flash the 7.17.631.7 RUU
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I would also recommend that you stop using toolkits and learn to use adb and fastboot directly from a command window. These tools are not up-to-date and will most likely cause some issues.
Click to expand...
Click to collapse
I am familiar with adb commands but not with fastboot its elt, i do not remember using on my samsung phones or lg so I was having problems so i decided to be lazy. Thank for the reply will let you know how it worked out.
carlos1984 said:
I am familiar with adb commands but not with fastboot its elt, i do not remember using on my samsung phones or lg so I was having problems so i decided to be lazy. Thank for the reply will let you know how it worked out.
Click to expand...
Click to collapse
If you have already used adb then you won't have any difficulty using fastboot, it's basically the same thing and the commands to flash the ruu are posted in the link above. Just don't forget to use the fastboot version from that thread or it won't work.
Sent from my HTC One using XDA Labs