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
Related
Hello all
Just bought this phone I9020T. The phone didn't go past Google so I tried to wipe and format/system. Everything completes fine but nothing changed interns of files and folders
I tried installing ICS via 4.0.4 fast boot but failed on system write.
I'm now able to get into the phone it is running cm9 rc0. However can't wipe from with in either. Neither can I wipe the sdcard.
Any thoughts?
I am unable to format /system or /data or /sdcard partition via CWM 5.0.2.3 recovery.
I can't factory reset the phone.
Here is the fastboot output:
-imm76d>fastboot -w update image-soju-imm76d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKL1
Baseband Version.....: I9020XXKI1
Serial Number........: 393204CBDFEE00EC
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3444 KB)... OKAY [ 0.629s]
writing 'boot'... OKAY [ 0.423s]
sending 'recovery' (3776 KB)... OKAY [ 0.696s]
writing 'recovery'... OKAY [ 0.466s]
sending 'system' (282046 KB)... OKAY [ 51.201s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 53.483s
Also just to add I was able to flash ICS bootloader and recovery via fastboot.
Do you have the newest ClockworkMod Recovery installed?
I have 5.0.2.3 installed.
Not touch. I can't flash system with fast boot why should it matter what recovery I have?
So you want to format your sdcard? Am I right? If so, while in recovery, go to "mount and storage" and choose format sdcard.
Sent from my Nexus S using Tapatalk
I am unable to format /system or /data or /sdcard partition via recovery.
I can't factory reset the phone.
Here is the fastboot output:
-imm76d>fastboot -w update image-soju-imm76d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKL1
Baseband Version.....: I9020XXKI1
Serial Number........: 393204CBDFEE00EC
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.001s]
checking version-baseband... OKAY [ 0.001s]
sending 'boot' (3444 KB)... OKAY [ 0.629s]
writing 'boot'... OKAY [ 0.423s]
sending 'recovery' (3776 KB)... OKAY [ 0.696s]
writing 'recovery'... OKAY [ 0.466s]
sending 'system' (282046 KB)... OKAY [ 51.201s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 53.483s
Made it worse when i did fastboot oem lock.
now I can't unlock.
fastboot oem unlock
... FAILED (remote: Erase Fail)
i have the same problem
accidently wiped the whole system and almost everything besides SD Card and now im stuck on the google logo. Well if you havent already, try fastboot flash recovery twrp-crespo-2.0.0RC0.img. From http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/. That will get you into team win recovery project. From there you can do the same things as CWM Recovery. The problem for me is that i cant flash a rom at all but i can flash google apps. The rom doesnt actually flash for some reason. I have a thread up about this problem aswell :http://forum.xda-developers.com/showthread.php?p=24827487#post24827487
Please check recovery.log after trying to format in CWM (by choosing Report error). If it shows bad blocks, the chances are your NAND chip should be replaced.
The same NAND memory chip stores all partitions (including USB storage area): with high read/write rates on a large storage area (USB/sdcard part) it's more likely for the chip to go wrong.
How do I change the NAND?
By replacing the NAND memory chip mounted on the PCB.
Are we sure it's hardware?
anglergab said:
By replacing the NAND memory chip mounted on the PCB.
Click to expand...
Click to collapse
As in, remove it from the mainboard, somehow find another that is compatible and re-solter the pins back on?
How sure are we that this is a hardware issue? I'd like to be sure before I go plucking NAND chips off of the PCB!
Same exact issue. I've tried countless ways to recover my phone (from recovery and fastboot flashes). It seems like /system not being writable is the kiss of death. Not having /sdcard writable means I can't really do much from recovery. Can't access my backups or transfer anything from my computer. My hands are pretty tied here!
i have the samme problem what can i do?really i can replace nand sd card?
I have the same issue as the OP when flashing the factory ROM for my Nexus S. Things fail at:
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 37.464s
I put on Clockwork recovery and can not mount / delete /sdcard, /system, or /data. The log message states:
Formatting /system...
E:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/system
Error formatting /system!
---
Formatting /sdcard
I:Formatting unknown device
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
---
Since Nexus S is a dev device for me I moved onto others, but would like to determine if I should put it out to pasture / throw it away since I assume there will be no equitable repair / return at this stage.
For several months prior the device gets stuck at the Google logo / flashes then requires a battery pull. Oddly enough I was able to get it to boot about 1 in 3 then 1 in 5 times if I went into stock recovery, let it sit there for a minute or so, reboot back into bootloader then hit power off. "Magically" next power on it without going to the bootloader it would boot normally. Well... This stopped working or I gave up after 5 tries!
This does make me think the poster mentioning NAND failure or a hardware failure for the storage is probably what is happening.
Anyway... I'd be glad to hear if there is any resolution to this matter, but kind of guess it's time to blend this device. Sucks cause it was my only ICS device right now... sigh...
I ended up going through warranty services from Samsung, and got it replaced free of charge, within the warranty timeframe. Interestingly enough they repaired it with me being the second-owner.
Thanks for the heads up on the warranty repair.. Though mine is out of warranty it appears they will fix it for no cost or that is what I was told over the phone. That much is good and wasn't my first assumption that it would be a free fix.
Hi all,
I have a friend's nexus 5, that I try to unbrick. Unfortunally, and after dragging all threads about unlocking via fastboot, I'm still unable to fix his device.
The fact is, I'm able to unlock (fastboot oem unlock) , then when I reboot the bootloader, it's back locked.
I've tried to flash stock bootloader (for both nexus 5 bootloaders (HHZ11k, HHZ10x) but without success
The device is locked on a bootloop Google screen, impossible to access to recovery mode (via fastboot or via vol up + power)
Anybody's got an idea ?
here is a sequence of trying to update bootloader, you can see that I must unlock for allmost each step
Code:
./fastboot oem unlock
...
OKAY [ 2.596s]
finished. total time: 2.596s
./fastboot erase boot
erasing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.217s
./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.215s]
finished. total time: 0.215s
./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.219s
./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.221s]
finished. total time: 0.221s
./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.493s]
finished. total time: 0.493s
./fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 0.404s]
finished. total time: 0.691s
./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
./fastboot oem unlock
...
OKAY [ 2.130s]
finished. total time: 2.130s
./fastboot oem unlock
...
OKAY [ 3.665s]
finished. total time: 3.665s
./fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.514s]
writing 'radio'...
OKAY [ 2.850s]
finished. total time: 4.364s
./fastboot oem unlock
...
OKAY [ 2.999s]
finished. total time: 2.999s
./fastboot -w update image-hammerhead-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ10x
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 02ffc80f08e51d0d
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ10x'.
Update requires 'HHZ11k'.
finished. total time: 0.601s
You need to flash the right bootloader first before the rest can go through
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with fastboot boot recovery.img).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (FAILED (remote: invalid bootloader image))
benoit.bds said:
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with
Code:
fastboot boot recovery.img
).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (
Code:
FAILED (remote: invalid bootloader image)
)
Click to expand...
Click to collapse
Looks like you have corrupted memory and nothing is going to work. Time to rma.
jd1639 said:
Looks like you have corrupted memory and nothing is going to work. Time to rma.
Click to expand...
Click to collapse
i agree.
I don't want to come off as alarmist, but I'm starting to see a worrying trend here. If you look at other threads over the past few days, there have been quite a few people with dying flash chips (myself included). There are a few differences in some of the symptoms, but the most common being that 'fastboot oem unlock / lock' fails to stick. It's like the chip is left in some random state of corruption, and unable to be written to. If I were I betting man, I'd say we can expect to see a flood of these posts in coming days.
I would recommend to anyone with an unlocked bootloader, that you get it locked asap and reset the tamper flag too, just in case this same issue occurs with your phone in future, and you need to RMA it.
To the OP, can you confirm whether the device has been previously unlocked, and whether anything was done to the device leading up to the issue? I'm hoping that if this issue is happening to both locked and unlocked devices that Google / LG will have to take the issue seriously should it become an epidemic.
:crying:
My friend has admitted that his n5 had fallen into water...
He gave it for deoxidation + battery replace, but they didn't manage to boot it more than fastboot mode, so I proposed him to give it a try.
To reply to sir_earl, the device was early bought, stock rom and official OTAs.
Anyway, thank you all for your responses !
Regards
Today I was facing a 4.4.3 issue so I've thought about doing a factory reset to see if this fixes it. So I've gone into Recovery and run a factory reset. Strangely this was taking so long, so after 2 hours I've decided to stop it. I know that stopping this process is not recommended, but I've considered it was getting out of the reasonable range. I've rerun it and same problem, so after 3 hours I've stopped it. And I've thought about restoring the factory image. Unfortunately the process get stuck in the "erasing cache" step:
Code:
# ./flash-all.sh
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.452s]
finished. total time: 0.749s
rebooting into bootloader...
OKAY [ 0.131s]
finished. total time: 0.132s
sending 'radio' (45409 KB)...
OKAY [ 1.614s]
writing 'radio'...
OKAY [ 3.102s]
finished. total time: 4.716s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.13
Serial Number........: 063b7fa3f0d88342
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8700 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9284 KB)...
OKAY [ 0.540s]
writing 'recovery'...
OKAY [ 0.776s]
erasing 'system'...
OKAY [ 1.074s]
sending 'system' (721400 KB)...
OKAY [ 23.132s]
writing 'system'...
OKAY [ 49.064s]
erasing 'userdata'...
OKAY [ 13.622s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 13.895s]
erasing 'cache'...
I'm afraid that even if I let it work for hours it'll be stuck forever. What can I do? What could be happening? Any suggestions? Thank you!
Just fastboot flash the cache image manually without erasing it.
fastboot flash cache cache.img
Sent from my Nexus 5 using Tapatalk
Thank you, the command works well:
Code:
# fastboot flash cache image/cache.img
erasing 'cache'...
OKAY [ 0.513s]
sending 'cache' (13348 KB)...
OKAY [ 0.640s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.228s
[email protected]:/home/jpabloae/Descargas/hammerhead-ktu84m# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
After that and following this tutorial for flashing the factory image (Method 2) I select "Recovery" and then press Power Button + Volume UP when the small Android appears. When I do that the small Android gets grey and it outputs "Formatting /data...", but it doesn't finish. I'm not sure what could be happening, any ideas?
What is your ultimate goal?
Sent from my Nexus 5 using Tapatalk
rootSU said:
What is your ultimate goal?
Click to expand...
Click to collapse
To boot a fresh stock 4.4.3.
To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk
rootSU said:
To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, as a first step I'd like to at least have the phone functional.
These are all the steps I've followed (the bootloader is unlocked):
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.13.img
fastboot reboot-bootloader
sleep 5
fastboot flash system image/system.img
fastboot flash userdata image/userdata.img
fastboot flash boot image/boot.img
fastboot flash recovery image/recovery.img
fastboot flash cache image/cache.img
And then what I said before: select "Recovery" and then press Power Button + Volume UP. And it get stuck on "Formatting /data...".
I don't know what the recovery is doing. Try and flash a custom recovery like philz or twrp. Then fast boot flash it
Then fastboot flash the system, boot, cache and userdata and then see what happens.. If it boots etc
By boot,, I mean kernel
Sent from my Nexus 5 using Tapatalk
I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.
jpabloae said:
I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.
Click to expand...
Click to collapse
Those steps are for someone who has returned to stock and forgotten to reset the tamper flag, so the recovery they are flashing is a custom one.
Full normal instructions are linked in my signature
rootSU said:
Full normal instructions are linked in my signature
Click to expand...
Click to collapse
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.
jpabloae said:
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.
Click to expand...
Click to collapse
In the steps he doesn't flash TWRP. He boots to it.
fastboot boot recovery.img
as opposed to
fastboot flash recovery recovery.img
That means you have stock recovery already installed at that point and you do not replace it.
There is also an app called BootUnlocker, which resets the taper flag from within android (With root) so you can just use that. I use that and mine is constantly showing as not tampered
rootSU said:
In the steps he doesn't flash TWRP. He boots to it.
Click to expand...
Click to collapse
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!
jpabloae said:
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!
Click to expand...
Click to collapse
No probs
Hi all great minds of XDAdev
I have a Motorola 4G LTE XT1040, with unlocked bootloader , fastboot version 41.1A, TWRP 3.0.2.0 and stock 5.1 ROM.
I didn't have a downgrade and my phone is not bricked.
The thing is, my phone works normally until it randomly just freezes, then when I turn it on it goes to the dreaded screen with "fastboot reason: failed to initialize partition table status code 0"
If I try to select "normal startup" or something, it says "Failed to find boot image" or something like that, yet when I turn it off and on again, it starts normally. The problem is that the freezes are completely random.
I find very weird that whenever that forced restart happens it says "Status: LOCKED" when the phone isn't, and when I start fastboot manually it says unlocked and status code 3. Not only that, but can also select "Normal Startup" with no problem.
I've tried to install many ROMs and stuff through fastboot and recovery with no luck, the phone keeps restarting to the error screen and then starts normally until the next freeze.
What can I do? Is there something you think I could do to stop this? Should I post more info for you? Thank you!
fastboot flash partition
我日你打夜 said:
fastboot flash partition
Click to expand...
Click to collapse
Excuse me, what partirion should I flash? Still no luck and it's getting worse.
Flash the latest XT1040 Factory Firmware Image using Fastboot. If this does not resolve your issue, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Flash the latest XT1040 Factory Firmware Image using Fastboot. If this does not resolve your issue, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Hi Lost. First of all, thank you very much, you're a great member.
Second, well, I don't know what to do. The symptoms are very random, sometimes it just goes to sleep and never wakes up, sometimes it freezes completely, then the screen locks itself and starts to flash until I hard reboot it, sometimes it goes to the corrupt fastboot screen I'm talking about. One special case which is very common under "stress" is that it goes to the lockscreen and while the screen becomes unresponsive, the lockscreen goes on and off, and the volume/power buttons work normally. Still, as it's unresponsive, it needs a hard reset to work again.
I tried your ROM and while the proccess goes normally the problem hasn't gone away (specially the "surprise lockscreen" thing). I tried to re-unlock the bootloader in one of the lucky times the phone got into the corrupt fastboot but it only says
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.016s
I tried to use the reset to fastboot option and the phone went to a black screen with no sings of life. Then, after a hard reset and normal fastboot reboot, there's nothing "wrong" and the screen says "unlocked".
The phone is almost unusable, as it seems to work fine until it suddenly doesn't. I'm certainly baffled.
If it helps, the phone was /probably/ in KitKat when I downloaded a stock Brazil ROM months ago to make the update to Lollipop. The phone didn't have this sudden reboot problem until a month or so ago.
This is the flash log, as you requested.
D:\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.336s]
finished. total time: 0.368s
D:\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.117s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.099s]
finished. total time: 1.221s
D:\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.070s]
finished. total time: 0.136s
D:\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.718s]
finished. total time: 1.181s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk0
target max-sparse-size: 256MB
sending 'system' (257719 KB)...
OKAY [ 10.299s]
writing 'system'...
OKAY [ 11.126s]
finished. total time: 21.447s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk1
target max-sparse-size: 256MB
sending 'system' (257518 KB)...
OKAY [ 10.311s]
writing 'system'...
OKAY [ 9.891s]
finished. total time: 20.206s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk2
target max-sparse-size: 256MB
sending 'system' (256627 KB)...
OKAY [ 10.376s]
writing 'system'...
OKAY [ 15.416s]
finished. total time: 25.796s
D:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk3
target max-sparse-size: 256MB
sending 'system' (189925 KB)...
OKAY [ 7.656s]
writing 'system'...
OKAY [ 8.848s]
finished. total time: 16.508s
D:\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (60236 KB)...
OKAY [ 2.465s]
writing 'modem'...
OKAY [ 1.531s]
finished. total time: 4.001s
D:\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.025s
D:\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.023s]
finished. total time: 0.024s
D:\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (661 KB)...
OKAY [ 0.098s]
writing 'fsg'...
OKAY [ 5.681s]
finished. total time: 5.787s
D:\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.348s]
finished. total time: 0.353s
D:\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 2.999s]
finished. total time: 3.002s
D:\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.003s
Click to expand...
Click to collapse
You're not giving me enough information. I need to know exactly what Firmware Image you are flashing.
A new XT1040 Firmware Image was added in the last few days: XT1040_PEREGRINE_RETBR_5.1_LPBS23.13-35.5-1_cid12
Hi Lost, that's just the one I flashed (Brasil's newest build).
Ahasverus said:
Hi Lost, that's just the one I flashed (Brasil's newest build).
Click to expand...
Click to collapse
In the fastboot log you provided, the sparsechunks are incorrectly named.
lost101 said:
In the fastboot log you provided, the sparsechunks are incorrectly named.
Click to expand...
Click to collapse
Yeah that was due to the fastboot commands I copy/pasted, for them to work I needed to change their names. Did I do wrong?
Ahasverus said:
Yeah that was due to the fastboot commands I copy/pasted, for them to work I needed to change their names. Did I do wrong?
Click to expand...
Click to collapse
I just wanted to make sure. I do not believe the issues are related to the ROM change you mention doing a month ago. Over time, a certain percentage of Moto Gs experience corruption / failure that require a new mainboard - even if they are never dropped or get wet. The only other thing I can suggest you try is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
lost101 said:
I just wanted to make sure. I do not believe the issues are related to the ROM change you mention doing a month ago. Over time, a certain percentage of Moto Gs experience corruption / failure that require a new mainboard - even if they are never dropped or get wet. The only other thing I can suggest you try is via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Oh, I see Well, this puts me a little wary of buying a MotoG 2015 as replacement. Will try the adb thing, thank you very much.
Ahasverus said:
Oh, I see Well, this puts me a little wary of buying a MotoG 2015 as replacement. Will try the adb thing, thank you very much.
Click to expand...
Click to collapse
Perhaps I should clarify; a certain percentage of any phone (from any manufacturer) as old as Moto G Falcon / Peregrine will fail. The phones were manufactured in 2013/2014. I still have more confidence in Motorola handsets than the alternatives in the same price range.
lost101 said:
Perhaps I should clarify; a certain percentage of any phone (from any manufacturer) as old as Moto G Falcon / Peregrine will fail. The phones were manufactured in 2013/2014. I still have more confidence in Motorola handsets than the alternatives in the same price range.
Click to expand...
Click to collapse
I see. I did the adb command formatting and it kept the same. Well, off to repair it goes. I wonder if you have an idea such I can tell the technician where to look at? Thank you so much for your help!
Ahasverus said:
I see. I did the adb command formatting and it kept the same. Well, off to repair it goes. I wonder if you have an idea such I can tell the technician where to look at? Thank you so much for your help!
Click to expand...
Click to collapse
I suspect you will be told the mainboard needs to be replaced - at pretty much the cost of a new phone. The cheapest fix would be to find a used, but functional Peregrine handset with broken screen on ebay and have the mainboard transplanted by someone who knows what they are doing.
Hi All! Just so you know, something REALLY WEIRD happened.
My phone kept locking as usual, it became ever more frequent to the point it was unusable. As a final measure I flashed the lastest brazil optimized stock rom because I thought "Well, if I'm getting it repaired, better have it on the best ROM and start anew". Then something weird happened, just as the ROM flashed and it turned into the very first "Welcome" screen, the phone froze in black, to never return. No hard reset, no corrupted fastboot screen, nothing. There I thought "Yep, it's done".
I waited for like 4 hours (was really busy) and after trying to turn it on again, I decided maybe it had no battery charge, so I plugged it in on my wall charger and then, oh god, some kind of whistling sound came from inside the phone. I could just thought "Yep it's going to explode", I was sure smoke was about to come out of the phone.. but it didn't. The sound eventually died out and then the notification LED turned on. No screen however, but the LED was permanently on.
I went to sleep with my dead phone in that state. Then after a night I woke up and went to check it, and I found.. the phone turned on, working normally. Of course I thought it was just a temporal thing but, well, it's been 3 days of normal use and it hasn't turned off, or froze, or anything. It's... fine.
It sounds like magic or voodoo, I have no idea what I did, if it's fixed or it's going to die again soon. But I thought it would be good to write this as a final post, as maybe someone will experience the same in the future and would like to have some hope, if only because he may need to backup his data.
So, what I /think/ did was
- Use TWRP Recovery and do a complete wipe of everything, even in advanced setting, just everything.
- Reboot to recovery
- Use the TWRP console command to manually insert the wiping commands lost101 suggested me as "last resort"
- Flash the lastest Brazil Optimized ROM as suggested by lost101
- ??? (Probably dry its battery to the lowest possible? like, when not even the screens turns on)
- ??? (Let it charging overnight or more, use a high voltage charger -I used Blackberry's-)
- Success.
Thank you very much lost101! And well, if you had an explanation for this weird behavior it would be much appreciated. Thanks!
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!