yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] rezo:
I've just checked it with my phone. Everything gone fine.

ARE you SURE that you are using the proper file? For 2.14:

If you have 2.14.401.1 you need that file:

OTA_Marvel_S_HTC_Europe_2.26.401.3-2.14.401.1_release_261810uuzn2yxubjlshdle.zip

You must copy it to the root of your SD card and type:

adb shell
su
rmdir "cache/recovery/command"
mkdir "cache/recovery"
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=SDCARD:OTA_Marvel_S_HTC_Europe_2.26.401.3-2.14.401.1_release_261810uuzn2yxubjlshdle.zip' >> /cache/recovery/command
reboot recovery

Or your stock recovery is outdated or ****ed-up... Change it.

BTW. If you flashed original RUU can't you update it directly from the phone?????
[HTC Wildfire S] Gloris:
definitely the right version

using the stock recovery from the 2.14.401.1 ruu

and no, if i goto settings, updates, it says no updates found, even on a totally fresh stock install.

trying now to manually push an older ruu, as the sd card method isn't working to dwongrade :s
[HTC Wildfire S] mud_f1:
Yes.
[HTC Wildfire S] rezo:
Ok, my next idea:

Open with winrar the OTA file and find:

OTA_Marvel_S_HTC_Europe_2.26.401.3-2.14.401.1_release_261810uuzn2yxubjlshdle.zip\META-INF\com\google\android\updater-script

Remove these lines:

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc_europe/htc_marvel/marvel:2.3.5/GRJ90/202358.1:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc_europe/htc_marvel/marvel:2.3.5/GRJ90/362953.3:user/release-keys");
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__001" , "HTC__N34" ,
"HTC__203" , "HTC__102" , "HTC__405" , "HTC__Y13" , "HTC__A07" ,
"HTC__304" , "HTC__032" , "HTC__016" ,
"HTC__E11") == "t");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PG7610000") == "t");,
assert(check_mid("simple", "PG7610000") == "t");
);
assert(getprop("ro.product.device") == "marvel" ||
getprop("ro.build.product") == "marvel");

That removes all initial checks. Maybe you have 'the special one' phone.

--- edit ---

BTW.

Go to settings and find a string with something like that:

GRJ90/202358.1:user/release-keys

GRJ90/362953.3:user/release-keys

These versions are granted to update OTA. But you can bypass it by removing lines that i wrote above.
[HTC Wildfire S] Gloris:
just got 2.13.401.3 manually pushed to the phone....unlocked....now rooting....then will try this version of the ota....

::EDIT::

still the same red triangle....going to give up now and just stuck with 2.14.401.1

maybe my phone isn't meant to get this update? lol
[HTC Wildfire S] rezo:
Try last time but DO that:

Open with winrar the OTA file and find:

OTA_Marvel_S_HTC_Europe_2.26.401.3-2.14.401.1_release_261810uuzn2yxubjlshdle.zip\META-INF\com\google\android\updater-script

Remove these lines:

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc_europe/htc_marvel/marvel:2.3.5/GRJ90/202358.1:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "htc_europe/htc_marvel/marvel:2.3.5/GRJ90/362953.3:user/release-keys");
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__001" , "HTC__N34" ,
"HTC__203" , "HTC__102" , "HTC__405" , "HTC__Y13" , "HTC__A07" ,
"HTC__304" , "HTC__032" , "HTC__016" ,
"HTC__E11") == "t");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PG7610000") == "t");,
assert(check_mid("simple", "PG7610000") == "t");
);
assert(getprop("ro.product.device") == "marvel" ||
getprop("ro.build.product") == "marvel");
[HTC Wildfire S] Gloris:
but maybe this update excludes certain phones because it will not operate with them?

maybe the radio will not work with my version or something?
[HTC Wildfire S] rezo:
Maybe. Even if for example wifi won't work, you can always go back... So why not to try? Maybe your experiance will be helpful for our community :)
[HTC Wildfire S] rioachim:
Why are you trying to root and do stuff between installing RUU 2.13 and aplying OTA? Just search for updates after RUU and only try the manual update if nothing is found. Read my post a few pages back.
[HTC Wildfire S] eoghan2t7:
Can someone package the hboot and radio from the latest update into a hboot flashable zip please I don't want to wipe my device again this week lol.

Thanks in advanced.
[HTC Wildfire S] alexlarisa:
btw is it worth to do all this or no?? because i have s-off rooted and cwm and i hate to wipe my phone just to install this update (or is there any other way to do that?)
[HTC Wildfire S] zorancd:
What is new since I did the OTA update 2.26.401.3

