yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] sftd:
First off, while very few people in this community "know" me, the remote few that do can attest to the fact that I have been blessed in life with the financial apptitude to put my proverbial "money where my mouth is" when I say the following.

I will make a you a deal, and upon review of the situation extend this same offer to others experiencing the same problems. You expressed concern in the other thread that you didn't at the time have to money to fulfil your insurance deductable. I will send you the money, and an additional sum to cover shipping expenses. Once you receive it, you send me your handset, and give me three days time starting from the day the tracking status shows as arrived. If I or a good friend of mine can not get the device back in good working order by that time, I will return it and you can keep the insurance deductable and use it to acquire a new device. However, should the device be restored to good working order, once it is returned to you, you would need to both return my money and an additional sum of 50.00 USD. Why the additional money? Its an arbitrary verification sum to see exactly how sure you are that your phone is not able to be fixed.

There is no chance of loss on your end here as you will receive the insurance deductable before you ever ship the phone, thus insuring that if I were to never return it you would still be in a situation that was better than your current. However, if this is not enough, I am also willing to pay for you to have an attorney of your choosing (up to a reasonable rate) draw up a mutualy binding contract locking both of us into the agreement.

Let me know if you'd be interested. Either way you will have a working device at the end of the process.
[EVO 4G General] gpz1100:
Please delete.
[EVO 4G General] HipKat:
What part of running RUU not working did you miss?
[EVO 4G General] mattykinsx:
What part of I don't believe that did you miss?

Flashing a ROM doesn't DO ANYYYYTHING but copy files to the system folder.

(Unless it has a kernel and then it's writing to BOOT as well..but not the bootloader..just the boot partition that handles booting the rom and such)

You know when you risk actually bricking a device??

When you root, change recoveries, update the pri, update hboot, update radios or update the NV.

Not when you're flashing a ROM
[EVO 4G General] snowboarda42:
Will recovery still work if you have s-on? I'm thinking about flashing the unrevoked-forever-son.zip but leaving it rooted with cm7, just as a preventative measure in case I get the bootloop o' death.

Sent from my hand with XDA Premium installed
[EVO 4G General] HipKat:
Did some folloow up research:

In a nutshell,. you lied or made up some things to try and debunk me, but I debunked you, instead...

Can we get back on point now?
[EVO 4G General] HipKat:
It's a solid offer, I'd take it and I don't know what other threads you have or haven't read, but people are running different RUU, reflashing recovery, different hboot versions and not fixing the problem, so if you know something that everyone else doesn't, why not just save your money and provide some steps that haven't been taqken yet.

BTW,

Don't believe all you want, but go actually READ THE OTHER THREADS. Almost ALL have tried to flash RUU, different versions of RUU, different recoveries, etc and NOT WORKING!!!!
[EVO 4G General] mattykinsx:
I wouldn't doubt this to be true.

Here's what happened, friend:

Cyanogen, because of a lot of things including Android's growth and so forth, has had an influx of new users.

Generally speaking, new users are new to this whole process.

Instead of being smart about it and either a) READING BEFORE YOU DO or b) NOT DOING WHEN YOU DON'T KNOW WHAT YOU'RE ACTUALLY DOING

A few people....10 you say...have ****ed their phones up.

10 users....out of 250,000+

User error.

I just want to add one thing to that, if you can change the recovery [actually if you can access the bootloader at all] you're not bricked...

again proving what I'm saying about people not knowing what they're doing but doing it anyway.
[EVO 4G General] Justin.G11:
To be clear _all_ AOSP ROMs available to the EVO are CM forks. They are the _only_ team actually deving a ROM from the ground up, everyone else is actually using their github and making some tweaks.

So splitting hairs at CM vs AOSP is silly unless you can point me to another ROM team that actually does all the work.

As for this bricking issue ... I think some people are assuming waaaaaaay too much and jumping to some really far-fetch conclusions. I don't think it's a CM issue at all, personally.
[EVO 4G General] Rippley05:
I don't either. Maybe it has something to do with Flashing SO much.. a nightly every night for like a year.. with some off time here and there to play around with the new Sense craze...

