Good, I've already gone through everything with the phone and no problems, always solve it either by entering fastboot or recovery! Yesterday I went to bed with the phone running, just a problem with installing large games, and today after charging all night does not turn on the screen does not come out the logo of miui or go into recovery or fastboot. I do not know what to do!!! Someone has passed him or knows how to fix it!
Now that:
In my myflash comes the following:
getvar product 2 & 1 findstr
In fastboot I think because I do not see anything but it makes like it takes figure the following:
List of devices attached
3e91a87a unauthorized
This adb server's $ADB_VENDOR_KEYS is not set
Please!!! Thanksssss
Related
Hello xperia community.
I am facing a problem with unlocking the boot loader of my ZU and fastboot. On my mac, I downloaded the art bundle and unzipped it. In the unzipped folder, i headed to sdk>platform-tools and then I dragged the fastboot app into my terminal. Now I was in fast boot. So I typed:
Last login: Sat Nov 15 11:16:44 on ttys000
Adrians-MacBook-Air-2:~ adrian$ /Users/adrian/Downloads/adt-bundle-mac-x86_64-20140702/sdk/platform-tools/fastboot fastboot devices
< waiting for device >
ERROR: Unable to create a plug-in (e00002be)
and then I tried it with sudo
Last login: Sat Nov 15 11:08:24 on ttys000
Adrians-MacBook-Air-2:~ adrian$ /Users/adrian/Downloads/adt-bundle-mac-x86_64-20140702/sdk/platform-tools/fastboot sudo fastboot devices
< waiting for device >
ERROR: Unable to create a plug-in (e00002be)
still the same error
I also noticed that I dont get a purple light with my volume up, Androxydes Flashtool always recognizes my phone in Flash Mode?
------
Please Help
------
*edit: tried it with restart, unplug etc. , still nothing... / in service menue, footlocker unlock is allowed
Okay, so you've tried the most basic thing like holding VOL UP when you connect your Ultra to your Mac? Does the LED turn blue? If yes, you're in fastboot mode.
Skip the whole Mac thing and borrow a Windows computer and use that instead. Stuff will work better there.
It didnt turn blue up and down key both green for just a sec and then no light
cippus said:
It didnt turn blue up and down key both green for just a sec and then no light
Click to expand...
Click to collapse
I don't know a thing about mac os but this may be worth a look.
http://forum.xda-developers.com/showthread.php?t=2564453
Here is another one that you can try also.
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
So I basically just need my fastboot back...
I think my access to THW fastboot is broken.
Is there a way, the bootloader or the thing which controls the fb, to reset it?
cippus said:
So I basically just need my fastboot back...
I think my access to THW fastboot is broken.
Is there a way, the bootloader or the thing which controls the fb, to reset it?
Click to expand...
Click to collapse
You say you need your fastboot "back" but has it ever worked before? Did you try either of the methods to install adb and fastboot that I linked?
Yeah i tried it with the Sony tutorial.... It didnt work
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
privateriem said:
The facts:
-I'm an idiot and I dun ****ed up.
-I'm a fool to believe I could power my way through learning how to flash roms and unlock the bootloader unofficially.
About the Device:
1: Kenzo.
2: I can access Fastboot (PWR +Volume down)
3: When I try to boot the device, the Mi logo is visible for 3 seconds, disappears, reappears again and then then the phone turns off.
3.a: When connected to my computer via the official cable, the screen remains pure black and the red light blinks repeatedly, as if in EDL. In device manager, the phone reads as "Qualcomm HS-USB Diagnostics 900E (COM10)
4:XiaoMIFlash and MiFlash tool both do not detect the phone when I hit refresh (which is why I can't seem to fix it)
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
6: I don't believe I can access recovery (PWR+Volume UP)
7: Could not unlock bootloader officially due to getting stuck at 50% with "Not connected to Mi Phone" error.
I ****ed up. Bad. I really need help. I tried following many tutorials, but all of them assume that the device can be detected by MiFlash, but mine can't.
Please, I desperately need help. I'm new to android and if I can somehow manage to get this fixed, I'm keeping MIUI, to hell with custom roms, as long as it works.
Please help, I'm at my wit's end.
PS: If the only possible way to fix it is test point method, please post the name of all tools I need, so I can go and buy them.
PSS: Device bricked after attempting unofficial unlock. I never got to the "OEM unlock" part, it bricked before that.
PSSS: Before bricking, I was using China Dev rom. As to try and avoid bricking the device, I switched using miflash to kenzo_global_images_V8.0.5.0.LHOMIDG_20160805.0000.29_5.1_global.
Then, following the unofficial unlock tutorial, I tried flashing the same rom with the modified prog_emmc_firehose_8976_ddr, and it bricked there.
Click to expand...
Click to collapse
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : https://www.androidfilehost.com/?fid=24591000424940129
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
HParra97 said:
Have your phone boot into fastboot. Connect your phone, run adb and check if it receives commands by using : "fastboot devices". If it returns a value then your phone is detected on your computer. Next, download this file : snip
Now, extract the zip file and open Reboot.bat . This will open cmd and press the enter key.
Your phone is now booted into EDL mode. Now MiFlash should detect your phone and you can flash a stock image from the Miui forum. Probably best to to flash stable ROM (fastboot ROM).
Click to expand...
Click to collapse
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
privateriem said:
5: Putting the device in Fastboot and attempting to send any command through CMD/ADB results in either nothing happening, or <waiting for device> showing up, and then nothing else happens. (This used to work before)
So far, I've managed to successfully boot into EDL by unplugging the battery and USB. Now, I just need to figure out why Miflash is giving me a "System can't find path specified"
Click to expand...
Click to collapse
Read this thread : http://en.miui.com/thread-91415-1-1.html
Make sure that you've disabled driver verification signature, your path to the image folder does not contain any spaces, and also the flash all data except data and storage option.
so my phone got the bootloop problem, a few days ago and after hours of research i found a thread here with a kernl to solve the problem, so i went ahead with the guide and had to unlock the bootloader, i tried LG's site but it seems the site is faulty and i cant get past the log in screen, so i found another guide using fastboot, but fastboot wont show the device, i tried "adb devices" showed nothing, "fastboot devices" also yielded the same result, even though i hear a sound when i connect the phone in fastboot mode, some other research lead me to believe that there is a conflict in drivers because in the device manager it shows android with a triangle next to it, i tried different drivers, nothing, i tried using Microsoft update online but it found nothing, can anyone provide help? cant go to lg bcause i got the phone used, and done have the money to get a new one, so if i could this one back up and running it would be a dream, thanks for any help in advance!
i managed to delete twrp and when i did then it shows that the system has been destroyed and after restart it is stuck on
fastboot windows. i tried to connect it with my pc so i could install flash rom but it doesnt show up on pc after connecting to usb.
i dont understand what to do next... helppppppppppppppppppppppppp
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
twistyplain said:
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
Click to expand...
Click to collapse
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
AjTheKiller1 said:
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
Click to expand...
Click to collapse
Have you ever had your phone detected by your pc in fastboot mode? And if you connect it to the pc, does the computer play the hardware detected sound?
You need to rule out a driver issue. I'm not the only other person to get the "system has been destroyed" message and people usually get out of it. I don't know why yours is so problematic.
Had you successfully unlocked bootloader?
The Good old "System has been destroyed" Message. Well, This is terrible This should not happen in the first place. I assume it happened Because you wiped data and then deleted twrp. But If you want help you have to specify how exactly did you " Delete TWRP" What steps did you follow to Delete it. None the less the best bet on getting your device back would be to go to the nearest service center. Pretend you did nothing and maybe they will say you got a bad update.
Hey, sorry if i bother or im posting where im not supposed to.
I have an amazfit stratos that has worked perfectly for years, but suddenly it got brick two weeks ago, I've trying to fix it lately, but I have no clue on what shpul I do.
I have installed the Adb libraries, Minimal Adb and fastboot and followed tutorial of some threads but I always get the same error, when I put the watch in fastboot mode it is recognized by the computer on the device manager, but whenever I try to execute the adb commands, it says that theres no device attached, I dont think I have a problem with adb libraries because it can recognize my other devices.
I've installed the "TOOL ALL IN ONE" and Huami AMAZFIT Tool of mauronofrio to try to install a ROM or at least get an idea of what could be happening, both of the Apps say that the device is in fastboot mode, but none of them can recognize the device, also when i click on check bootloader status it says its locked and whenever I try to unlock it the watch would restart getting stuck into the logo so the app throws an error.
I dont know if my problem is that the bootloader is locked or if Im doing something wrong.
Id take whatever advice, thanks