Database Info

Pushing Recovery on 3.2.6

Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks

DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.

after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.

Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.

DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way

[Q] Question concerning Dragonzkiller's Droid x2 CM9 Rom

Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.

Tab 2 10.1 GT-P5113 WIFI OTA Rooted.....

So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?

Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.

I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.

I'm wondering if I should remove CWM and unroot it first...

Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.

Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)

No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.

I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.

Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..

I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say

To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.

I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.

I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.

Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.

[Q] Acer A700 system bar missing

I bought an Acer A700 tablet off ebay, was supposed to be new unused condition. Booted it up and it had no system bar at bottom of page. That means you can't get out of any app you have to reboot, useless. Thru reading on site and exploring this tab i found out it has super user installed on it and on bootup in the left hand corner it reads "boot loader ICS-MRI 7173de1 (unlock mode)" every thing on the tablet seems to work except no navigation bar, no circle in center, and no status info no bar at all full screen. I have played with this thing been on Acer chat and they say hard ware failure. That is before i new it was rooted, i guess that is the reason the update he wanted me to try did not work. I don't know if i try a new OS system if that will even work. I am 68 years old and this is my first android tablet, new ground for me. Most every thing i read is above my knowledge, would appreciate any advice i might just try it. thanks ahead of time

demo mode
Is there a demo mode on this acer A700 and if so where to look thanks

easyreble said:
I bought an Acer A700 tablet off ebay, was supposed to be new unused condition. Booted it up and it had no system bar at bottom of page. That means you can't get out of any app you have to reboot, useless. Thru reading on site and exploring this tab i found out it has super user installed on it and on bootup in the left hand corner it reads "boot loader ICS-MRI 7173de1 (unlock mode)" every thing on the tablet seems to work except no navigation bar, no circle in center, and no status info no bar at all full screen. I have played with this thing been on Acer chat and they say hard ware failure. That is before i new it was rooted, i guess that is the reason the update he wanted me to try did not work. I don't know if i try a new OS system if that will even work. I am 68 years old and this is my first android tablet, new ground for me. Most every thing i read is above my knowledge, would appreciate any advice i might just try it. thanks ahead of time
Click to expand...
Click to collapse
Ok, so whoever you bought it from, told you an outright lie. The bootloader is unlocked, and, it most likely has a custom OS installed on it. You can check this by going into "Settings" "About Tablet" and seeing what is installed on it.
Or,
The previous owner had root access (obviously) and went mucking around with the SystemUI.apk and goobered something up (most likely). In fact, I would guess he had CM installed and didn't like the way the nav icons were (in the center) and tried doing something about it by modifying files he had no idea of what to do.
The most simple fix, would just be to install a fresh version of either a custom ROM, or, revert it back to a stock factory ROM. Both of which are relatively easy to do.
MD
EDIT: Other things to look for now that I think about it. Check your applications and see if any of the following are installed.
Launcher (Nova, Go, etc) These sometimes have an option to disable the system bar (Nav Bar).
ExPosed Installer - This allows loading of custom exposed frameworks mods that several have the option to disable the System Bar (nav bar)
Any Nav Bar/System Bar "Hide" application. These at one time were useful to open more display real estate for games. (not many use them anymore)
Those applications you can safely uninstall through Settings/Applications, then reboot.
Other than that, I can't think of anything else. Will wait till you tell us which OS is installed (CM; Cyanogen Mod, PA; Paranoid Android, etc)
Oh, and one more thing. Stop talking to those folks on Acer Chat. This is a software issue, and not a Hardware issue. This I can promise.

easyreble said:
Is there a demo mode on this acer A700 and if so where to look thanks
Click to expand...
Click to collapse
"Demo" mode, is not a configurable option on most devices. In reality, it is a custom software from Acer that is installed for Store Display purposes. Several items have been left out of the build, specifically to prevent casual customers from mucking things up.
This is generally fixed by installing a full ROM.
MD

Moscow Desire said:
Ok, so whoever you bought it from, told you an outright lie. The bootloader is unlocked, and, it most likely has a custom OS installed on it. You can check this by going into "Settings" "About Tablet" and seeing what is installed on it.
Or,
The previous owner had root access (obviously) and went mucking around with the SystemUI.apk and goobered something up (most likely). In fact, I would guess he had CM installed and didn't like the way the nav icons were (in the center) and tried doing something about it by modifying files he had no idea of what to do.
The most simple fix, would just be to install a fresh version of either a custom ROM, or, revert it back to a stock factory ROM. Both of which are relatively easy to do.
MD
EDIT: Other things to look for now that I think about it. Check your applications and see if any of the following are installed.
Launcher (Nova, Go, etc) These sometimes have an option to disable the system bar (Nav Bar).
ExPosed Installer - This allows loading of custom exposed frameworks mods that several have the option to disable the System Bar (nav bar)
Any Nav Bar/System Bar "Hide" application. These at one time were useful to open more display real estate for games. (not many use them anymore)
Those applications you can safely uninstall through Settings/Applications, then reboot.
Other than that, I can't think of anything else. Will wait till you tell us which OS is installed (CM; Cyanogen Mod, PA; Paranoid Android, etc)
Oh, and one more thing. Stop talking to those folks on Acer Chat. This is a software issue, and not a Hardware issue. This I can promise.
Click to expand...
Click to collapse
You are correct, i will never talk to acer support again. I am getting ready to install a rom if i can figure out which one to start with. It has Adroid Veersion 4.0.4 Kernal version 2.6.39.4+ Boot loader ICS-MRI 7173de1 (unlock mode) It has superuser app installed, I did download an app which gave me a navigation bar that i am using till i can get a rom installed. My problem is that looks like i need to upgrade this 4.0.4 ICS before i can install the up to date roms is that correct. Thanks for helping be get this straight this is a lot for an old man to take in lol.

