Database Info

[Q] Need some help with the 9020a

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

Broken Flash Memory?

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!

CWM not mounting anything.

So , I put the latest CWM on my tablet ( I think I was on 10.6.something) so I could reroot, but it won't mount anything. I tried to wipe data, no go.
Any time I try to write a new recovery via fastboot, it just hangs. I guess I'm soft bricked....Can anyone help?
Also, in CWM there are these errors:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't open /cache/recovery/log
can't mount /cache/recovery/last_log
can't open /cache/recovery/last_log
When I tried to mount or format any partition I got an error. Is my sdcard corrupted?

Also, if I try to write a recovery via fastboot, I get confirmation that it sends in the terminal
Code:
./fastboot -i 0x0B05 flash recovery twrp-2.5.0.0.blob
sending 'recovery' (6448 KB)...
OKAY [ 2.019s]
writing 'recovery'...
OKAY [ 3.141s]
finished. total time: 5.160s
but the blue bar does not show up indicating that the file is being written....I'm hosed, huh...dang it

Well, the good news is that I was able to cold boot my tablet, but still unable to push a recovery. I have to cold boot linux in order to get to my tablet. *sigh*

No one with suggestions?

Have the same issue.
I have tried quiet a lot but always ends in boot loop of cwm.
I finally was able to get fast boot back and to boot in my good android.
Sent from my Nexus 7 using xda app-developers app

kreutpet said:
Have the same issue.
I have tried quiet a lot but always ends in boot loop of cwm.
I finally was able to get fast boot back and to boot in my good android.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
How?
Sent from my HTC One using xda app-developers app

I have another thread ->
http://forum.xda-developers.com/showthread.php?t=2389950
I think the hard reset was the main point to bring me back to fastboot.
As fastboot was back i could do a "adb reboot fastboot" which then allowed me to boot into my android again.
As long i do not do a shutdown i can use now my android.
In case of a shutdown i have to bring back the fastboot with my PC.... :silly:
I decided to stop here as i would like to see more conclusions on that topic.
We are not allone with this issue.
I guess the main issue is the CWM version from the cyanogenmod guide line is not working with latest JB 4.2.1 on my TF300T.
But it is also reported with TWRP.
I am hoping that the xda community can give us soon a soluiton
So i still have the issue that i can not flash anything in CWM.
Also i can not write with fastboot, which i think is the main issue to even allow me to roll back the recovery back to stock.

Help!!! Nexus 5 won't boot or flash!!

Hi, I currently have a Nexus 5 that doesn't get past the flying dots screen. I tried everything and can't get anything to write on it! Nothing can be done succesfully through twrp or fastboot nor adb (i don't think) and I keep getting errors when trying to write or flash anything onto it. My warranty expired November and LG is going to charge me a lot to get my logic board. The thing is, my phone just randomly shut off after updating to lollipop and it just suddenly ended up this way. I didn't do anything physically wrong to the phone for this to occur. Is there anyone out there that is experienced who can take me through fixing my phone?!!
THANK YOU!!
-Brian

You mention TWRP, so I assume you're rooted with custom recovery. First, are you on the latest version of TWRP (2.8.6.1)? If not, flash that first.
Code:
fastboot flash recovery twrp-2.8.6.1-hammerhead.img
Next, follow this guide to freshly flash 5.1 again. This will not clear your data. Report back with the results.

Hi, sorry for the late response, I have been busy with exams and hadnt had the time to respond.
Whenever I try to flash anything onto the phone I get this message:
sending 'bootloader' <2577 KB>...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 0.478s
Anytime I try to write something it constantly fails...
but for some reason writing recovery worked....
I can't tell what's wrong. Any thoughts?
Thank You

fightonb3 said:
Hi, sorry for the late response, I have been busy with exams and hadnt had the time to respond.
Whenever I try to flash anything onto the phone I get this message:
sending 'bootloader' <2577 KB>...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 0.478s
Anytime I try to write something it constantly fails...
but for some reason writing recovery worked....
I can't tell what's wrong. Any thoughts?
Thank You
Click to expand...
Click to collapse
If you can get into recovery, do you have any errors while you wipe you're data?

i.adrian said:
If you can get into recovery, do you have any errors while you wipe you're data?
Click to expand...
Click to collapse
Yes gIget E: unable to mount '/data'

Did you try a factory reset?
SENT BY ENTANGLEMENT

fightonb3 said:
Yes gIget E: unable to mount '/data'
Click to expand...
Click to collapse
/data partition probably corrupted. There's a thread on general forum on how to try and fix it.

beekay201 said:
/data partition probably corrupted. There's a thread on general forum on how to try and fix it.
Click to expand...
Click to collapse
Could you link me to that?

fightonb3 said:
Could you link me to that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447 you could have Google it

Go and do a lot of reading

Moto G xt1032 - TWRP Internal storage 0mb

Hi,
I have Moto G (XT1032) with Optimized Stock Rom 5.1 from this topic. It was alright couple of months, but today I woke up with my softbricked phone
It's stuck on Warning Bootloader unlocked, TWRP can't access any folder (although he see folder structure, so i guess it's good sign? :crying: ), all Internal Storage is displayed as 0MB, if I try to do anything I always get
Code:
"Failed to unmount '/system' /* /data etc. */ (Invalid Argument)"
Adb recognize device, but as unauthorized, when I start ADB sideload feature in TWRP, phone is recognized as sideloaded, but when i try to push rom it's say error: closed.
Can I somehow fix this phone, or is it permanent eMMC damage?

You have to give to Wipe/Format Data and Reboot/Recovery. Later go to wipe/avanced wipe and select: Dalvik/ART, cache, data and system.

cristiansuarezg7 said:
You have to give to Wipe/Format Data and Reboot/Recovery
Click to expand...
Click to collapse
I already tried it. I got spam of error Failed to unmount... and mkfs.f2fs error: "E:Unknown MTP message type: 1"
And Reboot/Recovery just shutdown phone, I have to get to recovery thru Fastboot (Power and Vol down).

Fikoblin said:
Hi,
I have Moto G (XT1032) with Optimized Stock Rom 5.1 from this topic. It was alright couple of months, but today I woke up with my softbricked phone
It's stuck on Warning Bootloader unlocked, TWRP can't access any folder (although he see folder structure, so i guess it's good sign? :crying: ), all Internal Storage is displayed as 0MB, if I try to do anything I always get
Code:
"Failed to unmount '/system' /* /data etc. */ (Invalid Argument)"
Adb recognize device, but as unauthorized, when I start ADB sideload feature in TWRP, phone is recognized as sideloaded, but when i try to push rom it's say error: closed.
Can I somehow fix this phone, or is it permanent eMMC damage?
Click to expand...
Click to collapse
Have you tried flashing unoptimized factory fimware through fastboot? To do this, enter fastboot mode and then flash the factory firmware for your device from here.

Do you have TWRP or Stock recovery?

Professor Gibbins said:
Have you tried flashing unoptimized factory fimware through fastboot? To do this, enter fastboot mode and then flash the factory firmware for your device from here.
Click to expand...
Click to collapse
Yes, I got error, like on this video:
Code:
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.209s
cristiansuarezg7 said:
Do you have TWRP or Stock recovery?
Click to expand...
Click to collapse
TWRP

Hmm... Possibly an issue with drivers, or incorrect factory firmware. Also, have you tried skipping GPT and motoboot.img?