Can't boot into recovery on A500 Tablet - Acer Iconia A500

I can't seem to get into my recovery on my tablet. It gets to the screen of the Android and goes the gears moving thing, then it stops and gives me a yellow sign just like the icon I'm using for the this thread. The tablet has been rooted running 3.2.1, kernel version 3.6.36.3+, build number Acer_A500_7.014.02_COM_GEN2.
I downloaded Acer Recovery Installer and it's listing that I have Clockworkmod Recovery rev1.34 by thor2002ro, and Stock USA 1.141.07_COM_GEN1 recovery. When I tried to reboot into either recovery, I get the yellow exclamation mark.

sounds like you have the bootloader removed (it happens to Stock v3.2 and up)
Your booting into Acer's Recovery (not CWM)
sounds like you just installed "Acer Recovery installer" app from market.
IF YOU CAN, check the dot with "ClockworkMod Recovery v1.34" and install it. You will need ROOT to install CWM Recovery.
You can't have both Recoveries at once (those are your options to install with that prog) if your ROOTED!
*** FACT : If you can't get into CWM Recovery & your on HC v3.2 or newer, you have to do the following (to have Root)...
Option #1: TimmyDean's Method 3.2.1 v4 http://forum.xda-developers.com/showthread.php?t=1307539
Option #2: [TUT] Revert OTA 3.2 back to 3.0.1 (method #2 is easier) http://forum.xda-developers.com/showthread.php?t=1276227

I did install the Acer Recovery installer from the market, simply so I could see what Recoveries where on the tablet. I've tried booting in both recovery's and neither one will let me. I get the same error screen. The tablet is rooted already,super user is installed and working.

adamsavage said:
I did install the Acer Recovery installer from the market, simply so I could see what Recoveries where on the tablet. I've tried booting in both recovery's and neither one will let me. I get the same error screen. The tablet is rooted already,super user is installed and working.
Click to expand...
Click to collapse
Sorry you're having issues, but the yellow ! comes from ONLY the ACER stock recovery. So if that's what you are getting then you're not installing CWM correctly.
Also, ACER puts back their stock recovery on every reboot. Therefore, you have to make sure that you follow the instructions in CWM from the market place exactly so it turns off that behavior.
Lastly, if you believe you are installing CWM correctly and are still getting the yellow ! then you're root is not working. If root is failing, then CWM cannot install and you might however be mislead into thinking it did.
Hope this helps,
Let me know
TD

I'm pretty sure my root access is working, I wouldn't be able to even open super user unless I was. I have several aps that require root access to even open. I even ran root check basic and it says I'm rooted. I have a HTC Nexus One that's also rooted, so I would know right away if I wasn't rooted. Example being is AD Block, it requires root access to work. I don't see ad's when I browse websites that I know are full of ad's.
I wasn't trying to install anything, I simply wanted to get into the recovery but I can't even do that. As I mentioned when I try to reboot into recovery I get that error screen. I rooted my phone and all that stuff myself, but I remembered how much of a headache it was to set the computer up in order to do so. I'm not all that great with stuff like that, so it took me several hours to understand, and to get the SDK manager to see the phone and stuff. So I saved myself the headache and got my friend to do it for me. I already asked him what recovery software he put on it and he doesn't recall. The only thing I have to go on is what the Acer Recovery Installer tells me I have. I gives me 4 options. Install Recovery Image, Reboot into recovery, Backup/Restore tablet, Download/Install Rom's.
When I tap the Install Recovery Image option, It says under it in red "Premuim features (Backup/Restore tablet, Download/Install Rom's) require ClockworkMod Recovery Rev 1.3.4 or higher. It says just above red txt "Currently installed: Unknown stock or custom rom"
Is it possible I don't have any recovery Rom installed ?

