Good day. I really like my Note. I don't crave speed but it was definitely a bit laggy sometimes and I wanted more smoothness. Since my transformer really didn't like JB, and is working like a charm with the Energy ICS ROM and overclocked to 1.5Ghz.
With this in mind, I was looking for a smooth, stable ICS ROM for my I717 Note. After much searching, I settled on Padawan...and so far, it's working like a champ...smooth, much faster than the stock ICS and compatible with all of my apps.
I rooted with Odin, backed up with Titanium, wiped everything and loaded Padawan from my sd card using CWM...and nothing happened...or rather, nothing happened after the samsung splash screen.
I waited the requested 10 minutes, (though I now suspect that's supposed to be after a good boot), and still nothing. I did this a few times, wiping everything and the 4th time was the charm.
The only thing I did differently was to do the factory reset last. Maybe that had something to do with it or it was just a fluke...dunno. Regardless, Padawan with the Note 2 look is now working like a charm on my Note, so far without any problems and all of the apps that I loaded are also working.
So any guesses why it took 4 tries to get Padawan to load properly? Had this happened to anyone else?
JoeCanuck said:
Good day. I really like my Note. I don't crave speed but it was definitely a bit laggy sometimes and I wanted more smoothness. Since my transformer really didn't like JB, and is working like a charm with the Energy ICS ROM and overclocked to 1.5Ghz.
With this in mind, I was looking for a smooth, stable ICS ROM for my I717 Note. After much searching, I settled on Padawan...and so far, it's working like a champ...smooth, much faster than the stock ICS and compatible with all of my apps.
I rooted with Odin, backed up with Titanium, wiped everything and loaded Padawan from my sd card using CWM...and nothing happened...or rather, nothing happened after the samsung splash screen.
I waited the requested 10 minutes, (though I now suspect that's supposed to be after a good boot), and still nothing. I did this a few times, wiping everything and the 4th time was the charm.
The only thing I did differently was to do the factory reset last. Maybe that had something to do with it or it was just a fluke...dunno. Regardless, Padawan with the Note 2 look is now working like a charm on my Note, so far without any problems and all of the apps that I loaded are also working.
So any guesses why it took 4 tries to get Padawan to load properly? Had this happened to anyone else?
Click to expand...
Click to collapse
never and you know what? his other rom seems smoother than padawan.
Ltilt2 said:
never and you know what? his other rom seems smoother than padawan.
Click to expand...
Click to collapse
The other ROM is Nebula. Less bloat.
ddochi11 said:
The other ROM is Nebula. Less bloat.
Click to expand...
Click to collapse
Yes, no att bloat
Ltilt2 said:
Yes, no att bloat
Click to expand...
Click to collapse
I may give that a try...though the fact that the flash took 4 tries has me a bit leery. I'll leave it alone for a bit until frustration and/or boredom sucks me into flashing again.
JoeCanuck said:
I may give that a try...though the fact that the flash took 4 tries has me a bit leery. I'll leave it alone for a bit until frustration and/or boredom sucks me into flashing again.
Click to expand...
Click to collapse
I have flashed that rom many times with no issues. This is how I do it.
reboot to latest touch recovery, wipe data, wipe cache, wipe system, wipe dalvik cache than flash Rom.
after it reboots, I let set for 10 minutes than reboot to recover again and wipe dalvik cache and fix permissions. after that reboot and set up your phone. I have never had an issue flashing this way.
Right now I'm trying the N7005 rom. This thing is super smooth and snappy.
That's pretty much what I was doing. On my Milestone and Transformer, I never had any issues loading a new ROM by wiping then loading in CWM. I never worried about it bricking but I was a bit worried until it finally took. Now, it's running like a champ.
I'll do a nandroid backup of this and probably try something else in a while...after I smack this one around for a while.
JoeCanuck said:
Good day. I really like my Note. I don't crave speed but it was definitely a bit laggy sometimes and I wanted more smoothness. Since my transformer really didn't like JB, and is working like a charm with the Energy ICS ROM and overclocked to 1.5Ghz.
With this in mind, I was looking for a smooth, stable ICS ROM for my I717 Note. After much searching, I settled on Padawan...and so far, it's working like a champ...smooth, much faster than the stock ICS and compatible with all of my apps.
I rooted with Odin, backed up with Titanium, wiped everything and loaded Padawan from my sd card using CWM...and nothing happened...or rather, nothing happened after the samsung splash screen.
I waited the requested 10 minutes, (though I now suspect that's supposed to be after a good boot), and still nothing. I did this a few times, wiping everything and the 4th time was the charm.
The only thing I did differently was to do the factory reset last. Maybe that had something to do with it or it was just a fluke...dunno. Regardless, Padawan with the Note 2 look is now working like a charm on my Note, so far without any problems and all of the apps that I loaded are also working.
So any guesses why it took 4 tries to get Padawan to load properly? Had this happened to anyone else?
Click to expand...
Click to collapse
Hi. I'm having the same problem with my i717. When you say you "did this a few times", do you mean you just wiped the user data, wiped the cache, wiped the dalvik cache, fixed permissions & then rebooted the system 4 times or did you flash the Padawan rom 4 times too? Any help is much appreciated. Thank you.
Wipe everything, install, wipe everything again. Usually works for me
Sent from my GT-N7005 using xda premium
rajivr74 said:
Hi. I'm having the same problem with my i717. When you say you "did this a few times", do you mean you just wiped the user data, wiped the cache, wiped the dalvik cache, fixed permissions & then rebooted the system 4 times or did you flash the Padawan rom 4 times too? Any help is much appreciated. Thank you.
Click to expand...
Click to collapse
Yes...I wiped everything I could find. I believe the instruction to 'wait 10 minutes' is after it boots. It shouldn't take more than a couple of minutes to get past the boot splash, so if it doesn't work after 5 minutes, go through the entire wipe process again. I even went into 'mounts and storage' and formatted 'data', 'system' and 'cache'.
I don't know if this made any difference or not, but on the attempt that finally worked, I did the 'wipe data/factory reset' last.
Format of the system is critical on this device, even if the rom does it anyway.
Get it clean ...
And of course a good download is important as well....g
gregsarg said:
Format of the system is critical on this device, even if the rom does it anyway.
Get it clean ...
And of course a good download is important as well....g
Click to expand...
Click to collapse
Amen to that!!!!
MrRoxtar
Android Tech Heroes
Related
I'm having probelms after flashing the supra ROM for the second time. It won't let me post on the thread so I don't know where else to post. It all worked perfect the first time, but now after installing about half my apps it won't install anymore because it says there's no room even though I have 603 MB free. Any idea on how to fix this? It worked fine the first time, I switched to another ROM and wanted to switch back, and then I wiped everything and then reinstalled. Tried twice but same problem. Any help would be appreciated.
Have you tried a full wipe before reinstalling?? If you think that you may want to go back to a rom you should do a nand backup before installing the new rom that way all you have to do is restore the nand.
Yeah I did a full wipe
This happened to me too, on the first install. I just flashed a different ROM
Did it work ok when you flashed it back to supra?
I flashed back to Chogardjr3D and it worked fine. I just tried SteelROM, and it did the same thing. I would love to find out why this is happening. Makes no sense to me
me neither
This was happening to me on every ROM I flashed. I think it has something to do with Google syncing back apps after a clean install. I disabled the Google backup and restore and now all seems to be fine. Again, not sure this is the exact problem. Could just be coincidence.
Sent from my PG86100 using XDA Premium App
Yeah I flashed a different rom and it worked fine
Sent from my sexy s-off rooted 3DEVO
So I have seen quite a few threads about installing ICS but I have yet to see anyone install it over MIUI. Is there a suggested method for this?
I couldnt get it to install over MIUI, it kept throwing me an error, I restored to cm7 and it flashed fine
Thanks for the reply, I don't have a backup of cm7 as the wifi never worked for me on it. Is there really any reason to goto cm7 first?
To answer my own question I guess I could run a Titanium Backup restore of MIUI on CM7 then upgrade... So that should be one benefit
mcsephoenix said:
Thanks for the reply, I don't have a backup of cm7 as the wifi never worked for me on it. Is there really any reason to goto cm7 first?
Click to expand...
Click to collapse
I installed cm9 over miui. Did wipe dalvic, wipe cache, wipe data/factory reset, installed from sdcard. Worked fine.
Note - I hadn't done a lot in miui, so I didn't mind wiping and reinstalling apps.
Good luck and have fun.
jhon777 said:
I installed cm9 over miui. Did wipe dalvic, wipe cache, wipe data/factory reset, installed from sdcard. Worked fine.
Note - I hadn't done a lot in miui, so I didn't mind wiping and reinstalling apps.
Good luck and have fun.
Click to expand...
Click to collapse
Thanks for the reply not sure doing a wipe then fresh install really counts as installing over miui but good to know it worked out if it comes to that... I am still on the fence about installing alpha 0.5 as I am really happy with how I have miui setup at the moment...
I'm a huge MIUI fan and have been running it on my Mytouch 4G for a couple months now. I put it on my HP Touchpad and couldn't stand it after a couple days. It was just way too buggy. I installed ICS a few nights ago and it is running beyond what I expected! You could try both and back them up then switch back to the other if you don't like one.
mcsephoenix said:
Thanks for the reply not sure doing a wipe then fresh install really counts as installing over miui but good to know it worked out if it comes to that... I am still on the fence about installing alpha 0.5 as I am really happy with how I have miui setup at the moment...
Click to expand...
Click to collapse
What I meant was, I was running miui. It was my 1st android install.
When cm9 alpha0 came out, I installed it as I said by cwm wipe; then flashed cm9.
I like cm9 a lot better than miui. Feels more like a real tablet app. Please don't ask me to define that .
This phone was an insurance replacement from ATT, so alway a bit wary of these refurbished phones.
So for the longest time it has always been a bit glitchy, hanging, and unstable. I assumed it was a software problem, and something i had done wrong when flashing...but now I am wondering if maybe my phone is a lemon. Lately it has been rebooting randomly on its own,
I wanted to try flashing back to stock, just to start from scratch, and I did with Da G's stock rom . Then i just rooted it with Da G's root, and put on CWR. Then I flashed King Kang Rom. It's been still real buggy. Maybe I need to to stock ICS or JB then flash a ROM? OR maybe it's just this phone....either way not real happy with the stability i've been dealing with.
If youve tried multiple roms and stock roms and its still buggy then its probably the phone, I have got so many replacement phones that were duds
Are you doing a wipe between all those roms or just flashing one over the other? That could be a major problem that is easily fixed.
Yes, i do full wipes/factory reset in CWM every time.
I know i have seen some guys say you must flash like 3 times, so maybe i'm not flashing it enough times or something..? i also saw someone say don't touch your phone for 15 minutes after flashing. i have no idea if these tricks actually work or what. doesn't seem to be a definitive rule book on how to flash the right way
How are you restoring your apps? TB or letting Play reinstall them?
using TB. I usually do a just apps reinstall, then data
Was the TB backup from a different version of android, i.e. GB, ICS then installed on JB?
yes, i did create it on an ICS rom. you think that could be causing me problems?
Good possibility. I had the same issue. Moved from CM9 to CM10 and restored through TB. Lots of FC and reboots. Wiped and let Play reinstall everything, now its smooth.
great thought and worth a shot if that's what could be causing a problem. so did you lose all your data then with all apps? msgs, etc? sucks to start from complete scratch. i'll even miss call log
Lost data, but was able to d/l everything else. Messages and call logs were gone. It is worth it to have a working phone with out glitches. Let me know if it works.
Well a good test is to install a known solid ics problem free ROM like Padawan or Black ice? (exact name escapes me). If it works for u then over clock it to 1836 with setcpu and u will have a ROM VERY close to the JB rom smoothness but actually works.
If u still have problems then u may very well have a flaky phone.
(Oh yeah don't get to worried about stuff like wipe 3 times etc...old wifes tales. I haven't done that for over a year on 3 android phones. ). Also it is Safe to restore apps AND data with titaniumb (just not system data).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
+1 on the old wives tale. Seems more like a placebo effect. I only wipe once, and I've flashed roms on tons of phones.
Sent from my Galaxy Nexus using xda premium
tried installing padawan...so far so good, have not overclocked yet....will report back
Some roms will format your system partition prior to flashing the rom while others do not.
Beyond the wipe of data, cache, dalvik and such, it is wise to go into " mounts and storage" and format the system partition while in CWM recovery.
This ensures that nothing remains on the device before the new rom image is pushed to the system partition.
I agree that wiping 3 times is a bit over the top, but wiping the entire image base before flashing a new one is almost always mandatory.....g
For future reference, you can back up call and sms logs and restore them without causing lags or fc. The logs are simple .xml files.
Can anyone help.
I have recently started using Omega Rom...i previously was running stock JB.
I found Omega Rom V34 very slow, laggy and it crashed at least once a day.
I have just upgraded to V35 of omega.....its doing the same thing. Its just shocking.
With so many people using it and rating it so highly, it must be something ive done wrong as people would not use this rom as it is installed on my phone.
I used CWM recovery mode to install V34, i think its version 6.0.4? I got the CWM and rooted it etc through SGS3 Toolkit V6.
When i upgraded to V35, i simply, rebooted the phone into recovery mode using the new menu that i got from the V34 rom.
When it installs, it clears all the cache etc on its own.
When V34 installed i recovered all my apps using titanium backup. When V35 installed, for some reason all my apps were installed when it switched back on.
Any advice appreciated, im on the verge of going back stock!
Thanks
do a full wipe before updating
Glebun said:
do a full wipe before updating
Click to expand...
Click to collapse
I'm pretty sure that I did a full wipe using the Samsung galaxy S3 toolkit the time I stalled v34.
when I installed v35 just just used the installer so i don't think it did a full wipe.
Please advise the best tool for the full wipe. thanks
gaz_0001 said:
I'm pretty sure that I did a full wipe using the Samsung galaxy S3 toolkit the time I stalled v34.
when I installed v35 just just used the installer so i don't think it did a full wipe.
Please advise the best tool for the full wipe. thanks
Click to expand...
Click to collapse
i had been on omega and it was smooth as butter. perhaps there are apps that causes your phone to consume big memory and lag...
or you know, you can just flash another one if you are unhappy with it xD
saywhatt said:
i had been on omega and it was smooth as butter. perhaps there are apps that causes your phone to consume big memory and lag...
or you know, you can just flash another one if you are unhappy with it xD
Click to expand...
Click to collapse
Yeah,
I re-flashed with Android Revolution HD, and used the perseus Kernel.
Running sweet now!
Really happy with it so far.
If you're relying on the installer to clear your system and data partitions, that's where your lag and your crashes are coming from. You have to either use a Superwipe script which doesn't come with ARHD or Omega, or the much easier solution is to just clear cache/system/data partitions from recovery.
edit: let me know on here if you don't know how to do those things and I'll point you in the right direction to the best of my knowledge.
I have the same problem
Flashed latest version of OMEGA onto Samsung S3
Featurewise it's perfect, but there is an issue - like you say, it may be a clash with an installed app.
The lag is most noticeable when I bring up the Apps List, but I find over time it gets worse - if I reboot my phone it's improved again although the Apps List can still be slower than before to load.
I did think a likely candidate was avast, but I have the same issue if I don't use Avast.
Oh and I definitely wiped all relevant partitions prior to the install.
btw I'm not here to criticise OMEGA rom - didn't cost me a dime and lots of happy punters out there.
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Format
System
Data
Cache
Wipe dalvik
Then flash rom
Wipe cache again
Wipe dalvik again
Reboot.
--------------
alliances+siyah
iamdutchy said:
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Click to expand...
Click to collapse
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
chrismast said:
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
Click to expand...
Click to collapse
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
iamdutchy said:
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
Click to expand...
Click to collapse
SDS is, if I am not totally wrong, kernel related (btw @rootSU got a very informative thread about it). Hence the Android version does not matter that much whereas if a rom is using an "unsafe" kernel obviously it is not SDS safe. As described in that mentioned thread, if you upgrade recovery (newest CWM versions, e.g. philz) and kernel there should me not issue with SDS.