yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] undercover:
Yeah, rmk deserves slap on the wrist for including splash lol. If you alter file, md5 will be borked. Thing is, I'm not sure what makes phone flash images, if there is a command for flashing each IMG or phone checked for present IMG files. If there is a command, then removing splash is not a good idea. If phone just checks for presence of IMG, then it should not be a problem even with mismatched md5, as long as it matched initially. I will look into it, ask people around. :)

Solution for you would be to look up for FW without splash, there are few around Development section.
[HTC Sensation] |Black|:
Thank you very much for the reply as well as for the great guide.

It worked like a charm ;). firmware flashed without problems, ROM installed so let's see what this baby can do :D

EDIT: OMG... you just gave me a heart attack :D.. since you replied with just "Yeah, RMK" I probably jumped the gun, as it thouth it would be ok.

I have just removed the splash from the zip and started in the bootloader.

I was looking at the procedure when the phone was checking the contents of the zip and after I removed the splash, it just left out the splash image item and jumped to the next.

I was lucky I suppose, everything went ok and no problems during flashing.

But I need to be careful next time.

Thanks
[HTC Sensation] mick1475:
Moving my question to a more appropriate topic.

Strangely, before doing anything else I found that I couldn't use any fastboot commands - neither in adb, nor emulator nor ACommander. Hence I didn't SuperCID.

However, I found my CID to be supported (VODAP001) - or it seemed so - with the use of a Market app. Having weighed my chances I decided to take the risk knowing there was one. I checked MD5 three times on the PC and then on the phone. I did all I knew (a very limited knowlegde, sure) to contain the risk.

Unfortunately, things didn't work out as expected. No brick, though, which is GOOD news. I got 'wrong CID' message at the adsp stage. This, I assume, means I'm stuck at the older firmware level and cannot flash newer stuff.

ADB works just fine, I reinstalled HTC Sync, before attempting firmware flash I reflashed eng Hboot to no effect.

What I'm trying to find out now is what I can do (if at all) to repair the damage done. If impossible then, well, I still have a functional phone...

The best thing I cound get is a way to SuperCID or change CID without fastboot commands if there is one (I seem to remember one posted at some stage somewhere). Or else what? Reflash stock, locked HTC and start from scratch?
[HTC Sensation] undercover:
Lol, sorry about that, hit submit button when replying and went on to edit post to finish what I was saying. :)

On a bright side, we now now that removing splash works! All credit goes to you lol.
[HTC Sensation] undercover:
Need more info. S-off or not ( i never assume, hence the question lol)

Hboot version

radio version

rom

ruu

whatever you have on your phone

what you think is relevant

what you don't think is relevant, but has 0.1% chance to be relevant ;)
[HTC Sensation] mick1475:
OK. What I get in bootloader is:

the now iconic pink 'locked'

s-off

h-boot 1.23

radio 10.11.9007.27.m3

baseband 10.43a.9007.00U_10.51.9007.27_M3

ROM RCMIX 1.2 (4.0.1ITLDeng..20111216.235139test-keys)

De-Sensed with ARHD 1.6

Recovery CWM 5.0.2.0

What I did and in what order: (having come from revolutionary 1.17 H-boot)

attempted to SuperCID over adb - got 'fastboot is not a recognised internal or external command'. Adb itself fine, rebooted to fb no problem

attempted to check my CID using adb - as above

attempted to check my CID with terminal - fastboot: not found

flashed 1.17 from ziggy's thread, all went well, but no effect on fb commands (re-did all above steps)

checked CID with Market app (CID getter), found VODAP001, assumed fine to proceed

flashed FW after all the possible orders of MD5 checks

got my 'wrong CID' message at the adsp stage

tried flashing 1.17 out of sheer desperation - 'wrong CID'.

Re-installed HTC sync, had justr the drivers before. Still no fb commands if only to get the bleeding CID with getvar CID

