yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] thedan55:
for gods sake im sorry about this but im still getting errors!!!!!!

the ruu gets through a few steps but then stops with the error "bootloader version error"

this is the ruu im currently trying to use

RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed

RUU_Marvel_HTC_WWE_Tesco_1.37.1107.2_R3_Radio_47.10.35.3029H_7.46.35.08_release_196384_signed

neither of these work!!
[HTC Wildfire S] thedan55:
"checking mid/cid" thats where it crashes for some reason??

customer id error....

that means im using thr wrong ruu right? but ive tried 7 now

http://i.imgur.com/1MGcavQ.png this is what it says before i click update, i cant seem to find any ruu's that have a 1400 in it
[HTC Wildfire S] MiCeltic:
I was at an HOA meeting ::sheesh:: anyway, if I understand from that pic you posted, it looks like that 1400 you mention in your current version means china...like the CID region and language is China. Look at what it says When you run that, fastboot getvar all command. What does it say are your:

version-main

MID (modelid)

cidnum

ERROR [130]: MODEL ID ERROR

ERROR [131]: CUSTOMER ID ERROR

One of these error messages will appear when you use the wrong RUU to do the update. The RUU will check if the Model ID and Language ID are compatible with the Android phone. Make sure you use the correct RUU to update.

Your going the right direction (from the picture) in that your not trying to flash a lower software version, but you might need to flash a custom ROM that is not built on china based software (RUU) and then do one of the Europe or WWE (WorldWideEnglish) stock ones.

Or flash a china ruu and select English for the language.
[HTC Wildfire S] MiCeltic:
All that being said, you might be quickly approaching the point where you're ready to bypass any double-checks or whatever that an RUU does. If you decide to try and extract the ROM or ROM files from your selected RUU and flash from hboot, this is an excellent guide with pics. It's based on an HTC Sensation, so, again, if you go this route, make appropriate adjustments, like naming the [ROM].zip correctly for the WildfireS and whatever else...even though that might be the only thing needed. One thing that might make it easier is to delete most or all of the files from your PCs temp directory (Start>>Run>>%temp%) to make it easier to find the RUU files for extracting.

http://www.htcsensationforum.com/htc-sensation-rooting/how-to-extract-rom-zip-from-ruu
[HTC Wildfire S] MiCeltic:
I was thinking about deleting that last post from earlier today because it's just an alternate method if the RUU can't find your phone from Windows or something. So far you have not gotten dumb errors...they're all giving more information and seem appropriate to finding the

right RUU

. So, I'll leave that earlier post just for reference.
[HTC Wildfire S] thedan55:
thanks for all that. so if i pick the tsco ruu and manually flash it, wont that brick the device if its the wrong file?

this is the contents of getvar

:\nexus 7>fastboot getvar all

bootloader) version: 0.5

bootloader) version-bootloader: 1.09.0099

bootloader) version-baseband: 7.57.39.10M

bootloader) version-cpld: None

bootloader) version-microp: 0451

bootloader) version-main: 2.26.1107.1

bootloader) serialno: SH17LTR05799

bootloader) imei: 358701047031423

bootloader) product: marvel

bootloader) platform: HBOOT-7227

bootloader) modelid: PG7610000

bootloader) cidnum: HTC__052

bootloader) battery-status: good

bootloader) battery-voltage: 3754mV

bootloader) partition-layout: HTC

bootloader) security: on

bootloader) build-mode: SHIP

bootloader) boot-mode: FASTBOOT

bootloader) commitno-bootloader: 510e562c

bootloader) hbootpreupdate: 12

bootloader) gencheckpt: 0

ll: Done!

am i using the correct files or have i made a stupid mistake??
[HTC Wildfire S] MiCeltic:
Here's what I see:

obviously your bootloader was updated to 1.09.0099 when it was unlocked on htcdev.com.

Your radio is 7.57.39.10M

Somewhere along the way you seem to have been updated to software version 2.26.1107.1 (the latest and greatest OTA from Tesco/O2?)

