i installed corvus os on Xiaomi Mi A3. After the process is completed i rebooted my phone and its not starting. no power on (my battery was 100% when i installed corvus os)
cant just turn on the phone
is the phone hard bricked.
or how can i fix it
Hardbricked means a hardware component no longer is working ( e.g. power button is broken ).
My guess is that the operating system you flashed or the installed software is corrupted, what means the phone got softbricked.
jwoegerbauer said:
Hardbricked means a hardware component no longer is working ( e.g. power button is broken ).
My guess is that the operating system you flashed or the installed software is corrupted, what means the phone got softbricked.
Click to expand...
Click to collapse
Ok thank you for the info
How do you think if its soft bricked could be started again atleast on fastboot
and i dont think its ard bricked because when i hold my power button after 5-8 seconds i can see my phone connected in the pc but only in device manager
i think this could maybe help me for something to fix it
When in Windows's Device Manager under tab Portable Devices phone is listed that simply means phone is connected in USB-MTP mode.
You can check whether phone is accessible by means of Fastboot running these commands - one by one - in Windows CMD prompt
Code:
fastboot devices
fastboot getvar all
jwoegerbauer said:
When in Windows's Device Manager under tab Portable Devices phone is listed that simply means phone is connected in USB-MTP mode.
You can check whether phone is accessible by means of Fastboot running these commands - one by one - in Windows CMD prompt
Code:
fastboot devices
fastboot getvar all
Click to expand...
Click to collapse
i checked but its not showing the device also i can see that my phone is connected by the icon at there but still the problem persists
it maybe a unsupported rom that i installed.
i tried for adb as well but no devices found
As I can see you're proud owner of a softbricked phone, what is neither accessible via Fastboot nor ADB.
My recommendation: Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
As I can see you're proud owner of a softbricked phone, what is neither accessible via Fastboot nor ADB.
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
ok Thank you for your suggestions
Related
Since Xiaomi and Micro$oft released a public ROM of Windows 10 Mobile for Mi4, the curiosity drives me to try it. But I felt so uncomfortable after successfully installed win10 on my mi4.
So I decided go back to Android roms. But sh*t happened - my mi4 got bricked during the flashing.
Phone won't boot with black screen and no boot options. Holding any buttons (including power button + volume down more than 2 minutes) won't work.
The pc can not recognize a USB device after it is plugged in (in both Windows XP and Windows 8.1).
Then I plug it into my Mac OS X with a VirtualBox of Windows 7 OS inside.
The USB devices shows a unknown device of id 05C6:F006.
I did a lot of googling of 05c6:f006 which seems to be 05c6:9008 and something Qualcomm related.
And the most important thing is to make my computer to recognize it.
So things I need to figure out:
Is my phone hardware damaged or software damaged (hard bricked or soft bricked)?
Do I need to disassemble it?
How can I make my pc to recognize it ?
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
My phone was recognized as a USB input device, VID_05C6&PID_F006, seems to be Qualcomm_QHSUSB 9008 related
I have exacly the same probleme here, do you have find any solution ?
If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works
xiaomi mi4 lte not turn on
darkmaster566 said:
If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works
Click to expand...
Click to collapse
Good evening. I have a problem with my Xiaomi 4 lte, after trying to return from 6 to android 4.4 android after this tutorial : ]Now the phone does not start, if you stick to connect to PC loaded or red LED flashes once and the computer sounds like something I plugged in but not afiseaja nimicc device. He is charged for 24 hours and not start and MIFLASH program is not found
Mi4w hard brick
darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
Hey! I had bymistakely flashed wrong partition and tried flash in miii 6.3.3 ROM....
Now my device is bricked....Whenever i connect to charger the red light blinks....And when connected to pc....The red light comes.....But no drivers come on my pc...Means its to recognising.....Can you help me please????
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Smallsmx3 said:
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Click to expand...
Click to collapse
Update: Looks like I'm good to go. Phone is connected again. B Now when I try to unlock my bootloader I can't flash the unlock token I get an t error cannot load unlock_token.bin
Got it all figured out!
Smallsmx3 said:
Got it all figured out!
Click to expand...
Click to collapse
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Arr6 said:
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Click to expand...
Click to collapse
Honestly I was typing in adb devices instead of fastboot devices. So I think my computer was detecting it. I did reinstall drivers that I got from the OnePlus site. I made allot of dumb errors
I was having some issues with installing a factory update on my Pixel 2, and tried using fastboot to switch the boot slot to slot B. Now I'm unable to access the phone via USB cable because adb does not see my device. The phone isn't even recognised in Device Manager anymore and nothing I do seems to fix that, including different cables and different PCs.
In bootloader mode, I can see:
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: Slot Unbootable: Load Error
Any help would be appreciated. If I could just get Device Manager or adb to see my phone again, that would be a fix.
Tersnaus said:
I was having some issues with installing a factory update on my Pixel 2, and tried using fastboot to switch the boot slot to slot B. Now I'm unable to access the phone via USB cable because adb does not see my device. The phone isn't even recognised in Device Manager anymore and nothing I do seems to fix that, including different cables and different PCs.
In bootloader mode, I can see:
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: unlocked
ERROR: Slot Unbootable: Load Error
Any help would be appreciated. If I could just get Device Manager or adb to see my phone again, that would be a fix.
Click to expand...
Click to collapse
Hook your device up to your PC and open adb/fastboot whilst in bootloader screen and then hold down the power button until the phone vibrates and check if your pc has recognised it. It may well take many attempts but I revived mine from a similar scenario doing the above. If you search the forum for slot unbootable you will find a thread for exactly this issue also.
Good luck
Junglism93 said:
Hook your device up to your PC and open adb/fastboot whilst in bootloader screen and then hold down the power button until the phone vibrates and check if your pc has recognised it. It may well take many attempts but I revived mine from a similar scenario doing the above. If you search the forum for slot unbootable you will find a thread for exactly this issue also.
Click to expand...
Click to collapse
Thanks for the advice - I managed to fix the problem in just this way, although I needed to do it on a friend's machine that was running Linux. Windows was hopeless. I was quite sure at that moment that I was going to need a new phone.
Tersnaus said:
Thanks for the advice - I managed to fix the problem in just this way, although I needed to do it on a friend's machine that was running Linux. Windows was hopeless. I was quite sure at that moment that I was going to need a new phone.
Click to expand...
Click to collapse
At least your back up and running mate, that's the main thing. Yeah, I know what you mean, i thought mine was a paperweight the first time I ran into this problem!
hey, my motorola one vision got this message displaying " your device has failed verification and may not work properly" that i rescued it and replaced firmware with motorola assistant software then after a while it dead again and now hardbricked it is not not even recognized by my pc before it showed at least exynos driver in ports now it displays not recognized, I tried giving it to service center but they returned it and told they can't fix it connsider going come other center...., so is there anything i could do to get it recognized by my pc..?
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
if it is soft bricked at least it should show the processor connected.., bt in my case it just connects and not turning fastboot or cant even do blank flash
jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized
Re-flashing phone's Stock ROM never is done
Ammar595 said:
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized by Fastboot.
Click to expand...
Click to collapse
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
jwoegerbauer said:
Re-flashing phone's Stock ROM never is done
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
Click to expand...
Click to collapse
yes tried this too still not recoganized..
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
so what should i do now..?
jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
this is what its showing and phone is completly dead like a brick..
Delete this USB device from within Windows' Device Manager. Re-install the "Android USB Driver".
jwoegerbauer said:
Delete this USB device from within Windows' Device Manager.
Click to expand...
Click to collapse
yes i did that too, stilll not working....
Ammar595 said:
so what should i do now..?
Click to expand...
Click to collapse
Does this work?
Code:
adb devices
jwoegerbauer said:
Does this work?
Code:
adb devices
Click to expand...
Click to collapse
no..... the only thing working is that it shows not recoganized
We could have saved ourselves all this back and forth if this had been known from the start.
jwoegerbauer said:
We could have saved ourselves all this back and forth if this had been known from the start.
Click to expand...
Click to collapse
so there's nothing i could do now...?
Ammar595 said:
so there's nothing i could do now...?
Click to expand...
Click to collapse
my sdcard reader also show that i think thats normal
ineedroot69 said:
my sdcard reader also show that i think thats normal
Click to expand...
Click to collapse
what is normal....? my phone is entirely dead, it isn't responding al it does is shows not recognized
when i connects it to my pc, ya maybe that's normal, bt am asking for solution not a compliment
I corrupted my phone's root/system/etc files and when I restarted it, it wouldn't turn on and got stuck on the realme logo. i hold my phone vol+ and - and power key and when the realme logo comes up, i release the power key, i think download mode opens, but it usb device is faulty for 1-2 seconds and disappears immediately, meanwhile in device manager it shows unknown device for 1-2 seconds and disappears. After 10-15 seconds there is a usb connection sound but nothing happens. I can send adb commands but I have to confirm the confirmation window but I cant.
Please help me, how can I fix it?
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Renate said:
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Click to expand...
Click to collapse
Yes, I get the unauthorized message as below. If I can somehow authorize it, I will be able to enter fastboot mode and flash the stock rom.
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Okay, I'm trying
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
mvikrant97 said:
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
Click to expand...
Click to collapse
I updated with Driver Booster, no luck.
I only tried the front USB ports, do I need the back ones? There are 2 2.0 and 1 3.0 port on the front
The computer is new so I don't think it's defective, the phone is charging and I was using it before it went brick.
I also modified the boot file to install a new GSI and used the following guide.
Spoiler
First, you need to unlock fastbootd:
1. Download the stock ROM version 91: Download and extract the .pac file Link
2. Install the SPD research tool and drivers: GDrive
3. Open it
4. Click on the single gear icon
5. Select the .pac file of the stock rom
6. Wait until it loads
7. Click on the two gear icon
8. Find BOOT in the list
9. Right-click on the path next to it
10. Download here and select boot_r1.img
11. Click OK and then click the arrow icon
12. Turn off your phone
13. Press and hold Power + VolumeDown until you see the text "Downloading"
14. Release the buttons after seeing
15. Wait until you see the text "Passed"
16. Click on the Stop icon, disconnect your phone and turn it on
[/ISPOILER]
@leanord Can you help me?
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Renate said:
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Click to expand...
Click to collapse
I don't fully understand your question, but I have the stock recovery, I didn't install TWRP, and I installed dotOS 5.2 as GSI. I think I corrupted the fastboot, download mode boot files in the root files. I will take it to the service center, but if you have a solution, you can write, I don't want to give money.
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Renate said:
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Click to expand...
Click to collapse
It may have been disabled or because I corrupted system files.
Wanted? I came, to flash the phone, you do not need to press anything except the volume keys, the power button is only a catalyst, you need to hold it down until the screen goes out, and then just Keep the volume - and flash as usual, the main thing is to keep it immediately plugged into the PC with a ready-made flasher
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Luuukie said:
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Click to expand...
Click to collapse
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
leanord said:
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
Click to expand...
Click to collapse
SP Flash Tool doesn't see my device so I can't flash it. If you mean Fastboot, I can't get into it.
By the way, that font that's showing up in my UsbLog is UGLY.
I readjusted things, you can download a new copy that is prettier.
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Renate said:
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Click to expand...
Click to collapse
I'm sorry, I don't know that much. But if you tell me the steps how to do it, I can do it.
@leanord when installing GSI, I flashed boot_r1.img from your Realme C21Y GSI installation guide, did you disable fastboot or something?