OK, admitted n00b here. Go easy on me. I turn 60 next week
Anyways, I had no problem installing TWRP on my Kindle Fire. Made a backup. For some reason it didn't install Superuser so I installed that and OTA Rootkeeper. I can not for the life of me remember if I installed FFF (and I just did this yesterday). I used KFU and had no issues with drivers or connectivity or any of that. Following prompts it appeared to be doing exactly what one would expect.
NOW, however, I booted to TWRP to look around. Version is 2.2.1.
On screen at the upper right is a home icon, a back icon, and another one that looks like a little notepaper that I have absolutely no idea what it's for.... BUT (and it's a big but) I must have touched it as I was setting the Kindle in it's upright position in it's case.
I says:
* Verifying filesystems...
* Verifying partition sizes...
And there it sits. Been sitting here about 10 minutes. I have no idea what that icon in the far upper right corner does or what process I may have started. But it seems stuck.
So what's it doing? (Or what's it SUPPOSED to be doing?)
Thanks
Charlie
cjparker said:
OK, admitted n00b here. Go easy on me. I turn 60 next week
Click to expand...
Click to collapse
Nice
I can not for the life of me remember if I installed FFF.
Click to expand...
Click to collapse
FFF is your bootloader. It is the very first thing you see in action when you turn the device on. It will either be a blue Kindle Fire logo, Kindle Fire logo w/Android, or yellow triangle. If you don't see any of the aforementioned boot logos at startup, you don't have FFF installed.
and another one that looks like a little notepaper that I have absolutely no idea what it's for....
Click to expand...
Click to collapse
That is nothing more than a log. It allows you to go back over everything and look at error messages or whatever. Nothing to worry about.
I says:
* Verifying filesystems...
* Verifying partition sizes...
Click to expand...
Click to collapse
This may be from the backup you just created, but if you aren't experiencing any adverse effects such as inability to install ROMs or your backups not bring created, I wouldn't worry about.
And if worse comes to worse and there is something wrong with your device, there is an extremely good chance that it can get fixed pretty easily.
soupmagnet said:
Nice
FFF is your bootloader. It is the very first thing you see in action when you turn the device on. It will either be a blue Kindle Fire logo, Kindle Fire logo w/Android, or yellow triangle. If you don't see any of the aforementioned boot logos at startup, you don't have FFF installed.
That is nothing more than a log. It allows you to go back over everything and look at error messages or whatever. Nothing to worry about.
This may be from the backup you just created, but if you aren't experiencing any adverse effects such as inability to install ROMs or your backups not bring created, I wouldn't worry about.
And if worse comes to worse and there is something wrong with your device, there is an extremely good chance that it can get fixed pretty easily.
Click to expand...
Click to collapse
OK, well now I feel even more n00b-ish. Since you said it was a log, I touched the icon again and it went back to TWRP main screen.
Sheesh.... all those years in IT at the university taught me SQUAT... hehehe.
When the Fire boots up now I see Kindle Fire with the word "Fire" in blue. It says at the bottom to press the power button for boot menu. If I touch nothing it changes so the word "Fire" is yellow (or yellow-orange-ish) and it boots normally.
So I've obviously installed TWRP. How do I know if I installed FFF?
Finally, and I swear I've looked for this, is there a post that has step-by-step how to flash a new ROM? Like once you have TWRP installed and you aren't having connection/driver issues, here's what you do. There's a lot of information on this, but some is old and it gets tough to see what's the most current. It *LOOKS* (to this n00b) like I put a ROM.zip into the /sdcard directory, boot to TWRP and Install it from there. Then I see various mentions of "you should wipe first". Ok, wipe what? There are lots of choices what to wipe when I look in TWRP.
I am assuming (and I hate doing that) that I can get back to where I am now by restoring the backup I made yesterday.
And when I boot to Windows 7 (I normally use linux) to run KFU< WHEN I plug in the Kindle using the USB, the Kindle tells me I can transfer files. I haven't really looked again, but can I just copy a whatever-ROM.zip over to the /sdcard right from the windows file manager?
Apologies for all the questions, and I have read the suggested n00b stuff, and I really do kinda understand what's going on, but I think I hae analysis paralysis
cjparker said:
How do I know if I installed FFF?
Click to expand...
Click to collapse
The blue (and white) Kindle Fire logo is FFF.
And when installing a new ROM, wipe System and Factory Reset. Everything else, you seem to have under control.
soupmagnet said:
The blue (and white) Kindle Fire logo is FFF.
And when installing a new ROM, wipe System and Factory Reset. Everything else, you seem to have under control.
Click to expand...
Click to collapse
See what happens when you get old? You get CRS.... Can't Remember S.......stuff .....
Ok. Gonna see if I can find a ROM that sounds interesting and reliable and see if I can do this without brickin' it. At least once.
Thanks!
cjparker said:
See what happens when you get old? You get CRS.... Can't Remember S.......stuff .....
Ok. Gonna see if I can find a ROM that sounds interesting and reliable and see if I can do this without brickin' it. At least once.
Thanks!
Click to expand...
Click to collapse
Nice. I have a new ROM (CM10+3.x Kernel)
It wiped my Draw Something games with my wife. We were up yo over 150 drawings. Can't seem to find the login I used. Maybe I shouldn't have flashed the gapps.zip onto it.
Oh well. Live and learn. Seems to run nice.
Thanks again. At this point it loks like I can actually flash a new ROM without ever having to reconect to my PC. I just download it to the Fire, move it to /sdcard, reboot to TWRP and away we go.
Thanks again!
Yep.
You made a backup of your last ROM, correct? Restore it and install Titanium Backup. Use it to back up all of your apps and app data onto the sdcard so you can install it your new ROM.
soupmagnet said:
Yep.
You made a backup of your last ROM, correct? Restore it and install Titanium Backup. Use it to back up all of your apps and app data onto the sdcard so you can install it your new ROM.
Click to expand...
Click to collapse
Okay. Makes sense.
I knew there had to be an easier way to keep the apps and settings or folks wouldn't be so quick to try new ROMs.
Thanks AGAIN, soupmagnet.
And yepper on the backup. I've restored it twice just trying new stuff.
Time to restore it again and install Titanium Backup... hehehe
:good:
Related
I'm pretty new to this rooting for Android, I recently got my Incredible.. I used unrevoked to root my incredible. I did it normally like USB debugging and all that. Soon as it started to root it, the phone rebooted itself like it was supposed too, got to the HTC Incredible screen (the first screen on the boot up) and black screen and white bars on the sides. Now I got this phone like November 27th.. and I'm pretty postive my screen is an SLCD? And that seems to be what the problem is with the black screen white bars.. Thing is, of course the black screen white bars stayed there, so I pulled the battery out and put it pack in. It loaded up normally and it seemed to be rooted fine. It had the Superuser (ninja). And everything was normal. I downloaded ROM Manager and then downloaded the Flash ClockWorkMod Recovery, and then I clicked on Cynagen Mod and went down to Google apps. Downloaded it, installed it, then it asked to reboot. ALL OF WHAT I JUST DID, (followed from The Start to Finish Guide to Rooting Your Android Phone, I con't post links yet) .. So as it rebooted it got the HTC Incredible screen (the first screen on the boot up) and it did the black screen white bars. I removed the battery either twice or three times.. And still nothing, I THEN FOLLWED THIS Incredibleforum dot com (I rooted and now I only see a black screen with white bars in recovery.) and went to the Hboot menu and went down to recovery and selected it. It rebooted and still black screen white bars at the HTC Incredible screen. I then tried his other method and went to download that file and went to unrevoked and did the custom recovery and put recovery in the file and plugged my phone in. ( He actually said to like check USB debugging, which I couldnt actually do because I couldnt get to my menu..) So then after plugging it in and showing the orange light for charging. It did nothing other then charge. I turned it on ( I'm pretty sure, it might have turned on by itself) and it worked. It got the menu screen. And everything was the same. ROM Manager was still there, same with superuser. And the 3 game apps that I downloaded before I rebooted for Google Apps. I haven't found Google Apps, I'm not really sure where Google Apps would be anyways.. But what I'm getting at here is, What actually happened????? Why those white bars?? And will this happen everytime I have to reboot? If someone could just give me their best answer or an explanation It would really help. I'm new to this stuff.. But I'm getting nervous with this black screen thing white bars.. and I'm debating wether to just unroot..(how easy is unrooting?).. But my phone is fine now, I haven't tried like downloading anything but everything seems to be working fine.. Where could I find Google Apps? And which ROM? Cynagen Mod Or Bugless Beast.. Please Help
You have an slcd screen. Your recovery is for smiled. Use unrevocks recovery for slcd screens. As I have read you need that one for recovery to work properly. I don't have an slcd so I don't know to much about that end
Just cruise the forums there is tons of info out there.
Sent from CM Nightly 11-20 using Tapatalk.
I had similar issues, and poster above is correct... I was able to flash a modified clockwork recovery to get it working with slcd...but I'm halfway afraid to try any ROM Manager abilities due to the different recovery :>
Just flash the modified Clockwork- very simple and works perfectly. I have the zip if you want it.
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
mcolib8 said:
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
Click to expand...
Click to collapse
http://www.megaupload.com/?d=7O9ZPP2T
You don't need to uninstall anything from your phone obviously, but I'd uninstall any unrEVOKed stuff from your computer before you do the new version. Recovery is basically the tool that lets you modify the phone. You go there to do nandroid backups and restores, and to flash zips. Let me know if you need instructions on how to apply the fix.
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
mcolib8 said:
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
Click to expand...
Click to collapse
1. Mount your phone as disk drive (I'm assuming you know how to do that, if not, lemme know)
2. Move the file to the root of your sd card (not in any folders) and make sure you don't re-name it at all.
3. Disconnect your phone, wait for the card to format, and then yank your battery.
4. Put the battery back in, hold Volume Down+Power.
5. You'll see your bootloader and it will find the file automatically, let it install it.
6. Once it's done, yank your battery again and repeat Step 4.
7. This time, choose not to install it, and instead choose Recovery- should load up Clockwork just fine. Easiest way to access Clockwork in the future is thru ROM Manager- there's an option to boot into recovery.
PS. might wanna check your clockwork version first thru ROM Manager- my version is 2.5.0.5 and I'm not sure if Koush has included the SLCD fix in any of the newer versions, so I'd make sure you have that version before doing this.
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Edit... responded too late. Thanks for the advice!
Sent from my ADR6300 using XDA App
ithuwakaga said:
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm guessing you didn't read to the end of the thread before you posted
iBowToAndroid said:
I'm guessing you didn't read to the end of the thread before you posted
Click to expand...
Click to collapse
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
ithuwakaga said:
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
iBowToAndroid said:
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
Click to expand...
Click to collapse
Thank you!
Sent from my ADR6300 using XDA App
Back in January I got my Kindle and rooted it and took it to a CM build. Since then i've basically seen that it's useless to me so i've passed it on to my mom.
She doesn't understand android and finds it complicated so i decided to go back to the stock rom that I had made a recovery of on the initial update.
I opened my recovery (Team Win Recovery Project v2.0.0) I wiped Dalvik, Cache, and Factory Reset.
I went into Restore and restored my old backup.
Now when i start up the Kindle it just goes back into TWRP, no effort to go into any sort of rom.
Anybody care to help me out here? I'm always messing with my Inspire and consider myself pretty knowledgeable but am at a standstill here and only have 80% battery remaining so i'm not wanting to waste it.
Thanks for reading, Kudos if helping
Sounds like you are stuck in recovery... you have 2 options in your case for going back to stock.. #1 you can change the bootmode back to normal with kfu.. or #2 you can download stock software from amazon.com and flash from TWRP or in other words that will get rid of everything..(TWRP root and such.)
The back to stock thing sounds like the best choice since she's kinda dumb about Android. Care to share more details on how that works and where I would go to download?
I can always reroot and rerecover it later.
I found this page: http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6_updates?nodeId=200790620 but it sounds like you just run the update from inside Android which isn't possible for me.
boazjuggalo said:
The back to stock thing sounds like the best choice since she's kinda dumb about Android. Care to share more details on how that works and where I would go to download?
I can always reroot and rerecover it later.
I found this page: http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6_updates?nodeId=200790620 but it sounds like you just run the update from inside Android which isn't possible for me.
Click to expand...
Click to collapse
If you have TWRP and you can use adb, you can do it this way...
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Thank you very much. Starting the process now. Will post results.
I followed the guide step by step, did everything exactly as it says.
When the Kindle rebooted I no longer have TWRP but I got stuck with a boot loop for about 5 rounds and now I'm just on kindle fire logo that is not repeating... just sitting here. Been about 10 min..... nm, it's fixed hahaha. Thank you very much.
One more quick question. Lets say I want to free some memory. What is safe to delete? Which folders do i not want to touch? Is there a list somewhere of the "do not touch me" files on the kindle? I know alot of this stuff is garbage (like data files for old games and apps i had installed) but other stuff i'm unsure of. I know the backup i had made with TWRP is probably fairly large (100ish mb?) but have no clue where it's at.
PS: Strangly all my apps are here that I downloaded back when I still used it. Shouldn't this be a clean install?
I have a Kindle Fire that I have already rooted and was running Reloaded, and decided to make a switch to something that was still supported / developed.
Originally, I had CWM and all was well, I installed a ROM without giving it too much thought, and it didn't work - further investigation revealed that I would need to utilize TWRP in order to get the thing back up and running.
"OK", I says to myself, "TWRP it is then."
But... After installing TWRP and reinstalling FireFireFire (it disappeared somewhere along the way, don't ask - I haven't a clue) I am unable to install any ROM's on the device.
Basically, it boots to TWRP, I wipe everything, cache, dalvik and system, then choose the zip I want to install.
So far, so good...
But only, it's not good. Not good at 'tall - It starts to install, then just stops and three buttons pop up on the bottom (Wipe Dalvik; Home; Reboot System).
Now, just for the record - I'm no Android genius, but I think I know enough to get around pretty well; so I start doing some research, poking about in the forums here and elsewhere looking for a little bit of enlightenment, you know - that one little nugget of info that sets off the "AHA!" in the back of your head and you just know that everything is gonna be just hunky dory.
Long story short - I've yet to experience the AHA! moment, nothing is hunky dory and my sleep pattern is in danger of being seriously disrupted...
Any little flash of insight that anyone here can provide would be appreciated...
P.S. Oh, and yeah - in my smug, over-confident first attempt, I neglected to make a backup, so I can't even roll back to the previous image. I propose that you add a smiley guy with a dunce hat for the gallery, just for asshats like me.
Nevermind.
My AHA moment came about a minute after typing the question - I changed the permissions on the system folder to 755, wiped everything again and started over.
Joy.
My sleep pattern will not be disrupted.
To be honest, I would never have thought of that xD
Please Explain
mdwbeex said:
My AHA moment came about a minute after typing the question - I changed the permissions on the system folder to 755, wiped everything again and started over.
Joy.
My sleep pattern will not be disrupted.
Click to expand...
Click to collapse
I'm having the exact same issue as you. Please elaborate on how you fixed it by changing the permissions? I've tried the other fixes found in the forums (like downgrading my TWRP version) but nothing is working. Thanks for the help.
After over a month of running jandycane perfectly my wife felt chrome was slow and decided to reboot. On reboot it stuck on black screen for a long time till I came home and tried hard reset. I reflashed rom several times. first with only dalvik wipe and cache wipe. Then more agressive full wipe. And even a re root. What happens is after flashing rom from twrp I reboot and it hangs on the rotating diamonds. I've left it sit for hours on that plugged in and come back to them still there. If I reboot it somtimes goes back to those and sometimes peoceeds to install rom. when I installs rom its very sluggish and unresponsive to touches. only things i havent wiped are the sd partition and the emmc.If anyone thinks those could be the issue i'll wipe one or both if nessicary.
Try using Hellfire Cleaner or Nullifier before flashing the ROM and see if that helps.
soupmagnet said:
Try using Hellfire Cleaner or Nullifier before flashing the ROM and see if that helps.
Click to expand...
Click to collapse
trying but twrp refuses to mount so i can transfer nullifier suggestions?
Have you tried "adb push file.zip /sdcard"?
I'll do that next device is at home now so I'll reply later with results.
ok i got the hellfire nullifier to work and tried reinstalling jandycane noticed in the install process it says unable to mount '/data' and '/cache' same when i install gapps. i cant find any option in mount to format those so im lost suggestions? I did reboot and it crapped out in boootloader. before getting nullifier to work i did manage to get in and it ran fine for a while then chrome crashed and it died again...?
jefem24 said:
ok i got the hellfire nullifier to work and tried reinstalling jandycane noticed in the install process it says unable to mount '/data' and '/cache' same when i install gapps. i cant find any option in mount to format those so im lost suggestions? I did reboot and it crapped out in boootloader. before getting nullifier to work i did manage to get in and it ran fine for a while then chrome crashed and it died again...?
Click to expand...
Click to collapse
select mount make sure there are no checks in the boxes of sytem and data if so untick them and try again
i did wipes and it took care of it im re nullifying adn ill flash in am thanks
jefem24 said:
i did wipes and it took care of it im re nullifying adn ill flash in am thanks
Click to expand...
Click to collapse
Be sure not to overuse Nullifier. It is a once in a while "spring cleaning" type of utility. Read the Nullifier thread for info on why it's a bad idea.
ok so still having boot issues i've tried re-root re-install fire fire fire pretty much everything in the first kfu menu. on reboot it shows white and blue kindle fire then just sits at the black screen forever or until i give up and try something else (over 10-15min.). So im thinking maybe fast boot is messed up? it's version 1.4a is there another version out? Suggestions?
forced fastboot and it installed rom seems good for now but been here before and it craps out. it always seems to be an issue with chrome? it will fc and then it all goes crazy....? should i just use a different rom? this worked fine for a month or so but went crazy.
ran for a bit and slwed right down taking about 10 seconds to respond to touches then rebooted itself?
goo.im has google update package i think i tried last time and failed download of apps do i need the updated apps from there or ignore them and pray it stays running :|
jefem24 said:
ok so still having boot issues i've tried re-root re-install fire fire fire pretty much everything in the first kfu menu. on reboot it shows white and blue kindle fire then just sits at the black screen forever or until i give up and try something else (over 10-15min.). So im thinking maybe fast boot is messed up? it's version 1.4a is there another version out? Suggestions?
Click to expand...
Click to collapse
FFF is not the problem. The ROM itself is corrupted, so it hangs at or before the boot animation.
jefem24 said:
forced fastboot and it installed rom
Click to expand...
Click to collapse
What?
jefem24 said:
seems good for now but been here before and it craps out. it always seems to be an issue with chrome? it will fc and then it all goes crazy....? should i just use a different rom? this worked fine for a month or so but went crazy.
Click to expand...
Click to collapse
Some ROMs have a lot of trouble with Chrome and you'll have to check their respective threads to find out which ones.
jefem24 said:
ran for a bit and slwed right down taking about 10 seconds to respond to touches then rebooted itself?
Click to expand...
Click to collapse
You're going all over the place, so I have no way of telling what is causing that. What happened with Nullifier? Are you able to install a ROM normally?
jefem24 said:
goo.im has google update package i think i tried last time and failed download of apps do i need the updated apps from there or ignore them and pray it stays running :|
Click to expand...
Click to collapse
I'd say sort (identify) out your current problem now before you potentially add more problems to the mix.
I think the battery is getting flakey....she had just brought it down from the charger and it shut off with low battery tonight after less than an hour. rebooted fine on chargerr i'll let it charge overnight and see what happens. Yes the rom finally did install but it was sticking just after the blue/white kindle fire untill i ran KFU and out it into fastboot. after that it installed rom and installed and other than shutting off for battery it seem ok. Im wondering if she ran it out last time and didn't notice. It was charged when I got home so im still kinda lost as to why it messed up to begin with. Thanks for your help. I HOPE not to have to update thread anymore lol
Hi, guys. I've tried searching around, but everything I found didn't quite sound the same or else the instructions were far, far out of my league of knowledge (throw tech speak at me, and my brain melts, basically). So I was hoping someone could help me out, here.
My KFHD 8.9" was rooted on... I think it was 8.4.3, the first or second version of the Kindle OS which had the battery percent on the status bar and needed the wallpaper fix. It's been nice and rooted for a good, long while. Long enough I don't remember what I'm doing and am worried about screwing things up even just trying to touch KFFA (which is the rooting method I used).
Recently, the darn thing started behaving buggy, dropping massive battery percentage, etc. I spent a good half hour one day trying to just get it to stop lagging and draining battery. Skip forward a week, and I started having more troubles. To test my theory on battery drain being from the lock screen ads, I got Titanium Backup and used it to freeze the Special Offers app. I also used it to clean up the dalvik cache, which I googled and seemed to be safe enough. That seemed to fix everything, until today. I woke my tablet up, and every app which requires internet access force closed at the same time. I tried to turn my wifi off and back on, but when I pressed the on button, it refused to work. Airplane mode didn't initiate either, though the on button would light up (no airplane would appear).
I tried several reboots, which didn't work. I tried uninstalling Titanium Backup, but upon reboot it was back. I finally got the wifi to return, and unfroze the Special Offers app, then revoked root access to Titanium Backup and uninstalled it. Another reboot, and all seemed well. I started deleting unwanted apps and preparing to back stuff up to my dropbox when I noticed a toast notification. I couldnt' read it. Then the wifi broke again, and I checked my SuperSu permissions, to find that DroidWall had requested access at the same time. DroidWall claimed there was no root; Rootchecker claimed there was. I tried to disable DroidWall; it wouldn't let me, due to insufficient permissions, and so I tried to reboot again.
And now I'm in the boot loop where I have a dead android saying I should reboot (doesn't work) or restore.
My questions are: Does anyone have any idea what could have caused this weird behaviour and degradation? Is there any way at all to save the photos, personal documents, etc. on the device that exist only there and nowhere else? And, of course, how can I get this bleeding thing where it'll boot again?
I should add that I can get my kindle into fastboot, using KFFA (it's the same program I used to root; I have a full backup from KFFA saved). But I have no clue where to go from there or if I can recover anything.
You should just restore to stock, it may wipe the data off the device but it should fix the os so it will boot up at least. I hope the internal WiFi card isn't dying. They have died on kindles here and there.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You should just restore to stock, it may wipe the data off the device but it should fix the os so it will boot up at least. I hope the internal WiFi card isn't dying. They have died on kindles here and there.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
By restore to stock, do you mean choosing the factory reset option on the screen, or something involving KFFA? (Sorry, I'm really clueless and don't want to mess things up further by misunderstanding anything.) Also, would I need to do that then re-root it before restoring my backup through KFFA?
I sure hope it's not the WiFi going bad, too! Though from the symptoms presented (at one point, the status bar and such were flashing as it did when I first rooted it, before the process finished; before it finally went down, droidwall wasn't registering the permissions supersu allowed it) I almost think that maybe an app had a virus in it or something got corrupted. It was on a steady decline for the past month, really; I'm a doofus for not taking the many opportunities I had to back up my data beforehand.
In kffa there's a restore option, I didn't mean the one that does it from your own backup, its just a stock rooted restore. I don't use kffa so Idk the exact name or number. I do this kinda stuff manually.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
In kffa there's a restore option, I didn't mean the one that does it from your own backup, its just a stock rooted restore. I don't use kffa so Idk the exact name or number. I do this kinda stuff manually.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Oooh, gotcha. Thanks. I'll give it a shot, if I can find the setting in KFFA.
sonicanomaly said:
Oooh, gotcha. Thanks. I'll give it a shot, if I can find the setting in KFFA.
Click to expand...
Click to collapse
You can try this to factory restore too http://forum.xda-developers.com/showthread.php?t=2011126
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
You can try this to factory restore too http://forum.xda-developers.com/showthread.php?t=2011126
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
Success! The poor thing is sluggish as can be, but I can't decide if that's because Amazon's possibly attempting an ota update in the background or what. I have really low bandwidth (hence it took hours to download the recovery image there), so I guess it's possible that's the case. It's been so long since I dealt with ota updates that I can't remember if my kindle got sluggish around those times or not. The wifi seems to be working now, though!
Probably going to manually update it so I can re-root and be on a version with the battery percentage in the status bar, and I have to rebuild from scratch (and track down older versions of the apps I can't stand the current versions of and was intentionally not updating), but... I'm glad I don't just have an expensive paperweight anymore! Thanks for the help, and here's hoping the rest goes smoothly. :good: