I more or less understand the differences between versions and the install process, but I wanted to double check some things..
I just bought a Fire 7 2015 with 5.1.1 on it. I've used SuperTool to root and all its other functions. I want to install a custom ROM. There's detailed information about 5.0.x and 5.1.2+, but 5.1.1 seems like an odd duck.
- What is the difference between 5.1.1 and 5.1.2? Aside from the system, does it have a different bootloader and recovery?
- 5.1..1 doesn't allow modifying the bootloader or recovery, right? Not even temp booting TWRP? So, is the recovery same as 5.1.2?
- So without TWRP, I have to use FlashFire on 5.1.1?
- To revert back to stock FW, I can sideload 5.1.1, right? I don't have to sideload 5.1.2?
- Any comments on a ROM? I've used CM and AOSP before, but never Slim. There is varying information regarding which ROMS can be used on which Fire versions.
TIA.
mageus said:
I more or less understand the differences between versions and the install process, but I wanted to double check some things..
I just bought a Fire 7 2015 with 5.1.1 on it. I've used SuperTool to root and all its other functions. I want to install a custom ROM. There's detailed information about 5.0.x and 5.1.2+, but 5.1.1 seems like an odd duck.
- What is the difference between 5.1.1 and 5.1.2? Aside from the system, does it have a different bootloader and recovery?
- 5.1..1 doesn't allow modifying the bootloader or recovery, right? Not even temp booting TWRP? So, is the recovery same as 5.1.2?
- So without TWRP, I have to use FlashFire on 5.1.1?
- To revert back to stock FW, I can sideload 5.1.1, right? I don't have to sideload 5.1.2?
- Any comments on a ROM? I've used CM and AOSP before, but never Slim. There is varying information regarding which ROMS can be used on which Fire versions.
TIA.
Click to expand...
Click to collapse
5.1.1 can be easily upgraded to 5.1.2. The 5.1.1 bootloaders do not offer any good stuff (no TWRP), so not clear why keep them (other than hoping for the bugs found in the future). At this point prob only a few people have 5.1.1, so not much work would go into trying to hack 5.1.1 bootloaders specifically
Btw, I can easily add a package for preserving 5.1.1 bootloaders, if there is any demand ... See this post :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
with 5.1.1 you can easily gain temporary root
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Kramar111 said:
with 5.1.1 you can easily gain temporary root
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Click to expand...
Click to collapse
So sounds like one should try to keep it !
mageus said:
I more or less understand the differences between versions and the install process, but I wanted to double check some things..
I just bought a Fire 7 2015 with 5.1.1 on it. I've used SuperTool to root and all its other functions. I want to install a custom ROM. There's detailed information about 5.0.x and 5.1.2+, but 5.1.1 seems like an odd duck.
TIA.
Click to expand...
Click to collapse
Kramar111 said:
with 5.1.1 you can easily gain temporary root
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Click to expand...
Click to collapse
I've updated the post, it's possible now to keep 5.1.1 bootloaders if desired :
http://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
I started with 5.1.1 used slim ROM since then flashed with flashfire and never looked back haven't updated because I haven't encountered any bugs I couldn't fix on my own and battery life has been respectable under the hood I don't know the difference I know it runs to perfection and that's what I wanted
PS. I want to thank the developers for their hard work on this device is the only device I've been happy with and didn't go on a flash spree to find something i like
Sent from my VS986 using Tapatalk
mageus said:
... but I wanted to double check some things..
Click to expand...
Click to collapse
bibikalka said:
So sounds like one should try to keep it !
Click to expand...
Click to collapse
Sometimes a stupid question is worthwhile, eh?
Thanx for the clarifications. What everyone has said makes sense. I installed CM12, which works great. I'll stay with the 5.1.1 bl/recov for now since FlashFire works so well, and there's a temp-root option.
Related
Hi All,
I have just within the last few days received a brand new Nexus 6, did all updates and it is running 5.1.1. I have found multiple guides online in regards to rooting 5.0, but none of them have any reference to 5.1.1 (I assume because it is still fairly new). I would just like to make sure that the guides for 5.0 are still appropriate for 5.1.1 before I go ahead with the root, and will not brick my phone. (Would post link for the guide I was going to follow, but I have less than 10 posts)
If anyone could verify this for me, that would be awesome! As well, if anyone has any newer guide or anything else that I should know as I am starting from scratch with a new device, that would be great as well!
Thanks!
SnakeByte77 said:
Hi All,
I have just within the last few days received a brand new Nexus 6, did all updates and it is running 5.1.1. I have found multiple guides online in regards to rooting 5.0, but none of them have any reference to 5.1.1 (I assume because it is still fairly new). I would just like to make sure that the guides for 5.0 are still appropriate for 5.1.1 before I go ahead with the root, and will not brick my phone. (Would post link for the guide I was going to follow, but I have less than 10 posts)
If anyone could verify this for me, that would be awesome! As well, if anyone has any newer guide or anything else that I should know as I am starting from scratch with a new device, that would be great as well!
Thanks!
Click to expand...
Click to collapse
its all the same, for any nexus. 1. unlock the bootloader via fastboot. 2. flash twrp recovery via fastboot. 3. flash the latest supersu in your new recovery. 4. reboot, with your bootloader unlocked and with root.
Yes, the method to unlock bootloader, flash custom recovery, and root has not changed. I'd suggest this > http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Thanks! Just wanted to make sure!
Could I boot into ADB sideload and use an 5.1.1 image from Amazon? And then root?
Sent from my KFFOWI using Tapatalk
Distinct feeling that will just make it have the same effect as using the OTA upgrade, but I'm not sure.
Is there a problem with using twrp?
AntDeek said:
Could I boot into ADB sideload and use an 5.1.1 image from Amazon? And then root?
Click to expand...
Click to collapse
Indeed, you might as well just turn on OTA, and wait for it
You have to be able to root somehow, and the best way is through TWRP since otherwise 5.1.1 is currently impenetrable.
So if I wanted to do a fresh install I would just have to wait for the 5.1.1 root?
Sent from my KFFOWI using Tapatalk
Why on earth would you want to install 5.1.1?
Have you read what 5.1.1 does? See [PSA] Information Regarding Firmware Version 5.1.1.
Only safe way to install 5.1.1 is detailed here: HOWTO] Install FireOS 5.1.1, ROOT, GAPPS and keep TWRP access and even then you will be worse off on 5.1.1. I believe you can't remove any bloatware or the lockscreen ads.
In what way is installing it through twrp not a fresh install if (after backing up) you wipe it all? (assuming install files and backups made to an external sd)
AntDeek said:
So if I wanted to do a fresh install I would just have to wait for the 5.1.1 root?
Click to expand...
Click to collapse
Couldn't one factory reset in TWRP and then use bibikalka's upgrade/root method? (I'm asking.)
If you want a completely fresh install then you can just reinstall 5.0.1
No reason to go anywhere near 5.1.1
HOWTO How to restore frimware on your device + Amazon Frimware
Would it be possible to do a side load restore to 5.0.1 and then upgrade to 5.1.1 and wait for a root script and the google apps?
So long as you realise that they might never come.
If your tablet is functional atm I can't understand why you want to do something that might never work rather than something that does easily.
If you are on anything other than 5.1.1 atm see if you can swap with someone desperate to get rid of a Fire stuck on it.
So really I should just keep it on 5.0.1 rooted with Google launcher and see if 5.1.1 gets rooted
Sent from my KFFOWI using Tapatalk
Or just...
I don't know...
use twrp...
Some people (myself included at a certain point of time) just HAD to have the latest updated version, even though it sometimes is a downgrade really. Case in point is the current es file explorer.
That's how I am lol I feel the need to have the latest version
Sent from my KFFOWI using Tapatalk
julianpaul said:
Some people (myself included at a certain point of time) just HAD to have the latest updated version, even though it sometimes is a downgrade really. Case in point is the current es file explorer.
Click to expand...
Click to collapse
What's wrong with ES?
AntDeek said:
So really I should just keep it on 5.0.1 rooted with Google launcher and see if 5.1.1 gets rooted
Click to expand...
Click to collapse
5.1.1 can already be rooted (if installed through the proper procedure). See the link I posted.
blueberry.sky said:
Only safe way to install 5.1.1 is detailed here: HOWTO Install FireOS 5.1.1, ROOT, GAPPS and keep TWRP access and even then you will be worse off on 5.1.1. I believe you can't remove any bloatware or the lockscreen ads.
Click to expand...
Click to collapse
You are in root & custom Rom land now. There will be so called "upgrades" to the amazon OS that provide zero upgrade, only serve to disable root, roms, debloating & adblocking.
Pond-life said:
What's wrong with ES?
Click to expand...
Click to collapse
http://www.xda-developers.com/es-file-explorer-a-short-story-of-a-fallen-king/
---------- Post added at 05:00 PM ---------- Previous post was at 04:43 PM ----------
AntDeek said:
Would it be possible to do a side load restore to 5.0.1 and then upgrade to 5.1.1 and wait for a root script and the google apps?
Click to expand...
Click to collapse
Pond-life said:
If you are on anything other than 5.1.1 atm see if you can swap with someone desperate to get rid of a Fire stuck on it.
Click to expand...
Click to collapse
I will buy your 5.0.1 Fire / trade. I am entirely serious.
If you want 5.1.1 and don't mind taking a chance, waiting for a new 5.1.1 root exploit to come out, I have another Fire on it's way to me from Amazon. It may very well come preloaded with 5.1.1. I will seriously trade. I need a custom rom, root doesn't do what I need.
I am not looking to sell my device I'm sorry friend!
So I am better off leaving 5.0.1 rooted in my Fire since it does everything I need it to.
Pond-life said:
What's wrong with ES?
Click to expand...
Click to collapse
Unless you're on the pro version, you cannot disable the homepage, and the stupid cleaner function is a major annoyance. My opinion; others' may vary.
@blueberry.sky cheers for the link, reading now...
AntDeek said:
So I am better off leaving 5.0.1 rooted in my Fire since it does everything I need it to.
Click to expand...
Click to collapse
Finally ! you got it !
Is there any downside to using 5.0.1 until 5.1.1 can be easily rooted?
AntDeek said:
Is there any downside to using 5.0.1 until 5.1.1 can be easily rooted?
Click to expand...
Click to collapse
5.1.1 cannot be downgraded
Sent from my KFFOWI using Tapatalk
Hi All,
Not a Dev as such but have rooted and installed SlimLP on my Fire tablets.
Having trouble using some apps as they are detecting the root. Have looked into Xposed package and using the root cloak to solve these issues but can't find any info on whether my setup is supported or not and don't want to brick my devices.
What I have:
Device - Amazon Fire 5th Gen
Model - KFFOWI
Android Version - 5.1.1
Slim Version - slim-5.1.1.build.2.2-csolanol-20151210
All I want is to end up with both my devices running custom ROMs with the root cloaked, doesn't have to be SlimLP if it's not possible.
Any help would be appreciated on this. As I say I am not a Dev so won't understand technical jargon.
Thanks in Advance
Did your device have FireOS 5.0.1 on it before you flashed a custom rom? Aka can you load twrp recovery via fastboot.
If you have a 5.0.1 device then you should almost always be able to recovery from any issues.
I had 5.1.1 OS installed prior to flashing. I used RootJunkys supertool to root and used Flashfire to flash the rom.
Does this make a difference?
Chrisbonner89 said:
I had 5.1.1 OS installed prior to flashing. I used RootJunkys supertool to root and used Flashfire to flash the rom.
Does this make a difference?
Click to expand...
Click to collapse
Does make a difference but is irrelevant to your concern. You can not effectively cloak root on any android rom. Yes, some techniques can obscure root from poorly coded apps but most are more intelligent and can easily detect if the device has 'elevated' permissions - including if usb debug is enabled. Savvy users can defeat some checks but it's a cat and mouse game at best.
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.
devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.
no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone
trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you
zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!
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.