Database Info

VRALG7 Update Question

I am relatively new to the rooting experience but am a big fan of the benefits. I only do basic stuff and am too paranoid to try flashing ROMs or anything too advanced. I recently downloaded the most recent update and it didn't go as I had anticipated.
I was taken to the reboot screen as if I was using Clockwork Mod. It asked me questions that I had to answer in order to proceed but the choices were strange. It would ask me, "do you want to install this unfamiliar zip?" and the answers would be, "No, No, No, No, No, No, Yes, No, No, No, Go Back." I picked yes for the 3 different choices and it completed the install.
After the phone rebooted there was a message saying that the update had failed. I called my brother who has an unrooted phone and checked to see that I in fact do have the update. I am wondering if this is what will happen each time I get an update and if there is anything I should be worried about. The phone is still rooted and I don't notice anything different, but I am just paranoid that rooting my phone will make it so I am unable to install the jellybean update next month. Thanks for the advice in advance!

that sounds like CWM or it might be the factory download mode but either way i dont think you should have to do that for a factory update

So you are on stock, but rooted? Usually the rule of thumb is not not accept the OTA updates, but rather flash one of the stock, rooted roms when an update comes out. You might wnat to try something like the root66 rom, if not somehting like Synergy or CleanRom, which are still stock-based.
As far as this particular issue, as far as I knew, the OTA updates will usually always install. The problem is that they will sometimes revert back to un-rooted, and sometimes will even block the root exploit so you're stuck.

update will fail if you are using a custom recovery, i.e. cwm

wwjdd44 said:
update will fail if you are using a custom recovery, i.e. cwm
Click to expand...
Click to collapse
Is there any way to remove clockwork mod? I don't really need it.

[Q] A700 rooting question

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!

[Q] On VRBMD3 rooted and unlocked - how to take MF1?

Usually the information I need I can find easily here, I've never had a need to register and post until today. I've searched but can't quite find the answer to my question. So I apologize in advance if my search skills have failed me this time.
I am on a VzW SGS3 that has taken the unfortunate MD3 update. I am rooted and unlocked already. I have ClockworkMod Recovery installed. Everything is as OK as MD3 can be. I had followed the instructions in this thread in the past:
http://forum.xda-developers.com/showthread.php?t=2046439
It appears the users in that thread are awaiting the MF1 bootchain from the latest posts and other users have tried to take the OTA MF1 update and got the dreaded triangle, were forced to reflash stock, take all the OTA updates and await the bootchain to unlock again.
So with that bit of background, my question is thus: what is the easiest way to take on new OTA updates without losing all my data?
I can flash a stock ROM someone made for MF1 but I'm pretty sure I lose data since the best way to flash ROM's is clean. I don't want to deal with dirty flash issues. Do I really have to go through and set up Nova Launcher (and other apps) just the way I like it again? Do I have to go through each app and backup settings (or use Titanium?) I don't really want to go stock, take all OTA's then use Casual just to get MF1 now. I think that would require clean install too and I can certainly wait as Casual doesn't really give you a choice of your root and recovery elements from what I understand.
This thread ( http://forum.xda-developers.com/showthread.php?t=1974114 ) provides a nice stock image without losing any data. It's back to MB1, then one would take the OTA updates, then follow the rest of the guide to root and unlock. Still need to wait for the MF1 bootchain though - is THIS the best way?
Basically, what is the "best practice" when one is already rooted, unlocked and has a custom recovery to take on new OTA updates?

MRV18 said:
Usually the information I need I can find easily here, I've never had a need to register and post until today. I've searched but can't quite find the answer to my question. So I apologize in advance if my search skills have failed me this time.
I am on a VzW SGS3 that has taken the unfortunate MD3 update. I am rooted and unlocked already. I have ClockworkMod Recovery installed. Everything is as OK as MD3 can be. I had followed the instructions in this thread in the past:
http://forum.xda-developers.com/showthread.php?t=2046439
It appears the users in that thread are awaiting the MF1 bootchain from the latest posts and other users have tried to take the OTA MF1 update and got the dreaded triangle, were forced to reflash stock, take all the OTA updates and await the bootchain to unlock again.
So with that bit of background, my question is thus: what is the easiest way to take on new OTA updates without losing all my data?
I can flash a stock ROM someone made for MF1 but I'm pretty sure I lose data since the best way to flash ROM's is clean. I don't want to deal with dirty flash issues. Do I really have to go through and set up Nova Launcher (and other apps) just the way I like it again? Do I have to go through each app and backup settings (or use Titanium?) I don't really want to go stock, take all OTA's then use Casual just to get MF1 now. I think that would require clean install too and I can certainly wait as Casual doesn't really give you a choice of your root and recovery elements from what I understand.
This thread ( http://forum.xda-developers.com/showthread.php?t=1974114 ) provides a nice stock image without losing any data. It's back to MB1, then one would take the OTA updates, then follow the rest of the guide to root and unlock. Still need to wait for the MF1 bootchain though - is THIS the best way?
Basically, what is the "best practice" when one is already rooted, unlocked and has a custom recovery to take on new OTA updates?
Click to expand...
Click to collapse
Just flash Scrosler's stock rooted ROM and you'll be good to go. You won't have any problems with not wiping (except for it might be a little itchy :laugh::laugh::silly
The best "practice" is not to take an OTA when you're rooted because chances are you will already be running it before it is out! Also, it is always a good idea to keep a backup of your apps with TiBu and use Nova to backup your desktop settings.

Thanks, I did just flash that ROM. However, my Baseband Version still shows MD3 (the Build number is MF1, however) and I still get the nag screen to take the OTA update. Not sure what to do here. I think for the time being, I'll just experiment with some other ROM's and see if I truly miss anything from Samsung.

Flash the MF1 firmware package after to get the radio.

Thanks. I did such and everything now says MF1 but this still doesn't seem ideal. My root seems to be missing (Secure Settings isn't working, I see ads in apps) and my superuser app is missing. So, perhaps I have to reload that and allow the other apps su access again? Additionally, I'm still getting nagged by the OTA update.

So before I flashed Scrosler's stock rooted ROM, I performed a backup of my current build using CwM. I didn't necessarily care for the results of the flash since I was still being nagged (not sure how to deal with that part yet) I just decided to restore my backup. Well that just screwed everything up since the /system portion wouldn't restore. Wonderful.
So I used Odin to load the no-wipe-necessary MB1 file, accepted all the subsequent OTA's (it was only two - the first one being the application of the MB1 update.zip) then just used the Casual root method on a machine with Java installed. Worked great. I'll think I'll just leave well enough alone until the next update.

OTA
I took the MF1 update OTA. Then I used the root method provided by open1your1eyes0 to root and unlock. Still waiting for the final boot gain though.

[Q] new to forums.. info required on 4.4.1 pls

hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about

No you dont need to be unrooted to update your android version.
You need to have the stock recovery and rom. The update isnt available for everyone yet
you will get a update notification just wait

ayush88 said:
hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about
Click to expand...
Click to collapse
You technically voided your warranty when you rooted. But no big deal.
You can download the update and sideload on your own, or wait for the OTA to come to you. If all you have is root, stock recovery and no system mods it will update on its own.

ayush88 said:
hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about
Click to expand...
Click to collapse
Hi do not worry. Those posts really do not apply to you yet. You have a phone that is stock meaning, you bought it and using it. If you keep it like that you never have to worry about update. Google will automatically push the update to your phone by next week. Incidentally the phone is also a developer phone, so people usually play around with it. Root, custom roms, kernels etc. Now for these enthusiasts to get the update, they have to unroot, ,to stock just like your phone. After getting the update they will start messing with it again:laugh: this forum being the developers forum of the Internet is the reason why you are seeing all those posts.
Now you are sitting on a Ferrari phone, using it as a Honda. Some day in the future you will let it run at indy500

ayush88 said:
hi guys,
i read somewhere in this site that you have to unroot to get the 4.4.1 OTA... does this mean that stock android will never get updated?...or is this update not officially launched by google to the masses but just to the developers? pls im new to android and would like to know what the deal is here.
also i have no problem unrooting but i heard that you will stop getting OTA's and will have to side load all new updates everytime and you will also void your warranty...which im in two minds about
Click to expand...
Click to collapse
Did you mean to ask "do you need to root to get the 4.4.1 OTA"?? If not, your question doesn't seem to add up....
You definitely do NOT need to root to get the OTA. You can wait for the update to be pushed out, or, if you are impatient, you can sideload using ADB or install from recovery.
If you are rooted, as the other folks explained, you may need to get back to stock before you can install 4.4.1

To add to this, I only rooted my Nexus 5 so I could use BetterBatteryStats and some other monitoring apps. Is there any way to go back from TWRP to stock recovery without wiping data/losing root?
I'm quite happy with everything stock and don't plan on doing any mods.
Also, I sideloaded 4.4.1, but would I have gotten the OTA with TWRP?

mmmmBACON said:
To add to this, I only rooted my Nexus 5 so I could use BetterBatteryStats and some other monitoring apps. Is there any way to go back from TWRP to stock recovery without wiping data/losing root?
Click to expand...
Click to collapse
Yes, get the recovery.img from the factory image and: fastboot flash recovery recovery.img. That'll put the stock recovery back on your device

donentl are
thnks alot you guys!!
this really helped me out!
i know i am new to android right now and dont know the ins and outs of this os completely... i really liked a reply which said i am sitting on a ferrarri and using it like a honda..lol...i will run it like a veyron in some time but for now my car comes with a "L" sign and a speed limiter on it
thnks again you guys!

[Q] Just updated to Lollipop, Can't See My Internal Storage in My File Manager

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.