yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] timaloud:
out of options

Yeah nothing different happens after booloader reboot, still says "LOCKED"

Thank you anyway for being so helpful and supportive. I guess the phones good for the garbage then.:(
[HTC Sensation] quinns:
Hi guys, I'm sorry to necro this thread, but it's very close to the problem I'm having. I can't boot to recovery or android, just hboot. I can run commands on the phone through fastboot, but adb does not list the device. Fastboot devices does list the device. I'm thinking I need to run an RUU, but I don't know which one. My fastboot lists

Can anyone help me?
[HTC Sensation] ganeshp:
try any RUU

any RUU should work for you :)
[HTC Sensation] quinns:
Any at all? All right, thanks. I'm looking for one now.
[HTC Sensation] ganeshp:
Yes based on the site info you've given any ruu should work ;)
[HTC Sensation] quinns:
I flashed an RUU and it worked successfully. Just prior to that it randomly let me boot into recovery once! I could even flash roms. But it was a fleeting moment and it still will not boot past the HTC splash screen. No recovery even, though the RUU does list it's image version now and it does show that the bootloader is now locked... FML. Thanks for the help man. Any idea what I should try next?
[HTC Sensation] ganeshp:
Locked is fine ..but did the RUU ran successfully ? did it thrown any errors ?

also as long as you are SOFF (which cant be changed unless you do it explicitly via a specific command ) you can revert the Locked thing :D

now tell me what RUU you ran ..give me the name

also run the RUU again
[HTC Sensation] quinns:
I ran RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed. It didn't throw any errors. It seemed to work perfectly.
[HTC Sensation] ganeshp:
try any ICS RUU ..mostly try the European unbranded one ..and see
[HTC Sensation] quinns:
I'm now trying out RUU_PYRAMID_ICS_HTC_Europe_3.33.401.6_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_266171_signed. I tried re-running the other RUU and I still have the same problem.
[HTC Sensation] quinns:
That seems to have done the trick! Thank you! The fact that you took your own time to help me out of kindness is an amazing thing.
[HTC One X] jameslfc5:
I need to return my One X to Amazon as it has a long list of faults but I was just wanting to see what a Rooted one x was capable of first, so I was wondering if they would check this or not?

Thanks
[HTC One X] fekle:
Yep, i returned my first HOX, they didn't care and sent me a new one, after this one was faulty, too, I sent it back to get my money refunded, the didn't care either:)

After this I bought a new one on Amazon, which is faulty too -.- haha, however, I'm going to send this back at the end of the 30-day replacement period. ALL of my HOX were/are HTC-Dev unlocked. The first one actually was even bricked XD

So go for it mate, they don't care! ;)
[HTC One X] jameslfc5:
Haha! Cheers for the advice mate
[HTC One X] fekle:
you're welcome! :D
[HTC One X] ricksonchow:
seems there is something wrong with the white One X from Amazon UK, it was taken off the shelf...
[Huawei Ideos X5 U8800] brdnacer:
hi there. i have a question. is there a way anyone can port totally stock miui v4.0? why? because i need stock wifi driver. it supports ad-hoc, but with this new aurora wifi driver i just can't and can't astablish connection (i used the guide and still nothing -.- ).

i was on cm7 for a while but it is buggy (.35 kernel). so can anyone help me? i know porting whole rom is a big deal, so just to complement old aurora or stock miui driver in rom would be ok. anyone?
[Huawei Ideos X5 U8800] spirosbond:
I connect at ad-hoc normally using this guide with latest aurora :confused:

http://xdaforums.com/showthread.php?t=1511544

I already tried using the system's wpa_supplicant file from MIUI but with no luck...:(

Maybe we need more files from it... I don't know! I will make some more experiments though...
[Huawei Ideos X5 U8800] brdnacer:
yeah i tried that but no result. i really don't know why. first i tried with password, then without it. same thing. i would really appreciate it ^^
[Huawei Ideos X5 U8800] spirosbond:
just check the form to be exactly the same with other profiles (spacing, tabs, "" etc)... And also I tested it without security.
[Huawei Ideos X5 U8800] brdnacer:
i copied the other form from wifi from my school :p and just changed everything or added some lines - still only with copy/paste. still nothing
[Huawei Ideos X5 U8800] adaskar:
although i know this isnt correct place, I just wanna ask and know it

miui 4 works on u8800 or will be working some time ?

thanks in advance
[Huawei Ideos X5 U8800] brdnacer:
it is working :) currently i am on this one http://xdaforums.com/showthread.php?t=1562661 but there is also this one http://xdaforums.com/showthread.php?t=1475687
[Huawei Ideos X5 U8800] sr21:
There are two working versions already:

MIUI V4 2.5.11 for U8800 by Geno [end]

[ROM] Elite ROM SX Final Release (FIXED) - 2012-04-15
[Huawei Ideos X5 U8800] adaskar:
thanks guys

I'll have a look at them

do u mind if I ask some more question ?

I guess you said no :)

brdnacer the version which you are using now is stable ?

i mean how is the condition of battery or transition or something else ?

Im asking these question because I have a limited internet connection

and I can't try whatever I want :(

I'm so sorry
[Huawei Ideos X5 U8800] brdnacer:
i am using this one http://xdaforums.com/showthread.php?t=1562661 . battery is so so. lets say 7/10. games and android itself is running smooth, basicly nothing to complain about :) but ofcourse you must have official 2.3 already once before installed.

and about this limit... go for coffee or cola sometimes to a bar with wifi, and use it as much as possible :) + i have password for my school wifi :D a few of us managed to get password. and now we can use internet for free even at school :cool:
[Huawei Ideos X5 U8800] adaskar:
thanks for special advice :)

as soon as possible(when I go to a cafe or sth like that:) ) I will try it but its confusing my mind that it's said that this rom will have no more updates :| but as you say, I guess it doesn't need anymore :)

anyway, have a good day
[Huawei Ideos X5 U8800] brdnacer:
niether one of those 2 will get updates
[Galaxy S I9000 Q&A, Help & Troubleshooting] mohaimed:
hi. i am on slim ics v3.6. i have used almost every ics roms,but i have found one feature unavailabe in ics which is really bugging me.if i call someone,and if that person is already talking to someone i cant understand.in gingerbread it used to appear 'call waiting'. is this feature unavailable in ics?? any way to get this???
[Galaxy S I9000 Q&A, Help & Troubleshooting] broncosfan007:
Have you tried ICS ROM Vanilla ICS Graduation Edition? If not I think that is the ROM you are looking for.

Hope that helped! :D
[Galaxy S I9000 Q&A, Help & Troubleshooting] erpurohit:
Goto ics phone>settings>additional settings, here you can find call waiting option.

hit thanks if i helped you.

Sent using i9000 running Doc's Master 4.0.4
[Galaxy S I9000 Q&A, Help & Troubleshooting] mohaimed:
that notifies me wen someone calls me. but wat if i call someone and that person is already toking to somebody else.i cant understand tht.it gingerbread it used to pop up 'other party call waiting"
[Galaxy S I9000 Q&A, Help & Troubleshooting] erpurohit:
I havent seen that anywhere.... Can you guide where i can find that in gingerbread and then i will if i can help you on that.

Sent using i9000 running Doc's Master 4.0.4
[Galaxy S I9000 Q&A, Help & Troubleshooting] mohaimed:
there was no such 'option' in the gingerbread.call some one and make sure that person is already toking to someone else.wen u call that person,"call waiting" will pop up on your screen so that u understand that the person was toking to someone before answering ur call.there is no option to enable or disable it.but if i call someone from my ics dialer it doesnot notify me with "call waiting"..if the otherbperson is talking.hope u understood.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gopalasubramanium:
Goto Setting>>Call Settings>>Voice Calls>>Call waiting - Check this to enable.

However, please understand that this is a network dependent feature, call your network provider and understand.

Gopala Subramanium

http://www.FixMyStuff.In

Facebook: http://www.facebook.com/FixMyStuff.in | Twitter: @FixMyStuffIn
[Galaxy S I9000 Q&A, Help & Troubleshooting] :
Try the following

Call Dialer -> Options -> Settings

The call settings is not present in the general android settings.
[Galaxy S I9000 Q&A, Help & Troubleshooting] gopalasubramanium:
Goto Dialer >> Settings >> Additional settings >> Call Waiting - Check the check-box