easyreble said:
You are correct, i will never talk to acer support again. I am getting ready to install a rom if i can figure out which one to start with. It has Adroid Veersion 4.0.4 Kernal version 2.6.39.4+ Boot loader ICS-MRI 7173de1 (unlock mode) It has superuser app installed, I did download an app which gave me a navigation bar that i am using till i can get a rom installed. My problem is that looks like i need to upgrade this 4.0.4 ICS before i can install the up to date roms is that correct. Thanks for helping be get this straight this is a lot for an old man to take in lol.
Click to expand...
Click to collapse
4.0.4 should be the original ICS ROM. If you get it installed, it should get you a locked bootloader, and hopefully offer the upgrade to JellyBean (4.1.x I believe)
Don't worry about age, I'm not far behind you
Have an issue, just PM me and I'll see if I can help.
MD

Moscow Desire said:
4.0.4 should be the original ICS ROM. If you get it installed, it should get you a locked bootloader, and hopefully offer the upgrade to JellyBean (4.1.x I believe)
Don't worry about age, I'm not far behind you
Have an issue, just PM me and I'll see if I can help.
MD
Click to expand...
Click to collapse
No that is what is on my tablet now unlocked and rooted. thanks. i am not clear as to get it upgraded form 4.0.4 and not sure if i need to upgrade to put new rom on it, and which one to work with. I have all my info downloaded on my computer, got to get a cable to work with. Just not sure if i can put the newest version on it without flashing it back to stock locking the boot loader upgrading and then rooting it again just to much i may need to take a break after 3 days of reading, but i have learned a lot. thanks what do u think

easyreble said:
No that is what is on my tablet now unlocked and rooted. thanks. i am not clear as to get it upgraded form 4.0.4 and not sure if i need to upgrade to put new rom on it, and which one to work with. I have all my info downloaded on my computer, got to get a cable to work with. Just not sure if i can put the newest version on it without flashing it back to stock locking the boot loader upgrading and then rooting it again just to much i may need to take a break after 3 days of reading, but i have learned a lot. thanks what do u think
Click to expand...
Click to collapse
Well, 4.0.4 ICS (ice cream sandwich) is the OS these tablets were shipped with. Then, it generally, after some days, would upgrade to 4.1x (jelly bean) Gotta love Google and the names.
Now, considering your tablet has SU (Superuser), and and unlocked bootloader, means somebody mucked with it, hence the missing NAV(Sys) bar. Dude undoubtedly mucked around with things.
As I stated before, this can happen due to several different reasons. How it got to that point, who knows.... In testing ROMs, Ive had this issue by installing a different SystemUI.apk that didn't match all the other files, Or, by "dirty" flashing a ROM without wiping /System partition.
Basically, to get it back to a completely stock A700, you will need to install a stock Factory A700 ROM. the 4.0.4 version. Should be able to find one quite easily, but if not, let me know and I'll help.
Basically, you rename that Stock ROM to "update.zip", copy it to ext SD, then boot the tablet holding "VOL+ then PWR and it "should see the zip and start to install it. "Should".
If not, then I can walk you through the steps to install a custom recovery, and we can do it that way. Acer, with JellyBean, actually has a somewhat recovery menu. Not sure if the 4.0.4 has it or not. Been too long. It may just look for "update.zip" and try and install it.
So will just have to see how it plays out.
For my own, I use "fastboot" so install image files to revert back, but that's just me. Also I have an A701, so it wouldn't do you much good
Same hardware so to speak, except for the 3g part and some different files.
MD

Screwed Shield Up!

I'm completely overwhelmed with this Shield at the moment. Can't even think straight, because it's frustrating me so much. I rooted it and unlocked the bootloader. Now, I tried to update to 99, but it won't let me. So, finally, I decided to change it back to stock. After several attempts at this, now when it loads it just sits at a black screen. Before I got it to work, but it wouldn't check for updates and oddly enough the Play Store was acting weird (downloading slow, operating slow). Not sure if that's relevant, but I get 1.8 MB/s download speed, so I know it's not me. Everything else downloads just fine.
I'm using this thing called Shield Ram which includes adb, cwm recovery, fastboot, and the likes.
***Update***
While typing this, I was able to get the Shield back up after trying to flash the stock rom, but I still have the issue where I can't update.
I go to About Shield/System updates/ and it says "Your system is up to date. Last checked for update at 3:46PM." With a Check now button that doesn't work.
I know that there's update 99 out, but it's on 68 refusing to update or even check for it. I fear that rooting and unlocking it screwed everything up!
Any help would be much appreciated.

Screwed Shield Up! (Solved - I think)
So, just in case anyone is having the same problems as me. I followed this thread to a T and so far it seems to be working. I didn't install the root, though, because it seems like that is what got me in trouble in the first place. Not sure if that was bad or if now it's not rooted and that's the end of it. Hopefully I can just update normally, but if all else fails, then I'll have to reflash or reroot. Again, hopefully it doesn't come down to that.
:good:
[Firmware] Nvidia Root-Friendly Updates [No Wipe]

How do you get root after the latest patch? The one shown in here not working for me currently. :\