My tablet already installed cm12 and twrp 2.8.7.0. After fully charged the tablets become slow and said something i cannot clearly remember "can't find sdcard" so decided to boot to twrp and it stuck at twrp blue screen. I've tried to normal boot again and it brought me bootloop (after stay at blue android robot's face 5 min). I used KFHD system.img restore tools but it sends back an errors about "write protection'. I've tried to replace recovery with fastboot command and it said success (fastboot -i 0x1949 flash recovery) but i think it brought no change to my tablets cause it stuck at blue twrp title again. Please help me now!!!!
https://drive.google.com/file/d/0B8LasUq_e49bTS1aakQ5bENnYWM/view?usp=sharing
https://drive.google.com/file/d/0B8LasUq_e49bS0UtcEUzTGQ1RzA/view?usp=sharing
Nobody knows my problem? More details? plz help
@ductoan0295 Were you able to solve the "write partition" thing?
No i cannot fix this. I think the only way to fix is replacement of the eMMC chip on mainboard (this mean dead sdcard cause the error). I've not tried because i can't buy the same chip in my country and not sure if the replacement will work or not.
Related
I swear I looked far and wide but this appears to be different from the usual "bootloop" questions. Apologies if not.
I flashed a bad ROM, and the device won't boot all the way into the OS. Just sits at the ROM logo for hours.
I previously installed FFF 1.4, so I do get the blue KindleFire logo momentarily, but any fastboot commands I try to send to it just come back with "waiting for device" and then "ERROR: Unable to create a plug-in (e00002be)". I've got TWRP installed and backups galore but I cant figure out how to get to it. I do have a fastboot cable.
Totally at a loss as to what to do. I feel like there's a really simple fix I'm missing, but I've poured through pages of Kindle Fire posts and everyone seems to be having a problem with the KindleFire logo screen and pre-getting all the way to recovery and ROMS installed.
Any help would be much appreciated dudes, you guys always get me sorted out. Thanks!
It sounds like you need the fastboot drivers loaded. Does it appear in device manager when it is plugged in and in fastboot mode?
It comes up under Other Devices: Kindle
Well, now I've got it coming up under Kindle Fire: Android ADB Composite Device. But at no point, apparently does it enter fastboot mode and I can't get any commands to work. Just scoots right through both KindleFire logos and then on to the ROM logo ad infinitum.
History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!
Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?
you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.
hey guys follow this youtube
managed to unbrick my phone
smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..
This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!
the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus
Hello, I make this post to tell what happened to me and not happen to anyone else, it turns out that I wanted to install a GSI room and instead of accessing it from the fastboot I decided to do it through the recovery of orenage fox, flash the image in the super partition (systen, vendor .... ) after that, not only did not turn on my phone but I got the following error in the recovery "unable to update logical partition /system root" and the same with the vendor ..., I switched to twrp and the same, finally I entered fastboot to try to flash the stock room and failure and now my phone does not enter fastboot or recovery, and when you turn it on it turns off immediately.
Will this problem be solved in the technical center?
Thanks in advance.
So, I installed TWRP on to my Note 10 5G, and I rooted it with magisk successfully. But then magisk could update the app to v24 but it couldn't update the root itself. So I downloaded magisk v24, changed it to magisk.zip (not .apk) and tried to boot into TWRP but (to me) it didn't seem to be booting into it. I tried `adb reboot recovery` and `fastboot reboot recovery` but it didn't seem to work... or maybe it did work but I didn't realise that it had to show that "bootloader unlocked" bootscreen before going into TWRP.
So anyways when I thought it didn't work I tried to reflash it so I did fastboot flash a couple times but I can't remember what partition (I should of just refollowed the tutorial I was watching) but it seemed to erase the whole SDCard and stop it from booting (well it did boot but then it'd shut off and try to boot again). From there I could only get into fastboot. So I downloaded some sort of boot.img and flashed it to boot partition but then I broke it more and now I can't even get into fastboot and it's stuck in this infinite loop where:
It'd show that "bootloader unlocked icon" boot screen, then a glitchy static bar would come across the bottom of the screen for like 4 seconds before shutting off and then going back to that "bootloader unlocked" screen.
I can't detect it with ADB now, or get into fastboot to recover it. I wish I was more patient for TWRP to load.
So, what can I do now?
Spoiler
I swear I have an update curse. The last time I updated something was my PC's bios and accidentally turned it off and corrupted it. I fear that something like that could of happened.
(I got a new Mac since then tho, which is what I'm writing this post on.)
I'll help you tomorrow. Do you have Camellian?. Is your Device based on Mediatek?