yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] Jamesyboy:
Yep...the liquidsmooth website @ liquidsmooth.net is showing up completely blank, and the goo.im extras link leads to a theming page with launcher configs, widget suggestions, and wallpapers.

Does anyone know where I can find, or have a copy...of the MMS/SMS fix?
[AT&T Samsung Galaxy Note I717] MoJoe277:
LiquidSmooth Team, I don't know where y'all are at with getting a bootable kernel for 4.2, so I thought this news could he useful.

XDA dev. JamieD81 has successfully developed a working kernel for 4.2. Here is his thread. I hope this is helpful.

http://xdaforums.com/showthread.php?t=1686320
[AT&T Samsung Galaxy Note I717] Jamesyboy:
Issue solved. Is there any way I can get this post removed? If not...I'll be back soon to contribute to the project.
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Must say this is smooooooth so far and snappy.......notification background flickers a little ......

---------- Post added at 06:13 AM ---------- Previous post was at 05:50 AM ----------

Alright ...Google now won't stay open .....any fixes or I'm moving on to another ROM
[AT&T Samsung Galaxy Note I717] prbassplayer:
Locked due to OP's request

Moderator

prbassplayer
[AT&T Samsung Galaxy Note I717] skinblues:
Downloaded but not installed. If they're corrupt than I'll just wait it out until they're up again.
[AT&T Samsung Galaxy Note I717] RCranium666:
Why is the file size so small compared to Padawan ics rom?
[AT&T Samsung Galaxy Note I717] charlesthedestroyer:
because this is bare basics of jelly bean, it doesnt even come with the playstore. While padawan comes with a bunch of stuff.

Flashing right now with latest jb gapps, not liquid gapps, because the link was down. I love slow days at work. I will report back later
[AT&T Samsung Galaxy Note I717] skinblues:
It's also 29 MB smaller than RC7, but the addons are a separate 18 MB file. Maybe they were included for RC7. Overall, the sizes seem fine.
[AT&T Samsung Galaxy Note I717] taob:
I suspect there is a difference, but whether that difference is the cause for the various problems people might have is a different question. I don't think TB goes through the package manager when restoring an app. It simply copies (to my knowledge) the .apk back into /data/app. Restoring data copies back the appropriate subdirectory in /data/data . If you look in your TB backup folder, you'll see three files associated with each backup instance: the APK, the tar file with the /data/data directory structure, and a properties text file.

I can see how simply re-copying the files might cause problems whereas running through the installation process (which may or may not involve an installation script and tweaking some system databases that Package Manager normally handles) is the "official" method. But I don't know if that's merely correlation, or if actual causation has been established. I think the warning is more of a cover-your-ass approach, since in most instances we simply don't know. So to be safe, we are told to not use TB, even though it might not be causing any problems. My approach has been to restore only user app+data with TB. If there is a problem, I will uninstall the app and reinstall from Google Play to see if that makes a difference.

For example, I'm seeing a problem with the Liquid Launcher with RC8. If I try to install any widget, the launcher crashes. I don't know if this was a problem with RC7, since I was using GO Launcher EX and I could add widgets to it just fine. I uninstalled the widgets in question (HD Widgets and Agenda), reinstalled from Google Play, and the problem persists. Even the built-in analog clock widget is causing Liquid Launcher to crash, so I'm pretty sure this isn't because I restored my other widgets with TB. But just to be completely sure, I'm wiping everything and starting over to see if it makes a difference.
[AT&T Samsung Galaxy Note I717] charlesthedestroyer:
I am experiencing the same crashes with widgets. I wiped dalvik, cache, system and I restored no apps.
[AT&T Samsung Galaxy Note I717] taob:
Liquid Launcher crashes when adding widgets

Confirmed the problem with adding widgets. I did a factory reset, logged back into my Google account, but did not even visit the Play store. Tried adding the default analog clock widget to Liquid Launcher. Crash. Tried adding the default power control widget. Crash. Anyone else getting this? Let me install QuickSSHD so I can at least login to the phone and grab a logcat...
[AT&T Samsung Galaxy Note I717] mangiant:
Installed successfully for me (clean install from stock touchwiz).

No crashes, all is well except for 1 thing so far:

Sorry if this has been answered already, but I can't set google now settings. When I select "settings", a "google now has stopped working" dialog pops up and very quickly disappears.
[AT&T Samsung Galaxy Note I717] Bataga:
Still fc when opening display in settings. Can't set to landscape
[AT&T Samsung Galaxy Note I717] omariscal1019:
Its aweso.e download and install this morning... havent had a reboot... the keyboard heptic feedback is awesome...

