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
Related
Situation:
Phone unlocked
Clockwork mod installed and working
Phone stucks at boot - i think /system partition has no data
No nandroid backups in sdcard
no adb shell
no adb, only fastboot
when i try fastboot flash system system.img, i get this error
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (155194 KB)...
OKAY [ 24.396s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 24.401s
i have tried with different system.img files like these
http://forum.xda-developers.com/showthread.php?t=968403
i have tried in windows and linux
i have tried putting system.img in tools folder
Anyone can help me?
Sry for my english
Thanks
Solved with boot image and system image from http://forum.xda-developers.com/showthread.php?t=973534
got the same problem in my nexus one is there a fix for it?
Amritttt said:
got the same problem in my nexus one is there a fix for it?
Click to expand...
Click to collapse
- you need boot unlocked + clockworkmod recovery. do you have backups in sdcard?
- with fast boot you can flash boot and system
fastboot flash boot boot.img
fastboot flash system system.img
you can find that files searching nandroids backups for your device
Odin works great and if you are afraid or dont know how to use odin
another thing you could do if you dont have any roms or nandroid on sdcard and you wipe data is load clockwork and go to "mounts and storage" select "mount sdcard" plug your USB from computer in and you will be able to drag and drop rom onto you sd card from clockwork and install that way
http://forum.xda-developers.com/showthread.php?t=947950
Use Odin
i got the same problem this fixed it
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
romka7 said:
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
Click to expand...
Click to collapse
If I remember right, it's actually EXT4 and android uses FUSE to make it look like a FAT32 partition to a connected machine.
I would have suggested RUU, but it seems like that's not an option for you. Good luck with your phone, man.
If worst comes to worst just go to att and say it broke randomly, I don't think they can tell it's rooted if you messed it up that badly
Sent from my One X using xda premium
Did you try just running the RUU ?
Ok, I beat it to death.... got it working. Somewhere in my trial and error process I ended up flashing to CWM recovery, which did nothing new for me, then I pushed TWRP again but the 2.1.8, was on 2.2 when the problem started.... all of the sudden ADB started working, not sure what happened on the newer version. I still did not see my SDcard, but I was able to push a version of cleanrom to the system partition. The install did not go, but the the process it formated the sdcard to the proper format.... or it restored some setting. I was then able to mount SD in TWRP and installed newest version of CleanRom.. All good now.... its all a learning process I guess
Hi Xda members,
I've been running Jelly Beans stock OTA (rooted though) since it was released here, and have been working out great so far.
A couple of days ago I got a number of strange notification pop-ups in just a few seconds while I was watching the screen...
The messages read something like "some app is requesting to run as super user" (well, don't remember which app or the exact message). Anyway, as I hadn't start any app at this point I thought it was a bit strange when several of these message popped up.
So I rebooted the mobile to see if it would make the pop-ups stop, but after this the mobile didn't boot up again, it just locked at the first boot screen (showing the Google text and the "Unlocked" symbol)...
I can still boot into the bootloader and the recovery. And I can reprogram the bootloader and the recovery partition through fastboot, but when trying to write to the boot partition through fastboot I get this output:
Code:
fastboot flash boot ./boot.img
sending 'boot' (8192 KB)... OKAY
writing 'boot'... FAILED (remote: Write Fail)
And in the recovery when I try to "choose zip from sdcard" I get "E: Can't mount /sdcard/".
Do you think the internal flash memory might be broken or could it be the partition table, or what else?
Best regards,
Olle
Same problem here...
I've got a similar problem oll3
Last saturday couldnt get my nexus s w/ stock JB to boot up, it just hanged on the Google logo. I thought it was due to a failing charger which I replaced. Then the phone worked fine for some hours until I had to reboot it. Again, stuck on Google logo. I tried booting to recovery and stumbled into the same error "E: Can't mount /sdcard/".
I've tried pretty much everything. Got the sdcard mounted couple of times which was enough to quickly take backups. However the sdcard mounts at random. Not at every boot, and yep, I've tested several old&new versions of recovery's. When the sdcard mounts, if managed to install several different rom's successfully but only to get stuck on the Google logo.
So I think it really can be a internal flash problem. I'll flash a stock rom and take the phone to the dealer for maintenance or replacement...
I'd be grateful if someone would point out how to get pass the google logo
aktuls, thanks for answering.
Unfortunately my guarantee period has passed since a couple of month. Hope you'll get your Nexus fixed, and please update me if you make any progress.
oll3 said:
aktuls, thanks for answering.
Unfortunately my guarantee period has passed since a couple of month. Hope you'll get your Nexus fixed, and please update me if you make any progress.
Click to expand...
Click to collapse
Actually I'm happy report some progress!
After busy night trying and also fiddling with the updates trying to get the JB 4.1.1 original flashed, I stumbled into error that said I have an old bootloader! Ok, I checked up the latest needed for JB 4.1.1 which the adb reported as "i9020XXLC2" and flashed it. Now I got the rom flashed and the phone has been rebooted several times today without any hiccups. :good:
So I suggest you and everyone else, stuck in Google logo, having flashed some JB based rom, to check you bootloader version and update it if needed ! Hope this helps some ! :angel:
If you have a custom recovery, there's also a chance you have that version which can't mount the SDcard. I don't recall the exact version, but one of them won't mount the SDcard with that error. Updating it fixes that.
instead of flashing each partition: boot,...
type: fastboot -w update "image-...-...zip file"
I have now run fastboot update with factory image of different versions. At least it successfully flashed boot partition, but instead it now fails on the writing of system:
Code:
$ fastboot -w update soju-jro03l/image-soju-jro03l.zip
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........: xxx
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (3964 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (4308 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (333431 KB)... OKAY
writing 'system'... FAILED (remote: Write Fail)
Have tried with different bootloader versions, recoveries, different versions of CWM recovery. Nothing seems to get me past the writing of system partition. In cwm 6.0.1.0 recovery I still can't mount/format the sdcard.
Partitioning the sdcard in cwm gives me "Done!", but when looking in the log file it reports some error about "you are not using parted v1.8.8.1.179-aef3!", don't know what that's suppose to mean.
Anything else I should try?
Plug your phone to pc then right click in removal disk, format, fat32, uncheck quick format. It will take some time to finish but eventaully u will fix your sdcard
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Cascabreu said:
Plug your phone to pc then right click in removal disk, format, fat32, uncheck quick format. It will take some time to finish but eventaully u will fix your sdcard
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Click to expand...
Click to collapse
Unfortunately I am not able to access the sdcard from my PC as it seems... In cwm recovery when trying to mount USB storage I get "E: Unable to write to ums lunfile (No such file or directory)". Is there some other way?
oll3 said:
Unfortunately I am not able to access the sdcard from my PC as it seems... In cwm recovery when trying to mount USB storage I get "E: Unable to write to ums lunfile (No such file or directory)". Is there some other way?
Click to expand...
Click to collapse
lock and reunlock the bootloader to format it
try that
Cascabreu said:
lock and reunlock the bootloader to format it
try that
Click to expand...
Click to collapse
Locking worked alright, but unlocking fails with message:
Code:
$ fastboot oem unlock
...
FAILED (remote: Erase Fail)
More ideas? : )
Nop sorry. Now that its locked send it to a repair shop and say that it doesnt boot up...
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
Cascabreu said:
Nop sorry. Now that its locked send it to a repair shop and say that it doesnt boot up...
sent from my Nyan NeXus S
Click to expand...
Click to collapse
Thought so too, will try that.
Thanks anyway!
Hello,
I have a Motorola Moto G XT1032 on which I have successfully unlocked the bootloader. I can access to recovery (CWM 6.0.4.7) and transfer files using adb in this mod. However, CWM does not get past the splash logo (I do get the occasionnal lag when CWM rebuilds the cache, but this is another minor issue). I have tried the following ROMs, installed each after formatting /system, /data and /cache:
cm-11-20140308-SNAPSHOT-M4-falcon.zip
cm-11-20140405-SNAPSHOT-M5-falcon.zip
cm-11-20140504-SNAPSHOT-M6-falcon.zip
cm-11-20140613-NIGHTLY-falcon.zip
cm-11-20140730-NIGHTLY-falcon.zip
cm-11-20140823-NIGHTLY-falcon.zip
None worked. I did checked the md5 checksums. I have also tried installing GApps using gapps-kk-20140606-signed.zip .
I do not know how to get more information on what happens when CM11 stucks during the boot. 'Show log' from recovery only prints some configuration information as well as:
Code:
I: Checking for extendedcommand...
I: Skipping execution of extendedcommand, file not found...
From what I undersood, extendedcommand is an optional executable used to launch stuff at boot.
I found some ideas from another thread and tried locking/unlocking oem:
Code:
$ fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.057s]
finished. total time: 0.057s
$ fastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.037s]
finished. total time: 0.037s
$ fastboot oem unlock
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.008s
Additionnally I also reinstalled recovery:
Code:
$ fastboot erase recovery
$ fastboot flash recovery CWM-swipe-6.0.4.7-falcon.img
I did have a message "Mismatched partition size (recovery)" but CWM starts fine. I then reinstalled CM11 again, but it did not help either.
Would you have further instruction to try and get CM11 to work?
Just a short post to avoid the thread from being buried down into oblivion.
Same happened to me days ago. I was unable to install any custom ROM. I was in Enhdroix and I flashed the original version of my ROM via fast boot but every time I tried to install a custom was stocked and bootlogo. Some how I figured that the boot loader of the original version was corrupted so I flashed a different stock ROM, after that was able to install custom.
The recovery message is normal you can check videos or post.
Hope this helps my friend.
To prevent any further problems, I also recommend that you flash twrp or philz recovery because the stock cwm recovery is outdated and it will give you problems while flashing ROMs in the future...
---------------------------------------------------------
Hit the thanks button if I helped you 8)
---------------------------------------------------------
ThisIsMadness said:
Just a short post to avoid the thread from being buried down into oblivion.
Click to expand...
Click to collapse
Check previous answers
Thanks for your help, I finally got it to work!
If someone gets stuck with the same problem, here is what I did:
first, fastboot flash recovery to TWRP
reinstalling (wipe and so) CM11 from TWRP did not work any better
I reinstalled a stock ROM following http://forum.xda-developers.com/showthread.php?t=2542219
I did not boot at all (no logo), but I could still get to fastboot
I reinstalled TWRP, and then CM11
it worked!
From my own diagnosis, I must have accidentely corrupted a partition with fastboot flash. Or maybe I wiped something that I should not have. Anyway, by reinstalling stock, I restored all the partitions and could install CM11. I do not think CWM is to blame here.
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.