I search all over the internet and none address my issue.
I use my Gtab occasionally. Last week I turned on my tablet and it goes to the first screen with the three birds then move to the "Gtablet" screen and stays there. Tried several time to no avail. I finally did a hard reset (had to open the back), still the same thing. I then tried the recovery (ON button while holding Volume +) The three birds again shows up and the small message on the top left of the screen saying Recovery Key detected and stays there. Nothing else happens. All of the thread I saw always refers to the last option is to do the recovery mode. Well, my recovery mode does nothing. Anything else I can try?
Thanks for any help...
You need to nvflash. Please google "gtablet for dummies" website and follow directions.
good time to try JB
mbenazeraf said:
I search all over the internet and none address my issue.
I use my Gtab occasionally. Last week I turned on my tablet and it goes to the first screen with the three birds then move to the "Gtablet" screen and stays there. Tried several time to no avail. I finally did a hard reset (had to open the back), still the same thing. I then tried the recovery (ON button while holding Volume +) The three birds again shows up and the small message on the top left of the screen saying Recovery Key detected and stays there. Nothing else happens. All of the thread I saw always refers to the last option is to do the recovery mode. Well, my recovery mode does nothing. Anything else I can try?
Thanks for any help...
Click to expand...
Click to collapse
Since it appears you need to re-nflash back to BL1.2 I would think this would be a great time to try out one of the JB Roms. I would suggest Smooth Bean, http://forum.xda-developers.com/showthread.php?t=1900562.
I think some people issues with it are 1) not following install instructions, 2) related to Chrome and/or flash. I'm not a big fan of Chrome. Would prefer Opera Mobile but hadn't got flash to work yet with it but flash does work with the default browser. Also tried Firefox, flash didn't work there either. You will be surprises how fast it seems to be.
Well, I wrote a very thorough post explaining my situation, and when I tried to post it I was informed I was trying to register for my forum account instead. *facepalm* So with that thirty minutes wasted, let's try this again.
I have a Kindle Fire HDX 7. Software 4.5.2. I rooted it with an exploit, deleted some Metrics system files, and then after rebooting came up to a broken "desktop." The main Favorites window flashes from white to gray at me, there are no icons in it. I can't run any apps. I can get to the Settings menu, enable ADB, MTP, etc., but I can't turn on Wi-Fi or do updates. I did a Factory Reset, but that just erased all my content. If I reboot from this situation, I get stuck at the orange animated logo screen forever. If I hold the Volume + button and choose Factory Default from there, I can get back to the flashing Favorites desktop window, but still can't do anything just as before.
I have installed the Android SDK for Windows, installed the adb_usb.ini files, and the device is not recognized by Windows at all. It charges, but that's it. I tried using Ubuntu and SoupKit. They also don't see the Kindle as being there. No matter how many times I reboot the Kindle, all the SoupKit commands just hang at "Waiting for Device".
I made a Factory Cable. When I plug it in, the Kindle doesn't turn on. Holding down the power button does nothing. If I plug back in a regular USB, it turns right on. If I plug the Factory Cable in at the Flashing favorites screen, I hear the "plugged in" chime and the charging icon appears on the battery, but nothing else happens. If I try to reboot from there, with the Factory Cable still in, it shuts down but won't restart. I am open to the possibility I messed up the cable, but continuity seems good with my meter from both ends of the cable and from the solder joints to the micro-USB end, etc.
Has anyone seen the flashing desktop behavior? What should I be doing to try to get my Kindle recognized, so I can push the stock firmware back to it to fix this? Any help would be greatly appreciated. I made a foolish mistake and I can't seem to correct it myself, so I'm hoping someone else out there has the answer I'm overlooking. Thank you for your time.
Make sure you have the Kindle Fire ADB drivers installed.
EncryptedCurse said:
Make sure you have the (link text clipped due to restrictions on <10 posters) installed.
Click to expand...
Click to collapse
I had already installed the Google USB driver using the SDK Manager, and also modified adb_usb.ini and so forth, to no effect. I tried the instructions at the above link, though, since that Add-On site was something new. It appears some things have changed since that article was written, though, since the only thing available from the Add-On site from Amazon now is just the Kindle USB driver. I installed it, but Windows still doesn't recognize the Kindle. I rebooted the computer and the Kindle just to be sure.
To be clear, when I say it doesn't recognize it, I mean it doesn't even appear in Device Manager as an unknown device. No matter which computer, USB port, or cable I use, Windows 7 and Ubuntu simply do not see a device as there. The Kindle chimes and shows the charging icon, but Windows doesn't see anything as being plugged in.
From what I'm reading, it appears the factory cable I made is useless with the Fire HDX line.
I notice that the SuperSU app is still installed for what it's worth. I can't run anything, so it's kind of hopeless. I can't seem to find the original exploit that I used, but I basically just tapped a button that said "Gimme Root" and then I had super user access. Dangerous, dangerous super user access.
I'm not opposed to opening the Kindle up and tinkering with things, if there's any chance that will help correct this problem.
Valence1981 said:
I made a Factory Cable. When I plug it in, the Kindle doesn't turn on. Holding down the power button does nothing. If I plug back in a regular USB, it turns right on. If I plug the Factory Cable in at the Flashing favorites screen, I hear the "plugged in" chime and the charging icon appears on the battery, but nothing else happens. If I try to reboot from there, with the Factory Cable still in, it shuts down but won't restart. I am open to the possibility I messed up the cable, but continuity seems good with my meter from both ends of the cable and from the solder joints to the micro-USB end, etc.
Click to expand...
Click to collapse
"Factory cables" (sometimes called fastboot cable) are useless on all HDX models. Stick with a standard, high quality USB cable. I realize this seems counter intuitive but Amazon has done their best to make the latest generation of devices inaccessible to those looking to leverage the hardware or simply recover and non-functioning device.
Your issue with 'seeing the device' is likely due to Windows drivers. If the suggestion from @EncryptedCurse doesn't work suggest deleting all related entries from device manager when the device is tethered, reboot and then reconnect. Windows should install the correct drivers assuming you downloaded the Kindle specific ones in advance. There are shortcuts to this procedure (eg: a reboot really isn't necessary) if you know your way around Windows.
Davey126 said:
"Factory cables" (sometimes called fastboot cable) are useless on all HDX models. Stick with a standard, high quality USB cable. I realize this seems counter intuitive but Amazon has done their best to make the latest generation of devices inaccessible to those looking to leverage the hardware or simply recover and non-functioning device.
Your issue with 'seeing the device' is likely due to Windows drivers. If the suggestion from @EncryptedCurse doesn't work suggest deleting all related entries from device manager when the device is tethered, reboot and then reconnect. Windows should install the correct drivers assuming you downloaded the Kindle specific ones in advance. There are shortcuts to this procedure (eg: a reboot really isn't necessary) if you know your way around Windows.
Click to expand...
Click to collapse
I plugged the Kindle in (I'm at the Settings menu on it, since staying at the launcher/home/favorites screen just threatens to give me epilepsy with its constant flashing), I removed all the USB host controllers and root hubs, then scanned for hardware changes to reinstall them. The Kindle is not found, as a recognized device or an unknown one. As I said, when I boot from a thumb drive into Ubuntu, it doesn't find it either. When I run adb devices, it says no device is found. I have heard of people getting it to take ADB commands anyway, despite the not found error, by just repeatedly rebooting the Kindle, but it hasn't worked for me.
Valence1981 said:
I plugged the Kindle in (I'm at the Settings menu on it, since staying at the launcher/home/favorites screen just threatens to give me epilepsy with its constant flashing), I removed all the USB host controllers and root hubs, then scanned for hardware changes to reinstall them. The Kindle is not found, as a recognized device or an unknown one. As I said, when I boot from a thumb drive into Ubuntu, it doesn't find it either. When I run adb devices, it says no device is found. I have heard of people getting it to take ADB commands anyway, despite the not found error, by just repeatedly rebooting the Kindle, but it hasn't worked for me.
Click to expand...
Click to collapse
My bad - I overlooked some key details in your original post even though clearly stated. If you are not seeing the the device from any host (and you have certainly done the things I would have suggested) there is little you can do to recover via standard methods. A couple longshot suggestions:
- change cables. I know you tried a homebuilt cable but grab a couple standard cables just to rule out a bad wire; crappy usb cables are more common than people think
- check for a bent/missing pin in the micro-usb port; possible you aren't making a data connection (for others benefit, data and charge use different pins)
I realize both the above are highly unlikely given the sequence of events that lead up to your current problem. Running out of ideas ...
I doubt this will help, but one long shot on Windows is try to use the HDX toolkit to install the adv drivers. It won't do anything else with this build, but if this is a driver issue, it could possibly fix it. Also, if you can try revoking adb permissions if you can get to that window and try a different usb port.
These are all last ditch efforts though.
I tried the HDXToolkit driver install. It seemed promising, but it still doesn't see the Kindle. Checking the connector to see if the data pins were damaged was a good idea, but unfortunately they look unmangled. I am using a regular USB cable at this point, by the way.
I can't disable ADB mode on the Kindle itself. I can go to the Developer menu and try to disable it, but it just kicks me back to Settings and the option stays set to On when I go back to it. I can switch between MTP and CTP for whatever that's worth.
I appreciate the optimism. I'm quite upset with myself for doing this to my Kindle, as I really was getting a lot of use out of it. I can't help but be a little mad at Amazon, too, for making it so hard to fix this.
Oh, I was also going to mention that when I go to the stock recovery window with the option between reboot and factory restore, at the bottom under the Kindle logo it says "No Command" not sure what the significance is of that. I've seen where some people get a lot of error messages in that area.
Valence1981 said:
I tried the HDXToolkit driver install. It seemed promising, but it still doesn't see the Kindle. Checking the connector to see if the data pins were damaged was a good idea, but unfortunately they look unmangled. I am using a regular USB cable at this point, by the way.
I can't disable ADB mode on the Kindle itself. I can go to the Developer menu and try to disable it, but it just kicks me back to Settings and the option stays set to On when I go back to it. I can switch between MTP and CTP for whatever that's worth.
I appreciate the optimism. I'm quite upset with myself for doing this to my Kindle, as I really was getting a lot of use out of it. I can't help but be a little mad at Amazon, too, for making it so hard to fix this.
Oh, I was also going to mention that when I go to the stock recovery window with the option between reboot and factory restore, at the bottom under the Kindle logo it says "No Command" not sure what the significance is of that. I've seen where some people get a lot of error messages in that area.
Click to expand...
Click to collapse
Some very left-field ideas:
- try enabling bluetooth. Obviously if you can get that working there is a way to move files to/from device which might provide additional repair/recovery options.
- there is a rumor that long pressing power (40+ sec) performs some type of 'hard reset' on the device. Never see it work but worth a try.
If the device is still within warranty reach out to Amazon. They are pretty good about providing replacements (say it died during an update) although it will likely be a refurb. Who knows, might get one with a low enough fimware level to unlock. That opens a entirely new set of options.
It would appear that the HDX can't use Bluetooth for file transfers, only for connecting peripherals like keyboards and speakers. I'm going to try it anyway.
I have done the long power button hold down, but it doesn't seem to do anything.
I believe I should be in warranty. I got my Kindle for Christmas, so it's only about 6 months old. I'd rather not have to lie to customer service, though. So I'm still prodding at this trying to find a solution. If I could just get WiFi to work, so I could download a firmware update, I think that might help, but of course everytime I put in my network information and tell it to save it, it kicks me back to the Settings window and I get no connection.
The 40 second Hard Reset never worked in my case, although My Kindle didn't even boot up after my stupidity.
Valence1981 said:
It would appear that the HDX can't use Bluetooth for file transfers, only for connecting peripherals like keyboards and speakers. I'm going to try it anyway.
I have done the long power button hold down, but it doesn't seem to do anything.
I believe I should be in warranty. I got my Kindle for Christmas, so it's only about 6 months old. I'd rather not have to lie to customer service, though. So I'm still prodding at this trying to find a solution. If I could just get WiFi to work, so I could download a firmware update, I think that might help, but of course everytime I put in my network information and tell it to save it, it kicks me back to the Settings window and I get no connection.
Click to expand...
Click to collapse
Understand the ethical concern. Stating it died during an update is technically correct provided you don't indicate who was doing the updating. If asked if the device is rooted then you should come clean (which could impact Amazon's decision whether to replace). I have a great relationship with Amazon and believe honesty will ultimately get you further than deception.
So it doesn't appear there is anything else I can do about this. The Kindle isn't recognized by any computer I have, using Windows XP or 7, or using Ubuntu. I read that XP might be able to see it if I disabled ADB, but it's permanently turned on and if I try to turn it off it kicks me back to the Settings menu without actually changing the setting. Since no computer can see it, I don't think there is anything I can do to recover it. Unless someone figures out a way to flash the ROM by taking the thing apart and doing it manually, which I don't think is going to happen anytime soon. I can't believe I ruined my Kindle. Looks like all that's left is contacting support and seeing if they'll help me with a replacement.
Actually, one other thing. If I have to send the old one back, won't they notice that SuperSU is installed and realize what I did?
Valence1981 said:
So it doesn't appear there is anything else I can do about this. The Kindle isn't recognized by any computer I have, using Windows XP or 7, or using Ubuntu. I read that XP might be able to see it if I disabled ADB, but it's permanently turned on and if I try to turn it off it kicks me back to the Settings menu without actually changing the setting. Since no computer can see it, I don't think there is anything I can do to recover it. Unless someone figures out a way to flash the ROM by taking the thing apart and doing it manually, which I don't think is going to happen anytime soon. I can't believe I ruined my Kindle. Looks like all that's left is contacting support and seeing if they'll help me with a replacement.
Actually, one other thing. If I have to send the old one back, won't they notice that SuperSU is installed and realize what I did?
Click to expand...
Click to collapse
Sorry for your troubles. Amazon is pretty easy going - at least in my region. If the device is in warranty and you simply describe the symptoms without going into too much detail you should get a replacement. I don't believe they inspect devices beyond looking for obvious physical damage. The device will likely get 'reprogrammed' and be sold as a refurb. It makes little economic sense to have a tech inspect returned devices unless they are looking for something specific or a pattern of failures. Good luck.
Any have file APQ8074.hex and 8074_msimage.mbn for unbrick QHUSB?
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
horgenblorg said:
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
Click to expand...
Click to collapse
The symptoms you describe suggest a hardware vs software problem. Guessing bad memory (or controller) given the random boot behavior. Unfortunately, there is little you can do to rectify the problem, even if software based, on an unrooted 4th gen HDX. ADB will not allow privileged access unless the device rooted.
Look on eBay for another motherboard. Might also want to grab a daughterboard as well.
Watch some teardown videos on YouTube. Everything applies to the 4th gen as it does from the 3rd gen as far as taking it apart.
In total you can fix it for around $65. That's with buying both boards which you possibly only need the motherboard.
Sent from my KFSAWI using Tapatalk
Hi! I am using Fire phone, i post in this page because no one helps me in amazon fire phone thread. My phone started to freeze so i rebooted it, since 2 weeks i am stucked at amazon logo, can't reach fire logo, just reboots continously, can t acces recovery/fastboot. I can turn off the phone just when it is not plugged into charge. When i connect fire phone to pc, i hear a sound that show me it is connected, adb doesn't recognize it, device manager doesn't show any new device when that sound appears(that sound appears when reboots, it is like removing and connecting a device into usb). Battery percentage doesn't show, just the icon of a empty battery and a cable. Knows somebody a fix? Fire os 4.6.6.1 all stuf is stock, adb installed correctly.
ozan2 said:
Hi! I am using Fire phone, i post in this page because no one helps me in amazon fire phone thread. My phone started to freeze so i rebooted it, since 2 weeks i am stucked at amazon logo, can't reach fire logo, just reboots continously, can t acces recovery/fastboot. I can turn off the phone just when it is not plugged into charge. When i connect fire phone to pc, i hear a sound that show me it is connected, adb doesn't recognize it, device manager doesn't show any new device when that sound appears(that sound appears when reboots, it is like removing and connecting a device into usb). Battery percentage doesn't show, just the icon of a empty battery and a cable. Knows somebody a fix? Fire os 4.6.6.1 all stuf is stock, adb installed correctly.
Click to expand...
Click to collapse
Sorry - this forum/thread is for HDX devices only. Fire phone is a completely different beast. A freeze at the Amazon logo is indicative of a bootloader or hardware failure which have nothing in common with HDX devices.
Davey126 said:
Sorry - this forum/thread is for HDX devices only. Fire phone is a completely different beast. A freeze at the Amazon logo is indicative of a bootloader or hardware failure which have nothing in common with HDX devices.
Click to expand...
Click to collapse
Thanks for info, i used this thread because nobody helped me at fire phone section and also i didn't find any fix on google
I got a cheap Fusion5_108 tab off ebay working but with a cracked "screen"
i've ordered a new digitizer... atm it's totally unresponding to touch, but will work with a mouse / keyboard in the usb A socket on the tab.
So i was playing with it, i plan to use it for one specific task... part of a train driving control desk, the tablets will be the displays found in German trains... i.e. the 'MFA' thats speedo gauges and lights on one tab, electronic timetable on another tablet, the engine dignostic data on another tab, brake pressure gauges on another etc... i already have a lenovo A6700-f that i replaced the digitizer on and did the same things to, and it still works fine.
I loaded the 'TS_MFD' app that works with the train sim via tcp, got it all working fine.
Then i decided i didnt like the google search bar along the top of the home screen, and found out online that by disabeling google services app, it'd get rid of it... so i did that, the search bar went.. but left a shadow box where it used to be... so i thought i'd reboot the tablet and see if that got rid of it.
Held power button in till i got the shutdown / re-boot options, chose re-boot.
Aaaannnd... now it's stuck in a boot loop. all it does it begin to start up... the Fusion5 logo comes up, then it goes "android is starting" 'optimizing apps, 1, 2, 3 of 3...'
Then black screen with android in middle, and that screen goes brighter and dimmer... then eventually it'll reset, and show the "android is starting, optimizing apps' thing over and over.... once it froze on the optimizing apps screen, the circle that goes round froze. but usually it's just loops... left it overnight and still doing it this monring.
If i shut it down by holding power for 10 seconds or so, and hold any volume button and power, it'll start the recovery thing... BUT all i get is the dead android and "No Command'
And no combinations of pressing the power and volume buttons will do anymore... even tried with a mouse and a keyboard... best i could get is a re-boot pressing CTRL - ALT - DELETE on the keyboard.
There seems no way to get this thing to show the recovery options... when i did this on the lenovo tab, it went straight to the 'select option with volume buttons' thing i'm expecting.
Obviousely there's no wany to get this tablet into USB debugging mode, trying the thing where you hold volume button, plug usb cable in, press power 10 times, it sometimes shows up as a usb media devise, sometimes a NDIS internet sharing devise. but they go when it boot loops.
I even tried de-soldering the battery and leaving it for 20 minutes, but upon re-soldering the battery onto the mainboard, it does the same boot loop thing.
I've read i could use Phoenix card writer to make an SD card with the firmware on it, and start the tablet up with that sd card in the slot and it'll load from it.... but where do i find the firmware? the allwinner site doesnt seem to have a firmware... that i can find for the A83T processors.
This is all i know about this devise:
Allwinner
Fusion5_108
1.0
002001014108aa62de01
A83t processor (confirmed by looking inside it)
not mine.. but same model:
ro.product.firmware=v6.0rc4_20161114
ro.fota.version=Fusion5_108_16_OS60_UK_20170310_V2F
ro.inet.model.name=N1061L14BC
Any suggestions?
Got it fixed,
Been emailing the fusion5 people, started that via their store... just google fusion5 store.
And they spend a while figuring out which tablet i have, sent an .img file... first one was for the wrong devise..... never than the one i have... but the 2nd try they got me the right firmware,
Loaded it to a micro SD card using phoenic card, popped the sd card in the tablet, started it up and it loaded the firmware, took the sd card out, and it rebooted and started up fine,
Only thing is it's android 5, and the tablet used to be running android 6... so now i'm looking at how to upgrade to marshmallow, as there are some apps i used that wont run on older than android 6.
Rom needed
Hi mate, do you mind sharing the ROM for the fusion5 108 ?
Thanks
re: Fusion5 Rom
Hi there. I know this thread is a couple of years old, but I haven't been able to find the ROM for this tablet anywhere else, so I wanted to see if you (or anyone reading this) wouldn't mind sharing it. Thanks!
Buying copy of img file
Gazz said:
Got it fixed,
Been emailing the fusion5 people, started that via their store... just google fusion5 store.
And they spend a while figuring out which tablet i have, sent an .img file... first one was for the wrong devise..... never than the one i have... but the 2nd try they got me the right firmware,
Loaded it to a micro SD card using phoenic card, popped the sd card in the tablet, started it up and it loaded the firmware, took the sd card out, and it rebooted and started up fine,
Only thing is it's android 5, and the tablet used to be running android 6... so now i'm looking at how to upgrade to marshmallow, as there are some apps i used that wont run on older than android 6.
Click to expand...
Click to collapse
Hi any chance of buying a copy of the img file. My tablet has just gone to 'No Command' screen and I cannot get it to load.
Thanks.
Andy
---------- Post added at 06:23 PM ---------- Previous post was at 06:18 PM ----------
AndrewRobert said:
Hi any chance of buying a copy of the img file. My tablet has just gone to 'No Command' screen and I cannot get it to load.
Thanks.
Andy
Click to expand...
Click to collapse
The company say the tablet is obsolete and it will not support it any longer
Andy