Related
So, There's always paranoia about Flashing. No surprise there.
Here I will list the major worries and hopefully some aces will give opinions on all.
1) Network Locked Phones? - Does it REALLY matter if your phone is network locked before flashing a new Firmware? (i.e. CSC/PHONE&MODEM)? [If so, what firmware are/were you on?]
2) IMEI numbers - There have been various reports of IMEI numbers going down the drain on certain flashes.
EFS folders CAN be backed up but is it only ADB that can sucessfully back this folder up without restoration problems? And more questions...
3) Bricking - Seems like it's hard to brick any SGS entirely, but, whats the realistic percentage? 5%, 10% or up to 50%?
4) Warranty problems. Flashing does not necessarily void your warranty. ROOTING DOES, correct?
4a) OMG MY PHONE IS BRICKED! HOLY CAPERS BATMAN EVERYTHING IS RUINED!
Whilst unfortunate, seems like if a phone in this state is sent to samsung/ a repair centre they will have no idea what's gone on and replace it anyway, even if there was root. Discuss......
Flake x
aahhh come one guys, after 150+ views, someone MUST have something to say about this...
It's never safe 100% to do any flashing, but maybe a weigh up of the problems might be useful to first timers... pleeaase
F x
n99flake said:
So, There's always paranoia about Flashing. No surprise there.
Here I will list the major worries and hopefully some aces will give opinions on all.
1) Network Locked Phones? - Does it REALLY matter if your phone is network locked before flashing a new Firmware? (i.e. CSC/PHONE&MODEM)? [If so, what firmware are/were you on?]
2) IMEI numbers - There have been various reports of IMEI numbers going down the drain on certain flashes.
EFS folders CAN be backed up but is it only ADB that can sucessfully back this folder up without restoration problems? And more questions...
3) Bricking - Seems like it's hard to brick any SGS entirely, but, whats the realistic percentage? 5%, 10% or up to 50%?
4) Warranty problems. Flashing does not necessarily void your warranty. ROOTING DOES, correct?
4a) OMG MY PHONE IS BRICKED! HOLY CAPERS BATMAN EVERYTHING IS RUINED!
Whilst unfortunate, seems like if a phone in this state is sent to samsung/ a repair centre they will have no idea what's gone on and replace it anyway, even if there was root. Discuss......
Flake x
Click to expand...
Click to collapse
-i have a network locked phone, no problems at all.
-imei, just root your phone and backup the /EFS folder, although if you dont check EFS remove or wipe in odin, anything should happen.
-bricking is hard... almost allways you can run into download mode (and if usb isnt hw damaged will repair your phone)
-flashing and rooting both void your warranty, if you have a hw issue and want to send it, just take sure to flash a stock rom.
-if aint booting, and anything can be done by you, just cross your fingers send it, and never say what you did.
(all those questions are answered tons of times, thats why pple dont answer)
Nice one, cheers!
Don't suppose you know the best way to backup EFS?
n99flake said:
Nice one, cheers!
Don't suppose you know the best way to backup EFS?
Click to expand...
Click to collapse
I used Nitrality (from market) to backup my efs. Open it, click tools, then click backup efs. ***Note: your phone must be rooted and have superuser for Nitrality to be able to perform this backup***
That is one nice app.
Thanks again!
imo, just copy&paste /EFS folder is safe enough, to repair imei just copy back...
apps might make images or dunno...
cheers^^
-I backed up my efs folder with root-explorer. Just zip it with root-expl and send it to yourself via mail.
-My phone is network locked, i flashed a couple of fws and not any problem so far.
-For flashing only use trusted fws, like Ramad's, and don't tuch the phone during you flash the phone (because the contact of the USB port). So it should be all right!
Regards
Okay everybody,
I decided to write a new thread for my problem because I think my prob is a very special thing.
I'm from germany, so please don't wonder about my english. I think it is a understandable.
The story begins with a software update for my GT-I9305. After the update, the IMEI was just "null", after some work with google I found out that the efs partition was broken. With my bad knowledge for this case, I destroyed the whole EFS folder. I installed perseus kernel. And, there it was! The whole and correct IMEI. The solution was the perseus kernel (stock doesn't work, neither reflash). But then, after a while the phone doesn't boot anymore. I flashed Android 4.4.4 and my phone was revived but the IMEI was again "null". I have no backup or anything else!
So I spent approximately 20 hours or more to understand the efs thing. I found much solutions but nothing worked for me. So, here I am.
What I've tried before
-reflash KitKat
-reflash Perseus (not compatible anymore)
-formatting efs partition for a blank and new EFS for editing
-tried to edit nv_data.bin with HEX
-tried to backup efs with a 3rd party app and edit this with hex (the app doesn't support my GT-I9305)
and then, there it was:
-tried to use a working EFS partition from another GT-I9305
-editing with Qualcomm NV Tools! (I think THIS is the solution!)
I tried NV-items_reader_writer (1.0) and EFS Professional (2.1.73), but in both can't find my phone:
What I've done in NV-items_reader_writer
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened NV-items_reader_writer
-checked the both boxes near the SPC box
-selected the right port (last: COM4)
-clicked on "connect"
-clicked on "read"
-> here it search the phone, but it can't find it and says "Failed.. Phone does not answer"
What I've done in EFS Professional
-dialed *#7284#
-at "Qualcomm USB Settings": "RNDIS + DM + MODEM"
-enabled USB Debugging in phone
-connected the phone
-opened EFS Pro
-clicked on "Qualcomm NV Tools"
-refreshed the Available COM Ports
-selected "SAMSUNG Mobile USB Serial Port" (last COM4)
-clicked on "Connect"
-> Here it takes few seconds and he stops and says: "Phone connection has been lost!" and "Unable to send SPC to the Phone!"
What I've tried to solve this problem
-tried QUALCOMM USB Settings: "DM + MODEM + ADB"
-reinstall all Samsung drivers
-tried to install Samsung Modem with Qualcomm drivers (failed due to wrong platform; I've Win7 X64)
-reinstall Samsung Kies (for actual drivers)
-tried to dial *#9090# (in my case, this menu is totaly blank)
-tried in factory mode
It could be that I forgot some....
Now, my question to you all is, do you know what I've done wrong? I mean, this is working for the most users, but why not for me? What do you think? Did you think I really forgot something?
Some informations:
Phone: GT-I9305
Android: 4.4.4 KitKat
Kernel: Stock (3.0.31-2760029 ; [email protected] #1 ; Fri Sep 12 13:08:24 KST 2014)
Buildnumber: KTU84P.I9305XXUFNI3
Windows: Windows 7 X64
Do you need more informations? Post it!
Please help me, I want to bring this phone back to life!
And yes I know, to change the IMEI to a number which is not your own is ILLEGAL and to prevent this, it is not well seen to talk about, but this is MY PHONE and I want to change the "null" IMEI and IMSI to MY ORIGINAL IMEI. If this is a problem, I can send a PM to an mod with my phone (where you can see the IMEI), my username on a sheet of paper and the original box with the IMEI printed on. All on one picture!
Simply... I need a hero! Be MY HERO!
im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.
take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.
vnholden said:
im in the exact same problem as you. the reason nv tools and efs reader is not seeing your phone is because you have NULL well usb wont work. so try installing the original 4.1.1 firmware, then install perseus, then nv tools and efs software will see your phone. if you end up fixing it please help me out. upgrading to a later firmware is where I get stuck. just stays on the boot logo. and like you said perseus isn't compatible. you seem to know how to use nv tools so hopefully you can get somewhere. as I don't no how to use it. GOOD LUCK.
Click to expand...
Click to collapse
Thank you for your reply!
I tried this, already. But I can't downgrade from 4.4.4. I don't read very much about this. I just know that this is a new security option from samsung (or Android)... I will tell you when I know more
qasim799 said:
take your phone to the samsung if you have warranty.otherwise give to a phone repair shop for repair because your problem can only be solved with special boxes and equipments etc, and they have it. it will not cost too much.
Click to expand...
Click to collapse
Thank you for your reply!
The warranty is already expired...
This will be the last step I will do. Before this, I will try my very best to do this at home... But thank you for this tip
Edit:
What do you all think about this idea:
-I try to find somebody with a working EFS on GT-I9305 Android 4.4.4
-I get a backup from him
-I restore this backup to my phone
-I edit the duplicated IMEI with NV Tool to my IMEI
This requires that the NV Tool will with work with an existing IMEI and the the phone will be THE WHOLE TIME IN PLANE MODE to prevent IMEI ban...
What do you think? Will this work? Do I need somebody from germany (DBT) or is this not needed?
Take it to a phone repair shop they might have a way to fix it. And if they don't they might know someone who can and it would likely be cheaper than Samsung service center
Sent from my GT-I9305 using XDA Free mobile app
Identical case (Solved)
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!
When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
WesleyPs said:
Hello partner!
I had the same problem with imei after years of using various roons.
In my case I had a rom lollipop, between a night and other My IMEI is gone. Follow almost the same steps you. After a long time searching the internet was found a case was solved by installing an original rom Samsung via Odin.
Just wiped everything on the recovery and follow this tutorial and today I am with my IMEI back, and well relieved.
I hope it helps you too.
droidviews.com/install-official-android-4-4-4-kitkat-firmware-samsung-galaxy-s3-gt-i9305
Obs. I used all the programs and drivers available in the tutorial. and installed only the samsung drivers. I did not need the KIES
Good luck!!!
Click to expand...
Click to collapse
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
viktorak said:
When nothing is helping try to restore your Efs partition.:http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...
Hello,
someone could give me an EFS file because I deleted mine but my camera would not boot and remains on bootloop
thank you in advance
SurrendeR1993 said:
Hey,
Thank you for your reply.
I reinstalled my windows yesterday. So I can try it with a whole clean OS.
I will response after testing. But actual I'm very busy. I will reply as soon as possible.
Thank you, I will try this, too. But this is more if your efs isn't mounted. My partition is there but just clear.
I will tell my experience after testing.
€dit
Now I tried my idea with the EFS partition from somebody with a working GT-I9305. In my case, this isn't working... I think I must try the next step and try to repair it from a shop or so...
Click to expand...
Click to collapse
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
---------- Post added at 05:00 AM ---------- Previous post was at 04:46 AM ----------
banjomike said:
Repair shops aren't as expensive as you think to get my camera replaced all up cost 50$ au dollars and when I first got into Android I trashed heaps of phone's (low end thankfully) before I knew what the hell I was doing and never cost me more than 80$
Click to expand...
Click to collapse
Sorry dude just found out only samsung can restore Imei give phone shop a try but I don't think they could sorry
I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app
SurrendeR1993 said:
I want to update all you guys.
I flashed the old bootloader so I was able to downgrade to Jelly Bean. There I installed perseus and now I could connect to the Network, but I don't want. IMEI ist still 0.
But now I can enter *#9090# menu. But I can still not connect the phone with any DM Prog
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.
viktorak said:
If you were to 4.4.4 Official Stock rom can`t do downgrade the bootloader.What you have done is downgrade to Firmware with extracted knox bootloader.But you still with EFS corrupt partition.
Click to expand...
Click to collapse
Hm okay. I applied a "old bootloader" before here from xda. I don't know what it was exactly. There was a boot.so or so in it.
I will try my best. I mean, if I can beat this, this is a really great success for me. My next step is to restore a full NAND backup from a friends of mine (from a GT-I9305).
I wondered about that, after I restored a working EFS, there were no NV data.
My journey to restore a corrupted GT-I9305 without pay some money
Sent from my GT-I9300 using XDA Free mobile app
how did you success ?
how did you success ?
Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed
hope this helkps anyone, took me some 20 hours of tinkering
Oakhand said:
Hi guys, i had the same issue: after a botched restore of nandroid backup (something to do with it being over 2GB, different story though), I lost IMEI (null/null) and no baseband.
I was running CM so I tried to flash the original Samsung ROM, to no avail. Then a whole bunch of other stuff that didn't work, until:
- I flashed kitkat (which failed due to some error in the install script, dunno why)
- then flashed my last nandroid, which I had already flashed with no restoration of phone functionality, HOWEVER,
- I then flashed over that nandroid the modem files (see here: dropbox.com/sh/d2ljv1ylvr9nvib/M7UzMgux4f) , mine was Modem-I9305-XXUENE2.zip for i9305 LTE Intl.
- tadaa! fixed(
Click to expand...
Click to collapse
Can you post the links you used?
EwOkie said:
Can you post the links you used?
Click to expand...
Click to collapse
aside from the dropbox link in my post above I did not use much else. I downloaded a stock kitkat rom, but don't know from where.
Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.
bravept said:
Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.
Click to expand...
Click to collapse
first of all (search for doing this !! )
take a TA partition backup and then unlock your bootloader .....then install the recoveries on the stock ROM>>then replay to me after that
Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....
bravept said:
Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....
Click to expand...
Click to collapse
I think unlocking your bootloader resets everything so backup your apps for re installation once your are done.
I unlocked my bootloader the good old fashioned way via fastboot :
1 - Check if unlocking possible by typing *#*#7378423#*#* in the dialer and going into Service info > Configuration.
2 - If it says something like Bootloader unlock allowed - Yes then its unlockable. If its already unlocked, it will say something along those line as well.
If neither option appears then it isn't unlockable.
3 - Get the unlock code from Sony after filling the necessary details along with the IMEI no. of the phone.
3 - Open command prompt in the adb & flashboot folder by holding Shift + right click and selecting the "open command window here" option.
4 - Type fastboot.exe -i 0x0fce getvar version to check if device is connected properly.
5 - Type fastboot.exe -i 0x0fce oem unlock 0xKEY. Repalce KEY with the code that was received from Sony and hit Enter.
Alternatively the BLU option in FlashTool can be used to simplify things as it automates most of the above procedure. It can also be used to relock your bootloader.
There's also a new app called Kingo SONY Bootloader Unlock that apparently unlocks your bootloader with one click. Check it out.
I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...
bravept said:
I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...
Click to expand...
Click to collapse
If it says no then dunno what the chances of success are.
Came across this Youtube tutorial : https://www.youtube.com/watch?v=Li8Eim6gugw
Don't know how legit it is since its been posted a few months back and there are no comments at all so please proceed with caution and of course don't blame me if you brick your device
Also did you try the Kingo unlock app I mentioned?
Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...
Just install some 4.4.4 lbl build, for example cm11 by mateo337 is really good and even up-to-date.
You will not be able to unlock the boot loader i had XSP that said no and i was not able to do anything about it.
Dont use 5.x.x builds, they are really outdated and have a lot of bugs.
So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?
bravept said:
Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...
Click to expand...
Click to collapse
No you should still be able to enter fastboot mode. Are you using the latest version of FlashTool and have you installed all 3 required drivers? Does your phone show up in device manager when you connect it in fast boot mode?
I am not sure abt the last 2 procedures I posted but the first 2 require your phone to boot into fastboot and stay there till the job's done.
bravept said:
So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?
Click to expand...
Click to collapse
Yeah. Since your phone's rooted now, you can follow a LBL procedure for flashing a custom recovery to allow you to install custom ROMs.
Sent from my Xperia SP using XDA Free mobile app
I wrote a brief thread regarding my phone before...
I'll just give the details:
I'm the second owner, phone died while updating.
Phone was bootloader unlocked, and with TWRP recovery.
As such, baseband and IMEI info are missing, I have the original IMEI but, no efs backup or anything.
Any ideas? I've tried to re-install factory stock via both Skipsoft Toolkit and another Toolkit [Yes, I realize this is no help, now]
I've heard restoring another EFS from another phone may work...? I don't know though, I have two Nexus 5's and I can pull an EFS just to try to get back my original IMEI or I've read EFS Pro could help but, again I'm quite lost and just need a hand here.
Thanks.
Ive been an active user on this forum and the rules is that you cant discuss changing the imei here, because its illegal in many countries
Skickat från min Nexus 6 via Tapatalk
No changing!
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
RedHazy said:
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
Click to expand...
Click to collapse
here's a silly question.. how did you lose your imei? its not an issue on the n6 like earlier nexus phones, people just dont accidentally lose their imei, or their efs., unless they are restoring a nandroid from another phone, that has their efs backed up also..
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Sidenote: I did mess around with Titanium Backup but, I don't see that erasing my IMEI.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
If know the IEMI for your device there are threads on XDA that may restore it. If don't know the original IEMI you are dead in the water from the get go.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
i dont think that you are a criminal, seriously. i was just curious, as on the n5 and n4 that happens often. it really does happen very rarely on a n6. i think the phone dying while updating might of done it. if your bootloader is still unlocked, flashing the factory image might help you. but you will have to do it right, via fastboot while youre in the bootloader. dont use any toolkits, seriously!
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
RedHazy said:
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
Click to expand...
Click to collapse
heres some instructions, dont lock tbe bootloader after, just follow the flashing the factory image instruction. and if tou run into trouble, let us know, so we can help you http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
RedHazy said:
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
Click to expand...
Click to collapse
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Fingers crossed!
simms22 said:
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Click to expand...
Click to collapse
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
RedHazy said:
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
Click to expand...
Click to collapse
wipe the phone, factory reset i mean
(sorry for getting back so late)
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
droid4lif3 said:
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
Click to expand...
Click to collapse
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
graydiggy said:
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
Click to expand...
Click to collapse
The IMEI is stored in the CID partition. The CID is a small datablock containing the processor UID, Channel ID (different CID), a bootloader unlock flag, and IMEI. The CID is unique to each device, and controls several aspects of the device. This datablock has a signature on it so that your device information cannot be modified. Should you corrupt this partition, you will lose your IMEI, and the ability to unlock your bootloader. This is the only likely scenario in which you lost your IMEI. If you boot into your bootloader, you may see an error similar to
Code:
CID Datablock Error! 0xDEAD
otherwise I'm going to assume that is still intact. The IMEI has not been stored in the EFS for many years now. Check your CID on the device and make sure it's not 0xDEAD.
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
Click to expand...
Click to collapse
Did you seriously just ask an iPhone question? ???
Seriously though, bring it back to T-Mobile.
Lol, no, I knew I shouldn't of put that she had a iPhone 6S, now I will never be helped. I am just saying that I used a different sim card to make sure that it wasn't the sim card that was messed up.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
Click to expand...
Click to collapse
You can check by running the command
Code:
fastboot getvar all
in fastboot/bootloader mode.
You should see something like this:
Code:
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
The CID should be 0x00DE if it is not corrupt.
i went to unlock my bootloader this morning but when i tried i got a "command not allowed" message from fastboot, i checked and for some reason its bootloader unlock status says a big fat "NO" (not sure why as the phone came direct from sony)
anyway ive managed to get temp root via the method in the huge thread here (well i got it once so far) but i cant seem to find much info aside from backup of DRM keys, there may well be info in teh main thread but its some 1000+ posts long and a lot to slog through in the hope of finding a sliver of info so i figured id ask what there is i can do at this point?
all i really want is to be able to install viper audio, i dont really care what rom its running, i was planning on l16 but im happy with anything that works, any help would be appreciated