Database Info

Very unusual situation with HTC One Mini - Any Help?

A friend brought a HTC One Mini in a very unusual situation to me. The phone bootloader is "Locked" and "S-ON". It only boots to fastboot usb mode only. The battery is still ok because I checked with a script that is used to charge in that mode when the battery is low; at least it still has about 3870mV, and the minimum is around 3680mV. The problem is that:
1. When I try to unlock so I can flash a custom TWRP recovery the unlock spalsh screen does not appear, although the unlock command says sucessful.
C:\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
Click to expand...
Click to collapse
2. I downloaded this stock file OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip because it matches the OS version showing on the fastboot screen on the phone. When I try to flash it from fastboot I get this error:
C:\fastboot-win>fastboot flash zip OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip
sending 'zip' (346477 KB)...
OKAY [ 16.826s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 49.466s
Click to expand...
Click to collapse
Can anyone please render any help? I can follow any instructions to the letter, just that I have never come across this kind of issue before.
Thanks in advance.

[Q] Stock Nexus S stuck on Google logo: is it possible to recover the data?

Hi guys,
I know it sounds like one of many threads already created here.
I have read a bunch of them and the information sounds a bit contradictory or at least I'm unsure.
My Nexus S i9020 has sunk in salt water. I washed it in distilled water then gave it two weeks in a dry, warm environment.
When I try to turn it on I see a menu which is asking do I want to unlock a bootloader or not.
While on Power + Volume Up I can get into recovery menu. When I choose reboot I can see a Google logo with no progress. Pressing the Power button doesn't turn the phone off so I have to take the battery out. But power off through the menu works fine.
I installed necessary drivers / bits of SDK on Windows 7. ADB doesn't see the phone but fastboot does, so I can turn the phone off or can try to reboot it from PC. Looks like USB debugging is off.
Now the question is: can I actually turn it on without unlocking a bootloader? Can I _run_ CWM without unlocking a bootloader?
If not are there other options to turn USB debugging on?
If there are no options and I have to unlock a bootloader, would it 100% kill the data on memory card?
If it will is there any chance to restore it afterwards? If so, how can I do that?
Or should I just forget about it?
Thank you!

First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!

demkantor said:
First try to flash the factory system.img and boot.img through fastboot, don't wipe and only flash these, you may be able to get in and recover data this way.
If not and you want to try a custom recovery to the best of my knowledge you will need to unlock bootloader which will erase all data
There is a chance that you can still recovery some though, there are apps in the market (disc digger?)
But know that more than likely you won't get anything back
Best of luck though!
Click to expand...
Click to collapse
Hi demkantor,
Thanks a lot for reply!
Before I kill it completely... :cyclops: How do I find out which image I need to download?
I obviously need 4.1.2 one but do I need "soju" for Nexus S (worldwide version, i9020t and i9023) or "sojua" for Nexus S (850MHz version, i9020a)?
The phone I have is the UK version, as far as I remember (I'll double check it later) there was just i9020 on the phone, no other index.
Any ideas about this? Can device ID help here?
And after that the only thing I have to do would be:
> fastboot flash system system.img
> fastboot flash boot boot.img
> fastboot reboot
Am I right?

https://developers.google.com/android/nexus/images?csw=1
More than likely soju, since you can't get to about phone to check maybe it will say under battery or if you have original box?
And yes those are the correct commands
Best of luck!

Hi demkantor,
This is what I see in fastboot mode:
PRODUCT NAME - HERRING
HW VERSION - REW 11
BOOTLOADER VERSION - I9020XXLC2
BASEBAND VERSION - I9020XXKI1
CARRIER INFO - EUR
According to android-info.txt from soju-jzo54k-factory-36602333.tgz everything is fine so i downloaded it, extracted system.img and boot.img and tried to flash them with fastboot.
Unfortunately I got this:
C:\android-sdk-windows> fastboot flash system system.img
sending 'system' (337443 KB)... OKAY [ 53.034s]
writing 'system'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 53.035s
C:\android-sdk-windows> fastboot flash boot boot.img
sending 'boot' (3964 KB)... OKAY [ 0.621s]
writing 'boot'... FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.622s
Looks like whatever I want to flash I still have to unlock the bootloader. Any other ideas?
Can I boot into CWM without flashing and turn USB debugging on from there?

You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)

demkantor said:
You can try to just boot the recovery but its unlikely
fastboot boot nameofrecovery.img
That will probably fail too, my guess is you'll end up having to unlock bootloader or run the flashall.bat but either way will do a full wipe, there is the slight chance there are apps in the play store that can recover some stuff if you run them right away but I can't recall if unlocking the bootloader is a format or a wipe (format being much less likely to recover)
Click to expand...
Click to collapse
Yep looks like it is very unlikely that I will be able to do it without unlocking. I've seen a thread somewhere where the guy was in the same situation and he had to unlock the bootloader but after that was able to restore the data.
Okay then, I'll dig on this a bit more and then try it out. Thanks a lot!

Okay. So finally I had to try unlocking a bootloader and flashing the phone with flash-all.bat script.
The log looks like this
Code:
c:\android-sdk-windows\soju-jzo54k>flash-all.bat
sending 'bootloader' (1536 KB)... OKAY [ 0.241s]
writing 'bootloader'... OKAY [ 0.355s]
finished. total time: 0.597s
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)... OKAY [ 1.925s]
writing 'radio'... OKAY [ 1.740s]
finished. total time: 3.665s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: SERIAL
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3964 KB)... OKAY [ 0.620s]
writing 'boot'... OKAY [ 0.520s]
sending 'recovery' (4308 KB)... OKAY [ 0.674s]
writing 'recovery'... OKAY [ 0.565s]
sending 'system' (337443 KB)... OKAY [ 52.764s]
writing 'system'... OKAY [ 37.667s]
erasing 'userdata'... OKAY [ 0.185s]
erasing 'cache'... OKAY [ 1.999s]
rebooting...
finished. total time: 95.001s
After rebooting the phone I got the same problem i.e. it's stuck on Google logo. The same result I get when I insert the battery while the phone is unplugged from PC. But if I press Volume Up + Power (while disconnected from PC) I get a yellow triangle and the text "Downloading... Do not turn off the target".
Data is lost. Fine. Any ideas what could be done in order to make the phone bootable?

Try wiping through fastboot and then flashing the images one by one (instead of the flash all.bat)
This may help
http://forum.xda-developers.com/showthread.php?t=2277112

MOTO G XT1032 almost bricked

Hi all,
I have been seeking for infos to solve my problems for days and so, eventually, I come to you, begging for your help.
My device is a Moto G 2014 XT1032 (Europe), unlocked and used to be on android lollipop stock (I upgraded it manually during Easter).
Following a wrong attempt to restore a backup, I have (almost) bricked my phone.
Here is what works : Fastboot but NOT adb, acess to recovery (clockwork) and that's it. The usb debugging is not activated.
Otherwise, the phone is stucks in a bootloop.
Here is what I get when I try to update the phone :
Code:
C:\>fastboot update pa_dlx.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\>
And when I simply try to flash the sip (in order to install it from cwm) :
Code:
C:\>fastboot flash zip pa_dlx.zip
target reported max download size of 536870912 bytes
sending 'zip' (205116 KB)...
OKAY [ 6.461s]
writing 'zip'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 6.508s
Voilà. I would warmly accept any help you could give me.
I thank you in advance,
M.
EDIT : Thanks to this guide : GUIDE Moto G Restore Stock Firmware, I managed to solve my problem.

Pixel 2 might be bricked

Hello,
I got a Pixel 2 with Android 10. I wanted to downgrade the firmware, so I downloaded the official firmware from Google (Walleye). I did the following:
- Enabled dev options
- OEM Unlock allowed
- USB Debug allowed
I restartetd the phone into bootloader (mw8998-002.0059.00) and startet cmd wit the command
fastboot oem unlock
I tapped yes on the phone and the progress started. But it failed.
Since then, I cant start the phone. It always boots into the bootloader menu. Regardless if I choose Start, Restart Bootloader, Download Mode or Recovery Mode, it always boots into the bootloader again. Only exceptions are power off or barcodes.
I can, however, access the phone with fastboot and adb.
I tried to flash TWRP, but I could only start it once and it didnt really work (it was lagging extreme so I could barely swipe to start). If I try to boot with ADB and an image from harddisk, it doesnt work either. Since the phone lacks a recovery partition, flashing an official firmware always tells me "No such partition"
Secure boot = yes (Production)
Device state = Unlocked
Some firmware images dont do anything, others give me a message at the end
device version-bootloader is xxx56, update requires yyy.
Is there any possibility to get the phone working again?
Thanks in advance!

