Related
Hello,
1) Is there any way to root without losing all of your data? I'm not talking about basic things that Google backs up for you.
2) Is there any way to back up your apps and data without having root?
Thank you
1) If your bootloader is still locked, Nope.
2) Need root access to do full backups.
krelvinaz said:
1) If your bootloader is still locked, Nope.
2) Need root access to do full backups.
Click to expand...
Click to collapse
And the catch is the only way to unlock the bootloader is through a process by which you lose all of your user data, correct?
1. If your boot loader is still locked, then you have to do a full wipe.
2. If you use the Nexus Root Toolkit 1.5, you can create a backup of your apps, data and media, then restore it after root. Worked for me.
Sent from my Nexus 7 using xda premium
try this thread. you can back up your apps with adb without root or unlocking
http://forum.xda-developers.com/showthread.php?t=1420351
Hi,
Can you just root the N7, without loosing all your data?
I just want to be able to root it so I can use USB OTG properly.
With StickMount etc.
I don't want custom ROM's etc, just plain old root.
Any way to do this without loosing my apps/layout/data etc.
THANKS !
In order to "just" root, at a bare minimum, you will need to install su. In order to install su, you need to flash a custom recovery. To flash a custom recovery, your bootloader must be unlocked. Unlocking your bootloader erases everything unless you are already unlocked.
There might be a way but it involves relocking your bootloader before booting to the system. Booting the system in an unlocked state causes it to erase everything. All rooting operations can be done without booting the system and the last step would be to lock the bootloader. I have not tried this so no guarantees.
In order to root, you need to unlock your bootloader which will wipe your N7 app layouts etc. You can use adb to backup your apps and settings, or you can have a toolkit do it for you. Unfortunately, I can't help you with exactly how to backup. I didn't backup my settings when I unlocked my bootloader because I did it soon after I got my N7. I'm sure there is someone on here that's more knowledgeable in adb that can tell you the right commands.
Sent from my Paranoid Nexus 7
RockNrolling said:
In order to root, you need to unlock your bootloader which will wipe your N7 app layouts etc. You can use adb to backup your apps and settings, or you can have a toolkit do it for you. Unfortunately, I can't help you with exactly how to backup. I didn't backup my settings when I unlocked my bootloader because I did it soon after I got my N7. I'm sure there is someone on here that's more knowledgeable in adb that can tell you the right commands.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
Thanks both, what about the "All-In-One" nexus toolkit, I think that has a backup function and stuff.
And I guess this is a note to self "Root" before you customise and get all set etc.
I wouldn't even root it if I didn't want OTG but things have to be done I suppose.
Can any1 shed any light for the easiest way of rooting, and keeping my apps etc, because its such a ball-ache setting it up again
Hi everyone!
i want to root my nexus 7, if i'm not wrong to root it i have to unlock the bootloader, and i will lose all my data (i'll use the Wug's Toolkit)
if i root it now with 4.2.2, when i update it with the new 4.3, i'll lose root? if yes to root again my nexus, i'll lose again my data?
i hope my english is not that ugly :silly:
thanks for the help!
Zambo27 said:
Hi everyone!
i want to root my nexus 7, if i'm not wrong to root it i have to unlock the bootloader, and i will lose all my data (i'll use the Wug's Toolkit)
if i root it now with 4.2.2, when i update it with the new 4.3, i'll lose root? if yes to root again my nexus, i'll lose again my data?
i hope my english is not that ugly :silly:
thanks for the help!
Click to expand...
Click to collapse
Hi, Zambo27...
Your English is fine... don't worry about it.
You don't necessarily have to unlock the BOOTLOADER to root STOCK JellyBean 4.2.2.
An 'exploit' has become available which obviates this need...
http://forum.xda-developers.com/showthread.php?t=2233852
I have tested this myself, and I can confirm that it works... it's actually really easy; takes about a minute or so. The only 'downside' is because the BOOTLOADER is still locked, you won't be able to flash any custom ROMs or kernels.
But if all you care about is running ROOTED stock, then this is by far the easiest way to go.
(And the the 'upside' of course is... it doesn't wipe the tablet.)
------
For any future OTA updates from Google, you should be able to backup your ROOT (su binary), and restore it again after the OTA, using Voodoo OTA RootKeeper - http://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en.
Rgrds,
Ged.
GedBlake said:
Hi, Zambo27...
Your English is fine... don't worry about it.
You don't necessarily have to unlock the BOOTLOADER to root STOCK JellyBean 4.2.2.
An 'exploit' has become available which obviates this need...
http://forum.xda-developers.com/showthread.php?t=2233852
I have tested this myself, and I can confirm that it works... it's actually really easy; takes about a minute or so. The only 'downside' is because the BOOTLOADER is still locked, you won't be able to flash any custom ROMs or kernels.
But if all you care about is running ROOTED stock, then this is by far the easiest way to go.
(And the the 'upside' of course is... it doesn't wipe the tablet.)
------
For any future OTA updates from Google, you should be able to backup your ROOT (su binary), and restore it again after the OTA, using Voodoo OTA RootKeeper - http://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en.
Rgrds,
Ged.
Click to expand...
Click to collapse
2 try to get root... it almost killed me xD
on the first try SuperSU was installed but it told me that "su command" wasn't
then i tried again and now it's rooted and it work fine
one last question, i read a thing
if i modifies "too much" i'll lose the possibility to update to android's next version, i want to fix the issue with the xbox wireless controller (http://forum.xda-developers.com/showthread.php?t=1792531) it will make me some problems?
GedBlake said:
The only 'downside' is because the BOOTLOADER is still locked, you won't be able to flash any custom ROMs or kernels.
Click to expand...
Click to collapse
Ged,
That is a mis-statement. Using a single "dd" command from a root shell - for example either adb or a terminal emulator, you can write a custom recovery image file to the SOS (recovery) partition.
$ su
# dd if=/sdcard/recovery-image-file.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
That produces a tablet with a locked boot loader, a rooted stock ROM, and a custom recovery.
The very first thing to do at that point in time is to take a Nandroid backup - and get a copy of it off the tablet for safe keeping.
Jeez I wish the thread owners for toolkits and rooting methods would stress the importance of backups. There sure would be far fewer "omg help me please" requests in this (Q&A) forum if people would simply make backups of their nearly-stock ROMs.
bftb0 said:
Ged,
That is a mis-statement. Using a single "dd" command from a root shell - for example either adb or a terminal emulator, you can write a custom recovery image file to the SOS (recovery) partition.
$ su
# dd if=/sdcard/recovery-image-file.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
That produces a tablet with a locked boot loader, a rooted stock ROM, and a custom recovery.
The very first thing to do at that point in time is to take a Nandroid backup - and get a copy of it off the tablet for safe keeping.
Jeez I wish the thread owners for toolkits and rooting methods would stress the importance of backups. There sure would be far fewer "omg help me please" requests in this (Q&A) forum if people would simply make backups of their nearly-stock ROMs.
Click to expand...
Click to collapse
Thanks for the info, bfb0... I had some suspicions about the 'dd' command, but I wasn't confident/certain about whether it would work with a locked bootloader.
But if I understand you correctly, there would be nothing to stop somebody from gaining root by the 'exploit' method I alluded to earlier, and then flashing a custom recovery using 'dd'...
...and then by extension flashing a custom ROM or kernel...
If my understanding is correct, then does this not make unlocking the bootloader somewhat redundant (with the consequential wipe)... or am I missing something here?
Definitely going to have to experiment with this... when I have the time.
----
Incidentally, I'm with you on the Nandroid backup issue... it is vaguely puzzling why this step isn't as ingrained in peoples flashing habits as perhaps it should be.
It's so easy to do... takes less than 5 minutes... and is a potential lifeline back to a working tablet.
Rgrds,
Ged.
GedBlake said:
But if I understand you correctly, there would be nothing to stop somebody from gaining root by the 'exploit' method I alluded to earlier, and then flashing a custom recovery using 'dd'...
...and then by extension flashing a custom ROM or kernel...
Click to expand...
Click to collapse
You understand correctly. Unlocking the bootloader only allows you extra functionality of the bootloader itself (via fastboot flashing/boot commands). It doesn't "unlock" data in partitions - that security is normally provided by the Linux kernel permission system. Once you have root in ANY booted Linux kernel which properly reads the eMMC (flash chip) partitioning and plumbs /dev/block/ entries into the device tree corresponding to those partitions, any root-privileged process can write whatever it wants into those partitions.*
GedBlake said:
If my understanding is correct, then does this not make unlocking the bootloader somewhat redundant (with the consequential wipe)... or am I missing something here?
Click to expand...
Click to collapse
More or less, except that the bootloader will still fire up even if /cache, /data, and/or /system are completely bolluxed up. TWRP (and maybe CWM?) try to immediately mount /data and /cache so they are not quite as robust in the face of user screw-ups. But yeah - if you are careful, you could do everything you want without unlocking the bootloader... so long as the custom recovery stays healthy.
Mark my words: there will be people who root without unlocking their bootloader or installing a custom recovery (and thus fail to make a Nandroid backup), and then wedge their OS... and then come in here whining that they can't rescue their tablet without unlocking their bootloader (and thus wiping their entire tablet).
* there have been android devices which used hardware locking to restrict even kernel access to certain flash memory partitions, but there is no evidence that the N7 bootloader lock state affects any of the typical partitions involved in ROM flashing (recovery, boot, system, cache, use data).
bftb0 said:
You understand correctly. Unlocking the bootloader only allows you extra functionality of the bootloader itself (via fastboot flashing/boot commands). It doesn't "unlock" data in partitions - that security is normally provided by the Linux kernel permission system. Once you have root in ANY booted Linux kernel which properly reads the eMMC (flash chip) partitioning and plumbs /dev/block/ entries into the device tree corresponding to those partitions, any root-privileged process can write whatever it wants into those partitions.*
More or less, except that the bootloader will still fire up even if /cache, /data, and/or /system are completely bolluxed up. TWRP (and maybe CWM?) try to immediately mount /data and /cache so they are not quite as robust in the face of user screw-ups. But yeah - if you are careful, you could do everything you want without unlocking the bootloader... so long as the custom recovery stays healthy.
Mark my words: there will be people who root without unlocking their bootloader or installing a custom recovery (and thus fail to make a Nandroid backup), and then wedge their OS... and then come in here whining that they can't rescue their tablet without unlocking their bootloader (and thus wiping their entire tablet).
* there have been android devices which used hardware locking to restrict even kernel access to certain flash memory partitions, but there is no evidence that the N7 bootloader lock state affects any of the typical partitions involved in ROM flashing (recovery, boot, system, cache, use data).
Click to expand...
Click to collapse
Hi, again bfb0...
Much of this is is beyond me, I'm afraid...(actually, a lot of your posts are a bit beyond me, to be honest)...
...but I pick up bits and pieces here and there...
And I can confirm the 'dd' command does indeed work as you suggest.
-------------
A few hours ago, I fully backed up my N7 to my laptop (latest TWRP Nandroids, Titanium, etc)...
Fastboot flashed back to stock (JDQ39).
Relocked the bootloader.
Ran the 'exploit' - and acquired root.
Copied everything back over to my N7 from my laptop.
Flashed TWRP in Terminal Emulator via the 'dd' command - this took a few tries, 'cos it's a long command and there's plenty of scope for typos.
Booted into the Bootloader again, then TWRP...
First off was to flash Franco's kernel... which occurred without problem. (This was more of a test, than anything - just to see if it would work).
Next was to restore my last Nandroid backup... which also occurred without probems.
--------
So... as I write this, my Nexus 7 is more or less back to how it was... but with one significant difference... Custom Recovery, Custom ROM and Custom Kernel are all sitting behind a LOCKED BOOTLOADER.... no UNLOCKED PADLOCK symbol on boot. Oh... and it's also Rooted as well!.
I'm not sure why, but I find myself slightly amazed by this - I wouldn't have believed it possible...
Guess you learn something new everyday.
Cheers, bfb0!
(...and apologies to Zambo27 for ever-so-slightly hijacking your thread).
Rgrds,
Ged.
I wanted to install some root exclusive apps on my moto x to improve battery life and get most out of my style
But Iike my current rom and just wanted to only be able to install apps which require root
So, is it possible to only root the device without unlocking bootloader especially on MARSHMALLOW because most tutorials i able to find was lollipop
and also if I root my device ,does all my data and apps will be deleted?
please suggest me some tips regarding this issue and and any help is WELCOME:good:
P.S- my only experience with root is on samsung galaxy tab 2 on 4.4.2
- also please suggest any good backup application just in case
THANKYOU
Without unlocking bootloader I don't think anything will work since the rooting apps use system vulnerabilities till KitKat.
Unlocking bootloader do wipe all your data so u should backup important data before opening bootloader.
Rooting doesn't wipe your data, but for rooting u will need to unlock bootloader and it will wipe data so your data will be gone anyway.
U can backup through helium http://gs5.wonderhowto.com/how-to/back-up-your-android-apps-their-data-without-root-0158767/
Sent from my AO5510 using Tapatalk
Navi44 said:
Without unlocking bootloader I don't think anything will work since the rooting apps use system vulnerabilities till KitKat.
Unlocking bootloader do wipe all your data so u should backup important data before opening bootloader.
Rooting doesn't wipe your data, but for rooting u will need to unlock bootloader and it will wipe data so your data will be gone anyway.
U can backup through helium
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
also is there any difference in rooting Marshmallow and previous versions of android?
dwnloader said:
also is there any difference in rooting Marshmallow and previous versions of android?
Click to expand...
Click to collapse
Noops, just use new super su 2.62 from super su thread on xda
Sent from my AO5510 using Tapatalk
Weird question, I know, I know, just don't ask why I'm doing this.
Is there a way I can do it? I saw somewhere that there were command scripts on it but it doesn't work without root and based on reading the forum there isn't anything I can do to root it. So is there another way?
Try to flash twrp from odin without unlocking the bootloader it should (hard)brick your device but you cn boot from sd (google search and recover without losing any data
Lol idk why you would want to do this but flashing twrp will just say fail if you try to flash that in odin but Lol here downgrade the device to BPB1 https://www.androidfilehost.com/?fid=24438995911970571 then root the device using this guide https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 or this guide https://forum.xda-developers.com/ve...oot-method-t3561529/post71202995#post71202995 then download flashfire from the play store add this file to flash fire https://www.androidfilehost.com/?fid=23991606952607139 that contains the NCG Bootloader which wont flash in odin but should flash in flash fire doing this will completely hard brick the device where it wont boot anymore only to a black screen if you plug the device into your computer and it shows qualcomm high speed usb (might now show it) as the device connected lol you did it ??
Possibly to claim the warranty, if Knox isn't tripped.
The easiest, and most complete, way would be by using root. Using any other method can be fixed via Odin.
If you go the root way, if you have an eMMc 15 chip, just literally delete every folder using the File Manager in TWRP. No Odin flash can fix losing that data. Unfortunately, it will be quite obvious to a smart technician what you did they if "they" send it in to see what happened.
I'm not sure if you can do the same thing via SafeStrap, since both of my S5's are "originals" and use Samsung eMMc's and are Dev Unlocked.
If you don't mind me asking, why do you want to kill your S5?
The only reason I ask is because depending in the reason, it could be a simple solution or there may be no good solution.
EDIT:
Btw, you can root your phone no matter what eMMc chip the device has.
You just can't upgrade to Marshmallow afterwards. So you can still kill your device, with root, by downgrading to an older Android Version.
The easiest way to kill your device, without tripping Knox, and therefore prevent any questions about why your Knox flag might be tripped, is to use SafeStrap to delete everything, if you can. Like I said, I haven't had to use SafeStrap so I'm not sure what it's limitations are but if your phone is rooted, I'm sure it has very few differences/limitations when compared to TWRP.
Bottom line, root your phone, install SafeStrap, then use the File Manager to delete EVERYTHING. Save the /data section for last. I wish I could properly tell you the safe order to delete the files before your phone reboots on you but I've never had the need to kill a phone or had someone request how to. Maybe @GeTex or @jrkruse has more experience/better recommendations about how the best way to go about this might be. I doubt jrkruse will reply but GeTex seems to reply when needed. Hopefully she can provide insight/advice.
Another quick strategy is just to nuke the bootloader partition. This must be done using root from either safestrap or TWRP. Just type this command into the terminal with root permissions then reboot:
dd if=/dev/random of=/dev/block/platform/msm_sdcc.1/by-name/aboot
This will fill the aboot partition with random characters, leaving it unrecoverable even with an SD card. The only way to recover a phone from this is through the use of JTAG to manually rewrite the partition (requires disassembling the phone)