yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] cakoisee:
after i installed ics smoothie rom on my skyrocket, i have problem to shut down the phone or to restart. i have to pull of the battery to shut it down. I love the rom as it has no other problem other than this issue. anybody has same problem here?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] garydv2002:
What version of cwm are you using? I had the same problem and my older cwm was the cause. I flashed cwm touch found in the dev section with Odin wiped cache and dalvick cache and fixed permissions and it fixed my problem
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] chinthekng:
you might wanna try to reflash the rom a bad flash can mess you up in so many different ways
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] occupational_hazard:
Do what Gary says. That's the usual fix.
[Galaxy Ace S5830 Themes and Apps] charlessxavier:
Hello all,

Many of us would get annoyed by the last call cost flash message, that we get in our mobile after each and every sms

And that too specially in India because of the TRAI regulation to show the last call cost to the users after each message and call

Now an Indian developer had developed such a good app to block these flash messages :)

I have been using it for last one week and I can really feel the difference, i need not press ok each and every time i unlock my phone for reading sms from my girl frnd ;)

So, here it is :

Balance Update / USSD blocker

use the matching method as keyword list

keyword list as "last"

use "00:00:00" in the keyword list to block flash messages of SMS alone

This app is not developed by me, so i wont take responsibility if you ever mess and do anything wrong
[Galaxy Ace S5830 Themes and Apps] sarat_mit:
SO wat if i got a message from some one, having the word last.......?
[Galaxy Ace S5830 Themes and Apps] charlessxavier:
u mean flash message ?

well.. I actually found out a new way to block the flash messages for SMS alone.. as people would like to get flash notification for last call...

use "00:00:00" in the keyword list

none of your frnds would actually send a flash message with 00:00:00 ;) and if you want to block both call and sms last call notification u can use "00:00:"

by this way, u can block the flash notification for SMS alone.. and you would get it for calls :)
[Samsung Galaxy Nexus] Lost Dog:
I ran in to an issue today.... I used CWM (Touch recovery 5.8.0.2) to backup my system then flashed the latest CM9 nightly. I was getting some force close issues so I tried to revert back to my backup. I got an "error restoring /data" and the restore stopped.

After looking in to it I think the issue may be the /data backup is over 2 gigs. CWM (or busybox?) has an issue with this and cannot restore (or maybe the way the tar archive is created gives the problem). I've read some people trying things like:

I tried this but got the error:

/data/media # tar xvf data.ext4.tar.001 -C /
tar xvf data.ext4.tar.001 -C /
tar: invalid tar magic

Help! How can I restore my backup?

I even tried some earlier backups but they all had the same error with /data.

Thanks!
[Samsung Galaxy Nexus] WiredPirate:
I have heard bad things about touch recovery.:( have you tried restoring your backups with regular CWM?
[Samsung Galaxy Nexus] Lost Dog:
Yeah, I gave that a try and no luck... I think the tar used in both touch and non-touch have the same 2gig limit.

Would it be possible in adb to delete the /data then push the untared /data from my computer to the phone? The file untars fine on my desktop system.
[Samsung Galaxy Nexus] Jubakuba:
And this is why I switched to TWRP recovery.

Compression allows the backup to be less than 2 gigs...and it works.

Personally, I'd skip all that...

Just wipe all data.

Install the rom you're trying to restore data for...

And use titanium to restore app data from the nandroid.
[Samsung Galaxy Nexus] Lost Dog:
Yeah, I'm leaning that direction. I'm just really annoyed that they nandroids are sitting there but I'm being confounded by the tar functionality. I'll be switching to TWRP myself.
[Samsung Galaxy Nexus] flatflo:
When you want to install or send some data to your new rom, you can use "nandroid browser" from the store

https://play.google.com/store/apps/...dvZGRjaGVuLmFuZHJvaWQubmFuZHJvaWRicm93c2VyIl0.
[Samsung Galaxy Nexus] Hydera5:
With TWRP can you restore backups that were made in CWMR?
[Samsung Galaxy Nexus] Lost Dog:
I'm almost thinking this is not something to blame on CWM. If CWM makes a call to tar (in busybox) then it's the busybox version of tar that has the issue.

I was able to get my CWM /data backup back on my phone. I made two copies of /data. I opened them up in 7zip and split them in to two archives (deleting the first half of one and second half of the other). I then restored by doing:

tar xvf data.ext4-1.tar -C /

tar xvf data.ext4-2.tar -C /

(I had tried this earlier but I think I corrupted my tar archive which is why it was giving me the error).

Using the busybox (from CM9) and trying the same thing on the full 2.6GB tar archive I'd get an error stating "Value too large for defined data type". From what I've read this may be a result of how tar (in busybox) was compiled.

The funny thing is I'm getting the exact same problem in TWRP if I don't use the compression option and the /data backup is greater than 2GB! Using compression I'm at 1.6GB and everything is fine.
[HTC Rezound] freak2431:
tell me what you think

good or bad

and any ideas how i can make it better
[HTC Rezound] reggie cheeks:
Um... good.
[HTC Rezound] dyetheskin:
not bad
[HTC Rezound] trickster2369:
Looks good, though I don't care for the flames on HTC.
[HTC Rezound] lextex:
What is this for? Is it to replace that annoying white screen that says HTC in green letters?

I modded my wife's Rezound last night, so I'm just now getting acquainted with all of the different tricks.

As for the design itself... don't quit your day job? :P
[HTC Rezound] Watercycle:
I don't care for the flames on HTC or the "abstract" looking Rezound, but still nice :p
[Android Q&A, Help & Troubleshooting] ri123:
Please can someone tell me how to root htc explorer without voiding warranty:(
[Android Q&A, Help & Troubleshooting] SifJar:
Can't be done. The only way to root the Explorer is by unlocking the bootloader.

[I think this is something to do with it being S-ON, meaning that /system can't be mounted as writable while Android is running, so the su binary can't be put into /system/bin, as it needs to be.]
[Android Q&A, Help & Troubleshooting] Theonew:
Rooting the explorer is possible: http://xdaforums.com/showthread.php?t=1415223, but your warranty will be voided. There is no way to "root a device without voiding the warranty", because the process of rooting voids the warranty (no matter how its done).
[Android Q&A, Help & Troubleshooting] SifJar:
Technically, perhaps true. But on many devices, root can be reversed leaving no evidence the device was at one point rooted. And therefore manufacturers of said devices will honour the warranty in these cases.
[Android Q&A, Help & Troubleshooting] zelendel:
Which is fraud.
[Android Q&A, Help & Troubleshooting] whoqwerty:
Search before you post something stupid as this
[Android Q&A, Help & Troubleshooting] SifJar:
I see nothing morally wrong with what I suggested. Provided the defect was not caused by the root in any way (e.g. custom kernel with OC causing hardware damage or whatever), I see no valid reason for the manufacturer not to honour the warranty, and I reserve every right to make them do so. If they ask me if it was rooted, I would tell them yes it was.

The whole thing is irrelevant to me, seeing as I have an HTC Explorer, which requires an unlocked bootloader to root, and that can't be undone without leaving glaring evidence that is has been done, but that is besides the point.
[Android Q&A, Help & Troubleshooting] zelendel:
No I guess you wouldn't.

As stated above a search will tell the OP what they need to know.

Thread closed
[Galaxy Note GT-N7000 General] sjkoon:
http://opensource.samsung.com/

YEAH!! Go go go Custom Kernel!!

EDIT :

MIRROR!

http://www.mediafire.com/?y14t9y9j661jmt3

is alright?
[Galaxy Note GT-N7000 General] lionelia:
I have made a request to Samsung for having N7000 ICS sources.

Did it yesterday got it today.:)
[Galaxy Note GT-N7000 General] nandihno:
This is great yes the ics is there so this means we may know why the bug gets triggered
[Galaxy Note GT-N7000 General] ukicar:
finally. ... hopefully that bug will be solved
[Galaxy Note GT-N7000 General] plsoft:
Itching to flash safe roms LOL
[Galaxy Note GT-N7000 General] chasmodo:
It downloads at spectacular 10Kb/s. :mad:
[Galaxy Note GT-N7000 General] sjkoon:
http://www.mediafire.com/?y14t9y9j661jmt3

is mirror :D
[Galaxy Note GT-N7000 General] androidindian:
Thanks mate. added in the thread in dev section too if its ok :)
[Galaxy Note GT-N7000 General] Teren49:
Downloading at 578KBps at the moment from official site :D
[Galaxy Note GT-N7000 General] Ducati87:
Great news! I'm downloading it! Hope to see something cool! :D
[Galaxy Note GT-N7000 General] cletusarrarr:
Update 3 is out of the source code :D i guess thats the only one , now hope we can get going on the custom kernels :)
[Galaxy Note GT-N7000 General] spiral5:
No problem for me downloading at 416KBps at the moment.;)
[Galaxy Note GT-N7000 General] sharan.mu:
Wow soo funny.. anyway thanks
[Galaxy Note GT-N7000 General] jaiiscool:
Bump

