Related
Hello, I'm trying to manage these ROMs/kernels/firmwares/images/loaders/etc, and I'm having a lot of difficulty.
I came from a storm 1, and I'm used to a win32 app called "shrink a OS" or the blackberry commander. these would take care of flashing/debloating and everything for you.
at any rate, I'm rooted and I have adfree and titanium and rom manager loaded on the phone. but I'm ready to try and get the latest stuff going. I have DI01 loaded from OTA with 2.1 - so the phone guts are still very stock.
I have one final question: is it possible to brick the galaxy S/fascinate? because on a storm 1, it was not possible to brick it - you could always force push a working ROM to the pin over USB, and it would be reloaded no matter the condition of the phone. this is why I really am hoping for a win32 app so I can not spend too many hours with tweaking!!!
cheers
MOD EDIT - Thread moved to general forum as not related to development
ahh I thought it would be, as it directly relates to implementing development stuff for me, as illustrated by my storm 1 experience
oh well.
any help GREATLY appreciated!
thanks!
Short answer: no, there is no such program.
Long answer: my guess is that's because most people prefer managing things on their phone. One of the much-maligned aspects of the iPhone is how it's inseparably tied to your computer (specifically to iTunes), while Android has been lauded for not needing a computer for anything at all. Obviously, here in the modding world you need a computer to flash a new recovery (and modem if you want) via Odin, but once that's done, everything can be managed on-the-go through ROM Manager. This is just my personal opinion, but it would seem very 90's to have to plug in my phone each time I want to switch ROMs.
Also, it's worth noting you don't have to manually debloat if you put an already-debloated ROM on to begin with. So really, all you have to do if you already have ROM Manager setup is flash the DJ05 or DL09 modem in Odin, which you should know how to do from flashing the recovery ROM Manager depends on; and then install a DJ05/DL09 kernel and ROM right on the phone through recovery or ROM Manager.
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Click to expand...
Click to collapse
Well that i a good start. Good to see some reading before the jump in feet first.
corruptsmurf said:
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
Click to expand...
Click to collapse
That's why we're here.
corruptsmurf said:
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
Click to expand...
Click to collapse
Edited: added Later
ADB is a commander center/protocol (if you will) that allows you to control your phone via a PC/Mac/Linux. You can push files which would be taking the file and "pushing" to the phone. Or "pulling" files from the phone and putting them on the computer. It's simply as it states, pushing and pulling the files.
To see what a Kernel is read This.
A ROM is the phones physical Operating system. Similar to what Window, Mac or Linux world be.
corruptsmurf said:
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Click to expand...
Click to collapse
Before you can flash Clockwork Mod you need to root your phone and turn s=off. For one of the methods, - before you can start you need to set up the ADB (Android Debug Bridge). See my signature for the quickest and most painless way to get that set up. You will also need VISIONary.apk. A quick Google Search will find it for you. Link
corruptsmurf said:
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
If you want a 2.3 based ROM you will need to flash Recovery image 3.0.0.6, link can be found in my signature, and hit up the development section to read reviews on different ROMs. I personally like the plain AOSP look so that leave Cyanogen(mod). But i know TeamRoyal has put together some newer ROMs that i haven't tampered with yet.
I do everything on my phone through CWM (clockworkmod) or terminal emulator, so there's no need for a PC, unless to download the files and transfer them to my SDcard, as I don't understand adb. Anyways, I'm gonna explain this very short and sweet cuz I was once in your shoes, and remember how much I had to read to understand something That could've been explained so simply.
Think of it this way. You're building the software version of a car. Now, if the whole car is the ROM, then the engine is what would be the kernel. And flashing would then be another word for installing , Now, a toyota with a ferrari engine, would be a custom ROM. While a toyota with a ferrari engine and BMW insignias all over it would then be a custom themed ROM.
**Remember, you can never install a car on something, but you can always install something in a car**
Ex. You can never flash a ROM on a kernel, but you can always flash a kernel on a ROM.
Anyways, first off, you will need CWM recovery to flash. Get it from the market. In the app itself, flash (this is the "flash" in the app) recovery 3.0.0.6. This will flash (this flash is not in the app) anything; any ROM, any kernel, etc. as long as its a FLASHABLE ZIP.
To boot into the recovery (the place you do flashing), hold both volume down and power buttons down as you either turn on or restart your phone. The screen you see is the bootloader. Choose recovery using the volume buttons, and use the power button to select it.
Going to flash a new ROM? Do a factory reset (in recovery), wipe cache (in recovery), and wipe delvik cache (this is in advance in recovery). Then install zip. Its pretty straight forward from there.
Going to flash an updated ROM, skip factory reset (as this deletes all data on your phone) and do the rest.
After you've flashed the ROM, you can now flash the kernel.
Note that, kernels are ROM specific. Read what kinds of ROM's the kernel is for before you flash it.
There, easy as pie, yeah? Hope that helped.
I recommend cyanogenmod 7 (Gingerbread based ROM) with faux's kernel (Gingerbread based kernel)
Sent from my HTC Glacier using XDA App
corruptsmurf said:
Okay, so I've been reading for a couple days now, and I know the exact process that I want to take to Permaroot my MT4G and get S=Off, and I understand very clearly what those terms mean and why I want them.
Once I started looking into what to do beyond that, I got really, really confused.
If someone could refer me to somewhere so I can read more, I would really appreciate it.
For starters, I don't understand what flashing is. I also don't know what pushing files via the adb is. I don't know what the difference between a ROM and a kernel is.
^^^^All of those would be helpful
I guess I'm just confused about what to do now. Should I now set up the SDK on my PC and configure the ADB? Or should I flash Clockworkmod and do a nandroid backup? Neither?
Once I've done that, should I find a kernel, a ROM, or both? I know I want Gingerbread, I want OC capability, and I it stripped down (missing bloat), but I also want stability and for things like WiFi to work. On top of all of those questions I posted above, does anyone have any recommendation for a ROM/kernel like that?
Sorry about all the questions, and thanks.
Click to expand...
Click to collapse
Neidlinger's got your back.
1. Glad you're reading before doing. What a welcome change of pace!
2. Flashing is the process of installing new software. We "flash" it to the phone's memory.
3. ADB is using a computer to control the phone via command-prompt from DOS. Push is a command which sends a file from your computer to your phone. Do a search, there are lots of good guides on ADB. TrueBlueDrew made one just recently that I highly recommend.
Here's Drew's thread. Don't forget to hit his thanks button! - http://forum.xda-developers.com/showthread.php?t=928370
4. Start with Clockwork Recovery and a nandroid backup. That's good practice. CWR2 is compatible with Froyo (2.2) ROMs. CWR3 is compatible with Gingerbread (2.3) ROMs. CWR 3.0.0.6 is compatible with BOTH. Very convenient.
5. I say start with CM7. It's extremely stable, even though it's still in development. A ROM is a complete OS replacement for the phone. ROMs contain kernels, which control the most basic hardware, such as processor. If you flash a custom kernel on your stock ROM, you can overclock it more. You can also flash custom kernels on top of custom ROMs for different battery life, clock speed, etc.
To be honest I don't even bother with custom kernels since this phone is so damn fast out of the box I really don't see the point.
QUICK TIPS FOR CM7 - On your first boot, let it sit for 5-10 mins before setting up. There are background processes running and interrupting can harm stability. BEFORE you sign into google for the first time, after it's finished sitting, reboot. This will clear out any wifi glitches and give you smooth sailing.
Have fun!
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Uchennadi said:
BTW, I think most ROM's have a kernel already built in. People install custom kernels because they can have fixes for bugs, help with battery life, overclocked frequencies, no lags, etc. Otherwise, you can just flash the ROM, and if you're satisfied with the kernel its running on, then obviously you'll have no need to flash a custom kernel.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is pretty much spot on. The developers have included kernels that they feel make the OS preform at it's peak. and most of them will allow for overclocking. However on some of them you may need to use a program called "setCPU" to adjust the frequencies. Cyanogen(mod) will have this built into the ROM natively. However most of the veterans will not promote running your phone in an over clocked status 100% of the time. most of us leave the phone at 1Ghz or slower. There are physical reasons, ie the constant expansion and contract of the chip isn't good for the mother board.
If i were you i'd stick with the Stock Kernel and leave it running as it. That way the developer can adjust their ROM, if you use an 3rd party kernel they aren't familiar with the coding so it's not going to act correct.
I'm not putting down what the kernel coders do, they do an awesome job. but for a n3wb i'd leave well enough alone.
I was just wondering if there is a fallback if something is messed up during the root process or installing kernals or ROMs or other fun stuff? nandroids, SBF files etc..?
I want to root my TF, but ive been trying to figure out if I were to be stuck god forbid something happens...
any insight would be appreciated!
i would like to know this ass wel. I have had a lot of custom roms etc. At my glaxy S, and if something went wrong, i would just flash it back to stock using odin. Is there something like that for the transforner?
check out the thread "transformer secure key found" thread in the dev section. i'm not gonna pretend i know how the whole thing works exactly, but it seems now the we have the key to the TFs flashing mechanism, all that's needed is a tool to use it, and that can be used as an unbricker of sorts.
so you want to go the super safe route before rooting, you might want to watch the progress of that thread.
I don't need a signature.
I have seen on the TF IRC channel #asus-transformer that the developer RaYmaN intends to release "unbrick" software and instructions this weekend. He has at least two successful TF "unbricks" with his nvflash software already. He is also the developer associated with the "transformer secure key found".
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Zoandroid said:
I've got a new A500 and I intend to root it soon, but I would like advice on whether to take the current update 7.014.1 being pushed before I go through the rooting process? It currently shows having 3.2 OS version.
Click to expand...
Click to collapse
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
My concern, being still in the middle of researching just how to root the A500, was whether the update would have a similar effect as, for example, the more major update from 3.0 to 3.2, which, as I understand it totally changes the procedure used to achieve root. But if it won't matter one way or the other, I might as well take the update in the interim. I keep hoping to see a more simple 'one-click' style of root made available before I tackle this task. So far I've found something like 3 different ways to root the tablet between this forum and another. But each is a rather involved process.
Thanks!
timmyDean said:
Doesn't matter, the only way to root it is by flashing it which wipes it totally clean
Click to expand...
Click to collapse
I downgraded, rooted, and then flashed the stock ROM without wiping. If going to any other rom, you might need to wipe.
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
timmyDean said:
There currently is no way to root a stock 3.2 or later tablet with a simple one click. In the past GingerBreak gave us that ability but since has been plugged. The other thing causing issues is ACER locked the boot loader making it difficult to flash in a new boot image to get to root.
=== 411 on rooting ===
So, if you have a tablet and want to root it then you have to start looking at security holes. This is what the GingerBreak exploit did along with others. But, ACER plugged those holes and as of today, nobody has found anymore.
So, you might look at exploiting an update.zip. These are OTA's that run but they are signed by ACER. So you can take it apart (unzip) and modify it, but you cannot resign it with an ACER Key. Therefore, you have to sign it with your key. Since it is NOT signed by ACER, the ACER recovery will not install it. So, you have to replace the ACER recovery with CWM which will install any update.zip regardless of who signed it. You just need to change the built in recovery by flashing in CWM recovery.
Lastly, you can just change the boot image and add root. This is easy and straight forward to do. This is just like making your own custom update.zip. Once you have your custom boot, you can then just use Nvflash to flash in your custom boot.
Now, fast forward. ACER (can someone please explain to me why?) decided to lock the bootloader thereby not allowing you to replace the recovery, boot, or any other area. Meaning, you cannot use Nvflash anymore without a key.
With the bootloader locked, you can only load new images if you know the key used to lock it. Of course, they use a public and private key combination, and they appear to use the serial number of the USB device as part of the public key making the keys on my tablet unique compared to yours.
With all this said, this ends all the easy simple rooting methods because first, they've plugged all the security holes (which they should do). Secondly, they locked the boot loader making it very difficult for people to just flash in a rooted boot image.
Armed with this, how do you root a 3.2? One way to do it is to get to a version prior to 3.2 loaded that has a security hole or does not have the bootloader locked. You now exploit it and get root. Now, with root access you make a 'backdoor' that only you know about which allows you to get into your tablet as root. With this done, now roll your tablet forward apply all updates. Since you have a 'backdoor' you can always gain root access.
Unfortunately, this gets to be messy or can be more difficult to do than just clicking on a GingerBreak application. However, if you follow the steps posted here in the forum, it's straight forward and easy enough to do. If not, you are going to have to wait for someone to find a hole and build a oneclick application. I wouldn't hold my breath on this, it probably will never happen because everyone is working on ICS.
Lastly, everyone should write to ACER, refuse to buy ACER (or any tablet) that doesn't allow you (AS THE OWNER) to change it. How would you like to buy a Ford to just have Ford lock the lug nuts on the rims so you could NOT put on your custom wheels.
I believe failure to allow owners to unlock these devices will be the downfall to Android. Windows 8 does NOT have such restrictions and businesses are not going to use devices that are locked and cannot be customized for business. Because developers write software they can sell, they'll move to Windows 8 and drop supporting Android and all these goofy flavors and restrictions. Android might be great and everyone hates Microsoft, but software vendors are going to NOT want to support all these devices.
my 2¢
Click to expand...
Click to collapse
Hi, and thank you VERY much for posting such a nice explanation, especially in addition to all the work you have done posting your thread rooting 3.2. I understand, and completely agree with your explanation, as well as your position on taking control of what we bought and paid for. I take even stronger offense with this tablet's bootloader being locked than I do on my phones. This is not a discounted phone with a service plan tied to a cell provider. It has WiFi, but " I " am the only one providing its data (it never leaves my home). There is no justification here that I am 'leasing' a provider's technology . It was a gift, so I can't speak to choosing the vendor. But I like your wheel lug analogy.
I've been reading the threads on rooting, and both my Android phones are rooted and ROMed, so I've been around the block a couple times from the rooting aspect. But thus far I have been rather confused as to which route to take with the tablet. I don't want to be limited to using terminal for su access, so I want to 'fully root' the tablet. My goal is to allow apps like Titanium Backup, Root Explorer, and others I use on the phones, as well as having Clockworkmod Recovery, or similar recovery capable of working with nandroid backups. But for now I don't have plans to use a custom ROM. So having rooted stock 3.2 would suffice.
Although I do fully understand the need to research these kinds of things before jumping in, I also know that often times information evolves, and lengthy threads which were once considered current info end up not getting updated during that evolution. This can lead to wasted time reading information which can no longer actually be used . So in the spirit of pursuing the most current info, could you recommend which thread I can use to get the best results while rooting this 3.2.1 OS Tablet with the above goals in mind?
Used Timmydean's method, it is pretty easy as long as you follow his instructions with in the zip file he has made with all the tools you need inside of hat zip file. You root, install super user and busybox then download Acer recover installer and that will install cwm...
http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
Good luck and thanks again timmydean for this method.
Sent from my A500 using xda premium
Thanks, that sounds like the way to go. I'll head over to the link you provided.
I've got a couple of questions about the zip file at that post. I want to download that to my PC, and will be using ADB from there, right? I have the choice of doing so from either Windows XP SP3, or Windows 7 Home Premium. I read in older threads that many of the problems people had were only when they used XP, but were avoided by using Windows 7 (which was exactly opposite of what people experienced rooting the LG Ally), so it seems that in this case it is desirable to use Win7?
I presume I'll need to install a driver so the PC can 'see' the tablet. Is one provided in the tools, or do I need to download that somewhere?
I used windows 7. Yes the driver is in the zip file. I unzipped the file to a folder on my desktop and went from there.
In the zip there is a folder called usbpcdriver. Run the set up from within the fooder to get your driver... please read the instructions that say read me..
Sent from my A500 using xda premium
Thanks. I intend to read everything I can get my hands on before I actually start this. I definitely don't want any trouble or, heaven forbid, to brick the tablet.
pretty easy i think... good luck and let us know when you get rooted
I'm not finding any actual instructions on the steps to take for this procedure. The readme file in version 3 zip file only talks about "changes" from whatever the original procedure was.
Where can I get the actual instructions for the entire procedure?
Edit: I just downloaded version 2 of the zip file. In that one there is an additional PDF called "Steps". It is a little more detailed, and says at step 20 that "you should now have 3.2 with a SU shell installed". Does the DotNetDetector step actually ROOT the device? That seems simple enough, but it still has no mention of things like installing ADB and the PC driver. I located the actual thread from which the single post was derived (the target of the URL above, where it is suggested I use TimmyDean's procedure). I am now looking through that entire thread to try to sort out where the instructions are.
AHA! Post 119 of that main thread says "Also the instructions and everything you need are in earlier posts.".
It appears this procedure needs an instruction manual written to consolidate all the gathered information. Having a link to only the download zip files isn't telling me the whole picture. I'll try gleaning the thread and see if I can put together all the steps needed from start to finish to make this work. Looks like ROOT ain't happening tonight.
http://www.multiupload.com/SLR6XSV841
---------- Post added at 05:14 AM ---------- Previous post was at 05:11 AM ----------
thats the link to read me file.. I about to jail break an Iphone 4... Wish me luck
I edited the above post while you were replying. I'll check out that link, thanks.
Good luck on jailbreaking the DemonSpawn 4.
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
OK, so it looks like the file you just sent me a link to is the same one as the "Steps.PDF" file that was released in Version 2. It appears to me that what I need to do is blend the changes (detailed in version 3's readme file) into that original Steps file, to make a single contiguous set of instructions, and then start at the top. I notice it does mention installing the PC driver and ADB.
Do I have this right so far?
rdnkchevy said:
http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
he has updated it again. looks like a few steps where taken out to make it more simpler
good luck man. Iphone is jail broken
Click to expand...
Click to collapse
That was fast! Wanna do my tablet?
The link you sent just now is to the version 3 zip file posted on 12/25, which is what I had initially downloaded. It does appear he streamlined the procedure, but it is that readme file which leaves out the part about installing the PC driver and ADB in the beginning, and also leaves out the part at the end telling you that you should now have 3.2 with a SU shell installed.
Please understand that I want to be "fully" rooted, not just have the ability to gain an SU prompt in terminal. Will this procedure "fully root" the tablet? I'm confused by what he means saying "SU shell installed".
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
rdnkchevy said:
Yes if you use his v3 file you will be.. you will need to down load acer recovery from the market after you are rooted and then flash clockworkmod.. this should all take you about 30 min if that...
Click to expand...
Click to collapse
OK, thanks!! Rooting went well without incident. I just installed Root Explorer and Titanium Backup, and made a backup to SD of my apps and data. Then installed Acer Recovery Installer, and let it install CWM Recovery. But what is considered the "home" button on the tablet?? Is it the reset button? The only buttons on this thing are the Volume rocker and the Power button. ( I got brave and found out it is the POWER button ).
Edit: To clarify, I meant to ask which button serves as the Home button while you are IN the CWM Recovery environment, not while in the Android OS home screen.
I bought it and it appears to have ICS because the Android version is 4.0.3 but that is all I really know right now. I expect that it was never updated OTA though because the guy I bought it off had it for 2 months and he was not the one who rooted it. I was going to leave it as is because I bought it for my 10 year old daughter...but the camera takes very blurry, kind of grainy looking pictures.
I am not afraid to root because I had a Samsung Fascinate and I loved the custom roms I downloaded to it. It had been over a year since i had the Fascinate so i am a little rusty when it comes to all if this. My problem is not knowing where to start with this A500 because I am unsure what has already been done to it.
The guy who sold it to me said he did a factory restore, but when I ran the check root app it does state that it's rooted and I figured it was because there is a app called superuser on the device. I don't know what kernal it has. I don't know if it has a bootloader and/or the version number. I don't know if it has CWM and/or the version. number.
What is the best way to proceed? By the way, the tablet is very clean with absolutely no scratches anywhere. Not a bad buy for $175 with a leather case...
Setting > About tablet. That should tell you quite a bit of info about it no?
download the acer recovery app , it will tell you what Bootloader you have and what recovery
Thanks for the replies! When I get home I will check. I don't want to brick the thing. I ordered a micro SD today and I will get it in 2 days so there is no hurry for me to proceed. Is it worth it to keep it rooted? Is the OTA ICS good enough? I don't think my daughter cares if the tablet is overclocked but if the roms are much better than stock than I would keep it rooted and then download a preferred rom.
Vintage144, in another post you specified that there is a Acer recovery beta...will I need that or would I just get the one from google play? Also when I find out which version of recovery and bootloader I have...I am not sure what to do with the information. Could AfterOta help me accomplish what I want if my goal is to try and fix her camera issue...either by going back to stock or updating the kernal and rom.
I don't want to seem like a noob but my only rooting experience was with my Fascinate which I did everything from stock. Now that I am not coming from stock, I am unsure where to go with what I have. It's like trying to get to a goal but not sure what step to start at. If I was starting from stock I could follow some of the threads here but it's not stock.
What info will I need to post here to let you guys know what is in my A500? I know that the Android version is 4.0.3 , what else will I need to post?
well the beta copy I believe is at thors tegra forum , but its by euclids brother (thats his name on xda) anyway if you've upgraded your BL it will tell you version you have and might give you accurate Recovery as well, if the device is only for your daughter and she's too young to really do anything I would stick with a stock rom and realistically I would upgrade the boot loader , why be left behind?
Theres no reason to root if you dont plan on doing anything major with it,that being said you wont be able to get a newer Boot Loader or custom recovery without it, and custom recovery is well worth the effort!
You guys are the pros so I will take your advise. I don't mind it being rooted and if there are some really nice roms I expect my daughter would like the different looks...it would seperate hers from others.
Android
4.0.3
Kernel version
2.6.39.4+
Image version
Acer_AV041_A500_RV16RB02_WW_GEN1
Build number
KJY2010lcylicious
Anything else I will get when I get home.
I would like to know how to get through all this in case I decide to get myself a A500 it's a really nice tablet.
Okay
Recovery Version: Revamped for Iconia 3.16
Bootloader Version: 3.01
With all the above information what would be my next step?
Sorry
Recovery Version: RA Revamed for Iconia 3.16
Damn auto correct!!!
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
ultramag69 said:
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
Click to expand...
Click to collapse
Probably want to hold off on flashing roms a second.
He's running an HC Bootloader. I'm 99% sure of this. Reason, RA Revamped 3.16 doesn't work with ICS Bootloaders. So you can install an ICS Rom, but, it has to be an ICS Rom for the HC Bootloader. And the performance under HC BL is not near as good as ICS BL.
I would do like UltraMag mentioned as far as install steps and such. It's how we install roms.
Check this thread;
http://forum.xda-developers.com/showthread.php?t=1622425 (steps 1-6)
, and install an unlocked ICS Bootloader and a CWM 7 or 7.2 recovery. Then install one of the Roms made for the ICS Bootloader.
I know AfterOTA will do some of this for you. But this thread gives a good idea of what's going on.
Thanks for your help. I will be getting my micro sd card on Friday. In the mean time I will do a bunch of reading about the things you guys told me to do...again thanks a lot. I really appreciate the help.
I am the kind of person that really wants to know what I am doing...I don't expect all the answers, I just don't want to brick this device.
Forstir9,
Moscow Desire is a great dev on this board, his information about updating the bootloader is dead on. I recommend reading the entire OP in that thread, and then re-read section listed as Automated Flashing Tools, it really helps tremendously if you are a person familiar with root, but not extremely dynamic with making these changes.
I've rooted several BN Nooks and my A500 many many times and love it. I had the Honeylicious ROM that you listed prior to what I'm currently running. KYJ had a great HC ROM with that one! Personal preference currently for me on the ICS ROM is FLEXREAPER from Civato, poster of the referenced article from MD above, you can find that ROM info here: http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1 Lots of cool features and step by step directions, which are what UltraMag69 listed in their post. There are many many different options though and I recommend reviewing several and then settling in on one when you find the one that fits your (or your daughter's) preferences best.
If you enjoy doing this and playing with the tablet your daughter may not keep it and may end up getting something different, because you may have too much fun with it...good luck, have fun, don't be scared to try things and ask questions (after you read first), and most importantly BACKUP BACKUP BACKUP...
Good luck,
-DB
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
forstir9 said:
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
Click to expand...
Click to collapse
First off. Thanks for thinking I am the "God" of the 501". Yeah, I know it pretty well.
Second, Ultramag, is is one of my right hand men. So I suggest you heed his advice well. I always trust his judgement. Am sure he has puled my arse out of the wringer a few times. Well, maybe not, but you get the picture. Some of us on XDA, support each other. That's how it is. I just noticed the bootloader version, And being one who likes flashing experimental code, well, I noticed.
So;
1. ALWAYS make a recovery backup. Then, restore it to make sure it works. (lots of people don't do this and they get fubar'd later).
2. UID. Seriously. Ok, the link on the many ways to get it. You don't want to get it, well... your;e pretty much fubar'd
http://forum.xda-developers.com/showthread.php?t=1624645
3. He has the normal, and one with a kernel you can overclock. Your choice. Really, if you don't OC, then you run the same as the original. Please don't ask me the names of Civatos roms. The extreme will be fine for you. Just don't overclock it if you don't want to. Only difference is the kernel. Not the OS.
4. Yes.
5. For recovery, I would say CWM 1.7.2. Should work for you. 1.7.0 is also ok. Publick recovery is ok too.
6. Never ran After OTA. But hear it is good when you already have ICS.
Forget AcerRecovery. You will already have bootloaders and recovery installed.
MD
Know I'll probably get a bashing out of this but there's a V1.7.3 recovery on the site that must not be named (cough, tegraowners, cough) that supports the Aroma installer - on Thor's ICS rom anyway...
Just thought I'd throw that in too...
I am ready to do a backup...it's asking me what I want to backup...it has a (X) next to the following...
Boot
System
Data
Cache
Flexrom
Is this correct the way it is?
EDIT: ignore this post I didn't see page 2 -_-
Sorry that I didn't post this in Friday...but I really want to thank everyone for their help. It went very easy and it want too much different than my fascinate.
The camera still takes grainy pictures and a few apps has sounds issues but she really likes the rom a lot.
Thanks again for the help.