Related
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Root works with supersu version 2.62-3. Thanks
sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.
i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???
Try nexus root toolkit.
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device
Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562
dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.
i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.
Hi guys, I did the safe upgrade on my DevEd from 5.1.1 to 6.0.1. TWRP 3.0.2-0 starts up correctly. Then I try to choose any zip file to flash and TWRP immediately restarts itself instead of flashing it. Did I do something wrong with this upgrade, and why can't I flash anything using TWRP?
Well for anyone who reads this, I found the solution. By default, I can't use my external SD card for anything. Once I copied the files to the internal SD I was able to flash things.
Also it seems that I had to root the device first by forcing SuperSU to flash using FlashFire before it was going to accept any flashes, I don't think TWRP specifically requires you to have Android rooted but probably it set up directories or permissions or something by doing that.
FMXP said:
Well for anyone who reads this, I found the solution. By default, I can't use my external SD card for anything. Once I copied the files to the internal SD I was able to flash things.
Also it seems that I had to root the device first by forcing SuperSU to flash using FlashFire before it was going to accept any flashes, I don't think TWRP specifically requires you to have Android rooted but probably it set up directories or permissions or something by doing that.
Click to expand...
Click to collapse
wow 2 days messing around with this. man oh man thank you for the find.
works great!
I am rooted and unlocked still on 5.1.1 I updated to MM bootloader was unlocked after I updated but couldn't get root with the NewKingRoot app. It didn't give me the option to root. I also tried KingOroot and it failed also. When I was on MM when I rebooted my device I didn't see the custom lock icon on the splash screen but when I booted to download mode it said Mode developer. I work so much I can only spend a few hrs a day working on this. I would however rather go back to 4.4.4 I really miss kitkat.
Sent from my SM-N920F using Tapatalk
Having the same problem. I finished Bootloader Unlock and Upgrade to Marshmallow and now sitting on unrooted with recovery 3.0.2-0. I was rooted but one of the things I tried is a factory reset, Just throwing anything at it to see if it sticks.
ANYWAY If I try to flash supersu it starts listing activity. Gets to "creating space" phone immediately crashes when that displays with a vibration and can't turn phone back on without a battery pull. I have reflashed twrp via odin. I've tried flashing supersu from both internal and external card. No joy. I also tried checking mount system. It will crash with setting default off. Anyone have any ideas on what could be the problem?
My guess is it's something I'm not thinking and if I get a fix before anyone post I post it.
edit:
Well I could never get it to flash supersu but I did restore the Jasmine 7.0 backup. So that worked.
I bought my 5X in October and came here to root my phone and be able to use the ElementalX and the Advanced Interactive Governor tweaks.
Everything was working fine and my phone really performed outstandingly.
Then I saw the OTA 7.1.1. popping up. I didn't allow it until I installed it by mistake yesterday...
Now I'm stuck with google asking me to lock the bootloader.
I can access the bootloader. I get a lot of options.
I can access the recovery mode and it gets me to RecoveryProject 3.0.2-2 by Teamwin.
I already have the Android platform tools on my desktop and it's working.
From there I have 2 questions :
1. Is there a way to not wipe all the contents on my phone? I didn't get the chance to backup all the data on it.
2. After that how can I get my phone working with the latest android version as I was before, unrooted and running with EX Kernel Manager.
Thanks for your help.
1. try installing the supersu zip from the recovery
2.EX Kernel Manager cannot work without root. so you need to root your device
Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
2. I meant rooted sorry. So my phone is already rooted and I'm fine with staying that way.
Enzoli said:
Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
Click to expand...
Click to collapse
yes
you can actually backup you device from TWRP recovery.
flash the supersu zip and you will boot normally without any data lose
Insane! thanks a lot.
One more noob question. I got the latest superSu zip.
How can I flash it from the recovery?
How can i transfer it to the phone?
Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP
Enzoli said:
Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP
Click to expand...
Click to collapse
adb sideload from twrp
OK guys thanks. When I use adb sideload in twrp advanced menu it gets stuck on "Starting ADB sideload feature... "
And when I type ADB devices on the command prompt it does not show my device but if I'm just in the menu before sideload it does find my device and says the serial number + recovery.
What am I doing wrong?
Thanks for helping.
You should be able to transfer files while being in recovery using MTP mode.
How do I use MTP mode? Sorry what does that mean. Can't find an explanation on the internet.
I've looked at all the options in the menu but can't find such a option.
I really feel stupid.
Ok guys I transfered SuperSu to my phone using adb push.
I flashed my phone with SuperSu but when i reboot my phone, it still tells me I need to lock my bootloader.
What shall I do now?
I keep going to the Googl screen with the little locker and then I reach the No Command screen.
The phone won't boot into Android no more. Guys please help I'm desperate. Is my phone dead?
Ok so I guess my phone is now in bootloop.
Still anyone willing to help?
OK I tried many things in despair and now I cannot enter the recovery mode anymore. It just gets stuck on the teamwin screen.
Guess it's time to buy a new phone.
So miracle I could enter the recovery.
Now I don't know where to go. I would like to be able to enter normal android but my phone will keep on showing android screen with little lock and the end on the No command screen. Endlessly.
Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.
...
Enzoli said:
Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.
Click to expand...
Click to collapse
If you ever need help on updating your software to the latest Android version, follow my guide as a reference:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
Hi,
I understand this is probably a common problem with a simple fix, but this is my first attempt to root. My phone is unlocked and s-off, running 3.37.605.7. I used TWRP to install SuperSU and then after rebooting, it was stuck in a bootloop. After doing some research I think maybe I installed the wrong version of SuperSU, but I can't figure out how to fix it. I did a backup with adb beforehand, but when I tried restoring it said to unlock my phone and confirm, and I can't unlock my phone. I tried doing the restore command with TWRP open and it seemed to do something at first, but then nothing. I'm really stuck and would appreciate some help.
Thanks!
Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?
RoyalDrew said:
Are you wanting to keep the data you have on the phone or, would you be OK with starting fresh?
Click to expand...
Click to collapse
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.
jrzee45 said:
I'm fine with losing data. Actually I just flashed the RUU again and it's working again. I'll try to root again later.
Click to expand...
Click to collapse
After you get TWRP back, flash View attachment BETA-SuperSU-v2.65.zip to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.
RoyalDrew said:
After you get TWRP back, flash View attachment 4082602 to get root.
I just went through the same mess as you with the newer SuperSu versions. I read somewhere that 2.65 was the latest that would work and this is the zip I used.
Click to expand...
Click to collapse
Just flashed 2.65 and it worked! Thanks so much.
Unable to boot
Anyone having issues with this ROM. I flashed using TWRP 2.8.7.0, S-OFF and Unlocked, after flashing, phone reboots into aboot and i select reboot, and it rebots to aboot again without booting to the rom.