Develop Bugs

2016 version (new fingerprint scanner, combined sim/sd)

Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile

Nice! Can you provide a dump from /system and /boot maybe?

BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?

Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask

BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted

Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.

flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?

I will do
Edit: OK, see if there will be an answer.

Thank you flo1k!

I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?

ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)

FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising

Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished

FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?

Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....

FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.

The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.

I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work

These are great news!
"Which ones do you need?"
Probably all of them

Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!

Add L24 LTE bands to BND-L22 or BND-AL10?

Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!

rexian said:
Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!
Click to expand...
Click to collapse
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.

mrmazak said:
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.
Click to expand...
Click to collapse
Thanks mrmazak. Is this a viable option of getting L24 bands on AL10?

Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|

rexian said:
Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|
Click to expand...
Click to collapse
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.

mrmazak said:
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.
Click to expand...
Click to collapse
Thanks again, mrmazak. I saw your post in the other thread while searching but wasn't sure if there is more up to date information or an alternate tool.
Is it possible to just add certain bands to a model without removing existing bands? The only bands of interest are LTE 12 and 17 that are missing in this. The person doesn't really care about Oreo or Nougat - as long as it works with AT&T

Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.

I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.

rexian said:
Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.
Click to expand...
Click to collapse
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.

Klirensxp said:
I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.
Click to expand...
Click to collapse
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.

mrmazak said:
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.
Click to expand...
Click to collapse
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now

rexian said:
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now
Click to expand...
Click to collapse
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server

mrmazak said:
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server
Click to expand...
Click to collapse
Cool, done commenting #332. Also was able to root and make a copy of custom.bin / oeminfo.
Now, going to run the script :fingers-crossed:

Alright, an update - it went through lot of steps as expected (including installing oeminfo and unlocking the bootloader) but ended up with "software update failed" error on the phone. On command prompt here is the last few lines of the log -
Use the volume buttons to select YES and press the power button
...
(bootloader) The device will reboot and do factory reset...
OKAY [ 11.001s]
finished. total time: 11.001s
Wait for the device to boot into TWRP.
Press Enter to continue...
Wait for the files to load. Neither of which you do not need to press !!!.
Copying is in progress ....
[100%] /data/update/HWOTA/update.zip
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_data_public.zip': No such file or directory
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_all_hw.zip': No such file or directory
Copying recovery files, please be patient and wait....
[100%] /tmp/BND_RECOVERY_NoCheck.img
[100%] /tmp/BND_RECOVERY2_NoCheck.img
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.414091 seconds, 85.5MB/s
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.508804 seconds, 69.6MB/s
The system update should start automatically.
Press Enter to continue...
Click to expand...
Click to collapse
Error for update_data_public.zip was expected and on close inspection I noticed there was an extra '.' in the name of update_all_hw.zip. It was update_all_hw..zip.
So, fixed it and put the phone in fastboot mode and re-ran update.bat. It installed recovery and asked me to put into TWRP. I tried but it never went to TWRP started installing the previously copied ZIP files. It took a while but after it restarted, it went to straight to Android (YAY!). Went to Settings > About and say the model as BND-L24 and build number System 5.1.0.98(07DV).
So far it seemed everything was fine - then I inserted the FreedomPop SIM (uses AT&T towers), added the fp.com.attz APN and restarted it - AND the same issue, can't see the carriers and 0 bars
The oeminfo was definitely installed as I see a lot more options in "preferred network mode" but selecting Global or LTE or anything else does nothing...
Since I am not able to boot into TWRP, I wonder if that's causing an issue. Every attempt to boot into TWRP goes into a screen showing "installing update" with 5% status. It eventually (after 10 minutes or so) boots into Nougat.

Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...

rexian said:
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.
Click to expand...
Click to collapse
It’s just that the L21 is always 4G,and on the TL10 it goes to 3G,I switched from L21 to TL10 because of gestures, now I have 4G+ as well as on L21.

rexian said:
Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...
Click to expand...
Click to collapse
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.

mrmazak said:
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.
Click to expand...
Click to collapse
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?

rexian said:
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?
Click to expand...
Click to collapse
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175

mrmazak said:
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
Click to expand...
Click to collapse
I tried once more tonight but the same result - no service and carrier disabled.
mrmazak said:
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
Click to expand...
Click to collapse
There are 2 long numbers for the baseband - both start with 21C60B. Yes, both IMEIs show and are the same as before.
Yes, I always used the dedicated SIM slot as I have a micro-SD inserted for backup.
mrmazak said:
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175
Click to expand...
Click to collapse
I am inclining towards this as well - possibly missing hardware
Now, how do I get back to AL10C675 (don't see a Nougat option in FW Finder) and original radio? HWOTA doesn't have C675 as option, it has C00. I do have the original custom.bin and oeminfo but how do I create a zip to install with TWRP?

No Mobile Data on Treble Roms

I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.

Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie

Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?

sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks

Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.

Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance

Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot

Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom

Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??

Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??

I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.

Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.

I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know

hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks

Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.

not working, moist do you have rooted phone? because only on rooted phones you can do this trick

doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.

ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..

Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.

Restoring Serial Number - SN

Please read Bootloader Unlock and Root Instruction to understand how to work with Qfil.exe
1. Download Ftm - partition from phone. You can do it via Qfil.exe or Root
adb shell
su
dd if=/dev/block/bootdevice/by-name/ftm of=/sdcard/ftm.bin
2. You need to know your Serial Number so go imei24.com or imeipro.info and type yours IMEI.
3. Now open Ftm.bin with Hex.exe ( attached )
Then go Navigation -> Go to Offset... and type 73728
Type SN and save changes.
4. Flash it back in phone with Qfil.exe or copy ftm.bin to internal sdcard
adb shell
su
dd if=/sdcard/ftm.bin of=/dev/block/bootdevice/by-name/ftm
reboot
Done!

And if what I lost was my imei, can I recover it with this method?

IMEI recorded here twice: Offset 53248 and 14680132.
For restoring IMEI you need your backup efs

Thanks a lot for your instructions.
I've successfully restored my S/N on the V35AWM.
I updated my V35AWM to V35ULM last November, then I flashed the wrong firmware version in April 2020 when the newest firmware was released. After I resume the device, I found my S/N was lost but had no idea about how to get it restored.
But there was still a most difficult part in this instruction which is how to enter the 9008 mod, this cost me about 2 hours.
So everything is ready now only awaiting for the new Android 10 to release.

do you have video tutorials
do you have video tutorials?
SaiLas said:
Please read Bootloader Unlock and Root Instruction to understand how to work with Qfil.exe
1. Download Ftm - partition from phone. You can do it via Qfil.exe or Root
adb shell
su
dd if=/dev/block/bootdevice/by-name/ftm of=/sdcard/ftm.bin
2. You need to know your Serial Number so go imei24.com or imeipro.info and type yours IMEI.
3. Now open Ftm.bin with Hex.exe ( attached )
Then go Navigation -> Go to Offset... and type 73728
Type SN and save changes.
4. Flash it back in phone with Qfil.exe or copy ftm.bin to internal sdcard
adb shell
su
dd if=/sdcard/ftm.bin of=/dev/block/bootdevice/by-name/ftm
reboot
Done!
Click to expand...
Click to collapse

SaiLas said:
IMEI recorded here twice: Offset 53248 and 14680132.
For restoring IMEI you need your backup efs
Click to expand...
Click to collapse
Hy chazmatt. Is that possible to restore or change imei if forget to backup.

muzammil457 said:
Hy chazmatt. Is that possible to restore or change imei if forget to backup.
Click to expand...
Click to collapse
No, imei is gone. Now your phone is a tablet.

Kyrimeas said:
No, imei is gone. Now your phone is a tablet.
Click to expand...
Click to collapse
But in v30 there is a way to put imei no through service code *#546368#*933#. We can update imei no thorugh this. In v35 is there any option like this

muzammil457 said:
But in v30 there is a way to put imei no through service code *#546368#*933#. We can update imei no thorugh this. In v35 is there any option like this
Click to expand...
Click to collapse
There is. *#546368#*350#. But once you erased imei, this option gets blocked. Always imei will be 0.

Does missing serial number has anything to do with not being able to make phone calls?
I have a V35 unlocked version (pretty sure this is V350ULM), I flashed it with Korean Q and it worked fine while traveling in Korea. After coming back to U.S. I tried ATT based Tracfone SIM and data works fine but when I try to make calls it always immediately shows Call Ended. I notice the serial number is blank.

hp79 said:
Does missing serial number has anything to do with not being able to make phone calls?
I have a V35 unlocked version (pretty sure this is V350ULM), I flashed it with Korean Q and it worked fine while traveling in Korea. After coming back to U.S. I tried ATT based Tracfone SIM and data works fine but when I try to make calls it always immediately shows Call Ended. I notice the serial number is blank.
Click to expand...
Click to collapse
hp79 said:
Does missing serial number has anything to do with not being able to make phone calls?
I have a V35 unlocked version (pretty sure this is V350ULM), I flashed it with Korean Q and it worked fine while traveling in Korea. After coming back to U.S. I tried ATT based Tracfone SIM and data works fine but when I try to make calls it always immediately shows Call Ended. I notice the serial number is blank.
Click to expand...
Click to collapse
I've got a ULM with the A10 Korean rom. I have no issues making or receiving calls without a SN.

cmrntnnr said:
I've got a ULM with the A10 Korean rom. I have no issues making or receiving calls without a SN.
Click to expand...
Click to collapse
Is it possible for you to share some of your system partitions to get mine to work again? I'm not sure which partitions would be needed to get it back to working condition. I can get it to QFIL mode and flash some. I think this may have happened after some more flashing but not sure. My IMEI is still intact, serial number is blank.

It sounds like you are successfully rooted and on a Korean A10 rom. If you are unsure, follow clouds localize guide then flash the partition image in this post:
[Guide] Make the Korean Q Great Again [relocalise, volte, wowifi, debloat and more]
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign...
forum.xda-developers.com

It sounds like you are successfully rooted and on a Korean A10 rom. If you are unsure, follow clouds localize guide then flash the partition image in this post:
[Guide] Make the Korean Q Great Again [relocalise, volte, wowifi, debloat and more]
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign...
forum.xda-developers.com

No SIM recognition after OOS 10.0.1 update - EFS problem??

Hi,
I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full nandroid backup before.
Everything went fine until I noticed that during the booting of the phone after the flashing, it didn't ask for the SIM code as it used to. And once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network.
I tried switching Sim cards with another mpbile. My SIM worked fine in the other mobile and the other SIM was not recognized by my mobile.
I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done before. Nothing. Same thing with the modem partition. Nothing.
I tried then to restore the EFS from a safety backup that I had using Fastboot. Nothing.
I could still try to restore the full nandroid backup done at the beginning, but I forgot to take out pin protection code before taking the Nandroid, and I've read somewhere that it could be an issue after restoring the system. I might not be able to restart the phone and be obliged to factory reset, witch I would really like to avoid. And anyway, if restoring with Fastboot did not work, I wonder if the full restore would change anything.
Anyway, anybody has a magic idea about might be happening? A little help please??

Same problem!
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.

Working on this
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
rootlessabroad said:
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Click to expand...
Click to collapse

Hi
I've found a code (*#06#) in a page that gives you the MEID. It worked for me. Hopefully, I have the correct MEID too. The code for the IMEI did not show anything. I'll check the lynks you posted later today.
Thanks for sharing!!
PS. I can not include the lynk to codes page as I'm too junior a member and XDA forums won't let me.
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse

So I've tried te rebuild the QCN file. But my issue is that I can't make the ADB comunicate with my mobile. It is as the mobile was not plugged in?? The usb debugging is activated. I can browse the mobile memory from the computer. But the ADB doesn't lynk with the mobile; when you type adb devices, it says List of devices attached and nothing after. Any idea what might be happening?
What about you rootlessabroad? could you fix it?
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse