Hey guys, havent been on the forums in awhile, my buddy has an HTC One Max that he wanted to root/rom, we've had some trouble, was up to the new ROM however it wasn't getting service from sprint, pretty much wanted to go back to stock and just not worry about any of this, i have read through some of the RUU threads and such but im having a good amount of trouble. Could i get some help? i am able to send commands to the phone but cant get into anything else, keeps going to fastboot when phone is restart. believe it is locked in fastboot. Let me know any info you need.
I think you have re-locked your phone as of now. If you have re-locked it you need to run the RUU or flash the ROM.zip via hboot. you can find the RUU in couple of threads now..
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
asnpdirtezw said:
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
Click to expand...
Click to collapse
As pradeepvizz said you need to make sure your bootloader is Locked/Re-Locked to run the RUU it would also be good measure to have a stock Recovery installed.
DeadPhoenix said:
As pradeepvizz said you need to make sure your bootloader is Locked/Re-Locked to run the RUU it would also be good measure to have a stock Recovery installed.
Click to expand...
Click to collapse
I was sure to re-lock the unit, dont think i had flashed over a stock recovery now that i think about it, ill try that and get back to you.
asnpdirtezw said:
while attempting to flash the RUU i continue to get the error FAILED (remote: 12 signature verify fail) Everything else seems to go fine until i get to that point.
Click to expand...
Click to collapse
Do you mean you tried to flash it via command prompt on the PC?
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
asnpdirtezw said:
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
Click to expand...
Click to collapse
Weird because because I ruu the other day. But I'm also unlocked and soff
Sent from my HTC6600LVW using XDA Premium 4 mobile app
asnpdirtezw said:
That is correct, i managed to unlock it again so i could attempt to flash the stock recovery and see if i could flash the RUU that way but it keeps giving me an error.
Click to expand...
Click to collapse
well since you are unlocked again, i would suggest to go ahead and install an Custom ROM. I know you had problems with Sprint when you did if the first time, but do try again with the following checks
1. Make sure you get the proper ROM for your phone - i assume your phone is from Sprint and so download the Sprint variant and not the international or anything else.
2. Use TWRP recovery for flashing the ROM. we have had users reporting similar issues when CWM was used.
Related
Running Cleanrom right now and would like to install the updates for the radios from HTC..could i just flash stock RUU or do i also have to relock?
liquidraven said:
Running Cleanrom right now and would like to install the updates for the radios from HTC..could i just flash stock RUU or do i also have to relock?
Click to expand...
Click to collapse
As far as I know yes
Sent from my ADR6425LVW using Tapatalk
Yes you do have to relock.
I did not relock my phone and it updated without a problem. Just went back to stock rom and stock recovery then checked system updates and was suprised when it worked since everyone was saying that you had to relock.
Sent from my ADR6425LVW using XDA App
Can you get the radios from a ROM that has them baked in, or is that not how it works?
snowride20 said:
I did not relock my phone and it updated without a problem. Just went back to stock rom and stock recovery then checked system updates and was suprised when it worked since everyone was saying that you had to relock. And would be more appropriate if posted in general.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Same for me. No relocking, just reverted to stock image & recovery.
A2Aegis said:
Can you get the radios from a ROM that has them baked in, or is that not how it works?
Click to expand...
Click to collapse
I believe we would need S-OFF for that little trick.
kewl thanks, glad i can do this without re locking as i got rid of the folder with all the files;(
No worries you can find them in the dev section if you need them again.
Sent from my ADR6425LVW using xda premium
Caladus said:
I believe we would need S-OFF for that little trick.
Click to expand...
Click to collapse
That's unfortunate. Hopefully someone can get S-OFF one of the days.
liquidraven said:
kewl thanks, glad i can do this without re locking as i got rid of the folder with all the files;(
Click to expand...
Click to collapse
I've attached what you need, courtesy of MrSmith317. If you ever do need to relock you'd just need to get another unlock token from HTCdev to unlock again.
But you will most likely end up needing this for some sort of flashing at some point.
I think you only have to relock to run the ruu. You shouldn't have to with the updates since they are flashed in the stock recovery. The ruu being flashed through hboot requires relock.
Sent from my ADR6425LVW using XDA App
feralicious said:
I've attached what you need, courtesy of MrSmith317. If you ever do need to relock you'd just need to get another unlock token from HTCdev to unlock again.
But you will most likely end up needing this for some sort of flashing at some point.
Click to expand...
Click to collapse
If you still have your unlock token from HTC you can reuse it.
Sent from my ADR6425LVW using xda premium
feralicious said:
I've attached what you need, courtesy of MrSmith317. If you ever do need to relock you'd just need to get another unlock token from HTCdev to unlock again.
But you will most likely end up needing this for some sort of flashing at some point.
Click to expand...
Click to collapse
thanks for the tools..i have the recovery image on my desktop along with the tools..a lil confused on how to start the process as cmd promp isnt working for me?
getting this error
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lynkdev>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
actually im guessing i was supposed to flash stock recovery before this right?
so i accidently locked my phone..now stuck at hboot..went to htcdev,com and i select my phone and click submit to start the unlock process and nothing happens?? help pls.
nvm got my device unlocked again and back at step 1 lol..
liquidraven said:
so i accidently locked my phone..now stuck at hboot..went to htcdev,com and i select my phone and click submit to start the unlock process and nothing happens?? help pls.
nvm got my device unlocked again and back at step 1 lol..
Click to expand...
Click to collapse
So you have an unlocked phone and you want to get the OTA, correct? What ROM and kernel are you running?
That error you got, was that trying to run the RUU? Which one? 1.x or 2.x?
running cleanrom ICSE 2.3
kernal 3.0.13-gaf15497-dirty
i flashed stock recovery, relocked device and was stuck at hboot..couldnt get past it rebooting or anything..unlocked device and tried running the RUU exe..started up but error out saying it couldnt complete and my screen was left on HTC till i pulled battery...
liquidraven said:
running cleanrom ICSE 2.3
kernal 3.0.13-gaf15497-dirty
i flashed stock recovery, relocked device and was stuck at hboot..couldnt get past it rebooting or anything..unlocked device and tried running the RUU exe..started up but error out saying it couldnt complete and my screen was left on HTC till i pulled battery...
Click to expand...
Click to collapse
What version RUU did you use? 1.x or 2.x? Did you try running it while the phone was locked? It needs to be locked when you run RUU. But you also can't go back to an older mainver and some ICS ROMs are on 3.x
Also can you check what mainver your phone is on? In fastboot type:
fastboot getvar all
running 2.0.1 and wrong RUU i guess since its 1x
Yeah, you need to run 2.x RUU. Get it from link in this post:
http://forum.xda-developers.com/showpost.php?p=22045045&postcount=58
That should fix you up. Then after you run that and get the OTA, unlock, flash Amon Ra (there's a new version posted to that thread today), go to the developer menu in Amon Ra and install su and you will be stock OTA rooted.
Okay I have made a thread about this before, but no one had an answer for me, so I will try again, but I will be more descriptive of my issue.
So the other day, my Evo 3D, which is flashed to MetroPCS, lost its carrier settings when I was flashing a ROM. So I had to go home and use QPST to edit some files in the nvm/num folder (Using EFS). While I was editing, the program crashed, and I was forced to unplug my Evo.
Now, after it rebooted, it would go past the HTC Screen, and flash the boot animation for a split second, then shut off and restart. It would loop like this no matter how long I left it.
So I went into 4-EXT recovery, and formatted system, boot, data etc, and then flashed a ROM. Rebooted and got the same thing. So in a last ditch effort, I downloaded the latest ICS RUU for this phone, and tried all three methods to install. I ran the .exe, the program ran as expected, and the phone showed the progress bar on a black HTC Screen as updating, it rebooted when done, and then just continued to bootloop. I also pulling the rom.zip and renaming it to PG86IMG.zip and flashing it from fastboot. It worked and once it rebooted, did the same thing. I also ran it from fastboot usb, and got the same result.
However, I extracted the rom.zip and tried to use fastboot to flash individual .img files, and on EVERY one, I got "FAILED - Error: (remote: not allowed).
I had previously used the wiretrick to get S-OFF on my Hboot 1.58.
It says "Unlocked" at the top of the bootloader.
I really need to get my phone working, can someone PLEASE point me in the correct direction or at least help me out? Is my phone ruined? Is there a way I can clear the NV memory or something to truly reset the phone?
Once again, I will repeat, RUUs will not work!, I am S-OFF on HBOOT 1.58, my bootloader says "unlocked." No matter what I do it will bootloop. I can flash a recovery, but if I flash a rom it does the same stuff.
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
So now I screwed up, I got it to be able to erase/write in fastboot, I used fastboot erase instead of fastboot format and now my partitions are gone, how do I get those back?
AtmosFEAR4701 said:
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
Click to expand...
Click to collapse
Sounds like a similar thing that happened to me when trying to flash a JB rom with a kernal that was not compatable....no matter what I did I could not get it out of the boot loop...I am Hboot 1.58 HTC unlocked and wire trick S-off...I finally flashed an old backup I had with a stock kernal and it fixed it all...dont know if this helps you at all but try wiping everything possible and flashing a stock kernal or an old backup you may have...
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
His s-off so doesn't matter if its locked or not.
iTzLOLtrain said:
His s-off so doesn't matter if its locked or not.
Click to expand...
Click to collapse
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
coal686 said:
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
Click to expand...
Click to collapse
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
AtmosFEAR4701 said:
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
Click to expand...
Click to collapse
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
ramjet73 said:
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
Click to expand...
Click to collapse
My first post says that I have run the RUU countless times and it still bootloops.
Nevermind... I sold it.
AtmosFEAR4701 said:
Nevermind... I sold it.
Click to expand...
Click to collapse
That's one way to solve the problem.
Sorry we couldn't figure it out.
coal686 said:
That's one way to solve the problem.
Sorry we couldn't figure it out.
Click to expand...
Click to collapse
It's okay. I am not buying another Evo 3D though. I am a MetroPCS customer so I buy flashed phones a lot, and I have a low budget so I'll either grab a flash Galaxy S2, or possibly grab the MetroPCS Galaxy S3 when I get some money.
So just got the phone yesterday and I wanted to S-off immediately. Me being the idiot I am I fully rooted through fireballas method rather than temp-rooting and that messes up dirtyracun. So I need to flash the stock RUU again. I re-locked my phone and tried flashing the RUU and each time I get "FAILED (remote: 99 unknown fail)". Maybe I'm missing something here. How do I flash back to stock?
Are you following the instructions on the unlimited.io website? Because all you need to do is run the fastboot command and it should run just fine.
Sent from my ADR6410LVW using xda app-developers app
Ikikaea said:
So just got the phone yesterday and I wanted to S-off immediately. Me being the idiot I am I fully rooted through fireballas method rather than temp-rooting and that messes up dirtyracun. So I need to flash the stock RUU again. I re-locked my phone and tried flashing the RUU and each time I get "FAILED (remote: 99 unknown fail)". Maybe I'm missing something here. How do I flash back to stock?
Click to expand...
Click to collapse
after you get that error retype the command and it will go though. all part of the process
fastboot flash zip RUU.zip.
Aldo101t said:
after you get that error retype the command and it will go though. all part of the process
fastboot flash zip RUU.zip.
Click to expand...
Click to collapse
No matter how many times I try it won't flash. I figure it's the TWRP recovery or the root that's causing the problem. I must be missing something since I should be able to flash back to stock.
Ikikaea said:
No matter how many times I try it won't flash. I figure it's the TWRP recovery or the root that's causing the problem. I must be missing something since I should be able to flash back to stock.
Click to expand...
Click to collapse
It is most likely the custom recovery that is the problem. Flash the stock recovery (found HERE), then try the RUU again.
Good news! A factory reset and redownloading the RUU.zip fixed the problem. I have my theories on what was messed up, but I'm just glad it worked out in the end. Thanks to all the people who tried to help.
Help! My DNA isn't working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldn't mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Edit: Phone is now fixed, I went to IRC and a guy named Beaups took remote control and fixed it. Im not sure if thats his XDA username or not but if you guys see him make sure to give him a thanks Night everyone
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Its ok its very fixable, at this point. Just be very careful and very patient.
The worst thing you can do with something like this is get in a hurry or try to fix it while you're still very stressed out.
I'm passing on this advice because I almost screwed up yesterday because I made a boo boo and was in a huge hurry.
I'm going to wait for someone who knows more about this particular issue to chime in, but you have my word, I will help you resolve it after I do some more research while I wait for someone with more information or experience to post some info.
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
In the original unlock downloader thread, there is a link to an irc chatroom, I would suggest you go there as well as look for help here, and be patient waiting for some one to respond ...
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Did you use this?
http://forum.xda-developers.com/showthread.php?t=2017525
I am unfamiliar with sideload but seems like with the correct files and the right person with sideload experience, you should be ok, Someone will step up here, may take a bit.
Click to expand...
Click to collapse
Thats pretty much what I did but I keep getting that error:178 image file problem when its trying to finish (I am using the RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed.exe RUU) Also my phone is recognized as 2.04 when I haven't flashed anything
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Halcyon7 said:
Help! My DNA isnt working. I just used the unlock bootloader (Still s-on) and I had my recovery flashed so as usual I wiped all data and had a rom ready to sideload, but when I went to sideload everything said "Couldnt mount" and I couldnt do anything. So I got the RUU and I started to flash it and all of a sudden I keep getting error:178 image file. I saw someone else had this problem and they had a rom flashed and they got back in after unlocking it again but I dont have a rom installed so I have nothing. (Yes I relocked the bootloader when trying to flash the RUU and I did run it as an Admin.) Someone please help me
Click to expand...
Click to collapse
Re-Unlock your bootloader with your Unlock token (Unlock_code.bin) then do a fastboot flash recovery recovery.img and use the CWM recovery that is 6.0.2.8 (i believe is the most recent version) and you should be able to sideload your rom ... or if sideloading doesnt work just do an adb push rom.zip /sdcard/rom.zip and that will put the rom that you want to use on the root of the sdcard and then you can flash that there...
This should hopefully get you working again...
beasleyj62 said:
I had a similar situation recently. I am unlocked and s-off and i accepted the 2.04 update. I needed to go back to the original firmware but the ruu wouldnt flash and gave me an error 158 image error. The only way i was able to run the ruu was to revert my hboot and radio from http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19. Im sure there is another way, but this helped me.....good luck.
Click to expand...
Click to collapse
I keep getting this when I flash the hboot
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.274s
and when I flash the Radio I get
C:\Users\owner\AppData\Local\Android\android-sdk\platform-tools>fastboot flash z
ip PL83IMG.zip
error: cannot load 'PL83IMG.zip': Unknown error
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
beasleyj62 said:
you re-locked your bootloader.....
try what .torrented suggested or re-unlock and try to re-flash the zips.
Click to expand...
Click to collapse
I can unlock it at anytime....
see if you can flash after you unlock again
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
All I needed to run the RUU was the ENG Hboot. Flash it then you should be able to install the RUU provided you have the correct drivers installed.
Sent from my HTC6435LVW using xda app-developers app
He is still s-on.
Sent from my HTC Droid DNA
Andro X said:
Did you flash the stock recovery back to your phone before you tried the ruu?
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
How would I go about doing that?
beasleyj62 said:
see if you can flash after you unlock again
Click to expand...
Click to collapse
I didnt work. This is my 2nd DNA so I have done this before and it worked successfully(The first one had a screen problem)
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Halcyon7 said:
How would I go about doing that?
Click to expand...
Click to collapse
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
beasleyj62 said:
I'm away from my pc right now but if you look around the forum for the link to stock recovery, it might help as suggested above
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I only found 1 link on my computer doctors forum but that link wasn't it
.torrented said:
The RUU flashes a stock recovery... all that is required for running the RUU is a LOCKED bootloader...
Did you by chance take the OTA op? because if you did the RUU wont work...
Click to expand...
Click to collapse
No I haven't. I used the s-off facepalm method and I did everything as it said and now when I went into recovery nothing will mount and my device when trying to use the RUU says its a 2.04. So I didnt take the ota but thats what it is recognized as
I had already had my phone's bootloader unlocked and rooted and had a GPe ROM installed and worked perfectly. THEN I saw that you could literally make it a Google Play edition phone complete with OTA and worked on trying to achieve that. Getting my phone S-Off wasn't working because I believe of my HBOOT version (1.55) so I was told to download this stock ROM that would downgrade me to reach a version that I could then run revone to achieve S-OFF.
POST: http://forum.xda-developers.com/showpost.php?p=45487258&postcount=55
I ran a backup through TWRP first and then flahsed this ROM, which has kept my HTC One at the HTC One splash screen. I connected it to my computer/ADB and got it into the bootloader to go into custome recovery BUT the recovery takes me to a black screen with a phone and red triangle, so it's like my recovery isn't there anymore. Fine.
I download the latest TWRP for my phone(triple checked) and ran the fastboot flash recovery command through ADB but it says
"(bootloader) signature checking...FAILED (remote: signature verify fail)"
is there some sort of way to disable the signature check using ADB or am I actually going about this the wrong way?
I'll admit, I don't do this stuff oftem, so ask as many questions as needed as I probably left out details you may need
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
noobsquared said:
I may be wrong but you may have to re-lock the bootloader and run the ruu back to stock.
nandroid backup restore won't change the hboot so I don't think you'll have any luck there.
I'm running ARHD 40 just till we can find a way to run s-off on our AT&T devices.
Click to expand...
Click to collapse
Not to sound n00b-ish, but what would be the best way of doing this?
EDIT: Actually it is relocked already! Duh! On the bootloader screen it says "TAMPERED" and then "RELOCKED" below that
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I actually had that downloaded but I was just concerned if that was the right move since it wipes the phone.
noobsquared said:
That's alright, we were all noobs at some point in time.
Sounds like you re-locked the bootloader without stock recovery.
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2158151
Download the cingular:
RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe 1134.6MB 2013-10-07 16:47:53
Run the RUU from a windows based computer that has HTC drivers and it should restore it back to stock.
Click to expand...
Click to collapse
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
h_smith said:
I hate to say this actually, but I can't find that .exe in the link. I don't know exactly what I'm looking for in it.
Click to expand...
Click to collapse
Here you go:
http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
noobsquared said:
You can always unlock the bootloader again, install twrp and try to boot and see if that works.
Install the nandroid backup matching your system and you can then get to your data.
Click to expand...
Click to collapse
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
h_smith said:
But how would I do that if I can't even boot up the phone past the splash screen? I did all of the unlocking and TRWP installing via the phone
Downloading and installing the file right now. It's going slow as hell but I'll run when I get the chance
THANK YOU FOR STICKING WITH ME!
Click to expand...
Click to collapse
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
noobsquared said:
Sure thing man. It's stuck at that screen because when your phone is unlocked, it allows custom recovery but when it's locked, it won't boot unless it finds the stock recovery. I am not 100% sure but I've had that issue as well. I had to run the RUU to get back to stock since you can't lock the bootloader with custom recovery and expect it to boot. It may vary from device to device but I've always had to RUU back to stock or fastboot flash stock recovery to get past that screen before you lock the bootloader. You can try again, there is stock recovery posted by someone in forums. Download that, try to go in fastboot mode and try fastboot flash recovery recovery_name.img. I think once you've locked the bootloader it may not work but worth a shot.
Click to expand...
Click to collapse
Thank you. I'm downloading the .exe and will post the results. But it looks like that might take a few hours :/
hey is there another link? that one is so slow and keeps timing out :/
You can either use download manager or chrome browser is pretty good at managing that.
Try this: http://d-h.st/VWf
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
I just did a google search for the term RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_R and gave you the second result I got. Just search for the name of the file and you will find plenty of links.
Hope that helps.
This sounds like the exact same problem I had. The RUU and directions solved that one for me too...
Link to RUU: http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
Other thread: http://forum.xda-developers.com/showthread.php?t=2492266
THANK YOU NOOB!!
I managed to get it fixed. Turns out HTC hosted that exact file so I downloaded it and it fixed my phone. Good times..