Database Users

Downgrade 3.2 to 3.0.1 AND root help

i dont want to have my hand held every step of the way so i will try to outline what i believe i need to do and hopefully someone can confirm and correct me.
here goes....
first use this method, apparently method 2 better, to downgrade...
http://forum.xda-developers.com/showthread.php?t=1276227
i then need to follow a process to either root it and leave it as 3.0.1 but rooted or install a custom rom that is rooted? if i need to install custom rom due to that instability mentioned in method 2 i could just put a stock but rooted 3.2 i believe. is there a list of rooted 3.2 roms that i can just install without playing around with kernels or whatever? which is the best currently?
thanks guys and please be gentle

I used the downgrade to 3.0.1, root that, install cwm by thor, then for now flashed Taboonay.
I too am looking for a Rom that fits me right. I'll report back if I find it.
<warning>**** I Void Warranties ****</warning>

cheers mate. idecided to use method 1 and it went without a hiccup. i then rooted.
for now i will leave it with stock 3.0.1 rooted as i am sure ice cream sandwich will be out in a short period and then i will look to put a rooted version of that on when it is known to be stable and someone has a good tutorial on it.
thanks for all the work that goes into the development of this great OS.

one of the reasons i wanted to root is to increase cpu speed.
when i just installed setcpu it wont allow me to go over 1000mhz which i presume is to do with the stock rom.
any suggestions? does this mean i will HAVE to install a custom rom, if so is there a list or any roms that are definitely better than others? if so, i guess there will be different procedures to install depending on the rom,?.

Not necessarily a custom rom, but a custom kernel. Some roms include kernels, some dont. Any you can install kernel wthout rom if you want.

I used method 2 and downgraded to 3.0.1. This version is very unstable as I got a force close message every 5-10 seconds. I immediately rooted using iconia root. (Iconia root and the rom that I was going to flash were already on my sd card prior to going through the process) Kekinash has a rooted stock rom here in the development section if that's what you want. I downloaded it, but I have not flashed it yet because I am happy with Thor's current 13.2 rom. There is a link to Thor's website in the general section. I won't post it here because of xda rules. I can't speak for any other roms in this section because I only ran rooted stock before the 3.2 update.

Lightspeed Rom is pretty snappy

cheers guys, went with honeyvillain.
only probs: first it says to insert a sim card, as i have a a500 it doesnt use a sim card, this is probably why 2 force closes come up straight away for system updater possibly?
second, the market kept saying there was an error. i uninstalled the market and found the latest market apk and all is fine so far running 1400mhz.

bdaman80 said:
Not necessarily a custom rom, but a custom kernel. Some roms include kernels, some dont. Any you can install kernel wthout rom if you want.
Click to expand...
Click to collapse
www.tegraowners.com
Good kernels from the person who made the recovery possible....

[UPDATED] [17/06/12] Rooting, Recovery, Custom ROMs and Troubleshoot!

Okay, so I read many new threads daily regarding how to root, about custom ROMs and everything so I thought I would just start this thread where we all could share what all we know. Something like FAQs for SGN. Without further delay, let's start.
1. What is rooting? Is it dangerous?
A. “Rooting” your device means obtaining “superuser” rights and permissions to your Android phone. When rooted, the user can run various apps that require root permissions to run and also, it allows the user to install custom ROMs or to flash various kernels, overclocking or underclocking the device etc.
Rooting is NOT dangerous. There are guides available here on XDA on how to root and they are pretty easy, straightforward and risk free.
The only disadvantage of rooting is that it voids your warranty but you can easily unroot your phone to get the warranty back.
2. How to root?
A. Pretty easy! Dr Ketan has created this very very simple guide on how to root. You can find it here.
http://forum.xda-developers.com/showthread.php?t=1329360
Don't forget to thank him!
Easiest method in my opinion is to flash a pre rooted stock ROM through PC Odin.
3. How do I unroot?
It's mentioned in the guide above.
4. What is recovery?
A. Recovery refers to the dedicated, bootable partition that has the recovery console installed. A combination of key presses will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install official OS updates. Now because Android is open and has the recovery source code available, building a customized version with more and different options is relatively easy as well.
5. ClockWorkMod Recovery??? How do I install it?
A. CWM, as it is generally called, is a custom recovery for Android. It offers many more options than those offered by the stock recovery and it's generally used to flash custom ROMs.
Installing CWM on your phone is dead simple. Again, thanks to Dr Ketan for his awesome guide. Here you go.
http://forum.xda-developers.com/showthread.php?t=1329360
6. What is a custom ROM?
A. A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way.
Since Android is open source, developers are free to pick up the stock ROMs and modify them the way they like. As simple as that!
7. So how do I decide which is the best custom ROM?
A. There in no best custom ROM as such. Different ROMs have different advantages and disadvantages. Some give you incredible speed, some give you battery, some are better looking and so on. You have to decide what works best for you.
8. Do I really need to install a custom ROM or is stock good enough?
A. Ask yourself! Personally, I feel stock is crap. Also, there are many ROMs that offer stock experience whilst removing everything that makes the stock ROM crap.
9. Can I brick my phone while installing custom ROMs?
A. Yes and no. While it's pretty hard to actually brick a phone, it's possible. Use the CORRECT files and follow the steps as mentioned by the developer. But, as I said, it's highly unlikely that you'll end up with a bricked phone.
10. Okay, so I am ready to install a custom ROM. I know the risks and everything. How do I install it?
A. First of all, you need your phone to be rooted and you also need to have a recovery, like CWM. Now, different ROMs have difference installation procedures so I advice you to just read their respective threads thoroughly, know more about the ROM, decide if it's good enough and follow what the developer says. Use the CORRECT files.
Also, whatever you do, make sure you make backups of your current system through CWM. If ever something goes wrong, these backups will help you restore to your previous system.
Go on, it should all be easy!
Edit: Do not make Nandroid backups in CWM when on LPY, LPF, i9220 repack or other unsafe kernels. There's a very high risk of bricking your phone. Read the stickies!
11. What is Overclocking/Underclocking?
A. Simply put, overclocking is the process of increasing the clock frequency of your phone's processor. Underclocking is decreasing the frequency. It basically makes the processor run faster/slower according to what you set it for.
12. Risks of OC?
A.
Overclocking reduces the lifespan of the hardware of your phone.
It's possible to incurr permanent damage to the phone's compenets by OC.
Overclocking voids the warranty of your phone, but rooting has already done that!
13. Should I overclock?
A. Personally I think there is no use of OC except to fry off your processor and get higher quadrant score (which doesn't mean anything really!). With all these phones with fast processors, OC is less necessary.
14. How to overclock?
A. You need a kernel that supports overclocking. Like franco's kernel supports OC I think. Then you need an application (like SetCPU, No Frills CPU etc) to OC your device. Sometimes, OC options are built into a custom ROM as well.
15. I've had enough of rooting and custom ROMs. I need to go back. What do I do?
A. The easiest way to go back to stock ROM is to just simply flash any of the unrooted stock ROMs through PC Odin. As simple as that. Refer to Dr Ketan's guide for this.
16. What is an unsafe kernel?
A. Most stock ICS kernels are affected by the emmc bug, popularly known as the brick bug. The official CM9 kernels and some new other kernels are although free from this.
17. F***! I am on an unsafe kernel. What to do?
A. You should actually firstly know what not to do and than what to do. DO NOT wipe data in CWM, DO NOT factory reset your phone through either recovery or the Settings Menu and DO NOT delete big files from your internal or maybe even external memory. This heavy R/W operations triggers the brick bug and most often leaves the phone as useful as a paperweight.
Now, what should you be doing? If you're not gonna do any of the above, you're most probably as safe as those on a safe kernel. If you wanna get rid of this emmc bug altogether, you have to firstly go back to GB, use PC Odin method as stated above and then flash any of the new ROMs with safe kernels, read the dev section.
18. I wiped my data previously on an unsafe kernel and now my phone wouldn't boot up. I tried going back to stock GB with the PC Odin method but I'm stuck at "factoryfys.img". OMG! I can't even breathe now.. HELP!!!!
A. Superbrick. Yes, that's the word. Unfortunately, your phone is now bricked and only Samsung could help you now. Or if you're comfortable you can read and watch the DIY guides to replace the affected parts (motherboard).
So, this is all what I could think of at the moment. If you have any more Q&A that could help others, do add them!
Hope this helps..

Good one bro! It should help most of the folks out there! And quench many repeated questions

Thanks man!
Sent from my GT-N7000 using XDA

sujal said:
Thanks man!
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Its better to hit the thanks button than posting a post of thanks LOL
Cheers!! Enjoy your Note!!

Like that!
Sent from my GT-N7000 using XDA

By the way, I was wondering if the moderators could make this thread a sticky. Possible?
Sent from my GT-N7000 using XDA

Just Arrived
I am a burnt newbie. I tried to install a ROM from RootGalaxyNote that seemed perfect. A week later, after getting it back from MobileTechVideo and a full JTAG repair, I laid back on everything. Then I ran across Philz. Love what this guy does. Rooted the kernel MobileTech installed, and installed the Rom I'm using now, SweetROM V2.5. Hope this posts as I am 7 away from being able to talk to the"Big Boys".

Choosing a Kernal for your phone
I looked through PhilZ-cwm6 - Safe Stock Based Kernel but couldn't find anything that matches my kernal version. I honestly do not know where to ask so I hope you don't mind me asking you for your help. What kernal version do I download if this is my phone details:
Model number:
GT-N7000
Android version:
4.1.2
Baseband version:
N7000WELSA
Kernel version:
3.0.31-906371
[email protected]#3
SMP PREEMPT Mon Feb 18 15:19:46 KST 2013
Build number:
JZO54K.N7000UBLSF

You can try the XXLSA or XXLT4.

Is updated bootloader needed

Hey guys what's up sorry I'm sure there are other threads about this but I haven't been able to find one to answer me directly....is the updated ics sandwich boot loader necessary I was able to flash flexreapers and lightspeed's ics custom rooms without it? So is it really needed does it make it faster update cmw or just allow recovery boot menu and dual boot I'm at a lost on weather its neccesary or not thanks once again

It will be soon, alot of the developers, including Civato, have said they are going to stop development for the HC bootloader. It does significantly improve performance and eliminates most of the glitches on ICS.

And it will make life easier in the future - upgrading the bootloader, etc. straight from CWM among others.

strongergravity said:
And it will make life easier in the future - upgrading the bootloader, etc. straight from CWM among others.
Click to expand...
Click to collapse
cruise350 said:
It will be soon, alot of the developers, including Civato, have said they are going to stop development for the HC bootloader. It does significantly improve performance and eliminates most of the glitches on ICS.
Click to expand...
Click to collapse
Alright sweet +thanks ;-) I'll update it later then

