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!
Related
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
Hello
a few days ago I used "HTC ONE S AIO KIT" to install Jelly bean 4.2.2 on my HTC ONE S
I successfully installed the jelly bean and everything was fine
during the process, I created a backup from my phone in the ClockworkMod
today, I booted to ClockworkMod recovery > backup and restore > restore > and selected the backup file I created
the phone restarted and got stuck on the HTC ONE logo
I did everything I could in the past 2 hours, searching everywhere
even tried this command "fastboot flash boot "C:\...\boot.img"" but nothing worked - after doing this, the ClockworkMod gave me an error that said "can't mount /sdcard"
appreciate any help
Ok , I just updated to latest version of clockwork and still can not fix "can't mount sdcard" error
I have been doing this for 6 hrs now
can someone please help me ?
dnotoco some
jimlee2 said:
Ok , I just updated to latest version of clockwork and still can not fix "can't mount sdcard" error
I have been doing this for 6 hrs now
can someone please help me ?
Click to expand...
Click to collapse
install ruu original and unlok again is the most easiest for you
ZALACAYN2 said:
install ruu original and unlok again is the most easiest for you
Click to expand...
Click to collapse
thanks for the reply
I can't find the RUU for Fido/Rogers HTC ONE S
I searched for factory every where, I made a backup before but now I can't access the SD card to see if it it still there or not
jimlee2 said:
thanks for the reply
I can't find the RUU for Fido/Rogers HTC ONE S
I searched for factory every where, I made a backup before but now I can't access the SD card to see if it it still there or not
Click to expand...
Click to collapse
Well that is a pickle. Not having a RUU to fall back on.
Good news is you can still fastboot in bootloader.
So you can try different roms until one works. So at least you have a phone that works.
Push a rom to your phone
http://forum.xda-developers.com/showthread.php?t=1667929&highlight=adb+push
Flash a boot.img
http://forum.xda-developers.com/showthread.php?t=1752270&highlight=fastboot
fixing sd card mounting
http://forum.xda-developers.com/showthread.php?t=1630459
tivofool said:
Well that is a pickle. Not having a RUU to fall back on.
Good news is you can still fastboot in bootloader.
So you can try different roms until one works. So at least you have a phone that works.
Push a rom to your phone
http://forum.xda-developers.com/showthread.php?t=1667929&highlight=adb+push
Flash a boot.img
http://forum.xda-developers.com/showthread.php?t=1752270&highlight=fastboot
fixing sd card mounting
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
I followed all these steps but I am not able to get it fixed
is it possible to help me via google talk or something? thanks
I get this error now when I try to flash a recovery
Code:
C:\Fastboot>fastboot flash recovery op
enrecovery-twrp-2.4.1.0-ville.img
sending 'recovery' (7820 KB)... OKAY [ 1.426s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.251s
I searched the forum and tried different methods to fix it but still no luck
I am going crazy over this problem
jimlee2 said:
I get this error now when I try to flash a recovery
Code:
C:\Fastboot>fastboot flash recovery op
enrecovery-twrp-2.4.1.0-ville.img
sending 'recovery' (7820 KB)... OKAY [ 1.426s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.251s
I searched the forum and tried different methods to fix it but still no luck
I am going crazy over this problem
Click to expand...
Click to collapse
Where did you download that recovery from?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Where did you download that recovery from?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
from the original twrp site
Ok. Are you flashing the boot. img from the extracted rom zip that you are installing. I never used the c:/ blah blah. I always put the boot.img file in the same folder as adb and fastboot then with the phone in fastboot usb type fastboot flash boot boot.img in the command prompt on the computer. It sounds like you might have a bad recovery. Have you tried to flash a new recovery?
Sent from my HTC One using xda app-developers app
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Same issue
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
I have the same problem wit an I9020T for australia and would appreciate any advice available as well.
Send to samsung service
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Spanner127 said:
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Click to expand...
Click to collapse
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Dark_Eyes_ said:
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Click to expand...
Click to collapse
mY COMPUTER ONLY RECOGNISES abd IN SIDELOAD MODE. tHE FASTBOOT ANYTHING IS NOT RECOGNISED SO i CANNOT UPDATE OR FIX anything. Thanks for trying.
Can you try doing all the stuff you did in some another PC.
Worth a try.
Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
stevz34 said:
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
Click to expand...
Click to collapse
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Dark_Eyes_ said:
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Click to expand...
Click to collapse
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
stevz34 said:
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
Click to expand...
Click to collapse
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Dark_Eyes_ said:
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Click to expand...
Click to collapse
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
stevz34 said:
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
Click to expand...
Click to collapse
You have to rename the file to update.zip and place it on /sdcard. It will install it automatically. Stock recovery won't install custom zip file so that's why you need to do that. Let me know if it works...
Hey guys,
When i tried to flash stock via fastboot i got this error:
sending 'system' (209158 KB)...
OKAY [ 27.414s]
writing 'system'...
FAILED (remote: image update error)
finished. total time: 51.147s
Now I have bootloop with message "Unfortunely, Update Device has stopped." How I can fix partitions? Is there any way to fix my Nexus 5?
Can you boot into boot loader? If so, maybe try a different system image. 4.4.3 instead of 4.4.4? Maybe that will help?
sent from my nexus 5 running L
Could be a bad download. Re-download the latest zip and try to flash the img files individually.
- Sent from an IceCold Hammerhead!
vin4yak said:
Could be a bad download. Re-download the latest zip and try to flash the img files individually.
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
Agreed. If OP is using a previously working combination (host, host USB port, USB cable), I'd say download factory image again, checksum, if correct reflash. If OP is comfortable enough, formatting and/or erasing system partition would also be worth a try, not to say interesting to see the results.
I was also faced the same issue last week.
What I did to rectify it
I went to recovery mode where I did a wipe data factory reset and wipe cache
Then tried to flash it and again it got stuck on writing system
I keep on waiting still it says like writing and after 20min or so I finally unplug the USB cable while fastboot was still showing writing system ...then I tried to boot normally
And it worked
I don't know how
Sent from my Nexus 5
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