My friend gave me this tablet because he couldn't get it to work, and now I'm trying to fix it. I'm pretty sure he tried to root/install google apps on it, but not exactly sure what he did and did not do.
I started by trying to just reset the firmware by booting into recovery and choosing a factory install. It was not able to do it because of an error reading the cache files. There was also an option to reset the cache files, but this threw the same error. Because of this, I also cannot install from an SD card. Along with this, USB debugging had not been enabled, so I can't use ADB to sideload a new bootloader or firmware onto it.
Thanks in advance!
Related
Hello,
I have a Allview Speed City tablet, and after i installed root on it, i changed the dpi using an app..
(root thanks to mad_ady, root availible at http://forum.xda-developers.com/showthread.php?p=40740061#post40740061 )
After this, the tablet is stuck in a boot loop.
I tried to do a factory reset from recovery mode, but this didn't solved the problem.
(the tablet has only 2 buttons, power and home. The recovery can be accessed pressing and holding both buttons until the recovery boot).
I located the file where the dpi is changing, /system/build.prop , and tried to flash another file from Onda 701 ROM (a very similar tablet). I didn't managed to find the original file. Anyway, the flashing didn't succeeded, "instalation aborted" appeared on the screen.
I found on some forum a flashable zip with build.prop from another device, and i replaced the build.prop file with the one from Onda ROM, signed it with a tiny program and still fails.
What options do i have to replace/edit the build.prop file? Before bricking, the ADB was not turned on on the tablet, and i read that i cannot use the SDK (anyway don't know how to use it). I contacted Allview and they don't want to give me the ROM from the tablet. And so, i call anybody that can give me a backed up rom from the tablet, anyone who have the knowledge about AD ROMS and are willing to help me..
Thanks folks!
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
this worked for me for full reset
crististan said:
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
Click to expand...
Click to collapse
this has been done with the allview speed city
I had a simular problem...
here my solution, hold on and home button at the same time until the screen gets back
wait until you get the boot screen...
use both, 1. erase card and 2. media options...
then to be save I choosed the other option say something like for factory reset.
the I used the apply update from ADB...
the tablet shows the same screen for 5 or 6 minutes
after it booted normaly, but I still had some problems
and I used a needle for a reset...
after that the tablet worked fine
the only thing what I dont understand is why its still root
Thank you for this tutorial, but i solved my problem with warranty. Even so, i erased all cache, factory reset from recovery but still i had no access to system files, and factory reset didn't changed the build.prop (system settings) to defaults.
It's normal. build.prop is part of /system (and the su binary is installed under /system as well), and any changes you make to /system files are permanent until you flash a different firmware.
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
Hello, I'm a little bit new to all this, so any help and detailed instructions are very very helpfull.
So I have Gigabyte GSmart Aku A1 device (MediaTek 6589), I don't know if it's bricked or what but apparently is not working quite well.
When I turn on my phone, it just loads and loads and loads and nothing happens (waited for about 4-5 hours), that was starting to happen after I somehow installed CWM on my device with some tutorial, CWM worked for the first time and after next reboot, it disappeared and stock recovery came back (and the problem with infinite loading screen - only showing logo).
I have ADB drivers installed, SDK aswell, tried to put stock firmware (got it from official site) and in like 1/4 of installation it says:
Code:
symlink: some symlinks failed
After that, I tried to install few versions that I downloaded from that official site, but same error again and again. (I tried to install with SD card and with ADB too. ADB is only working when I go to "apply update from ADB" in recovery. I have also used 2 different types of SD cards.)
That didn't worked either, so I got to some russian forum, and using google translator I downloaded 5-6 types of custom ROM's / Firmwares. That didn't worked either, one time when installing one of those ROM's - it said something about signature..
After that I was trying to install those ROM's with ADB and with SD Cards aswell, but turns out that every single time I get error saying: "Installation aborted.".
I have ofcourse tried to wipe data/factory and to wipe cache too, but nothing helps..
Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.
I really don't know what to do anymore, so any help would be very very appreciated. Thank you for your help in advance, if you need any videos, pictures or something, just tell me.
Edit: When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".
BUMP!
BUMP^2!
luuksa said:
BUMP^2!
Click to expand...
Click to collapse
i would look for stock rom in form of full mtkdroidtools backup and preloader drivers for your mtk chipset
and flash it using flashtool (it uses preloader[you can determine if it's available/undamaged by turning phone off and opening device manager on pc and plugging phone to pc if there will be a flash in device manager before the charging starts it will flash ])
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.
Hey,
I'm quite new with all this stuff and I just got into some problem. I wiped everything in recovery mode using twrp, cache and internal memory etc (dont ask me why). Anyway, my phone seem to be stuck on a booting loop since I can't enter recovery because twrp fail to load up correctly. You can see where it gets stuck in the image I attached.
Someone know what's wrong and if it's possible to fix somehow?
Thanks :fingers-crossed:
Okay, it seems like I managed to fix it myself. I used adb and fastboot to install everything as stock.
https://developers.google.com/android/images
However I'm not sure about the USB debugging part, how do I enable that if there is no os installed? Do I even need it enabled when I use fastboot?