Got my SM-A217F rooted first attempt,
So what i did was.....
1) used Frija-v1.4.4 to download my latest stock firmware "SM-A217F_1_20210807114045_mzeyu27v8u_fac.zip"
2) Extracted the zip file and flashed the 4 files with "Odin3_v3.14.4"
3) after that i let the phone restart and boot up entered my google account details etc etc
4) on PC i used winrar and extracted the "boot.img.lz4" file only from "AP_A217FXXU6CUH1_CL21842546_QB42174009_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5"
5) on PC i then used "lz4_win64_v1_9_3" i copied the extracted "boot.img.lz4" file into the "lz4_win64_v1_9_3" folder
6) op PC inside the "lz4_win64_v1_9_3" folder i dragged the "boot.img.lz4" file onto "lz4.exe" wich created a new file "boot.img"
7) copied the "boot.img" file onto my phones internal storage
8) on phone i installed "Magisk_patched_for_A21S.apk" and opened it --> chose "Install" -->"select and patch a file" --> select "boot.img" from step 7 --> normal android way
9) That created a "magisk_patched-22104_0x2Ov.img" file in my phones "download" folder
10) Renamed that "magisk_patched-22104_0x2Ov.img" to "boot.img" on my phone
11) i then used "ZArchiver" and compressed that "boot.img" i just renamed from "boot.img" to "boot.tar"
12) Copied the "boot.tar" file to my pc and renamed it to "boot.img.tar" on my pc
13) On PC i used "Odin3_v3.14.4" and flashed the "boot.img.tar" file to my device, i left "Auto reboot" and "F reset time" ticked
14) after flashing and getting the green "PASS" logo i left my phone pluged into the the pc the whole time while the phone was restarting
15) after phone rebooted i installed "Magisk" with the "Magisk_patched_for_A21S" app --> let it reboot again after install
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
AND THATS IT
ONE A21S SUCCESSFULLY ROOTED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
NB: thank grccorps for this excellent magisk
thanks you
[email protected] said:
11) i then used "ZArchiver" and compressed that "boot.img" i just renamed from "boot.img" to "boot.tar"
12) Copied the "boot.tar" file to my pc and renamed it to "boot.img.tar" on my pc
Click to expand...
Click to collapse
This is not completely clear for me.
Compressing boot.img to .tar is action different from renaming it.
What exactly happened?
BTW:
Similar case with boot.img.lz4 and boot.img.
Renaming doesn't mean uncompressing or compressing file then finally people might have two different things inside what could cause confusion and in one of two described situations potential bootloop/brick.
Maybe this was the reason that some folk achieved success and other not?
Let's clarify that for benefit all of us.
Please anyone explain.
F308 said:
This is not completely clear for me.
Compressing boot.img to .tar is action different from renaming it.
What exactly happened?
BTW:
Similar case with boot.img.lz4 and boot.img.
Renaming doesn't mean uncompressing or compressing file then finally people might have two different things inside what could cause confusion and in one of two described situations potential bootloop/brick.
Maybe this was the reason that some folk achieved success and other not?
Let's clarify that for benefit all of us.
Please anyone explain.
Click to expand...
Click to collapse
Okay i see how this might cause confusion,
###########################################################################
STEP 10 : was just a rename no software used
STEP 11 : i used "ZArchiver" to comprerss and change the file from ".img" to ".tar" (not just rename)
###########################################################################
Thank you.
I will root my M12 soon, it will eventually save me some hours of unnecessary efforts.
My English is pretty bad, so please excuse me..
I copied the "boot.img.tar" to my PC.
under which tab do I have to insert them in ODIN?
But no matter what I try I get an error.
No, I changed them in step 11 with ZArchiver.
I just want to root my phone. Greeze
At start - don't apologize your English.
Not even Englishmen speak English.
At step two:
You are lucky you didn't land in bootloop or brick zone.
Even I was there because I was too fast to go into action.
I suggest to read at least 500 posts about rooting, myself I did it.
You will avoid lot of headache and will save much time.
[email protected] said:
Got my SM-A217F rooted first attempt,
So what i did was.....
1) used Frija-v1.4.4 to download my latest stock firmware "SM-A217F_1_20210807114045_mzeyu27v8u_fac.zip"
2) Extracted the zip file and flashed the 4 files with "Odin3_v3.14.4"
3) after that i let the phone restart and boot up entered my google account details etc etc
4) on PC i used winrar and extracted the "boot.img.lz4" file only from "AP_A217FXXU6CUH1_CL21842546_QB42174009_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5"
5) on PC i then used "lz4_win64_v1_9_3" i copied the extracted "boot.img.lz4" file into the "lz4_win64_v1_9_3" folder
6) op PC inside the "lz4_win64_v1_9_3" folder i dragged the "boot.img.lz4" file onto "lz4.exe" wich created a new file "boot.img"
7) copied the "boot.img" file onto my phones internal storage
8) on phone i installed "Magisk_patched_for_A21S.apk" and opened it --> chose "Install" -->"select and patch a file" --> select "boot.img" from step 7 --> normal android way
9) That created a "magisk_patched-22104_0x2Ov.img" file in my phones "download" folder
10) Renamed that "magisk_patched-22104_0x2Ov.img" to "boot.img" on my phone
11) i then used "ZArchiver" and compressed that "boot.img" i just renamed from "boot.img" to "boot.tar"
12) Copied the "boot.tar" file to my pc and renamed it to "boot.img.tar" on my pc
13) On PC i used "Odin3_v3.14.4" and flashed the "boot.img.tar" file to my device, i left "Auto reboot" and "F reset time" ticked
14) after flashing and getting the green "PASS" logo i left my phone pluged into the the pc the whole time while the phone was restarting
15) after phone rebooted i installed "Magisk" with the "Magisk_patched_for_A21S" app --> let it reboot again after install
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
AND THATS IT
ONE A21S SUCCESSFULLY ROOTED
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
NB: thank grccorps for this excellent magisk
Click to expand...
Click to collapse
If this works id pay you if i had money
Scia0 said:
If this works id pay you if i had money
Click to expand...
Click to collapse
It works ive done this personally
Does it work on Android 12 and with u8 protection
hamada2001 said:
Does it work on Android 12 and with u8 protection
Click to expand...
Click to collapse
Hello everyone.
I have read all the messages from the first to the last post from root to a21s.
Currently I just have to follow the steps in the first message without using modified magisk to be able to root?
Forgive my English I am Spanish and I use google translate.
localdemoda said:
Hello everyone.
I have read all the messages from the first to the last post from root to a21s.
Currently I just have to follow the steps in the first message without using modified magisk to be able to root?
Forgive my English I am Spanish and I use google
Click to expand...
Click to collapse
what android version are you on
I have android 12 but I can install android 11, which one is better for root?
ies thiss is best guide to root a21s im downgroaded to android11 (U8) .dont forget oem lock/bootloader unlock mode.
Related
I am trying to get my viewsonic g tab back to factory. I installed the APX driver ok, and downloaded the applicable files. I try to run the nvflash_gtablet.bat script and it comes up with a file configuration error that the file can't be found. I am running windows 7. Any suggestions?
i have never done nvflash and never got brick and loaded multiple roms and went on dif dev branches
this is for 1.1
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
and this is for 1.2
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-4349-user.zip
rename the zip file to "update.zip"
hopefully you partioned your tab before nvflashing it. if not then please ignore this.
put update.zip in root of your sd card.
create a folder named "recovery" and place an empty file named command with this text inside
Code:
--update_package=SDCARD:/update.zip
then go into recovery and let it update.
hope i helped somewhat
ps to make files in win 7. i open notepad and paste code then save a command.tmp then i go and delete tmp. it leaves it as a file. and works
Jrome86 said:
I am trying to get my viewsonic g tab back to factory. I installed the APX driver ok, and downloaded the applicable files. I try to run the nvflash_gtablet.bat script and it comes up with a file configuration error that the file can't be found. I am running windows 7. Any suggestions?
Click to expand...
Click to collapse
h i because you didn't have the image files to flash into. This is probably the most common mistake that beginners make.
Go to my website linked in my signature and go to the start here page. You're probably a code yellow.
Help!!
i been surfing the internet trying to find a way of how i can root my device. so far ive had on luck. i have tried gingerbreak but i don't think this has even worked. does anyone have any ideas of how you could root this particular device. if you have any suggestions or know how you can, i would be very grateful.
HOWTO - root PMP5080B
There is a way to root the tablet.
But it it does not root the runnning version, it roots the update image.
So if don't have the most actual firmware try this:
(maybe you can flash the firmware even it is not newer, but i don't know how)
Todo (Windows PC necessary):
At first load the latest firmware and unzip it:
h t t p : / / w w w .prestigio.com/info/product/downloads?NODE_ID=61101103718510974&ITEM=110706112617507776
Download the Wendal tool:
h t t p s :/ / docs.google.com/leaf?id=0B8h...RjZjFmODdiZTQ1
Then follow this steps:
1. Unzip the Wendal tool, you get a folder named "RK29xxImagetools_v2.1".
2. copy the update.img from Prestigio firmware download in the "RK29xxImagetools_v2.1" folder and rename the file to "wendal.img"
3. start "Runme.bat"
4. press "1", you get the message that you have to rename your file. Since you have already done this before proceed. The batch file starts, make sure you dont see any errors.
5. press "2" followed by "Enter". The rootet image will be created automatically
6. end the programm with "3"
7. in the "RK29xxImagetools_v2.1" you will find a file named "wendal-new.img", copy it to your SD card and rename it to "update.img".
8. put your SD card in your tablet, you will get a message to update your firmware
9. the tablet reboots, flashes the new firmware
10. be happy with your root access
Still having problems.
i have done what you said for me to do but when i rename the firmware to "wendal.img" and run it for some reason it keeps saying i haven't put the firmware in the folder when i have. do you know what how you can sort this out.
cheers
Did you unzip the firmware download?
Tried, tested & confirmed working
Just like to note that the software used will give you a warning about placing the update.img in the correct folder and renaming it even when it has already been done. You just have to press enter!
I have 5080B and i want to root it, but on ICS stock rom. Problem is, i cannot use wendal tools cause it can't add su and superuser.apk into /system ("no such directory") and even earlier i used to root gingerbread with these tools it is half-root - /system not rw, but superuser works
i saw update 2.0.2 from prestigio, pre-rooted, but i want to root this, newest version, 2.0.3
i have linux setup running and i tried mounting system.img but i can only add su, and nothing else cause there's no space...
also, how do i boot recovery from the device itself? i tried vol- and power key but there is an image of an 'destroyed' Android bot, no options there at all
Same problem - want root on Prestigio PMP 5080B
Just got a Prestigio PMP5080B running ICS 4 and want to root the tablet. I read from the preceding message that thhe method discussed here doesn't seem to work with it. Any ideas would be most welcomed here too.
By the way Hi!
Ziggy
help
remoh said:
There is a way to root the tablet.
But it it does not root the runnning version, it roots the update image.
So if don't have the most actual firmware try this:
(maybe you can flash the firmware even it is not newer, but i don't know how)
Todo (Windows PC necessary):
At first load the latest firmware and unzip it:
h t t p : / / w w w .prestigio.com/info/product/downloads?NODE_ID=61101103718510974&ITEM=110706112617507776
Download the Wendal tool:
h t t p s :/ / docs.google.com/leaf?id=0B8h...RjZjFmODdiZTQ1
Then follow this steps:
1. Unzip the Wendal tool, you get a folder named "RK29xxImagetools_v2.1".
2. copy the update.img from Prestigio firmware download in the "RK29xxImagetools_v2.1" folder and rename the file to "wendal.img"
3. start "Runme.bat"
4. press "1", you get the message that you have to rename your file. Since you have already done this before proceed. The batch file starts, make sure you dont see any errors.
5. press "2" followed by "Enter". The rootet image will be created automatically
6. end the programm with "3"
7. in the "RK29xxImagetools_v2.1" you will find a file named "wendal-new.img", copy it to your SD card and rename it to "update.img".
8. put your SD card in your tablet, you will get a message to update your firmware
9. the tablet reboots, flashes the new firmware
10. be happy with your root access
Click to expand...
Click to collapse
Hey, i have done everything right, but after unzipping the update.zip, i find only the boot.img file not the update.img file...and even after renaming it to wendal.img, the runme.bat program says FAILED...any clue how this can be fixed?
TVMALOPE.IM said:
Hey, i have done everything right, but after unzipping the update.zip, i find only the boot.img file not the update.img file...and even after renaming it to wendal.img, the runme.bat program says FAILED...any clue how this can be fixed?
Click to expand...
Click to collapse
If you want, i can share my rootet version 1.0.26 for you, i still have the old .img file
But actually i am using this version on my pad:
http://x--t-e-a-m.blogspot.de/
I think it is far better than the original firmware (root included, it is Android 4.1 !)
Italian people did it, so maybe bing translator can help you
http://www.microsofttranslator.com/bv.aspx?from=&to=en&a=http://x--t-e-a-m.blogspot.de/
help
thanks but im new to android so i cant understand, can you send me your .img file...because i just want to copy straight to memory card and get root access, please...my tab is PMP7170B3G
TVMALOPE.IM said:
thanks but im new to android so i cant understand, can you send me your .img file...because i just want to copy straight to memory card and get root access, please...my tab is PMP7170B3G
Click to expand...
Click to collapse
The img file is for PMP5080B, so it won't help. Wrong thread, sorry
Hello
here i am posting here because i cant post on Miscellaneous Android Development , how ever i think i post there before while working on B5512
I Just got new G700 it came with B115 middle east channel , phone is good but as a start is there is a update i must ask my self is root ready , and CWM for sure so i start the digging
@chamaruco thank you for your great thread which saved and helped many people
now i got a file and i think you were looking for it ""G700-U10_V100R001C00B124CUSTC432D001_Firmware_Portugal_Channel-Others_4.2.1_EMUI 1.8_05021LMW.zip"" it contain usb upgrade and sd upgrade with drv and flash tool
i notice EMUI 1.8 not 1.6 which i saw for example a permission manager with it on P6 is that here in that rom too ?
is that rom improved than mine b115 phone is good for first look but
(in B115)
1-camera quality is strange i dont mean bad but it look very strange it is like very poor on quality
2-in call volume is too low in my opinion all " in test mode"
Question now did any one get that update "EMUI 1.8 B124" can tell is there is any improvements ?!
Question am i able to flash CWM image directly with flash tool to save some annoying procedures ?!
a member here provide flasher and cwm.img and orginal recovery.img
i did not work with the phone yet need to shift data from old phone remove ext2 part and prepare for change , and feeling lost here
want to strike it all once
i will upload "EMUI 1.8 B124" soon as it came from a private server
any suggestions are welcome
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
how to install this firmware i.e. B124 on G700-10
chamaruco said:
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Click to expand...
Click to collapse
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
talvigi said:
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
Click to expand...
Click to collapse
Dload inside put update.app file, restart in updatemode
chamaruco said:
Dload inside put update.app file, restart in updatemode
Click to expand...
Click to collapse
But my mobile does not boot into CWM recovery mode as i have seen in my previous Qmobile A8 it always restarts in the defualt recovery mode which only give options to "1. reboot, 2. update from SDcard, 3. update from cashe, 4. wipe/delete user data and wipe/delete cache and in the last there is a calibarate TP, AND OFF COURSE THESE ALL ARE THE ANDROID BUILTIN RECOVERY STEPS NOT OF THE CWM
And off course there is not any file or folder named update.app in the downloaded .zip/extracted file. "as i have mentioned above the folder contains a folder named META-INF and three img files named as boot cust and system while a .bin file named logo too.
THANKS FOR YOUR TIME AND HELP.
foffa said:
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
Click to expand...
Click to collapse
So after I select the Reworked scatter file there is only the sec_ro partition checked to flash. So after flashing it do I now select the previous scatter file and then flash everything (including preloader)?
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!!
Hi all recently purchased the Mecool KM8 P 2GB/16GB S912 Amlogic, updated the firmware to 7.1 but lost root access. I have managed to find some instructions on a Russian website to root the stock firmware but can't make head nor tale of it and don't want to brick the device.
The google translate version of the instructions reads as follows:
To get root 7 Androide did:
1.Nado SuperSu create a text file without an ending .txt textBOOTIMAGE = / dev / block / boot
2. Flash card throw Recovery for 7 Androyd created Fail SuperSu and SuperSU.zip (5,63 MB)
3. Boot into Recovery with USB there "Advanced" ==> "File Manager" find the file on a flash drive that put his name it .SuperSu in and copy it into the folder / system
3. Without leaving the Recovery go to "Set" and set SuperSU.zip (5,63 MB)
Can someone please help to decipher the above?
Here's the link to the instructions website. The downloads are pinned to the top of the page. Please let me know if you have any success...
http://4pda.ru/forum/index.php?showtopic=807465&st=1100#entry62380504
1. Create a texfile with this content:
BOOTIMAGE = /dev/block/boot
If I am not mistaken then this file should be saved wit the name .SuperSU and no extension.
2. Copy this file and the Supersu.zip onto a SD with a working TWRP recovery.
3. The file .SuperSu is now to be copied into the system folder - it does not specify if the one from the box or the one from the recovery is used - I assume the one on the box. But needs to be tested to be sure.
4. Without ending the recovery session go back and install install SuperSu.
Thing is you need a recovery that works with Nougat to do any of this.
But then again translators suck and someone capable of reading russing could bring some light on it....
Managed to get it to work. Steps in common English are as follows:
To get root on Android 7.1:
1. Create a text file (eg in Notepad) and name it Supersu without an ending .txt with the folowing text BOOTIMAGE = / dev / block / boot
2. On a microsd card copy Recovery.img (TWRP 7), the created SuperSu file (from step 1) and SuperSU.zip (5.63 MB)
3. Insert the card into Boax and boot into Recovery.
4. Using theTWRP recovery got to Advanced" then "File Manager" find the created Supersu file (from step 1) and copy it into the folder / system.
5. Without leaving the Recovery go to "Install" and flash SuperSU.zip (5.63 MB) from the Microsd card
can you post the required Files here?
i dont understand russian so i dont know what they wrote on 4pda.ru
I have found all file and attached at end of the Post
1. decompress km8p.zip to the root of your TF-Card so you have 3 Files on the root of your TF-Card (.SuperSU, SuperSU.zip and recovery.img)
2. power off your KM8P
3. Press Reset and hold it
4. Power your Box on and hold Reset
5. If you see the TWRP-Logo you can stop press Reset
6. On the Screen accept write and modifying Systemfiles
7. go to Advanced" then "File Manager" copy .Supersu file from TF-Card in/ system of your Box
8. then go to "Install" and flash SuperSU.zip (5.63 MB) from the TF-Card
9. Reboot and now you have root installed
MetaIIica said:
I have found all file and attached at end of the Post
Click to expand...
Click to collapse
I think you uploaded the wrong file, as the zip file you uploaded only contain one file (km8p), which has no file extension (it is probably a .zip file).
However it is missing the other files you are talking about, so could you upload the right files?
Thanks for the effort!
afehst said:
I think you uploaded the wrong file, as the zip file you uploaded only contain one file (km8p), which has no file extension (it is probably a .zip file).
However it is missing the other files you are talking about, so could you upload the right files?
Thanks for the effort!
Click to expand...
Click to collapse
I attached the TWRP for Android 7 here, if you still need it.
I have also started a thread on how to root with Magisk instead of supersu, as supersu wouldn't work for me.
https://forum.xda-developers.com/android-stick--console-computers/amlogic/howto-km8-p-2gb-8gb-s912-amlogic-tv-box-t3745937