[Q] Home button doesn't work - 7" Kindle Fire HD Q&A, Help & Troubleshooting

I'm using Amazon Tate CM11 on my Kindle Fire and everything was going smoothly. After a few of the official updates, I don't recall which one, my home button stopped working. Everything else works fine. When I downgrade to previous updates, nothing gets fixed. Thank you for the help.

Did you try wiping cache and dalvik cache from twrp after downgrading?
Sent from my Amazon Tate using Tapatalk

Hashcode did say this next update would not be for the faint of heart. Might want to jump back an update or two.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

Where did Hashcode say that? And I'm sorry, it's been a long time, I rooted and flashed using a youtube video back in March, so I'm not famiiar with anything. How do I do the fix?

Reboot into recovery and hit wipe, choose advanced, only check cache and dalvik cache.if you want a easy way to get into recovery you can use "adb reboot recovery" or enable developer menu and check off advanced reboot and your reboot menu in cm will give you the option. There's always the normal waybas well, hood volume up as soon as you turn the kindle on until you see the twrp logo. I think it is volume up, might be volume down, I don't do it that way much so it is hard to remember.
Also to refer to the question about hashcode, he said it on the cm 11 thread as a heads up on the latest nightly that he would be rolling out.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
Reboot into recovery and hit wipe, choose advanced, only check cache and dalvik cache.if you want a easy way to get into recovery you can use "adb reboot recovery" or enable developer menu and check off advanced reboot and your reboot menu in cm will give you the option. There's always the normal waybas well, hood volume up as soon as you turn the kindle on until you see the twrp logo. I think it is volume up, might be volume down, I don't do it that way much so it is hard to remember.
Also to refer to the question about hashcode, he said it on the cm 11 thread as a heads up on the latest nightly that he would be rolling out.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
It was the volume up button. I followed your instructions, didn't work. Also, the top right menu doesn't pull down, which was a problem I had from the start of the home button problem as well.

I hate to reccomend a factory reset but you might want to go into twrp and factory reset it under wipe. Just backup any appdata for apps you want to save the data off of like games, I think you can do it with titanium backup, I just do it manually myself.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
I hate to reccomend a factory reset but you might want to go into twrp and factory reset it under wipe. Just backup any appdata for apps you want to save the data off of like games, I think you can do it with titanium backup, I just do it manually myself.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I really appreciate the help. I've gone into twrp, wiped system, data, and both the cache, factory reset, and tried installing the latest zip. It says "unable to open zip file," even after doing it through adb sideload.

FIXED
stunts513 said:
I hate to reccomend a factory reset but you might want to go into twrp and factory reset it under wipe. Just backup any appdata for apps you want to save the data off of like games, I think you can do it with titanium backup, I just do it manually myself.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
FIXED. I did a complete factory reset, I installed Flash Fire and reset through there. For some reason, THAT worked. Reboot into recovery after flash fire wipe and twrp did the rest. TWRP alone couldn't do it, I guess.

RossPeterson said:
Where did Hashcode say that? And I'm sorry, it's been a long time, I rooted and flashed using a youtube video back in March, so I'm not famiiar with anything. How do I do the fix?
Click to expand...
Click to collapse
In the CM11 thread.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
In the CM11 thread.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well that was helpful

Related

[Q] bootloops after flashing rom

