yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
Hmmmmm. A corrupted bootloader? How odd that you would come to that conclusion because that's the only thing I could come up with myself. Only mine was a bit different and evidently more deadly a situation.

As you know I've been doing some ports for our phone lately and in the process you go thru many scenarios that just won't boot. No way back to square one without pulling the battery and going back to recovery for a different flash thru Hboot. After working thru 18 or 20 ROMs and probably a couple of hundred flash attempts over time I hit another hangup. I pulled the battery....waited about 15 seconds, reinserted it & proceed to go back to recovery for a reboot of a different setup. Hboot came back up fine like always, volume buttoned down one to recovery & hit the power button to take me there. My phone just sat there for about 10 seconds which scared me in itself because you KNOW that's only about a ONE second operation. Then she went dark as if I'd hit the "power off" selection by accident when I KNEW I didn't. I pulled the battery once again and reinserted it, volume down & power button to bring it back up .....and NOTHING.

That's when I noticed the only response I was getting was the pale red trackpad "light of death". After I quit freaking out enough, I went into System Devices in Windows to see how it was reading my phone and I had the QHSUSB_DLOAD "Screw You" device showing. Needless to say, I now have a brand new DoubleShot which I'm still kind of babying at the time like you usually do after you've killed one. That was my SECOND meltdown. My first was the CWM 6.0.0.0 series of meltdowns that struck many of us.

The only logical thing I have come up with so far is that SOMEHOW my bootloader got corrupted and that's how whatever happened.....happened. That is unless you or someone else might have a better explaination.

SO......don't throw it against the wall, my friend. At least you're still using yours.
[T-Mobile myTouch 4G Slide] demkantor:
Wow, so you've hit that red light of death twice? Were you bear s off both times? Man that's terrible luck! Did you attempt the unbrick mod at all?

I wonder if these phones have the same issue that the g2 and glacier have (as this is just a glacier with a keyboard and nice camera :) where the made faulty emmcs that would randomly corrupt and leave you with an expensive paperwieght

Just checked mine out, its a MLL0M

Which of course doesn't mean much unless there is a bunch to compare with, if you want to check what you have boot to recovery and run adb shell

cat /proc/kmsg | grep 'mmc0:0001'

Running fastboot OEM check_emmc_mid it shows its made by Samsung, who by the way was the maker of the faulty emmc thrown in those others phones....

Eh, I'm sure its nothing but strange things happens with technology, I'm just one of those who like answers!
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
Thanks for the info Demkantor. I like answers too and just as soon as I have a few extra minutes I'll check that out and give you a much more complete response. (I've always said my parents should have named me Murphy, 'cause if ANYONE can mess something up .....it's ME)! LOL
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
I get this readout for the first command string:

cat /proc/kmsg | grep 'mmc0:0001'

<6>[ 4.528226] mmcblk0: mmc0:0001 MLL00M 2.25 GiB

For the second, I get:

C:\>fastboot oem check_emmc_mid

... INFOManufacturer ID, MID=15

INFOeMMC should be Samsung

DANG! Not only do they never give us an upgrade they continued to let us use a booby-trapped phone that they know could well "go off" at any time.

Ya know, as well as this DS runs....with the support we've gotten I have no intentions of staying with HTC. Making a lesser phone but actually giving a damn would be a much better thing to say about them!
[T-Mobile myTouch 4G Slide] demkantor:
Well we got the same chip, but I wasn't saying this one is for sure prone to failure, just that Samsung made the chip that was faulty in the other phones, it was a different model number though

There's a lot of things about HTC that I just can't stand, I mean they make (or rather used to make) the phones I want and 99% of the build quality is there, but they refuse to support even their flagship phones, and then make an awesome phone like the double shot and hide it from the public.... I don't feel like going on about them right now, we all have read tons of threads with complaints about HTC

But I really am curious about why this ROM couldn't flash, and why flashing a new hboot seemed to fix it. Also why did to of your phones go bad, somewhat out of the blue? Do you still have them by chance? Want to run some tests?
[T-Mobile myTouch 4G Slide] WeekendsR2Short:
OH....I misunderstood. They may have swapped out that lot for one that wasn't borked. OR....they could still be waiting on Samsung for an "OTR UPGRADE"! LOL

Yeah, that first one bit the dust on testing CWM 6.0.0.0 where partition tables got chewed up or at least that's the conclusion we came to anyway. I swapped that one with Tmo for a new one last July. Still under factory warranty.

