Related
something strange just happened
on my rooted nook tablet i can't access to google play store
it say "you must add an account to the device to continue. do u want to add an account now"
and when i click on YES it closes everything and goes back on the main screen
and also Gallery - Email - Talk have the same icons with the android logo
is this related to the fact that the software has been updated to the new version 1.4.3?
should i root it again?
thanks a lot
WhiterabbitITA said:
is this related to the fact that the software has been updated to the new version 1.4.3?
Click to expand...
Click to collapse
Yep. Reroot using the sdcard method and everything should go back to normal. A system update breaks root as it modifies the /system/apps/ directory which is where superuser/google play are stored when rooting.
helpppppp
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
I think I'm having this same problem.
WhiterabbitITA said:
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
Click to expand...
Click to collapse
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
RooterBooter said:
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
Click to expand...
Click to collapse
simple answer for avoising breaking root is to install a custom rom
Sent from my Nook Tablet CM7 BETA using xda premium app
RooterBooter said:
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
Click to expand...
Click to collapse
or install custom recovery (cwm) if you wish to continue to use stock
without stock recovery B&N can't send you updates
How do I tell if I'm using stock recovery or custom recovery?
tobdaryl said:
or install custom recovery (cwm) if you wish to continue to use stock
without stock recovery B&N can't send you updates
Click to expand...
Click to collapse
I used Albert Wertz's method for rooting using an sd card, and had no problems, except that I didn't go as far as to block the OTA updates. Is it possible to have a custom recovery and stock recovery on the same device? How do I tell, and how do I safely install cwm, without being able to use Titanium Backup (since my root is now broken)?
deleted because of multiple posts linked.
I have now booted into mac instead of ubuntu in an attempt to fix.
Looks as if I got caught in xda update!
It's still not correct but better now.
WhiterabbitITA said:
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
Click to expand...
Click to collapse
From main menu (first screen after cardboard box)
select - install zip from sdcard
next -
select - apply /sdcard/update.zip
next -
N down and select YES
---------- Post added 15th August 2012 at 12:16 AM ---------- Previous post was 14th August 2012 at 11:36 PM ----------
RooterBooter said:
I used Albert Wertz's method for rooting using an sd card, and had no problems, except that I didn't go as far as to block the OTA updates. Is it possible to have a custom recovery and stock recovery on the same device? How do I tell, and how do I safely install cwm, without being able to use Titanium Backup (since my root is now broken)?
Click to expand...
Click to collapse
No, there is one partition designated for recovery. You can run cwm from sdcard when you wish and keep stock recovery internal, but custom recovery is the only way I have seen that absolutely blocks otas (otas are blocked with custom rom also) if that is your concern. To tell about your recovery the only thing I can think of is the power and N key into recovery. If you read what is presented on the screen when it appears and refuse a reset you are safe, that takes care of stock, if you are nervous reread and take your time. For cwm if that is installed you will see a cardboard box flash and then a menu with the first item to reboot, that is also safe.
To get into either recovery (for looking) from power off press and hold power and N, after two seconds release power, after one or two more seconds release N also. That should do it.
If you wish to have absolutely what to click when you get stock recovery just wait a while and I'll come back and edit this post to reflect that info. At the moment have something else going on (NT) I can't stop.
Stock recovery shows Factory reset
do you want to reset your device to the factory default?
Press POWER key to exit
Press Home key to continue
press power and you are out and safe
Installing CWM recovery! There are now two apps(they require root) here on xda for that purpose, one is 16gig only (Nook Tab Recovery Flasher) by indirect the other is 8gig and I don't know who did it.
There are also flash zips for each and a flash zip that is both 8gig and 16gig. If you are 8gig make sure you choose one for 8gig
CWM sdcard with a flash zip does not require root.
Greetings All,
I am attempting to update my TF201 to Jelly Bean but am not having any luck. The OTA update failed initially, and now when I search for updates, the tablet says there are none. I then decided to get the update file manually, but I can't get my tablet to discover that the update is present and ready to be installed. Can't figure out what I am doing wrong. Everything I have read thus far says to download the update, extract the zip file (resulting in another zip file with a slightly different name - I am on the WW version of the tablet BTW) to the root of the tablets internal storage, and reboot the device. Once it boots up again, it should detect the update and prompt me to install it.
Regardless of whether I put it on the internal storage, or on the external SD card, I cannot get this thing to detect the update and prompt me to install. I have also attempted extracting the second zip file so I end up with a META-INF folder and the blob. Putting this in the root of the internal storage and the root of the SD card didn't work either.
The device is currently rooted, and has been reset to factory several times during this process.
Any suggestions? Have I missed something totally obvious here?
Thanks!
Edit: Currently running ICS, on the stock 9.4.2.28 build from Asus.
Can't post links right now but trekest has a method that worked for me
Sent from my Zio using xda app-developers app
McJesus15 said:
Can't post links right now but trekest has a method that worked for me
Sent from my Zio using xda app-developers app
Click to expand...
Click to collapse
This one?
http://forum.xda-developers.com/showpost.php?p=32099246&postcount=154
Followed it to the letter. Rebooted the tablet once I had done everything specified via shell and the tablet simply rebooted. Still on ICS. Tried to replace the build.prop as mentioned at the bottom (after backing up my existing one of course), and it still simply rebooted.
Update: After a few more reboots, the tablet detected the update file. Unfortunately, the dlpkgfile I got was the US version (I need the WW version). An alternate download link from the one listed in the link above also gave me the US version (even though the poster said it was WW). Once I find the WW version, I should be able to get this update wrapped up.
I had the same problem.
In my case the solution was to copy the extracted ZIP file to the root folder, rename it to 'dlpkgfile' then reboot.
When it restarted, I then had the prompt that a system update was available but on checking the root folder, the 'dlpkgfile' file had been deleted so I repeated the process above, then clicked the update notification & away it went & did the update normally.
Hope that helps.
magrath1 said:
I had the same problem.
In my case the solution was to copy the extracted ZIP file to the root folder, rename it to 'dlpkgfile' then reboot.
When it restarted, I then had the prompt that a system update was available but on checking the root folder, the 'dlpkgfile' file had been deleted so I repeated the process above, then clicked the update notification & away it went & did the update normally.
Hope that helps.
Click to expand...
Click to collapse
Seems to have worked. Thanks!
I backed up my root from ICS, but when I started VooDoo again, my root backup was gone. Is there a working root tool available yet? Or is JB rooting still being worked on? I've been poking around the forum but have only turned up rooting tools that work for ICS thus far.
dochouse said:
Seems to have worked. Thanks!
I backed up my root from ICS, but when I started VooDoo again, my root backup was gone. Is there a working root tool available yet? Or is JB rooting still being worked on? I've been poking around the forum but have only turned up rooting tools that work for ICS thus far.
Click to expand...
Click to collapse
Yeah. Same here.
Apparently it can be done by rolling back to an old ICS version, updating to .28, backing up root with RootKeeper, re-flashing JB & restoring root. Seems like a lot of trouble though.
Think I'll just wait until someone meare learned than I comes up with a working exploit...I'm sure it won't be too long.
magrath1 said:
I had the same problem.
In my case the solution was to copy the extracted ZIP file to the root folder, rename it to 'dlpkgfile' then reboot.
When it restarted, I then had the prompt that a system update was available but on checking the root folder, the 'dlpkgfile' file had been deleted so I repeated the process above, then clicked the update notification & away it went & did the update normally.
Hope that helps.
Click to expand...
Click to collapse
I just tried doing this several times and on my tablet the update starts but then at about one third in it stops and fails. I have repeated the process 5 times using all the suggestions and even re downloading the file and same thing, I am just going to wait but so far no OTA available yet when I do the firmware update check it just tells me no update available for my device .
Finally tried using Baxbuda's manual method by downloading the firmware from Asus then renaming the file EP201_SDUPDATE.zip and copying the file to my MicroSD card and started the update using the power + vol. down, then releasing the power button and pressing the vol. up and it completed the upadate and I now have JB and so far it is fast and smooth with no issues to report
Jesse6749 said:
I just tried doing this several times and on my tablet the update starts but then at about one third in it stops and fails. I have repeated the process 5 times using all the suggestions and even re downloading the file and same thing, I am just going to wait but so far no OTA available yet when I do the firmware update check it just tells me no update available for my device .
Finally tried using Baxbuda's manual method by downloading the firmware from Asus then renaming the file EP201_SDUPDATE.zip and copying the file to my MicroSD card and started the update using the power + vol. down, then releasing the power button and pressing the vol. up and it completed the upadate and I now have JB and so far it is fast and smooth with no issues to report
Click to expand...
Click to collapse
Tried both of the reported method and I had no luck at all. With the Power+vol down. then releasing power and then pressing vol.up... when is this done?
The following worked for me.
-------------------------------------------------------
To update to new firmware versions for the tablet.
Download the appropriate update from ASUS support website for the TF201 Transformer Prime Tablet
Extract the zip file within the downloaded zip file from ASUS support.
Get an SD card of some sort.
Create the Folder \ASUS
Create the folder \ASUS\Update within the ASUS folder
Copy and Paste the US-epad-user-x.x.x.x.zip file into the \ASUS\Update folder.
Plug the SD card into the Tablet. It will show a triangle with ! in the system area.
Tap on it to start the update process.
anyone managed to root a tf201 with the latest asus jellbean rom on? seems a real pain to have to flash down to the factory rom, unlock, root then install a custom rom.
when i say "real pain" i mean, it's a heap more hassle than trying out a few custom roms on my i9300!
Hello,
To install to clockwork recovery manually I replaced the recovery.img file but when i restarted my phone it says:
Image signature verify fail
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one
you can remove battery for power down.
now i can access only to pink screen, but when i connect my phone with a usb cable then computer only checks drivers etc but does not open a drive where i could change recovery.img back to normal.
maybe some drivers are missing..
also made video of it: https://www.dropbox.com/s/48ogtdy7momwout/VIDEO0007.mp4
anyone? Help me please
i can get to firmware update but it always fails
Solution to ur problem
Had the same problem.. but solved it by following these:
Insert microSD card into ur pc via card reader,etc.
Download the file B919_official.7z. from (kaefert.is-a-geek.org/huawei_honor/B919_official.7z)
Extract the contents of the archive to the root of the microSD card.
Create a new folder named “dload” (without the quotes)
Within the “dload” folder, copy 2 files named “UPDATE.APP” and “UPDATE_CUST.APP” (without the quotes) from the extracted content of B919_official.7z.
Insert the microSD card into the Huawei U8860. Do not power on the Huawei Honor U8860.
While the Huawei Honor U8860 is powered off, press and hold Vol Up + Vol Down + Power. Release the buttons when it starts flashing.
The Huawei Honor U8860 should power on and reflect flashing 1/2, followed by 2/2.
Wait for it to complete.
There u got the mobile back good as new.
Note: ur data that is not memory card will be deleted.
thanks it worked. had the same problem and solved
thanks it worked. had the same problem and solved.
U8860 inage signature verify fail
Have the same problem and would appreciate any help extended
Mine is that accidentally renamed the image file without the extension ".img" thus android does not recognize it.
i had disabled usb debugging and am thus unable to connect my phone via usb to change the name.
my phone was rooted though
i am able to reach the pink screen but any effort to flash in a new ROM fails
i had not installed CMW and was running ics.
Please help.
is there any way to enable usb debugging when phone is off and cant start?
rohanadvani007 said:
Had the same problem.. but solved it by following these:
Insert microSD card into ur pc via card reader,etc.
Download the file B919_official.7z. from (kaefert.is-a-geek.org/huawei_honor/B919_official.7z)
Extract the contents of the archive to the root of the microSD card.
Create a new folder named “dload” (without the quotes)
Within the “dload” folder, copy 2 files named “UPDATE.APP” and “UPDATE_CUST.APP” (without the quotes) from the extracted content of B919_official.7z.
Insert the microSD card into the Huawei U8860. Do not power on the Huawei Honor U8860.
While the Huawei Honor U8860 is powered off, press and hold Vol Up + Vol Down + Power. Release the buttons when it starts flashing.
The Huawei Honor U8860 should power on and reflect flashing 1/2, followed by 2/2.
Wait for it to complete.
There u got the mobile back good as new.
Note: ur data that is not memory card will be deleted.
Click to expand...
Click to collapse
error while step 2/2
update failed..
what can i do to fix that?
vuralemre said:
error while step 2/2
update failed..
what can i do to fix that?
Click to expand...
Click to collapse
Update. ..
Hi, after try to replace the recovery.img and i've got the same problem.
when i try to restore the stock rom i got a error "Update failed" at step 2/2.
i try with the violet screen but the drive don't mount.
I try 4 time and have the update failed at step 2/2 systematicaly.
Can somebody help please.
Broken Link
Hi, this file link broken "B919_official.7z" please share new link.
Killerdog said:
Hi, after try to replace the recovery.img and i've got the same problem.
when i try to restore the stock rom i got a error "Update failed" at step 2/2.
i try with the violet screen but the drive don't mount.
I try 4 time and have the update failed at step 2/2 systematicaly.
Can somebody help please.
Click to expand...
Click to collapse
You'll have to use this downgrade patch first, before you can install the stock ROM.
http://forum.xda-developers.com/showthread.php?p=33000395&highlight=b930+downgrade#post33000395
1) erase all data on usb card
2) extract downloaded file and move the folder dload to the card
3) volume up, down and power to install update
4) erase the card again
5) now move the dload folder with the stock ROM to the card
4) volume up, down and power to install update
5) after the installation the phone reboots several times
6) done
good luck :good:
Had the same problem but SOLVED
sc0rpp said:
Hello,
To install to clockwork recovery manually I replaced the recovery.img file but when i restarted my phone it says:
Image signature verify fail
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one
you can remove battery for power down.
now i can access only to pink screen, but when i connect my phone with a usb cable then computer only checks drivers etc but does not open a drive where i could change recovery.img back to normal.
maybe some drivers are missing..
also made video of it:
I used the b935 ics rom and put it into my sdcard.
Then i use the three button trick and flashed it.
done!
Click to expand...
Click to collapse
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!!
For those who are interested and are on stock non-rooted and didn't receive the (german) update by now, here is the logcat link i took :
( i was already on B04(bootstack/system (Australia)) but couldn't help to go back to B02 to have the link and share it - of course back on B04 :cyclops: )
( http://dl1.ztems.com:80/zxmdmp/down...es/HK/ZTE/ZTE A2017G/406489/fota_B04_B06MR.up )
or here the same uploaded zip file with a "little" bit faster download speed
https://www.androidfilehost.com/?fid=817550096634768949
Rename to .zip (or try the .up file) ( you may even rename it to update.zip ...)
you don't have to upzip it
Put into root SD (external) or try internal storage
...and update via settings ( when on B02)
ps : when your phone won't detect the zip, you could try to wipe cache in stock recovery and reboot again and try to update again into settings menu
or update in stock recovery either via ADB sideload or update from SD
Enjoy !
Thanks Bro was looking for this.
So I'm able to flash the fota updates via system recovery, but is there any reason why the system updater isn't detecting the files on SD card/not receiving the B04 prompt? ?
Hamburgle4 said:
So I'm able to flash the fota updates via system recovery, but is there any reason why the system updater isn't detecting the files on SD card/not receiving the B04 prompt? ?
Click to expand...
Click to collapse
Unpack the zip-file, but it in the root of your phone or in the root of external sd card.
jopomopo said:
Unpack the zip-file, but it in the root of your phone or in the root of external sd card.
Click to expand...
Click to collapse
Just to be clear, you're suggesting to rename the .up file to .zip, then unpack said .zip file to root directory? ?
Hamburgle4 said:
Just to be clear, you're suggesting to rename the .up file to .zip, then unpack said .zip file to root directory?
Click to expand...
Click to collapse
Just rename. You don't have to unzip anything.
Although I did the update with the UP file once in adb sideload (in stock recovery) when I was on B01.
This is for non rooted users. It's just the clean, German original update from ZTE. Just for those who didn't get it by now.
Hamburgle4 said:
So I'm able to flash the fota updates via system recovery, but is there any reason why the system updater isn't detecting the files on SD card/not receiving the B04 prompt? ?
Click to expand...
Click to collapse
Yes you can, either adb sideload or via update sd, all in stock recovery.
Or via the normal way when your phone detects the SD update. I have no idea why your phone doesn't detect the OTA on your SD by the normal way via settings. It should but this thing happens often.
Hamburgle4 said:
Just to be clear, you're suggesting to rename the .up file to .zip, then unpack said .zip file to root directory? ?
Click to expand...
Click to collapse
ooops, sorry my bad...didn't read the whole thread...thought you had the whole zip...I had similar problem with the .up file so the easiest way to do the update was downloading the whole firmware zip...
jopomopo said:
ooops, sorry my bad...didn't read the whole thread...thought you had the whole zip...I had similar problem with the .up file so the easiest way to do the update was downloading the whole firmware zip...
Click to expand...
Click to collapse
You mean the " australian " one. AFAIK there isn't already posted a german region whole firmware zip. (could be wrong)
Although i believe there won't be much difference in the end result
raystef66 said:
You mean the " australian " one. AFAIK there isn't already posted a german region whole firmware zip. (could be wrong)
Although i believe there won't be much difference in the end result
Click to expand...
Click to collapse
Jep, you are not wrong...there's no German full version released yet...I've used Australian one, and so far so good...
Sorry for the noob question ..I am on v1.0 B11..can I upgrade straight to this firmware or do I need to upgrade step by step ?
Sent from my ZTE A2017G using XDA-Developers Legacy app
First to 7.0 and then to 7.1.1
Hussainally said:
Sorry for the noob question ..I am on v1.0 B11..can I upgrade straight to this firmware or do I need to upgrade step by step ?
Click to expand...
Click to collapse
You can upgrade straight using the Australian full V1.2.0B04 ROM. It's 2GB++ file size. Extract the update.zip and put into the root directory of your internal storage or SD card. Then open the system update and it should detect the new firmware.
My phone doesn't detect the update from internal neither from SD. I tried both files, and cleared cache. Says my firmware is up to date, I'll wait till it pops up officially for my region
ГАСООП said:
My phone doesn't detect the update from internal neither from SD. I tried both files, and cleared cache. Says my firmware is up to date, I'll wait till it pops up officially for my region
Click to expand...
Click to collapse
Try in recovery. Either via SD or via adb sideload update.zip (put zip in adb folder PC)
(Also try all these steps with .UP instead of .ZIP)
Or flash the whole Australian zip bootstack + system. I'm running on that one. Or flash the original full Australian zip.
Possibilities enough
I know...the A7 can be stubborn :silly:
I am on the German B04..I have terrible mobile signal ..does anyone have a solution to improve the signal .?that's the only thing pushing me to sell this phone ...I love everything else about this phone ...please help
Sent from my ZTE A2017G using XDA-Developers Legacy app
Hussainally said:
I am on the German B04..I have terrible mobile signal ..does anyone have a solution to improve the signal .?that's the only thing pushing me to sell this phone ...I love everything else about this phone ...please help
Click to expand...
Click to collapse
You should try factory reset first.
MrMD69 said:
You should try factory reset first.
Click to expand...
Click to collapse
Ok will do ...but anyways I heard B02 has better signal..can I just flash B02 over B04?
Sent from my ZTE A2017G using XDA-Developers Legacy app
Does anyone know weather widget work or NO on b04 Australian update??? Thanks