Note 1107 is a WWE [as region] "HTC WWE Tesco - - 2.17.1107.1 - - PG7610000" is what would have been selected on htcdev.com when unlocking the bootloader

The MID is PG7610000 a marvel (good, see next paragraph)

The CID is HTC__052 that's HTC-Tesco (there are 8 characters there...two underscores)

That's good news because in one of your previous posts you linked to a picture of the RUU screen showing you were trying to update from software 1.20.1400.7 to whatever...That is an HTC A310E Explorer (pico), Model Id Pj03100 ROM, and as I said, the 1400 is a China region CID. I'm guessing it was the base of whatever custom ROM you had on there, but my imagination was running wild ::haha:: and the version the pic said you were updating to was 1.66.401.1 what RUU was that, or I guess it really doesn't matter...it's just confusing cause sometimes it doesn't seem to add up.

Ideally you could maybe find the right RUU on the O2 site (didn't Tesco merge with O2?) or is there still a Tesco site? An RUU with your 2.26.1107.1 version and you could flash that because an RUU won't update to a lower version software, so that is why the Tesco RUU you posted failed. I'm not sure what error it showed. I don't think it will run from the SD card either as a [ROM].zip meaning PG76IMG.zip. Ultimately you might get away with pulling the Recovery.img, Boot.img, and System.img out of the Rom.zip and flashing them from your SD card in recovery which might also solve the potential for not having the right hboot (even if you find the right RUU) since it was upgraded during unlocking the bootloader...then getting an OTA update from O2/Tesco if they're still doing them.

So I see 3 options:

1. The right RUU for your software version and CID with a possible need to downgrade the hboot or extract the Recovery.img, Boot.img, and System.img and install them from recovery. I mentioned some version of this on that first post on 12 Oct.

2. Same as #1, but with an older Tesco/O2 ROM for your device and then hope for an OTA update to the latest Android version for the phone.

3. Find a custom ROM that works.

4. There's also the option to add th HTC__052 cid into that European RUU that has software 2.26.xx-- Probably have to extract Rom.zip, then get into the, "Android-[something].txt file and add it (You can see I'm getting tired...)

So, that's all I can contribute for tonight. Let me know what you're thinking.
[HTC Wildfire S] MiCeltic:
Don't know where you're at with this, but # 3. here looks promising, might be worth a try. Totally stock and based on the latest EU 2.26.401.3 release,android version: 2.3.5 multi language support. You have the 2.26 software as you know.

http://xdaforums.com/showthread.php?t=2143410
[HTC Wildfire S] thedan55:
first of all i genuinely want to thank you for all your help and advice, you are a star!!!

ive downloaded the right RUU for tesco (via htcdev) but that tells me to use another RUU to update it to another version. so thats still not happening, when my nephew messed around with it he mustve flashed a bad file or something as none of the RUUs will work.

the reason i want to go to stock is that ive had ZERO luck with custom roms on this device, but it does look like thats the only route now....
[Galaxy S 4 Q&A, Help & Troubleshooting] palcoNe:
Hi, a friend received from his cousin, as gift a "galaxy s4" but after he asked me to take a look at it, I said him that phone is a fake one.

Now I want to ask you what can I do for him, because he doesn't want to sell it.

Can I flash the official firmware and ROM ? what about the rooting method ?

The phone is smaller than the real one, has the air gestures but they work only on the home and app screen(not in webpages, etc), is micro-sim also.

Also you can see from the pictures the result of Antutu Benchmark test and other pictures that may help you.

http://tinypic.com/r/2zoxdnm/5

http://tinypic.com/r/14brryf/5

http://tinypic.com/r/2hzl1u9/5

http://tinypic.com/r/244dy60/5

http://tinypic.com/r/212zatj/5

http://tinypic.com/r/282e5vb/5

http://tinypic.com/r/dyvl6s/5

http://tinypic.com/r/sljwx3/5

http://tinypic.com/r/2vao0w8/5

http://tinypic.com/r/2itj8th/5

http://tinypic.com/r/r2pydz/5