However, please note that this is a network dependent feature.
[Galaxy S I9000 Q&A, Help & Troubleshooting] nilzkul:
Call waiting is there but i am not able to switch between two calls.. and i guess call conference is also not available in ics right?
[Galaxy S I9000 Q&A, Help & Troubleshooting] gopalasubramanium:
Call conference is also available in ICS, while you are on 2 calls you would see a merge call icon. again it is a network dependent feature.
[Galaxy Note GT-N7000 General] pakalrtb:
I am in no way an expert and what I am about to say could just make no sense. But after reading hundreds of posts on the subject I believe that ONE common pattern emerges. The brick is not really caused by a faulty wiping process of either CWM or Stock recovery. It's rather caused by the use of the power button in a recovery environment in combination with a faulty process. I'd be glad to hear the voice of some expert to either validate or completely reject my theory.

P_
[Galaxy Note GT-N7000 General] Ashren81:
like how? if its not a faulty wiping then why the faulty process combination? its the kernel source. samsung changed something to make it problematic with cwm. the rest of GB is fine. but since the leak of ICS and the latest official one, the problem persisted.
[Galaxy Note GT-N7000 General] EdgaBimbam:
i think samsung changed kernel against cwm(as we know it is very popular) to brick phones thats how they would earn some extra money: from repairing, buying new phone. Just my opinion :D
[Galaxy Note GT-N7000 General] Ashren81:
i second that. just like how apple did to their baseband kernel every now and then to block jailbreaking.
[Galaxy Note GT-N7000 General] friedje:
Negative publicity would cost a lot more to samsung then the profit of selling/repairing less then 50 bricked phones worldwide, you guys should stop reading conspiracy novels
[Galaxy Note GT-N7000 General] Entropy512:
Except that stock recovery is also affected.

Nothing to do with the power button - just a broken MMC driver.
[Galaxy Note GT-N7000 General] M3TALLICA:
I believe this. Samsung will be generating more revenue this year.

There are thousands of users outside XDA who are waiting for OTA/Kies updates of their regions.

----

Probably my last samsung phone. Delayed and dangerous update.
[Galaxy Note GT-N7000 General] Ashren81:
why dont u provide the community with a solution rather than publicising ur conspiracy theory. :D

---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------

Stock recovery is also affected when u try to wipe a note with rooted/cwm kernel as far as I can tell. As long as it its stock virgin, no problem.
[Galaxy Note GT-N7000 General] JamieD81:
150% FALSE

i dont touch the power button in recover ever, i use the menu-key/home-key/vol-keys

yet i still bricked my phone :P
[Galaxy Note GT-N7000 General] Tiny Wiz:
Most Notes are under some kind of warranty. If you believe that Samsung would brick phone intentionally to make $$ then I disagree with you in every way.
[Galaxy Note GT-N7000 General] M3TALLICA:
Intentionally or unintentionally... not everyone but hundreds of users will have pay for MoBos just because they flashed official ICS.

And 'you flashed it yourself' is NOT an excuse. It proves Samsung has poor quality control and testing, period.
[Galaxy Note GT-N7000 General] chasmodo:
I never ever touched anything during cache wipe in CWMR, and I still got the black brick.

So much for your little theory.
[Galaxy Note GT-N7000 General] clandestino123:
Did you (at any earlier date) flash CM9 or a variant of CM9 on your note?

My theory/hypothesis is that these bricks are occurring when LPY is flashed on a note that has, or has previously had, CM9 or a variant flashed on it.

I am not sure that the ICS kernels themselves are actually faulty.
[Galaxy Note GT-N7000 General] praetorius:
It's the cwm. Period. A lot of people call it a bug, i would assume it is a feature designed by sammy devs to avoid tinkering with their software.

I am on stock LPY and i did a data wipe via stock recovery.

Zapped through server hops to XDA forums
[Galaxy Note GT-N7000 General] freedomispopular:
Isn't Samsung known to be one of the most dev friendly manufacturers? So why would they try to keep people from tinkering with it? As far as I can tell, they just made a mistake. Besides, I know it's cliche, but we all know that when you tinker with stuff you do so at your own risk. Our experiences with the Note should serve as a reminder of that.
[Galaxy Note GT-N7000 General] chasmodo:
Very interesting theory ideed. Tell me, how does your pet theory cover at least half-dozen hard-bricks happening after upgrading from stock GB, rooting and then doing a wipe?

I see.

____________________________________________________________

Entropy512:

These kernels are fundamentally dangerous. Samsung introduced some sort of bug in the eMMC driver that can permanently damage the eMMC flash storage of the phone.

Kernels that have been confirmed affected are:

XXLPY official ICS release for the GT-N7000 - At least one user has fully hardbricked and at least 2-3 others have "blown" /system or /data partitions - one of those was after wiping with stock recovery

