I am in a bootloop that takes me to the "choose language" over and over. I have adb access but am having trouble figuring out which file to download and the commands to get a good file on my HDX 8.9.
I've done a bunch of searching but nothing seems to match what I need. Any help or links would be greatly appreciated!
Thanks
This is an easy one, but don't feel bad. It vexed me too. It is because it wants a to connect to the server and verify your account and device (in doing so, it will also try to push an update).
The solution is to click the orange "complete registration later" (or something like that) text which shows up centered on the bottom.
I'm rooted and connected to wifi already..I'm downloading update kindle 14.5.2 but I'm guessing that I'll lose root.Tthe screen blinks on the desktop of the kindle then goes back to the language...like it doesnt know what to do next.
I also see an update file thats rooted but it doesn't appear to be the right one for me...
So many instructions and downloads that it gets confusing.
Also, thanks leko for the great help with adb!!!
Oh_wow said:
I'm rooted and connected to wifi already..I'm downloading update kindle 14.5.2 but I'm guessing that I'll lose root.Tthe screen blinks on the desktop of the kindle then goes back to the language...like it doesnt know what to do next.
I also see an update file thats rooted but it doesn't appear to be the right one for me...
So many instructions and downloads that it gets confusing.
Also, thanks leko for the great help with adb!!!
Click to expand...
Click to collapse
You can root 4.5.2. If the update fixes the issue then just root and you'll be good. Once your rooted, find instructions to disable OTA here so you don't automatically update to 4.5.4, like what happened to me.
-Zman8881
Is there a rooted download I should use instead? I'm still not positive that I'm doing the right thing which is why I asked for help. And I'll definitely block those ota's..thanks for that tip
Oh_wow said:
Is there a rooted download I should use instead? I'm still not positive that I'm doing the right thing which is why I asked for help. And I'll definitely block those ota's..thanks for that tip
Click to expand...
Click to collapse
There is no pre-rooted 4.5.2; you have to root if needed. Whether you retain root from an earlier install depends on where you came from and the method used to upgrade.
The looping problem you describe has happened to others. You'll need to poke around to find the solution. Hopefully someone will pop in with a direct link or more specific instructions. Point is it's solvable. Don't do anything radical while searching/waiting for resolution.
Sent from my Kindle Fire HDX 7 using XDA Forums Pro.
I've already learned the hard way that jumping in without knowledge is painful (R.I.P my 1st kindle). This device is twitchy but the searching I've done so far has be a great learning experience! And that's the thing, I really want to learn how to do this stuff...unfortunately I may not explain the problem correctly and am terrified of getting shot down by more knowledgeable folks. I've survived modifying the Droid x, note 2 and note 3 so I know I can do this...eventually☺
Oh_wow said:
I've already learned the hard way that jumping in without knowledge is painful (R.I.P my 1st kindle). This device is twitchy but the searching I've done so far has be a great learning experience! And that's the thing, I really want to learn how to do this stuff...unfortunately I may not explain the problem correctly and am terrified of getting shot down by more knowledgeable folks. I've survived modifying the Droid x, note 2 and note 3 so I know I can do this...eventually☺
Click to expand...
Click to collapse
The only time you'll get shot down around here is if you do bad stuff (eg: flash incompatible components) that have been well covered in the forums. People are willing to help if you ask questions before getting into trouble. Kindles (at least HDX models) are tough to tame and easy to ruin.
Are you having difficulties now? You reported a soft bootloop (stuck on language screen) in a earlier post. Has that been resolved?
Davey126 said:
The only time you'll get shot down around here is if you do bad stuff (eg: flash incompatible components) that have been well covered in the forums. People are willing to help if you ask questions before getting into trouble. Kindles (at least HDX models) are tough to tame and easy to ruin.
Are you having difficulties now? You reported a soft bootloop (stuck on language screen) in a earlier post. Has that been resolved?
Click to expand...
Click to collapse
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (if I'm quick, I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Oh_wow said:
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (f I'm quick it there that I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Click to expand...
Click to collapse
This is a really random thought and I'm not sure if it will work, but when you get into the desktop try to power off and power back on. You need to be quick, but it might work.
Random is good...but it didn't work in this case.
Thanks
Oh_wow said:
No, its still in the bootloop---or maybe that's the wrong word. It boots thru grey and then orange screens and lands on the language screen. When I choose english, it continues to the desktop where it stays for maybe 2 seconds (if I'm quick, I can enter settings to ensure unknown sources is checked). That's when it goes back to the language screen. The PC (w7) sees the HDX (8.9, 3rd) in ADB just fine. (A million thanks to lekofraggle)
Root checker says its rooted and I had previously blocked OTA's by changing the apk name to .old.
It is at this point that I don't know what to do...Any help would be greatly appreciated.
And a big thanks to YOU Mr. Davey--with the hours I've spent reading posts throughout this forum, you have consistently been there to help anyone in trouble!! Thank you!
Click to expand...
Click to collapse
Sorry for the delay in responding; was out with family.
Like many others I am the beneficiary of the experiences, suggestions and knowledge generously shared by others. It's the collective community you need to thank
Have you looked at this thread? Post #2 seems to offer a solution. Others noted the need to disable (or more correctly not enable) wifi during initial setup which suggest a factory reset may be part of the solution. Another thread indicated the 'language looping' problem was related to corruption in the default launcher. Installing another (eg: Nova) via ADB restored some control and ability to further diagnose from within FireOS. However, this was for the prior version of FireOS (3.x "Otter") and may not be applicable to Fire OS 4 ("Sangria").
Davey126 said:
Sorry for the delay in responding; was out with family.
Like many others I am the beneficiary of the experiences, suggestions and knowledge generously shared by others. It's the collective community you need to thank
Have you looked at this thread? Post #2 seems to offer a solution. Others noted the need to disable (or more correctly not enable) wifi during initial setup which suggest a factory reset may be part of the solution. Another thread indicated the 'language looping' problem was related to corruption in the default launcher. Installing another (eg: Nova) via ADB restored some control and ability to further diagnose from within FireOS. However, this was for the prior version of FireOS (3.x "Otter") and may not be applicable to Fire OS 4 ("Sangria").
Click to expand...
Click to collapse
There's a chance it's me being stupid, but don't you need root access to do that solution? If not, do you think this kind of idea could work to get around the earlier version error or even disabling OTA without root access?
Zman8881 said:
There's a chance it's me being stupid, but don't you need root access to do that solution? If not, do you think this kind of idea could work to get around the earlier version error or even disabling OTA without root access?
Click to expand...
Click to collapse
@Oh_wow indicated in a earlier post that his device remains rooted. Otherwise most of the recovery techniques discussed in the links would not work. Sorry to dampen your hopes ...
You could try installing an alternate launcher. That should work. However making it default is annoying. If the install works and helps with the screen, I can help with setting it as default.
Download the launcher (I like Nova)on your computer. You can probably find it on apkmirror. Then, run this command.
Adb install and drag the file.
A little note. The and install command is potentially dangerous, but for some apps it is safe, and I am mostly certain a launcher counts.
Also, have you tried clicking the register later button?
lekofraggle said:
You could try installing an alternate launcher. That should work. However making it default is annoying. If the install works and helps with the screen, I can help with setting it as default.
Download the launcher (I like Nova)on your computer. You can probably find it on apkmirror. Then, run this command.
Adb install and drag the file.
A little note. The and install command is potentially dangerous, but for some apps it is safe, and I am mostly certain a launcher counts.
Also, have you tried clicking the register later button?
Click to expand...
Click to collapse
Bonanza! That solved the language question but it is annoying that Nova won't stick as default. I'd love to know how to set it! Thanks!
Now what? Gapps? Wait, safestrap or TWRP?
Nevermind---I lost root and the toolkit isn't working,,,good grief
Oh_wow said:
Bonanza! That solved the language question but it is annoying that Nova won't stick as default. I'd love to know how to set it! Thanks!
Now what? Gapps? Wait, safestrap or TWRP?
Click to expand...
Click to collapse
Getting 3rd party launchers to 'stick' has been a issue on newer releases of FireOS. However, regaining some control over your device does offer the opportunity to fix the problem with Amazon's launcher if it can be identified (eg: missing/renamed file) or rolling back to 3.2.8 and followed by an upgrade to 4.5.2 (there is risk in doing this; make sure you understand the procedure before diving in).
Native TWRP is not an option on 4.5.2. Nor would it help.
You could install Safestrap v4 followed by a patched version of 4.5.2 which should fix the launcher problem. You could continue running FireOS under Safestrap or remove it; the version installed under Safestrap would remain as the default OS. If you keep Safestrap you also have the option of running Nexus v4 or CM11 which offer a more native Android experience and full access to the Google Play store, services and apps.
You should still have nova though. So, you can download cve
Here
, and then have unfettered (well mostly) access.
As far as your other question.
You can run these commands from adb or the app command runner (if you can find it, they took it out of the play store).
There are two ways...
#1 If you do not want to use the stock launcher at all, run this command...
Code:
pm block com.amazon.kindle.otter
To undo, run
Code:
pm unblock com.amazon.kindle.otter
To just make it so the launcher does not work, but the other kindle pieces do (like your library), use this command.
Code:
pm disable com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher
To reverse this, run...
Code:
pm enable com.amazon.kindle.otter/com.amazon.kindle.otter.Launcher
I do not think you even need root for these commands if you run them from adb, but I could be wrong.
Some words of caution. If your device upgrades through ota while otter is blocked (or probably disabled), you will brick your device (unless you have a working recovery/unlocked boot loader and know how to use them to completely restore your system.
If you block otter without a working alternate launcher, you may brick your device, but and could save you by reversing the command.
Good luck.
~Leko
Thank you for all those instructions!
I'll report back how it works for me...
Oh_wow said:
I am in a bootloop that takes me to the "choose language" over and over. I have adb access but am having trouble figuring out which file to download and the commands to get a good file on my HDX 8.9.
I've done a bunch of searching but nothing seems to match what I need. Any help or links would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
Did you install gapps an got
stock on setup
Related
I am sure by now you have caught some of my posts floating around the forum in a near panic with confusion. Here are the steps I have taken followed by the issue I am dealing with. I understand I may have taken these steps out of order and am very interested in getting some detailed help on how to fix the issue I am in.
Starting with a fresh stock Atrix I..
Step 1 - Ran Adeo for version 0.1 I downloaded all of the drivers correctly from the MobileTech video website however I honestly don't know what this even means.
Step 2 - Rooted using Super Once click.
Step 3 - I tried to install the Gingerbread theme but after much frustration and many failed attempts I found out I suffer from the missing ADBD file.. I read the thread and it said to download the file unzip it and add it to SBIN.. I have done this countless times and my phone is still unreadable but AROOT, Super once click and Adeo installer..
Rebooting removes the file as mentioned in that thread but I can never actually get anything to recognize my device while the file is in there.
I am set to USB connection NONE and using the Debugging setting in the ON position.
At this point I want to start all over.. Completely go back to stock and then try again, maybe not even that.. I am very turned off of this experience and am starting to get worried considering the investment in this phone I have. (Full Retail)
I understand many people on this forum are not only busy but do no suffer from this problem but I have also seen some incredible help given so as always anyone who is willing to help me just know it will be very appreciated. Thanks!
JoshRH said:
I am sure by now you have caught some of my posts floating around the forum in a near panic with confusion. Here are the steps I have taken followed by the issue I am dealing with. I understand I may have taken these steps out of order and am very interested in getting some detailed help on how to fix the issue I am in.
Starting with a fresh stock Atrix I..
Step 1 - Ran Adeo for version 0.1 I downloaded all of the drivers correctly from the MobileTech video website however I honestly don't know what this even means.
Step 2 - Rooted using Super Once click.
Step 3 - I tried to install the Gingerbread theme but after much frustration and many failed attempts I found out I suffer from the missing ADBD file.. I read the thread and it said to download the file unzip it and add it to SBIN.. I have done this countless times and my phone is still unreadable but AROOT, Super once click and Adeo installer..
Rebooting removes the file as mentioned in that thread but I can never actually get anything to recognize my device while the file is in there.
I am set to USB connection NONE and using the Debugging setting in the ON position.
At this point I want to start all over.. Completely go back to stock and then try again, maybe not even that.. I am very turned off of this experience and am starting to get worried considering the investment in this phone I have. (Full Retail)
I understand many people on this forum are not only busy but do no suffer from this problem but I have also seen some incredible help given so as always anyone who is willing to help me just know it will be very appreciated. Thanks!
Click to expand...
Click to collapse
At a glance I would try looking into the adb offline issue [fixed] thread in this section. though thats from the glance over what you seem to behaving and use aroot, superoneclick is sai by some devs to make a mess of things.
Sadly this is my actual problem. I do suffer from the missing ADBD file however unlike others in that thread I am unable to get anything to work after adding the file back in.
Someone has to have a solution to this. I know my OP is long but I'm at a loss here.
Sent from my MB860 using XDA App
At this point I would be willing to make a hefty donation to a devs paypal to help solve my issue.
Would anyone at least be able to offer advice on what to do from this point forward? Thanks
JoshRH said:
Would anyone at least be able to offer advice on what to do from this point forward? Thanks
Click to expand...
Click to collapse
Warning this will restore your phone to a "updated" stock build and will wipe all your data
1) Download this http://bandbinnovations.com/OLYFR_U4_1.5.2_SIGNED.rar
2) Change the .rar to .gz then extract with .7zip or Winrar
4) Install if not already the 32 bit http://www.multiupload.com/QNFILE4F07 and/or 64 bit http://www.multiupload.com/FIN3KYUD7S
5) Install RSD Lite 5.0 (from here http://www.mirrorcreator.com/files/1TFKDEHB/rsdlite_5.0.msi_links )
6) Turn off the phone
7) Turn on the phone while holding the volume button top
8) Once again, press the volume key up
9) click the ... icon in rsd lite select the firmware file and click start
10) grab a beer and wait until it says passed
EDIT: Well I managed to get clockworkmod installed and everything; still having some issues with aspects of it, but in general I'm good. I'll probably make a dedicated thread to the device; if anyone wants to suggest a proper forum section, be my guest.
Ok, so I need some assistance on installing CWM or another recovery mode on my YourPad P4. I've already rooted and installed ROM Manager, but it could not find a compatible CWM version.
Now, first off I have also been unable to get an exact or better identification of this tablet other than it being sold as a "YourPad P4" and that it's model is MID; so I might also need help getting more details to better assist the finding of a compatible or working recovery.
Here is some information about it...
* Site purchased from/detail page:
http://www.yourstoreonline.net/yourpad_p4_new_android_40/id2040716/product.html
Don't worry, I got it for ~$100 (with the 1GB RAM upgrade), not the displayed price on the site!
* About tablet page info:
Model number: MID
Android version: 4.0.3
Kernel version: 3.0.8
[email protected] #2
Build number: 20120807-A721
Also, before I start messing with it I was going to make a nandroid backup to share for others...does nandroid backup firmware as well? I've never needed to restore a backup so I have no idea what goes into it and can't find a quick answer. I'd like to make a backup of a clean as possible system to share for anyone wanting it. Although I'm surprised that its not been mentioned on xda, I'd expect this tablet to have at least been asked about once considering it was mentioned on woot.
Thanks to anyone for any help, and I apologize if this should be in a different section. If so, could a mod please move it before any fuss is made.
And now, I'm off to bed (so I won't be responding/checking this for a few hours).
Not to sure about the rules for thread bumping, but I just wanna make sure this gets seen soon (as I'll be very busy and it will be hard to work on it next week and the the days that follow).
Also I thought it was worth mentioning now that only really mentions of this tablet I can find are in posts by me, ahahahahaha
EDIT: Oh, and I havn't verified I even have a recovery partition yet as I can't cat /proc/mtd
it's been about a week now and no response; I even posted it over here http://www.androidtablets.net/forum...cs-need-help-recovery-install-yourpad-p4.html
so bumping, if anyone at the very least knows some mystical other worldly site that somehow manages the chance of providing me an answer over the ever amazing xda; please post
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
AJ88 said:
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
Thanks alot for this, I'll definitely read it over a few times before attempting. Hopefully this will work out. Thread is still open for any other input, so anyone else coming here that can provide any additional help go ahead and post.
Well I still have been unable to get a recovery option going. I tried the link mentioned by AJ88 and it didn't work for me. Essentially the link boiled down to 2 simple adb commands and a custom recovery.img. First step was to "adb push recovery.img /data/", but I ran into a permission denied issue and could not figure out a way around it (didn't want to mess with chmod, but I did run the "fix permissions" script in the clockworkmod rom manager. So instead I just pushed the recovery.img to my sdcard. Next step was "adb shell "cat /data/recovery.img > /dev/block/nandg; sync""; so instead I went "adb shell" then su to make sure I didn't get any more issues, then just "cat /sdcard/recovery.img > /dev/block/nandg; sync". Rebooted and tried all combinations of key pressings to access recovery with no luck (even tried via adb). So any ideas on my next course of action?
youtPad P4 issues
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Well I've been waiting for a reply to either of my threads with no luck, so today I figured I'd just try again the method of manually setting up a recovery, and this time I just decided to try and hold every button I could while powering and and BAM RECOVERY MODE *****ES!!!!!! So guess either I must've just screwed up last time or something. Anyways, I'll edit the OP to reflect all this later...maybe start a dedicated thread with any quirks I figure out down the line using this tablet; and of course post my nandroid backup. When I setup my 2nd YourPad, I'll make sure to make backups of any files I may have had to change (ie, nandg, etc). The question is, what section would such a thread belong?
5lita5 said:
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Click to expand...
Click to collapse
I don't feel any buyer's remorse...yet at least, haha. If I end up having the same issues as you, maybe I'll change my mind; but I really don't see much wrong yet with this tablet. I mean, obviously its cheap and all, but for the poor man its fantastic. But ya, I HATE the YourStore, they took FOREVER to ship out the tablets. Anyways, for people like you, it really makes me thing I should take point on this tablet and start a dedicated thread.
I apologize if this has been asked before, but I have been searching around through dozens of threads over days and don't see much about people in a bootloop without ADB access. Is this an unsolvable problem or is there some way to reconnect to ADB so I can run a fix?
Just for background, I had a fully functioning towel rooted kindle 8.9 HDX which had the Google marketplace, OTC disabled, APEX launcher running, ADB connectivity with all the SDK stuff installed and safestrap. I must have done something wrong with safestrap because my backup didn't take, and when I tried to hide the nav bar I got stuck in a bootloop. I see the grey logo then a lighted black screen, but the kindle no longer connects.
dburns865 said:
I apologize if this has been asked before, but I have been searching around through dozens of threads over days and don't see much about people in a bootloop without ADB access. Is this an unsolvable problem or is there some way to reconnect to ADB so I can run a fix?
Just for background, I had a fully functioning towel rooted kindle 8.9 HDX which had the Google marketplace, OTC disabled, APEX launcher running, ADB connectivity with all the SDK stuff installed and safestrap. I must have done something wrong with safestrap because my backup didn't take, and when I tried to hide the nav bar I got stuck in a bootloop. I see the grey logo then a lighted black screen, but the kindle no longer connects.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2588608 Look a whole thread devoted to your problem .. I would suggest reading the whole thread and understanding as much as possible before you start issuing commands . Good luck ,and by the way this would not have happened if you were using a slot on your safestrap. If you were in fact using a slot. Just hold the power down for over 25 seconds. Then safestrap should boot whatever you do do not do a factory reset in stock recovery
jimyv said:
http://forum.xda-developers.com/showthread.php?t=2588608 Look a whole thread devoted to your problem .. I would suggest reading the whole thread and understanding as much as possible before you start issuing commands . Good luck ,and by the way this would not have happened if you were using a slot on your safestrap. If you were in fact using a slot. Just hold the power down for over 25 seconds. Then safestrap should boot whatever you do do not do a factory reset in stock recovery
Click to expand...
Click to collapse
Maybe I am confused about something, I had already read through that thread a few times and it seems like that assumes you have ADB access or a way to gain it which I do not have. Issuing any of the commands listed in that guide just gets me the same response, Error: Device not found. I saw one guy asking my question and GSLEON said to download the update.bin, but I am not really sure what to do with it and they didn't elaborate. In addition, the advice he gives him about it says the computer should fail to recognize my device but still acknowledge something was plugged in but that doesn't happen with mine. He also suggested trying in linux so that is what I am working on doing now but I have never used Linux so I will see how that goes.
I may just not be understanding something, I'd be in your debt if you'd elaborate on something I am not understanding but in any case sorry if I asked a dumb question. I appreciate you responding, it's good to know what I need is in that thread, I guess I just wasn't able to figure it out yet. I will try harder
I picked up this device from walmart for $29.99 with the intentions of learning some new development stuff.I
thought for 30 bucks there's gonna be a lot of these little "duallies" running around why not a cheap candidate?
So far as i can tell there is little info found about this device so I'm looking to collect what little is known about
it in one place in hopes to get a jump on it. First things first, I am responsible for my own actions as you are yours.
If your not sure ask or simply dont do, some of this stuff can brick your device!
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
dont forget to install supersu
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
and busybox afterwards!
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
*RECOVERY*
Downloaded "TWRP Manager" from play store.
twrp settings, I enabled the sd card patch.
Install twrp\device name :l34c\version i instaled: openrecovery-twrp-2.8.4.0-l34c.img
click install... wait... things will pop up..... things will go away... wait some more...
finally a dialogue that states sucess.
***ISSUES HAVE BEEN REPORTED OF LOSING RECOVERY OR THE ABILITY TO ENTER IT AFTER
A WIPE AS WELL AS PROBLEMS BACKING UP AND OR RESTORING.
I have "injected" twrp manager into the system using titanium backup (link2sd will work also). This seems to
prevent any issues I have read about previously mentioned. Also I have successfully preformed backups as
well as restores, both before and after wiping. I have not figured out how to enter twrp recovery upon boot
yet, so be careful of what you do!
*SAFE TO REMOVE APPS*
yet to come
I use "titanium backup" from the play store, still trimming.I can get it down to about 230MB
available "free" ram at the moment but not consistently.
Ok had an issue with a task manager improperly reporting free available ram... true availability was
around 150mb free. There are apps that have to be replaced when removed, for example a launcher
for a launcher but some do not. Again I'm still trimming and experimenting, right now my system rom
around 244mb free. Most every thing I have done has been on the phone its self without the need of a P.C.
*STOCK BACK UP*
Yet to come
Any candidates for a true stock rom? Ive hacked the crap out of this one so far without the need of a back up... i know tisk tisk tisk!
I'm going for a debloated deodexed stock rom, hopefully!
*DRIVERS*
The only ones I could find that actually work. The Verizon drivers mentioned for the g2, not surprising since it runs on vz towers!
http://forum.xda-developers.com/showthread.php?t=2432476
*TETHERING*
using the android wifi tether 3.3beta2
https://code.google.com/p/android-wifi-tether/
all settings untouched except
device profile
lg optimus 3d
device access does work as well as encryption
*XPOSED*
Does work, im using 2.6.1.
*DPI*
The app I'm using for safe keeping to test dpi settings
https://play.google.com/store/apps/details?id=com.oumugai.densityadjuster
200 not working
170 works
160 native
150 works
140 works
130 works
120 works (looks good)
110 works
Temporarily went back to native dpi for debloating purposes. Will revisit later.
After messing with DPI settings I'm having a"contacts has stopped working " when tapping on the phone app.
DPI set to 120 when I noticed. All dpi switches affect lg home launcher
so you will need another launcher.
ok so far thats what i got. whats the nexts step to a stock AOSP rom?
questions and/or constructive comments wecome
reserved
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Any chance you know how to get it in diag mode? I need to connect it to DFS but can't without diag. Thanks for your help!
DrPhant0m said:
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Click to expand...
Click to collapse
My apologies for the delayed response. I have a lot going on in life.
As for recovering them, use the device you have closest to stock to make a backup. Do this before you attach your account or put any thing in to it after a "fresh wipe". To the best of my knowledge there isnt a tool like odin available, i could be wrong though. You can push a back up to the looping devices via adb. in order to do this you must have previously enabled usb debugging. The instructions are available on the web, i my self dont know how to do this. If you can establish an adb connection im sure you can command it to boot into twrp. For setup and testing use one of the devices that doesnt have a problem to establish adb. There is a little info on another thread i created about investigating the boot process the link is in my signature for the defy. Please be patient with me as i have two jobs and a single father, im not a hacker or developer. just a normal guy that is fascinated by my little robot willing to learn any thing. now that I know this thread is becoming active Ill monitor a little closer. Also if there is any thing i can help with ill be glad to do so. Im wanting to get a second fuel just for dev and learning purposes.
Recovery
Is there a way to access recovery on the lg fuel? I am stuck in a boot loop because I disabled the home screen service as well as other things that I did not pay attention to. I do not have a custom recovery installed.
I've never been able to boot to recovery by way of button press. Seems like there's a way to get into boot loader mode though. Just can't remember off the top of my head, I'm at work now and don't have the fuel with me. I'll see what I can figure out in a few hours when I get home. In the mean time you can try button combos upon boot to include the home button. If we can get ADB talking to it there's a chance I can send you copies of the files needed. Give me more details of what you have done just before the boot looping.
Sent from my ALCATEL A564C using XDA Free mobile app
I bought the optimus fuel a few months ago and i've been using it primarily for a music player/run keeping devices during my jogs. I turned off mobile data and i've noticed that i still see signal bars on the top notification area - does this mean that the radios are still on?
I was wondering if there was some way to completely disable the cellular radios so that i could conserve battery life inbetween days where I don't run?
Thanks!
This is a pretty cool app....
https://play.google.com/store/apps/details?id=com.latedroid.juicedefender
Airplane mode and then turn WiFi back on does the trick. "Radios off" = ton more juice
Has anyone found out anything else for this little phone? I have the LG Optimus Fuel. Had it for a few months now. I rooted it as soon as I got it and uninstalled a few system apps like the LG keyboard, the default SMS app and Chrome along with 2 or 3 other Google apps. It's still running fine.
I installed TWRP recovery and a custom boot image so I could boot into recovery by pressing the up volume button. Works great. I made a full system backup and saved it to my external SD card and saved it to my Debian laptop.
Right now I'm just looking for a custom ROM for this little phone but can't find one. I'd love to get Cyanogenmod on this phone but there are none. I'd port it myself but I'm not able to at the moment.
reemobeens19 said:
...
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
...
Click to expand...
Click to collapse
I'll expand on the above link because no one can view all of the info in that thread w/o registering for that site [PITA].
Load towelroot (www.towelroot.com). Upon running towelroot, press "welcome to towelroot v3" 3-times (quickly). Change 1337 0 1 0 4 0 to 1337 0 0 0 4 0 (change only the ONE to a ZERO), click "make it ra1n" and you're rooted. :good:
This was verified on an L34C running Android 4.4, Kernel 3.4.0+, build KRT16S.L34CV10c, Sw ver L34CV10c.
YMMV; IANAL
My apologies for the inconvenience, I was unaware for the need to register.
What I would like to do with the L34C is find a ROM with all the phone functionality removed, and few to no Google Apps (let me just add the ones I need). I am not planning on using it as a phone (I still have my old Casio flip-phone, need nothing else). My intention was to experiment with creating a PalmPDA "replacement", something small to carry around for addresses, notes/memos, calendar (you know, the stuff you used to do on PalmOS), and in addition figure out how to do record-level synchronization **locally** (as in I don't need to send my data to some dirt-floor shack in Bangalore just to have it sent back to a device 2 feet away from my computer). Additionally, would line to use it as a basic portable media player. Essentially, trying to re-create the Palm LifeDrive on Android.
To my knowledge there are no roms available for this device. Your best bet in my opinion is to remove apps 1 by 1 after rooting. Google each and find out what the risk and severity of removing them are. I have donated my device to a less fortunate fellow employee. So as of now I'm unable to help with testing. This method is what I do for all of my devices until I'm finally happy with its performance and functionality. Think of Android as the swiss army knife of the computer world, you can do just about any thing with it, you just gotta figure out what tools are useful to you and the ones you can do with out, then you gotta ask Google witch ones Android can function with out. I hope you find what your looking for in the little robot, its a really neat world inside there!
I hate to bump an old thread but, I also don't it necessary to start a new one, at least not yet anyway but, I too am looking for a way to flash stock ROM. I have LG34Cs to use as a reference..
Where is the link to exposed framework at for this phone?
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.
Here is working twrp 3.1.1 if anyone interested:
Code:
mega.nz/#!I0lhAYAY!fRbQtQjYFI2kiJOD0FSEBPnBJm0JZxpiBaw52kyOfQE
majexuj said:
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.]
Click to expand...
Click to collapse
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Mac23 said:
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Click to expand...
Click to collapse
Broken as in doesn't boot into recovery. The phone will still boot into android, assuming you have a working system, and within android with root you can flash a working recovery image over a broken flash with the dd command on the twrp device info page (twrp.me/lg/lgoptimusfuel.html). So no real risk of brick, just possible inconvenience that might require a battery pull.
I built twrp 3.2.1 with same sources but I have not tested it since my battery seems to have completely died and the phone won't boot with usb power alone.
Here is link anyway in case anyone is interested:
Code:
mega.nz/#!ssExSY7S!_B3FcAmclzRwCKTX461Tl_QhpdwwK0tmvhL-6zkKLRw
---
Hey guys I desperately need help here. I got this Kindle Fire 8.9" years ago, and got abandoned by my Dad because we live in SEA, can't do much with it, I cannot even get the free apps through Amazon Appstore. I can use fake US CC in this matter to get the free apps but Is that even legit? I have real CC and a legit Amazon account I bought real stuffs from Amazon too back then (books, some shirts and some gadgets) but that doesn't seem to help much.
Anyway sideloading apps from Google Play don't help much since the compatibility are horrible, and sideloading the Google Playstore itself just don't work. I've attempted to install all the Playstore requirements, some installed and some spit out "Parse error - There was a problem parsing the package".
I figure I needed to convert it to a full Android. So searching around I found about "fastboot" but I'm not familiar with it. I only got my hands dirty on Odin and SP Flash Tool.
I followed the instruction here :
http://forum.xda-developers.com/kin...t-install-twrp-android-fire-os-8-5-1-t3278286
Works very well, rooted with KingRoot (which I already have offline), installed FireFlash, flashed the bootloader and recovery (100% like the instruction told me), got into TWRP, did a full backup of the current ROM and reboot. I can get it to the Carousel just fine. I attempted to flash Gapps package for ICS (gapps-ics-20120429-signed.zip) from here (found from googling around, checked the content too) :
https://docs.google.com/file/d/0B6zwjGaKK0GVUll5Sm95LWpNaDg/edit
The installation went quite well, after running Play Store, it crashes constantly. Found another tutorial on installing Google Apps on another forum, which I lost the link, so I want to attempt another Google Play install before went to CyanogenMod.
I noticed something, after each reboot, I need to re-flash TWRP and reboot. When I attempt to reflash TWRP I notice that kfhd8freedom-boot-8.4.6.img didn't have any warning anymore.
The tablet was a gift from my brother in law to my Dad. It was never been reset ever since. In fact after I installed Google Play, it still got my brother in law login in it, even though it doesn't have the Google Play store. So I figure I need to do a factory reset and start 100% fresh, just to be sure.
And this is where it went wrong. After the factory reset the device rebooted into fastboot mode. I don't know why. I see the orange Kindle Fire logo, then the screen went red then "fast boot mode" appear on screen. At this point I cannot do anything to it. Followed every power button tutorials out there, like pressing the power for 20 seconds then release then hold it for 2 seconds, or power plus volume up/volume down, no luck.
I plugged it into my PC, it shows as "Android", and below it "Android ADB". So I tried to use ADB console for it, it didn't respond. However it responds to "fastboot" commands, tried some commands from here :
http://forum.xda-developers.com/showthread.php?t=1474566&page=2
These commands works :
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
But it went straight back to fastboot mode. My guess is that the culprit is kfhd8freedom-boot-8.4.6.img.
Looking around in the forum there're so many obsolete solutions, like Kindle Fire HD First Aide download link are dead and it was intended for Fire 7.
So the questions are :
How would you recommend me to fix this? Fastboot command definitely still working from PC to my Kindle, if that is any help for this case. I really have no clue on what to do next. I only experienced with Odin and SP Flash Tool. I have no experience with fastboot.
I don't have any stock rom at hands, neither can find any googling around. Can anyone provide me with one? Just in case anything bad happen again after I fix this.
Will this work for 8.9"? Since he posted it in Fire 7 forum : http://forum.xda-developers.com/showthread.php?t=1951254
Info on my devices :
Kindle Fire Jem 8.9"
Latest stock (8.5.1_user_5159720) was installed
Rooted with KingRoot before went brick
I have no fastboot cable, but the fastboot command mentioned earlier works on regular USB (OnePlus One's stock cable)
Gapps for ICS was installed within too
I got both Windows 10 and Windows XP PCs at my hand. XP seems to recognize it better as ADB something under "android" in device manager.
I also got Ubuntu 16.04 installation, if needed.
Please help.
Thank you in advance!
Managed to boot into Fire OS
I just use fastboot to flash both kfhd8-twrp-2.8.7.0-recovery.img and kfhd8-u-boot-prod-8.1.4.bin.
After a reboot I went into TWRP, it does a few stuffs then rebooted again automatically.
Blue logo came up, then the orange logo, but it took longer than usual, I was a bit panicking. Forgot that on each first boot Android would take longer than usual.
But then kindle fire up the first time setup *phew*
First I want to get Gapps working on this device. If that working well, I'll stick with stock + GAPPS and custom launcher.
Only after that I will try CM12 on it.
I'll update on this thread later on how it goes.
Did anyone still have the stock recovery.img and boot.img?
Also after completing the initial setup my navigation and status bar went missing
The navigation bar blinks for a second then went black. While the status bar which displays wifi icons and hide the settings are missing. I cannot swipe from above at all.
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Finally SOLVED.
I forgot I can download ES file explorer from Silk. But turn out my Amazon appstore account allowed me to download it instead. Probably because my dad and brother's credentials was wiped clean from it.
I went to find flashfire.apk in my internal storage. Install it, then the unknown source popup warning appeared. Luckily it got the settings button which lead me to that particular option. After I tick it, I need to shut my kindle down, reboot then went to install it again, because there's no navigation bar available.
After it installed, turn out Kingroot's root are still intact. Kingroot's root permission pop up appeared.
Reflashed TWRP and Freedom boot. Shut my Kindle down, volume up + power and I'm in TWRP!!!
I decide I'll just go full CM this time. So, continued this :
http://forum.xda-developers.com/kind...8-5-1-t3278286
Now I'm currently updating the default Google apps from Google Play within CM 12. A little laggy but most definitely far better than FireOS.
I'll be using this Kindle for a week, I'll report here and hopefully can contribute to CM's bug report.
So far : camera, bluetooth, WIFI, GPS works out of the box. Brightness settings don't work.
Just one question, does this fastboot cable thingy "standard"? I saw one seller in my local online shop but it's for Xiaomi. Can I use it for OnePlus One and Kindle?
Oh yeah I got TWRP backup of the stock kindle, but I would still need both stock boot and recovery image. If someone kindly enough to provide me I'll be very thankful.
Checking in
Root are enabled by default, just found out about this. It got build in, barebone SU management, on which you can allow an app to have root access or not, but didn't see any comprehensive root access management like those found in SuperSU.
So installed SuperSU, told SuperSU to just update through TWRP, update binary was a breeze, all done automatically.
Watching YouTube on it was quite convenient. The screen obviously have near-retina display. Much better than viewing it on my Note 10.1 2012 obviously.
No problem browsing on Chrome.
Installed couple of other root apps, transfered it from my cheap chinese phone (Mito) using Bluetooth. All works well.
Tried to play Shooty Skies on it but it stuck on the intro screen. However on my OPO Shooty Skies refuses to run too and stuck on the intro screen. I've unlocked all characters on it I'll just wait for an update then.
Did some theming, custom boot animations works, styles applied, icons and everything applied without any problem at all.
One complain, the sound are too low, even when maxed out. Perhaps because the Dolby isn't supported by this CM yet?
My dad complained that there're too many updates after the initial setup so I use System Cleaner 2 to merge the updates into the system. The app did wonderful job on my Mito :
https://play.google.com/store/apps/details?id=com.flaki.systemcleaner2
Merged all updates into the system. If I don't do this everytime I wipe the device, the device will keep asking for updates. At least on the Gapps. It stuck at the middle, so I restart the System Cleaner 2 and it continue to do its job.
Then when I install Link2SD, which often do better job and more comprehensive apk management, weird things started to happen. It's said SuperSU are not installed. That and also couple of Google Apps. When I run Link2SD, their size is 0.
I think it's most likely caused by System Cleaner 2, couple of apps got interrupted when I merge the updated apk into the system?
So I reboot, then after I got into trebuchet, all the supposedly installed apps are gone. I don't know why. Thus I wipe everything clean again, reflash CM12, and just go into unrooted mode, update the gapps, remove my account and let my dad login using his and do whatever he want with this kindle.
Another minor update.
Since I've downloaded ICS (CM11), I figure I might just try it anyway. Since on whatever softwares I use I prefer older, stable version than bleeding edge and feature-rich but unstable ones.
Take a note I'm not saying CM12 is unstable, no problem so far, only those I pointed out in the previous post. But mostly because CM11 was marked "stable" on CyanogenMod download site.
First impression? It's snappier than CM12, and much more familiar than Lollipop. (since most devices I own still using JellyBean, with the exception of my OPO which already running Marshmellow).
My dad should be familiar with it too. Quite happy with it. But unfortunately the gapps are too outdated. It throws me server errors, and I cannot reach anything within Google Play. I can browse google websites without problem, even google play itself inside the default browser, so it's not connection problem definitely.
Updating the google play manually doesn't fix this. So any solution for this? Perhaps updated gapps for CM11/4.0.4?
Edit : eh nevermind, the Gapps provided for CM12 works with CM11. And very stable too.
Edit : CM11 for Kindle 8.9 is JellyBean 4.4, not ICS.
I guess I'll stick to CM11 for awhile then.
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
stubbe said:
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
Click to expand...
Click to collapse
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Hey Davey. Thanks for the response.
Davey126 said:
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Click to expand...
Click to collapse
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
stubbe said:
Hey Davey. Thanks for the response.
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
Click to expand...
Click to collapse
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
- fastboot cables do not work with this device
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Davey126 said:
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
Click to expand...
Click to collapse
Ah dang. Not that much of a problem though. I just like to keep stocks ROMs around just to be safe. I won't be returning this thing to Amazon anytime soon, and I guess judging by my brief experience with the FireOS it won't be much of a use for our locals using the stock ROM if I or my dad actually decide to sell it.
- fastboot cables do not work with this device
Click to expand...
Click to collapse
Mmm... okay.
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Click to expand...
Click to collapse
Ok fair enough and besides I don't go to the recovery much other than doing a backup.
Thanks Davey.
stubbe said:
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Click to expand...
Click to collapse
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Praxxer1 said:
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Click to expand...
Click to collapse
Answered elsewhere (one 48 other threads you posted to with the same question)
Stuck in Fastboot. I can flash and write and reboot, but 100% of the time it returns to FB. I had flashed freedom boot 8.46 2x. I most recently had lineage 14.1 and twrp 2.78.
Tried every tool in the book zero have worked.
UPDATE 6-9, out of fastboot, now stuck on kindle logo.
tia
KF 8.9hd jem