Database Info

IMEI Messed up, help please!

I was told to post here so:
Hi,
Yesterday I flashed a custom ROM , the rom somehow messed up my IMEI number.
Then i went back to the forum and found out that everyone who flashed the rom got his IMEI messed up and we all got the same IMEI now, i still have calls working but im afraid they will stop working soon, i know what was my original IMEI, can anyone help us please. (Heres the rom i flashed: http://forum.xda-developers.com/showthread.php?t=1034130)
I saw that the devs on samsung captivate managed to restore their imeis, there should be a way to do that to the nexus s.

Same Problem with my phone...

same here
I'm restore my backup .. and nothing change
and imei still changed :S

Same here, i think the phone is as good as network dead.

Hi all, I also was unfortunate to flash this rom resulting in the changed imei issue. My Phone was displaying emergency calls only and i was unable to connect to data services. I used Odin to flash back to stock GRH 78 ticking the phone efs clear box . After rebooting i checked my imei number but it still displays the wrong number. However my phone now connects to the network and i can make and recieve calls and data is enabled. Not a full fix and i am not sure for how long it will work but definately an improvement on the very expensive paperweight i had. Hopefully a full fix will come soon.

Trying that~!
UPDATE :
Nope Odin again didn't help.

Isn't it kinda stupid to discuss this in not only one or two but four threads? I get it, you guys want a fix and I feel with you, but having four threads will only cause confusion.
How about you all agree on one and work together to fix it instead of dividing your efforts?
Sent from my Nexus S using Tapatalk

bloodhawk said:
Trying that~!
UPDATE :
Nope Odin again didn't help.
Click to expand...
Click to collapse
Sorry to hear that worked for me. I'm in UK on vodafone network. Lets hope a solution is found real soon.

james7dean said:
Sorry to hear that worked for me. I'm in UK on vodafone network. Lets hope a solution is found real soon.
Click to expand...
Click to collapse
Can you explain what version of Odin you used - Odin3 v1.8 ??
What rom did you flash stock GRH78 ??
Did you use a .pit file and if yes which one ??
What boxes were ticked and de-ticked in Odin ??
Cheers mate

Hi,
I used odin 3v1.8 and the stock GRH 78 rom. I opened odin and loaded the
bootloader, Pda and scs files and ticked the phone efs clear box ,this was the only box i manually ticked all other boxes were left in their default state. i did not have a pit. file. Previous to using odin I had just unlocked my bootloader as it was locked. Odin won't work with bootloader locked all atempts to access download mode were met with a unlock bootloader screen.
After flashing I checked my emei no. but was disappointed to find no change. I then checked for system updates and clicked on the update which started to download. It then suddenly dawned on me that i had not linked my phone to my router and that data was enabled. I cancelled the Gingerbread update and went into notifications and saw my network instead of the previous Emergency Calls Only. A quick phone call verified that my phone was now connecting to the network. I then connected to wifi and installed the update.
I am still stuck with the wrong emei but can now connect to the network and
have restored my favourite rom from a nandroid. The only issue i now have is the
wrong emei but for now my phone functions perfectly

RisinT96 said:
Yesterday I flashed a custom ROM , the rom somehow messed up my IMEI number.
Click to expand...
Click to collapse
Probably something messed with your /efs partition.
james7dean said:
I used odin 3v1.8 and the stock GRH 78 rom. I opened odin and loaded the bootloader, Pda and scs files and ticked the phone efs clear box ...
Click to expand...
Click to collapse
Why did you have to do that? I don't assume you have a backup of /efs, do you?
james7dean said:
The only issue i now have is the wrong emei but for now my phone functions perfectly
Click to expand...
Click to collapse
I wonder how long it'll work ...
Y'all could try to look in the forums of the various Samsung Galaxy S variants, AFAIK there are ways to restore your IMEI on this kind of Samsung phone, maybe they apply to the Nexus S as well.

IMEI=0 - how to enter working IMEI?

Hi everyone & thanks for reading this!
I bought 2 new, unused Nexus 5 as presents for my sisters for Christmas (not via playstore, but via a reseller. Still: new, sealed, unused.)
I unlocked, installed a custom recovery, rooted both devices without problems, then set up one in a smartphone-newbie-friendly way, which took quite some time. Then, to save me some time, I fear I made quite a big mistake: I made a nandroid-backup of the newly-setup device and restored/installed it on the second nexus (so I wouldn't have to change all the settings again, install apps, etc).
Unfortunately, this seems to have erased the IMEI on the second device (it shows as IMEI=0), so I can't connect to any cell service. Some googling leads me to believe that this might be due to a corrupt/missing EFS-folder, which, second mistake, I did NOT make a backup of beforehand. I know, it's my own fault - my thinking was: why backup, there's nothing backupworthy on the device *yet*.
FML. :crying:
I am not sure if the phone is still in warranty (and even if it was - I guess I voided that by unlocking/rooting?!). I want to re-iterate that I own both devices LEGALLY, I have the bill, I have the original sticker with the original IMEI - I just need a way to re-enter it. Any dialer-code for that? Any modify-able EFS-backups? Any other way?
Thanks in advance!
PS: tried so far & found useless: other simcard (not working) & simcard in other phone (working), so it's a device-issue; factory-reset;

Try fastboot flashing the cache.img from the factory image.

jd1639 said:
Try fastboot flashing the cache.img from the factory image.
Click to expand...
Click to collapse
thanks for the super-quick reply jd1639!
to make sure I understand you correctly:
I can use the factory image from
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
(nexus 5, android 4.4.2), extract the cache.img from there & flash that via fastboot? (or would it have to be a factory image of this very device - which I do not have, unfortunately)
and, just for my understanding: how does that restore the imei? I mean, the factory image itself (or it's cache) can't really contain MY imei. does this just delete the invalid imei & force the phone to get it's original imei from some other, not yet overwritten source? e.g. hardware?

Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk

Thank you for clarifying, rootSU - that gives me hope.
I will try tomorrow & hopefully report success

Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).

RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...

RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato

charesa39 said:
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
Click to expand...
Click to collapse
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).

CellPhish said:
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
Click to expand...
Click to collapse
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!

RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
If all fails you can try to contact LG service and tell them your situation. Though its not good to lie, just tell them you got the IMEI=0 problem, they'll say its a hardware problem and will replace the motherboard(if your device is on warranty)
Sent from a potato

You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.

rootSU said:
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The IMEI is stored in the EFS partition, not the cache partition.
RogerG said:
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
Click to expand...
Click to collapse
Sounds like you turned the phone into a $400 paperweight. TWRP backs up and restores the EFS partition by default, and each device has a unique EFS partition, which contains the IMEI among other things. I don't know of a way of manually restoring the EFS data. This is unfortunately a $400 lesson for people who tinker without first doing their homework.

Hey guy. Let's not be so judgemental. There's always a risk of the imei being corrupted when you flash a ROM. As a matter of fact just before I even unlocked my nexus the imei got corrupted and I had to factory flash my phone to save it. Its scary but op, if you manage to get your phone working again make a backup and store it on your PC and or email yourself the backup.

BirchBarlow said:
The IMEI is stored in the EFS partition, not the cache partition.
Click to expand...
Click to collapse
Ha ha thanks! Can't believe you think I don't know that :/
Actually the "EFS partition" is 2 partitions..
/dev/block/platform/msm_sdcc.1/by-name/modemst1
And...
/dev/block/platform/msm_sdcc.1/by-name/modemst2
That doesn't change the fact that reflashing the cache.img is a known fix for missing IMEI. Corrupt cache can make the imei appear as 0 even when the EFS imei is in tact so reflashing the cache.img can resolve this.
Unfortunately though, I didn't read the OP fully. I just elaborated on an earlier response for the OP
jd1639 said:
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
Click to expand...
Click to collapse
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk

rootSU said:
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes but all talks about how to change it in any way are not allowed here. Legally the only people that are allowed to do so is the OEM. You can look at international news reports of cellular dealers that are doing so are being closed down and arrested.
That is why it is well know to back up the efs before you do anything.
Bat cave One

My newly bought Nexus 5 shows IMEI 0 also
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
i just update my newly bought nexus 5 from initial 4.4.2 to 4.4.4 which is appear at update section but then my IMEI appear =0 .. dont understand what to do..
if your problem solved, pls tell me the detail procedure to recover my IMEI no.

RogerG, did you ever get this working? I'm on 6.0 and having the same problem, flashing cache.img also does nothing.
Thanks.

[Q] Stuck in Fight Mode. No IMEI. Not Able to Detect Sim Card. Baseband Unknown :(

Can Anyone Helped me? My Samsung Galaxy SL GT i9003 stuck in a flight mode. NO IMEI. Not able to access SIM Card. and also Baseband Number is Unknown. I dont know what to do. i already did HARD Reset.

stainedmortixia said:
Can Anyone Helped me? My Samsung Galaxy SL GT i9003 stuck in a flight mode. NO IMEI. Not able to access SIM Card. and also Baseband Number is Unknown. I dont know what to do. i already did HARD Reset.
Click to expand...
Click to collapse
There are issues like with samsung galaxy series. but, i was unable to do anything with this., so, i replaced my motherboard through samsung service center.

stainedmortixia said:
Can Anyone Helped me? My Samsung Galaxy SL GT i9003 stuck in a flight mode. NO IMEI. Not able to access SIM Card. and also Baseband Number is Unknown. I dont know what to do. i already did HARD Reset.
Click to expand...
Click to collapse
If you can enter in Download Mode you can try Full KPE including latona.pit (repartition) ,and then any other Full 2.3 Firmware ,i use DDLF2 . Maybe it solves the problem .

Got the same issue . Anyone have a sure solution ?
Edit: On a friend's galaxy SL

Same thing here.
Lost my imei after flashing Nameless Rom.
Got it back with DDLF2 ROM.
But a couple days ago my phone stopped acessing the network completely.
I have a backup of my efs and no matter what I do it won't restore the imei.
Read and done every single tutorial.
I'm out of ideas to fix this.
I think my portable device era as reached an end. And will definitelly change to windows products as Android is a piece of ****.
Sent from my GT-I9003 using XDA Free mobile app

rgxHost said:
Same thing here.
Lost my imei after flashing Nameless Rom.
Got it back with DDLF2 ROM.
But a couple days ago my phone stopped acessing the network completely.
I have a backup of my efs and no matter what I do it won't restore the imei.
Read and done every single tutorial.
I'm out of ideas to fix this.
I think my portable device era as reached an end. And will definitelly change to windows products as Android is a piece of ****.
Sent from my GT-I9003 using XDA Free mobile app
Click to expand...
Click to collapse
Android is good, what is a sh*t nowadays is galaxy sl. Go buy a newer device and enjoy android without lack of ram and good hardware.
Enviado desde mi A0001 mediante Tapatalk

Yeah.. I thought about it. But this Galaxy SL is a versy special version given by my girlfriend [untill her iphone dies completely]...
So... Im a little bit screwed...
Although i do believe my case must be due to efs version. As far as i know Nameless Rom uses EFS v2.
Im guessing my *.tar.gz file was backed up from that rom.
Still i have tried to restore without success.
My backup seems to be ok..
By the way is there a way to convert my tar.gz file to an iso? (so i could try a couple of methods)
Sent from my GT-I9003 using XDA Free mobile app

Goto dial pad and key in
*#*#197328640#*#*
Service Mode menu will be displayed.
Tap on [6] COMMON
Now select [6] NV REBUILD
May work for you.
Good LUCK!

Greetings. Thanks for the tip but... I get a black Service Mode. No content.
Any idea why?
Alternative Code:
*#*#7284#*#*
Also in some previous ROM i had some content with this code.
Not sure if it is the same.. But it asks for a password when selecting the "nv backup option".
Inserted one password that was referenced in the Forum; but password is wrong.
Sent from my GT-I9003 using XDA Free mobile app

I'm on nameless and baseband is ddle1. What about you!
Password! No, it is not askin for it. Is it asking for an unlock key!!
Sent from my GT-I9003 using XDA Free mobile app

stainedmortixia said:
Can Anyone Helped me? My Samsung Galaxy SL GT i9003 stuck in a flight mode. NO IMEI. Not able to access SIM Card. and also Baseband Number is Unknown. I dont know what to do. i already did HARD Reset.
Click to expand...
Click to collapse
Hello,
I am in the same situation. I tried to flash several "modem" with Odin, but baseband is always unknown.
Do you know how to solve the "baseband unknown" problem?
Thanks in advance.

Im also using Nameless Rom. But... Depending on the ROM i either i get a black screen, a message saying i dont have sim card or a message saying i dont have service mode installed. So it seems i dont have a solution to fix my device.
Sent from my GT-I9003 using XDA Free mobile app

I hope I will be the one who will save you
Did somebody tried to flash a efs file. If not try. I was having the same problem in the past.
To flash the efs for I9003 you have to follow some steps
Get phone to the Download mode (Vol Down+Home+Power bundle)
Open Odin
Connect phone to pc with USB cable
Put efs.tar to PDA row
Click flash
Enjoy
*You have to install Samsung USB drivers to use ODIN flash tool
*File attached to this post
*Be carefull, I'm not responsable for using wrong the flash tool
* Hit THANKS Button if I helped you
Cheers, :highfive:

CSI.ISC said:
Did somebody tried to flash a efs file. If not try. I was having the same problem in the past.
To flash the efs for I9003 you have to follow some steps
Get phone to the Download mode (Vol Down+Home+Power bundle)
Open Odin
Connect phone to pc with USB cable
Put efs.tar to PDA row
Click flash
Enjoy
*You have to install Samsung USB drivers to use ODIN flash tool
*File attached to this post
*Be carefull, I'm not responsable for using wrong the flash tool
* Hit THANKS Button if I helped you
Cheers, :highfive:
Click to expand...
Click to collapse
Yeah...no doubt... A Savior.
Thanks a ton.

still on flight mode - IMEI still missing, not able to detect sim card
sam_777 said:
Yeah...no doubt... A Savior.
Thanks a ton.
Click to expand...
Click to collapse
CSI.ISC said:
Did somebody tried to flash a efs file. If not try. I was having the same problem in the past.
To flash the efs for I9003 you have to follow some steps
Get phone to the Download mode (Vol Down+Home+Power bundle)
Open Odin
Connect phone to pc with USB cable
Put efs.tar to PDA row
Click flash
Enjoy
*You have to install Samsung USB drivers to use ODIN flash tool
*File attached to this post
*Be carefull, I'm not responsable for using wrong the flash tool
* Hit THANKS Button if I helped you
Cheers, :highfive:
Click to expand...
Click to collapse
please help! still on flight mode - IMEI still missing, not able to detect sim card
Model Number:
GT-I9003
Firmware Version
2.3.6
Baseband Version
unknown
Kernel Version
2.6.35.7-CL709629
[email protected] #1
Build Number
GINGERBREAD.XXKPQ

georgeii13 said:
please help! still on flight mode - IMEI still missing, not able to detect sim card
Model Number:
GT-I9003
Firmware Version
2.3.6
Baseband Version
unknown
Kernel Version
2.6.35.7-CL709629
[email protected] #1
Build Number
GINGERBREAD.XXKPQ
Click to expand...
Click to collapse
Try to flash a stock rom. Try XXKPQ. And then if there still isn't an IMEI number try to reflash the efs file.

CSI.ISC said:
Try to flash a stock rom. Try XXKPQ. And then if there still isn't an IMEI number try to reflash the efs file.
Click to expand...
Click to collapse
Thank you for the response, CSI.ISC.
Can you please provide me the steps? Including the links for the tools? I'm sorry as I'm really a newbie on these stuffs. This would be my first time doing these..

Good luck.
georgeii13 said:
Thank you for the response, CSI.ISC.
Can you please provide me the steps? Including the links for the tools? I'm sorry as I'm really a newbie on these stuffs. This would be my first time doing these..
Click to expand...
Click to collapse
Well hello then, heres a guide for you. http://forum.xda-developers.com/showthread.php?t=1894737 There you can find almost everything that a newbie like you should know right now about our beloved device. When it comes to XXKPQ you can fint it here http://forum.xda-developers.com/showthread.php?t=1004647 along other stock roms and the efs you can find somewere up in this thread.
If you need any further help PM me .:highfive:

Ok. That (and a lot more methods) didn't work for me.
I'm running out of alternatives. There are a few left though...
I found out a long time ago that it is possible to fix some stuff through Hex Editing.
Today i found a tutorial that could help me. But it is for Samsung Captivate.
First im going to point out the following:
- I've done na extensive search and learning (that goes for almost a year and almost everyday for countless hours);
- I have my EFS.tar file but restore doesn't work. (Either through adb, either through SG Repair apk, PC Software to repair / restore efs; etc);
- Tried reverting to Froyo or GB... Didn't Work. (Among the other 35 diferente methods i've tried);
- I have the EFS Folder (a Copy Paste Backup) - From the date it was working;
- This issue happened after flashing Nameless Rom. (Don't ask what happened - i have no clue...);
- I Don't have Service Mode (Nor can enter 99% of menu codes - It displays no Network Message);
- I'm now using DDLF2 Custom Rom;
- After Reading this tutorial (for another Samsung device - Samsung Captivate): [http://forum.xda-developers.com/showthread.php?t=880223]
I went to discover and learn even more.
- So, after opening nv_data.bin (inside the folder) with na Hex editor i found out this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see it displays "DDBT". Shouldn't it display DDLF2?
- Searched for a Rom with the same build number. I couldnt find anythng. Although im pretty sure that there's a rom with this Build Number.
- My rom Build Number: GINGERBREAD.DDLF2
If someonecan help me (us - No Imei Users) with this:
- To know if the batch files from Samsung Captivate will work on our devices ["i9003"]
- How, What to verify and to correct under the efs files (with the Hex Editor)
- How to push my efs folder to the device (if the nv_data.bin is correct)
- Know if it is possible to change my IMEI with Hex Editor (since it is forbidden to post how in this forum due to US laws).
- Finally some help to make a tutorial for our device based on that thread, but for our device. (wich i dont mind to do it after i get it working). (Can also help and require help in builting a Windows Application for this Device specifically - So no one get their devices bricked :good: ) and to mark these kind of threads as solved. =)
Any experienced help would be 1000% apreciated.
Best Personal Regards;

CSI.ISC said:
Did somebody tried to flash a efs file. If not try. I was having the same problem in the past.
To flash the efs for I9003 you have to follow some steps
Get phone to the Download mode (Vol Down+Home+Power bundle)
Open Odin
Connect phone to pc with USB cable
Put efs.tar to PDA row
Click flash
Enjoy
*You have to install Samsung USB drivers to use ODIN flash tool
*File attached to this post
*Be carefull, I'm not responsable for using wrong the flash tool
* Hit THANKS Button if I helped you
Cheers, :highfive:
Click to expand...
Click to collapse
Do i have to be on the original stock rom while doing this?

Phone bricked itself and having issues recovering

Thanks in advance for any help you guys can provide. This one has me stumped.
First, I have never rooted my wife's device.
The other day it rebooted randomly and would never make it past the t-mobile splash screen. I figured since it wouldn't boot I would try clearing the cache within the bootloader. That made matters worse.
Finally, I did a factory reset to try and fix the problem and now the phone is telling me that there was a problem applying an update and I must use Smart Switch.
Well, when I tried using smart switch it get right to the very end and fails saying the it is FRP locked and no custom software can be installed. I read through some threads and tried using Odin to flash the device using the latest firmware version. Same error with FRP lock. At this point my phone wont boot and I can only get to the bootloader, or to the download screen.
Any suggestions on what I should do next? My KNOX is still at 0, but my software version reads custom for some reason, even though I didn't try to flash anything.

Have you tried using Kies recovery?

blah_blah_blah_blah said:
Have you tried using Kies recovery?
Click to expand...
Click to collapse
Yes, gives the same error as Odin and Smart Switch.
As another note when i enter the bootloader menu it says that it is unable to mount /system so it's as though it got corrupted some how. But I can't flash stock firmware to fix it due to the FRP lock.

Droid_phreek said:
Yes, gives the same error as Odin and Smart Switch.
As another note when i enter the bootloader menu it says that it is unable to mount /system so it's as though it got corrupted some how. But I can't flash stock firmware to fix it due to the FRP lock.
Click to expand...
Click to collapse
Just to make sure you use kies and emergency restore rite? You enter the phones serial number?

blah_blah_blah_blah said:
Just to make sure you use kies and emergency restore rite? You enter the phones serial number?
Click to expand...
Click to collapse
I did. It gets to the very end and then give me the FRP error. I could clear the FRP error if the stupid thing would boot to the OS so I could login.

Do you have tmobile ? And if so do you have insurance on it ?

Sounds like you should exchange. The only other thing to try is root the hell out of it.
---------- Post added at 09:51 PM ---------- Previous post was at 09:48 PM ----------
Mines had a tough life, but I brought it back to life after erasing everything in recovery. New, recovery first then the operating system. Yours could be broken, but you wouldn't know till you tripped knox. Not that t-mobile seems to care.

6.0.1 OTA for stock rooted system

Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.

Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.

Safest way.. ruu back to stock everything take ota and re root/download apps etc...

Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse

What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe

Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse

Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse

Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse

Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse

Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse

First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse

And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...

I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond

txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....

mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.

Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.

Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.