I know one guy was on cm6 stable and said he only ran stables. That is very unfortunate.. but I wonder if repeated flashing/wiping/flashing/wiping is causing some failure.
[EVO 4G General] HipKat:
TBH, I was wondering the same thing when I had my first white screen of (almost) death, as I had been flashing like mad, ona daily or almost daily basis.

THat was the sole reason, I ran RUU and reformattd my SD Card and basically started over.
[EVO 4G General] mattykinsx:
It is true that the memory only has so many writes like all solid state memory ...and really all drives... but the amount of writes is so high it's of no concern.

Being as "flashing a ROM" does nothing but format /system and then unzip your file into the /system folder...it's no different than using the device which is constantly causing writes.
[EVO 4G General] rushco:
The factories produces millions so I'm sure there are some bad ones in the bunch that will stop working right. Some can be DOA some can die 6 months later. That's probably it and people are not looking at the root problem (how they were made) but what happened right before it gave out.
[EVO 4G General] mattykinsx:
It's possible, I'm still chalking it up to user error though.
[EVO 4G General] Rippley05:
That's kinda what I think. Eventually, some of the defected EVOs fail. Maybe that's why CM users are more common because of multiple flash/wipes.

Maybe it doesn't have anything to do with it.. I am at a loss honestly..
[EVO 4G General] gpz1100:
Matt, I agree, but disagree with you. Your first part about what constitutes flashing a rom is correct. However, on a stock phone, the system partition is RO, not RW. All the configuration and settings is stored on the data partition. The system partition never gets touch until an OTA update occurs.

Most flash memory manufacturers offer warranties 3-10 years, so the life cycle is definitely finite.

Now, the question becomes, does the memory on our evo's become corrupt because of a combination of all the flashing + potential constant writing to areas not normally written to.

Most puzzling is the the inaccessible recovery, even when successfully flashed via flashboot :confused:
[EVO 4G General] mattykinsx:
You have a few issues here though.

First of all the system partition and data partition are just partitions.

Its just like making different paritions on your hard drive on your desktop.

Its all the same drive.

One partition doesn't get more or less writes than another.

Also, this recovery writing issue further proves what I'm saying.

When you flash a rom it doesn't do anything with the recovery partition as far as writing to it or modifiying it.

Thus what I said is most likely the fact of the matter:

People that don't know what they're doing are doing things without reading or learning.

People that should probably just leave the phone stock.
[EVO 4G General] remman:
Your bold part is where I believe people are taking offense. I personally think it is a hardware issue. Mine was not caused by user error as far as I know. I had been on the same nightly for 2 or 3 days then out of the blue while sitting on my desk it went into loops. Tried both AmonRA and CWM recovery flashes multiple times and neither took. While you may be right about a few of the cases, if you acknowledge that even 1 of the people who it happened to is someone who does not fall into your "noob" category, then your argument is wrong.
[EVO 4G General] boliviano3:
This thread is starting to remind me of this one: http://xdaforums.com/showthread.php?t=909763
[EVO 4G General] donatom3:
So to the OP how do you explain my brother's EVO which I never put a CM7 or ASOP rom on. It only ran Sense roms, in fact only one sense rom, and I'm not going to name which one because I don't blame them at all. My phone and my brothers other phone that have cm7 (both of which I rooted and flashed myself) have had no issues.
[EVO 4G General] HipKat:
Fair question. Were they rooted with Unrevoked forever?
[EVO 4G General] mattykinsx:
I don't care where people are taking offense.

I take offense to this idea that cyanogen roms are the problem.

Also, just because EVERY SINGLE CASE isn't caused by the exact same problem doesn't mean that my argument isn't completely sound.

Copying files from your SD card to your /system folder (flashing a rom) doesn't touch your recovery partition and its not going to brick your device.

/end
[EVO 4G General] rstuckmaier:
Part of my thinks that if there is a REAL issue (not user related) that this is probably it. NAND only takes so many re-writes and technically our phones weren't designed to be flashed 100s of times.

On the other hand, HTC being the root-friendly company it is probably took this into account. And to further this point, NAND should be able to take millions of writes, just like an SD card or solid state drive.
[EVO 4G General] mattykinsx:
Dude...do you understand that when you 'wake' your phone it writes to NAND?

In fact, when your phone sits there idle, it's STILL writing to NAND.

