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
Related
Please help, I've searched and searched and couldn't find anything to help me. I flashed CyanogenMod-6-19Oct2010-EXTBLUE on my sprint hero and didn't like it. I then tried to flash back to Fresh 2.3.3 and kept getting error code can't symlink/system/xbin/zcip Failure at Line 62:symlink busybox SYSTEM:xbin/zcip. I also tried several other roms with the same result. Now the only thing that will flash is CyanogenMod-6. Thank you and if I overlooked a fix for this I'm sorry, I looked all night long and couldn't find anything.
Did you try wiping before flashing back?
Also, wrong forum. Q/A would be better.
I did, wiped everything, can't restore nandroid backup either. Using recovery image 1.6.2. Sorry about posting in wrong forum.
Sent from my HERO200 using XDA App
try the command ‘fastboot erase system' will wipe the entire system partition from adb as g ****s dont like to wipe correctly
Thanks for the info, I tried but with no luck in fastboot. Kept getting error, erasing 'system' ...FAILED<remote: not allow> finished. total time: 0.000s
jbroyles_23 said:
Thanks for the info, I tried but with no luck in fastboot. Kept getting error, erasing 'system' ...FAILED<remote: not allow> finished. total time: 0.000s
Click to expand...
Click to collapse
try this first "fastboot oem unlock"
jbroyles_23 said:
Thanks for the info, I tried but with no luck in fastboot. Kept getting error, erasing 'system' ...FAILED<remote: not allow> finished. total time: 0.000s
Click to expand...
Click to collapse
I had the same problem on my wifes phone. I had to flash the file from this link.
http://forum.xda-developers.com/showthread.php?t=765237
After flashing that restarting and it loading. I then went into fastboot and tried again and it worked like a charm (meaning fastboot commands.)
I got the same error code once. I was trying the firerat mtd partition. It didn't work, would not boot. So I went into boot loader and switched to fastboot. It ran some commands so fast I couldn't see them. After that I couldn't boot nothing but cm6. Everything other rom would come up with that same exact code. But on cm6 I couldn't set cpu, use rom manager, or even terminal. After bout 8 hours of researching aggressively, I abd 'd to check to see if I still had root, I did not. I had to flash the ruu for fastboot. So, what I'm trying to get at is, check to see if you still if you have root. Because, I got that same exact code.
Wow... Glad I didn't flash that one :X
But seriously..
Did you try flashing clockwork mod and using that? That's the only other thing I could suggest but tbh what everyone else has said pretty much has to work unless it had something to do with something that altered recovery... Either that or like nfinitefx gave you should have wiped everything that wasn't there.
I appreciate everyone's help. I think I finally figured out where my problem was, I was trying Firerat's Custom MTD Partitions and after looking through my sdcard, the mtdpartmap.txt file that I had made, like an idiot, I named it mtdpartmap.txt so when it saved, it saved as mtdpartmap.txt.txt. Wish I would have caught it sooner because I reverted back to the .5 stock update and rerooted, but I think all is good now.
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!
Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?
Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?
Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app
Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?
Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
any suggestions on trying something else?
waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
What's the message that appears in ADB when you flash it?
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
Did u unlocked the bootloader?
Sent from my Redmi Note 7 Pro using XDA Labs
Naveenthemi said:
What's the message that appears in ADB when you flash it?
Click to expand...
Click to collapse
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
toyspeed said:
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
Click to expand...
Click to collapse
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Naveenthemi said:
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Click to expand...
Click to collapse
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
toyspeed said:
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
Click to expand...
Click to collapse
Did it work?
Naveenthemi said:
Did it work?
Click to expand...
Click to collapse
I actually decided to flash Superior OS instead, loving it so far!