i cant unlock my mtk tablet its stuck on ... how can i fix this? i tried it on linux on windows 7 and windows 8.1 with diferent drivers
my tablet says that it is secure how can i remove that secure thing i cant install anything cwm or twrp
Related
Hi All
I got myself a Mediapad 10 FHD two weeks ago, 1.2MHz 1GB Ram, 8GB Rom, Wifi.
It looks like I cannot get root nor custom recovery installed on the device. I have tried all I could find so far, without any luck.
What I have tried so far is:
Hi Suite Setup v1.7.00.1006
Hi Suite Setup v1.8.10.1506
custom USB driver from Team Android
standard Linux ADB driver (which work on my Nexus 4)
Windows XP in a virtual box running the driver above
standalone Windows XP computer running this drivers
toolboxes for ADB / root
Genotools v2.0
Root with Restore by Bin4ry22
auto recovery installer for huawei mediapad
root with repair
Genotools seems to work for some people, no luck here.
When I follow the steps for root manually from a Linux console I can move all the needed files onto the device but cannot change permissions or dont have access to the desired folders.
The weird thing is that that I cant access the device when in recovery at all, while access with ADB debugging is ok.
adb reboot bootloader boots the device into recovery
afterwards fastboot devices doesnt show anything
fastboot flash recovery cwm.img just waits for the device forever
Anybody have an idea what else I can try?
Recoveries in that installer are ONLY for 7" mediapad (hws7300)
At first sorry for my bad english -_-
I have LG P670 v20i eur, i have unlocked bootloader and rooted. But, if i boot to bootloader mode when i want to flash recovery, my pc wont recognize the phone. And it doing a strange thing. Connects and disconnects and connects and disconnects....doing classic windows sound around. I hit the device manager and found unrecognized device and install fastboot drivers manualy, and it sasy that i have last drivers sinstalled but windows sill disconnecting my phone. I can do it in windows 8.1 and on win XP. Than i install cwm based recovery with lg recovery installer (for locked BL). Is there any possible way to install "artas182x" recovery without bootloader ? If i make flashable zip with "artas182x" recovery and flash with recovery for lock BL ?
Thanks for answer, for now i'm very sad :/
Edit: friend tell me that app "Flashify" can do this, and i have installed unofficial CM11 for now but, in bootloader my pc still doing same error
I wanted to reflash Android after unsuccessful Xposed install and accidentally used the wrong file in the Manufacturing Flash Tool.
I now have no Android, no Windows -- just BIOS and fastboot are functional. When it boots normally all I see is a UEFI shell with the list of partitions.
I've tried using MFT with the correct file and it didn't help.
I think I need to set up proper (dual-boot) partitions thru fastboot and only then try flashing Android again. Can anyone please help?
Android flashed just fine once I switched from a Windows XP running in a VM to a laptop running Windows 7 64bit.
I'm having problems rolling over the Windows image, I'm guessing it's because I've messed up the partition table -- it can't find the drive with the images now. Anyone had that?
I want to flash TWRP as my recovery on my MiPad 2, yet after I enter the TWRP mode and connect it to a macOS or Windows 10, fastboot won't be able to list it as a device (`fastboot devices`).
I check the device manager in Windows 10, MiPad 2 shows up in unknown device as mipad with a yellow triangular warning sign. I installed the official XiaoMiFlash thingy from their Chinese forum, yet it doesn't help at all. Do anyone have a driver for MiPad 2's fastboot mode? P.S., the tablet does show up under Windows when booting normally as a media device.
Hello,
Testing Windows on my test Poco F1 after running the windows installer my fastboot does not work anymore.
Windows and MIUI are loading fine, but if i boot to bootloader the phone freeze on POCO logo, in recovery works (miui recovery) i can reinstall miui if i put the device in "mi assistant" in recovery, but the fastboot does not want to start anymore.
I wonder if anyone here know which partition was modified by the WIndows installer, or what was modified that damaged only fastboot mode?
I tried to use MiFlash in EDL mode, but my notebook USB seems to have issues, after finds the right COM port MiFlash say that the hello packet was missed....
Best regards,
Marc
What do you mean by testing windows
Bobmarley2022 said:
What do you mean by testing windows
Click to expand...
Click to collapse
I mean i have installed Windows 10, by testing i mean i am testing some EFI drivers, I created a USB stick with Windows 10 for ARM64 and installed windows, the installer performed some changes to the phone and i wonder if anyone here know what can be changed to brick only fastboot.
serdeliuk said:
I mean i have installed Windows 10, by testing i mean i am testing some EFI drivers, I created a USB stick with Windows 10 for ARM64 and installed windows, the installer performed some changes to the phone and i wonder if anyone here know what can be changed to brick only fastboot.
Click to expand...
Click to collapse
Use mi flash
Bobmarley2022 said:
Use mi flash
Click to expand...
Click to collapse
Unfortunately miflash gives error, say that missed hello packet.
But my question is about what the installer changed that broke the fastboot, i manually created the required partitions and normally nothing else was touched, yet fastboot is not working, but only fastboot mode was damaged