I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
nvillamob said:
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
Click to expand...
Click to collapse
Before flashing a ROM, clear cache/ dalvik-cache from recovery. If you don't do these, then you will see bootloops.
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
nvillamob said:
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you are changing ROMs, its always advisable to do a factory reset in addition to clearing cache and dalvik. Try it
Sent from my Nexus One
Best advice is to skip ROM manager and always do everything manually in recovery, this has never been a problem for me
And just because, I would suggest using 4ext recovery as in my opinion it is by far the most superior recovery... Just saying
Sent from my Nexus 4 using xda premium
Unfortunately, I've tried flashing manually via recovery too...still bootloops
Check md5sum of ROM (maybe bad download)
Make sure you wipe fully (manually in recovery or with fastboot)
Make sure you meet requirements of ROM in op (as in you flashed gapps if needed or you have a large enough system partition etc)
Sent from my Nexus 4 using xda premium
yeah, i haven't checked the md5's but it's odd that it's happened with both official miui and cyanogenmod. i did wipe cache and dalvik. i think i'm just going to give up. i'd do a factory restore but don't want to do that because then i'd have to root my phone again. i rooted the phone using a Vista computer but now I'm back home and my computer runs windows 8. from what I can tell, installing the android SDK is kinda complicated on W8.
Factory reset is needed and will not mean you have to reroot your phone, this is something that would be done before each flash, in fact the cleaner the wipe the less chance of an issue.
Also there is no need for the SDK to root (but its easy to get for windows 8 anyway and tools such as fastboot and adb are very handy... Also there are other ways to get these tools without the SDK) but all that besides the point, these are your steps
Nandroid backup
Wipe everything as clean as possible
Flash ROM and anything else needed (gapps etc)
Reboot
This is the procedure you should follow for any ROM flash for any android and never a need to reroot in between
Best of luck
Sent from my Nexus 4 using xda premium
I really appreciate the help. the reason I mention the SDK is that my computer doesn't recognize my phone unless I install the SDK and the associated drivers. So I'd hate the wipe my phone so that I can flash a rom, but then be unable to flash a rom because I'm not rooted!
But you feel confident that if I factory reset, I won't loose root?
I factory reset daily! You'll be just fine, when you factory reset and wipe all partitions you are following the proper procedure to change roms. When you flash the new one you are sure to still have root access
Sent from my Nexus 4 using xda premium
well, did a factory reset last night but i'm still having the same problem. I'm at a loss.

P880 won't boot after 442 flashing

Hi guys,
Need your assistance in this. I downloaded the 4.4.2, the Gapps (stock version), and the CWM Touch 6044. Flashed successfully the 6044. Rebooted, and flashed omni 442 and then the gapps. Did a wipe data/factory reset. Then pressed reboot device. The phone will restart and stay stuck at the Omni Logo. No progress from there at all. Did a few other reboots and different combinations to the above but to no result. Stuck there. Finally, did a restore from my backup just to have a phone again..Any idea what I did wrong from the start?
How long did you wait at the first bootup? It took quite long for me, so I'd suggest waiting up to 20 minutes before turning off the phone. Try flashing with the most lightweight Gapps package, that's what everyone seems to be using. You could also try wiping cache and dalvik cache.
Nalefyre said:
How long did you wait at the first bootup? It took quite long for me, so I'd suggest waiting up to 20 minutes before turning off the phone. Try flashing with the most lightweight Gapps package, that's what everyone seems to be using. You could also try wiping cache and dalvik cache.
Click to expand...
Click to collapse
Well, did the Dalvik cache but later on, when I was experimenting. I had waited at least 16/18 minutes till my patience ran out...
Decided to have one more go right now. 1. Did a wipe data / factory reset. 2. After that, wiped Dalvik cache. 3. Presently installing Omni and then will install gapps. 4. Will reboot and leave it to boot until I leave work. (couple of hours from now). And will see what happens.
- Forgot to add thaty in all instances, I selected YES in the "root" question in the end. -
Thanks for replying!
---Update
Nothing changed. Stuck at the Omni logo for about 50 minutes..
The_Sniper said:
Well, did the Dalvik cache but later on, when I was experimenting. I had waited at least 16/18 minutes till my patience ran out...
Decided to have one more go right now. 1. Did a wipe data / factory reset. 2. After that, wiped Dalvik cache. 3. Presently installing Omni and then will install gapps. 4. Will reboot and leave it to boot until I leave work. (couple of hours from now). And will see what happens.
- Forgot to add thaty in all instances, I selected YES in the "root" question in the end. -
Thanks for replying!
---Update
Nothing changed. Stuck at the Omni logo for about 50 minutes..
Click to expand...
Click to collapse
So don't flash gapps and ROM back to back. Flash ROM then reboot and after waiting 5 mins reboot and flash gapps again.
Sent from my LG-P880 using XDA Premium 4 mobile app
Maybe format /system in addition to the factory reset (it's under mounts and storage). So you get a completely clean install
Sent from my LG Optimus 4X HD
Thanks for your advice guys - Unfortunately I don't see any results
I booted in recovery and in this order: Wiped data / did factory reset - then wiped Dalvik - then did format /system - then flashed successfully Omnirom and at the end select YES in the "root" question. Did not touch the Gapps.
Same result - has been in the Omni Logo for more than half an hour.
Can someone tell me the absolute prerequisites needed to install and boot normally? Apart from CWM Touch 6.0.4.4 that is?
Thanks in advance
I really don't see any more required steps to install OmniRom. Did you try another downloaded OmniRom? Maybe something is wrong with your used version.
Sent from my LG Optimus 4X HD
The_Sniper said:
Thanks for your advice guys - Unfortunately I don't see any results
I booted in recovery and in this order: Wiped data / did factory reset - then wiped Dalvik - then did format /system - then flashed successfully Omnirom and at the end select YES in the "root" question. Did not touch the Gapps.
Same result - has been in the Omni Logo for more than half an hour.
Can someone tell me the absolute prerequisites needed to install and boot normally? Apart from CWM Touch 6.0.4.4 that is?
Thanks in advance
Click to expand...
Click to collapse
Select No in the root option.
Sent from my LG-P880 using XDA Premium 4 mobile app
[email protected] said:
Select No in the root option.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That shouldn't do any damage (I tried both ways and didn't notice any difference )
I really think your downloaded ROM zip is corrupt as nobody else having problems with it
Sent from my LG Optimus 4X HD
Omario-242 said:
That shouldn't do any damage (I tried both ways and didn't notice any difference )
I really think your downloaded ROM zip is corrupt as nobody else having problems with it
Sent from my LG Optimus 4X HD
Click to expand...
Click to collapse
Yeah, will redownload - choosing NO also did not make any difference
Did you mount all under mounts and storage?
Coolneng said:
Did you mount all under mounts and storage?
Click to expand...
Click to collapse
all I did under mount & storage is the "format /system". Did not mount anything any other time. Is this part of the procedure too or are we shooting blind here? - Cause directions in the post say flash rom, flash apps, wipe data & reboot, let alone the 15 other combos I've done.
Haven't tried anything yet cause I need to re-download the ROM and presently I can't get any of my 3 PCs "see" the LG's contents like a flash drive. Can only do it in my work's laptop. Beats me why..
If you don't have important data, format internal storage too. No idea for 4.4, but if you flash kdz, this is a must.
Sent from my LG-P880 using XDA Premium 4 mobile app
[email protected] said:
If you don't have important data, format internal storage too. No idea for 4.4, but if you flash kdz, this is a must.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks Black, will try that too. Have everything I need in Helium right now, ready to be restored at any time.
The_Sniper said:
all I did under mount & storage is the "format /system". Did not mount anything any other time. Is this part of the procedure too or are we shooting blind here? - Cause directions in the post say flash rom, flash apps, wipe data & reboot, let alone the 15 other combos I've done.
Haven't tried anything yet cause I need to re-download the ROM and presently I can't get any of my 3 PCs "see" the LG's contents like a flash drive. Can only do it in my work's laptop. Beats me why..
Click to expand...
Click to collapse
It is important to mount everything as far as I know. In my old device's forum it always a step that is specified, I never see it in these forums though.
Try it, you don't loose anything.

Slow system on CM 11 M12

