I have sitting here a Samsun Nexus S from Fido in Canada. From what I can tell that makes it the 9020a.
It belongs to a friend and he really wanted CM7 on it after seeing CM7 on my Nexus One.
I helped him root and unlock the phone along with installing ClockWork Recovery.
I left before getting around to installing the ROM. He downloaded it through the ROM manager. After the phone restarted though he was just presented with the white Google logo and it never moved on.
I am trying to help fix this, but he wiped the sdcard and the backup that was done when ROM Manager did a backup.
Here is the problem though, I have installed about 5 or 6 different recovery ROM's trying to get this to work, even more ROM's themselves.
I have tried combinations of ROM's and recovery ROM's.
All of them end with me staring at a white Google logo.
I have access to fastboot and the recovery ROM still. So I decided to just go back to stock by flashing the partitions from fastboot. Some of them will flash, but others won't. I can flash the cache, but I can't flash the recovery, data, or system partitions. When I try I get
sending 'recovery' (8192 KB).
OKAY [ 1.029s]
writing 'recovery'...
FAILED (remote: Write Fail)
or this for Data
FAILED (remote: Unkown Partition)
or this for System
FAILED (remote: Write Fail)
Any and all help would be greatly appreciated. Right now the phone is basically bricked. I am going to sleep but will check back in the morning. If I left some information out please let me know.
Did you unlock the bootloader?
fastboot oem unlock
Then follow the on screen instructions. I had to do that to flash certain *.imgs. I think it has to do with the security checks....
Sent from my Nexus S using XDA Premium App
Does the white Google logo have a padlock symbol at the bottom of the screen? If not then the bootloader is locked. What root method did you use?
Sent from my Nexus S 4G using xda premium
And also what were the commands you used to flash the images.
Sorry for the late reply. Some stuff at work blew up and kept me out late.
atrixboy:
Yes, the bootloader is unlocked.
Rem3Dy:
Yes, there is a pad lock at the bottom of the screen.
suksit:
The commands run originally was just to unlock the phone (fastboot.exe oem unlock). The phone was then rooted and the OS was launched. Once in the OS RomManager was downloaded and installed. Through RomManager clockwork recovery was installed. After that CM7 was selected as the Rom to install. The phone rebooted, did its thing in recovery, then booted to this black screen with white Google logo which I have yet to get passed.
Since then though I have flashed several different recovery images trying to get this to work, right now the recovery is: CWM-based Recovery v4.0.1.4
If I install a Rom from zip through the recovery it says it was OK, but I still get the white logo and nothing else on boot.
I have been trying to just flash boot and system images at this point and am having no luck.
When I try the following:
C:\1>fastboot.exe flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.032s]
writing 'boot'...
FAILED (remote: Write Fail)
finished. total time: 1.039s
C:\1>fastboot.exe flash system system.img
sending 'system' (151459 KB)...
OKAY [ 19.073s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.078s
C:\1>fastboot.exe flash data data.img
sending 'data' (4 KB)...
OKAY [ 0.002s]
writing 'data'...
FAILED (remote: Unknown Partition)
finished. total time: 0.032s
If I boot the recovery and go into adb and try and mount the same 3 partitions I get the following:
mount /system - works fine
mount /boot - mount: can't find /boot in /etc/fstab
mount /data - this one runs for like 5 minutes and then fails with the following error: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
I just realized that there is some more information on the screen of the device while in fastboot and I try this. When I try "fasboot.exe flash boot boot.img" I get the following on screen:
Exceed blocks 0x00000020 > 0x0000001e (The exact number of zeros may be wrong, hard counting them at that size)
FASTBOOT STATUS - FAILWrite Fail
Fastboot also indicates at the top of the screen: FASTBOOT MODE - NO BOOT OR RECOVERY IMG
I am able to get into the recovery though...
Not sure what other information to include.
I have run out of ideas. Does anyone know where else could I go and get help with this?
are you flashing *.img files in cwm or bootloader mode?
In fastboot I am flashing .img files, from CWM I am trying to flash .zip. I downloaded a nandroid backup and tried restoring that from within CWM with no luck.
try formatting all memory locations except sd card in "mounts & storage" and fix permissions and then flash img files.
What exactly do you mean by "fix permissions" ?
Edit: Stupid question, found it under advanced.
So I formatted each of the partitions, did the fix permissions option, and then booted back into the bootloader and tried to flash the system.img file with fastboot. It failed.
C:\1>fastboot.exe flash system system.img
< waiting for device >
sending 'system' (151459 KB)...
OKAY [ 19.001s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 19.006s
Thank you in advance for trying to help, I really appreciate it.
Edit: I just realized at the bottom of the bootloader after trying to flash the system.img file it now says in bold orange text:
Invalid Magic Code! 0x00000003
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
litanyoffail said:
When in CWM recovery, can you mount each of those partitions, or does it spit out an error? (mount /sdcard && mount /system && mount /data etc...)
On the subject of the model version, the model number should be on the sticker under the battery. Mine says "GT-i9020a" and in the bootloader it says my carrier is AT&T, even though my phone is from Telus.
Click to expand...
Click to collapse
I can mount:
/sdcard
/system
/cache
When I try and mount /data it takes 15 minutes and then fails. Says: Error mounting /data!
The model is most definitively i9020a, I just checked under the battery. Thanks for telling me where that is.
milesman said:
did you try this? http://forum.xda-developers.com/showthread.php?t=884093
Click to expand...
Click to collapse
I did, but I am trying it again now.
So, I tried that Nandroid backup again, and it says MD5 mismatch. I checked the MD5's myself and they match. The ones listed in the MD5 file, and the files match.
I tried flashing the *.img files from fastboot, and get that failed to write message I posted earlier.
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
milesman said:
install this in cwm su-2.3.6.1-ef-signed.zip
let me know if this lets you mount etc...
Click to expand...
Click to collapse
Did this, still having the same problems.
Possible the bootloader unlock corrupted guys? Sounds to me like either a bootloader error else the nand may have died. Unlikely but possible. I read somewhere about loading a custom bootloader to the Nexus S. Maybe try looking for that, I know it was here on XDA, only place to get good help IMHO. The orange error codes are generally related to a corrupt bootloader/bad nand chip to the best of knowledge, feel free to correct me if I'm wrong.
Sent from my Nexus S using xda premium
If the nand was shot, data, SD and system wouldn't mount either. I had a busted nand on my nexus last month, had to send it in.
Seems like the bootloader is unlocked, but acting as if it is locked. Do fastboot devices, make sure the numbers match on your screen and your command prompt.
Something I noticed: If the fastboot flash recovery is failing, how did you get the multiple recoveries on prior to posting here?
Sent from my Nexus S
Hi all,
I just got my brand new LG N5 (hammerhead d820(h) 32gb HHZ11K)... and after a week of using it i was sending a chat to a friend and the screen shoock a little then the whole machine froze. I had to reboot, but when I did, it froze when the colored balls appeared. After many attempts I decided to just reflash the whole thing with the hammerhead-kot49h factory image.
But when I do that, it never succeeds
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.475s
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.505s]
writing 'radio'...
OKAY [ 2.849s]
finished. total time: 4.355s
and to just test, i tried
fastboot flash boot boot.img (succeeds)
fastboot flash recovery recovery.img (succeeds)
fastboot flash system system.img (fails - device freezes on 'erasing...'))
fastboot flash userdata userdata.img (succeeds)
fastboot flash cache cache.img (fails - device freezes on 'erasing...')
I read somewhere that it is best to use the manufacturers tools, so I downloaded the LG Nexus Root Kit, but that was a mess.. still trying)
To me it seems like the internal memory just blew up!
so, my questions are:
Is this bricked?
Can i reformat and somehow mark bad section of memory off limits? like e2fsck/mkfs does?
Can i replace the internal memory myself somehow? (I live in Argentina, and to get this RMA'd, fixed and returned will take many many months and cost $$$ in import fees, assuming it doesn't get 'lost' in customs, like half my stuff)?
Any ideas?
It seems rather bizarre that a brand new N5 justs bricks itself for no reason... but, here I am.
Thanks for any advice
Hi. I can't get passed the google splash screen on a Nexus 5 D821 and could use some help.
Here are the facts:
* The owner of the device told me it bricked after an update.
* The Bootloader is unlocked. When i tried to lock i got the following message:
Code:
fastboot oem lock
...
OKAY [ 0.041s]
finished. total time: 0.041s
But it wasnt persistent. When given reboot comand the phone switched OFF instead. I turned it on to bootloader again and it was still unlocked.
* I tried flashing stock rom LRX22c manually after a failed attempt with the flash-all script. I got the following error for bootloader, radio, boot and recovery:
Code:
FAILED (remote: flash write failure)
* I tried erasing cache and flashing userdata but the after over 60 minutes waiting i came to the conclusion that i wasnt going anywhere and just rebooted the phone.
*The only thing im actually able to flash without an error message is system.img:
Code:
fastboot flash system ~/Downloads/hammerhead-lrx22c/image-hammerhead-lrx22c/system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (981472 KB)...
OKAY [ 30.934s]
writing 'system'...
OKAY [ 62.705s]
finished. total time: 93.767s
* I tried booting TWRP, but i was unable to mount the file system (perhaps because i wasnt able to flash it. i used "fastboot boot twrp.img").
Are phones technically able to get to splash screen or bootloader with a damaged NAND or EEMC chip? Im starting to consider the possibility of a hardbrick. Why would i be able to write system.img if that was the case though? Any help is welcome
===============================================
alright so im pretty sure its a hard brick. The emmc is dead. its a shame :/ guess ill just try to sell it for parts. I would delete this thread because its pretty useless, but i have created my account a few days ago, and i ddont know how to.
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Ben36 said:
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of the imgs in their respective order. they all failed. i got the error
Code:
FAILED (remote: flash write failure)
. system.img was the only .img i was able to write, and i was wondering why. Also, when i try fastboot reboot the phone switches off. It doesnt reboot.
Hi everyone,
Long time Lurker, first time poster.
I have a D821 (Red Nexus 5) that appears to have eMMC issues, but I just need another opinion before I give up;
I have a bootloop and I can't remember how I got into it as I replaced this Nexus 5 with another Nexus 5 18months ago. The bootloop looks like the android-cogs-wiggly-antennae updating/installing screen.
Here's the current firmware stats:
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D821(E) 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11k
BASEBANDVERSION - M8974A-2.0.50.2.30
CARRIER INFO - None (from Play Store, but missed RMA opportunity)
SERIAL NUMBER - 06e[XXX]85d[XXXX]917 -> maybe I shouldn't post this? I've ommited chars.
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
So, I try to use fastboot to reflash stock using the flashall batch file, and this is how it goes:
Code:
sending 'bootloader' (3124 KB)...
OKAY [ 0.226s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.394s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
< waiting for device >
It then restarts into a different bootloop, where it restarts by showing the "Google" & the unlocked padlock a few times. It then turns off and shows the charging icon, indicating the device is off.
When I restart by holding Power + Volume down, I get further through the FlashAll.bat.
Code:
sending 'radio' (45489 KB)...
OKAY [ 1.612s]
writing 'radio'...
OKAY [ 3.123s]
finished. total time: 4.735s
rebooting into bootloader...
OKAY [ 0.122s]
finished. total time: 0.122s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
Okay. So, I'm not sure if this is consistent with internal memory failure.
Here's the capability of the phone right now:
I can flash radio, TWRP custom recovery & userdata.
I can erase bootloader & cache.
I can send almost anything through fastboot flash [whatever] [whatever.img].
But I can't erase system. I also can't write a system, boot or cache.
Lastly, I can boot into TWRP recovery 3.0.2-0 (and get recognized on adb), however I get a whole range of mounting issues.
For instance, I can't mount anything, "Internal Storage" shows (0MB), but using the ADVANCED->FILE MANAGER, I can view all the files still on the eMMC, including signs that my flashing has actually written to the system. When going into the WIPE-ADVANCED->REPAIR-OR-CHANGE-FILESYSTEM section, I can see SYSTEM uses 1009MB, with 50MB free. I can see cache uses 689MB. The Dalbik / ART cache & internal memory show "Invalid partition selection", and /data shows "0MB".
Also, when I "Reboot to Recovery", I get stuck in the bootloop.
Is this dead? Or do I just need to use fastboot in a particular way to get out of the deep, bricked trench of a bootloop? It's no longer even showing the Android updating bootloop.
On TWRP, go to Wipe -> Format Data. I got the problem fixed that way.
KAGE-008 said:
On TWRP, go to Wipe -> Format Data. I got the problem fixed that way.
Click to expand...
Click to collapse
Unfortunately, I can't wipe Data. It fails to mount /Data, and cannot wipe data.
The simplest solution IMHO is to find a used Nexus 5 with a smashed screen and working motherboard to perform a motherboard swap.
Have you tried dling again, could be a bad dl. Also, try flashing each partition in fastboot separately.
EXACTO
I have exaclty the same issue [email protected][email protected] hope you found a solution !
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if it still available .. but beware , pay attention to the instructions
Help. I got an error today while trying to power on. It was something along the lines of validation failed. Cannot boot.
Then i tried installing the stock rom with the help of fastboot. It was going well. It even had success. But then I ran the command fastboot reboot and the phone doesn't turn on. Stays on black screen. Tried charging. No luck. I don't get any visual confirmation. Can I do anything to fix this phone?
Good. Via ADB the command adb devices or fastboot devices returns something? And the computer even recognizes him? It could be the same case that happened to me.
A year ago his screen turned bran and I sent in an assistance (it was updated in android stock 6.0, until it happened)... Only with the ROM it had, the system did not recognize the new screen (which was changed). Result: They downgraded the android (returned to 5.0) and now I'm breaking to solve an error, i can not even flash any twrp .... The message is
sending 'partition' (32 KB)...
OKAY [ 0.135s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.732s
Same issue here. I've been attemting to run stock firmware on mine. But I've been getting the same error. Idk if it's fixable and my recovery boot is corrupted.