Venomiz said:
Hello,
I got a Pixel 2 with Android 10. I wanted to downgrade the firmware, so I downloaded the official firmware from Google (Walleye). I did the following:
- Enabled dev options
- OEM Unlock allowed
- USB Debug allowed
I restartetd the phone into bootloader (mw8998-002.0059.00) and startet cmd wit the command
fastboot oem unlock
I tapped yes on the phone and the progress started. But it failed.
Since then, I cant start the phone. It always boots into the bootloader menu. Regardless if I choose Start, Restart Bootloader, Download Mode or Recovery Mode, it always boots into the bootloader again. Only exceptions are power off or barcodes.
I can, however, access the phone with fastboot and adb.
I tried to flash TWRP, but I could only start it once and it didnt really work (it was lagging extreme so I could barely swipe to start). If I try to boot with ADB and an image from harddisk, it doesnt work either. Since the phone lacks a recovery partition, flashing an official firmware always tells me "No such partition"
Secure boot = yes (Production)
Device state = Unlocked
Some firmware images dont do anything, others give me a message at the end
device version-bootloader is xxx56, update requires yyy.
Is there any possibility to get the phone working again?
Thanks in advance!
Click to expand...
Click to collapse
Make sure you have the latest android-sdk platform tools.
Try downloading full system firmware zip (not OTA). Unzip where you have the fastboot.exe installed (fastboot.exe flash-all files should be in the same folder) and run the flash-all.bat or flash-all.sh with phone connected to PC and in bootloader/fastboot mode.

I used the latest ADB / Fastboot and the firmware 10.0.0 (QQ3A.200805.001, Aug 2020)
walleye-qq3a.200805.001-factory-a3367352.zip
I executed the flash-all.bat, and this is the output:
target reported max download size of 536870912 bytes
sending 'bootloaderb' (38688 KB)...
OKAY [ 0.825s]
writing 'bootloaderb'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.835s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
sending 'radiob' (60388 KB)...
OKAY [ 1.275s]
writing 'radiob'...
(bootloader) Updating: modem @00001000 sz=03AF7000
OKAY [ 0.541s]
finished. total time: 1.821s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00023-2004070200
Serial Number........: FA7A31A05854
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'mw8998-002.0059.00'.
Update requires 'mw8998-002.0083.00'.
finished. total time: 0.022s
Press any key to exit...
The phone is still not booting at all.

archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
The only time I have seen those errors was when the Fastboot version was out of spec for a flash.
I am using this version for OTA updates "fastboot version 30.0.0-6374843" no problems so far.

Soft brick after attempting flashing stock ROM

Hi, just so you know, I am very new to this so please excuse any dumb mistakes I may have done.
I got a stock ROM for my device from LMSA and I am attempting to flash it using fastboot. The first problem I came across while trying to do this, which I still don't know how to fix, is that whenever I try to flash my bootloader with bootloader.img, I get this:
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.342s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've searched online for answers on how to fix it, and I came to threads like this which told me to try to just keep going with the rest of the flashes, which I then tried. After, I tried entering recovery mode. I got a no command error, so I went back to fastboot to try to just start my phone with the start option, in which I got a bootloop where it first, sent me to the Motorola screen for a couple seconds, showed me a warning about my unlocked bootloader, went back to the Motorola screen for 10-20 seconds, then turned my screen black for a second, and started over again. This happens for a long time until, finally, I get an error message saying: (color corresponding)
Boot failed. Press POWER KEY to Retry
Your device didn't start up successfully.
Follow these instructions if the failure cannot be recovered after retrying.
If this is a Verizon device, please use Software Repair Assistant on your computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assistant did not help for any reason, please contact customer care center for further assistant.
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode​
Click to expand...
Click to collapse
I'm using T-Mobile on my device, so it isn't locked to Verizon or using Verizon (my phone is unlocked carrier), so I decided to try to flash boot_a and boot_b with my boot.img:
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.504s]
Writing 'boot_a' OKAY [ 0.512s]
Finished. Total time: 2.020s
C:\Users\spong\OneDrive\Documents\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (65536 KB) OKAY [ 1.504s]
Writing 'boot_b' OKAY [ 0.506s]
Finished. Total time: 2.014s
Click to expand...
Click to collapse
Doing this changed nothing.
I honestly do not know what to do, since I can't find any help online anywhere for my specific scenario. I found this forum of someone having a really similar problem with me, but they never fixed it and just decided to flash a stock ROM, which is what I was already doing.
Any solution, and I mean any, will help.
Here is the ROM that I was trying to flash, and here is my "fastboot getvar all" txt file.

I have similar issue here. Please if anyone knows how to manage this