What is new since I did the OTA update 2.26.401.3

Could it be improved for example a camera or radio, or maybe something else is added. Is there any expert to help everyone here ...

thank you
[HTC Wildfire S] Gloris:
because even on a totally clean, fresh ruu install, my particular phone does not find any updates ota if i go to settings menus...hence the root and manual update process.

will try this again later...
[HTC Wildfire S] zabeganiot:
Defragment???

With this update we have options for defragment the disk?! BTW how to root, i can't root my phone since i update. Please help.
[HTC Wildfire S] Gloris:
eeeek....tried to downgrade completely (downgrade hboot and radio too) using tutorial i found on the forum.....

thought that this might make the ota appear under settings....still no....

no idea why but whichever ruu i use, i always get "there are no updates available for your phone"....really don't understand why :s

even if i totally downgrade back to android 2.3.3....it STILL says no updates available....

and the next downshot is that since i've done this downgrade, i seem unable to unlock my bootloader again now, or root the device.

i'm going to try to run the ruu to get back to 2.14.401.1.....hopefully this will update the hboot and radio again, so at least i can unlock.....otherwise i'm stuck with a phone that can't be updated.....

anyways.....if i get going again, i'll try removing those lines and see what happens :s

::EDIT::

p.s. at the moment, in hboot, it no longer says re-locked, locked, unlocked.....there's just nothing there at all....like it's totally stock again....and still no ota from within the settigns :s

---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------

nope....modified ota file just gives a red question mark....so, not the same as the red exclamation error....but still no update for me :s

one more thing i will try is to use the bootloader tool to change the bootloader to say "locked" instead of "relocked"....fingers crossed

::EDIT:: and thinking about it....that's not going to work either....since you need custom recovery to flash the bootloader tool....and you need stock recovery in order to update......and you can't flash custom stock recovery back over a locked bootloader......

sorry...i tried....but now i give up...ha ha.
[HTC Wildfire S] rezo:
Are you sure that you have Wildfire S? :D

Check this last time:

1. Remove lines from update-script.

2. Use a CWM RECOVERY instead a stock one! (for me it works) - Then you will be able to see where the update causes errors. We find out what's wrong with your phone.
[HTC Wildfire S] Gloris:
ha ha. definitely a wildfire s (510e).

i thought it needs stock recovery to work though?
[HTC Wildfire S] rezo:
When you remove those lines (checks) it is possible.
[HTC Wildfire S] Gloris:
just tried, and i get basically the same error (! in triangle)....although because i'm using custom recovery, i obviously get slightly different graphic....it's the graphic from cwm error screeen.
[HTC Wildfire S] rezo:
What the hell... eee maybe remove lines and use an option in CWM "update from zip file". My last guess :(
[HTC Wildfire S] Zlobizlob:
Hi, sorry i'm novice...

I have 2.13.401.3 STOCK ROM, root, S-ON. Bootloader unlocked via HTCDEV.com

I try update fota update: OTA_Marvel_S_HTC_Europe_2.26.401.3-2.13.401.3_release_2617117t5xizmcxam8j8v6.zip

but i have problem - yellow exclamation in triangl :(
[HTC Wildfire S] nzrocks:
Unlock this software version

Hi all,

I upgraded to 2.26.401.3 via OTA. Before I had no unlocked bootloader. I tried to unlock the bootloader via htcdev.com and via this method.

The HTC method didn't work because they don't seem to have a RUU for the new version. I don't know why simonsimons34's method did not work for me, but I guess it is because of the new version.

Can anyone confirm this? Any ideas how to unlock the bootloader in 2.26.401.3?
[HTC Wildfire S] Cataulin:
Just wanted to say after installing the update it made no difference. Im switching back to simonsense3.5.
[HTC Wildfire S] Zlobizlob:
This is working only with S-OFF?

i have only bootloader unlocked and don't working...
[HTC Wildfire S] zabeganiot:
I have unlocked with simons utility from here.
[HTC Wildfire S] Gloris:
if anyone else on 2.13.401.3 or 2.14.401.1 was getting "no updates available".....been reading a translation on some russian forum and apparently, if you install the 2.13.401.2 ruu (RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M_release_225747_signed.zip)

it will find the ota updates?

i'm currently testing another rom, but after a few days i maye give this method a try....
[HTC Wildfire S] Gloris:
just tried that 2.13.401.2 ruu, and my phone stikll doesn't find any ota updates.

i'm ondring if it's to do with whichever network you are using maybe?

i'm on T-Mobile UK if that makes any difference?

::EDIT::

possible progress now.

updated back to the 2.14.401.1 ruu (latest ruu), unlocked via fastboot unlock token, installed cwm recovery, removed those lines form the ota update script and renamed to update.zip. choose to install update.zip from sd card.....and it seems to go through ok, it says update completed.

now rebooting phone and greete with a logo that looks like a box with an arror coming out and pointing to the anroid character.....green progress bar.....here goes....

::EDIT2::

phone reboots and greets you with that awesome message, "congratulations, you have succesfully updated your phone to version 2.26.401.3".

can confirm that this method now works for those who were having trouble before.

also can confirm that i'm still bl-unlocked after this process, and have successfully re-installed cwm recovery, and it's easily rooted by installing the attached zip :)

thanks again for all the help getting this to work :)
[HTC Wildfire S] Stevk:
How can I root this. I seem to have no success.
[HTC Wildfire S] Gloris:
unlock bootloader with the htcdev process (no need to download any of their ruu's again), install custom recovery via fastboot (fastboot flash recovery recovery.img), then install the root.zip i've attached in the post above :)
[HTC Wildfire S] Stevk:
Jayzus, that was easy! Thanks so much. My proximity sensor is broken so I badly needed to edit the build.prop. Really appreciate it!
[HTC Wildfire S] nzrocks:
I tried this with v4 of the tool (the GUI version). I get an error that says:

