yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] taylorinnov:
I have already ruled out SD Card problems through the use of multiple cards and verifying MD5 sums of the file on the card itself, not just the downloaded file on my C Drive. I just now tried another SD Card just in case. No change.

I followed the SD Card Fix instructions. RA Recovery is now able to mount the SD Card. However, upon attempting to flash the zip file, I receive this (line-by-line accurate):

Build : RA-supersonic-v2.3 - HAUS MOD rev.A

Install : 5.07.651.1_Supersonic_Stock_Rooted_CPT

B.zip ?

Press Power to confirm,

any other key to abort.

Install from sdcard...

Finding update package...

Opening update package...

Installing update...

assert failed: write_raw_image("/tmp/boot.img",

"boot")

E:Error in /sdcard/5.07.651.1_Supersonic_Stock_Rooted_CPTB.zip

(Status 7)

Installation aborted.
[EVO 4G Q&A, Help & Troubleshooting] Captain_Throwback:
That sounds like a bad download. Did you verify the md5?

If not that, it almost seems like you might have bad blocks on the boot partition, which there might not be much we can do about.

Maybe try downloading an older ROM (2.3.3 or previous) that has a smaller boot.img, and see how that works. It's also possible that your misc partition got messed up somewhere along in this process, so once you can get a ROM flashed, we should probably flash that back to the ENG version.

But if you can confirm you got a good download of my ROM, try instead flashing MikG v3.11. That's a good one to use because of the Wireless ADB, just in case there are USB issues when we get the ROM on there. That one is updated to Android 2.3.5, so it might not work. If I have to find you an older one, I will.
[EVO 4G Q&A, Help & Troubleshooting] taylorinnov:
I pulled the SD Card and connected it to my computer. MD5 sum of the file on the SD card checks out.

I tried to flash this file:

MikG-v3.11-signed.zip

Same error as before. I took your suggestion and tried to flash the same firmware that had worked before:

update-cm-6.1.2-Supersonic-signed.zip

It worked... At least it wrote without any errors.

Upon rebooting, the white HTC screen comes up but after about 15 seconds the screen goes black and the phone vibrates 5 times. Then the green light starts flashing.

Ok... So I checked the boot.img file sizes. All the files that failed had sizes over 2.4MB. All the ones that worked were smaller. So I thought CM7.2 should work. I tried flashing it and this happened:

assert failed: write_raw_image("/tmp/boot.img",

"boot")

E:Error in /sdcard/cm-7.2.0-supersonic.zip

(Status 7)

E:Can't finish MISC:

(No space left on device)

That last error repeats every 5 seconds or so as long as I remain in RA Recovery.

Couldn't find MISC partition listed under the wipe menu, so I did a wipe all and a wipe /BOOT. This made no difference.... Except...

After rebooting, this is my new HBOOT status:

*** LOCKED (OOW) ***

SUPERSONIC EVT3 SHIP S-OFF

HBOOT-2.18.0001

MICROP-041f

TOUCH PANEL-ATMEL224-16ab

RADIO-2.15.00.12.19

DEC 21 2011,12:50:32

So I tried flashing one more time. No change. I rebooted again and guess what? My HBOOT status changed to S-ON!!

*** LOCKED (OOW) ***

SUPERSONIC EVT3 SHIP S-ON

HBOOT-2.18.0001

MICROP-041f

TOUCH PANEL-ATMEL224-16ab

RADIO-2.15.00.12.19

DEC 21 2011,12:50:32

Obviously I need to unlock it again... I apparently have discovered how to get an Evo back to factory locked status... By accident. Besides that, what should I do next?
[EVO 4G Q&A, Help & Troubleshooting] Captain_Throwback:
Your problem is definitely your misc partition. It got messed up somehow, and is causing your bootloader to falsely report your NAND security status.

When you get it unlocked again, we'll need to update the misc partition through recovery.

