Database Info

RUU - Error 140.

I tried to run a RUU.exe on my HTC One S. Sadly I get a error 140 everytime I try. I read somewhere it could be something with I try to flash an older RUU version, than my current version. What can I do about it?
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 1.06es.50.02.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.31.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4164mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
EDIT: THIS PICTURE I POSTET, SAYS UNLOCKED. BUT I DID RELOCKED WHEN I TRYID TO FLASH.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Your hboot is 1.14 thats highest currently hence cannot RUU an older version, RUU 2.31 is released by football in development section, try it to return stock!

mughalgxt said:
Your hboot is 1.14 thats highest currently hence cannot RUU an older version, RUU 2.31 is released by football in development section, try it to return stock!
Click to expand...
Click to collapse
I will try to take a look on it. Tyvm.
EDIT: Wow, he just uploaded it, 1 hour ago?

mughalgxt said:
Your hboot is 1.14 thats highest currently hence cannot RUU an older version, RUU 2.31 is released by football in development section, try it to return stock!
Click to expand...
Click to collapse
Alright. RUU did work. But I'm very confused about what ClockMod I should install, can anyone be nice and guide me?
I also read there is a different between HTC One S models, S1, S2, and S3. How to find out which one I have?

DownClock said:
Alright. RUU did work. But I'm very confused about what ClockMod I should install, can anyone be nice and guide me?
I also read there is a different between HTC One S models, S1, S2, and S3. How to find out which one I have?
Click to expand...
Click to collapse
Lol there is only the S4 and S3. Check your box the phone came in and see if it says 1.5GHz or 1.7GHz. 1.5 is the S4
Sent from my HTC One S running ViperOneS!

invasion2 said:
Lol there is only the S4 and S3. Check your box the phone came in and see if it says 1.5GHz or 1.7GHz. 1.5 is the S4
Sent from my HTC One S running ViperOneS!
Click to expand...
Click to collapse
Ah kewl, I just skipped most of the text. It's 1.5GHz, so it's S4.
EDIT: It worked! Perfectly!
Thanks for helping me put guys!

DownClock said:
Ah kewl, I just skipped most of the text. It's 1.5GHz, so it's S4.
EDIT: It worked! Perfectly!
Thanks for helping me put guys!
Click to expand...
Click to collapse
Hey DownClock,
yesterday I tried to install the 2.31 RUU but it did not work for me. I am on codefireX nightlies (CM10 derivate). To install the RUU I flashed stock recovery and relocked the bootloader. But the the phone stuck on boot animation and I had to revert everything (re-unlock, flash custom recovery (TWRP) and restored a backup).
What ROM were you on when you installed the RUU and did you relock the bootloader and flash stock recovery? Is that all necessary?
TIA
Burkhard

herzbert said:
Hey DownClock,
yesterday I tried to install the 2.31 RUU but it did not work for me. I am on codefireX nightlies (CM10 derivate). To install the RUU I flashed stock recovery and relocked the bootloader. But the the phone stuck on boot animation and I had to revert everything (re-unlock, flash custom recovery (TWRP) and restored a backup).
What ROM were you on when you installed the RUU and did you relock the bootloader and flash stock recovery? Is that all necessary?
TIA
Burkhard
Click to expand...
Click to collapse
Yes you need to relock your device. My (or my friends ROM) was Stock, but that should not affect anything. What I did was:
Step 1: Relock.
Step 2: Run the RUU.
Sendt fra min HTC One X med Tapatalk2

How do I relock? Also, I have an S4, but I'm not sure what version my hboot is. I never flashed a new radio, jsut rooted and am running CM10. Which RUU do I download and where do I download it from? Thanks!

Legaleye3000 said:
How do I relock? Also, I have an S4, but I'm not sure what version my hboot is. I never flashed a new radio, jsut rooted and am running CM10. Which RUU do I download and where do I download it from? Thanks!
Click to expand...
Click to collapse
This is not my primary phone, but my friends. But I will try my best
Your HBOOT version should not being affected if you install the newest RUU.
You can download a RUU here. Remember to choose the right country!
And as you noticed the accecs will cost you a bit.
Here is also a guide you should follow.