"Invalid conversion of string 'Press OK to continue' to type integer."

The phone reboots and goes to a screen with a green update symbol, which is replaced after a few seconds by the red triangle (warning sign).

The "Marvel -- simonsimons23" window says

180 KB/s (1478 bytes in 0.008s)

1475 KB/s (660089 bytes in 0.437s)

1625 KB/s (793908 bytes in 0.477s)

1803 KB/s (793908 bytes in 0.430s)

The only way to continue seems to be removing the battery.
[HTC Wildfire S] Gloris:
use the htcdev method, but just skip the step about installing a new ruu. i believe that that step was originally there to get people to upgrade their hboot to an unlockable one? which the latest hboots in the ruu's are anyways?

just go through the rest of the process to get your unlock_code.bin (or if you've done it before, just use the same file) and unlock with fastboot :) then you can use the root zip i attached a few posts back.

but yeah, if that's where you were stuck on the htcdev method, just skip the ruu
[HTC Wildfire S] nzrocks:
v2 worked

Ok, thanks for the tip. I didn't try this, though. Instead I tried v2 of simonsimon34's tool, which worked perfectly. The bootloader is now unlocked.
[HTC Wildfire S] atom_cz:
Have the same problem.

updating with CWM ends with error 7

edit:

assert failed:apply_patch_check ("/system/bin/debuggerd", "2a652bc1479541a54ae5a309426294632141s695", "0a2a387e516d8d08fbf69c175179f3ec6e44b6c2")

E:Error in /sdcard/OTA_Marvel_S_HTC_Europe_2.26.401.3-2.13.401.3_release_2617117t5xizmcxam8j8v6.zip

(status 7)

Installation aborted.
[HTC Wildfire S] Gloris:
assert failed is to do with the lines that should be removed from the updater-script?

which software version are you on at the moment?

try this:-

1 - install the ruu for 2.14.401.1

(http://www.mediafire.com/download.php?o6ox43q3taa33iu)

1.5 - if you can't do this because you already have the rom from 2.26 (but old radio etc), follow this tutorial so that you can go back to ruu 2.14.401.1

http://xdaforums.com/show...ight=downgrade

2 - use htcdev process (without ruu step) to unlock bootloader

3 - install cwm recovery by flashing this file (http://www.mediafire.com/download.php?1rdxmtpx26201or) via "fastboot flash recovery recovery(custom).img"

4 - put update.zip (http://www.mediafire.com/download.php?vycb7415nn9boct) on the root of your sd card and install from cwm recovery.

4.5 - if the update doesn't work (i.e. if you still get "triangle !" logo flash this file (http://www.mediafire.com/download.php?bqni648c46r5e44) via cwm and choose the option "supervision", then try the update again.

5 - after installation and first boot (take a while) boot back to cwm and flash this root.zip (http://www.mediafire.com/download.php?dumbffr3n8igau4)

you should now have the latest stock rom, latest hboot, latest radio, and be root.
[HTC Wildfire S] atom_cz:
Now I have 2.13.401.3

and unlocked bootloader.

I'll try your method.

---------- Post added at 02:04 PM ---------- Previous post was at 01:52 PM ----------

Can't install RUU

on screen:

***UNLOCKED***

MARVEL PVT SHIP S-ON RL

HBOOT-1.09.0099

MICROCORP-0451

RADIO-7.54.39.28M

Feb 8 2012,18:29:31

RUU

Security fail!

Update Fail!
[HTC Wildfire S] Zlobizlob:
i have same problem with RUU:(
[HTC Wildfire S] Gloris:
ok, if you're on 2.13.401.3, and are bl-unlocked, install cwm recovery and try this version of the update.zip

this is just the ota 2.26 from 2.13, but i've pre-edited the update script to remove the assert lines.

so, to be clear...

if you are on 2.13.401.3 ONLY and are already bl-unlocked with cw recovery.....use THIS ZIP. http://www.mediafire.com/?vw2733he828h5zl

if you are 2.14.401.1 unlocked with cwm recovery use THIS ZIP http://www.mediafire.com/download.php?vycb7415nn9boct

the only reason i said to use that ruu, was because this is the method that worked for me, and because i couldn't get unlocked bootloader for 2.13.401.3 for some reason. but to install ruu you must first have stock system i believe? and you must be LOCKED or RELOCKED....

try the new zip i've uploaded for you first, but if that doesn't work, use the tutorial for downgrading...

let me know how you get on?
[HTC Wildfire S] atom_cz:
I tried to update.zip, unfortunately the same error

assert failed:apply_patch_check ("/system/bin/debuggerd", "2a652bc1479541a54ae5a309426294632141s695", "0a2a387e516d8d08fbf69c175179f3ec6e44b6c2")

E:Error in /sdcard/update.zip

(status 7)

Installation aborted.

Ill try downgrade

thank you for your patience

---------- Post added at 06:26 PM ---------- Previous post was at 05:44 PM ----------

but I do not know in which ROM dwngrade

tutorial link si broken
[HTC Wildfire S] Gloris:
use that downgrade method just to get to a stage where you can run an ruu, then instead of downgrade, run the 2.14.401.1 ruu....

or if you really want to do it the long way, use this ruu to go all the way back to 2.3.3

http://www.mediafire.com/?rdl6fktk68yipf3

once you're successfully on a stock rom of some description, then you can follow my guide to go to 2.14.401.1 then on to 2.26 :)
[HTC Wildfire S] atom_cz:
Set bl to relock, tried 2.14.401.1 ruu.

RUU

Main Version is older!

Update Fail!

I do not know what to do next, I give up... :(
[HTC Wildfire S] zionptm:
update failed - red exclamation mark

I have 2.13.401.3 and received OTA update 2.26.401.3.

I tried to update but upon phone restart the progress bar stops and the screen shows a phone with a big red exclamation mark.

My phone is rooted with bootloader unlocked via HTCDEV.

Help! :)
[HTC Wildfire S] Gloris:
are you sure you followed the downgrade tutorial? i.e. you should have flashed the bl-tool and chosen supervision....this should letb you run any ruu, regardless of which version you are currently on?

---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------

ok, good news....you don't have to go thriugh all this manual update procedure if your phone is already finding the update :)

bad news....it's not workign for you at the moment?

have you modified any system files? i.e. with titanium bakcup or link2sd, move system apps, delete system apps, or move or modify any system or dalvik files?

also, in order top do it ota, i think you need to have stock recovery and be bl-relocked or bl-locked?

re-read through the thread for more info?
[HTC Wildfire S] Zlobizlob:
My HTC WFS before update:

2.13.401.3, unlocked, root

This working for me:

1) Lock botloader with this tool link credit to theq86

2) Download shiped rom from this site: lnk

for me:

Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed_ROM.zip

3) Rename to PG76IMG.IMG and put to root SD Card

4) Remove baterry and start with power + volume down

5) Installed via hboot.

6) Reboot, you have stock rom now

