Related
hi guys,i need your help,i search for this but i don't find nothing,after last update from asus i decide to root my device and put custom rom,but can't find any method to root my device,i tried unlockroot and not work,thank's in advance
You can't root it yet. This is what I did:
1. Flash 9.2.1.17 using nvflash (look in this forum, there are threads on page 1 or 2)
2. Install OTA rootkeeper and backup the root using it
3. Update to 9.2.1.17 through the update notification
4. Restore root using OTA rootkeeper
5. ???
6. Profit
mariox26 said:
hi guys,i need your help,i search for this but i don't find nothing,after last update from asus i decide to root my device and put custom rom,but can't find any method to root my device,i tried unlockroot and not work,thank's in advance
Click to expand...
Click to collapse
Was able to root 9.2.1.21 using Wolf's ultimate flash and downgrade guide .
That guide needs to be stickied at the top of the thread list as it would've definitely helped avoid similar frustration for new TF101 owners like myself. The current ICS rooting references guide scattered around the forums are outdated.
k,i will try your sugestion,thank's.
i try the wolf's but adb is telling me not recognize the command,i tried outher thing to put tablet in apx but when i start download bat is commig up command prompt after is closing,no hope
You probably need to reinstall ADB using the latest Android SDK with latest platform tools installed.
1. Ensure USB debugging is enabled in the tablet
2. Install the correct drivers from Asus and install Asus Sync to ensure you get a proper connection. You can verify connection with cmd "ADB devices" and you should see your device with serial #
3. Follow whatever Wolf's method applies to you. I used Method 3 since it was an unrooted TF101 tablet.
I just did this last night...
1) nvflash back to 9.2.1.17 (my TF101 is B60)
2) use vipermod - root(option 1)
3) Install Voodoo OTA root keeper (press backup/keep root)
4) install recovery installer apk (by guever)
5) flash update 9.2.1.21 update zip (by lizard)
6) restore root using via rootkeeper.
7) somehow my root was not properly restored. setCPU, rootExplorer work fine but titaniumBackup failed for insuficient root access. (this was due to su is not present in system/xbin)
8) no worry... flash root superuser 3.0.7 zip via CWM (by Wolf)
9) finnally clean 9.2.1.21 with Root and CWM running like heaven!!
10) these guys (vipermod, guever, lizard, Wolf) are legends!!
farsight73 said:
I just did this last night...
1) nvflash back to 9.2.1.17 (my TF101 is B60)
2) use vipermod - root(option 1)
3) Install Voodoo OTA root keeper (press backup/keep root)
4) install recovery installer apk (by guever)
5) flash update 9.2.1.21 update zip (by lizard)
6) restore root using via rootkeeper.
7) somehow my root was not properly restored. setCPU, rootExplorer work fine but titaniumBackup failed for insuficient root access. (this was due to su is not present in system/xbin)
8) no worry... flash root superuser 3.0.7 zip via CWM (by Wolf)
9) finnally clean 9.2.1.21 with Root and CWM running like heaven!!
10) these guys (vipermod, guever, lizard, Wolf) are legends!!
Click to expand...
Click to collapse
This sounds great, I am on 9.2.1.21 using CWM and my Transformer can't be detected in Windows in order to nvflash back to .17. If anyone has any suggestions that I can try please let me know. btw I no longer have a recovery, just Android on his back with red triangle exclamation mark
joefloater said:
This sounds great, I am on 9.2.1.21 using CWM and my Transformer can't be detected in Windows in order to nvflash back to .17. If anyone has any suggestions that I can try please let me know. btw I no longer have a recovery, just Android on his back with red triangle exclamation mark
Click to expand...
Click to collapse
Importantly your TF101 must be B60 or below... At B70 or above, nvflash will not work.
Preparing to nvflash..
1. Connect cable to computer and turn device ON while holding Volume Up. Screen will stay off, but USB will come on.
2. Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the extracted nvflash.zip
3. Run download.bat (windows)
4. Wait it to finish and it will reboot into a virgin 9.1.2.17 stock...
But if you know cmd and linux commands.. Use Wolf's guide in general thread to put your way back on track...
mine it is B80 and not working nvflash,any chance to downgrade to .17?
Yes, someone already linked you once.
http://forum.xda-developers.com/showthread.php?t=1622628
And btw this is the development area, not Q&A.
farsight73 said:
I just did this last night...
1) nvflash back to 9.2.1.17 (my TF101 is B60)
2) use vipermod - root(option 1)
3) Install Voodoo OTA root keeper (press backup/keep root)
4) install recovery installer apk (by guever)
5) flash update 9.2.1.21 update zip (by lizard)
6) restore root using via rootkeeper.
7) somehow my root was not properly restored. setCPU, rootExplorer work fine but titaniumBackup failed for insuficient root access. (this was due to su is not present in system/xbin)
8) no worry... flash root superuser 3.0.7 zip via CWM (by Wolf)
9) finnally clean 9.2.1.21 with Root and CWM running like heaven!!
10) these guys (vipermod, guever, lizard, Wolf) are legends!!
Click to expand...
Click to collapse
Sorry, I am not quite sure what do I need to do in step 9?
If you can nvflash, just use Brk's root toolkit. I just rooted my B60 with this.
Did the exact same thing and now i'm on .21, Rooted and CWM...
Now, Can I use guevor's kernel with ASUS stock rom (9.2.1.21)?
xbs said:
Did the exact same thing and now i'm on .21, Rooted and CWM...
Now, Can I use guevor's kernel with ASUS stock rom (9.2.1.21)?
Click to expand...
Click to collapse
Yes, both guevor's and TestyMeh kernels are compatible with the stock rom. You may need to try different versions to see which one suits you best as a lot of users reported different behaviors with the same kernels.
why is not working for me nvflash?
farsight73 said:
I just did this last night...
1) nvflash back to 9.2.1.17 (my TF101 is B60)
2) use vipermod - root(option 1)
3) Install Voodoo OTA root keeper (press backup/keep root)
4) install recovery installer apk (by guever)
5) flash update 9.2.1.21 update zip (by lizard)
6) restore root using via rootkeeper.
7) somehow my root was not properly restored. setCPU, rootExplorer work fine but titaniumBackup failed for insuficient root access. (this was due to su is not present in system/xbin)
8) no worry... flash root superuser 3.0.7 zip via CWM (by Wolf)
9) finnally clean 9.2.1.21 with Root and CWM running like heaven!!
10) these guys (vipermod, guever, lizard, Wolf) are legends!!
Click to expand...
Click to collapse
For step 1-4, after I finished, shouldn't I be able to use setcpu and overclock my tab? Why is my maximum clock speed still 1000 mHz?
How can I overclock it? Thanks
farsight73 said:
4) install recovery installer apk (by guever)
7) somehow my root was not properly restored. setCPU, rootExplorer work fine but titaniumBackup failed for insuficient root access. (this was due to su is not present in system/xbin)
Click to expand...
Click to collapse
4) RecoveryInstaller apk is actually by Gnufabio
7) OTA Rootkeeper only restore full root when you do an OTA update. If you manually update, OTA Rootkeeper will not install su to system/xbin in most cases.
You'll have to manually copy su from system/bin to system/xbin
therock9 said:
For step 1-4, after I finished, shouldn't I be able to use setcpu and overclock my tab? Why is my maximum clock speed still 1000 mHz?
How can I overclock it? Thanks
Click to expand...
Click to collapse
No because you still have not installed any OC kernel up to this point.
farsight73 said:
I just did this last night...
1) nvflash back to 9.2.1.17 (my TF101 is B60)
2) use vipermod - root(option 1)
3) Install Voodoo OTA root keeper (press backup/keep root)
4) install recovery installer apk (by guever)
5) flash update 9.2.1.21 update zip (by lizard)
6) restore root using via rootkeeper.
7) somehow my root was not properly restored. setCPU, rootExplorer work fine but titaniumBackup failed for insuficient root access. (this was due to su is not present in system/xbin)
8) no worry... flash root superuser 3.0.7 zip via CWM (by Wolf)
9) finnally clean 9.2.1.21 with Root and CWM running like heaven!!
10) these guys (vipermod, guever, lizard, Wolf) are legends!!
Click to expand...
Click to collapse
I've done Step 1-4
Step 5: Are we download the update in ASUS website and flash it in CWM, this is what I did.
Step 6: When open Rootkeeper:
Superuser app is not installed
Device is not rooted
Root permission is not granted
Filesystem is support root protection
Protected su copy is not available
So I click restore root, nothing change.
Step 7: So I look at the system/bin folder, didn't seem to find su file
Step 8: So I try to go to CWM again, but it didn't let me in anymore
So basically it back to a non-rooted .21
Am I missing something?
Hmmm
mackdaddy187 said:
You can't root it yet. This is what I did:
1. Flash 9.2.1.17 using nvflash (look in this forum, there are threads on page 1 or 2)
2. Install OTA rootkeeper and backup the root using it
3. Update to 9.2.1.17 through the update notification
4. Restore root using OTA rootkeeper
5. ???
6. Profit
Click to expand...
Click to collapse
The question is, is there anyone working to root the latest build of the tf101? Even the downgrade method seems a tad elaborate...
.21 is the latest, and is rooted. Wolfs ultimate guide in transformer general forum is how I did it. Used option 3. Took me 20 minutes and that is including installation of Asus sync and adb.
If anyone is having problems with the methods described in wolfs thread, one key point is that prior to executing adb commands you have to type "adb shell" to enter shell.
Sent from my Transformer TF101 using xda premium
this may have been asked, but i'm new to the nexus 7. i rooted it right away, and put TWRP on. probably shouldn't have but i like doing nandroids. i was excited for the OTA and want to just install it since my tab got it, but it won't obviously since i've got a custom recovery (duh i should've thought of that..) and i don't want to go flashing roms yet (i like keeping everything stock right away, it's so smooth)
so my question is, is there a way to go back and flash the stock recovery somehow so i can OTA, then put TWRP back on? i can't find the stock file to fastboot flash or anything
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
kangy said:
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
Click to expand...
Click to collapse
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Alright try this.
Go to SuperSU settings and and click on Reinstall under Cleanup, it will give you a prompt and tell you it will self close and to re-install from the market. (Mine never fully uninstalled which I assume is due to it being flashed to ROM, I checked under the App manager and it only had a downgrade option so) Anywho. If it did uninstall go ahead and redownload it from the market, if it didn't check the market anyway, the Dev published and update for it to help with 4.2 multi users.
Once you get it reinstalled and/or updated from the market go back to the settings and Toggle off Enable Superuser, close the app, re-open and then re-enable superuser. You probably will want to give it a reboot at this point. (Ive restarted my device a hundred times since going to 4.2 from trying to work through the bugs. Once you restart test a root app. I used Adaway for the test. Important, if the app fails or gives an error about not having root, try again. After I went through all of those motions SuperSU was pretty slow for a while with giving root access, usually the second request from the app wakes it up. Since then though it is back to being snappy with zero lag.
Yes, the reason you can't flash TWRP through ROM Toolbox is that requires root. Once you get your SuperSU working try flashing the latest TWRP again, it should only take a few seconds to flash. Let me know how it goes, I'm subscribed to the thread. I may not be the smartest guy on XDA but you are in the same exact boat I was last night!
jayochs said:
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Click to expand...
Click to collapse
First, determine if you have root or not. Open TiBackup, if it opens correctly and you can see all your apps listed, you have root. Otherwise it will say "Failed to obtain root," and quit.
If you have root, then great. If not, you can flash the SuperSU zip in TWRP/CWM: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
I haven't tried flashing superSU, I've always flashed Superuser zip [google "superuser zip"], and then installed superSU from Play store.
Once you have root..
Go to Settings > Security and check allow installation from non-market apps, and uncheck the security feature that checks all apps for being malicious.
Then try it. If you still cannot restore apps, you might have to install them with adb.
I just updated someone's N7 to 4.2, and as usual I backed up everything in TiBackup.
Then I backed up the TitaniumBackup directory [because I had to do a full factory reset].
I then extracted all the .apk.gz files with gunzip. [in linux OR adb: $ gunzip *.apk.gz -- for windows, I suppose you would have to use 7-Zip].
Then I tried to install with pm:
Code:
for i in *.apk; do pm install $i; done
But every one was giving me an error, INSTALL_FAILED_INVALID_URI, I couldn't figure it out. Found a thread said to chmod 755 /data/local, but that did not fix it.
So what I had to do, was on my linux PC:
Code:
for i in *.apk;
do adb install "$i"
done
So I finally was able to batch install my apk files.
after that I restored all apps data.
Nandroid back ups not possible after 4.2 update
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Yordan5 said:
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Click to expand...
Click to collapse
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
mvmacd said:
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
Click to expand...
Click to collapse
NRTK 1.5.5 would not flash the 4.2 custom rom I fed it either. Just kept stalling out with errors that it could not find the zip file.
So I booted into TWRP and flashed it with no problem at all.
I also did backup in TWRP and checked everything but saw no mention that is was a Nandroid backup. How can I be sure?
i'm trying to nandroid back to a 4.1.2 nandroid i have, problem is, twrp has different directories for nandroids in 4.2 than 4.1.2...so it can't find the old nandroids and i can't find the 4.2 dir where twrp stores them now. ugh. such a damn headache for an update that it turns out i didn't want lol
Read my post below, I was having the same problem but got back on 4.1.2. You have to use the twrp explorer and relocate the twrp files since 4.2 moved them.
http://forum.xda-developers.com/showthread.php?t=1992552
Nandroid Downgrade from 4.2 to 4.1.2
Sent from my Nexus 7 using Tapatalk 2
Here's the situation:
I have a Lenovo A8-50F table. After attempting to flash a new TWRP recovery rom on it after unlocking the bootloader, I ended up with a tablet that would constantly reboot. I am attempting to fix this issue with the SP Flash Tool but I have two issues:
I don't know if the MT file is the right file for this.
You are supposed to see a red bar pass when you hit download indicating it has finished the upload and it never comes.
I have done the volume up + voume down + down and all the other combinations and at most what it produces is a 2005 error.
I have the a58p rom in zip file that I downloaded from here.
I'd like to have some help, but I'm not sure what I'm supposed to be searching for.
chicago4545 said:
Here's the situation:
I have a Lenovo A8-50F table. After attempting to flash a new TWRP recovery rom on it after unlocking the bootloader, I ended up with a tablet that would constantly reboot. I am attempting to fix this issue with the SP Flash Tool but I have two issues:
I don't know if the MT file is the right file for this.
You are supposed to see a red bar pass when you hit download indicating it has finished the upload and it never comes.
I have done the volume up + voume down + down and all the other combinations and at most what it produces is a 2005 error.
I have the a58p rom in zip file that I downloaded from here.
I'd like to have some help, but I'm not sure what I'm supposed to be searching for.
Click to expand...
Click to collapse
i also have the same problem now and have been searching for about a week now and experimenting it seems there are no tools which are compatible with our tab.. which version of sp flash tool are you using? and could you send me a link to that a58p rom
chicago4545 said:
Here's the situation:
I have a Lenovo A8-50F table. After attempting to flash a new TWRP recovery rom on it after unlocking the bootloader, I ended up with a tablet that would constantly reboot. I am attempting to fix this issue with the SP Flash Tool but I have two issues:
I don't know if the MT file is the right file for this.
You are supposed to see a red bar pass when you hit download indicating it has finished the upload and it never comes.
I have done the volume up + voume down + down and all the other combinations and at most what it produces is a 2005 error.
I have the a58p rom in zip file that I downloaded from here.
I'd like to have some help, but I'm not sure what I'm supposed to be searching for.
Click to expand...
Click to collapse
Hi, I know to recovery you Lenovo A8-50F. It's yet actually?
Thanks.
I used KingRoot (ver 4.8.2) to root my Lenovo Tab2 A8-50F Tablet.
I used KingRoot as part of a SuperTool. The SuperTool, using a batchfile script, also removed KingRoot after the tablet was rooted and then installed SuperSU.
The SuperTool (April 6, 2016 version) was created by xda's RootJunky for the Amazon Fire 7 5th gen tablet, using KingRoot and SuperSU, but it rooted my Lenovo Tab2 A8-50F Tablet, uninstalled KingRoot and installed SuperSU, all with only a couple of mouse clicks.
Even if you are already rooted with KingRoot, you can use this tool to uninstall KingRoot and install SuperSU. (Just run the tool, let it re-install KingRoot, don't run KingRoot but hit Enter on the SuperTool to then uninstall KingRoot and install SuperSU).
Lenovo Tab2 A8-50F Tablet info:
Model Number: Lenovo TAB 2 A8-50F
Android version: 5.1
Kernel version: 3.10.65
Build number: A8-50F_S000037_151023_ROW
Software version: A8-50F_151023
Hardware version; LenovoPad A8-50F
The SuperTool batch file script rooted the tablet with KingRoot and then uninstalled KingRoot and installed SuperSu.
I have since installed ES File Manager, Titanium Backup, Link2sd on the tablet. Root is totally working. Rooted with only a couple of clicks!
Just enable Developer options on Lenovo Tab2 A8-50F (by tapping tablet Build Number 7 to 10 times [Settings, About Tablet, Build Number (tap 7 to 10 times)]), enable USB debugging on Tablet in the Developer options settings.
Connect Tablet to Windows 10 with a USB data cable (I used the USB 2.0 port). When screen message on the Tablet mentions connections, make sure it is in the MTP mode.
Extract RootJunky's SuperTool Zip file to the Windows 10 desktop.
Run RootJunky's SuperTool (Amazon-Fire-5th-gen.bat) You may have to read the instructions on the pages below and install adb drivers. Pick option #6 Root. Choose Option #3: version 5.1.2. This will run a script that installs KingRoot, allows you to run it manually, and then removes KingRoot and installs SuperSU.
Press enter and KingRoot will be installed on the Tablet from the SuperTool. (approve any messages that appear on Tablet screen) Now don't touch the PC SuperTool until the Tablet is rooted.
Open KingRoot on the Tablet and run it. You may have to run KingRoot several times and the Tablet may reboot. Just keep running KingRoot until the Tablet is rooted. After KingRoot reaches 100%, then press ENTER on the PC.
The SuperTool will now uninstall KingRoot and install SuperSU on the Tablet.
Choose NORMAL SuperSU install on the Tablet when prompted. When SuperSU is installed, reboot the Tablet. Disconnect data cable.
After reboot the Lenovo Tab2 A8-50F Tablet is rooted. There will be a request by SuperSU to upgrade. Approve it. You can now install Titanium Backup, Link2sd, ES File Manager, etc. Your Tablet is rooted. As easy as that. THANKS ROOTJUNKY!!!
Info and links to Download RootJunky's SuperTool at these pages:
Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
"AmazonFire5thGenSuperTool.zip"
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool
Follow this ROM Installation Guide.
Root it with KingoRoot.
Flash patched aboot.img by typing "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7" command in Android Terminal Emulator App, I don't like to use PC.
Then download ChainFire SuperSU from GooglePlay.
On first application start it will ask to install su Binary, say Yes.
Wait about 5 minutes or until it fails…
If so, don't worry, be happy.
Reboot…
Try again.
It must ask for Root Authorization!
Continue Rebooting and tying again and again, until you see su binary installed successfully!
Now you can dance, you Switched to SuperSU
After that you can remove all KingoRoot sh**t and install SuperSU like System app in application options…
I'm still experimenting with this rom, so I'm keeping KingRoot and SuperSU apps, for reroot my device if I will reflash KDZ.
Since now we have Working TWRP…
Simply flash it via recovery.
There are two ways available : System(by system partition) and Systemless (by Repacking and flashing Modified Kernel Image)…
Google it to know more ?
(1) Download this: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
(2) Place it in /sdcard/
(3) Reboot to TWRP.
(4) Select "Install" and go to the folder where you had placed the SuperSu zip and select the zip.
(5) Swipe to confirm flash.
(6) Reboot to system.
(7) Remove kingoroot's supersu.
D_Vovan_238 said:
Follow this ROM Installation Guide.
Root it with KingoRoot.
Flash patched aboot.img by typing "dd if=/sdcard/aboot_patched.img of=/dev/block/mmcblk0p7" command in Android Terminal Emulator App, I don't like to use PC.
Then download ChainFire SuperSU from GooglePlay.
On first application start it will ask to install su Binary, say Yes.
Wait about 5 minutes or until it fails…
If so, don't worry, be happy.
Reboot…
Try again.
It must ask for Root Authorization!
Continue Rebooting and tying again and again, until you see su binary installed successfully!
Now you can dance, you Switched to SuperSU
After that you can remove all KingoRoot sh**t and install SuperSU like System app in application options…
I'm still experimenting with this rom, so I'm keeping KingRoot and SuperSU apps, for reroot my device if I will reflash KDZ.
Since now we have Working TWRP…
Simply flash it via recovery.
There are two ways available : System(by system partition) and Systemless (by Repacking and flashing Modified Kernel Image)…
Google it to know more
Click to expand...
Click to collapse
I rebooted like +10 times and still nothing. Also it doesn't ask for root authorization after reboot
Krystiannnnnn said:
I rebooted like +10 times and still nothing. Also it doesn't ask for root authorization after reboot
Click to expand...
Click to collapse
Follow this:
(1) Download this: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
(2) Place it in /sdcard/
(3) Reboot to TWRP.
(4) Select "Install" and go to the folder where you had placed the SuperSu zip and select the zip.
(5) Swipe to confirm flash.
(6) Reboot to system.
(7) Remove kingoroot's supersu.
Hello all,
This may seem like a stupid question, but I want to make sure that I know what i'm doing before I mess something up and become
So I'm running a Samsung Galaxy S5 (G900V ovbiously), and it has the tobisha emmc chip
Is the only way to gain root on Marshmallow/Nougat or whatever is by reverting to Lollipop, gaining root access, installing TWRP, and then flashing LineageOS/some ROM?
Directions For Users With CID 11 Toshiba eMMC
1. Download EMMC_11_ Root S5_QB2_PB1.zip
2. Unzip
Copy the following to your External SD card:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and the TouchWiz ROM you want to install.
3. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
4. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
5. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
6. If you do not have an External SD Card, copy the following NOW to your Internal Storage:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and whatever TouchWiz ROM you want to install.
7. Use the File Manager in the app drawer of the phone and install Apex_Lancher.apk press home button and set Apex as the default launcher.
Install Superuser.apk, Busybox.apk and SafeStrapKK.apk do not open anything yet.
8. Now Install tr_v2.apk.
Open TowelRoot and CLICK MAKE IT RAIN . It should tell you you have succeeded.
9. Now Open Superuser app and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot. You can skip doing this. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
10. Now open the BusyBox app, grant SuperSU access and install BusyBox.
11. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed) if not click "install" again, reboot phone and open SafeStrap and try to install recovery again
12. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
13. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
14. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember, you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
15. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something bad goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
16. Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
Get the needed files at https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529