Related
Hello Friends,
I just got my G-tab today morning and rite now it not working (Not even 12 hours)
Its still intact in factory condition with Android 2.2 and all latest updates. I haven't jail broke it yet.
I just downloaded 'LaunchPro' from G-Market and the screen got hanged so I rebooted.
It shows Viewsonic Screen with birds >> g Tablet logo >> Tap n Tap >> Tap and Tap disappears and gets stuck in 'n' and 'paw' screen.
I am sure there should be a cure for this as I haven't done anything yet. Also its not in boot loop. Just stays on the screen.
Please help me.
Please help guys??
Read up on clockworkmod, nvflash, and visit member goodintentions's gtabfordummies website.
Sent from my Droid using XDA App
Go to my website start here page at the following link.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Congrats, you have somehow bricked your gtab before you even tried to flash a custom rom.
You're a code red.
ganesh911 said:
Hello Friends,
I just got my G-tab today morning and rite now it not working (Not even 12 hours)
Its still intact in factory condition with Android 2.2 and all latest updates. I haven't jail broke it yet.
I just downloaded 'LaunchPro' from G-Market and the screen got hanged so I rebooted.
It shows Viewsonic Screen with birds >> g Tablet logo >> Tap n Tap >> Tap and Tap disappears and gets stuck in 'n' and 'paw' screen.
I am sure there should be a cure for this as I haven't done anything yet. Also its not in boot loop. Just stays on the screen.
Please help me.
Click to expand...
Click to collapse
It's not bricked. I've seen this happen on stock ROM's when multiple launchers are installed but no default launcher has been selected. Try a data wipe from recovery (if you have an early stock recovery look here: http://forum.xda-developers.com/showthread.php?t=1030915).
If that clears it up then you can reinstall whatever launcher(s) you like just make sure to make one default.
K J Rad said:
It's not bricked. I've seen this happen on stock ROM's when multiple launchers are installed but no default launcher has been selected. Try a data wipe from recovery (if you have an early stock recovery look here: http://forum.xda-developers.com/showthread.php?t=1030915).
If that clears it up then you can reinstall whatever launcher(s) you like just make sure to make one default.
Click to expand...
Click to collapse
Really? Cool! Since I used the stock rom for about 5 minutes before I ditched it, I'm happy someone else knows about it more than I do.
goodintentions said:
Really? Cool! Since I used the stock rom for about 5 minutes before I ditched it, I'm happy someone else knows about it more than I do.
Click to expand...
Click to collapse
I ditched it pretty quickly, too. In this case the first place I noticed this problem was on one of Roebeet's stock-based ROMs (Mountain Laurel, I think). Another one of those "It's failing for everyone but me" kind of moments so I decided to research it. Took a few times to duplicate it successfully since it doesn't happen on every stock ROM either. More likely on 1.2 based stuff.
OK. I have had my Atrix 4G since it first came out. I rooted it and installed apps and made customizations to it, etc.
I never installed a custom ROM since the tweaks I made fit my taste enough to not need to install a custom ROM. I have thought of it...but that is for another time.
Anyways, I recently changed fonts on using FontChanger and everything was working fine. However, last night I decided to change to another font and after rebooting my phone, I am now stuck in the ever so pleasant "Boot Loop".
I have tried wiping and restoring back to factory defaults, which appeared to work, but once I start going thru the process of setting up the phone and getting to the "home" page, the phone will suddenly automatically reboot and start to loop again. I can perform a reset which allows me to go thru the setup process again, but it suddenly reboots again after a few minutes.
I am guessing that perhaps the font is still causing problems, but I am not sure how to check to see if that is the case or not.
I have looked at other boot loop threads but I keep getting a bit confused as to what I should attempt or not attempt to do. It seemed to me that loading the 1.2.6 SBF might be my answer, but I have read that I could brick my phone doing that. Not to mention that some of the download links are dead....
Sorry for being yet another numbnutz and the long thread, but I would greatly appreciate some guidance on how to recover!
Thanks!
Ok... So after resetting my phone a few times I noticed that it goes into the boot loop cycle once the screen shuts off/or goes into sleep mode. If I keep the system from going to sleep everything appears to work fine.
My guess is still a font issue, but I thought a factory reset would've replaced the font back to default.
Anyone experience this issue or something similar to it?
And as a second thought can someone link me to the default fonts that I can try to reload?
UPDATE: well it looks like i am good to go again. It just occured to me that I can just download and use FontChanger to replace the bad font with the stock font. i let me phone go to standby mode and it didnt boot loop.
MODERATOR - Please feel free to close this thread as I believe I solved my own problem.
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh:
This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images (md5sum: 5e774497b3bad5c47d1c744410f6db12)
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+ramdisk.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+ramdisk.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+ramdisk.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
rbox said:
This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+recovery.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+recovery.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+recovery.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
Click to expand...
Click to collapse
Awesome rbox! I see you've been busy...Really appreciate everything you do for us Fire TV folks.
Awesome work as always!
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
samykoka said:
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
Click to expand...
Click to collapse
You can flash whatever version you want...
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
daffung said:
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
Click to expand...
Click to collapse
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Many thanks, rbox -- unbrick_firetv2.bat worked for me in bootcamp. Selected unbrick+ramdisk.img, then rebooted into TWRP. Initially when I installed prerooted 5.0.5_r2, setup gave me a screen (after remote pairing and language selection) that it was checking for updates. The setup then halted with an error window that it could not connect to Amazon's server, and that I should power off and reset the AFTV. I then flashed prerooted 5.0.4_r2, completed the initial setup, and reflashed prerooted 5.0.5_r2 (which let me get around the update error).
Again, thanks for all your work!!
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
i wonder what caused that bricked.. , ( well it was already bricked, when amazon send it to me it was stuck at white amazon logo, then only when i applied the pre rooted firmware, thats when it stop showing screens from there..wouldn't it fix the problem already since i was able to get to recovery.....
id try the sd card 1 last thing il probably go to walmart and try that, if nothing fix it i guess its total beyond brick..
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Takeoo111111 said:
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Click to expand...
Click to collapse
Thanks. I fixed it all.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
daffung said:
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
Click to expand...
Click to collapse
Well try the unbrick image and see if it works.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox said:
Well try the unbrick image and see if it works.
Click to expand...
Click to collapse
yup,
sucessfully flashed unbrick.img, and had sd card ramdisk-recovery.cpio.lzm.
still the same...
no boot, no screen, not even white screen?
and no signal from hdmi
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black and then back to the Video in Kodi twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
harlekinrains said:
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
Click to expand...
Click to collapse
The unbrick image just puts enough on system to be able to get to recovery. If you can already get to recovery, it won't get you anything. The disabled stock recovery isn't going to effect anything while running android. All it does it prevent the bootloader from running it. I can't really explain it if you did an advanced wipe of data.
Hardware Issue probably. Thanks for the fast response.
Cheers.
(I'll do another advanced wipe - just for kicks.. )
edit: Went through with another full wipe - rebooting the device afterwards (= softbrick for sure, because not even TWRP is accessible and there is no OS on the device) - which at that point got "parked" on the white amazon logo indefinitely. (Perfect for the "I aint know nothing" returning the device approach. Just in case Amazons 5.0.5 turns out to brick a few more Fire TVs... As long as rbox didnt modify the kernel, I'd say its Amazons fault. ) Then went through the unbrick procedure in this thread - which worked as described (TWRP was installed on the device and autobooted on the powercycle after the unbrick script had finished). Then installed 5.0.5r1 again and rebootet - just to be met with the same error profile as before "dark screen" - not even the animated amazon logo (just the white one in the beginning).
This time - on a better TV screen it was visible though, that the screen showed a small horizontal line, and then flashed in a lighter black color twice, before going back to full TV black. So yes the problem seems to lay somewhere on the video signal path. Its curious though, that TWRP still got (and gets) displayed...
Works perfect. Thx
Can someone help me? I followed all the steps in the guide and when the unbricking program is writing the filesystem, it always gets stuck at 17%. Maybe I am doing something wrong?
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
I am in a boot loop. Goes to amazon white logo. Light on FireTV2 turns orange then reboots into custom recovery but it automatically starts trying to mount partitions (one of them is cache) and it fails on all of them. Then moves along to the white amazon screen again and repeats the entire process. I ran the unbrick.img and the problem persists.
I'm currently in the process of running unbrick+recovery.img method to see if it makes any difference. Should it? Is there anything that I may be overlooking?
I'm fairly sure that the reason this happened is from checking ALL the check boxes in the format/wipe section of the custom recovery. After that these issues happened. Does that mean permabrick?
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