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
Related
I have my HTC Sensation XE which has originally the 2.3.4 Gingerbread.
I would like to have an assistance on how to do it?
Do I need to flash specific firmwares? Where could I get it? and is it safe to use the backup I made before with that Gingerbread Rom?
Thank you.
I used SUPERCID method.. Therefore I'm not exactly sure whats my CID number and RUU but im pretty sure its either HTC__038 or HTC__044 asia or wwe_asia.
If it helps , I had some Starhub apps, Singtel or whatever, so I assume its more of an HTC__044 CID number?
Thank you.
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
stringer7 said:
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
ardom said:
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
Click to expand...
Click to collapse
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
stringer7 said:
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
I had changed my CID when i rooted mine i used supercid method and changed it to 11111111 i forgot my original ru. Im nt sure exactly too if its wwe_asia or asia but im sure its either of the two. I had Starhub app too so i have a premonition that it could be htc__044 or asiawwe singapore version.
Im confused lol. I Want to go back to my stock ruu and cid. Or least the cid so i could restore my backup if possible. Then if ever i ota update. Less prblems could be encountered.
Sent from my HTC Sensation XE with Beats Audio
What are the steps I need to do?
Which to flash? any firmware?
THank you.
This is a prime example of making sure you check for the RUU BEFORE you flash anything new
Do what is said above and it will tell you your original CID. We can then see if we can find the RUU
Good luck. I just updated my xe to ics by simply reading a lot of posts on this site. And simply following all instructions.
At first tho, I mistakenly flashed sensation and not sensation xe. But again, found the correct files here on this site. All sorted and now have beats audio back, now with sense and ics latest.
So many helpful people here, so I hope you too get your fine sorted to the way you want yours. Although curious as to why you wanna go back to gb.
Surely ics is better?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
hi
hi guys, do you have any link for official Gingerbread RUU 1.73 with beats audio for sensation XE? i just turn my sensation XE to s-on and flash the RUU but i flashed a wrong ruu.thanks guys.i want to update my sensation XE to ics through system update
Are you S-ON again now? If so, you'll need to S-OFF before you can flash the XE RUU (which you can find here):
https://www.yousendit.com/download/M3BtWmd2YWJ6NE5qQTlVag
Its already 1111111 for my CID. Im planning to go back to stock gb so i can get the ota ics and try it out.
Sent from my HTC Sensation XE with Beats Audio
Yes my phone is s-on again, so how do I flash the ruu?and just s-off? No need to do rooting?thanks
Help ~ Loop boot
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
soldierforus said:
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
Click to expand...
Click to collapse
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
ganeshp said:
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
Click to expand...
Click to collapse
Sorry to double post, I thought this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later I found a cynaogen tutorial to help with boot loop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So how do the RUU's function exactly? I read the glossary term in wiki, but I don't fully understand the concept. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
soldierforus said:
Sorry to double post, I though this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later found a cynaogen turoial to help with bootloop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So How the RUU's function exactly. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
Click to expand...
Click to collapse
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
No-Go
ganeshp said:
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
Click to expand...
Click to collapse
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
soldierforus said:
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
Click to expand...
Click to collapse
RUU is rom update utility.. It's official htc file
Ruu is complete software for your phone
It wipes everything.. Rom, recovery firmware.. Everything and flashes the corresponding stock One...
So when you run ics ruu.. You will have complete ics stock rom of tmobile US
And the recovery flash you did earlier was wrong..
You need to keep that recovery file in the adb folder (it should be in pc) Then the command will fetch the file.. As you have kept it on top of sdcard.. It can't find it..
Sent from my pyramid.. Through blazing fast sonic waves
I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.
Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita
I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33
Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita
Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off
:thumbup:
Sent from my Evita
Btw.... If I helped you, please press the thanks button.
Sent from my Evita
Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app
Will this RUU work if I have a locked bootloader and s-on?
Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita
guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?
Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita
3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>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) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.
Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?
Hi all!
Im in a big pickle here and I cant get myself out at the moment.
First hand.. The info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3917mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Now i've been running cyanogenmod 10 stable since I started rooting etc...
And it's been amazing, but now since there has been a release candidate for 10.1, I was looking into updating it.
I ran into an issue where my boot-loader was not accepted , therefor i would run into an error on Clockwork mod stopping me from flashing 10.1
The bad thing was that I erased my previous installation without backing up the stock and CM10.
So now i'm left with no system. Though I can get into Fastboot and ADB via recovery.I
For some reason if I try to flash CM10 (The rom and the boot file) the cyanogenmod logo will continue spinning.
I tried to fiddle around with my RUU afterwards because I currently have S-On. But i later learned that i need superCID.
^(Which i learned that you need your phone on to alter it to the 8 "1"s) Which i cant do because i have no system.
I might have already altered some files guessing that my boot-loader is named "dirty-d92cc658" and im afraid that I messed up something internally.
So anyways. Im here with my Ville S4 plugged in on fastboot not knowing what to do.
Any Help would be amazing , thank you
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
c19932 said:
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
Click to expand...
Click to collapse
Do I need to have superCID to flash RUU's ?
Mozziliac said:
Do I need to have superCID to flash RUU's ?
Click to expand...
Click to collapse
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
tivofool said:
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
Click to expand...
Click to collapse
How can I superCID my phone if I cant boot into the rom?
I've never superCid, can't help you there.
Good news is you can get into bootloader still.
You could fastboot flash a boot.img and flash a rom in recovery.
Just need to mount usb storage in recovery to put the rom.zip on your phone.
Edit: reread that you tried that but rom didn't boot. Hopefully you waited 5-10 min for first load.
try wipedata/factory reset from CWM like 3 times then flashing?
Good luck to ya.
Edit 2: kind of wondering if you can run the Rogers RUU with that low of a bootloader (version-bootloader: 1.13.0000)
Maybe someone can chime in, because that would be nice not having to SuperCid.
Alright so I seemed to get it running on CM 10 by switching recoveries and flashing it's boot.
Then I was able to superCID the phone, which then lead my into S-off'ing it.
Then I was able to update the hboot firmware to 2.15
Cleared the cache and installed the new kernel and flashed cyanogenmod 10.1 rc
Everything went well after that. I did run into a laggy issue, which I then fixed by switching the CPU governor to ondemand instead of interactive.
Thanks for the post guys
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.
I'm stuck on hboot 1.09 with S-on and a custom recovery. My questions are
1. Are there any roms that i can flash ?
2. Can i S-off using fasboot since adb isn't accessible atm
3. Any other way to get this phone running ?
4. I dont have any backup, wiped everything and don't even have the previous rom that was flashed on the phone.
{
"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"
}
Enter recovery and mount USB .
Copy a ROM that is working on ur hboot.
Unmount usb, do a full wipe and than flash the copied ROM .
Don't forget to flash the boot IMG( after flashing the ROM) via fasboot.
Restart system .
Sent from my One S using Tapatalk
matu89 said:
Enter recovery and mount USB .
Copy a ROM that is working on ur hboot.
Unmount usb, do a full wipe and than flash the copied ROM .
Don't forget to flash the boot IMG( after flashing the ROM) via fasboot.
Restart system .
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
I've tried a few roms from xda, none working. Flashed boot.img and all ?
Sent from my Nexus 7 using Tapatalk
What's the error says?
Sent from my One S using Tapatalk
matu89 said:
What's the error says?
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
No error, just doesn't boot. Gets stuck on the htc logo
Sent from my Nexus 7 using Tapatalk
Try to update twrp and see
Sent from my One S using Tapatalk
matu89 said:
Try to update twrp and see
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
Already am on 2.5.0 Twrp :|
U must doing something wrong , flash again the previous ROM (the last one that worked for u) , return to fastboot and issue the command : flash boot xxx.IMG
Sent from my One S using Tapatalk
Yo, had the sam issue while trying to flash to CyanogenMod 12.1.
Forgot to flash boot.img using fastboot and it ended up in infinite looping, and i was unable to even get tot he fastboot menu.
It helped to disconnect the battery for 10 seconds.
Took me a while to get to it, as Torx 5 is needed for disassembly.
I'm sorry i can't post links as i am a newbie, but the YT video ID is the following: KkG2mPkfGZI
matu89 said:
U must doing something wrong , flash again the previous ROM (the last one that worked for u) , return to fastboot and issue the command : flash boot xxx.IMG
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
I dont have the previous rom on the phone either. A relative was using this phone and wanted to sell it off. Wiped it without actually knowing and now am in this situation. Tried flashing viper 2.2.0 from http://forum.xda-developers.com/showthread.php?t=2105863 but it stops before ending. I guess i need to update my hboot to be able to flash any rom at the moment ?
You could still try with a RUU...
DaMachk said:
You could still try with a RUU...
Click to expand...
Click to collapse
I haven't found the RUU for my mobile. I'd prefer to go full stock or anything. I'm willing to try anything at the moment :| my "fastboot getvar all" result is following
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT249W403058
(bootloader) imei: 359902040657367
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
How 'bout ths site?
http://forum.xda-developers.com/showthread.php?t=2094414
DaMachk said:
How 'bout ths site?
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Quick question. Is T-MOB010 = TMOUS ?
shani248 said:
Quick question. Is T-MOB010 = TMOUS ?
Click to expand...
Click to collapse
Sorry, but i'm not sure...
But if you are in the US and the mobile is T-MOBILE branded, then go with the TMOUS...
If the mobile was bought in Europe and is T-MOBILE branded, then i suggest you go with the TMOB_DE.
EDIT: so apparenlty, regarding this topic: http://forum.xda-developers.com/showthread.php?t=1228787
the T-MOBILE010 is TMOUS.
DaMachk said:
Sorry, but i'm not sure...
But if you are in the US and the mobile is T-MOBILE branded, then go with the TMOUS...
If the mobile was bought in Europe and is T-MOBILE branded, then i suggest you go with the TMOB_DE.
EDIT: so apparenlty, regarding this topic: http://forum.xda-developers.com/showthread.php?t=1228787
the T-MOBILE010 is TMOUS.
Click to expand...
Click to collapse
Thank you for this so much ! Downloading the RUU as we speak. Will update after it finishes !
Finally flashed the RUU after some windows 8.1 problems but the phone is working now. Thank you so much guys ! You've been great help !
Great to hear.
Hope it serves you well. Mine will be 3 yeas old in a few weeks.