http://tinypic.com/r/w8p9vq/5
[Galaxy S 4 Q&A, Help & Troubleshooting] plasmastate:
Personal advice. Use it as is.
[Galaxy S 4 Q&A, Help & Troubleshooting] Skipjacks:
If its a knock off s4 you can't use ANY ROMs or mods that were designed for the s4. Its got different hardware so any s4 ROMs won't work and could brick it.

There likely aren't rooting methods available because there isn't a big developer following to create rooting methods.

The software it has now is the software the device will have forever.

Sent from your phone. You should be careful where you leave that thing.
[Galaxy S 4 Q&A, Help & Troubleshooting] MistahBungle:
Bin it. Tell the friend to slap his cousin.
[Galaxy S 4 Q&A, Help & Troubleshooting] palcoNe:
Thanks, he thinks even his cousin didn'nt knew the phone is fake.

I thought flashing other firmware would make sensors to work better.Thank you for the answers.
[Galaxy S 4 Q&A, Help & Troubleshooting] rl421403:
The IMEI number belongs to NOKIA 1661. lol :P

Why not let him use it if it's a gift. It's not like who purchased it got cheated. May be his friend knew he is buying fake one.
[Galaxy S 4 Q&A, Help & Troubleshooting] faiyo:
Wow that's the best fake product I've ever seen. Find out where he got it and beg to import a lot
[Galaxy S 4 Q&A, Help & Troubleshooting] Hazerm:
Wow antutu scores not bad for a replica if its a real score. I've seen some knock offs with modified antutu scores. But if that score is real, its actually not bad, Galaxy S3 range.
[Galaxy S 4 Q&A, Help & Troubleshooting] palcoNe:
I don't have any reason to post a fake score ;)), this is the score showed on the screen. I can't ask him where he got it, but if anyone knows more details about this replica i would be glad to listen :)
[Galaxy S 4 Q&A, Help & Troubleshooting] Skipjacks:
He means the phone is forcing a fake score, not that you photo shopped the image and changed the numbers. A phone can manipulate benchmarking scores by over performing in the tested areas briefly, without giving any real world performance boosts.

Even TouchWiz does this.

Its one of many reasons why benchmark scores are utterly pointless and meaningless.

As for the device and what to do with it...again...you won't be able to modify it without figuring out how to root it and build custom roms for it yourself. There won't be any ready to go software for it. Use it as is and enjoy. Could make a great backup phone, or spare to use when you are going somewhere a more expensive phone might get broken. (I always keep my last phone handy for when I go to the amusement park or something)

Sent from your phone. You should be careful where you leave that thing.
[Galaxy S 4 Q&A, Help & Troubleshooting] palcoNe:
Ok, but why are the sensors working only on the home screen and app screen ? I think if are there, something cand be to work properly.

I think the replica is the one presented here [YOUTUBE]http://www.youtube.com/watch?v=8x-EBIgTfnk[/YOUTUBE]
[Galaxy S 4 Q&A, Help & Troubleshooting] Skipjacks:
Because its a fake. Its not a great phone. Things don't work right on fakes. There is no way around this. No matter how much you try to convince yourself this thing is as good as a real s4 its not. Accept it and see the phone for what it is...a decent wifi device for web browsing.

Also I suggest not using any banking apps or going to bank websites on it because god only knows what the software is recording and sending to someone.
[Galaxy S 4 Q&A, Help & Troubleshooting] palcoNe:
I don't want to convince myself or anyone its a good device, only that my friend asked me to do something with it.Thank you for adivce.
[Galaxy S 4 Q&A, Help & Troubleshooting] norml:
Put it on CL as a fake/replica S4 and get rid of it.
[Galaxy S 4 Q&A, Help & Troubleshooting] deathnotice01:
Put some bacon on it. It will be glorious!

This post has been approved by the supreme potato overlord of earth.

[via Galaxia S Cuatro LTE]
[Galaxy S 4 Q&A, Help & Troubleshooting] ranger4740:
A suggestion for you, do some endurance/destruction tests on it then post your findings on you tube or other out lets.