It's better to flash RUU by fastboot usb.

hawkattack said:
It's better to flash RUU by fastboot usb.
Click to expand...
Click to collapse
Eh.. How else can you flash?
Sendt fra min HTC One X med Tapatalk2

DownClock said:
Here is also a guide you should follow.
Click to expand...
Click to collapse
That guide helped me. Relock bootloader, reboot into fastboot and start the RUU exe file.
Tanks.

herzbert said:
That guide helped me. Relock bootloader, reboot into fastboot and start the RUU exe file.
Tanks.
Click to expand...
Click to collapse
Glad I could help
Sendt fra min HTC One X med Tapatalk2

Current ROM is not stable, unable to flash most of the roms via TWRP with S-Off

Ok, I'll start from the beginning.
I purchased my phone from Rogers at April 2012. So it was Rogers stock 4.0.x rom, everything was locked at that time. I FORGOT the stock hboot/ruu version number for Rogers ONE XL.
From the time being, I rooted it, superCID, unlocked via HTC DEV. After these, I flashed customer recovery, and successfully flashed several roms from time being. Finally I stayed with ViperXL.
Then, facepalm s-off is released, and I s-offed my phone. Everything worked just fine.
The problem occurred when I started to flash sense 5 roms about couple weeks ago. I did not upgrade my firmware and I flashed sense 5 based roms (this is my bad), so I'm experiencing random reboot and signal drops. Then I upgraded my firmware using the instruction in this tread: http://forum.xda-developers.com/showthread.php?t=2423735 . I verified my installtion with ./fastboot gervar all . At this time, there were two warnings on the top of my bootloader: "tampered" and "unlocked".
So, at this time, I tried several sense 5 roms. My recovery at this time was TWRP 2.6.3.0. All the roms have one common problem on my phone: after I locked the screen and left my phone for a while, if I wanna wake my phone/display, nothing happened by pressing the power button. I have to press the power button for 10+ seconds to restart my phone. If I just left my phone for a short time and wake it, it will work properly.
I was thinking are these sense 5 problems, so I tried to flash cm roms yesterday. I followed the instructions in http://forum.xda-developers.com/showthread.php?t=2382933 to upgrade my RUU to 3.18. I flashed TWRP 2.6.3.0, and tried to flash cm 10.1 and 10.2. For cm 10.2, there were a lot of force close when I boot my phone. For cm 10.1, it is so unstable with random reboots as well as did not respond when I try to wake up the phone. I am not questioning CM's roms, I am sure there were something wrong with my phone or what I've done to it.
So, I tried to flash viper rom again with ruu 3.18 installed. The rom won't even boot...... However I found something interesting when I am flashing the viper rom. The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.
Then I re-installed the RUU 3.18 update on my phone. Right now, the AT&T stock rom also will not respond after I left my phone idle for a moment......
User timmaaa kindly reminds me about something. I am posting the original post I started in another tread.
Originally Posted by snake3276120 View Post
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/show....php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB. (Sorry for the bad English, I actually mean "The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.")
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.
timmaaa:
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OK, I am wondering where I can get my RUU number......
Also, in this case, what I should do now? Install TWRP 2.6.0.0 and try to flash everything again?
Currently "tampered" is gone from my bootloader, only "unlocked" stays there.

Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita

timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
Because some posts are saying RUU 3.17 or 3.18, so I got confused...... but as long as it's a program, I will assume they are talking about the firmware or bootloader after running RUU 3.17 or 3.18 upgrade.

timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
I fixed the qoute

Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita

timmaaa said:
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
Click to expand...
Click to collapse
That's right, I didn't even flash recovery... Well, my stock rom just self-rebooted, and stuck at booting animation while adb is still able to recognize it, and I can issue a reboot from adb. This also applies to my sense 5 roms.
If it's hardware problem, looks like upgrading to hboot 2.15 ruined my hardware, which is hard to believe...... Everything works fine before I upgrade my hboot to 2.15

Unfortunately it isn't under warranty anymore either.
Sent from my Evita

timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I know... it is unfortunate...

timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.

snake3276120 said:
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
Click to expand...
Click to collapse
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.

Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita

timmaaa said:
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
Click to expand...
Click to collapse
I used 2.6.0.0 to flash my current magiorom 4..... well at least it is usable now, with app/sense/notification bar/wake phone do not respond sometimes... I'm not blaming the rom, I am blaming my phone... probably now it's the time to get a new one lol

redpoint73 said:
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Click to expand...
Click to collapse
Here you are, boss.
PS E:\Program Files (x86)> cd '.\Minimal ADB and Fastboot'
PS E:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
PS E:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I think the result is the same in thread http://forum.xda-developers.com/showthread.php?t=2423735
Quoted from the thread:
Install:
Installing the rom:
Download the rom and copy to your sdcard
Reboot to Recovery
Flash rom
I recommend you wipe data before or after flashing the rom
For root access, flash this: Flash this in recovery for root access
Reboot
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip>
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Click to expand...
Click to collapse
Please refer to the attachment for a photo of my bootloader

Will TWRP 2.3.3.0 solve my problem? It looks like most roms recommend this recovery.... btw I'm running 2.6.0.0 at the moment.

No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita

timmaaa said:
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
Click to expand...
Click to collapse
lol thanks... Every time before I flash a new rom, I just format everything...

I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita

timmaaa said:
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...

snake3276120 said:
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
Click to expand...
Click to collapse
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4

sandys1 said:
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Ok I'll do a backup and try tonight....latest twrp do u mean 2.6.3.0, or there is another new release?

SOLVED Boot Loop and bricked

Hey guys already tried everything and everything is still same so what's my problem here we go. 5 Hours ago or less downloaded stock rom and installed with recovery mods everything was great until the phone restarting after android boot logo appears after 1 min device starting to boot loopping . Also i cant handle recovery or factory reset. While installing the rom something comes around " want to install supersu?" and i said no , and why answered no , because thought already this rom has superuser mod . so why i have this problem i know about rooting and i cant open anything to install superuser also with adb i cant handle the device some commands working but others not. Please help me searched almost all the words but still i cant fix that .
Thanks.
Edit: Also when trying to push ROM to sdcard getting " error: device is not found" downloaded all the sdk things and drivers still cannot connect to cmd prompt.
Edit2 : So still trying to do something i think the problem is as i said rooting. The main question is how i can root my device without recovery mode because i cant handle it also i cant push anything with adb , and its so annoying i cant handle anything please help me :/

Korvacs said:
Hey guys already tried everything and everything is still same so what's my problem here we go. 5 Hours ago or less downloaded stock rom and installed with recovery mods everything was great until the phone restarting after android boot logo appears after 1 min device starting to boot loopping . Also i cant handle recovery or factory reset. While installing the rom something comes around " want to install supersu?" and i said no , and why answered no , because thought already this rom has superuser mod . so why i have this problem i know about rooting and i cant open anything to install superuser also with adb i cant handle the device some commands working but others not. Please help me searched almost all the words but still i cant fix that .
Thanks.
Edit: Also when trying to push ROM to sdcard getting " error: device is not found" downloaded all the sdk things and drivers still cannot connect to cmd prompt.
Click to expand...
Click to collapse
Is your one mini international or at&t?also, can you go to your boot loader? just hold down the power button until ur phone is turn off and hold volume down and power. if ur model is the at&t one, you can take the at&t ruu. if not idk what u can do.

abzboi said:
Is your one mini international or at&t?also, can you go to your boot loader? just hold down the power button until ur phone is turn off and hold volume down and power. if ur model is the at&t one, you can take the at&t ruu. if not idk what u can do.
Click to expand...
Click to collapse
Nope its international i bought it from Turkey i think its international also tried HBOOT recovery thins as i said recovery mode is doesnt working anymore . Entering recovery text appear then black screen coming and then device continue loopping forever.

