If YES, please state how did get into the Official [LPY] ICS ROM and the problem you are experiencing.
If NO, then just please tell us your success story.
The reason why this thread exists is to, once and for all, trace the HARDBRICK that plague (?) some (?) ITCHY SGN fanatics and to pacify the fear of some of the other kids.
Don't need your opinions on why blah blah, just the scenario, OK?
Thanks
no problems now, except maybe battery but that might because we are all using it more to test it out
gonna test the battery today when i go to work, if it drops 20% in my pocket then theres a problem but last night it only dropped 5%
Does anyone know anybody that bricked te note with LPY?
I have no problems at all. All working excellent. From miui, flashed back to gingerbread then update to LPY all with mobile odin. No Cwm only everRoot.
Sent from my GT-N7000 using xda premium
No problem coming from official LC1 GB with CF-Root kernel using Mobile Odin Pro with Everoot and injections. Had no problems before factory reset in CWM nor after. I let the system rest both after the initial flash, and after the factory reset/wipe cache/wipe dalvik for about 20 minutes without touching the device.
This is my best experience on the note yet.
Alejandrissimo said:
Does anyone know anybody that bricked te note with LPY?
I have no problems at all. All working excellent. From miui, flashed back to gingerbread then update to LPY all with mobile odin. No Cwm only everRoot.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
One person has, but it is VERY questionable as to the cause of the brick. Time will tell.
No problem occurred thusfar.
I kept my Note stock, didn't want to root to give Sammy a chance...especially with the premium suite and S apps.
So used Odin v1.85..downloaded the 600mb+ file from samfirmware.com..extracted, loaded .tar file In PDA..flash and succes so far.
Good battery life..using Apex launcher but graphics seem improved, Tweakers.net did some benchmarks and conforms my feeling about this.
No trouble downloading large files, playing them and deleting.
So far nothing but good feelings about this..got bit scared by the posible brick stories but keeping it all stock seems to do the trick.
Sent from my GT-N7000 using xda premium
All good here as well . I returned to my stock rooted GB nandroid when the problems with the leaked kernels started (from Stunner, using the Abyss method without any problems). Stayed on it and then upgraded today with mobile odin and everoot (with full wipe). With that I kept root and restored my apps & data with TB. As I read a lot about bricking even with stock ICS I hesitated a bit to also flash the CF kernel. In the end I even flashed that (also using mobile odin). Went into CWM an wiped cashes to flash lidroid's 15 toggle mod. That is working fine now as well. Been using it since some hours now and no problems whatsoever! The only thing I didn't do as yet is a nandroid backup of it.
Sent from my GT-N7000 using xda premium
I am having issues with screen sensitivity.
Battery life isn't very good...
Runs a little warm...
Otherwise, I'm very happy with ICS
zkyevolved said:
I am having issues with screen sensitivity.
Battery life isn't very good...
Runs a little warm...
Otherwise, I'm very happy with ICS
Click to expand...
Click to collapse
I noticed some wonky screen sensitivity issues too. Scrolling through lists on Tapatalk 2 is a pain in the arse. Going to try touch screen booster app
I froze a lot of apps in Titanium Backup, and my battery life/heat issue went away
Itchy SGN fanatics and other kids? Calling an opinion bla bla?
Here's my bla bla: don't patronize people if you want them to contribute to your cause.
Here's my success story: flashed LPY with PC Odin, hated it, reverted back to CM9, happy again.
smooth so far 2 days now and working great battery drains a bit faster but np.
No problems here. Flashed rom and CF-Kernel using Mobile Odin Pro. Have got now a rooted ICS which works very well.
Sent from my rooted Galaxy Note using XDA Premium App
[Success]
Flashed from CM9 build#7 via Mobile Odin with everroot, inject su, inject Mobile Odin and Wipe data and cache options. Worked fine for me.
Flashed CF's CWM injected LPY kernel via Mobile Odin and that worked too.
After the whole brick panic I reverted to the original Samsung LPY kernel via Mobile Odin, no problem.
I didn't use CWM at all though given the suggestions that there may be some imcompatibility between it and the lpy kernel.
bioweb said:
Itchy SGN fanatics and other kids? Calling an opinion bla bla?
Here's my bla bla: don't patronize people if you want them to contribute to your cause.
Here's my success story: flashed LPY with PC Odin, hated it, reverted back to CM9, happy again.
Click to expand...
Click to collapse
Nobody cares... Thread asks if you had problems, not if you hated it. So we will assume it was working just fine for you.
Ok. Here's the real deal. I upgraded through Kies. No root here. DONT UPGRADE NOW:
Problems:
1. Its just as jerky as Gingerbread. Its actually even worse at times in slowness. It has a fast homescreen scroll at first and then has random pauses (almost the same). What worst is in apps when scrolling up and down on text it randomly pauses sometimes for several seconds. Also, every once in a while it does this on and off screen flashing then (not very seldom though). When it does it sucks.
2. The "fast reboot" app now crashes apps if you use them within the first 5-10 seconds after doing a reboot.
3. I'm noticing lots of compatibility issues with apps that aren't fully ics ready.
4. Samsung's version of Ics is dumbed down to almost look like gingerbread. So it runs worse and almost looks the same. I'm historically the one that notices all of the bugs because of how frequently I use multiple apps and because of the amount of apps I have on my phone. Thats why I constantly help by emailing devs pointing out bugs that 98% dont see for some reason.
5. Please dont get mad at me because I'm not a follower to give all praises to samsung and google (I am the same way towards apple too, even know I prefer android).
6. I suspect one of the problems is that Ics takes a little more juice and that the 1.4 exynos is once again underpowered. I think the other problem is samsung tried to rush this update out to the people and that the current touchwiz overlay is buggy. I expect an updgrade on touchwiz shortly (if they are a ethical company).
7. A primary example of the problems: While I'm typing this post I get a phone call. After I reject the phone call it goes back to taptalk with a less lighter screen. It is totally unresponsive. I then have to hit the back key to get back to composing. I then try to move up and down. It won't let me. After 15 to 30 seconds in able to once again continue this post.
8. I am sorry also that I upgraded because it might be glitchy for whom ever buys my phone eventually when I sell it (sell my phone every 6 months) and they may think there is something wrong with the phone, even though I baby my phones for future resell.
9. Bottom line: If its not broke dont fix it. We all want ice cream sandwich. Unfortunately, samsung's touchwiz version of ics at least doesn't appear to be ready for prime time. If you like beta testing and dont mind even worst glitches, then go for it. I definitely wont be upgrading to another phone with ics unless it has the new tegra 3 or the latest exynos processor.
AC
Sent from my GT-N7000 using Tapatalk 2
Well said my man, if it is slower and chews my battery faster wtf is the point of upgrading. We don't gain any mind blowing feature. Fyi who gives a flying F^k about angry birds space or whatever they come out with next
Sent from my GT-N7000
I went from gb, to german release ics, worked fine no issues from pc odin, then chainfire produced rooted kernel for it flashed with pc odin. all worked fine, but now i had triangle and 1 on the counter, ahhh, ok so triangle away dont work, flashed chinese repack did triangle away worked, using mobile odin, then i flashed the repack of the release with chainfire kernel, had nothing but problems, so went back to mobile odin flashed stock ics, then lost root, ahhh so flashed chainfire kernel with pc odin all well but still have triangle and 1 on the counter, i did full factory reset each time. I find ics a bit laggy more than latest gingerbread, i am leaving mine as is for the moment.
Was on several Leaks, to CM9 Official, to Official ICS. 0 problems!
People panic to easily in this forum. 1 guy bricks his phone and the damn section blows up and a public service announcement is made. Really?
Follow the directions.. EXACTLY, don't do anything erroneous, and you will be perfectly fine! Just like the rest of us.
Nope, not yet. Flashed with Mobile Odin Pro with Everroot and not the CF kernel.
Folowed dr ketan method from the lc1 cf root kernel. No problem so far
Related
So I got the Vibrant the other day and for the most part I absolutely love the phone. Feels like I'm holding a light sabre or a magic wand. The thing is just so powerful. I have been reading up as much as possible on how to flash ROMs and root. A month ago I'd never even heard of this stuff and now I feel like I at least have a basic knowledge....just don't have the balls to attempt it yet. I want to make sure I know what I'm doing.
So in the meantime (while I work on growing a pair and actually doing it) I want to update to the Tmob 2.2 froyo official. I have read that if I do this I won't be able to get in download or recovery mode. Is this correct? And if this is correct then does that mean it will be impossible to flash roms after updating?
I just want a little performance boost and have my system a little snappier til I decide if I'm gonna flash some roms or not. Anyone know the answer?
Thanks fellas
If you can muster the balls to get the official 2.2, just flash team whiskey s bionix. Its better, easier, more reliable, better supported, and looks cooler. Don't be scared, follow directions and its easy!! GL!
Sent from my SGH-T959 using XDA App
In all seriousness, you're far better off flashing the latest Bionix-v than you are the "official" 2.2. Having done both, you are far more likely to have an issue during the update process using that garbage mini Kies program than you are rooting and flashing. I rooted and flashed 4 different ROMS without issue. Then I used ODIN to go back to stock because I wanted to see the official release.
4 hours later I was able to get my phone back to a usable state. Between driver issues and crappy software (Kies), it just wasn't worth it. And after using my buddies Vibrant that was running the official release, it was way slower and less usable than most of the latest ROMS offered here.
You should root and then flash the latest Whiskey or Axura ROM and be done with it. The devs here have given us a far better experience and options on our phones than Samsung has.
Actually, the official 2.2 tmo update got rid of the hardware lock for me. I couldn't get into recovery or download mode out the box. The previous JI6 update through Kies mini didn't help. Since I am no longer hardware locked, I'll probably flash some roms. I am pretty dissappointed with this official update after that long wait.
I agree with the other comments that just getting one of the better/faster ROMs here is going to be what you want. As for your question about getting the "official" update and then being able to flash, that's what I did so it should work for you with just a little reading.
I disagree...I love team whiskey and all the other custom roms and even used them for a long time. But right now I have been using stock 2.2 ka7 with voodoo kernel and it is really fast and snappy. I like the stock look as well and haven't experienced any bugs or slowdowns since I installed this rom ...my suggestion: if you want stock....then read up a bit and Odin to ka7...mini lies is the worst program invented and it only flashes you to ka6
Sent from my SGH-T959 using XDA App
Don't download the official! Take your time, read a lot, grow a pair and then execute! You'll be alright. confidence comes from research and doing. Everyone was nervous at one point.
Sent from my SGH-T959 using XDA App
tmo throws people in jail for flashing custom roms making our phones super amazin and they dont want that so remember to odin back when u bring ur phone for warranty
Yaz75 said:
In all seriousness, you're far better off flashing the latest Bionix-v than you are the "official" 2.2. Having done both, you are far more likely to have an issue during the update process using that garbage mini Kies program than you are rooting and flashing. I rooted and flashed 4 different ROMS without issue. Then I used ODIN to go back to stock because I wanted to see the official release.
4 hours later I was able to get my phone back to a usable state. Between driver issues and crappy software (Kies), it just wasn't worth it. And after using my buddies Vibrant that was running the official release, it was way slower and less usable than most of the latest ROMS offered here.
You should root and then flash the latest Whiskey or Axura ROM and be done with it. The devs here have given us a far better experience and options on our phones than Samsung has.
Click to expand...
Click to collapse
The only time you'll have an issue is if you're too dumb to turn on debug mode. And most of those people who are too dumb to do that were likely too dumb to read the threads where it was repeated ad nauseum to turn debug mode on...
Turn on Debug Mode
Update
Format Internal SD
Factory Reset
Enjoy.
N8ter said:
The only time you'll have an issue is if you're too dumb to turn on debug mode. And most of those people who are too dumb to do that were likely too dumb to read the threads where it was repeated ad nauseum to turn debug mode on...
Turn on Debug Mode
Update
Format Internal SD
Factory Reset
Enjoy.
Click to expand...
Click to collapse
Well thank goodness you aren't talking about me because I did have debugging mode turned on! And then mini Kies started to update the firmware, then it decided to crap the bed at about 75% and turned the phone into a confused jumble of uselessness.
But I guess you were there so I'll let you tell everyone how I recovered it.
bartek25 said:
tmo throws people in jail for flashing custom roms making our phones super amazin and they dont want that so remember to odin back when u bring ur phone for warranty
Click to expand...
Click to collapse
What the heck are you talking about?!
So thanks to some of the competent answers from guys in here and a leap of faith and trusting my extensive research (I read way too many threads about rooting, flashing, odin, custom roms, etc..), I am now rooted and have backed up my system. To be honest I'm almost just happy with that. While completeing this process I ran into a few questions that I didn't have the answer for mainly revolving around wheter to reboot or reinstall from recovery mode whether it be clockwork or samsung.
I posted a question in the Q and A forum about it (so I apologize for the kinda double post but this is more of a update on my progress) but whats the deal with update.zip file? I don't know when to reinstall it from recovery and when to delete it once the phone has booted. Should I delete it every time I have booted back up or does it even matter?
Thanks guys. I'm the kind of guy that, once I have the knowledge I am just as willing to share. Hopefully a year from now I'll be in your shoes and able to help others.
Next up after the update.zip question is resolved in my mind I plan to flash to bionix v. Official froyo 2.2 be damned lol
You use Clockwork Recovery to backup or flash anything. Sometimes you will get the Samsung recovery and you'll need to select reinstall packages to get to Clockwork. Sometimes you'll even need to reinstall packages twice.
Leave the update.zip on your sd. That's a necessary file for Clockwork.
Everything is working flawlessly for me, I have had zero issues with this ROM since day one. Maybe I just don't use the phone enough or really stress it, but I have yet to come across any quirks on this leaked 4.5.573. Everything works - gps, netflix, any apps I download, corporate sync, etc. etc.
Is there any sense in upgrading to the latest official OTA GB? I figure if it ain't broke don't fix it...right? Or are there compelling reasons to go ahead with the official OTA? And if the answer is YES UPGRADE, what's the best way to do this considering I'm on 4.5.573 right now? BTW, I'm on Cricket.
I've got this same question. I want to upgrade for several reasons, but what I've read on several sites is that we have to do the SBF thing back to 2.2, then upgrade.
Almost none of the threads I've read at several sites even mention .573 anymore, so I'm not exactly sure of the route to go.
Why do you want to upgrade? Are you running into problems? Unless there's a good reason to upgrade I'd prefer not to, especially if I have to SBF in order to upgrade. That means I'll have to re-do my Cricket flash which I've probably done 50 times now but I'd prefer not to have to do it again.
hey guys,
i am on version 596 of gb, the official version. and i would highly recommend upgrading, there is a new kernel and new baseband. that means the phone runs more smooth and you have cleaner calling and stuff. i have noticed a big improvement in the new kernel and stuff. it would be very beneficial to upgrade in my opinion.
^^^
Those were the reasons I wanted to upgrade. Performance took a GOOD bump in the updates after .573
I just followed the instructions here...
http://www.mydroidworld.com/forums/...new-full-sbf-droid-x-2-3-340-a.html#post56464
Method 2 worked for me, the first one wouldn't detect my phone. I got a boot loop after it finished so I booted into recovery and cleared the cache/data factory reset.
Now it's all fine.
Now to find the right set of GB update roms.
you'll want the updated radio found in the later versions and .596 runs buttery smooth. about a week of heavy use not one reboot or crash.
I gotta say, I'm VERY glad I did it. It was smooth and quick before, but good lord, this is CLEAN.
Not one reboot, not one crash, all NOICE!
i'm on 4.5.573 with root and the phone has been running crazy slow for the last week. will this work? i'm trying method 2 but it will not recognize my phone.
thanks!
RED ZMAN said:
^^^
Those were the reasons I wanted to upgrade. Performance took a GOOD bump in the updates after .573
I just followed the instructions here...
Method 2 worked for me, the first one wouldn't detect my phone. I got a boot loop after it finished so I booted into recovery and cleared the cache/data factory reset.
Now it's all fine.
Now to find the right set of GB update roms.
Click to expand...
Click to collapse
I would reccomend updating to a newer version from team black hat. Its faster, smoother, the blur is different (better) and best of all, pre rooted.
Sent from my Xoom using XDA Premium App
Hello All,
Here's my 2 cents on SODs and killing of it (even if only temporary)
I am currently on @Anti's Asylum ROM. Previous to that, I was on CM9 ver 7.
Had been plagues by SODs and had almost given up and was about to flash Samsung Stock ROM.
I was on Stunner previous to CM9. Once I was on CM9 and loving it, I came across this nasty looking creature called SOD for the first time in my life.
Threads suggested I should flash GB ROM back and do a clean install. @AndroidIndian was kind enough to walk me through all the steps and I did everything I had to. Then flashed CM9 back. Guess what, those SODDIN SODs were still there.
So, apologetically, I posted that I had to betray my brethren here and go back to Samsung Stock.
Then, @Tremorone PMed me to try @Anti's asylum, built on CM9 code. He said since I was trying to hold on to an AOSP thing, I should try it at leas once. In one last ditch effort, I did the right thing - flashed Asylum ROM over the CM9 ver 7.
Now, the interesting bit:
Initially, I was on XXLPT Modem (the latest one). Overnight, there was no SOD and I was a happy bunny. Next morning I got a long call (about 20 mins). Once the call was over, SOD !!!! Figured it HAD to be a modem.
So, I did the following:
1) I flashed LP5 Modem through Mobile Odin. SODs were less but the lockscreen froze up once.
2) Being the impatient prick that I am, after a while I flashed LB2 Modem via CWM Recovery.
SODs has drastically gone down on that. No SODs in the last 7 hours as a matter of fact.
I don't know if it's the ROM, LB2 via CWM or the combination of Steps 1 and 2 above, but seems like it has more or less solved the problem. Of course, it is still early days and I need to observe for a couple days more.
To everyone suffering at the hands of the SOD demon, I would suggest why not try Step 1, let the ROM settle, and then proceed with Step 2 (as above).
There's no harm in trying, right? And if it solves it, nothing more beautiful than it. Then you can go CM flash happy as soon as new builds start being avaialble.
Thanks to @Abhisahara for helping me keep the faith.
All the best SODding off the SOD.
Cheers.
Well, I think I'm a lucky guy. I had never one SOD since I own a note. I have nearly the same flashing history like you. Flashed also many modems . I can't imagine why the devices are so different. The same thing I noticed with my old HD2. I hope you will find the reason/way to solve this f******* SOD issue
Gesendet von meinem GT-N7000 mit Tapatalk 2
I'm the same after flashing cm9 I had one screen of death on the lb2 modem.. I flashed lp6 just because.. After that I used cm9 for a week with not one sod before flashing ics official
Sent from my superior Nokia 3210 using XDA Premium Plus Legacy Edition
My SODs stopped after I flashed .19 Stunner with LP5 kernel and LP6 modem. I haven't had one since then (**knock on wood**). I am on stock ICS now with the new modem, not CF-root kernel though. Strange how variables are always so different though.
Hmm,
I've flashed several modems since being plagued by the SODs. I'm on CM9 nightlies and am using LP6 from LB2. The SODs have gone down with the newer modem since I was getting 5 or 6 a day! But, I still get at least one or two a day now. I'll try with the latest LPT or LR1 and see if these make any improvements.
They are a bit of a mystery though since there never seems to be any consistency to what is actually causing the sleeps.
I always flashed modems through Mobile Odin and flashed every single modem available for note, but still had SODs.
So I wiped everything and reinstalled the ROM and did not restore data and I did not have SOD.
I have data backed up on Google, it restored my apps (through play store), contacts and wifi access points, so I was kind of OK, since I did not lose out much. But thats just me!
I tried LB2 ,LA4 ,LPY Modems ,and had one SOD in two weeks time while on CM9 build#3 and LA4 modem.
LB2 modem iks very good and I'm using it right now with the latest nightly with no SODs what so ever.
I've flashed modems using CWM and still get the SODs. I'm beginning to think these are not directly related to the modem. I did a clean install of GB from Imilka's CM9 (Chinese leak) then Chainfire's rooted kernal and then on to the CM9 nightly. I didn't copy any system data but I did use TB to resinstall my apps (against advice I know). I had no SODs on Imilka's rom but they appeared following install of CM9 nightly.
I guess I'll try a clean install again but I hate having reconfig my phone everytime since I change so many things via Apex, Minimalistic Text and Folder Organiser apps.
I'm hoping though that we'll get to a nice update on CM9 that will resolve the problem eventually.
I think SOD is WIFI related (not just modem). Since upgrading to ICS, different ROMs, I had many of them on all ROMs and modems, until I set my WIFI to never sleep and disabled any battery saver trying to make it sleep when screen off. That solved it for me. Then started testing battery savers, most of them brought SOD again, until I tried battery defender, which seem to work without SODs.
Had lots of SODs in the past on CM9, none for 3 days since I installed nightly 20120515 and LPT modem. Fingers crossed
I've read on this forum that some well-respected users* hypothesizing that LS8 may actually be just another test rom based on the following things:
- Only released in Spain (FOP) [not sure what the other 2 Chinese releases brought to the table)
- Bootloops/freezes seem to happen even while using the stock rom (this seems to happen to all users eventually)
In my experience, I had one freeze in which I couldn't wake the device. I turned it off, removed the battery,
and it got stuck on boot. Then I turned it off (by holding the power button) and turned it on again and it work. Hours later the same thing happened. I thought it was Jeboo Kernel 1.2's fault, but now that I read this I am uncertain.
So what do you guys think? Are we running a test rom? Did Samsung release it so that we would shut the hell up for a while? Or is it the real deal and it is the best we'll get?
*not mentioning them just to avoid them getting hatemail (actuallly hatePMs) if this proves not to be true
Dexter_prog said:
I've read on this forum that some well-respected users* hypothesizing that LS8 may actually be just another test rom based on the following things:
- Only released in Spain (FOP) [not sure what the other 2 Chinese releases brought to the table)
- Bootloops/freezes seem to happen even while using the stock rom (this seems to happen to all users eventually)
In my experience, I had one freeze in which I couldn't wake the device. I turned it off, removed the battery,
and it got stuck on boot. Then I turned it off (by holding the power button) and turned it on again and it work. Hours later the same thing happened. I thought it was Jeboo Kernel 1.2's fault, but now that I read this I am uncertain.
So what do you guys think? Are we running a test rom? Did Samsung release it so that we would shut the hell up for a while? Or is it the real deal and it is the best we'll get?
*not mentioning them just to avoid them getting hatemail (actuallly hatePMs) if this proves not to be true
Click to expand...
Click to collapse
I would say so, why would they only release it in one country? I has to be released only in Spain so they can iron out the rest of the bugs, including the annoying freezing/random turning off ones that kill your battery. Battery drain has to be sorted also, so some call it the final build, but I reckon it will another month or two before we see the true "final" build, hopefully with all the bugs ironed out.
Question. ...are people getting these bugs you talk about if they run the rom bone stock no root? I do believe this was rushed out but not that its another test rom. Staying on my rock solid neat rom 4.0 with siyah for now. Something better is coming....fingers crossed.
Sent from my GT-I9100 using xda app-developers app
themadba said:
I would say so, why would they only release it in one country? I has to be released only in Spain so they can iron out the rest of the bugs, including the annoying freezing/random turning off ones that kill your battery. Battery drain has to be sorted also, so some call it the final build, but I reckon it will another month or two before we see the true "final" build, hopefully with all the bugs ironed out.
Click to expand...
Click to collapse
Perhaps, but doesn't that make it a test rom by definition?
vanisleryan said:
Question. ...are people getting these bugs you talk about if they run the rom bone stock no root? I do believe this was rushed out but not that its another test rom. Staying on my rock solid neat rom 4.0 with siyah for now. Something better is coming....fingers crossed.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
This dev claims that the first time he installed it (straight from the sammobile odin file) it caused him bugs. I haven't tried the stock, untouched, unrooted version.
I've said before that LS8 feels unfinished.
Sent from my GT-I9100 using xda premium
I don't have any bug or freeze. I'm on LS8 with PhilZ kernel btw.
Until UK's XEU is out, I won't call anything "final".
I have the spanish rom, clean install. Without root, pure stock, odexed, not zipaligned... I had thoose problems using custom kernels and rooting my phone! going back to stock, everything is fine. I think that the problem is that some files are changed, I tried cooking my own rom and it didn't worked (ok a "first try").
I think that we must wait some weeks for good kernels, because the development of a kernel requires time. You can make one that boots in a short amount of time, but one without freezes... It should need some weeks.
No freezes, stucks nor bootloops for me. U'll get the best of it if u actually did total wiping rom & kernel by wiper scripts provided by hawkerpaul's especially if u ran custom rom & kernel before.
And u'll get worth battery savings if u wipe the bloatware by TiB & slimmin down ls8 at ur taste, those will grab out crappy ware from ur ram & kill the batt eater. Disable gnow, syncing at certains need & disabling fast dormancy if ur operator doesnt supported.
Just one so annoyed for me & does anyone has idea why : stock browser didn't run & got FC at custom dpi ??? and pls provide me a link a multi dpi playstore to install at stock recovery, the one I had got unsigned to install.
Please give me some respect for useful answer..
Sent from my GT-I9100 using xda app-developers app
It definitely is a test ROM... There are bugs.:banghead:
Sent from my GT-I9100 using xda premium
Never had this sort of issues with any ROM before. Sure I had buggy ROMs that crashed apps left and right, but never have I had to worry that forcing a reboot will corrupt the system.
So in my opinion there are two issues here. One being that the phone can freeze in pretty much any app. The other being that holding the volume and power buttons down to force a reboot will ruin the boot sequence somehow.
In some ways, the inevitable freezes bother me the most. On my old 4.0.4 RR AOKP ROM I just to have this issue where scrolling too fast in lists in certain 3rd party apps (like Amazon, Techpowerup, Ebay etc) would freeze the phone and I had to reboot. Well, at least it never broke the OS ...
I got the tip from the official Jelly Bean thread that backing up, wiping and restoring an installation with a boot freeze / loop will in fact bring the system back to life. As to why this works I have no idea.
I also noticed someone talking about possible issues with restoring apps via Titanium Backup, the Android ID and some mismatch. I have never seen the Android ID pop-up in TB though and I assume this is just another developer mantra, like wipe - reinstall - wipe - reinstall. In truth they seem to have no clue what is going on.
Good job Samsung, good job ...
Well. I too think that this is a test release. One for Europe and one for Asia (China releases). We'll have the proof when we will see the next releases in other countries (like UK XEU and/or Nordic NEE). I assume that there will be different PDA's with newer changelog.
But, from my experience, this release is very good. I flashed it from the first day it has been released via Kies and I kept it unrooted since (only disabling some apps). I haven't experienced any of the issues mentioned time and again in this forum and the battery is on par with ICS 4.0.4 LPY for me. 2d10h with 2h screen on.
Maybe I'm lucky or maybe this is the way to go for now (kies and all stock), until the dev and optimizing process matures itself.
Compared to CM10 and LSJ, this ROM have been the the most smoothest and most stable ROM. I haven't encountered any freezes or instability since I installed it last week. However I did loose service last saturday, presumably a RIL crash, but since restarting it have been running problem free for 69 hours.
I have kept it completely stock, but it is rooted through Mobile Odin.
LS8 is not a test rom, Its available via kies so its public final, The fact that its only been released via Spain so far is irrelevant.
All the people moaning about problems are also irrelevant since you will always have some people who have issues after updating to new rom whether its Sammy official or a custom.
LS8 is very stable and very smooth for me.
i never seen such an crappy rom, its unstable.( xwls8)
First, format my card,rom, etc, put xwls8, default kernel.
After 1-2 hours the bugs appears: when i click on almost anything( like any game, my file, es file explorer, stweak, etc), it freeze, then i was force to close and start again the phone, then bootloop.
Or after an force shutdown i stuck at samsung logo.
I tried siyah, dorimanx, etc, wipe cache, etc, etc
Then after 4-5 days of bugs an unlimited shutdown, freezes, etc, i wipe everyting an install 404 xwlq3, stuck at samsung logo, force to install the rom again, etc.
Now im on xwlq3 and dorimanx 5.92 till a new rom appear. This 4.1.2 is not usable.
Previous one, xxlsj, except lag on lock screen, i dont seen serious bugs.
Boy this xwlq3 rom it feel so nice and fast. And no bugs.
If any of you read on siyah , dorimanx, philz, rootbox, etc,etc thread you will see that a lot of us have this problem.
TheATHEiST said:
LS8 is not a test rom, Its available via kies so its public final, The fact that its only been released via Spain so far is irrelevant.
All the people moaning about problems are also irrelevant since you will always have some people who have issues after updating to new rom whether its Sammy official or a custom.
LS8 is very stable and very smooth for me.
Click to expand...
Click to collapse
Agreed.
Sent from my GT-I9100 using xda premium
TheATHEiST said:
LS8 is not a test rom, Its available via kies so its public final, The fact that its only been released via Spain so far is irrelevant.
All the people moaning about problems are also irrelevant since you will always have some people who have issues after updating to new rom whether its Sammy official or a custom.
LS8 is very stable and very smooth for me.
Click to expand...
Click to collapse
LS8 feels unfinished.
Yes, people may have issues after upgrading but those people are silly and invariably don't know what they're doing. I am however sure that I don't fall in to this category.
Yes, it may be an official release but even so it seems rushed out to appease the masses who were getting sick of waiting.
Yes, it is you lot who're at fault for rushing Sammy in to releasing sub-par, unpolished updates.
I hope you're all happy!
Sent from my GT-I9100 using xda premium
No issues experienced whatsoever
Sent from my Samsung GT-i9100M
ROM NeatRom Lite 4.2 XWLS8
Kernel Philz 4.00b30
Mods:
23 toggles blue w/rt clock
Automatic Call Recorder
Sorry if this is in the wrong place, but is it necessary to change the CSC after flashing this ROM?
I've been using LS8 + Siyah 6.0
Not getting great performance. No hangs/freezes but my battery drains pretty quickly.
Hey guys just thought is let you know cm11 nearly bricked my phone, the update downloads fine and restarts but fails half way through install. Unfortunately I didn't write theberror code down as I was concentrating on getting it all running. The dates of the nightlies were the 14th and 16th on my i9300 rooted using clockworkmod recovery. I tried also downloading the 16th nightly with my PC and transferring it. Same result. Ended up with bootloop and even Odin failed several times. Ended up working after try 4
Note if you want to flash firmware its your risk and the risk gets higher if you don't read .
This is a developers forum and we all accept the risk of a brick.
Without the error we can't say for certain what the issue is, you are sure the rom was for the i9300 and not another device weren't you?
No problem here
I flashed both 14th and 16th nightly and did not have any kind of installation problem. All worked fine. Are you sure you are using latest recovery? (CWM 6.0.4.3+ are ok, don't know for older versions)
Was close to sending my phone into repair as well.
Installed CM11, GoogyMax kernel and Gapps package, phone froze on entering sim unlock code.
Afterwards my PIT/partition table was corrupted, no way of reflashing using Odin.
I've tried Kies as my last resort and luckily the emergency recovery fixed my phone.
Awful feeling, have never been as close to 'bricking' my phone :\
Been running CM11 nightly since start of December without issue. Check your CWM version before flashing.
Sent from my GT-I9300 using Tapatalk
That's a typical case of PEBCAK. Bricking a phone with CM is nearly impossible(chance is probably lower than using odin to flash stock), but there are always people that can do that. Good job.
Moster2 said:
That's a typical case of PEBCAK. Bricking a phone with CM is nearly impossible(chance is probably lower than using odin to flash stock), but there are always people that can do that. Good job.
Click to expand...
Click to collapse
It's not like I've never flashed stuff before, I'm doing things like this regularly since the days of my good old SGS1.
I've never encountered such a thing and I also didn't say it was CM11's fault. CM10 has been installed for months on my phone, flashing dailys when they came out - and I never had any problems even remotely similar to this.
I'm not sure how it's even possible for the partition table to gay haywire shortly after booting up but that's what happened. For me the problem seems to be related to Googymax, as I've been booting fine without and had problems after changing the kernel.
Cy4n1d3 said:
It's not like I've never flashed stuff before, I'm doing things like this regularly since the days of my good old SGS1.
I've never encountered such a thing and I also didn't say it was CM11's fault. CM10 has been installed for months on my phone, flashing dailys when they came out - and I never had any problems even remotely similar to this.
I'm not sure how it's even possible for the partition table to gay haywire shortly after booting up but that's what happened. For me the problem seems to be related to Googymax, as I've been booting fine without and had problems after changing the kernel.
Click to expand...
Click to collapse
I wasnt refering to you. You seem to have knowledge about the stuff and fixed it, but to the guy in the first post. Opens a thread, useless and wrong section, no error message etc. He just more or less rants about his failure
Sent from my GT-I9300 using XDA Premium 4 mobile app
Alright, must have misinterpreted your post then
In the OPs' case, it seems like there was something wrong with his recovery, as others have already hinted.
TWRP 2.6.3.0 was giving me similar problems, 2.6.3.1 fixed those for me.
Really, pathetic thread.
Checking md5sum of downloaded zip, few simple adb and standardblinux command like ls, flashing newer and/or other recovery, and the most important; understand what being read, will never brick your phone. Even if it did, softbrick is child's play.
Sent from my GT-I9300 using xda app-developers app
I using CM11 since the first Version with no real Problems.
Gesendet von meinem GT-I9300 mit Tapatalk 2
This should be closed. We know the risks.
Threads like this just put new android flashers off flashing customs roms because of someones bad experience.
Sent from my GT-I9300 using xda app-developers app