My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!
You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb
It's my first post on this forum, so I'm saying hello.
I've recently bought Nexus S which after turning on is stuck on Google logo, but I could enter fastboot and recovery. But it has locked bootloader. I tried unlocking it by "fastboot oem unlock" but it asks me if I'm sure and then i click yes it freezes (phone not fastboot). I tried it using different drivers, machines, operating systems, cables, but still nothing. Unbrick tool by AdamOutler says that "device not found". When trying to flash stock image by Odin on the phone there is message if I'm sure that I want to unlock bootloader but with nothing to choose, and after while it shows by red characters that system image was verified.
I don't know past of this phone. (I have no idea, which version of android was it running)
I'd be extremely helpful for any kind of advice.
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
meonit said:
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
Click to expand...
Click to collapse
If its stuck in Fastboot, you can fastboot flash the stock firmware for your device.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Don't worry dude, There is always a way.
meonit said:
Hi all android gurus, I have a little problem to which I wonder if there is a solution or not
I was given a oneplus 3 that I can keep if I can get it to work.
The guy had installed twrp and CM14.1
and then he doesn't know how but it's stuck in fastboot mode with locked bootloader.
trying to unlock via adb say it can't be done remotely.
All commands I tried say it's "not allowed remotely"
Windows device manager say it is an "android device"
Trying to boot to recovery or os doesn't work
both these options just give lines of text saying what don't work.
What do all you experts say, is there a way out of this, or should I throw the phone away?
He already bought a new phone so I guess it's mine to either fix or trash.
Click to expand...
Click to collapse
Try flashing a new recovery of your choice in Fastboot mode, but for flashing it first you have to unlock your Bootloader, which you can do it with the help of an Android-SDK package for your pc.
sanjeevikrishna said:
Try flashing a new recovery of your choice in Fastboot mode, but for flashing it first you have to unlock your Bootloader, which you can do it with the help of an Android-SDK package for your pc.
Click to expand...
Click to collapse
when I try to unlock bootloader i am getting:
FAILED (remote: oem unlock is not allowed)
meonit said:
when I try to unlock bootloader i am getting:
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Not all bootloader can be unlocked, and the ones that can be unlocked can't all unlock via Fastboot.
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
mark_at said:
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
Click to expand...
Click to collapse
Did you already try ro flash ramdisk and system sith stock images via fastboot?
alohahe3000 said:
Did you already try ro flash ramdisk and system sith stock images via fastboot?
Click to expand...
Click to collapse
I would flash anything ... if I could! That is my problem at the moment and I can not solve it.
When I start phone I get into Huawei eRecovery after two tries to boot > does not help!
When I connect to PC > phone gets not detected! (during boot try it gets connected shortly ... but then gets disconnected after some seconds, in between I can not get into phone via PC)
So when I would want to use fastboot .... not possible because of that issue. I tried to connect in fastboot mode ... but no difference. Actually I do not understand why I can not connect to PC anymore!
The only way I can imagine now is flash or update something via SD card. I tried with asian update.zip, but it will only go to 5% .... and then ends.
But to be honest ... I am not very optimistic about finding any solution. I think only some very smart pro from this site might have an idea. But not sure if these guys read questions about bootloops.
mark_at said:
Next try was to force the phone to update with SD card.
Click to expand...
Click to collapse
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
here the link to the stock ROM:
https://mega.nz/#!W9hjiTgZ!_ZGq7V83bkWPF_Ue7_c41wVXNrQ_YjnsQUxRS0_MevU
Taobaibai said:
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
Click to expand...
Click to collapse
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
mark_at said:
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
Click to expand...
Click to collapse
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image. Stock system.img download link can be found in AOSP thread, second post.
alohahe3000 said:
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image.
Click to expand...
Click to collapse
Exactly
alohahe3000 said:
Stock system.img download link can be found in AOSP thread, second post.
Click to expand...
Click to collapse
Or just use my link. I copied it from the AOSP Thread
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
mark_at said:
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
Click to expand...
Click to collapse
It wasn't so difficult.
Viel Spaß mit dem Smartphone!!!
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
mark_at said:
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
Click to expand...
Click to collapse
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
mark_at said:
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
Click to expand...
Click to collapse
Never ever relock bootloader untill you have a backup plan. We have dload method till emui 7 buut not sure on EMUI 8 so can't suggest you anything at the moment. Someone played with EMUI 8 can guide you through it.
I understand that I was not allowed to relock bootloader! I feel awful and stupid about it ... believe me!
I was able to erase FRP with HCU client from DC Phoenix.
After that I was in phone again
And afterwards I could open the bootloader again.
Halleluja!!
Thanks for everyone's help here ...
Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error