Still waiting for any help guys please.
Also device information here maybe it helps to make something.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.22.40e.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ADWA03301
(bootloader) imei: 35586605630****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Korvacs said:
Still waiting for any help guys please.
Also device information here maybe it helps to make something.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.22.40e.00.07
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3ADWA03301
(bootloader) imei: 35586605630****
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5820000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-871d213f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
If your boot loader is unlocked, then flash a recovery. Flash the twrp 2.6 one not that newest one. And I hope it'll work. Good luck

abzboi said:
If your boot loader is unlocked, then flash a recovery. Flash the twrp 2.6 one not that newest one. And I hope it'll work. Good luck
Click to expand...
Click to collapse
Wont work flashed recovery again and still same thing happened boot loopping

Korvacs said:
Wont work flashed recovery again and still same thing happened boot loopping
Click to expand...
Click to collapse
Can you go to recovery after flash the twrp 2.6.0.0?
Edit: Hey I think I know what you did wrong. Did you flash the boot.img from the zip in the boot loader after flashing the rom? If not go ahead and try. You won't be able to boot through htc logo until you flash the boot.img.

abzboi said:
Can you go to recovery after flash the twrp 2.6.0.0?
Edit: Hey I think I know what you did wrong. Did you flash the boot.img from the zip in the boot loader after flashing the rom? If not go ahead and try. You won't be able to boot through htc logo until you flash the boot.img.
Click to expand...
Click to collapse
Yup first flashed recovery then flashed boot.img but still same thing stuck at htc boot screen and recovery wont working.

Here we go Flashed this http://forum.xda-developers.com/showthread.php?t=2594253 recovery mode and worked now what to i dont know but still trying to fix it.

Korvacs said:
Here we go Flashed this http://forum.xda-developers.com/showthread.php?t=2594253 recovery mode and worked now what to i dont know but still trying to fix it.
Click to expand...
Click to collapse
reflash the rom?

abzboi said:
reflash the rom?
Click to expand...
Click to collapse
Yeah trying to move rom file to sdcard but its more harder for me , i think . Also in ADB Cmd promt while in sideload recovery mode my device was there so its good growth for me So after installing rom.zip getting weird error .

Korvacs said:
Yeah trying to move rom file to sdcard but its more harder for me , i think . Also in ADB Cmd promt while in sideload recovery mode my device was there so its good growth for me So after installing rom.zip getting weird error .
Click to expand...
Click to collapse
Try to install a different rom. The newest 4.3 rom that trigger made

abzboi said:
Try to install a different rom. The newest 4.3 rom that trigger made
Click to expand...
Click to collapse
You mean magio rom ? i am trying to install stocked rom i think its better than modded rom . Also i cant move rom file to sdcard the problem is here i think . I can give teamviewer id pw if u want to help me please.

Korvacs said:
You mean magio rom ? i am trying to install stocked rom i think its better than modded rom . Also i cant move rom file to sdcard the problem is here i think . I can give teamviewer id pw if u want to help me please.
Click to expand...
Click to collapse
Is adb not working for you?

Solved
Anyway fixed everything and flashed stocked rom from trigger. This device make a so much headcache nevermind thanks for helping " abzoi"

Korvacs said:
Anyway fixed everything and flashed stocked rom from trigger. This device make a so much headcache nevermind thanks for helping " abzoi"
Click to expand...
Click to collapse
No problem, glad to hear that your device is working again I hope you'll enjoy you one mini

abzboi said:
No problem, glad to hear that your device is working again I hope you'll enjoy you one mini
Click to expand...
Click to collapse
Yup finally i fixed it but it took almost 24 hours to work it Flashed 4.3 rooted stock rom and working well :good:

Korvacs said:
Yup finally i fixed it but it took almost 24 hours to work it Flashed 4.3 rooted stock rom and working well :good:
Click to expand...
Click to collapse
I had a problem too yesterday. I finally know how to use adb now.

[FIRMWARE][2.18] AT&T Sense 5 OTA Firmware.

AT&T Latest Firmware For There Sense 5 Android 4.2.2 Release.
I took the honors of removing "Boot.img" and "Recovery.img". So it doesnt overwrite your current boot.img or recovery.img... Should of been posted last night ( Feb 16 ) when I did this but was busy with my family afterwards.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0000
(bootloader) version-baseband: 1.35a.32.45.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.18.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3bfc037
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Click to expand...
Click to collapse
Download:
AT&T 5.18 Firmware MD5 Checksum - 78aa08f90d38c16f1b0a93f508bece8f

Definitely going to try this after switching from cm to viper
Sent from my One X using XDA Premium 4 mobile app

Arrow44 said:
Definitely going to try this after switching from cm to viper
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
please tell me if all goes well. it worked on my at&t Varient idk about other Varients... but it should work fine with telstra and rogers longs your s-off

Does anyone know if updating hboot would cause any problems if I'm currently running a modified hboot?

jacobas92 said:
Does anyone know if updating hboot would cause any problems if I'm currently running a modified hboot?
Click to expand...
Click to collapse
What hboot is that?
Sent from my HTC6435LVW using XDA Premium 4 mobile app

24ky said:
What hboot is that?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
2.15. I just have the tampered, lock, and security flag status spoofed.
Sorry if this is OT btw, I didn't know if it really warranted a new thread.

jacobas92 said:
2.15. I just have the tampered, lock, and security flag status spoofed.
Click to expand...
Click to collapse
Picture?
Sent from my HTC6435LVW using XDA Premium 4 mobile app

24ky said:
Picture?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Uhh, well I don't actually have any other way to take a picture. It's fine, I guess I can just reflash an unmodified 2.15 just to be on the safe side. I don't know why I didn't think of that before.

24ky said:
please tell me if all goes well. it worked on my at&t Varient idk about other Varients... but it should work fine with telstra and rogers longs your s-off
Click to expand...
Click to collapse
Worked flawlessly, had to flash image twice then rebooted into twrp and proceded to flash Viper. After running it for a little it seems snappier and hopefully more battery friendly.
Sent from my HTC One XL using XDA Premium 4 mobile app

Arrow44 said:
Worked flawlessly, had to flash image twice then rebooted into twrp and proceded to flash Viper. After running it for a little it seems snappier and hopefully more battery friendly.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So if I understand correctly, this will update the ROM without touching the bootloader or recovery, right?
And once installed, the One X will have the latest firmware and ROM, but retain any root already in place?
And if I restore from nandroid backup, it will keep the new radio and firmware, but replace ATT new ROM with the one from the backup?

No, this is a hboot, radio, WiFi partition updates ... You will remain on what ever rom your on now... Just you'll be on the company's latest software minus the rom, boot.img and recovery.ing
Sent from my HTC6435LVW using XDA Premium 4 mobile app

24ky said:
No, this is a hboot, radio, WiFi partition updates ... You will remain on what ever rom your on now... Just you'll be on the company's latest software minus the rom, boot.img and recovery.ing
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for this clarification. I read the initial post completely reversed...

Worked as advertised. I rebooted to bootloader and I flashed a clean copy of my recovery anyway. Then I wiped all but the SD and flashed a backup I had just made prior to this.
Everything is running good. I will be checking it out this week and seeing if it makes a difference if any at all.
I got so used to the red text being gone that it surprised me when it displayed on my splash screen. No big deal, it's a cosmetic thing.

Fastboot flash zip returns unknown partition 'zip'
Error cannot determine image filename for 'zip'.
Is this placed in adb folder or on sd?
Sent from my HTC One XL using XDA Premium 4 mobile app

I'm pretty sure you flash this like the other firmware file by putting it into your adb folder on the PC.

Venomtester said:
Fastboot flash zip returns unknown partition 'zip'
Error cannot determine image filename for 'zip'.
Is this placed in adb folder or on sd?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Zip stands for the zip-name.
in this case fastboot flash zip Att_5.18_firmware.zip.
and yes put it in the adb Folder.

Hi,
I am getting following message when tried on my Windows 7 machine in Bootloader.
C:\New folder\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.066s]
finished. total time: 0.067s
C:\New folder\platform-tools>fastboot flash Att_5.18_firmware.zip
unknown partition 'Att_5.18_firmware.zip'
error: cannot determine image filename for 'Att_5.18_firmware.zip'
Kindly help me to get rid of the error.
Thanks and Regards,
Sathish.

