Database Info

[Q] problem with flashing cm

Hi all,
i want to flash cm on my xperia arc. i have already rooted the device and unlocked the bootloader. i have followed the guide from the cm wiki. Now i run fastboot -i 0xfce flash boot boot.img and then appears this: sending 'boot' (5228 KB)...
(bootloader) USB download speed was 9342kB/s
OKAY [ 0.581s]
writing 'boot'...
FAILED (remote: Wrong range:0x20208020-0x4050f79f. Ok:0x00200000 - 0x03dfff)
finished. total time: 0.583s
help me please
regards
excuse my bad english please.

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

Only fastboot with unknown usb device (device descriptor request failed)

I got a Nexus 5 that won't boot. When you turn it on normally it hangs on the Google logo indefinitely. Recovery mode results in the red triangle logo. The only thing that 'works' is fastboot. But when I plug it into any of my PC's they all say: unknown usb device (device descriptor request failed) in the device manager.
I've tried installing various drivers, but it won't detect my phone in any way. As long as the descriptor isn't known by Windows it cannot install any driver. It will just resort back to the error message. Is there any way for Windows to recognize my device again?
I've tried various PC's and USB cables / ports. It's the device at fault not my other hardware for sure.

I plugged in my Galaxy S6, and it works just fine. Now the funny thing is when I plug back to Nexus 5 it is all the sudden recognized. I flashed the stock firmware back and it hang on the google logo again. Now going to fastboot the device is not recognized again. Recovery mode now also results in a Google logo that is stuck instead of the triangle.
After some retries I can connect in fastboot and the device is recognized as: "android bootloader interface"
Now how can I unbrick it? I am able to flash something to the device, i've tried the Restore_Nexus_5_KTU84P toolkit. It flashes but when it's done the phone reboots into the same brick mode.
When I manually try to flash an .img it says:
FAILED (command write failed (Unknown error))

The bootloader remains unlocked when the phone is rebooted? What OS is on the computer? Tried different USB ports and USB cables?

Tried with Ubuntu and I can flash stable now. But no matter what stock OS I flash (tried 6,5,4.4) after that flashing is done and the phone reboots it stuck on the google logo again. Any options beside throwing it in the bin?
And yeah, the bootloader stays unlocked.

Tried the unbrick method as shown here:
http://forum.xda-developers.com/goo...ck-nexus-5-stucked-qualcomm-hs-t3043301/page1
Flashes fine, also the memory tests pass. But it doesn't change the situation at all.

If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app

Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.

jd1639 said:
If when you try to lock or unlock the bootloader and after a reboot the locking or unlocking didn't take that usually means the emmc is bad.
Sent from my Nexus 9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Lock / unlock sticks just fine.
audit13 said:
Are you flashing the userdata.img file too? The file should be flashed last. After flashong, immediately boot into recovery and perform a factory wipe, then reboot.
Click to expand...
Click to collapse
I did indeed also manually flash all img files including the userdata.
Code:
sending 'bootloader' (2506 KB)...
OKAY [ 0.317s]
writing 'bootloader'...
OKAY [ 0.462s]
finished. total time: 0.779s
rebooting into bootloader...
OKAY [ 0.061s]
finished. total time: 0.162s
sending 'radio' (42033 KB)...
OKAY [ 2.006s]
writing 'radio'...
OKAY [ 2.892s]
finished. total time: 4.898s
rebooting into bootloader...
OKAY [ 0.077s]
finished. total time: 0.278s
erasing 'system'...
OKAY [ 1.125s]
sending 'system' (692940 KB)...
OKAY [ 31.024s]
writing 'system'...
OKAY [ 47.110s]
finished. total time: 79.259s
sending 'boot' (8620 KB)...
OKAY [ 0.615s]
writing 'boot'...
OKAY [ 0.743s]
finished. total time: 1.358s
sending 'recovery' (9202 KB)...
OKAY [ 0.644s]
writing 'recovery'...
OKAY [ 0.775s]
finished. total time: 1.418s
erasing 'cache'...
OKAY [ 0.531s]
sending 'cache' (13348 KB)...
OKAY [ 0.840s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.446s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.911s]
finished. total time: 6.911s
erasing 'userdata'...
OKAY [ 6.697s]
sending 'userdata' (137318 KB)...
OKAY [ 6.441s]
writing 'userdata'...
OKAY [ 9.135s]
finished. total time: 22.273s
rebooting...
finished. total time: 0.274s
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.