7) Then check for OTA updates and install OTA updates.

8) Remove PG76IMG.IMG from SD Card

9) Need this files in pc- fastboot.exe, adb.exe, AdbWinApi.dll, Unlock_code.bin (this file is from unlocking via htcdev.com)

10) Remove baterry and start with power + volume down

11) Run cmd.exe (and go to directory where you have files ready)

12) fastboot flash unlocktoken Unlock_code.bin

13) Download recovery-clockwork-5.0.2.8-marvel.img from this site: link

14) Rename to recovery.img

15) fastboot flash recovery recovery.img

16) Restart phone - you can use another procces to root your phone, this working for me

17) Download CWM, install and download in CWM su-3.0.7-test7.zip

18) Instal in CWM recovery su-3.0.7-test7.zip

19) restart

all is done :)

PS: sorry for my english...
[HTC Wildfire S] BackDaws:
Is this an official update ? i just checked my SIM Free Wildfire S and it says no update :(
[HTC Wildfire S] Gloris:
i had the same thing, for some reason my phone doesn't actually find ANY updates for stock roms....ever. Like, even if i reflash to a totally fresh install stock ruu, or even go back to android 2.3.3....it still says "your phone is up to date" or "there are no updates found" or something like that.

but other people have reported to have received this update ota, so i'm honesly not sure why, but i'm fairly certain this is an official htc update.
[HTC Wildfire S] atom_cz:
works perfectly, thx
[HTC Wildfire S] generationgav:
I'm on 2.13.401.2 stock, and the OTA isn't working at all. Only thing I did was debranded the phone via a gold card, would this cause me not to get the OTA?

If not is there any way of upgrading without wiping the phone?
[HTC Wildfire S] Lt.Win:
Its because you need to be on 2.16.401.3 . Follow the quote in the previous quote.
[HTC Wildfire S] generationgav:
Some people def claim to have got the OTA. How can I upgrade to that version without wiping? Don't think I can if no OTA found...
[HTC Wildfire S] Lt.Win:
I have no idea. I went back to stock by flashing system and boot img. Then I used the bl tool to lock my bl. I then used ruu for 2.26 and upgraded. Try that method. You need root, Though.
[HTC Wildfire S] Cap'flamme:
Be carefull, I HARDBRICKED my GF wildfire S by doing this on a 1.33 stock ROM!

No bootloader access...ARGhhh...

Just telling this in case somebody would be about to do the same mistake!
[HTC One S] Closed Source Project:
Hey guys, I was just wondering if it is possible to re arrange the sort of which our device displays images in folders in the stock gallery? I think it would only make sense if it showed the newest images first as opposed to what it is now, last. I have tried checking settings and everything, seems there is no way to change the sort order. Any one else have issues with this or know how to change it? Preferably, not by using a 3rd party gallery app. Thanks.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ger_o:
Like the Title says, today I've flashed Team Nix [rc5] and the phone boot without signal, and never come back, I've tried flashing AOKP build 35 (previous one), and the problem persists.

I have a Samsung Galaxy S i9000T.

Please HELP!..

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] nyloncrack:
Could your problem be similar as for the i9000m?

