My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
ronii1123 said:
My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
Click to expand...
Click to collapse
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
dc959 said:
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
ronii1123 said:
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
Click to expand...
Click to collapse
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
dc959 said:
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
Click to expand...
Click to collapse
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
ronii1123 said:
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
Click to expand...
Click to collapse
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
dc959 said:
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
Click to expand...
Click to collapse
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
Click to expand...
Click to collapse
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
Click to expand...
Click to collapse
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
dc959 said:
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
Click to expand...
Click to collapse
Alright I'll give that a shot, thanks! I'll let you know of my results.
Related
So I'm trying to flash a new RUU for GPE HTC One Jelly Bean 4.3. The RUU is suppose to work for unlocked devices; the person who posted the download links had two, with one for unlocked devices and the other for locked devices. I think I messed up somewhere because I had a custom kernel installed via .zip, then booted back to the stock GPE kernel with "fastboot flash boot boot.img"; the system booted up fine but the 3 dot menu was missing so I went back to the customer kernel. The system wouldn't get past the Google screen and now I'm trying to flash the RUU but it won't work. If I do it on my computer via commands, I get "<bootloader> zip info parsing," then "FAILED <remote: 99 unknown fail>". So now I'm in TWRP recovery with the RUU on my SD card; tried flashing it on my phone and it says "Updating partition details...", "E: unable to mount ' /data'", "E: unable to mount internal storage", E: unable to mount ' /data," then lastly "Error flashing zip." I wiped the cache, data, and system; it won't wipe the Dalvik cache and gives me the same error when I do it. Can someone help me?
Edit: When I also try to wipe via "fastboot -w" it comes up with an error saying "FAILED <remote: not allowed>.
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
InflatedTitan said:
You need S-off to ruu to another firmware that's not made for your particular model/carrier.
Once you s-off enter fastboot oem rebootRUU
fastboot flash zip firmware.zip
(Firmware.zip being the actually name of the ruu zip)
It will begin to flash, then fail and say to flush image immediately. Simply press the "up" arrow on keyboard to repeat the exact same command. It will work the second time.
For some reason fastbooting a ruu in that mode always fails the first time, so you have to do it twice without exiting.
Good luck and enjoy
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
May be the alcohol but I'm having trouble keeping up lol. You're having questions with the hboot trying to s-off? If you can't s-off, nor ruu BC the firmware doesn't match with the most recent ruu then you may be stuck or hopefully someone with more advanced knowledge can help you a little better
Sent from my HTC One using Tapatalk 2
yorkies88888 said:
I think the GPE RUU supports MID: PN0713000 and CID: T-MOB010. http://forum.xda-developers.com/showthread.php?t=2358781
Edit: Oh, never mind; it says S-Off needed...
Any advice on what to do now since my HBoot is 1.54? The HBoot for the latest T-Mobile Sense 5 RUU is 1.44... I'm stuck now...
Click to expand...
Click to collapse
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
CoryTallman said:
For some reason Google firmware will flash on certain s-on phones when it shouldn't. First we need to know if this happened.
When booted into the boot loader, is the screen black or white?
Now if there's an RUU available for your cid and mid (an official ruu.exe not an unsigned zip) that is greater than the firmware version currently on the phone, flashing that will fix everything.
If not, head over to original android development and grab a GPE ROM ( you could also use sense or AOSP, but I'm assuming you want GPe) and attempt to flash the ROM in recovery just like you normally would.
AT&T HTC M7ul
Baad Newz's InsertCoin 3.4-2
Flar2's Bulletproof 6.2
Click to expand...
Click to collapse
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
yorkies88888 said:
So basically I accidentally put security back on BEFORE flashing back to stock so now I'm stuck here. The bootloader screen is black and since I upgraded to HBoot 1.54 via OTA update for stock Jelly Bean when I was S-Off, there is no compatible HBoot for me since the one for T-Mobile is 1.44 currently. My biggest worries right now is that I screwed something up with the partitions or if there's a bigger issue here because it's saying it can't mount the data and SD card, and I can't even wipe the phone via commands. If it's just the CID, MID, and HBoot not matching, then I'm not worried since I can still flash a custom ROM right?
Click to expand...
Click to collapse
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
wwjdd44 said:
here is the latest signed RUU for TMOB.
http://forum.xda-developers.com/showthread.php?t=2427325
Click to expand...
Click to collapse
It's of no use to him; he can't run it because he's on 1.54 and s-on.
iElvis said:
This is why going back to s-on is almost always a bad idea. You can't flash any unsigned RUUs or firmware packages now, so you can't return your phone to stock.
It sounds like you may have corrupted your sdcard during all this. Try reformatting it from your PC. This will wipe all your data, but if it's corrupted, it's gone anyway. Then you can push a new rom and kernel and flash.
Click to expand...
Click to collapse
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
yorkies88888 said:
So even if T-Mobile releases an RUU with HBoot 1.54, I can't go back to stock? And how do I reformat it on my PC? CMD? And can you recommend me a ROM that's closest to stock Sense 5? And do I flash the ROM first or the kernel? Sorry about all the questions; I'm just freaking out right now.
Click to expand...
Click to collapse
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
nkk71 said:
You still have an unlocked bootloader right?
Then I would just flash a custom recovery and "format sdcard" from there.
Then "adb push Rom.zip /sdcard/" (or sideload) and flash the Rom.
I personally use ARHD 13.x which is very close to stock Sense 5.
ROMs already include a kernel, so no need to flash separately.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
yorkies88888 said:
Yes, I have an unlocked bootloader but TWRP doesn't seem to have a "format SD card" option.
Click to expand...
Click to collapse
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
nkk71 said:
I haven't used TWRP, but I'm sure it's there somewhere. Usually under advanced.
Might be called something else? What format options does TWRP have? Maybe /data/media
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
yorkies88888 said:
Oh, I found it! Thanks! Woot! Do you recommend ARHD 13.x or 21.x?
Click to expand...
Click to collapse
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
nkk71 said:
Personal preference. Why don't you try both. 13.x is based on official 4.2.2 and 21.x is based on leaked 4.3 (but still very good)
Just note on 21.0 you have to enter APN settings manually to get mobile data & mms, and there's a bug which won't let you access SIM card contacts.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
yorkies88888 said:
Edit: And do you know if it's still possible to use the T-Mobile RUU when they come out with Jelly Bean 4.3 update with HBoot 1.54? Or am I just stuck with custom ROMS now?
Click to expand...
Click to collapse
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
yorkies88888 said:
Well is 13.x compatible with HBoot 1.54? And I have Google's bootloader and when I boot up the phone it has a Google logo on it; will it be able to install and get rid of the Google logo and bootloader? Thanks for the help by the way; I finally got past the corrupt files.
Click to expand...
Click to collapse
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
iElvis said:
You can't use unsigned RUUs. If T-Mo releases a RUU with 1.54 or later hboot, then yes, you should be able to use it (unless you changed your MID or CID).
Yes it is, but you're stuck with the Google bootloader for now, until there is an s-off exploit for 1.54 or T-Mo releases that RUU.
Click to expand...
Click to collapse
nkk71 said:
It is compatible with 1.54, but I've never tried GPe, so I can't answer that. Don't know if it is firmware, ROM related, or if GPe hboot is different.
Can someone pitch in?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
yorkies88888 said:
Well it's a good thing I changed my CID back to T-MOB010 before I put security back on then... I had SuperCID so not like it would've mattered... But thanks for the good news! And the GPE ARHD is compatible because it's Jelly Bean 4.3, but would flashing the ARHD 13.x ROM change the bootloader and start-up screen to HTC instead of Google?
Click to expand...
Click to collapse
No. No rom will change your bootloader or splash screen. You need s-off to do that.
So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.
details
Bloodrave said:
So, first of all i want to say that i wouldn`t have written here if i hadn`t tried every possible way. I want to know where i did wrong, because this is the case and i wand to ask for your help.
The situation : I flashed the google edition to my htc one, it was fine, and i didn`t quite like it so i wanted to go back.
Now the show starts. I flashed Hboot 1.44, got the old bootloader back, and then when i tried to flash the old ruu zip it says : couldnt allocate 1034027008bytes. Also i have tried the exe file and it stops right at the start and says connection interrupted or some sort like this and it doesn`t continue.
I have S-off, unlocked bootloader. I had stock 4.2.2 with htc__001 cid, and twrp as recovery and of course it was rooted. I flashed the Google Edition after i put the stock recovery.
Thank you in advance for all your help.
Click to expand...
Click to collapse
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC
cc999 said:
What phone is it? Developer Edition?
First thing is to change your CID to a Super CID 11111111
Then you need the proper RUU file for the phone. If its an ATT version
you can flash the 4.3 Developer Edition RUU on the HTC site.
CC
Click to expand...
Click to collapse
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.
hboot
Bloodrave said:
@cc999: first of all thank you for your answer. I have the CID changed to supercid 11111111 and i want to flash the europe version. I have tried with both variants from the thread with the RUUs. The Zips and Exe`s dont work.
Click to expand...
Click to collapse
Then your Hboot 1.44 may not be the correct one. PM me with your email and I will give
you the correct one.
CC
I have tried once again with the 1.44 Hboot and the zip from htc official website , the developer edition one.
Still no luck.
With the help of cc999 i managed to revert back to 4.3 Developer Edition.
Apparently there was a mess in my adb and usb drivers.
So i managed to install the 4.3 Developer Edition on another laptop and it worked just fine.
Thank you again cc999 for the support.
You should use the stock recovery to flash the ruu.exe. Makes life so much easier!
Sent from my HTC One using Tapatalk 4
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
kikinhorap said:
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
Click to expand...
Click to collapse
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Answer
attanasi0 said:
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Click to expand...
Click to collapse
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
kikinhorap said:
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
Click to expand...
Click to collapse
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
A
attanasi0 said:
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
Click to expand...
Click to collapse
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
kikinhorap said:
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
Click to expand...
Click to collapse
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
nkk71 said:
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
Click to expand...
Click to collapse
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
kikinhorap said:
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
Click to expand...
Click to collapse
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
nkk71 said:
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
Click to expand...
Click to collapse
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
kikinhorap said:
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
Click to expand...
Click to collapse
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
nkk71 said:
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
Click to expand...
Click to collapse
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
kikinhorap said:
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
Click to expand...
Click to collapse
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
nkk71 said:
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
Click to expand...
Click to collapse
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
kikinhorap said:
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
Click to expand...
Click to collapse
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
nkk71 said:
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
Click to expand...
Click to collapse
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
kikinhorap said:
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Click to expand...
Click to collapse
Excellent :good:
kikinhorap said:
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
Click to expand...
Click to collapse
That's normal, dont worry about it.
kikinhorap said:
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
Click to expand...
Click to collapse
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
nkk71 said:
Excellent :good:
That's normal, dont worry about it.
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
Click to expand...
Click to collapse
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
kikinhorap said:
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
Click to expand...
Click to collapse
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
nkk71 said:
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
Click to expand...
Click to collapse
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
kikinhorap said:
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
Click to expand...
Click to collapse
You should have LOCKED it before running the RUU, because that's what made you loose root.
So before proceeding, can you give me an update of your status:
bootloader: locked/relocked/unlocked?
tampered?
ROM?
"fastboot getvar all" (remove IMEI and s/n)
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
might be your hardware, i am soff with 651.8
Sent from my 831C using XDA Free mobile app
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
If Firewater says it won't work on your device, then you can't get S-OFF for the time being. There's nothing you can do about that.
Don't flash anything above 1.54.651.8 without being S-Off
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
I'm running into the same problem and I need it badly.
If you do flash .13 without S-off you basically will have no way to flash the firmware and could be without audio from the stock music app.
Wow it's been a long night. This is a learning process for me. I've never come to a new phone so quickly so I'm getting used to the fact that development takes time and I need to be patient. I pretty much soft bricked my phone last night. Ended up deleting my system partition and had to pull some tricks to even get back into a bootable rom. I took one of the TWRP stock restores and reverted all the way back to 1.12.651.17. Then I fastboot flashed the stock recovery from 1.54.651.8 and took the OTA update so now I am completely back to stock....FEW...avoided a trip to the sprint store. I now understand that since I don't have S-OFF yet, I should flash any software versions over .8. In order to have a fully working .13, I'm sure the firmware is required as well (most likely the reason why my audio wasn't working for some of the ROMs). However, I'm still stuck with the issue in the picture below. I need to get S-OFF so I can flash the firmware 1.54.651.8, including the Hboot, Is it possible to flash an Hboot.img without being S-OFF?
#firewater is the IRC channel for the S-OFF by the way.
Also why is my radio and open dsp showing invalid-ver-info?
Anybody please help?
And something is really messed up because now my vibration won't work. No idea what is going on I just badly need s-off.
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Captain_Throwback said:
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Click to expand...
Click to collapse
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
mjhuffer said:
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
Click to expand...
Click to collapse
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
mjhuffer said:
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
Click to expand...
Click to collapse
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Konfuzion said:
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
mjhuffer said:
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
Click to expand...
Click to collapse
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
skizzled said:
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
Click to expand...
Click to collapse
I never got a message of "You are out of luck" on my failed attempts. But....
First phone took me like 3 tries. Windows 7 x64
Second phone took like 4 failed attempts Windows 8.1 x64 (same computer) (timing out with over 2 minutes of dots......) using the exact same version of firewater as previous phone.
I was not sure if it was a Windows 8 issue.
Then I tried downloading the latest firewater and it was different from what I downloaded a month ago and worked the first time.
I agree. Try multiple times. Try with phone on WIFI vs Mobile Data. SO that Data is available quickly after adb reboot.
Try rebooting computer and try even another computer another USB port. Some computers have internal "USB Hubs". Try front vs Back etc.
I was able to do it on Windows 8.1 x64. I install latest HTC Sync. Then uninstall everything but the drivers.
I also had flashed Bad Boys 1.1 (Unlocked with S-ON) to get my rooted OS instead of manually rooting it. Then Factory Reset it. Turned on WIFI then did S-OFF.
Most rooted ROMs remove a lot of baggage that might interfere with rooting.
I'm still running all stock firmware though except for Recovery.
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
It doesn't matter how many times you try. It won't work. Read the message.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
Ouch, pretty blunt message.
You don't need S-OFF to get wifi tether. All you need is HTC Unlock and Root.
S-OFF mainly allows you to flash firmware. You can only flash complete and signed firmware without S-OFF.
And each time you do, you'll have to reflash recovery.
I believe you can install several ROMs with S-ON that support Wifi Tether.
I ran "Wifi Tether Router" from Google Play ($1.99) with S-ON (HTC Unlock/Root) before S-OFF was available.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
The Captain is right. I got on the IRC this morning and talked to the firewater guys. They didn't really say why but they were at least a good amount of help. I can't say I blame them for not releasing any information on why. I just wish I knew about bootloader exploits.
Also, I'm on windows 7 pro 64-bit. I have a laptop with win 8 64-bit, but am afraid to try on that PC due to ALL its USB ports are 3.0 (and firewater says to avoid 3.0 ports).
Captain_Throwback said:
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
Click to expand...
Click to collapse
Does this firmware.zip possibly have the hboot and boot.img included? If not could you please make me one with it. It worked but the Hboot still says Tampered Relocked and my Radio and Open DSP say Invalid_Ver_Info and I still don't have vibration.
mjhuffer said:
Does this firmware.zip possibly have the hboot and boot.img included?
Click to expand...
Click to collapse
Yes.
Thanks in advance for any help... I've searched and come up empty in terms of up-to-date stuff. I'm super-cid, unlocked bootloader, s-off (phone came that way off a private sale) with a RUU conversion to GPE. I want to take advantage of the sense 6 update especially the new battery saving mode. Really wondering weather:
1- downgrading firmware is still a thing coming from GPE and going to the latest Sense 6 roms
2- Weather I should use an RUU or try flashing a custom recovery and a wrong
3- Weather there's any other watch-outs I should know
Change your CID/MID accordingly for Dev edition and run the http://www.androidruu.com/getdownlo...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
This will get you going all the way to Sense 6 with a few updates. Do not LOCK boot loader or turn S-ON
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Without further details can't help
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Based on the google searches I've done, this is normal. The HTC RUU installation never actually finishes. You just need to wait until the progress bar stops moving, make a coffee, then reboot and hope you haven't just bricked the phone.
SaHiLzZ said:
Without further details can't help
Click to expand...
Click to collapse
See above--what happened to him is normal.
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
komienski said:
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
Click to expand...
Click to collapse
Change cid to BS_US001 and make sure mid is PN0712000
Sent from my HTC One using XDA Free mobile app