So satble and fast... lovin it..
[AT&T Samsung Galaxy Note I717] k03703:
I'm having the same problem with HD widget, when try to add to main screen it FC. I also did factory reset and wipe system to do clean install.
[AT&T Samsung Galaxy Note I717] leo5111:
im not saying its this rom that did it, but it was this rom it happened on, i went into recovery wiped everything including internal storage did a factory reset then installed this and super gapps, phone did the reboot vibrate bump but never came back up to even the samsung logo now it acts like its dead, odin doesnt see it and connected to pc it randomly sees my sd card but it appears and vanishes and wants me to format it, so im currently trying to de-brick my phone :(
[AT&T Samsung Galaxy Note I717] Mauijpm:
Did you do a MD5 check before flashing the ROM?
[AT&T Samsung Galaxy Note I717] leo5111:
no i didnt but i have the file on my pc says for at&t galaxy note
[AT&T Samsung Galaxy Note I717] Mauijpm:
Download a free MD5 checking program and make sure your file's MD5 matches this: fa1c49b9b0536de7efd3d558f4bcfad7

If it doesn't that means your download that you flashed is either incomplete or corrupt.
[AT&T Samsung Galaxy Note I717] leo5111:
doesnt match there was talk originaly about it being corrupt or incomplete but that was earlier before i downloaded it
[AT&T Samsung Galaxy Note I717] Mauijpm:
Can you get the phone in download mode?
[AT&T Samsung Galaxy Note I717] Jmelendez1:
Same here. Dont know what went wrong here but im officially bricked. Dead as a door nail. No download mode.
[AT&T Samsung Galaxy Note I717] leo5111:
welcome to the club :eek:

---------- Post added at 03:06 AM ---------- Previous post was at 03:05 AM ----------

i tried with button methods and it would appear i cant get into download mode screen does not even come on

---------- Post added at 03:26 AM ---------- Previous post was at 03:06 AM ----------

before the flame throwers come out i looked at file still on my pc says for i717
[AT&T Samsung Galaxy Note I717] digitalcrash:
What recovery were you using?
[AT&T Samsung Galaxy Note I717] ricco333:
Up and running good, the widgets do cause the stock launcher to FC but switched to apex and is all good, I flashed the 4.2 gapps from Truth77 and Google Now works great. The only thing I'm missing is the option under display to make the font small, medium or large; it was there on RC7.

Other than that is a solid ROM.

Erik
[AT&T Samsung Galaxy Note I717] leo5111:
http://xdaforums.com/showthread.php?t=889128 if you want to try it i did that with my captivate made a usb jig cost like 3 bucks see if it will go into download mode with that

---------- Post added at 03:34 AM ---------- Previous post was at 03:33 AM ----------

newest twrp
[AT&T Samsung Galaxy Note I717] Jmelendez1:
I actually have one of those off of ebay but doesnt do anything.:(
[AT&T Samsung Galaxy Note I717] digitalcrash:
Damn it sounds like the superbrick bug but I thought they removed the emmc cap erase
[AT&T Samsung Galaxy Note I717] Mauijpm:
Sounds more like bad downloads that weren't checked (MD5) and whatever was missing in the zip bricked their phones. Not trying to sound like a jerk, but I just don't think the superbrick bug has anything to do with this as that was focused on the international Note and not the AT&T version. I downloaded the ROM, checked the MD5, wiped and flashed, and I haven't had any issues at all.
[AT&T Samsung Galaxy Note I717] digitalcrash:
I've bricked two s2 with the bug before it was discovered when ICS first dropped and there is barely any kernel development for this phone. And got the same result he is having.

From the Moderator, when stating you bricked your phone... please provide ALL the information of what you did to make this happen, it sounds like you never did a md5 check..... so the bricking you are talking about is a result of you failing to do your homework BEFORE flashing...... but in order for anyone to help you...... you have to provide a complete picture of what you did ..... otherwise you post is just for griping value only........ ~~ oka1
[AT&T Samsung Galaxy Note I717] taob:
Display settings always FCs now. It was working fine from the main Settings window in RC7, but it would crash if invoked from the Liquid Splasher section. I see it has been removed from there, but now Display crashes every time I try it. :(

I'm seeing a lot of Google Search FCs, perhaps related to Voice Search. Voice dictation works, but then FCs when I'm done. Google Now comes up initially, but then FCs if I try to initiate a voice search.

---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------

You may have downloaded the correct file, but it looks like it is either corrupted or incomplete. My first try a downloading the addons and gapps ZIPs also resulted in truncated files. I restarted the downloads, and they came through fine the second time.

Make sure your ZIP file is intact before flashing it. Try opening up the archive, or better yet verify the MD5 checksum.
[AT&T Samsung Galaxy Note I717] Mauijpm:
The S2 has nothing to do with the Note. There isn't much kernel dev for this phone because JB source isn't released. DAGr8 has a kernel for this phone, CM has one, and so does Flappjaxxx.

I understand your result was the same (a hard brick), but flashing incomplete files can brick a phone. Just stating that it is the superbrick with no corroboration will just cause unnecessary fear in the thread.
[AT&T Samsung Galaxy Note I717] Jmelendez1:
I'll head on over to the store tomorrow and get it replaced. I should be good cause the phone wont power on at all.
[AT&T Samsung Galaxy Note I717] leo5111:
mine is coming via fedex tomorrow, anyone know what they use for return shipping?
[AT&T Samsung Galaxy Note I717] Mez-Jr:
this feature from RC7:

◘ Addded group mms threading - viekvanasani

does not appear to be in RC8

Am I missing something?
[AT&T Samsung Galaxy Note I717] Raleran:
Where did you get this md5 from? I don't see it in the original post.
[AT&T Samsung Galaxy Note I717] ricco333:
There were a lot of download links in the Facebook page, everyone needed to make sure that the downloaded file was the one that said Quincyatt I downloaded it from my phone using the browser and flashed with 4.2gapps and did not have any troubles, didn't check any md5s either.

Erik
[AT&T Samsung Galaxy Note I717] taob:
The original post has been edited, and the download links are on the Facebook page for now. The ones we are interested in:

Liquid JB v2.0 RC8 (QUINCYATT)*

SIZE: 98 MB

MD5: fa1c49b9b0536de7efd3d558f4bcfad7

MAINDL: http://bit.ly/PWYXxZ

LIQUIDS JB GOOGLEAPPS: http://bit.ly/QJCiGP

MD5: 9fe09935527a2c4aa739a181bf301a38

LIQUIDS JB 4.2 ADDONS: http://bit.ly/W9RCJx

MD5: c3d6cc3ed28ea626c2305d2c9ea3aa37

LIQUIDS JB WALLPAPERS: http://bit.ly/U2dbOA

MD5: a34ed96cd3bf36e8aa421e08a70bfe5c
[AT&T Samsung Galaxy Note I717] ricco333:
Ok, so other than a couple of reboots during calls everything else is working fine, but reboots are happening in every single CM10 based ROM now so not a reason to complaint, will see how it goes and change to the kk.12 kernel if the reboots continue. The ROM is pretty good.

Erik
[AT&T Samsung Galaxy Note I717] taob:
Based on their comments on the Facebook page, it sounds like the developers are well aware of the issues people are having with RC8, and not just on the Note. I'll see how it goes today, but I may roll back to RC7 until RC9 comes out. And I'll let others play around with it first. ;)
[AT&T Samsung Galaxy Note I717] yongh:
Why. Every time I press the back button and that kill my app instead go back, any help?
[AT&T Samsung Galaxy Note I717] erad1:
There are too many red flags on this...I'm glad I waited to flash. Maybe I missed something but why the new thread? and where is DaGr8 (I mean is he ok)? The op has responded to the issues in the other Liquid device threads but not here other than a redirect? and personally I would rather see a changelog before flashing not after (and a dedicated Note dev)...I feel bad for the guys that bricked as it looks like they each had enough experience at flashing...sure it could have been bad downloads as they (liquid) admit server troubles...but with so many devices (18) under one ROM it could've been a misplaced file too!
[AT&T Samsung Galaxy Note I717] twopumpchump:
What about ADB? Can you connect to your pc with it? Can you manually put it into recovery by removing the battery and pressing the volume button? I don't see how you can be hard bricked by just flashing this rom...if you flashed the correct one for your device.
[AT&T Samsung Galaxy Note I717] taob:
Rolling back to RC7 for now. It seems RC8 just gets slower and slower the longer it runs. It took over two minutes for it to boot, and not because it had to rebuild the Dalvik cache! While screen transitions and window animations are usually smooth, everything else seems to lag: reaction to screen taps, launching apps, even response time while typing on a command line. I do like the 4.2 camera with RC8, so I'm going to try flashing the addon ZIP with RC7 and see if that works.
[AT&T Samsung Galaxy Note I717] delock:
Can we use the wallpaper and addon with rc7?
[AT&T Samsung Galaxy Note I717] taob:
I don't use the wallpapers, but they are just JPEGs, so they should work fine. I just flash RC7, left all my user apps intact. I then flashed the RC8 addons (for the Photosphere camera and 4.2 keyboard) and also the RC8 gapps (for the Photosphere viewer). I had to clear the data for the built-in Clock app, or else it would crash when bringing up the alarm clock ("android.database.sqlite.SQLiteException: Can't downgrade database from version 7 to 5"). But since I'm running the RC8 gapps, voice searches will crash as described earlier in this thread. I'm going to try disabling GoogleQuickSearchBox.apk and installing the version that's on Google Play to see if that helps.
[AT&T Samsung Galaxy Note I717] Jmelendez1:
Thank you. I now realize what i did wrong. Oh well, just got my replacement from the store. :D
[AT&T Samsung Galaxy Note I717] taob:
Yep, that trick seems to have worked with GoogleQuickSearchBox.apk. The odd thing is, I compared the two APKs and they are identical (same MD5 checksum). The only difference is that one lives in /system/app while the other is in /data/app. Don't know why that should make a difference, but it does.
[AT&T Samsung Galaxy Note I717] k03703:
Hi can you use the 4.2 camera to record video and verify the video playback works? I've been trying to install it on my phone and everytime I record video it always display garbage. Thanks :)
[AT&T Samsung Galaxy Note I717] leo5111:
last time i will mention this when my replacement note came i stuck my sd card in and looked and it was for the at&t Note :good:
[AT&T Samsung Galaxy Note I717] taob:
No, it doesn't work. Rather, video playback works fine, but the 4.2 camera app does not actually save the video file to flash. So there is nothing to play back. It thinks it did (you can even see the filename), but there is nothing there.
[AT&T Samsung Galaxy Note I717] k03703:
ThanKs for trying
[AT&T Samsung Galaxy Note I717] csrohena:
Same problem here... After flash, phone is acting dead.. Any suggestions? Thanks.
[AT&T Samsung Galaxy Note I717] taob:
Pull out the battery, put it back in, hold down both ends of the volume rocker, hold down power button for several seconds... does the phone still boot into recovery?
[AT&T Samsung Galaxy Note I717] 2sl0w:
Flash gapps and liquid addons.
[AT&T Samsung Galaxy Note I717] severinca:
It says my SD card is damaged even tho it worked on my other rom
[AT&T Samsung Galaxy Note I717] MoJoe277:
Anyone having a good experience on this ROM? Seeing only negative comments so farv which has kept me from flashing.
[AT&T Samsung Galaxy Note I717] severinca:
Everything is good for me except my sd
[AT&T Samsung Galaxy Note I717] SayWhat10:
did you get your phone back up and running yet?
[AT&T Samsung Galaxy Note I717] Mauijpm:
I am having a phenomenal experience on this ROM. I woke up the day it was released, downloaded it, did a MD5 check and just wiped cache and dalvik before flashing (I was on RC7). I haven't had any issues. I haven't had any force closes. Maybe 2 or 3 total reboots. Not a big deal. I flashed JusTunBean's inverted Gapps as well. This ROM has truly made my Note awesome. :D:good:
[AT&T Samsung Galaxy Note I717] csrohena:
Tried and nothing... it's not even getting power from the usb cable.

---------- Post added at 04:48 PM ---------- Previous post was at 04:43 PM ----------

I will...as soon as I find the way to boot up the phone. Thanks.

---------- Post added at 05:08 PM ---------- Previous post was at 04:48 PM ----------

I will...as soon as I find the way to boot up the phone. Thanks.
[AT&T Samsung Galaxy Note I717] jpcdeux:
Download mode and Odin back stock? This seems to be plagued with issues
[AT&T Samsung Galaxy Note I717] erad1:
Edit...deleted
[AT&T Samsung Galaxy Note I717] taob:
Maybe standards have dropped, but "maybe 2 or 3 total reboots" in the span of a few days should be a pretty big warning flag. Spontaneous reboots should never happen. When they do, there should be some sort of diagnostic provided by the phone to help track down the problem. On a phone with healthy hardware and stable kernel, userland apps should not be able to cause an unwanted reboot. My phone rebooted twice today for no apparent reason. The first time was after I sent an SMS to three friends. The second time was browsing Facebook in Dolphin.

Ideally, the only time I should have to reboot is when flashing a new ROM. Right now, we are very far from that ideal.
[AT&T Samsung Galaxy Note I717] Mauijpm:
Is this your first time on a Jelly Bean ROM on the Note? As far as I know of, EVERY ROM gets random reboots. We don't have source and these ROMs were built from scratch. If you can show me a Note thread with absolutely zero reboots based off a JB / CM10 kernel, then I will agree with you. I have been on nearly every ROM for the Note and have experienced a reboot on each and every one of them. You said a "stable" kernel, but we won't have that until we have source. It's not a warning, it's a beta.
[AT&T Samsung Galaxy Note I717] 2sl0w:
Running fine here. No battery drains or reboots. Running dagr8s kko.12 kernel and justunbeans inverted gapps. Full wipe of course. Running strong at 1.72ghz lulzaxtive gov with noop scheduler.
[AT&T Samsung Galaxy Note I717] csrohena:
No. No Luck...:(
[AT&T Samsung Galaxy Note I717] erad1:
Try this if you haven't already...this worked for me once when I thought my captivate was dead. Its a method to get into download mode not recovery. Have Odin up and running on your PC...have the odin flashable file you want to flash ready also, now similar to a previous mentioned method have the battery out of your phone, now press the both +/- of the volume rocker and continue to hold it thru the process, plug in the USB cable to the phone port, then insert the battery. It's worth a shot. Good luck.
[AT&T Samsung Galaxy Note I717] taob:
Well, that's partly my point... just because every other ROM does it, doesn't mean we should strive for better. I don't think it is unreasonable to compare it to other Android releases in terms of stability, just as we compare features and functionality. Not having kernel source might be the cause of some reboots, but that doesn't negate a poor user experience. One of my pet peeves is how every ROM seems to be "great!" and "stable!" and "smoothest one yet!" and "awesome battery life!", etc., etc. Sometimes the hype is worse than what Apple spews out. ;) I understand that hacking together a ROM from binary distributions is not the most exact science, but lets be a bit more realistic and selective about where praise deserves to be heaped. :)
[AT&T Samsung Galaxy Note I717] liawoft:
dead phone

My phone is also dead after this update coming from RC7. Have no way to power it on
[AT&T Samsung Galaxy Note I717] erad1:
Edit; deleted.
[AT&T Samsung Galaxy Note I717] SayWhat10:
Wow this is crazy, 4 bricked phones? Guess its all user error though huh? Smh
[AT&T Samsung Galaxy Note I717] taob:
Until someone can show evidence to the contrary, then yes. I don't know these people, nor do I know their level of expertise when it comes to stuff like this. I've seen people describe a boot loop as "a bricked phone"... do we know that all reports here are from people who understand the proper terminology? One fellow seems to think that simply having the correctly-named file is sufficient, without checking the MD5 checksum. So we need to ascertain that ALL reports are of a hard-bricked phone caused by flashing the ROM and not by a coincidental hardware fault or other problem. I've personally gone back and forth between RC7 and RC8 three times (and now back on a hybrid RC7 + RC8), and have yet to encounter any major problems. Since we're all using the same hardware, starting from the same state (full wipe, etc.), and flashing the same ZIP files, there must be some other factor causing these problems.
[AT&T Samsung Galaxy Note I717] delock:
I was wondering the same thing. Guess one of the people that bricked their phone can chime in.
[AT&T Samsung Galaxy Note I717] SystemErrorOne:
boo

Yeahh..I bricked my phone as well..

I first rooted my device coming straight from 4.0.4 ICS

then flashed TWRP2 and everything worked flawless.

Then I flashed this rom from internal sd card and nothing.

The phone wont go into download mode nor will it be detected in my computer.

One thing that it does do is show is "you need to format the disk in drive e before you can use it "

I already have the drivers installed from samsung and i even tried the heimaloneclick thing and nada..plz someone shed some light.

Very Much appreciated.
[AT&T Samsung Galaxy Note I717] SayWhat10:
I mean i doubt this is the FIRST rom folks have ever installed. Most are simply coming from RC7, are flashing instructions different from RC7 than RC 8?

Not trying to start a war, but in light of recent events, would simply request that the powers that be double check and make sure this rom is A O K
[AT&T Samsung Galaxy Note I717] taob:
What do you mean by this? You rebooted back into stock ICS, but with root?

Again, what exactly do you mean by this? You started flashing the ZIP, but the progress bar and status messages never updated? Or did it successfully complete, and then froze? "Nothing" is literally saying nothing, and does not help with the troubleshooting. ;)

Can you boot into recovery? Hold down both the up and down volume buttons while pressing the power button until the device turns on.

Wait... I thought you said "nothing" happens. What is saying that? It sounds like it might be a Windows error, but you just said the phone is not detected by your computer, so it can't be that...