Database Info

[Q] Nexus s 4g locked up

Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.

Did you try ADB fastboot method?

Not sure how to try that

I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.

ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>

also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.

TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.

I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.

You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.

Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.

Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.

The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.

Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.

Confused trying to enter bootloader mode on Xperia M2

Hi everyone, I am looking for some help and I will try to be specific. I am trying to root my Xperia M2 (I have unlocked the bootloader).
-USB debugging is ON.
I am trying to boot into my bootloader, flash TWRP, boot into TWRP, install SuperSu.
I am stuck in the step of booting into my bootloader using ADB. I have tried the simple method of running a CMD and using the "adb reboot bootloader" command. CMD responds with "no devices/emulators found".
I tried the "adb reboot bootloader" command while my phone is on fastboot mode and while it's turned on. None seem to work.
What I am expecting is my phone to boot in a screen showing the android logo. Am I wrong?
Other commands I've tried and the response I got:
Adb devices --> List of devices: empty
fastboot devices --> my model and the word "fastboot"
Before you comment "install drivers", please note that I am aware of this, I have searched the web for drivers and I am pretty sure I have the drivers. If you are familiar with the process of installing the drivers please post the way of installing them, because i might have done something wrong..
I believe that what i am doing wrong is having the phone in the wrong state.. I might be executing a command with my phone turned on, while it needs to be off, so if you could clarify the phone's state in every step, that would be great
I apologize if I forgot crucial details, I am a newbie. Thanks in advance, i will make sure to answer every question and provide info needed.

reboot as boot loader
You already have TWRP means 1st go to recovery mod use switch of mobile and on it Press v- button after vibrate and untile come sony big logo you get recovery mod then there is option reboot in to boot loader ... please check

Scrap everything and follow http://forum.xda-developers.com/xperia-m2/general/unlocked-bl-root-sony-xperia-m2-android-t3214498

Phone wont go into bootloader. How to root + flash new recovery?

Hello. I can't get my phone rooted in any way.
I want to Root so I can use TWRP app to flash TWRP recovery .img, and after that I can boot into TWRP recovery and flash new ROM. Correct????
What I've tried so far. OppoTools 1.6.5 = One key root gets hard stuck on Oppo logo at start-up and then I have to flash Coloros ROM again from recovery. Also KingRoot says app not installed. On windows version of KingRoot it gets to some percentage and then it Fails.
I have downloaded "unlocked bootloader" Coloros from this forum that was mentioned before ( Dropbox link )
I have also tried two different ColorOs versions.
I have installed 15sec ADB installer.
I plug my phone into PC and run CMD.
I type adb devices into command prompt and it detects my R7 plus.
then I try to command " adb reboot bootloader "
Phone restarts normally and doesnt go to bootloader. Tell me if im stupid, but isn't Bootloader different than Recovery? Because I can get to recovery command "adb reboot recovery"
I tried some weird button combination Vol+ Vol- + Power and phone semibricked for awhile and PC didnt even react USB driver correctly and almost waved the white flag on this case.
I've enabled USB-debuggin and OEM unlock from devices dev-options.
When I to type command "fastboot oem unlock" on command prompt is says Waiting for device. Nothing pops-up on device and nothing happens.
So now Im stuck on situation that my phone doesnt launch into bootloader where presumably "fastboot oem unlock" would work?

If you have flashed the version of Color OS that has bootloader enabled, you should simply need to go into the settings, enable USB debugging and OEM unlocking, then shutdown the phone before holding the power and volume+ buttons and waiting the ADB bootloader screen. After that, just plug it into the computer and follow the guide on flashing twrp with ADB.

Oneplus 6 in Fastboot Loop

Hi,
i'm facing the problem that my phone only starts in "FastBoot Mode" at least i guess that's the mode.
OnePlus 6 with root.
It happened after i rebooted after installing an OTA Update and installing a Magisk Manager Update.
I used the method described here. The last few times it worked perfectly.
But now the only thing that happens when i try to boot the phone is a screen that says
FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - d8a34971
SECURE BOOT - yes
DEVICE STATE - unlocked
with the volume button i can select "START, Restart bootloader, Recovery Mode and Power off"
but nothing happens when i select e.g. Recovery Mode, or simply START.
The phone shows the boot logo for a second, then I'm back at the screen with "FastBoot Mode"
I installed the USB-drivers for the device and can find it with my PC when i type "fastboot devices" in the command prompt.
But that's pretty much all. I don't know how to continue.
I would be very glad if i could keep my data, is there a way to save my phone and if not how do i install the normal OS again?
I really hope someone can help me here.
Edit:
When I type "adb devices" it says "List of devices attached" but there is no entry.
USB-Debugging is on, since the Root-process i didn't touch the developer options
So should be the USB mode for file transfer (MTP)
I'm not sure if i checked the "always allow from this computer" setting
So following this guide the only thing i can't do is checking the prompt for USB-debugging since i can't boot the OS.
Is there anoter way to get a adb connection?

[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via stock recovery (with twrp is possible but not recommended). The updates will be done on the slot not used for example...
forum.xda-developers.com
For everyone that can't connect to the device via ADB but fastboot, this does the trick.
Thank you guys!

flashing pixel 2 without usb debugging

Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.

If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.

Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.

mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.

Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.

mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/

Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.

mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache

Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.