CM12/12.1/13 Dark Side Theme not working - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hello. I have a 5th gen kindle fire 7" tablet. I installed CM 12.1 last week. It was working great. Yesterday I decided to try a new theme out. I downloaded the CM12/12.1/13 Dark Side Theme, via the theme modifier. After installation I started having issues with my tablet. Now I can no longer change the theme, launch the Google Play store, go on the internet, or even make changes through the settings. Every time I try, it force closes. When I went to power down, the tablet would only reboot and start up again (yes, i tried rebooting too, hoping there was a command issue or something that had reboot and power off reversed). I tried using flashfire as well and it keeps force closing. It seems any route I take to try and remove the theme, i get booted back to homepage. I've tried factory reset to no avail. I tried using the Super Tool on rootjunky to try to get it back to stock or just do something but all of those options require I go through recovery mode which I can't get to unless I power down, which I can't. Please help.

Did you ever figure this out? This just happened to me.

Shawnshine94 said:
Did you ever figure this out? This just happened to me.
Click to expand...
Click to collapse
Nope. I even emailed the app developer. No response. If I find something out I'll post it on here.

Kenn210 said:
Nope. I even emailed the app developer. No response. If I find something out I'll post it on here.
Click to expand...
Click to collapse
Ok, I finally figured this out. The Day after I went out and bought another one too, go figure. Since I couldn't power down to enter recovery mode, I had to figure out another way to get there. It turns out that if you hold the Power button and the Up button at the same time, It'll power down your phone. From there you can Press the Power button and the Down button to enter into recovery mode. From here there are tutorials on how to go int ADB and sideload the old Kindle Fire firmware. I'm glad I figured this out. I think I'll stay away from those CM 12 themes for a while.

Related

[Q] How to get rid of this "congrat" message after new update

I think I successfully installed the new update last night.
But everytime I reboot the phone, this same message keeps popping up.
----------------------------------------------
Congratualtions!
New software is update for phone is installed.
Phone is ready for use.
----------------------------------------------
*When I click Software Update again, it says "No Firmware"
*My phone also tries to connect to DM server right after every single boot
*My phone was never rooted, never tempered with.
There is something wrong with the update. Will this message go away in time?
tommae said:
I think I successfully installed the new update last night.
But everytime I reboot the phone, this same message keeps popping up and it seems the boot-time got slower than before.
Congratualtions!
New software is update for phone is installed.
Phone is ready for use.
Will this message go away in time? do I need to disable it from somewhere?
Click to expand...
Click to collapse
Mine did it maybe the first 5 times, but it seems to have gone away now
I am seeing the same thing. I think I've seen it 4 or 5 times by now. Will try a few times, to see how many times more it does that.
btw, mine's rooted, with stock firmware.
I rebooted at least 20 more times but the msg still pops up . Mine has never been rooted btw.
The problem isn't just the message.the update is being downloaded and installed everytime I reboot. In one instance, I was in the basement with bad signal, and it took about 30mins before it finished the update - and all that time, it wouldn't let me go past the password screen (my corporate acct requires me to have a password on the device).
So, is it just the 3 or 4 of us with this problem?
Sent from my SAMSUNG-SGH-I897
Try maybe rebooting through recovery (using the 3 button trick?)
Brynne85,
Could you explain the 3-button trick?
Thnx.
Sent from my SAMSUNG-SGH-I897 using XDA App
If u are getting the message that.....your update was installed successfully.... after ever reboot of the phone. In order to get rid of this message you need to dial this code from your phone. Code is *2767*3855# (be aware that code will factory format you phone so what this means is that u will loose every thing on the phone. For example: downloaded apps etc. I got this advise from samsung level 3 tech support. I did this on my brothers stock samsung captivate not rooted or anything, just stock. Also i am not responsible for anything that happens to u phone due to being rooted or whatever when preforming factory format. Backup u stuff like contacts or whatever.
hkk said:
Brynne85,
Could you explain the 3-button trick?
Thnx.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Turn your phone off, then press both the up & down volume buttons (hold them in) then press and hold in the power button as well. Continue holding all 3 until the ATT logo shows up, then let go of the power button, and a few seconds later, let go of the volume buttons. Your phone should boot up into a recovery console with blue letters. You'll use the up/down volume & power buttons to navigate this. But to do a reboot, I believe it's the first option and it will tell you to press the power button to "select" it...
May wanna try that before doing a whole format of your phone, but can't promise it'll work :-/ I just know mine quit doing after about 5 times and I'm pretty sure at some point between those times, I did this recovery thing just to see if my buttons worked (as some reported they couldn't get this to happen for them)

Boot loop

And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks

Strange Problem

