I got clockworkmod working fine, but I am unable to loan ROMs. Whenever I downloand a ROM it opens in muiltiple files and it also happens with TNT, Thi is where Im stuck
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped, Clockwork will install it from the .zip file as is). trying to get VEGan 5.1 final
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
I cant fiqure how to get the update.zip. When I do open the files i get 3 files
META_INF,boot, and system. I tried to copy and paste all three files in the ROMs, but it never show the update.zip
You don't need an update.zip with clockworkmod recovery... you just need the rom that is zipped and can be named anything.
Stop unzipping the rom you are downloading and just copy it to your device. Install that with clockworkmod recovery.
Sent from my Viewsonic 10" GTab...
novicexda said:
I got clockworkmod working fine, but I am unable to loan ROMs. Whenever I downloand a ROM it opens in muiltiple files and it also happens with TNT, Thi is where Im stuck
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped]/B], Clockwork will install it from the .zip file as is). trying to get VEGan 5.1 final
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
I cant fiqure how to get the update.zip. When I do open the files i get 3 files
META_INF,boot, and system. I tried to copy and paste all three files in the ROMs, but it never show the update.zip
Click to expand...
Click to collapse
you've answered your own question, the rar or zip file you downloaded might be in diff names, but always leave it in zip format. if in rar, unrar and the zip file should be in it.
in clockwork recovery, you can update by update.zip or choose your own zip
tcrews said:
You don't need an update.zip with clockworkmod recovery... you just need the rom that is zipped and can be named anything.
Stop unzipping the rom you are downloading and just copy it to your device. Install that with clockworkmod recovery.
Sent from my Viewsonic 10" GTab...
Click to expand...
Click to collapse
That is my problem, if automaticly unzips when it downloads. I am not sure if its my windows setting becaue I am unable to download TNT lite because I keep getting " windows can no opem" message. Is there a way i can prevent it from unzipping? Thanks BTW
maybe use a diff browser to download or right click on link and "save as"
You might be hitting open instead of save ...
down load it direct to your Gtab
Download the file directly to your tab. Use ES file explorer to move it to your SD card if necessary. Reboot in to clock work - choose file from SD card-select it and install.
I have Vista Home Premium 64bit and I did download WinRAR 64 bit edition. Whenever I try to install that there claims to be a corrupt file and I have downloaded it a few times from a few sites.
So I go back to the 32 bit version of WinRAR and that installs fine, but reminds me for better performance to use the 64 bit version.
Now, whenever I extract a ZIP or RAR file the Update.exe is missing or I receive a message about the CRC security not matching. AND if and only if I can get the files extracted when I try to install the ROM the Gtab is constantly stating a "status 7" error. I have tried TNT, VEGAn and 1 other ROM and each will not install.
Is there anyone who would be willing to use Skype or some other means to assist me in getting the tablet back up and running something, even if that's the stock ROM?
I do have Clockwork Mod installed already, that was the only thing that seems to have installed correctly.
Thank you in advance,
Brian
If I undertsand correctly: Youre trying to extract the contents of the "update.zip" file that comes as part of the ROM download?
If so.. you dont extract it, you leave it as "update.zip" in your sdcard directory.
I remember seeing a "pictoral" view of what your filesystem should look like in this xda somewhere. Ill try to find it.
No, I am having problem extracting the ROMs from Zip or Rar, so I went and downloaded Memtest86 just to see if there was a RAM problem. That checked out fine after an hour of testing.
Most every Zip or Rar I try to extract have CRC errors, even if it's unrelated to this site. But part of that causes the Update.zip not to extract at all and I only get the "recovery" folder and Command and the Update.zip had an error and doesn't extract.
I then tried it on a laptop with Win7 and I could extract some files then more errors, then I tried a Win XP laptop and that seemed to extract the files fine.
My latest is now the Gtab is bricked, stuck trying to install recovery that never ends. So I looked up for the USB driver and nvflash and the ROM that goes with that and the Gtab doesn't show up as a removable drive so I can transfer the files on there. I have copied them to SDcard but I can't get that to read the data.
So, at this point the Gtab is looping and I cannot get back into Clockwork or get it to show as a drive using the USB drivers and the -Vol and Power button.
Currently when I just power on the tablet in red text I get:
Magic value mismatch:
:"
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
FIXED
PROBLEM FIXED.
I saw another thread stating similar problem, located here http://forum.xda-developers.com/showthread.php?t=1026757 and followed the advice of a few people and now the Gtab is working again. Its stock ROM but the main thing is it's working again.
I ordered my g tablet yesterday and cant wait for it to come in. So tonight I am downloading a rom and clockworkmod v8 so I will be ready when it comes in. However I need a little help. I read the guide on installing clockworkmod and a rom but cant firgure something out. It says to un zip the files into the root of the device. When it means un-zip does it mean to "right click" than "extract all" Because when I do this the recovery folder doesn't have the zipper on it anymore but the update folder still does. Is this right?
The recovery folder and the zip file called update is what you will need to transfer to the root of your SD card when you connect your tablet to the PC. The recovery folder should not be in a zip format, but the update file should be.
ok thanks. But both folders go in the root right?
Yes. Then boot into recovery and it will start the update after so many seconds.
the update folder just says "update" it doesn't say update.zip however it is a zipped folder. Is it the same thing?
Most operating systems, referring to Mcrosoft, hides the extensions of files, but if it has the look of a zip file or what ever software you may be using, I would assume that would be the update file just not showing the .zip extension.
You are making it hard. Just do this.
Hook up Gtablet to your pc by USB. See which drive your pc asigns to your GTablet. Download the correct Clockwork Mod you need.
Unzip it to a folder on your pc. Then just drag and drop the two files after zipping to the drive your pc assigned to your Gtablet. On mine it is G. Yours may be F.
Then just power down your GTablet and then power up holding down power and volume + till you get Viewsonic screen and a message in upper left corner that recovery has started.
Then go here: http://forum.xda-developers.com/showthread.php?t=865245
If ClockworkMod installed, start with Part 1, step 6 or 7. READ IT ALL.
I posted this on the fool proof thread for going from 3588 to 4349. Having troubles and looking for help.
NVFlash confuses me.
I basically just want to install a good 1.2 based ROM and stick with it. Have no intention of going back top 3588.
How do i make it so that if i ever do brick the device or have a need to go back, it just starts as if 4349 is my starting point?
My problems using the foolproof method is that the external SD card i purchased an loaded the necessary files to was not recognized when i followed the choose sdcard/update from sdcard instruction. I am thinking it might be looking for internal SD card as i definitely put the files on it and partioned per intructions...
Anyway, did work or i messed up somehow - looking for alternatives.
Thanks
Okay...I located the file from one of Robeet's threads.
New/additional question to any who view and have know-how/skills:
In his thread he mentions to flash to 4349 DO NOT use CWM. Well, that was teh first thing i did - install CWM.
How do i go about uninstalling?
I also noticed mybe some of my earlier troubles were in that my command file was created in notepad (he warns against file extensions).
Hendge said:
Okay...I located the file from one of Robeet's threads.
New/additional question to any who view and have know-how/skills:
In his thread he mentions to flash to 4349 DO NOT use CWM. Well, that was teh first thing i did - install CWM.
How do i go about uninstalling?
I also noticed mybe some of my earlier troubles were in that my command file was created in notepad (he warns against file extensions).
Click to expand...
Click to collapse
You can still use CWM to flash the stock firmware from teh source he provides. Let me guess, his file is a rar file, when unzipped, you are left with a file called "update.zip" and a folder called "recovery" with a command file in it.
What this is, is the format used to flash something using stock recovery. If you do not have CWM, you'd turn on your tablet, holding +, and it will "see" the recovery file, which will let it know to run the update.zip file.
Since you HAVE CWM, all you need to do is "install zip from SD" and install the update.zip file, just like you would any other rom.
to keep it organized, I suggest you rename it 4349.zip, or stockfirmware.zip, etc.
but yeah, it's completely possible to do it through CWM
as for the "command" file, yes, if it's created in notepad on a windows machine, it will be command.txt. you can't have the .txt part. I use notepad++ to creat files without extensions. You can also do it on the tablet using ES file explorer, root explorer, etc...
Thanks so much for replying!!
Let me ask you or anyone else who knows - When you write "install zip from SD" are you referring to the external or internal?
One more possibly one of the silliest questions that can be asked: How do you move files from one drive to another on this device? I was toying around last night with teh file explorer program and honestlt could not figure it out. I do not use a mouse or anything - normally i would cut/copy and paste teh file to desired location.
Please Help. Thanks again!
SD is generally the internal, MICROSD or SDCARD2 is the external.
Re: The windows notepad. If you want to save a file without the .txt extension or to change the extension simply Save As and put quotes around the name.
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
the best way using complete firmware (containing stock rom) like this version UL-K017-WW-11.2.3.18.2-user, if succeed then later on you can continue with OTA system update
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
So awesome you figured this out! Glad it worked out for you and I'll be saving this in case I find myself in the same boat. Thank you for this!!
Sent from my Nexus 6
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
2. Extract (archive in archive) and throws to the SD card. Rename the file to K017_sdupdate.zip and Insert the flash drive into a tablet. (Use good one SD card)
Click to expand...
Click to collapse
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
WeAreNotAlone said:
K01A, aka ASUS MeMO Pad ME170CX
Prod date 2014-10 IIRC.
I appreciate you taking time to create this thread, have been unable to flash stock firmware to the ME170CX using just the ME170CX itself. ASUS website just mentions a SOP method and when I insert SD that has had the firmware files which have been extracted (1) time to the SD card, the prompt that is supposed to "pop-up" on the taskbar as mentioned in the PDF's I found online about the SOP method does NOT occur.
(I have 2 ME170CX's about 30-days old running 4.4.2, firmware Version WW_V11.2.3.27 in which one of them all the sudden the camera app crashes 100% of the time, then gives a "No camera is found" error message.
Beyond a hardware issue no-one knows what causes this beyond (1) poster that mentioned he thought problem first occurred after hitting the "Home" button right after hitting the cam icon and the thought is the app gets confused by this and the app/firmware for the camera gets corrupted.
Reset via OS itself. Wiping data and choosing "Recovery" in DROIDBOOT with "FASTBOOT" text at bottom of screen didn't make any difference. Camera is dead, dead, dead.
Figured I'd re-flash with same Version WW_V11.2.3.27, if that doesn't work try Version WW_V11.2.3.28 before RMA'ing it back to ASUS so I appreciate you listing the steps, and also attaching the needed files.)
***************
Question about Step 2, Please clarify:
To clarify you are saying to extract the firmware from the "zip" package of zip that matches the firmware specific to the device from ASUS, which itself contains a zip file named IFWI.ZIP (1 ), one time, then rename the file named IFWI.ZIP (which contains 4 Bin files) to K017_sdupdate.zip.
Upon extraction process completing and renaming the zip you then copy the contents over to a known good MiroSD of at least 2GB which is formatted FAT32 to the ROOT of the drive.
IE: You do not extract the zip within the archive, you're just renaming IFWI.ZIP to K017_sdupdate.zip?
OR are you saying to extract the BINS also?
If so do these go in the ROOT of the SD card?
Another question, is there a reason for renaming IFWI.zip to K017_sdupdate.zip?
.
Click to expand...
Click to collapse
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
sevensvr said:
some firmware when you download it from asus site ZIP compresed twice, you can rename it directly from WW_V11.2.3.28.zip to K017_sdupdate.zip, if your device is K01A try to renaming firmware to K01A_sdupdate.zip and then put in SD card (do not created any folder in SD card ). the key to success is the SD card compatibility with ASUS DROIDBOOT, I was using Sandisk SD card. I did format fat32 the SD card and insert in another android devices first and then put the renamed firmware file there.
inside firmware file there is boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder and then flashing it your tablet. this trick to make firmware recognize correct devices to be update.
try again.
Click to expand...
Click to collapse
RE: boot.img, fastboot.img and splashscreen.img you need to extract it in flashtool/fasboot folder ???????
Having some progress, renaming ifwi.zip which contains (4) bin files when Recovery was selected caused the robot with the Updating System Settings to appear, but a couple of seconds later it said ERROR with the robot laying on it's back, then it exits. Device reboots as normal.
To clarify:
WW_V11.2.3.28.zip download from ASUS was extracted with a Windows computer,
WW_V11.2.3.28.zip extracting /creating following folders, files, then the contents were copied to the ROOT of a MicroSD card formated Fat32
1: boot.img, fastboot.img and splashscreen.img (TO ROOT)
2: ifwi.zip to ROOT. (contains (4) bin files, is this supposed to be extracted to I assume folder by same name off root? OR does this ZIP file just get renamed?)
3: System folder
4: Recovery folder
5: META-INF folder
I do not see a flashtool/fasboot folder. (Fastboot, right?)
Q: Is boot.img, fastboot.img and splashscreen.img supposed to be in a folder named "Flashtool" OR are they supposed to be in folder named "Fastboot" with a pathway of Root (Drive) D:/Flashtool/fastboot ?
.
(NOTE ALL OF THIS IS BEING DONE ON THE DEVICE ITSELF, with contents on SD card.)
Still getting the ERROR! message wit the Adroid robot that is laying on his back.
The zip file that extracts from the main zip WW_V11.2.3.28.zip is named:
ifwi.zip...
I have left a copy of it in the ROOT, plus copied it and renamed it to
K01A_sdupdate.zip
K017_sdupdate.zip
LEAVING COPIES OF ALL IN THE ROOT OF THE SDCARD.
Q: If more than (1) zip is present does this confuse fastboot? OR does fastboot automatically look for zip zip which matches model ID of device? (K01A)
I have left copies of boot.img, fastboot.img and splashscreen.img in the ROOT of the drive.
AND
Created: (ROOT) flashtools/fastboot with *img files in it.
Created: (ROOT) fastboot with *img files in it.
Copied the *img files to under "Flashtools" folder in flashtools/fastboot.
Figuring all the bases would be covered. (EG: *img Files in ROOT, files in Flashtools, Flashtools/fastboot, and a folder named fastboot as well.
Q: I've noticed on the SD card files appearing that previously were not there, when the flash aborts is there some kind of file or files you need to delete, or is it ok to leave the newly generated files there?
---------- Post added at 03:43 AM ---------- Previous post was at 03:37 AM ----------
Deleted:
ifwi.zip.
K017_sdupdate.zip
Tried:
K01A_sdupdate.zip
Still getting robot on it's back with ERROR!
who said you need to renaming ifwi.zip, What you need is read all instruction carefully,
do not put more than 1 zip file in SD card only firmware file which is already renamed to K017_sdupdate.zip, and use good brand SD card.
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
commando987 said:
I successfully complete all step after "Installing system update" nothing change again stuck on asus logo.
Click to expand...
Click to collapse
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
My Asus MemoPad ME170C has risen again!
sevensvr said:
After 3 days tried to find out how to recovered or fix bootloop/brick ME170C, here is the way which was succeed for me.
1. Download latest firmware from ASUS website
2. Rename the firmware file to K017_sdupdate.zip and put on SD card then Insert the SD card into a tablet. (Use good one SD card, Sandisk perfect I don't know others)
3. Download flashtools and USB driver at the bottom of this thread
4. Enter the DROIDBOOT, for this purpose on the tablet off push and hold button volume + and power then connect USB cable to tablet and PC.
5. Open your firmware archive and copy or drag & drop the boot.img, fastboot.img, splashscreen.img into Flashtools folder ( in computer )
6. go to flashtools folder and then push button shift and right click together and choose “Open command windows here”, to start open CMD on the right folder (in computer)
7. Test your device by typing fastboot devices on that cmd (in computer)
8. Enter the queue codes on CMD; (in computer)
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash fastboot fastboot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
8. Disconnect the USB cable and select the SD update or Recovery.
9. Take your coffee and sit, walaaaaaaa I see you are smiling
I am curious , is it work for others ASUS tablet? do with your own risk, but btw with this step I did wake up a hard brick devices.
Tag [ Asus memopad fonepad zenfone ME170 brick, bootloop, stuck on asus logo, boot problem, solved brick, guide how to]
Click to expand...
Click to collapse
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
sevensvr said:
when installing update, the robot end with error or not?, the installing bar moved till finish ? the installing process will take 3 to 5 minutes.
if you did all above and still got stuck on asus logo, try to change the firmware with this version UL-K017-WW-11.2.3.18.2-user, if succeed then you can continue with OTA system update
Click to expand...
Click to collapse
Installing bar not complete at the end but not give error and restart. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
mapagmatyag said:
I bought my memopad 170c just a couple of days ago and because of excitement i flash the wrong firmware and it went dead i tried the recovery method but nothing happens i'm beginning to get nervous as this tablet is a gift for my daughter but thankfully i found this site especially to your instruction did every step with my finger crossed and like what you said sit back and walaaaaa! my tablet err my daughter's tablet has risen again. thank you for sharing your knowledge.
Click to expand...
Click to collapse
you welcome friend
commando987 said:
Installing bar not complete at the end but not give error and restart it. After restart stuck on asus logo. Now i download version UL-K017-WW-11.2.3.18.2 and check it.
Click to expand...
Click to collapse
it seems the tablet didn't read your SD card, to assure SD card problem when the robot appear while system update press buttom vol + and - rapidly to show installing status.
if the tablet didn't read ur SD card try to use another SD card
BIG Thanks
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
mnabarro said:
I've been stuck with the bricked 2 day old tablet for at least 3 months. Today I did the procedure you described and it worked. I had to install version V11.2.3.18.2 and then, once unbricked, apply latest version update.
Again, thanks a lot!.. Best regards.
Click to expand...
Click to collapse
happy to heard it
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
mashton70 said:
Hi, am trying to fix my ME170CX because an original root attempt that failed and am getting a demo error message that won't go away.
I tried following all your instructions to fix this but it gets stuck "waiting for device" once I begin entering the commands.
I have tried multiple sd cards (including a sandisk) and both the V11.2.3.27 & V11.2.3.28 firmware versions to no avail.
I also tried naming the zip file K017 & K01A.
I am also wondering why we need to download the USB driver file? I don't see anywhere in your instructions on what to do with this.
Any help would be greatly appreciated.
Mike
Click to expand...
Click to collapse
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
OK, I finally got the usb drivers working on my computer and made it through all commands which is much further than I was getting before.
I got to step 8 "Disconnect the USB cable and select the SD update or Recovery" and selected "Recovery" in DROIDBOOT (I don't have an "SD update" option there) and after like 1 second of "installing system updates" I get the android falling over guy error and then it hangs on the asus splash screen for ever.
download ME70CX for ME170CX
anthonyg45157 said:
Youll want to get your answer from him but i think i may be able to help. You need to install usb drivers so you can access abd and give commands to your tablet. Which i think is why it just says waiting for device... I could be wrong though....
Sent from my Nexus 6
Click to expand...
Click to collapse
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
ydobon.999 said:
have you been able to restore it ?
Can NOT use download of ME170C
Use download of ME70CX. Just did it, and tablet back to "almost" normal.
I have wifi button issue now. Button is stuck.
bye
Click to expand...
Click to collapse
That did it!
I used the firmware ME70CX and renamed the file "K01A_sdupdate.zip" and followed all of the other steps as per the original instructions and got my ME170CX working again but for one problem. . . I was still getting the "demo has stopped" error! So I proceeded to attempt root again, this time with RootZenFone-1.4.6r and and now it's working perfectly and rooted as well!
Many thanks to all!!