____________________________________________________________

Chainfire:

WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !

Deleting large files while fully booted may also cause problems with your flash memory.

____________________________________________________________

These two are top-notch kernel developers, and they don't know what they are talking about? Get out of here....
[Galaxy Note GT-N7000 General] Note_E:
Great but either way you make it worse. Its already been said and resaid...and stickied. This **** is getting so lame now
[Galaxy Note GT-N7000 General] PJ147:
+1 for this

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] trahzebuck:
Yes you are right. This is lame - until you brick your device.

What i really don't understand in all this discussions is the mistrust in Chainfire.

We all are more or less using his great work. almost every custom rom has it's roots in CF-Kernel.

Now Chainfire give a warning and people try to argue it away. What's that?

Same to Entropy... :(

It's a bit like not using safety belt in a car. In the most cases nothing happens....

Though I'm eagerly waiting for ICS - I'll wait for a new update from Sammy or a new statement from CF.

And yes, the discussions should be stopped. but there are new roms released and the risk is growing....
[Galaxy Note GT-N7000 General] ukicar:
as well as profit .... samsung :mad:
[Galaxy Note GT-N7000 General] clandestino123:
Well let me explain. :)

When we read through threads in the N7000 developers section (and the SGS section, and I'm sure, other android developers forums too) we see something crop up time and time again: People flashing ROMs/kernels with a full wipe, and getting different results. Logically there are only a few reasons why this might be the case...

a) Most likely, the users are at fault and not following the steps correctly. In fact, this is highly likely on XDA, as very often, English isn't the first language of an XDA member.

b) The ROM / kernel download did not complete properly. I would say that this is very rare.

c) The hardware configurations are not identical. I would say that whilst each hardware component operates within certain parameters and tolerances, this factor would be extremely rare. In practical terms, the hardware configurations are identical.

But perhaps there are another 2 possible explanations:

d) the "full wipe" is not actually fully resetting the device back to factory set-up.

e) Sometimes, the flashing process does not properly complete, even though it appears to have been 100% successful.

Consider this. 2 people with 2 separate galaxy notes, with identical ROMs. Both follow an identical flashing process.... yet 1 ends up with a 100% working device with no issues, whilst the other ends up experiencing some FCs, and lag on his device. The latter has to reflash, or do a full wipe, before he gets his 100% working rom... How does this kind of thing happen??? It can't be explained by (a), (b) or (c). I suggest that (d) or (e) must be the cause.

I realise that you are quoting some posts from respected developers. I am not a developer. However I am a scientist. In the ICS warning thread, it is stated that the LPY kernels are dangerous, and it is also acknowledged that many users can wipe data time and time again, without problem. It is then stated that a couple of ICS kernels are definitely safe. How can this be known for certain? If a user bricks his phone whilst using one of the "safe" kernels, does that mean that the kernels become "unsafe" ?

Anyway, these are my thoughts on the issue. :p Maybe someone will soon uncover the root cause, and blow my theories out of the water, ha ha.....

---------- Post added at 09:58 PM ---------- Previous post was at 09:47 PM ----------

In my view, you are perceiving this as "mistrust". However it isn't mistrust, it is simply rational thinking/ decision making at work.

I acknowledge that these two guys are doing, and have done, fantastic work for everyone who loves to tinker with their phones. However no-one has yet identified the real cause of the hard bricks. By root cause, I mean the actual lines in the code that are causing these hard bricks to occur.

It is one thing to warn people not to do something, in case something bad might happen.

However if the warning were to say 'do not do x, y, z otherwise your phone will 100% certainly be hard bricked' - then people would sit up and take notice. Why? Because the warning can be tested.

Hope this is clear.... it's not an issue of trust, or mistrust, at all ! cheers
[Galaxy Note GT-N7000 General] musashiro:
the best description to this is that its like a Roulette, you wont now when you are hitting the bullseye...

i do believe at first that the problem does not exist due to small incidents of brick and most came from LEAK... but once i started reading people who got bricked for wiping on stock recovery, people getting unrecoverable /data and /system partitions, i decided to give up the "amazing" ICS until all problems are ironed out... i flashed GB using pc odin and gave up on chrome beta and nova launcher...

its like choosing between a short usage of ICS and have longer (as for me im just a student and it is a gift) suffering of having a bricked note...

