[Q] Stuck between Roms - HTC Incredible S

I was flashing custom ROMs and accidentally soft-bricked my phone after attempting to go from an alpha Ice Cream Sandwich build to flashing the RUU of the official Sense 3.0 OTA (I know, stupid rookie mistake. I was tired). I tried fixing it, but so far have come up empty handed. The bootloader has just been unlocked through htcdev.com after multiple failed attempts and previously was S-OFF through AlphaRev's Revolutionary (S-ON => Revolutionary S-OFF => S-ON => HTCDEV unlock).
Bootloader reads:
VIVO PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-3822.10.08.28_M
eMMC-boot
Nov 1 2011,20:33:03
When I attempt to boot, it stays on the htc logo screen, then turns off and back on and into recovery.
Does anyone else have this problem or know how to solve it?
I'd like to flash the new RUU.
So far I've tried:
Flashing htc recovery so I can try flashing the RUUs again. No luck
I even modified the android-info.txt inside the RUUs.
I've tried the WWE RUU, the Asia HK RUU and the Asia WWE RUU (the guy from pakistan who posted in the general thread)
Should I be downgrading using a goldcard?

A goldcard is not for downgrading as such, its for flashing another carriers rom. So by all means, try flashing stock RUU with goldcard if you can't locate RUU from your carrier.
You mentioned trying to flash stock recovery but having no luck. With recovery or RUU after that?

Since you are in Canada, you probably have a IncS S710A/PG3212000 model. All of the 3.0x RUUs are for the PG3213000 model, so your only hope is that the unlocked bootloader is going to allow you to flash a modified PG32IMG.zip that has the android-info.txt file changed for modeled PG3212000.
I was able to do this with the 3.08.405.3 WWE RUU, but in my case I have permanent S-OFF via the XTC clip, so the real question is whether the 2.00.0000 unlocked HBOOT will allow you to flash a modified RUU ROM.zip or not. Good luck. You may just have to settle for custom ROMs.

Nonverbose said:
You mentioned trying to flash stock recovery but having no luck. With recovery or RUU after that?
Click to expand...
Click to collapse
I can flash the stock recovery all right by extracting recovery.img from the RUU.zip through fastboot. Sorry, I was unclear. I meant that flashing the RUUs through the bootloader still didn't work even after flashing the recovery. It's mentioned somewhere that you need the htc recovery to flash the RUU, and that it won't work with CWM.

tpbklake said:
Since you are in Canada, you probably have a IncS S710A/PG3212000 model. All of the 3.0x RUUs are for the PG3213000 model, so your only hope is that the unlocked bootloader is going to allow you to flash a modified PG32IMG.zip that has the android-info.txt file changed for modeled PG3212000.
Click to expand...
Click to collapse
Actually, I own a S710e/PG32130 model. I bought it from Taiwan, unlocked.
tpbklake said:
I was able to do this with the 3.08.405.3 WWE RUU, but in my case I have permanent S-OFF via the XTC clip, so the real question is whether the 2.00.0000 unlocked HBOOT will allow you to flash a modified RUU ROM.zip or not. Good luck. You may just have to settle for custom ROMs.
Click to expand...
Click to collapse
I tried the HK one first, because I thought it might be the one that Taiwan receives (Apparently the WWE was for European countries?). Anyways, that worked (sort of, that's how I got this updated Hboot and radio). Then I couldn't boot so I tried the other Asia WWE and the Euro WWE and neither will flash.

If the device is unlocked you can just extract the update zip file and flash it manually. Probably just needs boot.img
fastboot flash boot boot.img
(Although this depends on what exactly is unlocked and with what method,something your posts do not state)

Nonverbose said:
(Although this depends on what exactly is unlocked and with what method,something your posts do not state)
Click to expand...
Click to collapse
I mean I bought it off contract, for the full price of 500 dollars. There are no carrier markings on it either. I bought it from an independent shop, not from a carrier store.
Nonverbose said:
If the device is unlocked you can just extract the update zip file and flash it manually. Probably just needs boot.img
Click to expand...
Click to collapse
Do you mean extract the rom.zip from the RUU.exe, flash the rom.zip as PG32IMG.zip in the bootloader and then fastboot flash boot.img (extracted from PG32IMG.zip)? I've tried that, I'll try it again.
Thanks for the help by the way, and happy new year!

exaltedbladder said:
I mean I bought it off contract, for the full price of 500 dollars. There are no carrier markings on it either. I bought it from an independent shop, not from a carrier store.
Do you mean extract the rom.zip from the RUU.exe, flash the rom.zip as PG32IMG.zip in the bootloader and then fastboot flash boot.img (extracted from PG32IMG.zip)? I've tried that, I'll try it again.
Thanks for the help by the way, and happy new year!
Click to expand...
Click to collapse
Actually just meant the boot.img as there seems to be a common trend of it failing on this phone with symptoms of stopping at splash screen.
On that note when flashing img file in fastboot you need to specify the partition you wish to flash, which is missing in your post, it should read:
fastboot flash(command) boot(partition) boot.img(file)
Minus the brackets of course.
Happy new year to you also

Flashing the boot.img still isn't working. I've tried all three boot.imgs.
EDIT: I've been doing
"fastboot flash boot boot.img"

Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
@tpbklake can you see what filesystem stock rom is using please

Nonverbose said:
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
@tpbklake can you see what filesystem stock rom is using please
Click to expand...
Click to collapse
The stock ROM uses EXT3 for the filesystem.

Nonverbose said:
Flash a custom recovery and boot into it. Wipe cache, dalvik cache and do factory reset. Restart phone and give it 5-10 mins boot time in case its trying to rebuild dalvik cache
Click to expand...
Click to collapse
I used CWM, and it's just like before. It shows the htc screen for around 10 seconds then reboots into recovery.

exaltedbladder said:
I used CWM, and it's just like before. It shows the htc screen for around 10 seconds then reboots into recovery.
Click to expand...
Click to collapse
Flash 4ext recovery so you can confirm that your partitions are formatted to the correct filesystem (ext3) I'm not 100% but I think ics may use ext4

Nonverbose said:
Flash 4ext recovery so you can confirm that your partitions are formatted to the correct filesystem (ext3) I'm not 100% but I think ics may use ext4
Click to expand...
Click to collapse
Yeah, great idea. I had a feeling it was to do with ICS. I'll get right on that.

Whelp, looks like they're all ext3 unfortunately.

exaltedbladder said:
Whelp, looks like they're all ext3 unfortunately.
Click to expand...
Click to collapse
OK, here is a thought after rereading your original post. You currently have HBOOT 2.00.0000 and it has been unlocked via HTCDEV.com, right?
In order to flash a RUU with HBOOT 2.00.0000 in place, it must be in a LOCKED/RELOCKED state. So one suggestion you could try is go into FASTBOOT mode and enter
fastboot oem lock
to relock and then try and run the Sense 3.0 RUU that you attempted in the first post.

tpbklake said:
OK, here is a thought after rereading your original post. You currently have HBOOT 2.00.0000 and it has been unlocked via HTCDEV.com, right?
In order to flash a RUU with HBOOT 2.00.0000 in place, it must be in a LOCKED/RELOCKED state. So one suggestion you could try is go into FASTBOOT mode and enter
fastboot oem lock
to relock and then try and run the Sense 3.0 RUU that you attempted in the first post.
Click to expand...
Click to collapse
Okay, it wasn't locked before. After issuing the command, the bootloader now says
*** RELOCKED ***
*** Security Warning ***
at the top. I tried flashing the PG32IMG.zip, but now it's giving me a CID error. I did getvar all to find out out my cidnum is HTC__621 while in the android-info.txt for the RUU it is HTC__622. Is it enough to edit the android-info.txts or do I need a goldcard or something else to flash the RUU? I'm going to try the other RUUs as well.
EDIT: I just checked all my RUUs. None of them are HTC__621. The closest is HTC__622. Yikes.

exaltedbladder said:
Okay, it wasn't locked before. After issuing the command, the bootloader now says
*** RELOCKED ***
*** Security Warning ***
at the top. I tried flashing the PG32IMG.zip, but now it's giving me a CID error. I did getvar all to find out out my cidnum is HTC__621 while in the android-info.txt for the RUU it is HTC__622. Is it enough to edit the android-info.txts or do I need a goldcard or something else to flash the RUU? I'm going to try the other RUUs as well.
EDIT: I just checked all my RUUs. None of them are HTC__621. The closest is HTC__622. Yikes.
Click to expand...
Click to collapse
Then you will need a goldcard to try and flash.

tpbklake said:
Then you will need a goldcard to try and flash.
Click to expand...
Click to collapse
All the guides I've found require me to install GoldCardHelper from the Android Market or to use adb. My phone doesn't work. Is there any other way to create a goldcard?

exaltedbladder said:
All the guides I've found require me to install GoldCardHelper from the Android Market or to use adb. My phone doesn't work. Is there any other way to create a goldcard?
Click to expand...
Click to collapse
Do you have another phone that you could use?
---------- Post added at 03:46 PM ---------- Previous post was at 03:31 PM ----------
tpbklake said:
Do you have another phone that you could use?
Click to expand...
Click to collapse
OK, so once again reading through this thread, here is what the current status of your phone is:
HBOOT 2.00.0000 RELOCKED
You can boot into HBOOT USB and FASTBOOT USB mode, right? There is currently no RUU for your CID, so a goldcard is needed.
When you were attempting to flash the boot.img files in FASTBOOT mode, the phone was in a LOCKED state, not the UNLOCKED state, right?
Since you can't boot the phone so you can use adb.exe plus the fact that zergRush cannot temp root HBOOT 2.00.0000 anyway, you could try going to HTCDEV.com and follow the unlock bootloader procedure to change HBOOT to UNLOCKED. Then you could retry flashing a boot_signed.img from the PG32IMG.zip file in FASTBOOT mode.

Related

[Q] HELP!!! Unroot Attempt - Different Fastboot than the normal

Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...
Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again
Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:

[Q] Help! Problems to unroot M7_UL!

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)