For bringing it on top.

Other threads have been locked.
[Galaxy Note GT-N7000 General] tsk1979:
So what does it mean for users.

Does it mean that ROMs like CM9 will start supporting everything like S-Pen, FM radio etc.,?

Or does it mean we will see slightly modified versions of stock roms. For example touchwiz removed, but swype there.
[Galaxy Note GT-N7000 General] jaiiscool:
All of above +

Awesome custom kernels from devs.

Not sure about FM Radio though....
[Galaxy Note GT-N7000 General] chasmodo:
You are going to see a lot of different Roms once we have several safe custom kerenels.

CM9 will always remain lean and Samsung-free, but there'll be lots of CM9-based hybrid Roms catering for everybody's needs. Also, a lot of TW-based Roms.

I suspect that our Dev will soon start to look like SGS2 one:

http://xdaforums.com/forumdisplay.php?f=1058

http://xdaforums.com/forumdisplay.php?f=1204
[Galaxy Note GT-N7000 General] kandem:
Yeahh! Im wainting for speedmod kernel and and update of stunner rom

Enviat des del meu GT-N7000
[Galaxy Note GT-N7000 General] k1ng617:
So does this mean this source is really old or maybe really new?
[Galaxy Note GT-N7000 General] mFlorin:
I hope kernel devs sees this and take into account: best feature of a kernel will be dual-boot mode, like siyah's kernel for SGS2 :X
[Galaxy Note GT-N7000 General] k1ng617:
Hopefully they corrected the emmc issue since it's been recently exposed
[Galaxy Note GT-N7000 General] ahenderson223:
This is great news!!!!
[Galaxy Note GT-N7000 General] GocaS6:
Well there you go our beloved developers you've got official ICS ROMs, you've got open source kernels, basically you have everything that you want it, so now make us couple of mind blowing Roms and we'll donate lots of :beer: :):)!
[Galaxy Note GT-N7000 General] GocaS6:
Ok they're different but how can we know for sure Arobase :)?
[Galaxy Note GT-N7000 General] Entropy512:
Many of the differences are due to the fact that the I9100 Update4 release was comprehensive and had stuff for many devices - even unreleased ones. Most of that stuff was removed from the Note release. (Such as, for example, all of the defconfigs)

Nope, still there. Absolutely DO NOT run kernels built from unmodified N7000 Update3 source.
[Galaxy Note GT-N7000 General] lagittaja:
I'm sorry for a tad stupid question but I don't know much about kernels myself.

