Database Develop

[Q] Restore original IMEI?

Long story short, my imei is not the current one under the battery and i want to get it back. Before i thought my phone wasnt unlocked and that was the problem but its not. The phone is unlocked and i even have the codes, i just want to use my own IMEI. I currently can not connect to any networks with the captivate.
So far i have tried using the .bak file in /efs with no success (different imei).
I have tried several posts on xda but all seem to unlock and not give you your proper imei back.
Any advice or information would be greatly appreciated.

Buuummmppp

b0uncyfr0 said:
Long story short, my imei is not the current one under the battery and i want to get it back. Before i thought my phone wasnt unlocked and that was the problem but its not. The phone is unlocked and i even have the codes, i just want to use my own IMEI. I currently can not connect to any networks with the captivate.
So far i have tried using the .bak file in /efs with no success (different imei).
I have tried several posts on xda but all seem to unlock and not give you your proper imei back.
Any advice or information would be greatly appreciated.
Click to expand...
Click to collapse
How did u manage to mess it up, may I ask. This way atleast u could warn the rest of the community not to mess ours up.

Its quite simple really, dont back up your /efs folder and keep messing around with roms.

I don't think anyone has solved this. Everything around the nv_data.bin file relates to unlocking and it says you must have a good IMEI number to start with. There was some 3rd party software that can fix IMEI numbers - but it required a separate breakout box. I forget the name, but many downloaded the software only to discover they needed to buy the box to get it to work.

One of mine managed to wind up with the generic imei but I have yet to see any ill effects from it.

I am sorry to hear about this, and even sorrier to have to say this, but xda does not allow posting of instruction on how one can change the imei.
Sent from my SAMSUNG-SGH-I897 using XDA App

Ok if we cant talk about this thats fine. Right now i cant connect to any networks. If someone would be willing to upload their /efs for me so i can try it out. Would that work?
Im in Australia so anything apart from that should work right??

did you ever got to restore your original imei?

Check here for a how to restore your IMEI.

New JL2 Bell i9000M not unlockable?

Hey guys. So I finally got my SGS back from Bell again (This is my 2nd replacement). Right away I got to work to unlock it. However, it seems that Bell has changed how unlocking works again. I recall when I got my first replacement, I could not unlock it. I could get the network control key (aka the "unlock code") using the SGS Unlock apk, but the phone would not accept this as a valid code. Instead, I was able to relock the phone to my carrier by changing the MCC/MNC code, and then entering the network control key. This worked perfectly.
This method does not to seem to work on my new replacement, however. Using the SGS Unlock and the generate unlock script, both can not seem to find the nv_data.bin file. As a result, I do not get an unlock code of any sort.
I've also attempted to downgrade my phone, but flashing JH2 with Odin puts my phone in a boot loop. Should I try another 2.1 ROM?
In the worst case, is it possible that Bell has been replacing phones with totally non-unlockable phones?
I'm at my wit's end as to what to try next. Any suggestions?

Greetings...Assuming you have rooted your phone, use SGS unlock from the market and you will need to install busy box as well.
That's what I used for my JL2 build and it worked.
Sent from my GT-I9000 using XDA App

Is busy box absolutely necessary? I had installed Darky's rom, so I had root+super user, but I'm not sure if I had busy box.
I had also tried to use the app to generate root codes, but it gave me the same error; no code found.

Rashar said:
Greetings...Assuming you have rooted your phone, use SGS unlock from the market and you will need to install busy box as well.
That's what I used for my JL2 build and it worked.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Rooted my phone and have busybox installed (I forgot that SuperUser = busy box).
Tried the apps from the market, didn't work.
When did you get your phone? Did you buy it new from Bell or was it a replacement?
edit: OKAY FORGET EVERYTHING I SAID
I figured it out.
This what I did:
1) http://forum.xda-developers.com/showthread.php?t=803682
I used this application to root my phone.
2) Restarted my phone (I tried to unlock without restarting, it didn't work.)
3) http://www.androlib.com/android.application.com-helroz-galaxysunlock-zxpBC.aspx
I then used this application to unlock. Remember to back up your EFS before doing anything.
4) I entered *#7465625# on the phone to verify the unlock.
I hope this helps anyone else who had the same problem as me.
Thanks a lot guys!