aapje1299 said:
Lock / unlock sticks just fine.
I did indeed also manually flash all img files including the userdata.
After flashing I cannot enter recovery, cause every mode except for fastboot results in a stuck Google logo.
Click to expand...
Click to collapse
Let's try something. I'm going to have you try to boot into twrp recovery and if you can do a factory reset from that. At the bootloader you'll use the commands fastboot boot twrp.img. Where twrp.img file be the full file name of the twrp recovery image. If you don't know where to get twrp Google teamwin nexus 5. Download that to your pc. If it boots to twrp go to wipe and wipe the device. Then try rebooting to system.

So you can't enter recovery, even from fastboot mode?

I couldn't
Don't ask me how, but today I flashed it again to show my collegue that it wouldn't work. And after flashing it it came alive all the sudden. I'm a happy man! Everything seems to work except for the camera, but that is probably something else!
--
Hmm, disconnected and reconnected the charger, phone froze. Reboot and now it's stuck on the google logo again. I think this phone is toast
--
Another update
I removed the cover, and all the sudden it booted fine again. The battery was loose inside and there was some duct inside to keep it in place. This phone has been repaired before because the screen was broken. I think something is short circuiting in there. I got it booted now and first I'm going to give it a full charge.

I declared it dead, was able to actually get TeamWin recovery flashed and it worked. Then after some time it was dead again and unable to boot. Also the camera was broken. Thanks for thinking along guys!

Z3 bricked, no recovery

Hi all,
somehow my sons' D6603 messed up and didn't boot anymore. Had an old CarbonROM installed before, but that failed for no reason I can pinpoint.
OK, to recover I tried to reflash the ROM - but boot process got stuck in boot animation for hours (until battery ran out).
OK, so I fired up flashtool and tried to install an FTF - but all FTFs I tried to retrieve failed to unpack.
OK - one more try - got me a stock ROM that was supposed to be flashed through recovery.
Now I get Sony splashscreen, then display turns black and stays like that forever. Only sign of something happening is that the notification LED blinks occasionally.
I tried to enter recovery - wouldn't work at all: never saw any change in boot process.
I can put the phone into flash mode and into fastboot - so I tried to flash a new TWRP:
Code:
[email protected] ~/temp/TWRP-z3 $ fastboot flash FOTAKernel recovery.img
target didn't report max-download-size
sending 'FOTAKernel' (15904 KB)...
OKAY [ 0.502s]
writing 'FOTAKernel'...
OKAY [ 1.056s]
finished. total time: 1.558s
[email protected] ~/temp/TWRP-z3 $ fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (15904 KB)...
OKAY [ 0.501s]
writing 'recovery'...
OKAY [ 1.055s]
finished. total time: 1.556s
But still the mobile won't boot into recovery
OK, there's a different TWRP available - but I can't flash it to FOTAkernel:
Code:
[email protected] ~/Downloads $ fastboot flash FOTAkernel twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'FOTAkernel' (10808 KB)...
OKAY [ 0.342s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Downloads $ fastboot flash recovery twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'recovery' (10808 KB)...
OKAY [ 0.342s]
writing 'recovery'...
OKAY [ 0.721s]
finished. total time: 1.063s
Can anyone help me to get stuff working again? I'm lost for options right now - TWRP won't come up, and I can't get an FTF via flashtool to my harddrive. Any other ways to unbrick the phone?
Got a recent LinuxMint 19.x here as my machine right now. Getting a Windows up and running would be an obstacle (although I might get a hand to one).