Someday i rooted my "ASUS MemoPad 7 (Not HD7) [Codename is: K017]" and i downloaded "Rom Manager" and i flashed "CWM Recovery for Motorola Droid" to my tablet.
Tried rebooting but in the rebooting text tablet freezed, i force shutted down tablet and, i powered on tablet. But tablet won't booted and i think: [Wow! Lets reflash system files].
I go to the PC and i investigated all internet but i can't find the solution. Now it cant boot it stuck in "BootAnimation" [System installed and tablet detects system kernel and other critical partitions.]
New supplemental: If try "Wipe Data" with DroidBoot tablet says: "ERROR!". [But i can wipe data with fastboot.]
New supplemental 2: It says "Serial Number:111111111111111111"
I tried:
Reflashing system kernel and other things [I provided firmware zip from ASUS website.]
Flashing temporary generic x86 recovery for any solutions [Vampirefo Venus Tethered Recovery]
THIS LINKS AND BUNCH OF LINKS:
https://eriffoorp.wordpress.com/2015/10/21/unbrick-asus-memo-pad-7-me176c-model-k017/
http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
GREETING FROM TURKEY
Sorry For My Bad English
Related
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
HuskyHamburger said:
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
Click to expand...
Click to collapse
If you can enter the bootloader, the OS, recovery or you have your nvflash backups then you have a chance.
If you can access none of these then you are hard bricked.
Tried Ubuntu Dual Boot: bootloop/brick; but fastboot, apx, and adb access OK
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
AnotherBrickInTheWall said:
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
Click to expand...
Click to collapse
Shoot me an email here [email protected]
We can get you going and than post our finding back here to help everyone out...
Thx Josh
I managed to land a root (for the first time) on my Zenpad S earlyer today.
it was the Kingo 1click usb root who landed for me. duno how that happend cuz i was trying to install the one described on the forum here.
anyways lots of **** on my Zenpad so i google factory reset and foun that it does not remove the root. So i did a factory reset to clean up the system. after reset i got some firmware update from asus and on reboot it stuck on Asus loading screen. i foregot to install the SuperSu before i installed to update from asus.
I have tried
Reboot - stuck
Factory reset - stuck
Running the root - over agen - stuck
Clearing the cash - stuck
asus image from official site from micro usb - didnt work
waiting more - dont work
is there any hope for my zenpad s?
Hi,
Yes, I think I had a similiar situation.
You need to download the 1.3Gb zip firmware image from support.asus.com. Put it and why not also updated super su.zip on a 8Gb microsd formated to fat2.
Then download the tools on first the page of
http://forum.xda-developers.com/showthread.php?p=61930837
Extract the files to pc. Ensure you have working adb drivers. Reboot zenpad s 8.0 with volume up +power. Connect zenpad to pc and run the launcher.bat from toolkit.
Type ACCEPT, select 5 for cwm and finally T2 method.
Now you should be in temporary cwm. Install the 1.3Gb zip image from sdcard and be patient. It looks like md5 checking forever but finally you will have a restored zenpad.
Before rebooting you might also install supersu but when rebootin do NOT let cwm fix root, just select no.
I think asus is great for providing fw and even source for us. Did not even consider samsung due to their silly knox fuses.
I hope you get back on you pad with this.
Mulperi
My tablet frozen on boot screen (help!)
Hello everyone, I'm new here. I hope this is the correct place to write this problem and you can help me with it.
I bought one year ago a Wolder miTab MINT with Android 4.2. This tablet hasn't got the Play Store, then I decided to root the tablet and install the apk. The problem is that now the Play Store is using to much ram or cache (I don't remember) and because of that the tablet can't goes any further than the boot screen.
The solution will be to reset the tablet like was before but I tried everything without good results. For example:
1.- Use the recovery mode and use wipe data/factory reset. Don't work.
2.- I downloaded the Phoenix Suite and the firmware of this tablet. The software doesn't detect the tablet in normal mode or recovery mode.
3.- I installed the ADB generic drivers. My computer detect the tablet like Galaxy adb tablet or something like that but the Phoenix Suite still the same, it doesn't detect the tablet.
4.- My last option was to try to install the firmware (.img file) with adb sideload. The computer send the file but the tablet shows an error in the verification and it doesn't begin to install it.
Please, any help to reset this tablet to factory settings?? Thanks a lot!!
Fix it
Have you had any solution for this problem?
I decided to root my ME302C tablet to remove some bloatware using an app that required a rooted device. I had the latest firmware so I couldn't use any of the rooting guides online, but I tried Kingo Root, an automatic rooting PC program (all I had to do was enabled USB Debugging), and it worked, at least for one session (after a reboot, it appears to stop working).
After I removed the bloatware, I reset the tablet to its factory state without using the remove root option in Kingo SuperUser (not SuperSU) (I did not know that the option existed). I'm not sure if it would have made a difference if I had used that option, but after resetting, Android booted properly, but I had no lock screen, broken default browser, unresponsive on-screen home button, no notification area, and I lost some options that appeared when powering off (airplane mode and mute). I occasionally get "unfortunately *app* has stopped" errors, but it doesn't appear to affect anything. The tablet works fine otherwise.
I would really appreciate it if someone could direct me on how to restore the default firmware entirely. If I factory-reset, it just removes the apps and resets the settings without affecting the system (clears cache and user partitions), and this website confirms that: search for Isn't Factory Reset exactly the same as wiping /data and /cache? stackexchange. I can't link to it directly. Sorry.
I found a post about an unrelated problem while typing the title where somebody attempted to root using an unofficial firmware update and totally bricked their FHD 10. They ran these commands:
fastboot erase cache
fastboot erase system
fastboot flash update "updatename".zip
Suppose that instead of using the unofficial, rooted update.zip he used, I used an official one from this page (it contains links to updates for my tablet's firmware): search for me302c asus. I can't link to it directly. Sorry.
Would that work? I am assuming that a firmware update is a copy of the entire firmware.
If I could use an update, could you please let me know how to flash it exactly? I can boot into recovery mode, Droidboot Provision OS. It has an option to update the firmware, I believe, called "SD DOWNLOAD". If I place an update.zip file named ASUS_BUNDLE.zip on an external SD card and use the option, it'll look like it's updating (there are a few screens, I think they say "clearing cache" and something else, but nothing mentioned of the system partition) - however, it just acts as if it is a factory reset, taking me back to that state where things are borken.
SD Download doesn't look like it is doing something for every random ZIP you put on the SD card, because if I use a ZIP file that has, say, a picture of my cat enclosed, it will not do anything. I think that it does do something with the ASUS_BUNDLE.ZIP, but just not anything that solves my problem.
In Droidboot, if I plug a USB cable into the tablet and the other end into my PC, an icon will appear saying "USB connected". If I enable USB debugging in Android and connect the tablet to my PC in the Droidboot Provision OS recovery mode, should I run the commands then?
I realize that this is a mouthful and thank you for taking the time to read my post.
Did you solve this in the end?
Yes.
_MsG_ said:
Did you solve this in the end?
Click to expand...
Click to collapse
I used the method that I posted to fix the tablet.
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?