Related
Hey guys, I have a 64GB stock T-Mobile Galaxy S6 that I have (somewhat) debloated and so far the battery is okay.
I've heard promising reviews about XtreStoLite G920T Pure Edition ROM.
First, I want to make a backup of the STOCK ROM I currently have, but IIRC, you cannot back it up unless you root first?
I was looking into PingPongRoot so I could go back to stock just in case anything would happen but I need to know how to back it up first.
Second, I want to install the ROM and I'm pretty sure I'm correct. Do I need Odin if I use PingPongRoot?
Third, I want to install Ktoonzes kernel as well but I don't know anything about that.
So, pretty much I need help with:
1. Backup current stock ROM before rooting
2. Root with PingPong
3. Install XtreStoLite
4. Install Ktoonzes
Also, if there is anything else I should be cautious of let me know. Thanks guys!
While all of this info is easily accessible, in the spirit of giving... Here you go.
To backup, you need root.
Install SuperSu from play store, open SuperSu at least one time, then download Ping Pong Root APK and run it. It may take two tries, that's normal.
Then, to back up, either install TWRP with Flashify (downloadable from Play Store) or via Odin (Either method will trip Knox in bootloader and void Samsung warranty, will not harm phone in any way) and back up
To install ROM, Flash in TWRP recovery (if you installed TWRP in last step Knox is already tripped)
Then, use TWRP to flash Ktoonzes kernel (I recommend letting ROM boot at least once fully then going back to recovery to flash kernel)
norcalsfinest said:
While all of this info is easily accessible, in the spirit of giving... Here you go.
To backup, you need root.
Install SuperSu from play store, open SuperSu at least one time, then download Ping Pong Root APK and run it. It may take two tries, that's normal.
Then, to back up, either install TWRP with Flashify (downloadable from Play Store) or via Odin (Either method will trip Knox in bootloader and void Samsung warranty, will not harm phone in any way) and back up
To install ROM, Flash in TWRP recovery (if you installed TWRP in last step Knox is already tripped)
Then, use TWRP to flash Ktoonzes kernel (I recommend letting ROM boot at least once fully then going back to recovery to flash kernel)
Click to expand...
Click to collapse
jeffreylin_ said:
If you don't want to void your warranty, you could back up using Chainfire's FlashFire, but note that it is an app and therefore you need to have a semi-working system to restore! Which is fine since you can flash stock using Odin, then root using PingPong and install FlashFire again. Just slightly more of a hassle.
Click to expand...
Click to collapse
Thanks guys!
jeffreylin_ said:
If you don't want to void your warranty, you could back up using Chainfire's FlashFire, but note that it is an app and therefore you need to have a semi-working system to restore! Which is fine since you can flash stock using Odin, then root using PingPong and install FlashFire again. Just slightly more of a hassle.
Click to expand...
Click to collapse
So wait... flashfire and pingpong root i can flash a new rom without tripping knox????
frettfreak said:
So wait... flashfire and pingpong root i can flash a new rom without tripping knox????
Click to expand...
Click to collapse
Yes, only if you don't flash a kernel with the new ROM. You have to edit the zip and remove the boot.IMG , then edit the updater script to remove the command to wipe and flash boot.img. if this sounds too difficult to you don't try it
norcalsfinest said:
Yes, only if you don't flash a kernel with the new ROM. You have to edit the zip and remove the boot.IMG , then edit the updater script to remove the command to wipe and flash boot.img. if this sounds too difficult to you don't try it
Click to expand...
Click to collapse
So how do you flash a custom ROM without a custom recovery? Recovery trips Knox...
I'm gonna need to look into this one. Been a while since I did anything with a Samsung device.
Marine6680 said:
So how do you flash a custom ROM without a custom recovery? Recovery trips Knox...
I'm gonna need to look into this one. Been a while since I did anything with a Samsung device.
Click to expand...
Click to collapse
I don't think chain fire has been to open about how flashfire works (not a problem his choice). So if you want a good idea how it works look into safestrap, I'm sure it's close other than the fact safestrap doesn't need a app in a working system.
ThePagel said:
I don't think chain fire has been to open about how flashfire works (not a problem his choice). So if you want a good idea how it works look into safestrap, I'm sure it's close other than the fact safestrap doesn't need a app in a working system.
Click to expand...
Click to collapse
Needs a zip without the kernel... I remember seeing a ROM that mentioned not having a kernel, I guess for this reason.
I don't think any of the t-mobile ROMs come setup like that though. So I would need to go through the trouble of repackaging the ROMs myself.
May not bother and just trip the counter and flash normal. Custom kernels are often the way to go for battery life and performance.
Marine6680 said:
Needs a zip without the kernel... I remember seeing a ROM that mentioned not having a kernel, I guess for this reason.
I don't think any of the t-mobile ROMs come setup like that though. So I would need to go through the trouble of repackaging the ROMs myself.
May not bother and just trip the counter and flash normal. Custom kernels are often the way to go for battery life and performance.
Click to expand...
Click to collapse
Oh I thought you meant how flashfire boots into its recovery mode without tripping knox, yeah custom kernels and recoveries will trip knox but if the demand is high enough there are ways to use custom kernels without flashing them and someone is bound to bring it to the s6, but I'm sure the demand has to be high enough.
ThePagel said:
Oh I thought you meant how flashfire boots into its recovery mode without tripping knox, yeah custom kernels and recoveries will trip knox but if the demand is high enough there are ways to use custom kernels without flashing them and someone is bound to bring it to the s6, but I'm sure the demand has to be high enough.
Click to expand...
Click to collapse
Its an interesting alternative to full root flashing. Preserving the warranty is good for some people.
Ever since I did pingpong root, I have been having odd issues with pandora bluetooth streaming to my car. Hopeing a custom ROM will solve this.
So, today I upgraded to 6.0 and had a hell of a time (took me 7 hours) and the problem was that when I installed su from twrp it'd soft brick my phone, anyway, that's not the problem, the problem is everything is saving to /storage/emulated and I can't access it without root. I noticed this when I was on OGInsta and I wanted to download a picture, it gave me an error code about how it couldn't find the directory, so I went to my file manager, everything was fine but I accidentally hit up instead of home and it brought me to an empty page. I started messing with the settings of my file manager assuming something went wrong with it, new version etc, and I found it had a root option. I clicked it and gave it root access and went back and I could see the files where I was previously. To make sure I tried to save something on kik, didn't work. I tried accessing my storage from the rar app and it wouldn't. I don't know what's going on or how it even got this way.
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
scryan said:
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
Click to expand...
Click to collapse
Also, to clearly, I have 2 storage paths. One is "sdcard/" and the other is "storage/emulated/0" I'm not sure if the "storage" folder is new in 6.0, I know 4.+ and 5.+ used "sdcard/". Too see "storage/emulated/0" I need to grant root access to the file manager. And any app the does not have root, cannot access that directory.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
Click to expand...
Click to collapse
you might have knowledge in making apps, but you are missing lots of knowledge when modding your phone. you are going to have to use an app like root explorer, and find where your storage was placed, then move it to the right location. or you can reflash the factory image. ive always just moved my storage back when its happened to me. anyways, flash the factory image the right way, not through a toolkit. then flash any custom kernel(if flashing marshmallow), and supersu.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat.
Click to expand...
Click to collapse
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
YoureVexing said:
So then I used adb, flashed boot.img and then recovery.
Click to expand...
Click to collapse
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
scryan said:
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
Click to expand...
Click to collapse
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
YoureVexing said:
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Click to expand...
Click to collapse
/sdcard is a simlink, its the same folder.
internetpilot said:
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
Click to expand...
Click to collapse
The rootkit wasn't working for me, it's been a charm for my nexus 5 and from 4.+ and nexus 6 on 5.+, on 6.0 it wasn't working so I tried to flash it on fastboot and I still got the same thing. I'll try it once more I suppose, thank you.
Did anyone's amazon fire tablet 7 come with 5.3.1 out of the box? What version did it come with? I am planning to buy one soon and I was wondering if anyone has bought one that had lower firmware on it? Thanks a lot!!
cyberdude020 said:
Did anyone's amazon fire tablet 7 come with 5.3.1 out of the box? What version did it come with? I am planning to buy one soon and I was wondering if anyone has bought one that had lower firmware on it? Thanks a lot!!
Click to expand...
Click to collapse
Based on self reporting the general trend seems to be 5.3.1 but you might receive any version depending on what the shipping warehouse has in stock. If you are seeking an older build (presumably 5.1.4 or lower) your best bet is a local retailer where you can check it out in the store before committing to a purchase. Turnover is often slower so better chance of scoring a 'dated' device.
Ok so my gf bought a Kindle fire for my birthday next month because I thought buy it sooner and it's more likely to have the firmware I want. I just opened it up to check the firmware before packing it away and fortunately it came with 5.1.3 out of the box. I didn't dare connect it to WiFi incase it updated lol. Just incase anyone is interested I bought this from Argos (UK) now I just need to figure out if I can downgrade and install a custom android ROM or just stick with fire OS and root. Fun times ahead
cyberdude020 said:
Ok so my gf bought a Kindle fire for my birthday next month because I thought buy it sooner and it's more likely to have the firmware I want. I just opened it up to check the firmware before packing it away and fortunately it came with 5.1.3 out of the box. I didn't dare connect it to WiFi incase it updated lol. Just incase anyone is interested I bought this from Argos (UK) now I just need to figure out if I can downgrade and install a custom android ROM or just stick with fire OS and root. Fun times ahead
Click to expand...
Click to collapse
5.1.3 can be rolled back to 5.1.2 which is fully rootable. From there you can flash several custom roms. See forum index for detailed procedures.
Davey126 said:
5.1.3 can be rolled back to 5.1.2 which is fully rootable. From there you can flash several custom roms. See forum index for detailed procedures.
Click to expand...
Click to collapse
Thanks, I looked into it. I just wasn't sure about using flashfire with 5.1.2 because I read before you can't get supersu on 5.1.2 only kingroot. Now I see there's a way to get supersu Can't wait for my birthday now, I feel like a kid again haha.
One question I haven't found the answer to yet which you might be able to answer for me. Well actually two Does the stock recovery have a backup feature like TWRP does? So if I mess up installing something and get a boot loop for example I can just recover the ROM and will that work with backing up an android ROM?
The second question is if I install android and something messes up can I just recover back to fire os by just installing the 5.1.2 .bin file? I've not looked at the stock recovery so I haven't seen the features or how exactly it works.
Thanks again for your help
cyberdude020 said:
Thanks, I looked into it. I just wasn't sure about using flashfire with 5.1.2 because I read before you can't get supersu on 5.1.2 only kingroot. Now I see there's a way to get supersu Can't wait for my birthday now, I feel like a kid again haha.
One question I haven't found the answer to yet which you might be able to answer for me. Well actually two Does the stock recovery have a backup feature like TWRP does? So if I mess up installing something and get a boot loop for example I can just recover the ROM and will that work with backing up an android ROM?
The second question is if I install android and something messes up can I just recover back to fire os by just installing the 5.1.2 .bin file? I've not looked at the stock recovery so I haven't seen the features or how exactly it works.
Thanks again for your help
Click to expand...
Click to collapse
- stock recovery offers no backup/restore capability (thanks, Amazon)
- FlashFire does offer this feature along with an experimental restore from fastboot; read docs carefully to understand capabilities/limitations
- 3rd party backup tool offers best option to protect against personal data loss
- FireOS can be restored via stock recovery; be sure to use 5.1.2 bin; anything lower will brick device
Davey126 said:
- stock recovery offers no backup/restore capability (thanks, Amazon)
- FlashFire does offer this feature along with an experimental restore from fastboot; read docs carefully to understand capabilities/limitations
- 3rd party backup tool offers best option to protect against personal data loss
- FireOS can be restored via stock recovery; be sure to use 5.1.2 bin; anything lower will brick device
Click to expand...
Click to collapse
OK cool thanks a lot, it's all making much more sense now, it a bit daunting at first as all my flashing experience is through TWRP which is much easier While I'm picking your brain though, one more question. Is there a way to backup the android ROM? Or if I get into a boot loop I have to restore 5.1.2 and then reinstall android again?
I'm feeling much more comfortable doing this now though knowing even if I completely mess up the rooting or installing android I can just restore the 5.1.2 firmware. For £50 this thing is a steal.
cyberdude020 said:
OK cool thanks a lot, it's all making much more sense now, it a bit daunting at first as all my flashing experience is through TWRP which is much easier While I'm picking your brain though, one more question. Is there a way to backup the android ROM? Or if I get into a boot loop I have to restore 5.1.2 and then reinstall android again?
I'm feeling much more comfortable doing this now though knowing even if I completely mess up the rooting or installing android I can just restore the 5.1.2 firmware. For £50 this thing is a steal.
Click to expand...
Click to collapse
Answered this in previous post.
Mine just showed up yesterday. 5.0.1.
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
you can downgrade and then you can root
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os. Is it required to side load?
Ubuntu_noobi said:
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os.
Click to expand...
Click to collapse
Wrong procedure. See forum index for details, in particular the first two posts in this thread.
Ubuntu_noobi said:
Is it required to side load?
Click to expand...
Click to collapse
Yes.
So glad I found this post. Researching the same thing. Trying it out now
Sent from my iPhone using Tapatalk
yungskeeme01 said:
So glad I found this post. Researching the same thing. Trying it out now
Click to expand...
Click to collapse
Any new info to share? I still haven't been able to figure it out
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
What exactly are you trying to "figure out"? Responded a few days ago with downgrade/rollback links which includes a step-by-step video.
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
I downgraded to 5.3.1. Rooted the fire and am now running CM 12.1. Very smooth!. Took me a awhile to get since I have a Mac but got it working. Used Rootjunky's YouTube video on how to restore. That's how I downgraded. Then used his Supertool for Mac and rooted. I then installed Flashfire and put CM12 on the tablet.
Sent from my iPhone using Tapatalk
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
Davey126 already answered it here.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
amerkiller1995 said:
I used KingRoot directly and decided not to replace it with SuperSu.
Click to expand...
Click to collapse
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
amerkiller1995 said:
Davey126 already answered it here.
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
Click to expand...
Click to collapse
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Davey126 said:
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
Click to expand...
Click to collapse
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
yungskeeme01 said:
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
amerkiller1995 said:
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
Click to expand...
Click to collapse
Sorry if I misread it. I used the version included and KingRoot so I replaced it in Supertool and re-rooted using SuperTool and it removed it no issues. Whatever though, it got rooted one way or another!
Sent from my iPhone using Tapatalk
Awesome I will try again tonight
Solved!!! Finally!!!
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
TL;DR: THERE IS NO "One click" OPTION THAT WORKS. I DOWNLOADED ALL OF THEM. IVE TRIED EVERY DAMN ONE OF THEM. STOP SEARCHING. You MUST side load the system with the code necessary to make it capable to root. Downgrading to 5.3.1 was the secret, instead of trying to root on 5.3.2. I made a glossary of the confusing terminology, made a step by step walk through for noobs
SO, having felt encouraged by the response by people on this forum, last night I decided it was worth another try.
I finally figured out what I was missing. IF YOU CURRENTLY HAVE FIREOS VERSION 5.3.1, YOU MUST ROLL IT BACK THRU SIDE LOADING see here: SIDELOAD TUTORIAL
I tried to load straight onto the system disk and caused all kinds of problems. Once I followed that step by step, which TBH, was a lot of pausing and rewinding. I am not familiar with many terms so I made this...
Android Common Terms:
Boot: A sequence of commands written into the underlying software that tells the device what order to operate in
Bootloader: See Previous (this is the sequence I referenced previously)
Locked Bootloader: Think of trying to edit a PDF you did not create... Exactly.
ADB Fastboot: THIS IS A PROGRAM... NOT A FUNCTION. I still get this confused, thinking that it is a quicker version of the boot sequence... IT IS NOT. ADB Fastboot is a program that gives access to the base software code making it reachable to use certain sections of to "edit the PDF".
Custom Recovery: It is the new version of Windows 10 you were updating to when your crappy laptop you JUST bought came with Windows 8.1. Essentially.
Root: Remember the PDF? Well, if you work somewhere that has Adobe Reader, and you see the window on the right pop up with the ability to login to Adobe Online or whatever? Well, rooting is having login credentials to ACTUALLY edit that damn PDF.
Flash: Download from the internet, and install on your hard drive, or SD Card. It actually means you erase whatever is there completely first, then install. It's two steps, which is why they don't just call it installing... I think.
Partition: Have you ever worked in an office with cubicles? Exactly. A partition is a wall that you put up to segregate files, or programs, or whatever.
SuperTool: Based in your computer. RootJunky Went through and basically made one tool that has everything you need for rooting. PROBLEM IS THAT HE TELLS YOU TO DOWNLOAD ADB FASTBOOT AND DRIVERS AND A BUNCH OF STUFF, then says, or you can just download the SuperTool, which means, I now HAVE TWO OF ALL OF IT, and then I spend the next three hours trying to figure out if its the "custom rom that I sideload into the TWRP, or if the Flashed version of the bootloader gets added to the recovery image, but not before the drivers are flashed into the fastboot."
While this doesn't cover a lot, I hope that people in this community understand what it is like for someone unversed in the lingo to grasp exactly what is going on. I don't think we should speak like idiots and elementary students, but I also think we lose a ton of people that may have something to offer one day because they got frustrated with the terminology and gave up. Luckily, I stuck it out and gave it one last chance and I got it.
So, once I downgraded from 5.3.2 to 5.3.1, I went about trying to root the device, which was also a little confusing.
Step 1: Downgrade if you have 5.3.2 to 5.3.1
Step 2: Enable ADB and Debug in the Settings
Step 3: Hold down the Power and Volume Down button, release the power button once the device starts to reboot and a menu will popup
Step 4: Use the volume keys to access the first selection. This is how you access the "sideloading".
Step 5: Open the SuperTool, click on the batch file which should say Auto... because calling it SuperTool would be confusing
Step 6: follow the super easy instructions. Honestly.
It will walk you through the process and get you to the part about Kingroot and FlashFire and eventually root the device.
I honestly hope this helps someone. God knows it would have saved me from spending approximately 30 hours trying to figure this out.
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
havikx said:
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
Click to expand...
Click to collapse
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Davey126 said:
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Click to expand...
Click to collapse
now that you mention, thats probably exactly what i forgot to do. Also, i'm on 5.1.1. My bad. As far as i know, 5.1.1 system still has that locked bootloader preventing android upgrades. Though I havent kept up with development too much. Ill get started on returning to stock and rerooting. Hope this little tablet get a breakthru in the near future!
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
havikx said:
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
Click to expand...
Click to collapse
Agreed. The technique you used doesn't work for everyone; hence my generic 'return-to-stock and redo everything' guidance. Glad you are back in business with minimum fuss.