Greetings,
I recently acquired an Android Q8 Tablet and proceeded to successfully root it. After looking up compatible recoveries on these forums, I flashed CWM version 6.0.1.2 (turned out to be the wrong one). Now, my tablet only boots into recovery and is unable to mount anything (internal). It can't mount neither /cache nor the internal sdcard. I do believe it ought to be able to mount an external card, as there is a slot but I haven't tried it yet. ADB barely works - while it detects my device (it displays that the device is in recovery mode), any command simply results in a " <waiting for device> ". I tried the button combination to boot into download mode, but that does not work either. I'm all out of ideas - any help would be greatly appreciated!
Thanks!
Almost forgot - the tablet is running Android 4.1, and I accidentally flashed a CWM for Android 4.2. My laptop is currently running Windows 7.
Q8 rooted?
Would you post how you rooted it please? My Q8 is running 4.2.2 do you have working Win7 flash util drivers?
If you"re in recovery, It should mount an external SD, On you PC copy the correct cwm mod root.zip to the micro SD , mount the card in Q8 and re-root it.
or
This may work:
Do you have a usb debug connection and flash utility? If you do:
on your PC unzip the correct cwm root.zip file
flash the .img file from the zip to the tablet.
This worked when I bricked my Samsung t679,
Good Luck!
Shyshan said:
Greetings,
I recently acquired an Android Q8 Tablet and proceeded to successfully root it. After looking up compatible recoveries on these forums, I flashed CWM version 6.0.1.2 (turned out to be the wrong one). Now, my tablet only boots into recovery and is unable to mount anything (internal). It can't mount neither /cache nor the internal sdcard. I do believe it ought to be able to mount an external card, as there is a slot but I haven't tried it yet. ADB barely works - while it detects my device (it displays that the device is in recovery mode), any command simply results in a " <waiting for device> ". I tried the button combination to boot into download mode, but that does not work either. I'm all out of ideas - any help would be greatly appreciated!
Thanks!
Almost forgot - the tablet is running Android 4.1, and I accidentally flashed a CWM for Android 4.2. My laptop is currently running Windows 7.
Click to expand...
Click to collapse
Related
Hi Guys!
I have a problem with my P7510.
My tab is on a bootloop
Stock recovery and download mode work
BUT
Tab is not recognized by PC or Odin
Wiping cache and factory reset don't solve this :crying:
This happened after i installed A1 Kernel on Infamous Rom 4.0.4, looking for USB charging. After installing it, no matter what, the PC wouldn't recognize the tablet (no notifications of any kind. Couldn't even find the tab on device manager. tested it on 3 computers, installing and reinstalling drivers, and the same error kept happening), it just charges it's battery. Tried several Roms and Kernels, but the problem was still there
Trying to find a solution i considered installing a stock firmware from samsung, but without USB recognition from my computer, i couldn't use ODIN3 1.85, but i stumbled upon MOBILE ODIN, so i used it to flash a stock firmware, but after a succesfull flash, the tab went into a bootloop. Tried wiping cache and factory reset,on the STOCK RECOVERY (not CWM) and the tab kept bootlooping :crying:
So, to recover my Tab, i need ODIN, but i can't use ODIN since my PC (and therefore ODIN) doesn't recognize my tablet.
So here's when i ask you ¿What can i do to recover my tablet? ¿Should i send it to a technician?
Thanks in advance
Sebastian
Some aclarations:
-I use odin as administrator on windows 7 32 bit
-i don't have Kies on the background
-I instaled and reinstalled the tab drivers
-I looked for the tablet on device manager. I didn't find it.
-The PC doesn't respond at all when i plug the Tablet (no notifications or sound),
Maybe you can try using ADB while your tab is in the Recovery mode.
I accidentally wiped my /sdcard fs and used this method to push a custom rom in the /data/media fs.
Since your Recovery mode is working, you can try to flash a new rom.
ADB Still works on Stock Recovery? (not CWM or TWRP)
ayankm said:
Maybe you can try using ADB while your tab is in the Recovery mode.
I accidentally wiped my /sdcard fs and used this method to push a custom rom in the /data/media fs.
Since your Recovery mode is working, you can try to flash a new rom.
Click to expand...
Click to collapse
My recovery is the STOCK samsung recovery, not CWM are you sure ADB still works with it?
Thanks for your reply, anyways
Hi All
I have an ainol novo 7 aurora v1
I previously had a nice working rom (the essential clean rom by android-kun from slatedroid), but just wanted to flash to cm10 to see what it would be like
I followed the thread below:
http://forum.xda-developers.com/showthread.php?t=1821398
before starting i flashed the recovery using Novotools then booted into recovery
i downloaded aurora-v1-v2_legacy-compatibility-jb_vX.zip and aurora-v1-v2_legacy-compatibility_v1.zip
then i used cwm to install
aurora-v1-v2_legacy-compatibility_v1
then the JB zip in that order
I then rebooted fine
did the usuall startup...thats when problems begain
Firstly. I couldnt get wifi to turn on. Basically you drag it on and it bounces back to off immediately
then i tried to open file manager, but nothing was showing up
then i opened a video/photo/camera app and got messages saying that no external memory could be found
if i try to access "Apps" or "storage" in settings, it crashes the settings app
i plugged the device into the computer and could turn on usb mode just fine but can only access internal storage but not external
so basically, i now have a device that cannot access any media, cannot access the internet, cannot install apk from file manager and cannot access full settings
All i have is superuser and terminal
so i tried to install novotools.apk manually via terminal but it didnt work and i tried to do it via windows via ADB but it said no device found (i have the drivers)
also i cannot boot into recovery
i have tried holding down power and vol – or +
and i have tried the terminal command
reboot recovery
both just reboot me back into the main OS
or just turn the device off
i have also tried to flash_image recovery a recovery.img
but it says directory not found referring to recovery
I am now tearing my hair out, so if someone could help me itd be much appreciated
it is running android 4.0.3 maybe thats what caused the issue (incompatability with cyanogenmod 10?)
The irony is that the tablet runs super super super smoothly but is completely useless BIG SIGH
Thanks for any assistance.
i have a feeling that if i can get the recovery to work then i should be able to reflash everything
i have also tried using livesuit but i cant get it into that volume+ and power button mode for it to flash
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
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 was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.