sathish804 said:
C:\New folder\platform-tools>fastboot flash Att_5.18_firmware.zip
unknown partition 'Att_5.18_firmware.zip'
error: cannot determine image filename for 'Att_5.18_firmware.zip'
Kindly help me to get rid of the error.
Thanks and Regards,
Sathish.
Click to expand...
Click to collapse
you forgot the zip !!
fastboot flash zip Att_5.18_firmware.zip
you can copy past this!

ok so i got this little problem, and im trying to do everything i can to flash this successfully, please help, any ideas?
C:\Users\student>fastboot flash C:\User\student Att_5.18_firmware.zip
sending 'C:\User\student' (20880 KB)...
OKAY [ 2.260s]
writing 'C:\User\student'...
FAILED (remote: not allowed)
finished. total time: 2.292s

Ghostrider said:
you forgot the zip !!
fastboot flash zip Att_5.18_firmware.zip
you can copy past this!
Click to expand...
Click to collapse
Thank You!!
Its worked after correcting the fasboot command.
Regards,
Sathish.

[Q] Rooting mistake

Hey guys.
I wanted to root my HTC One S, and I read that the program SuperOneClick was the fastest way of doing it, so I went ahead and connected the HTC to my PC with the USB cable and clicked "root". After like 15 minutes however the program didn't do anything, it just froze and I had to close it. Root Checker Basic said something similiar to no valid root or something. Tried to click "unroot" now so I could start again with a different method, froze again, closed SuperOneClick again. What am I supposed to do now? Is rooting it again safe as I now probably have some half / corrupted root? And can someone link me to the best method? Thanks in advance.

CrackedHippo said:
Hey guys.
I wanted to root my HTC One S, and I read that the program SuperOneClick was the fastest way of doing it, so I went ahead and connected the HTC to my PC with the USB cable and clicked "root". After like 15 minutes however the program didn't do anything, it just froze and I had to close it. Root Checker Basic said something similiar to no valid root or something. Tried to click "unroot" now so I could start again with a different method, froze again, closed SuperOneClick again. What am I supposed to do now? Is rooting it again safe as I now probably have some half / corrupted root? And can someone link me to the best method? Thanks in advance.
Click to expand...
Click to collapse
One-click-roots are not suggested...
Did you unlock the bootloader?

Just unlocked the bootloader and flashed cwm, my own fault for using superoneclick. Thanks anyway ;p

Sorry for the double post. I may need some help as I probably bricked(?) my One S.
Didn't do anything root-related for a long time so I think I made a beginner's mistake.
What I did was unlock (htcDEV), and flash CWM recovery.
I tried installing liquid kitkat custom rom, but now it won't boot, not even in recovery.
Help?
EDIT: It's stuck in a boot loop :/

CrackedHippo said:
Sorry for the double post. I may need some help as I probably bricked(?) my One S.
Didn't do anything root-related for a long time so I think I made a beginner's mistake.
What I did was unlock (htcDEV), and flash CWM recovery.
I tried installing liquid kitkat custom rom, but now it won't boot, not even in recovery.
Help?
EDIT: It's stuck in a boot loop :/
Click to expand...
Click to collapse
Press Power button for 10secs+ to power off
Can you enter fastboot? Is your phone S4 ville or s3 villeC2?

LS.xD said:
Press Power button for 10secs+ to power off
Can you enter fastboot? Is your phone S4 ville or s3 villeC2?
Click to expand...
Click to collapse
I finally managed to enter recovery / fastboot.
Sorry for the foolish comment but I actually have no idea if it's S4 or S3, how do I find out?
Also what should I do right now? Flash stock rom on it or..?

CrackedHippo said:
I finally managed to enter recovery / fastboot.
Sorry for the foolish comment but I actually have no idea if it's S4 or S3, how do I find out?
Also what should I do right now? Flash stock rom on it or..?
Click to expand...
Click to collapse
FIRST you need to know which phone / firmware you got.
Enter fastboot, connect to pc, open CMD and type "fastboot getvar all"
Copy the log and post it here please. Delete IMEI/serial before you post the log. Then i can exactly tell you what you need to install

LS.xD said:
FIRST you need to know which phone / firmware you got.
Enter fastboot, connect to pc, open CMD and type "fastboot getvar all"
Copy the log and post it here please. Delete IMEI/serial before you post the log. Then i can exactly tell you what you need to install
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Here you go, thanks in advance!

CrackedHippo said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Here you go, thanks in advance!
Click to expand...
Click to collapse
HTC One S - S4 ville - generic dutch version
You will just need to flash the kernel contained in the rom (boot.img) via fastboot (S-ON means u need to flash kernel manually) to fix your installation
Generally I'd suggest
Flash this recovery via fastboot --> TWRP 2.7.0.8
(its compatible to the lastest CM11 versions 05/01/2014 and newer
And may be try PAC rom (I just love it)

LS.xD said:
HTC One S - S4 ville - generic dutch version
You will just need to flash the kernel contained in the rom (boot.img) via fastboot (S-ON means u need to flash kernel manually) to fix your installation
Generally I'd suggest
Flash this recovery via fastboot --> TWRP 2.7.0.8
(its compatible to the lastest CM11 versions 05/01/2014 and newer
And may be try PAC rom (I just love it)
Click to expand...
Click to collapse
I indeed just flashed the boot.img seperately which was in the rom, and now it works. It's a huge relief to see my phone work again, thanks a lot!!
One more thing so I avoid messing up in the future; When I decide to install another rom, do I always do a factory reset / clear cache, then flash the rom and flash the kernel via fasboot?

CrackedHippo said:
I indeed just flashed the boot.img seperately which was in the rom, and now it works. It's a huge relief to see my phone work again, thanks a lot!!
One more thing so I avoid messing up in the future; When I decide to install another rom, do I always do a factory reset / clear cache, then flash the rom and flash the kernel via fasboot?
Click to expand...
Click to collapse
FULL wipe --> format system, data, cache, dalvik --> flash rom --> immediately go to fastboot and flash the kernel --> reboot and done
Just try to get S-OFF, then the kernel get installed with the rom via recovery

LS.xD said:
FULL wipe --> format system, data, cache, dalvik --> flash rom --> immediately go to fastboot and flash the kernel --> reboot and done
Just try to get S-OFF, then the kernel get installed with the rom via recovery
Click to expand...
Click to collapse
Looks like I was cheering too early. Roughly 1 minute after launching my phone, .comSystemGUI or something along those lines stopped working, and whenever I pressed "ok" the message would instantly return. I can't connect my phone to my PC to put another ROM on it since the message won't disappear. Also I tried re-flashing the same ROM, but now it says can't mount storage/sdcard0.
Really frustrating!

http://forum.xda-developers.com/showthread.php?t=2206434
This topic guided me into getting the sdcard mountable again, but in the process I lost the rom .zip file.
And my phone won't boot anymore, it doesn't get past the HTC logo, so I can't put a new rom on it and flash it.
What is there left for me to do? Stock rom? How do I find the stock rom?
Thanks in advance.

I figured it out, thanks for your guidance LS.xD!
Basically what I did was mount the SD storage in CWM and transfer Pac-man rom onto the storage, then flash the .zip, flash Gapps and finally in bootloader fastboot the boot.img (because I'm S-ON). Maybe this will help anyone.
EDIT: Someone may wanna be careful with using TWRP, it corrupted my SD storage for a while.

CrackedHippo said:
I figured it out, thanks for your guidance LS.xD!
Basically what I did was mount the SD storage in CWM and transfer Pac-man rom onto the storage, then flash the .zip, flash Gapps and finally in bootloader fastboot the boot.img (because I'm S-ON). Maybe this will help anyone.
EDIT: Someone may wanna be careful with using TWRP, it corrupted my SD storage for a while.
Click to expand...
Click to collapse
SD card bug can also be caused by CWM or flashing a rom (Viper really loves to brick SD). I never had any issues with TWRP. The only SD card bug I had in over a year flashing roms to my One S was caused by flashing CWM
Sent from my beloved HTC One S using (most time buggy) Tapatalk