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.
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)
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
Hi all,
I have a rooted oneplus X with CM13 installed together with cyanogenmod recovery.
I update CM nightly build through the cyanogen update utility and then my phone would not boot.
I can boot to recovery mode and my phone is detected as unauthorized.
I can boot in fastboot mode but the device is not detected (I checked I had the correct drivers).
I then tried to sideload Oneplus ROM and CM13 ROM but it stops during the process. (device is recognized by adb as sideload).
Any ideas of what I could try ?
After a few hours I solved the issue by disabling windows 10 driver signature verification and selecting manually the Oneplus X USB driver. I was then able to flash TWRP in fastboot mode.
I have a nokia 1 TA 1066 currently on android 10 go
I want to downgrade to android 9 or 8.1
I have the SPTool scatter file and zip ready.
But SPTool just sits there doing nothing.
My device is detected in fastboot when I run
Code:
fastboot devices
command.
I have all the drivers as mentioned on the internet (see screenshots).
I'm on windows 10 1909, with driver signature verification turned off
Any help or pointers is appreciated.
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