Hey guys, a little help over here!
My M8 At&t variant is unlocked, have a tampered banner but is S-On and I don't know which recovery I'm using. When I go in recovery it gets stuck showing a red triangle. I want to go fully stock and unroot to get lollipop update. Will running RUU solve it?
77tammy7 said:
I don't know which recovery I'm using.
Click to expand...
Click to collapse
Why not? This statement implies that you are either messing with the phone without proper knowledge; or doing so in a manner that is careless, and not keeping track of what you are flashing to the phone. Either way, its worrisome.
77tammy7 said:
When I go in recovery it gets stuck showing a red triangle. I want to go fully stock and unroot to get lollipop update. Will running RUU solve it?
Click to expand...
Click to collapse
Red triangle is stock recovery.
The RUU will certainly restore you to full stock. And you can RUU right up to Lollipop, without having to take an update to do so.
Since you are s-on, you need to relock the bootloader to run the RUU.
Keep in mind that the RUU will wipe user data, so backup anything you want to keep (preferebly backup to an off-phone location) before you RUU.
redpoint73 said:
Why not? This statement implies that you are either messing with the phone without proper knowledge; or doing so in a manner that is careless, and not keeping track of what you are flashing to the phone. Either way, its worrisome.
Red triangle is stock recovery.
The RUU will certainly restore you to full stock. And you can RUU right up to Lollipop, without having to take an update to do so.
Since you are s-on, you need to relock the bootloader to run the RUU.
Keep in mind that the RUU will wipe user data, so backup anything you want to keep (preferebly backup to an off-phone location) before you RUU.
Click to expand...
Click to collapse
Actually I got that phone from a friend, in used form, that's why I didn't know about recovery. Anyways, will I have to unroot and remove the tampered banner to RUU or just relock the bootloader?
Thanks.
77tammy7 said:
will I have to unroot and remove the tampered banner to RUU or just relock the bootloader?
.
Click to expand...
Click to collapse
Just relock the bootloader (fastboot command: fastboot oem lock).
If updating to Lollipop is what you want, the correct RUU is linked at the bottom of the following webpage, along with additional instructions on how to run the RUU (under "Manual system Update instructions"): http://www.htc.com/us/support/htc-one-m8-att/news/
redpoint73 said:
Just relock the bootloader (fastboot command: fastboot oem lock).
Click to expand...
Click to collapse
Thanks alot man. Appreciate it.
77tammy7 said:
Thanks alot man. Appreciate it.
Click to expand...
Click to collapse
There's a button for that.
You're very welcome.
Related
Hi, I Have a friend with an EVO 3d but he wants to take ota from sprint. His phone is running a custom Rom installed and a custom kernel. So, how can he update to latest ota? All help is welcome. Thanks.
luis4ever said:
Hi, I Have a friend with an EVO 3d but he wants to take ota from sprint. His phone is running a custom Rom installed and a custom kernel. So, how can he update to latest ota? All help is welcome. Thanks.
Click to expand...
Click to collapse
I would do it with RUU. My ota had issues not being able to unlock.
iTzLOLtrain said:
I would do it with RUU. My ota had issues not being able to unlock.
Click to expand...
Click to collapse
I forgot to mention He is on hboot 1.50 so he can't use the .zip from bootloader.
Since he's running a custom ROM, the way for him to upgrade to the latest 2.17 without going back to an unrooted base ROM would be to check to see if the ROM's author has updated to the new version, or going with a completely different ROM.
~co~
Edit: If he wants to go back to base, stock, unrooted, he could run the 2.17 RUU. That will flash as long as he relocks his device. If he wants to unlock his bootloader again, he can do so after he flashes the RUU.
closeone said:
Since he's running a custom ROM, the way for him to upgrade to the latest 2.17 without going back to an unrooted base ROM would be to check to see if the ROM's author has updated to the new version, or going with a completely different ROM.
~co~
Click to expand...
Click to collapse
Doesn't matter if he is back to stock. In fact that's What he want. Go to stock Rom on 2.17
Just in case, I did edit my post above with a bit more info.
~co~
closeone said:
Just in case, I did edit my post above with a bit more info.
~co~
Click to expand...
Click to collapse
If I understood only thing he needs to do is go to fastboot and type oem lock to lock the bootloader right? Then run the RUU for 2.17?
He'll run the command "fastboot oem lock." He will likely get a security warning because of the custom ROM on there. Go ahead and run the RUU now. Realize that this will wipe everything off the phone (not off the SDCard).
closeone said:
He'll run the command "fastboot oem lock." He will likely get a security warning because of the custom ROM on there. Go ahead and run the RUU now. Realize that this will wipe everything off the phone (not off the SDCard).
Click to expand...
Click to collapse
Does he need to run the RUU in normal mode, Bootloader, fastboot or when the security warning appears?
luis4ever said:
Does he need to run the RUU in normal mode, Bootloader, fastboot or when the security warning appears?
Click to expand...
Click to collapse
The security warning will show up inside the bootloader. (If I remember correctly) You'll have to run it when the phone is in the bootloader.
Just got to the thread i made.
http://forum.xda-developers.com/showthread.php?t=1578977
iTzLOLtrain said:
Just got to the thread i made.
http://forum.xda-developers.com/showthread.php?t=1578977
Click to expand...
Click to collapse
Thanks, iTzLOLtrain. Didn't check the stickies beforehand.
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Minker17 said:
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Click to expand...
Click to collapse
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
freakasis said:
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
Click to expand...
Click to collapse
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Dark Nightmare said:
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Guess that does make sense, huh?
But everything looks OK then?
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Final Steps
Minker17 said:
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Click to expand...
Click to collapse
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
TheCount01 said:
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
Click to expand...
Click to collapse
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
S-off
FutureAirways said:
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. That makes sense, too. Plus, it'll save me a step. I'm new to Android and got a lot to learn. With the help of xda-developers, I've learned a lot these past three weeks.
From what I've been reading, it's apparent that I need to have S-off before I do any flashing. Like I mentioned, I bought the phone with a custom rom. I'm guessing if it has a custom rom, then it was S-off at one time. If so, I should be able to S-off easily. Since I didn't flash the phone, I'm not sure what program is installed. Your knowledge and experience will be greatly appreciated if you can tell me if I'm able to S-off easily and how. Whenever I go into HBOOT I see the following:
***UNLOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0008
eMMC-boot
FASTBOOT
<vol up> to previous item
<vol Down> to next item
<Power>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
If you are s-off, flash the ruu.exe. Everything will go back to stock (ROM, recovery, etc), but you will remain s-off. I think you have to lock the bootloader first, but you don't need to be s-on.
Imagika FTW... with Tapatalk 2
Raillery said:
My 3G has been terrible since I got the phone, so I finally took it in to the sprint repair shop. They said before they can look at it I need to unroot and take the latest sprint update.
If I go stock and take the official OTA update, will I be able to achieve S-OFF and root again?
How do I go about going completely back to stock?
Thanks!
Click to expand...
Click to collapse
Hello,
I believe I can help you out with this. Are you s-off right now? If so, then all you have to do is download the latest ruu. It's easy. You can find it in the development section under stickies. If your s-on however you will need to run the ruu.exe on your pc which I believe you can find that file under the stickies. Now if your s-off, you can flash the ruu file by renaming it to PG86IMG in all caps and placing it on the root of your sdcard and booting into bootloader and flashing it from there. If you are going to turn s-off back to s-on you must do this immediately after you flash the ruu. Just go to fastboot on your computer with your phone in fastboot and type this command fastboot oem write securityflag 3. I believe that's the right command. Just make sure your hboot is stock and not modified or else you will brick your phone. And of course you can still achieve s-off and reroot after that. Ramjet wrote a very simple and easy guide that will help you step by step with the easiest way to get there. You can find his guide in the general discussion section. If you have any questions please do not hesitate to ask.
Please hit the thanks button if helped you in Anyway. Goodluck.
This ruu? The second one?
Raillery said:
This ruu? The second one?
Click to expand...
Click to collapse
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
ramjet73 said:
Those are firmware .zip's that won't return everything to stock. I'd suggest that you download the 2.89.651.2 ICS RUU.exe from one of the links in this post and run it from Windows. Then you will be totally stock except for S-OFF and they shouldn't care about that. When you get the phone back you can just flash a custom recovery then root the stock ROM or flash a custom rooted ROM without having to worry about getting S-OFF again, unless they set it back to S-ON when it is serviced.
ramjet73
Click to expand...
Click to collapse
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
EDIT: Nvm it worked, just had to manually rebooted to bootloader.
Raillery said:
Do you have the link to the ruu that can be run through the phone? I keep getting error 155 unknown error.
Click to expand...
Click to collapse
That error means you didn't lock the bootloader first. Use the fastboot command: fastboot oem lock. Then run the ruu.
Imagika FTW... with Tapatalk 2
Hey guys. Yes I have searched, but have only found instructions so far for going back to stock gingerbread.
I need to send my amaze in to get fixed under warranty, and I'm assuming they won't like it if I send them the phone with an unlocked bootloader, rooted, and CM10 installed, and that's what I need help with. How can I reinstall stock ICS, unroot, and lock the bootloader of the amaze? And will it show as "relocked" or "locked"? Of course I plan on putting the root and unlocked bootloader and CM10 once I get it back, so I'm looking for a reversible way to do this. Thanks in advance!
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Double0EK said:
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Click to expand...
Click to collapse
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
No. That's the only way for it to say "locked" if you relock it it will say "relocked"
So if you really want it to say "locked" you'll need to S-Off first. Then flash the RUU.
Once you get it back you can do as you feel.
bruner1981 said:
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
Click to expand...
Click to collapse
What makes you think you will be stuck with anything? Everything u need to do is reversible and then re-doable.
Im just not really sure which part u think would make it stuck. Let us know and im sure we can explain the cofusion
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Boot into fastboot, type "fastboot OEM lock" in the command prompt. Put the appropriate RUU on your external SD card and rename it PH85ING.zip and boot into bootloader.
Edit: its PH85IMG.zip. sorry about my fatty fingers. Also, make sure to check the md5 sum on the RUU. I always had trouble with the download.
Sent from my HTC Ruby using xda app-developers app
fubag said:
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Click to expand...
Click to collapse
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
aj_2423 said:
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
Click to expand...
Click to collapse
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
fubag said:
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
Click to expand...
Click to collapse
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
aj_2423 said:
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
Click to expand...
Click to collapse
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
fubag said:
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
Click to expand...
Click to collapse
noo it has nothing to do with what carrier you're using at the moment...
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
geeDoh said:
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
Click to expand...
Click to collapse
The good news is, if you really are stuck in fastboot, you can still use adb/fastboot commands to get your phone working again. There is an important distinction between fastboot and hboot, though: fastboot is basically the bootloader's "debug" mode, while hboot is the regular bootloader mode. You won't be able to do much if your bootloader says "hboot" above the available options, but if it says "fastboot" or "fastboot usb" you're fine.
You should try to get s-off again (assuming you haven't relocked your bootloader) either via revone or facepalm, then flash a stock rom and proceed from there.
Clarification: if you have relocked your bootloader, unlock, then get s-off.
Used adb to S-On? Meaning what exactly? Did you lock beforehand?
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
geeDoh said:
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
Click to expand...
Click to collapse
Does the unit show up in device manager? You may need to install a driver.
Phaded said:
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
Click to expand...
Click to collapse
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
geeDoh said:
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
Click to expand...
Click to collapse
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Phaded said:
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Click to expand...
Click to collapse
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
geeDoh said:
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
Click to expand...
Click to collapse
That's because you have unsigned boot.img and/or recovery and relocked the device.
You need to RUU or unlock again to boot to anything.
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
geeDoh said:
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
Click to expand...
Click to collapse
Run Moonshine.
If that fails, RUU to stock.
You didn't happen to make an unlock_code.bin with htc did you?
No, i didn't. Not even sure what that is...haha...
I'm going to run RUU, and hope that works! Thanks for everyones input...
still no luck! =T
So, I've tried running RUU (this is the RUU file I'm using: 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), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
geeDoh said:
So, I've tried running RUU (this is the RUU file I'm using: 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), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
Click to expand...
Click to collapse
Just run the RUU. There is only one RUU. You are on 2.06, that's why it tells you that. Let the whole thing run.
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
beaups said:
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
Click to expand...
Click to collapse
Ah forgot he went back to S-On.
Phaded said:
Ah forgot he went back to S-On.
Click to expand...
Click to collapse
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
okyere said:
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
Click to expand...
Click to collapse
Still have the token? Or the email that it got sent in?