[Q] HTC ONE bootloop, no recovery, wrong CID, S-ON

Hi Guys,
1 month ago I chaged my HTC ONE into Google Play Edition. Then Yesterday I wanted to get it to stock sense.
What I did:
*) restore CID to HTC__032 (do not know if it is right CID, network: P4 play for Poland)
*) restore stock via TWRP
*) downgrade bootloader from 1.54 to 1.44
*) locked (reveone)
*) S-On
Now, my phone got always bootoader with a msg: "Security Warrinig"
Canno go to recovery - phone always reboots. System doesn't start.
I'm assuming that to repair my phone the first thing I have to do is S-OFF. I cannot do this via HTCDEV unlock file, every time when i fire "fastboot flash unlocktoken unlock_code.bin"
file is successfully sent and that's all. "Swipe - unlock" screen doesn't appear. As we know ADB PUSH won't work in fastboot mode.
How I can transfer reveone file into internal storage to get my phone s-Off again and corretley flash a bootloader (1.54)?
Regards.
rwachowiak said:
Hi Guys,
1 month ago I chaged my HTC ONE into Google Play Edition. Then Yesterday I wanted to get it to stock sense.
What I did:
*) restore CID to HTC__032 (do not know if it is right CID, network: P4 play for Poland)
*) restore stock via TWRP
*) downgrade bootloader from 1.54 to 1.44
*) locked (reveone)
*) S-On
Now, my phone got always bootoader with a msg: "Security Warrinig"
Canno go to recovery - phone always reboots. System doesn't start.
I'm assuming that to repair my phone the first thing I have to do is S-OFF. I cannot do this via HTCDEV unlock file, every time when i fire "fastboot flash unlocktoken unlock_code.bin"
file is successfully sent and that's all. "Swipe - unlock" screen doesn't appear. As we know ADB PUSH won't work in fastboot mode.
How I can transfer reveone file into internal storage to get my phone s-Off again and corretley flash a bootloader (1.54)?
Regards.
Click to expand...
Click to collapse
so let me get this straight:
1- S-On
2- LOCKED
3- No functioning ROM
if yes, you're pretty much stuck
did you get a new unlocktoken from HTCdev or are you using the old one. try registering a new account with HTCdev and get a new unlock file.
nkk71 said:
so let me get this straight:
1- S-On
2- LOCKED
3- No functioning ROM
if yes, you're pretty much stuck
did you get a new unlocktoken from HTCdev or are you using the old one. try registering a new account with HTCdev and get a new unlock file.
Click to expand...
Click to collapse
yes, I have tried - no success.
At first, the HTC Dev Unlock does NOT give you S-Off. It just unlocks your bootloader. And why did you change your CID if you didnt know if it was the right one? Google will help you to find the right one.
In case this IS the right one, I dont think you need S-Off as you're able to flash a new Recovery without S-Off. Try HTC aio Tool for example or via adb/fastboot flash. If this worked you'll be able to flash a new firmware.
Good Luck
http://xda7.androidrevolution.nl/db_mirror/Grafika/Sygnatura/User_banners/atticus182-2.png
Gesendet von meinem HTC One mit Tapatalk
rwachowiak said:
yes, I have tried - no success.
Click to expand...
Click to collapse
did you try with a new email account?
So you were s-off before then back to s-on. Or how you downgraded from 1.54 to 1.44 ? I am confused now
Sent from my HTC One using xda app-developers app
Thank's for all your responses.
So:
 @nkk71 - tried with new account - still no success.
 @Frask3r - as long as I'm not able to run anything except bootloader: adb commant won't work(no way to perform push), fastboot only works.
 @polariscon - I wanted to flash my googles' bootloader with the orginal one from HTC, so I flashed via fastboot.
