Related
Hi guys, this is my first tut here, about an alternative way for rooting my S6500D...
Q : Why do I need this? There is a better and easy way already using CWM....
A : This tut will only give you root access, without a busybox, CWM, etc. If you want Root+BB+CWM, please follow an other TUTs.
Okey, Here we go...
This TUT is based on "poot" exploit created by giantpune from androidforums.com (We should thanks him/her)
He/She create this exploit for LG Optimus Elite originally, but mod it to work for several phone model.
He said that this exploit will work on android version 2.3.5 - 2.3.7. Thats why I try this on Jena
Giantpune from androidforums, posted original application and some modded apk to work with other phone.
To respect his work and his thread, I only attached a working apk that root my Mini 2.
And provide his thread's link, so you can download all poot apks from there, thanks him and his team, and maybe donating him.
Here is the link : http://androidforums.com/elite-all-things-root/612914-optimus-elite-root-apk.html
Requirement :
- poot-debug.apk for h866c (Huawei ascend Y). I tried another version, but fail.
- Ministro II. You can download it from Playstore.
- Please remove your SD card.
Step by step :
1. Install Ministro II from Play Store.
2. Install poot-debug.apk for h866c. I already attached it.
3. Create Poot shortcut to Home.
4. Turn on USB Debugging in the Settings>Application>Developement
5. Open Poot, it will request to download some Ministro library. This library needed by poot to work. You will need an internet connection.
6. After all library downloaded, close Poot. Its better to reboot our phone first.
7. Let the phone boot completely. If you have much app installed, kill all running app, so nothing can interrupt this exploit.
8. Open Poot, tap "Press Here to Poot" button.
- If the phone reboot suddenly, try again this step.
- If Poot app show an error log, like error : 87 or 22, reboot your phone and try again.
- If it still fail, try to reboot your phone. When lockscreen showed up, immediately unlock it while system scanning storage. Open Poot quickly (thats why I want you to put a shortcut in home). Then tap "Press Here to Poot".
9. If Poot show log like "successfully push su file to /system/xbin...bla..bla...bla", then you have successfully rooted your phone.
10. After a successful poot, Poot will show 3 option:
- Get Superuser = it will open Play Store straightly to Superuser by ChainsDD page. Install it to manage root access.
- Get Root Checker Basic = it will open Play Store to Root Checker Basic page. If you want to check root access using this app, download it.
- Built-in Root Checker = Instead of download Root Checker Basic, you can use this built in feature.
11. After Superuser installed, dont forget to update su binary file from it.
12. Its done!!! now you have a rooted Mini 2.
Note: I have tested original poot for LG Optimus Elite, Cherry W100, and PCD Venture without success. If your phone can not be rooted with poot for h866c, I advice you to try another versions.
The advantage of this method :
- This method of rooting will not increase your custom bin, because you dont need to flash CWM.
- You dont need a PC to root Jena.
Disadvantage :
- You need to install/download Superuser by ChainsDD + BusyBox manually. This exploit only push su file (Superuser's su file by ChainDD) to /system/xbin.
Note: If you want to flash CWM, we need to wait mobile Odin compatible with our device. Therefore, if you want CWM very badly...I suggest you to flash it using PC.
Credits:
- giantpune from androidforums.com, who made the exploit.
- me, who try and test this exploit on Jena all night long :crying:
PM me, if someone should be listed on Credits
Really nice, very god man. But Triangle Away is working for our phones so there's no problem regarding bin counter
Thanks man
Yup, triangle away worked as you said. But I never try it yet tho. I bought a new Jena 1month ago, and I dont want to loose my warranty.
Thats why I search another way to root safely, without worries
Maybe this tuts dedicated for someone like me, who didnt have a PC or notebook yet.
Well that's something new. Portable rooting where you're in a car without CWM?
In all seriousness, it's great to see great things show up for our Jena, like this and MIUI, and TWRP, and CM 10, and OC Kernels, and many other stuff.
It's you people who make this phone awesome.
I have a question, is the "su" binary the latest one?
Yup, we hope Jena community will grow up like mini I
No, it is not. We need to update it to the latest version, after Superuser installed.
Iam still figuring out how to migrate to CWM superuser tho. Its Open Source, and looks like better security.
BusyBox can be installed downloading Busybox installer from play store
https://play.google.com/store/apps/details?id=stericson.busybox
and maybe CWM can be installed with mobile odin (i don't know)
i am saying this because I am an admin of a spanish blog and many people ask us for a way to root and install CWM without PC,
Maybe I miss spelling something...
Or you dont understand what I mean
I mean superuser.apk by clockworkmod, or koush's superuser.
If I want CWM, I will not root using this method
Yup, thats busybox installer that I mean
I was only thinking in a way to install CWM for users that don't have PC. I am a admin of a Spanish blog and many people want it.
And in sOme other devices ROM MANAGER can install CWM. maybe it's possible with mobile Odin or rom manager, I guess
Rom Manager can brick the mini 2, because it's not compatible with mini 2 I think.
manu19thebest said:
I was only thinking in a way to install CWM for users that don't have PC. I am a admin of a Spanish blog and many people want it.
And in sOme other devices ROM MANAGER can install CWM. maybe it's possible with mobile Odin or rom manager, I guess
Click to expand...
Click to collapse
MrMateczko said:
Rom Manager can brick the mini 2, because it's not compatible with mini 2 I think.
Click to expand...
Click to collapse
Yup, i heard that rom manager can brick mini 2.
My best bet is mobile odin.
It is compatible with ace plus.
And mini 2 almost the same with ace plus.
physcodelic said:
Yup, i heard that rom manager can brick mini 2.
My best bet is mobile odin.
It is compatible with ace plus.
And mini 2 almost the same with ace plus.
Click to expand...
Click to collapse
I am dumping info now via mobile Odin app. I will put it in mobile Odin xda thread, so chainfire can develop it for our phone
Please, can other person do the same? Cause I've squadzone kernel installed
manu19thebest said:
I am dumping info now via mobile Odin app. I will put it in mobile Odin xda thread, so chainfire can develop it for our phone
Please, can other person do the same? Cause I've squadzone kernel installed
Click to expand...
Click to collapse
Already done that, but havent send it.
I will send it soon.
Jena full stock.
physcodelic said:
Yup, i heard that rom manager can brick mini 2.
My best bet is mobile odin.
It is compatible with ace plus.
And mini 2 almost the same with ace plus.
Click to expand...
Click to collapse
Now I am dumping information for chainfire(with that he could make odin compatible). You can do it installing mobile odin app
Ive done that too. Already dump and send it to chainfire thread.
Just wait him to make it work with our device
physcodelic said:
Ive done that too. Already dump and send it to chainfire thread.
Just wait him to make it work with our device
Click to expand...
Click to collapse
Finally, I didn't send it because I am using squadzone's kernel, so maybe it's different
But maybe it'll be useful to send one using CM10 (is more compatible)
I read somewhere that mobile Odin works on Ace Plus which has exactly the same partition layout as Mini 2. Also, since we don't need any specific file which contains the info about our partition layout (like ops file for some devices) while flashing something, it's pretty generic therefore mobile odin should work.
Sent from my GT-S6500D using xda app-developers app
TheWhisp said:
I read somewhere that mobile Odin works on Ace Plus which has exactly the same partition layout as Mini 2. Also, since we don't need any specific file which contains the info about our partition layout (like ops file for some devices) while flashing something, it's pretty generic therefore mobile odin should work.
Sent from my GT-S6500D using xda app-developers app
Click to expand...
Click to collapse
Finally, a confirmation from a genious person
Maybe yes sir, it should work for our device.
But chainfire's mobile odin wont let us use it, if our device is not compatible.
Maybe, just maybe, (I dont know how it work ) mobile odin read our build.prop and compare them to it's device compatibility database.
If those not match, it just showing black screen, and an intructions to dump a log, then close it self.
Hopes he/she make it worked for Mini2 someday
physcodelic said:
Finally, a confirmation from a genious person
Maybe yes sir, it should work for our device.
But chainfire's mobile odin wont let us use it, if our device is not compatible.
Maybe, just maybe, (I dont know how it work ) mobile odin read our build.prop and compare them to it's device compatibility database.
If those not match, it just showing black screen, and an intructions to dump a log, then close it self.
Hopes he/she make it worked for Mini2 someday
Click to expand...
Click to collapse
write private msg to chainfire mayby he do MO for Jena, but in OP chainfire i see many spam and hm 4 post from galaxy mini 2 users, this device is not popular and low range so chainfire do not even think about develop app to this phone. its my opinion...
well, yes, this is not popular. For reference, my latest CM10 build for Mini 1 is downloaded like 20k times. When I uploaded the first CM10 build in the first day it got 5k downloads. Mini 2 barely get 1k downloads in months. Mini 1 is quite popular, even after 2 years of its release. Perhaps it will change after camera is fixed.
TheWhisp said:
well, yes, this is not popular. For reference, my latest CM10 build for Mini 1 is downloaded like 20k times. When I uploaded the first CM10 build in the first day it got 5k downloads. Mini 2 barely get 1k downloads in months. Mini 1 is quite popular, even after 2 years of its release. Perhaps it will change after camera is fixed.
Click to expand...
Click to collapse
well some of the users really is concerned about the camera, so they stick with Stock Rom.
but for us user whose not using the camera (crap for taking picture) CM10 is really great.
Rooted twrp all that fun stuff installed but live wall papers will not work. I fllowed the steps and it just keeps telling me its stopped and wont let me use one.
ajac said:
Rooted twrp all that fun stuff installed but live wall papers will not work. I fllowed the steps and it just keeps telling me its stopped and wont let me use one.
Click to expand...
Click to collapse
What ROM are you using? It could be a kernel problem, post the instructions you followed and I'll take a look, I also need to know exactly which device you have.
For now though, have you trued booting to recovery and wiping only the cache and dalvik cache.
N_psycho_PD_uh? said:
What ROM are you using? It could be a kernel problem, post the instructions you followed and I'll take a look, I also need to know exactly which device you have.
For now though, have you trued booting to recovery and wiping only the cache and dalvik cache.
Click to expand...
Click to collapse
just using stock
1) download LiveWallpapersPicker.apk from below.
2) Make sure you have root access.
3) Install a application to manage files with root access (example Root Explorer).
4) Move the downloaded file to your Kindle Fire HD. (Remember where you place it).
5) Go into your system/App folder, and move the LiveWallpapersPicker.apk to this folder.
6) Change permissions on LiveWallpapersPicker.apk to rw-r-r.
7) Install Live Wallpapers from the Google Market, or Sideload them
steps I followed been to scared to try another rom fear of bricking lol on 3.2.8
ajac said:
just using stock
1) download LiveWallpapersPicker.apk from below.
2) Make sure you have root access.
3) Install a application to manage files with root access (example Root Explorer).
4) Move the downloaded file to your Kindle Fire HD. (Remember where you place it).
5) Go into your system/App folder, and move the LiveWallpapersPicker.apk to this folder.
6) Change permissions on LiveWallpapersPicker.apk to rw-r-r.
7) Install Live Wallpapers from the Google Market, or Sideload them
steps I followed been to scared to try another rom fear of bricking lol on 3.2.8
Click to expand...
Click to collapse
No, I meant post a link to your instructions so I can read it myself to see what it contains and whether it is made for your device/ROM and kernel version. What exact model of kindle fire HD do you have, they are not all the sane even if they are called by the same name, when they were manufactured makes a difference on these sometimes because slight changes have been made or things were updated from what was released before it that causes issues, just because someone did something on their device doesn't mean you can do it on yours because some changes may have been made that were not done on theirs and that effects what you can use or how you do it. Having said that can you identify exactly which device you have, what size it is, your firmware version, and your kernel version, I want to verify what you are using is actually supposed to work on yours.
N_psycho_PD_uh? said:
No, I meant post a link to your instructions so I can read it myself to see what it contains and whether it is made for your device/ROM and kernel version. What exact model of kindle fire HD do you have, they are not all the sane even if they are called by the same name, when they were manufactured makes a difference on these sometimes because slight changes have been made or things were updated from what was released before it that causes issues, just because someone did something on their device doesn't mean you can do it on yours because some changes may have been made that were not done on theirs and that effects what you can use or how you do it. Having said that can you identify exactly which device you have, what size it is, your firmware version, and your kernel version, I want to verify what you are using is actually supposed to work on yours.
Click to expand...
Click to collapse
Hdx 8.9 kindle fire apollo
ajac said:
Hdx 8.9 kindle fire apollo
Click to expand...
Click to collapse
OK, that's the device, I've got that, now what firmware version and kernel version does your device have? I need to know more than just what device you have. Are you even reading my replies, this is the third time I've asked you for your firmware and kernel versions, if you aren't going to give me that information then I'm wasting my time trying to help you because that information is what determines what methods and mods you can use.
N_psycho_PD_uh? said:
OK, that's the device, I've got that, now what firmware version and kernel version does your device have? I need to know more than just what device you have. Are you even reading my replies, this is the third time I've asked you for your firmware and kernel versions, if you aren't going to give me that information then I'm wasting my time trying to help you because that information is what determines what methods and mods you can use.
Click to expand...
Click to collapse
well I figured since I said I was rooted it would been pretty easy to figure out but 3.2.8
ajac said:
well I figured since I said I was rooted it would been pretty easy to figure out but 3.2.8
Click to expand...
Click to collapse
I got that, now what kernel do you have, some devices have identical firmware but different kernel. I have your device model and your firmware version now I need your kernel version, the kernel is the main thing, the kernel is what tells the firmware how to interface with your device, you can change your firmware and keep the same kernel on another firmware, the two don't necessarily go together, the kernel resides within the device itself and not the firmware you have and can remain there even if you flash a new ROM on it. The new ROM will still be using your original kernel unless the ROM has it's own kernel built in.
Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Bob Boblaw said:
Hi all
I've just bought a Fire Tablet on Amazon day with the intention of rooting it and installing CM, but I am a newbie and there's so much information on here it's kind of overwhelming, and most of it has a lot of "if this, then that, or if you want to use that, do this" type guides, which for someones who doesn't really know what all the different methods and options are is really confusing!
So can someone please tell me the step by step process for doing it?
From what I've read I think I have to downgrade to 5.1.2 of the OS as I can't root on 5.1.4? Is that correct?
So do I have to root before I do that? Or do I downgrade first and then root, and then install the CM?
If someone can list each of the steps I need to take to get it from a fresh new 5th Gen Fire 7 to having all the Amazon rubbish off and having it running CM, then I can look for the guides for each step!
Thanks, I hope that makes sense!
:angel:
PS: I've already bricked one by trying to downgrade to 5.1.1 because that wasn't apparent until it was too late, replacement on its way!
Click to expand...
Click to collapse
I did the same thing, bought the tablet on prime day and was successfully able to root it and put the AOSP nexus rom
First things first make sure you have the 7-inch tablet for the following steps because apparently it only works with that specific model. Since this is my first post I can't post any links so sorry about that however, I have added the video title so that you can just google it and find the video.
Anything above fire os 5.1.2 ( that is 5.1.4, 5.1.3, 5.1.2.1) has to be downgraded to 5.1.2.
Also downgrading from 5.1.4 to 5.1.1 is going to give you a hard brick. I don't know how you didn't know that but it was clearly stated in the xda guide I was following
Basically you have to follow rootjunkys video and instead of using the file he uses in the video use the fire OS 5.1.2 file which is also available on his website.
Imortant: Do a factory reset before downgrading. I did not do that and the rooting process did not work.
Video title: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
After you have fire OS 5.1.2 follow the rooting process shown in another rootjunky video
Video title: How to root the Amazon Fire 5th gen 7in on Fire OS 5 1 2 SuperTool Mac linux and Windows
Note: He shows how to do the whole process while using mac but it can be done on windows awell and the windows files are already present. Instead of using the .sh file and opening the terminal double click the .bat file and follow along.
You can use his SuperTool to put the play store app and fire flash app.
Note: For some reason fire flash was not working properly for me by using the SuperTool, so I just installed it from the google play store.
Now you should have rooted fire OS 5.1.2 along with superSU. Now with the fire flash app and you can download any rom that you want to flash. Follow the steps in the video for instructions
Video title: Amazon Fire 5th gen AOSP Nexus rom install with Flash Fire app
Hope this helps.
All credit to rootjunky
erikthebikeman said:
Yeah, I read the same thing and I bought it on Prime day. When's the 5.14 tool going to come out? I know, beggars... I really think it's silly to have to downgrade and risk bricking it when normal root for those OS versions don't have such a concern.
Click to expand...
Click to collapse
It's not a matter of someone getting off their keister and whipping up a "tool" (presumably you are talking about root) that works with FireOS 5.1.4 or whatever the latest version is. Like many manufactures Amazon actively discourages rooting devices and attempt to block known exploits. It's a cat and mouse game. We may see a "tool" soon, much further down the road or never. Be happy you can root the device at all and be thankful for the individuals who unselfishly share their time and talents with the community.
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Bob Boblaw said:
Thanks nefarian.
The problem was that the guide I was referred to for getting CM onto it already assumed it had been rooted, and when I started googling and looking on the different guides on rootjunky there were so many coming from different angles but nothing giving the clear start to end steps for what I wanted to do, for a newbie it was very confusing. Plus in the guide I was following (a rootjunky one) he had an older version of the OS and the toolkit had different files/folders to what are in it now, so I guess at that time there was no mentioned of 5.1.4 and not being able to go back.
After thinking I needed to downgrade the OS I found the one for unbrinking and downgrading and did that fine to 5.1.2, but then when I tried the superkit it still said it was too new, so I tried to downgrade further, which is when I bricked it.
There was no mention of it on the video..... other than a bloody great overlay in the corner, which must have been added later on, and probably because I was tearing my hair out and getting confused I didn't spot it. That's my excuse anyway!
Thanks for your help, I'll have a go with the new one on Monday. So instead of trying to find an all in one guide, I need to find guide for the steps in this order;
1 - do a factory reset on the device (from the device settings, or do I need to do it in the bootloader settings?)
2 -downgrade to 5.1.2 (I should be able to do this now)
3 - root the device (and install supersu?)
4 - install CM
Then it should have full CM and none of the Amazon OS left.
I'm not missing any steps there am I?
Thanks again!
Click to expand...
Click to collapse
- no need for a factory reset at any point; offers no benefit for what you are trying to accomplish.
- installation of SuperSU (replacing Kinguser and related Kingroot cruft) after rooting is highly recommended prior to using FlashFire or any other tool that messes with the system partition. The SuperTool can facilitate this otherwise ugly task.
- if you are struggling with RootJunky videos you should give serious consideration to the challenges of installing a custom rom. It doesn't get any easier going forward.
Thanks. I managed to root my Nvidia Shield TV fine so I should be able to do it, I just needed to be clear of the full process from start to finish, and as I wasn't starting from the beginning of the process that made it more confusing. The rootjunky videos are great, but when someone is saying you can use this or that or do this or that it's putting choices and variables in to the mix so it's not a straighforward step by step, and when the kits and the webpages shown on the videos have changed since they were made, for someone trying to piece the info together it takes a bit more time.
Maybe I should point out that I didn't look on here initially when I started trying to do it, I basically saw the fire on offer mentioned on a forum I use and someone said yeah, it's easy to root and get CM on if, just user this video, with the link to a rootjunky YouTube video which didn't mention the prerequisite of already having downgraded the OS (why would it) so in hindsight I didn't start at the right place or have the best information.
After reading through some stuff on here (and that's over whelming for a first timer as there is so much stuff on here for many, many devices and platforms - even just finding the Amazon fire sub forum on an iPad wasn't easy!) I'm getting a better idea for attempt two.
I'll get there, and at least I know how to not brick it now! :good:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (
&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
- Kingroot/Purify, not Kingmaker/Purity
- I can't think of a better suite of guides than the videos produced by RootJunky
- use FlashFire 0.51 to install (flash) the rom of your choice
- OP for Nexus rom has video link and and basic FlashFire guidance
- get over the minor variations in the language/tools used to support this device between the making of videos and the latest release.
Bob Boblaw said:
OK, so making progress. I have downgraded the new one fine, it now has 5.1.2 of the Fire OS.
I've used rootjunkys supertool to root the device with Kingmaker, which then installed SuperSU, and I finally uninstalled Kingmaker/Purity.
So I now have a rooted Fire, which is great. I have also installed the Google Play store, disabled OTA updates and removed ads from the lock screen. But I don't want the Amazon OS on it (pretty fugly isn't it!), so the next step, flashing it with CM.
What guide would be best for a Fire with 5.1.2 on it? When I look at the Rootjunkys guide for installing CM on the Fire (https://www.youtube.com/watch?v=4dwguHoxTvo&feature=youtu.be) the super tool kit does differ, and the one I downloaded from his link only has the tool for doing it for OS 5.0.1, so it won't let me boot into TWRP recovery. What would be the best tools/guide/method to use for installing CM onto a Fire with 5.1.2?
Thanks
Click to expand...
Click to collapse
1. Get the CM rom and put it in the tablet from here: http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
2. Install FlashFire 0.51 from play store or use the SuperTool
3. Follow the video instructions and instead of the nexus rom use the CM rom you downloaded:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Bob Boblaw said:
Thanks guys. All going well. CM12 is now installed using that Nexus guide. However, because he used Nexus the Play store was installed by default, which CM12 doesn't have.
Looking here - https://wiki.cyanogenmod.org/w/Google_Apps#Installation - I need to download Google Apps and install it, but which package for the Fire 7 5th gen? There are a number of variants to choose from. Looks like using twrp it would have been a pico one, but as it's a new OS a different one is needed?
So it's ARM device, Android 5.1 and Nano variant?
That gives me a zip file, but I can't work out how to install it. The videos I've found all have it as being installed as part of the OS installation via twrp. Should I have installed gapps when I installed the CM12.1 OS, or can I still install it later?
When I go into the boot menu the only install option is to apply update from ADB, wipe data/factory reset, wipe cache partition, reboot to bootloader or power down/reboot.
I tried to use apply update from ADB and did "adb sideload gapps-filename.zip" but it failed to complete the install and went back to the boot menu.
What do I need to do to get Play Store on there?
Thanks again
Click to expand...
Click to collapse
Reinstall FlashFire 0.51 (here) on CM 12.1 then use it to flash the GAapps package. Agree with your selection: ARM/5.1/nano.
Ah, great, thank you, yep, that's got it on there.
Excellent! All modded and running very quickly! Thanks for the help guys, I appreciate the patience.
Not much space on these Fire's is there, it's already telling me it's low on space and I've only installed MediaMonkey!
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage? For example, my Shield TV lets me 'add' the SD card to the main storage so it sees it all as one instead of a second removable device, so can install apps on it, etc. If this possible with Cyanogenmod? (Not sure what you'd call that feature to search for it!) Thankfully the main reason I bought it was to help manage my music with MediaMonkey so I won't be installing lots on it, but if it is possible it would be useful.
Second, with regard to OS updates on CM, are they automated or do they need to be done manually (and, if so, with care?)
Thanks again!
Bob Boblaw said:
Two more quick questions and I'll leave you alone....!
Is it possible to have the SD card to be used as combined storage?
Second, with regard to OS updates on CM, are they automated or do they need to be done manually ...
Click to expand...
Click to collapse
Short answer: 'yes'. There are various approaches to utilizing SD cards for app installation/storage each with pros, cons and compromises. I highly recommend using a tool that leverages 'symbolic links' which is by far the most reliable method. An example is Link2SD which you can find in the Play Store.
All custom roms for this device are updated manually via FlaahFire or TWRP (if available). Instructions can usually be found in the OP.
@Bob Boblaw
did you open up the file manager and install the flashfire.apk? I am on the same problem you had on your post #11, but my problem I ran into now is flash fire says "root access could not be acquired" otherwise this would be a easy to do.
I think I might have to reinstall everything and start over. >_<
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Bob Boblaw said:
Yes, I copied it over via USB and installed it from the file manager. Do you have root enabled in the developer settings, I enabled it for adb and apps.
Click to expand...
Click to collapse
Yes! Thank you, that is what I had missed plus I didn't reboot my device so took like 15mins trying to figure out why it wasn't still working.
Glad you got it working ! :good:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
thunderman98 said:
Great post guys!! I am getting ready to root my fire OS 5.1.4 and this helps me greatly! Been searching for a downgrade guide and this is it! Have one question is Cm only recovery program or is there a TWRP version for this ? I would think that lastest TWRP would work since its all android but have to ask .I like TWRP myself cause i have it on rooted tablets
Click to expand...
Click to collapse
You can not boot/install/use twrp on this device unless running FireOS 5.0.1 or lower. Nor can you rollback to any version below 5.1.2 without bricking the device. FlashFire is the tool of choice for installing roms and performing other maintenance tasks that are typically done in a custom recovery environment.
Ok I'm sorry if this is stupid but this is my first root, I just got the acer iconia one 8 (B1-850). I was able to root it with kingoroot and replace their super user app with supersu but I can't seem to get a custom recovery installed that is comparable with it. Also I'm trying to install the xposed framework and I know I need the armv8 version but I don't know which one because I'm still using the stock rom, I would prefer to stick with stock but if I can't can someone link a good one?
Sorry as I said this is my first root and I'm hitting a dead end with my researching, or I just misunderstand a cow principal.
this is mosty a copy and past cuz i didnt find this part of the forums when i had to remake my acc. if u watch the video u'll see what i did and what i should cuz the how-to for install magisk is broken to say the least
i have a sony xperia z3v and before u ask yes i did follow when was on the xda but NOTHING works as u see in this video here - https://www.youtube.com/watch?v=Jaga6MUcTdc&feature=youtu.be.
so first thing i need is a Custom Recovery. so i follow what that page here - https://www.xda-developers.com/how-to-flash-install-custom-recovery/ says...
first thing it is say i need Android SDK but never once talks about needing it ONE TIME.
2nd, both links given on that page for the custom recoverys 404! - https://imgur.com/bV9egdH
so what do i do next? i follow whats given and BOTH SITE R DEAD! also that page doesnt ONCE going into how to set up a custom recovery at all.
how is that u guys can help me out when it comes to flashing my sony xperia z3v back to stock after i F-ed up on a root and yet not have a set by set for geting Magisk to work install and work on your phone?
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Didgeridoohan said:
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
yes u do need a custom recovery as said on this page here - https://www.xda-developers.com/how-to-install-magisk/
"What You’ll Need:
A device running Android 4.2+
Custom Recovery (how to install)
We’ll be using TWRP in this guide"
i have the magisk manager already install as is my phone it rooted as u can see in this SS from the phone here - https://imgur.com/a/Kq1EChq but as u see magisk has a red X since its not installed so i go to install it but it give a .zip so i use that and it errors out EVERY ****ING TIME as see here - https://imgur.com/a/VyAslvt
if u toke a few mins of your day to watching the video instead of being a ass and commenting that knowning full well u could have watched the video to see i did everthing that the pages sad u wouldnt be most the comment u just did. u just make yours look like a ass. i want ppl the help me not say "u dont need a custom recovery" when the page on the how to install SAYS U ****ING NEED ONE.
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Didgeridoohan said:
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Click to expand...
Click to collapse
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
let me make it as simple to understand what im looking for. i want to use my Sony Xperia Z3v to game assets dumps for Uta-Macross so i can have pull the 3D models and cards (very nice photos) from the game. to do this i need to have my sony phone rooted and i need to have Magisk so i can hide the root from Uta-Macross so i launch into the game to download the assests to do a dumb. everthing up to this point i have YET to understand what do at all. that link u give - https://topjohnwu.github.io/Magisk/install.html says to this then go here then go here and do this over and over again never saying just do this, this, and this, and your done.
tankball said:
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
Click to expand...
Click to collapse
The instructions by @topjohnwu are pretty complete... They do assume that you are somewhat familiar with things like fastboot, but that is information that can easily be found by searching the big ol' interwebz.
Using a custom recovery is one of the ways of installing Magisk. If this is the route you really want to go I suggest you take a look in your device's forum here on XDA:
https://forum.xda-developers.com/z3
That's usually a good first step since you'll likely find others discussing the same device specific topics.
But if you take a look again in the linked docs, you'll find that you can also use something called boot image patching (which doesn't require a custom recovery at all):
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Rooting and tinkering with your device does require a certain level of knowledge about what you're doing. If you can't follow/understand the instructions available there's a good chance you might mess up your device. If you have your data backed up somewhere off the phone (which you should always have when playing with this stuff) you should be good since a complete and catastrophic failure is very unlikely. It's really annoying to have to set everything up from scratch though...
But if you take a look again in the linked docs said:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching[/url]
Click to expand...
Click to collapse
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
tankball said:
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
Click to expand...
Click to collapse
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Didgeridoohan said:
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Click to expand...
Click to collapse
i should also root the phone again also?
tankball said:
i should also root the phone again also?
Click to expand...
Click to collapse
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Didgeridoohan said:
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Click to expand...
Click to collapse
ok now im lost again. to do date dumps for Uta-Macross i need a rooted phone so i can pull the files without windows again tard and saying "unknow error" when i go to copy the files from my phone. but to play this game i need to hide the root from Uta-Macross so i need to use Magisk. is Masgisk a root itself? im really lost again
Magisk provides a way to do systemless modifications to your device, it is a root solution in itself, and it has the ability to hide itself and it's components from most apps and services that look for a rooted or modded device.
This is kind of the basics, so I reallly suggest you do more research before continuing. The best source for information is the Magisk GitHub page:
https://github.com/topjohnwu/Magisk
Start there, take a look at the readme and the documentation available and continue searching for whatever other information you might need.
I'm not going to be available for further assistance for the next 8 to 9 hours (I hope, but that's entierly up to my little one). G'night.
nothing i did worked. the .zip fail or the D6708_23.4.B.0.319_1288-1477_R30C.ftf file in the .zip witch in the rom from the phone, it will ALWAYS say failed, unsupported/unknow image format.
Morning. Like I posted previously, old (and new) Sony devices have been known to have issues installing Magisk. Search your device's forum for Magisk related posts and you'll likely find the info you need.
Good luck.