Seems about it...
[HTC Sensation] undercover:
Right, trying to get my head around it. How come you are on New hboot but old radio? Try reflashing whole package from op again.

Dang. One thing to try before you do anything else. Go to the folder where adb is. Hold right shift + right click mouse and choose "run command prompt" or something like that. Connect sensation. Type adb devices. Report back.
[HTC Sensation] mick1475:
Hi,

Radio is the last item to flash in the packege, mine aborted at the penultimate one. Hence old radio, new hboot. Already tried reflashing the whole thing(both 1.17 and 1.23), got my 'wrong CID'. Will check device in a moment.

/Edit: HT15BV800532 device
[HTC Sensation] undercover:
Now. Reboot your phone into fastboot and type fastboot OEM writecid 11111111 .

After that flash firmware.

I hope you understand where was your mistake. If not, ask, and I'll tell you :)
[HTC Sensation] mick1475:
My mistake, moja wina, mea culpa, sure enough. However:

how do I type the command in fastboot? I understand that it should be done under fastboot usb in adb terminal. I tried this at least 10 times, as described above. Before I tried anything I did my reading, your thread included. Might have missed something, there is a lot of posts to cover in a few threads...

If it was all it took (on my phone) I would have done it and not pested anyone with noobish questions. I am a bit of an idiot, but not that much, I hope :)

Giving it a shot, anyway. Maybe a miracle will happen and I get SCID at last. Tried this procedure before, though

No miracles. Unless there's something else I'm missing.
[HTC Sensation] undercover:
Login to #sensation-devs on webchat freenode, we need live chat :)
[HTC Sensation] mick1475:
Will do at about 10pm. that OK?

Sent from my dishwasher
[HTC Sensation] undercover:
Yup. Try to be there a bit earlier if you can.
[HTC Sensation] lehteck:
i had my sensation supercid which is 11111111.

And i download the 'Firmware from 3.12.401.2/102 RUU' from http://xdaforums.com/showthread.php?t=1412618

Put the file 'PG58IMG.zip' into the root of my sdcard and reboot the phone in bootloader mode.

After all the unzipping + updating process, and it show my phone is successfully updated and reboot the phone.

I check the more information from the baseband, my build number is still 3.06.401.101, and not the latest 3.12.

Any opinions / comments? Need to try on the arhd 6.0.X version.
[HTC Sensation] undercover:
Probably wrong pg58. Try one from any other thread.
[HTC Sensation] lehteck:
After i flash the fw, hboot is the latest version - 1.23, just the fw is still shown as 3.06.

I even try the fw from http://xdaforums.com/showthread.php?t=1432220

Same as previous, updated successfully but the fw is still shown 3.06.

MD5 no problem, everything running smooth, just no idea why the fw is still 3.06.
[HTC Sensation] TheWaulicus:
Works like a charm, very easy to follow. I would like to thank you immensely for this :D
[HTC Sensation] undercover:
That normally happens when you are not superCID. double check your cid.
[HTC Sensation] joaquinf:
After 3 days of ics trial i decided to go back to GB (coming from hboot 1.23 and ARHD 6.0.2).

Just flashed the 1.17 hboot posted here but i found that it doesn't say anything on the top of the screen ... no revolutionary, no locked neither unlocked .. the pink letters i used to have are gone.

I already installed ARHD 3.6.11 and the matching radio via fastboot commands though, and I can also read S-off so apparently nothing to be worried about (imho). Just want to share what happened to me and i wanna know if there is any consecuences because of this? Is there any partitions from the 1.23 firmware that could affect performance or stability?

I'll appreciate if any of you guys can give me some info about this :D

Thanks

Picture attached
[HTC Sensation] lehteck:
Hi,

I use the fb getvar cid, it return supercid 11111111, but when i use the app CID Getter, it will return HTC_044, so which one i need to trust? -_-....

This is the result when i use adb

C:\Users\MSS2\Desktop\adb>fastboot getvar cid

cid: 11111111

finished. total time: 0.003s
[HTC Sensation] undercover:
It's probably because of eng hboot. nothing to worry about. I would have stayed on new fw, works just fine with old ROMs but hey, its your choice.
[HTC Sensation] undercover:
Adb and fb are the ones to trust. I wonder where cid getter pulls cid from.....

Just realised you said fw said 3.06. Where? It doesn't say that anywhere. As long as nothing failed when flashing fw, and you are on latest hboot and radio.you are fine.
[HTC Sensation] lehteck:
Sorry. My Bad. Maybe i mis-understanding between fw and build number from my phone.

As i check the phone build number (setting->abt phone->sw info->more), it show it is 3.06.401.101 CL234376 release-key, so i assume my phone is running fw 3.06?

If it's different, then i might go for arhd 6.X since the update is successfully.
[HTC Sensation] undercover:
You are running older ROM based on 3.06 on newer fw. Again, as long as hboot is 1.23 and radio is the newest one you are good to go.
[HTC Sensation] lehteck:
Oh, That's the meaning.

Thanks Bro.

You help me a lot.

Thanks again!!
[HTC Sensation] dest4b:
thanks

Thanks for the guide
[HTC Sensation] nkojic:
Ok another question from me :). I have a problem in quadrant standard aplication. When i reboot the phone i have i very nice score (Pyramid3D v8.3.0 XE rom) but after some time the aplication loads very slow and the score is very bad :( . When i restart the phone the aplication is again normal. This problems acure even before i flash this new firmware. What is the problem?
[HTC Sensation] undercover:
Some app is getting stuck and takes over CPU.
[HTC Sensation] nkojic:
can i use this new radio on a pyramid rom or arhd rom who needs a different radio version (10.58.9035.00U_10.15.9035.02_2) ?
[HTC Sensation] undercover:
yes you can.
[HTC Sensation] Phil750123:
Hi,

Had trouble flashing firmware first, but resolved that,

i have installed it fine, i did have to re supercid after as it wiped it again.

installed the insertcoin 4.09 ics rom but i cant get any signal. tried re flashing the fw with no luck,

Im on radio 11.19.3504.29_2.

Any ideas?

I was going to flash a new radio but cant find any for ics??

Please ignore i fixed it -

i did 2 things at the same time so could be either -

i flashed the update to insertcoin 4.10 .

and i also removed the sim card put a new one in then put the old one back in.
[HTC Sensation] undercover:
IC 4.0.9 reception was borked ( Baad gets slap on the wrist), 4.1.0 was made to fix it :)
[HTC Sensation] cwibel:
Random reboots on 1.20 HBOOT

Hello tinky1,

I'm sorry for posting here, but unfortunatelly i can't find an answer. I'm on CoreDroid ROM and for smoother working i changed a 1.17 HBOOT on 1.20 HBOOT and it worked, but i get random reboots. I do not have OV or UV, i didn't changed antyhing except a kernels (i tried 3 different versions) I'm pretty sure that random reboots are caused by a HBOOT, because when i changed on 1.17 HBOOT reboots are gone. Can You advised me how can i get 1.20 HBOOT without a random reboots?
[HTC Sensation] undercover:
Did you flash full.firmware package or just hboot?
[HTC Sensation] cwibel:
It was just a 1.20 HBOOT
[HTC Sensation] undercover:
Flash the whole package then.
[HTC Sensation] cwibel:
What is included in a whole package?
[HTC Sensation] Skipjacks:
Do you have that modified FW file available so the rest of us can use it without taking the chance on borking up the file ourselves? Since you've got a known working file and all...

---------- Post added at 04:50 PM ---------- Previous post was at 04:43 PM ----------

Okay, I read the entire thread so forgive me if I just missed the info.

I know flashing the new FW doesn't take away S-Off.