So today I installed M12 with clean install. At first, everything was veery slow, like it needed 10-15 sec for one operation. Apps were opening to black screen or opening with huge delay. After few hours, it got better, UI is responsive, but apps are still opening slowly(no black screens through). How can I help it?
Sent from my C6603
asakurato said:
So today I installed M12 with clean install. At first, everything was veery slow, like it needed 10-15 sec for one operation. Apps were opening to black screen or opening with huge delay. After few hours, it got better, UI is responsive, but apps are still opening slowly(no black screens through). How can I help it?
Sent from my C6603
Click to expand...
Click to collapse
I suffered a while with this myself, and finally I did a full system reset, even wiping all the appropriate partitions and folders including MEDIA. Since then my Nook HD+ has been snappy and reliable.
danshane said:
... and finally I did a full system reset, even wiping all the partitions...
Click to expand...
Click to collapse
The only partitions that should ever need to be wiped are /cache, /data, and /system. Wiping some partitions other than these 3 (e.g., /rom and /factory) will brick your Nook.
Sent from my C6603
digixmax said:
The only partitions that should ever need to be wiped are /cache, /data, and /system. Wiping some partitions other than these 3 (e.g., /rom and /factory) will brick your Nook.
Click to expand...
Click to collapse
I did exactly that. Now it's better, but some apps are still slow when opening, especially google apps
Sent from my C6603
asakurato said:
I did exactly that. Now it's better, but some apps are still slow when opening, especially google apps
Sent from my C6603
Click to expand...
Click to collapse
asakurato said:
So today I installed M12 with clean install. At first, everything was veery slow, like it needed 10-15 sec for one operation. Apps were opening to black screen or opening with huge delay. After few hours, it got better, UI is responsive, but apps are still opening slowly(no black screens through). How can I help it?
Sent from my C6603
Click to expand...
Click to collapse
My Nook HD+ became intolerably slow on CM roms - so slow that after years of running CM I switched to the latest version of Liquidsmooth in the forums. Liquidsmooth isn't exactly speedy, but it is usable.
freecity said:
My Nook HD+ became intolerably slow on CM roms - so slow that after years of running CM I switched to the latest version of Liquidsmooth in the forums. Liquidsmooth isn't exactly speedy, but it is usable.
Click to expand...
Click to collapse
Just did factory reset and everything is super smooth now!
Sent from my BN NookHD+ using XDA Free mobile app
digixmax said:
The only partitions that should ever need to be wiped are /cache, /data, and /system. Wiping some partitions other than these 3 (e.g., /rom and /factory) will brick your Nook.
Click to expand...
Click to collapse
Right-o! I edited my post to clarify what I actually did. Thanks for that correction -- I might have done someone a mischief.
asakurato said:
Just did factory reset and everything is super smooth now!
Sent from my BN NookHD+ using XDA Free mobile app
Click to expand...
Click to collapse
I'm having the same issue as the OP. Followed these instructions to upgrade to CM11 M12 :
http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171
And now stuck with a very sluggish tablet - any apps opening are really slow - has been like this for a couple of days now. Battery life also seems to be worse.
You suggested a factory reset - do you mean the factory reset option in the Backup and reset menu?
Almost tempted to downgrade back to 10.2.1 - it had its faults, but was still better than this.... but i can't find any info on how i'd do that - can i use my current version of CWM Recovery (had to update it to do the upgrade) and just flash the old version of CM10 and the relevant Gapps?
jonas_r said:
I'm having the same issue as the OP. Followed these instructions to upgrade to CM11 M12 :
http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171
And now stuck with a very sluggish tablet - any apps opening are really slow - has been like this for a couple of days now. Battery life also seems to be worse.
You suggested a factory reset - do you mean the factory reset option in the Backup and reset menu?
Almost tempted to downgrade back to 10.2.1 - it had its faults, but was still better than this.... but i can't find any info on how i'd do that - can i use my current version of CWM Recovery (had to update it to do the upgrade) and just flash the old version of CM10 and the relevant Gapps?
Click to expand...
Click to collapse
No, you can't use the new CWM to go back to CM10.2.1. It requires the old CWM. And to factory reset boot to CWM to do it (either version).
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
No, you can't use the new CWM to go back to CM10.2.1. It requires the old CWM. And to factory reset boot to CWM to do it (either version).
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I performed the wipe data & factory reset as instructed after updating CWM recovery and before installing CM11 and the Gapps file - is that the option i could try now? That wont wipe anything "important"?
Also, if i was to downgrade to 10.2.1 could i do it by just copying the files to the internal or external memory and doing the following? :
downgrade the CWM recovery, reboot into the new recovery, wipe data/factory reset and then install chosen CM10 and Gapps?
Thanks for the help!
jonas_r said:
I performed the wipe data & factory reset as instructed after updating CWM recovery and before installing CM11 and the Gapps file - is that the option i could try now? That wont wipe anything "important"?
Click to expand...
Click to collapse
The current ROM, all the apps and their data/settings would be gone -- but your user-media content should be intact.
Also, if i was to downgrade to 10.2.1 could i do it by just copying the files to the internal or external memory and doing the following? :
downgrade the CWM recovery, reboot into the new recovery, wipe data/factory reset and then install chosen CM10 and Gapps?
...
Click to expand...
Click to collapse
Yes.
jonas_r said:
I performed the wipe data & factory reset as instructed after updating CWM recovery and before installing CM11 and the Gapps file - is that the option i could try now? That wont wipe anything "important"?
Also, if i was to downgrade to 10.2.1 could i do it by just copying the files to the internal or external memory and doing the following? :
downgrade the CWM recovery, reboot into the new recovery, wipe data/factory reset and then install chosen CM10 and Gapps?
Thanks for the help!
Click to expand...
Click to collapse
If you only factory reset (in other words don't wipe /system) then your ROM stays and should still run, just settings and installed apps removed.
And yes on procedure to downgrade.
Sent from my BN NookHD+ using XDA Premium HD app
jonas_r said:
I'm having the same issue as the OP. Followed these instructions to upgrade to CM11 M12 :
http://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171
And now stuck with a very sluggish tablet - any apps opening are really slow - has been like this for a couple of days now. Battery life also seems to be worse.
You suggested a factory reset - do you mean the factory reset option in the Backup and reset menu?
Almost tempted to downgrade back to 10.2.1 - it had its faults, but was still better than this.... but i can't find any info on how i'd do that - can i use my current version of CWM Recovery (had to update it to do the upgrade) and just flash the old version of CM10 and the relevant Gapps?
Click to expand...
Click to collapse
Yes I did it from backup and reset menu, but I think it did reset with cwm anyway, so it doesn't matter.
Sent from my BN NookHD+ using XDA Free mobile app
Just to share my observations. In general the performance is very good. Currently I'm on M12.
I'm mostly using it to read PDFs.
In the past I observed, that after a while of operation it gets slow and even the touchscreen is not responding properly. After a reboot everything is fine again. I couldn't observe it anymore lately, but not sure whether this is because of I did a reboot (before it becomes necessary).
A question because I first read the thread title wrong: will there be a CM12 for this device? Or other way around, is someone (leapinlar?) working on a port lollipop to nook or is intended to do so?
starbright_ said:
Just to share my observations. In general the performance is very good. Currently I'm on M12.
I'm mostly using it to read PDFs.
In the past I observed, that after a while of operation it gets slow and even the touchscreen is not responding properly. After a reboot everything is fine again. I couldn't observe it anymore lately, but not sure whether this is because of I did a reboot (before it becomes necessary).
A question because I first read the thread title wrong: will there be a CM12 for this device? Or other way around, is someone (leapinlar?) working on a port lollipop to nook or is intended to do so?
Click to expand...
Click to collapse
There should be, but I dont know who is working on it.
Sent from my C6603

TWRP doesn't show files after Chroma M Rom install

Complete noob so i'm sure it's something simple i'm missing, but i rooted yesterday and am using twrp for recovery. I have the new chroma M up and running but now when I go back to recovery all the files I had with my backup and other roms are not showing. When I boot into chroma and use my file explorer I can see them in the data shortcut on the phone, and have even moved my files to other folders on the phone, but when i go back into recovery I can never find them. Is there a way for me to load my backups and roms somewhere that TWRP will see them and boot them?
Same thing happened to me luckily otg worked for me. You'll have to format your data. In twrp recovery. Make back up of your apps and pics and music etc then do it and I would also factory reset it as well.
Sent from my Nexus 6 using XDA Premium HD app
cameljockey1 said:
Same thing happened to me luckily otg worked for me. You'll have to format your data. In twrp recovery. Make back up of your apps and pics and music etc then do it and I would also factory reset it as well.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
It looks like just doing the factory reset fixed it. Thanks!

Stuck on boot animation after ****ing around with layers (SlimLP)

Flashed SlimLP and had been succesfully using it for about a month before I decided to **** around with layers (Evolve and Commute specifically). When I reboot to apply it got stuck on the boot animation, I left it to charge overnight and it was still stuck in the morning. Tried wiping the cache partition but don't want to do a factory reset if there's a way to salvage it (nothing too vital, just pain in the ass having to reinstall all my apps, etc.)
Total noob to flashing and ROMS, etc. No backups that I know of, not sure if there's a custom recovery. Only found the Amazon one and Fastboot mode.
terkrockerfeller said:
Flashed SlimLP and had been succesfully using it for about a month before I decided to **** around with layers (Evolve and Commute specifically). When I reboot to apply it got stuck on the boot animation, I left it to charge overnight and it was still stuck in the morning. Tried wiping the cache partition but don't want to do a factory reset if there's a way to salvage it (nothing too vital, just pain in the ass having to reinstall all my apps, etc.)
Total noob to flashing and ROMS, etc. No backups that I know of, not sure if there's a custom recovery. Only found the Amazon one and Fastboot mode.
Click to expand...
Click to collapse
How did you flash slimlp?
Sent from my KFFOWI using XDA Labs
sd_shadow said:
How did you flash slimlp?
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Flashfire
terkrockerfeller said:
Flashfire
Click to expand...
Click to collapse
do you know which stock system version it was on?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
do you know which stock system version it was on?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
5.1.
terkrockerfeller said:
5.1.
Click to expand...
Click to collapse
you tried wiping cache in Stock recovery?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
you tried wiping cache in Stock recovery?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Yup
You are lucky you can still access the stock recovery. If your device had 5.1.1 then reinstall FireOS 5.1.1 via stock recovery. From that point you can re-root & reinstall your rom + apps & stuff.
Be thankful you're not bricked & don't screw with layers if you don't have a 5.0.1 device. The Fire does not play well with many layers.
blueberry.sky said:
You are lucky you can still access the stock recovery. If your device had 5.1.1 then reinstall FireOS 5.1.1 via stock recovery. From that point you can re-root & reinstall your rom + apps & stuff.
Be thankful you're not bricked & don't screw with layers if you don't have a 5.0.1 device. The Fire does not play well with many layers.
Click to expand...
Click to collapse
Don't know what happened but I can't seem to access the stock recovery any longer. Fastboot mode still works, though. What do I do from here?
Edit: scratch that, I got to the recovery menu again
terkrockerfeller said:
Flashed SlimLP and had been succesfully using it for about a month before I decided to **** around with layers (Evolve and Commute specifically). When I reboot to apply it got stuck on the boot animation, I left it to charge overnight and it was still stuck in the morning. Tried wiping the cache partition but don't want to do a factory reset if there's a way to salvage it (nothing too vital, just pain in the ass having to reinstall all my apps, etc.)
Total noob to flashing and ROMS, etc. No backups that I know of, not sure if there's a custom recovery. Only found the Amazon one and Fastboot mode.
Click to expand...
Click to collapse
I know on my nexus 6P it has a overlay folder, if you delete that it should delete your layers that you added(if that folder exists on this)

Categories

Resources