Related
Hi guys,
I had posted a brief thread a couple weeks ago stating that my Nexus 4 restarted by itself, and got stuck in the bootloader animation loop. I couldn't remember whether I had enabled USB debugging in my phone prior to it killing itself (not rooted, completely stock, did the OTA 4.4.3 update just a few days before my phone died, and phone's been out of warranty for quite a while now ).
So I installed the SDK developer tooklit, and followed instructions to set up ADB.
However, everytime I boot my nexus 4 into recovery mode/"safe" mode, I get the following screen ("Screenshot 1" below).
From there, when I boot into recovery mode, I get the following screen ("Screenshot 2").
Every time I connected my phone to my laptop (keep in mind that I cannot start it .. I always plug it in when I'm in "Screenshot 1" mode) and try to used "adb devices", I get the following cmd screen ("CMD ADB Devices" picture below). I've repeated this process and tried plugging the nexus in during various points in different "safe mode" options. Same result: nothing is detected.
So I got frustrated at trying to backup any data from my phone, and just chose the "wipe data/factory reset" option from the nexus recovery mode, and I got this screen ("Screenshot 3"). I've tried this several times, and I keep getting this screen.
So my nexus committed suicide, and I'm totally not sure what to do. I've been trying to learn how to use ADB etc for the past couple of days by scouring through the xda nexus 4 forums, but I'm still very much a n00b. Do you guys have any advice as to what I can do to get my nexus 4 back to a usable state again?
Things I've already tried (in order):
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
I also tried to ADB sideload a stock Nexus 4.4.3 factory image, but it is useless since my device won't even show up in CMD when i enter ADB devices.
However, the problem is that my nexus is never detected in CMD no matter what combination of things I tried, so I can't even do half of the things both of those thread instructions state.
I would greatly appreciate ANY ways to factory reset or flash working firmware on my phone! :highfive:
Edit: I reinstalled Android SDK, and connected my nexus to my laptop after entering fastboot ("safe" mode; volume down + power from phone off state), and I was able to get a slightly better looking CMD window when running ADB Devices command (See "CMD ADB Devices 2" picture). However, same problem as before, where my phone isn't even registering via ADB.
So again, your input would be tremendously appreciated.
If you boot in the bootloader (Volume- and Power) it's normal that you can't use adb. You have to use fastboot in the bootloader.
What is the output of fastboot devices?
Code:
fastboot devices
Have you already tried to flash the factory image or did this fail, too? You have to download the factory image from google, extract it and connect the phone in the bootloader/fastboot mode. Run the flash-all.bat then and it will reflash the stock rom. This will wipe your data, but I guess this shouldn't be a problem for you anymore because you already tried to do a factory reset!
If this worked, boot your phone and if it works fine, I would recommend to relock the bootloader (because it gets unlocked automatically if you flash the factory image and if you don't want to root/modify your phone in any way, your bootloader is usually locked):
Code:
fastboot oem lock
Try it and if there are any other problems or if it doesn't work, just ask again
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
From your description, it seems like TWRP was not installed correctly. But don't worry, on this phone you do not have to install the recovery to use it. You can boot straight into recovery from your PC while the phone is in 'fastboot' mode. The 'fastboot' mode is what you get when you do 'adb reboot bootloader'. The screen off, blue LED is signalling that the phone is ready for fastboot commands. You can then run:
Code:
fastboot boot <recovery image file>
The phone should load and run the recovery.
Please note that adb will not see your device while it is in fastboot mode. Likewise, fastboot does not work while the phone is accessible through adb. adb support comes from the ROM, but TWRP also supports adb, so you can also use adb while in TWRP.
Rendini said:
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
Click to expand...
Click to collapse
Switch the phone off.
To enter fastboot mode: Hold the Volume UP and connect your phone to the USB port of your PC. The blue LED should come on and provided you have correctly installed drivers, you will be able to use fastboot commands.
To enter bootloader/flashmode: Hold Volume DOWN button and plug USB cable to your PC. Green LED should lit up and provided you have correctly installed the drivers, you will be able to use Flashtool, Emma or other software to flash firmware files.
FAILED (remote: Command not allowed)
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Rendini said:
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Click to expand...
Click to collapse
because your bootloader is not unlocked. you have set your bootloader to allow unlocking in developers options, but you need to do the actual unlock using "fastboot unlock" command. you need a unique unlock code from Sony Developers portal and keep in mind that unlocking your device irrevocably deletes DRM keys. it is advisable that you backup your DRM keys before unlocking your device.
the problem is not Sony device, but your unability to read and follow guides and get yourself informed and educated before you dive into trial and error, finaly blaming manufacturer for your own faults...
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
maltydog said:
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
Click to expand...
Click to collapse
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did to flash the stock firmware.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
maltydog said:
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
Click to expand...
Click to collapse
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
kbonnel said:
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
Click to expand...
Click to collapse
Thanks, I understand now. I can't start this tonight, but I will try the again next time I have time at the desktop.
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
damn it, I read somewhere that there are problems while using adb on the current official beta. There was a command for getting connection again. But I can't find it right now.
Just to be clear. when the phone is on, you enabled USB debugging and plugged in the USB cable and checked the tickbox before you granted debugging access, right? If you don't check the box, there is no access granted after a phone reboot.
take care, I had problems getting through the initial phone setup after I did a factory reset. The Oreo beta still has some hickups. I got it to work after a few reboots. Without finishing the intial phone setup you can't enable USB debugging, you know.
emowing said:
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
Click to expand...
Click to collapse
Good point on the driver, I wasn't even thinking about that.
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
maltydog said:
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
Click to expand...
Click to collapse
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes.
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks.
F
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks. Trying to reply and it doesn't appear. Edit: Sorry for the multiple posts,they all appeared at once.
Okay, I am back to this now, I had time today. I installed the windows drivers from the Essential site (I am running Windows 10 64 bit) and the device was recognized in fastboot devices. The phone wiped my data and restarted with a setup screen. So far, so good. So I shut down the phone again, turned it on again in fastboot mode, it was unlocked. I went into a CMD screen and typed fastboot devices, and the phone was still listed there. So I opened windows explorer and got to the folder where I had unpacked the image files and also copied the flashboot file. I right-clicked the flashall.bat file, chose run as administrator. When I did this, I got a bunch of error messages that went by so fast, they were practically impossible to read, though they seem to say something about files not found. I didn't see any log file in the folder, so I guess they are not created. I went back to the Essential site and downloaded the zip file with the correct image files again and tried a second time, with the same results. Anyway I have wiped my phone, but still have not reinstalled the Sprint nougat software I need on this phone. Any other suggestions?
Okay, I tried again, and I was able to read the error message. They all said cannot load "filename" no such file or directory. It sounds like some kind of path error, right? I expanded the file from the Essential download for build Build NMI81C into their own directory, a subdirectory of a library where I have been keeping various android files, and I copied the flashboot file into the same directory from the platform-tools download, but only that file. That seems to be what instructions specify.
Also, I notice on this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page3 it mentions also using the command "fastboot flashing unlock_critical" but I do not see that elsewhere.
I was able to get flashall to run using the command prompt instead of Windows Explorer. It seemed to run okay, except a couple of items cause me some concern.
I got a message "FAILED (remote: Flashing is not allowed for Critical Partitions)" for the abl.img file.
And the other command "Did you mean to fashboot format this ext4 partition".
Are either of these a problem?
Try running the commands one at a time. Open the flash-all.sh in a text editor and copy the commands.
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
maltydog said:
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
Click to expand...
Click to collapse
Did u not do the flashing unlock_critical?
Airwolf79 said:
Did u not do the flashing unlock_critical?
Click to expand...
Click to collapse
No I didn't. It was not mentioned by anyone but me in this thread until you did.
So far I have received no error messages since I did the reversion to stock. As I said,
I did get an update almost immediately.
I realize there are many other threads on this, bear with me please, I was not able to find a solution that works.
-display is broken, shows light but nothing else
-digitizer is 99%? broken, back and menu buttons work, there is some heptic feedback in upper part of the screen
-phone does not have a lock pattern or password, just swipe to unlock
-voice commands work
-phone was rooted a long time ago, I don't recall the mehod, I think the current OS is likely 4.4 but i'm not sure (is there a way to check)?
-I had a custom recovery on it which i think was CWM, again, not sure how to check this now
-I can install apps via web appstore
-At some point I installed a clockroot app (never worked) it's probably still on the phone
-I don't have OTG, ordered one
-I don't want to order a new digitizer
Here are somethings that kind of work and some that don't
-dr.fone shows a USB debug promt with instructions on how to accept the RSA key. I'm guessing USB debugging mode is on but it's not the same computer
-if I have the device in download mode, it is "sometimes" recognized by dr.fone, just says its in download mode and asks to reboot
-if I have the device in recovery mode (i think), it's not recognized at all, does not even show up in device manager
-when phone is just on, it's recognized by the computer, I can browse and backup files (i need to backup google auth app)
-with phone on, its recognized by windows and adb, adb says the device is not authorized.
-however adb does not recognize it if I boot into recovery
I think my best best to just to push the rsa key to the phone in recovery but I'm stuck because the phone is not recognized. I will try re-installing drivers next but I doubt this will help.
Lastly, I wasn't sure if I really do have CWM installed or its stock recovery. So I tried to flash CWM using Odin, with phone in download mode, recognized by Odin, the flash fails with an auth error, i'm reading that might mean the phone is not rooted which is 100% not the case here, maybe the rootclock app is doing something to it.
Any advice?
I'm starting to recall the rooting process a bit and I'm fairly sure I used safestrap method, as I was on 4.4.2-4 NJ something kitcat at the time. So I may not have CWM installed after all.
little bit of progress to report. I'm fairly certain i have safestrap recovery on this phone. So booting into recovery must have been bringing me to the safestrap screen that needs a screen tap to recovery or continue. If I hit power it reboots, if its only 2 options recovery or continue to normal boot, volume down move me to the other option, + power....now adb detects the phone! in sideload mode, lets see if I can do something with this, fingers crossed.
no luck, sideloading seems useless. How can i get myself into recovery!?
I think if I can push the adb rsa key I would be set to use one of the screen mirroring apps. How can I sideload it in?
Hello,
I'll try to be as specific as I can with my steps, so sorry If you don't like the format (or if its not even allowed), it's the best way I can explain step by step everything I did.
so... what do I want to do? Simply install some custom ROM to my SM-G570M so I can get rid of all the bloatware.
What's stopping me from doing it like I did it before? well...
>I flashed last version of TWRP via Odin
>Download mode (V- + Power + Home), Odin, the flash itself, everything went well, at least it appeared so
>When trying to load into it (V+ + Power + Home), I get a blue screen with android's logo and the words "Instaling system update"
>Immediately after I get another screen, this time android's logo is laying down, with a yellow ! above and the words "No command"
>Waiting a few seconds will get me to Android Recovery (the clasic move with Volume select with Power menu) with this in it:
#fail to open recovery_cause(No such file or directory)#
#Reboot recovery cause is [UNKNOWN]#
No support SINGLE-SKU
Click to expand...
Click to collapse
>I don't really know what to do, TWRP is nowhere to be seen
>I factory reset my phone (I don't really know why)
this is when things get interesting (that is, frustrating af)
>Phone boots fine, but OEM Unlock is not available. Not even greyed out, not even locked. It's not there at all
>I Google about it and try about... 50 different "solutions"
>Change system date to 7+ days to the past and trigger a false Update lookout, restart... nothing
>Triggered Update lookouts twice to make the sure the phone "knows" I searched for it 10 days ago and today... nothing
>I Literally write the steps down and start superpermutating that **** for around two hours... nothing
>Some other random non-Samsung, non-my-phone-specific "solutions"... nothing
>I come across adb (never used it before, never had to)
>It claimed I could do the OEM Unlock from Windows cmd
>I download adb 15 seconds installer, adb and fastboot drivers (both), I already had Samsung specific USB drivers, everything I need
>open CMD and do adb devices
>see my device there, nice
>adb reboot bootloader
>it boots there, n i c e
>fastboot devices
>... nothing
>fastboot device, maybe it was without the s
>stuck in waiting for device
>close everything, start again
>this time I do directly fastboot OEM unlock
>waiting for device
here I'll explain what I saw in Device Manager in all my adb odyssey:
Drivers are recognized in its normal state (that is, phone connected, no dev ****, just using it) with its full name (Samsung J5 Prime bla bla bla). Besides that I have some Samsung USB Drivers showing as modems? idk why. Once I change my phone state (let's say, I do adb reboot bootloader) drivers completely dissapear. Not even showing as *Unrecognized !*, no "Android Device 1.0". It's not there at all. Only thing I see is is the usb modems? drivers.
And yes, I used every USB Port I have, the only thing it changes is a #n besides the modem drivers.
I did read you have to install drivers twice? Once in each state? I did so and nothing.
I did "Added Legacy Hardware", where I saw different ones: ADB Interface, Samsung ADB Interface, Bootloader Interface, etc. Added every single one of them, updated them (I even got the Google USB thing, it did nothing) Sometimes it would bring some error (Can't do that right now or something like that), sometimes "It's already the best we have", but still not regognizing it in cmd fastboot devices.
I also superpermutated every step I could, even doing things completely illogical. I didn't care, I stayed awake until 9AM doing it... and nothing
I did noticed, at around 5am, half asleep, that my "bootloader" window (in my phone) was... not... really... a bootloader? whenever I would adb reboot bootloader it would get me to the same Download Mode I would get by pressing V- + Power + Home. I dismissed it, not only it was really late, It could have just been a normal misunderstanding... you know, language barriers and such (I'm not english native, so I'm constantly reading things in practically two languages, maybe *Bootloader* and the *DW Mode* where actually the same and people are arbitrarily obtuse, I thought) but it still bothers me nonetheless.
I also tried, since, you know, all I want is a custom ROM, to play with Recovery Mode adb sideload? But I would always get some error 21 and other I didn't really catch.
That's my problem(s). I don't really know what to do, and I don't want to wait seven days (or more, because I read some people waiting for weeks) to have the actual OEM Unlock option in my Dev Options.
Can I get a hand with this? Is my bootloader even active? Can I even do OEM unlock in my current state? did I miss a driver, among the 100+ I downloaded even from dubious webs? Never worked with phones before so I'm practically new on this, last time I touched android I did perfectly flash TWRP through Odin and did everything from there.
please
pretty please
Nezvanova said:
Hello,
I'll try to be as specific as I can with my steps, so sorry If you don't like the format (or if its not even allowed), it's the best way I can explain step by step everything I did.
so... what do I want to do? Simply install some custom ROM to my SM-G570M so I can get rid of all the bloatware.
What's stopping me from doing it like I did it before? well...
>I flashed last version of TWRP via Odin
>Download mode (V- + Power + Home), Odin, the flash itself, everything went well, at least it appeared so
>When trying to load into it (V+ + Power + Home), I get a blue screen with android's logo and the words "Instaling system update"
>Immediately after I get another screen, this time android's logo is laying down, with a yellow ! above and the words "No command"
>Waiting a few seconds will get me to Android Recovery (the clasic move with Volume select with Power menu) with this in it:
>I don't really know what to do, TWRP is nowhere to be seen
>I factory reset my phone (I don't really know why)
this is when things get interesting (that is, frustrating af)
>Phone boots fine, but OEM Unlock is not available. Not even greyed out, not even locked. It's not there at all
>I Google about it and try about... 50 different "solutions"
>Change system date to 7+ days to the past and trigger a false Update lookout, restart... nothing
>Triggered Update lookouts twice to make the sure the phone "knows" I searched for it 10 days ago and today... nothing
>I Literally write the steps down and start superpermutating that **** for around two hours... nothing
>Some other random non-Samsung, non-my-phone-specific "solutions"... nothing
>I come across adb (never used it before, never had to)
>It claimed I could do the OEM Unlock from Windows cmd
>I download adb 15 seconds installer, adb and fastboot drivers (both), I already had Samsung specific USB drivers, everything I need
>open CMD and do adb devices
>see my device there, nice
>adb reboot bootloader
>it boots there, n i c e
>fastboot devices
>... nothing
>fastboot device, maybe it was without the s
>stuck in waiting for device
>close everything, start again
>this time I do directly fastboot OEM unlock
>waiting for device
here I'll explain what I saw in Device Manager in all my adb odyssey:
Drivers are recognized in its normal state (that is, phone connected, no dev ****, just using it) with its full name (Samsung J5 Prime bla bla bla). Besides that I have some Samsung USB Drivers showing as modems? idk why. Once I change my phone state (let's say, I do adb reboot bootloader) drivers completely dissapear. Not even showing as *Unrecognized !*, no "Android Device 1.0". It's not there at all. Only thing I see is is the usb modems? drivers.
And yes, I used every USB Port I have, the only thing it changes is a #n besides the modem drivers.
I did read you have to install drivers twice? Once in each state? I did so and nothing.
I did "Added Legacy Hardware", where I saw different ones: ADB Interface, Samsung ADB Interface, Bootloader Interface, etc. Added every single one of them, updated them (I even got the Google USB thing, it did nothing) Sometimes it would bring some error (Can't do that right now or something like that), sometimes "It's already the best we have", but still not regognizing it in cmd fastboot devices.
I also superpermutated every step I could, even doing things completely illogical. I didn't care, I stayed awake until 9AM doing it... and nothing
I did noticed, at around 5am, half asleep, that my "bootloader" window (in my phone) was... not... really... a bootloader? whenever I would adb reboot bootloader it would get me to the same Download Mode I would get by pressing V- + Power + Home. I dismissed it, not only it was really late, It could have just been a normal misunderstanding... you know, language barriers and such (I'm not english native, so I'm constantly reading things in practically two languages, maybe *Bootloader* and the *DW Mode* where actually the same and people are arbitrarily obtuse, I thought) but it still bothers me nonetheless.
I also tried, since, you know, all I want is a custom ROM, to play with Recovery Mode adb sideload? But I would always get some error 21 and other I didn't really catch.
That's my problem(s). I don't really know what to do, and I don't want to wait seven days (or more, because I read some people waiting for weeks) to have the actual OEM Unlock option in my Dev Options.
Can I get a hand with this? Is my bootloader even active? Can I even do OEM unlock in my current state? did I miss a driver, among the 100+ I downloaded even from dubious webs? Never worked with phones before so I'm practically new on this, last time I touched android I did perfectly flash TWRP through Odin and did everything from there.
please
pretty please
Click to expand...
Click to collapse
Too much long bro
Let me know if you untick the autorestart at odin when you wanna install twrp
Or seen:just enable OEM and usbdebug at dev option
Make sure that download right and latests version of twrp for your phone(so important)
And install that via odin and untick the autoreboot at odin( bc if you don't that android will uninstall it)
When you see the done message on odin unplug your phone and turn it off and after that try to go recovery mode by V+home and power
Hope that works
amirizad_7436 said:
Too much long bro
Let me know if you untick the autorestart at odin when you wanna install twrp
Or seen:just enable OEM and usbdebug at dev option
Make sure that download right and latests version of twrp for your phone(so important)
And install that via odin and untick the autoreboot at odin( bc if you don't that android will uninstall it)
When you see the done message on odin unplug your phone and turn it off and after that try to go recovery mode by V+home and power
Hope that works
Click to expand...
Click to collapse
I made it long so I don't have to reply a hundred times to things I already did.
Yes, I did untick autorestart. No, I can't enable OEM Unlock (that's the problem I'm having), and usbdebug es required to use adb, so yes, I do have that enabled.
Can't do Odin, it always fails.
Nezvanova said:
I made it long so I don't have to reply a hundred times to things I already did.
Yes, I did untick autorestart. No, I can't enable OEM Unlock (that's the problem I'm having), and usbdebug es required to use adb, so yes, I do have that enabled.
Can't do Odin, it always fails.
Click to expand...
Click to collapse
Well
Try to reset factory and use you phone for a week or a month!i don't know any way
If you find one i would be happy to know
I have exactly same problem!
Hello! Maybe its too long ago but did you manage to solve it??
same problem U9 no OEM unlock option :/