Codes often don't work on the new i9000m revisions. Use the nv_data hexedit method, changing 01 to 00, as can be found elsewhere in the forums.
Read around, your solution is out there already.
Best to do these things manually instead of with an automatic tool imo - only takes a few minutes longer, and then you'll actually understand the process.
Sent from xda premium app on i9000m.

update ASUS TF701T (k00c) android to latest version

Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob

(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!

one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.

thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again

I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2

bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?

greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.

fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke

V40 is it possible to change NT Code without Root?

I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.

suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code https://4pda.ru/forum/index.php?showtopic=951883&view=findpost&p=100635159 here is a list of NT codes:View attachment NT_code.txtunfortunately needed root!working with QFIL do backup ftm.bin!

lexih said:
I'm not sure, but worth a try,I warn the site is Russian, here's how to edit NT code here is a list of NT codes:View attachment 5134107unfortunately needed root!
Click to expand...
Click to collapse
Thank you for your reply. Yes, I have read many instructions even on this page how to edit, cust_path_mapping.cfg, and that it's surely easy once the phone is rooted. But that's why I first wanted to see the possibilities to do this without that I have to root the phone.

suain81 said:
I have read through many posts here in the forum, where I got some tips that I have tried, but nothing that totally applied to my problem, only parts of it. I have upgraded my phone with every firmware of the Open_EU since January 2020 without any problem using LGUP. Last time I upgraded to Android 10 in August, it was also successful but then check nt-code: 222201: ff started to appear everytime I turned on the phone. It's annoying, but not a big problem since the phone works perfect. However I tried to upgrade to Android 10 v405ebw30c recently, and now LGUP can't make the upgrade, it says can't cross-DL, with a strange message judypn_lao_eea ->judypn_lao_com. Could the NT-code be the cause of this? I also tried to enter the hidden menu, *#546368#*405# and I can see the nt code, but I can't change it. Nothing happens. Will I have to root my phone to make this work? or are there other options?
Some history, this phone doesn't officially exist in Sweden, where I live. However, it's possible to buy it anyway. It was sold as brand new and unlocked. The first week I discovered that I couldn't make the officially update . Then I found out it's originally italian (TIM), and probably someone that unlocked afterwards. But maybe not properly made since it was problem to make upgrades with LG Bridge. And when I succefully managed to make the upgrade with LGUP I decided to keep the phone anyway, because I liked it too much. But since this NT code started to appear after the Android 10 upgrade, I wondered if maybe there's some "leftovers" from TIM italy. So is rooting the only option for me? Except for the upgrade problems it works perfect every day.
Click to expand...
Click to collapse
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers

AsItLies said:
So, u have 2 problems right? u want to upgrade to v405ebw30c, but can't, and you also have the nt-code error right?
First, no, they aren't related. I think that's highly unlikely. That's not something lgup checks for. I'd bet you're using the 1.14 version dll and should be using the 1.16 dll and should be doing a refurbish.
As far as the nt-code error. It's a pain, lots and lots of info about fixing it, most of them need root. But here's what worked for me, no root needed: I switched from att pie to Korean open Q (first time had the nt-error and no editing anything would fix it), so went back to att and then did the korean 409N again, first with partition DL. Let that finish, it has to reboot the phone completely to finish. Then, don't change the phone in anyway, just shut it off. Back to LGUP and do a Refurbish with the same kdz.
No more nt-error code. It *seems* that nt-error code info gets propagated to various partitions as a part of refurbish. I verified that the ftm partition, where that information lives, was completely spaces (blank) after the refurbish... it's odd, I know. But for whatever reason, I no longer have the nt-error code problem.
cheers
Click to expand...
Click to collapse
Thank you for your reply. No I don't know if they're related either, it was just a guess since the problems started at the same time. Well, I always had a kind of "problem" since I never have been able to upgrade from LG Bridge. And that I guess is from the NT-code. But the sign in the start appeared after the Android 10 upgrade. However, I'm using LGUP 1.16.0.3 and I have used it everytime, with DLL version 1.9.39.7.
And actually it wouldn't bother me too much having this sign in the start anyway, I only restart the phone like once per week. But of course it bothers me that I can't make the upgrade like before. And I can also mention that I have never tried to refurbish with LGUP, only upgrades, because I have some bank apps etc. that are a bit complicated to reinstall. Of course it's possible, but I have to be mentally prepared for it. So I'll only do that when I know there's no other option. And the phone work good today, so I'm not in a rush, but in a couple of months I should be doing an upgrade of course.
And thanks for telling me the other option too, I will surely try it one day but since it also requires refurbish I will try after I fail to make the normal refurbish.
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.

suain81 said:
I don't have any experience of rooting, if I root my phone, will I keep all the data or is it comparable to refurbish? Are the any other risks rooting the phone? I'll lose the warranty, but I don't really have the warranty anyway since it's not an official product in my country.
Click to expand...
Click to collapse
No, to root, you loose all data and have to start again. Part of rooting is to flash dm-verity which turns off encryption. But, that allows you to do a backup of the data partition once you've reinstalled everything. The positive side there is that in the future, you could back up that partition (data), make any other changes, then flash data back, and your apps would be back as they were.
Other risks? Well, maybe, if the phone was stolen I guess, it would be easier for someone to steal your data. Your situation, with serious banking apps, it **may be** you don't want that risk...
Maybe for just trying a refurb to lose nt-code, look at LG's 'restore' from previous device ability, use it to save off the apps somewhere, then restore after refurb? no root needed.
cheers

Lancelot IMEI issue

Hello there.
I've got another problem with my lancelot. I've managed to rooted it successfully and install waveos, however, I still got an issue with no gsm data. I've found out, that my imei is missing - after typing *#06# phone shows you only hex serial number. It also does not show anything in system page in options.
I've read something about and tried to put back original imei back from the sticker. However, hydratool cannot open mtk module - it opens and before it is even able to load itself fully, it forceclose with no errors in log (it is the only module that it cannot open, rest works fine XDn't) and rest of the "tools" are simply crap.
What can I do? I did not have imei even when rolled back to miui 12 (I though it might be the issue, but it is not).