As I've said 50 times in this thread thus far, when you 'flash a ROM' all you're doing is deleting the files in the /system folder and copying from the SDCARD to /system.

And yes, NAND is just like an SD card/SSD, the amount of writes is so high that the device usually breaks because of some other issue before you ever get close to that number.
[EVO 4G General] hatlesszone:
A good memory controller should do wear leveling on the NAND, so bad blocks from writes shouldn't be an issue unless the memory is full and it runs out of extra NAND cells to use.
[EVO 4G General] N_Jones:
Why can't I find an ignore button?
[EVO 4G General] ropodope:
how many RC's does it take to get a real release i mean seriously folks. when you see a RC you assume it's pretty much ready for the big leagues at that point. when you see an RC4 it's kind of a joke in the community if you want to know the truth. i don't know how old some of these cm developers are but they should take a lesson in respect and humility because the ego's do not match their output these days.

rope!
[EVO 4G General] Rippley05:
Blah blah blah. Sounds like a ramble of someone who has nothing to say but wants to be heard

Sent from my parents basement..
[EVO 4G General] mattykinsx:
Honestly, if this post is in reference to me, I don't care whether you ignore me or not.

But if you put someone on ignore when they're speaking the truth because you don't like what the truth is, well, that really speaks about who you are.

First of all, if you're trying to suggest that a thread getting to "28 pages" is somehow a verification or validation then that's just silly.

Hands down.

As far as everything you've said, I don't know exactly what to tell you.

I do know that different RUUs can not work on certain hardware versions and such.

But, being as you CAN get into the Bootloader and you CAN do things within the Bootloader, it IS recoverable.

One other thing, don't you think it's a little convenient that all these problems started once Cyanogen users increased significantly?

Cyanogen has 250,000 [likely much more] users.

And has had a serious increase of userbase in the past few months.

And NOW Cyanogen starts causing problems like this?

C'mon man.

Give me a break.

What you have here is newbs that, respectfully, shouldn't be rooting [because they don't read and don't know what they're doing] and such doing so and ****ing their devices.

Show me a KNOWN [I don't care how LONG they've been users on XDA] advanced user that this has happened to and a MIGHT re-consider my position on this.

But my knowledge about how computers work and my logic [referring to the increase of newbs and THEN the showing up of this issue] point to me being the one right here.

I expect this level of arrogance/ignorance in a thread like this.
[EVO 4G General] ropodope:
you prove my point. when i installed cm7 rc1 i had 5, count them 1,2,3,4,5 fc issues in about 5 minutes. sloppy engineering these days. keep your cm7 rc50 for all i care. you are a moron. it seems to my like you are the one who has nothing but blahblahblah to say.

rope!
[EVO 4G General] gpz1100:
So are you claiming there are other steps to try while in fastboot besides those already mentioned.

If that is indeed the case, then do share this information. Why would you keep it secret??

I'm certain those that are experiencing this issue would love to fix it without going through the trouble of swapping to another device.
[EVO 4G General] mattykinsx:
I cannot answer that question.

Besides very basic troubleshooting, I refrain from giving advice on such matters simply because I would rather hold the device in my hand and do it myself.

I don't know what that person was doing with their device when the problem occurred nor do I know what that persons background knowledge in technology is.

Yes, people SAY what they were doing.

"Oh I just flashed the ROM and it happened" but 99/100 times when I ask someone what they were doing on a device [whether it be a computer or phone or what have you] they're not telling you the whole truth. (either to protect them from looking like a fool or what-have-you. And I'm not just speaking about people online, I'm talking about my only family/extended family/friends too)
[EVO 4G General] N_Jones:
Yea matty I was talking about you. If there is any truth in your long winded posts its lost in your elitist attitude.

Your just another xda douche bag. Which is why I read this site less and less.
[EVO 4G General] mattykinsx:
1. I know what you said. That quote actually shows that this thread should be deleted and it also supports the idea of newbs ****ing their devices due to ignorance. People have been flashing ROMs for years on devices with no issues.

2. If I told a non-tech savvy person to "run a RUU", even if I explained how, 9/10 they won't be successful. Like I said, I don't trust people when it comes to repairing devices. Most don't even understand what they're doing much less how to do it. Even if you give them a step by step.