Like

Drop test

Water submergence

Sitting on it

Put in front pocket and see if screen breaks...
[Galaxy S 4 Q&A, Help & Troubleshooting] palcoNe:
Seems there are lots of "funny" guys on xda..
[Galaxy S 4 Q&A, Help & Troubleshooting] Obagleyfreer:
This thread might help you :)

http://xdaforums.com/showthread.php?p=43003332
[Galaxy S 4 Q&A, Help & Troubleshooting] Mushoz:
How much did it cost? It looks actually really good for a fake. Decent performance numbers also!
[Galaxy S 4 Q&A, Help & Troubleshooting] palcoNe:
He doesn't know the price, it was a present. After some research it is arround 250-300$.
[T-Mobile, Samsung Galaxy SIII] stevespens:
Hi All,

I just picked up a beautiful SGSIII. It is originally on T-Mobile, I am on AT&T. The phone is unlocked and works fine. My question is, would I flash a rom for the T-Mobile version or for the AT&T version? Or would both roms be the same. I've not yet been in this situation. I've flashed all of my smart phones, just not an unlocked one on as different carrier.

Also, is the hardware internally the same between models? Do they use different parts? I know the outsides can be slightly different.

Thanks in advance. I did a qick search on this forum and didn't see anything to help me.
[T-Mobile, Samsung Galaxy SIII] Da Kine:
T-Mobile phone= ROMs meant for T-Mobile phone

You could flash T-Mobile ROMs on an at&t phone and vice versa, but you may end up with APN/data issues. STAY AWAY FROM THE INTERNATIONAL THREAD, DOWNLOAD AND FLASH ANYTHING FROM THERE WILL AND YOU WILL BRICK YOUR DEVICE.

basically the same, slightly different hardware.

Before you go crazy with flashing ROMs, look into backing up your imei.
[T-Mobile, Samsung Galaxy SIII] stevespens:
Thanks a lot, appreciate the response.
[HTC Desire X] Nidhoegger:
Hi,

today ive rootet my phone and tried to flash Shadow DX Rom. But first it didnt boot up and got hang up in boot screen (HTC boot screen). Then i looked into it and got to not beeing able to mount /cache. I can format it via Mounts & Storage menu. But cant mount. CWM gives me just "Error", mounting via adb gives me "Invalid Argument".

I dont know what to do now.

Any ideas?

Thanks!
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
Dear friends,

Please Check the mages attachments..

I am Not bale to get what the issue is with the ROm.

I have HTC ONE SPRINT a locked one.. earlier the ROM was Deleted and i flashed the other ROM : windows based and flashed via WINDOWS.

and the other picture shows the Original ROM from Sprint.

Can any one help to make visible the Mobile Network option.

Or Can u please give me the link for ORIGINAL ROM OFFICIAL ROM FROM SPRINT.

Thank you,
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
View attachment 2223807

View attachment 2223808

View attachment 2223809

View attachment 2223810
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
mobile network Sharing Visible 3/4

Problem Sorted Out..

Changed the Build.prop setting..

It worked..

In Mobile Network sharing : 3/4 features are on..

But not getting the Solution for 4/4 ...(Please Help)

one more problem i noticed is that Original Setting if seen via Terminal Emulator

TerminalEmulator>su>getprop(enter)

In Original ROM : [persist.sys.usb.config]: [adboff]

In Cusotm ROM : [persist.sys.usb.config]: [adb]

but not able to edit and make changes in getprop

Can anyone sort off the problem..

or let me know HOW TO make Changes in getprop???

Thank you,
[Sprint HTC One (M7)] skippper:
I have the same problem in my stock ROM. I have been able to enable wifi and bluetooth tethering via build.prop, but USB tethering is still missing.
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
Got success.. for bringing usb tethering visibility on....it shows usb now. ..

The trick... It's not recommend but did

RND... And got it by hook or crook...

So just go on imagining...

You need 2 HTC ONE mobiles

1. In 1st one USB is not visible

2. Original ROM HTC ONE