The one that just died I had to mail back in to ASSurion for the replacement I just got. But it WAS out of the blue even though I've been doing ALOT of flashing. Nowhere NEAR the estimated limit though. Plus it crashed from the bootloader & not from or during a flash which is how I would assume it would do if it was the emmc.
[T-Mobile myTouch 4G Slide] Jesterfell:
Hey, demkantor, thanks for the link in xmc's thread.

My hair-pulling ROM was xmc wildchild22's JellyKang. By now, it's at the point that I am no longer interested in the ROM, but I am still interested in why it would not boot with the original kernel, but WOULD boot after flashing scverhagen's kernel from YOUR 9.1 hair-pulling ROM.

I'm a relative noob, so I did not think to check logs (wouldn't know how to interpret them, anyway), or flash another hboot, but I did a lot of searching, reading, and experimenting without getting any closer to an answer.

If you read my post in the JellyKang thread, you know I wiped till I was raw, tried different recoveries, both TWRP and CWM (not CWM 6.0.0.0, thank goodness), triple checked MD5, re-downloaded the MD5 file, just in case...

None of it helped.

It looks like HBOOT may be the problem in my case too. Each phone has a different HBOOT version. I never intentionally flashed hboot on either phone. I can't really remember if that was part of the rooting process. (see HBOOT, below)

It sounds like you have some ideas. Fire away! I've been keeping both phones near me for a while. My wife got fed up with her phone "going missing" all the time, and went back to her previous phone, the G2, until, as she puts it, I "get over it."

Anyway, it feels good that I am not alone in my curiosity--many nights I would yell out "WHY?!" LOL

I show almost exactly the same thing as you on both phones:

-- BLACK model DS --

cat /proc/kmsg | grep 'mmc0:0001'

<6>[ 2.581846] mmcblk0: mmc0:0001 MLL00M 2.25 GiB

fastboot oem check_emmc_mid

...

(bootloader) Manufacturer ID, MID=15

(bootloader) eMMC should be Samsung

-- TAN model DS --

cat /proc/kmsg | grep 'mmc0:0001'

<6>[ 1.927336] mmcblk0: mmc0:0001 MLL00M 2.25 GiB

fastboot oem check_emmc_mid

...

(bootloader) Manufacturer ID, MID=15

(bootloader) eMMC should be Samsung

--- HBOOT ---

The only difference I've found between the phones, so far, are:

1. different model numbers (probably just the color)

2. different hboot -- TAN: HBOOT-1.45.0013; BLACK: HBOOT-1.44.1107

3. at the bootloader screen, the BLACK one says "Revolutionary" and the TAN one says "UNLOCKED" (I used the HTC boot unlocker on the tan one)

I'm enough of a noob that I wouldn't even have thought of comparing hboot versions if it hadn't been for demkantor's comments.