I can confirm that CID is correct one HTC__032. I do not know if it will help.
You can flash with fastboot commands
http://xda7.androidrevolution.nl/db_mirror/Grafika/Sygnatura/User_banners/atticus182-2.png
Gesendet von meinem HTC One mit Tapatalk
Frask3r said:
You can flash with fastboot commands
Click to expand...
Click to collapse
Ok.. so to do it, I need: RUU 1.29.401.12 Radio 4A.18.32.63.15 for model PN0710000.
This software version I have installed on my HTC ONE. As far as I know I cannot flash it with any other RUU.
Am I correct?
Regards.
rwachowiak said:
Ok.. so to do it, I need: RUU 1.29.401.12 Radio 4A.18.32.63.15 for model PN0710000.
This software version I have installed on my HTC ONE. As far as I know I cannot flash it with any other RUU.
Am I correct?
Regards.
Click to expand...
Click to collapse
oh I just saw you downgraded to 1.44, try an RUU (windows exe) from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
which is compatible with your MID & CID (use fastboot getvar all, to determine MID & CID)
Hello.
I need help to fix my htc one.
I did delete everything on my internal sdcard. Cause i want to make it as new to give it to my girlfriend. But when i did that. Its stopped working. I've tried to use all in one kit by squabbi. But it won't work to change boot or anything. Maybe i did smt wrong.
When i turn on my htc one. Its stuck in boot. White screen with htc logo on it. I cant even turn it off again. I have to wait when the battery its empty. And then i can turn it on to fastboot. Before all that. I came into recovery and then its stands no OS on the phone.
But after i yried to fix it by myself then it will not be able to even touch the recovery. I push the screen,but nothing happend. I think i did it worse or smt. Pleas help if somebody can. It would be great.
Sent from my C6603 using XDA Premium HD app
Sent from my C6603 using XDA Premium 4 mobile app
nkk71 said:
oh I just saw you downgraded to 1.44, try an RUU (windows exe) from here...
which is compatible with your MID & CID (use fastboot getvar all, to determine MID & CID)
Click to expand...
Click to collapse
Thanks nkk71. I will try this, but I'm not to sure if I can do it without S-OFF especialy when I have a higher firmware version installed (1.29.401.12). I will let you know as soon as I'm done.
rwachowiak said:
Thanks nkk71. I will try this, but I'm not to sure if I can do it without S-OFF especialy when I have a higher firmware version installed (1.29.401.12). I will let you know as soon as I'm done.
Click to expand...
Click to collapse
if the ruu.exe doesnt work, then there's this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
flashable with s-on and locked using fastboot in RUU mode, let me know if you need the exact commands and remember the flash zip has to be done twice, one after another!!
rwachowiak said:
Thanks nkk71. I will try this, but I'm not to sure if I can do it without S-OFF especialy when I have a higher firmware version installed (1.29.401.12). I will let you know as soon as I'm done.
Click to expand...
Click to collapse
doesn't work:
updating signature....
error[140] bootloader version error
I will try with dectypted version.
nkk71 said:
if the ruu.exe doesnt work, then there's this: http://www.htc1guru.com/dld/ruu-zip...0-01_release_318486_signed_2_4_decrypted-zip/
flashable with s-on and locked using fastboot in RUU mode, let me know if you need the exact commands and remember the flash zip has to be done twice, one after another!!
Click to expand...
Click to collapse
Doesn't work.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
system msg:
FAILED (remote:12 signature verify fail)
Any suggestions?
rwachowiak said:
Doesn't work.
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
system msg:
FAILED (remote:12 signature verify fail)
Any suggestions?
Click to expand...
Click to collapse
After reading OP i think you have many things mixed up so plz clarify
What happens when you try to boot into recovery...if its stock recovery it takes some time for red triangle to appear.
Which "swipe-unlock" screen are you talking about in unlocking bootloader.
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work
grayhawk11 said:
After reading OP i think you have many things mixed up so plz clarify
What happens when you try to boot into recovery...if its stock recovery it takes some time for red triangle to appear.
Which "swipe-unlock" screen are you talking about in unlocking bootloader.
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work
Click to expand...
Click to collapse
so..
What happens when you try to boot into recovery... phone reboots to bootloader mode
Which "swipe-unlock" screen are you talking about in unlocking bootloader.fastboot flash unlocktoken Unlock_code.bin
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work -I have tried more then 5 times
I think that my bootloader is corrupted...
rwachowiak said:
so..
What happens when you try to boot into recovery... phone reboots to bootloader mode
Which "swipe-unlock" screen are you talking about in unlocking bootloader.fastboot flash unlocktoken Unlock_code.bin
When using RUU zip try more than once sometimes it takes 2 - 3 tries to work -I have tried more then 5 times
I think that my bootloader is corrupted...
Click to expand...
Click to collapse
But you can still boot into hboot so it might not be all lost
When was the last time you able to boot normally (after each steps you mentioned in OP)
I'm Sorry for answering so late. My phone just came back from "local" GSM repair center.
So what they done?
They destroyed my back cover and using JTAG changed cid to: HTC_02_2 and version-main to 1.00.000.00
and they told me that I'm not able to flash my phone with any current ROM version because I have to wait for
the latest one.
I have tried to update my phone with RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe on my own.
I changed my cid in android-info.txt but after "signatures checking" step i received error msg no 131 (customer id)
Now I'm wondering, if I will procceed with below steps:
*) change cid to: 11111111 (using JTAG)
*) still s-on (i cannot change it - bootloop)
*) bootloader locked
are there any chances to make it works again?
Cheers
Robert
Can you unlock bootloader, flash custom recovery, root, and install a custom rom?
Then S-Off, and move to a HTC__001 based International HTC One RUU file.
What is your hboot version? or fastboot getvar all output?

Help me please! :(

My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me
JeySee said:
My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me
Click to expand...
Click to collapse
tried to boot into recovery with this command:
fastboot boot "C:\pathtorecovery\recoveryname.img"
Click to expand...
Click to collapse
simply replace the path and filename with yours...
If you are able to do this.. you can reply so I can decide what you have to do next...
Thank you but have to wait until I get home in approx 4-5 hrs, will try it! Thanks
LibertyMarine said:
tried to boot into recovery with this command:
simply replace the path and filename with yours...
If you are able to do this.. you can reply so I can decide what you have to do next...
Click to expand...
Click to collapse
Im pretty sure you cannot boot into a custom recovery with S-ON
To remove the TAMPERED and LOCK the bootloader, you will have to S-OFF using rumrunner for hboot 1.5x or revone for hboot 1.44
The current Rumrunner can work with a custom rom e.g. the latest version of ARHD or Insertcoin ROM that has an unsecure kernel. To do this though you will have to unlock the bootloader using htcdev and install the custom rom and then S-OFF
stovie_steve said:
Im pretty sure you cannot boot into a custom recovery with S-ON
To remove the TAMPERED and LOCK the bootloader, you will have to S-OFF using rumrunner for hboot 1.5x or revone for hboot 1.44
The current Rumrunner can work with a custom rom e.g. the latest version of ARHD or Insertcoin ROM that has an unsecure kernel. To do this though you will have to unlock the bootloader using htcdev and install the custom rom and then S-OFF
Click to expand...
Click to collapse
JeySee said:
My current situation is : M7_UL PVT Ship S- On Tampered relocked & unrooted again. No Rom installed, no backup, no recovery!
:'(
I tried installing RUU file but it failed, tried two/three different RUUs.
Also tried to achieve S-Off but maybe I'm to dumb & it didn't work.
I'm out of ideas, please help me
Click to expand...
Click to collapse
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:
klashnikoff said:
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:
Click to expand...
Click to collapse
Could You please tell me the comand i need to type to push the rom.zip (cmd is open in the directory were the zip is).
Thank You for Your help!!!
Edit: I found a way with HTC ONE Toolkit 2.0, hope I´ll get everything You said working
JeySee said:
Could You please tell me the comand i need to type to push the rom.zip (cmd is open in the directory were the zip is).
Thank You for Your help!!!
Click to expand...
Click to collapse
I already put it up mate it's "adb push Rom.zip /sdcard
klashnikoff said:
I already put it up mate it's "adb push Rom.zip /sdcard
Click to expand...
Click to collapse
Got Rom installed
JeySee said:
Got Rom installed
Click to expand...
Click to collapse
Ooo good good let me know how it goes
klashnikoff said:
Ooo good good let me know how it goes
Click to expand...
Click to collapse
Well it´s a great Rom, the same i had since yesterday & I´m realy happy!!!
I´m concidering not to S-off my device, or what´s Your opinion?
I´m going to do a backup asap before I´ll do anything again with the Xposed Installer, which did something this morning, that completly messed uo my phone.. Perhaps You know which mods are not to be touched
Best regards!!!!!
JeySee said:
Well it´s a great Rom, the same i had since yesterday & I´m realy happy!!!
I´m concidering not to S-off my device, or what´s Your opinion?
I´m going to do a backup asap before I´ll do anything again with the Xposed Installer, which did something this morning, that completly messed uo my phone.. Perhaps You know which mods are not to be touched
Best regards!!!!!
Click to expand...
Click to collapse
Tbh I know in theory xposed should be dangerous but it's really not. I would defo s-off though you need to install the latest firmware which you will be missing and addresses a LOT of issues. S-off the device and I will show you how to upgrade the firmware
klashnikoff said:
Tbh I know in theory xposed should be dangerous but it's really not. I would defo s-off though you need to install the latest firmware which you will be missing and addresses a LOT of issues. S-off the device and I will show you how to upgrade the firmware
Click to expand...
Click to collapse
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?
JeySee said:
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?
Click to expand...
Click to collapse
I used to use ARHD but I switched to maximus HD because of the OTA and the 360 camera mod.
So to upgrade firmware you want to boot into fastboot and type "fastboot getvar mid" write it down then go to http://forum.xda-developers.com/showthread.php?t=2485651 and download the correct version against your mid.
Put it in your adb/fastboot folders and making sure your still in fastboot type "fastboot oem rebootRUU"
Once you phone boots into update mode you will see a HTC logo on your screen and nothing else.
Rename the firmware you just downloaded to firmware.zip and type "fastboot flash zip firmware.zip"
It will say say failed pre hboot update flush image again. Simply type the exact same cmd again "fastboot flash zip firmware.zip" and it will flash the latest firmware.
The progress bar on your phone probably won't go all the way up but as long as cmd says finished its done so just type "fastboot reboot-bootloader" and if you look your main-os will have changed.
That's it.
Your on the latest firmware meaning all the Roms should run smoothly and you should have no more issues with exposed.
---------- Post added at 04:46 AM ---------- Previous post was at 04:43 AM ----------
JeySee said:
Ok
I tried very hard to S-Off by using the revone method without success & now I´m giving Rumrunner do its magic :victory:
It´s seems to do a good job fingers crossed!!!
Btw on what Rom are You??? Is it a stable Rom or are there some bugs???
Finished.... S-Off
What´s next?
Click to expand...
Click to collapse
One thing I forgot to mention you need super cid so if you havn't already you need to be in fastboot and you need to type "fastboot oem writecid 11111111" and then fastboot reboot-bootloader you cod should have changed to 11111111 allowing you to flash an ruu for any phone now.
Everything done, thanks for your help!
Good night ;;?
Sent from my HTC One using xda app-developers app
klashnikoff said:
I used to use ARHD but I switched to maximus HD because of the OTA and the 360 camera mod.
So to upgrade firmware you want to boot into fastboot and type "fastboot getvar mid" write it down then go to http://forum.xda-developers.com/showthread.php?t=2485651 and download the correct version against your mid.
Put it in your adb/fastboot folders and making sure your still in fastboot type "fastboot oem rebootRUU"
Once you phone boots into update mode you will see a HTC logo on your screen and nothing else.
Rename the firmware you just downloaded to firmware.zip and type "fastboot flash zip firmware.zip"
It will say say failed pre hboot update flush image again. Simply type the exact same cmd again "fastboot flash zip firmware.zip" and it will flash the latest firmware.
The progress bar on your phone probably won't go all the way up but as long as cmd says finished its done so just type "fastboot reboot-bootloader" and if you look your main-os will have changed.
That's it.
Your on the latest firmware meaning all the Roms should run smoothly and you should have no more issues with exposed.
---------- Post added at 04:46 AM ---------- Previous post was at 04:43 AM ----------
One thing I forgot to mention you need super cid so if you havn't already you need to be in fastboot and you need to type "fastboot oem writecid 11111111" and then fastboot reboot-bootloader you cod should have changed to 11111111 allowing you to flash an ruu for any phone now.
Click to expand...
Click to collapse
Your welcome good night
Sent from my HTC One using xda app-developers app
klashnikoff said:
Yeah you cant boot .img files any more with s-on or s-off htc removed it in the now HBOOT and fastboot.
Dont panic mate its really easy to fix
Simply download ARHD from http://forum.xda-developers.com/showthread.php?t=2183023 make sure you have all the latest drivers and everything installed and rename the file to rom.zip you will need TWRP for this i believe and simply boot to recovery (TWRP) and push thw file to your sdcard using adb push rom.zip /sdcard (takes a while) simply flash arhd rom.
Once your phone boots you can use rumrunner.us to s-off the phone. Follow the instructions on their site. Once thats done boot to fastboot and use the command fastboot oem writecid 11111111 you will now have supercid and you can now flash any ruu you like. (unless you need to downgrade hboot.) If thats the case pm me and i can guide you through it on here.
Kris :laugh:
Click to expand...
Click to collapse
You mean I can't boot into a custom recovery with S-OFF and a unlocked bootloader? Sry.. I'd test that but my phone is sent in for repair
LibertyMarine said:
You mean I can't boot into a custom recovery with S-OFF and a unlocked bootloader? Sry.. I'd test that but my phone is sent in for repair
Click to expand...
Click to collapse
Yeah afraid so. Tbf I don't know of that is the case for every phone but the m7_ul UK edition couldn't get it to work on any device I tried after contacting a friend who I have inside HTC's repair centre he claimed the feature does not work with the latest hboot.
I might see if I can get some other devices from work to test this further and if it is true for all variants then maybe enroll on a workaround
Kris
klashnikoff said:
Yeah afraid so. Tbf I don't know of that is the case for every phone but the m7_ul UK edition couldn't get it to work on any device I tried after contacting a friend who I have inside HTC's repair centre he claimed the feature does not work with the latest hboot.
I might see if I can get some other devices from work to test this further and if it is true for all variants then maybe enroll on a workaround
Kris
Click to expand...
Click to collapse
fastboot boot recovery.img only works in hboot 1.44, it was either patched or broken in hboot 1.54
nkk71 said:
fastboot boot recovery.img only works in hboot 1.44, it was either patched or broken in hboot 1.54
Click to expand...
Click to collapse
Thought so. Thanks for clarifying
klashnikoff said:
Thought so. Thanks for clarifying
Click to expand...
Click to collapse
no problem, it might have actually been broken by accident, someone disassembled the code and saw a bad memcpy; sort of lost track of the post though

[Q] RUU update: stuck @ 5% checking headers

HTC One
Tamperd
Relocked
2.24.401.8
S-ON
Cidnum HTC_Y13
Hboot: 1.54.0
I'm using this RUU:
RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1
I double checked my fastboot connection, every thing seems to be working just fine.
Everytime i try to run it it get stuck at checking headers (5%)
what am i doing wrong ?
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
SaHiLzZ said:
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
Click to expand...
Click to collapse
Any other RUU suggested ?, i'm currently stuck with the bootloader, can i even normally boot up the device with the current ROM ?
SaHiLzZ said:
I think there is something wrong with that ruu. I have not been able to run the 4.x RUU
Click to expand...
Click to collapse
S7atem said:
what do you suggest i should do ?, i'm currently stuck with the bootloader, can i even normally boot up the device with the current ROM ?
Click to expand...
Click to collapse
It does actually work, just seems very sensitive to OS, USB ports, drivers, (possibly even locale), etc.
Recommend you use a plain vanilla Win7 PC with USB2 port.
Try extract Rom.zip & flash with fastboot
from HTC One
yatindroid said:
Try extract Rom.zip & flash with fastboot
from HTC One
Click to expand...
Click to collapse
where can i find the .ZIP of this ROM ?
S7atem said:
where can i find the .ZIP of this ROM ?
Click to expand...
Click to collapse
you can extract it from current ruu exe
Follow thread http://forum.xda-developers.com/showthread.php?t=2497614
from HTC One
I had this exact problem trying to go back from 5.11.401.10. When i extracted the rom.zip, fastboot came back with remote: 02 data length is too large.
I had already unlocked with HTCDev, flashed TWRP and s-off. i just wanted a stock ruu to go back to sense 5.5. In the end, i found TeHashX has created a twrp flash here: Link I flashed that without root, with radio and recovery and I'm back to stock. You'll probably need to be s-off for this but I'm not sure. I kept s-off and the unlocked bootloader.
Ps. You can remove the tampered with a rooted rom in the process.
Craig
craiglay said:
I had this exact problem trying to go back from 5.11.401.10. When i extracted the rom.zip, fastboot came back with remote: 02 data length is too large.
I had already unlocked with HTCDev, flashed TWRP and s-off. i just wanted a stock ruu to go back to sense 5.5. In the end, i found TeHashX has created a twrp flash here: Link I flashed that without root, with radio and recovery and I'm back to stock. You'll probably need to be s-off for this but I'm not sure. I kept s-off and the unlocked bootloader.
Ps. You can remove the tampered with a rooted rom in the process.
Craig
Click to expand...
Click to collapse
I have also been unable to use any of the 4.xx RUU... They worked once but none of them work now. Anyway I just wanted to say I also created a Guru Reset for the 5.21.502.2 (AT&T) here >> http://www.androidfilehost.com/?fid=23501681358545274 to go along with the files posted by @TeHashX
The only thing i can think of was the hboot prevents it now but i wasnt going to play with that. I personally went to 4.xx to get away from sense 6
Is there any other maybe older stock ROM i can try ?
I tried 1.29.401.x and that failed too. There was a note with the download saying you need to flash hboot 1.44 which i didn't bother with.

Categories

Resources