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!
Related
Hi I have stock Nexus S GT-9020T UK running ICS 4.0.3 (which I installed after the stock update failed - by placing the file on SD/Card in recovery mode and installing) . However I'm having problems with battery, radio (Wireless & 3G) and it won't re-boot after it's turned off. (I get round this by heating it up with a hairdryer then it will re-boot eek!).
So to try and resolve some of these issues I have tried to unlock the phone with fastboot. Fastboot runs ok 'fastboot devises' shows serial number but I get a failed message rather than an unlock. Phone just goes back to recovery screen as if nothing happened.
I was hoping to unlock, root and then try a different OS.
So next I have tried to re-install 4.0.3 but when in recovery mode I can't access the SD/Card to run the file. I get a failed to access E:/drive message.
Can anyone give me any pointers to help either unlock and root phone or re-install 4.0.3?
I have been following the relevant guides on these forums but am now stuck for ideas!
Thanks Dinger
I read somewhere about having to heat it up for it to boot. Ended up the nand chip was dying/dead. Exchange if you can else it looks like a hardware failure.
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks. bit disappointing, Samsung customer services suggested I tried Samsung Kies but my Nexus S was not recognised by that either. As it boots into recovery mode I was hoping it was a software problem rather than hardware.
i have a big problem
i buy a stock phone (I9020T)
but i cant unlock the phone with any method and cant root or flash and ...
phone random correctly boot and random (90%) hang on google logo
i cant do anything with phone when randomly boot on ! (many error)
i even cant erase and restore factory device (failed) in recovery mode (after press all keys i see standard menu)
i must 10 - 20 time pull battery and power again to ics boot up
but every thing back to a point (last user setting and photo-gallery and ...)
and dont save anything in next boot !!!
how can check internal memory for any damage ?
i thing have exact problem http://forum.xda-developers.com/showthread.php?t=993403
but phone is LOCKED and cant test that methods and cant return to samsung :'(
please helpppppppp me
Carrier TMB
LOCKED
Rom: ICS (no root, no mod, no customize)
bootloader ver: I9020XXKL1
Baseband ver: I9020XXKI1
i try every guid and tutorial to unlock and root, not work anyone !
FAILED (remote: Erase Fail) and many error like this Erase Fail or write failed
memory is readonly ? or phone was crashed ?
any solutions ????
tanx
i see same error in nexusshacks.com ics root guid :'(
please helpppppp ....
anybody any idea .......
Have you encrypted your phone?
Sent from my Nexus S using XDA
maybe your sdcard / internel memory is faulty?
jorim.tielemans said:
Have you encrypted your phone?
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
no i dont ! how can check it ?
mtothearkus said:
maybe your sdcard / internel memory is faulty?
Click to expand...
Click to collapse
some time when ics boot up and i can use usb storage mount i can work with memory and its ok.
but how can check internal ? its maybe readonly !
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
ninfragile14 said:
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
Click to expand...
Click to collapse
i found very good solution : recycle bin
but i see on it : don't recycle
-> ye shoare ghadimi hast ke mige samsung faghat lcd ! (khak too saret samsung)
i have same problem and i cant work with my mobile
ninfragile14 said:
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
Click to expand...
Click to collapse
i have same problem and i cant work with my mobile
I Have Same Problem how can i fix it?
ali.md said:
i have a big problem
i buy a stock phone (I9020T)
but i cant unlock the phone with any method and cant root or flash and ...
phone random correctly boot and random (90%) hang on google logo
i cant do anything with phone when randomly boot on ! (many error)
i even cant erase and restore factory device (failed) in recovery mode (after press all keys i see standard menu)
i must 10 - 20 time pull battery and power again to ics boot up
but every thing back to a point (last user setting and photo-gallery and ...)
and dont save anything in next boot !!!
how can check internal memory for any damage ?
i thing have exact problem http://forum.xda-developers.com/showthread.php?t=993403
but phone is LOCKED and cant test that methods and cant return to samsung :'(
please helpppppppp me
Carrier TMB
LOCKED
Rom: ICS (no root, no mod, no customize)
bootloader ver: I9020XXKL1
Baseband ver: I9020XXKI1
i try every guid and tutorial to unlock and root, not work anyone !
FAILED (remote: Erase Fail) and many error like this Erase Fail or write failed
memory is readonly ? or phone was crashed ?
any solutions ????
tanx
Click to expand...
Click to collapse
can u help me ? my mobile stop with google logo
i try to unlock with fastboot oem unlock but it doesnt work
i get feil ...
Help me please if u get the solution
[email protected] please send to me email if u get the answer thank you
zaherrrr said:
can u help me ? my mobile stop with google logo
i try to unlock with fastboot oem unlock but it doesnt work
i get feil ...
Help me please if u get the solution
[email protected] please send to me email if u get the answer thank you
Click to expand...
Click to collapse
I have same problem too,Any way to fix this ?
Paper Weight
My nexus s has the fail problem too and so does my daughters,nothing will fix this problem but a new motherboard.Its a result of a hardware failure.I have tried even reseating the chips.My fix was searching the net for people selling their phone due to broken screen.I found one so far for 50 bucks and bought it.Fixed my daughters with easy by changing the board.I have spent hours upon hours reading articles on this problem.The best article i read addressing the problem was the placement of chips too close to the edge of a circuit board.After looking at the placement of the memory chip in my nexus s,I fully understand why it fails.Just by upgrading your phone and causing the phone to over heat a bit could warp the BGA seating of a chip resulting in a paper weight so to speak.This is only my response to how i feel on this subject.The end result for those with no warranty.Search the resell sites for a phone with broken screen and fix.
any solution yet ?
i look at my phone every day on my desk and ... :crying:
my phone turn back on after full wipe but storage freezed
for example wen i copy file/ delete/ format / ... and turn usb storage off and on again (without restart) everything backed !!!!
storage locked and freezed or corrupted !
help us someone please
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
hi - i have in my nexus 5 only the google logo and the unlocked key is on the screen;
when i get to fast boot it does see the device.
when ienter " fastboot oem device-info
igot device tampered true
device unlock true
off mode charge - true
when i try to write twrp recovery it says sending recovery okay and writing recovery okay.
but ucant enter to the recovery of twrp.
when i try to flash an image it says:
writing bootloader
failed (remoteflash write failure)
rebooting into bootloader okay
writing radio - failed remoteflash write failure
target reported max size of 1073741824bytes
is there any way to save my phone?
i can enter adb its says on the phone "now send the package you want to apply to the device with "adb sideload filename"..
how do i can send an image?
thank u
re
i try to flash with the lg flash rool - i did everything ok and it stuck in 6% and says"user data erase fail" what can i do?
You're using the batch commands included with the stock ROM to re-flash?
Hi my Nexus 5 also suddenly die too. And I have the same exact problem that you have when trying to flash it. I looked for hours on the internet tried formatting, erasing and many other alternatives and nothing. There are some people experiencing this same problem like us. For no reason the memory is getting corrupt or died. I get mant errors on the cache when I boot to regular recovery. The only recovery that I have manage to boot to (except for the original one) is Clockworkmod using fastboot boot "therecoveryname.img". With clockworkmod I have adb working but still can get the phone to boot or accept factory images. I can't lock the bootloader either.
I think this error was cause by the software. There was a very similar problem that never got fixed for the nexus 7 when lollipop came out.
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
No I don't need to. I tried just to see if the phone will relock itself. I read somewhere in the internet that if you can't relock/unlock the device the nand if fried.
If you look for these errors there are people with LG G2 and LG G3 that are having something similar happen. I think LG hardware is partly behind the problem. I call Google and told them about it and the put me through LG which want me to send the phone for repairs but not free. My guess is that it will be way to expensive to repair and that is not worthy.
Hopefully someone with real repair skill can give us light if this is something fixable by software.
audit13 said:
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
Click to expand...
Click to collapse
I had two different Nexus 5 phones that were stuck in a bootloop with the spinning coloured KK animation.
Every time I unlocked the bootloader, the bootloader would always re-lock itself when rebooting. Even when I managed to unlock the bootloader, I could not re-flash a stock ROM because the bootloader kept relocking itself.
Whenever I unlocked the bootloader, the phone would only take 2 ot 3 seconds to wipe the phone which is too fast.
In the end, I purchased a nexus 5 with a smashed screen to use its motherboard in my defective N5.
I have never come across a post where someone was able to solve the problem unless they had LG replace the motherboard with a new imei.
Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.
Cactus1ne said:
Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.
Click to expand...
Click to collapse
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.
@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571
V0latyle said:
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.
Click to expand...
Click to collapse
Thanks for the quick reply, much appreciated.
I have already tried complete data wipe using Odin; didn't work. But I had totally forgotten about the bootloader screen (rookie mistake). I'll definitely do that after trying what @Jerffelly suggested.
Jerffelly said:
@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571
Click to expand...
Click to collapse
Worked like a charm. Much love to you and @dronkit for the detailed and easy-to-follow guide. I struggled a bit with the stuck on file analysis from Odin and device unauthorized from adb; nothing an xda forum search won't fix though.