Like both of you, I keep railing against HTC to the point that even my dogs look at me funny. But, somehow, I keep buying their stuff. My son just got a Galaxy (I think it's the S2, but may be the S3--huge screen!) and it has some great stuff, but I'll stick to my doubleshot, thank you.
[T-Mobile myTouch 4G Slide] demkantor:
hmm, i think we should change them, if your willing jbear s-off is the way to go.

out of curiosity are you s-on or s-off on the .0013 phone

im under the impression there is s-on and s-off for that bootloader but the .1107 can only be s-off
[T-Mobile myTouch 4G Slide] Jesterfell:
Both are S-OFF using different methods (don't remember more, right now).

I'm, planning to flash a new hboot on the problem phone (the TAN one) to see if that's it, but I'm too sleepy to think clearly. That phone has the newer hboot, so I would think the other one should be the problem...

---------- Post added at 12:35 AM ---------- Previous post was at 12:24 AM ----------

OUCH!!!

DOUBLE OUCH!!!

And there I was, whining just cause I couldn't flash another ROM!

OT: I keep trying out the wealth of ROMs that have come our way recently (kid-in-a-candy-store syndrome), but keep going back to Black Dahlia as my DD--thanks.
[T-Mobile myTouch 4G Slide] demkantor:
wow...

so it happened to me a few weeks back, turned on my double shot and nothing.... then plugged it in thinking the battery may be dead. got the vibrations and blinking red led and constant off then on, off then on. tried a different battery charged via external charger, same. tried different pcs, different cables, different button combos, nothing...

said nuts to this and tossed it aside. tried again a week later... same event...

tried tonight after a week of sitting around with no battery, sim or sd card in, poped in battery and it works like day one.

powered of and poped in sim and sd, all is good.

tried a last_kmsg with nothing worthwhile. not sure if this device is doomed to fail, not sure the cause, its just random hardware faults really get on my nerves...

just venting yall...
[T-Mobile myTouch 4G Slide] Blue6IX:
So, my original doubleshot I got on launch ended up having a light under the keyboard die after a handful of months. Sent it back to HTC and they fixed the light, thankfully just the light and didn't mess with the memory or anything. I got it back with a working light and s-off.

Fast forward about the same amount of time again, and one night I have netflix running through the tv-out cable to the tv in the room. I wasn't paying it much mind as others were watching ... until it suddenly stopped.

Variety of batteries later that work fine in my other doubleshot to no effect. I haven't had the chance to look too far into it, but with the overclocking experiments I did with it smart money would be on a dead processor.

I ran it pretty consistently at 1.7, that's where it really did shine. As a power user directing every lick of performance I can muster into the timely execution of the tasks at hand ... the times I bumped it back down to 1.2 or 1.5 due to non-use were infrequent.

I also am the curious sort and wanted to see what it could do, really take it for a spin. I had it at some ridiculous levels of speed just to see.

It also happens to be sitting right here next to me. Well, both of them. Once I learned that development is so much easier with two target devices to work with, I at least had a 'back up'.

Now I have one working and one non, but I wouldn't try to file an insurance claim on something likely my own fault. Nevermind the fact that this very instance is what one of the big sticking points in relenting on blocking all handset owners categorically from access to doing that.

I may (probably) or may not have fried the processor, but either way the onus is on me to determine that first due to the way I used - and in part deliberately abused - the device.

Honestly, I am content with the doubleshot I have. From another developer here it's an original rev s-off device, in silver. I put my black backplate on it and a privacy screen protector so the face is solid, unbroken black (no logo) framed in silver. I still use it often for photography, and as a wireless bridge for my devices and printer.

Not much more anymore though i'm afraid. I half-moved into the S3, hated every minute of it despite some of the things I liked about it, then ended up in a note 2. The S3 prepped me for the size of the note 2. Ghastly as it is, it fits a utility purpose of my life so perfectly I can't not have it. Not really a subject for this neck of the woods.
[T-Mobile myTouch 4G Slide] demkantor:
i too have moved on from the doubleshot, well hardly ever used it really, it was the ol ladies and just got it for her being she always wanted a phone with an awesome camera.

she then got the nexus four from me and i stole the doubleshot back. after craking the screen on her n4 i decided to commandeer that and got her a lumia 720 (finally realized android isnt for everyone no matter how much i want it to be)

well she broke that too... ugg... another 100 some dollars later shes back to being happier than ever with her windows phone... oh well.... back to subject

so wifi is not working, three roms and a thousand wipes later still no good. i think i have some serious hardware faults here... damn

also noticed that my bootloader has very few fastboot commands available, just these:

(bootloader) command list

(bootloader) get_identifier_token

(bootloader) checkSbl1

(bootloader) checkHWSecurity

(bootloader) keytest

(bootloader) heap

(bootloader) boot

(bootloader) reset

(bootloader) powerdown

(bootloader) rebootRUU

(bootloader) heap_test

(bootloader) gotohboot

(bootloader) rtask

(bootloader) task

(bootloader) enableqxdm

(bootloader) gencheckpt

(bootloader) readpid

(bootloader) writepid

(bootloader) readcid

(bootloader) writecid

(bootloader) readimei

(bootloader) writeimei

(bootloader) readsecureflag

(bootloader) writesecureflag

(bootloader) lock

(bootloader) list_partition_emmc

(bootloader) load_emmc

(bootloader) check_emmc

(bootloader) check_emmc_mid

(bootloader) read_mmc

(bootloader) load_modem_emmc

(bootloader) get_wp_info_emmc

(bootloader) send_wp_info_emmc

(bootloader) get_ext_csd_emmc

(bootloader) get_sector_info_emmc

finished. total time: 0.013s

OKAY [ 0.043s]

finished. total time: 0.045s

besides the usual, means no bad block tests etc... damn bootloader...
[MENTION=4103240]Blue6IX[/MENTION] , being you have rev-soff and i jbear, mind doing a quick test

fastboot oem ?

is your list of available commands larger or different?

anyway maybe ill grab a new board, oh and can you see what emmc and processor you have?

mine is

MLL00M

version-microp: 0353

just looking for some comparisons here, thanks!
[T-Mobile myTouch 4G Slide] Blue6IX:
I don't have to check, because I already know they are the same.

We didn't get an engineering bootloader, but what we did get (due to some brave exploring by someone here) is the ability to flash the sensation engineering bootloader for the commands you are looking for.

I forget which thread it was in but the answer is here if that is what you need.

Edit:

Booted to bootloader menu, looking at 0353 as well on microprocessor. Not that it matters but i'm running the 1.44.0007 hboot.
[T-Mobile myTouch 4G Slide] demkantor:
Thanks, I may look into stealing that engineering bootloader as I prefer having full debuuging tools handy with fastboot.

I know some of the microprocessors carried on the nexus1 and some had issues so was just curious as my phone seems to have issues what others have.

There's been a few unexplained bricks in these threads so I'm just looking to see if different variants had different issues

But yeah thanks for checking!
[HTC One V] pavan003:
hi

i have an htc one v

i'm from india

my phone details are

HBOOT-1.18.0000

Radio-3831.19.00.120

CID is HTC_038 i need an correct ruu i'm so desperate i've trying for correct ruu since 2 day's pls some one help me and suggest me the procedure to pls guy's :rolleyes:
[HTC One V] junshong:
Can you say what happened after you soft bricked?

Sent from my HTC One V using Xparent Purple Tapatalk 2
[Android General] RamanaNick:
HI GUYS,

Facebook Home, the social networking giant’s attempt to convert your Android smartphone into a Facebook-oriented device might have seen a mixed reaction from the public, but the truth is, it’s officially available for only five Android smartphones at present, and not everyone has been able to try the new launcher for themselves.

If you’re a Facebook addict, you must be feeling left out if you don’t own one of the five smartphones that currently support Facebook Home.

Well, if that’s the case with you, this guide will surely cheer you up as today, we’ll be telling you how you can install Facebook Home on your Android smartphone running on Android 4.0 Ice Cream Sandwich or higher. :D

Facebook Home available to all devices, even unrooted ones. That is correct. You do not have to be rooted to give Facebook Home a try. :laugh::good::o

To install Facebook Home on your Android smartphone, here’s what you need

Android smartphone running on Android 4.0 or higher.

Facebook app by MoDaCo, which can be downloaded from here.(loadbalancing.modaco.com/download.php?file=com.facebook.katana.modaco.apk)

Facebook Messenger app by MoDaCo, which can be downloaded from here.(loadbalancing.modaco.com/download.php?file=com.facebook.orca.modaco.apk)

Modified Facebook Home app, which can be downloaded from here. (loadbalancing.modaco.com/download.php?file=com.facebook.home.modaco.apk)

After you’ve downloaded these files, follow some simple steps which have been mentioned below, to get Facebook Home on your device

Before you start the process, you need to uninstall the Facebook app and Facebook Messenger app if they are currently installed on your smartphone. Sadly, if you’re smartphone came pre-installed with these apps, you will need to root your smartphone in order to uninstall them.

Now, go into Settings > Security and then check the box which says “Unknown Sources”.

Copy the three downloaded apps to your phone or you can download the apps directly to your smartphone as well. Once done, you’ll need a file manager app to access the downloaded apps. Popular File Manager apps like ES File Manager, Astro File Manager, etc. can be downloaded from the play store for this purpose.

Now, once you spot the three downloaded apps, click on the Facebook app (com.facebook.katana.modaco.apk) to install it first. Then, click on the Messenger app (com.facebook.orca.modaco.apk) to install it, and finally, install the Facebook Home app (com.facebook.home.modaco.apk) as well.

Once installed, the three apps should appear on your smartphone.

Now, open the Facebook app and enter your credentials to log-in. Once you’re logged in, tap the “Menu” icon located at the top-left of the app, then, go to Accounts > App Settings and check the “Enable Facebook Home” box.

When prompted, select Facebook Home and then tap on “Always”.

That’s it! Give some time for the launcher to load-up and once it’s done, you’ll have your own, personal Facebook Phone! :D

:D:D:good::good::o:cool::cool::cool::cool::laugh:

Guys, HIT THANKS!! :laugh::laugh::laugh::good::good::good:
[Android Q&A, Help & Troubleshooting] yousef_shad:
Hi ..

Xperia S .. android version 4.0.4 ... Build Number 6.1.A.2.55

I can't find wireless lans with channel more than 11

is this a software issue ?? can i solve this problem??
[Android Q&A, Help & Troubleshooting] yousef_shad:
no answer .... :confused::confused::confused:
[General Questions and Answers] Click95:
I doubt anyone has had a problem like this before, I think I'm in a real pickle (forum is censored), so brace yourself:

Phone: Optimus L7 P705

Firmware(that's what's called, right?): V20 (official update for jellybean)

I installed CM 10 today, and it was great, but I decided to uninstall it after 5 minutes of ''fun'' since some major features were missing like the ability to make calls (no signal) and the ability to listen to music with headphones (they won't work). Now I tried to look for fixes for it, but nothing worked, so I decided to get rid of it

Now this is where it gets

REALLY INTERESTING

: I have tried to flash ROMS with the KDZ updater, it gave me an error with 3 different KDZ files, I have also tried installing another ROM from the recovery mode, but it just gives me an ''install aborted'' error right after I start the install. I have made sure that all my settings were right and tried several times, I tried re-installing CM but nothing seems to work....

My phone is now as useless and basic as an iPhone....(Well okay, not THAT bad) but I need a solution urgently, so your help would be very appreciated.

Edit: RESOLVED, if you found this topic and want to know how I solved the issue, check the last post.
[General Questions and Answers] Click95:
Thank you for the reply, but as I had already explained, the KDZ Update Tool does not work for me, I have tried 3 different KDZ files including the v10k

Edit: Issue fixed, I downloaded the v10 baseband zip file and installed it with clockworkmod.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] keithhidalgo:
Does anybody have problems with their screen having the black crush when brightness is low?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] cl_l:
black crush? When I put my brightness to absolute lowest is i scroll fast in settings screen it looks like the black is "bleeding" as if the black were being delayed or something. Not sure if u understand wut im saying :p
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] j510:
What's your definition of black crush? Never heard this term
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] KillaHurtz:
Black crush ? I assume you are talking about blotches and such. This is an artifact of amoled screens known to us nerds as "mura", and is present on all Galaxy phones.
[General Questions and Answers] ams77:
My daughter only uses her Samsung Vibrant for games and searching online, so she don't really need an add-a-line. Would a T-Mobile mobile broadband (data plan) sim work if I put it in her Vibrant? I searched online, and found many people claim it works, but I called T-Mobile twice and both time said it would not work. Are they saying this to prevent customers from using the data-only sims with their smartphones?

