Hi
I would like to ask for some advice.
I've recently soft bricked my MI2S. I can boot to recovery (TWRP 2.8.1) and fastboot. The phone isn't recognised by Windows or Ubuntu, so I can't flash anything with fastboot. Actually, fastboot, adb or MiFlash don't detect the phone. I've tried to use a USB stick with an OTG cable, but TWRP doesn't detect the USB stick. If I boot to system, it stays on the MI logo (I can wait a full night, it won't change).
My question is, do I have a problem with my USB port? I'm equipped to solder a new one, if necessary. Or is my connection problem due to another reason? I wouldn't want to go through soldering if it is for nothing. Especially, when I started to mess up with the phone, it was locked with a different MI account (it was my wife's account, but it took me a few days to connect the dots together), and I couldn't connect with MiFlash, adb or fastboot either.
The steps I did to get it soft bricked:
Flashed TWRP 2.8.1 with fastboot
Rebooted to recovery
Rebooted to MIUI (a few times)
Attempted to flash TWRP 3.5.0 (my memory fails a bit there, I think I did it via fastboot)
The last didn't work because I'm still on TWRP 2.8.1
And I can't add any more zip file to flash via recovery, nor can I use adb sideload or flash with fastboot.
Any advice or comments are more than welcome. You may just have an idea that I didn't think of.
Regards
Matt
Quick update:
I don't know if you would agree, but I can't see my issue to be a software one (the device not being recognised)
I've ordered a USB port directly from China and I'll see if I can unbrick the phone from that point.
It's great that you can still access to recovery and fastboot.
First, I advice you to back up your data.
If you cannot use adb sideload or flash with fastboot.
Try in fastboot mode
- fastboot erase cache;
- fastboot erase system;
- fastboot erase userdata.
See if that can solve your issue.
Related
Anyone else have this problem?
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
CharliesTheMan said:
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
Click to expand...
Click to collapse
Pretty sure it is fastboot... You use the volume rocker to select recovery and hit the power button... It shows the Bootscreen but doesn't go any further than that.
Edit: it says in red FASTBOOT MODE.. When i select recovery it goes tot he google screen (witht he unlock icon) and doesn't go any further than that.
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
I'm having trouble too. I have it plugged in to my laptop. When I select "Recovery" and press Power, it just reboots, and then boots into Android.
No recovery.
So I'm gonna try TWRP..
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
so any solution at the same screen, same problem.
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
You want to be in the bootloader mode and select recovery. The trick is that to do that, you have to have your Asus USB cable connected to a live usb port when you do it, and it usually works if recovery isn't damaged.
And you can also use Wug's toolkit on the computer, or if you can boot the tablet, you can use goo manager to reboot to recovery, or the Trinity kernel app, or your rom's advanced power menu.
With the USB cable attached from the computer to tablet, here's what I did:
- Went to bootloader
- Did "fastboot erase recovery"
- Did "fastboot flash recovery IMG"
- Then boot to recovery manually from the device itself via volume buttons and Power
Hasn't failed me yet when trying out different recoveries. There was some issue a while back where you had to have the USB cable hooked to your computer and Nexus 7 in order to get to recovery. Not sure if the bug still exists, but it may be worth trying with the cable in.
Also you probably have to have an unlocked bootloader (lock at bottom of Google boot screen).
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
Thanks for that.
That worked for me
Does the USB port you're plugged into need to be a computer with the fastboot drivers already installed? My unit freezes up in bootloader every time I plug in any live USB cable, whether it's a computer or not. My recovery is fine, but with the bootloader constantly freezing I'm not able to install the N7 drivers on my computer, let alone input any fastboot commands. And no, I don't have access to the computer with the drivers already installed sadly.
Sent from my SGH-T989 using xda premium
Turn it off plug USB lead into PC/laptop and nexus hold volume up and down and turn it on, or it also works via my otg cable in my s3 also, its a bug..
Sent from my Nexus 7 using Tapatalk 2
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
sert00 said:
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
Click to expand...
Click to collapse
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
..
mvmacd said:
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
Click to expand...
Click to collapse
I did this and I still can't boot into recovery. The only way I can boot into recovery is if I use the fastboot command. The rom toolbox does not work for me.
similar problem
I have somewhat similar problem. Well, actually the problem is not very uncommon the way it looks, but usual solutions do not work.
Basically I have erased my old rom (rebooted to recovery from aokp menu) and erased my rom. I've tried mounting the device from the recovery mode, but it was not recognised on my PC. I assumed that this was an Win8 issue.
Once I've rebooted, I could no logger boot to recovery (after selecting recovery all I got was google logo). I've thought of flashing recovery via fastboot, but bootloader seams to freeze with usb cable in (no matter the cable) and resetting does not help (the way it helped others). Also I cannot fastboot at that time either as PC (neither win8 nor win7 machine can see the device).
Any ideas would be appreciated.
When the bootloader freezes with the usb cable plugged into a PC, it is a driver issue. Uninstall and reinstall the drivers. I have experienced this on a win7 x64 system.
It isn't a driver issue as the same thing happens when connecting to a charger and not the PC.
It happens on mine as well.
Well it wouldn't crash with wall charger if it was a PC driver issue.
In either case, I've actually figured out what's the problem. It seems that usb connector is not very reliable. If the it usb connection is poor, the bootloader crashes. To avoid this issue you have to bend the cable towards the screen to ensure the proper connection. It load that way just fine.
Edit: or not... probably bending just removed the connection completely...
Edit2: did not figure out what was the problem, but after playing around some more, the phone has popped up in computer manager and I was able to continue from there. After flashing the recovery (twm -> cwm), the bootloader un-froze as well.
Hi,
I rooted my mojo and then i installed twrp, then i installed cyanogenmod 12 and i tryed to reboot but when i pressed reboot TWRP asked "Your device isnt rooted want to root? but i presed no accidentaly (one of the worst mistakes of my life) and it stucked on bootloop and i tryed to reboot it on recovery mode to fix it using fastboot but it stucks on rebooting... (on the screen of terminal on my laptop) and i waited for a long long time, but nothing happened.
Please help!
Did you use towelroot, or the USB-USB cable?
If towelroot, then you may not be able to recover the device without using a USB-USB cable. The fastboot prevents the MOJO from being bricked, because you can always re-flash it using the USB-USB method, even if the OS installed isn't working.
If you have a USB-USB cable, you need to use that to boot from TWRP again (or re-flash it to the fastboot if it won't work) and then re-wipe the MOJO and re-install CM12 + the Gapps, then re-boot the system as per the instructions. If you have any questions regarding clarification of the procedure, feel free to ask.
I used towelroot to root it and i tried fastboot to reboot it but on windows 10 don't detect it and on mac os X el capitan stucks on rebooting.....
The Windows driver should be in the same folder as fastboot. I was using Windows 7 and it didn't detect either, but the driver makes it detect correctly.
http://i.imgur.com/8O5FDgB.jpg
Windows 10 cant, but i will try with an windows 7 old (not so old) laptop
https://drive.google.com/file/d/0B3gWeKqMPK8HcjE2ZC1hOU0yUDA/view?usp=sharing
hi again, i tried with the windows 7 laptop but now fastboot dont detect it,i installed the drivers succesfully but fastboot dont detects it
https://drive.google.com/file/d/0B3gWeKqMPK8HajBUNlMyZEcxV1k/view?usp=sharing
SOLVED: the reason it didnt detected it its because on windows you needed to turn on testdriversigning and install the .inf file included on the MoDaCo mod zip on the windows.drivers and after that you needed to write "fastboot -i 0x0738 <command> , "0x0738" is the mojo´s usb vendor so it sended the commands directly to the mojo.
The problem was that the data and system partitions were corrupted so i reformated them with "fastboot -i 0x0738 erase system -w", the -w is for erase userdata. After that i booted the twrp recovery by "fastboot -i 0x738 boot <recovery.img path>" and from twrp i reinstalled android and it worked!
Hello All
I've rooted and installed TWRP recovery. And accidently wiped all partitions (system, data, caches...). Currently no OS installed.
Tried installing Cyanogen mods and also default ROMs via TWRP but getting error saying
====
Unknown command "screenshot"
E: Unable to mount /spare
====
Also tried flashing default ROMs...same error . No luck.
Tried wiping all partitions again.
connected to my linux lap
Device is connected and listed while running command "lsusb". (USB data connection working)
But not detecting under adb devices also not shown under fastboot mode. (So no luck to flash via PC).
All forums saying "check usb debugging" to show under adb devices. How can I ..if there is no ROM
Also TWRP is restarting after some time.
-------------------*******helppp******************************
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Elokwentnyemu said:
Hi,
I have the same problem, few post below.
During my searching I found this post, but I get error during
fastboot erase spare
It hard to say what wrong is with this partition.
Maybe you will be have more luck
Click to expand...
Click to collapse
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
antoponline said:
In my case, the phone is not listed under fastboot devices But it's connected to computer in fastboot mode and we can see the device is listed when command lsusb is executed.
Click to expand...
Click to collapse
I checked on Manjaro and my phone is present under fastboot. Try reinstall drivers or use other PC to connect by fastboot.
so sad for both of you guys i've already encountered this before try this any of these.
- use adb sideload via TWRP using stock firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip
- if you have a back up restore it, then boot to fastboot and flash the fastboot, boot and recovery of this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip then boot to recovery and side again using this firmware.
- try this link if it's work http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
sorry guys i forgot how i managed to solve this i will update this thread. just always remember use always this firmware UL-ASUS_T00F-WW-2.22.40.54-user.zip and back your current rom even if it's stock or custom this is most important. if you can access bootloader just do the flashing fastboot, boot and recovery this would be easy if you can access bootloader.
Hey guys!
It's been a while since I've used my Mi A1. I turned it back on after a very long time and it was stuck on the android screen as if there was nothing to boot into so I tried booting into my recovery but there was nothing there either. I figured I probably formatted some stuff a while ago but I don't really remember what happened. Anyways, here's what I did next:
I could only boot into fastboot so I ran the command
Code:
fastboot boot path/to/tissot/twrp.img
but that didn't work.
So I flash the img to boot and tried rebooting to recovery but I was stuck on the android logo and again. I then again had to wait for my battery to run out before I could do anything else (I couldn't enter fastboot again. Only works when the phone is off for some reason)
I then erased the system partition using fastboot and tried booting into the recovery again but no luck. Can someone help me?
I know I messed up... big time. Someone save me
EDIT: Some more details
I tried two recoveries. The Pitch Black on XDA and also the standard "twrp-3.3.1-0-tissot.img" but had the same issue of getting stuck at the splash screen for both.
Also, I remember using Android 10 before all this happened.
EDIT 2: I ran the following commands:
Code:
fastboot set_active a
Code:
fastboot flash boot path/to/tissot/twrp.img
And I can now use the button combination to boot into recovery but I still get stuck on the splash screen
Hi,
have you fixed it? I face the same/similar issue, that I stuck at twrp splash screen after booting in twrp with fastboot
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I have erased/formatted everything (userdata, cache, boot) and also tried to reflash the original rom with mi flash tool, but without success.
Any ideas?
MBR might be creating problem , try clean install with mi flash tool with official ROM .
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
xiaomiA1 said:
@MIN313 Thanks for your response.
I tried to flash the official rom with the flash tool ( see here: https://forum.xda-developers.com/t/mi-a1-flash-sec-error.4139573/#_=_ ) .
Click to expand...
Click to collapse
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
MIN313 said:
Does MiFlash recognize your phone? If not, try instaling ADB drivers nd disable driver enforcment,
To kick device out of diagnostic mode and into QDLoader you will need either:
1) A "deep flash" cable
2) Take the phone apart and bridge test points
There are guides online for both, you can Google. You can make deep flash cable yourself fairly easily with a spare USB cable. Testpoint location is found easily via Google and can be bridged with tweezers or small flat-head screw driver.
Click to expand...
Click to collapse
If Phone Showing Charging Only and Can't Even Transfer Data , Not Detected on Pc then will have to do EDL flash
My phone is recognized by MiFlash when I enter the fastboot mode
It is also shown with
Code:
fastboot devices
and I can boot into TWRP, but it stucks in splash screen of twrp.
Code:
fastboot boot twrp-3.5.2_9-0-tissot.img
I also tried older versions of twrp for tissot.
smilar issue, following attempts:
flashed with MiFlash, with or without EDL
flashed installing image with twrp
flashing after wiping dalwik, data, system and so on
flashed several type of ROM: official from xiaomi, crdroid, pixel, lineage
phone only booting with twrp (if installed) or stuck on mi logo
Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!
Hello, I have exactly the same issue.
I would be really grateful if someone could help us.
i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv
Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(
what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea
Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.
i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC