Related
Hey guys, i've a big problem.
Yesterday, suddently my nexus s didn't boot. It was stucked on Google logo.
It's rooted and it has the cm7 rom.
I tryed to reflash with cw recovery but i have an issue.
I cannot copy nothing on the sdcard partition.
I mount it with recovery and correctly copy the img from my pc. After i sync and dismount but if i remount the sdcard i cannot see the file that i've copied before.
It seems strange because if i try to format sdcard from recovery it says "done" but the data still remain.
After that i tried to lock and reunlock my phone but it fail.
I launch the command fastboot oem unlock, correctly the two-choices window appear, i select yes but on my pc i see (erase fail) and bootload remain unlocked.
Please give me some advice to resurrect my phone.
Thanks for the support, and sorry for my bad english.
Emiliano
fastboot oem unlock wont lock it, use fastboot oem lock.
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
I had almost the exact same problem yesterday. Tried literally everything and nothing worked. In fact it kept getting a little worse with every battery pull/reboot.
I purposely re locked the boot loader, right before I went to Sprint and paid $38 for a working replacement.
Probably be a good long while before I root another phone.
Sent from my Nexus S 4G using Tapatalk
After 4.0.4 OTA update device is bricked.
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Sounds like hardware issue. Have you tried formatting the sdcard in windows or running chkdsk /F.
I Have Same Problem how can i fix it?
LeeVidor said:
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Click to expand...
Click to collapse
please anyone can help me how can i fix my mobile ...
You can't. It's a hardware common issue without any solution. Better sent it to repair. My two cents
Sent from my
( •_•)
( •_•)>⌐■-■
Nexus S
(⌐■_■)
YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
sammme problem har you fix it?
benazhack said:
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
Click to expand...
Click to collapse
please help me if u get the solution plz
zaherrrr said:
please help me if u get the solution plz
Click to expand...
Click to collapse
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
OEM unlock FAILED (remote: Erase Fail)
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
TimeClypse said:
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
Click to expand...
Click to collapse
hetile said:
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
Click to expand...
Click to collapse
I'm speechless..hair dryer works for me too!!! THANK YOU GUYS!
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
When i powered it on, the bootloader was missing so it just froze with the Android logo on the screen and after a few seconds it shut down.
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have. no adb, fastboot. So it's pretty much useless.
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless.
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it.
The phone is still covered by warranty, but I'm not sure if they are going to do it for free, because I messed with it.
I can try that story: "I was taking an OTA Update and the phone never powered on." maybe they are going to buy it.
So is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ?
RO.maniac said:
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
Logically, when i powered it on, the bootloader was missing (I've erased it earlier and the phone Powered Off just before writing the bootloader from backup) it just freoze with the Android logo on the screen and after a few seconds it shut down. Because it has no bootloader and it doesn't know how and what to boot...
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have... no adb, fastboot, odin. So it's pretty much useless...
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless...
I have no fastboot, adb, odin (that I'm not sure if works on this phone) access... :crying:
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it...
The phone is still covered by the warranty, but I'm not sure if they are going to do it for free, because I messed with it. Basically, I can try that story: "I was doing an On The Air Update and the phone never powered on..." maybe they are going to take it... anyways...
So, I'm asking you, is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ???
Click to expand...
Click to collapse
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Bigkiler5 said:
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Click to expand...
Click to collapse
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
RO.maniac said:
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
Click to expand...
Click to collapse
Like i said i have xperia x10 so i have knowledge about my device. You should ask this question in your mobile's forum. That will really help..... I think the solution they will give may be similar but in a different way.
Greets
i cant power on phone vodafone smart 2
my Vodafone won't turned on after trying to make recovery from alberto. and even did not vibrate after pressing power button to turn it on.
also it does not work at all like there are no battery attached to it. almost dead phone. and my computer not detect it anymore. and can't access fastboot or recovery screen.
do anyone fix this problem??
same problem bricked Vodafone smart ii
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
mixeristu said:
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
Click to expand...
Click to collapse
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
vodacrap II bricked
Bigkiler5 said:
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
Click to expand...
Click to collapse
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
mixeristu said:
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
Click to expand...
Click to collapse
It could be a hard brick and your info seems to confirm this but don't take my word for it. Search on google for issues with your device I seem to remember reply to a thread similar to this a while back.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
The I think.this is because when some phones are bricked they show the manufactures name such as on a hard bricked htc device it sometimes shows qhsusb_dload (don't quote me on that if my spelling is wrong) and it connects under a Qualcomm USB device driver. That is because sometimes on devices the chipset is made by Qualcomm but on your device the chipset is made by Broadcom and that why it shows a Broadcom named device driver.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Hi!
Someone has news about this topic?
bad news
cfjrocha said:
Hi!
Someone has news about this topic?
Click to expand...
Click to collapse
Yes, the bad news is that even JTAG could not repair my hard-bricked vodacrap II. My advice is to be really carefull when installing the custom android version, especially when using another sim than vodafone, some of the mods won't let you insert the network cod (eight of 1), mine didn't work with any version of the mods, sometimes I wasn't able to receive calls, sometimes to make calls, depending. Take it and keep it using vodafone or in any other case don't buy is not worthy.
i accidentally erased boot and bootloader.nor download mode nor recovery work and my pc recognize it like Broadcom USB wireless modem.Any solution?
As per title, it just happened while I was using the phone while charging. Trying my luck as I'm not in the country(Australia) that I bought my Pixel from. Grateful for any suggestion that the sub can provide. Non rooted stock rom
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Yes only bootloader. What you have mentioned do not require recovery mode right ? Cos I can't boot into it. Thanks for your reply
k.s.deviate said:
You're only able to get into bootloader and that's all? I would suggest unlock the bootloader, a factory reset will follow. Try rebooting after that. If that doesn't work, at least your unlocked and you can fastboot boot twrp and reset that way or flash a stock rom. If nothing works you "may" have a defective device. I'm no expert but I would try those things first.
Click to expand...
Click to collapse
The bootloader would have needed to have been unlocked already.
indifferent1 said:
The bootloader would have needed to have been unlocked already.
Click to expand...
Click to collapse
no it doesnt, I suggested unlocking the bootloader first, that way it factory resets. this might fix the problem, if not its unlocked so he can flash the factory image.
Bump? I'm having this problem as well.
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
graymoment said:
Same here. How would we unlock the bootloader of the phone when it's stuck in either a Google screen the reboots over and over again, or the bootloader interface (that won't load recovery)? Sorry about the noob question, but I'm not sure how to do it.
Click to expand...
Click to collapse
I'm having the same issue. My wife's Pixel entered a continuous boot loop today. It only loads the white screen that says "Google." I can enter the bootloader, but when I select "recover," it goes back to the bootloop. As far as I know, she is on Android 8.1, debugging mode is off and the phone is 100% factory.
If anyone has solved this issue, it would be greatly appreciated!
Thanks
has anyone figured this out?? this happened to me today, i was using the phone, the poof it restarted itself and stayed in a boot loop. i can get into the recovery, i tried wipe/factory reset. any suggestions? google told me i need to send it to whatever company to get it fixed or get a new phone. verizon told me to go through insurance. insurance told me to go through verizon because i may be able to use the extended warranty. went back to verizon but they wont take it because the screen cracked a year ago. its not a deep crack and it didnt affect the phone at all, never had an issue. so now i go back to assurion and now they need an affidavit about my screen being cracked. im at a loss.... i havent rooted a phone since my droid x, then s3 days. so im essentially new again!
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
thedosbox said:
Same issue here. Phone starts on the bootloader (shows device is locked), but won't start recovery or boot any further.
I'm guessing it's time for a new phone? I hadn't taken the Android 10 update yet, so it was running Pie.
[edit] it's dead - won't let me unlock bootloader or switch boot slots
Click to expand...
Click to collapse
I had the same thing happen yesterday (not long after the Android 10 update). I was finally able to get it to boot after multiple tries and it stayed up long enough for me to enable "OEM unlocking" in Developer options. Now at least I have the option of unlocking the bootloader and re-flashing the OS with an image directly from Google.
Has anyone been able to get past this problem by reflashing the image? I suspect the underlying problem is some kind of hardware fault with eMMC, DDR, or the SOC itself.
One other interesting behavior I noticed is that the only way to shut it down and stop the bootloop is to select the "Power off" option in the bootloader menu. However, if I plug it in to charge when it is fully powered "off", it will start up the bootloop again.
Same sitution here. A couple of days after installaing it suddenly went inte a G-bootloop frenzy.
Erratic though, sometimes I could boot up (2-3/40 boots) but then it froze and started again.
Also Recovery and Safemode is very hard to get into.
Got in once or twice out of 100 boots, Bootloader Fastboot is generally reachable though.
It exhausted the battery and now I'm holding off trying to interfere, until I get more info off the net.
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!
Dear friends,
I have LG Google Nexus 5 (Hammerhead D821(H) 32GB) model. Some days ago I tried to install Ubuntu Touch OS through UBports Software in my nexus 5 phone. But I forgot to enable USB Debugging first. So when I started the flash process and try to unlock bootloader, one time it show lock state unlocked. But In reality it was not unlocked. Because of this reason Ubuntu Touch OS installation is not completed and it corrupted my phone. Now I am unable to boot in android also. I also tried to re-flash my phone with Google Factory image but it was not completed because of my bootloader is locked. I don't know how i can unlock bootloader now. I used Wipe Data & Factory Reset option in Recovery Mode but it is also vain. Please help me how can I correct my phone.
Assuming you have adb/fastboot drivers correctly installed, you have to reboot to bootloader by pressing volume down + power and keeping them pressed until you see the bootloader screen. Then connect your phone to the PC and issue the following command from a command prompt:
fastboot oem unlock
Keep in mind that unlocking the bootloader will erase all your data, just like a factory reset, so backup everything first!
shivmahar said:
Dear friends,
I have LG Google Nexus 5 (Hammerhead D821(H) 32GB) model. Some days ago I tried to install Ubuntu Touch OS through UBports Software in my nexus 5 phone. But I forgot to enable USB Debugging first. So when I started the flash process and try to unlock bootloader, one time it show lock state unlocked. But In reality it was not unlocked. Because of this reason Ubuntu Touch OS installation is not completed and it corrupted my phone. Now I am unable to boot in android also. I also tried to re-flash my phone with Google Factory image but it was not completed because of my bootloader is locked. I don't know how i can unlock bootloader now. I used Wipe Data & Factory Reset option in Recovery Mode but it is also vain. Please help me how can I correct my phone.
Click to expand...
Click to collapse
perhaps it can help
https://forum.xda-developers.com/go...l-06-03-14-one-click-factory-restore-t2513937
shivmahar said:
Dear friends,
I have LG Google Nexus 5 (Hammerhead D821(H) 32GB) model. Some days ago I tried to install Ubuntu Touch OS through UBports Software in my nexus 5 phone. But I forgot to enable USB Debugging first. So when I started the flash process and try to unlock bootloader, one time it show lock state unlocked. But In reality it was not unlocked. Because of this reason Ubuntu Touch OS installation is not completed and it corrupted my phone. Now I am unable to boot in android also. I also tried to re-flash my phone with Google Factory image but it was not completed because of my bootloader is locked. I don't know how i can unlock bootloader now. I used Wipe Data & Factory Reset option in Recovery Mode but it is also vain. Please help me how can I correct my phone.
Click to expand...
Click to collapse
You can try with this toolkit http://www.wugfresh.com/nrt/
Surf the net in search of tutorial and info,there are also some videos on YouTube.
I already tried it but vain.
ilciumbia said:
Assuming you have adb/fastboot drivers correctly installed, you have to reboot to bootloader by pressing volume down + power and keeping them pressed until you see the bootloader screen. Then connect your phone to the PC and issue the following command from a command prompt:
fastboot oem unlock
Keep in mind that unlocking the bootloader will erase all your data, just like a factory reset, so backup everything first!
Click to expand...
Click to collapse
Dear Sir,
I tried to unlock bootloader with fastboot oem unlock command many times. When I used this command one time it shows unlocked but when I restarted bootloader it again shows locked.
Eh, this is not good. In my experience, this happens when the eMMC has gone bad, either faulty or write protected for some reason. I have investigated the issue and I have not found a solution yet... Even desoldering it and soldering it to a uSD custom PCB does not allow me to write to it... I am afraid you are stuck with a secretly bricked phone...
I don't know if you already tried all possible,just take a look at this thread.
https://forum.xda-developers.com/go...nexus-5-doesnt-boot-access-adb-t2521691/page3
Or even look at this,LG Flashtool.You don't need unlocked bootloader to flash.
https://forum.xda-developers.com/go...orial-how-to-flash-factory-images-lg-t2713833
The thread is quite old,but needed links are working correctly,i've just checked.