But....do you have to redo everything else? Like installing ClockworkMod recovery, rooting, reinstalling a custom ROM, etc?

Or does all that stuff stay. Or at least does ClockworkMod Recovery stay so you can just reinstall a nandroid backup of your current ROM?

Also....in the new firmware, does anyone know if the splash screen is still at mmcblk0p14? So that my super handy dandy 1 click splash screen flashing method will still work? (Link to the aforementioned super handy dandy 1 click method)
[HTC Sensation] undercover:
Flash splash1 won't work.

Custom recovery will stay.
[HTC Sensation] Skipjacks:
Right. How about flashing splash screens fr the phone using the method above? It should work as long as the location of the splash screen isnt moved. But I have no idea if its moved.

And if cwm recovery stays I assume that flashing any custom rom restores root and su access?
[HTC Sensation] undercover:
As easy method flasher os probably just using same command just without you knowing it, it probably won't work. But you can always give it a go.

No need to reroot, as fw won't affect your current Rom installation.
[HTC Sensation] Skipjacks:
Are we talking about the same thing here?

My method of flashing splash screens doesn't use fastboot at all or any Splash flashing apps. It's done entirely through the terminal on the phone and replaces mmcblk0p14 (which is where the splash screen is stored on the phone) with whatever I feel like putting in there.

If the new firmware keeps the splash screen in mmcblk0p14, I'm sure that the flashing method will continue to work. Hell, if it stores the splash screen in some other mmcblk**** it should work fine, so long as we know what block it is.

The real question here is does the new firmware store the splash screens in the same way? Or does it completely reinvent the wheel and totally change the way it stores basic information internally?

I'd bet heavily that it doesn't do a massive overhaul of everything and that my way still works. So much so that I'm going to give it a crack and report back. (What the hell, right? I can always go back to the old firmware if I miss my splash screen that much)

Thanks for answering those other questions though! I hate starting a flash without knowing exactly what to expect.

As for this not overwriting ClockworkMod recovery, the update file contains "recovery.img". Wouldn't that overwrite Clockwork?
[HTC Sensation] undercover:
Oh, I see. I cannot answer that question for you, sorry. I do know.that 3.06 firmware moved few blocks.about, more infor in "difference between xe and non xe (or something like that)" thread in dev section.
[HTC Sensation] Skipjacks:
How can you check something like that? I mean I wouldn't want to go trying it just to see if hopefully the blocks were the same.

Also, what about the recovery? You said that the firmware doesn't replace the clockwork recovery, but the zip file contains "recovery.img". Is that a replacement recovery? Or do you just boot into the ROM after that and flash the Clockwork recovery back using the app?
[HTC Sensation] undercover:
Rmk included cwm recovery for some reason. I installed touchcovery right away. You can use any other firmware package which doesn't replace recovery if you want, but I can only recommend what I have used and tested. Let's say its my personal policy LOL .
[Viewsonic ViewPad 7 & Variants] darthstrider:
Good day! just like to ask how can i fix the multi-touch screen on my viewpad 7 after ROM change. the unit was just given to me by my cousin with issues already (multi-touch screen problem) unfortunately, default rom were not saved. please help me. Thank you!
[Viewsonic ViewPad 7 & Variants] Letitride:
Can you be more specific about your screen problem(s) - i.e. not responding at all? What rom is it running now? Identifying info from the label on the back of the device?
[Viewsonic ViewPad 7 & Variants] darthstrider:
MY CW Recovery v2.5.1.2

i'm currently using TJ style by downloading update 2.2.2 boot.zip and update_tj.zip to my SD

only the screen nearer to the navi keys are working. i have to put two fingers if i have to select icons (by chance)

my procedure:

1. i format/ partition my SD card (1024-0M)

2. i copied update 2.2.2 boot.zip and update_tj.zip to my SD

3. i use CW recovery and choose "install zip from SD" first update_tj.zip and immediately update 2.2.2 boot zip before i reboot

