So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.
raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...
Try the Marshall London Bootloader Interface driver maybe?
nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.
Related
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
not sure if you found out already but
all you have t do is go to mount and mount what uou need
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
device manager, right click phone, update drivers, browse computer, let me pick from a list, unclick show compatible hardware, and find LGE or LG and pick the adb driver
Yes, I solved it. Got the drivers fixed.
Fun fact : If your G2 is just getting stuck at boot, turn it off for an over and try again. I stupidly flashed a zip containing a recovery using Flashify and not the boot.img and I got stuck in Fastboot mode or it'd just stuck at the boot animation. I had given up and decided to go back to stock, wiping all my photos. But thankfully the stock flash got stuck because I am using a custom kernal. I turned it off, watched some tv and tried again. Booted right back into the rom. Flashed a proper recovery using adb, got into TWRP, reflashed my rom and didn't lose any data. @autoprime got me through the process via IRC so big kudos to him!
Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.
Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk
Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?
No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.
colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk
Hello,
i delete the System and Data on my LeEco Le Pro3.
TWRP is installed.
Can i flash a rom with an usb flash drive in TWRP or fastboot?
greeting gizez
Boot into TWRP and use MTP to transfer ROM file from your PC to Phone. Then flash the ROM.
I have this problem, but I can't see the phone when connected to a PC. adb sideload doesn't work (adb devices doesn't find anything). Do I need to install driver for the phone? I originally used fastboot to unlock the bootloader and flashed TWRP, then installed LineageOS and gapps just fine. I then proceeded to wipe system in TWRP (I was trying to get back to new phone setup so I can transfer stuff from old phone, which I skipped the first time).
Any idea how to get around this? I tried plugging in pen drive through an micro USB OTG and a usb-c to micro usb adapter, but it's not recognized in TWRP, either. Would very much appreciate any help!
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
marik1 said:
[...]
Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system.
[...]
Click to expand...
Click to collapse
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
marik1 said:
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
Click to expand...
Click to collapse
Thanks, but unfortunately no luck. Both adb sideload and adb push said error - device '(null)' not found. It seems like the PC is not recognizing the phone. I checked device manager on the PC, it showed LEX727. I right-click and had it install the driver. It says driver successfully installed. Then device manager showed MTP device with a !. I again tried having driver installed, but this time it doesn't find any driver.
I'm at my wit's end... Any more suggestion?
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
marik1 said:
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
Click to expand...
Click to collapse
Actually, the problem is solved, by using another PC. This one showed LEX727 in windows explorer as soon as i plug in the phonr (in twrp). I was able to drag and drop the zip files to the phone and go on my merry way. Now back in business!
I want to unroot my phone and I did manage to flash stock recovery.
But now I want to flash stock firmware through adb sideload.
But when I typ adb devices it does not recognize my device and when I type the sideload command, it says error: device not found.
I am using minimal adb fastboot version 1.4.2.
I already tried to use all the different kinds of drivers @ device manager
I am really out of idea's and hope someone here knows what to do.
Edit:
When I use TWRP recovery and I use sideload, adb can recognize my device (and fastboot can also recognize my device).
So only through stock recovery adb cannot recognize my device.
And I remember that USB debugging is off, I do not know if that has to do something with this?
vldholy said:
When I use TWRP recovery and I use sideload, adb can recognize my device (and fastboot can also recognize my device).
So only through stock recovery adb cannot recognize my device.
And I remember that USB debugging is off, I do not know if that has to do something with this?
Click to expand...
Click to collapse
For the stock recovery, Side load Works.
But only Side load, not "adb devices".
After you have selected Side load from stock recovery,
(Boot in stock recovery,
Select your language, -> install from usb -> yes )
Only after this, your device will show in "adb devices"
It will show as Side load device. Then Side load as usual., It will work.
P.S. - USB debugging is not checked in recovery mode.
pollob666 said:
For the stock recovery, Side load Works.
But only Side load, not "adb devices".
After you have selected Side load from stock recovery,
(Boot in stock recovery,
Select your language, -> install from usb -> yes )
Only after this, your device will show in "adb devices"
It will show as Side load device. Then Side load as usual., It will work.
P.S. - USB debugging is not checked in recovery mode.
Click to expand...
Click to collapse
Sorry for late reply!
I did what you said, but I get this error:
error: device '(null)' not found
And when I select install from usb -> yes, Windows notify that there is a problem with the device and cannot recognize it.
What drivers must be installed, OnePlus drivers and ADB drivers?
Does someone know how to fix it?
vldholy said:
Does someone know how to fix it?
Click to expand...
Click to collapse
The problem is stock recovery that you Install does not work well in windows 10
1 Boot in bootloader install TWRP again here
2 Reboot in TWRP Recovery
3 Wipe> Advance Wipe> Select Dalvik & Cache System & Data> Swipe to Wipe
4 Reboot in TWRP Recovery Transfer OOS 4.5.8 Full Rom Zip to the device over MTP
5 Install Menu> Select OOS 4.5.8 Full Rom Zip> Swipe to Flash
6 Reboot System
Now you are in full stock OOS
If you restart now in stock recovery you will see that sideload will work
Adb sideload with stock recovery not work in Windows 10, if you use Windows 7, you'll find that it work well.
The problem is stock recovery from the official site
This OP5_recovery.img
If you are in TWRP and install OOS stock rom sideload will work in windows 10
Had driver issues to what j did was with twrp installed I transferred the Oxygenos rom to internal storage installed it from twrp and then put the OnePlus recovery back on
Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.