and having GB for a while and wait for a better ICS in the future...
[Galaxy Note GT-N7000 General] clandestino123:
I also did this. But then I couldn't go without ICSbrowser+ so I had to go back !!
[Galaxy Note GT-N7000 General] Chest3r:
Could someone tell he how the hardbrick looks like?

My Phone isn't turning on anymore :eek:
[Galaxy Note GT-N7000 General] musashiro:
can you go to download mode and recovery?? what did you do exactly?
[Galaxy Note GT-N7000 General] Chest3r:
tryed to flash Asylum ICS via CWM, phone turned >automaticly< off while it was trying to flash, bar didn't move at all tough.

Now I can't turn it on, neither CWM nor download mode just a blackscreen...tought it might be the battery (but that should be at least 50% afaik) so i plugged it in but I don't even get the green loading battery screen I'd normaly get.

I'm scared as ****
[Galaxy Note GT-N7000 General] neos_83:
What ROM where you on previously?
[Galaxy Note GT-N7000 General] Chest3r:
King Droid ICS
[Galaxy Note GT-N7000 General] musashiro:
instead of telling the story bit by bit, please enumerate the things you did,
[Galaxy Note GT-N7000 General] Chest3r:
ain't much to tell.

Got ICS Trough Pc Odin on my Note, flashed CF Kernel, Flashed King Droid ICS, Flashed http://xdaforums.com/showthread.php?t=1620625 , tryed a couple of things with apks (replace a couple with AOSP apks), nothing more no system files or something.

Tryed to flash King Droid ICS back, stuck in the Bootscreen.

Tryed to flash another rom.. well Note shutsdown while flashing and doesn't turn on anymore.
[Galaxy Note GT-N7000 General] trahzebuck:
Are your sure about that? No - even slight - differences in the hardware? regarding to the region / country or revision?

There are to be differences. I'm sure sammy tries permanent to optimize their production processes. same way like all producing companies.

beside pebcak I think this could be reason cause some users are hit and the most users aren't.
[Galaxy Note GT-N7000 General] andreww88:
+1

---------- Post added at 09:54 AM ---------- Previous post was at 09:43 AM ----------

Okay, so when you flashed these ROMs, did you wipe data, cache, and dalvik?

The big question we need to know is can you get into download mode right now or recovery? Hold down Volume down + Power + Home. Or Volume up + Power + Home.
[Galaxy Note GT-N7000 General] Entropy512:
It has NOTHING to do with CWM. People HAVE bricked using stock recovery.

Because the I9100 community has been using the I9100 Update4 source code base for kernels for two months without any issues. The ONLY time any I9100 kernel has started causing these problems on devices was when the kernel developer rebased on the SHW-M250L Update4 release - within 1-2 days there were more reports of hardbricks than the entire history of I9100 development previously.

The I9100 Update4 source base is proven by two months of use on Samsung's flagship device without issues. Whenever a "superbrick" kernel comes into play - there's a flood of brick reports, multiple per day. This is NOT NORMAL.

As an example, in the SGH-I777 community (AT&T Galaxy S II), I can only recall 1-2 hardbricks at most from October until April - In both cases, the user had done something incredibly stupid like flash firmware for a completely different device. Then the I777 UCLD3 leak came along and it had CWM repacked into it - within a day or two, at least 5-10 users were hardbricked or had permanently damaged /data or /system partitions, all by doing operations that had been 100% safe for over six months. If that isn't clear evidence of a problem (activities that have been safe for over 6 months suddenly bricking 5-10 users in a matter of days), I don't know what is.

The same goes here - the number of people that have reported eMMC damage since Thursday is higher than the total number of hardbricks for the entire history of this device should be, and almost surely IS higher than the total number of hardbricks over the entire history of this device prior to the first ICS leaks.

Seriously, there have been at least 1-2 new eMMC damage reports A DAY since XXPLY was released, all caused by "normally safe" operations such as wiping in recovery. In normal circumstances, you should only see 1-2 hardbricks a MONTH for a device, and those always can be traced back to the user doing something incredibly stupid and dangerous.

You understate the role of hardware manufacturing variation - after all, don't you think there's a reason there's such a wide variance in how far users can undervolt their CPUs? Same goes for the eMMC chip - it may only be that a small percentage of them are "weak" and susceptible to this problem, or it could be that they are using a different manufacturing variant.

I work for a defense contractor - you wouldn't believe how many times I've seen semiconductor manufacturing variation cause MAJOR problems.