Related
Quick conundrum...
Rooted my 32bg Nexus7 a couple of days ago using the Nexus 7 toolkit.
I have an unlocked bootloader and CWM recovery installed . i did the all in option in the toolkit..
Just installed Titaanium backup, and it says i'm not rooted??
Root check says i am rooted !
Busybox says i'm not rooted
Superuser fails on updating binary (root acess)
So the 64K question..
Am i rooted or not?
if not ,how do i root properly?
Mart
Srsly? Please go back and root it manually. It will work.
Mart360 said:
Quick conundrum...
Rooted my 32bg Nexus7 a couple of days ago using the Nexus 7 toolkit.
I have an unlocked bootloader and CWM recovery installed . i did the all in option in the toolkit..
Just installed Titaanium backup, and it says i'm not rooted??
Root check says i am rooted !
Busybox says i'm not rooted
Superuser fails on updating binary (root acess)
So the 64K question..
Am i rooted or not?
if not ,how do i root properly?
Mart
Click to expand...
Click to collapse
flash this in your recovery http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
your problem is that you used the rootkit on a nexus device. theres no need for that.
simms22 said:
flash this in your recovery http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
your problem is that you used the rootkit on a nexus device. theres no need for that.
Click to expand...
Click to collapse
This is what i used
http://forum.xda-developers.com/showthread.php?t=1809195
So if thats not correct, what is?
i looked at the nexus rootkit, but it didnt specify my model so i gave it a miss
Mart
Mart360 said:
This is what i used
http://forum.xda-developers.com/showthread.php?t=1809195
So if thats not correct, what is?
i looked at the nexus rootkit, but it didnt specify my model so i gave it a miss
Mart
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash a custom recovery, flash either the su binaries or a custom rom in your new recovery, reboot. that is all.
all you need to do is have the drivers and fastboot installed http://forum.xda-developers.com/showthread.php?t=1741395
If you go to terminal emulator and type in su, does the $ change to a #?
Sent from my Nexus 7
If you have access to directories like /system and /dev, you're rooted. If not, you're not. Skipsoft's Nexus 7 Toolkit works well. Just redo the root steps, watch for error messages, and use Super SU (not SuperUser), and you'll be fine.
This happened to me too so I re rooted it manually. I just followed this link:
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
Wow this is getting confusing... ive got two or more guides open both with varying methods and files to install..
if i download the new SU files and reroot, then it wipes all files ? so how does having the SU work
As to reflashing a new binary, thats what i dont want, i just want a stock set up thas rooted.
Also re terminal? it that putty ? and go into the device that way?
Mart
all the binary will do is give you root/su, that is what you want. no more, no less. youll need the supersu app too, to grant su.
simms22 said:
all the binary will do is give you root/su, that is what you want. no more, no less. youll need the supersu app too, to grant su.
Click to expand...
Click to collapse
Which binary? im really confused lol
I have SU as an APK, do i run this before rooting or do i run this apk from CWM? and then reroot using the toolkit?
Mart
Mart360 said:
Which binary? im really confused lol
I have SU as an APK, do i run this before rooting or do i run this apk from CWM? and then reroot using the toolkit?
Mart
Click to expand...
Click to collapse
the binaries i posted in post #3 http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
flash it in your custom recovery and reboot. you do have cwm recovery installed as i understand, right? that su binary is the most recent. you dont want su(superuser) you want the supersu app.
simms22 said:
the binaries i posted in post #3 http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
flash it in your custom recovery and reboot. you do have cwm recovery installed as i understand, right? that su binary is the most recent. you dont want su(superuser) you want the supersu app.
Click to expand...
Click to collapse
Yes i have those , i went into CWM and went to apply update from zip on SD card
the options i had were folders
one called clockwork mod
then a file called update zip appears, thats all iget
Its just a leap of faith now i guess, im just being cautious incase i brick the puppy
Mart
Mart360 said:
Yes i have those , i went into CWM and went to apply update from zip on SD card
the options i had were folders
one called clockwork mod
then a file called update zip appears, thats all iget
Its just a leap of faith now i guess, im just being cautious incase i brick the puppy
Mart
Click to expand...
Click to collapse
look in /data/media/0(downloads folder if you downloaded directly to your seven)
also, do you have the latest version of cwm?
simms22 said:
look in /data/media/0(downloads folder if you downloaded directly to your seven)
also, do you have the latest version of cwm?
Click to expand...
Click to collapse
:good: Done many thanks... it was in a different folder, but all seems to have gone ok, just backing up with Titanium backup.
One more daft nooby question,,,, where does Titanium backup actually backup too?
I havnt given any patch to my PC?
Mart
Mart360 said:
:good: Done many thanks... it was in a different folder, but all seems to have gone ok, just backing up with Titanium backup.
One more daft nooby question,,,, where does Titanium backup actually backup too?
I havnt given any patch to my PC?
Mart
Click to expand...
Click to collapse
they dont go onto your pc. normally they would go into the titanium backup folder, but you have an option of storing them in the cloud(i use the google drive option, then just restore from there too).
simms22 said:
they dont go onto your pc. normally they would go into the titanium backup folder, but you have an option of storing them in the cloud(i use the google drive option, then just restore from there too).
Click to expand...
Click to collapse
Again Many thanks sometimes we can be a bit slow on the uptake lol
cheers for sticking with me and seeing it through
Mart
after rooting my s4 (i9500) :S using this method http://galaxys4root.com/galaxy-s4-root/how-to-root-galaxy-s4-cwm-method/ everything is fine but when i open supersu it says need update binary i chose OK but says installation failed i got enough space! 3gb left!
i bought it yesterday
anyone please answer me((
i also tryed root ur phone in cwm but same in superuser update binary everything goes fine expext gaining root accses seems i dont got root
kamranhaghighi said:
i also tryed root ur phone in cwm but same in superuser update binary everything goes fine expext gaining root accses seems i dont got root
Click to expand...
Click to collapse
kamranhaghighi said:
anyone please answer me((
Click to expand...
Click to collapse
Use this method for rooting & revert then -> http://forum.xda-developers.com/showthread.php?t=2262110
unroot and re root?
thanks so much is this coz its new ? i mean almsot no roms and only few rooting methods!
yeaa really thanks! ThAnks it workedddLDDDDDD
Disturbed™ said:
Use this method for rooting & revert then -> http://forum.xda-developers.com/showthread.php?t=2262110
Click to expand...
Click to collapse
you also have to make sure you also have a custom recovery and not just root access with stock recovery
i have the same problem pn my samsung galaxy s3 i9300 plzz help me
..
..
I've never done a backup myself but that's bad practice I know.
If SuperSu does not ask you for root privileges, then there might be some issues with your root. Have you tried to install the latest update? I had the same issue right after root, the default SuperSu app did not work so what I did was flashing the latest SuperSu app via Recovery and it worked.
Get it here: http://forum.xda-developers.com/showthread.php?t=1538053
I just flash 4.4.2 INU, just backup yr msg & call logs, the installation process automatically backup & restore apps
Sent from my GT-I9500 using xda app-developers app
Always make a backup before doing anything to your system. You never know what might go wrong. You can backup using nandroid or your custom recovery.
Regarding you SuperSU issue, make sure you answer "No" when your custom recovery asks you fix root (unless specified by the rooting procedure - philz touch recovery when rooting Russian firmware i9500 4.4.2).
Moreover, you can download an app to check if you lost your root privileges. If you did lose it, root your system again.
..
Ap0rd said:
I already backed up my stock rom as an image, I'm talking about backing up apps, settings, etc to restore them. About superuser, I tried several times to re root but i won't work.
Click to expand...
Click to collapse
you can use titanium backup but that needs root. uninstall Super SU and install it from the play store. The app will detect if its activity is hindered by KNOX.
..
Ap0rd said:
By uninstalling , you mean unrooting?
Click to expand...
Click to collapse
First, make sure that your are, indeed, rooted. Uninstall Super SU in Applications Manager in your Settings. Install again from play store.
..
download a root checker app to check if you are rooted. try downloading Super SU from play store anyway. See what happens.
cheers ~
..
Ap0rd said:
How am i supposed to check for root if supersu isn't giving root access
Click to expand...
Click to collapse
ohhh right. reinstall your recovery and reroot your phone. When I was on 4.3, I used CWM 6.0.4.5.
..
Ap0rd said:
Why do I have to reinstall the recovery? And more importantly, I tried to re root before but it didn't work?
Click to expand...
Click to collapse
I read you first post again and you stated that you can grant root privileges to apps (always grant). Install Titanium Backup and backup your apps and flash 4.4.2. What's the problem here?
..
Ap0rd said:
Thanks for the help. Did you flash 4.4.2? And if you did, did you encounter any problems with it?
Click to expand...
Click to collapse
Yes. Flashed it with ODIN. No problems whatsoever. ALTHOUGH... some users are complaining about sd card permissions.
..
Ap0rd said:
Flashed 4.4.2 and rooted with philz recovery... No problems...
Thanks for the help everyone, especially @deandoi
Click to expand...
Click to collapse
Gladly.
cheers ~
Dear friends,
First all, I tried to search, found some threads (Titanium Backup problem) but it did not work for me.
I just bought a N9005 (after 1 year stick with i9500). With i9500 everything very simple with 4.3, I haven't upgraded to KitKat.
With N9005 I stuck with some problem for days: Tried to install some Custom Rom: Crash, Echoe, X-Note ... same problems:
- Dropbox: can not export file, can not save.
- Titanium Backup: FC
- Some apps can not download file.
-----------------------------------------------------------
I tried
"su
Restorecon -R -v /data/data/
But still didnot work. I think the problem is can not write on the storage. But it's weird, in Browser i'm still able to download files.
-----------------------------------------------------------
Later I went back to stock rom, with root flashed. Everything go smooth. But I still want to go with custom rom (as I always did with my i9500). Is this custom rom problem?
-----------------------------------------------------------
Thank you all.
Best regards.
Ryan.
Alan_Hill said:
Dear friends,
First all, I tried to search, found some threads (Titanium Backup problem) but it did not work for me.
I just bought a N9005 (after 1 year stick with i9500). With i9500 everything very simple with 4.3, I haven't upgraded to KitKat.
With N9005 I stuck with some problem for days: Tried to install some Custom Rom: Crash, Echoe, X-Note ... same problems:
- Dropbox: can not export file, can not save.
- Titanium Backup: FC
- Some "black market" can not download file.
-----------------------------------------------------------
I tried
"su
Restorecon -R -v /data/data/
But still didnot work. I think the problem is can not write on the storage. But it's weird, in Browser i'm still able to download files.
-----------------------------------------------------------
Later I went back to stock rom, with root flashed. Everything go smooth. But I still want to go with custom rom (as I always did with my i9500). Is this custom rom problem?
-----------------------------------------------------------
Thank you all.
Best regards.
Ryan.
Click to expand...
Click to collapse
To be clear, what rom are you using now? JB or KK?
fadhil3536 said:
To be clear, what rom are you using now? JB or KK?
Click to expand...
Click to collapse
KitKat my friend
Alan_Hill said:
- Some "black market" can not download file
Click to expand...
Click to collapse
No warez or discussion thereof allowed here, forum rules. That may be your problem - corrupted or virus-ridden warez apks. Good luck....
B3311 said:
No warez or discussion thereof allowed here, forum rules. That may be your problem - corrupted or virus-ridden warez apks. Good luck....
Click to expand...
Click to collapse
Ok sorry my bad, may I edit my post?
Might not be crrupted or virus, I tried many times with different roms, with full wipe, format ...
Still not entirely clear - did you have a working KK ROM and now you're trying to install a KK custom ROM, or did you have JB 4.3 before trying to upgrade?
Alan_Hill said:
Ok sorry my bad, may I edit my post?
Might not be crrupted or virus, I tried many times with different roms, with full wipe, format ...
Click to expand...
Click to collapse
Before installing custom rom, did you wipe your rom manually using recovery (CWM)? wipe cache, systems, dalvik and data partitions?
Titanium backup have a problem when restoring data in KK, but there is a fix for it in the playstore. When finished restore (batch restore) don't run the app yet, run the TB fix and restart.phone.
All downloaded file using any browser will go to phone memory.
I am using stock root NC2. to bypass this SD Card issue copy this file to system/etc/permissions and set permission. Restart phone. hope it help.
https://www.dropbox.com/s/5yxb1kqv8lc6ycp/platform.xml
fadhil3536 said:
Before installing custom rom, did you wipe your rom manually using recovery (CWM)? wipe cache, systems, dalvik and data partitions?
Titanium backup have a problem when restoring data in KK, but there is a fix for it in the playstore. When finished restore (batch restore) don't run the app yet, run the TB fix and restart.phone.
All downloaded file using any browser will go to phone memory.
I am using stock root NC2. to bypass this SD Card issue copy this file to system/etc/permissions and set permission. Restart phone. hope it help.
https://www.dropbox.com/s/5yxb1kqv8lc6ycp/platform.xml
Click to expand...
Click to collapse
To be clearer, I have stock root NC2, wanna try other custom roms (Crash, Echoe, Xnote).
I tried them all but still have the same issue.
I always do full wipe in CWM when switch to another custom rom.
I tried to edit the permission as you mentioned (both manually and copy file) but got error message all the time, seem like I couldn't write or edit file.
I installed the TB fix on Play Store, but It say no issues with the phone (weird), so can not run.
Stock rom everything seem ok but custom roms always have same issues T_T
Its mean your phone doesnt fully root?
fadhil3536 said:
Its mean your phone doesnt fully root?
Click to expand...
Click to collapse
I double checked that. Tried to flash root again. Superuser ok, but still stuck .
Alan_Hill said:
I double checked that. Tried to flash root again. Superuser ok, but still stuck .
Click to expand...
Click to collapse
Can i know which method you are using to root the phone?
fadhil3536 said:
Can i know which method you are using to root the phone?
Click to expand...
Click to collapse
I flash the auto root in team win recovery mode .
Did you remove the file explorer from supersu app then give root permissions again afterwads?
This fixed ES for me...
I'm using this:
https://plus.google.com/app/basic/stream/z12fsrl4jujntr24h04cjl1aoor5ezninhc
MY GUIDES TOWARDS VICTORY:-
FR34K-B1B0
vaskodogamagmail
HmanA6399
Peontikos_Desmos
I am truly very much grateful to you guys! Owe you!!!
TOOLS YOU NEED:-
EFS PROFESSIONAL (PC) [Get it here!]
TWRP Recovery Installed Phone [Get it here!]
BUSY BOX PRO (APK) [Get it Here!]
ODIN (PC)
N910C PIT FILE (FIND ONE FOR YOUR EXACT PHONE MODEL!)
APPROPRIATE STOCK ROM. (AS PER YOUR CURRENT BASEBAND VERSION!)
ROOT EXPLORER PRO (APK).[Get it here!]
Okay, Now carefully follow my instructions.
BOOTLOOP FIX
Make a TWRP NANDROID BACKUP of your current properly working ROM [eg: CM13].
Make sure that your phone is rooted. Then, Install Busybox (Run the application and then install busybox) and Root Explorer in your current custom ROM (Don't forget to grant root permissions).
In Root Explorer, Go to root (R/w mode enabled), Enter EFS folder, Copy the following files to your SD card.
imei (folder)
.nv_data.bak (file)
(Keep these two things safe somewhere, Because you will need it later to fix your IMEI)
In your phone settings, make sure 'USB debugging' is enabled from 'Settings->Developer Options->'.
Run 'EFS Professional' on PC. (On your PC, Make Sure that you have installed 'Samsung USB Drivers' from here & 'Google adb USB drivers' from here.)
Connect the phone to PC, Grant root access to your PC by confirming the dialog box showing up in the phone.
On EFS Professional, Go to "Samsung Tools" tab , Go to "Other tools" and select "Format EFS Folder" then click "Execute".
Power off the phone, Reboot into TWRP Recovery.
Wipe all data/factory reset.
Power down the Phone and Reboot into 'Download' mode.
Start ODIN on PC and Connect the Phone.
In Odin, Load the 'PIT' File, Check 'Re-partition' and Load your Stock ROM file to AP. Click Start to flash the stock firmware.
VOILA!! ONCE FLASHING IS DONE, YOUR PHONE WILL BE AUTOMATICALLY REBOOTED INTO YOUR STOCK ROM WITHOUT ANY FRUSTRATING BOOTLOOPS !!!!!!
NOW YOU PEOPLE WILL BE FACING A 'NOT REGISTERED ON THE NETWORK' PROBLEM. DON'T WORRY! LET'S FIX IT! FOLLOW MY LEAD!
EFS / IMEI FIX
Boot to your new stock ROM.
Install BusyBox (Run the application and then install busybox) and RootExplorer.
Start 'root explorer', Go to root ((R/w mode enabled), Go to EFS folder
Delete all the files and Restart the phone.
Again repeat 'Step 3'.
Now you will see some files again. Now, carefully delete only the 'imei' folder and 'nv_data.bin' file.
Make two copies of your previous ROM backup file ".nv_data.bak" into the new ROM's EFS folder and rename it to "nv_data.bin" and "nv_data.bin.bak" respectively.
Finally, Reboot the Device.
THATS IT! YOU NOW GOT YOUR NETWORK BACK!!! ENJOY THE STOCK ROM!!!!
(Keep a TWRP Nandroid backup of your Stock ROM. It will help you out from other troubles in the future!)
Hit 'Thanks' If I helped you out!! Ask for more assistance!
Cheers!
Arun
Grrrrr8??
Sent from my HTC Desire 820s dual sim using Tapatalk
Can anyone confirm this works?
I attempted this method with not much luck in the end
Same, when i open the EFS folder / copy it with Root Explorer, and it say need Root Access. When i press okay the phone is rebooting. Please someone help me.
I'm glad you got your phone back!
But I still don't know what the EFS folder has to do with the bootloops. I guess we should try the following
1- Make an EFS backup in your CM13 rom (just in case) but don't delete anything.
2-Go to recovery and wipe data cache and dalvik.
3-Reboot in download mode and connect your phone to your pc, then open ODIN.
4-Load your .PIT file and tick 'Repartition". Add your stock TW 5.1.1 rom and flash everything
5-Wait until it boots and check if you have signal.
I've used CM12 and reverted to stock Lollipop doing these steps (even without repartitioning) and worked just fine but maybe CM13 partitioning is different. Can anyone follow these steps and report what happend? Remember to make an EFS backup (as I said, just in case) before.
AlStarsKyz said:
Same, when i open the EFS folder / copy it with Root Explorer, and it say need Root Access. When i press okay the phone is rebooting. Please someone help me.
Click to expand...
Click to collapse
Give me more details about your phone, So that I can help you!
ColtD said:
Can anyone confirm this works?
I attempted this method with not much luck in the end
Click to expand...
Click to collapse
Tell me what happened for u. I will assist you.
galaxynote2 said:
I'm glad you got your phone back!
But I still don't know what the EFS folder has to do with the bootloops. I guess we should try the following
1- Make an EFS backup in your CM13 rom (just in case) but don't delete anything.
2-Go to recovery and wipe data cache and dalvik.
3-Reboot in download mode and connect your phone to your pc, then open ODIN.
4-Load your .PIT file and tick 'Repartition". Add your stock TW 5.1.1 rom and flash everything
5-Wait until it boots and check if you have signal.
I've used CM12 and reverted to stock Lollipop doing these steps (even without repartitioning) and worked just fine but maybe CM13 partitioning is different. Can anyone follow these steps and report what happend? Remember to make an EFS backup (as I said, just in case) before.
Click to expand...
Click to collapse
You can't simply restore a lollipop backup into marshmallow. Trust me, It won't work.
arunkrishnanr said:
Give me more details about your phone, So that I can help you!
Click to expand...
Click to collapse
What can i say to you?
AlStarsKyz said:
What can i say to you?
Click to expand...
Click to collapse
Where do you face the problem while doing this method?
arunkrishnanr said:
Where do you face the problem while doing this method?
Click to expand...
Click to collapse
When i'm open the EFS folder with Root Explorer, my phone got reboot automatically. And i try to copy it too and it's still rebooting. I got that after receive the verification root and i press ok, and i my phone reboot it self automatically.
AlStarsKyz said:
When i'm open the EFS folder with Root Explorer, my phone got reboot automatically. And i try to copy it too and it's still rebooting. I got that after receive the verification root and i press ok, and i my phone reboot it self automatically.
Click to expand...
Click to collapse
Try again. Use CF root to properly root your stock ROM. And then flash TWRP Recovery. Then setup busybox and root explorer in your stock rom. Make a backup of your EFS folder by copying it somewhere safe.
I used this method and I worked fine for me.
arunkrishnanr said:
Try again. Use CF root to properly root your stock ROM. And then flash TWRP Recovery. Then setup busybox and root explorer in your stock rom. Make a backup of your EFS folder by copying it somewhere safe.
I used this method and I worked fine for me.
Click to expand...
Click to collapse
Btw, i got this problem only on CM13, but when in stock it's working to open the EFS folder.
At least credit me
FR34K-B1B0 said:
At least credit me
Click to expand...
Click to collapse
May I ask why?
arunkrishnanr said:
May I ask why?
Click to expand...
Click to collapse
May i ask help me?
arunkrishnanr said:
May I ask why?
Click to expand...
Click to collapse
Because you're using the method I found?
FR34K-B1B0 said:
Because you're using the method I found?
Click to expand...
Click to collapse
Yes! Im sorry.. you are the one who helped me in the end.. i will credit u for sure..
AlStarsKyz said:
May i ask help me?
Click to expand...
Click to collapse
Sure. First of all, if your phone model is N910C and you are facing the problem, I would recommend you to try again my methods carefully. If you are facing any difficulty, Please let me know!
AlStarsKyz said:
Btw, i got this problem only on CM13, but when in stock it's working to open the EFS folder.
Click to expand...
Click to collapse
If your stock rom is working, then all you have to do is to follow the steps in the 'IMEI Fix'. Try that! But I hope you have made the backup from cm13.