hi considering rooting device as cant hidecleanback launcher without root, my issue is this, if i ever wanted to return item for any reason is it possible to unroot, lock bootloader and return factory state or would it always be possible to tell it was a rooted device
Hi, yes you can.
Rooting with supersu is systemless for quite long time now so if you wipe data root is gone but supersu doea modify boot.img
1. It's better if you don't install TWRP recovery but only boot into it with "fastboot boot recovery.img" command in case you just want to test and aren't sure you want to keep the device.
2. Then you'll need to flash stock firmware, Nvidia provides a recovery image with everything needed to flash using fastboot, you'll also need USB Fastboot drivers provided by them if you use Windows.
From that recovery package you'll just need to flash boot.img and system.img so uncompress it to obtain only those 2 images OR you could flash OTA via TWRP recovery.
Then use "fastboot -w" to wipe everything (in 500GB Pro model that command takes 2 hours as it wipes entire hdd) OR you could also wipe data and cache via TWRP (that will help to avoid the 2 hours wipe for 500GB Pro too)
3. Once stock firmware is installed and data/cache wiped, boot to fastboot or bootloader mode and run:
"fastboot oem lock"
Done.
Here is a .zip package i made with all tools needed:
- ShieldTV Drivers + ADB + Fastboot + TWRP + Supersu (Uncompress in C:\ )
http://www.mediafire.com/file/bw5b39v0pqb78yi/ShieldTV_ADB+Fastboot+Drivers+TWRP+Supersu.zip
Enviado desde mi Moto X via Tapatalk!
Related
Prerequisites
In order to complete the steps below, you need to have the Android SDK installed. The SDK contains the latest version of adb and fastboot, which you will need for flashing files and issuing commands. You will also need a MicroUSB cable to execute adb sideload, fastboot flash, and other commands. You also need to unlock your bootloader - a process that wipes your data.
Enable Developer options by going to the Settings -> About screen and tapping Build number until the OS unlocks the hidden Developer options menu. Now go to Developer options and make sure you have USB debugging turned on. For security purposes, you can turn it off after we're done.
To unlock the bootloader, if you haven't already done so:
Reboot into the bootloader by issuing an adb reboot bootloader command on your computer or holding VolDn+Power while booting (power off, hold VolDn, then hold Power).
Warning: This will wipe your data. Type in fastboot oem unlock on your computer. Agree to the unlock by selecting Yes on your tablet (VolUp, then Power).
You have now unlocked your bootloader (and the data partition was wiped clean). Verify by rebooting to the bootloader again and looking at Lock State.
wm_IMG_20130809_162939
The Steps
Download the full factory image corresponding to your exact model (for example, 2013 Nexus 7 Wi-Fi is razor), which includes the full system, bootloader, recovery, kernel (boot.img), and radio (radio not included for Wi-Fi-only variants). It's a clean slate for these components - they'll flash cleanly over anything you have now.
Unpack the tgz (tar/gz) archive into its own directory. I use Total Commander, but you can use any tool that reads gz and tar, like 7-Zip:
image
Proceed with this step if you want to keep your data intact. If you skip this step, your data will be wiped. With your favorite text editor, edit (be careful not to run it by accident instead of editing) flash-all.bat (if you're on Windows) or flash-all.sh (Mac, Linux) and remove "-w" from the fastboot update command. For example, if the line reads fastboot -w update image-razor-jss15j.zip, it should now read fastboot update image-razor-jss15j.zip. The -w option instructs fastboot to wipe data.
Reboot into the bootloader and run the appropriate flash-all script:
8-9-2013 5-20-09 PM
That's it, you're done. In my case, the Nexus 7 is now running stock Android 4.3:
wm_Screenshot_2013-08-09-16-32-51
Note: The above procedure restored the factory recovery, so if you want a custom one, you can flash one now (see below).
For better security, you can relock the bootloader by issuing fastboot oem lock while booted to the bootloader. This will, however, mean that if you ever want to do anything that requires an unlocked bootloader, you will lose your data in the unlock process.
Rooting
Rooting a Nexus 7 is very easy. It requires an unlocked bootloader and a custom recovery. I recommend using TWRP.
Flash TWRP from here (Reboot into the bootloader as before and then fastboot flash recovery FILENAME.img).
Reboot into recovery (adb reboot recovery or hold VolUp and Power while booting).
Flash SuperSU from this post. To do that, download the zip, then put the recovery into adb sideload mode (in TWRP, it's under Advanced), and then do adb sideload FILENAME.zip. I've seen some people complain that doing so via CWM doesn't work, but flashing through TWRP and selecting Fix Superuser Permissions at the end does the trick.
You should be rooted.
Reboot, head to the Play Store, and update SuperSU.
wm_IMG_20130809_172741
To see full article with pictures go to source : cloudandro.com//revu_2_en.html
Hope this helps.
1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2.Download latest stock image for Nexus 9 from google: https://developers.google.com/android/nexus/images?hl=en
3.Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nex...recovery-twrp-2-8-2-0-touch-recovery-t2944788
4.Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a.I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
b.A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexus-9/general/marshmallow-factory-images-available-t3218290/page3
5.Download the latest supersu that works with nexus (beta now) : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
6.Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7.Unzip the 6.0 stock image into a folder and open a command window in the folder.
8.Type the following:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot oem unlock
c.flash-all, now wait a few minutes while the stock image flashes
9.At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot flash recovery twrp.img (or whatever the image filename is from the twrp download).
10.Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12.Now type adb push supersufile.zip /sdcard/supersufile.zip, make sure you’re typing from the correct directory.
13.Install supersu via the install menu on TWRP.
14.You now need to install a kernel with the no-forceencrypt flag set:
a.If you want to install a custom kernel (like elementalx), type adb push elementalxfile.zip /sdcard/elementalxfile.zip, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b.If you want to install the modified stock boot.img then unzip the boot.zip, boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step or you'll have to reflash twrp.
Reboot and you’re good to go.
Didnt work for me.
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
typo
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Fda979 said:
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Click to expand...
Click to collapse
Fixed. Thanks.
Sent from my Nexus 9 using Tapatalk
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I flashed the latest supersu and the latest elementalx kernel.... been running it since about an hour after elementalx kernel for 6.0 final was posted....... everything seems to be working fine. Are you sure? Maybe i'm having no problems with supersu because i'm using elementalx? let me know the reason, i'll check it out on my tablet and see if i can reproduce, and if so i'll modify the guide. But after about a day and a half use, i've had no issues. thx for quality checking.
gt
Am I missing something?
can I not just do a wipe and flash the img with twrp like a custom rom? Edit: Got it working. For me it was much easier to use this as opposed to the android sdk, because it would not detect my version of java. From there I followed your instructions, mostly. Putting the files you posted inside the directory the mini adb client allowed the flash-all command to work. From there I followed chainfire's instructions on the latest SU. Everything seems to be running smoothly. Thanks for the initiative, OP :good:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
dkryder said:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
Click to expand...
Click to collapse
Of course update binaries. Choose normal method.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I was facing same issue, then updated fastboot(android-sdk) and flash-all script worked fine for me.
That should work as well. That sequence of commands should work with any fastboot version. Just make sure to flash the vendor.img, some scripts don't use that as it's only used for the Nexus 9.
Why so complicated? I just installed @wug's NRT toolkit(on a Venue8 pro) and it did everything for me. Now im on rooted stock 6.0 with disabled encryption. Only thing i needed to do is to flash latest super su beta 2.52, that's it.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i did all this, no worries and no error messages
i did fastboot reboot
now I am in a weird loop of
- google screen
- your device is corrupt
- google screen
- twrp (it flashes quite quickly, error messages on mounting everything and last line says something about renaming and something about stock rom)
loop
any ideas ?
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Verttex said:
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Click to expand...
Click to collapse
yes, that seems to have been it
flashing TWRP seems to have been the problem so I have left everything as stock until root etc works on the stovk kernel
thanks for your help
Nice guide.
I install Busybox from Play, I assume that's needed? Everyone else doing this?
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
added link to the latest beta supersu. thx.
All of these steps worked for me, but my battery doesn't charge right I don't think. It says battery life is at 3,745%. It runs out somewhere around 3,000%. Any ideas on how to fix that?
Hello Friends,
I have seen several Youtube videos and read the thread of xda senior member the rooter to unroot and revert the oneplus 3t to stock. The senior member guided very beautifully to have the stock ROM with or without the bootloader unlocked and fix DM-verity issue.
The following guide is not my invention, I have taken the sources from internet and xda site. The difference is that I used TWRP to flash official oxygenOS zip file of 4.1.6 and I am surprised that this file also flash stock recovery, therefore I did not flash stock recovery and proceeded further for full wipe and lock bootloader. In the middle of thread, I also alerted and said that if stock recovery is not flashed after installing zip of 4.1.6, then it is mandatory to flash stock recovery from fastboot before locking bootloader, otherwise your devices will be bricked.
1) Flash Oxygen OS 4.1.6 through latest TWRP 3.1.1.2 and remember to wipe system, cache, data and delvic cache excluding internal storage before flashing. Do not wipe completely otherwise you will have TWRP installed again and you will have to flash stock recovery through fastboot method.
Link for official TWRP for oneplus 3t: https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Link for official stock recovery for oneplus 3t: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/ , here go down the page and click on "Download Oxygen Recovey (Optional)"
After booting successfully, go to setting and tap the build number 7 times to enable advanced reboot and usb debugging and connect your mobile with your PC and make sure that you have adb drivers installed on your PC.
Now, extract the folder of fastboot and press the right click of mouse while pressing shift button. Basically you have to open command prompts. Now type: adb reboot recovery and hit enter.
2) Your phone should boot into oxygen stock recovery and if it does not boot to stock recovery then flash stock recovery from fastboot.
2) Now your oneplus 3t is having Oxygen OS 4.1.6 with stock recovery but having DM verity issue. Now, full wipe ( select erase everything) in stock recovery and reboot. This wiping through stock recovery may be extra step (locking the bootloader will erase your data completely) but I did this to avoid any problem.
3) Now, sideloaded the same file i.e. oxygen OS 4.1.6 or OOS 4.1.7 through the following command:
adb sideload OTA.zip
where OTA is zip file downloaded from oneplus site for oneplus 3t and renamed it as OTA
(For this, you will have to go to stock recovery and select the option of "install from ADB" then a pop up screen will show you that you are in sideload mode. But remember that sideloading the OS is a slow process; so keep patience and do not remove cable in the middle of installation otherwise your device will be bricked.)
4) Now, lock the bootloader from the command in fastboot mode:
fastboot oem lock
after entering the command in fastboot mode, a confirmation will be asked to lock the bootloader for Yes or No, confirm from the volume keys and let boot the phone automatically and wait to finish.
5) If you sideloaded the OOS 4.1.6 in step 3 then you will see the update notification of OOS 4.1.7 which is about 450MB, download it ,install it and reboot.
6) Enjoy............the stock
Thanks to guides on youtubes and xda site.
Please note that if you follow these steps, you will not have any issues because I have done again and again without any issues but I do not take any responsibility of bricked devices if you perform wrong method or skip any thing.
Please hit the like if find this useful, it is absolutely freeeeee.............
What if I currently have no OS installed? Does that matter?
sandeep_kumar said:
Hello Friends,
I have seen several Youtube videos and read the thread of xda senior member the rooter to unroot and revert the oneplus 3t to stock. The senior member guided very beautifully to have the stock ROM with or without the bootloader unlocked and fix DM-verity issue.
The following guide is not my invention, I have taken the sources from internet and xda site. The difference is that I used TWRP to flash official oxygenOS zip file of 4.1.6 and I am surprised that this file also flash stock recovery, therefore I did not flash stock recovery and proceeded further for full wipe and lock bootloader. In the middle of thread, I also alerted and said that if stock recovery is not flashed after installing zip of 4.1.6, then it is mandatory to flash stock recovery from fastboot before locking bootloader, otherwise your devices will be bricked.
1) Flash Oxygen OS 4.1.6 through latest TWRP 3.1.1.2 and remember to wipe system, cache, data and delvic cache excluding internal storage before flashing. Do not wipe completely otherwise you will have TWRP installed again and you will have to flash stock recovery through fastboot method.
Link for official TWRP for oneplus 3t: https://dl.twrp.me/oneplus3t/twrp-3.1.1-2-oneplus3t.img.html
Link for official stock recovery for oneplus 3t: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.7/ , here go down the page and click on "Download Oxygen Recovey (Optional)"
After booting successfully, go to setting and tap the build number 7 times to enable advanced reboot and usb debugging and connect your mobile with your PC and make sure that you have adb drivers installed on your PC.
Now, extract the folder of fastboot and press the right click of mouse while pressing shift button. Basically you have to open command prompts. Now type: adb reboot recovery and hit enter.
2) Your phone should boot into oxygen stock recovery and if it does not boot to stock recovery then flash stock recovery from fastboot.
2) Now your oneplus 3t is having Oxygen OS 4.1.6 with stock recovery but having DM verity issue. Now, full wipe ( select erase everything) in stock recovery and reboot. This wiping through stock recovery may be extra step (locking the bootloader will erase your data completely) but I did this to avoid any problem.
3) Now, sideloaded the same file i.e. oxygen OS 4.1.6 or OOS 4.1.7 through the following command:
adb sideload OTA.zip
where OTA is zip file downloaded from oneplus site for oneplus 3t and renamed it as OTA
(For this, you will have to go to stock recovery and select the option of "install from ADB" then a pop up screen will show you that you are in sideload mode. But remember that sideloading the OS is a slow process; so keep patience and do not remove cable in the middle of installation otherwise your device will be bricked.)
4) Now, lock the bootloader from the command in fastboot mode:
fastboot oem lock
after entering the command in fastboot mode, a confirmation will be asked to lock the bootloader for Yes or No, confirm from the volume keys and let boot the phone automatically and wait to finish.
5) If you sideloaded the OOS 4.1.6 in step 3 then you will see the update notification of OOS 4.1.7 which is about 450MB, download it ,install it and reboot.
6) Enjoy............the stock
Thanks to guides on youtubes and xda site.
Please note that if you follow these steps, you will not have any issues because I have done again and again without any issues but I do not take any responsibility of bricked devices if you perform wrong method or skip any thing.
Please hit the like if find this useful, it is absolutely freeeeee.............
Click to expand...
Click to collapse
How can i find one plus 3t recovery I cant find both twrp and one plus official recovery.
I was flashing TWRP
I couldn't boot into system after flashing..
This is what I did:
1. fastboot boot recovery.img
2. Swipe to allow modifications in twrp
3. Flash TWRP installer zip
4. Reboot into partition B
5. Reboot bootloader
6. fastboot boot recovery.img
7. Swipe to allow modifications in twrp
8. Flash TWRP installer zip
9. Then I rebooted into recovery to check if recovery boots and it did.
But afterwards couldn't boot back into system. It was again booting into recovery.
I booted into recovery using fastboot boot, that's why it might won't boot into system. Is there a command to boot into system after above procedure?
Files used: https://m.youtube.com/watch?v=tRcYUMBgvaI
? How to Root Mi A1! Unlock Bootloader, TWRP Recovery ... - YouTube
By Dhananjay Bhosale
Kindly also suggest source of files you used, if you know another working method.
I have the same problem. Meanwhile, flash the stock fastboot images.
Why do you want to have TWRP installed? I am following these steps each month (fastboot ROM was always out sooner than my OTA) without any issues.
1. flash stock ROM via fastboot
2. fastboot boot twrp-3.1.1.img and don't allow system modifications or you won't be able to apply OTA
3. install magisk 15.1
4. reboot to system
If first boot takes more than 2-3 minutes, hold power off button until phones restarts, second start will take the usual time.
I also don't allow any modifications from TWRP, and just boot to TWRP when I need to. I do not install TWRP.
Sounds like you'll have to do a miflash of the rom, then try not installing TWRP and not allowing any modifications in TWRP to system. Just use TWRP to flash Magisk.
Hi everybody
I come back on my concern to root my Xiaomi Mi 9T under miui 11.0.3.
I managed to root it by installing the magiskmanager.zip by the recovery twrp.
Here are the manips that I made via fastboot.
-Fastboot devices
-fastboot flash recovery twrp.img
I restart in the recovery manually because doing fastboot reboot recovey twrp.img it does not work.
So I install magiskmanager.zip
All is well for the moment I am rooted at startup.
May the worry is that the recovery does not stay when I restart in recovery mode I fall on the original one.
So suddenly I redo everything from the beginning and in magiskmanager I do the direct installation (recommended) and I download the app twrp on the playstore.
I download the twrp that offers and the flash via the application twrp and there surprise I restart recovery twrp mode.
Bizarre all these manipulations before it was much simpler.
Tell me if I made mistakes during my manips.
Sorry about the novel ...
Thanks for reading me
Use instructions from thread "root without twrp". Did that a few days ago and there was not a single issue. You can flash twrp (I used official) at the beginning via fastboot and you good to go.
Making long story short:
Unlock bootloader, flash twrp, flash ROM, install magisk manager, flash boot.img use magisk manager to patch boot and you got it