Hi sorry for bad english
I had to edit my thread and put more informations, so, after i revert to stock rom (i used the self reverter rom in zte site), my imeis got doubled and with same 000039485642710 in both sim 1 and sim 2. For what i have research, its a commom bug that happends. If you search in google this imei, you will see that a lot of ZTE users got this problem. I tryied almost everything, but with no sucess. I have all original itens with original imei on the back of the phone box. The imeis was all right before. Now i have no data on sim slots since the imei have changed. Can anyone please help me to repair/revert to my original imei ? I cant buy other phone. Thanks
@brunojborges: No, custom ROMs dont change the IMEI. Sometimes my IMEI appeared as 0 when swapping SIM cards, but 4G LTE still worked.
I no longer own an an A7, but i did have to send it in for repair, i did notice that the IMEI had changed on the returned device. So i called ZTE and they confirmed that the device had been swapped with a different refurbished A7.
However, it is rare but possible that flashing firmware can corrupt the EFS, which is where the IMEI is stored.
Where did you buy your device? And how long ago? If you got it off Craigslist or from some shady site online, it is possible that previous owner reported the device and so the carriers blocked the IMEI.
And, if your IMEI really is blocked, you will need to contact your carrier. Have the IMEI ready, have them check it to see if it is blocked. If so, then by who and when. Try to get details. Depending on the details, you can explain your situation and they might unblock it. Or, they can advise on who to contact. Tough luck with this though, once an IMEI is blocked it will be very hard to get it off the blacklist, esp if it was reported stolen/lost. In that case, you have nothing more than a wifi phone.
AnonVendetta said:
@brunojborges: No, custom ROMs dont change the IMEI. Sometimes my IMEI appeared as 0 when swapping SIM cards, but 4G LTE still worked.
I no longer own an an A7, but i did have to send it in for repair, i did notice that the IMEI had changed on the returned device. So i called ZTE and they confirmed that the device had been swapped with a different refurbished A7.
However, it is rare but possible that flashing firmware can corrupt the EFS, which is where the IMEI is stored.
Where did you buy your device? And how long ago? If you got it off Craigslist or from some shady site online, it is possible that previous owner reported the device and so the carriers blocked the IMEI.
And, if your IMEI really is blocked, you will need to contact your carrier. Have the IMEI ready, have them check it to see if it is blocked. If so, then by who and when. Try to get details. Depending on the details, you can explain your situation and they might unblock it. Or, they can advise on who to contact. Tough luck with this though, once an IMEI is blocked it will be very hard to get it off the blacklist, esp if it was reported stolen/lost. In that case, you have nothing more than a wifi phone.
Click to expand...
Click to collapse
thanks to your answer friend!
So, i purchase this phone used, on sale site. With box, manuals, and all itens, and a import doc. I never had any problem with him (using 1 month or more). Everything was working ok. Just after i change the rom, in the same moment, my sims stop to work. So i decide to check the imei, and i realize that is different from the imeis on the back of the box (not shure but i guess, before the imeis was the same). The seller is from here (brazil), was the first owner, and the imei block is from argentina (the phone has never been there). So i just want to know if there is a software or something that i can use to insert the original imeis on the back of the box to the phone.
One more thing, the both imeis are exactly the same. I guess this makes no sense :laugh: :laugh:
@brunojborges: Well the issue is that you bought it used, which implies there was a previous ownee. Probably the online seller you bought from knew it was lost/stolen, but sold it anyway. There is a good chance that the phone IS from Argentina, probably where the previous owner lives. Everything may have seemed to be working OK, and was, up until it was reported, then it becomes blacklisted.
As already stated, changing custom ROMs doesnt mess with the IMEI. However, flashing firmware might. It is also entirely possible that your device is legit, legally speaking, and that whatever you did messed up the IMEI.
It is possible to restore the original IMEI/EFS with QFIL/QPST. I did so once on a friend's ZTE Blade and it worked. You can find instructions online. However, this program can do more harm than good, it is relatively complex to use, and so you must be careful and follow instructions to the letter.
I would still contact your carrier first.
AnonVendetta said:
@brunojborges: Well the issue is that you bought it used, which implies there was a previous ownee. Probably the online seller you bought from knew it was lost/stolen, but sold it anyway. There is a good chance that the phone IS from Argentina, probably where the previous owner lives. Everything may have seemed to be working OK, and was, up until it was reported, then it becomes blacklisted.
As already stated, changing custom ROMs doesnt mess with the IMEI. However, flashing firmware might. It is also entirely possible that your device is legit, legally speaking, and that whatever you did messed up the IMEI.
It is possible to restore the original IMEI/EFS with QFIL/QPST. I did so once on a friend's ZTE Blade and it worked. You can find instructions online. However, this program can do more harm than good, it is relatively complex to use, and so you must be careful and follow instructions to the letter.
I would still contact your carrier first.
Click to expand...
Click to collapse
thank a lot. i will try to learn what is this qfil and fix this issue, as i said, the both sim 1 and sim 2 are with the same number so something must be wrong with the device. and i remember to have flashed some firmware when installing any of the 10 or more roms. thanks.
Do you have the correct modem installed
Predatorhaze said:
Do you have the correct modem installed
Click to expand...
Click to collapse
yes i have. saddly, modem files dont chance imei numbers i guess. the key to my problem is the fact that the 2 numers are the same (and start with 0000xxxxxxxxxxx). Sould be different, but isnt. why? im very very sad coz im loosing nights trying to change this imeis and put the originals wrhiten in the back of the box. Xposed work, says ok saved and must restart, but when i do, there is no change at all. Tried softwares on pc in adb mode then shell then su, the program says ok but dont change. Dont know more what to do
any help please?
i want to thank everyone that knows how to solve this problem but didnt help me. Know that after 1 week of no sleeping and trying thousand things, i finally changed the both imeis to originals from the box. Im not a chief, i have buyed this phone legally, i have all original itens and documents and just got a bug. I hope i could continue to help people here with what i know, and never do what they did to me (or did not).
Did you try this guide here: https://www.******.com/repair-imei-snapdragon-device/
It's what I used to repair my IMEI in 2016 when I had a similar problem.
KwesiJnr said:
Did you try this guide here: https://www.******.com/repair-imei-snapdragon-device/
It's what I used to repair my IMEI in 2016 when I had a similar problem.
Click to expand...
Click to collapse
i tryied. A lot of things. A thousand tutorials and guides indeed. What worked was using a program to backup the partitions, then find, inside the binary file, the codified imeis, then change them to original imeis (using another program to change imei to binary) and save the file, then erase modem partitions in the phone with twrp, and then flash back the edited backup file with the right imeis changed.
edit: ofcouse nobody told me that, i had to try almost all possibilities on whole web and get little informations from thousand topics about thousand different things and put the pieces together.
brunojborges said:
...
edit: ofcouse nobody told me that, i had to try almost all possibilities on whole web and get little informations from thousand topics about thousand different things and put the pieces together.
Click to expand...
Click to collapse
Great that you solved your issue on your own... What I was asking myself is if you're seriously blaming others here for not providing a solution? Here people share what they now and their experiences... And I'm sure that all who read about your issue shared what could help you if they knew anything at all (and it didn't involve stuff forbidden from XDA Forum rules).
If you should really except, that folks here owe you to provide a solution then better look out for ZTE customer support (and be glad if you get any [surely useless] answer at all...) ... Although even they are fine out if device's software was modified...
But what I ask you do is to give a good example and provide your solution in a handy guide as you're the first one that I know of that actually found a solution for the lost IMEI issue, that happend only to very few persons before you here on XDA.
Gachmuret said:
Great that you solved your issue on your own... What I was asking myself is if you're seriously blaming others here for not providing a solution? Here people share what they now and their experiences... And I'm sure that all who read about your issue shared what could help you if they knew anything at all (and it didn't involve stuff forbidden from XDA Forum rules).
If you should really except, that folks here owe you to provide a solution then better look out for ZTE customer support (and be glad if you get any [surely useless] answer at all...) ... Although even they are fine out if device's software was modified...
But what I ask you do is to give a good example and provide your solution in a handy guide as you're the first one that I know of that actually found a solution for the lost IMEI issue, that happend only to very few persons before you here on XDA.
Click to expand...
Click to collapse
This forum has the most expert phone users in the world together, i can shure u at least one or two that knew how to solve, did read this thread but say nothing. But no problem my friend, was the very most hard thing i ever did, i will try make a simple steps and try to guide who need this to the right way. Just a moment.
Gachmuret said:
Great that you solved your issue on your own... What I was asking myself is if you're seriously blaming others here for not providing a solution? Here people share what they now and their experiences... And I'm sure that all who read about your issue shared what could help you if they knew anything at all (and it didn't involve stuff forbidden from XDA Forum rules).
If you should really except, that folks here owe you to provide a solution then better look out for ZTE customer support (and be glad if you get any [surely useless] answer at all...) ... Although even they are fine out if device's software was modified...
But what I ask you do is to give a good example and provide your solution in a handy guide as you're the first one that I know of that actually found a solution for the lost IMEI issue, that happend only to very few persons before you here on XDA.
Click to expand...
Click to collapse
Fist: This can potentially screw up your phone rendering it the equivalent of a paper weight IF not done correctly. So pay attention to each step. I am not responsible for lost baseband's, lost IMEI's, bricked phones and nuclear war. Proceed with caution and via your own will.
the phone must be rooted and with twrp.
in my case, i had the imei numbers on phone settings, but was invalid numers and they was the same on sim1 and sim2. Im saying that because we will make a backup of the partitions where are the wrong imeis, then find this numbers in binary inside the backup file (we will use other program to open and edit this file, and there is a tip to find this numbers in binady, so i dont know how to find where line is the imeis stored if they are erased or 0), then change this numbers in the file to the right ones using another program to change the right imeis to binary (so you must have the box of the phone with the original imeis or know them from somewhere as in any photo, text backup, etc), then erase this partitions on phone (after that my phone got crazy, hot, and with a lot of strange lines on system>about phone>imei information), then flash full stock with miflash (so then the imeis will show as 0 as the partitions will back but erased), then reflash any other rom with root and magisk and twrp, and then flash back the backup partitions file with right numbers changed. Then voalaa
most of the files to do this are here https://forum.xda-developers.com/general/general/guide-repairing-imei-qpst-qualcomm-t3856968
steps:
WRITE DOWN YOUR IMEI SOMEWHERE SAFE! IF you don't have it don't worry as your IMEI most likely is false / null. Whole reason we're here right? Ok. Now you want to connect your phone to your PC, enable diag mode on your phone, Install QPST Tools then open QPST Configuration. Allow debbug on developer options in phone, and when conect to pc, open adb prompt, and type:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
if this did not work, your phone has no root, or are not in debbug mode.
if was all right, you can proceed. remember if QPST.2.7.437 (version i used) did not recongnize your phone, maybe you must go into devices in windows and change driver to the one "qualcom" and with "901D" in the end.
Next open QPST Software Download and navigate to the Backup tab.
Make sure your com port is still showing and you are connected. Next click to the right of where it says xQCN file the "Browse" button and set a location and name your backup file something like coolpad_original_qcn.qcn . Save it as .qcn format not xQCN.
Now you are ready to open up MiTeC Hex Editor(program name) and load up your QCN file. So do this. Once loaded you will want to search for 088a to find your IMEI within the file. Why? Thats how it is stored in hex format. The 08 will be what stays but the 3rd letter "8" is what your IMEI starts with so make sure you replace it.. e.g. IMEI 762429035623741 would be 087a.. and if it started with 6 086a etc.
You should have located the string now that shows 087a then following will be the rest of your IMEI just reversed. Should look like this which is from our example IMEI in step 3, "087A 2624 0953 2673 1400". This translates out to 7 skip the first 08 and the A then 62429035623741 so 762429035623741.
Open the last tool called IMEI Converter. Input your phones new (factory original) IMEI in the first box and take the output and replace "087A 2624 0953 2673 1400" with this string you just created. Save your .qcn file and MAKE SURE you do not overwrite your original QCN backup.
now i had to erase the partitions on phone. what was in this tutorial i found, did not work. but this did: fist i had to go into twrp, so i go into console and typed this 3 lines, pressing enter after each line separately:
dd if=/dev/zero bs=16384 count=1 of=erase_modemst.bin
fastboot flash modemst1 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
fastboot flash modemst2 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
after that, reboot your phone. mine got very hot, a little crazy, and with strange infos in imei options. so i thought if i restore to stock, the software would make partitions back again but erased. and this is what happend. i flashed full stock nougat with miflash (no need links here, is easy to find stock nougat for your device as miflash software), and boot phone. all ok and imeis "unknow".
so then, i used edl tools to flash a eld package oreo with twrp after (my goad was only install twrp, but i only know do this with this method, any other doesnt work for me). https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759 (dont forget to read and get required files)
so with twrp, i did flashed a newer twrp and a rom slim aroma that has inbuid options to root and install magisk https://forum.xda-developers.com/axon-7/development/rom-slm7-dfnr-t3896486 (dont forget to read and get required files)
now, i enabled again debbug mode, and all this lines again in adb through pc:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
now for last, Open up QPST Software Downloader and goto Restore tab. Select your file we saved in the last step (.qcn file with imeis changed) and write it. Now reboot your phone. Check to see that your new imei is showing. Mine was back and i coudnt belive, only thing is that as the imeis was doubled, i didnt know how to change first so the imei 1 in my box is the imei2 on phone and imei 2 on box are imei 1 on phone. Not a big deal. I will not do all this again, no way.
tips: if your phone has stuck in DFU mode, just plug on pc and open edl tools, it will reboot to edl mode for you.
if your phone has stuck in edl mode, you will have to disassembly and disconect/connect battery flat. Is a bit easy, as you dont have to do nothing with the screen. or wait any days to drain the battery.
this is what i did after 1 week trying thousand tutorials. there was a lot of threads that i take some parts from one, ones from another, so i cant give the credits coz the truth is that i dont remember all them. I created nothing here, and 90% of what is here are not my words. all i did is put the pieces together. Really sorry for my bad english.
brunojborges said:
Fist: This can potentially screw up your phone rendering it the equivalent of a paper weight IF not done correctly. So pay attention to each step. I am not responsible for lost baseband's, lost IMEI's, bricked phones and nuclear war. Proceed with caution and via your own will.
the phone must be rooted and with twrp.
in my case, i had the imei numbers on phone settings, but was invalid numers and they was the same on sim1 and sim2. Im saying that because we will make a backup of the partitions where are the wrong imeis, then find this numbers in binary inside the backup file (we will use other program to open and edit this file, and there is a tip to find this numbers in binady, so i dont know how to find where line is the imeis stored if they are erased or 0), then change this numbers in the file to the right ones using another program to change the right imeis to binary (so you must have the box of the phone with the original imeis or know them from somewhere as in any photo, text backup, etc), then erase this partitions on phone (after that my phone got crazy, hot, and with a lot of strange lines on system>about phone>imei information), then flash full stock with miflash (so then the imeis will show as 0 as the partitions will back but erased), then reflash any other rom with root and magisk and twrp, and then flash back the backup partitions file with right numbers changed. Then voalaa
most of the files to do this are here https://forum.xda-developers.com/general/general/guide-repairing-imei-qpst-qualcomm-t3856968
steps:
WRITE DOWN YOUR IMEI SOMEWHERE SAFE! IF you don't have it don't worry as your IMEI most likely is false / null. Whole reason we're here right? Ok. Now you want to connect your phone to your PC, enable diag mode on your phone, Install QPST Tools then open QPST Configuration. Allow debbug on developer options in phone, and when conect to pc, open adb prompt, and type:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
if this did not work, your phone has no root, or are not in debbug mode.
if was all right, you can proceed. remember if QPST.2.7.437 (version i used) did not recongnize your phone, maybe you must go into devices in windows and change driver to the one "qualcom" and with "901D" in the end.
Next open QPST Software Download and navigate to the Backup tab.
Make sure your com port is still showing and you are connected. Next click to the right of where it says xQCN file the "Browse" button and set a location and name your backup file something like coolpad_original_qcn.qcn . Save it as .qcn format not xQCN.
Now you are ready to open up MiTeC Hex Editor(program name) and load up your QCN file. So do this. Once loaded you will want to search for 088a to find your IMEI within the file. Why? Thats how it is stored in hex format. The 08 will be what stays but the 3rd letter "8" is what your IMEI starts with so make sure you replace it.. e.g. IMEI 762429035623741 would be 087a.. and if it started with 6 086a etc.
You should have located the string now that shows 087a then following will be the rest of your IMEI just reversed. Should look like this which is from our example IMEI in step 3, "087A 2624 0953 2673 1400". This translates out to 7 skip the first 08 and the A then 62429035623741 so 762429035623741.
Open the last tool called IMEI Converter. Input your phones new (factory original) IMEI in the first box and take the output and replace "087A 2624 0953 2673 1400" with this string you just created. Save your .qcn file and MAKE SURE you do not overwrite your original QCN backup.
now i had to erase the partitions on phone. what was in this tutorial i found, did not work. but this did: fist i had to go into twrp, so i go into console and typed this 3 lines, pressing enter after each line separately:
dd if=/dev/zero bs=16384 count=1 of=erase_modemst.bin
fastboot flash modemst1 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
fastboot flash modemst2 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
after that, reboot your phone. mine got very hot, a little crazy, and with strange infos in imei options. so i thought if i restore to stock, the software would make partitions back again but erased. and this is what happend. i flashed full stock nougat with miflash (no need links here, is easy to find stock nougat for your device as miflash software), and boot phone. all ok and imeis "unknow".
so then, i used edl tools to flash a eld package oreo with twrp after (my goad was only install twrp, but i only know do this with this method, any other doesnt work for me). https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759 (dont forget to read and get required files)
so with twrp, i did flashed a newer twrp and a rom slim aroma that has inbuid options to root and install magisk https://forum.xda-developers.com/axon-7/development/rom-slm7-dfnr-t3896486 (dont forget to read and get required files)
now, i enabled again debbug mode, and all this lines again in adb through pc:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
now for last, Open up QPST Software Downloader and goto Restore tab. Select your file we saved in the last step (.qcn file with imeis changed) and write it. Now reboot your phone. Check to see that your new imei is showing. Mine was back and i coudnt belive, only thing is that as the imeis was doubled, i didnt know how to change first so the imei 1 in my box is the imei2 on phone and imei 2 on box are imei 1 on phone. Not a big deal. I will not do all this again, no way.
tips: if your phone has stuck in DFU mode, just plug on pc and open edl tools, it will reboot to edl mode for you.
if your phone has stuck in edl mode, you will have to disassembly and disconect/connect battery flat. Is a bit easy, as you dont have to do nothing with the screen. or wait any days to drain the battery.
this is what i did after 1 week trying thousand tutorials. there was a lot of threads that i take some parts from one, ones from another, so i cant give the credits coz the truth is that i dont remember all them. I created nothing here, and 90% of what is here are not my words. all i did is put the pieces together. Really sorry for my bad english.
Click to expand...
Click to collapse
Great to have that here. Thanks for putting it together, impressive.
Related
Hi all,
Apologies but I am real new to this and not sure if I am doing it right.
My Galaxy S I9000 on day stopped receiving and making calls. To cut a long story short after a million calls to my network found that my IMEI was not the same as the one on the back of my phone and told me I have tried to Jailbreak it (whatever this means) and nobody will take responsibility for it. After much heartache I had to purchase a new phone as I really need it.
Now my Galaxy S I9000 is a pc. Works perfectly on the net, games, videos etc but cant make calls or receive them. All I can think is that my 3 year old did something to it while playing games.
I wonder if the IMEI number can be restore, this should be legal as the phone is mine and I just want to repair it.
I am absolutely useless at all the jargon so I will pretty please ask for plain plain english.
Thanks for your help in advance.
I`ts illegal to modify the IMEI.So noone can help you here.Even if that means restoring it to the original.
Flash a new stock rom. This will usually solve your problem.
If something has overwritten your IMEI details, I.e "jailbreaking" or updating firmware. Then flashing a stock ROM will not help. It's near to impossible to change the IMEI data as it is encrypted information.
What may be a possibilty is restoring the backup file located in your /efs filesystem. I have done this before and worked flawlessly
How much experience do you have within linux/android?
EDIT: Backup your /efs filesystem first.
What you will have to do first is move the nv_data.md5 to say.....nv_data.md5.old. Reboot the phone, if it is recreated, then you should be good to go to attempt a recovery to your IMEI.
You must have root access. Do not flash a new level of firmware yet. Type in to *#1234# and reply with what it says :-D
I'm going to try and find my old post on another forum which should help you.
EDIT: CLICK HERE For link
How is this even possible to change the IMEI number ???
zamiurratul said:
How is this even possible to change the IMEI number ???
Click to expand...
Click to collapse
Same question here. If it's possible, than the existence and purpose of the IMEI would be pointless.
Some googling brought up similar threads here on xda and other forums. One guy posted something like this, hopefully it will work:
Hey guys, I flashed back to JPY (single file - no 512 pit) and on reboot it came up with a load of errors. On recovery screen, I formatted everything, wiped the partition and formatted the internal sd. Rebooted the phone and everything was fine.
Click to expand...
Click to collapse
I cannot post link to the original topic because of my post number.
I hope this helps, I didn't test it myself (because I didn't have this kind of trouble).
Some basics - About bootloader, kernel, recovery, rom, /system and some other partitions.
There are many noobs out there and sometimes even I am one. Two days ago @Closed Force asked me, where I know my stuff from and why things are like they are... So I finally decided to write this little guide about how Android devices basically work and what are the special things about our G2.
If you find wrong facts or any other mistakes (grammatical, language, contentwise), please bear with me. That's how I read it in the forums. And of course not everything written on XDA is correct. So please tell me by PM, or by posting in this thread if you have additions, corrections or any other concerns about this OP.
Where I got to know all this stuff? Reading, reading, reading. I first started modding my old HTC desire like 4 years ago. Since then and even before I'm reading. Mainly here on XDA but also on some german forums and wikis. It might have taken me easily 200 hours or more. So the only way to learn for a newbie (and everyone else too) is reading.
Personally I own a D802 variant. I know about some things that were different in details for the US variants, but things should be right as they are.
Finally thanks to
@d00lz for some extra research/additions and a quick read through.
@Art Vanderlay for some additions.
So let's get started:
When you press the power button, your device will load the Bootloader. The Bootloader afterwards wil load either the Recovery Image (recovery.img), the Kernel (boot.img) or the Download Mode Bootloader (laf.img), depending on the keys you press. At the moment there are three different bootloaders; The Jellybean one, the KitKat one, and the new Lollipop one. Not one of these Bootloaders can be unlocked yet, so there are workarounds which allow us to boot custom ROMs (specifically Kernels, but more about that later) and custom Recoverys. At the beginning there was the Jellybean Bootloader. The Developers (sorry, I don't know which ones) found out how to get around the locked Bootloader pretty early. They called this workaround Loki. It's intergrated into nearly every ROM except the ones which require the KitKat Bootloader (but that's usually not the reason they don't support the JellyBean one). Anyways, soon the KitKat update came and so did the new KitKat Bootloader. Sadly, LG patched the Loki exploit with this new update. However, the Developers found a new way to get the Bootloader booting files which weren't signed by LG. They called this workaround Bump. Bump basically imitates the LG signature so the bootloader thinks this file was really signed by LG. Obviously this workaround works with the JellyBean Bootloader too. In the Lollipop Bootloader this exploit has been closed and no one knows how to get around the new Bootloader, yet. In conclusion to Bootloaders, as long you have a working Bootloader, your device is not dead. You can usually recover it in some way.
The G2 has about 30 partitions (for a more detailed explanation, look here, thanks @d00lz). Each partition has its own purpose. One of them is the Recovery partition. Imagine: A Recovery partiton and a working Bootloader are everything you need to keep your phone working. It's kind of an Operating System in itself, completely independent from Android or anything else stored on your Mobile. The great thing about the Recovery partition is that it's so small that it can be run directly in the RAM. This means it's capable of modifing EVERY goddamn partition on your Mobile, including the Bootloader and the Recovery partition itself (means you can flash a new recovery.zip in your current recovery). Attention: if you are using the Recovery with a 4.4 KitKat Bootloader, it needs to be a Bumped Recovery. If it isn't bumped the Bootloader realizes that the Recovery is not genuine and generates a "Secure Boot Error".
Same thing goes for the Kernel. The Kernel is located in your /boot partition (found gzipped inside your boot.img) and is loaded by the Bootloader when you only press the Power Button and you let your Mobile boot normally. This is the reason why your Kernel also needs to be Bumped if you want to get your system booting on a KitKat Bootloader. When 4.4 KitKat came out, most Developers switched over to using LG's 4.4 KitKat sources for their projects. After a while it was realized that 4.2 JellyBean sources were a lot more reliable for AOSP baed ROMs. This is why most AOSP ROMs use the 4.2 JellyBean Bootloader and the 4.2 JellyBean Kernel sources while Stock based ROMs use the 4.4 KiKat Bootloader and 4.4 KitKat Kernel. There are different Kernels for AOSP ROMs and for Stock based ROMs. This is because Stock Kernels support some ROM functionalities that AOSP ROMs don't have, for example; Knock Code. (Note: Knock Code isn't open source, which is also another big reason why it isn't available for AOSP ROMs.) So there are huge differences between Stock and AOSP based ROMs/Kernels. The Kernel (without factoring in the AOSP and Stock issue) can be switch at anytime you want.
Now about the /data partition... All your personal stuff, including Apps, System Settings, App Data and so on will be stored there. The reason why you should clear it every time you change the ROM is that there are many variables set by the ROM you are coming from. Your current ROM may have some tweaks the new one doesn't have which means the new ROM doesn't know how to handle them which leads to crashes and instability.
Now let's get to the ROM... Having a 4.2 JellyBean Bootloader and a 4.2 JellyBean Kernel doesn't mean the top layer has to be 4.2 too. Most of the AOSP based ROMs are based on Googles KitKat or Lollipop sources. And this is true KitKat or Lollipop, with all its functionalities. Those huge version differences cause some problems in development. No wonder some things do not work properly today, but it's still the best working combination at the moment. It's kind of a wonder how it works as it is, but let's be happy with it. I'm very curious how AOSP ROMs with Lollipop Kernel sources will work. Your ROM and your entire existing Operating System is found in the /system partition. This is why it's the main partition which is modified while flashing. Which partitions will be modified and (how) is written in the updater-script file of the file you're going to flash. Theoretically, running a updater-script of a ROM which changes the Bootloader (/aboot partition) can brick your device. That's also the reason why you should only flash stuff made for your device only!
As already said an updaterscript can modify every partition through the recovery. All ROMs bring their own kernel, so you basically don't have to care about it, except you want to use a non-bumped ROM (with kernel) together with the KitKat bootloader.
Finally something about the baseband/modem (these terms are interchangeable). I noticed that the Developers or rather the Original Posters sometimes don't know which baseband the user should use with the ROM. In earlier days the wrong baseband could make the ROM bootloop. Today most ROMs work with most basebands. It's obviously best if you stay on the one you currently are on and just flash another one if something doesn't work (auto-rotation for example). The baseband can be flashed at any time and is on it's own partition.
Okay Download Mode time. It's part of the laf partition (laf.img). This partition is used by LG and it's PC software to recover the phone and bring it back to Stock. It's a partition in itself, but not completely independent of the Bootloader. It's because of this that you can of course have a fully working Bootloader, but a dead Download Mode. This means you will not be able to flash a .KDZ/.TOT file the next time you are in big trouble! ^^
Okay to wrap up I should mention the EFS partition. The EFS partition stores your device's IMEI (and the serial number as far as I know) of your device. NEVER wipe it. With a empty EFS partition you can use your mobile as a brick, ok maybe you can use it as a media tablet, but that's it (WiFi still works, @Art Vanderlay tested; see below).
Again: if you got questions/additions/correction or see a mistake, post below, or PM me, I'll edit this post...
reserved
Great post. A thread like this should be the first thread you read as soon as you enter the LGG2 sub forum.
Expect a private message soon.
Also, reserved for possible future additions .
d00lz said:
Great post. A thread like this should be the first thread you read as soon as you enter the LGG2 sub forum.
Expect a private message soon.
Also, reserved for possible future additions .
Click to expand...
Click to collapse
And you could modify your signature now^^
Sunandroid said:
And you could modify your signature now^^
Click to expand...
Click to collapse
Nice write up Sunny. You can credit Dan Rosenburg for creating loki. I can also confirm that wifi still works without modemst1 and modemst2 aka efs. My phone suffers for this thread.
@Sunandroid
Perfect! This was all I was looking for. Now I finnaly understand how my G2 works and I'll most likely not need to ask more "noob questions" in this matter.
But I would like to ask some questions because I've left with doubts after reading the OP.
As long as I have /recovery/ and /aboot/ working, I can recover my device exclusively with software. Is this right?
I've concluded that you need /aboot/ to be able to enter in /recovery/ and with recovery you can mess up with any other partition.´
How can I tell if /modem/ found here is compatible with my device? Are all /modem/ partitions the same in the same models? For example, I'm from Portugal so I have a Portuguese D802 LG G2 (if I type its IMEI in a site, it recognizes it as portuguese). If I flash a German D802 modem or English or even American, considering that they are all from D802 would they work flawlessly with my device?
Why does /modem/ cause auto-rotation to work? What exactly is /modem/?
I have a backup of all the partitions in my laptop (made via TWRP). But what happens if I accidentaly lose my /efs/ partition? Can I flash another phone's /efs/?
Rayaxe said:
@Sunandroid
Perfect! This was all I was looking for. Now I finnaly understand how my G2 works and I'll most likely not need to ask more "noob questions" in this matter.
But I would like to ask some questions because I've left with doubts after reading the OP.
As long as I have /recovery/ and /aboot/ working, I can recover my device exclusively with software. Is this right?
I've concluded that you need /aboot/ to be able to enter in /recovery/ and with recovery you can mess up with any other partition.´
How can I tell if /modem/ found here is compatible with my device? Are all /modem/ partitions the same in the same models? For example, I'm from Portugal so I have a Portuguese D802 LG G2 (if I type its IMEI in a site, it recognizes it as portuguese). If I flash a German D802 modem or English or even American, considering that they are all from D802 would they work flawlessly with my device?
Why does /modem/ cause auto-rotation to work? What exactly is /modem/?
I have a backup of all the partitions in my laptop (made via TWRP). But what happens if I accidentaly lose my /efs/ partition? Can I flash another phone's /efs/?
Click to expand...
Click to collapse
Glad I could help you this way...
about /aboot and /recovery: yes you are right. It is even better, if you have an intact laf too. That's the download mode. But as long the other two work, you can fix the laf partition easily. But if you get into the situation, that only those two are working, better don't flash a bootloader (=/aboot). If it's the wrong one your device is bricked.
Aboot is the key to your device. Everything else is fixable. At least with a little bit of knowledge and time. But better don't try it out.
No, the modems are not all the same. There are (sometimes depending on the branding) extremely small differences between the basebands/modems. I personally never had the problem, that I couldn't get any connection at all. But that's not fatal. Just flash another one and try again if it works. Btw: I once made a test in some german forums with different KK basebands. I'm not sure anymore, but the differences were minimal and I think killed my connection totally.
If you loose your efs stuff, your device is a brick with extended functionalities. The IMEI and some other data stored in the efs partition is worldwide unique. So you can't just pick the one of another phone (except the other G2 is bricked or whatever). You need the IMEI for general network connection. So it will still boot up, but you won't be able to text or call anyone with this phone.
Okay ^^
So this is a full backup of all the needed partitions right? http://prntscr.com/76edu4
Should I convert these files to something like .img to be able to flash in the phone just in case I get something that disables my TWRP access?
Rayaxe said:
Okay ^^
So this is a full backup of all the needed partitions right? http://prntscr.com/76edu4
Should I convert these files to something like .img to be able to flash in the phone just in case I get something that disables my TWRP access?
Click to expand...
Click to collapse
Yeah, I guess so. As long as you ticked everything when you backed up (with blastagators TWRP!; the official one doesn't allow to backup the efs stuff), this should be fine.
Well you could. But tbh I have no idea how to convert those files into .img files. But it isn't necessary anyways: It's unlikely that you loose the efs data on your phone unless you brick it somehow. If the phone stays recoverable, The first thing you are going to do is: flashing bootloader, laf and boot.img. Then you will go back to stock through the download mode. Once you've done this it's an easy one to install twrp again and restore the efs backup. No one is gonna flash ~32 partitions by hand. There are "easier" and more usefull ways to recover the device.
Oh and btw: no backup contains the bootloader, laf and boot (recovery developer don't implement this for some reasons). But this doesn't matter. The only thing you really need is the efs backup (which partitions exactly you can see here). Everything else isn't unique and can be extracted out of kdz files and restored this way.
Edit: the two partitions mentioned here are
Sunandroid said:
Okay Download Mode time. It's part of the laf partition (laf.img). This partition is used by LG and it's PC software to recover the phone and bring it back to Stock. It's a partition in itself, but not completely independent of the Bootloader. It's because of this that you can of course have a fully working Bootloader, but a dead Download Mode. This means you will not be able to flash a .KDZ/.TOT file the next time you are in big trouble! ^^
Click to expand...
Click to collapse
My PC doesn't install any driver when my phone is on download mode,
On recovery mode (twrp) i have MTP access but on download mode i'm not having any access,
does that mean my download mode is dead?
GoPogoOreo! said:
My PC doesn't install any driver when my phone is on download mode,
On recovery mode (twrp) i have MTP access but on download mode i'm not having any access,
does that mean my download mode is dead?
Click to expand...
Click to collapse
This has nothing to do with this thread here. The issue is different. But I have no clue what it might be... If I can elaborate a maybe working answer I'm gonna answer you in the noob thread.
Sunandroid said:
This has nothing to do with this thread here. The issue is different. But I have no clue what it might be... If I can elaborate a maybe working answer I'm gonna answer you in the noob thread.
Click to expand...
Click to collapse
Oh btw i tried your (noob friendly) no download mode, no recovery mode ..... using slax,
when i typed ls /dev/sd* it's only showed my PC (only one sda) and there is no sdb, not even one
Weirdly i can access TWRP, but i can't make any custom rom boot,
Man this is frustating
I have a phone, G2 D802 Int., which probably has a corrupt EFS partition. I guess the owner broke it flashing incompatible things into it. As a result of the corruption, ESN/IMEI is lost. It shows null. But very interestingly, the EFS partition mustn't have been wiped because by chance of a boot among a hundred, it shows up the ESN. If by chance you come across to ESN, everything operates normally. And if you reboot the phone, ESN is gone again..
I managed to make recovery work again, by upgrading the phone to lollipop. (It was another time I came across ESN.) But no download mode, USB is never identified (unkonwn usb device), USB modes cannot be changed, unless by chance you come across, USB debugging is no more either.
I was thinking to backup some necessary partitions from a working phone of the same variant, but since it's "unknown device", I cannot query it as a disk. Neither it works in Ubuntu. ls /dev/sd* doesn't show the phone. It even doesn't show the working phone.
Any idea about how I can fix the corrupted EFS partition?
pisisler said:
I have a phone, G2 D802 Int., which probably has a corrupt EFS partition. I guess the owner broke it flashing incompatible things into it. As a result of the corruption, ESN/IMEI is lost. It shows null. But very interestingly, the EFS partition mustn't have been wiped because by chance of a boot among a hundred, it shows up the ESN. If by chance you come across to ESN, everything operates normally. And if you reboot the phone, ESN is gone again..
I managed to make recovery work again, by upgrading the phone to lollipop. (It was another time I came across ESN.) But no download mode, USB is never identified (unkonwn usb device), USB modes cannot be changed, unless by chance you come across, USB debugging is no more either.
I was thinking to backup some necessary partitions from a working phone of the same variant, but since it's "unknown device", I cannot query it as a disk. Neither it works in Ubuntu. ls /dev/sd* doesn't show the phone. It even doesn't show the working phone.
Any idea about how I can fix the corrupted EFS partition?
Click to expand...
Click to collapse
I luckily never had to try it, but scroll down a bit over here: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
I wish you luck!
Sunandroid said:
I luckily never had to try it, but scroll down a bit over here: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
I wish you luck!
Click to expand...
Click to collapse
Yes I know that, but since I cannot take the device to USB debugging mode, it's not the first step I could take. "USB device descriptor is failed", this is what I get when I plug the phone.
pisisler said:
Yes I know that, but since I cannot take the device to USB debugging mode, it's not the first step I could take. "USB device descriptor is failed", this is what I get when I plug the phone.
Click to expand...
Click to collapse
So what is the current state of your phone? You have twrp installed. Can you push stuff through adb when you are in the recovery (this is pretty important, since we maybe can fix the download mode this way)? Does it boot into android?
@Sunandroid, device operates normally except the voice call & data, since these depend on IMEI. The phone boots normally, and everything is working, only the IMEI shows as "null". Additionaly, cannot enter to download mode, no recovery installed, original recovery is working, which is used to do a factory reset only. No USB debugging, it says "USB device descriptor failed". Thus no adb.
pisisler said:
@Sunandroid, device operates normally except the voice call & data, since these depend on IMEI. The phone boots normally, and everything is working, only the IMEI shows as "null". Additionaly, cannot enter to download mode, no recovery installed, original recovery is working, which is used to do a factory reset only. No USB debugging, it says "USB device descriptor failed". Thus no adb.
Click to expand...
Click to collapse
From what I've read about this issue (device descriptor...) just now, it is not software but hardware related.
I've heard of people solving that issue but I couldn't manage to do. Gave the phone to my customer back after 4 days. Importer service put the phone out of warranty and offered him a motherboard replacement for 75 $ and it's pretty fair I think. After all it comes funny when he says he's gonna file a case about returning the phone and take his money back. Well, it's up to him to end up with nothing in hands after months of waiting for a case.
Shortly, this file has been closed without a reasonable solution.
Thanks for your effort @Sunandroid.
pisisler said:
I've heard of people solving that issue but I couldn't manage to do. Gave the phone to my customer back after 4 days. Importer service put the phone out of warranty and offered him a motherboard replacement for 75 $ and it's pretty fair I think. After all it comes funny when he says he's gonna file a case about returning the phone and take his money back. Well, it's up to him to end up with nothing in hands after months of waiting for a case.
Shortly, this file has been closed without a reasonable solution.
Thanks for your effort @Sunandroid.
Click to expand...
Click to collapse
Glad to hear that. Hitting the thanks button doesn't hurt.
I recently had to flash a new rom to my 306sh. Many posts here claim to have a rom for anyone in need of one. I had no luck with these roms. My brother happens to have the same phone I have, and I had rooted and installed twrp awhile back. I was able to use his twrp backup to restore my phone. It was a matter of replacing the serial numbers in his twrp backup log file from his phone's serial number to my phone's serial number, otherwise his backup would not show up in my twrp restore option. It was a real pain dealing with a phone that barley worked, and I want to help anyone here that may be needing to restore their aquos crystal. There isn't much development going on for our phones unfortunately, but maybe this small gesture will help someone. If you need it, pm me and I will share a link. I will answer any questions that may arise for those of you attempting to use this backup. As usual, I am not liable for any damages that may result in using this method. Use this at your own risk. I can tell you that everything went fine for me with no errors.
You'll need:
rooted aquos crystal 306sh
twrp
sdcard
TWRP.rar
1. Unrar TWRP.rar
2. Rename serial number folder in: Twrp/backups/"serial number"/1970-04-28--18-00-22_KVT49L/ to your serial number. (I got my serial number by doing a backup in twrp. The name of the folder in twrp/backups/**************/ was my serial number.)
3. Open recovery.log file in twrp/backups/"**************"/1970-04-28--18-00-22_KVT49L/ and ctrl find every instance of my serial number and replace it with your serial number. There were about 12 instances for me. Now save recovery.log.
4. Copy twrp folder to your sdcard.
5. Boot into twrp and make sure the backup is showing up in the restore section. (When I first tried to use my brothers backup, it wouldn't show up in twrp. Apparently this is because twrp makes a backup of your phone with your phone's serial number embedded in it, hence having to rename all instances of the serial number.) Once you've confirmed that it is showing up go ahead and factory reset your phone.
6. Now go to the restore option in twrp and restore the backup.
7. Profit
I'm terrible at explaining things over the net, so if any of these steps are unclear, feel free to ask questions here or pm me. Good luck. Also, if you haven't tried Bullet Force on the play store, I highly recommend it. Looking for friends to play with.
Boost Mobile Sharp Aquos Crystal 306sh
HW version: 1.00
Android 4.4.2
Baseband: 01.00.00
Kernal: 3.4.0 [email protected] # 68
Build: KVT49L01
SW: S7323
I did it, but the sound is terrible
wheeze rather than voice
I don't see a download link for this
KnightTim said:
I don't see a download link for this
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B2lJ_mumqoU2a01zQjlFZnhuTlk/view
take this ... it is the text now, but it works
I need (find) firmware SPRINT
I need a 306sh Rom PLEASE PLEASE PLEASE
Kingroot got me stuck in a boot loop and I did a factory restore but for some reason, my phone has NO recovery partition on it! Factory sent it that way!!! The company refuses to give me the ROM unless I renew my service but I just use this phone as a Kodi remote now. Can you PLEASE email the link to that rom? [email protected]
jen0va said:
I recently had to flash a new rom to my 306sh. Many posts here claim to have a rom for anyone in need of one. I had no luck with these roms. My brother happens to have the same phone I have, and I had rooted and installed twrp awhile back. I was able to use his twrp backup to restore my phone. It was a matter of replacing the serial numbers in his twrp backup log file from his phone's serial number to my phone's serial number, otherwise his backup would not show up in my twrp restore option. It was a real pain dealing with a phone that barley worked, and I want to help anyone here that may be needing to restore their aquos crystal. There isn't much development going on for our phones unfortunately, but maybe this small gesture will help someone. If you need it, pm me and I will share a link. I will answer any questions that may arise for those of you attempting to use this backup. As usual, I am not liable for any damages that may result in using this method. Use this at your own risk. I can tell you that everything went fine for me with no errors.
You'll need:
rooted aquos crystal 306sh
twrp
sdcard
TWRP.rar
1. Unrar TWRP.rar
2. Rename serial number folder in: Twrp/backups/"serial number"/1970-04-28--18-00-22_KVT49L/ to your serial number. (I got my serial number by doing a backup in twrp. The name of the folder in twrp/backups/**************/ was my serial number.)
3. Open recovery.log file in twrp/backups/"**************"/1970-04-28--18-00-22_KVT49L/ and ctrl find every instance of my serial number and replace it with your serial number. There were about 12 instances for me. Now save recovery.log.
4. Copy twrp folder to your sdcard.
5. Boot into twrp and make sure the backup is showing up in the restore section. (When I first tried to use my brothers backup, it wouldn't show up in twrp. Apparently this is because twrp makes a backup of your phone with your phone's serial number embedded in it, hence having to rename all instances of the serial number.) Once you've confirmed that it is showing up go ahead and factory reset your phone.
6. Now go to the restore option in twrp and restore the backup.
7. Profit
I'm terrible at explaining things over the net, so if any of these steps are unclear, feel free to ask questions here or pm me. Good luck. Also, if you haven't tried Bullet Force on the play store, I highly recommend it. Looking for friends to play with.
Boost Mobile Sharp Aquos Crystal 306sh
HW version: 1.00
Android 4.4.2
Baseband: 01.00.00
Kernal: 3.4.0 [email protected] # 68
Build: KVT49L01
SW: S7323
Click to expand...
Click to collapse
!!!!!!!!
WOW THIS IS EXACTLY WHAT I SPENT THE LAST 3 HOURS GOOGLING FOR!!! I wonder why it didn't show up higher in the SERPs?
304sh
cybernoir84 said:
WOW THIS IS EXACTLY WHAT I SPENT THE LAST 3 HOURS GOOGLING FOR!!! I wonder why it didn't show up higher in the SERPs?
Click to expand...
Click to collapse
Dear all bros,
I have an 304sh. I tried to boot it into TWRP but it didn't. I pressed Power button and hold until the phone had a long vibrate, then I tried to press, press and press continuously, the phone was turn off. It didn't go into TWRP. I dont know why. Anyone can help me please?
I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.
Same here, except I have no issues with it saying its rooted
just the boot message
If you want a normal stock phone then don't buy Chinese oem devices. They have to add tons of tracking and spying software that is required by the Chinese government. You can research it. Many are even banned in many countries due to their back ally tactics
Darth_revan_returns said:
Same here, except I have no issues with it saying its rooted
just the boot message
Click to expand...
Click to collapse
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.
vostok_amphibia said:
I managed to solve the problem. If you don't have a lot of experience with Android, you'll have to do a bunch of research, but you should manage. Very roughly, I pretty much flashed a new operating system on the phone. I found the correct os rom from here: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657. I'm definitely a novice in doing weird **** with androids so don't consider me an expert or anything, but I did get my phone to work.
If you don't know what to do here's a rough guide.
1. Get adb to work
Adb is basically a way for your computer to tell crude instructions to your phone and all kinds of random ****. The very very first thing you should do is unlock developer options and turn on developer options by going to settings->system->about phone and click on build number something like 7 times and then go back to system, where developer options have appeared and turn on OEM unlocking and usb debugging. You should be able to find some type of adb installer installer simply by googling how to install adb or something, I can't remember at all where i found mine from, but there are certainly a lot of guides online. It really doesn't matter that much if it's from a few years back, as long as adb works. Your phone should install all correct drivers from your phone simply by connecting it, but you may need to download qualcomm drivers online, I don't really know because I downloaded every random driver online until finally it worked. All I can say that to finally get it to work I connected my phone to my computer via cable with usb debugging enabled and clicked the windows message so that the phone agreed to the final necessary drivers and amazingly it worked. To make sure that everything you need is in working order type the following commands into adb:
First "adb devices" if it says something like device found, DRG...., everything's good so far
Then "adb reboot bootloader" and "fastboot devices", if it says the same thing again, adb is completely installed.
I found this to be by far the hardest part in the whole operation, because the Nokia X6 is such a new phone that there are no real guides or official drivers online. Don't be discouraged if it takes some time to get through this part!
2. Unlock your bootloader
Nokia is pretty cool and all, but that they are pretty restrictive with their phones so that you actually have to pay to a third party to be able to unlock your bootloader. You need to buy a bootloader unlock key from this place: https://www.techmesto.com/buy-nokia-bootloader-unlock-key/. I know it seems super shady, but it at least worked for me so there's that. I wouldn't really buy the unlock key before getting adb to work, though. After that, you'll probably be best off following this guide to unlock the bootloader: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
3. Install the nokia online service tool and nb0 unpacker
The Nokia OST you can find here: https://www.theandroidsoul.com/download-nokia-online-service-tool-ost/, and I think the guide there is pretty self-explanatory, so just follow that. The nb0 unpacker you can find here: https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464. This one should be very simple to install.
4. Download the Nokia X6 operating system and unpack it so you can flash it with the online service tool.
The nokia X6 operating system can be found from the google drive link in this post: https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657, and be sure to pick the on mentioned in the post, the one labeled "DRG-229E-0-00CN-B01". After downloading it, you should be able to find a .nb0 file in the zip. Extract it somewhere nice and then use the nb0 unpacker you installed to unpack it. After this, open the mlf-file in the unpacked nb0 folder and follow the following instruction found on the download post i linked before:
"Modify *.mlf file, line 7 ~ 9;
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001" @Xkernels
5. Flash the os on your phone
Make sure to delete everything from your phone before doing this, because every guide I've seen instructs to do this. This may not even be necessary as the OST setting you'll check later indicate that everything will be erased anyways, but idk what could happen so better safe than sorry. You can do this probably in many ways but one way i found is to go to recovery (type "adb reboot recovery" on your pc and then press the power and vol up button at the same time), and factory reset. Then go to the bootloader from there and type "fastboot erase system". A bunch of text should appear and you should be set to flash. Now with your phone connected to your pc, open the Nokia OST and "Select *.mlf files and tick "Normal Download", "Erase user data", "Erase error data", begin to flash." @Xkernels.
6. Your phone should be ready to use, though it will probably need some configuring
The first things you'll probably want to do is use the browser to download a google play apk online after which you can use the play store and download all necessary apps from online. I couldn't find netflix from the appstore but I simply downloaded the apk online and it works too. I had problems with the stock keyboard so I installed Gboard, but all apps should be in working order and my phone works without a hitch now!
For the record if you manage to brick your phone during the process, don't hold me liable. If you followed this guide, you probably bought a chinese random phone and it didn't work like you wanted it to and wanted to fix the problems by installing an operating system from online, using a guide from a person you didn't know at all. All I can say is that what I did worked for me and I simply wanted to help strangers on the internet and this worked for me. So if, because of this guide, everything is ****ed with your phone and your computer is full of viruses, I will most likely be glad to help and you can blame me by yourself, but I definitely would appreciate if you would simply be civil and not tell me how I'm an awful person, because once again, I'm just a Finnish guy, who himself bought a Nokia for 200€ from eBay and had to spend hours upon hours of my own time trying various methods of getting my phone to work and learning how to use adb and how to flash roms on my phone. Honestly the experience was pretty fun for me, because I like to do random **** like this and learning new things, but I did have other things to do with my time like study physics and even now I wrote this, in my own biased opinion pretty good, guide using my own time, simply because knowing I did something good brings joy to my heart.
Click to expand...
Click to collapse
Thanks man, now that the 6.1 plus is coming soon I think we'll be able to put it on using this guide!
vostok_amphibia said:
I bought a Nokia X6 from China and the phone appears to be rooted. The play store app System info says that I have all the correct specs but also tells me the phone is rooted. Additionally, when booting my phone gives me a message that says: Your device has loaded a different operating system. I have pretty much no idea what to do and honestly just would want a normal stock phone so any help would be very much appreciated.
Click to expand...
Click to collapse
Same here, so anyone help us to solve this problem?
When I try to enable wifi (or bluetooth), it says 'Turning on...' underneath the icon but the process never succeeds.
Note:
-Under About > Status I see no MAC address for Wifi or Bluetooth.
-Phone is not rooted.
-Bootloader is unlocked.
-No custom recovery.
-Airplane mode is off.
-I am able to access the internet when I put in my SIM card and use my cellular data.
-EDIT: Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
-EDIT: I keep my SIM out of this phone (it's in my fully working phone). Can insert if need be.
My attempts to solve this issue (none have worked):
-I updated to OxygenOS 11.
-I booted into recovery and wiped everything, including cache. I also did a System Reset.
-I went to Settings > System > Reset Wifi, mobile and Bluetooth. I also did Erase all data (factory reset) in the same place.
Is there anything else left to try? Is there a way to flash the modem image maybe, I remember having to do that with my Nexus 4 many years ago.
Thanks!
A factory reset never finds the root cause. A virus or an old load are the only reasons to use it otherwise find the root cause. Usually a bad setting. If it's software caused the solution is right in front of you.
Network reset, worth a shot.
Clear system cache, can't hurt.
Clear data in sim card tool kit apk.
Both are probably redundant since you already did a hard reset, but try anyway.
Otherwise...
Bad sim card (try reseating it or replace otherwise) , corrupted firmware, or defective hardware.
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
dladz said:
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
Click to expand...
Click to collapse
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
bassamanator said:
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
Click to expand...
Click to collapse
Ah yea that's not good. 2025 AFAIK is global mainly sold in the US.
The MSM tool is in discussion I believe and it's a tool you use to restore your phone using EDL mode, to get to EDL.
Power off your phone.
Connect it to your computer (if it turns on again turn it back off)
Then open up the MSM tool and press and hold volume up and down
Your computer will recognise the the device and at this point you should start the process as it will try again to reboot shortly after without any input from you.
This is the thread you need.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Bare in mind this will relock your bootloader but it's easy to get that back unlocked.
Any questions regarding the tool just ask in the thread.
(you shouldn't need to providing you download the right one)
Download the latest firmware within the tool. If you get stuck don't just guess, ask someone.
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
bassamanator said:
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
Click to expand...
Click to collapse
But now you have bt?
blackhawk said:
But now you have bt?
Click to expand...
Click to collapse
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
bassamanator said:
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
Click to expand...
Click to collapse
How/when did it start? Anything happen to the phone?
bassamanator said:
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
Click to expand...
Click to collapse
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
blackhawk said:
How/when did it start? Anything happen to the phone?
Click to expand...
Click to collapse
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
bassamanator said:
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
Click to expand...
Click to collapse
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
dladz said:
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
EDIT: the phone has 2 IMEI numbers.
bassamanator said:
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
Click to expand...
Click to collapse
I've already posted in the MSM thread for you.
What about your fingerprint? Is that still working?
dladz said:
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
Click to expand...
Click to collapse
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
bassamanator said:
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
Click to expand...
Click to collapse
Yea for me it does, it shows there's a correlation between the persist problem and the EFS problem and a direct connection to your IMEI or Mac address issue.
With this in mind I would recommend the persist.img fix thread..
Getting that working may be key to solving the Mac / IMEI problem.
At this point nothing is going to hurt.
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
dladz said:
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
Click to expand...
Click to collapse
I was about to say, I want to try something along the lines of
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Click to expand...
Click to collapse
or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
bassamanator said:
I was about to say, I want to try something along the lines of or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
Click to expand...
Click to collapse
Ok don't do the EFS fix you do not have an EFS back up.
Give this a shot
go to data/misc/wifi (required root)
-backup file wpa_supplicant.conf in this folder which contains usename and password wifi
- delete all file in this folder
- turn on wifi ( if you careful, you can reboot )
- now you can connect to wifi
- recovery file wpa_supplicant.conf
This isn't my writing. The English is a little broken but you get the point