This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Pull the battery fo a few and wait before a reboot?
http://www.youtube.com/watch?v=TGjBRAVZKW4&feature=youtube_gdata_player this is the issue that's happening.
Sent from my MB860 using XDA App
so you said you went in to recovery and it did nothing? So you couldn't even get recovery to load? and are you stock or rooted with clockworkmod recovery?
I can't even get it into recovery. I hold the volume keys and power buttons and it just does the boot up then black screens.
Sent from my MB860 using XDA App
Just hold down the volume down button, then hold down the power button also. Continue to hold both through the lg splash, then it should be into recovery.
Sent from my VS910 4G using XDA Premium App
isoutsider said:
This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Click to expand...
Click to collapse
I had the same thing happen to mine 20 days after I got it. I had to have it replaced under the warranty, which means they had to ship it next day air.
I've heard of a few other people with the same problem.
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Unfortunately you are going to have to get a replacement from VZW. If you are within the 14 day period you can just swap it at the store. otherwise you have to go through the Warranty folks and make sure you have them ship it to you overnight.
isoutsider said:
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Click to expand...
Click to collapse
Do you have Clockwork installed?
If so, this is an easy fix.
If not, well, it's a little tougher.
The gist of what's happening is easy to find by connecting your phone while it's booting to USB and running "adb logcat" on your desktop.
That will give you the boot logs and the exact reason for what's happening.
If you're running my decrapified ROM, you may want to switch back to the stock ROM. Go to my stock NANDROID thread, download that, put it in the right folder on your SD card, then boot into clockwork and follow the instructions in the stock nandroid thread.
Make sure you clear data also!
No need to call verizon
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
isoutsider said:
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yep, having ADB access is a surefire way to get your phone up and running again.
But, just for future reference, LG has a failsafe firmware updater that will always work, no matter what state the phone is in.
It's not super easy to set up, but it will fix a phone no matter how broken the software may be.
There's a thread in the Dev subforum with the files and instructions, but the gist is that it's accessed by holding VOLUP+POWER with usb plugged in, then plugging in the battery.
It's successfully recovered 3 phones so far.
It may not be the easiest way to get the phone back, but it has a 100% success rate
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
isoutsider said:
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
Click to expand...
Click to collapse
Well... you could always try my "toggle ADB" trick.
Turn usb debugging on, then back off, then on again.
Then follow the rest of the rooting instructions, but skip the whole exploit section.
(Basically, remount /system as rw, push su, chmod su, and push superuser, and install busybox)
Ironically, the phone doesn't actually NEED any exploits at all-- it's pretty unlocked to begin with!

[Q] I think I Bricked My TP

I was following these instructions http://forum.xda-developers.com/showthread.php?t=1305891
And under step 3 section where it says create a folder called cminstall, I was unclear if that was on the TP or on my PC. I created it on my pc. I follwed the rest of the steps and when I ran novacom my TP did it's install thing and then at the very end there was a message
"no cminstall dir found, nothing to install.
Power off when ready"
I guess cminstall was supposed to be on the TP. No I can't turn it off. I tried the power button, I tried the power and volume up button, and the center button and the up button, nothing.
Am I hosed? If I can't turn it off how do I web doctor it to get back to webOS?
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
justfor4 said:
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
Click to expand...
Click to collapse
Yeah I just found that button combo on the webos nation forum. Dammit I just made a useless help me thread.
Well, though that this its true, the issue is solved.
And this is thankfully a good thing...
Great
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
lvpre said:
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
VGSmatt said:
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
Click to expand...
Click to collapse
Why don't u test the xronified version? U will be happier
+1 happy user of xronified version
klear72 said:
Why don't u test the xronified version? U will be happier
Click to expand...
Click to collapse
What makes xron better? After only one day, I like cm way more then webos!
Leoisright
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
Too many..or only...Leoisright !!! I've never known anyone who works much as he did and now with the help of MiSfit it will be even better
http://forum.xda-developers.com/showthread.php?t=1321335
What makes xron better?
Click to expand...
Click to collapse
It's faster+beter games support+some fixes like wi-fi. Check benchmarks of cm a3.5 and latest xronified version
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
the rom developer leo has been so enthusiastic and has been pushing updates one after the other in a regular basis and the rom is fast. you will see it when you try it . moreover few more devs have just joined the development which in my opinion is going to make the rom rock
ok before i got to into cm7, i made the jump to xron. You guys were right, its pretty fantastic.
You can't brick your TouchPad.
It's not possible.
Yeah, I may have panicked a little when all the button combos I knew weren't working. Then I found the correct button combo on the webos forum.
I'm having an issue. I was prompted to update to webOS 3.0.4. Long story short after and hour and a half with the black HP screen coming and going I decided something probably wasn't right. I downloaded webOS doctor and am trying to run it, but for the life of me I can't get my PC to see my TP. My PC keeps making the "USB connecting" sounds. I think the problem is that it's looping between the HP logo and total black screen.
F***ing HP and their ****ty software! Anyone have any ideas on what I can do? I've tried holding menu/power and it just keeps looping
Thanks in advance
edit: got it working, here's what I did thanks to webOS support:
Hold power and press center button 15 times. This turns device into a powered off state.
Hold power and volume up to enter USB mode
Download and run webOS doctor.
After about a total of 3 hours of thinking my TP was dead, I kind of have a new found love for it, lol
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
VGSmatt said:
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
Click to expand...
Click to collapse
Xron comes with Gapps but Leo replaced stock browser with Dolphin (which is better). There is a problem if random FCs but they are so much less then what I had in CM7...as Xron is also based on CM7...you will see few bugs...but overall it made my TP so useful..
i agree, this is so much better then before. i don't see dolphin in my app drawer, no matter, firefox is working fine.
yip, it is better and if you want some eye candy the SPB shell 3D is really cool

[Q] Bricked?

Hi guys,
I've screwed up royally...
I got my Kindle Fire 2 (not HD) today and... tried to root it. Unsuccessfully.
It's now got a flickering Kindle Fire logo and it's responding with a 30 second to 1 minute lag (so unusable).
My Vista laptop still recognises it as an ADB device but I don't know what to do now
Can anyone help me please?
Many thanks.
EDIT: I've held the power button for 20+ seconds and it still does this...
Same thing happened to me today on my fire 2. Do a reset to factory settings in the device options. It'll takes some time to get there but it is no problem. Someone should warn people with recently purchased KFs about rooting. Doesn't seem to work anymore!
433Mhz said:
Same thing happened to me today on my fire 2. Do a reset to factory settings in the device options. It'll takes some time to get there but it is no problem. Someone should warn people with recently purchased KFs about rooting. Doesn't seem to work anymore!
Click to expand...
Click to collapse
Thanks I'll try that and report back
It's beyond laggy though, so it's gonna be a pain
UPDATE: I love you 433Mhz It's worked, I wish I could give you a million thanks. I really hope Amazon reverse their stance on the locked bootloader with an OTA update, because that was all I wanted to start with haha.
Thanks again mate
Think I'm bricked
The root process went perfectly clean and it rebooted fine. Then I couldn't find instructions to install the Play Store. I finally found some that said to copy GoogleServicesFramework.apk to the Kindle and install, I did that cleanly. Then to copy vending.apk to /system/app/ and I did that and was able to change permissions to 664. I then rebooted the Kindle. It goes straight to the triangle. If you push the power button 5 times it reboots to the same thing. I did not try to flash TWRP to it because I saw some having problems with it. I have 10.2.1 on it. I have the proper drivers installed and each time the Kindle rebooted during boot the computer beeped that it recognized it. Since the triangle the PC no longer recognizes it, it does not show up in Device manager and it does not show up in explorer as connected. I think it is hard bricked but wanted to run it by everyone.
Sparkym3's root process went flawlessly on my Fire2, It only took a couple minutes to root and be booted to a working Kindle. I just screwed up the market process somehow.
Let me know your thoughts. Being that everything went so clean with rooting I have a hard time thinking it can be the drivers, cable, usb port.
I've rooted a phone and 2 tablets multiple times but never had this happen. Any help is greatly appreciated.
This is an exact description of the problem:
I get the Kindle Fire logo, sits there several seconds, reboots and the power light goes out and back on, then the logo comes up again, it flashes a couple of times then I get an orange triangle with an exclamation point inside Below that is a message stating "Your Kindle device cannot boot".
Below that is You can reset device to Factory defaults to fix this issue (all data will be deleted from the device"
<Menu options>
To reboot your device, press and hold the power button for 4 seconds and release.
To reset to Factory Defaults, press the power button 5 times in succession.
Well the 4 second thing does not work at all, more like 20 seconds. The pressing 5 times just reboots to the same problem and warning triangle. I tried fastboot commands but nothing.and my laptop no longer recognizes the Kindle and nothing is in Device Manager about the Kindle now. The fastboot command just says waiting for device. As I said above the root process went flawlessly and the Fire reboot 3-4 times and the laptop beeped each time that it saw it.
Any help is greatly appreciated
So, I'm totally lost. Maybe a frisbee at this point.
http://forum.xda-developers.com/showthread.php?p=33156486
Trys this
Sent from my SAMSUNG-SGH-T989 using xda premium
---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------
Ops wrong link srry tthast for the hd :banghead:
Sent from my SAMSUNG-SGH-T989 using xda premium

Categories

Resources