How will this affect us, the end users? Will our awesome devs be able to make even better ics roms now that the source for the kernel has been released?
[Galaxy Note GT-N7000 General] JoshuaTumanda:
Pretty much yes! We'll see stable custom ROMs and bug free kernels. From the official source code, it'll give us brighter future for our note and brick-free devices.
[Galaxy Note GT-N7000 General] dannstarr:
Ok, so as a kind of experiment for myself, here I am providing you with another download site for this file.

I say experiment because it's the first time I have tried something like this, but it is something I am hoping to be able to do a lot more of, in an attempt to help the XDA community.

Please use, and advise me of any issues:

Link
[Galaxy Note GT-N7000 General] :
Cool. I am new to source code, did some googling and searching but was unable to find versioning in the source. Anyone know if its version 25 and not 19, which has the bug?

Anyone know of a good tutorial on jow to work with the source? All I found are pretty technical, plus in this day and age cannot fathom why there is so much 1970 command line crap to it lmao serious respect to the devs, just the hours they put in to find stuff out. Its amazing
[Galaxy Note GT-N7000 General] erichbitch:
Wow im very happy now !

I feel so naked without fully working CWM.

There are so many awesome ROM concepts (Stunner, CM9, PPARANOIDANDROID) which are very promising !

I have no experience with such things, how long does it take at xda until custom kernels appear?
[Galaxy Note GT-N7000 General] chasmodo:
I'd say give the kernel guys at least 10-14 days to produce the goodies.

Kernels are sensitive stuff, they can brick your device, hence they need to

be thoroughly tested before they are released.
[Galaxy Note GT-N7000 General] dannstarr:
No, its the exact same file
[Galaxy Note GT-N7000 General] friedje:
If you confuse the kernel version with the firmware version of the mmc controller,

then better let other do the dev work and just enjoy their result ;)
[Galaxy Note GT-N7000 General] DJsCrIBbLe:
So even tho Samsung or whoever was aware of the eMMC bug they didnt fix for source ?
[Galaxy Note GT-N7000 General] chasmodo:
I'd have to reconsider what I'd said if you agree with me.
[Galaxy Note GT-N7000 General] andreww88:
That's crazy that the bug is still there. It's like Samsung WANTS to keep it there to make more money on these bricks. Ugh!
[Galaxy Note GT-N7000 General] andreww88:
It isn't free of charge to everyone, I heard though....
[Galaxy Note GT-N7000 General] Entropy512:
The eMMC fwrev has NOTHING to do with the kernel itself.

You need TWO things for Superbrick:

buggy fwrev 0x19 AND a kernel that triggers the bug

The eMMC firmware currently cannot be changed - what you have is what your device shipped with, and that is 0x19 for every Exynos device anyone has checked so far

The kernel can be changed to not trigger the bug - but this source definitely still has MMC_CAP_ERASE enabled

It's not the first kernel/source that Samsung has let loose with the bug trigger - SHW-M250S/K/L devices are also affected.

Nope. Seriously - they've been aware of this since before they started ICS development for this device, as it was discovered initially with Galaxy Nexus PROTOTYPES. As in - prior to November 2011.
[Galaxy Note GT-N7000 General] Latoc:
But didn't you say that it was also enabled in GB kernels ?

And that GB kernels strangely presented no risk even with it enabled ?

Maybe it's enabled but not dangerous because they changed something else ?

Maybe you already checked that, and then what I'm saying is meaningless and useless...

EDIT: one more question: is it even possible to know if the mmc cap erase command is executed like in GB and thus not dangerous or will you have to eliminate it entirely ? Because it's supposed to improve performance so if it is applied safely in this kernel then maybe it is not bad to leave it ?
[Galaxy Note GT-N7000 General] :
Entropy seriously... Samsung deserves a big FACEPALM for releasing sources and still knowing that it would bricks it's customers devices!

This is the biggest facepalm i've ever seen!

Btw, SGS2 also had this problem? Or only SGNote and the other devices you said?
[Galaxy Note GT-N7000 General] trell959:
Yes. The Note, E4GT, SHW-M250S/K/L devices, and at&t galaxy s II (i777) are effected. I don't know about the i9100, however.
[Galaxy Note GT-N7000 General] nandihno:
so most likely the Samsung S 3 might have it aswell.