3. Name calling, expected.

4. Can't handle my logic?

5. Name calling, expected.

You like to ignore logic and parts of my post that show the likely cause of this eh?

Elitist attitude because I think that people, that don't know what they're doing, shouldn't do it?

I wouldn't trust my Grandma with rebuilding her engine, is it really elitist of me to expect that, if she needs that done, she take it to someone that knows what they're doing?

Fail.
[EVO 4G General] k2buckley:
I just simply don't agree with your logic. That's all. And I wasn't name calling, just stating an observation I had made.

You apparently like to ignore the fact that I stated that I had one of these bricked devices, to work on myself. I was unable to get anywhere with it. I had other guys, more knowledgeable than myself, trying to assist as well. Also as I stated, I personally helped a few of these guys with the problems (outside of XDA) and am positive they were doing the steps correctly. They were not incompetent.

The only reason for my initial post here, in response to one of your statements, was simply to tell you, whether you believe it or not, that you can end up at the bootloader, with a non functioning and non repairable device. As I also stated, I also used to think that this couldn't happen, and I went into each one of these individual cases 100% confident that it would be able to be fixed. Thats all, I wasn't trying to argue, or anything of that nature. I wasn't even really trying to contest you, rather let you in on some new info, that it does seem possible to be bricked at the bootloader. Like I said, if someone knows any other possible ways to attempt recovering these phones, I'm sure some of those guys would be thrilled to have some more suggestions thrown at them.

Anyways, I'm really out of this thread this time:p That's enough.
[EVO 4G General] Rippley05:
K, thanks. Bye Bye

Sent from my parents basement..
[EVO 4G General] mattykinsx:
You don't agree with the logic that, with the increase of noobs this problems starts showing up, thus that it's very very likely user error?

Again, c'mon now.

Wait, you mean that something that is FREE and in BETA didn't work correctly?

Who do you think you are and where does this sense of entitlement come from? Your mom should slap you.
[EVO 4G General] badassdes:
Before

in case

this thread is "closed"...

can someone answer my question(s)? I've been flashing ROMs since Sep 2010 and this is the 1st time that my phone is having issues....

My phone is stocked with this problem since yesterday.... Thanks in advance
[EVO 4G General] mattykinsx:
I would unroot the device, returning it to complete stock.

Then, if the reboots continue at stock, take the device to a store.

If not, reroot the phone etc...
[EVO 4G General] ropodope:
release candidates are typically a month from final release maybe two. You certainly dont see 4 release candidates. Rc's are supposed to be quite a bit better than beta. That's why they call it a candidate for release you unmitigated fool.

If my mother slapped me I would end up with the same kind of mentality that you have which apparently isn't much for you to make a ridiculous comment like that. What are you 12? If so that would make you just slightly older than what seems to pass for cm7 developers of late so do me a favor, take my quarter and buy a clue.

Cm7, making bad roms look good one mistake at a time.

rope!

Sent from my Vaelpak 3.2 enhanced Evo 4g
[EVO 4G General] mattykinsx:
As ungrateful as you are for something provided free, with them spending countless hours building it, you should be banned from XDA and every developer should ban your ip from their mirrors.
[EVO 4G General] ropodope:
ah you are a lover of free speech I see, if you don't like it dont use it mentality rather than deal with the issues that obviously people are having who never had unresolvable issues before. It's ok for you to sit there and run your big mouth because you are on "their" side. You are dumb, your are really really dumb. So answer the points I just said rather than crying like a mamas boy begging xda to ban me. Does 4 release candidates seem a bit ridiculous or not Einstein?

You really are a loser.

rope!

Sent from my Vaelpak 3.2 enhanced Evo 4g
[EVO 4G General] mattykinsx:
No, you are a "loser."

You have NO EVIDENCE that Cyanogenmod has caused ANY bricks.

In fact, we have EVIDENCE that SHOWS that non-cm ROMs have caused these SAME issues.

As far as your complaints about too many release candidates, your sense of entitlement is why I wish I was not born in this country.

Cyanogenmod is FREE.

These guys spend HOURS to provide people with a great alternative with no cost.

Also, your free speech comment is the most ridiculous thing ever.

Free speech comes with responsibility.

Just because you CAN say something, doesn't mean you should.
[EVO 4G General] remman:
And yet in every post you call anyone who this has happened to a noob.
[EVO 4G General] ropodope:
And so does yours. you are free to move anytime you like. I don't feel like I am entitled to anything free, that's what you get for making assumptions. I do feel there should be a big difference between alpha, beta, and release candidate. And I do feel I have the right to voice problems that I have with the rom. Just because it is free doesn't mean real problems shouldn't be brought to light and dealt with in a professional manner by the developers if which there are quite a few with cyanogen mod.

What are you their spokesperson? Are you getting a stipend? Then chirp on your own branch there beetlegeuse.

rope!

Sent from my Vaelpak 3.2 enhanced Evo 4g
[EVO 4G General] mattykinsx:
As I said, I have yet to see a KNOWN tech savvy person report this happening.

[keeping in mind that the amount of time you've been registered here doesn't make you tech savvy]

You're free to report bugs to their bug tracker or do it in a constructive way.

Nothing you've posted here has been constructive.

Your whine because of their naming structure is irrelevant.

And no, I'm not their spokesperson but I will defend anyone or anything that is being unfairly judged or bad mouthed.

Side note: when I have the money to move it will be considered, that's for sure.
[EVO 4G General] ropodope:
Sounds good to me, all of it.

rope!

Sent from my Vaelpak 3.2 enhanced Evo 4g
[EVO 4G General] gpz1100:
Matt, quit beating around the bush!

Put your money where your virtual mouth is! If there are other steps people can take to try to recover, then share them, otherwise find another thread to troll in.
[EVO 4G General] mattykinsx:
Troll in eh?

I love when people name-call when they don't like what's being said.

As far as your sharing steps to repair, can't.

I don't know the circumstances that lead these people into this "bricked" situation nor have I ever seen a device in this "un-repairable but unusable" bootlocker state.

Now take your name calling, look up the true definition of the word while you're at it, and shove it up your ass.
[EVO 4G General] checkititishuge:
Look everyone my e-penis is bigger than yours

8========================================D

SO SUCK IT
[EVO 4G General] ropodope:
you just now coming out of the closet? Hooray for you!

rope!

Sent from my Vaelpak 3.2 enhanced Evo 4g
[EVO 4G General] Rippley05:
Good thing it doesn't matter what you "feel".

It is being dealt with in a professional manner by everyone except you. How hypocritical is it to demand someone be professional while acting like a jackass yourself?
[EVO 4G General] ropodope:
And this coming from a professional like yourself who strikes me as being just a bit too late to your own party. If you had an uncle named jack who was on an elephant and couldn't get off would you help your uncle...

rope!

Sent from my Vaelpak 3.2 enhanced Evo 4g
[EVO 4G General] Captainkrtek:
Thread Locked...
[Android Software/Hacking General [Developers Only]] almar2:
Hi guys,

A lot of the current android devices use armv6, many of them support SIMD instructions. Armv6 adds 60 SIMD instruction which compare to the NEON extension in later armv7 series. Android does future some armv7 NEON optimalisations in dalvik and the javascript renderer. Compilers used to build for android at the moment do not support armv6 SIMD vectorisation. My idea was to rewrite specific armv7 optimalisations for android into armv6 ones using these SIMD instructions. The realview compiler is able to vectorise for SIMD armv6 but doesn't support android building (eabi) as I understand it.

We could improve the performance of many devices at once by doing this (I think).

So my question is, who is experienced enough to help start creating specific armv6 SIMD optimalisations.

Reference: Search for armv6 simd instructions keil on google.
[Thunderbolt Q&A, Help & Troubleshooting] Stevez48:
Is it possible to reload the stock OS, but keep Root?
[Thunderbolt Q&A, Help & Troubleshooting] mthorn79:
On xda-developers website they have the Easy Root tutorial that does just what your asking.

Im keeping mine stock with root as well, I love Sense so I see no reason to change.

Sent from my Tbolt from Tapatalk
[Thunderbolt Q&A, Help & Troubleshooting] Jrocker23:
If you follow the post here http://xdaforums.com/showthread.php?t=996616

You will be rooted and already be on the stock release. Thats what im on now.

Im not sure about the one click methods..