[Q] Mach Speed Trio 7 possible brick issue - Android Q&A, Help & Troubleshooting

Just bought this as a replacement for another tablet. When I got it, the wifi would not turn on properly so I flashed this rom going through the recovery menu. Now upon booting, the screen with the android robot comes up, and then switches to a black screen with the backlight on and nothing happens. What I've tried:
-adb devices does show that it sees the devices
-abd reboot recovery results in a restart and nothing else (that I can see)
-abd reboot bootloader also results in nothing
-adb shell results in " - exec '/system/bin/sh' failed: no such file or directory (2) -"
-allowing the tablet to die and then recharging it does nothing
Trying to flash via livesuit results in device not found error, and I can't boot into recovery via the hardware buttons. Should I just give up and send it back to the manufacturer?
This tablet comes rooted. CWM is not installed. Pretty much everything I've found involves either CWM or the recovery menu, neither which I can access. Any other ideas, or is it time to give up?

HELP!!!! bricked trio stealth 4.0
Ok so I havE the exact same tablet as you and have done the exact same thing and come to the exact same finally. No luck get passed the backlit screen. Have you been able to bring yours back yet
ftkatyowser said:
Just bought this as a replacement for another tablet. When I got it, the wifi would not turn on properly so I flashed this rom going through the recovery menu. Now upon booting, the screen with the android robot comes up, and then switches to a black screen with the backlight on and nothing happens. What I've tried:
-adb devices does show that it sees the devices
-abd reboot recovery results in a restart and nothing else (that I can see)
-abd reboot bootloader also results in nothing
-adb shell results in " - exec '/system/bin/sh' failed: no such file or directory (2) -"
-allowing the tablet to die and then recharging it does nothing
Trying to flash via livesuit results in device not found error, and I can't boot into recovery via the hardware buttons. Should I just give up and send it back to the manufacturer?
This tablet comes rooted. CWM is not installed. Pretty much everything I've found involves either CWM or the recovery menu, neither which I can access. Any other ideas, or is it time to give up?
Click to expand...
Click to collapse

Related

[Q] Help with bricked generic tablet

Hi!
I was trying to root my "titan pc8008" tablet the other day. Being a noob i ended up screwing it up and now it when i turn it on i always gets stuck in the loading screen android os.
When it worked i managed to have adb working properly (that's how i was doing the rooting).
It never occurred to me to install cwm or make any kind of back up before tinkering with the device.
I've done some research and manage to boot into a screen with a green android laying with a red triangle over it' belly. I think this is the stock recovery.
The thing is the tablet doesn't have vol keys and the stock recovery screen doesn't show any options.
I've tried pressing all kind of combinations with the keys the tablet has but nothing happens.
Also, when im in the recovery screen i can do some adb commands like "adb reboot recovery" ,which takes me to the same screen, and "adb reboot-bootloader" which just powers off the device. "adb shell" says something about like it can't mount the file system.
How can i flash cwm (or do anything) from this point?
Btw, sorry for the long post but i wanted to give as much info as posible
btw this is all i get in the recovery screen
....//i.imgur.com/ZTpo5CC.jpg (sorry can't post links yet)

Help! Boot Loop or Complete Brick? :(

So a friend recently bought this spanish voxter tab 97 IPS (16GB) and after a few days of usage and several attempt to install a custom ROM, the tablet stopped booting. According to him, he tried loading a "compatibility bla bla bla.zip" file with CMW which I really do not know what it is, and since he did the installation, the tab stopped booting into system. Every time it's turned on, it just stops at the boot screen and nothing more. Although before this, he had installed a custom recovery and had also done a Nandroid backup with the recovery. However, what baffles me is, CMW is no longer accessible through the normal "power + volume up" key combo and I'm quite unsure of how to boot into fastboot.
That aside, I tried booting into recovery with adb because apparently, adb recognizes the device whenever it's stuck at boot screen, this also failed, neither did rebooting into fastboot via adb work. All I need to know is if this device is totally bricked, or if there's still something I can do. If there's any, I really would appreciate every help offered. Thanks..

[Q] LGC800g w/CM9 - Weird boot loop that re-flashes OS

I recently picked up a C800g to tinker with, and was able to install CM9 on it. Everything was working fine until I rebooted: It appears to re-flash the OS everytime I restart, wiping all settings/apps, etc. None of the key combinations seem to yield 'recovery' mode any more, and though adb works, it just runs through the same start process (shows the 'LG' logo twice, then the cardboard box + arrow + robot + progress bar, and boot to "factory" state.)
Even after I removed the 'update.zip' file on the SD (this seemed the obvious culprit), it continues to re-flash on every boot. I can't seem to get to fastboot, as it goes through the same startup everytime ('adb reboot bootloader', while 'fastboot devices' never picks up anything.)
Outside of keeping the phone powered up, I seem to be in a weird state -- I can't help but think it's something stupid, but I can't seem to get out of this cycle (I'm thinking I should be able to 'dd' cwm to one of the partitions, but I haven't seen reference as to which it should be.)
Kind of solved the problem: Found another thread that identified the download mode for the phone (vol up + E + power) -- This enabled the LG support tool to reflash the phone, albeit back to GB. :good:

[Q] DOPO d7020 stuck in loop with mysterious issues

I bought this tablet exactly a year ago, never modified or rooted it, and suddenly a lot of apps started having issues. Went to reinsall a few of them then suddenly the whole OS froze.
Rebooted and the Dopo splash would show, then the android logo showing movement like it is trying to boot but gets stuck there.
Tried going into recovery by holding the power and volume button, that *worked* but when selecting factory reset then it crashed again.
So I repeated the process and now it won't even boot into recovery using the power and volume button!
Tried running the battery dead and restarting, tried using the reset button pinhole. Nothing worked.
I installed adb and fastboot (I use linux) and went through most of the simpler procedures.
adb connects and I can run its shell and view my files that are on the tablets. Ran the command to see its debugging output and noticed that the boot loop was because the filesystem turned everything except userspace to read-only!
Now here is what is real odd.. when I try pushing a file onto the tablet using adb, it instantly becomes corrupted when reading it back.
Like if I make a simple text file called hello.txt with some text in it saying "Hi there!", when I push that file onto the tablet, then read its contents it is gibberish.
This leads me to believe the whole filesystem somehow became corrupted and can no longer write files properly.
There doesn't seem to be a way to run fsck or anything alike and I can not put any files on the tablet because they instantly become garbled.
No use in running fastboot when the tablet no longer can go into the recovery screen either by vol+power pressing or by adb reboot recovery. Both simply just try to boot the tablet normally now, unlike the first time I tried
Assuming I have the factory .img file is there any way I can fix this?
Or does this sound like the hardware got damaged?
I fear the worst at this point.

Question Bootproblem and how go back to the standards

Dear Community,
I am a real noob when it comes to Android, flashing ROM, root and so on.
I got a Oneplus here where supposedly root rights are on it and another ROM.
Current problem, as soon as I turn it on it hangs when booting. (Bootloop - red dot with 2 running white dots)
I already tried it with power + volume+. Unfortunately unsuccessful.
Is it correct when I press Power + Volume- that you get into fastboot?
I can't get into the recovery mode either.
I would like to get the device running, but without root rights, OEM lock and the Oxygen OS from Oneplus.
So far my attempts to get it running have been unsuccessful.
Update: after 4h in the bootloop, it booted successfully. *yeah*
So how i can see, if the phone is rooted and how can i lock it?
I tried it with adb, i can find the phone with adb devices.
Then adb reboot fastboot, after that i tried to find it with fastboot devices but then he finds nothing more. the drivers are installed. also fastboot oem lock doesnt work, because the phone is not found.

Categories

Resources