Related
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-developer-os-images
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Hi there,
my shield is on stock now with several apps on it.
How can I flash without losing my data? Is it enough to NOT flash the userdata?
THX
Chaos
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
BillTheCat said:
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-open-source
Click to expand...
Click to collapse
I have a question, where do you find pre-root load in below link?
I only find Open source and recovery image.
you mean to modify Open source and build pre-root load?
https://developer.nvidia.com/shield-open-source
https://developer.nvidia.com/shield-developer-os-images
BillTheCat said:
https://developer.nvidia.com/shield-developer-os-images
Click to expand...
Click to collapse
thanks
hardwarechaos said:
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
Click to expand...
Click to collapse
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
hardwarechaos said:
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image
Click to expand...
Click to collapse
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Hi
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
IMHO if you have adb root there should be a way to install it via adb too, but I could not find one and didn't want to mess around with installing the SuperSU files manually.
THX
Chaos
hardwarechaos said:
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
Click to expand...
Click to collapse
Agreed - turns out the Dev images are no real benefit. I found that installing TWRP, rebooting the bootloader, entering recovery and then flashing SuperSU works like a champ.
Anyone else having trouble flashing system and userdata? Keeps saying FAILED (Remote: data too large)
BillTheCat said:
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Click to expand...
Click to collapse
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
jweaks said:
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
Click to expand...
Click to collapse
Yes it will kill amazon video.
BillTheCat said:
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Click to expand...
Click to collapse
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
dillfever said:
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
Click to expand...
Click to collapse
can close this got er all done.......dill
hardwarechaos said:
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
Click to expand...
Click to collapse
Hello,
Same result for me.
I've just received my Shield, I've followed the instructions given on the developers web page. I have an up-to-date 3.0.0 version, but applications don't have the root authorisations (tested with ES File Explorer).
I think I'll use the TWRP method...
i download 3.0 rooted version it came a zip with all files on it on nvidia shield.com tutorial said just ento bootloader and type comand flash-all.bat and gualahhh! but try like 1000 times and always said null error message and force close adb
can some one tell what im doing wrong please and thanks people!
bye the way gamestop its selling shield tv for 100bucks so for those who want another its the right time to get one
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
dismissthesky said:
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
Click to expand...
Click to collapse
to remove zulu rom this is easy.
just go to nvidia site and get the complete factory images for your shield.
it will come with a guide on how to flash your shield with them.
it will delete everything in your shield and it will be stock like brand new.
then you can root it if you want or install a different rom.
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Just restore your backup ... you should already make one before you tried to root it.
Post here fastboot getvar all result without serial & imei no then we'll see what you need.
ChiefMustardo said:
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Click to expand...
Click to collapse
When I helped you previously, I had to advise you to provide the proper details. So why are you repeating the same mistakes here? You need to help us help you, by posting the proper details.
In addition to the getvar output requested by ckpv5, what versions of SuperSU did you use? "Much newer version" doesn't really tell us anything (at least not specific enough for us to help you).
Your current firmware version greatly affects what version TWRP and SuperSU you need to use to avoid problems that you mentioned (no boot). So we can't begin to properly help, until you provide the proper info.
Additionally, you started another thread asking same/related questions. I won't respond to that thread, as making multiple threads (for related issues) is confusing and will only cause more problems (such as hopping back and forth between the threads). Bump your existing thread, if you have to (and asking subsequent questions in that existing thread is an acceptable way of doing that). But please don't make more threads. I have some input on the specific questions you asked in the other thread:
ChiefMustardo said:
Can someone please explain to me why when i use twrp or cwm no ROM installs and the md5 check fails as does the signature verification and it says that the zip file is corrupt. It isn't because i got it from the skydragon website.
Click to expand...
Click to collapse
Can't say for sure why TWRP is failing, until you provide the getvar info. It can be a mismatch between your current firmware and the TWRP version. But we have no way of telling, unless you provide the requested details.
And are you trying to use multiple TWRP versions, or just the one mentioned? And BTW, there is no TWRP 3.2.0, so I assume you mean 3.0.2, but please confirm.
Also, I would avoid CWM, as it hasn't been updated in a very long time, which can create a lot of issue in itself.
What is the exact file name, or Skydragon version of the ROM you are trying to install (also very important)?
Just because you downloaded from Skydragon website, does not exclude the possibility the file is corrupt. A perfectly working file can get corrupted during download to your phone/computer. Try downloading twice, to eliminate that as a possibility.
You should also turn off MD5 verification in TWRP; which is probably causing the MD5 error (as mentioned by dottat here). MD5 check typically not used for ROMs (particularly if there was no MD5 hash code supplied with the ROM).
Here is my fastboot getvar all
http://prntscr.com/bd24cj
ChiefMustardo said:
Here is my fastboot getvar all
http://prntscr.com/bd24cj
Click to expand...
Click to collapse
It was also the SuperSU 2.46
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
Skydragon: SkyDragon+M8+v4.0.0+Sense+8+MM
TWRP: twrp-3.0.2-0-m8
Philz touch: philz_touch_6.26.6-m8
1. You used wrong TWRP recovery 2.7.x.x that make your version-main now empty.
2. You installed wrong SuperSU - 2.46 is NOT for Marshmallow.
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
I suggest you revert to stock first then redo the whole thing ... rooting or installing a custom ROM, these you can do later after you fix your phone.
Read this for the drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
And this for installing RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
That version is really old, released about Feb 2015!
SuperSU 2.65 is recommended. Anything older than 2.52 or so does not include the ability to root MM, and will fail with no boot/boot loop.
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
ckpv5 said:
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
Click to expand...
Click to collapse
That is true, its not clear what the OP is currently trying to accomplish. This thread started out asking about root (stock ROM?) than started another thread asking about custom ROMs.
Its one or the other, not both (root vs. custom ROM) since as you mention, custom ROMs are already rooted.
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
ChiefMustardo said:
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
Click to expand...
Click to collapse
Just kill the process, and start it again. This is a reported issue for some folks.
If the issue reoccurs, we may have to look at USB connection issues.
Are you using the RUU zip method that ckpv5 directed in Post #7 above?
The RUU method you have suggested seems like it isworking.
The RUU worked thank you so much. Now to install SkyDragon ROM.
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked. It is on Optimizing 44 of 153
ChiefMustardo said:
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked.
Click to expand...
Click to collapse
The .exe is finicky. Anything but Windows 7 and USB 2.0 can cause problems with its USB connectivity. The zip method is more reliable (as you've seen).
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
ChiefMustardo said:
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
Click to expand...
Click to collapse
Read again : http://forum.xda-developers.com/showpost.php?p=67197327&postcount=7
Clearly stated :
ckpv5 said:
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
Click to expand...
Click to collapse
OK thanks. Do I not require s-off then?
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
ChiefMustardo said:
OK thanks. Do I not require s-off then?
Click to expand...
Click to collapse
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
ChiefMustardo said:
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
Click to expand...
Click to collapse
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
redpoint73 said:
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
Click to expand...
Click to collapse
I am using the skydragon ROM (latest for Marshmallow) but in the zip the only file there is system. It also skips the MD5 check and has a progress bar for a bit and then comes up with the corrupt zip message.
Hey, been a while I visited here though but this site has always been my first call when I have issues with my Android.
Kindly help me. I have this m8 intl ver. running marshmallow and I have been trying to use kingroot to root the phone but all the versions I have used so far couldn't get the job done. I am inaccessible to a computer. Although I once used kingroot long time ago when the phone was running lollipop and it worked. After I upgraded the OS to 6.0, the kingroot didn't work.
If kingroot doesn't work, I don't think you have any choice but to use a PC to unlock the bootloader, etc.
Even if you don't personally have a PC, surely a friend or family member has one, they will let you use for an hour or so? Buy them a 6 pack or something, for the privilege.
Well, thank you. I already unlocked the bootloader. And I thought about that options you gave me but the 1hr on a PC is what I don't have. So I have no choice now but to create that 1hr. Thank you.
tunnex190 said:
Well, thank you. I already unlocked the bootloader. And I thought about that options you gave me but the 1hr on a PC is what I don't have. So I have no choice now but to create that 1hr. Thank you.
Click to expand...
Click to collapse
If your bootloader is unlocked, then you don't need a PC. Do you have TWRP installed? There are ways to flash it without a PC (from SD in hboot) if you don't. If you already have TWRP then flash SuperSU with it or a rooted ROM (most M8 ROMs are rooted).
I used to have a TWRP.zip that was flashable from extSD, but I've deleted it from my DropBox. If you need one I could make another
xunholyx said:
If your bootloader is unlocked, then you don't need a PC
Click to expand...
Click to collapse
To install an unsigned zip, needs S-Off.
ckpv5 said:
To install an unsigned zip, it needs S-Off.
Click to expand...
Click to collapse
I never even thought of it being unsigned, but of course you can't. With my HTC devices I have went S-Off soon after getting them, so I was thinking to myself "yeah, I've done that after an RUU"
Thanks for clearing that up.
Thanks guys but the phone is s-off already and unlocked bootloader. And how can I install this twrp? I remembered I did flash twrp-2.8.7.0-m8.img during a time when I was upgrading to Marshmallow; if that's kind of twrp you were talking about? Kindly tell me the way to go about it
tunnex190 said:
Thanks guys but the phone is s-off already and unlocked bootloader. And how can I install this twrp? I remembered I did flash twrp-2.8.7.0-m8.img during a time when I was upgrading to Marshmallow; if that's kind of twrp you were talking about? Kindly tell me the way to go about it
Click to expand...
Click to collapse
It's something like this - http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
You put the 0P6BIMG.zip on root of your microsd, then reboot to hboot. System will scan and ask you to update, volume up to update. Once finish, reboot .. you have TWRP 3.0.2-0 already installed.
Then download SuperSU.zip.
Boot to recovery (TWRP) - select install SuperSU.zip - done, now your device is rooted.
If you want me to edit the OS no. to fit your current software version, let me know what it is then I make a new one for you and upload here.
tunnex190 said:
Thanks guys but the phone is s-off already and unlocked bootloader.
Click to expand...
Click to collapse
That is a lot of info that should have been supplied in the top post.
First its an unlocked bootloader, you didn't tell us about. Now its s-off, that you didn't tell us about.
I already thought of the method to flash TWRP by zip with SD card method; but realized that you need s-off to do so.
When someone asks how to root, and doesn't give any details; the assumption I would make is that the phone is not previously modified.
I assume the phone was modified by a previous owner? Again, a detail that should have been supplied from the beginning.
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
xunholyx said:
I never even thought of it being unsigned, but of course you can't. With my HTC devices I have went S-Off soon after getting them
Click to expand...
Click to collapse
I was about to post about the SD card flashable TWRP zips that have been posted around here. But then, I realized that you need to be s-off.
I'm normally of the opposite mindset, especially since the introduction of sunshine; I assume that users are s-on unless they indicate otherwise.
redpoint73 said:
That is a lot of info that should have been supplied in the top post.
First its an unlocked bootloader, you didn't tell us about. Now its s-off, that you didn't tell us about.
I already thought of the method to flash TWRP by zip with SD card method; but realized that you need s-off to do so.
When someone asks how to root, and doesn't give any details; the assumption I would make is that the phone is not previously modified.
I assume the phone was modified by a previous owner? Again, a detail that should have been supplied from the beginning.
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
I was about to post about the SD card flashable TWRP zips that have been posted around here. But then, I realized that you need to be s-off.
I'm normally of the opposite mindset, especially since the introduction of sunshine; I assume that users are s-on unless they indicate otherwise.
Click to expand...
Click to collapse
I'm sorry It escaped my mind to tell all of this. I actually modified the phone myself. It was a brand new then, I'm the first owner.
Do I just need to flash superuser through hboot recovery now?
ckpv5 said:
It's something like this - http://forum.xda-developers.com/showpost.php?p=67526388&postcount=387
You put the 0P6BIMG.zip on root of your microsd, then reboot to hboot. System will scan and ask you to update, volume up to update. Once finish, reboot .. you have TWRP 3.0.2-0 already installed.
Then download SuperSU.zip.
Boot to recovery (TWRP) - select install SuperSU.zip - done, now your device is rooted.
If you want me to edit the OS no. to fit your current software version, let me know what it is then I make a new one for you and upload here.
Click to expand...
Click to collapse
Thanks I assume I have installed the twrp version twrp-2.8.7.0. Hope it can get the work done by flashing SuperUser through twrp recovery?
tunnex190 said:
Thanks I assume I have installed the twrp version twrp-2.8.7.0. Hope it can get the work done by flashing SuperUser through twrp recovery?
Click to expand...
Click to collapse
If you already have TWRP 2.8.7.0 - don't accept root offer by that TWRP version (won't work on Marshmallow) but download the latest SuperSU zip and install it in recovery.
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
If you wish to update the TWRP to version 3.0.2-0 or later, just download the TWRP.img then in current TWRP you can select Install and select image then select the TWRP.img and select recovery then install.
Thanks. I downloaded the flashable Zipped Superuser from the link you gave. And since you said the older version of TWRP I'm running won't accept root offer, I bet upgrade it then and use it to flash the SuperUser. Do you have a link to download the latest twrp.img?
tunnex190 said:
Thanks. I downloaded the flashable Zipped Superuser from the link you gave. And since you said the older version of TWRP I'm running won't accept root offer, I bet upgrade it then and use it to flash the SuperUser. Do you have a link to download the latest twrp.img?
Click to expand...
Click to collapse
I didn't say the TWRP won't accept root offer .. I said you don't accept root offered by TWRP because that SuperSU offered by TWRP is old version and won't work on Marshmallow.
No problem to use that version TWRP to install latest SuperSU.zip
https://dl.twrp.me/m8/
ckpv5 said:
I didn't say the TWRP won't accept root offer .. I said you don't accept root offered by TWRP because that SuperSU offered by TWRP is old version and won't work on Marshmallow.
No problem to use that version TWRP to install latest SuperSU.zip
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
can you help me with latest flashable TWRP zip? I downloaded the .img but then I realize I would need PC to flash it.
ckpv5 said:
I didn't say the TWRP won't accept root offer .. I said you don't accept root offered by TWRP because that SuperSU offered by TWRP is old version and won't work on Marshmallow.
No problem to use that version TWRP to install latest SuperSU.zip
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
can you help me with latest flashable TWRP zip? I downloaded the .img but then I realize I would need PC to flash it. Or is there other way to install the .img because I couldn't locate it when I entered twrp recovery
tunnex190 said:
can you help me with latest flashable TWRP zip? I downloaded the .img but then I realize I would need PC to flash it.
Click to expand...
Click to collapse
You don't really read what I already posted before. I gave you two options earlier.
1. If you need the flashable zip - you need to give me your OS no.
or
2. Put the downloaded TWRP.img on root of your sdcard. In TWRP select install, below you'll see menu install images, select that, then browse to your downloaded TWRP.img then install. It will ask that image is for recovery or boot, select recovery .. install, done.
ckpv5 said:
You don't really read what I already posted before. I gave you two options earlier.
1. If you need the flashable zip - you need to give me your OS no.
or
2. Put the downloaded TWRP.img on root of your sdcard. In TWRP select install, below you'll see menu install images, select that, then browse to your downloaded TWRP.img then install. It will ask that image is for recovery or boot, select recovery .. install, done.
Click to expand...
Click to collapse
Really I am sorry to bother you. I would prefer option 1. Here's the OS no: 6.12.401.4.
tunnex190 said:
Really I am sorry to bother you. I would prefer option 1. Here's the OS no: 6.12.401.4.
Click to expand...
Click to collapse
Attached .. how-to, read back my earlier post.
Thank you all. Everything went well. I'm grateful
I am considering buying S7 Active, and I have a question about rooting.
I will buy one on ebay, I'm not sure which firmware it will be on.
What is the latest rom that can be rooted, and how can I download that rom? There is no combined guide and it is a little confusing. Once I root my phone I usually use it until I replace my phone, so I would like to get to the latest.
Also how do I root the phone? Do I still need to follow the post?
https://forum.xda-developers.com/s7-active/help/samsung-galaxy-s7-active-root-t3473649
Thank you in advance!
all version are rootable...
that link althou starts out as links to android 6... ends up on 7 at around #700
there is no recovery like twrp,.. but yes they all got root ....
if not follow rom modder thread tut, up to flashfire if you only want root
miniminus said:
all version are rootable...
that link althou starts out as links to android 6... ends up on 7 at around #700
there is no recovery like twrp,.. but yes they all got root ....
if not follow rom modder thread tut, uo
p to flashfire if you only want root
Click to expand...
Click to collapse
Thank you for the reply.
I couldn't understand some parts of your comment... So the latest firmware is still rootable using the method in the above link? Then how can I obtain and flash the latest firmware? I'll not use the phone on AT&T.
Also I couldn't understand the last line of your comment... what did you mean?
think its oulined in the main thread you posted ...
but use this site ..
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/
which has all the 'update' zips, of which you can use in normal stock recovery and load up via memorycard
is a slow process, and wipes everthing (you can stop it before it does, but you gotta be ready, so make backup anyhows !!)
miniminus said:
think its oulined in the main thread you posted ...
but use this site ..
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/
which has all the 'update' zips, of which you can use in normal stock recovery and load up via memorycard
is a slow process, and wipes everthing (you can stop it before it does, but you gotta be ready, so make backup anyhows !!)
Click to expand...
Click to collapse
Thank you for the link! QF2 seems to be the most recent one. I will follow the steps when I get the phone.
EDIT: someone said QF2 is not rootable yet... is it still the case? Then I may have to go for QE1.
well people had issues at the start, as i think they was not using the most recent (2.82) root methods...
but people on the Ufirm Rom modder thread ARE rooted on QF2...
miniminus said:
well people had issues at the start, as i think they was not using the most recent (2.82) root methods...
but people on the Ufirm Rom modder thread ARE rooted on QF2...
Click to expand...
Click to collapse
Ummmm... sorry but what is the 2.82 root method? Is it different from the above method?
2.82 is the newest version of SuperSU which provides you root privileges, and thus the version of 'root.bat' that you run (on your PC with phone connected, with ADB USB debugging enabled in Developer mode)
AFTER you flash the Eng.Boot file (teh engineering boot image that you flash with Odin, while phones in 'download' mode)
miniminus said:
2.82 is the newest version of SuperSU which provides you root privileges, and thus the version of 'root.bat' that you run (on your PC with phone connected, with ADB USB debugging enabled in Developer mode)
AFTER you flash the Eng.Boot file (teh engineering boot image that you flash with Odin, while phones in 'download' mode)
Click to expand...
Click to collapse
Thanks. The post explains based on 2.76, I should do some research how to do that with ver 2.82 when I get the phone.
TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
DiamondJohn said:
Please let me know if it works for you?
Click to expand...
Click to collapse
No-one has tried it?
Works like a charm for me
Worked like a charm here.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Works great so far, just about to try a lineage rom.
DiamondJohn said:
TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
Click to expand...
Click to collapse
Will keep you posted.
For anyone wanting to try this just a pointer. This isn't a TWRP flashable zip so you will need to use your computer to extract the IMG file and sideload using fastboot. Working great so far.
Does this require an unlocked bootloader? I am rooted.
---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------
DiamondJohn said:
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Click to expand...
Click to collapse
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
DragonFire1024 said:
Does this require an unlocked bootloader? I am rooted.
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
Click to expand...
Click to collapse
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
DiamondJohn said:
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
Click to expand...
Click to collapse
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
It appears it was just me
I re-flashed my bootloader upgrade CAREFULLY via fastboot, and the error on wiping cache disappeared. however, I still haven't been able to flash a bootable KKBL ROM. It was suggest via PM that I also wipe my internal SDCard, which I have yet to try.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
mr3p said:
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
Click to expand...
Click to collapse
I see the posts saying it works, but has anyone actually successfully flashed and booted (ie past the bootanimation ) any ROM Zip file using this recovery?
Or performed a backup and restore?
I ask this as I finally got around to creating an upgrade (from JBBL to KKBL) for my phone (an xt905 not an xt907) and the two ROMs I tried both boot looped on the bootanimation. Also, I get errors when i try to wipe my cache.
Is it just me?
-----edit-----
I got a PM saying that someone has managed to flash an LP ROM for KKBL using this recovery. So obviously I need to go back to the drawing board on my upgrade to KKBL...
I am considering adding PDS (ie FSD) backup to my TWRP builds see https://forum.xda-developers.com/showpost.php?p=74136332&postcount=9 it also applies to KKBL.
DragonFire1024 said:
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Click to expand...
Click to collapse
The boot loader has to be unlocked because of the nature of the boot loader itself. I ain't no expert, but based on my understanding and what I personally know, here is what a boot loader does:
A boot loader checks the various images (recovery, boot, radio, etc.) and if any of these are incorrect/unsigned (like a custom recovery), your device won't boot. This makes sense, because most users aren't flashing their devices, so when an image is unsigned something is VERY WRONG. Unlocking a boot loader basically turns off the signature check that the boot loader does. If the boot loader isn't checking each image than it will boot up fine whether you have a custom recovery or not.
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
DragonFire1024 said:
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
Click to expand...
Click to collapse
Easy is a relative scale to the person asking the question. Read and answer it for yourself. TWRP builds are muuuuuch simpler than ROM builds.
The following two may mean you do not have to build. I have never used them, as I built mine from source.
https://forum.xda-developers.com/android/general/unofficial-twrps-devices-source-code-t3833338
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
https://forum.xda-developers.com/showthread.php?t=1943625
The question may also be better asked, after reading, in the thread above