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!
Hello, before I call Samsung in hopes they might give me a RMA, I need help.
I had unlocked the bootloader in the past and had recently installed the IMM26D official stock rom that was not rooted. This worked fine for a month or so then yesterday the phone would not boot up anymore, just sitting at "GOOGLE' across the screen with the unlocked padlock on the bottom. So here is what I have tried ;
I was able to load CWM on it, but once in there, I could not do anything that pointed to the sdcard (mount, mount usb, format, wipe and erase). The minute I tried this, the log would show "Error mounting \sdcard\".
I then tried ODIN to see if I could reload the IMM26D, It would start and get only about 5% of the way and just stop for eternity. I tried the same cable I used before when this worked, and a different one.
And at the last step (Stupidly), I tried doing a fastboot oem lock and it locked it. Now when I go back in and do a fastboot oem unlock, the options come up on the screen and when choosing Yes to unlock, the phone just locks up.
Could this be a corrupted or damaged SDcard in the phone (now I wish it wasn't internal and rather a external one) ?
Is there ANYTHING I can do at this point? Is there a .PIT file specific for this phone that I can try loading with ODIN ?
I would love to somehow load the "stock" recovery back on it but since I can't unlock the bootloader, seems that idea is toast. It would be a lot easier to take to Sprint or send to Samsung if it didn't have CMW on it.
Sorry for the long post, but thanks in advance ..
what happened with this issue? Was it resolved, did you have it swapped with another phone?
Sent from my Nexus S 4G using Tapatalk 2
Ended up calling Samsung and sending it in, luckily it was still under warranty. Looks like they fixed it and waiting for it to return. There was nothing I could do on my end at the time, it was a corrupted internal SD card.
Hey guys, I really need some help, my co-worker tried to root his phone, but he messed up somewhere along the lines, and im pretty sure he bricked it.
When i boot the phone it gets stuck at the htc one logo, when i do manage to get into bootloader/recovery. it loads cwm even though the rom i was trying to install recommended twrp, even installing that and restarting, it would always go back into cwm... when i try to mount usb storage, it says no file or directory found (something like that)
using the all in one kit it keeps telling me to have usb debugging enabled. i really doubt my co-worker enabled this; besides cant even boot the damn phone to check.
all i want to know is it possible to be able to mount the storage on the phone?? once i can figure that out i can start everything from scratch.
The phone not bricked yet ....just relock and ruu your co worker shouldn't be messing if he doesn't read... So go into fastboot and have the apporpiate set up on the comp type fastboot oem lock from a comnd prompt within the fastboot folder and than find the ruu that is appropiate...
If you have any questions bout fastboot or ruu feel free to ask
If the screen comes on, its not bricked. Not even close.
Since the device already has a custom recovery (CWM), it was already bootloader unlocked, so rooting and the all-in-one kit is not needed.
USB mount does not work in CWM, its a known issue. And one of the several reasons to not have CWM in the first place.
You can either relock and run RUU as previously stated to return to stock.
Or you can use adb to flash TWRP (then mount USB and put a ROM on the SD), or push a ROM to the phone with adb.
Hi there,
i have a huge problem. As there was no warrenty left for my One S I thought about to change the firmware to CM11.
I have to admit that i don't have any experience in doing such things, but i thought, it couldnt go wrong if i follow a tutorial.
So at first i unlocked the bootloader via HTC website and istalled TWRP 2.7.1 (latest version). Everything went well, I placed the ROM into the phones root directory, started the recovery and then whiped it before choosing install and selected the file. After about 30 seconds the phone reported the step was successful and i pressed reboot. Then there was the HTC starting screen and then a black screen.
After that i had no reaction but the blinking buttons when i press the power button for a longer time. But it changes nothing. No normal boot. No access to fastboot. Only if i connect it to my PC there is an aditional device to see, but whitout any access.
I know I did wrong but i have no idea what or how to fix it. I hope you can help me.
ElDorado1993
Now i found a way to get access to fastboot again, but i dont really know what to do now.
Can you give me an detailed tutorial, for jelly bean or kitkat (dont matter) that is surely working now?
My main problem is that i can't copy my files into the root directory as i cant boot the phone.
Does it show up in computer connected devices?
If it does, download stock kernel and ROM and upload to phone and go into recovery[power +volume up while off] and flash them both kernel first.
Sent from my ZTE_N9511 using XDA Free mobile app
The problem is the phone wasnt ever shown as device on the pc (like a flash drive) since version 4.1 so I allways needed some tricks like airdroid. So i suppose i need adb commands to copy files and i dont have so much experience in doing this.
Do you know how to use adb?You don't need adb I just wanted to know to see if it shows up there and not on computer you simply need to install the drivers.Try holding down all 3 buttons to see if it powers down. Do what it says http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930 if works go into fast boot. Does it say locked or unlocked. If unlocked go herehttps://github.com/koush/UniversalAdbDriver and get the windows installer if your on windows.
Sent from my ZTE_N9511
I now found out how adb and fastboot are working, but the main problem now is, that it says the sdcard cant be mounted. I tried this tutorial http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 but i dont know how to do the first step. Du i need an extra file and where do i get it from and how to use it. As long as i dont get back this access, i couldnt install any OS. I tried also sideload. It was able to copy but cant install because of the missing sdcard access.
I hope you can help me to become my phone running again.
Go here http://m.youtube.com/watch?v=xWmnHwkDrKk but first type adb devices in cmd. If it shows ur HTC type adb shell and and type mount sdcard next to the "#" once it appears although you should be using the fastboot shell not adb commands.adb should only work on a powered on device or you can use fast boot in cmd while phone is in fastboot not recovery(you did say the phone can go into fast boot right?). Just make sure you got the right drivers and both fast boot and adb. You should get Koush's Universal drivers from my previous post since some phones have multiple drivers and MAY cause problems with cmd. Also HTC one S doesn't have expandable storage correct?
Sent from my ZTE_N9511
Wow. Now I incidentally soft bricked my phone again if you would believe it and nothing works this time.
Have you been able to fix?
Sent from my ZTE_N9511
Okay, i forgot to write but adb and fastboot are working on my Mac. I use the Mac because Win 8.1 has the known driver problems.
I tried a lot now, but i recognized maybe the main problem. My phone is still S-ON in bootloader. For sure thats the problem. Do I need to get rid of it and how do I do. The tutorial i used hasn't mentioned this step, maybe the person was still S-OFF.
The first thing i try now is to flash the original recovery, lock the bootloader and execute the original signed RUU to get back the original software first. Im going on holiday on tuesday and it would be a pitty without the phone. When I get it working i will leave it, and thy it again, when I'm back. Otherwise.......****
Use this tutorialhttp://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/unless its the one you used already. From boot loader you were supposed to have gone to fastboot.boot loader has to be unlocked.From fast boot you flash TWRP.IMG which happens to have a special adb side load feature under advanced options. There you upload another ROM and kernel.here is the full list of supported devices as I don't know what variant or carrier you havehttp://teamw.in/twrp_view_all_devicesAlso, a stock kernel is optional but it always seems to fix my problems.
Sent from my ZTE_N9511
Thank you. But I already did it like this. The issue is, than after using sideload successfully the installation fails because of the known "unable to mount storage" text. And i don't know what to do wrong.
Like I already said, my phone is still S-ON, but can this make a difference?
Now i got it to bring the stock ROM running again, and as I'm on holiday for a few days I'm happy it is working again.
But one thing is left. It seems like there is no 3G/HSDPA connection now, only EDGE. I dont know what went wrong. Did you hear about this problem.
By the way, my phone is the standalone version whithout any provider.
Search the forums about edge only. There is a huge thread on this.
So, Ive tried to boot into fastboot and recovery on my xperia z3 and I get nothing but a black screen. Is this normal? Ive tried the adb commands to reboot into fastboot and recovery and still nothing but a black screen. Ive tried volume up and plugging in the USB cable and get the blue LED and a black screen. Ive tried the powering on and pressing volume up and down repeatedly and still nothing.
I have the T Mobile International supposedly Factory Unlocked version 6603.
Also, whats the point in having a SD card to expand memory if you cant install any apps to it? I understand that you can put music and such on there but if you start installing any large games the 16GB internal is gone quick and you cant put any apps on the SD Card.
This phone is great but cant install to the SD, cant change the install location as its not supported in Kit Kat. Sony's ROM doesn't allow move to SD anymore, cant boot to fastboot to flash can view recovery..perhaps there is something I have not read about this phone yet in the forums.
Anybody have any sugestions?
J
There is no stock recovery on xperia devices, you need to install one yourself. Also, there is no UI on the phone when in fastboot. You can just send fastboot commands from a terminal on your PC
Currently the only was to do that is to unlock the bootloader (Just google "Sony unlock bootloader" to find out how to do that) then flash a custom kernel from the development sections to get recovery and root
Terminal doesn't show any devices connected. Can't start a shell nothing in fastboot. I have not tried to use the command to flash the kernal I guess that works?
There is really no fastboot menu just a black screen huh? Strange
Jason0071 said:
Terminal doesn't show any devices connected. Can't start a shell nothing in fastboot. I have not tried to use the command to flash the kernal I guess that works?
There is really no fastboot menu just a black screen huh? Strange
Click to expand...
Click to collapse
Yes just a black screen.
Have you unlocked the bootloader? Have you installed ADB and fastboot drivers?
No I've not done these things yet. I was thinking there was something wrong with my device. It seems it's functioning correctly. I'll proceed with unlocking the boot loader and see how it goes
Jason0071 said:
No I've not done these things yet. I was thinking there was something wrong with my device. It seems it's functioning correctly. I'll proceed with unlocking the boot loader and see how it goes
Click to expand...
Click to collapse
Make sure you read the warning first
What's the worst besides bricking the phone?
Jason0071 said:
What's the worst besides bricking the phone?
Click to expand...
Click to collapse
You will loose some of what makes Sony camera so good on this phone + some audio / video post processing.
Myself, I have rooted immediately after getting this phone since coming from HTC phones I did not expect any noteworthy disadvantages only to learn later that I have reduced the phone's functionality forever.
I still like a phone a lot; but it bothers me that a lot of functionality in this phone is based on software wizardry rather than hardware quality.
Being so used to flash custom ROMs often I am beginning to realize that Sony might not be such a great choice, although, once again Z3 (dual) I own has a lot going for it compared to current HTC phones.
Agreed opted not to root