Related
Hello, after playing with a tablet I got boot loop so below is solution for this.
This is what I wrote first:
I purchased Chinese tablet called CyberNav, there is link to the website with specs http://www.dracotek.com/cybernav-7-...ps-navigator-ultra-slim-wifi-8gb-gps70yw.html It works great and is worth the money. I received- on request- firmware for it, but it is with .img extension and I have no idea how to get to the files. Attached application PhoenixCard should install it on sd card but it does nothing. So there is my question- can anyone help me with it? Possibly root it? Or update to newer firmware version? I'll post a link to, just need to upload it to my dropbox on my next break at work.
Sek
im pretty sure you need a 3rd party application to flash that firmware, i think you load the .img file into the software on your pc, connect tablet in flash/recovery mode then flash it that way, dont know which software you would need to use though , sorry i cant help further
There is link to rar package http://db.tt/jm7eHfbq
If there is someone who wants to spend some time... Please help.
Bump
Some new infos:
As far I found out tablet is detectable during boot in adb, but it stays in boot loop. I think I've got right usb drivers.
I tried unyaffs the .img file using C:/unyaffs/unyaffs pw08.img but it shows file corrupted (might be wrong method?).
Logcat attached.
Maybe there is someone who will find what it's missing...
I see there is nobody who can help me, so... If some of u have similar problem with chinese tablet- bootloop, can't flash it with LiveSuit our update from sdcard, I found solution which worked for me. Using adb, pulled catalog /dev/data/ to hard disk, then deleted all dalvik cache, installed by me apps and almost every other file from /data on my hard disk. Then typed adb remount, then adb shell rm -r /dev/data/* to delete all data catalog on tablet. Then pushed /data catalog from my hard disk to tablet, and finally adb reboot. And it WORKS! Booting without problems. I wasted 4 days on research how to turn it in flash mode etc. But it was very simple.
Cheers
Sek
Hi, sek111
It was necessary to use the LiveSuite to flash through usb.
Thank you very much, from your post, I found the firmware for my tablet.
An experience with another low cost tablet with Bootloop
I happen to got my tab (Wammy from WickedLeak.org) stuck in BootLoop and was struggling to get a way out for the past 3 days, checking almost all of the posts for this issue!
The tab would stuck on the android loading animation despite running for 2-3 hours and after several hard reboots, it throw-ed following error-
Encryption Unsuccessful
encrytion was interupted and cant complete. as a result the data on your tablet is no longer accessible
to resume using your tablet, you must perform a factory reset. when you set up your tab after the reset, u'll hav an opportunity to restore any data that was backed up to ur google account
Click to expand...
Click to collapse
Despite going for the factory reset, it still didn't workout as the reset activity never completed or proceeded. I happen to be a beginner/noob and was trying my luck with possible solution but was comfortable with ADB stuff and workaround. Well i checked the solution which sek111 offered in this post and it was most closely helped me out. So i would like to Thank him a ton for sharing his solution.
Another method for few others if you don't get through the technical stuff and handling all the flashing tools, i was successful in bringing up the setting window of my tab and chose to do Reset via GUI which worked. Actually my battery got drained out to 7% and a popup message for same displayed while i was on the above error page. I selected the "check battery" option from that pop up and got my way out via factory "Backup and Reset" option under settings.
I hope this might help few people if not all! But the XDA forum is great and everyone will find a solution here. Cheers!!!
So I got this wm8850 chinese generic tablet. The camera is in the front in the middle (wide). It was shipped to me with 4.0.3 in boot loop. I soon found out that it boots into safe mode when I usb to pc. This is the furthest I've gotten with it so far. I can adb into it and have already tried to wipe data. It seems like since its from factory screwed up that a may need to reload the firmware or the os or something. Im kind of a noob because I only have my droid x. I've gotten it out of a boot loop before but I also knew what I had done to cause it so I fixed it. I tried to follow seks adb commands but im too noob to do it I guess. I was able to wipe data and dalvik-cache. Issue still occurs . If anybody can give me some adb commands than can help I would greatly appreciate it. Im fairly sure that I found the firmware elsewhere on xda. I thank you guys for any help at all you can give. I don't wanna send it back without trying everything software related as I can, but ill send it back if I can't fix it or if I brick it
Sent from my DROIDX using xda app-developers app
i have same problem in my china mobile.. dupad k1 ... after in installed new boot screen, device stuck in boot... please help to recover my device in step by step....
Hey guys, first off, I got a new Kindle Fire HDX 8.9 from BestBuy yesterday and of course I had to mess with it. I do it to every new tech I buy haha.
Well, stupidly I didn't realize there was a recovery option for the 8.9 just yet, so I went ahead and rooted my Kindle Fire and attempted to install the GAPPS and remove the signature verification inside the Kindle Fire. This all went okay but then I noticed I could no longer download files from the Amazon store nor did the Google Play store work for me. So I attempted to reset the Kindle back to factory settings thinking it would just wipe it all and I could start anew. I removed root access through SU and all that before resetting it to it's default settings.
After it finished, I realized it didn't get rid of the Google play store or any of the apps and I still couldn't download any files from the Amazon store. So I used ADB to install some files like ES File Explorer, SU, Busybox, etc.
After all that I noticed something was wrong with my Root access, I couldn't fully use any of the applications that required Super User. I couldn't modify the build.prop to attempt at resetting the Kindle Fire to it's full stock form, so instead I modified it on my computer, then pushed it through to ES.
After I had it on ES I deleted the original Build.prop, saving a back-up of course, and then putting in the new one. Low and behold, after doing this, I reset my Kindle and now I'm stuck at a gray Kindle Fire screen for about 10 or so seconds then it just goes black with the light still coming through. I can boot into recovery mode, but only have two options, to reset to factory, or reboot.
I did reset it to factory here, thinking it would do some good, but nothing came out of it. Either way, ADB didn't recognize my device, even before I reset it to factory settings via recovery mode.
So I'm at a loss now. I can't get ADB to recognize my device and I have no idea how to get it to. Any help on this matter is greatly appreciated.
I am running Windows 7 64-bit right now and am in the process to dual booting Ubuntu in an attempt to see if I can get it to find my device. I am new to Linux so I'm not sure how that will go.
Amazon, being the amazing company they are, is sending me a replacement, but I would like to get this one to work so they don't have to fork out another Kindle for my stupid mistake. Again, any help or information on what I can do to proceed from here would be amazing.
Thank you for taking the time to read this and look forward to some responses!
Fataldelay said:
Hey guys, first off, I got a new Kindle Fire HDX 8.9 from BestBuy yesterday and of course I had to mess with it. I do it to every new tech I buy haha.
Well, stupidly I didn't realize there was a recovery option for the 8.9 just yet, so I went ahead and rooted my Kindle Fire and attempted to install the GAPPS and remove the signature verification inside the Kindle Fire. This all went okay but then I noticed I could no longer download files from the Amazon store nor did the Google Play store work for me. So I attempted to reset the Kindle back to factory settings thinking it would just wipe it all and I could start anew. I removed root access through SU and all that before resetting it to it's default settings.
After it finished, I realized it didn't get rid of the Google play store or any of the apps and I still couldn't download any files from the Amazon store. So I used ADB to install some files like ES File Explorer, SU, Busybox, etc.
After all that I noticed something was wrong with my Root access, I couldn't fully use any of the applications that required Super User. I couldn't modify the build.prop to attempt at resetting the Kindle Fire to it's full stock form, so instead I modified it on my computer, then pushed it through to ES.
After I had it on ES I deleted the original Build.prop, saving a back-up of course, and then putting in the new one. Low and behold, after doing this, I reset my Kindle and now I'm stuck at a gray Kindle Fire screen for about 10 or so seconds then it just goes black with the light still coming through. I can boot into recovery mode, but only have two options, to reset to factory, or reboot.
I did reset it to factory here, thinking it would do some good, but nothing came out of it. Either way, ADB didn't recognize my device, even before I reset it to factory settings via recovery mode.
So I'm at a loss now. I can't get ADB to recognize my device and I have no idea how to get it to. Any help on this matter is greatly appreciated.
I am running Windows 7 64-bit right now and am in the process to dual booting Ubuntu in an attempt to see if I can get it to find my device. I am new to Linux so I'm not sure how that will go.
Amazon, being the amazing company they are, is sending me a replacement, but I would like to get this one to work so they don't have to fork out another Kindle for my stupid mistake. Again, any help or information on what I can do to proceed from here would be amazing.
Thank you for taking the time to read this and look forward to some responses!
Click to expand...
Click to collapse
I think you can contact Amazon, asking them How to get into the fastboot mode or ADB mode, the stock recovery mode can do nothing good. I think the only way to fix it is via ADB mode.
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
---
Hi everyone,
i have a rooted Kindle Fire HDX 7" which is kind of softbricked. Maybe even hardbricked but my knowledge doesnt reach that far to determine.
Here's the thing. I already got in touch with Amazon, they checked my Amazon Account and were pleased to send me a new Kindle since i still got warranty on it.
Okay so far so good.
But here comes the real deal.
I'm pretty sure my warranty doesnt really cover the whole root -> brick story.
I told the Lady that after a factory reset the Tablet keeps trying to start the Setup over and over again. Which is indeed the case. I did not mention anything else.
So. My plan was, since i'm still able to go into safestrap recovery, to delete everything that could point out that the Tablet was rooted. Atleast on the first view.
TL.DR:
Is it possible to delete Safestrap/TWRP via the Terminal Command?
I know you can browse through the Tablet, but i couldnt find where the Folders are located.
Even if the Tablet doesnt Boot at all after deletion, i wouldnt mind.
Cause then i could still keep my new Tablet and hope they cant find anything on the broken one.
Hope anyone can help me.
If it is hard to understand what i meant i can give you further informations.
It's kind a hard for me to describe such technical things in a foreign language.
If you can access safestap, you can unbrick your device mate.
Well i kind of tried everything possible.
It's not on topic but i can describe what i did, maybe it helps other to not do the same mistake.
I had my Kindle rooted on 13.3.2.4 with the HDX Toolkit.
Everything worked fine since one day the Google Store stopped working.
Well at that time i wasnt using the Tablet on a daily basis so i didnt mind much and got a little off touch with the whole rooting thing, and the do's and dont's.
Then after a couple of weeks i got a bit frustrated over the fact that the integrated Prime Video Streaming is so out of date, that you cant even watch movies USK18 or switch languages within the Movie.
So i decided to use the Kindle as it was meant to by amazon and remove everything.
I really shouldve read more about the prodecure, i know that now.
But here's what i did:
1. Wiped and Removed my non-StockROM
2. Booted on StockROM and did a Factory Reset
3. Sh#t got weird so i went into recovery and wiped the StockROM aswell
4. Now i can still go into Recovery, but when i try to Boot i kind of dont have a FIrmware installed. It trys to re-do the Setup where you have to choose ur language over and over again.
So by now i already know what i should've done instead.
But at this point; my Kindle doesnt get recognized by my PC nor by ADB.
And i dont know what i can do with the Safestrap Recovery at the beginning.
So far, any more ideas?
Should i still try to unbrick it or just wipe my fingerprints off of it and hope i can keep the new one.
KDroidB said:
Well i kind of tried everything possible.
It's not on topic but i can describe what i did, maybe it helps other to not do the same mistake.
I had my Kindle rooted on 13.3.2.4 with the HDX Toolkit.
Everything worked fine since one day the Google Store stopped working.
Well at that time i wasnt using the Tablet on a daily basis so i didnt mind much and got a little off touch with the whole rooting thing, and the do's and dont's.
Then after a couple of weeks i got a bit frustrated over the fact that the integrated Prime Video Streaming is so out of date, that you cant even watch movies USK18 or switch languages within the Movie.
So i decided to use the Kindle as it was meant to by amazon and remove everything.
I really shouldve read more about the prodecure, i know that now.
But here's what i did:
1. Wiped and Removed my non-StockROM
2. Booted on StockROM and did a Factory Reset
3. Sh#t got weird so i went into recovery and wiped the StockROM aswell
4. Now i can still go into Recovery, but when i try to Boot i kind of dont have a FIrmware installed. It trys to re-do the Setup where you have to choose ur language over and over again.
So by now i already know what i should've done instead.
But at this point; my Kindle doesnt get recognized by my PC nor by ADB.
And i dont know what i can do with the Safestrap Recovery at the beginning.
So far, any more ideas?
Should i still try to unbrick it or just wipe my fingerprints off of it and hope i can keep the new one.
Click to expand...
Click to collapse
So you can open safestap ? If you can, then try ADB on a Linux/Mac machine. It will work. Windows has a problem with the drivers. Also I am not sure about this, but if you access the stock kindle recovery and do a factory reset from there, you might wipe safestap.
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