Related
Hai,
First... i'm from holland and sorry for my bad english!
My problem
I have a Incredible S made in Twaiwan and i search for a RUU that works!
I have try the follow one and comes a error 155.
Maby the wrong RUU?
I have try this one:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed
Can you help me please?
Thanks!
xander1986 said:
Hai,
First... i'm from holland and sorry for my bad english!
My problem
I have a Incredible S made in Twaiwan and i search for a RUU that works!
I have try the follow one and comes a error 155.
Maby the wrong RUU?
I have try this one:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed
Can you help me please?
Thanks!
Click to expand...
Click to collapse
The error 155 usually means that you are attempting to run a RUU on an unlocked HBOOT. You must relock the unlock boot loader and then you will be able to run the RUU. You may also need to create a goldcard to flash a WWE ROM on a Twaiwan IncS.
Ok how can i flash this goldcard?
xander1986 said:
Ok how can i flash this goldcard?
Click to expand...
Click to collapse
There is a process that turns your SD card into a goldcard so that you can flash RUUs from different regions. Once you make a goldcard, you can continue to use it as a normal SD card. Search xda for the procedure.
It's resolved! Thank you!
The thanks button is good for situations like these.
Hi, I bricked my htc incredible s.
After unbricking with jtag I have writed only bootloader with s-ON.
Recovery not working.
My phone has cid: BM___001 mid: PG3213000
I tried flash ruu rom from PG32IMG.zip i get a several errors
if i flash rom with PG3212000 i am geting wrong mid error
if rom cid not BM_001 i geting error wrong cid
if I manualy changin these parameter in android-info.txt i get signature error
tried flash from stock exe files like
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_release_199657_signed.exe
RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed.exe
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
same errors
port working not well
cant flash recovery, geting signature check error
What can I do?
Beneris said:
Hi, I bricked my htc incredible s.
After unbricking with jtag I have writed only bootloader with s-ON.
Recovery not working.
My phone has cid: BM___001 mid: PG3213000
I tried flash ruu rom from PG32IMG.zip i get a several errors
if i flash rom with PG3212000 i am geting wrong mid error
if rom cid not BM_001 i geting error wrong cid
if I manualy changin these parameter in android-info.txt i get signature error
tried flash from stock exe files like
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_release_199657_signed.exe
RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed.exe
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
same errors
port working not well
cant flash recovery, geting signature check error
What can I do?
Click to expand...
Click to collapse
Create a goldcard and then flash the RUU:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.480 2.30.0822U_3822.10.08.28_M_release_227170_signed.e xe
It is really strange that you have a PG3213000 but your CID is BM_0001 but a goldcard should allow you to flash the WWE RUU.
And another stupid question
If i make gold card with my another android phone (HTC Dream) do hi works in HTC Incredible S?
Beneris said:
And another stupid question
If i make gold card with my another android phone (HTC Dream) do hi works in HTC Incredible S?
Click to expand...
Click to collapse
Yes a goldcard is not specific to the phone it was created on. It is a special signature on the SD card that HTC is able to read.
Maked goldcard and same CID error
ht tp://img40.imageshack.us/img40/9578/ciderrorwithgoldcard.jpg
Any options?
Beneris said:
Maked goldcard and same CID error
ht tp://img40.imageshack.us/img40/9578/ciderrorwithgoldcard.jpg
Any options?
Click to expand...
Click to collapse
What procedure did you use to create the goldcard? It appears that the goldcard did not work.
You are trying to flash the 3.08.405.2 RUU, correct?
No, flashed this rom WWE_3.08.405.3, (3.08.405.2).
1. Inserted sdcard to htc derise hd
2. Unmounted from system
3. With GoldCardTool_0.0.5 readed card CID
4. From webpage with cid generated goldcard.img
5. And finaly with button [Load GoldCard.img] finished job
Cheked with DxH Hexeditor goldcard.img and SdCard first 170 lines the same.
another strange detail, nn the other side my phone model writed PG32120 but connsole said PG3213000
Beneris said:
No, flashed this rom WWE_3.08.405.3, (3.08.405.2).
1. Inserted sdcard to htc derise hd
2. Unmounted from system
3. With GoldCardTool_0.0.5 readed card CID
4. From webpage with cid generated goldcard.img
5. And finaly with button [Load GoldCard.img] finished job
Cheked with DxH Hexeditor goldcard.img and SdCard first 170 lines the same.
another strange detail, nn the other side my phone model writed PG32120 but connsole said PG3213000
Click to expand...
Click to collapse
OK, that is making more sense now. I was wondering how you had CID of BM_0001 with a PG321300 model. You need to flash this RUU:
http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_199657_signed.exe
On a side note, since you created it on a HTC Desire HD, did you use the right MMC value? You need to use MMC1 not MMC0.
Thanks a lot, my error was MMC0 value.
Now i maked right GoldCard.
Tried flash RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_ elease_199657_signed but after ZIP check, phone didn't done anything.
Second time flashed
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805.30.085AU_3805.04.03.27_M_release_199657_signed successful
One prob, wifi not working. Wifi wasn't worked and with others roms before brick.
Now in my settings showing Wifi mac address Unavailable
Do I missing wifi driver? I was told that wifi micro chip is new. (The man who writed a bootloader said to me)
Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?
The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Shu. said:
The recovery is broken, and the rom doesn't boot.
I can enter the recovery, but as soon as I try to wipe data or install a rom, it reboots. I tried "fastboot erase cache", I tried reflashing CWM and TWRP, and I tried ADB Sideload on both, same results.
The only way for me is to run RUU, but the problem is, any RUU that I try says "The ROM Update Utility Cannot update you Android phone. Please get the correct ROM Update Utility and try again.
I am s-off and supercid on hboot 1.55, with the 3.57 firmware. Any ideas on how to get the RUU working? Thanks!
Click to expand...
Click to collapse
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
nkk71 said:
which RUU are using? you probably have to change CID to SuperCID.
also read through this about recovery problems: http://forum.xda-developers.com/showthread.php?t=2494111
EDIT: also for RUU to work, I believe you need to be locked or relocked.
Click to expand...
Click to collapse
Okay, then that seems to be the issue, i'll try to relock, thanks!
Shu. said:
Okay, then that seems to be the issue, i'll try to relock, thanks!
Click to expand...
Click to collapse
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
nkk71 said:
DO NOT GO S-ON !!
and check CID if it's compatible with the RUU, otherwise change to SuperCID.
Click to expand...
Click to collapse
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
If you have S-off you don't have to lock your bootloader to run a ruu.
Shu. said:
I am already super CID, so I think the only issue is with the unlocked boot loader. I'm gonna try to re-lock it now. And thanks again for the warning, I won't go s-on
Click to expand...
Click to collapse
No problem :good:
Post back with your results so we know
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
maxal said:
If you have S-off you don't have to lock your bootloader to run a ruu.
Click to expand...
Click to collapse
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
I stand corrected
---------- Post added at 05:11 PM ---------- Previous post was at 05:09 PM ----------
Shu. said:
If that is the case, could the newer version of the hboot cause the issue? because I'm trying to flash an old RUU. I tried the hTC_Asia_WWE_1.29.707.3, which is for my region, as well as US_WWE_1.29.1540.16 (developer edition) as I'm supercid. both failed
Click to expand...
Click to collapse
with S-Off it's no problem to downgrade. where did you get the RUU, can you post link.
And what's the exact error you get?
EddyOS said:
This. I've never had to relock the bootloader to flash an RUU as I'm S-OFF. Just connect the phone in fastboot mode and run the RUU you want to use
Click to expand...
Click to collapse
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Shu. said:
Now I tried the developer edition 3.22.1540.1 that I just downloaded from HTC dev, and its installing, so I think its gonna be okay. Thanks to everyone for the speedy replies!
Click to expand...
Click to collapse
For other RUUs check this site: http://www.htc1guru.com/downloads/ruu-file-downloads/
I find HTCdev way too confusing, as it clutters everything together, you can easily download a RUU for "HTC One S" instead of "HTC One" (aka M7)
And since you're S-Off downgrading is no problem
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?
hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work
reealumni said:
hello guys.
i had an htc one m7 ul for a while and all was great until the network stopped working.
so i decided to flash an RUU exe for my device which is HTC___J15
the process did not finish and it gave the error "failed zip" on the fastboot screen.
i rebooted the phone and it went back to the fastboot screen and it never got back in the system, this was two days ago.
yesterday i tried to flash the htc___j15 ruu zip file and it gave me the signature verification failed error.
it says tampered and reclocked *security warning* and my hboot version is 1.61 and os-7.19.401.51
after some reaserch im discovering it says s-on .
is there any way to put it to s-off or downgrade the hboot from 1.61
tried revone,rumrunner and all those did not work
Click to expand...
Click to collapse
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.
alray said:
If your version main is 7.19.401.51 then the only RUU you can flash is the 7.19.401.51 version. You don't need S-OFF to flash this RUU and fyi, S-OFF can only be acheived using the Sunshine S-OFF exploit on this hboot version. Hboot can only be downgraded when already S-OFF.
If you need more help, pleas post the output of "fastboot getvar all" with your next post (hide imei/serial)
The 7.19.401.51 RUU can be found here at post #2 and instruction how to flash at post #1.
Click to expand...
Click to collapse
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF
reealumni said:
i will try use the exact OS from your given link. and how do i use SUnshine for S-OFF
Click to expand...
Click to collapse
At first you need a running system cause sunshine is an app based service. After that you can download the latest sunshine app and install it, then the app will test your device if it is possible to make it s-off. If it can, in the second step you have to buy a license for your device within sunshine (about 20€/25$). After sucessfully payment your device will reboot and sunshine will set it to s-off.(The license is bind to your device and you can use it on this device as often as you want, for other devices you need to buy another license)
http://theroot.ninja/
phone is now working but...
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
If after flashing the RUU your problem isn't fixed, it's probably an hardware problem.
reealumni said:
so guys i flashed the zip using htc-fastboot and the phone is back to normal but with unkown imei and baseband. Thats basically no network
how to fix that now?
Click to expand...
Click to collapse
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd
KARIM9377 said:
Reflash ruu
Or
If you have backup of partition 2,3,4,5. You can restored the partitions that have phone info like imei and serial no with TWRP by if=dd
Click to expand...
Click to collapse
will try reflash the RUU. i do not have any backups of the partitions :crying: