Blinking teamwin-screen - can't get access with ADB - Huawei Ascend P6, Mate

Hey,
after flashing Omni-Re ROM my p6 is stuck in a loop. Entering TWRP it stucks on the blinking teamwin screen, booting it normally, it stucks on the boot-logo.
While hanging on teamwin i cannot get connection with ADB.
While hanging on boot-logo "adb devices" shows me either "unauthorized" ord "offline"
I tried fastboot recovery twrp.img - without success.
Is there any chance to reflash the recovery?
PS: windows device manager shows me either an "Alcatel ADB Device" (while stucking on TW) or "Android Adapter ADB Interface" (while on boot-logo).
I tried, installed, uninstalled all huawei drivers i could find on the web - it's frustrating...
Mates, any help strongly appreciated
Thank you so much,
Grobie
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

can you go inside twrp and set something?
maybe you could load a different custom rom (as zip-file) through adb-sideload feature inside twrp..
Gesendet von meinem HUAWEI P7-L10 B852

If only I could...
No, i cannot - that's the issue. Entering Recovery is not possible, as the phone stucks on the TWRP logo.
GrĂ¼sse,
Grobie

Boot logo means fastboot mode not adb. Thats why adb commands dont work there. Try detecting it with "fastboot devices" command. If it shows up you can try to flash a rexovery.
Sent from my SM-G850F

Tried that, without success. fastboot devices shows nothing.

grobie.der.reisende said:
Tried that, without success. fastboot devices shows nothing.
Click to expand...
Click to collapse
Are you sure that usb drivers are properly installed?
Sent from my SM-G850F

No, i'm not
Pls. read my first post. Which drivers did you install and as what exactly is your P6 shown in the device manager?

grobie.der.reisende said:
No, i'm not
Pls. read my first post. Which drivers did you install and as what exactly is your P6 shown in the device manager?
Click to expand...
Click to collapse
Get HiSuite and while in fastboot mode try to run it.
Sent from my SM-G850F

I installed HiSuite hundreds of times already. Allways the same result.
How do I get into fastboot mode?

Powering on the phone while holding volume down button too.
Sent from my SM-G850F

Power + Vol down boots into bootloop. It just shows the boot logo.
Power + both vol buttons enters recovery, but stucks on blinking teamwin logo - as described above.

grobie.der.reisende said:
Power + Vol down boots into bootloop. It just shows the boot logo.
Power + both vol buttons enters recovery, but stucks on blinking teamwin logo - as described above.
Click to expand...
Click to collapse
At huawei devices being stuck on boot logo doesnt mean its in a bootloop. That is actually the way huawei made it to recognise if its in fastboot mode or not. Unless it restarts all the time, like in boot logo shows up and then disapears soon after and so on.
Sent from my SM-G850F

So that means it could be in fastboot mode anyway? I will check that out.
Which drivers do you recommend to install for the P6 under Win7? Just HiSuite or additional ones?

Exactly. As for the drivers hisuite should be enough even though win 7 can find drivers online too. And if after installing them it doesnt work the it may need a restart on the pc before it can recognise the device. And if it does with "fastboot devices" command you should be able to see the phone. It will be in some question marks and other signs but thats ok.
Sent from my SM-G850F

Does the p6 show some "fastboot" logo or sth. like that or just the boot logo?
My Redmi Note shows "fastboot" with a nice logo.

Nothing like that just the logo.
Sent from my SM-G850F

What does your Win device manager show when you connect your p6 in fastboot mode?
I re-installed HiSuite. Just HiSuite, no additional drivers. The phone is now showed as a Android Phone ->
Android Adapter ADB Interface. So far, so good.
adb devices shows the the phone, but "unauthorized". I googeled that issue. Most guys solved it by checking or unchecking USB debugging... But that's no way here, as there is no more OS installed and entering TWRP also doesn't work.
So - what else can i do? How can i authorize the p6 (or the PC) to be able to work with adb/fastboot?
desperately,
Grobie

Okay Fellas, didn't solve the problem yet, but at least - now I know WHAT THE PROBLEM IS
I can boot the phone into fastmode. fastboot or adb -devices shows the phone.
BUT: it's unauthorized
So, how do I manage to skip that authorization? I just need to reflash TWRP... the rest ist "kindergarden"
Pls...

Try to flash stock rom. It might get you up and running from there.
Sent from my SM-G850F

tileeq said:
Try to flash stock rom. It might get you up and running from there.
Sent from my SM-G850F
Click to expand...
Click to collapse
are you kidding? :laugh:

Related

Serious bricked Galaxy Nexus

I tried unlocking bootloader and root using Superboot. I got into Google boot loop then went to download mode and tried to restore to factory using odin. Phone connected went all the way to end and failed. Now I can not get into recovery or download mode. I just have yellow triangle screen. I cant use adb because laptop does not recognize device. what am I missing. Is there another file to download and use with odin?
So can you not get into the factory bootloader?
No I can not. All I get is yellow triangle between a phone icon and computer icon. When this happened on droid I could always odin a recovery folder. But I when I try that method I keep getting a failed error message
When I first rooted my PC was having trouble recognizing the phone as well. Make sure you have ALL of the drivers installed. The drivers for adb in recovery/boot are different that the drivers the GNex uses once boot into the OS.
Once it's plugged in, you have to actually go into Device Manager and find the "unrecognized device", then you select from a list of drivers. it will be called Android ADB or something along those lines.
you should be using fastboot not adb
mickrg123 said:
I tried unlocking bootloader and root using Superboot. I got into Google boot loop then went to download mode and tried to restore to factory using odin. Phone connected went all the way to end and failed. Now I can not get into recovery or download mode. I just have yellow triangle screen. I cant use adb because laptop does not recognize device. what am I missing. Is there another file to download and use with odin?
Click to expand...
Click to collapse
If you get a Yellow Triangle you are not bricked. Plugin phone and reload fastboot drivers. Try ODIN again or try to flash a custom recovery via fastboot.
I say "bricked" when I can't do anything with phone. I can not get into fastboot from yellow triangle screen.
mickrg123 said:
I say "bricked" when I can't do anything with phone. I can not get into fastboot from yellow triangle screen.
Click to expand...
Click to collapse
Fastboot IS the yellow triangle screen. If fastboot doesn't see any devices, you have a driver issue. Go into device manager and look for devices without proper drivers loaded (usually a yellow exclamation mark on the device)
Ok thx, Fastboot does not see any devices in device manager. I do have a second GNex when I connect it to computer it is recognized. How do I get drivers from fastboot?
mickrg123 said:
Ok thx, Fastboot does not see any devices in device manager. I do have a second GNex when I connect it to computer it is recognized. How do I get drivers from fastboot?
Click to expand...
Click to collapse
I hope all goes well for you. Try installed PDANET on the working Nexus, and get the drivers from their PC software.
http://droidmodderx.com/galaxynexus/unbrick-unroot-unlock-restore-your-galaxy-nexus-to-factory
boom
Samsuck said:
I hope all goes well for you. Try installed PDANET on the working Nexus, and get the drivers from their PC software.
Click to expand...
Click to collapse
+1 THIS ^^^^^
I do have drivers from pdanet installed. But this phone will not connect to laptop. I thought Fastboot screen was when you hold down vol up and down and power at same time.
I haven't encountered a yellow triangle screen you spoke of. Neither the fasboot or download mode should have that. Can you take a pic and post it?
Sent from my Galaxy Nexus using XDA App
I can't get past first adb command, says device not found
Here is screen I cant get past. (I don't think this is fastboot is it) And the odin error screen. Fyi nexus is just a sticker not on phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No that is not fast boot. Can you get into fast boot with Power, Vol +, Vol- ?
Sent from my Galaxy Nexus using XDA App
That's what I thought, someone had told me yellow triangle IS fastboot. I cannot get to any other screen!
I have had this screen on my Samsung Charge all I had to do was load stock .tar through odin, but I keep getting error message with this phone.
Are you able to get into Fastboot ( Power, Vol+, Vol-) or download mode (Power, Vol-) at all?
Sent from my Galaxy Nexus using XDA App
No I can not get to any other screen. Holding vol up, down and power, or holding vol down and power, all take me to same screen.

Sprint LG G2 Brick - Not showing in device manager - Download mode working!

Hey guys, my friend recently bought an LG G2 on Sprint, but switched carriers to T-Mobile. He rooted his phone successfully, and tried to install custom recovery but downloaded some app that screwed up his phone (not completely sure what happened... he told me he installed a flashing app that flashed recovery but long story short, his phone is in a boot loop.) I can access download mode, and fastboot. When I connect the phone to the computer, my Windows 8.1 Laptop, nothing pops up. I already installed ADB and Fastboot, and when I put the phone into fastboot mode and plug it into the computer, it is recognized but keeps saying "oops!" connection to USB failed trying again.... fastboot ready! etc. etc. I installed the LG Flash tool but the computer won't recognize my device in device manager! I'm really frustrated why it won't recognize it. It shows nothing except ACER Fastboot Device. I just want it to recognize it in download mode so i can flash it back to stock with the LG Flash tool.
Pls halp.
I had to download lg universal drivers for my laptop to recognize my phone in download mode give that a try
im in the same boat as the op. i have tried to install various drivers. im able to get into download mode but no communication with the comp. i try going to recovery but it is gonna and i see some type of fastboot. unsure where to go from here...
This is exactly what i did
Www.rwilco12.com/forum/showthread.php?tid=96
My phone wasnt recognized by laptop until i was in download mode with flash tool running
not finding the ports under device manager anywhere.
Hi
I also have issue with don't recognized device in device manager. Did you solve this issue?
P.S. I have another G2 with normal running android. This G2 has normaly recognized in device manager. So problem not in cable or usb port's.
kdm212 said:
not finding the ports under device manager anywhere.
Click to expand...
Click to collapse
does the computer make a noise when you plug in the device? Also are you sure your in download mode ? (not just the dots) If you have just the dots, then go info fastboot mode and flash both the boot.img and laf.img then reboot into download mode and see if it works
I just put my g2 in download mode and pluged her up. in device manager it poped up under lge android modem, in the modem section of device manager.
Look there first. Then you will have to change the port to 41 so the flash tool will work
If you have qpst it will Tell you what port
Sent from my LG-LS980 using XDA Free mobile app
jcwxguy said:
does the computer make a noise when you plug in the device? Also are you sure your in download mode ? (not just the dots) If you have just the dots, then go info fastboot mode and flash both the boot.img and laf.img then reboot into download mode and see if it works
Click to expand...
Click to collapse
Have the same problem as the OP.
PC don't make any noise.
Yes sure, have a download mode screen on display.
Can't access to fast boot:
1) When i press Vol Up + plug the cable, have a download mode, but PC show nothing in device manager.
Stuck on this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) When i press Vol Down + power, have a factory hard reset screen which stuck if i agreed to factory reset.
3) When i press Vol up + Vol down + power, have a Hardware key control mode screen.
DEFNUB said:
I just put my g2 in download mode and pluged her up. in device manager it poped up under lge android modem, in the modem section of device manager.
Look there first. Then you will have to change the port to 41 so the flash tool will work
If you have qpst it will Tell you what port
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
OP says that device is not recognized in device manager!
demos98 said:
Have the same problem as the OP.
PC don't make any noise.
Yes sure, have a download mode screen on display.
Can't access to fast boot:
1) When i press Vol Up + plug the cable, have a download mode, but PC show nothing in device manager.
Stuck on this
View attachment 2912813
2) When i press Vol Down + power, have a factory hard reset screen which stuck if i agreed to factory reset.
3) When i press Vol up + Vol down + power, have a Hardware key control mode screen.
Click to expand...
Click to collapse
what i had to do when this happened to me, was swap out the device at sprint (had insurance), without insurance you can swap it for $75ish plus tax or if its still under warranty, go through LG
Could also try this thread :
http://forum.xda-developers.com/showthread.php?t=2582142

The current image(boot/recovery) have been destroyed and can not boot.

Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I faced a similar problem described in this topic https://forum.xda-developers.com/re...-3-pro-boot-recovery-destroyed-t3938481/page3
When you turn on the phone an error pops up for 20 seconds and then phone reboots and everything goes in a circle.
If you press the power button once, the reboot process stops and the phone turns off.
I tried to enter fastboot mode by pressing the power + volume button -
But I didn't succeed.
Can you tell me what I'm doing wrong ?
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
kkffiirr said:
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
Click to expand...
Click to collapse
Thanks for the answer, but unfortunately due to this error fastboot does not load.
If you can tell me how I can flash the phone I will be very grateful.
I would not like to contact an unofficial service...
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
kkffiirr said:
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
Click to expand...
Click to collapse
Before lock, I installed TWRP, but idk if it's still there.
UMF cable will help me ?
Me i too i got same your problem i bricked my realme x2 i still didnt find the solution to flash it again
Maybe contact service center
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medusa Box; they seem to have underground connections with manufactors, they may provide a solution too.
EDIT. Thanks to the clarification from @T1MOXA, you can enter EDL mode by holding VolUp and VolDown and plugging the switched off phone to a computer.
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
yakovpol said:
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medisa Box; they seem to have underground connections with manufactors, they may provide a solution too.
Click to expand...
Click to collapse
I've tried this option before, but it led me to the same error screen.
I turned off the phone with a single press of the power button, then pressed all the buttons at the same time.
razu031 said:
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
Click to expand...
Click to collapse
I just got the same error.
When you connect the cable, the phone boots with the same error.
narshi shukla said:
Maybe contact service center
Click to expand...
Click to collapse
Unofficial ?
They too bad in my country.
They can easily make it worse.
I can buy a UMF cable, but whether it will help me I do not know.
What do you think ?
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
T1MOXA said:
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
Click to expand...
Click to collapse
Most phones will be able to flash in this mode using qfil tool,
But first you need to find necessary firmware, idk if stock rom downloaded from official site will work or not, maybe fastboot one will work.
This mode is called emergency download mode (edl).
But pls do a lil research as its a newly launched device and you can easily mess it up.
BTW exact same error(boot recovery destroyed) is common error on realme Phones and it can be fixed by flashing vbmeta.img using fastboot.
See attached image for reference only
The 1kb vbmeta is modified to bypass boot verification.
Idk if such vbmeta is available for x2.
If not then flashing stock vbmeta might work.
T1MOXA said:
Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
Click to expand...
Click to collapse
I have the same problem. On 4pda there is a firmware for MsmDownload Tool and the tool itself, but it requires a username and password. Are there alternative options to restore your phone?
Problem: The current image have been destroyed and can not boot
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Iamsanthoshravi said:
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Click to expand...
Click to collapse
Look friend i had the same problem and i fix it u have to download the firmware RMX1991 not ozp file then u have to buy the password of the firmware there are sone website they ask you to install teamviewer because thet gonna flash your phone online ok friend i did as i mentioned and i fixed so there is no other way to fix it i cant put the link of firmwares because last time xda warned me
I got same
Hey bro can you fix your phone?
Today I experience same.
What can I do now?

Stuck in a bootloop but can't go into recovery and phone isn't recognized by pc.

Ok, so this is my first phone without a removable battery so very new in terms of fixing bootloops. I just have to deplete the battery because I can't turn off the phone in said bootloop, and also when I plug the charger it goes into loop again...
So anyways, it's very sketchy but 1 out of 20 power-ons I can get it into bootloader/fastboot? but I can't get adb or MiFlash tool to recognize the phone. So for now it's a brick. Is there any way to fix this? My phone has unlocked bootloader and had pixel experience 9, and it was years ago since I did all the romming so I don't have the old files nor the old drivers because of fresh Windows install.
Looking forward for your answers.
How did you get in bootloop in the first place? Did you try to boot to the recovery using volume up and power button?
Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.
Fedegblack said:
Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.
Click to expand...
Click to collapse
When the phone is turned off press first the volume up and while holding it press the power button. After phone vibrates release the power button but still keep the volume up button pressed and wait until twrp starts. If it gets stuck again tell where exactly.
I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?
Fedegblack said:
I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?
Click to expand...
Click to collapse
If USB debugging is working you can try to flash twrp or even fastboot rom with MiFlash.
Ok, tried to flash twrp but it says write protected, so I did "fastboot boot twrp.img" but freezes in the same place as my old twrp. Seems likely I have to flash stock now.
Edit: On second thought I might be able to do something else now, even if it freezes before the twrp menu it's showing with "adb devices" instead of "fastboot devices" so I will try dirty flashing what I think is the same rom as before.
Also, if it's likely this issue with twrp I will be sad. I have no idea when my internal memory got encrypted since it was one of the first things I didn't want when I first romed this.
Welp, after days of trying to enter fastboot again I find myself with this problem.
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried fastboot -w or flashing twrp and orangefox recoveries but same ol' same ol'. Write protection error, it's likely to be hardware issues, but I'm open to suggestions.
Your Odyssey might have an end!
Try to flash the factory rom instead, the one that came with the device, not the most recent one!
I'll guarantee it will work!
I also would try OrangeFox recovery if I was you... way better then twrp. Both my devices have OF as recovery.
Note 5 Pro and Note 8T. My willow have Carbon OS on it but I'm not using it since it only serves as a backup device, in worst case scenario...

HELP NEEDED - Having issues with pc connection/downloadmode/recoverymode

Device Name: Sony Xperia XA2
Device ID: H3113
Internal Storage: 32 GB
Software Version: Android 8.0.0
What i want to do: Install LineageOS 19.1 on the phone.
How far i got: I'f been trying to follow the instructions here https://wiki.lineageos.org/devices/pioneer/install
However after 2 hours and no progress i decided to ask on XDA...
On the PC i installed platform-tools_r33.0.2 for windows and UniversalAdbDriverSetup
Then i added this path %USERPROFILE%\adb-fastboot\platform-tools to "Environment Variables"
On the Phone i have USB Debugging Enabled also OEM and Bootloader are both unlocked.
I am ready to install LineageOS however when i connect the Phone to the PC and check device manager there is a yellow marker, something is not right.
The Phone asked me what shall be transfered and i selected data, still the PC doesnt seem to "like" the phone.
I have installed LineageOS on a samsung device before and there only difference i can spot now is that for samsung i installed usb drivers on the pc, however for sony i cannot find usb drivers for the Xperia XA2. Do i need these and where do i get them??
I have noticed another "issue" when i try to boot the phone in recovery by pressing Volume Down + Power, the phone vibrates once and the screen goes on fully white with the sony logo.
After that nothing happens i continue to press Volume Down + Power and everything repeats, phone reboots, vibrates once and shows sony logo, this will go forever untill i stop pressing Volume Down + Power and the Phone now boots normally to system. It seems i cannot boot into recoverymode?
The phone is acting wired, when i press Volume Up and connect it to the usb/power cable sometimes it does nothing and shows the battery % while sometimes it boots to system and sometimes i managed to get into download/fastboot mode where ican see a blue light but the screen remains off.
I was going to install TWRP with ADB but since the phone isn't showing on the PC i cannot continue, i have no idea what to do... cant be so hard can it? So many people flashed lineage on this phone so there really should be a way... i hope someone can help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi, I believe I have the same issue.
When pressing "volume up" (for bootloader) while connecting the USB cable I get an "Android" device without driver. I've tried several drivers without result. Emma sees the phone (but gives "device locked"), Windows sees the phone, adb sees the phone, but when in bootloader... no result.
Any assistance is welcome.
WIndows 10 64
Xperia XA2 (H3113)
You have to know how your device is presenting: ABD? Fastboot? Bootloader?
You need to look in Device Manager and identify devices that are not happy.
Try to install a stock driver. If you can't, then identify the VID/PID of the device.
You may need to make a copy of the stock Google .inf file and make new entries for your device.
Then you can try to install that, although you'll have to use the procedure for unsigned drivers.
In any case, if things are not going right, don't bother with long adb or fastboot commands. Just try.
Code:
C:\>adb devices
...
C:\>fastboot devices
...
Thanks for the reply,
While stock android is started
ADB gives:
List of devices attached
CQ3001ERRN device
Fastboot devices: No result
Reboot phone in flash mode (Volume down): Emma recognizes phone(but locked)
Reboot phone in recovery (Volume up): Unknown Android device.
When trying to install the Google driver (or any other related) I just get: could not find the driver for your device. In my view this has nothing to do with unsigned (message is different).
Uninstalling "Android" and re-installing it, does not help, picking it out of the list of available drivers does not help.
"You may need to make a copy of the stock Google .inf file and make new entries for your device."
How would one proceed with this, keeping in mind that when the phone is booted using stock ROM it is fully recognized as a Xperia XA2?
Any advice is welcome
A device needs drivers for every single different mode that it can be in.
For the thing that you can't load drivers on, you need to get the VID/PID and if there is an MI.
Just go to DeviceManager > MysteryDevice > Properties > Details > Device instance path
From DM it's not possible to see if this is ADB or Fastboot but the driver is the same.
Copy over the Google .inf file to your own.
Add what you found in DM to look just like the others.
Note that you need to enter the same line twice in the NTx86 and NTamd64 sections.
When you try to install a driver using your .inf it will obviously be unsigned.
Do the restart PC with allow unsigned and install.
@Renate You have made me a happy man.
I'm looking at a Xperia with LineageOS running smoothly
Thank you for your instructions

Categories

Resources