Related
Hi
To be able to bypass the process of a flash to v13_13, open the backdoor, flash to 14_14 etc. can anyone point me to a rooted 14_14 rom?
In particular "K1_A301_14_14_120109_US"
Thanks
http://rootzwiki.com/topic/13407-alpha-ideapad-k1-cwm-stock-rooted-rom-120109-build/
Although still in the alpha stage, I switched from using timmydean's rom to this one specifically so I could successfully run the 14_14 rom and keep my root. Nothing against timmydean and his work, this just worked easier and faster. Also this rom add cwm which is the only rom out currently that does this for the k1, from what I've seen.
Just reemeber that this is still just an alpha, so be sure to read the post fully. Hope this helps!
Thanks for posting the link Dueces99. I compiled the CWM and ROM that Deuces99 linked to. I just wanted to add that there is nothing alpha about the ROM, just CWM. The ROM is stock and rooted and has no bugs (Other than the ones the stock ROM has).
The reason I left the Alpha status is because backup/restore don't work in CWM, and there is currently no key combination to boot into recovery. You must boot to recovery using the included app/widget
Right, there is no physical key combo. associated to booting into Recovery, the rom atleast provides the means to boot into recovery (widget/app) which atleast leaves the option. I personally, have not had any issues at all with this rom, and love the fact that all the bloatware misc. 3rd party apps and some Lenovo apps were removed, which made the rom seem that much more responsive upon first boot IMO.
Glad to hear that was of some help to you, kinda surprised there hasnt been anyother spinoff roms from this, regardless of its released stage. Just how cut and dry it is with flashing the 2nd newest update with root, then simply flashing the 14_14 update through CWM and keeping root. That was my biggest hurdle following timmydean's guide (and still is) was keeping root once taking the update from Lenovo.
Just my 0.02
so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium
prfstrkr said:
so all i need is to flash alpha 3 and latest update 120109 in order to be on a rooted 14_14 build? can someone confirm?
Sent from my K1 using xda premium
Click to expand...
Click to collapse
Correct. After that you will be up to date and rooted.
Right, confirming with khanning88 flashing alpha 3 would be the 13_13 update. After flashing that, reboot into recovery via the Reboot Recovery app/widget included in the ROM, follow the instructions from there provided by the rootzwiki post and you'll be good to go with the latest 14_14 update. By far, the most cut-n-dry rooted ROM out there as far as I know. IMHO kinda deceiving that the ROM is listed as an Alpha (for CWM understandably) only because it's been extremely stable for me with nada one FC.
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...
Dueces99 said:
Wierd how an alpha build ROM is more stable than the OS that the K1 comes with...
Click to expand...
Click to collapse
From what I understand, it's the same firmware as the stock Lenovo, so maybe a little bit of a placebo effect? The CWM ROM does take out all the built-in non-Google apps, so maybe that has something to do with it.
I hope Lenovo gets its act together and shares out the proper source code so that some good samaritan out there can build a stock Android ROM to run on the K1. I've been using it a bit on the 14_14 CWM firmware, and it's still not as good as the firmware I've experienced on the ASUS Transformer TF101 or the Acer Iconia A500. The biggest issue I've found with the Lenovo firmware is that there is a lag closing out of apps and going back to the launcher, sometimes to the point that a forceclose-wait window pops up. I've not experienced that on the Honeycomb ROMs of any of those other two devices, so I wonder if it's because of Lenovo's customizations to Honeycomb, like the ability to close apps from the multitasking sidebar. In that case, maybe a more vanilla version of Honeycomb won't have that problem. Don't get me wrong; I think it's a great feature that Lenovo added to the taskswitcher. But I'd rather not have it than have the operating system lag. I trust Android's memory management enough to not really need to go manually closing apps.
Right, im sure all the bloatware taken out from Lenovo had to have some effect on overall performance. As far as stability between the two, maybe I meant to say "Wierd how an alpha build ROM feels more stable than the OS that the K1 comes with..."
But placebo effect or not, I've experienced zero issues with this rom even though I probably don't do near as much as other K1 owners with their tab. Lenovo does need to fix this, or preferably just provide full source to all...
khanning88 said:
Correct. After that you will be up to date and rooted.
Click to expand...
Click to collapse
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed
prfstrkr said:
Thank you so much! I am finally rooted with 14_14 with all the bloatware removed
Click to expand...
Click to collapse
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update
I'm glad I remembered to check back on my thread!
I'll be a rooting tomorrow morning
Thanks Dueces99
omg ... plz tell me it's ICS
Sent from my Xoom using xda premium
khanning88 said:
Welcome, glad you like it.
P.S. I should have an update ready in a couple of days....... and this one is a BIG update
Click to expand...
Click to collapse
Thank you so much, khanning, for all of your efforts. As I mentioned in this thread http://forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285 , your CWM firmware is the only effective workaround at the moment for those of us whose K1's are inexplicably locking up with "unrecoverable bootloader" errors to get onto the latest firmware.
We still aren't completely out of the woods though. In post 44 of your rootzwiki thread http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__390175 and post 47 http://rootzwiki.com/topic/13407-al...-120109-build/page__view__findpost__p__392343 , the users kennethrkennedy and aig787 both confirm that the "unrecoverable bootloader error" can still come back with updates, even through your CWM recovery. With your Alpha3 and your 120109.zip update, you managed to avoid updating whatever it is that causes the "unrecoverable bootloader error." This is my long rambling plea that, whatever you did there, you will continue to do for the latest update you are working on, so that those of us with these K1's that are prone to the "unrecoverable bootloader errors" can join the fun too. Thanks!
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Wait till Asus fix the problems.
Yea dont install ICS, it would be like pouring water over your PC
It might seem fun at the time, but its really not a good idea
I would say it is a very bad idea. Avoid it. I did it and literally my tablet is unusable now because of
Slow response
Random rebooted
Random no message crash of apps like gmail.
Dead slow,app response
white screen on app loading
It is now embarrassing infront of ipad users.
Sent from my Transformer TF101 using Tapatalk
spinaldex said:
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Click to expand...
Click to collapse
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
horndroid said:
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
Click to expand...
Click to collapse
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
*Detection* said:
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
Click to expand...
Click to collapse
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
I would no say my TF is unusable under ICS.
It works fine, apart from not so random reboots, as it reboots mainly in the morning when I wake it up form the night...
maybe the Sleeping Beauty requires a kiss from the Prince ...
By the way, it used to be really better under HoneyComb, I wish i could have refused that damned firmware upgrade ...
If I were you I'd rather wait as an other poster said for a really proven Stable version from Asus
Nickola
horndroid said:
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
Click to expand...
Click to collapse
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
*Detection* said:
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
Click to expand...
Click to collapse
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
I've got issues on Stock and I did a full wipe using voldn+power method and this was before I rooted. I also lost sound randomly on Stock, and the custom kernels I still get reboots but my sound for the main part does work.
So, if the OP needs their tablet to work correctly then wait, if it's not that important to them and they don't need for day to day tasks then take a chance, you might get lucky or you might be causing yourself a headache, up to you.
horndroid said:
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
Click to expand...
Click to collapse
How is the problem me when I am doing everything the "ASUS way" ?
The problem is ASUS and their code.
If you read the OP's actual post, you will see this line
"Is it possible to upgrade to the stock ICS"
And if you want to go even further into it, your line "Probably because I do it correctly and do a full wipe including format /system before I flash anything"
I don't think you can get a cleaner flash than NVFLASH, which is how I always flash my ROMs
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.
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!
What I cant understand is why people are downloading the ics rom when the acer a500 auto updates to ics when you update your update service?
another question, I believe black thunder is an app that flashes roms and it gives you an sbk, and you put the "0" in front of the cpuid to do this
but what about clockwork rom manager? do I still need to do this or can I just backup with titaniam and run the zip off my sd card?
and im sorry but im painstaiking at this moment to find the roms for ics...I fould a list and FLEX-resurrection caught my attention although iv'e seen no screen shots or anything on it where might I find that,?
ROM's are way better than stock
zolteck said:
What I cant understand is why people are downloading the ics rom when the acer a500 auto updates to ics when you update your update service?
another question, I believe black thunder is an app that flashes roms and it gives you an sbk, and you put the "0" in front of the cpuid to do this
but what about clockwork rom manager? do I still need to do this or can I just backup with titaniam and run the zip off my sd card?
and im sorry but im painstaiking at this moment to find the roms for ics...I fould a list and FLEX-resurrection caught my attention although iv'e seen no screen shots or anything on it where might I find that,?
Click to expand...
Click to collapse
Hi Zolteck,
ROM flashing to ICS was begun even before we got official ICS. Separately, ROMs by their nature are to allow some of us to do more with our devices than is possible with Stock eg extend battery/Overclock/USB audio/USB 3G. Also sometimes we can add features from future Android releases. In essence ROM's are super customizable and allow the user to convert his device for his purposes.
One of the issues that came with stock ICS was that its bootloader was locked thus preventing us from flashing new ROM's. There are many ways to now to circumvent this Blackthunder app being on of those. Thus, if you are on stock ICS you need to load CWM after unlocking. I am partial to this tool http://forum.xda-developers.com/showthread.php?t=1675939. After unlocking you can run the zip file from your SD card and then reinstall your apps using Titanium Back up.
There are lot of ICS ROMs in the development forum. I encourage you to also give a couple of Jelly Bean ROMs a rip.
Best of luck and happy flashing
thanks
gsurath said:
Hi Zolteck,
ROM flashing to ICS was begun even before we got official ICS. Separately, ROMs by their nature are to allow some of us to do more with our devices than is possible with Stock eg extend battery/Overclock/USB audio/USB 3G. Also sometimes we can add features from future Android releases. In essence ROM's are super customizable and allow the user to convert his device for his purposes.
One of the issues that came with stock ICS was that its bootloader was locked thus preventing us from flashing new ROM's. There are many ways to now to circumvent this Blackthunder app being on of those. Thus, if you are on stock ICS you need to load CWM after unlocking. I am partial to this tool http://forum.xda-developers.com/showthread.php?t=1675939. After unlocking you can run the zip file from your SD card and then reinstall your apps using Titanium Back up.
There are lot of ICS ROMs in the development forum. I encourage you to also give a couple of Jelly Bean ROMs a rip.
Best of luck and happy flashing
Click to expand...
Click to collapse
thanks a lot!..I will give it a try today see how it all goes
cpuid
[when I edit and put the '0' in front of my cpuid it says ok and creates a back up but when I go to look at it again the '0' is not there..any ideas?
hmm
gsurath said:
Hi Zolteck,
ROM flashing to ICS was begun even before we got official ICS. Separately, ROMs by their nature are to allow some of us to do more with our devices than is possible with Stock eg extend battery/Overclock/USB audio/USB 3G. Also sometimes we can add features from future Android releases. In essence ROM's are super customizable and allow the user to convert his device for his purposes.
One of the issues that came with stock ICS was that its bootloader was locked thus preventing us from flashing new ROM's. There are many ways to now to circumvent this Blackthunder app being on of those. Thus, if you are on stock ICS you need to load CWM after unlocking. I am partial to this tool http://forum.xda-developers.com/showthread.php?t=1675939. After unlocking you can run the zip file from your SD card and then reinstall your apps using Titanium Back up.
There are lot of ICS ROMs in the development forum. I encourage you to also give a couple of Jelly Bean ROMs a rip.
Best of luck and happy flashing
Click to expand...
Click to collapse
when I tried to install afterota on pc it said my uac must be disabled..any idea?
zolteck said:
when I tried to install afterota on pc it said my uac must be disabled..any idea?
Click to expand...
Click to collapse
Just Google how to disable windows uac
oh
shaun298 said:
Just Google how to disable windows uac
Click to expand...
Click to collapse
ahh thank you
OAT decryption
I cant seem to find my version or where to dl the oat from acer my version is stock ics acer_AV041_A500_RV05RC01_PA_CUS1
OTA tool
Here is the link for the full tool. Remember to save all the numbers associated with your tablet before you use this tool.
https://hotfile.com/dl/160313682/62f94d6/Afterota_v1_09.zip.html
This tool has a lot of features and will let you choose the bootloader to install and also install CWM. It will also help you to revert back in case of issues using simple update.zip files.
Follow the instructions carefully and happy flashing
btw, Why are you looking for your OTA version?