I have been seeing MANY threads lately involving questions such as, "How do I get on ICS?", "Should I update to ICS?", "I think I am bricked, how can I fix this?", and "How do I FXZ back to GB?" So I am creating this thread as an information only thread to answer these questions and more with links to proper threads that have already been posted for your benefit. Unless otherwise noted by the OP's or myself the following threads apply to the AT&T MB865. So without further ado....
What you need to know about ICS and your Atrix 2
The first link you need to look at is the Noob thread. I am going to be using terms like "Bootloader", "Soft-Brick", "Hard-Brick", "FXZ", "Fastboot", "OTA", and the like and user/developer JRW28 has posted a FANTASTIC thread to help you familiarize yourself with certain Android terminologies and certain HOWTO's that will help you understand and accomplish much of what I am going to be referring to. So with the Atrix 2, if you are confused with something. START WITH THE NOOB THREAD. Find it here: JRW28's NOOB Thread
Done? Well read it AGAIN.
Oh, what's that? You read it twice and memorized it? Okay, moving on....
The first question that needs to be answered is:
SHOULD I UPDATE TO ICS?
Well, we have all been waiting for ICS to come out, and it has officially been running on the Atrix 2 for a while via a find through Cheesecake. The initial leak is NOT the final OTA that is still trickling out. You need to first understand that. Is ICS better than GB? Of course it is. No one will argue that here, but what we are tackling is, should you upgrade to it?
When it comes to XDA, we are always looking for ways to improve our phones. That's why we're all here right? This is a DEVELOPERS site. With developing comes trials, and with trials comes ERRORS. Now when it comes to the Atrix 2 (A2 from here on) we have a locked bootloader. This means that recovering from developing, and/or modding errors is not as easy as recovering from errors and mistakes with phones that have unlocked bootloaders. Normally, on phones with unlocked bootloaders, it is easy enough to jump into Clockwork Recovery and restore a previously saved nandroid backup, because with unlocked phones the modified recovery REPLACES the original. Poof. Back to normal.
On locked down phones such as the A2, we have to depend on either a bootstrap recovery or the like to make up for the lack of our locked phones. Do we have recoveries? Sure, but they DO NOT replace the original stock recovery and therefore we depend on things such as Bootmenu and Safestrap to makeup for this. While this works it is definitely not ideal. So what happens when the recovery get's borked, ROM goes belly up, or your phone is stuck at the splash screen and won't boot into recovery?
Well this is where the ICS upgrade question comes into play. This phones DEPENDS on FXZ's (see noob thread for more info). If the above scenario(s) happen then we depend on being able to jump into Fastboot (FB from here on) and reflash our phone back to stock. With Gingerbread this was easy enough as we had an FXZ for GB.
With ICS, ONLY THE FIRST LEAK IS ABLE TO REFLASH BACK TO GB! WE HAVE NO WAY TO REFLASH BACK TO GB WITH THE LATEST LEAKS AND THE SOON TO BE OTA UPDATE!!!!!!
Only when we find an ICS FXZ will this be possible!
Now I can hear it now. Some might say at this point, "Well once I'm on ICS, I won't want to go back to Gingerbread." The point, my friend, is not WANTING to go back to GB, it is needing a way to fix your phone. I myself have a paperweight for an A2 for EXACTLY this reason. I was running the latest of the leaks (NOT the first, which we can go back with). I had made a couple of mods, as bootmenu was working for it, and I made a backup. Well, I flashed a mod, rebooted and BOOM. Bootloop. No biggie, I thought, I will just restore my backup. But apparently I had deleted my backup. I tried, with the help of Devs (whom will be named later) to FXZ back and quickly found that this was impossible to do at this point. Now I have a phone that is able to boot in FB, with no way of restoring it. Fastboot does us no good without a proper working FXZ to flash.
So upgrading to ICS at this point, is fine, but be warned, if you make just the littlest boo boo, you might have a paperweight on your hands. Myself, many of the other Senior Members, and many of the A2 developers are recommending to run the first leak, because it is the most stable and dependable as far as getting yourself out of a jam. Also, many of the the more stable leaks have been baked into the current ICS ROMS we have. Now once you are on the first leak, you will have no problems flashing these ROMS with the more stable versions on them, but you MUST be on the first leak beforehand!!!!! As always read carefully the install instructions from the developer and if you're unsure, ask a question in the ROM's thread before flashing!!!!
UDPATE 9/20/12 It seems as though Moto and AT&T are now releasing OTA updates to our leak! Remember the reasons as to why we are advising against them! IF YOU GET A MESSAGE TO UPDATE WHILE ON THE FIRST LEAK, COMPARE THE FIRMWARE INFO WITH THOSE LISTED IN THE THREAD BELOW BEFORE UPDATING!!!!!
THREAD WITH INFO ON OTHER ICS LEAKS AND WHY WE ARE ADVISING AGAINST THEM AT THIS POINT. Originally posted by alteredlikeness
The rest of this will mainly be references to threads as most questions have already been answered in other threads as I just felt we needed a place to consolidate all the info out there on this. Here goes...
In the following theads, PLEASE thank the OP's!
HOW DO I UPDATE TO ICS?
Other than the OTA method that has been trickling out at this point, I am ONLY going to refer you to the thread to get you onto the initial leak. Because at this point many of us see this is as the safest leak. As you have a way out. Because we want to do what is best for you and YOUR phone.
NOTE: The rest of these threads (unless otherwise specified) refer ONLY to the first leak, and to NOTHING ELSE!!!!
How to get your phone on ICS, and how to root it: Originally posted by Jimbridgman
Ok so now that you are comfortably running ICS and rooted.....
HOW DO I INSTALL A RECOVERY?
We currently have two recoveries for the first ICS leak. Both are very stable and work well, but are slightly different. Read each of the following threads for how to install and the differences between them.
BOOTMENU RECOVERY Originally posted and developed by lukensteinz and Whirleyes
SAFESTRAP RECOVERY Originally developed and posted by Recognized Developer Hashcode
And FOR PETE'S SAKE, now that you have a slick recovery working MAKE A BACKUP!. And then copy it and put one on your desktop!!!!
I MADE A MISTAKE, HOW DO I FXZ BACK?
You are ONLY going to be doing this if you somehow messed up a MOD, didn't make a backup, and now you are in a bootloop. REMEMBER, THIS IS ONLY FOR THE FIRST LEAK. I AM NOT RESPONSIBLE IF YOU DID NOT READ THROUGH FAR ENOUGH AND BRICK YOUR PHONE. If you managed to try and FXZ back while NOT on the first leak, or your phone won't turn on or go into FB, then, well sorry mate, but you are HARD-BRICKED. But if you are on the first leak then the following should work.
HOW TO FXZ BACK TO GINGERBREAD FROM THE FIRST ICS LEAK Originally posted and developed by Jimbridgman
ROMS TO INSTALL BASED ON THE FIRST LEAK
NOTE: You must be on the first ICS leak in aforementioned post to properly install the following ROMS, unless otherwise noted by the devs! And as always read CAREFULLY the installation procedure as laid out by the developer!!!
ScV7 - ICSupercharged Originally developed and posted by rdavisct
De-odexed and De-bloated basic ROM Originally developed and posted by timmytim
ROMS THAT ARE STILL A WIP:
MIUI PORT FOR A2 V4 2.8.17 Originally developed and posted by rdavisct
CYANOGENMOD 10 - JELLYBEAN Originally posted and ported by wanggjghost with continued help and fixes by rdavisct and Jimbridgman
In closing, hopefully this will answer all your who's, what's, and how's of ICS on the A2. Please DO NOT post questions regarding the threads themselves here. Post those in the appropriate posted thread, as this is what this is for. TO KEEP THINGS ORGANIZED!!!!!
If I need to update the OP, or have left something out. Feel free to post it here.
Enjoy ICS! And remember! ALWAYS MAKE A BACKUP!!!!!!!
Special thanks to the following: Jimbridgman, rdavisct, alteredlikeness, Apex_Strider, DX2Trip, Mtnlion and any others I left out.
One quick question what does bootloader, hard-brick and fastboot mean. JK
Thanks for the write up. I hope this saves alot of question's from being posted.
Sent from my MB865 on ICS
Good post man. Answered alot of my questions
Thanks for this, plenty of good information.
rdhoggattjr said:
One quick question what does bootloader, hard-brick and fastboot mean. JK
Thanks for the write up. I hope this saves alot of question's from being posted.
Sent from my MB865 on ICS
Click to expand...
Click to collapse
Consider your bootloader a prison warden. Nothing happens unless the bootloader says so. Pretty much plain and simple really. It's the partition on your device, which initiates first. And it checks to make sure the OS is a legitimate one. Ultimate security. If it thinks everything is in order (after communicating with the kernel), it boots the OS. This is the security most devs have to work at, to allow installation of custom recovery and roms.
There are 2 types of "bricks". A hard and soft brick. Soft bricks you can usually recover from. A hard brick, well, it's not impossible, but difficult. Typically with a hard brick, your device is basically dead. No response, or stuck at the logo screen forever more. forever more. forever more...... Edgar Allen Poe. You always want to avoid a hard brick. In essence, your device becomes nothing more than a ....brick.
Fastboot, is a part of the Android SDK. It allows some types of files to be "flashed" to certain partitions of the device, without a need for a custom recovery. For example a boot.img (kernel for easier terms), a recovery image, and a few other image files. Of course depending on the Bootloader, depends on what fastboot capability you have.
Some devices, Devs have been able to re-write the Bootloader to enable fastboot when it wasn't there from the factory. See Iconia A500. By virtue of patching, and re-writing, the bootloader was stripped of all security and features added. But you can't do this with all bootloaders.
Hope this explained.
MD
Hey Bro I have an Ics ota now. Will that unroot the phone? If yes how do I root it back? And is there gonna b any problem if I update with root?
Sent from my stock rooted Atrix2!
If you are stock 2.3.6 rooted, then yes you will lose root.
As far as rooting ICS goes you should be able to root it with Jim's script from the thread I posted in the OP.
Sent from my SAMSUNG-SGH-I727 using xda premium
Just a question out of the discussion but not of the thread. Why does ATT gets last the ICS OTA?? I see Cambodia and India got it already while ATT phones are still on leaks!!! Isnt this weird considering that ATT is the biggest Moto fan?!
how is the battery life on ics? better or less than GB???
V1P3R92 said:
Just a question out of the discussion but not of the thread. Why does ATT gets last the ICS OTA?? I see Cambodia and India got it already while ATT phones are still on leaks!!! Isnt this weird considering that ATT is the biggest Moto fan?!
Click to expand...
Click to collapse
Ahem, Viper? Did you not read my post man? TRUST ME. You want to be on the leak.
hemanbond said:
how is the battery life on ics? better or less than GB???
Click to expand...
Click to collapse
When I was on the leak, I personally was getting better battery life.
However, remember that battery life is all subjective. What might be good for me might not be others!
Sent from my SAMSUNG-SGH-I727 using xda premium
and what about root checker?
Yes there is a "Root checker" however, it will not hinder your installation, but as far as long term issues? We have no idea as to what Motorola is going to do with this.
its obvious for voiding our warranty
hemanbond said:
its obvious for voiding our warranty
Click to expand...
Click to collapse
If you're rooting/modding/theming/tweaking/overclocking/underclocking/changing voltages/editing build.prop/etc./etc./etc. haven't you already thrown caution to the wind in regards to your warranty?
If you are concerned about it, they (Apple) just released a new iToy, so all you have to do is pull it out of the box and use it.. as is... unless you 'jailbreak it', in which case, warranty worries wander back into the equation, right?
once started how do i stop the ota download
You don't. You can download it, and then NOT install it if you like. Once downloaded it will be in your cache folder.
Sent from my SAMSUNG-SGH-I727 using xda premium
it said update failed and now its asking me to download again....wth
---------- Post added at 10:57 AM ---------- Previous post was at 10:38 AM ----------
downloading was so slow that it took me 4 hrs...damn...and now it failed and asking me to download again
hemanbond said:
it said update failed and now its asking me to download again....wth
Click to expand...
Click to collapse
If update failed because of checksum error, downloading again won't be of help. Most likely you have changed a file that the update is trying to patch. Better you go back to stock 2.3.6 and then apply OTA.
Same happened with me as to the person above. Downloaded the update. I but it says update failed? Do I have to unroot or something?
Sent from my stock rooted Atrix2!
Related
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
There's a script in the thread that gives you cwm on boot. The catch is it goes to recovery first EVERYTIME you boot.
ubersoft said:
I feel monumentally stupid asking this question, but I've run out of options. I have tried searching first, but I'm having trouble figuring out how to phrase the search and most of the search results are for non-Atrix 2 phones, so I don't know how reliable the information is.
My previous phone was an HTC Evo which was fully rootable and unlockable etc., and an HTC Evo 3d which was fully rootable and unlockable at the time I managed to do it (apparently the 3d goes through phases where it is, then phases where it isn't, depending on its updates). My basic and non-technical understanding of the Atrix 2 environment is that becauase the bootloader is currently locked, the backup/restore/flashing solutions have to perform a few tricks to work.
So from what I can tell in the dev forum, there are currently two ways to backup and flash roms. There is safestrap, which apparently isn't quite working yet, which partitions your microSD card and runs everything from there -- essentially when you boot your phone it tells the OS to boot from the microSD card which effectively lets you treat your Atrix 2 as a fully unlocked and rooted device with a remarkably large and well-configured recovery partition. Unfortunately, according to the title of the safestrap thread, it's not quite working yet, and a few of the roms posted in the development forum specifically say not to use it.
OK, so bootstrap. It was updated as of Jan 1. If you have already rooted your Atrix 2 (I have) then it throws up a menu that lets you boot into recovery, and it will install (I think this is my understanding) a custom version of ClockwordMod Recovery? But you can't get there from boot, you have to boot into Android and then reboot back into the recovery environment.
Is that correct?
If that is correct, then my next question is what happens in the hypothetical scenario where you install a rom, something goes wrong, and you want to restore a previous backup but you can't boot into Android?
There's something I'm missing about how all this is supposed to work and it looks like it's something so obvious that nobody actually talks about it in the threads -- or when they're talking about it, I don't actually realize that's what they're talking about so it doesn't register.
Anyway. Thanks for your time.
Click to expand...
Click to collapse
In the situation that you describe, even the CWM on boot that mtnlion mentioned, still may not get you into CWM. In that case your ONLY option is to flash the fxz file with rsd lite, that will restore you to a full stock out of the box atrix 2, which you then have to re-root, then re-install bootstrap, then restore your backup.
Sorry there is not an easier way right now, but until the bootloader is unlocked we can't flash CWM, so that we can get to it, as you would the default android recovery, because that does require the default recovery to be replaced, and an unlocked bootloader is required for that to work.
Safestrap is really a tool that is only useful to those actually developing, or people that we have asked to test something out, and since lfaber06 and I don't have a version to release to the public that we are happy with yet, that is not an option.
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
ubersoft said:
Oh!
So you install bootstrap, then you install the script, and when you do that it basically acts like a grub menu? That makes sense.
Click to expand...
Click to collapse
No, if you get a bad flash you still may not be able to get into CWM, since it requires files that are actually in the Android ROM, to fully work. Read my post above ^^^
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
ubersoft said:
Heh. Apparently I started posting at about the same time you posted your detailed explanation...
Thanks for the additional information. Based on that, it looks like I need to wait a bit longer before mucking about with my Atrix 2. Thanks for the update!
Click to expand...
Click to collapse
No, it is perfectly safe, but the restore is just a little more complex than you had to deal with, with other phones. I have done exactly what I mentioned above SEVERAL times, with out issue, since I am doing a ton of dev work on this phone.
The ROMs that are out there are great right now, and lfaber06s ROM is really good, and I will be releasing a version of CM7 very soon. If you wait for a bootloader unlock, it may never come, or at least it may not be very soon.
The worst thing that happens is that you have to flash the fxz, which it is documented how to do that with RSD lite very well in the noob thread here. then you can restore your backup with out issue, it is just a few extra steps.
Bootstrap is really safe as is all of lfaber06 Roms right now. I have no problem recommending either of his roms to anyone. They are both very good. As Jim has stated the only problems we have is if something wrong happens on boot, but with the fastboot files, RSD lite, and the one click root method you have everything available to get you right back to where you were before you flashed.
I can promise you everything works very good as I have soft bricked my phone so many rimes in the last 2 weeks that I have become very efficient at getting back to stock, rooting and then flashing a backup with bootstrap and can be back in business n around 20 mins. Just always be near a computer when you start flashing things. One thing that will help out is to keep a backup of the bootstrap on tour SD card so if you have something go wrong you don't have to redownload it again.
We have a very good group of people here and if anyone has any problems we can get you through them and back running
Well there we are then!
So after getting a clearer picture of the situation (thanks for the explanation) I blocked off most of the night, installed bootstrap, then installed lfaber06's Supercharged v4. It took forever, but it worked flawlessly.
Thanks everyone for your patience and encouragement.
Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
ianrobbie said:
Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
Click to expand...
Click to collapse
No problem. Seeing you are on JB, then you have a JB bootloader.
You need to go here http://forum.xda-developers.com/showthread.php?t=1953917
And download Vorbeths easyroot2.0. It's for the 700.
You have to unlock your bootloader first, which shouldn't be an issue for you. Easy instructions for that.
Then download his package to a folder on your PC. (not sure, but you may have to download each file individually) Open a command window (shift & right mouse click) and type in whatever his instructions say. Should be painless.
Make sure USB Debugging is turned on first in your tablet (Settings/Developer Options/USB Debugging), and make sure you have the Acer Drivers installed on your PC.
Then connect, wait 30 seconds, and run his batch file.
You should be ok.
MD
Oh yes, one more thing, once you unlock your bootloader, chances are you will not be able to get OTA. And the only way to re-lock the bootloader is to install a stock rom.
Thanks!
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
ianrobbie said:
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
Click to expand...
Click to collapse
No problem. I thought I mentioned it timed out in about 5 seconds These days I don't remember much
Yeah, I haven't looked at Vorbeth's script, so I don't know which screen he launches it from. With mine for the 701, you can be when the tab is running normal. No difference in the end result though
Happy Hunting!
MD
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
ianrobbie said:
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Moscow Desire said:
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Click to expand...
Click to collapse
So, just for future reference, how would I go about re-flashing the stock image? I'm assuming it's saved on the tablet in a separate partition?
I've decided to stick with the stock rooted ROM but would like to know how to re-flash for when Key Lime Pie and future updates are released.
And, seeing as how you haven't steered me wrong so far, I though I'd pick your brains one last time.
Hope you don't mind!
New to the S3 but not new to rooting. I came from an Incredible 2 that I was running Incredible HD with. Absolutely loved it.
Anywho, the thanks part in the title is in regards to all the wonderful tips and tutorials in these forums that I've used to successfully root, unlock, backup nandroid and IMEI, and finally flash CleanROM 5.0 on both mine and my wife's Verizon S3's that are less than a week old. I was blown away by the sheer amount of garbage on the stock phone and knew I had to root ASAP.
So far, CleanROM is running wonderfully with the stock kernel, radio, and RPM.
These questions I'm about to ask; I know they've probably been answered a dozen times already but when I search for, say "install rpm S3", I get tons of results. Basically anything that includes the word "install". So I apologize if these questions have been asked. I promise I will "pay it forward" and answer as many mundane questions asked by newbs like me so that all of you gurus can spend your time doing more productive things.
1) I haven't seen anything regarding tripping the flash counter by flashing CleanROM. Granted I don't really know exactly what this means, only that tripping the flash counter is bad. I used the tutorials here and the whole process went flawlessly. Have I tripped the counter? How can I check?
2) I have downloaded the VRBLK1 modem and rpm. To install these is it as simple as booting into recovery and installing these zips in TWRP?
That said, what is the general consensus on these modem/rpm variations? Are they bonafide improvements over the stock ICS 4.0.4 modem/rpm that are on my phone currently? My signal strength is currently around -97-105dba. My main concern is the rpm. If it will make cleanROM run more efficient battery-wise, I'll definitely install it.
3) Stock kernel seems to be running fine. I've read some positive things about various kernels ike KT747 and Imoson's Lean. Haven't found any concrete data on whether either of them are legitimately better than the stock kernel. I guess since I'm running fine with stock I'll stick with it however if there is a definite improvement over stock I'd like to change.
Thanks for your time and patience answering my newb questions.
Occidentalist said:
New to the S3 but not new to rooting. I came from an Incredible 2 that I was running Incredible HD with. Absolutely loved it.
Anywho, the thanks part in the title is in regards to all the wonderful tips and tutorials in these forums that I've used to successfully root, unlock, backup nandroid and IMEI, and finally flash CleanROM 5.0 on both mine and my wife's Verizon S3's that are less than a week old. I was blown away by the sheer amount of garbage on the stock phone and knew I had to root ASAP.
So far, CleanROM is running wonderfully with the stock kernel, radio, and RPM.
These questions I'm about to ask; I know they've probably been answered a dozen times already but when I search for, say "install rpm S3", I get tons of results. Basically anything that includes the word "install". So I apologize if these questions have been asked. I promise I will "pay it forward" and answer as many mundane questions asked by newbs like me so that all of you gurus can spend your time doing more productive things.
1) I haven't seen anything regarding tripping the flash counter by flashing CleanROM. Granted I don't really know exactly what this means, only that tripping the flash counter is bad. I used the tutorials here and the whole process went flawlessly. Have I tripped the counter? How can I check?
2) I have downloaded the VRBLK1 modem and rpm. To install these is it as simple as booting into recovery and installing these zips in TWRP?
That said, what is the general consensus on these modem/rpm variations? Are they bonafide improvements over the stock ICS 4.0.4 modem/rpm that are on my phone currently? My signal strength is currently around -97-105dba. My main concern is the rpm. If it will make cleanROM run more efficient battery-wise, I'll definitely install it.
3) Stock kernel seems to be running fine. I've read some positive things about various kernels ike KT747 and Imoson's Lean. Haven't found any concrete data on whether either of them are legitimately better than the stock kernel. I guess since I'm running fine with stock I'll stick with it however if there is a definite improvement over stock I'd like to change.
Thanks for your time and patience answering my newb questions.
Click to expand...
Click to collapse
1. No, you shouldn't haven't tripped it.
2. Yes, you just flash them like any other zip. And improvement just really depends on you. If you think it did, then awesome!
3. In my opinion, KT747 is amazing on whatever I'm running it on.
THE BEAST
To be honest, there is not a whole lot known about the RPM, except that it is a partition that has been updated with every OTA and leak. The common consensus is that it doesn't really seem to do a whole lot. There is no harm in flashing it though, as you would receive this partition update if you were to accept an OTA from Verizon. I personally choose to install them for peace of mind.
See the following thread for more information:
http://rootzwiki.com/topic/36114-wip-rpm-explained/
Thanks for the info!
One last question. In Settings>Phone Status, all the way at the bottom there is a section that says "Device Status" and the value is: Modified.
Is that normal? Is it something Verizon can see?
Occidentalist said:
Thanks for the info!
One last question. In Settings>Phone Status, all the way at the bottom there is a section that says "Device Status" and the value is: Modified.
Is that normal? Is it something Verizon can see?
Click to expand...
Click to collapse
That is normal if you are running on a modified device, and yes Verizon can and will see that.
Which is why you should always return your device to stock before returning it to Verizon. Returning it to stock will change that status back to normal.
pdykstra said:
That is normal if you are running on a modified device, and yes Verizon can and will see that.
Which is why you should always return your device to stock before returning it to Verizon. Returning it to stock will change that status back to normal.
Click to expand...
Click to collapse
I think he means before he takes it back. Like right now can they see that my phone is modified so later on down the road if I do unroot to return can they say my phone was modified and will not be covered under Warranty. I also always wondered this.
Sent from my SCH-I535 using xda premium
mikeman45 said:
I think he means before he takes it back. Like right now can they see that my phone is modified so later on down the road if I do unroot to return can they say my phone was modified and will not be covered under Warranty. I also always wondered this.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Theoretically, yes I suppose they could monitor that with an app that checks in with them. But in practice, I have never heard of them actually tracking and logging this. You are fine as long as your return your phone to stock before bringing it in to them.
Atrix2 ATT, on stock GB 2.3.6
I accidentally hit download on the prompt for ICA OTA. Couldn't stop the darn download so it's now downloaded and keeps prompting me everyday to install it.
How do I get rid of it? I don't want it. Rather hope & wait on the JB port that Jim is working on
Thx
The downloaded file is in /cache, I think you can delete it
But the ICS is awesome, there're no reasons to stay on GB
Anyway, you must be on ICS to flash JB
PhoenixNghi said:
The downloaded file is in /cache, I think you can delete it
But the ICS is awesome, there're no reasons to stay on GB
Anyway, you must be on ICS to flash JB
Click to expand...
Click to collapse
Where exactly is this cache? and is it safe to do so?
gcretro said:
Where exactly is this cache? and is it safe to do so?
Click to expand...
Click to collapse
You'll need to be rooted and have a root explorer/browser app installed to delete it. The directory is simply /cache and yes it's safe to remove it. If it was me I'd just let it install since jimbridgman has already said that porting the jb leak was not likely to happen and he isn't working on it anymore. See here:
http://forum.xda-developers.com/showthread.php?p=37823784
But it's your phone, and your decision.
Sent from this thing.
1BadWolf said:
You'll need to be rooted and have a root explorer/browser app installed to delete it. The directory is simply /cache and yes it's safe to remove it. If it was me I'd just let it install since jimbridgman has already said that porting the jb leak was not likely to happen and he isn't working on it anymore. See here:
http://forum.xda-developers.com/showthread.php?p=37823784
But it's your phone, and your decision.
Sent from this thing.
Click to expand...
Click to collapse
hmm... but don't I have to be on the ICS leak1 to install other ATT support custom roms like NUMA?
gcretro said:
hmm... but don't I have to be on the ICS leak1 to install other ATT support custom roms like NUMA?
Click to expand...
Click to collapse
You can install NUMA on leak1 or leak2(which is the same as the ota). No matter what, you have to be on ICS in order to install an ICS ROM. Personally, I am on the ota and running NUMA, so I can say from personal experience that it works. NUMA is a very good choice, by the way. :thumbup:
Sent from this thing.
1BadWolf said:
You can install NUMA on leak1 or leak2(which is the same as the ota). No matter what, you have to be on ICS in order to install an ICS ROM. Personally, I am on the ota and running NUMA, so I can say from personal experience that it works. NUMA is a very good choice, by the way. :thumbup:
Sent from this thing.
Click to expand...
Click to collapse
Thx for helping a noob :good:. But I have more questions:
1. So you have an US AT&T atrix 2 that you OTA's to ICS? And then put on NUMA? I see a gamma version of Numa out, what are the bugs that you know of? I recall seeing that in ICS, icons (like the dialer button etc) were made smaller. Is it the same in NUMA?
2. If I OTA to ICS and put Numa, then want to revert back to the ICA OTA, is that possible?
3. Different question: If a JB based rom comes out in the future for us, will being on ICS OTA be a disadvantage. I suppose NO. I recall reading many times esp in Jim's posts, that many things require being on ICS leak1 and not to OTA. Is that constraint gone now?
gcretro said:
Thx for helping a noob :good:. But I have more questions:
1. So you have an US AT&T atrix 2 that you OTA's to ICS? And then put on NUMA? I see a gamma version of Numa out, what are the bugs that you know of? I recall seeing that in ICS, icons (like the dialer button etc) were made smaller. Is it the same in NUMA?
2. If I OTA to ICS and put Numa, then want to revert back to the ICA OTA, is that possible?
3. Different question: If a JB based rom comes out in the future for us, will being on ICS OTA be a disadvantage. I suppose NO. I recall reading many times esp in Jim's posts, that many things require being on ICS leak1 and not to OTA. Is that constraint gone now?
Click to expand...
Click to collapse
You have a lot of reading to do.lol Bugs in NUMA will be listed in the change log in the op. Personally, I haven't had any issues with it, but read the entire thread to see what others are reporting.
To revert to ICS ota you'll need the fxz, aka firmware, posted by Pzyduck over in the development section. For a tutorial on how to do that look in the general section, Alteredlikeness has a great one called something like "fxz what?" or something similar.
There is Paranoid Android, CM10, CM10.1, and Magic Mod, all of which are jb ROMs that can be flashed on ICS.
Staying on leak1 was most important before Pzyduck posted the ICS fxz. Now the only reason that I know of to stay on leak1 is if you intend to go back to gb. I don't know of any reason to go back to gb unless you just want the better version of webtop.
Now do yourself a huge favor and read, read, read, read before doing anything else. And just when you think you understand, read it all again.
Good luck to ya.:thumbup:
Sent from this thing.
gcretro said:
Thx for helping a noob :good:. But I have more questions:
1. So you have an US AT&T atrix 2 that you OTA's to ICS? And then put on NUMA? I see a gamma version of Numa out, what are the bugs that you know of? I recall seeing that in ICS, icons (like the dialer button etc) were made smaller. Is it the same in NUMA?
2. If I OTA to ICS and put Numa, then want to revert back to the ICA OTA, is that possible?
3. Different question: If a JB based rom comes out in the future for us, will being on ICS OTA be a disadvantage. I suppose NO. I recall reading many times esp in Jim's posts, that many things require being on ICS leak1 and not to OTA. Is that constraint gone now?
Click to expand...
Click to collapse
I will answer number 3 for you.
It is safe now to upgrade to the ICS OTA, since we do have an official AT&T ICS FXZ version that can be flashed through RSD lite. Now if you are a fan of webtop or GB, and want the ability to go back to GB, then do not update to the OTA, or leak 2. You can go back to GB from ICS leak one ONLY, I have a script in the dev section for just that. There is NO difference between leak 1, leak 2, or the "official" OTA, so you can pick what you want to install based on the notes I have given here.
Yes you can load any ICS or JB ROM once you are on ICS, just not any of the GB ROMs.
Sorry but I do not have much knowledge on NUMA, since I was mostly working on CM, and the like, or I would have tried to answer your other questions.
Thx!!
yes. I located the thread with the ICS FZX here http://forum.xda-developers.com/showthread.php?t=1961310&page=11. There was dropbox link from where I downloaded "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip". (I have no use for this now. Just downloaded it in case these links die later and I have to search again.).
Alright baby steps. I am ready to finally accept the OTA to ICS. Its already downloaded.
---I am stock GB (only thing I have done is uninstalled some ATT bloatware apps like ATT navigator etc...).
---I assume the ICS OTA will be successful? If something happens, what should I do?
gcretro said:
Thx!!
yes. I located the thread with the ICS FZX here http://forum.xda-developers.com/showthread.php?t=1961310&page=11. There was dropbox link from where I downloaded "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip". (I have no use for this now. Just downloaded it in case these links die later and I have to search again.).
Alright baby steps. I am ready to finally accept the OTA to ICS. Its already downloaded.
---I am stock GB (only thing I have done is uninstalled some ATT bloatware apps like ATT navigator etc...).
---I assume the ICS OTA will be successful? If something happens, what should I do?
Click to expand...
Click to collapse
The OTA will most likely fail since you've removed some system apps. You'll probably have to factory reset, then push the OTA. If all else fails, you can flash the FXZ that you downloaded using RSDlite, same effect, but it isn't an upgrade like an OTA is, it's just raw flashing. If the OTA fails, no worries, you'll be able to boot back up, but you'll have to explore the options I just stated.
jimbridgman said:
I will answer number 3 for you.
It is safe now to upgrade to the ICS OTA, since we do have an official AT&T ICS FXZ version that can be flashed through RSD lite. Now if you are a fan of webtop or GB, and want the ability to go back to GB, then do not update to the OTA, or leak 2. You can go back to GB from ICS leak one ONLY, I have a script in the dev section for just that. There is NO difference between leak 1, leak 2, or the "official" OTA, so you can pick what you want to install based on the notes I have given here.
Click to expand...
Click to collapse
Thx Jim. I found your post on how to get toe leak 1 here: http://forum.xda-developers.com/showthread.php?t=1779968
However, your line "There is NO difference between leak 1, leak 2, or the "official" OTA..." confused me? No difference as the are the exact same?
gcretro said:
Thx Jim. I found your post on how to get toe leak 1 here: http://forum.xda-developers.com/showthread.php?t=1779968
However, your line "There is NO difference between leak 1, leak 2, or the "official" OTA..." confused me? No difference as the are the exact same?
Click to expand...
Click to collapse
Sort of, but not exactly. The only real difference between leak 1 and leak 2 is the bootloader version that gets installed, once leak 2 is installed the bootloader will not allow you to go back to GB no matter what. As far as the firmware/ROM itself, all three do not have really any noticeable differences, so you can use any JB or ICS ROM on top of any of them with out issue. I think that there might have also been a small kernel update in leak 2 and the OTA as well, but it was a very small one, that does not effect much for the end user.
On thing we have noticed with leaks and OTA's since the 2.3.6 update, is that motorola will not put a leak on their servers until it is very stable and very close to the final OTA.
Also note that ONLY AT&T phones can use the leaks that we are speaking of. There were different ICS leaks for the international and the TW/HK versions of the atrix2 as well, so they will have different posts out there, if you need those, and you can not flash any other firmware if you are on the AT&T branded phone, and if you are on an international, or the TW/HK phone I would NOT flash the AT&T version (it might lock you to that firmware). The AT&T phone will hard brick if you install the wrong firmware, so be very careful.
Here is the link for the official FXZ and also where all the FXZ files are kept, for future reference:
All FXZ files for the atrix2:
http://sbf.droid-developers.org/edison/list.php
The one for ICS and AT&T:
http://sbf.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
Now the FXZ method is the best and easiest way to do this, the leak method that I have is a real PIA, so I am laying them both out here for you, so you have all the cards in the deck.
Again the ONLY reason to stay on GB is the ubuntu webtop, and while I still had my A2, I kept it on leak 1 without any issues, and would go back to GB weekly to try and get the ubuntu webtop ported to ICS, but without much luck. so.... there it is all laid out for you.
Let us know what you decide to do and how it goes, then also how you like ICS, I think it runs awesome on the A2, much better than GB.
Done. ATT OTA to ICS was successful. My my setting and apps were retained.
Now: since I am test engineer by profession, on to finding issues.
1. I read somewhere that ICS was to bump the cpu to 1.2ghz? I downloaded android system info and it said current frequency is 1ghz :crying:
2. Next I plan to root. I assume rooting is needed (for trying custom roms later on?) and has no negative aspects. I should follow this thread to root right? http://forum.xda-developers.com/showthread.php?t=1787796
gcretro said:
Done. ATT OTA to ICS was successful. My my setting and apps were retained.
Now: since I am test engineer by profession, on to finding issues.
1. I read somewhere that ICS was to bump the cpu to 1.2ghz? I downloaded android system info and it said current frequency is 1ghz :crying:
2. Next I plan to root. I assume rooting is needed (for trying custom roms later on?) and has no negative aspects. I should follow this thread to root right? http://forum.xda-developers.com/showthread.php?t=1787796
Click to expand...
Click to collapse
Thanks for reporting back. I'm glad you got it.:thumbup: The root method I use is the one posted by jimbridgman here:
http://forum.xda-developers.com/showthread.php?p=28934153
Other than the things I have screwed up by my own mistakes, I haven't noticed anything but positive effects by rooting. No biggie as long as you have an fxz and/or nandroid backups. You will need to be rooted to install custom ROMs, and you'll need a custom recovery as well. Some ROMs are specific to certain custom recoveries, just be sure to follow the install instructions for each ROM to a T and you can't go wrong. As far as CPU speed goes, it's a really weird thing that seems to vary for some reason I don't quite understand so I can't elaborate on that too much. (Maybe someone with more knowledge on that can fill in the blanks for us both.) But daavis has some over clock zips posted in the development section. I haven't used them since I was one of the lucky ones that got 1.2 GHz out of the box, but most people seem to have had good luck with them.
Sent from this thing.
Is this normal?
I've avoided Lollipop this while time because of all the storage crap, but it has too many features for the shield I can't go without.
I'd hate to have to reflash from scratch (for the 100th time), this thing wipes data like it's nothing.
Let me know if you guys have any insight.
Thanks.
Nevermind
Reflashed from scratch.
It almost makes no sense to mod this thing. You can't get OTAs.
Every time you flash you have to wipe.
I almost don't want to start modding again in fear that I'll lose a function and have to start over again...
Gootah said:
Reflashed from scratch.
It almost makes no sense to mod this thing. You can't get OTAs.
Every time you flash you have to wipe.
I almost don't want to start modding again in fear that I'll lose a function and have to start over again...
Click to expand...
Click to collapse
You know you can flash OTA's when rooted... So you don't have to wipe.
For example, let's say your rooted and on the latest 2.2.1. If 2.3 comes out, you just flash the 2.3 OTA in TWRP or CWM, and do NOT have to wipe data.
THIS link has all the OTA's, along with a bunch of other useful things.
FoxyDrew said:
You know you can flash the incremental OTA's... So you don't have to wipe.
For example, let's say your rooted and on the latest 2.2.1. If 2.3 comes out, you just flash the 2.2.1 - 2.3 incremental update in TWRP or CWM, and do NOT have to wipe data.
THIS link has all the incremental OTA's, along with a bunch of other useful things.
Click to expand...
Click to collapse
Don't mean to step on your toes @FoxyDrew, but I believe you meant full OTAs. Incremental OTAs check the device version and report the wrong thing (if rooted), however full OTAs don't give two sh!t$ on what your build number is lol. You are correct however in that OTAs of any nature do not wipe a thing besides your rooted status.
MidgetMob said:
Don't mean to step on your toes @FoxyDrew, but I believe you meant full OTAs. Incremental OTAs check the device version and report the wrong thing (if rooted), however full OTAs don't give two sh!t$ on what your build number is lol. You are correct however in that OTAs of any nature do not wipe a thing besides your rooted status.
Click to expand...
Click to collapse
Woops haha, was late when I posted that ;-;
BTW thanks for that thread, has saved my butt a few times and definitely helped when I was new to the tablet.
Thanks for replying guys.
The base of what I'm saying is that this is the most temperamental device I've ever had to maintain.
Even more so than my S4 with it's random kernel rejections (WiFi sometime doesn't work when swapping ROMs).
Another issues I have is pulling the OTAs. I hate waiting from a random contributor to post the link to the full OTA FOR me.
Then I have to worry about whether there's a root method for it afterward, so frustrating.
Seriously considering just going CM12+Limelight.
FoxyDrew said:
Woops haha, was late when I posted that ;-;
BTW thanks for that thread, has saved my butt a few times and definitely helped when I was new to the tablet.
Click to expand...
Click to collapse
Yea man, no worries. That's what the thread is for haha
Gootah said:
Thanks for replying guys.
The base of what I'm saying is that this is the most temperamental device I've ever had to maintain.
Even more so than my S4 with it's random kernel rejections (WiFi sometime doesn't work when swapping ROMs).
Another issues I have is pulling the OTAs. I hate waiting from a random contributor to post the link to the full OTA FOR me.
Then I have to worry about whether there's a root method for it afterward, so frustrating.
Seriously considering just going CM12+Limelight.
Click to expand...
Click to collapse
I understand your complaints with this device. It's been buggy since release day, however I will say that the amount of hiccups per week has gone down to maybe 1 or 2 with 5.0.1.
Regarding OTAs - the thread that FoxyDrew posted (the thread that I maintain) will always have new OTAs and recovery images posted within a day. I'd recommend subscribing to that thread so you know when I post the new OTAs/recovery images. That is, as long as you're fine with waiting up to a day for the update. If not, maybe CM12 is right for you.
As for the root method, rooting has been as simple as flashing a zip file from recovery. It's been like that for quite awhile now. As long as there isn't some major change to the software, it should continue to be that simple for the lifespan of this device.
Hey man, custom ROMs may be the thing for you if you really hate stock android on this tablet. Give it a try and see what you like the best. Just know that there are solutions to almost every problem that you have stated, you just gotta dig around a little bit. If you do end up sticking with the stock ROM, be sure to bookmark that thread as it will make your life a hell of a lot easier
Gootah said:
Thanks for replying guys.
The base of what I'm saying is that this is the most temperamental device I've ever had to maintain.
Even more so than my S4 with it's random kernel rejections (WiFi sometime doesn't work when swapping ROMs).
Another issues I have is pulling the OTAs. I hate waiting from a random contributor to post the link to the full OTA FOR me.
Then I have to worry about whether there's a root method for it afterward, so frustrating.
Seriously considering just going CM12+Limelight.
Click to expand...
Click to collapse
I personally run CM12.1. Best thing ever for this tablet in my opinion. Fixed the sluggishness of Lollipop that people had, and only con is lack of some Nvidia features, although Nvidia Hub and Grid Gaming still work just fine along with other things (the lack of the button mapper sucks most for me). Anyways before I start sounding like I'm being paid to promote CM, I recommend you make a nandroid, try it, and then if you hate it just flash back.
FoxyDrew said:
I personally run CM12.1. Best thing ever for this tablet in my opinion. Fixed the sluggishness of Lollipop that people had, and only con is lack of some Nvidia features, although Nvidia Hub and Grid Gaming still work just fine along with other things (the lack of the button mapper sucks most for me). Anyways before I start sounding like I'm being paid to promote CM, I recommend you make a nandroid, try it, and then if you hate it just flash back.
Click to expand...
Click to collapse
MidgetMob said:
Yea man, no worries. That's what the thread is for haha
I understand your complaints with this device. It's been buggy since release day, however I will say that the amount of hiccups per week has gone down to maybe 1 or 2 with 5.0.1.
Regarding OTAs - the thread that FoxyDrew posted (the thread that I maintain) will always have new OTAs and recovery images posted within a day. I'd recommend subscribing to that thread so you know when I post the new OTAs/recovery images. That is, as long as you're fine with waiting up to a day for the update. If not, maybe CM12 is right for you.
As for the root method, rooting has been as simple as flashing a zip file from recovery. It's been like that for quite awhile now. As long as there isn't some major change to the software, it should continue to be that simple for the lifespan of this device.
Hey man, custom ROMs may be the thing for you if you really hate stock android on this tablet. Give it a try and see what you like the best. Just know that there are solutions to almost every problem that you have stated, you just gotta dig around a little bit. If you do end up sticking with the stock ROM, be sure to bookmark that thread as it will make your life a hell of a lot easier
Click to expand...
Click to collapse
Collectively you guys have outlined why this is a complicated decision. The button mapper gives my life meaning!
And I bought it for the Nvidia apps!
I think I'll just come to terms with the fact that this device just requires more time than most.
Maybe I'll commit to doing nandroid>clean flash/recovery flash via thread mentioned above>restore data if necessary.
I can never get a clean flash out of this device. I flashed 4.0->5.0, got a black screen.
Flashed 5.0->5.0.1, internal storage not working.
The only thing thas has been working is full clean flash via Fastboot and as far as root, finding the right ZIP I guess.
The one from Chainfire's site never works for me, but some on the forums do.