Related
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
Can you still boot into your main ROM or not? IF so, just reinstall recovery - Clockwork Mod 0.8 works, I don't know about later versions or ROM Manager, I don't trust them, based on what I see on the forums.
If you can't boot into recovery OR boot normally, then you have to use APX mode and nvflash to reflash your G Tablet. That completely wipes and rewrites everything on the tablet.
EDIT: If indeed it sounds like clockwork isn't installed and stock recovery is still working, see the instructions in the next post to install clockwork mod 0.8. No need to resort to nvflash.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
mr.frankm said:
So, here's a little back story for my frustration.
I asked for the G-tablet for X-mas because of the hardware, and I didn't actually receive the present until just a few hours ago. My PC is refusing to boot Linux at all, so i'm stuck on Win 7, my Samsung Intercept is refusing to root, so no custom rom there... and now I think I broke my G-Tablet.
(I rooted/flashed a ROM on the Vibrant, G1 and mt3g[several times] before this)
I was looking for how to install the custom ROM for the last few days anticipating today, I read Android Police's Guide (it won't let me post the link) several times before actually having the tablet, and I thought I had it down. After installing CW Recovery, I tried booting into recovery mode, which didn't work. It got up to the caution symbol and rebooted. So i figured it could be a boot problem.
I installed ROM Manager because of the useful "boot to recovery" button, but that lead me to the same problem. I looked at all the supported devices on the website and it was listed, but when I tried to flash the ROM inside of ROM Manager, it asked me to confirm if it was a Vega. I was a bit confused with what to do and decided to click accept anyways.
It said it was booting into recovery to complete the process but didn't, so in about a minute, I decided to shut down and boot into recovery myself, and it didn't help. It just cycles though the first two splash screens.
I don't know what to do. =(
Can I somehow hard reset it or something to start over?
Click to expand...
Click to collapse
You could become a professional gadget breaker with all the broken stuff you have
Clockwork never got installed if you are seeing the ! and then it reboots. I would not fool with rom manager, or any of the other stuff. Your tablet is NOT a Vega. The vega rom is used as a base to build stuff for the G tablet but it is not the same.
Get clockwork installed. You need to find Clockwork.8 ... You will have an update.zip file, and a recovery folder with a command file inside it. You can install it from the internal sdcard, or an external. You just need to look at the command file with a text editor like notepad and see if it lists sdcard, or sdcard2. If you want to install from internal, sdcard.. From external, sdcard2. The command file does not have an extension. If you do not have one in your clockwork package then download one of the other roms. Most of them will have it. Or even the stock rom package. They are all the same.
Go to SDX and we'll help you with the Intercept. Follow the info hear and the G will be rockin.
webosb said:
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.)
The file needed is cwmod_v08.zip at http://forum.xda-developers.com/attachment.php?attachmentid=458883&d=1291787239
Step 2.
Unzip the downloaded file to your microSD card. After unzipping, your microSD card should contain a folder called recovery, and a file named update.zip. (This cannot be done using the internal memory with this download.)
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch it install. Your tablet will reboot when installation is complete. And you can access the bootloader by booting the device holding the power and volume+ buttons.
Click to expand...
Click to collapse
I'm pretty sure I wrote that... I don't care that your reposting it...just link where you got it from next time.
Anywho, keep in mind that it's nearly impossible to completely brick these things. Follow this guide, step by step, from start to finish. You will need a microSD card with a way to get files onto it (microSD slot on computer/SD slot with microSD -> SD adapter)
http://forum.xda-developers.com/showthread.php?t=865245
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
mr.frankm said:
But that's the problem, I can't boot. This is the only thing I've actually broke. =/
I press Vol + and Power, I get the "detect a recovery key pressed", the android screen comes up, and the I get the Yield Sign for about 2 seconds before the boot cycle resets.
I can't get into anything. at all. I thought I was following a propper set of instuctions I'll be glad to follow @scsione889's guide here on XDA, but atm, i can't.
Click to expand...
Click to collapse
If you really have managed to mess up recovery.. You can use Nvflash to get all the way back to stock. Just use caution.. The only 2 tablets I know of that may have actually been completely bricked have been from folks that ran the incorrect batch file in Nvflash... It is really simple to use though... Guide is here...
http://forum.xda-developers.com/showthread.php?t=861950&highlight=nvflash
scsione889 said:
That yield sign is part of the stock recovery, you should still be able to install clockworkmod from microSD. Try it.
Click to expand...
Click to collapse
Yeah, I got it to recognize it, I didn't take recovery and update.zip out of the cwrecovery folder so it didn't work before. I just got it to "unpackage" for a second. but the same boot cycle happened.
I have to run out now for a bit, I'll try the flash later. Thanks for the help so far.
As mentioned before you need a microSD to put the CM recovery on. It also needs to be the .8version of clockwork. AndroidPolice is alright but you really should stick to the xda forums for this kinda thing. It only took me 5 mins to flash clockwork and get the VEGAn build up and running. I wish you the best of luck with your tab. It really is a nifty device....once you're running a custom ROM lol.
Edit: you can hard reset...unfortunately viewsonic failed to make a hole in the case to be able to reach it
Sent from my VEGAn G-Tab
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
Happy New Year! I hope!
Hello,
I flashed my GTab with TNT Lite a while back, but I was going to switch to Vegan. When I try to go into recovery mode, I get the message in the corner "Recovery Key Detected" but it won't go into CWM. I've got the update.zip and Recovery folder (with command file) in the root of my sdcard. I opened the command file to check the file path, and it's to the internal sdcard, not sdcard2. I even put those files on sdcard2 just in case, but still no go.
Any ideas? CWM 0.8 worked like a charm the first time around when I flashed to TNT Lite 4.2.1, but I just can't get into recovery anymore. I redownloaded it, and erased and put new versions of the update.zip and recovery folder on the sdcard (when the existing ones didn't work), just in case, but still no go.
I can still boot into my ROM, so I also tried "Reboot into recovery mode" from CWM inside the app, but it reboots to the Viewsonic splash screen and hangs there.
Any help would really be appreciated.
Hey, so I ran into the same problem as the first post (with the recycling boot screens). I flashed TNT-Lite onto it, and it worked for a few hours before the problem happened. I NVFlashed it, and at the very least I know the recovery screen is different than after I flashed it, but the yield sign only lasts a few seconds and then the problem persists.
Does NVFlash actually unroot? If so, can I return this to viewsonic and get a replacement? If not, am I screwed?
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
mr.frankm said:
Go figure, nvflash won't work because the APX driver won't install and the SDK won't install either because it doesn't recognize the JDK as installed although I installed it like 5 times.
I am a very disgruntled Ubuntu user stuck on Win 7 and I will not take it anymore.
I just finished backing up a few files and i'm blowing it up...
Happy New Years everybody, and I'll let you know what happens next year!
Click to expand...
Click to collapse
To NVFlash using windows 7 shouldn't be a problem I actually used it today and I'm running windows 7 home edition maybe you need to update your PC and try a linux live CD to run linux on a PC it has more drivers available for equipment and saves someone who doesn't understand linux alot of headache as it uses the CD as your hard disk and it sets it self up just make your system boot from the CD first.
Sent from my Bottle of Smoke using XDA Premium App
TimmSpinn said:
I got mine running again that same day. I also figured out that the reason Clockwork 0.8 wouldn't work anymore, was because I installed the market version in TNTLite.
But if you follow the NVFlash instructions, start to finish, it should get you back into the original stock ROM. And then from there, you can put Clockwork 0.8 back in place, and re-flash with whatever you want. With the G-tablet, it seems like you gotta go back to stock every time you wanna re-flash, or even upgrade from say TNTLite 4.2.x to 5.x, etc.
Here's the post I followed to NVFlash it properly:
http://forum.xda-developers.com/showthread.php?t=861950
Is that what you did? It should have brought you back to stock.
-Timm
HTC EVO 4g - Fresh EVO 3.5
Viewsonic G-tablet - Vegan 7-Ginger
Click to expand...
Click to collapse
Really it depends on your boot loader branch and its good practice to ensure that everything installs as the Rom develoer intends.
Sent from my Bottle of Smoke using XDA Premium App
While I was checking my emails i rediscovered this thread... lol
I'm a linux user, I got ubuntu 10.10 on my laptop running, again, months ago.
But now I don't touch it and use my tablet or phone 98% of the time. (this is 2% other on an XP desktop)
I also share the same recovery mode issues, but after reading the rest of this topic, I think I might feel adventurous enough to try that honeycomb... >.>
stuck cant get into cwm and is stuck on the tapntap logo
after i nvflash the tablet it wont boot. it gets stuck on the tapntap logo after a few seconds it turns the screen black. and even cant get into cwn it just get stuck on the view sonic logo. i need help
Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Tech1381 said:
Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Click to expand...
Click to collapse
Most definitely not bricked. I've recovered from a much worse situation (bootloader wouldn't even budge - couldn't boot into recovery or regular at all).
Since you are able to boot into recovery, there's probably a way to get things working without resorting to nvflash (we'll get to that in a second - nvflash is the failsafe mechanism, and you should be able to re-nvflash your tablet back to its original state if all else fails).
Here's roughly what I'd try in order:
Option 1) Figure out why you are unable to mount as USB in recovery. I've actually never heard of this problem. Are you using the right cable - i.e. a working USB-to-mini-USB cable (I don't think this works at all with the full sized USB port under the latch cover). Have you tried it with another computer - perhaps there's a driver issue on your PC?
Option 2) If for some reason you really aren't able to get USB mounting working in recovery (I'm skeptical - again, I've never heard of that problem - unless you really did flash a bum recovery image or something - but seems unlikely), then I'd see if you can get ADB working properly when you are in recovery mode. Search around and read about setting up ADB if you haven't already - just a matter of getting the right driver installed on your PC and installing the binary stuff (either from the full Android SDK or one of the packages that just has the ADB stuff floating around). Search the forums, you'll find some references to help you get this working and download the right stuff.
If ADB works, you can always use "adb push filetoflash.zip /sdcard/filetoflash.zip" to put a new file on your internal SD card area and flash it.
Option 3) You can always use nvflash. I'm not going to write up a tutorial on it here - search the forums for nvflash, there are several HOWTOs. Look for the stuff Roebeet posted. You'll need to install the APX driver on your PC first before this will work, and Roebeet's posts don't explain how to install it on Windows, so you'll need to search separately for that. I have gotten this to work before, but it's a pain and I only recommend it if your recovery image is truly trashed or your bootloader is malfunctioning as mine was. In other words, don't bother until you've exhausted the first two options.
So in short - you are in a pain-in-the-ass situation, but you have by no means bricked your tablet - it is very, very far from bricked. Give us more info on *exactly* what happens when you try to "mount as USB" while you have your mini USB cable plugged into the G Tablet - do you see a drive appear on your PC? Are you running a Windows box? Mac? Linux? Have you verified that a USB keychain drive works fine with your PC but the G Tablet won't mount? Basically we need some more info to guide you in your search.
Ok finally had some free time from cleaning/packing and house hunting to try fixing the tablet.
Good news is that I was able to mount the USB. I didn't notice the cat nibble on my cable... So once I dug a spare out, I was able to copy a TnT-Lite image (still had on computer) onto it right quick. Restarted and it installed the image.
So now it has TnT-Lite, though it is weirdly stuck on the setup wizard. It tells me to touch the android to continue and shows an animation of a hand touching the android. But when I touch the android, it turns white and thats it. Also I can change the language to UK or American English. Plus when I press the menu button, I can go to wireless settings, as in cell phone wireless settings. Lastly, I can make an emergency call. So new worthless image. YEY!
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
So how do I go about screwing it up more?
Tech1381 said:
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
)
Click to expand...
Click to collapse
CWM is not installed
flash the latest firmware using stock recovery
read read read
http://forum.xda-developers.com/showthread.php?t=892090
It almost sounds like you now have stock recovery in your Gtab.
If that's the case, then maybe copy a stock TNT update.zip onto the external Sdcard, and create recovery/command file on there with the string for SDCARD2, then reboot w power and volume+. If you do have stock recovery, that should flash it back to stick TNT. Try Stock TNT 3452, since that'll also flash a stock recovery for sure.
Jim
Looks like Brian and I crossposted each other .
For the recovery/command file on the external SDCARD, put the following text in it:
--update_package=SDCARD2:/update.zip
NOTE THE 2 DASHES AT BEGINNING OF THE LINE...
Jim
No really, I've Bricked It
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
f3justusc said:
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
Click to expand...
Click to collapse
I'm freaking out, I think I bricked it...
I'm only getting the black android screen, I can't seem to mount USB, suggestions?
Ive been stuck right where you are a few times, not to big of a deal, just NVFlash back and start over. I am assuming you are getting the black screen you mention is the APX mode one you get by starting your tab by pressing vol down and power at the same time.
Hi all,
Ok, so I have a weird problem with my Asus TF101 that for the life of me I can't seem to solve myself. Which is why I finally decided to ask for help.
To make a long story short: About two years ago I bought a used TF101 that I have been very happy with so far. And I definitely don't want to give it up, as it's been working fine until a few weeks ago. Then those boot loops (that everybody seems to be talking about) started and I was able to revive the device once by leaving it plugged off for a few days until the battery was empty (thus, I think, forcing a clearing of some kind of cache) and then re-booting it. Unfortunately, this does not seem to work anymore.
My TF101 has been rooted by the guy that owned it before. It features TWRP in version 2.2.1.4 and an older KatKiss ROM. Now, my situation is as follows:
Boot loops are preventing me from getting past the boot screen. I can thus not install or use any apps.
I can enter TWRP recovery mode and I could wipe the device, but I cannot find any ROM on the internal memory.
When connecting the TF101 to the computer (I'm using Linux Mint 17.3) it doesn't show up as disk. Only when unplugging it again, an error shows up on the Linux screen saying that the TF101 could not be connected. This is preventing me from loading a new ROM onto the device via a cable.
The device doesn't seem to recognize an SD card (32GB), no matter if formatted as FAT32 or as EXT3, with or without SWAP. So, in the TWRP file manager I cannot access an external SD card to load and flash a ROM.
When I enter "Mount" in the TWRP menu, I can't seem to switch to "Using external SD": When doing that I get an error "E:failed to mount /sdc (No such file or directory)" in the terminal window.
I have been reading forums up and down, but can't seem to find any helpful advice that applies in my case. I'm guessing the boot loop would disappear, if I could flash a new ROM, but I don't know how to put that on the device. Also, in case some of the problems are caused by version of TWRP that is installed, I would like to update that... but, again, I don't know how to get the new version on the device. I thought about entering APX mode, but holding Power and Vol+ simply turns my display black after a few seconds... no sounds, no beeps, nothing showing up on my desktop.
Any ideas? Pretty please?
Any help would be much appreciated.
Thanks in advance.
I'm not a n00b, I've rooted every Android device I've ever had, and I have my OnePlus Two running the latest CM14.1 nightlies. But I can not figure out what to do for this poor tablet.
I had downloaded and installed an OTA from Lenovo, but it must have been corrupt because the tablet got stuck in a boot loop. I can boot into recovery, so I tried formatting it and clearing all the caches, then it goes to a screen with a loading bar, which fills completely and just sits there. I've left the thing on all night. Nothing.
Sending it to Lenovo is a no-go because I voided the warranty when I rooted it.
I've also tried reinstalling the stock firmware, but the Intel phone flash tool either get's blocked by Windows 10 (with no way to whitelist it) or fails to flash properly.
crandroid99 said:
I'm not a n00b, I've rooted every Android device I've ever had, and I have my OnePlus Two running the latest CM14.1 nightlies. But I can not figure out what to do for this poor tablet.
I had downloaded and installed an OTA from Lenovo, but it must have been corrupt because the tablet got stuck in a boot loop. I can boot into recovery, so I tried formatting it and clearing all the caches, then it goes to a screen with a loading bar, which fills completely and just sits there. I've left the thing on all night. Nothing.
Sending it to Lenovo is a no-go because I voided the warranty when I rooted it.
I've also tried reinstalling the stock firmware, but the Intel phone flash tool either get's blocked by Windows 10 (with no way to whitelist it) or fails to flash properly.
Click to expand...
Click to collapse
What I've tried:
Just plain booting it - screen turns on and doesn't do anything, just black
Rebooting through recovery (power + vol_up) - plays boot animation, goes to a screen with a loading bar like it does after an update, but once the bar fills, a white line appears at the top of the screen and nothing happens
Downloading the official KitKat firmware (http://forum.xda-developers.com/android/help/lenovo-tab-s8-50f-stock-firmware-rom-t2989791), unarchiving the rar file and rearchiving it into a .zip, putting it on a MicroSD card, putting the card in the tablet, flashing through recovery - can't find the .zip, says SD card is blank
Clearing caches and wiping data - same as when rebooting through recovery
Using the Intel phone flash tool through bootloader (power + vol_down) - tool can't find device
Using the same tool through fastboot (power + vol_up + vol_down) - gets to the sleep 4000 ms step, reboots the device, then the device goes to the same loading screen and the flash tool can't contact it. I think it's trying to boot into the OS to finish the flash, but that's the problem to begin with
I've tried loading the temporary CWM session but that fails
I can't for the life of me figure out what the @bailka011 Unlock Tool is supposed to do or how to use it, plus the download link isn't working.
Can someone please guide my through this? I'm so confused
crandroid99 said:
What I've tried:
Just plain booting it - screen turns on and doesn't do anything, just black
Rebooting through recovery (power + vol_up) - plays boot animation, goes to a screen with a loading bar like it does after an update, but once the bar fills, a white line appears at the top of the screen and nothing happens
Downloading the official KitKat firmware (http://forum.xda-developers.com/android/help/lenovo-tab-s8-50f-stock-firmware-rom-t2989791), unarchiving the rar file and rearchiving it into a .zip, putting it on a MicroSD card, putting the card in the tablet, flashing through recovery - can't find the .zip, says SD card is blank
Clearing caches and wiping data - same as when rebooting through recovery
Using the Intel phone flash tool through bootloader (power + vol_down) - tool can't find device
Using the same tool through fastboot (power + vol_up + vol_down) - gets to the sleep 4000 ms step, reboots the device, then the device goes to the same loading screen and the flash tool can't contact it. I think it's trying to boot into the OS to finish the flash, but that's the problem to begin with
I've tried loading the temporary CWM session but that fails
I can't for the life of me figure out what the @bailka011 Unlock Tool is supposed to do or how to use it, plus the download link isn't working.
Can someone please guide my through this? I'm so confused
Click to expand...
Click to collapse
what did it says the update would do? android 6.0? latest update for this tablet was released 7 months ago... the unlock tool u mentioned unlocks the bootloader, and try to find a win7 pc to do the flashing. some users on a different forum stated that windows 10 will cause problems during flashing
good luck
xaocot said:
what did it says the update would do? android 6.0? latest update for this tablet was released 7 months ago... the unlock tool u mentioned unlocks the bootloader, and try to find a win7 pc to do the flashing. some users on a different forum stated that windows 10 will cause problems during flashing
good luck
Click to expand...
Click to collapse
This update was seven months ago. It did not claim to bring 6.0, just minor fixes.
Thank you for clearing that up, now I just have to figure out how to download and use it xD.
Also I have figured out how to enable the hidden administrator account in Win10 and use that to get around the security warning, still tries to boot partway through flashing. Unless there's some other part of Win10 that's disagreeing with it.
Sent from my ONE A2005 using Tapatalk
the same problem with me!
crandroid99 said:
What I've tried:
Just plain booting it - screen turns on and doesn't do anything, just black
Rebooting through recovery (power + vol_up) - plays boot animation, goes to a screen with a loading bar like it does after an update, but once the bar fills, a white line appears at the top of the screen and nothing happens
Downloading the official KitKat firmware (http://forum.xda-developers.com/android/help/lenovo-tab-s8-50f-stock-firmware-rom-t2989791), unarchiving the rar file and rearchiving it into a .zip, putting it on a MicroSD card, putting the card in the tablet, flashing through recovery - can't find the .zip, says SD card is blank
Clearing caches and wiping data - same as when rebooting through recovery
Using the Intel phone flash tool through bootloader (power + vol_down) - tool can't find device
Using the same tool through fastboot (power + vol_up + vol_down) - gets to the sleep 4000 ms step, reboots the device, then the device goes to the same loading screen and the flash tool can't contact it. I think it's trying to boot into the OS to finish the flash, but that's the problem to begin with
I've tried loading the temporary CWM session but that fails
I can't for the life of me figure out what the @bailka011 Unlock Tool is supposed to do or how to use it, plus the download link isn't working.
plz someone too guide me ,the same problem is happening but there is no appearance of a loading screen,when i switch on the tab ,it showws the lenova logo and goes to a black screen thats keeps on flahsing!! i dont knwo what to do ,when i connect to pc and try to flash it doesnt work,i dont what to do plz help me!!
Click to expand...
Click to collapse
I have a big problem with my AGM A8.
The original ROM started displaying advertisements and malfunctioning so I wanted to change it.
I downloaded TWRP 3.1.0 AND- If I press the power button, or the screen will go sleep, it can not be woken up - the phone and touch works, the screen is black. When using TWRP 3.1.0 I install lineage-14.1 or RR v5.8.3, they work very well, but also - if phone will go sleep or I press the power button - I have to pull the battery out to reset and start.
I installed TWRP 3.2.3. It works very well, there are no problems with the black screen, but it do not want to install any rom (allways error 7).
I was scared, so I tried to install the original rom using an SD card (T88Q_14.bin file) and 3 buttons, but the phone does not detect it (on few different sd cards).
Please help me... I have a brick instead of a smartphone :/
I have a similar problem... As far as the SD card 3 button boot... Deep format the card before use... That worked for me.
The problem I have is:
The (T88Q_14.bin) file I have is probably for a different version and will not restore my phone correctly.
I've lost fastboot mode and recovery.
Now the phone boots with the screen scrambled with only colored lines.
It seems to boot in Android but OEM locked so I can't do anything with ADB.
I can't unlock it because I can't see anything but colors on the screen... The touch screen does not seem to work.
My AGM A8 is 4gb ram 64 rom. (The newest version)
If anyone have the T88Q_14.bin for that phone... please share
Same problem, I found this one and I am back in!!
search for LA6622(Q14)_HW1.R1.V09.A8_MultiDownload_20180411user
found link at 4pda russian, google translate.
Xda won't let me post the link.
Still have bars in the background but at least it is workingP
Sent from Mail for Windows 10
hello friends,
i did also struggle with preparing the reboot sd card for AGM A9.
in the end, my following actions were successful:
i've just formatted the tf card in android,
downloaded the zip file for my phone model
to the root directory of the tf card,
powered off the phone,
and booted by symultaneous press of [on] and [vol-dn].
i don't know whether this wipes the cache,
so if you want to make sure, reboot with [on] and [vol-dn] without the tf,
select with vol-up/dn the wipe cache option, and do it by [on/off],
and then select reboot the same way.
good luck