Well guys this is what I did... OTA Voodoo did not work to unroot for... me so I started from scratch... At 403 9.x.x17 with NVFlash that I have Lucky me with B50... then took the new OTA update ICS update v9.2.1.21......Butttt Now when pressing the Volume Down and power and then press up it goes into Asus Recovery.. but with the android lying down with an ! over him...ViperMod does not see the the tablet at all...Sooooo Now I guess it's a waiting game to root again..
The Android with ! Is your stock recovery. It doesn't do anything except handle official update file.
I would just nvflash to .17 root it and wait for a cwm version of the new.21. Usually a day or two most till a dev make a cwm version.
Thanks Base I can wait not going back... Just thought I was doing something wrong
really
Yea.. I just killed my DMclient so no Asus update notification harrassing me around..
Will wait for the CWM update for v9.2.1.21 to come.. It's the safer way to update when we have CWM installed and running under v9.2.1.17 at the moment..
what about flashing .17, root it, install ota rootkeeper, update and recover root?
just don't flash a custom recovery before updating via OTA
oifi said:
what about flashing .17, root it, install ota rootkeeper, update and recover root?
just don't flash a custom recovery before updating via OTA
Click to expand...
Click to collapse
Did you try what your saying... and did it work ???
JohnM109R said:
Did you try what your saying... and did it work ???
Click to expand...
Click to collapse
There's a lot of peoples in the "firmware update" thread reporting that it work.
baseballfanz said:
There's a lot of peoples in the "firmware update" thread reporting that it work.
Click to expand...
Click to collapse
Well I got it going as the above said....But after restoring root from Voodoo..that was ok but when I got to install gnufabio one click RecoveryInstaller it says i'm not rooted but I am...Now what LOL ?
Everything is working fine so far the only thing that bugs me is no CWR....
JohnM109R said:
Well I got it going as the above said....But after restoring root from Voodoo..that was ok but when I got to install gnufabio one click RecoveryInstaller it says i'm not rooted but I am...Now what LOL ?
Everything is working fine so far the only thing that bugs me is no CWR....
Click to expand...
Click to collapse
Try this, look in system/xbin to see if you have an su there. If not look in system/bin and copy the su from there and paste it to system/xbin
Yessss thats what was missing.... Thanks So Now I can confirm that this procedure works Great Thanks... Baseballfanz and oifi..
JohnM109R said:
Yessss thats what was missing.... Thanks So Now I can confirm that this procedure works Great Thanks... Baseballfanz and oifi..
Click to expand...
Click to collapse
Ok, would you be able to guide me through the same? I have the same problem. No recovery and no root after .21 update.
I checked my system/xbin and I have su in there. Also in system/bin. I tried using root explorer to copy it over anyways, but can't mount R/W.
Any other ideas?
oifi said:
what about flashing .17, root it, install ota rootkeeper, update and recover root?
just don't flash a custom recovery before updating via OTA
Click to expand...
Click to collapse
The is worked for me! Thanks
Gr8Danes said:
Ok, would you be able to guide me through the same? I have the same problem. No recovery and no root after .21 update.
I checked my system/xbin and I have su in there. Also in system/bin. I tried using root explorer to copy it over anyways, but can't mount R/W.
Any other ideas?
Click to expand...
Click to collapse
Nevermind
Related
Hi i just update to 2.3.4 and try to root it and work fine with me
Download this file and move it to your NS
http://www.mediafire.com/?0a4abln7x3gjgrv
after your flash the recovery then ..
On your phone, use the volume key to highlight "recovery". Press power to boot into recovery.
in the recovery screen, select mounts and storage
mount /system
mount /data
go back, and choose install zip from sd card
choose "choose zip from sd card"
pick the su package zip file you copied over earlier
choose Yes
when done, reboot.
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
it is for the i9023??
So after I flash 2.3.4 update, all I have to do is reboot and flash SuperUser again, and then Nexus S is re-rooted again?? Thanks!
amjad_2020 said:
Hi i just update to 2.3.4 and try to root it and work fine with me
Click to expand...
Click to collapse
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
I have a custom kernel. How do I Install 2.3.4
Sent from my Nexus S using XDA App
italia0101 said:
I have a custom kernel. How do I Install 2.3.4
Click to expand...
Click to collapse
You have to go back to stock GRI40, i.e. with a Nandroid restore?! But this will be the correct thread for you: http://forum.xda-developers.com/showthread.php?t=1055591&page=12
kevin_ngckk said:
Thanks ,i will try it how is the battery life?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
hehe how on earth can someone provide real feedback on battery life 2 seconds after installation?
Thanks for sharing, I'll wait for Team Douche to implement this on CM7.
Trouble
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
smlmn said:
Hi guys
I have some problems with root on 2.3.4
Probably I can not have any permissions for programms, such as ShootMe (for examle). Do you?
Click to expand...
Click to collapse
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
jungbum said:
That probably means your phone is no longer rooted. Download 'Root Checker' from the Market to check, but if you installed 2.3.4 ROM, your phone should be un-rooted though.
Click to expand...
Click to collapse
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
Yes, same here SuperUser ist still available, but without any function
on nexus s 9023 ??
what about it ?
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
jamallj said:
maybe try to download busybox from market and apply busybox.. then the system will be rooted properly..
Click to expand...
Click to collapse
No sorry. It's not possible to install busybox without root
smlmn said:
I've already install this zip su-2.3.6.1-ef-signed.zip for rooting after update
In my app organizer I can see Superuser, but Root Checker also said me that I dont have root
Click to expand...
Click to collapse
That means you're not rooted.. you have to root again.
bolabola118 said:
That means you're not rooted.. you have to root again.
Click to expand...
Click to collapse
I've tried to reroot again and totally get result
But I also done that:
!Once you are in recovery mode, select the relevent mounts and storage by Mount / System and Mount / data.
(I can not post links)
Thx
Handymeister said:
Sorry, but how can I get the custom recovery back? With stock recovery I can't flash this file
Click to expand...
Click to collapse
Same situation/problem
For those stock rooted but bootloader locked 2.3.3 users that previously rooting using CWM recovery to update and superuser root method.
You can root the same way...but save the trouble of fastboot recovery step via PC which novice users could be stuck on getting fastboot usb driver to work properly.
0) Just installed ROM Manager (From Market) into your phone
1) Store both 2.3.4 update.zip and SuperUser.zip into SDCard
2) Run ROM Manager
3) Activate CWM Recovery
=> Make sure recovery is installed succesfully..check ROM Manager screen which tell whether the installation is successfully done.
4) Reboot recovery from ROM Manager App
5) Follow thread #1 on the rest
6) After applying update.zip..do not reboot...do a system mount from CWM Recovery then apply SuperUser.zip ..after completing all steps..do a reboot..
Voila your 2.3.4 is installed and rooted..
Thanks, but this way comes to late for me and some other users. We've flashed the update without rooting.
And now we need another way for root ...
Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help
Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!
FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.
I know it's a bit early, but does one exist yet?
Just flashed from rooted/stock 4.1.2 to 4.2 and have seemed to lost root access. I don't really NEED it, but would like to install my Titanium backups asap. It's also worth noting that the flash took me from TWRP back to stock recovery (andy with red exclamation mark?)
Thanks in advance!
Flash TWRP, then flash SuperSU
See post #5 and #11 in thread below:
http://forum.xda-developers.com/showthread.php?t=1989351&page=1
asimons81 said:
I know it's a bit early, but does one exist yet?
Just flashed from rooted/stock 4.1.2 to 4.2 and have seemed to lost root access. I don't really NEED it, but would like to install my Titanium backups asap. It's also worth noting that the flash took me from TWRP back to stock recovery (andy with red exclamation mark?)
Thanks in advance!
Click to expand...
Click to collapse
It's a Nexus device. You root it the same way you did last time.
It would be noteworthy if it didn't flash you back to stock recovery. That it did is expected.
Sent from my Nexus 7 using Tapatalk 2
Next time use OTA Rootkeeper before you update to backup and to restore the root after update
others are reporting wugfresh's kit is still working in the thread in general
NeoMagus said:
Next time use OTA Rootkeeper before you update to backup and to restore the root after update
others are reporting wugfresh's kit is still working in the thread in general
Click to expand...
Click to collapse
I did, didn't work for me!
PromaneX said:
I did, didn't work for me!
Click to expand...
Click to collapse
What didn't, Rootkeeper or Wugfresh? I can't confirm the toolkit since I don't use it myself just going off of what is being said over in General.
If you are talking about Rootkeeper you have to go into the program BEFORE updating and backup the root first, then after the update you go back in and restore it.. if it didn't work, it was user error, not once has it failed to restore for me on several devices, and others have confirmed it still working in the general thread.
eager27 said:
Rootkeeper worked for me. Root fully maintained after update.
Click to expand...
Click to collapse
just install a custom recovery - cwm or twrp following the instructions in the android development part of forums and then install the supersu/superuser zip from there
I managed to have root access on 4.2 by using Nexus Root Toolkit. Set the device type to "Nakasi: Android *.*.* Any Build"
Hi guys. I have a small question and maybe a problem. I have Nexus 4 rooted with unlocked boot loader, and TWRP installed on it. And as I think with stock rom, because only done everything to root, but nothing else.
Now I have a problem: phone offering to update to 4.3. I press update. It updating and restarting, but after restart it loads TWRP. And what should I do next to finish update? Because I don't know how to make it finish updating with TWRP? What should I do with TWRP to do so? I will be very thankful for any help. Because twice was making update, but still on 4.2.2.
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
You can actually OTA with TWRP.. The device should load into TWRP and complete the update. After the update you will lose TWRP and root
Rizy7 said:
You can actually OTA with TWRP.. The device should load into TWRP and complete the update. After the update you will lose TWRP and root
Click to expand...
Click to collapse
I have seen this in 4.2.2 but not on 4.3. Could you please elaborate a bit more? How did you accomplish this with all these new security policies in 4.3? Thanks.
Mercado_Negro said:
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
Click to expand...
Click to collapse
This is incorrect. The best way to update is download the ota zip from here http://forum.xda-developers.com/showthread.php?t=2145848
Go to twrp recovery flash the ota zip then SU zip v1.51 reboot done. Now you got 4.3 with root and you won't lose your recovery
From my BLACKED OUT N4
spaceman860 said:
This is incorrect. The best way to update is download the ota zip from here http://forum.xda-developers.com/showthread.php?t=2145848
Go to twrp recovery flash the ota zip then SU zip v1.51 reboot done. Now you got 4.3 with root and you won't lose your recovery
From my BLACKED OUT N4
Click to expand...
Click to collapse
Sorry if it sounded incorrect to you but what you just suggested, although it works, it is not an OTA update per definition as far as I know. Please correct me if I'm wrong.
Mercado_Negro said:
Sorry if it sounded incorrect to you but what you just suggested, although it works, it is not an OTA update per definition as far as I know. Please correct me if I'm wrong.
Click to expand...
Click to collapse
When you get the notification saying there is a update on your phone you select it and it downloads flashes the ota zip. What I said is the same thing except you download it and flash it your self and by doing it this way you can flash the SU zip at the same time and not lose root or recovery.
From my BLACKED OUT N4
spaceman860 said:
When you get the notification saying there is a update on your phone you select it and it downloads flashes the ota zip. What I said is the same thing except you download it and flash it your self and by doing it this way you can flash the SU zip at the same time and not lose root or recovery.
From my BLACKED OUT N4
Click to expand...
Click to collapse
Thanks, your post above made me read that thread you linked and while it works, it's not a real OTA (notification from Google or OEMs), but let's not fall into semantics here, the thing is it works and does the job pretty much like a real OTA. Thanks again, I learned (and downloaded) something new today
Mercado_Negro said:
Thanks, your post above made me read that thread you linked and while it works, it's not a real OTA (notification from Google or OEMs), but let's not fall into semantics here, the thing is it works and does the job pretty much like a real OTA. Thanks again, I learned (and downloaded) something new today
Click to expand...
Click to collapse
The zip in the link is from Google. When someone got the notification on there phone they posted the link to the zip it would be the same file if you received it on your phone
From my BLACKED OUT N4
spaceman860 said:
The zip in the link is from Google. When someone got the notification on there phone they posted the link to the zip it would be the same file if you received it on your phone
From my BLACKED OUT N4
Click to expand...
Click to collapse
I know my friend I'm just trying to say that the affirmation "yes, you can update via OTA using a custom recovery" is not valid for someone getting the notification which is the common scenario for most people. Anyways, it's all good :thumbsup:
Mercado_Negro said:
You need to flash the stock recovery because you can't update via OTA with a custom recovery.
Click to expand...
Click to collapse
If I flash the stick recovery will I lose any data such as pics n vids?
rabidrotty said:
If I flash the stick recovery will I lose any data such as pics n vids?
Click to expand...
Click to collapse
No, you won't.
Mercado_Negro said:
No, you won't.
Click to expand...
Click to collapse
Awessome thanks bud. It's been awhile and I forgot if it did or not. You rock.
Hello,i got a new phone and i immideatly wanted to root it beacuse of blootware etc. open uped odin and downloaded cf-auto root.tar for THIS phone and flashed it,pass showed up got the super su and i get into super su and it asks for me to update the binary,ok nothing to suprising but it says it didnt flash and i should reebot reeboted,tryed again nothing (yes i did try several cf-auto root.tar files to download)
I rooted with CF-Root and I can tell you that it is working like a charm!! There are two methods to update the binary: letting SuperSU install it on \system\something or flash it trought the recovery. Try both methods and let me know of it worked.
Good luck
Root your dev with Kingroot.. I rooted my phone with this apk and its so easy and fast
Enry997S3 said:
Root your dev with Kingroot.. I rooted my phone with this apk and its so easy and fast
Click to expand...
Click to collapse
With Kingroot you need to stay stick to the disgusting KingoUser app, unless ypu are lucky to get super-sume to work on your phone.
Just my opinion
xSuperMegaPenizx said:
I rooted with CF-Root and I can tell you that it is working like a charm!! There are two methods to update the binary: letting SuperSU install it on \system\something or flash it trought the recovery. Try both methods and let me know of it worked.
Good luck
Click to expand...
Click to collapse
I think it has problems because i already installed kingroot and in cwm on reboot it tries to fix it,Kingroot blocks it somehow :/
Enry997S3 said:
Root your dev with Kingroot.. I rooted my phone with this apk and its so easy and fast
Click to expand...
Click to collapse
I already have that but it isnt a full root,ex gamekiller wont work because i dont have full root access
Vutraman said:
I already have that but it isnt a full root,ex gamekiller wont work because i dont have full root access
Click to expand...
Click to collapse
That's why you should root with CF-ROOT. Remove root on the KingoUser app and then root using the Chainfire CF-ROOT.
Hopefuly your problem will be solved
xSuperMegaPenizx said:
That's why you should root with CF-ROOT. Remove root on the KingoUser app and then root using the Chainfire CF-ROOT.
Hopefuly your problem will be solved
Click to expand...
Click to collapse
i tried but SuperSu doesn't appear but i see its rooted
Vutraman said:
i tried but SuperSu doesn't appear but i see its rooted
Click to expand...
Click to collapse
Then just download the SuperSU from the Play Store and I think you are good to go!! If it fails to update the binary, just choose the recovery update option and I think you're good to go.
Good luck
xSuperMegaPenizx said:
Then just download the SuperSU from the Play Store and I think you are good to go!! If it fails to update the binary, just choose the recovery update option and I think you're good to go.
Good luck
Click to expand...
Click to collapse
Trying it right now will post updates to ya quick
Update:
i got into super su and it tells me i need to install it etc. and then i select cwm option and it doesnt boot down i booted it down myself and when i got into recovery nothing began installing,am i doing something wrong,when i go to reboot it says like no and yes and by yes -Fix root /system/xbin/su
Vutraman said:
Trying it right now will post updates to ya quick
Update:
i got into super su and it tells me i need to install it etc. and then i select cwm option and it doesnt boot down i booted it down myself and when i got into recovery nothing began installing,am i doing something wrong,when i go to reboot it says like no and yes and by yes -Fix root /system/xbin/su
Click to expand...
Click to collapse
You must click on yes, so you won't lose root everytime you reboot.
Hope it's working
xSuperMegaPenizx said:
You must click on yes, so you won't lose root everytime you reboot.
Hope it's working
Click to expand...
Click to collapse
i click yes everytime and it just reboots and i still need to udate the binary,i tried installing a binary zip from cwm for super su and that doesnt work either
Thanks for the help and quick replies
Vutraman said:
i click yes everytime and it just reboots and i still need to udate the binary,i tried installing a binary zip from cwm for super su and that doesnt work either
Thanks for the help and quick replies
Click to expand...
Click to collapse
Just try this guide: http://forum.xda-developers.com/showthread.php?t=2906840
Don't forget to thanks @Rox if it worked
xSuperMegaPenizx said:
Just try this guide: http://forum.xda-developers.com/showthread.php?t=2906840
Don't forget to thanks @Rox if it worked
Click to expand...
Click to collapse
Will do thanks
Edit: i did this way already and it didnt work
Do a factory reset from the recovery and then try again
Good luck
xSuperMegaPenizx said:
Do a factory reset from the recovery and then try again
Good luck
Click to expand...
Click to collapse
Will try thanks just need to back it up