I made a dumb mistake. Sometime back i had mistakenly deleted the contents of the sdcard after voodoo rootkeeper su backup. Forgot about the su backup!
Updated the latest update, without backing up again.
Rootkeeper shows that su copy is available but doesn't restore.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried cold booting, multiple restarts, everything in vain.
Question is, can I restore root from the backup of other users in the forum? Or is it device specific?
Somebody care to upload the contents of the folder if it doesn't give away any personal data?
Thanks.
Sent from my Asus TF300T
Tell us more, please.
Are you on JB or ICS ?
Have you tried to cheched "device rooted" and "root permission granted"
and finally click on "Restore root"
philos64 said:
Tell us more, please.
Are you on JB or ICS ?
Click to expand...
Click to collapse
I am currently in JB (v10.4.2.13).
Tablet is not unlocked
Vodoo OTA Rootkeeper restored fine when I updated from ICS(9.4.3.30) to JB (10.4.2.9).
The check-boxes will be checked by the app not manually AFAIK.
Anyhow gave it a try, not clickable
Stupid of me not to backup before updating
It's possible to have backup of rootkeeper?
I have solved so, removed supersu, instal superuser from market.
Restore root from rootkeeper and all ok.
Remove superuser and reinstall supersu.
Now I have root access.
Inviato dal mio ASUS Transformer Pad TF300T con Tapatalk 2
Root Achieved
Solved the problem.
Followed the steps in the thread posted here
Steps:
Most of the commands are copy-paste from the thread just modified for this specific problem (I do not take credit for these steps).
Download View attachment su.zip from this post (thanks to calisro)
Extract the contents to a folder.
Start a cmd window in that folder and logon to adb
In adb shell type
Code:
/system/usr/we-need-root/su-backup
(check the file availability in that folder and the file name and correct the command accordingly)
Confirm whether you have root. The adb shell prompt should be # not $, also can be confirmed by typing id and should echo something like this "uid=0(root) gid=0(root)"
Remount system as RW:
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
Code:
adb push c:\<some path>\su /sdcard/
Then copy it to /system/bin from the adb session where you got root.
Code:
cat /sdcard/su > /system/bin/su
Change permissions for SU
Code:
chmod 6755 /system/bin/su
Download superuser (NOT SUPERSU) from play store if you do not have it already.
Force superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
congrats. your now re-rooted.
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
k1chy said:
Solved the problem.
Followed the steps in the thread posted here
Steps:
Most of the commands are copy-paste from the thread just modified for this specific problem (I do not take credit for these steps).
Download View attachment 1338410 from this post (thanks to calisro)
Extract the contents to a folder.
Start a cmd window in that folder and logon to adb
In adb shell type
Code:
/system/usr/we-need-root/su-backup
(check the file availability in that folder and the file name and correct the command accordingly)
Confirm whether you have root. The adb shell prompt should be # not $, also can be confirmed by typing id and should echo something like this "uid=0(root) gid=0(root)"
Remount system as RW:
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
Code:
adb push c:\<some path>\su /sdcard/
Then copy it to /system/bin from the adb session where you got root.
Code:
cat /sdcard/su > /system/bin/su
Change permissions for SU
Code:
chmod 6755 /system/bin/su
Download superuser (NOT SUPERSU) from play store if you do not have it already.
Force superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
congrats. your now re-rooted.
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
Click to expand...
Click to collapse
It works fine.
Thank you k1chy & calisro
nevermind, figured out.
thanks for the tutorial
It will be nice if this was a sticky
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Thank you! The last OTA that my tablet took resulted in me not being able to restore root. OTA RootKeeper kept freezing up and doing nothing. This helped me in restoring root!
Thanks a million
k1chy said:
Think, this will solve the problem plaguing few people who could not restore root after latest OTA.
Thanks to calisro for his easy to understand steps (please rep him in the thread, if this helped you)
Click to expand...
Click to collapse
Thanks a million!!
Couldn't recover root on a Razr M after JB OTA - tried all of the exploits around the forums but NONE worked
- This, however, worked a treat!!! :victory:
Related
[7/13/2011]New method to get "temp-root"(root won't disappear until reboot!)
Sorry for poor English
This method is based on joel.bourquard's method,here is the orignal link:
http://forum.xda-developers.com/showthread.php?t=1151735
Thanks to joel.bourquard's.
I've tried almost all the method in xda And the newest perma-root caused that i can not install apps from computer..Today i found that link /data/bin/su to /system/bin/su and then root explorer works and i can delete apks easily..I shutdown my phone(fastboot enabled)and boot it twice,root still exists..That will be nice
Root Explorer 2.16, Titanium Backup 3.8.9.2 ,Setcpu 2.2.4 all tested,workds perfect
Requirements:
Original "out of the box" Sensation or EVO 3D (untested).
Android SDK tools ("adb" command) on a computer.
USB connection between computer and phone.
USB debugging enabled(Settings, Applications, Development
Initial (one-time) setup:
Extract Easy_Fre3vo_Bat.7z
Put all the files in the "Resource"folder" to User's folder(For example,My computer user's name is Jerry,so i put them into C:\Users\Jerry)
run cmd and input the following command
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
adb shell mount -oremount /dev/block/mmcblk0p22 /system
adb install Superuser.apk
adb shell chmod 06755 /data/bin/su
adb shell ln -s /data/bin/su /system/bin/su
After every reboot:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
adb shell mount -oremount /dev/block/mmcblk0p22 /system
adb shell chmod 06755 /data/bin/su
adb shell ln -s /data/bin/su /system/bin/su
And here is a bat(No need ADB from SDK)
Thanks to Wisefire
View attachment Easy_Fre3vo_Bat.7z
And here is some picture to see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now it is time to go to bed
Have fun!
Will try and report back. It's a shame eugene's version is so buggy.. It was working really great until the last few releases where it was deemed 'stable' but had the memory bug that prevented some apps like Root Explorer from running and the installation glitch
EDIT: Been using it. Don't know if there is any diff from the one you used the method from, but it definitely doesn't have the glitches in eugene's version so I will continue using this one for now.
Loses root just like the rest of them, thanks for you effort...
kartikb said:
Loses root just like the rest of them, thanks for you effort...
Click to expand...
Click to collapse
I don't mind losing root and re-enabling. It's the bugginess that crept in using other version that caused me some grief. Not meant as a complaint at all. Just reporting the issue. My bugs included wifi error, the negative values already reported and touch screen wonkiness that included inability to use the password touch screen pattern lock utility at all. Turning off rotation as a fix for the password touch screen utility fix did NOT work for me BTW. I ended up doing the factory reset.
kartikb said:
Loses root just like the rest of them, thanks for you effort...
Click to expand...
Click to collapse
After rooting it is 14 hours and i have shutdown－boot many times, root still existAnyway,htc will unlock our devices
next month
EDIT:If you have any error in the command window when using bat ,please reboot your phone and use adb to input command by yourself
Sent from my HTC Sensation Z710e using XDA App
Are you sure you have unchecked Fastboot?
Kid Poker said:
Are you sure you have unchecked Fastboot?
Click to expand...
Click to collapse
Of course fastboot enabled..And have you looked the title it said "temproot" Now there is no mothed to get permroot..
Sent from my HTC Sensation Z710e using XDA App
Using his method has anyone been able to get AdFree to work? No root options have this working [yet].
quailallstar said:
Using his method has anyone been able to get AdFree to work? No root options have this working [yet].
Click to expand...
Click to collapse
AdFree must reboot your phone then it will work..It needs permroot.. I am sad as well because of too much advertisement!
Sent from my HTC Sensation Z710e using XDA App
Use the apk hot reboot and do a hotreboot. Root should stick. Did for me.
Fails on second command.
Sent from my HTC Sensation Z710e using XDA Premium App
djmaz said:
Fails on second command.
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
fail in bat?
Sent from my HTC Sensation Z710e using XDA App
Appears to be okay right now...I'm running a Titanium restore at the moment.
One thing I did notice, as alluded to in the OP: if you've used some of the other Fre3vo offshoots before this one you likely will see a fail when trying this one out. I suspect it has to do with changes the other Fre3vo's make being incompatible with this latest?
At any rate, I did a factory restore and now this temp root process works, from what I've seen so far.
I'm currently live in China and I got the phone from here and I tried this method too. didn't work for me, it's because I have a asian one.
chesterr said:
I'm currently live in China and I got the phone from here and I tried this method too. didn't work for me, it's because I have a asian one.
Click to expand...
Click to collapse
I am asia sensation as well,matePlease reboot your phone and then use adb to get root.
Sent from my HTC Sensation Z710e using XDA App
First: I'd like to make it clear I am not claiming this process as my own. This method was created by p3droid over at the MyDroidWorld Forums. I am not a dev, just someone compiling information.
Second: This root method is originally intended for the Droid Bionic and I take no responsibility if this bricks your phone.
Third: This root was discovered by JRW 28 So give him some love with that thanks button.
If you are on 2.3.6:
Install the OTA and upgrade your phone to 2.3.6
Download the 2.3.6 root zip from HERE
Make sure you have the right drivers installed then connect your phone to your PC.
Unzip the file and then double-click "Click-To-Root.bat".
Refer to the trouble shooting step bleow the 2.3.5 method if you are unable to attain root!
If you are on 2.3.5:
Root: I used the Lazy One Click and it worked perfectly, others have had success with the full manual method.
I am a manual man, I don't use 1 clicks so I will post this the only way I know how...
Download the follow file: it contains the exploit, su, Superuser
Download exploit ---> Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
********************************
Windows Version
For the lazy I made you a 1-click ---> 1-click-exploit.zip
Click to expand...
Click to collapse
Original Thread on MyDroidWorld: http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072
Important for those using Oneclick:
1.Extract the files from 1-click_exploit.zip.
2.Enable USB debugging. Do so by going into your settings, then to applications, then to development.
3.Set your connection type to charge only. You can change your connection type through the notification bar once your are connected.
4.Make sure you go to Settings, Applications, and check Unknown sources if you haven't done so already.
5.Click runme.bat while your phone is connected. Be patient and let the program do it's thing. YOUR PHONE WILL REBOOT! Do not be alarmed as this is normal. Your phone should now be rooted.
Cheers!
If runme.bat hangs after daemeon starts:
1.First make sure you have USB Debugging, Unknown Sources, and Charge only connection enabled
2.If none of these options work, uninstall your drivers and download and install one of these:
Driver-wise:
Try this if on 32-bit:http://www.mediafire.com/?71c12qc4a1svqza
And this for 64-bit:http://www.mediafire.com/?ysphmaz131d3an9
Proof of Root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a terminal screen showing the Atrix 2 (Codenamed Edison, look it up if you must) accessing root.
Anyone else try?
I'll be uploading a terminal screen in a second accessing root.
Sent from my MB865 using XDA App
Yea I have it working and full SU Access. No wonder the computer doesnt have access to the phones internal memory it is by default set as r/o...Im gonna change it to R/W and see if that changes anything other than allowing R/W access. And after trying notta still only SD Card access like I thought, I assume there is some sorta setting we can edit though. At least that is my assumption. I used the One Click method Worked flawlessly on my device and Very Simple.
built in wifi tether
http://forum.xda-developers.com/showthread.php?t=1160452
this method also works for the Atrix 2
Thanks for the tip!
Sent from my MB865 using XDA App
malickie said:
Yea I have it working and full SU Access. No wonder the computer doesnt have access to the phones internal memory it is by default set as r/o...Im gonna change it to R/W and see if that changes anything other than allowing R/W access. And after trying notta still only SD Card access like I thought, I assume there is some sorta setting we can edit though. At least that is my assumption. I used the One Click method Worked flawlessly on my device and Very Simple.
Click to expand...
Click to collapse
How do you root the phone using the one click method? I've downloaded the zip and extracted it. Do I just connect my phone and then click on the runme.bat? When I connect my phone, any special instructions there or just connect it as if i was going to charge it, then enable usb debugging? Please clarify. Thanks.
Enable USB debugging. Then connect your phone to the computer. In the notification area, click on "USB connection" for more options. Click charge only.
Then double click on runme.bat
Follow instructions. Be patient while phone reboots. It will say (in the command prompt window) you have successfully rooted when it's all done.
It's schweet.
loderjm said:
Enable USB debugging. Then connect your phone to the computer. In the notification area, click on "USB connection" for more options. Click charge only.
Then double click on runme.bat
Follow instructions. Be patient while phone reboots. It will say (in the command prompt window) you have successfully rooted when it's all done.
It's schweet.
Click to expand...
Click to collapse
Thanks for clarifying, worked like a charm! Let the developing begin!!!!
yes it works!!! Thank you so much
Updated/clarified the oneclick method.
Sent from my MB865 using XDA App
So, what's the next step? Do we have to get the BL unlocked in order to get a Recovery installed or what?
Contact a admin and let him know you got some development so you'll get a thread
Sent from my MB860 using xda premium
Requesting this thread be moved -
http://forum.xda-developers.com/forumdisplay.php?f=1376
If you read at the end of my original post I document what I've tried. If your really adventurous you may want to try the bionic bootstrapper but it may brick your phone... I haven't tried that yet, though the similarities between the atrix2 and the bionic lead me to believe it may work.
Sent from my MB865 using XDA App
Calundle said:
Requesting this thread be moved -
http://forum.xda-developers.com/forumdisplay.php?f=1376
Click to expand...
Click to collapse
Thread Moved.
Yes i have tested and it works perfectly.
my only question is which CMW do we flash?
rinnycoop121 said:
Yes i have tested and it works perfectly.
my only question is which CMW do we flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1328434
Right now we don't have a CWM of our own to flash. There is a possibility of flashing the Bionics bootstrap recovery but we don't know what the circumstances are gonna be. Someone could result in a bricked A2, what we need is some development help right now
JRW 28 said:
Right now we don't have a CWM of our own to flash. There is a possibility of flashing the Bionics bootstrap recovery but we don't know what the circumstances are gonna be. Someone could result in a bricked A2, what we need is some development help right now
Click to expand...
Click to collapse
i have tried Bionic and Atrix 4G but no good.
wil lnot boot into recovery
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
ok just noticed something, upon running market been getting random restarts.
please i help i try unlock pin my tab without loss my data by android-sdk
my device
1- not rooted
2-have original rom Samsung
3- system recovery 3e , not install any costume recovery
i use this command
adb devices
adb shell
cd data/system
su
rm *.key
Click to expand...
Click to collapse
C:\>cd android-sdk
C:\android-sdk>cd platform-tools
C:\android-sdk\platform-tools>adb devices
List of devices attached
c16079a4137277f recovery
C:\android-sdk\platform-tools>adb shell
[email protected]:/ $ cd data/system
cd data/system
/system/bin/sh: cd: /data/system - No such file or directory
1|[email protected]:/ $
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please any help i need unlock my device without lost data
sorry for my bad english
Do this
adb devices
adb shell
cd data
cd system
rm passwork.key (for PIN and password)
rm gesture.key (for pattern)
dr.ketan said:
Do this
adb devices
adb shell
cd data
cd system
rm passwork.key (for PIN and password)
rm gesture.key (for pattern)
Click to expand...
Click to collapse
C:\android-sdk\platform-tools>adb devices
List of devices attached
c16079a4137277f recovery
C:\android-sdk\platform-tools>cd data
The system cannot find the path specified.
C:\android-sdk\platform-tools>adb shell
[email protected]:/ $ cd data
cd data
[email protected]:/data $ cd system
cd system
/system/bin/sh: cd: /data/system - No such file or directory
1|[email protected]:/data $
Click to expand...
Click to collapse
it's ask for sh i think it's ask for su , for root and devices not rooted [ /system/bin/sh: cd: /data/system - No such file or directory ]
the terminal cmd not see my devices if i open on lock i do that , with my device open recovery mode
I think you needs root
But if you install cwm recovery then tool I have posted should work.
Sent from my GT-N7100 using xda premium
dr.ketan said:
I think you needs root
But if you install cwm recovery then tool I have posted should work.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
if i do that will make any problem on my device ?
It will raise flash counter and you will lose warranty.
Read chainfire's triangle away thread, if your device listed then you can revert warranty.
Sent from my GT-N7100 using xda premium
dr.ketan said:
It will raise flash counter and you will lose warranty.
Read chainfire's triangle away thread, if your device listed then you can revert warranty.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
i don't have warranty on my device ,
can u tell me what is best to do that and how i can do it thank you
USB debugging mode not enable
What exact your tab model number?
Sent from my GT-N7100 using xda premium
Use this app
My app can temporary disable the lockscreen, but the home button not work.
Install via adb and use this command:
adb shell am start -n hu.hexadecimal.locktester/.UnlockActivity
Sorry for my bad English!
Need help.
My friend come to me with her device (Samsung galaxy S2 i9100). She forgot password, but doesn't lose any data.
She use stock rom, but i don't know the android version her used.
Sorry for my bad english.
---------- Post added at 06:00 PM ---------- Previous post was at 05:55 PM ----------
[email protected] said:
My app can temporary disable the lockscreen, but the home button not work.
Install via adb and use this command:
adb shell am start -n hu.hexadecimal.locktester/.UnlockActivity
Sorry for my bad English!
Click to expand...
Click to collapse
how to install apps without turn on usb debugging.
Sorry for my bad english too.
Natur said:
Need help.
My friend come to me with her device (Samsung galaxy S2 i9100). She forgot password, but doesn't lose any data.
She use stock rom, but i don't know the android version her used.
Click to expand...
Click to collapse
Installing apps without usb debugging is not possible.
But you have an another chance:
1. Follow the instructions at here: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-install-cwm-recovery-flash-t1814801 (Install CWM Recovery)
2. Download the AROMA Filemanager (http://forum.xda-developers.com/showthread.php?t=1646108) and place it to sd.
3. Reboot to recovery and select AROMA Filemanager's zip, and install.
4. In AROMA go to settings and mount all partitions.
5. Delete /data/system/settings.db
6. Reboot and enjoy
If not working go to step 5. and delete /data/system.
[email protected] said:
Installing apps without usb debugging is not possible.
But you have an another chance:
1. Follow the instructions at here: http://forum.xda-developers.com/galaxy-s2/general/how-to-root-install-cwm-recovery-flash-t1814801 (Install CWM Recovery)
2. Download the AROMA Filemanager (http://forum.xda-developers.com/showthread.php?t=1646108) and place it to sd.
3. Reboot to recovery and select AROMA Filemanager's zip, and install.
4. In AROMA go to settings and mount all partitions.
5. Delete /data/system/settings.db
6. Reboot and enjoy
If not working go to step 5. and delete /data/system.
Click to expand...
Click to collapse
Thanks Sir, i will try.
I know this is a old thread but I just unlocked my Tab4 10.1 with this method but I didnt have a settings.db file so just renamed the _password.key to _password.key.old and the sparepassword.key with .old as well. I was like hey what do I gotta lose anyway if I mess it up I'll just restore.. I hit exited out of everything rebooted & presto no more password.. I dont know if this would be the same if I set a pin, what the file would be called but maybe I'll set one and see just for the hell of it.. lol
Anyway just thought I'd share that you dont have to panic & lose everything by doing a hard reset..
Cheers !
And thank you to [email protected] !!
Q&A for [ROOT] [TOOL] Easy Ace Root Tool
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Problem using Easy Ace Root Tool
I was using Easy Ace Root Tool to unlock the bootloader since this seems like the most updated method. I can tell it worked because there's a green "UNLOCKED" word on the top of the recovery screen. But I don't believe I completed the whole process. When I was using the tool, I encountered an issue after the step where I pasted the Unlock code into the token folder. The command prompt message stated that I will be prompted by the phone to do something and I have to answer "Yes". My phone never prompted me to do anything. It was just displaying the recovery screen the whole time. I chose to Reboot the phone and it did a factory reset. I used Root Checker to see if the root was successful and it said I do not have root access.
I'm assuming that there are still more steps to follow so that the tool will install CWM and SU for me, correct?
At this point, what can I do? I tried twice already to rerun the tool and unlock the bootloader but I encountered the same issue where my phone did not prompt me to answer "Yes" to a question...
My phone is running GB 2.3.5 but it was running Froyo when I first bought it new in June 2011 (if this makes any difference).
Solved
I was reading around the forums here and noticed someone had a similar issue. Turns out the CWM was installed without my notice. I downloaded a zip of the latest SuperSU like another user said and installed it from the CWM recovery. According to Root Checker, I'm rooted now.
It's weird because I know for a fact that the Easy Ace Root process didn't 100% finish.
This has been very informative and helpful!
It can't find the fre3vo file that's in the path it's looking for.
There is no antivirus on this system.
The file is there.
Everything worked fine up to this point.
It's actually stopped there, after several retries, this is where it repeatedly fails on me at.
Running in VM because host OS is linux, and the tool is designed for Windows OS.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please Help Me
I'm having an issue getting root, first two steps are cake, but root wont go through. After tweaking the cmd file a bit to get it to find fre3vo this is the error I get.
Achieving Temp Root
231 KB/s (9704 bytes in 0.041s)
Locating access point...
This device does not support this exploit.
This device does not support this exploit.
The exploit has failed.
Pushing Busybox, SU and Superuser
174 KB/s (536 bytes in 0.003s)
1561 KB/s (380532 bytes in 0.238s)
1962 KB/s (1372660 bytes in 0.683s)
Trying to gain Perm Root
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'tools\su\su' to '/system/bin/su': Read-only file system
failed to copy 'tools\su\Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
FIND: Parameter format not correct
rm failed for EasyAceRoot.cmd, No such file or directory
Perm Root achieved...
Press any key to continue . . .
Click to expand...
Click to collapse
For anyone interested, here is the tweak I made to the cmd file to find fre3vo:
Original:
echo Achieving Temp Root
echo.
adb push /tools/tmp/fre3vo /data/local/tmp
Click to expand...
Click to collapse
Tweak:
echo Achieving Temp Root
echo.
adb push tools\tmp\fre3vo /data/local/tmp
Click to expand...
Click to collapse
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
Gakuseinozen said:
I have two separate issues which I believe are caused by the same thing.
1. When I try to alter platform.xml in the /system/etc/permissions folder via ES File Explorer to enable 3rd party apps to have write capability to the SD card, the edit is unsuccessful and my phone reboots. When I pull a copy of the file to my PC, alter it, and then try to push it via ADB, the same thing happens. I previously used the ADB pull/push method to edit my hosts file and had success with that after doing it while in Recovery, but this time around both ways (in recovery and with the device booted up) result in my device rebooting. For the SD card fix, I've also tried the app that does it for you and encounter the same issue.
2. When attempting to update the SuperSU binary, the update fails my device reboots. This happens with either update method - normal and recovery.
So both issues seem to have the same root cause... my phone will not allow any editing of system files. Anyone have any suggestions?
For reference I'm on a Galaxy Note 4 (model SM-N910T) on T-Mobile.
Baseband version N910TUVU1ANJ7
Android version 4.4.4 (stock ROM)
Kernel version 3.10.0-2796035
Build number KTU84P.N910TUVU1ANJ7
I'm also running Wanam Xposed - not sure if that has anything to do with anything but just fyi.
Thanks
Click to expand...
Click to collapse
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
ИΘΘK¡€ said:
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
Click to expand...
Click to collapse
I went into the terminal emulator app, typed su and then the command you listed and even after that I'm still having the same problem. Any other ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gakuseinozen said:
I went into the terminal emulator app, typed su and then the command you listed and even after that I'm still having the same problem. Any other ideas?
Click to expand...
Click to collapse
Yes, try this:
Code:
mount -o rw,remount /system
ИΘΘK¡€ said:
Yes, try this:
Code:
mount -o rw,remount /system
Click to expand...
Click to collapse
No luck after that one either.
Any more ideas?
ИΘΘK¡€ said:
You probably need to remount /system as rw. Use this in a shell:
Code:
mount -o rw,remount rootfs /
Click to expand...
Click to collapse
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
instinctblade said:
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
Click to expand...
Click to collapse
Are you saying to un-root and root again? Is 'unlockroot pro' an app?
Thanks
Gakuseinozen said:
Are you saying to un-root and root again? Is 'unlockroot pro' an app?
Thanks
Click to expand...
Click to collapse
Yes "Unlock-Root" is a pc software which can Unroot & Root your device
instinctblade said:
Yes "Unlock-Root" is a pc software which can Unroot & Root your device
Click to expand...
Click to collapse
That wasn't the method I used to root in the first place. Does that matter?
Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
Gakuseinozen said:
Anyone else have any ideas? I tried posting logs in the SuperSU update failure thread, with the logic that if I get that issue fixed my other issue will be resolved also, but Chainfire hasn't responded to any of the requests in a while.
Click to expand...
Click to collapse
Try older version of supersu? Or could it be something inside the supersu setting? Just a thought.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)
Naimlaaa said:
Try older version of supersu? Or could it be something inside the supersu setting? Just a thought.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)
Click to expand...
Click to collapse
Don't think an older version would help since i started having this problem with the version I'm currently running. I also went through the SuperSu settings and tried a few different things but nothing helped. I changed Default access from "grant" to "prompt", changed Mount namespace separation to "all root processes share inits mount namespace" and enabled "trust system user".
Not sure what else I could try really.
instinctblade said:
Did you try uninstalling the root from the unlockroot pro and rooting it again using the [super su update.zip]
try this it might work
Click to expand...
Click to collapse
Did you try this method yet? Also can try VoodooOTA rootkeeper.
And/or remove xposed first?
Im a noob in this but just trying to share some idea though.
SGs3n SlimKat9.0(Android-Andi)/F_Kernel1.3(Fred6681)/SuperSU2.4?(ChainFire)/BusyBoxX33(MaxIce)