my Opinion: If you truly had SuperUser installed (I get that you see it in your apps), you should be able to PUT CWM recovery on from the Market app "Acer Recovery Installer".
also It says that it can't Tell what Recovery you have (cus you have stock recovery).
Maybe it's possible, you're friend installed part of the Superuser, like maybe he tested TD's v3.2.1 "backdoor.cmd" or "busybox.cmd" tools and sorta got part of it installed. I know what I'm talking about (even if i haven't correctly articulated it here)
maybe testing other apps (like Root Explorer, titanium backup, SETCPU, etc.)
or maybe test TD'S 3.2.1 v4 batch files (to get foot in the door)
Sounds to me, like you have what i would say is "Half Root"
it could be like installing "superuser" app from the market and running, where it need more than just that to work.
This is messy, i know, i get what what I'm saying, even though i can't articulate it well. Just trying to be helpful. and frustraited. If i was there, i could fix it, by messing arround, just can't explain it. LAUGHING at MYSELF (on the inside)

ktmdave7 said:
my Opinion: If you truly had SuperUser installed (I get that you see it in your apps), you should be able to PUT CWM recovery on from the Market app "Acer Recovery Installer".
also It says that it can't Tell what Recovery you have (cus you have stock recovery).
Maybe it's possible, you're friend installed part of the Superuser, like maybe he tested TD's v3.2.1 "backdoor.cmd" or "busybox.cmd" tools and sorta got part of it installed. I know what I'm talking about (even if i haven't correctly articulated it here)
maybe testing other apps (like Root Explorer, titanium backup, SETCPU, etc.)
or maybe test TD'S 3.2.1 v4 batch files (to get foot in the door)
Sounds to me, like you have what i would say is "Half Root"
it could be like installing "superuser" app from the market and running, where it need more than just that to work.
This is messy, i know, i get what what I'm saying, even though i can't articulate it well. Just trying to be helpful. and frustraited. If i was there, i could fix it, by messing arround, just can't explain it. LAUGHING at MYSELF (on the inside)
Click to expand...
Click to collapse
Exactly, well put your install is fubar

Ahhh I'm a dumb ass...I never actually tried to install the clockwork mod recovery. I taped the option. It did it's thing and said it was installed. Then I told the Acer Recovery Installer to reboot into that recovery and it worked!

adamsavage said:
Ahhh I'm a dumb ass...I never actually tried to install the clockwork mod recovery. I taped the option. It did it's thing and said it was installed. Then I told the Acer Recovery Installer to reboot into that recovery and it worked!
Click to expand...
Click to collapse
LOL, good to hear it.

Boot Recovery
timmyDean said:
LOL, good to hear it.
Click to expand...
Click to collapse
Recovery Verified Failed message when I try to boot to recovery. I have the Acer recover installer install have root access but I dont see an option to install "ClockworkMod Recovery v1.34"
Any light on the matter
iconia a500 ics

Related

Problems installing OTA updates

OK, for starters:
Tablet's current stats:
ROM: CWM-Rooted_Acer_A500_7.006.01_COM_GEN2
Recovery: Stock US 1.141.07_COM_GEN1
Root status: Rooted
Problem at hand: Cannot install OTA updates. I used Acer Recovery Installer to originally install CWM so I could flash ROMs (duh). So I used Acer Recovery Installer to have it install the stock recovery image so I could actually install the OTA updates. I know this likely means I would lose root, and that is OK.
When I installed the stock recovery back, I tried to let it install the update. It would reboot, show the package opening (little box that was open and a progress bar showed up). The bar got about 25% completed, then it changed into a triangle with a "!" inside it, and the little Android dude below it. After a few minutes, it would reboot by itself. Once booted up, I would get a message that simply said "Update Failed".
I brought this up in another thread, and someone suggested I unroot as well. I immediately tried to do that, but IconiaRoot gives me the following:
Removing superuser.apk
Removing /system/xbin/su
Sleeping in 5 seconds...
Something went wrong.. you are still root?!?!
I can confirm I am still rooted by going into terminal emulator and running su and I get a # sign. So I am at a loss now on what else to try. With the stock recovery, if I tell Acer Recovery Installer to reboot into recovery, when it reboots, all I get is the triangle with a "!" in it. I noticed the ROM has GEN2 and my stock recovery has GEN1, and the OTA update ends with GEN2, is that an issue?
EDIT: I also know now there are other rooted ROMs with these OTAs applied. I'd like to unroot and go back to stock, so please do not recommend this.
Ok did you make a backup via CWM ?
In the other thread the recovery i restored was the backup i made of my one via Acer recovery,
If i was you i would reinstall CWM and make sure that recovery is working then wait for someone to come in and tell you the correct stock recovery for your one is.
oh i get u now, u got the gen2rom installed and u want back to your own stock gen1 to get the OTA, correct?
u need a cwm backup of 3.2 gen1 stock, when u restore it, u should receive an OTA notification for the 3.2.1 GEN1 OTA. Before you download it, u need to be rooted, use the backdoor/OTA method of timmyDeans. It will create a backdoor so after you have installed the OTA you can get in to run the installtools command again to root and install cwm again. AND you will still recieve OTA's.
Iconia Root - only works on 3.1, it will not work for 3.2, so it will throw an error.
But i'm sure root wont prevent the install as the OTA overwrites system files and resets the permissions, it also checks all system apps are there, so if you;ve deleted any bloatware or changed build.props the update will fail.
I have spent the last week trying to get back to stock so i can OTA. I have read hundreds of posts and tried all the methods that had been posted. The easiest and quickest and most successful way of achieving this was the backdoor method. Yes you need adb installed but you dont actually use it, it is all done for you. there is a very good walkthrough here http://www.chdcomputers.gr/en/mnu-kb-en/mnu-kb-android-en/mnu-kb-android-devices-en/mnu-kb-android-a500-en/254-art-kb000005-en
Then install the backdoor v3 (link in sig) -have a look and see if that will get u to where u wanna be!
Decideed it was easieeer to just install one of the prerooted roms from the dev forum. Running 7.014.14.com gen 1 now. Thanks guys.

Unable to boot into recovery using "Acer Recovery" from market/playstore

Hello. After updating my A500 to the official ICS rom, I easily rooted my tablet succesfully by downloading a program found on this website:
http://forum.tegraowners.com/viewtopic.php?f=30&t=350
Then, I downloaded an app from the market/play store called "Acer Recovery" wich lets you flash CWM recovery (which is built in into the app). The app said it flashed the recovery succesfully. Now, when I press the "boot into recovery" button I get stuck in the Acer logo and on the top left corner it sais in red: Recovery Failed
I would like to flash custom roms. What am I doing wrong?
Many thanks...
domenicostorino said:
Hello. After updating my A500 to the official ICS rom, I easily rooted my tablet succesfully by downloading a program found on this website:
http://forum.tegraowners.com/viewtopic.php?f=30&t=350
Then, I downloaded an app from the market/play store called "Acer Recovery" wich lets you flash CWM recovery (which is built in into the app). The app said it flashed the recovery succesfully. Now, when I press the "boot into recovery" button I get stuck in the Acer logo and on the top left corner it sais in red: Recovery Failed
I would like to flash custom roms. What am I doing wrong?
Many thanks...
Click to expand...
Click to collapse
Which version of Bootloader are you running? The recovery installer app should tell you when you start it.
Also, which version of Recovery did you try to install?
Moscow Desire said:
Which version of Bootloader are you running? The recovery installer app should tell you when you start it.
Also, which version of Recovery did you try to install?
Click to expand...
Click to collapse
Thanks for helping me out.
-Bootloader Version: 0.03.12-ICS
I tried installing the two only recoveries avaliable wich are:
-ClockworkMod Recovery rev1.3.4 by thor2002ro
-Stock USA 1.141.07_COM_GEN1 recovery
After flashing any of the two I click on "Reboot into recovery", it reboots but gets stuck in Acer logo and on the top left corner says:
-Recovery verified failed
I have the same problem too and I still couldn't find a way out
Firmware Specs are same as yours
I wonder if there is a simple way out
Anyone can help ?
Thanks
Ramp
Ok, both of you need to go to this thread and read over the info.
The reason why your recovery "might have failed" is probably because you didn't delete a certain file from your rom before you flashed your CWM. That is... "recovery.from.boot.p" in the system folder.
If you don't, every time you reboot your will lose your CWM.
Anyhow, read this thread. Everything you need is there.
http://forum.xda-developers.com/showthread.php?t=1622425
And if you;re going to install some ICS Customs in the future, I advise you install a patched unlocked bootloader.
EDIT: One more important thing. Before you folks go off flashing and everything, PLEASE... Get your UID number now, and write it down in a safe place (like the box your tablet came in . If you tab gets borked up, it's the only thing that'll save it.
MD
As MD stated be sure to read that thread , once down reading it, re-read it , I would try using that method first ,it helps you learn , but if you want to go to this thread and it will be a whole lot easier :http://forum.xda-developers.com/showthread.php?t=1675939
I always tell people in here read as much as you can , read through the Android section as well!
uahuuuuuuuuuuu !
What can I say ......Afterota is AMAZING!!!!
Made my day, not my day...my month!
It works like a charm and it's really easy to handle
Thanks thanks thanks !
Ramp
Thanks, I did it as well with AfterOta, what a great tool. I am already rooted in ICS and have public recovery working. I'd like to try some custom roms. Is there any other step I have to complete before flashing a new custom rom?
Thanks again for the help
domenicostorino said:
Thanks, I did it as well with AfterOta, what a great tool. I am already rooted in ICS and have public recovery working. I'd like to try some custom roms. Is there any other step I have to complete before flashing a new custom rom?
Thanks again for the help
Click to expand...
Click to collapse
I would advise making sure you have at least Version 3 or higher of the unlocked bootloader. Version 4 is better as you can change the boot image. Also, with version 4 (and higher) you can flash any future bootloaders through CWM.
Also, make a system (nand) recovery backup before you go flashing roms. This way you have something to go back to if the flash doesn't go right.
part of the original problem you had was the recovery you tried to flash was an earlier version which doesnt match ICS , You can get the beta copy of Acer Recovery ,but you'll have to search for it , it also has updated ICS recovery listed

Installed firefirefire & clockworkmod; rooting and twrp failed

I'm trying to install jelly bean on my kindle fire but using KFU I've only managed firefirefire and clockworkrecovery.
I tried rooting using KFU to root but that doesn't work. Always gets stuck with the twrp.img error saying it's the wrong image (seems to be a common problem)
I've tried getting twrp installed using adb shell but when I get to the command to load the recovery image I get error; couldn't load recovery image. I thought maybe there was a problem so I tried loading the fff bootloader even though I already had it on my kf but it also returned with error: couldn't load image.
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
soupmagnet said:
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
Click to expand...
Click to collapse
The problem is getting root access. Most of the guides I've tried to follow require twrp installed to get into recovery. Without root I can't flash another rom.
I also already have FFF 1.4.
So I reverted back to stock and went through the manual process again and I was able to get it to work. When I was initially trying to flash twrp with the command line I copied pasted the name of the file without adding the file extension. Fixed that by adding .img and everything went through. Got Jellybean on here now and it's running great.
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
soupmagnet said:
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
Click to expand...
Click to collapse
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
hxu976 said:
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
Click to expand...
Click to collapse
That has nothing to do with "rooting". Most of the time it's caused by a bad download (always check MD5s) or not "wiping" correctly before installation.

[Q] Problems rooting Nexus 4 on Linux

(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Crell42 said:
(OK, the board ate my first post; maybe this one will do better...)
I am trying to root my Nexus 4 in order to install Titanium Backup. (I have some user data to transfer over from my old Samsung Vibrant before I retire it.) I'm using the Nexus Toolkit for Linux, here:
http://forum.xda-developers.com/showthread.php?t=1999065
The first two steps work fine. I can unlock the bootloader and install clockwork mod. When I try to actually root the device and install su, though, I run into a problem. Specifically, going into recovery mode (either automatic through the toolkit or manually myself) I get the Andy the Android "error" icon (Android flat on his back, chest open, with a red warning triangle over it). That remains until I reboot the device.
Any suggestions? I'm not an experienced rooter (Ti Backup is the ony reason I'm even bothering), so keep it basic please.
Click to expand...
Click to collapse
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
hoponpop said:
It sounds like you're losing recovery. Do you restart your device after you flash CWM?
Try flashing CWM manually through fastboot, don't restart the device (will overwrite custom recovery) and just go directly into recovery then flash SU.
Alternatively, make sure you're using the right version of CWM and/or double check that the writing process for CWM is going to completion. I don't know if you can disable the stock recovery overwrite without first having root, but you can also look into that
Click to expand...
Click to collapse
I'm using whatever version is included in the Universal Tooklkit download. It has two versions included, Standard and Touch. I've tried both, same effect.
Any pointers on "manual" installation of CWM? (As I said, rooting newbie.)

[Q] Lost TWRP and root - Help needed

Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?

Resources