gears177 said:
Alright sweet +thanks ;-) I'll update it later then
Click to expand...
Click to collapse
Just stick with whatever custom recovery that is provided with the package you
use...not all features in all recoveries are yet supported.
some are meant only for certain BL's for instance HC3.2 and TWRP
from v4 BL on you are able to flash a zip thru recovery and more fastboot commands are available.
You need to read the change logs for each version as things are being added with each new release.
One thing i am certain of and that is if you are having ANY weird issues, sod, wifi OFF, nvflash issues then what seems to settle everything down is a rollback to HC - I think alot of us myself included, never flashed the right thing at the right time when first upgrading to ICS (and at some future point ending up with a "freakenstein" not one thing or the other and not working all that well either) when you start running a "compatible system" i.e kernel, bootloader, recovery, rom all working as they should, then things look and work a whole heccuvalot better!!!

I will not support HC bootloader for the Overclocking kernel for ICS.
To much problems. So expect no OC support for my rom if you stay on HC bootloader.

Stock JB unlock and custom recovery considerations

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.

[Q] out of practice and need jelly bean advice

Hi xda
I am totally out of practice but really want a jelly bean update. I am running the last Taboonay vache did before he had to stop development, so i already have cwm running (version 1.3.4)
Is this just like usual? Grab a rom, boot cwm, wipe data dalvik and cache, flash new rom? Do i need to update cwm first?
And finally, what jelly bean rom (if any) should i go with? Looking for something nice and stable.
Thanks in advance for your help and advice!

entropy.of.avarice said:
Hi xda
I am totally out of practice but really want a jelly bean update. I am running the last Taboonay vache did before he had to stop development, so i already have cwm running (version 1.3.4)
Is this just like usual? Grab a rom, boot cwm, wipe data dalvik and cache, flash new rom? Do i need to update cwm first?
And finally, what jelly bean rom (if any) should i go with? Looking for something nice and stable.
Thanks in advance for your help and advice!
Click to expand...
Click to collapse
noooooo lol you have to update your bootloader if your still on honeycomb i got the ota then got an unlocked bootloader after that install your recovery and your good honeycomb roms wont work ics bootloader though so beware

This thread has a guide on how to get from stock to a custom ROM, it also details how to unlock the bootloader.
In one of their updates, Acer updated the Iconia's bootloader (the part that starts up Android) and it is now necessary to install a patched version in order to install ICS/Jelly Bean ROMS. Feel free to ask more questions in that thread if you get stuck.

TastyPi said:
This thread has a guide on how to get from stock to a custom ROM, it also details how to unlock the bootloader.
In one of their updates, Acer updated the Iconia's bootloader (the part that starts up Android) and it is now necessary to install a patched version in order to install ICS/Jelly Bean ROMS. Feel free to ask more questions in that thread if you get stuck.
Click to expand...
Click to collapse
Thanks, both of you! I finally figured it out, now got unlocked boot loader - light speed ROM (the jb rooms seem a little too soon to use), custom kernel, and overclocking enabled with the Lulzactive governor. I am *very* happy!

entropy.of.avarice said:
Thanks, both of you! I finally figured it out, now got unlocked boot loader - light speed ROM (the jb rooms seem a little too soon to use), custom kernel, and overclocking enabled with the Lulzactive governor. I am *very* happy!
Click to expand...
Click to collapse
Glad I could help, I'd appreciate it if you clicked the "Thanks" button under my post

TastyPi said:
Glad I could help, I'd appreciate it if you clicked the "Thanks" button under my post
Click to expand...
Click to collapse
Done!