EDIT: What you'll need to do is download the flash_image binary & mtd-end.img from this post, and follow the instructions there under "STEP 2~FLASHING MTD PARTITION TO ENABLE DOWNGRADE:" In recovery, in the "Mounts" section, you'll have to mount /data and /sdcard (/system couldn't hurt either). Then you can connect to your computer and run those commands from wherever you have adb.

Hopefully once that is done, your partitions should be normalized and the bootloader should read everything correctly.
[EVO 4G Q&A, Help & Troubleshooting] taylorinnov:
It took 3 tries to get HBOOT to accept the unlock code. Finally got the HBOOT unlocked.

HBOOT now reads:

*** UNLOCKED ***

SUPERSONIC EVT3 SHIP S-ON

HBOOT-2.18.0001

MICROP-041f

TOUCH PANEL-ATMEL224-16ab

RADIO-2.15.00.12.19

DEC 21 2011,12:50:32

SD Card access was broken again. Same procedure as before fixed it though.

Entered RA Recovery.

Mounted /system, /data, and /sdcard successfully.

Attched USB cable.

Attempted first command and received the following error:

C:\Android>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device not found
[EVO 4G Q&A, Help & Troubleshooting] ruben1221:
Well if u think u wouldn't have any problems try going to the htcdev website and root it that way. Correct me if I'm wrong but try that. Best of luck to you.
[EVO 4G Q&A, Help & Troubleshooting] NxNW:
Um, ok HBOOT is unlocked, but now you are S-ON? Seems like that will definitely be an obstacle...
[EVO 4G Q&A, Help & Troubleshooting] Captain_Throwback:
You're going to have to reflash a ROM on there first. You need a ROM that has wireless adb capability, but it has to be one with a smaller boot.img, i.e. Android 2.3.3 or older. I'll see what I can find. We're going to gave to get the phone to boot up to proceed, at this point.

I'll see what I can find.

EDIT: See if MikG v3.00 will work. Make sure you fully wipe in recovery before flashing (everything except SD card). If you can get it booted up, then we definitely have a chance.
[EVO 4G Q&A, Help & Troubleshooting] taylorinnov:
Well, after attempting many versions of MikG's I came to realize that the main problem there is that his ROMs mess around with the MISC partition somehow. After unlocking the phone 3 more times, I tried CyanogenMod 7.0.... No dice.

Finally got CyanoGenMod 6.12 loaded and booted successfully. I confirmed USB Debugging is enabled. Also, it appears that the phone has lost its wireless and bluetooth MAC addresses.

I did a little recon for my own curiosity:

cat /proc/mtd

dev: size erasesize name

mtd0: 00c00000 00020000 "wimax"

mtd1: 000a0000 00020000 "misc"

mtd2: 00480000 00020000 "recovery"

mtd3: 00300000 00020000 "boot"

mtd4: 15e00000 00020000 "system"

mtd5: 0a000000 00020000 "cache"

mtd6: 1aba0000 00020000 "userdata"

Looks like the old partition scheme.

I successfully overwrote the MISC partition using ADB and mtd-eng.img as instructed and rebooted. Here is the HBOOT status immediately after the procedure:

*** LOCKED (OOW) ***

SUPERSONIC EVT3 SHIP S-OFF

HBOOT-2.18.0001

MICROP-041f

TOUCH PANEL-ATMEL224-16ab

RADIO-2.15.00.12.19

DEC 21 2011,12:50:32

Unlock and try to flash? Or is there something else we should do since 6.1.2 seems to be fully functional?
[EVO 4G Q&A, Help & Troubleshooting] Captain_Throwback:
No need to unlock now - you're S-OFF.

Mik's ROMs don't do anything to the misc partition. There was an issue with your device (possibly NV corruption). At this point, I would downgrade to the 4.54 Gingerbread ROM, and re-root with Revolutionary. If I'm right, everything should work fine after that.
[EVO 4G Q&A, Help & Troubleshooting] taylorinnov:
What procedure should I use for that? I would usually search for something, but I don't want to leave anything to chance here.

EDIT: Spelling errors corrected.
[EVO 4G Q&A, Help & Troubleshooting] Captain_Throwback:
First, check and see if you have wireless & bluetooth addresses now. If you do, then I think we're safe to proceed. Flashing the mtd-eng file should normalize the misc and other partitions so that they're recognized correctly by the bootloader (thus why your device now shows S-OFF, as it technically always was).

I think unrooting, and then re-rooting via Revolutionary should prevent this from happening in the future (this is speculation, but it has some basis in fact). from the "How to unroot Revolutionary" link in my signature, download the 2.15.00.11.19 recovery-flashable radio, unrevoked s-on zip, and the PC36IMG file for the 4.54 Gingerbread update (rename that to PC36IMG, place on the root of the SD card).

First, flash the radio zip in recovery (you'll need to reboot the device once to complete this process - make sure you don't pull the battery during this process!). Once it drops you back into recovery, you can flash the S-ON zip. When complete, power off, and then hold volume down while powering back on to get to the bootloader. The PC36IMG should should, and choose yes to update. The device will reboot once during the process after the bootloader downgrades, and the digital watermark should be gone. The update should continue after it re-reads the zip, and finish flashing. If it doesn't, post back and let us know. When complete, choose "Yes" to reboot. You should be back to stock. Confirm everything works, and then you can follow the procedure at revolutionary.io to unlock/root the device (if you're so inclined).
[EVO 4G Q&A, Help & Troubleshooting] taylorinnov:
The WiFi MAC is there, but the Bluetooth MAC is 0'ed out (only the manufacturer component is present):

43:29:B0:00:00:00

Just to confirm, I have downloaded these files:

CM-EVO_Radio-2.15.00.12.19-Only

PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_ 2.15.00.0808_NV_2.15_release_220182_signed

(Radio in that last one is older than first?)

And I didn't see any reference to S-ON in your signature, so I don't have that file yet.
[Xperia Arc Themes and Apps] popthosegaskets:
I'm currently in need of an original framework-res.apk for ICS 4.0.4 as I will be decompiling system apks from ICS 4.0.4 . My Arc S is currently on 4.0.3, so I do not have 4.0.4 framework-res.apk :(
[Xperia Arc Themes and Apps] popthosegaskets:
Thanks

Thanks Bro :D
[Desire HD Q&A, Help & Troubleshooting] Rencx:
I would like to do some small research about things what influence vibration on phone boot.

I haven't noticed it before, but my DHD vibrate 2 times on splash screen (just before bootanimation). And no more until complete boot.

This idea was in my head just to make sure everything is ok with my DHD boot. So please can you turn off your DHD completly ( uncheck Power - Fast boot and then power off your phone or remove battery :p ).

Then report here how much times your DHD vibrate on splash screen and until complete boot.

Maybe ROM make difference, so report also what ROM you are using.

If this helps you please say thanks! :good:
[Desire HD Q&A, Help & Troubleshooting] GuyInTheCorner:
Using BlaxkICE v 1.60

One long vibrate at the HTC logo and one short one before booting into the ROM
[Desire HD Q&A, Help & Troubleshooting] Muikkuman:
I get one short vibration before HTC logo and and one short before room boots up.

Rom info in my signature.
[Desire HD Q&A, Help & Troubleshooting] Rencx:
I have flashed more than 10 ROMs an now it looks like it realy depends on ROM.

Why this realy is happening?

Can we edit how much times phone will vibrate?

Sent from my Desire HD
[Galaxy S III Q&A, Help & Troubleshooting] silvervirtual:
Hi there guys ... my SGS III has a weird thing happening the phone icon has a 1 on it as though there was a missed call but in fact there was none and I can't get rid of it.

Any ideas?
[Galaxy S III Q&A, Help & Troubleshooting] KeanuC:
Have you tried rebooting the phone? If so, but you could take a more advanced step by booting into recovery and clearing the cache.
[Samsung Epic 4G Touch] Thumper333:
I followed the instructions by sfhub (BIG THANKS) to install SPH-D710.FE16_CL579416 (FE16 Modem/Kernel/ROM - Full Restore - Rooted) on my Epic 4G Touch and it works great. The problem I'm having is with CWM-Rouge blocking some apps from being installed (at least I think CWM is the cause).Without CMW all apps install but with CWM some give me an error msg saying that the app could not be installed to sd card. Is there something I need to tweak or am I using the wrong version of CWM?
[Galaxy S III General] kantk20111:
Sorry folks, I promise that this will be the last post!

The S3 comes with a nifty feature to adjust the saturation levels of the colors. Just go to Settings-Display-Screen Mode to choose which one you like best.

After experimenting with all four for a while, I settled with natural. Standard looked great on the homescreen and most apps but for games like Temple run, it was way too oversaturated. I found natural struck a good balance between saturation and 'normalness'.

I was just interested in what others use most of the time :).
[Galaxy S III General] okpc:
Dynamic for me...
[Galaxy S III General] muhamet:
Dynamic
[Galaxy S III General] Tachikoma_kun:
Dynamic, but that's because I am red/green colourblind, so I find the extra saturation helps.
[Galaxy S III General] Drunkenmazter:
Switching between natural and movie at the moment

Sendt fra min GT-I9300 med Tapatalk2
[Galaxy S III General] xqwiza:
Natural. The other modes are to saturated.
[Galaxy S III General] adz63:
standard for me .. looks better than the others
[Galaxy S III General] nascar24usa:
International Version?