BOTH PHONES must BE rooted.

And install TWRP, in both phones.

Make a back-up copy of both phones...

A BACKUP WILL BE CREATED IN BOTH PHONES in folders TWRP.

Now copy the backup of 2 and paste it in one...

Remember the backup should be copied of 2 to that of 1, n only files should be copied...

Then reboot ur phone...

Then go to ur 1 phone in build.prop

Makes changes from 0 to 1 for three properties...

N reboot again...

Usb will be enabled...

But remember that phone 2 should not be with any personal data... If any, same data will be copied to 1.

Please check, try, enjoy n then reply :)
[Sprint HTC One (M7)] indy1811:
Hi,

What did you change in the build.prop file to enable mobile network sharing? Any steps or guide you followed?
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
build.prop file to enable mobile network sharing

Specially

ro.wifi.hotspotUI=0

ro.bt.tetheringUI=0

ro.usb.tetheringUI=0

ichanged the above parameters in CUSTOM ROM to

ro.wifi.hotspotUI=1

ro.bt.tetheringUI=1

ro.usb.tetheringUI=1

thats it...
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
build.prop file to enable mobile network sharing

Specially

ro.wifi.hotspotUI=0

ro.bt.tetheringUI=0

ro.usb.tetheringUI=0

ichanged the above parameters in CUSTOM ROM to

ro.wifi.hotspotUI=1

ro.bt.tetheringUI=1

ro.usb.tetheringUI=1

reboot without fail...

no usb sharing will be enabled... so please for go for the Post given above post on 18 Sept 13

thats it...
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
Now copy the backup of 2 and paste it in one...

Remember the backup should be copied of 2 to that of 1, n only files should be copied...

After above Steps..

Please Restore the Phone 1, as the backup files in Phone 1 are that of 2.. so please RESTORE
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
USB Tethering is on... u can now use USB of HTC ONE...

Hope you Met the USB Tethering VISIBILITY...
[Sprint HTC One (M7)] skippper:
So, what you actually did is to flash system partition. I think some application, responsible for usb tethering was missing in our Rom.

Отправлено из моего HTCONE с помощью Tapatalk
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
TWRP(TeamWin Recovery Project)
[Sprint HTC One (M7)] kgowrav:
How did u get wifi and bluetooth working, I tried editing build.prop but in ES file explorer i couldnt save the changes and when I used build prop editor the changes were not saving on restart. I am rooted. Can you help me out.
[Sprint HTC One (M7)] skippper:
I use Android Tuner Free application. There is a build.prop editor in it which allows to save build.prop file easily.
[Sprint HTC One (M7)] indy1811:
You must tap the tick symbol on the top right corner once you make the changes in the build.prop editor to save the changes.
[Sprint HTC One (M7)] kgowrav:
I am saving the changes, it is clearly saying that the file is saved, but on restart nada all are set back to 0.
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
Just Try one thing... HOPE IT MIGHT WORK..... :)

- Just Backup a "Copy of build.prop"

- Edit in the "Copy of buil.prop" to 1's.

- change the original name of "build.prop" to some other name(say "Original build.prop")

- now change file name of "Copy of build.prop" to "build.prop"

Try ...

ad yeah dear, SU Permissions should be Granted...