after rebooting, i cannot use multi-touch screen.

the vpad7 was just given to me by my cousin having problem with no touch sensitivity at all. worst, he did not backup the original ROM. i even try amalgation euviepad7 1.7b.zip but still no response. please help thanks in advance! i'm a newbie in configuring this device so if you can help me in step by step procedure would be a big help. thanks and happy new year to everybody!
[Viewsonic ViewPad 7 & Variants] darthstrider:
my viewpad 7

model no VS13761

2011-04-06

FTM

SWVER=3.620

MODEL: FM6-001

HWVER: 106
[Viewsonic ViewPad 7 & Variants] almartin:
I've flashed euviepad7 1.7 and the touch screen failed to function too. Then I've flashed euviepad7 1.7 ITE and the problem was solved.
[Viewsonic ViewPad 7 & Variants] Alleycatzero:
darthstrider i got the same problem i dont think it got anything to do with software because it worked fine with stock or custom rom`s i send my viewpad in for repair waiting for it to return

Well just got it back 30 min ago.it works i think it`s a otherone only its got a red dot in the screen now gonna contact viewsonic again that dot wasnt there bevoure
[Viewsonic ViewPad 7 & Variants] Alleycatzero:
Well just got it back 30 min ago.it works i think it`s a other one only its got a red dot in the screen now gonna contact viewsonic again that dot wasnt there bevoure no response on the ite drivers
[Viewsonic ViewPad 7 & Variants] darthstrider:
i even used euviewpad 1.7b ITE and it works fine after a few hours then went back with the same problem after i accidentally left it in my bag and had scanned in a bag check. then after that, i cannot restore it again... maybe i missed one of the procedure specially the flashing or the the oneclick root. can you just give me detailed step by step procedure? thanks! Sadly i don't think we have a viewsonic service center here in the philippines specifically for viewpad 7. I'll try to re-install euviewpad7. thank you very much everybody and happy new year!
[Viewsonic ViewPad 7 & Variants] Letitride:
Happy New Year of 2012, just realized that for many in Asia - it has arrived.

Ok, back on topic - it sounded like the problems isn't a software/firmware and/or ITE or non-ITE issue, but rather, just a defective display that need to be exchanged/repaired at VS's authorized service center. The newest EU v1.7 ROMS is very smooth with a choice of both ITE and non-ITE ("older") kernel and virtually free of any issues, been running mine on it for past 3 months with A2SD running, everything just worked (except for Adobe Flash 10.x of course.)

As a last resort, use the earlier posted thread's link to download the utility & stock/oem firmware to restore/reflash it - and if that still doesn't work, the choice is (unfortunately) to send it back for a warranty claim based on your region's prcoedures.
[Viewsonic ViewPad 7 & Variants] darthstrider:
thanks a lot sir! i will send my unit back for repair today. yup! i guess it has defective screen. thanks a lot sir and happy new year to all!!!
[Samsung Galaxy Nexus] wallendiaz:
Hi guys I would like to know how to install an Factory image to my nexus and the other is my phone is Android 4.0.1 (ITL41F) I wonder if I can install the Android Factory Images 4.0.2 (ICL53F) without problems or it would cause me some problem??

Thanks
[Samsung Galaxy Nexus] spences10:
Get the factory images here

http://code.google.com/android/nexus/images.html

Extract everything out into a folder then there's a script in there with them that has all the fastboot commands in there to flash the images
[Samsung Galaxy Nexus] wallendiaz:
ok i know that.... but, ma phone is Android 4.0.1 (ITL41F) I wonder if I can install the Android Factory Images 4.0.2 (ICL53F) without problems or it would cause me some problem??
[Samsung Galaxy Nexus] cheetah2k:
Is your phone a "Pure" google YAKJU or is it a carrier release? Have you checked it with GN Checker from the Android Market??

If its a Carrier release, you'll have to wait for the carrier to throw you the 4.0.2 line

If its a pure YAKJU, then just download the TGZ file, unzip it using 7-zip, and follow the Fastboot commands within the script file.

I've installed 4.0.2 manually on my GN (got sick of waiting) and I'm finding it simply brilliant (certainly much quicker too)
[Samsung Galaxy Nexus] wallendiaz:
Ma phone is yakjuzs I think I can not install it, right??
[Samsung Galaxy Nexus] spences10:
Bummer, I checked my build.prop file to see which build I had
[Samsung Galaxy S (4G Model)] payazo915:
I flashed the vahalla black edition rom to my Sgs4g last night and found the mms.apk was missing. This is the steps i took to get mms back on the phone.

I extracted the mms.apk from vahalla final edition. placed it on the root of my sd card then with adb followed these commands.

adb shell busybox mount -o rw,remount /dev/block/stl9 /system

adb shell busybox cp /sdcard/mms.apk /system/app/

adb shell reboot

Once the phone rebooted, the mms app was back on my sgs4g. I would have posted this in the development thread but since I am a new user on the forums, I'm unable to. Hope this helps out!
[Samsung Galaxy S (4G Model)] bhundven:
This may help, too:

http://xdaforums.com/showpost.php?p=20740424&postcount=209
[Samsung Galaxy S (4G Model)] payazo915:
Thanks. I was going nuts last night trying to get mms back on my sgs4g. Then i came across these commands and tried it...and it worked. Good looking out
[Samsung Galaxy S (4G Model)] tehgyb:
This had been an issue with the original transparent mms I created, which ravers Is loosely based on, for a while now. From everything I can tell its a conflict of the mms app and touch wiz. Try refreshing your launcher, or try out some others.
[Samsung Galaxy S (4G Model)] Jrico2:
Same Edition, i hade a problem with bluetooth not turning on.

Have you had that problem?
[Samsung Galaxy S (4G Model)] bhundven:
You should be asking this question in another thread or in raver's thread for this rom... but... Just enable bluetooth and reboot.
[Samsung Galaxy S (4G Model)] Jrico2:
There is no "raver's" in the first 5 pages of Q&A, and I dont's have enough posts to ask in Rom thread........ yet......

Well, maybe now...... nope, still not, lol.

Thanks for the tip, worked great.

+1
[Samsung Galaxy S (4G Model)] bhundven:
Ah, yea. I was talking about the valhalla black-edition thread in the dev forum.

No problem. Actually, RaverX3X showed me that one. Im sure Ive fixed bluetooth this way before on accident. Good tip!

I think the issue has something to do with the mount issue I noted in the thread I previously mentioned.
[T-Mobile Samsung Galaxy S II SGH-T989] alchrisr01:
I am on 2.3.6 and used the latest root method (odin), installed SU3.0.7 and everything was great! Bought TiPro and froze the wifi apps and tried to tether and browser went to the TMO gotcha site. I thought I must have missed something so I tried to go back into TI and it says that I am not rooted! Rebooted into recovery and flashed recovery.tar again just to make sure, successful. Open TI again, no root. Open Super manager, go to "enable root" SU grants permission. Any Ideas? I just wanted to get wifi sharing working, nothing more really. Apologies if this is posted elsewhere, I could not find it.

chris
[T-Mobile Samsung Galaxy S II SGH-T989] alchrisr01:
bump....anybody got a clue on this? I really miss the tether I had on my TP2
[T-Mobile Samsung Galaxy S II SGH-T989] _eroz:
are you on a custom rom? Have you tried going into recovery and wiping cache, wiping davlik and fixing permissions?
[T-Mobile Samsung Galaxy S II SGH-T989] audi_on_u:
Did you freeze wifi tether I beloved its called..also T-Mobile account manager...I froze both while running into same issue. Had to clear cache, data and fix permissions and did trick. Just make sure to freeze those two apps....hope it helps