Achieved today. Rooted with KingRoot 4.9.0.142. Took 3 times but root is achieved!
finally!! thanks for the heads up.
I think mine finally worked on the 6th attempt
so just keep going until it works!!!!
SoreGums said:
finally!! thanks for the heads up.
I think mine finally worked on the 6th attempt
so just keep going until it works!!!!
Click to expand...
Click to collapse
The down side is that you won't be able to get any OTA updates. The process would be to revert to 1.5, then let all the updates apply and then repeat the root process.
tomlogan1 said:
The down side is that you won't be able to get any OTA updates. The process would be to revert to 1.5, then let all the updates apply and then repeat the root process.
Click to expand...
Click to collapse
I dont have this problem (dont tested test release) just unroot in supersu. Maybe your install recovery.sh isnt original?
Gesendet von meinem LG-D855 mit Tapatalk
tschmid said:
I dont have this problem (dont tested test release) just unroot in supersu. Maybe your install recovery.sh isnt original?
Gesendet von meinem LG-D855 mit Tapatalk
Click to expand...
Click to collapse
Have not messed with the recovery.sh unlesss Kingo Root causes that. I believe that there is a thread I saw somewhere to replace Kingo with supersu. Will try to see if that will help.
Done f*cking with this
tomlogan1 said:
Have not messed with the recovery.sh unlesss Kingo Root causes that. I believe that there is a thread I saw somewhere to replace Kingo with supersu. Will try to see if that will help.
Click to expand...
Click to collapse
Found an app that was supposed to add supersu instead of KingoRoot. Link is http://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/. Tried the option to use super su me pro.
App said it worked but went into an extended boot loop. Had to revert, again, to 1.5 and now coming back to current. Going to stay unrooted for the foreseeable future.
Plain android is SO much better.
tomlogan1 said:
Found an app that was supposed to add supersu instead of KingoRoot. Link is http://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/. Tried the option to use super su me pro.
App said it worked but went into an extended boot loop. Had to revert, again, to 1.5 and now coming back to current. Going to stay unrooted for the foreseeable future.
Plain android is SO much better.
Click to expand...
Click to collapse
How does one revert to 1.5? I'm a noob but I just wanted to root and have a backup plan in case it goes south. Thanks!
Also, will Kingoroot work on 2.0.305
Madethisjustnow said:
How does one revert to 1.5? I'm a noob but I just wanted to root and have a backup plan in case it goes south. Thanks!
Also, will Kingoroot work on 2.0.305
Click to expand...
Click to collapse
Try cwm Recovery and flash supersu. Theres also a flashable 2.0.305 in this forum
Gesendet von meinem Nexus 6P mit Tapatalk
tschmid said:
Try cwm Recovery and flash supersu. Theres also a flashable 2.0.305 in this forum
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
The Cyanogen recovery also works well. Have verified that using Supersu unlike other exploits allows you to unroot, upgrade and then reroot. Much better than King Root or Kingo root.
tomlogan1 said:
The Cyanogen recovery also works well. Have verified that using Supersu unlike other exploits allows you to unroot, upgrade and then reroot. Much better than King Root or Kingo root.
Click to expand...
Click to collapse
Btw I've made some progress with cm-13.0 hope i can upload soon a Test Version ?
Gesendet von meinem Nexus 6P mit Tapatalk
tschmid said:
Btw I've made some progress with cm-13.0 hope i can upload soon a Test Version
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
Wonderful! Let me know if you need someone to test. Happy to help and hope to be off of Remix as we are probably not going to get any real support from Jide.
i agree with tomlogan -- i'd definitely love to give CM a try! thank you for your work!
tschmid said:
Try cwm Recovery and flash supersu. Theres also a flashable 2.0.305 in this forum
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
thanks for responding! do you think you could make a step by step tutorial of how to use cwm on the remix? i apologize if that is asking too much. I've only used towelroot on my (4.4) phone a while ago. thanks in advance!
Madethisjustnow said:
thanks for responding! do you think you could make a step by step tutorial of how to use cwm on the remix? i apologize if that is asking too much. I've only used towelroot on my (4.4) phone a while ago. thanks in advance!
Click to expand...
Click to collapse
In the thread CM13 there was a zip of cwm recovery. But the link is availble further in the thread it's also here
Using fastboot you flash it to your tablet (for example fastboot flash recovery recoveryxxxxx.zip )
Reboot bootloader, and flash superuser from chainfire's site.
Madethisjustnow said:
thanks for responding! do you think you could make a step by step tutorial of how to use cwm on the remix? i apologize if that is asking too much. I've only used towelroot on my (4.4) phone a while ago. thanks in advance!
Click to expand...
Click to collapse
I presume you already have enabled developer options under settings. You should also have ADB installed. Here is my version:
Download SuperSu from the market. Option - Pay the author - worth it to keep good software coming.
Connect your tablet via USB.
Have the recovery (cwm or cyanogen) located in your ADB directory.
Open a command prompt (Windows) For Linux, ask someone else.
Move to your ADB directory and type ADB Devices. Hit Enter.
If you are OK with ADB you should get a serial number as verification.
Then enter ADB reboot bootloader. Hit enter.
Then enter fastboot boot (recovery name). Hit enter.
This will take a few minutes. If all is OK you should have a screen on your tablet with an option to install upgrade etc.
Select Supersu and hit enter.
If you reboot now, you will be rooted, but with the stock recovery. If you are OK with that reboot, otherwise you will need to flash the recovery (cwm or cyanogen) with a command fastboot flash recovery (recovery name).
This worked for me. Good luck.
Cyanogen Mod Recovery
tomlogan1 said:
I presume you already have enabled developer options under settings. You should also have ADB installed. Here is my version:
Download SuperSu from the market. Option - Pay the author - worth it to keep good software coming.
Connect your tablet via USB.
Have the recovery (cwm or cyanogen) located in your ADB directory.
Open a command prompt (Windows) For Linux, ask someone else.
Move to your ADB directory and type ADB Devices. Hit Enter.
If you are OK with ADB you should get a serial number as verification.
Then enter ADB reboot bootloader. Hit enter.
Then enter fastboot boot (recovery name). Hit enter.
This will take a few minutes. If all is OK you should have a screen on your tablet with an option to install upgrade etc.
Select Supersu and hit enter.
If you reboot now, you will be rooted, but with the stock recovery. If you are OK with that reboot, otherwise you will need to flash the recovery (cwm or cyanogen) with a command fastboot flash recovery (recovery name).
This worked for me. Good luck.
Click to expand...
Click to collapse
Courtesy of Herr Schmidt. I did not make this recovery, but it is my every day recovery.
Thank you, Thomas.
Related
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.
Hey all,
So I've managed to upgrade to FW 4, Doom's latest kernel, & Doom's autoroot also. Thanks Doom
I still can't seem to get root working. When I go in to Superuser to try to update, I get the following:
su-2.3.1-bin-signed.zip
reboot into recovery and flash it
I can't reboot into recovery (not sw cuz it's not rooted, hitting back key when powering on ignores me).
Anyone else know what I could try?
If you flashed to 4.0 first, then autoroot, then use kernel you will keep root and data.
Sent from my Xperia PLAY R800i using XDA App
Cat_On_Droid said:
If you flashed to 4.0 first, then autoroot, then use kernel you will keep root and data.
Sent from my Xperia PLAY R800i using XDA App
Click to expand...
Click to collapse
Logseman told me to flash 4, kernel, then autoroot. Is this the wrong order? Have I lost my chance to root until Doom releases a new kernel?
I kept my data ok, just lost root... which is pants cuz the bloatware needs wiped before my sanity does :-/
Rixter757 said:
Logseman told me to flash 4, kernel, then autoroot. Is this the wrong order? Have I lost my chance to root until Doom releases a new kernel?
I kept my data ok, just lost root... which is pants cuz the bloatware needs wiped before my sanity does :-/
Click to expand...
Click to collapse
If you have superuser you are rooted, if your using doomlords kernel there is no need to auto root as it comes with root. you dont need to update the app just the binaries, but you have the latest version with doomlords kernel so an update is not needed
worst comes to the worst, connect your device to flashtool and hit root
AndroHero said:
If you have superuser you are rooted, if your using doomlords kernel there is no need to auto root as it comes with root. you dont need to update the app just the binaries, but you have the latest version with doomlords kernel so an update is not needed
worst comes to the worst, connect your device to flashtool and hit root
Click to expand...
Click to collapse
Thanks for taking the time to reply.
I agree, def still rooted because i can delete sys apps through root explorer. I can't get Titanium to run - it reports I'm not rooted. Their "problems" link me to update Superuser but it compains re my 1st post that it can't update.
I uninstalled su, new install is 2.3.6.3 but it still refuses the update. Why I can't get into safe mode by hitting the back key on boot is strange too.
Don't know how to run Root from Flashtool, it's greyed out & sounds like I might lose data?
More idea's welcome
Rixter757 said:
Thanks for taking the time to reply.
I agree, def still rooted because i can delete sys apps through root explorer. I can't get Titanium to run - it reports I'm not rooted. Their "problems" link me to update Superuser but it compains re my 1st post that it can't update.
I uninstalled su, new install is 2.3.6.3 but it still refuses the update. Why I can't get into safe mode by hitting the back key on boot is strange too.
Don't know how to run Root from Flashtool, it's greyed out & sounds like I might lose data?
More idea's welcome
Click to expand...
Click to collapse
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
AndroHero said:
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
Click to expand...
Click to collapse
Works like a charm FW 4.0.A.2.368_World successfully rooted. Thank you and all those dev's & guides that made it possible.
AndroHero said:
Go to this thread.....
http://forum.xda-developers.com/showthread.php?t=1130639
Download the recoveryPLAY.img
and
download rootxperia.zip from the botton of the OP
Copy the rootxperia.zip to the root of your SD Card
Put your device in fastboot mode and connect to pc
type in "fastboot boot recoveryPLAY.img"
DO NOT FLASH IT. NOTICE THE BOOT COMMAND NOT FLASH
When recovery pops up flash the .zip and reboot
done
Click to expand...
Click to collapse
You Sir, are an absolute legend
Worked perfectly, I'm good to go. Thanks very much for your patience.
Thanks also to all the Devs for their brilliant work
azuell said:
Works like a charm FW 4.0.A.2.368_World successfully rooted. Thank you and all those dev's & guides that made it possible.
Click to expand...
Click to collapse
Rixter757 said:
You Sir, are an absolute legend
Worked perfectly, I'm good to go. Thanks very much for your patience.
Thanks also to all the Devs for their brilliant work
Click to expand...
Click to collapse
WooHooo glad your sorted
Hi
I will get my N7 in Calender week 37, this is the week starting with the 10. September.
Now I have some questions.
1. I want to root it, like my arc S. I also know how to root. Unlock the BL, flash CWM using fastboot flash recovery recovery.img, then flash SuperSU Package via CWM. Is this ok? Somewhere i read, i have to delete any file in /system. Is this right?
2. If my BL is unlocked and a custon recovery is flashed, will i still be able to update OTA?
3. If my Bootloader is unlocked, a lock will be shown under the Kernel logo. If I relock the Bootloader using fastboot oem relock, will the lock still be there?
Thank you!
Gesendet von meinem Arc S mit Tapatalk 2
Please answer!
Gesendet von meinem Arc S mit Tapatalk 2
Comeon, please answer.
Gesendet von meinem Arc S mit Tapatalk 2
papayayoghurt said:
1. I want to root it, like my arc S. I also know how to root. Unlock the BL, flash CWM using fastboot flash recovery recovery.img, then flash SuperSU Package via CWM. Is this ok? Somewhere i read, i have to delete any file in /system. Is this right?
Click to expand...
Click to collapse
You should run CWM at least once after flashing it; it should automatically correct the ROM-wants-to-overwrite-recovery problem so that you don't have to delete some /system file. So after flashing, you would do
Code:
fastboot boot recovery.img
(I'm assuming from your sample instructions that you've renamed the recovery to "recovery.img". If not, replace it with whatever the file name is.)
Note: I'm basing this suggestion on paulobrien's earlier advice (which was for an outdated version of CWM). I'm not actually an expert at this stuff.
papayayoghurt said:
2. If my BL is unlocked and a custon recovery is flashed, will i still be able to update OTA?
Click to expand...
Click to collapse
I think so (don't trust me on this) but I'm also pretty sure it'll remove root. I recommend just going fullon with custom ROM so you don't have to worry about this.
papayayoghurt said:
3. If my Bootloader is unlocked, a lock will be shown under the Kernel logo. If I relock the Bootloader using fastboot oem relock, will the lock still be there?
Click to expand...
Click to collapse
No.
papayayoghurt said:
Hi
I will get my N7 in Calender week 37, this is the week starting with the 10. September.
Now I have some questions.
1. I want to root it, like my arc S. I also know how to root. Unlock the BL, flash CWM using fastboot flash recovery recovery.img, then flash SuperSU Package via CWM. Is this ok? Somewhere i read, i have to delete any file in /system. Is this right?
2. If my BL is unlocked and a custon recovery is flashed, will i still be able to update OTA?
3. If my Bootloader is unlocked, a lock will be shown under the Kernel logo. If I relock the Bootloader using fastboot oem relock, will the lock still be there?
Thank you!
Click to expand...
Click to collapse
Before stating some answers, please don't continually bump your thread, it was a total of 5 hours... A couple of days, maybe... We have lives...
Now here is my answers to your questions:
1. This is OK, you dont need to touch anything in /system
2. Yes, and no. They will appear, but to keep it as is, may be a bit more involved.
3. The lock will be gone, it will look like nothing was different.
For points 1 and 2, I referred to http://www.nexustablets.net/forum/n...-7-windows-keep-root-through-ota-updates.html. It has a pretty good walkthrough on how to do things.
papayayoghurt said:
Comeon, please answer.
Gesendet von meinem Arc S mit Tapatalk 2
Click to expand...
Click to collapse
Dude - we don't work for you - you can't expect answers instantly!! Man, is that annoying! Give people time - they will answer your questions - or if you are in such a hurry for answers (as apparently you are), do some searching on your own! Geez...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
thebobp said:
You should run CWM at least once after flashing it; it should automatically correct the ROM-wants-to-overwrite-recovery problem so that you don't have to delete some /system file. So after flashing, you would do
Code:
fastboot boot recovery.img
(I'm assuming from your sample instructions that you've renamed the recovery to "recovery.img". If not, replace it with whatever the file name is.)
Click to expand...
Click to collapse
Do i have to do fastboot boot recovery.img before or after fastboot flash recovery recovery.img?
But thanks for the answers and sorry for pushing.
EDIT: the link of mouse_man solved all my questions. Thanks!
Gesendet von meinem Arc S mit Tapatalk 2
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?
Anyone brave enough to try the new PA release?
http://get.aospa.co/official/scorpion_windy
Gesendet von meinem Xperia Z3 Tablet Compact Wifi mit Tapatalk
hmmmmm, you have to unlock the bootloader, it makes me not want to try.
I tried the version for scorpion but I am unable to setup the device as the keyboard always crashes during setup. and after that the device ends up in a bootloop, unable to get into recovery.
I would try if not for the bootloader. But also, when I get to the page it's empty. Did they pull it?
The page doesn't actually load any info for the ROM? Was it there but it's been taken down?
andyrtr said:
Anyone brave enough to try the new PA release?
http://get.aospa.co/official/scorpion_windy
Gesendet von meinem Xperia Z3 Tablet Compact Wifi mit Tapatalk
Click to expand...
Click to collapse
It's back up now, pretty stable, everything seems fine but I couldn't get SuperSU to work just Xposed.
NTRNSTR said:
It's back up now, pretty stable, everything seems fine but I couldn't get SuperSU to work just Xposed.
Click to expand...
Click to collapse
So this PA rom works on both Z3TC Wifi & LTE
AOSPA works like a charm on my SGP611. I have not encountered any bug so far. It is so nice to have a near Android stock experience.
Only problem I have is that I have lost recovery in the process. Anyone knows how to set TWRP or CM on Android 6.0.2 ? I still have root for the record.
REundo said:
So this PA rom works on both Z3TC Wifi & LTE
Click to expand...
Click to collapse
I think there's a build for both but I testsed it on the Wifi model.
---------- Post added at 04:49 PM ---------- Previous post was at 04:46 PM ----------
augustinleman said:
AOSPA works like a charm on my SGP611. I have not encountered any bug so far. It is so nice to have a near Android stock experience.
Only problem I have is that I have lost recovery in the process. Anyone knows how to set TWRP or CM on Android 6.0.2 ? I still have root for the record.
Click to expand...
Click to collapse
I'm facing a lot of random reboots and couldn't get root working, could you tell me how you flashed it and which packages you used.
One way I've found to get a recovery is to connect it in fastbood mode and flash the official TWRPthen boot into it, but you have to reboot back to fastboot and flash the boot.img from the PA zip when you're done.
NTRNSTR said:
I think there's a build for both but I testsed it on the Wifi model.
Click to expand...
Click to collapse
Oh! thank you!
NTRNSTR said:
I'm facing a lot of random reboots and couldn't get root working, could you tell me how you flashed it and which packages you used.
One way I've found to get a recovery is to connect it in fastbood mode and flash the official TWRPthen boot into it, but you have to reboot back to fastboot and flash the boot.img from the PA zip when you're done.
Click to expand...
Click to collapse
I did flash the recovery image, SuperSU v2.76 and Gapps from TWRP (3.0.2.0 official) recovery and then wiped cache and dalvik. I realize I forgot to perform a factory reset before the flash but I do not think it is a good thing and that it is related in any way.
As I had rooted my device through KingRoot, I did run SuperSu Me that you can find on the PlayStore to uninstall Kingroot while maintaining root.
I will give a try to your technique. Thanks
augustinleman said:
I did flash the recovery image, SuperSU v2.76 and Gapps from TWRP (3.0.2.0 official) recovery and then wiped cache and dalvik. I realize I forgot to perform a factory reset before the flash but I do not think it is a good thing and that it is related in any way.
As I had rooted my device through KingRoot, I did run SuperSu Me that you can find on the PlayStore to uninstall Kingroot while maintaining root.
I will give a try to your technique. Thanks
Click to expand...
Click to collapse
Did you use banks or opengapps?
I'll try reflashing it your way hopefully it'll work.
NTRNSTR said:
Did you use banks or opengapps?
I'll try reflashing it your way hopefully it'll work.
Click to expand...
Click to collapse
I did use open gapps (aroma version). To be fair, on top of PA, SuperSU and Gapps, I did flash XZDualKernel and XZDRecovery but I do not think it was necessary.
Got it mostly working by:
Booting into official TWRP.
Flashing PA.
Flashing opengapps nano.
Flashing regular xposed
Flashing systemless SuperSU using the SuperSU aroma installer.
(Doing all that before first boot.)
Everything worked except that some apps couldn't get root access while others such as titanium were fine.
Oh well back to stock I guess
NTRNSTR said:
Got it mostly working by:
Booting into official TWRP.
Flashing PA.
Flashing opengapps nano.
Flashing regular xposed
Flashing systemless SuperSU using the SuperSU aroma installer.
(Doing all that before first boot.)
Everything worked except that some apps couldn't get root access while others such as titanium were fine.
Oh well back to stock I guess
Click to expand...
Click to collapse
Okay I just flash aospa scorpion on my SPG21 (LTE) via TWRP
everything work just fine except camera not working & IMEI is missing . im sure i flash the scorpion and not scorpion_windy. Good thing is i have backups of my lovely cm12 . Anyone know how to fix imei on aospa