Wondering what Steve K thinks of all this...he is a Kernel guy it will be interesting to hear his input on this
[Galaxy Note GT-N7000 General] musashiro:
I can see a lot of legal concerns if the s3 ships with the "t-virus" haha
[Galaxy Note GT-N7000 General] nandihno:
its bit shame that major blog sites (Engadget, Android Central, TwiT) have not heard us...

again they did hear the HTC One X crowd ...maybe cuz thats the hot phone of today.

..have to say though that

i went from CM9 to GB to LP9 (after LP9 appeared i went to stock recovery and did a full wipe data and cache) and booted successfully.

I then didnt like LP9 was bit choppy and sound wasnt that good...so went from

LP9 to GB (wipe cache/data) then from GB to LPF (wipe cache/data)

maybe because i dont have much in my SD card? well

4.26 GB ?
[Galaxy Note GT-N7000 General] :
Well the only bricks i heard of were on ICS leaks on Angelom kernels and Siyah RC6!

Have no idea also!!

I'm on Asylum 05 waiting for the bug to be corrected..
[Galaxy Note GT-N7000 General] Latoc:
Mince t'as raison, j'avais pas vu ça sous cet angle ;)
[Galaxy Note GT-N7000 General] senectus:
Find the original reason for Entroy's reply, the post he was replying to was asking which kernel version this source release is and if it contained the bug.

The bug isn't in the kernel, its in the EMMc Firmware that we all have. The Kernel contains a call that triggers the bug.

New kernel wont erase the bug, but it *might* if we're lucky and guys like Entropy are clever enough, find a way to not have the trigger in it to fire the bug off.

It looks like we'll have the bug forever...
[Galaxy Note GT-N7000 General] Latoc:
So it looks like if we want to be safe and have a stock rom then we have to stay on Gingerbread for ever :(
[Galaxy Note GT-N7000 General] PoisonWolf:
Has anyone checked the emmc firmware of 32gb notes?
[Galaxy Note GT-N7000 General] ckhnet:
this is great
[Galaxy Note GT-N7000 General] beestee:
There is an emmc firmware fix samsung is working with internally from what I have gathered from the PSA stickies, but the issue is that it is difficult to apply for end users. It would involve a low level flash on the device, known as JTAG i believe, which requires hardware and know-how that is typically only available at service centers.

I am positive that as costly as the prospect of a recall would be on the how many millions of devices that are affected now, it is most likely the only way to truly fix the problem officially. But due to that cost it seems samsung would be more likely to just issue kernels that work around the problem by simply avoiding the problematic function.

This means that the GS3 should NOT have this bug at all.
[Galaxy Note GT-N7000 General] trell959:
Because we can fix the kernel to keep it from triggering the bug.
[Galaxy Note GT-N7000 General] Entropy512:
I9100 has the bad firmware in the eMMC chip, but never had an affected kernel that triggered the bug released. (Except Siyah 3.1rc6 - which was based off of SHW-M250L sources)

As I've said - I don't know how Gingerbread rendered MMC_CAP_ERASE safe, but I'm fairly positive that outright disabling it will make a kernel safe. (Which is why I9100 Update4 is safe - it's completely disabled in the MSHCI driver.)
[Galaxy Note GT-N7000 General] Entropy512:
Try reading ALL of the research, instead of picking and choosing what you want to hear.

It's stated very clearly WHAT the bug in fwrev 0x19 is - it doesn't handle eMMC command 38 (ERASE) well.

SO - if you don't fire ERASE commands at it, it's safe.

It may be possible, if you fire ERASE commands at it in the right order, to be safe (this is one of two possibilities for why Gingerbread kernels are safe, the other being that even though MMC_CAP_ERASE is set in the driver, something else is blocking the ERASE command from being sent.)