Here is a nice full guide that searching it certainly took less than writing this post ==> done by VD171
Make sure to thank him if you successfully solve the issue.
On a side note: Learn how to search stuff, it will save a lot of time for you and others.

XDHx86 said:
On a side note: Learn how to search stuff, it will save a lot of time for you and others.
Click to expand...
Click to collapse
You are definitelly right. I simply spend whole day on this and got actually tired of looking stuff, that leads to paid solution. I've even though of manual editing corrupted parts of rom (nvram etc), have working nvram from other phone as a correct matrix to do so.
Hope it works, I'll try it tommorow.

buczek0711 said:
You are definitelly right. I simply spend whole day on this and got actually tired of looking stuff, that leads to paid solution. I've even though of manual editing corrupted parts of rom (nvram etc), have working nvram from other phone as a correct matrix to do so.
Hope it works, I'll try it tommorow.
Click to expand...
Click to collapse
To edit nvram partition you need to flash engineering ROM first.
Hydra tool works, but it only works on engineering ROM, like I just said. And it's actually one of the main tools to fix IMEI.
Also Hydra tool isn't paid, what are you talking about?

XDHx86 said:
To edit nvram partition you need to flash engineering ROM first.
Hydra tool works, but it only works on engineering ROM, like I just said. And it's actually one of the main tools to fix IMEI.
Also Hydra tool isn't paid, what are you talking about?
Click to expand...
Click to collapse
Hydra ain't paid? That's good to know. I've got problem starting it though, mtk exe forced close itself before it loaded itself with no errors in logs, so I gave it up. I'll not have time today to do anything here, but I'll try in the following days.
I just assumed that changing imei is paid, just like getting rid of simlock years away.