Related
Can someone give me link on how to properly root epic 4g
Former Army sergeant 11C
Next time check out the stickies before you post.
Here you go, http://forum.xda-developers.com/showthread.php?t=1009997
Take your time
Just wanted to tell you to read read read and take your time. The Epic is a little more in depth unit, and the best thing you can do is research. There is a lot of memory and ram tweaks, tons of roms, and tons of themes and hacks to use. I suggest going to YouTube and checking out some of QBking77's 'how to' videos, he has tons of great stuff and is really good about how he explains everything, he also is an avid supporter...meaning he definitely will get back to you if you have any questions. As the previous poster said, it is wise to read through as much as possible though, as this unit has been out awhile and there is a lot of information, I would say 95% of your questions are most likely already answered. But good luck!
Kchitown1977 said:
Can someone give me link on how to properly root epic 4g
Former Army sergeant 11C
Click to expand...
Click to collapse
Thank you for your service, sgt.
Sent from my SPH-D700 using Tapatalk
yea check out this dude.
put qbking77 on youtube
he's got all the info you could possibly need on sprint phones
Even with reading lots of threads it would be hard to know where to start.
What you need to know:
ODIN - a tool which lets you directly flash "stuff" (roms, kernels, recoveries) to your phone when in download mode. Find threads/directions to get this all setup because you'll need it. (drivers, etc) Be careful with Odin, it can brick your phone if you don't follow directions.
CWM 3101 - Current version of clockwork recovery mod. This is what you need to be able to flash things from the SD Card.
EI22 - Current version of Gingerbread OS. Don't use anything older. The stock kernel from samsung will overwrite any custom recovery at bootup, so if you want CWM you will need to use a custom kernel. Most (all?) custom ROMs include a custom kernel so if you go the route of a custom ROM this becomes a non-issue.
rocket321 said:
Even with reading lots of threads it would be hard to know where to start.
What you need to know:
ODIN - a tool which lets you directly flash "stuff" (roms, kernels, recoveries) to your phone when in download mode. Find threads/directions to get this all setup because you'll need it. (drivers, etc) Be careful with Odin, it can brick your phone if you don't follow directions.
CWM 3101 - Current version of clockwork recovery mod. This is what you need to be able to flash things from the SD Card.
EI22 - Current version of Gingerbread OS. Don't use anything older. The stock kernel from samsung will overwrite any custom recovery at bootup, so if you want CWM you will need to use a custom kernel. Most (all?) custom ROMs include a custom kernel so if you go the route of a custom ROM this becomes a non-issue.
Click to expand...
Click to collapse
rocket321, Very good information for the beginners.
Here is the link directly to QBking77. It's a step-by-step video explaining how to install my personal favorite ROM to date, "ACS ICS 4.0". Very clean look, very stable, pre-rooted, overclockable.
http://www.youtube.com/user/qbking77#p/u/30/GZCF5qXsn_M
Another thing worth mentioning is that only certain Kernel's with work certain ROM's. The kernel included in that ACS ICS ROM is the Samurai Kernel. I do recommend installing the "Samurai-2.6.35_gen1.0.4+" with the ACS ICS ROM at...
http://forum.xda-developers.com/showthread.php?t=1342047
rocket321 said:
Even with reading lots of threads it would be hard to know where to start.
What you need to know:
ODIN - a tool which lets you directly flash "stuff" (roms, kernels, recoveries) to your phone when in download mode. Find threads/directions to get this all setup because you'll need it. (drivers, etc) Be careful with Odin, it can brick your phone if you don't follow directions.
CWM 3101 - Current version of clockwork recovery mod. This is what you need to be able to flash things from the SD Card.
EI22 - Current version of Gingerbread OS. Don't use anything older. The stock kernel from samsung will overwrite any custom recovery at bootup, so if you want CWM you will need to use a custom kernel. Most (all?) custom ROMs include a custom kernel so if you go the route of a custom ROM this becomes a non-issue.
Click to expand...
Click to collapse
Good explanation, I didn't mean to sound off putting by saying do your own work and research...there are plenty of people in here willing to help, hence why I mentioned QBKing77; dude knows his ****, and his how to videos are great for noobs (myself included) and experts alike. I just believe you should do your homework...get some base knowledge, and jump in...you can learn a lot from how to videos, but you'll never get better of you just rely on other people to show you what to do.
Odin is key, get comfortable with this program.
sent Epically via XDA mobile
EI22 ACS ICS
One more thing...ditch the usb cable that came with the epic. Its crap. Go to best buy (or other mega store) and get a blackberry cable. You will need this for odin.
Sent from my SPH-D700 using XDA App
and if you love your keyboard, but hate that it tends to skip when you're typing too fast, a good rom is the way to go.
Yeah, definitely get rid of the stock Sammy mUSB, it was the cause of a lot of my initial problems. Blackberry and HTC cables have worked great.
Like I sad, these devices have been out awhile, and there is TONS of really great stuff available, check out the development section, and just absorb as much as you can...also, take advantage of the general and q and sections of the forum.
Good luck!
sent Epically via XDA mobile
EI22 ACS ICS
V6 supercharged, adrenaline injected
I am writing this because I know nobody has the time to go through all the threads.
People don't use the SEARCH button (there is no alternative to that..neither my rant here)
So tried to sum up all that I can here. Do let know below in comments if anything else is to be added or removed.I urge everyone to go through this complete post and I am sure you will find something interesting or something worth for you. If not then I am sorry for your 5 mins wasted !!
For all the members who are about to get their hands dirty or are already in the dirty waters! Welcome!
Just make yourself double sure that you are here and you are comfortable about playing with your device. Be okay with bricking it (yeah had to say this because whining and pointing fingers at others is not acceptable here)
Please avoid asking questions about rooting and stock roms in a particular rom thread. Let there be talk about that rom development and not rooting.
You want to root your device. Here you go – Rooting Guide by Dr Ketan
You want stock Roms – Here you go – Stock Roms by Dr Ketan again
You want Stock Prerooted Roms – Here you go – Stock Odex Prerooted Roms by Bodivas
PS - If you are using the Prerooted Stock Roms from the above link then after PC ODIN flash of the stock rom of your choice just download the corresponding CF Root Kernel (i.e. if you flashed LC1 Rom, download LC1 CF-Root kernel) and flash it through Mobile Odin to inject CWMR. Done.
You want all the Safe kernels - Here you go - [ICS][GB] Kernel Repository
So you are now rooted. Now as per Samsung your warranty is now void. Congrats. Remember you only did it and you only wanted it. So cheers!! Pour yourself and me a beer
Now go flash any GB custom rom you like choosing from here – GT N7000 Development Thread
Okay remember to read the changelog and the Features. Don’t crib for the features that are not included. You don’t like the rom and features move on. Don’t curse the developer for it.
Very Famous Example- asking for touchwiz features like SMemo, SPen gestures in APOKP/AOSP roms. Blasts on your way. Better reading about them here by Chasmodo - Flash ICS and Survive
Who wants GB now. All wants the cool IceCream!
Okay so WAIT.
Now remember there are much serious repercussions in getting to ICS than doing all the above stuff with GB.
Here this is to be read very first – Hard Bricking Kernels Public Announcement by Entropy
NEVER perform any sort of WIPE or FACTORY RESET when on Stock ICS Kernel/Rom (rooted or non-rooted)
DO NOT try to go to any CM9 or CM10 based rom from the Samsung ICS rom/kernel. Sure shot BRICK.(those who haven't got bricked by doing this consider your self lucky...huh) Best way is to - Go to GB > root > then flash any CM9 based rom.
Only These roms are termed completely safe till now and are build on safe kernels till the time Samsung doesn’t release the source code and we have plethora of kernels like in GB.(will keep adding to the list)
CM9 Nightlies
Asylum ICS
MIUI
ParanoidAndroid
HALF-ILLUSION
All other ROMs that are based on the CM9 source.(info about it in the OP of each ROM thread...must read always)
The stock ICS roms which are on custom kernels like Franco / Speedmod etc which have MMC_CAP_ERASE command disabled.
There are many ROMs in the dev section which are based on LPY kernel. They too work perfect but still have the volatility and the warnings applied as the LPY is not that safe. So flash on your own risk and don't pester the Devs of those roms about question of safety and security. Read the above Public Announcement and decide which way you want to go!
Now some more info. Always before doing any of the flashing
Check your current kernel from
Settings > About Phone > Kernel Version .
Do NOT flash from the following kernels:
i9220ZCLP1
i9220ZCLP5
i9220ZCLP6
N7000XXLPY
Some most asked questions.
Q1 –Man m already on one of these kernels. Now waaahhhat?
Don’t panic. If you are on the rom which includes any of these kernels then refrain from flashing anything in the CWM. If the rom you are on presently is good for you just be there and don’t go on experimenting on the unsafe kernels. Wait for the stable safe kernls to come out.
Or
Switch to any of the above safe roms.
Before going to any of the safe roms go back to stock GB. Use PC Odin.
Here we have another complication. Check this thread. LPY to GB via PC Odin = super brick? This might be the fix of these Superbricks - Here
Now best way is always PC odin. And it still is unless your EMMC is not already damaged by using the wipe function . Check Here Above case happened to some users but most of the users whent back successfully. Now always remember to use PC odin when you have installed all the drivers. If you use Windows 7 PC then always check for the Online Searching for Drivers in the notification bar on your PC. This should be stopped or completed before doing any PC odin activity.
IMP - You can use Mobile Odin. But make sure first that the rom you are on and using the Mobile Odin that is having complete root by pasting any file in the root folder which is /system (use any file explorer with root privileges)
Once on GB, root it. If you going for the Pre Rooted Stock Roms remember you will have to inject the CWM using the CF Root zip from Chainfire’s thread for any subsequent flashing you want to do or use Mobile Odin (remember to check complete root status before using it)
Q2 - I am already on CM9 or Asylum or MIUI can I try the stock ICS German release?
Sure you can try but with no CWM. It sucks so recommendation is don’t try. Be on the safe roms and wait. And I bet they are much better and smoother than the stock. There are some cases of bricks with LPY having root when flashing in CWM or doing intensive I/O tasks.
There is no reported harm to flash ics without cf root(stock kernel + root no cwm) Check the Official ICS Flashing guide by Dr ketan again (Man this guy helps the Note community a lot )
Q3 – Man I am on GB and it sucks. I want ICS.
GB doesn’t suck in this case. At least you have your device working. If you are not comfortable enough with all the cautions and thin lines to tread its better to stay on GB a little longer. If you daring enough go tread on the lines of ICS but don’t cry over the brick you might achieve if you are not careful enough.
Q4 – I cant paste into /system folder nor can change DPI.
You have lost root. Kindly PC ODIN (only and only PC Odin) back to GB and then get it rooted (or flash pre rooted rom then inject CWM or use mobile odin now after flashing the pre rooted rom) and then flash the ICS rom of your choice (better stick to the safe ones…if not your wish)
Q5 – Am Senior Member I Know my way in and out and daring enough to tinker. All Warnings Applied
So you don’t want the Odin back to GB. Well then you have the Abyss Note 4.2 Kernel with Redpill Touch recovery. You are on any unsafe kernel ICS Rom and you want to go to safe rom then do one last CWM flash of Abyss kernel reboot recovery and then flash the safe roms. This keeps your root intact. You can even acieve root though this if you have lost it. Just flash Abyss 4.2 go to GB. Check root there and then flash the ICS rom. No need of repack. If any of this gets struck or brick then you know your way out already…..you told that in the question. My little guide here. Link for Abyss 4.2 Kernel in the guide.
Q6 - Most asked in the rom threads – I want the LP5 and LP6 modems. Here please.
Q7 - I want to go to LPF or whatever stock kernel ICS. And is it safe?
PLEASE dont go that route. Better stay on GB or root it and flash any of the CM9 kernel based rom. Please humble request!! :angel: Ask why in the comments if you don't get it by reading all the info in this post.
Q8 - The ICS source code is out. Where are the new kernels?
Yeah the SGN ICS sources are out. Check HERE
Wait for the developers to wield their magic and you will have the awesome kernels out for you in no time! Patience is the key
Q9 - I seriously want the safe CM9 kernel. Where is it?
Search for it in the CM9 thread. But i know many of you wont do that. So just to make this OP a lil more lengthy and one stop kind of shop m attaching the file below. Thanks Xplodwild. Flash the extracted zImage using mobile odin. Its a safe kernel so you can use its CWM anytime you want.I cant say with what all roms it will work. Might break some features in some roms so flash at your OWN RISK.
Q10 - What about the new ICS kernels??
Well the safest kernel CM9 is attached and the other one by Entropy's DAFUQ kernel got updated too. Franco and Speedmod kernels are build on the latest ICS Sources and have the formatting of MMC is blocked. So you are safe from damaged MMC bricking bug but not sure about the any other bricking bug on that as two users (AFAIK) reported bricks in the Franco kernel thread.
Also look for as Entropy told here - "install CPUSpy and make sure you don't see "se.infra" anywhere - that's the buildhost of Samsung's own kernels which are dangerous"
Be safe, Play safe. Check their change-logs...what works and what not and where and what roms you can install them on!
Q11 - I want to jump off from the unsafe kernels. How ???
A quick guide from Chasmodo - Here And lil Info about Mobile Odin Here
Q12 - Brick! Brick Brick!! What Man everywhere i read this on ICS!! Why is it so happening??
Well, as very well explained by Entropy -
"We now know there are three things that are ALL needed for this to happen:
1) A recovery (can be the recovery itself OR it can be the update-binary in a ZIP you flash!) that performs ERASE commands in addition to formatting. (GB recoveries and update-binaries don't do this, ICS ones do)
2) A kernel that allows those ERASE attempts to actually go through. (Disabling MMC_CAP_ERASE prevents this.)
3) Buggy eMMC firmware
Basically:
In Gingerbread, condition 1 was not met (However, this isn't guaranteed - if a Gingerbread ROM developer happens to accidentally grab an ICS update-binary in his installation ZIP, this COULD brick!)
In I9100 ICS releases, condition 2 was not met due to MMC_CAP_ERASE being removed
Condition 3 is true for nearly every GT-I9100, SGH-I777, SPH-D710, and GT-N7000 ever sold."
So got it ? Wanna get your minds more widen with the knowledge on this aspect - Visit HERE
Q13 - Got Brickbug ???
CHECK HERE - Thanks Chainfire
Q14 - I want to have CM10 on my rom!! How to??
Check on what kernel you are on. Any Stock ICS kernel or any kernel based on stock ICS sources then go PC odin back to GB (just read the above conditions on wiping and factory restoring first). Now get root on your GB. Install a CM9 based rom and after that install CM10 rom. For people being extra adventurous you can use the CM9 safe kernel to switch between roms. :angel: And never forget doing full wipe before coming to CM10
Don’t use any repacks now please. LP1 is a NO NO ! And don’t even think about the other one!
To Devs – If you find this guide or rant useful then please link in your OP. Thanks for your great work and time you invest you us. You are providing all this awesomeness free of cost. Hats off to you all !!
Respect them people. Or read this - Show your Support, Don't Whine by toxicthunder
To All Members – If you find this useful kindly hit the thanks button. And remember to read OP of each rom thread!!
Happy Flashing and Enjoy your Notes !I would like to quote+edit from toxicthunder post.
If something goes wrong, cry yourself a river.
But then don't forget to build a bridge and get over it.
A highly recommended and awesome and handy extension for you all (Thanks Toxicthunder)
*Galaxy Note Toxic Toolbar* - Check it out
Lastly thanks to Chainfire , Entropy512 , Xplodwild , Dr Ketan , Original_Ganjaman , Chasmodo , Antiochasylum , Matius44 , Tremerone , Toxicthunder , Androidindian , Geo.Samuel for all the help and support you guys have provided to me and the community.
And just in case you thought this have helped you save your precious time and device and you have some pennies to spare , Then you are most welcome todonate here This will encourage me more
Reserved for some future addons
For Mac Users - read Heimdall instead of PC Odin
Thanks for this it will be very use full to many who choose to take the time to read fine work thanks
Will be linking this in my OP.
As long as people READ it, very very good info.
Looks great brother!
.....like Anti said....hopefully people will READ it and understand. It's pretty crystal clear if you ask me.
Good summary!
Impeccable. Must read for every user.
If I had my way, this post should flash on each and every user's screen before he clicks on the "Post Quick Reply" button.
Many thanks for this!!
A good summary of our current and somewhat unfortunate ICS situation.
So the new LPF firmware/kernel is it safe? Because I saw some members wipe etc. and say it works fine except it doesnt restore. but is it safe from bricks?
androidindian said:
So the new LPF firmware/kernel is it safe? Because I saw some members wipe etc. and say it works fine except it doesnt restore. but is it safe from bricks?
Click to expand...
Click to collapse
It's early days yet. Be patient and we'll see.
Good one dawg!!
But if everybody had an habit of reading.............
Great work mate, added to the sticky list
Thanks Friends for all the support!! Yeah the only effort one has to do is to read. I made an effort to bring as many things as possible under one thread/OP. If not 100 threads then at least read this one. Yeah it still has so many threads linked but at least most of the info that is strewn in many threads i have tried to catch up here with direct linking. Will keep updating as new things keep popping. The first on the list being the LPF. Update in a couple of hours
Hope it helps all !!
Ah...and thanks OG for the sticky
Awesome thread.... for the awesome phone
Sent from my GT-N7000 using XDA
Great thread.
With so much information flowing these days, it's hard to keep track of what's going on.
Also, I had no idea that going back to GB from LPY may hard brick.. **** this.
Very well written post mate might recommend you as an editor trainee under the supeevision of our guru chas
Seriously though, very helpful thread and I really wish more and more members read it first.. Congrats on the sticky, well deserved
Cheers mate
Nice and concise.... Much appreciated
Sent from my GT-N7000 using xda premium
I found this threat very usefull..thanks mate
Sent from my GT-N7000 using Tapatalk 2
First off GREAT POST ABHISAHARA!!! A thanks is coming your way . Soooo..... after reading your initial post, the the LPY to GB via PC Odin = super brick? thread, and THEN the how to revert back to gb from lpy ics View Single Post thread. I have a "decent" grasp on where I'm at. I was one of the gunslingers that jumped on board the LPY on day 1. I was on rooted (GB or ICS Repack, can't remember honestly) and installed LPY Stock unrooted via PC odin. It did NOT wipe all my data so i'm assuming that means I did not do a full wipe (seems like a good thing from what I read), I really would feel better if I got off of this and went back to GB. I understand if my phone works fine I should sit tight, but I do deal with large movie files on a reg basis. The steps are where it gets grainy.
What I plan to do:
1: Connect via pc odin and flash only the abyss kernel 4.2
2. Connect and flash the 3 file Rooted GB rom
3. Finally wipe everything
Could someone just tell me if a: I am being flat out stupid and should really stick with what I got, or b: let me know if what I plan to do is a best course of action for taking this plunge. Thanks in advance guys!!!
A very nice piece of work that should be read by every member.
Sent from my GT-N7000 using XDA
I purchased a new Samsung Galaxy Note approximately 2 months ago on a rather long 24-month contract at £27 GBP per month with unlimited data, 500 minutes and 5000 texts. So far, the phone has impressed me immensely but I have been disappointed to discover yesterday that the ICS I updated to around 3 weeks ago is likely infected with the infamous "brick bug".
I know that the initial recommended solution for this is simply to root and change your kernel, yet being only 14 and this my first proper Android device (minus an old second-hand HTC Desire which I only used for around 3 months) I simply don't have the technological know-how to pull this off. I've also heard of a potential fix from Samsung coming soon, however. So, what is it I should do - change kernels and risk messing it up or keep the same kernel (waiting for the fix from Samsung) but have the risk of bricking my phone if I delete a lot of data in one go?
If my phone were to brick due to this bricking bug, would it be covered under a warranty from Samsung? If I should change kernels, how should I go about doing this? Is this rooting guide here safe to follow for ICS or is it Gingerbread only? Once my phone is rooted, how do I change kernels, which kernels do you recommend and will changing kernels cause me to lose data such as contacts and apps? How is changing kernels different from flashing ROMs?
EDIT: Kernel info is available here.
What rom do you have in your phone? Gingerbread or ice cream sandwich?
jonpaslim said:
What rom do you have in your phone? Gingerbread or ice cream sandwich?
Click to expand...
Click to collapse
Stock Samsung ICS ROM, which also has an infected kernel as you might expect. It was mentioned in the opening post anyway. So, any ideas on what I should do? Someone? Help!
Nobody willing to help?
i've had the same problem too and to me i felt that with all the hype with official ICS the con's (brick bug, horrible batter drain, no deep sleep, wakelocks and unfortunately for me - a mysterious overclocking of cpu) far outweigh the pro's...
so after being on official ICS (LP9) for a busy week full of tweaking, fine tuning, hours of reading, searching for fixes on the bugs... i just felt it wasn't worth it and flashed back to GB, wiped data and rooted it
couldn't be happier, my phone now sleeps like a baby when screen is off. battery lasts me at least 48 hrs with moderate to average usage
my suggestion is go back to GB, root it and enjoy the device and the many wonderful custom ROMS with little risk of bricking it... as long as you read (and do your homework) before flashing a custom ROM you'll rarely go wrong..
just my personal opinion though... others may feel differently so at the end of the day its still personal preference
I do really appreciate developers in developing safe kernel for ICS..
Of course most of them make what is thought to be bugless kernels but I prefer SpeedMod Kernel...
If you are interested you can follow one of the following methods to get root access and CWM recovery (These methods are only suggestion but you can stick to which one you prefer..)
Method #1:
Use rooting method provided by dr.ketan "the rooting part only" (click here)
Then install Mobile Odin Pro from the market... Then flash any custom kernel by Mobile Odin Pro (suggestion SpeedMod k3-3 kernel)
By doing these steps, you will have root and CWM recovery in the end
Method #2:
You can just install SpeedMod k3-3 kernel by PC Odin without a need for dr.ketan method and you will end up having root and CWM recovery in the end; but I don't know if this is going to increase binary count in download mode or not... So the safest is to go through the first method mentioned..
Cheers
scarlet_sg said:
i've had the same problem too and to me i felt that with all the hype with official ICS the con's (brick bug, horrible batter drain, no deep sleep, wakelocks and unfortunately for me - a mysterious overclocking of cpu) far outweigh the pro's...
so after being on official ICS (LP9) for a busy week full of tweaking, fine tuning, hours of reading, searching for fixes on the bugs... i just felt it wasn't worth it and flashed back to GB, wiped data and rooted it
couldn't be happier, my phone now sleeps like a baby when screen is off. battery lasts me at least 48 hrs with moderate to average usage
my suggestion is go back to GB, root it and enjoy the device and the many wonderful custom ROMS with little risk of bricking it... as long as you read (and do your homework) before flashing a custom ROM you'll rarely go wrong..
just my personal opinion though... others may feel differently so at the end of the day its still personal preference
Click to expand...
Click to collapse
ICS has been problematic for the Galaxy Note for me, like many other people too, but I still think it is worthwhile having the latest version of Android especially with talks of 4.1 and 5.0 coming soon. It won't be long before 2.3 becomes old and redundant.
majdinj said:
I do really appreciate developers in developing safe kernel for ICS..
Of course most of them make what is thought to be bugless kernels but I prefer SpeedMod Kernel...
If you are interested you can follow one of the following methods to get root access and CWM recovery (These methods are only suggestion but you can stick to which one you prefer..)
Method #1:
Use rooting method provided by dr.ketan "the rooting part only" (click here)
Then install Mobile Odin Pro from the market... Then flash any custom kernel by Mobile Odin Pro (suggestion SpeedMod k3-3 kernel)
By doing these steps, you will have root and CWM recovery in the end
Method #2:
You can just install SpeedMod k3-3 kernel by PC Odin without a need for dr.ketan method and you will end up having root and CWM recovery in the end; but I don't know if this is going to increase binary count in download mode or not... So the safest is to go through the first method mentioned..
Cheers
Click to expand...
Click to collapse
This is going to sound stupid, but I have know idea what you just said really. What's Odin or Binary Counter or any of that stuff?
Any ideas on also how to get my phone to deep sleep?
if you have to ask what is binary counter and/or odin, you are threading on dangerous grounds. i say STOP! right now and start READING all the STICKY threads in the development section.
your phone being on stock, untouched state i think the chances of you bricking it is very slim, if non-existent.
as for your deep-sleep issues, how did you determine that your phone does not go into deep sleep?
praetorius said:
if you have to ask what is binary counter and/or odin, you are threading on dangerous grounds. i say STOP! right now and start READING all the STICKY threads in the development section.
your phone being on stock, untouched state i think the chances of you bricking it is very slim, if non-existent.
as for your deep-sleep issues, how did you determine that your phone does not go into deep sleep?
Click to expand...
Click to collapse
Well, I keep being told I shouldn't be using the stock ICS firmware due to a brick bug, but I don't plan on flashing a new ROM or wiping data for a factory reset so I should be safe - no? As for deep sleep, I know this from CPU Spy.
Brad387 said:
This is going to sound stupid, but I have know idea what you just said really. What's Odin or Binary Counter or any of that stuff?
Click to expand...
Click to collapse
You are not joking, right???
If you don't know what is Odin or binary counter>>>> PLEASE STOP HERE RIGHT NOW
You have to read more before attempting to root, flash or doing anything to your note
The forum is filled with tutorials of these stuffs
>>>LEARN TO READ FIRST<<<
majdinj said:
You are not joking, right???
If you don't know what is Odin or binary counter>>>> PLEASE STOP HERE RIGHT NOW
You have to read more before attempting to root, flash or doing anything to your note
The forum is filled with tutorials of these stuffs
>>>LEARN TO READ FIRST<<<
Click to expand...
Click to collapse
Well, I keep being told I shouldn't be using the stock ICS firmware due to a brick bug, but I don't plan on flashing a new ROM or wiping data for a factory reset so I should be safe - no? As for deep sleep, I know this from CPU Spy.
Here's the steps you need to follow:
0- Back up all your media to your PC (movies, videos, photos, pictures, documents, music, voice recordings, etc etc)
1- Back up all your personal files (contacts, sms, call log, apn)
2- Root Gingerbread ROM (CF-Root, doesn't increase flash counter, no Triangle)
3- Back up all your Apps (Titanium BackUp Free)
4- Back up your EFS system folder (has imei etc, just to be safe)
5- Back up everything NANDROID
Then:
-UnRoot the Gingerbread ROM (don't hide it and risk a buggy update)
-Apply the OTA to Official Samsung ICS (4.0.3)
-Use PC Odin to flash a SAFE (TouchWizz) kernel, choices include:
--Franco (v5), Speedmod
-Reboot
-TriangleAway (reset counter)
Now you have official Samsung TouchWizz ROM, Android 4.0.3, cwm recovery, safe Samsung kernel with root and busybox.
Finalize Official Samsung ICS Update:
-Test if everything works
-Do a NANDROID backup (now you have TouchWizz ICS backed up, if you want S Pen/TWizz Apps)
-Issue updates for any Apps
-Back Up your Apps again with Titanium BackUp (for the ICS Samsung Apps)
-Restore all your media (after you nandroid, so its not too bloated)
And hopefully that will be a "good enough" experience for you, otherwise proceed below.
And if you want a better experience:
--Use CWM to flash the (AOSP) ROM of your choice from recovery (eg ParanoidAndroid)
-Wipe wipe wipe (Dalvik, cache, factory reset)
-Use CWM to flash a SAFE (AOSP) kernel, choices include:
--Thor(v12), XPLODWILD, DAFUQ, or updated CF-kernel
-Fix permissions
-Reboot
Now you have a Pure Google/Stock experience, Android 4.0.4, cwm recovery, custom ROM and custom KERNEL with root and busybox.
Finalize your custom firmware:
-(Optional) From CWM, flash Google Apps (Play Store etc) if they aren't included in the rom (most roms have it pre-installed)
-Download Titanium BackUp from Play Store
-Restore all your apps
-Restore all your personal files (contacts, sms, call log) (apn only if necessary)
-Test if everything works
--Play around with the ROM (features etc) and the KERNEL (test O'C, U'V, Stability and Battery Life)
-Nandroid backup (if you want)
-Restore all your media (after you nandroid, so its not too bloated)
For any of the steps that you don't know how to do it. Search for it here on xda, or Google. I would recommend RootGalaxyNote website and YouTube videos for easy to understand instructions. Most people are happy to help as long as you post in the correct thread for each step.
After completion, if you wanted/went as far as custom aosp kernel and rom, maybe some O'C and U'V, I'd formally say you've graduated Android 101. And that you should be able to do many other things, otherwise have the capacity to learn them
Brad387 said:
I purchased a new Samsung Galaxy Note approximately 2 months ago on a rather long 24-month contract at £27 GBP per month with unlimited data, 500 minutes and 5000 texts. So far, the phone has impressed me immensely but I have been disappointed to discover yesterday that the ICS I updated to around 3 weeks ago is likely infected with the infamous "brick bug".
I know that the initial recommended solution for this is simply to root and change your kernel, yet being only 14 and this my first proper Android device (minus an old second-hand HTC Desire which I only used for around 3 months) I simply don't have the technological know-how to pull this off. I've also heard of a potential fix from Samsung coming soon, however. So, what is it I should do - change kernels and risk messing it up or keep the same kernel (waiting for the fix from Samsung) but have the risk of bricking my phone if I delete a lot of data in one go?
If my phone were to brick due to this bricking bug, would it be covered under a warranty from Samsung? If I should change kernels, how should I go about doing this? Is this rooting guide here safe to follow for ICS or is it Gingerbread only? Once my phone is rooted, how do I change kernels, which kernels do you recommend and will changing kernels cause me to lose data such as contacts and apps? How is changing kernels different from flashing ROMs?
EDIT: Kernel info is available here.
Click to expand...
Click to collapse
Easy Peasy.. If you are on ICS, flash speedmod k3-3 kernel via PC ODIN, this will give you a) a safe kernel b) a yellow triangle and a custom binary count which can be easily removed with chainire's app called remove yellow triangle.
Cheers
Brad387 said:
I purchased a new Samsung Galaxy Note approximately 2 months ago on a rather long 24-month contract at £27 GBP per month with unlimited data, 500 minutes and 5000 texts. So far, the phone has impressed me immensely but I have been disappointed to discover yesterday that the ICS I updated to around 3 weeks ago is likely infected with the infamous "brick bug".
I know that the initial recommended solution for this is simply to root and change your kernel, yet being only 14 and this my first proper Android device (minus an old second-hand HTC Desire which I only used for around 3 months) I simply don't have the technological know-how to pull this off. I've also heard of a potential fix from Samsung coming soon, however. So, what is it I should do - change kernels and risk messing it up or keep the same kernel (waiting for the fix from Samsung) but have the risk of bricking my phone if I delete a lot of data in one go?
If my phone were to brick due to this bricking bug, would it be covered under a warranty from Samsung? If I should change kernels, how should I go about doing this? Is this rooting guide here safe to follow for ICS or is it Gingerbread only? Once my phone is rooted, how do I change kernels, which kernels do you recommend and will changing kernels cause me to lose data such as contacts and apps? How is changing kernels different from flashing ROMs?
EDIT: Kernel info is available here.
Click to expand...
Click to collapse
Read the information give by Ayush770 on this page
http://forum.xda-developers.com/showthread.php?t=1670137&page=2
Then READ ALL of these pages then READ them again do not skim READ
dr Ketan http://forum.xda-developers.com/showthread.php?t=1424997
Chainfire http://forum.xda-developers.com/showthread.php?t=1331784
CW9 http://forum.xda-developers.com/showthread.php?t=1627854
there is loads of information if you are unsure READ again, make a plan of action & post it for comments (it may take time )
Once your ready & get started! Boy what a rush! first time you squirt something into your phone!!!
itsmix said:
Once your ready & get started! Boy what a rush! first time you squirt something into your phone!!!
Click to expand...
Click to collapse
+1 very good advice generally plus great closing statement
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Galaxy Note N7000.
Was running stock ICS-ROM Samsung.
Always wanted to install and use a custom ROM but was always afraid of BRICKS..
But yesterday ended up being sucessfully running CM9.
Steps I undertook were as follows:
1. Installed Samsung Kies.
2. Check for update from Samsung Kies and updated Kies.
3. Connected my phone to Kies and checked if Kies detected the phone properly.
After sucess, exit Kies.
4. Downloaded PC Odin from this link
http://forum.xda-developers.com/attachment.php?attachmentid=815370&stc=1&d=1323799721
password:samfirmware.com
5. Download pre rooted GingerBread ROM
SGN_XX_OXA_KJ1_FACTORYFS.zip (thx dr.ketan)
http://d-h.st/HJM
6. Run PC odin
7. Reboot Note in download mode
vol. down+home+power buttons
8. Connect Download mode note to PC
9. PC odin ID:COM turns yellow:
(ALL THE BEST NOW)
10. In PC ODIN
Auto Reboot and F.Reset Time ---> Ticked
Others --> Unticked
10. Click PDA and select the SGN_XX_OXA_KJ1_FACTORYFS.zip you had downloaded.
Click start.
Wait for 10minutes.
Your phone will restart.
11. WOW..!!! now ur on a GB Rom
And its a safe kernel
Now you can play around
Plus already rooted
12. Now to get this GB Rom working
go to recovery mode (vol up + home + power)
clean dalvik cache and wipe data and factory reset
13. Time to install CM9
14. Download
CM9 latest nightly:
http://get.cm/?device=n7000
Googleapps:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
15. Copy these 2 files in the internal SD card anywhere (do not rename)
16. Reboot into recovery mode:
vol up + home + power
17. Flash the 2 files from where you saved them:
"install zip from sd card" option in recovery mode
now flash cm9 file
then flash gapps file
18. DO A DATA WIPE / FACTORY RESET
19. Reboot
And wow..
Enter the world of custom ROMS
[[[to switch to another ROM, follow steps 1 to 17, and after that flash the ROM of your choice]]]
Steps 6 and 9
it shud be PC Odin Not Mobile
sorry dr. ketan
my mistake
corrected
thanks
So...
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.
dr.ketan said:
Steps 6 and 9
it shud be PC Odin Not Mobile
Click to expand...
Click to collapse
Noticed that u are very experienced contributor, so mybe u can answer on my question, does the step by step guide is safe for galaxt note with brickbug? I realy want to flash, but i want to do it if i am on the safe side
Latvianization said:
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.
Click to expand...
Click to collapse
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!
SirRhor said:
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!
Click to expand...
Click to collapse
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?
Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.
I installed rom before 2 days and had similar doubts.
Just want to share what problem I faced :
The mobile should be in ON state when rooting CF I was doing it in OFF download mode
Latvianization said:
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?
Click to expand...
Click to collapse
CyanogenMod 9 is based on ICS, CM7 is based on Gingerbread. There wasn't a CM8 because Google never released the source code for Honeycomb.
And what you need is a safe kernel, because the kernel is what sends a erase command to a chip inside the phone and that's when you brick it (I think). That happens when you do a factory reset.
Now, what I always do when I want to change ROMS is to use AbbysNote 4.2 as a safe GB kernel so I can then flash the ROM/Kernel of my choice.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1362424&highlight=abyssnote
So let's say you want to go from CM9 to LiquidSmooth (or pretty much any other), which is the one I use now:
You go to CWM recovery, from there you flash AbyssNote.
Once the flashing is completed, you DO NOT exit CWM, instead you go to "Advanced" and then "Reboot to Recovery" so the phone will restart but it will go directly to CWM again, but now with AbyssNote installed.
AbyssNote has a TOUCH based recovery, so it is easier to use. Don't use the physical power and volume buttons to navigate.
From there you can safely do a factory reset, format cache, format Dalvik, flash a new ROM and Kernel.
AbyssNote will then disappear because it will be overwritten by the new Kernel of your choice. So every time I want to change to a new ROM, I repeat the steps above I haven't had any problems whatsoever.
I hope I'm right with my technicalities, but the procedures the OP and I describe are safe to try as long you follow the exact instructions, so before you try anything, read and re-read and you will be just fine.
---------- Post added at 12:38 PM ---------- Previous post was at 12:34 PM ----------
tribalkg said:
Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.
Click to expand...
Click to collapse
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360
Thanks for the useful information and for putting to rest some of my safety concerns.
Now you've wetted my appetite and I have to give it a go soon.
Sent from my GT-N7000 using xda premium
Thanks for this great guide! I haven't gotten my Note yet as I just ordered it yesterday but I have been lurking around the forums already and trying to understand how flashing roms and kernels works around here. Like someone already said before some of the guides / threads are 'a little' confusing for newcomers. I was really confused with the brick bug that people were writing about. This thread clarified things a lot for me and I believe it will help many more Note-newbies!
So, new Note community member reporting to duty here! :highfive: It's gonna be pretty neat upgrade considering from what phone I come from. Well, the Huawei at least was great step stone to android world gotta admit. I just got somewhat bored with the not so great custom scene.
SirRhor said:
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!
tribalkg said:
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!
Click to expand...
Click to collapse
Dont worry about AbyssNote, is safe in both respects. That's the one I always use to do anything that is flashing related.
If, for some reason, you start seeing that dreaded triangle at boot, you can use TriangleAway from Chainfire on Google Play.
Sent from a GNote, hell yeah!
Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.
tribalkg said:
Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.
Click to expand...
Click to collapse
Dont worry, I'm glad I can help you.
You can try Marker and Jotter as well, they work well.
Sent from a GNote, hell yeah!
thanks
thanks for the guide.
I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2
maddog2727 said:
I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
If you are on GB already, you just have to root the ROM and flash CWM because the brick bug is present only on ICS kernels. 99% sure.
There are some GB Stock ROMs that you cannot root directly, so it depends.
OTA updates from Samsung to ICS I'm not sure, you should ask someone else. When I got my Note it already had ICS, so I never did an OTA update. I don't use Kies at all.
I was very weary at first too, but with the instructions above you will be fine.
Sent from a GNote, hell yeah!
I've followed the guide from OP and now I'm rockin' CM9! No problems at all.
My content on the internal memory was intact (apps data, games data, etc), it's all there and I've flashed Indian ROM and then CM9. Have I made a mistake or what?
First of all, I like to share I am not a stranger with rooting, flashing, granting bootloader access (not an tablets, but on HTC an SE WM phones in the past (assuming the S-off/S-on switching is somewhat comparable)). Despite not being a stranger, I am no whizzkid either, it's just that I am able to read instructions well, re-read them and carefully follow the instructions step by step. During the process I have reasonable understanding of what I am doing, but I am not someone that could have 'invented' such workflows and adjustments myself.
So, what is new for me? Installing a custom recovery. I haven't done that before. No problem, because I know there are enough techs on XDA that have the great quality to share their knowledge, something I appreciate very much and use regularly.
My story:
Asus created a situation in which you have to register your device and actively decline your warranty, whenever you want to unlock the bootloader. This is why I didn't do that yet. Now, having my TF300 for almost 6 months, reasonably comfortable with the feeling there will be no issues to need the warranty, I am willing to unlock my bootloader and void my warranty. However, shortly after the JB OTA I read a lot of messages that this was not possible with a TF300 on JB. Later I read it might be possible, but that changing the bootloader was not possible. Then I read this was possible too, but you could only install roms based on official Asus JB OTA.
Well... I guess things have evolved since the initial JB OTA, but I am not sure that I understood things well enough to just give it a try (yet). So I am looking for confirmation and a bit more in depth info. First I will summarize my TF300's history in detail and things I found so far regarding custom recovery. In this way you know what the situation is and I also hope this post becomes 'informative' for other TF300 owners too, besides being a question topic for me only.
Ok, what do I have:
- An original TF300T (no dock), bought in June 2012 with stock ICS
- Granted myself root access via 1-Click Transformer Root
- All original Asus OTA's applied, including the upgrade to JB (and succeeding OTA's)
- Still have root (kept root during all OTA's, including upgrade to JB with help from Voodoo OTA rootkeeper)
- Recently wiped/factory reset my device (still have root)
What I used in the past, but currently not running on the tablet:
- Used different Custom build.props on ICS and JB, but now have stock build.prop again
- Used SwitchMe profile manager (still want it, but waiting on decision to possibly unlock/install custom recovery first)
- Used browser2ram (don't want to need it anymore, but ability to boost performance with a custom rom will be a requirement)
What custom recovery options did I see? There are 3 of them and all seem to be safe with the TF300 JB OTA:
- TWRP 2.3.1.0
- CWM 6.0.1.3 / 5.5.0.4 (don't know why it has 2 version numbers... ICS and JB version?)
- Clockworkmod 6.0.1.4 Touch (same as CWM 6.0.1.3 but with touch functionality?)
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
These are my major 'need to knows' before I dare....
Besides this information, I am curious if someone can confirm my representation of (or explain) the different parts in Android/Asus installation and how it is affected by a custom recovery. During reading along the forums, I have created this visualization of the different parts of the system:
1. Bootloader or kernel (first thing on system, somewhat comparable with a PC BIOS? Are the terms bootloader and kernel interchangeable?)
2. Asus recovery/boot options or custom recovery (custom recovery replace the standard Asus recovery/boot options, I assume)
3. Android (stock JB/ICS or custom rom)
Is this a correct representation?
Well, that was all... Hopefully my post didn't become a TLDR and some of you are willing to help me out. I am very thankful in advance!
1. Bootloader is something else then a kernel. You just have to have the right kernel for the 2 different bootloader
2. Boot options are in the bootloader. Stock Recovery has no options.
3. dont understand your question
1st if you are still on ICS I would recommend to use NVflash and create the needed NVflash files. After that your tablet is nearly unbrickable and you are able to NVflash back to the ICS bootloader (my opinion not so importent anymore, caus even CM is now compatible with the JB Bootloader)
2nd If you are still on ICS I would use the unlock app on ICS not on JB and would then flash the JB update.
The Custom Recovery is best right now would be TWRP 2.2. Its the only one with no known issues.
Hope that helps a little and hope that my explanations are correct, because I am just a flasher like you
Last but not least. The best ROMs out there in my opinion are the Clean Rom 2.5 for the TF700 with clemsyns Kernel and BlueAndroid V.1.0.
Thank you for your reply, it helps me a bit. Unfortunately it doesn't answer my major questions, but I don't blame you (not at all). Every bit of help is welcome.
mikaole said:
1. Bootloader is something else then a kernel. You just have to have the right kernel for the 2 different bootloader
Click to expand...
Click to collapse
Ok... clear... but then.. what is a kernel...? (*feeling noob*)
mikaole said:
2. Boot options are in the bootloader. Stock Recovery has no options.
Click to expand...
Click to collapse
Ok, so what happens if I install a custom recovery? Does it replace the bootloader with a different one that includes recovery options? Or does it add recovery options to the existing bootloader?
mikaole said:
3. dont understand your question
Click to expand...
Click to collapse
The numbers (1, 2 and 3) were the 'layers' I imagined on how Android is build up from boot to OS, where 3 being the final layer (Android OS presented to the user on screen).
mikaole said:
1st if you are still on ICS I would recommend to use NVflash and create the needed NVflash files. After that your tablet is nearly unbrickable and you are able to NVflash back to the ICS bootloader (my opinion not so importent anymore, caus even CM is now compatible with the JB Bootloader)
2nd If you are still on ICS I would use the unlock app on ICS not on JB and would then flash the JB update.
Click to expand...
Click to collapse
That's the point why I started this topic, I am on (stock OTA) JB already. If I was still on ICS, I would have had the guts to unlock and install custom recovery. I am hesitating because I read about issues with JB and unlocking/installing custom recovery.
mikaole said:
The Custom Recovery is best right now would be TWRP 2.2. Its the only one with no known issues.
Click to expand...
Click to collapse
Thanks for the tip, I will keep this in mind.
mikaole said:
Hope that helps a little and hope that my explanations are correct, because I am just a flasher like you
Click to expand...
Click to collapse
*shakes hands* Yes, it helped a bit.
mikaole said:
Last but not least. The best ROMs out there in my opinion are the Clean Rom 2.5 for the TF700 with clemsyns Kernel and BlueAndroid V.1.0.
Click to expand...
Click to collapse
Thank you, I will consider this when I am ready to search for custom roms.
@all: Is there someone out there that can (and is willing to) answer my 'major' questions? I will re-post them below:
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Yes the unlock tool works on JB as well as ICS. I used it while on JB.
Recovery choose one for JB since you have said you were on JB. In fact that is how you will determine which roms you can use as well (JB).
There have been many complaints posted about problems with CWM on this device.
Safe is something I can't answer - twrp itself appears to be safe but that is relative.
One mistake can usually be overcome (or one weird issue); add a mistake to that and you are out at two strikes with this unit most of the time. That is the way I see it after reading hundreds of posts.
You must have recovery, adb, or fastboot working to recover from a problem with this unit.
Before you make any changes make sure adb and fastboot work.
When you flash a rom make sure early in the game you turn on usb debugging in developer options. Learn to get into and use the bootloader menu for adb, fastboot, and recovery access. This would be with both stock recovery and twrp.
Custom roms are usually by default rooted. With a custom recovery you can flash root at will.
It is long but I feel I touched on each of your questions, if not ask.
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Other kernels can let you run "low voltage" or "ultra low voltage" settings for the processor. This allows you to send less power to the processor but still get the same amount of oomph out. The result is greater battery life, and no cost to performance. Obviously this can be dangerous to some hardware... so be careful and know what you're doing. It can be as bad as damaging hardware, or as minor as getting your phone stuck in a boot loop. DO A BACKUP with Rom Manager before installing a kernel. Always do a backup before you do anything to your phone.
moisaal said:
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Other kernels can let you run "low voltage" or "ultra low voltage" settings for the processor. This allows you to send less power to the processor but still get the same amount of oomph out. The result is greater battery life, and no cost to performance. Obviously this can be dangerous to some hardware... so be careful and know what you're doing. It can be as bad as damaging hardware, or as minor as getting your phone stuck in a boot loop. DO A BACKUP with Rom Manager before installing a kernel. Always do a backup before you do anything to your phone.
Click to expand...
Click to collapse
+1
tobdaryl said:
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Yes the unlock tool works on JB as well as ICS. I used it while on JB.
Recovery choose one for JB since you have said you were on JB. In fact that is how you will determine which roms you can use as well (JB).
There have been many complaints posted about problems with CWM on this device.
Safe is something I can't answer - twrp itself appears to be safe but that is relative.
One mistake can usually be overcome (or one weird issue); add a mistake to that and you are out at two strikes with this unit most of the time. That is the way I see it after reading hundreds of posts.
You must have recovery, adb, or fastboot working to recover from a problem with this unit.
Before you make any changes make sure adb and fastboot work.
When you flash a rom make sure early in the game you turn on usb debugging in developer options. Learn to get into and use the bootloader menu for adb, fastboot, and recovery access. This would be with both stock recovery and twrp.
Custom roms are usually by default rooted. With a custom recovery you can flash root at will.
It is long but I feel I touched on each of your questions, if not ask.
Click to expand...
Click to collapse
Thank you for this clear answer. Allow me to summarize your answer (actually it is a confirmation request to see if I fully understand your answer):
- Asus unlock tool is working fine on JB, no problems
- Since my TF300 is on JB and to stay on the safe side (no guaranties) your advice is to use TWRP 2.3.1.0 for JB (to use the JB version is obvious for me, thanks for confirming)
- Once these steps are done (unlock and custom recovery) , I can flash roms at will, but have to keep in mind to use JB-based roms
Did I summarize (and thus understand) your answer correct?
Thanks for pointing out to have adb and fastboot working before making changes and to learn to get into and use bootloader menu for adb, fastboot and recovery access (with both stock recovery and twrp). I am very much aware of this, but it is always wise to make that clear to anyone whom wants to play with this stuff.
You helped me very much! To be complete sure, I'll wait for confirmation, but then I have more than enough confidence to give it a go (Yes, I will beware it won't exaggerate into over-confidence and I become sloppy . I'll stay punctual and cautious during the process.).
moisaal said:
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Click to expand...
Click to collapse
Can I see the kernel somewhat equal to the bios on a pc, or is that a misinterpretation?
If I understood it correct, then it is not fully comparable to a pc bios, as on Android the kernel also determines which version of Android is able to run on your device (ICS needs another kernel than JB), right?
ralph075 said:
Can I see the kernel somewhat equal to the bios on a pc, or is that a misinterpretation?
Click to expand...
Click to collapse
BIOS (basic input-output system, or something along those lines) is loaded before the kernel! They are different. The kernel acts as a mediator between hardware and software.
Trimis de pe Motorola Defy
vap_66 said:
BIOS (basic input-output system, or something along those lines) is loaded before the kernel! They are different. The kernel acts as a mediator between hardware and software.
Click to expand...
Click to collapse
Thanks for clarifying. I found this article and read it to learn more... (I had a few questions again, but realized that there probably would be something to read in here that could answer those questions too... )
Did I summarize (and thus understand) your answer correct?
Yes that is correct.
tobdaryl said:
Did I summarize (and thus understand) your answer correct?
Yes that is correct.
Click to expand...
Click to collapse
Thanks again, now the challenge is to find some spare time this weekend
ralph075 said:
Thanks again, now the challenge is to find some spare time this weekend
Click to expand...
Click to collapse
Good Luck!
Go slow and enjoy your new tab.
tobdaryl said:
Good Luck!
Go slow and enjoy your new tab.
Click to expand...
Click to collapse
Thank you. Well, slow it will go, as last weekend didn't have any spare time...
Hopefully I will experience my new tab soon...
ralph075 said:
Thank you. Well, slow it will go, as last weekend didn't have any spare time...
Hopefully I will experience my new tab soon...
Click to expand...
Click to collapse
You're very welcome.
Yes, it seems time to play is sporadic and limited.
Life would probably be very boring if we always had time.