Database Info

[Q] bootloader unlock doesn't 'register' in Nexus S

I've spent lots of time looking through forums trying to answer/solve my issue so I hope it's not something stupid I've missed. Sorry for the trouble if it is though.
So, my issue is that I simply cannot unlock the bootloader of my Nexus S (i9020T). The phone's connecting to my computer via Samsung Android ADB Interface as seen under the Device Manager. I see the proper device ID when I type "fastboot devices" into the adb command prompt w/ phone in fastboot mode. Then, when I type "fastboot oem unlock" the phone starts the unlock verification process -- I select yes, the phone restarts, but it goes back to the stuck Google screen. Then, if I pull the battery and go into fastboot mode directly, bootloader's still locked. I've tried this quite a few times and same result -- same result trying to unlock w/ some of the toolkits here (WugFresh's NRT, m.sabra's root tool). Haven't tried Odin but from what I've read it would also require an unlocked bootloader to do anything. I've even tried a few other things like pushing recovery and bootloader images onto the phone via adb, but these also failed due to the locked bootloader.
I also cannot enable USB debugging under phone settings either b/c I now can't get past the Google logo/fastboot mode menu. Didn't think this was required to unlock bootloader though.
Background: Phone had the latest auto updated version of Android when the phone all of a sudden turned off in the middle of the night recently. Weird b/c the battery was basically full. It now always gets stuck on the Google logo upon normal restart. It goes into fastboot mode OK if I remove the battery and press power/vol. buttons -- I then first tried the restore and recovery functions there, etc, but no effect.
Any ideas? Or is the phone just dead now?
Thanks! :fingers-crossed:
Edit:
I've now tried what's described as a possible solution here: http://forum.xda-developers.com/showthread.php?p=44753413#post44753413. It didn't work since that also needs bootloader to be unlocked.
I've also tried to solve it w/ all versions of Odin. None of them detect my phone even after installing Kies w/ drivers. I think I have the required drivers though since I can command the phone fine through adb. And Odin should need bootloader unlocked to work anyway...
Edit 2:
To add, one of the first things I tried was to do a manual factory data reset in the recovery menu (selecting 'yes' to erase all data).
And I tried adb sideload of the OTA .zip file. But installation was aborted. The following appeared immediately under the regular adb sideload instruction in the system recovery menu (under "Now send the package you want to apply to the device..."):
Finding update package...
Opening update package...
Verifying update package...
Installing update...
file_getprop: failed to stat "/system/build.prop": No such file or directory
Installation aborted.

Bump w/ more info.

[Q] HTC one m7 always boots in recovery mode

I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.

patrickgrantm said:
I tried to install the android revolution hd one 71.1 on my phone and it went out good so far into the installation but after the installation, i rebooted my phone and it went to a boot logo then went to the TWRP recovery mode. i tried deleting the cache and doing a reset but nothing is happening. please help me.
Click to expand...
Click to collapse
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.

lurkeratthegate said:
Having the same problem. The phone only reboots into twrp recovery mode, yet shows no errors when re-flashing device with most recent version of sense ui.
I'd really like to be able to use my phone.
Click to expand...
Click to collapse
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again

LS.xD said:
Flash latest stock RUU. Once phone is fixed you can go for a custom rom again
Click to expand...
Click to collapse
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.

lurkeratthegate said:
I tried that. My computer is no longer recognizing the device at all. I thought I was making progress through the first part of the day, but for some reason, usb recognition seems to fluctuate.
I'm normally pretty alright working with this type of thing, but this phone has me completely baffled.
Click to expand...
Click to collapse
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!

LS.xD said:
Really weird. So you have no chance to get into fastboot mode, not even by selection reboot to bootloader in twrp?!
Click to expand...
Click to collapse
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.

lurkeratthegate said:
I supposed I should have been more clear. Fastboot will work, but all of the adb commands fail as the "device not found". I have tried restarting everything multiple times, updated all of the drivers, deleted the drivers, re-installed them, and while it makes the chime noise when I plug the phone in, all I can do is look at it in device manager. I'm running windows 8.1 and twrp 2.8.5.0, by the way.
Click to expand...
Click to collapse
RUU flashing is fastboot based I suppose. So you won't need adb at all.

LS.xD said:
RUU flashing is fastboot based I suppose. So you won't need adb at all.
Click to expand...
Click to collapse
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?