Best Luck
[Sprint HTC One (M7)] kgowrav:
Tried it earler...No luck :(
[Sprint HTC One (M7)] pm.mohanani@gmail.com:
Are you opening it in edit mode with write permission....

Please do S-Off and Perform the same operation said in OP

Thank you,
[Sprint HTC One (M7)] chap_man:
Steps performed to restore

Thanks to pm.mohanani@gmail.com for his pointers

These steps are to be performed on a Sprint HTC ON PN0720000

S-OFF, rooted, su, TWRP-ed 2.6.3,rooted.

adb shell

dd if=/system/build.prop of=/sdcard/build.prop

-------------------------------------------------------------------

shell@m7wls:/ $ dd if=/system/build.prop of=/sdcard/build.prop

dd if=/system/build.prop of=/sdcard/build.prop

15+1 records in

15+1 records out

8138 bytes transferred in 0.006 secs (1356333 bytes/sec)

shell@m7wls:/ $ exit

exit

-------------------------------------------------------------------

C:\Android>adb pull /sdcard/build.prop

124 KB/s (8138 bytes in 0.064s)

Use Hxd.exe or any hex editor to edit build.prop

FROM---------------------------------

ro.wifi.hotspotUI=0

ro.bt.tetheringUI=0

ro.usb.tetheringUI=0

TO---------------------------------

ro.wifi.hotspotUI=1

ro.bt.tetheringUI=1

ro.usb.tetheringUI=1

save file

adb push build.prop /sdcard/

-------------------------------------------------------------------

C:\Android>adb push build.prop /sdcard/

882 KB/s (8138 bytes in 0.009s)

-------------------------------------------------------------------

Reboot HTC One in recover

adb reboot recovery

In TWRP ,

Go to MOUNT

checkbox System

Go to File Manager, navigate to /system and select build.prop and rename to build.prop.orig

Got to File Manager navigate to /sdcard, select build.prop file and choose Move to /system

select /system/build.prop and select chmod 755 - if you dont do this step, the phone will be brick-ed

reboot system

Go to Settings, Tap More... and you should be able to see

Mobile Network Sharing with Mobile Hotspot and USB and Bluetooth tethering.

cheers!!!
[MDA II, XDA II, 2060 ROM Development] Oreste:
My Xda II is always charging. Even when is not plugged in.

Battery life is around 6 - 7 hrs.

First i thought that is the battery dead, but i tried with a new one.. and got the same result. He eats like 10 % in one hour.

Now I have Sin.Merged.V.2.0 but is not the soft fault.

I hared that I have do a hard reset but I don’t know how.

Anybody have an idea what to do so will not be on charge mode anymore ? :(
[MDA II, XDA II, 2060 ROM Development] Rudegar:
it's normal for a himalaya to charge up to 100% then run of the battery untill it reach a surden % and then begin charging once more
[MDA II, XDA II, 2060 ROM Development] Oreste:
Is always on charging mode. Even when is not plugged in.
[MDA II, XDA II, 2060 ROM Development] cruisin-thru:
Probably a short on the pins on base of phone. Get a magnifying glass and take close look.
[MDA II, XDA II, 2060 ROM Development] Oreste:
up

is not this .. i checked...

does anyone know ? why it shows charging and eats up my xda2 battery ?
[MDA II, XDA II, 2060 ROM Development] mesecm:
I have the same problem! My XDA II is always charging. Even when is not plugged in. And i think it needs more thime for charging.

Battery life is around 4 hours.

I also tried hard reset a couple of times. It did not work. Still charging all the time!

I NEED SOME GOOD ADVICE ABOUT THIS.

[/url]
[MDA II, XDA II, 2060 ROM Development] Oreste:
up

ME TOO !! please anyone knows something about this ? Why is always charging and eats bettery life time ?
[MDA II, XDA II, 2060 ROM Development] Olipro:
ok, so consider the possibility your battery is on the way out and you need to buy a new one, obviously if you haven't had the PDA/Battery wrong, this shouldn't be true, but nonetheless a possibiliy
[MDA II, XDA II, 2060 ROM Development] mesecm:
always charging and eats bettery life time

I found out that my qtek 2020 has some other failure than yust bad battery. I took it to the service and they try with other battery and also put on my ppc new software (upgrade) but no succes.Battery still always charging and eats bettery life time.

:?:
[MDA II, XDA II, 2060 ROM Development] Oreste:
up

yes i tried with a new battery and also made a software upgrade but still the same problem...it always says charging...

anyone knows a solution ?
[MDA II, XDA II, 2060 ROM Development] mesecm:
There is a green lite always on. Usualy it is blinking and while it is always on, it needs at least 10times more power than usualy. This is the reason why battery life is so short.

On monday i will try to diskonect the green lite and hope solve the problem with battery life.

:?: