Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
jonathanmoneill said:
Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
Click to expand...
Click to collapse
Symptoms are similar to a recently reported issue in the Lineage 12.1 thread if you applied the latest Nexus update. If that's the case simply roll back to the prior build.
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
jonathanmoneill said:
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
Click to expand...
Click to collapse
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Davey126 said:
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Click to expand...
Click to collapse
Thanks for the ROM advice. I love the Nexus ROm but I've been tempted by lineage for a while so I might take this opportunity to give it a go
In relation to sorting my current issues, the device doesn't shut down while the grey logo is being displayed, the OS loads and I usually get about 30-90 seconds of functioning before it dies again. Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
jonathanmoneill said:
Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
Click to expand...
Click to collapse
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Davey126 said:
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Click to expand...
Click to collapse
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
jonathanmoneill said:
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
Click to expand...
Click to collapse
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Davey126 said:
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Click to expand...
Click to collapse
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
jonathanmoneill said:
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
Click to expand...
Click to collapse
I was the one having the update issues, but it was on the Lineage ROM! Looks like whatever ggow did, it's affecting both Nexus and Lineage. I think I'll just roll back to the previous build then restore apps.
Related
im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!
1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Flash custom rom and enjoy lollipop
pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad
anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.
these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:
pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:
Tip: When you receive your Fire 2015 tablet, don't setup WiFi if you want to install custom ROM (skip WiFi setup)
Why: They are still shipping with FireOS 5.0.1 and it will autoupdate to 5.1.1 as soon as it sees Internet connection (it doesn't ask and takes over tablet)
Why is that bad: Because it's easier to install custom ROM with 5.0 and still a pain/riskier if from 5.1.1 (as of December 2015)
Why is this method easier/safer: No need to root first, no messing with original ROM (can backup first), no need to enable Developer mode, no need to grant ADB permissions
Prerequisites:
- This method will not work if tablet has upgraded to FireOS 5.1.1 or higher, only 5.0.x works
- Need fastboot tools installed on a computer (Windows tools/drivers here if needed) or (Linux/Mac)
- Download TWRP Recovery here to same computer
- Download your new ROM/support files of choice to an external SD Card
- If on Windows, to keep things simple you might place fastboot command, Recovery image in same folder/directory
Install: Fastboot TWRP Recovery from computer, Install Custom ROM from SD Card
- When you receive Fire, don't power it on (or if you do, don't setup WiFi as it will autoupdate to 5.1.1)
- Copy your downloaded ROM image and support files to an SD card, then insert SD into tablet
- Boot tablet directly into fastboot (power button and volume up button)
- USB attach tablet to computer that has fastboot tools and TWRP recovery image
- Unlock and Boot directly into TWRP image from computer terminal or command line
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot boot TWRP_Fire_2.8.7.0_adb.img
- Takes seconds to transfer file then recovery should appear
- Optional but recommended: From TWRP, Backup Stock Amazon ROM to external SD card
- Factory Reset from TWRP Recovery
- Install ROM and support files from TWRP via external SD card
- Reboot, profit
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
xenokc said:
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
Click to expand...
Click to collapse
Did you buy it from Amazon? I just ordered mine yesterday.
stef-nix said:
Did you buy it from Amazon? I just ordered mine yesterday.
Click to expand...
Click to collapse
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
xenokc said:
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
Click to expand...
Click to collapse
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
stef-nix said:
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
Click to expand...
Click to collapse
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
xenokc said:
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
Click to expand...
Click to collapse
Gotcha. As soon as I opened it, I blocked OTA updates. Rooted/installed SuperSU, and backed up the stock ROM.
I'm currently running CM12.1 and it's working perfectly.
I did not like how it auto signed into my Amazon account once connecting to WiFi (with OTAs blocked)
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Parhelius said:
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Click to expand...
Click to collapse
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
stef-nix said:
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
Click to expand...
Click to collapse
I connected to wifi and the updates came through automatically. I hadn't read threads like this one beforehand unfortunately, so I didn't realise that would happen.
Sounds like Amazon is still shipping with 5.0.1 so this method can still apply for those who catch this thread before receiving/booting their tablet. What's nice about this method is you can backup original ROM before modding and don't need to root. Sounds like many have thrashed their tablet trying to root.
Just dont connect to wifi and your fine.
Amazon having a $40 sale, if you ordered one might not setup WiFi when first receiving - re-read first post why.
http://www.amazon.com/Fire-Display-Wi-Fi-GB-Includes/dp/B00TSUGXKE
Just ordered 3 today ... Can't wait to tinker with it.
Thanks for the heads up regarding auto-update!
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
percussionking said:
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
Click to expand...
Click to collapse
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
vn33 said:
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
Click to expand...
Click to collapse
My 4th one came from Ft. Worth. I immediately booted into recovery mode but could not boot TWRP. Obviously this turned out to be a 5.1.1 system. If this had been a 5.0.1 system, the first full boot would have been to CM rather than to stock. So if 5.1.1 is installed at the factory you can't get your TWRP on this way.
Just got mine today it had 5.0.1 creating a backup now
Hi,
where can you download twrp from their page?
I see their list of devices but none of them says fire 5th generation.
https://twrp.me/Devices/
THANK YOU!
No you get twrp from here http://forum.xda-developers.com/amazon-fire/development/wip-bootable-recovery-kffowi-ford-t3238683
I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.
sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Why did you need root for the Google now launcher?
mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?
Your original post made it seem like you need root for double tap to wake and Google now launcher.
sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).
HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?
is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Pcprik said:
Hello and thanks for reading!
I have a Kindle Fire 5th Gen that was just given to me. I'd like to get rid of the Amazon OS and install anything (I'll take CM or whatever). It is currently running 5.1.2 yet KingRoot v4.9.2 says it is 5.1.1.
I've tried KingRoot a few times (apparently you need root to get TWRP going) and nothing happens - it keeps failing.
I've gone through some RootJunky videos but those aren't updated for 5.1.2 via Windows.
I'm at a loss of what to do next. This video says that installing an old version of Fire OS will brick your Kindle.
All of these different threads have me confused.
My questions are:
I understand that TWRP doesn't work on 5.1.2, so how do I get to a different version of Fire OS? And how do I disable OTA's? Turn off Wifi?
When I get to a different version of Fire OS, will RootJunky's tools work like in his videos?
I apologize if this is already answered in another thread as I can't find it and am new to the Kindle Fire.
I'd like to be able to use it for my school books next semester instead of having to bring the big effin things back and forth. For $50 bucks (retail), this seems like a steal to get a vanilla version of Android running on it!
Thanks in advance!
Click to expand...
Click to collapse
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Davey126 said:
- although your device shows 5.1.2 it is likely running 5.1.2.1 which can not be rooted at present
- you need to reload (sideload) 'pure' 5.1.2 via the stock recovery menu; there are instructions and videos posted elsewhere in this forum
- once on 5.1.2 use the SuperTool to root, block OTA, swap out Kinguser for SuperSU and obtain FlashFire which is used to install custom roms
- TWRP is not an option for your device at this time (nor is it likely in the near future)
- suggest looking through the index for relevant material (link below)
- keep reading; you'll get the hang of it
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Pcprik said:
Thanks!
I may have hit a 'small' snag though. When I put 5.1.2 from the Index page on, Kingroot still didn't work so I put the next oldest version on (5.1.1 I believe). Now it won't startup and just has a black screen - I believe I forgot to select wipe cache before restarting. When I plug it into my Surface, Device Manager keeps making noises and I have installed the MTK VCOM drivers. I'm going to try to put 5.1.2.1 back on but I'm wondering if this thing is actually bricked? According to this thread it's possible to 'unbrick' it but if it doesn't turn on, how does it get into recovery mode?! Perhaps it's in recovery mode now with the blank screen? When I do 'adb devices', nothing shows up so I'm guessing it's not connected? Even doing 'adb sideload <filename>' shows no devices connected.
Thanks again!
Click to expand...
Click to collapse
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
That's what I thought.
Thanks again for your help!
Davey126 said:
Your device is bricked; can't roll back to 5.1.1 from any higher version of FireOS. Contact Amazon for a one-time courtesy exchange if still in warranty.
Unbrick methods are technically complex and still evolving; not for the faint of heart. Also don't believe your device is eligible.
Click to expand...
Click to collapse
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Pcprik said:
Just to confirm, I should have put 5.1.2 and then rooted, correct? I may buy a new one.
Click to expand...
Click to collapse
Correct. Summary here; see index for more robust coverage.
Hi Guys,
So I recently got my hands on a kindle fire 5th gen (2015), running the latest OS 5.3.2.1.
I have read many things and many different opinions on what can and cannot be done, and ideally I am looking for a conclusive list i there is one available.
So I was searching and Root Junky has provided custom ROM's and a few other files, however, this is my understanding
CANNOT: root
CAN: downgrade to an older OS, which may allow root, but its likely it will brick it
CANNOT: unlock bootloader for custom ROM installation
CANNOT: install a custom flash zip file from the inbuilt android recovery interface
I dont know if they just happened to crash down and lockdown the fire recently, but pages such as this below, indicate it can (or at least could) be done.
https://www.thepolyglotdeveloper.com/2016/05/install-better-custom-rom-amazon-kindle-fire/
and this, indicates its probably too late since I connected it and downloaded 5.3.2.1.
http://android.stackexchange.com/qu...ot-and-install-cm-12-1-on-5th-gen-kindle-fire
So, is there a conclusive list, aside "using your tablet as out of the box" as to what you can and cannot do to modify the fire 5th gen?
I got mine right before bootloader lock running slim LP haven't updated since used flash fire on 5.1.1 to the best of my knowledge
Sent from my Robin using Tapatalk
FF51, so very lucky, I am really envious actually.
The fire, when not suffering pixel outages, and without a dire need for GPS, makes an excellent hardware base, and from my reading, installng a custom rom would really unlock the xperience of the tablet and give it a much more competitive edge.
Out of curiosity, did you jump straight into the slim build, or did you try others?
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
jeebob said:
Also I have read you cannot install CM13+ due to the limitations of the bootloader, but can you install CM12 instead (I think thats based on lollipop isnt it?) and can you do that with the stock bootloader / recovery module?
Click to expand...
Click to collapse
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Davey126 said:
- can not root (at present) or downgrade (ever) FireOS 5.3.2.1
- bootloader remains locked; no custom kernels or recoveries (eg: TWRP)
- rooted devices can only run Lollipop based ROMs due to kernel restrictions
- custom ROMs must be installed with FlashFire
- see forum index for further info: http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485
Click to expand...
Click to collapse
Thanks Davey, a concise list which is great, now I just have to hope we can get the bootloader and root sorted on 5.3.2.1!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
It looks like the answer is not at this time, as from my reading, 5.3.2.1 cannot be rooted directly with current methods, only 5.3.1 onwards.
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
thats all I have managed to achieve so far, next I want to remove the adverts!
bojkoio said:
Hi every one!
Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
Click to expand...
Click to collapse
Nope - no custom ROMs without root.
---------- Post added at 12:50 PM ---------- Previous post was at 12:49 PM ----------
freaky2xd said:
So I can`t downgrade 5.3.2.1?
My device isn`t rooted and locked. my only achievement was the google play store
Click to expand...
Click to collapse
No - nor likely ever. Best hope is for a root solution.
Well Sh*t
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Edit: A simple reboot after allowing unknown sources fixed the problem and I completed the installation of Google play store
luck_shawn said:
I got all 3 of my daughters a kindle fire 7" 5th gen for Christmas. I ran thru the updates and was going to install the google framework and all that goes with it to be able to install works of ahhh painting app. However, I have hit a roadblock since it seems even tho I have enabled unknown sources and rebooted each device (all running 5.3.2.1) I can download apks but when I attempt to install them, it's like the install button just doesn't register touch response no matter what direction you rotate the device. I'm not new to this, I got kindles because of how easy it was to customize a previous one my 7 year old had, and besides, $30 each was a pretty good deal. So maybe it's a software glitch in the new update, maybe it's that I just don't care enough to dig into it but that's where it stands here.
Click to expand...
Click to collapse
On mine I downloaded the four apks needed installed them (in proper order) using apk permission remover and it worked for me. There's a thread in the fourms I folllwed
I just used the kindle supertool to install the google framework and APK's. once click and leave it to its own devices - a tool by superjunky I think?
Anyway, as for the rotation, I havent noticed any particular problems with it, but I havent done a lot of work with testing it, I will try take a look a bit later!
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
oilyrag said:
i have the same problem. I managed to install Google Play but trying to side load the Popcorntime apk fails with the next and install button not registering touch input, cancel button works fine.
Click to expand...
Click to collapse
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Davey126 said:
Have you enabled FireOS setting that allows installs from unknown sources and then rebooted device?
Click to expand...
Click to collapse
Thought I had rebooted device, done it again, now works. Many thanks
Sent from my SM-N9005 using Tapatalk
I bought two 7" fires on the Black Friday sale to use as home automation panels in the house (with SmartThings). I installed the Play Store but found the SmartThings app was still not compatible . But really I was waiting for the new ActionTiles (web client) to come out. The one Fire upgraded to 5.3.2.1 and I haven't opened the other yet. The Play Store will no longer launch on the 5.3.2.1 tablet either. My original thought was to probably flash a new rom that is not as restrictive but doesn't look like that will happen now. Have a few additional questions for the "can" and "can't" list with 5.3.2.1 please:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Coods said:
1) Can the lock screen be disabled/removed?
2) Can the device be woken up by screen touch?
3) Does the non-root Play Store hack still work? (maybe I just need to redo something after the upgrade?)
4) Are there any browsers I can have auto load the ActionTiles dashboard (web page) and always keep it up and full screen?
Thanks a lot!
Click to expand...
Click to collapse
1) not completely that I have found, unless you keep the screen alive 24/7.
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
3) yes it does, I have uploaded it to about 6 different kindle recently all running 5.3.2.1
4) again root would help, however you can use automateit free or pro from plastered. It's very powerful and you should be able to achieve a lot with it. If it doesn't support it though, tasker is another powerful tool which might be worth exploring
Sent from my D6603 using Tapatalk
jeebob said:
2) power button only however root could allow this but 5.3.2.1 doesn't support (or should I say have a method for) root at this time.
Click to expand...
Click to collapse
No hardware support for this capability regardless of root (re: touch to wake).
Davey126 said:
No hardware support for this capability regardless of root (re: touch to wake).
Click to expand...
Click to collapse
Thanks for confirming davey!
Sent from my D6603 using Tapatalk
Thanks for the info guys, appreciate it! This helps me understand the direction I want to take with these as alarm panels