Not on an AT&T version? At least, I can't locate it.
[Galaxy S III General] qhinton:
Sprint either
[Galaxy S III General] daraj:
This feature is absent on all US variants.
[Galaxy S III General] Deusdies:
Natural. Like someone said, I never realized how much more saturated the other modes are.
[Galaxy S III General] kantk20111:
Weird it's not on the US versions. Also I'm surprised that a lot of people like dynamic. It's so saturated. Each to their own, i guess..
[Galaxy S III General] nory82688:
I would use dynamic, but I have the Tmo US version, and for some reason Samsung or out carriers felt the need to leave this awesome setting out.... hopefully a dev can implement it into a rom or something , I hope.
[Galaxy S III General] Baldilocks:
I use Standard. (And there are a lot of missing options on the U.S. versions.)
[Galaxy S III General] moustic_moustic:
Natural here
[Galaxy S III General] As2O:
dynamic is the way to go :)
[Galaxy S III General] the2rrell:
Have to say Natural is perfect.....the others are just to saturated. love the vividness dynamic, and do use it when watching movies. but natural is my go to screen setting.

That sucks the US version does not have this option....plus one for us International users....:good:
[Galaxy S III General] Franc38:
My thoughts exactly...

At startup for a few seconds I get the "standard mode" before natural kicks in, and really that's way too saturated.

Natural does respect much better the actual colours. Except for the pics taken with the S3 camera... It may be that there is some kind of compensation that is taken into account for the "starndard mode"?
[Galaxy S III General] Wootever:
I like the Standard mode (international version)
[Galaxy S III General] NaimC:
Natural is the best and closest to accurate imo. Movie is great (especially on whites) but just lacking on certain colours and depth. The others are far too saturated.
[Galaxy S III General] laneyofdeath:
Standard. (Standard) :-)
[Galaxy S III General] hefonthefjords:
I swtch betwee standard and dynamic. Mostly standard though.
[Galaxy S III General] sydios:
i use Standard
[Galaxy S III General] nickpraeger:
does it affect battery life

just wondering if the screen mode choice would affect battery life. certainly looks like natural/movie would use less. i stick with natural as colours look more natural (naturally)
[Galaxy S III General] quattro_rs:
Natural but i would prefer something in between natural and standard .
[Galaxy S III General] Alphadan:
Kinda funny to see some guys complaining about how overly saturated colours are... Well guess what, SAMOLED has 130% of the colour gamut, oversaturation is an intrinsic feature.
[Galaxy S III General] alias_neo:
I use Movie, the others are far too saturated. The colours do look pretty though when it first boots up, before the setting takes affect.
[Galaxy S III General] badassballer:
I keep switching between the natural and the standard mode -
[Galaxy S III General] drumhitz:
support dynamic to the max.. it makes the screen look vivid
[Galaxy S III General] Rydder:
I also use the natural screen. It's the one that goes "easiest on the eyes", imo. :)
[Galaxy S III General] armiinco4:
standard, and dynamic sometimes
[Galaxy S III General] AndroidDan:
Natural sometime dynamic.. Depends on what mood I'm in xD
[Galaxy S III General] schwarma:
Standard for me. The others look over-saturated or dull.
[Galaxy S III General] donalgodon:
I have to agree with one of the previous posters. I am also very surprised by how many people like the overly blown-out colors of Dynamic mode. No accounting for taste, as they say.
[Galaxy S III General] TheCraig:
I use dynamic, who doesn't like vivid colours?
[Galaxy S III General] m0cha5hake:
Standard with UI. Dynamic is vivid but some colors (especially greens) are too over saturated
[Galaxy S III General] rockler:
Standard mode suits me :good:
[Galaxy S III General] ballmead:
Standard for me.

The others are too saturated or washed out.

Sent from my SG3
[Galaxy S III General] jnr21:
+1
[Galaxy S III General] jinosong:
After using MOVIE mode, STANDARD and DYNAMIC look ridiculous.
[Galaxy S III General] Saiba:
Using standard. Seriously, dynamic is absolutely not enjoyable...

Natural is fine, but it looks a little bit too undynamic.
[Galaxy S III General] avercros:
Natural.

I don't like dynamic.

Sent from my rooted quadcore-microwave.
[Galaxy S III General] TheCraig:
I'm like wtf is wrong with everyone with using movie mode, tomorrow I will use my Galaxy s3 the entire day on Natural, and see if I prefer it to dynamic, People have different tastes :P
[Galaxy S III General] thisisuzair:
Dynamic works for me
[Galaxy S I9000 Q&A, Help & Troubleshooting] Dan-D:
I am currently on stock 2.3.6 XWJW5 gamerzrom v11 and i want to flash this http://xdaforums.com/showthread.php?t=1189676

and this http://xdaforums.com/showthread.php?t=1687727

How can I flash this rom??

Juz flash from CWM??
[Galaxy S I9000 Q&A, Help & Troubleshooting] 5aaled:
hello mate,

First of all from odin

1-you have to flash any full GB stock rom with repartition select

2- root it using Cf root kernal or semaphore

3- download any of rom u want to internal sd card

4- from CWM flash the rom u want
[Desire HD Q&A, Help & Troubleshooting] paulzerounu:
Phone was off for a while and now when i try to switch it on it just vibrates like 5 times and no screen light ...any ideas :) ?:fingers-crossed:
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Maybe the battery Is bad. Try to turn it ON plugged to electricity
[Desire HD Q&A, Help & Troubleshooting] paulzerounu:
i did try that but nothing still vibrates and that is it ...:crying:
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Have u installed a froyo RUU? or flashed anything at all?
[Desire HD Q&A, Help & Troubleshooting] Teichopsia:
Give more details. Are you stock, custom rom, what rom were you using, did you do anything before that happened besides the phone being off? The more the better.

Sent from a dream.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sundaemcdick:
im using S2 HD LTE (shv-e120s)

i manage to return my phone back from ics to gingerbread. but after the flashing from odin. everythings fine, except that i cannot open the phone dial and message inbox and send sms. and some errors pops up. i just flash only one file, the tar.md5. do i just need to wipe data and cache in recovery mode to solve my problem? or do i need to reflash it together with the complete phone and csc files?

btw, i flashed in the PDA: Home_e120s_fb13.....lowship_tar.md5

somebody said here that the PHONE and CSC are included. because i cannot find those individual files that matches my phone on the net..

please somebody help me..t.i.a
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] hugovince:
Somehow my tab bent (the screen was bent and there were small cracks by the charging port and the headphone port) and i cant bend it back. Im not sure how this happened, but in 2 weeks it will be the end of my one year warranty. Is this covered and if not, is there any way to work around it and have them fix it for me?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] raymond513:
This might not be of much help, but Samsung customer service seems pretty lenient with their warranties so I bet if it doesn't look like you just dropped your tab and you describe your problem, you can get it fixed. Also, btw if you register your tab you get 3 extra months of warranty (even without receipt),you have until august at the earliest for your tab's warranty.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] hugovince:
Thanks for your help. I actually might have lost the reciept so can you tell me how to register it
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] raymond513:
You don't need the receipt, all Tabs are at least under warranty until the end of I June, or the end of August if you register. You'll see a link to register under the support tab on the Samsung website and then it will walk you through step by step. Once you've registered try calling about your problem.
[Galaxy S III Q&A, Help & Troubleshooting] silvervirtual:
You guys have any issues with this?

Mine does not seem to work no matter how I stare at the screen :)

Is there something I am missing?
[Galaxy S III Q&A, Help & Troubleshooting] daisun:
Smart Stay only looks for your face and eyes when the screen is about to time out. If you set the screen timeout to be very low (15s), you'll see the eye icon in the status bar just before it dims your screen. If it detects your face and eyes the screen will stay on, if not, the screen will turn off.
[Galaxy S III Q&A, Help & Troubleshooting] silvervirtual:
I guess it doesn't know who its master is.
[Galaxy S III Q&A, Help & Troubleshooting] daisun:
Well I guess it doesn't make sense to keep the front camera on all the time. If you want the phone to 'know you' you can try Face Unlock. It works extremely well.
[Galaxy S III Q&A, Help & Troubleshooting] BrokenPixel:
Did you turn it on on settings?

I was doing the same until I realized it was OFF lol. same goes for some "Motions" seems like everything is OFF.
[Galaxy S III Q&A, Help & Troubleshooting] radeonxt:
just woke up and seriously i read your name as silverurinal. hehe

now on topic, on dim situations smart stay doesn't work as good as advertised.

i'm guessing it's not using the light sensors for detection but the front cam.

i have tested it, if i seem to notice smart stay doesn't work well then i open the front camera and see if my face can be seen or it's dimmed, if the face is dimmed then that's the time smart stay doesn't work like it should.

the way smart stay works, is every 5 seconds it activates

if it detects you're still looking at the phone then it won't dim.

if it detects you're not looking at the phone then it will just dim the display not turn it off. then it activates the next 5 seconds and if you are still not looking at the phone then it will turn off the display.
[Galaxy S III Q&A, Help & Troubleshooting] UpInTheAir:
No, smart stay is only active just before the screen off timeout.

You will notice the 'eye' on to the status bar, and only when it is active.
[Galaxy S III Q&A, Help & Troubleshooting] nodstuff:
Bingo ^^

Dunno what the other lad was on about with his every 5 seconds! :D