To use any i9000 ics rom, I have to use a cm7-kg3 modem and not the one that comes with a particular custom rom.

Perhaps for the i9000t, it's the same situation?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Marshy919:
Check the modem. Post what version you have.
[Galaxy S I9000 Q&A, Help & Troubleshooting] sbnaul:
Do u ve ur imei or is it changed ??? Dial *#06# in dialer and do check... if its the developer imei then u need to flash back gingerbread to get ur imei bavk...

If u ve a backup of ur efs folder even that does the job...
[Galaxy S I9000 Q&A, Help & Troubleshooting] ger_o:
Hi All, thanks for the replies.

I've found the problem, but not the solution. I have a generic IMEI on my phone that doesn't match with the one in the phone sticker.

I don't have a backup of the efs folder. I've tried several Guides, including

http://xdaforums.com/showthread.php?t=1264021&page=2

and the IMEI is not changing.

Is there any other way to solve this problem?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Lexrsk:
ICSSGS roms used to copy EFS folder to the internal SD card might be worth having a look there

If EFS folder is not in the SD card Flashing back to Gingerbread ROM may recover your IMEI if you have not already killed it by trying the fix in the link that you posted.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ts.shay:
SOmetimes, EFS is backed up automatically (sometimes!).. Anyhow, one method that worked for many people is by reverting back to GB using Odin.. Hope that helps you. And as mentioned in a previous post, try to look for an EFS folder in your SD Card. Perhaps, that could help you restore your IMEI. Good luck! ^.~
[Galaxy S I9000 Q&A, Help & Troubleshooting] ger_o:
Thanks, That was the case, I had a backup in the sd at Trash1000/files..

Thanks!!!.. The phone is back!
[General Questions and Answers] The_Wolf91:
Hi, I'm looking for a good smartphone similar to Samsung Galaxy S (I9000) but cheaper (200€ max price). What you suggest? :)
[General Questions and Answers] CuBE_:
Definitely the Nexus S.

Get it.
[General Questions and Answers] boborone:
wow, you're on the ball.

Just like the i9000, sept stock android. But, and here's the big one, he wanted under 200 euros. For that much man, idk anything.
[General Questions and Answers] thatdefault:
Sony live with Walkman or Samsung Galaxy SL.