If this is indeed possible, it is said that the sim card must be activated correctly prior to putting it in the Vibrant. What exactly does that mean, and how do I do that? THANKS!!!
[Desire HD Android Development] tweakos:
Strike X

Strike X Stock S4.1 - post 4

​

This is my own rom , i cooked for myself, and i just want to share it with you :)

Based on One v,one SV, Desire S\X , inc s.

Features:

Android 4.0.4 \ Custom sense ui 4.1+
blah blah blah........

What is working:

Everything should....

What is not working

Camera:
Burst shot not supported
HDR not working
you should turn off stereo recording in video options

Camera is the WIP

Bugs:

Maybe some graphical bugs,please report about them in this thread (attach screenshot that i can see what and where)

video preview by sany789

[YOUTUBE]S2AezkZsk4U[/YOUTUBE]

Download:

Strike X V 2.0

Important ! - rom is little different then V1 version, so read changelog !

Strike X v 2.0

strike x v1.0

mirror - http://d-h.st/c8O

Recommended kernel for this rom - T8-StrikeX-edition.zip - flash it via recovery

Strike X OTA 1

OTA 1

Strike X beta

mirror

Important notes:

Full Wipe reqired.After first boot and setup , go to personalize, choose sense 5 skin for full s5 theme expirience and reboot your phone - this is important!.

For recent app - go to setting,buttons,and choose press menu to open menu,keep press to open recent app

Big Thanx TO ALL Devs on this forum and htc to make it possible :)
[Desire HD Android Development] tweakos:
Mods

Sense 5 like lockscreen: thanks to ckpv5

Lock.zip

Sense 4.1 lockscreen

Sense 4.1 lockscreen

default sense 4.1 fonts - flash via recovery.

FONTS

Status bar with clock - flash via recovery.

Status bar with clock (v1.0)

mirror

skins:

aluminium,mate,infinite,memories,purple passion,PaintingTheWorld,SpaceshipEarth

skins - extract - install

Strike X themes by f_enzo

post 238