What do we know about I9100 Update4? The driver does not set the MMC_CAP_ERASE flag. So the kernel will never send an ERASE command to the kernel.

And I NEVER stated that N7000 sources would be a direct fix. In fact, I was sure that they would be just as dangerous as the kernels.

But that's the point of source code - when you have source code for a kernel that is safe but doesn't quite support your hardware correctly (see DAFUQ - safe but broken wifi, no video hwaccel, busted speakerphone), and a kernel that is dangerous but supports all your hardware features - with time you can mix and match and get a kernel that is both safe and supports everything.

N7000 source isn't a miracle magic bullet that fixes everything immediately. However it's the prerequisite to even having a hope of creating a kernel that is safe AND fully functional for N7000.

As to Snapdragon devices - they're unknown. However it was confirmed that the SGH-I717 (AT&T Galaxy Note) appears to have eMMC fwrev 0x25, which is safe. It seems that only Exynos devices were ever shipped with fwrev 0x19. Of course - this could change, a new discovery could be made, but I suspect if any of the other Snapdragon-based Samsungs were affected, we'd have heard something about it by now.
[Galaxy Note GT-N7000 General] will5:
Can we have CIFS support now? :)
[Galaxy Note GT-N7000 General] k1ng617:
Entropy, thanks for all the hard work and also for the heads up early on. Had it not been for your warnings my no warranty Note might not be alive.

Honestly, this whole fiasco has left a sour taste in my mouth. Samsung lost what little faith I've had left in them since my 10 month old Samsung TV failed last year and required home repair. Now this emmc bug that they were well aware of and apparently don't care enough about to fix before sending it out to end users. Honestly, as much as I enjoy my Note, I might try HTC or just go back for a third Motorola (awesome quality/durability IMO) for my next phone.
[Galaxy Note GT-N7000 General] senectus:
I do wish they'd be more open about this bug... fess up and say "we're working on it".

Just confirmed I have the 0x19 FWVer and am on the stock ICE from Open Germany.

I suspect I'm operating on borrowed time, but I really don't want to go back.

Hopefully I can survive till a fix come.
[Galaxy Note GT-N7000 General] :
Where can I find mine? Lol
[Galaxy Note GT-N7000 General] senectus:
You mean how do you find out what FWVersion you have?

http://xdaforums.com/showpost.php?p=26349717&postcount=57
[Galaxy Note GT-N7000 General] erichbitch:
Damn it, i have 19 too :(

Thanks to captainhakan for the short instruction !

I think i will go back to GB pretty soon, its too dangerous.

Or will Samsung also repair rooted devices free of charge since it is a eMMC bug combined with a corrupt kernel from samsung?
[Galaxy Note GT-N7000 General] dchkchung:
I hear everyone complaining on the bug from Samsung. Personally, all of us still manage to use Samsung phone on a day to day basis. With the kernel released, does that mean that coders can start removing bloatware like touchwiz while retain stuff like My Story, SNote etc.

This GNote ICS released still has lots of room for improvement in terms of speed and battery life. Expecting great work from the coders.

Thanks in advance.
[Galaxy Note GT-N7000 General] jonpaslim:
I type the command (su) and then i enter, after that i type the command (cd/sys/class/block/mmcblk0/device) and then i enter, then it said (not found). Pls help. Thanks
[Galaxy Note GT-N7000 General] honf:
the command should be "cd sys/class/block/mmcblk0/device"
[Galaxy Note GT-N7000 General] jonpaslim:
Thanks for your help and I found out I have 19 emmc.
[Galaxy Note GT-N7000 General] erichbitch:
i had to type it path by path:

cd sys/

cd class/

cd block/

cd mmcblk0/

cd device

I tried exactly that full patch for 3 times.

No matter what, i think 95% will have 19
[Galaxy Note GT-N7000 General] ZeCoder:
If they are aware of the problem, they must not release/continue to release kernels that trigger it. As simple as that.

What possible reasons the may have?