Related
Hi all, I hope you're not all tired of another noob posting up how-to questions. I come from a pretty solid background of writing modified firmware packages Motorola and Blackberry units, and writing custom themes for them both, so I am a bit familiar with the processes involved in rooting. Android is an entirely new beast though. I love it already, but I've also identified some things I'd love to be able to change. I've been reading everything I can in these forums for the past week, and I think I might be nearly ready to start diving into the root world. Yes, I've used the search a LOT Before I do root though, I wonder if you all might be able to add some insight into a few questions I haven't found the answers to thus far:
My rooting goals: remove the AT&T bloatware, possibly do a lag fix, and above all, do it the safest way possible. Baby steps first for me.
1) Rooting methods: Should I do the manual way, I found in that pdf guide on this site, the "GalaxyS_One-Click_Root_All_Models.zip" method, the mystery "update.zip" folder method, or the "one click root lag fix" method? Which is the safest and most tried and true for Stock 2.1 f/w, Baseband I897UCJH7? Also, what would be the best method to use if I wanted later to unroot?
2) Lag fixes: I've read that lag fixes can cause major problems when trying to undo them later on. Is there a lag fix that works well that is safer than others to load that can be removed easily? Are lag fixes even worth it?
3) Odin3: Am I correct in assuming that since I have JH7 that the most recent version of Odin is not capable of fully restoring my phone back to stock? I've been seeing posts from many people say that even using Odin, their phones get stuck during the revert process and cannot get back to stock. This is probably my biggest concern of all, in case I brick my phone. I've done that a LOT of times with Motorolas, and it's not a bit of fun trying to restore them.
Thanks very much in advance. Best wishes to all
The first piece of advice I have is make sure you have a cappi that you can get into recovery and download modes via the button combinations - if you can do this then you will be able to recover to a working configuration from just about any situation.
second, make sure you want to do this, because as you can get back to a "stock configuration" once you begin applying lag fixes or custom roms you will not likely be ever able to get back to your own stock configuration.
As for which rooting method - I have used and update zip and ryanza OCLF to root. Both of these methods are easy to unroot - at least until you begin applying lag fixes and/or custom roms.
If you are sure you want to move forward and root the very first thing you should do after rooting before you do any lag fixes or remove any bloat is get clockwork rom manager. Learn how to use rom manager and make a full nandroid backup of your phone before you do anything. If you have a good nandroid backup saved in a safe location then you can use this to get back as close as possible as you can to your own stock configuration later on.
Oden3 will get you back to a stock jf6 configuration. This will not be your stock configuration, but it is a working stock configuration.
Lag fixes do improve the lag in the file system some. However, before you play with any of them educate yourself as much as you can about the particular one you are going to try and use. I have applied both OCLF and voodoo and have been able to remove both of them. But if you don't follow the steps correctly you can have problems - after all with the lag fixes you are reformatting part or all of your data partition where the os is residing which is inherently risky. You can easily lose data and even soft brick your phone forcing you to use Oden3 to get back to a working state.
Lastly, I am running Cognition 2.2 beta 5 very successfully - and I do recommend it for anyone that has entered the rabbit hole of modifying this phone. And with my current config my phone is running so well that the lag fix is not needed for me anyway. My phone is running smooth and fast.
P.S. Just make sure you are not going to have any major regrets if things go wrong before you do anything at all, because any and all of these steps have some amount of risk associated with them. Make sure you are prepared for dealing with voiding your warranty and even though it is hard to brick this phone, it could still happen so be ready for that too should it happen.
i would agree, go with cognition 2.2. i only had my captivate for a day, and found it very easy to get it installed without any hassle.
Thanks for the info all. I've read about Cognition a fair bit and was wondering if I ought to go for it. What are the differences between it and the standrd Froyo leak?
A more pressing question: If I went to Cognition 2.2, would I be able to easily get the official release OTA and install it normally when/if it becomes available? Are there step-by-step guides out there for getting that release onto and off of the phone? I'd hate to get Cognition on there and find out that i couldn't easily get it back to a state where I could get the full deal on there. I've read some horror stories about just that lately...
charging rhinos said:
Thanks for the info all. I've read about Cognition a fair bit and was wondering if I ought to go for it. What are the differences between it and the standrd Froyo leak?
A more pressing question: If I went to Cognition 2.2, would I be able to easily get the official release OTA and install it normally when/if it becomes available? Are there step-by-step guides out there for getting that release onto and off of the phone? I'd hate to get Cognition on there and find out that i couldn't easily get it back to a state where I could get the full deal on there. I've read some horror stories about just that lately...
Click to expand...
Click to collapse
If you are wanting to get OTA updates then I wouldn't even root your phone - while it is possible to still get OTA's after rooting, once you begin modding (lag fix, or custom rom) you oare increasing making your phone less and les compatible with any OTA available.
NOTE: I personally will not ever apply an OTA myself - but rather will wait for someone else to create a custom mod of any OTA feature I like - them donate that dev a few dollars and use their mod.
Im getting my cap this Friday, I was going to post the same thing OP. Looks like cog 2.2 is the way to go when i get it.
I have been trying to find answers for a week now and have found a lot of info. The problem is most of the info is contradictory and I'm not really sure which is good and which is not. I currently have an AT&T Samsung Captivate, firmware ver 2.2, kernel ver. 2.6.32.9 build# FROYO.UCKB1. I believe that is the stock At&t froyo build. It is rooted, I do have SGS tools (which I don't really understand what all it can do for me) and Titanium backup (which I've not tried to use yet for fear of breaking my phone). I run 91PandaHome and a bunch of apps I like.
My problem is that the phone sometimes is just really sluggish, certain programs really kill it. For example, I have PlantVsZombies which mostly runs ok, but sometimes slows down and worse 3 out of 5 times I play will not close. I have to power/volume up reboot to get out of the game. Other programs occasionally do this to me, but not as often.
I've been reading up and see that there are lagfixes, and understand that samsung apparently chose a ****ty file system, but I don't understand android well enough to know what's safe. What I want to know is what is as of today the safest, easiest way to fix the lag. I think I am going to be told something that changes the file system to ext4 is what I want, but I really don't understand what will be safe to use for that. I thought I wanted OneClickLagFix, then I found that maybe Voodoo was what I wanted, and now it seems that neither is currently being developed. Reliability, ease of transition and ease of putting it back to stock are important factors for me.
Suggestions, links and general help will be greatly appreciated.
Try going to a custom rom where all of that is done for you. Since you are new to this, I suggest you go look up the rom Serendipity 6.4, it's very easy to install and has it's own thread in the development section.
fianor said:
I have been trying to find answers for a week now and have found a lot of info. The problem is most of the info is contradictory and I'm not really sure which is good and which is not. I currently have an AT&T Samsung Captivate, firmware ver 2.2, kernel ver. 2.6.32.9 build# FROYO.UCKB1. I believe that is the stock At&t froyo build. It is rooted, I do have SGS tools (which I don't really understand what all it can do for me) and Titanium backup (which I've not tried to use yet for fear of breaking my phone). I run 91PandaHome and a bunch of apps I like.
My problem is that the phone sometimes is just really sluggish, certain programs really kill it. For example, I have PlantVsZombies which mostly runs ok, but sometimes slows down and worse 3 out of 5 times I play will not close. I have to power/volume up reboot to get out of the game. Other programs occasionally do this to me, but not as often.
I've been reading up and see that there are lagfixes, and understand that samsung apparently chose a ****ty file system, but I don't understand android well enough to know what's safe. What I want to know is what is as of today the safest, easiest way to fix the lag. I think I am going to be told something that changes the file system to ext4 is what I want, but I really don't understand what will be safe to use for that. I thought I wanted OneClickLagFix, then I found that maybe Voodoo was what I wanted, and now it seems that neither is currently being developed. Reliability, ease of transition and ease of putting it back to stock are important factors for me.
Suggestions, links and general help will be greatly appreciated.
Click to expand...
Click to collapse
Just a few quick things:
Titanium backup is a good friend to have on your phone. It won't break it - it will just take snapshots (for lack of a better phrase) of your apps so that you can restore them later if you need to.
Most lagfixes are cooked into kernels, so using lagfix will most likely go hand-in-hand with flashing to a custom rom. Not that you can't lagfix stock, but statistically speaking, lagfix will be done with a new kernel via the Clockworkmod Recovery Menu.
As for general fixing of lagginess... (READ UP FIRST) Flash a custom Rom (READ MORE). Most of the problems you're experiencing (ARE YOU READING UP ON FLASHING?) should be fixed by flashing (DO MORE READING) a custom rom. Do some research on roms and pick one that you think you'll like. (Note - don't post questions asking which one to do, it tends to be a bit of a touchy subject on the forum.) If you're wanting to be cautious, it would be safer to stay with a Froyo-based rom, as they're more tested and there's less danger involved (specifically, you don't have to flash bootloaders, which is the area where you can get a real brick).
Oh, and (shameless self plug) if you need to know what different terminology and items on the forum mean, just click the link in my signature.
jmtheiss said:
Just a few quick things:
Titanium backup is a good friend to have on your phone. It won't break it -
Click to expand...
Click to collapse
Actually, it CAN break your phone if you don't know how to use it. Backing up is safe, but never, ever restore system data with TiBu when changing ROMs and only restore app data you know is safe.
I would recommend staying away from any Gingerbread-based ROMs until you have a better understanding of the phone and the process. Andromeda 3 is a good choice for a Froyo-based ROM and is very easy to flash, but do your research on the process before you attempt it. Almost any custom ROM will have a lagfix in the kernel and performance will be noticeably better than stock. You will likely have to redo your root after installing a new ROM, so read up on that process, too.
jmtheiss said:
As for general fixing of lagginess... (READ UP FIRST) Flash a custom Rom (READ MORE). Most of the problems you're experiencing (ARE YOU READING UP ON FLASHING?) should be fixed by flashing (DO MORE READING) a custom rom.
Click to expand...
Click to collapse
I lol'd at the "()" parts
To build on jmtheiss post. For "reliability" look for a KB1 based ROM as this is what your phone is currently running, and is the newest version of firmware written specifically for the AT&T captivate. You won't come across any major issues that make the phone unusable, nor any "annoying" bugs. Then if your feeling more adventurous, and have gotten a solid understanding of the process of flashing ROMs, look to I9000 based 2.2.x ROMs, and lastly 2.3.x based ROMs.
For "ease of transition" start by getting the SGS Kernel Flasher or Heimdall to change the kernel. From there you can get past 3e recovery and you'll be free to make other changes.
For "ease of putting it back to stock" first find out what is your stock. Since this phone technically has 3 different "stock" firmwares. Then get a copy of that firmware (and steps on how to flash it) and keep it on your computer, in a location you'll be able to find easily in case of problems. Depending on how far "to the dark side" you go, will effect just how much of the "stock" files you'll need to keep as backups.
Personally I'd suggest this ROM as it's whats currently on my phone. Many have started off with Cognition and it's still a crowd fav. Both are KB1 based ROMs
I was able to root my captivate, my specs are: 2.3.5- 1897UCKK4- kernel 2.6.35.7-I897UCKK4-CL614489 Gingerbread. Downloaded ROM manager and it doesn't list captivate when I try to flash clockworkmod, why? Also have OCLF and when I try to lagfix it says I don't have playlogos file. Can some help me out here. I am fairly new to this, but I think it has something to do with EXT2 not being EXT4?
Don't use ROM manager. You need to flash a kernel that has CWM baked in. You can find one in the dev section. Also, I'm pretty sure lagfix is not really used anymore
Sent from my CM9 ICS i897 Captivate
captivate
Thank, I used Odin and the kk4 kernel you recommended, seems to work good, but I was wondering how I can make my phone faster. I only get a 1240 with quadrant
Quadrant means nothing... Those scores are able to be manipulated by a single line of code.
root 2.3.5 CKK4
I was able to root my captivate, my specs are: 2.3.5- 1897UCKK4- kernel 2.6.35.7-I897UCKK4-CL614489 Gingerbread.
Click to expand...
Click to collapse
gj23, Thanks for listing the fw versions of your phone, I'm interested in how you were able to root your stock 2.3.5 Captivate. I have tried three the following root methods and all have failed.
1) Super1Click, freezes during su from file system errors in logs.
2) update.zip to sdcard, fails with file signature not recognized.
3) rageagainstthecage.zip, fails to reconnect to PC after adb disconnects; or terminal emulator freezes up.
So I'm wondering if AT&T didn't make this build harder to root.
Is there a rooted mod compatible with this phone build?
If so, Can I use a rooted mod and flash it without being rooted first to get root permission?
I have searched and read so hopefully I'm not wasting anyones time. These are my phone specs.
Model Samsung Captivate SGH-I897
Firmware 2.3.5
Baseband I897UCKK4
Kernel 2.6.35.7-I897UCKK4-CL614489
Build GINGERBREAD.UCKK4
^
Rooting kk4 is cake.
Odin flash mtcarey's Corn Kernel version 7.0a and reboot into Recovery. There is an option to Root.
U can find the Corn Kernel thread in the Captivate Development forum.
Sent by XDA Premium App
worked like a charm
Thanks for the info, I was afraid of compatibility issues with modem/kernel/bootloaders but this worked flawlessly!
Im trying to run 2.3.5 stock with lagfix
This is the only forum that comes close to my question.
what i am trying to do:
Run 2.3.5 Gingerbread stock (i have to official kies mini release)
apply a lagfix
debloat.
but i always get a random reboot effect.
i took a look into the Fasty Rom but the DL links are dead.
since this was the only rom that seemed to appeal to me right now.
I wouldnt Mind a Deodexed rom. but i want to keep it as much of a stock as possible.
I am still learning the captivate ways since this was given to me and i use it as a tablet.
the stuff i use.
I897UCKF1-AutoRoot-DesignGears.tar
CornKernel_UCKK4_v706.tar (v705 also causes reboots)
my potential problems are
init.d
CWM (kernel)
and debloating (have gotten cases where the reboots dont start till after i debloat.)
any information might help since ive searched google and the androidforums website.
but the lagfix seems to be intended for 2.2 and 2.1
EDIT:
ima be trying this in the mean time.
4-2ndtwin said:
Odin flash mtcarey's Corn Kernel version 7.0a and reboot into Recovery. There is an option to Root.
U can find the Corn Kernel thread in the Captivate Development forum.
Click to expand...
Click to collapse
so far its working wonders for me. ran through a whole tutorial of a game on an emulator.
im gonna fresh install and debloat.
1stRarewolf said:
This is the only forum that comes close to my question.
what i am trying to do:
Run 2.3.5 Gingerbread stock (i have to official kies mini release)
apply a lagfix
debloat.
but i always get a random reboot effect.
i took a look into the Fasty Rom but the DL links are dead.
since this was the only rom that seemed to appeal to me right now.
I wouldnt Mind a Deodexed rom. but i want to keep it as much of a stock as possible.
I am still learning the captivate ways since this was given to me and i use it as a tablet.
the stuff i use.
I897UCKF1-AutoRoot-DesignGears.tar
CornKernel_UCKK4_v706.tar (v705 also causes reboots)
my potential problems are
init.d
CWM (kernel)
and debloating (have gotten cases where the reboots dont start till after i debloat.)
any information might help since ive searched google and the androidforums website.
but the lagfix seems to be intended for 2.2 and 2.1
EDIT:
ima be trying this in the mean time.
so far its working wonders for me. ran through a whole tutorial of a game on an emulator.
im gonna fresh install and debloat.
Click to expand...
Click to collapse
As you probably noticed, Corn is probably your best answer for what you wanna run.
If you're looking into something with better performance, I'd suggest a JB ROM. That being said, this device will only go so far which the hardware it has.
Any recommendations?
BWolf56 said:
As you probably noticed, Corn is probably your best answer for what you wanna run.
If you're looking into something with better performance, I'd suggest a JB ROM. That being said, this device will only go so far which the hardware it has.
Click to expand...
Click to collapse
if this is true about the performance, how noticeable would it be?
and what Jellybean Rom Would you suggest that could give me a balance of performance and battery life?
which is something im going for right now.
so far the specs i have are running great but if there really is a way to boost my performance by more then 30% it would be a welcoming sight.
1stRarewolf said:
if this is true about the performance, how noticeable would it be?
and what Jellybean Rom Would you suggest that could give me a balance of performance and battery life?
which is something im going for right now.
so far the specs i have are running great but if there really is a way to boost my performance by more then 30% it would be a welcoming sight.
Click to expand...
Click to collapse
You won't get much more than what you're getting atm cause like I said, the hardware can only go so far.
As for ROM, we don't make suggestion (to avoid flaming). If you really wanna take on a JB ROM, look them up and choose the one that suits your style the best.
i see then...`
BWolf56 said:
You won't get much more than what you're getting atm cause like I said, the hardware can only go so far.
As for ROM, we don't make suggestion (to avoid flaming). If you really wanna take on a JB ROM, look them up and choose the one that suits your style the best.
Click to expand...
Click to collapse
oh, i see.
its hard to find all of them since theres so many threads with ROMs.
ill try and take a look. but it seems like it would be just more time spent on it then it would actually be beneficial.
With so many horror stories being posted, I don't know what to believe. When will it be relatively safe for us to update to ics?
I came from an HD2, and that was a treasure for flashing different roms. But it seems like the note is so easy to brick.
Edit: All I've done so far is root my note using Dr. Ketan's method.
It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.
I've flashed dozends of ROMs on my old HTC desire including ICS. At the end it worked always fine.
1. Backup
2. Wait after flashing - some roms need their time. After 10 min I've sometimes put out the battery to restart...
3. Enjoy
So don't fear!
I'm waiting for ICS OTA also. There have been lots of mixed reports with the previously leaked ICS ROMS - some bricked and some not. I've had a great run with flashing GB ROMs and Kernels but will wait for more official versions.
BTW - A colleague has a Note about four weeks old bought via the web. It turned out to be a German handset and he was successfully able to flash via KIES. I'm jealous - my Note 6 months old and I am still waiting for official ICS !
If you dont have any crazy combination of rom with custom kernel and cwm then is fine
Just dont wipe before flashing
And wipe after flashing
Sent from my iPad using Tapatalk
The fact that we have had ANY bricks at all suggests to me that this is not safe to flash, and even though I have been able to successfully flash LPY and run it, (not without problems), the bit that concerns me is the bricking due to large file copying which has been mentioned by various people.
Since I regularly copy large files to and from the device, I do not plan to subject my device to testing the theory.
I flashed ics yesterday and everything went fine, Iam always paranoid when comes to flashing but research before actual flash is vital! SEARCH button overheats and Iam ALWAYS following instructions!
Dont know what would I do without xda and those so capaple devs!
Galaxy Note!!!
I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.
nandihno said:
Just dont wipe before flashing
And wipe after flashing
Click to expand...
Click to collapse
Why is it safe to wipe after flashing and not before? I thought it was the other way around?
neos_83 said:
Why is it safe to wipe after flashing and not before? I thought it was the other way around?
Click to expand...
Click to collapse
It is the other way around.
Anyway, I fear this might be another superbrick in the making...
http://forum.xda-developers.com/showthread.php?t=1653290
And another one...
http://forum.xda-developers.com/showthread.php?t=1649982
vetchems said:
I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.
Click to expand...
Click to collapse
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.
to answer the original question... no... because i thoroughly read as much as i can find before i flash anything...even google it to see if there are problems ... hence i have ics rumming and running without any strange issues...
tbong777 said:
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.
Click to expand...
Click to collapse
I decided I did not want to "tip toe" around my normal processes with this device and went ahead and flashed CF Root with CWM. Going to need CWM to flash Roms and the LPY kernel has nt proven to be all that safe either. There is at least one case of a Superbrick wiping from Stock Recovery.
I bought these devices to mess with. I have a back up S2 and the s3 is out....Worst that can happen is I sell for parts.
well i am lucky so far as i dint have any issue with my note even after flashing lpy somany times from cwm may b me lucky till now
I'm terrified of flashing any roms on now after all the horror stories. I honestly don't even really care if I have ICS. I just hate how slow the stock ROM is. I would be very very happy with CM7 with SPen functionality.
This kind of sucks coming from an LG G2X which had so many stable roms and kernals to choose from
I thought a Samsung phone would have had even more but I guess not.
Probably like everyone else, I read Entropy's thread and became SUPER paranoid. He said there's no way to tell if you're slowly degrading the emmc or not unless you're on a 100% safe kernel / rom. I'm confused about the rest of the details. Apparently cm9 is 100% safe, but even the official ics can brick our note if we still have reminants of a leaked ics rom / kernel?
People alot more knowledgable than me have been bricking their note, so I will wait for an idiot proof method.
I would luv to see a step by step guide on video.
Also still dont grasp the fact that even if we put an official ics from Germany will won't get upgrades.
Sent from my GT-N7000 using XDA
I've been using lpy since release, and although I've had no problems so far, don't have cwm just root, but the more posts IM reading about people experiencing bricks from many different methods is definitively scaring me.
Chasmodo is a very reputable developer as is Entropy. I heed their words and will flash back to GB today, it's just not worth the risk.
Sent from my GT-N7000 using xda premium
Thijsvr said:
It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.
Click to expand...
Click to collapse
I also initially thought it was all speculation and anecdotal evidence. However, it appears that at least one user who has upgraded a brand new Note via Kies to LPY and wiped immediately thereafter has bricked his device.
That being said, I updated via PC Odin, rooted with temp CWM and full wiped from stock recovery thereafter without any issues (so far, been 3-4 days now). The performance improvements that ICS brings are significant, IMHO.
Basically, update if you really want to and refrain from wiping if possible (i.e. if you are not facing any FCs etc).
Greetings to all,
I am new to these forums as well as the curious world of rooting, flashing ROMS, etc, it is all very interesting to me. After simply scouring and reading for many months I have chosen to do a bit of tinkering with my new N7000. A few days ago I followed Dr. Ketan's guide here ----> http://forum.xda-developers.com/showthread.php?t=1424997 and used Odin to flash LPY (Open Germany). Everything was fine, however after reading a few posts about hardbricking, specifically this one by Entropy512 ----> http://forum.xda-developers.com/showthread.php?t=1633943 I realized that LPY was unsafe and heeded the warning to switch off of that version. Using the same steps I used before in Dr Ketan's guide I used Odin to go back to GB, specifically version N7000XEULA1 (Europe) which to my knowledge is the version my Note would have come with out of box living in Ireland.
After reverting back to GB I have been getting this warning "The process android.process.acore has stopped unexpectedly" with the option to Force Close. My instincts tell me to do a factory reset but I have read many posts about not doing any factory resets from recovery. Here lies my question: What is my next move if I wish to revert back to the currently available version of GB that would be available to me before I started tinkering? I realize now that maybe I need to do a little bit more research before venturing down the dark path of flashing ROMs as I have no interest in bricking my phone...eeek!
I am in Ireland running on the Meteor network. Current Kernal version is [email protected]#2 I never rooted my phone throughout this process to my knowledge.
Any assistance would be very appreciated and certainly rewarded with a "Thanks"
Good to wipe now you're on GB.
Cheers
Thanks for the response Towserspvm2000, much appriciated. I did as you suggested and all looks fine. I guess it is only dangerous to wipe from recovery while on ICS ROMs then? Are you only at risk of hardbricking if you are rooted and using LPY ICS or is unrooted LPY ICS dangerous as well? I went the unrooted route because I thought it was safer and more simple as I am new to this and trying to learn something. I appreciate what all you guys do. Thanks again.
Justinbuckley said:
Are you only at risk of hardbricking if you are rooted and using LPY ICS or is unrooted LPY ICS dangerous as well?
Click to expand...
Click to collapse
That is the 64,000 dollar question. Just don't wipe from any of the ICS roms. If i'm on ICS and something goes wrong, I always PC Odin back to GB before doing anything else. I've always had root too.
I much preferred ICS to GB, but I'm sticking to GB for now, until the delvelopers on here and/or samsung know where the problem lies exactly.
Yeah I much prefer ICS as well. I was on the HTC One X (a beast of a phone when it works, very powerful) which comes with ICS out of box but after having to return 2 of them because of hardware issues I came over to the Note. I love it but the lack of ICS is killing me, it's just a superior OS and the few days I had it on the Note were great but can't risk breaking such an expensive device. I'm with you on waiting until a more stable version is out so I'll cheer from the sidelines until I learn more. The amount of info on these forums is great but for a noobie like me it's a bit overload and no matter how much you read you still have questions (and I even work in IT so I'm not 100% lost)
@Justinbuckley I read somewhere in the forum a signature line which basically inspired me to venture into 'dark world of roms'.. The line was "Its not important which phone you have, what matters is how much you can mod it"
And ya, I think since you are on GB, you should go ahead and do a flashing again for any custom stable rom of GB first. I would suggest Rocket ROM or Check ROM.
This android.process.... Problem should get solved first
Thanks for the encouraging words. I didn't mean to suggest that I was put off of flashing ROMs and learning more about development, I just realized that maybe I bit off a bit more than I can chew initially. I will continue to read and learn from the big guys but maybe stick with GB based ROMs for now as they seem to be more safe. I will do some more scouring and perhaps try Rocket but isn't that also an LPY kernal which is what we have been advised to stay away from? Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for? Or are you limited to what you can flash if you are not rooted? Learning more by the day!
I will reply soon when I wake up.. and its alright. :beer:
Sent from my GT-N7000 using xda premium
Justinbuckley said:
Thanks for the encouraging words. I didn't mean to suggest that I was put off of flashing ROMs and learning more about development, I just realized that maybe I bit off a bit more than I can chew initially. I will continue to read and learn from the big guys but maybe stick with GB based ROMs for now as they seem to be more safe. I will do some more scouring and perhaps try Rocket but isn't that also an LPY kernal which is what we have been advised to stay away from? Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for? Or are you limited to what you can flash if you are not rooted? Learning more by the day!
Click to expand...
Click to collapse
Alright. Here is the ROCKETROM GINGERBREAD version(which I was talking about ):
http://forum.xda-developers.com/showthread.php?t=1380284
The GB version is pretty stable and good working. I always keep it as a backup GB ROM whenever I revert from ICS to GB.
Well, I would say that there are two types of ICS ROMs which I found and was quite ambiguous at the first time when I was a beginner. Here are the both:
1. RocketROM ICS V2: Based on LPY ROM. (Recommended*)
Link: http://forum.xda-developers.com/showthread.php?t=1654838
2. TeamRocket : which I believe is based on chinese leak.
http://forum.xda-developers.com/showthread.php?t=1507265
*If you want desperately the TouchWIZ based rom then go for RocketROM than TeamRocket.
Aye, RocketROM is ICS based on LPY (Boooo ! ) kernel. And it is risky. All LPY, LPF kernels are risky at the moment.
So if you want to move to ICS safely and also desperate to get the 'so far' best features out of your Note, then go for AOSP based roms. They are not cooked in a kitchen. They are properly developed. I suggest you should go for Asylum ICS or ParanoidAndroid or MIUI 2.0 etc. All these are based on CM9 Build which is safe.
About: Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for?
Ahh, see rooting doesn't have any effect on bricking as far as I believe. Its the bootloader which is acts as the bomb. And that slacky emmc bug in ICS is the trigger to make that bomb go off. So more than rooting and unrooting, the technique of install should be precise to what the Dev has prescribed. They surely know a gazillion more info than what any of us know
About: Or are you limited to what you can flash if you are not rooted?
I guess PC Odin should do its job for flashing phone without root. If you want to know more, refer to Dr. Ketan's Guide on how to flash the firmwares using Odin.
So, this is give you the crux of what's happening in the sea! xD
Always, think twice & read thrice before flashing any ROM.
Also remember, samsung knows how many flashes you have made till now
Good luck!
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
badjaguar007 said:
Alright. Here is the ROCKETROM GINGERBREAD version(which I was talking about ):
http://forum.xda-developers.com/showthread.php?t=1380284
The GB version is pretty stable and good working. I always keep it as a backup GB ROM whenever I revert from ICS to GB.
Well, I would say that there are two types of ICS ROMs which I found and was quite ambiguous at the first time when I was a beginner. Here are the both:
1. RocketROM ICS V2: Based on LPY ROM. (Recommended*)
Link: http://forum.xda-developers.com/showthread.php?t=1654838
2. TeamRocket : which I believe is based on chinese leak.
http://forum.xda-developers.com/showthread.php?t=1507265
*If you want desperately the TouchWIZ based rom then go for RocketROM than TeamRocket.
Aye, RocketROM is ICS based on LPY (Boooo ! ) kernel. And it is risky. All LPY, LPF kernels are risky at the moment.
So if you want to move to ICS safely and also desperate to get the 'so far' best features out of your Note, then go for AOSP based roms. They are not cooked in a kitchen. They are properly developed. I suggest you should go for Asylum ICS or ParanoidAndroid or MIUI 2.0 etc. All these are based on CM9 Build which is safe.
About: Is it valid to say that ROM flashing while unrooted is generally "safer" than flashing ROMs you need to be rooted for?
Ahh, see rooting doesn't have any effect on bricking as far as I believe. Its the bootloader which is acts as the bomb. And that slacky emmc bug in ICS is the trigger to make that bomb go off. So more than rooting and unrooting, the technique of install should be precise to what the Dev has prescribed. They surely know a gazillion more info than what any of us know
About: Or are you limited to what you can flash if you are not rooted?
I guess PC Odin should do its job for flashing phone without root. If you want to know more, refer to Dr. Ketan's Guide on how to flash the firmwares using Odin.
So, this is give you the crux of what's happening in the sea! xD
Always, think twice & read thrice before flashing any ROM.
Also remember, samsung knows how many flashes you have made till now
Good luck!
Click to expand...
Click to collapse
And ya I woke up
Thanks
Just a great post, I think I am going to go for one of the CM9 build ROMs as I think I should stay away from LPY for now. I know many of the ICS roms don't have s-pen capability which is really a deal breaker for me, I'll do some more research now to se if the CM9's do. ICS was promised in Q2 (and in Q1) so that should be by today if I'm not mistaken. What's the deal with Samsung? Sheesh!
Seems that there really is no added danger in rooting your phone and that there is a lot to gain from doing it. I may have to do this.
Glad you woke up from your beer coma! lol
i did the same thing
in my brothers phone we went from LPY TO ALC1
follow these instructions... there are for safely change any rom , go in ICS and back etc
the files you need are in a rar in my public drop box.. you have there ANYTHING you need without reading post after post and getting confused..
http://dl.dropbox.com/u/43609376/Steps for a Rooted GB/Steps for a safe rooted rom.exe
1. i connect the phone to the pc (while i have ticked in my phone
the "usb debuging " option ) you find it in "applications" -> development -> usb debuging
i wait for the pc to install the phone drivers
and i open Odin 1.85
thourgh odin i use the files of the folder
"Rooted_Stock_Odex_N7000XXLC1"
with the order showed in the pic "odin file order"
i press start .
the phone is now rooted and i just need CWM
2.
i choose in the folder
"CF-Root-SGN_XX_OXA_LC1-v5.3-CWM5"
the file "already-rooted.bat"
i follow the pc screen instructions and let the program do it's thing. when it's finished
it will tell me to reboot ...
now i have a safe rooted phone with CWM , (the program i need to have in my boot menu for endless custom roms)
NOW
3. for ANY custom rom .. GB or ICS ,that i want to install
I FOLLOW THESE GOLDEN RULES and i am safe...
Four steps to installing any rom for galaxy note
a. put the file abyss 4.2 into your phone reboot to recovery
choose install zip and then choose the file... now you have Abyss kernel.
b. press reboot to recovery ( just to be sure )
c.chose wipe Data, cache and in advanced the dalvike cache wipe
d. if you want to be extra cool reboot to recovery one more and
chose the custom rom of your choise (the one you have downloaded allready and placed inside the phone waiting
as a zip file..
YOU ARE DONE..
This is the universal instructions for any ics rom installation.
No brick and maintain root.
Justinbuckley said:
Just a great post, I think I am going to go for one of the CM9 build ROMs as I think I should stay away from LPY for now. I know many of the ICS roms don't have s-pen capability which is really a deal breaker for me, I'll do some more research now to se if the CM9's do. ICS was promised in Q2 (and in Q1) so that should be by today if I'm not mistaken. What's the deal with Samsung? Sheesh!
Seems that there really is no added danger in rooting your phone and that there is a lot to gain from doing it. I may have to do this.
Glad you woke up from your beer coma! lol
Click to expand...
Click to collapse
Haha. Chuckles! And ya I would say one more thing. Always before wiping and switching to any ICS, I made a policy to revert back to stable GB. Even though I don't expect you to follow that (I know its a tiresome process), but at the times of flashing risky kernel make sure you do go back to a GB
CM9
Must I be rooted to flash a CM9 ROM like Paranoidandroid?
Also, just to be clear, is this installation process different than when I flashed LPY using ODIN because that is the only kind I have done thus far. Haven't done the flash from the sd card yet.
Visit the Thread of Asylum ICS or ParanoidAndroid. I guess you should use search button. You will get it. And ya make sure you find the ROM under your phone's development section only Else many have wrongly flashed Samsung S2 ROMs
Search
I really have been using the search button, and have scoured that thread, I find the instructions for install to not be very beginner friendly which is why I asked. The fact many have flashed the SGS2 ROM is probably evidence of that I'd say. I'll keep looking though.