Question The phone does not see the PC in bootloader mode - OnePlus Nord CE 5G

There are several devices, all EU, all with the same problem, are seen by adb but are not seen in the bootloader by a computer. If you run the adb reboot fastboot command in the adb, you will get into a strange half-repair half-fastboot mode, and the flash oem unlock command works there, but it falls out with an error. At the same time, everything is enabled in the development settings. If you run the adb reboot bootloader command through the adb, we get into the standard bootloader, but the computer does not react to this in any way, firewood from the site off the vanka is downloaded. Vanka 8ya is lying around, connects without any problems. I thought well, there is a forum member Mamay72 he has India and he unlocked the bootloader. I took advantage of the restoration of the brick, installed the firmware India, now tel India. But nothing has changed, oddly enough, the firmware has become DA, but NFC works. And it also does not seem to be a computer (there is no connection sound at all, nor any device in the dispatcher. There are thoughts at least where to dig while I monitor 4pda, but it's also deaf there

Related

[Q] Nexus i9020T stuck on unlock bootloader

I have an i9020T that is stuck in the Google boot loop. I was given this phone in this state so I am not sure how it happened. I can volume+ and power and get to fastboot. When I do a fastboot oem unlock, the screen changes on the phone to confirm I want to unlock the bootloader. I use volume+ to move to Yes then press the power button to select.
The PC terminal shows the little dots as if it is working on it. After 9 hours, the phone's screen remains on the Unlock Bootloader? screen and the PC terminal has Failed with too many links.
I have tried with the Android ADB Interface driver, the Android Bootloader Interface driver, and the Samsung drivers. I have removed the drivers and downloaded PDAnet, put the phone in fastboot mode, connected to the pc and let PDAnet install the driver (although it cannot install PDAnet on the phone). All resulting in the same outcome.
If I type fastboot devices, it returns the serial number that is displayed on the phones fastboot screen. It will not fastboot oem unlock.
I have searched and read as much as I can find on this and other forums. It appears this has happened before but the threads I have found seem to stop without concluding if there is a solution or it's a lost cause.
Anyone have a solution to this? Or, is this phone just a brick?
This is the Nexus One forum, and you have the Nexus S device. I would suggest posting in the Nexus S forums, as you are likely to get someone more knowledgeable with your device.

Fast Boot

I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.

Can't Re-lock bootloader

I've been an android developers for years and years now and even have made my own ROMs, but this phone....this phone is testing me. I unlocked it months ago to install an original Android 11 ROM, but it was awful and lacked support for even the most basic functionality, so I flashed the stock image back. That alone was a nightmare and I don't remember how I managed it. That being said, the Asus Android 11 update is rolling out OTA and can be downloaded directly from their site. I downloaded it and put it in the root directory, where it is found on start-up, but when I tell it to install, it fails after a few seconds and doesn't give me any explanation for it. I thought it may be that the bootloader is unlocked, so I've been trying to re-lock it for weeks with no success. I managed to get the damn fastbootd mode recognised by my computer and it sees the phone, but when I give it any relock command I receive this error:
"FAILED (remote: Command not supported in default implementation)"​I have no clue what to make of that or what it even means. My only guess is that the commands I'm using aren't supported in the latest version of the tools. I've tried the following commands:
fastrboot oem asus-lock​
fastboot oem lock​
fastboot oem asus_csk_lk​
fastboot flashing lock​
fastboot oem relock (I don't think that's a real command, but I was irritated and figured it was worth a shot)​
I'm at a total loss. All I want is to get Android 11 to the damn thing and the OTA isn't coming through to my phone. The phone itself is an international model I bought from China back before it was released in the US. IDK if that's causing a problem, but at this point I'm out of ideas. I'd also note that normal fastboot, found by going to the bootloader instead of "adb reboot fastboot" doesn't even allow the computer to recognise the phone and when I try to install the fastboot driver via device manager, it outright refuses to install it. There's no apparent way to get it to install the driver anyway. I AM able to get it to install the driver and see the phone while in fastbootd mode.
Anyone got any ideas?
fastrboot oem asus-lock
This worked for me on tencent phone converted to ww firmware. I had no troubles with updating to 11 from 10 as well. I had also no troubles to flash raw firmware with bootloader unlocked.
Waiting now for new ww firmware as CN has been already released couple days ago.. If they didn't fix thing I'm annoyed with I going back to 10!
Try different cable. Had guy from reddit with same problem like yours and simple new cable sorted everything
fastboot oem asus_csk_lk should do it.
I think you may be in the wrong fastboot mode You need to be in the bootloader. Try powering off and boot with Vol UP + Power until you land on the bootloader page (don't navigate to Fastboot from the bootloader menu, just stay on the bootloader menu. Doing 'fastboot reboot bootloader' should also do the trick but suggest trying with the physical buttons.

Question no devices in fastboot after the oxygen 12 update

EDIT3:
Resolved! I changed the usb port on my computer... Weird problem as adb worked fine over the old port. What I say about having relocked the bootloader below is wrong. I just assumed I had because my system said so and I didn't see the scary letters at startup. Leaving this here in case it helps future idiots.
Excuse me if this is a dumb question. I'm not too familiar with how this is exactly supposed to work.
I tried to update and messed up (of course) so I had to do a full reset which relocked my bootloader. Now I have a locked device on the latest software but I can't see the device in with `fastboot devices` anymore. Thus I can't unlock the bootloader again.
I'm running the apt installed version of fastboot on ubuntu.
EDIT:
I did find the oem unlock toggle in settings but it's greyed out.
EDIT2:
`lsusb` is also recognizes nothing in when the device is in fastboot mode.

Help unbricking device

Ok just like many of us, I have had trouble getting fastboot to work on my ROG 2 even though ADB worked fine.
Well getting annoyed I couldnt use fastboot I tired to flash omnirom from TWRP. Well that has locked me out of anything besides fastboot. Recovery doenst work anymore, and of course cant get into rom.
Ive tried using many of the suggested ADB variants all without success. I am also using the side port on the device.
Any suggestions?
When trying on another computer I do get a the usb connection sound but even on this computer (old ADB) it doesnt show any devices in fastboot.
Is there anything Asus offers that would flash automatically from the bootloader or something?
The phone even shows up in device manager (as Android) but PS and CMD cant talk to the bootloader.
Bump

Categories

Resources