lurkeratthegate said:
Wait, what? I can flash images like twrp to my phone via fastboot, but the only ruu's I've found either have executable wizard files, or are self extracting. How can I flash a rom or update utility using fastboot?
Click to expand...
Click to collapse
Connect phone in fastboot mode, run RUU, click next plenty of times, and done
If your phone is S-ON, flash stock recovery first and relock the bootloader before running the RUU

Stuck at "...unlocked...booting now..." Bricked?

Solved.
AL10, NXT-C900B133, rescue0.3, NEXT
I unlocked bootloader, installed TWRP, and rooted using SuperSU with no problem by following these directions:
http://forum.xda-developers.com/mate-8/general/guide-unlock-bootloader-root-install-t3301371
I then formatted data using TWRP wipe, then tried to install Stock Rooted No Encrypted Boot from
http://forum.xda-developers.com/mate-8/development/rom-stock-rooted-encrypted-boot-t3303606
The phone never gets past "...unlocked...booting now...." (I did not install insecure_boot because I had trouble finding it---it is not in Mate 8 Android Development, only in Mate 8 Original Android Development.)
I can get to fastboot and to the Huawei recovery in Chinese (which doesn't work---wifi downloading stops with an exclamation point), but TWRP is gone, and I can't get it back by reflashing it. I've tried HiSuite recovery, unbricking using the Italian knife following these instructions:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
with various roms, and I've tried force flashing an UPDATE.APP from /sdcard/dload. No joy.
I caused the problem by installing a B331 rom when I was at B133—dyslexic much? Once I got TWRP back, flashing a B180 rom worked fine.
The difficulty was getting TWRP back. To do that, I flashed the following files using fastboot—it may be overkill:
TWRP-2.8.7.0-ENG.img,
insecure_boot_b331.img,
and the files in
L29Fastboot.rar.
TWRP

Hey ho!
I had exactly the same problem yesterday.
I figured out my system only was able to boot when I hold down [vol-]&[power].
Then the "not trusted message" had a few more lines and the phone booted up.
When it's up again, you can use adb to reboot to fastboot: adb reboot bootloader
You can also try to go directly to recovery if you alrteady flashed it: adb reboot recovery
From threre you can try again.
btw: I had to use a complete different TWRP version. 3.x somewhat. I think it was from here: http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
Info: I was NOT able to use [vol+]&[power] for Recovery, eRecovery or anything else. I was just stuck.
I hope it helps.

I recommend after getting your device back on track to use twrp to make a recovery on your microsd card. That way u have a sure chance of getting bwck to working order

Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?

iAngus said:
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
Click to expand...
Click to collapse
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".

Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Click to expand...
Click to collapse
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".

iAngus said:
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
Click to expand...
Click to collapse
you could fix the same problem I have is not to do help me

Need help recovering phone!

I'm in way over my head guys, so here's my situation:
I have no OS installed, for some reason I can't get into TWRP anymore (it goes to eRecovery instead).
I CAN get to bootloader screen (bootloader is unlocked).
adb does not recognize my device on device list command (it worked before, but now I can't get into the OS to turn on USB debugging and such...).
please help! I don't know what else to do!

liran96 said:
I'm in way over my head guys, so here's my situation:
I have no OS installed, for some reason I can't get into TWRP anymore (it goes to eRecovery instead).
I CAN get to bootloader screen (bootloader is unlocked).
adb does not recognize my device on device list command (it worked before, but now I can't get into the OS to turn on USB debugging and such...).
please help! I don't know what else to do!
Click to expand...
Click to collapse
I think the first step to fixing my phone is to get it recognized in the list of devices attached in adb.
how do I go about doing that?

In device manager I got it to recognize my phone as Android Phone > Android ADB Interface.
so I believe the drivers are updated, what else can I do to get my phone recognized in cmd adb?

If I need to provide any more details then please say, I am getting hopeless
Edit: I managed to get into TWRP. still no clue how to continue from here as I can't transfer any files from PC

I found a update.zip file on my phone's SD card, I can't remember which ROM version it holds, but when I try to flash it I get a few errors:
check_write_data_to_partition,write data error
E:unknown command [errno]
Update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip files '/external_sd/update.zip'
I think I managed to screw my phone up even more, I can no longer get into TWRP...
:crying:

Phone boots into fastboot, system files corrupted

Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?

Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.

Both failed. I attached the errors I recieved.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com

I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.

crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/

It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.

Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?

Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.

That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .

crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!