Softbrick(?) Mediapad S8-301L - Huawei MediaPad, T-Mobile SpringBoard

So, I've been having this issue for a while now. I have a mediapd S8-301L and a few weeks ago it started crashing and I had to restart it a few times. One time while restarting, it stuck on the startup logo screen, and it would take me around 7 - 8 times of turning on and off until it would actually restart. When that happens, it crashes very shortly after.
I tried to open the recovery mode, and I don't get any options and only see a screen that says:
entry SDCARD upgrade...
sd_update_path =/sdcard/dload/update.app
update_type = 0
check _factory_mode succeed.
ERROR: update_package_exist, /sdcard/dload/update.app not mounted
sdcard upgrade failed!
Please press the POWER key for 10 seconds to reboot.
FAIL
Since this did nothing, I did a factory reset thinking this would hopefully solve it. It didn't do anything!
I don't know what else I can do, and I would appreciate any help.
P.S. my tablet is not rooted, and I have no clue whatsoever when it comes to rooting.

Related

[Q] gt-i9100g freezing during boot or a few seconds later

About 3-4 months ago I flashed stock ICS into my Galaxy S2 (I did not wipe the cache, which I discover today was a mistake). I noticed a few weeks later that it was a bit unstable, crashing, restarting, etc. I did not care much and just kept using it.
Today it just would not boot, so after 1 hour trying, I managed to keep it alive (using safe mode) long enough to go to setting and have a factory reset.
Then it would not boot again.
From there, I tried several times the factory reset and wipe cache (using volume up + home + power menu). It would sometimes hang on the "installing applications" until several restarts it would eventually go. Then it would hang randomly on startup "s" video, until I managed to get to the welcome screen - which freezes pretty much on the first or second screen (choosing language and date/time).
I flashed I9100GXXLPY_I9100GDBTLP3_DBT and got the same result.
The phone is not rooted, there is no clockwork and I can't even access the phone to put it into debug mode.
Anyone has any more idea of what can be done besides throwing it on the trash? :/

[Q] Problem rebooting 'e:error in /data/log/recovery_log.txt '

Hi guys,
little bit of background on the phone, had it since new close to 2 years away (2 year contract and im 7weeks from an upgrade) the phone is on orange (well EE now)
Basically when I turn my phone on it is stuck in a force close loop, with loads of different messages appearing, such as;
(process com.sec.android.provider.logsprovider)
calenders, messaging etc etc
So I have tried going into the boot mode, by pressing volume up, home screen and the power button.
Then when I try to reboot it comes up with the error messages;
e:error in /data/log/recovery_log.txt (read-only file system)
(read-only file system)
e:copy_kernel_file :: Can't Open /data/log/recovery_kernel_log.txt
Rebooting...
It then just continues onto the normal home screen, then when I enter my swipe code it comes up with the force close loop again.
Any solutions to this problem, Or will I have to factory restore, or is completly broken? Im not due an upgrade for about 7weeks either
Would rather not have to factory restore if possible as I have some files on there I dont want to loose, but if its unhelpable so be it
Thanks in advance guys!
Cheeky little bump, Anyone know a fix to this?
Have similar problem...
I believe a factory reset will fix it...sorry to hear you losing files though..
I have a similar problem. I should probably make a new thread for this though...
Background: Samsung Galaxy SII 1900 bought October 2011. Yesterday flashed a stock ROM for the phone and everything was working perfectly. This is probably not related but have been trying to install a working version of Android Keyboard which has gesture typing working for other languages than English, German, Spanish and French and so some hours before this happened I tried to flash a zip with that but it turned up "e: signature verification failed" so I pretty much gave it up and the phone was still working. Then I decided to install another recovery mode on the phone cause that should allow me to install without verification. So I downloaded the one for SGS2 at clockworkmod com rommanager and put it in on the SD card. Then I shut down the phone and this is the weird part: First I accidentally pressed the power button first so I realised the phone was gonna boot normall so I pressed the power button again to force shut it down. I pressed for quite a long time and then it just restarted and I'm at a boot loop where it says Samsung Galaxy S II with white text on black background.... Then suddenly after removing the battery and trying start several times it booted normally. So I just continued where I left off going to make a backup in Titanium Backup before flashing CWM and suddenly the phone just restarted and I got into the boot loop again. I am able to enter Download mode and Recovery mode but the phone no longer starts. Been trying like 30 times to restart it... Now when I entered Recovery mode just now I got the error message
"E:Error in /data/recovery_kernel_log.txt(Read-only file system)" in red letters... and that's where I'm at now.
Here's a sitty picture of it from my HP Chromebook webcam ******* (Google Drive) Edit: Not allowed to post links in first 10 posts

[Q] Deleting cryption meta data Help

Ok,I tried to install a different OS, on my phone via ODIN, i couldnt get it right the first couple of times so i kept doing more research. SO after i THOUGHT i had a solution i tried again. i was on the last step of the finalization and it said " about two minutes left" or something like that, and i waited about 40 minutes and it still said the same thing. so i thought i'd UNPLUG IT AND TRY AGAIN. well now after i do so,
i try to plug my device in again and it doesn't read it at all, This ALL HAPPENED AFTER THE PHONE ENCOUNTERED THE FIRMWARE PROBLEM WITH THE PHONE... WARNING SIGN... AND COMPUTER.
the only thing i was able to do was go to recovery mode, or download mode. CAN NOT GET INTO THE PHONE. now i'm smart enough to click an option on the recovery menu, but my power button or home button, or ANY Button, would not respond, besides the volume buttons to go up and down. So since the computer will not detect it, i dont know what to do, and i am using the factory cables, and i tried KIES AND ODIN. I have uninstalled drives in and out. still no solution, i read posts ever since last morning until now and decided to create my own posts for my own problems and seek help from people like ones on here who ACTUALLY KNOW WHAT THEY ARE DOING.
it starts up as Samsung GT-i9100 and they goes to Android System Recovery <3e>
and below reads in yellow,
Deleting Cryptoin Meta Data
--Copying media files...
Successfully copied meida files.
# MANUAL MODE #
--Updating application...
Successfully updated application.
--Appling Multi-CSC...
Successfully applied multi-CSC.
and shows and android robot with a white triangle and Orange ! mark in the middle.
The crazy thing about it is that i could use a button as an (Enter key) before i tried to flash my phone , before that i just cleaned the memory,
and once again after i removed phone from ODIN at about 98% im guessing, after i waited 40 minutes when it said about 2 minutes remaining. i was not able to try any other solution or connect to my laptop. and ive tried others, and my other phone connects fine. so i know i did something wrong....
Please Assist me, i'd really appreciate the time and effort,

Asus me371 (k004) failure to reset factory

Hi, i have Asus Fonepad ( K004 ) which stucked at boot loop, it boots and then after few seconds black screen and it starts boot again... . This all started after i have turned it off, because there was error message "google.apps.process" stopped working and after pressing ok this message won't go aways, so the tablet was turned off and after power on it stuck. I have tried to do factory reset, but got this message "still unable to mount /cache give up | result: fail (problem with write cache command!)". And have loaded new firmware twice but it's not working. I have seen topics with such problem, but people solve it through adb and .img file. For this device there is only one firmware file .raw. Help if you know what should i do?

Honor 8 stuck on boot (no fastboot, no recovery, stock rom)

Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.

Categories

Resources