Related
Is there anyway I can get my IMEI back from my s5830 I managed with mt s5830i but things just arent the same?
Is there a way to get to my efs folder?
Please help ASAP
anyone help me
Sent from my GT-S5830i using xda premium
Follow..
1.You need to be on stock ROM
2.Phone has to be rooted
3.Dial *#7284# on phone's keypad
4.Click Qualcomm USB Settings
5.Select RMNET + DM + MODEM and click ok
6.Download QPST and install it QPST
7.Connect T999 to Windows PC with USB cable (make sure you have all Samsung drivers installed and working)
8. In Windows open Device Manager, go to Ports (COM&LPT) and look up what port your T999 is using
9.Open QPST Configuration program
10.Click Add new port
11. Enter port (for example "COM6") from step 8 to boxes "Port" and "Port Label"
12.Open QPST RF NV Item Manager program
13.From top menu click on Settings then Comport
14. In Comport Configuration window click on drop down menu and select your port from Step 8 then click OK
15. In RF NV Item Manager click on Read Supported NV RF Items (first toolbar button or select it from File menu on the top)
16. Below on left side go to line number 550 and click on it
17. On the right side, check box "Hex" this will display 9 boxes below where you enter your IMEI
18. You enter it in pairs of 2 digits and backwards
Example:
your IMEI is 353024052511214
8 (this number is not part of your IMEI but has to be entered)
3a (first digit of your IMEI ,"a" has to be there also)
35
20
04 (this can be written as just 4 also)
25
15
21
41
19. Click Write NV button
20.You can reboot and disconnect your phone now.
21. On your phone's keypad dial *#7284# go to settings and check MTP + ADB to go back to original state.
Or refer to this thread.
http://forum.xda-developers.com/showthread.php?t=1802024
Hi does this method work? I have tried QPST it read phone nv fine but when writing i get
Exception Thrown!! error
NvManager;;writeToPhonoe( const string comPort ) -
QpstServer;;sendSynclmpl - Error
Code = 80004005.
It seem like the phone is stopping the writing of the imei. Any ideas? Is this method confirmed working on s5830 not (i).
[email protected]
[email protected] said:
Hi does this method work? I have tried QPST it read phone nv fine but when writing i get
Exception Thrown!! error
NvManager;;writeToPhonoe( const string comPort ) -
QpstServer;;sendSynclmpl - Error
Code = 80004005.
It seem like the phone is stopping the writing of the imei. Any ideas? Is this method confirmed working on s5830 not (i).
[email protected]
Click to expand...
Click to collapse
I have the same problem with my S5830. Any solution?
hi I can't see the hidden menù after pressing the code in the dialpad, sorry for my bad english i'm Italian
I'm going to try and summarise the steps to play around with 3G and 4G bands on Samsung Galaxy S5 devices.
I didn't come to it on my own, all thanks and contributors are listed below.
Happy to close any gaps in the guide - just shout.
The process might help add extra 3G or 4G/LTE bands if the hardware of your device allows it.
So far there have been found a lot of limitations on Sammy devices so the success is by no means guaranteed.
Use everything at your own risk, I'm not going to be responsible for any damage to your phone as a result of you trying to follow the steps.
The steps worked for me, I was able to disable and then enable some GSM bands.
So if nothing else the guide should be useful for those who accidentally delete default bands on their phones.
Additional LTE bands have been successfully unlocked on some brands already.
Thanks for providing inspiration, guidance and working assumptions to following threads and folks:
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
@fffft
@olokos
@BlackSoulxxx
@Isriam
@dl12345
Original Quick Guide as compiled by @fffft quoted here:
The Mod:
Step by step guide
1. You need a phone with a Qualcomm processor that has been rooted.
2. If you need to root your phone, click on the button below for guidance. Otherwise skip to step 3.
3. If you are running a custom ROM and kernel that were compiled from source code, well done. Skip to Step 4.
Otherwise click on the button below for more information.
4. Download and install QPST. We will use this program to edit your phone settings. This runs best on Windows XP. But you can use Windows 7 (and probably Win 8, if you must). Right click on setup.exe (not the .msi file) and choose run as adminstrator.
5. Download and install QXDM. We will use this program to "write enable" your phone settings. QXDM won't work unless QPST is also installed, so you need both programs. Right click on setup.exe and choose run as administrator to install.
6. Open the USB settings screen on your phone. Change USB from AP to CP. And USB settings from MTP + ADB to RNDIS + DM + Modem mode (after you have finished making edits in your phone's memory, remember to revert the original settings in this screen).
This is the hardest part of this mod as the USB setting menu is usually hidden and the method to access it is slightly different on some brands. For the S5, you can open it by dialing *#0808# . Other phones may use *#7284# , *#8778# , *#*#8778#*#* , ##3424# or something else entirely. If those codes don't work on your phone, try a Google search for keywords like those below to find out how to open the USB settings menu for your phone:
Google: USB settings xda
Google: how to use QPST xda
6a. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
For Sony, the following CLI commands have been reported to work. These may or may not work for other brands.
You can enter these using a terminal emulator app or from an adb shell.
From terminal emulator:
Code:
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable
Or using adb:
Code:
adb start-server
adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable
exit
If you use either of these, remember to revert the USB settings after you finish your phone edits. e.g.
Code:
su
setprop persist.usb.eng 0
setprop usb.rndis.enable 0
echo 0 > /sys/class/usb_composite/modem/enable
6b. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an LGE phone, try the dialer codes here and change the USB mode from AP to CP (Modem mode). If that doesn't work, then it has been reported that the following commands will also enable diagnostic mode for you:
Code:
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
6c. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an HTC phone, this diagnostic driver may work for your phone.
6d. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an Opo phone, it been reported that the following commands will enable diagnostic mode for your phone.
Code:
su
setprop sys.usb.config diag,adb
6e. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have a custom kernel installed (which has permissive permissions) then you can probably enable diagnostic USB mode from the EFS Professional program menu.
6f. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you cannot find out how to access the USB settings on your phone anywhere, you may be able to force diagnostic mode by installing the Windows USB drivers for your phone in advance. You can download Motorola /Sony/ LG/ HTC/ ASUS/ Huawei /Google, etc drivers here. Otherwise do a Google /XDA search to find USB drivers for your phone. Install the USB driver.
7. Enable USB debugging on your phone. This is a hidden menu. Look for Settings menu > System > About Device > Developer. If you don't see a Developer option, then tap on the firmware build number about ten times to unhide it.
8. Connect your phone to your phone to an USB port on your PC. Do not use an USB hub, connect directly to your computer. Windows will install a diagnostic driver.
9. Open the Windows (Control panel) Device Manager and confirm that you see something like "Samsung Mobile USB Serial Port" listed there. If you see a yellow triangle there > right click and update the driver.
10. Open the "QPST Configuration" program > Ports > Add new port > choose the port labeled diagnostic > OK.
If you do not see a diagnostic port listed and you were not able to explictly able to set USB diagnostic mode earlier, then right click on the driver that Windows has assigned to your phone in the Windows (Control panel) Device Manager > Update Driver Software > Browse. Choose the folder where you extracted the USB driver that you downloaded for your phone. This forces Windows to use the downloaded driver.
11. Now select the QPST Start Clients > Software download > Backup > Start. This saves a backup copy of your phone's stock NV memory to your computer in case you need it later.
12. Navigate to the C:/Program Files/Qualcomm/QPST/bin folder.
13. Right click on ServiceProg.exe > run as administrator.
14. Choose Phone > Read from phone > UMTS System. This will show which 3G bands are currently enabled. Add checkmarks to the additional 3G bands that you would like to add. Resist the temptation to check everything unless you are prepared to troubleshoot possible issues with non-existant bands, slow boot times and other issues. Just add specific bands that you need for another carrier or are missing in the areas you travel. If you aren't sure what to add, then don't check any extra bands for now - you can always come back later after you find out which 3G bands you can actually make use of.
Either way, do not click write to phone yet. And do not close the Service Programming window either.
15. Before we write anything to your phone, we need to write enable the locations we are going to edit. Navigate to the C:/Program Files/Qualcomm/QXDM/bin folder.
16. Right click on QXDM.exe > run as administrator. If you are not adding any new 3G bands at this time, skip to step 21.
17. In the NV Browser window, scroll down to ID 01877 (aka NV 1877) > Read.
Then write "0" to NV 01877 with QXDM. This initializes (write enables) the item for QPST. We need to do the same for several more NV items.
18. Select ID 00441 > Read. > Write "0" to NV 00441 with QXDM. This initializes (write enables) the item for QPST.
19. Select ID 00946 > Read. > Write "0" to NV 00946 with QXDM. This initializes (write enables) the item for QPST.
20. Select ID 02954 > Read. > Write "0" to NV 02954 with QXDM. This initializes (write enables) the item for QPST.
21. If you do not intend to add any new LTE bands, skip to step 24. Otherwise,
Select ID 06828 > Read. > Write "0" to NV 06828 with QXDM. This initializes (write enables) the item for QPST.
22. Select ID 06829 > Read. > Write "0" to NV 06829 with QXDM. This initializes (write enables) the item for QPST.
23. If you wish to add LTE bands and have already calculated a custom value from the instructions in the thread, then use QXDM to write that value to both ID 06829 and ID 06829, writing one item at a time.
Otherwise, write (decimal) "17592185995263" to both ID 06828 and ID 06829, writing one item at a time. This will enable all LTE bands.
Note that LTE edits will only work if your firmware has an LTE modem. If you already have at least one LTE band active, then you are OK. If your current firmware is from a carrier that does not use LTE at all, then you'll also need to update your modem to an LTE capable version as well.
24. Now go back to the Service Programming window that you left open. If you added any new 3G bands, click on write to phone to write the current selection of 3G bands to your phone. Otherwise do not click write, simply continue on to the next step.
25. You are now finished editing the NV values in your phone.
26. Reboot your phone.
27 In the Service Programming screen, choose Phone > Read from phone > UMTS System to confirm that your new 3G band selection are persistent. If they revert and you don't have a custom kernel installed, this confirms that you will need a custom kernel for this mod to work.
28. In the QXDM NV Browser screen, scroll down to ID 06828 > Read. Note the value.
29. In the QXDM NV Browser screen, scroll down to ID 06829 > Read. Note the value.
ID 06828 and ID 06829 should both show the custom value that you wrote. i.e. "17592185995263" (or hex "0xFFFFFFF3FFF") or the custom value, if you had used one.
30. Remember to change your USB settings back to normal mode, e.g. on the S5, dial *#0808# again and choose USB = AP and USB Settings = MTP + ADB > Click OK.
31. Celebrate! And let us know about your success (or sticking points).
32. You can test your results by checking whether your phone uses the new bands when you roam onto other systems that use them. Or if you have a SIM card for an alternate carrier. To tell if your phone is using the new bands, you can look at the current band being used in the Service menu or with various apps, e.g. LTE Discovery.
Your device should be rooted.
1. Enter into diag mode from *#0808# dial pad command. If a direct dial doesn't get you to the menu then use any Secret Code explorer app from Google Market, e.g. Phone Info Samsung by @vndnguyen.
AP
RMDIS + DM + MODEM
2. Enter into USB debug mode,
3. In Terminal Emulator ran
su
setenforce 0
4. Connect to PC
5. In device manager enable hidden devices.
You should see your Sammy in ports like COMxx
6. Run QPST
7. In QPST, add the COM port where you see your device. If one port won't work, try the next one.
Now you should be able to run NV manager or QXDM.
NV values responsible for GSM are 00441, 00946, 02954 and 01877
NV values responsible for LTE bands are 06828 and 06829.
The correct values that you would write in these NV can be derived by using Qualcomm NV Calculator app by @vndnguyen.
Further details on the values are in this thread http://forum.xda-developers.com/andr...lcomm-t2950491 courtesy of @yakapa40
---------------
Another important aspect of controlling the phone network behaviour is through the hidden menu.
Use with extreme care & do this at your own risk.
Here's how you can check you existing LTE bands:
Open the dial pad
Type: *#0011# to enter Service Mode (Be very careful with what you do here)
Note: You need to be rooted for this to work
Once in Service Mode, do the following:
Tap the menu button and tap Back
Tap the menu button again and select "Key Input" and enter an upper case Q and press OK
Tap the menu button again and select "Key Input" and enter 4 zeroes (0000) and press OK
Wait 5 - 15 seconds. You'll see the Main Menu
Choose option [2]: UE SETTING & INFO
Choose option [1]: SETTING
Choose option [1]: PROTOCOL
Choose option [2]: NAS
Choose option [1]: NETWORK CONTROL
Choose option [4]: BAND SELECTION
Choose option [4]: LTE Band Preference
Choose option [7]: LTE ALL (Or you can choose any band instead)
If you want to go back then tap the menu button and choose Back (Don't press the back key)
Press the back key to exit
seems most have lost interest because its not capabile with the basic instructions provided previously. good luck though, let me know if you ever need a g900f nv list.
Isriam said:
seems most have lost interest because its not capabile with the basic instructions provided previously. good luck though, let me know if you ever need a g900f nv list.
Click to expand...
Click to collapse
True. Just hoping one day someone with specific knowledge will be able to move it forward.
My motivation for reviving the topic was as someone destroyed their LTE bands through service menu and I believe our method can help restore it.
3rd time lucky for this topic
Just dont let ffff spoil it again.
juDGEY2k10 said:
3rd time lucky for this topic
Just dont let ffff spoil it again.
Click to expand...
Click to collapse
Far from that. Need to get it in motion first
@Hongdae since the latest samsung rom update I also reach *#0808# through hidden menu app only, not via dial pad.
I'll update the OP accordingly.
I had the issue of QPST connection dropping but was able to reestablishe after several attempts.
Try to launch nv manager, you should be able to select the 3g bands from the check boxes without the need of edit nv values manually.
Also check if your phone shows a valid IMEI number that also equals the one printed on the back of your device.
botwa2000 said:
@Hongdae since the latest samsung rom update I also reach *#0808# through hidden menu app only, not via dial pad.
I'll update the OP accordingly.
I had the issue of QPST connection dropping but was able to reestablishe after several attempts.
Try to launch nv manager, you should be able to select the 3g bands from the check boxes without the need of edit nv values manually.
Also check if your phone shows a valid IMEI number that also equals the one printed on the back of your device.
Click to expand...
Click to collapse
Okay. Yeah the IMEI is the same as the one printed on the back, so I guess it is valid. By now I'm trying to fix the QPST connection but it is not working yet.
Maybe KIES recovery could fix my phone, but I think this problem comes from EFS folder and I don't know if KIES reinstalls that content.
Hongdae said:
Okay. Yeah the IMEI is the same as the one printed on the back, so I guess it is valid. By now I'm trying to fix the QPST connection but it is not working yet.
Maybe KIES recovery could fix my phone, but I think this problem comes from EFS folder and I don't know if KIES reinstalls that content.
Click to expand...
Click to collapse
Yeah maybe a good idea to do a full format and then use kies recovery.
I can upload my EFS folder backup for you if you want to check against your existing folder and see if there're any major differences.
Though mine is a G906K model if it makes any difference.
....
botwa2000 said:
Yeah maybe a good idea to do a full format and then use kies recovery.
I can upload my EFS folder backup for you if you want to check against your existing folder and see if there're any major differences.
Though mine is a G906K model if it makes any difference.
Click to expand...
Click to collapse
That would be awesome, thanks! I made a backup of my NV values with QPST but the restore is not working, so I have no backup of mine.
Actually, what I modified are these values, following the procedure on:
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
17. In the NV Browser window, scroll down to ID 01877 (aka NV 1877) > Read.
Then write "0" to NV 01877 with QXDM. This initializes (write enables) the item for QPST. We need to do the same for several more NV items.
18. Select ID 00441 > Read. > Write "0" to NV 00441 with QXDM. This initializes (write enables) the item for QPST.
19. Select ID 00946 > Read. > Write "0" to NV 00946 with QXDM. This initializes (write enables) the item for QPST.
20. Select ID 02954 > Read. > Write "0" to NV 02954 with QXDM. This initializes (write enables) the item for QPST.
21. If you do not intend to add any new LTE bands, skip to step 24. Otherwise,
Select ID 06828 > Read. > Write "0" to NV 06828 with QXDM. This initializes (write enables) the item for QPST.
22. Select ID 06829 > Read. > Write "0" to NV 06829 with QXDM. This initializes (write enables) the item for QPST.
23. If you wish to add LTE bands and have already calculated a custom value from the instructions in the thread, then use QXDM to write that value to both ID 06829 and ID 06829, writing one item at a time.
Otherwise, write (decimal) "17592185995263" to both ID 06828 and ID 06829, writing one item at a time. This will enable all LTE bands.
Maybe I made a mistake when changing them.
Hongdae said:
That would be awesome, thanks! I made a backup of my NV values with QPST but the restore is not working, so I have no backup of mine.
Actually, what I modified are these values, following the procedure on:
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
17. In the NV Browser window, scroll down to ID 01877 (aka NV 1877) > Read.
Then write "0" to NV 01877 with QXDM. This initializes (write enables) the item for QPST. We need to do the same for several more NV items.
18. Select ID 00441 > Read. > Write "0" to NV 00441 with QXDM. This initializes (write enables) the item for QPST.
19. Select ID 00946 > Read. > Write "0" to NV 00946 with QXDM. This initializes (write enables) the item for QPST.
20. Select ID 02954 > Read. > Write "0" to NV 02954 with QXDM. This initializes (write enables) the item for QPST.
21. If you do not intend to add any new LTE bands, skip to step 24. Otherwise,
Select ID 06828 > Read. > Write "0" to NV 06828 with QXDM. This initializes (write enables) the item for QPST.
22. Select ID 06829 > Read. > Write "0" to NV 06829 with QXDM. This initializes (write enables) the item for QPST.
23. If you wish to add LTE bands and have already calculated a custom value from the instructions in the thread, then use QXDM to write that value to both ID 06829 and ID 06829, writing one item at a time.
Otherwise, write (decimal) "17592185995263" to both ID 06828 and ID 06829, writing one item at a time. This will enable all LTE bands.
Maybe I made a mistake when changing them.
Click to expand...
Click to collapse
Yep same happened to me! I guess editing values other than 1877, 6828 and 6829 is what killed GSM for me. That's why I haven't even quoted these steps in my guide.
I guess editing the three NV values above is safe as you can change them any time.
In terms of deriving the right decimal value you should use QualComm NV Calculator app by @vndnguyen from Google Market - it proved to be accurate.
PM me your details I'll send you my EFS backup.
botwa2000 said:
Yep same happened to me! I guess editing values other than 1877, 6828 and 6829 is what killed GSM for me. That's why I haven't even quoted these steps in my guide.
I guess editing the three NV values above is safe as you can change them any time.
In terms of deriving the right decimal value you should use QualComm NV Calculator app by @vndnguyen from Google Market - it proved to be accurate.
PM me your details I'll send you my EFS backup.
Click to expand...
Click to collapse
Sent! How did you manage to fix the QPST connection? Still dropping
Hongdae said:
Sent! How did you manage to fix the QPST connection? Still dropping
Click to expand...
Click to collapse
I did a clean install of the stock firmware.
My QPST connection wasn't completely dead but dropped every few seconds or so.
I was able to open NV Manager, select all GSM bands and write to the phone within a couple of seconds. The connection dropped before the write operation was finished but I managed to get the network back.
Afterwards I got QPST connection back normally.
botwa2000 said:
I did a clean install of the stock firmware.
My QPST connection wasn't completely dead but dropped every few seconds or so.
I was able to open NV Manager, select all GSM bands and write to the phone within a couple of seconds. The connection dropped before the write operation was finished but I managed to get the network back.
Afterwards I got QPST connection back normally.
Click to expand...
Click to collapse
Okay. The same happened and now connection is working fine. Just one more question, in order to edit the NV values I have opened QXDM, then NV Browser. Now I have the following values from the calculator:
NV 1877: 844, 425, 062, 777, 216
How do I input this?
Hongdae said:
Okay. The same happened and now connection is working fine. Just one more question, in order to edit the NV values I have opened QXDM, then NV Browser. Now I have the following values from the calculator:
NV 1877: 844, 425, 062, 777, 216
How do I input this?
Click to expand...
Click to collapse
I'm not sure I understand how you got to these values...
For starters I suggest you check all your phone's default bands and calculate the decimal value. You should use it without commas.
In my first post in this thread I included the original guide on how to edit the NV values with QXDM.
Read the current value from 1877, what does it say?
BTW if you find any of my posts useful feel free to hit 'Thanks' button
botwa2000 said:
I'm not sure I understand how you got to these values...
For starters I suggest you check all your phone's default bands and calculate the decimal value. You should use it without commas.
In my first post in this thread I included the original guide on how to edit the NV values with QXDM.
Read the current value from 1877, what does it say?
BTW if you find any of my posts useful feel free to hit 'Thanks' button
Click to expand...
Click to collapse
Yeah you are right, I am a total rookie here. If I read 1877 it it shows 0, but now I have written 422212531388608. I have selected "Use QXDM Notation" on the NV calculator, I guess that should be correct.
However, the calculator gives 192 for NV 0441 and when I write it it says: Parameter Bad. I have 0 on nam and 0xFFFF on band when I read it
Hongdae said:
Yeah you are right, I am a total rookie here. If I read 1877 it it shows 0, but now I have written 422212531388608. I have selected "Use QXDM Notation" on the NV calculator, I guess that should be correct.
However, the calculator gives 192 for NV 0441 and when I write it it says: Parameter Bad. I have 0 on nam and 0xFFFF on band when I read it
Click to expand...
Click to collapse
Looks like by now you should have your 3G connection back I hope
Do you also have your LTE back?
I believe only NV 6828 and 6829 are relevant for LTE.
What values do you read in those?
botwa2000 said:
Looks like by now you should have your 3G connection back I hope
Do you also have your LTE back?
I believe only NV 6828 and 6829 are relevant for LTE.
What values do you read in those?
Click to expand...
Click to collapse
I have nothing back, still no signal. No GSM, 3G or LTE. I can't write on NV 0441, 0946, 2954 values...
Hongdae said:
I have nothing back, still no signal. No GSM, 3G or LTE. I can't write on NV 0441, 0946, 2954 values...
Click to expand...
Click to collapse
Hmm. At this point I had my connection back after reboot.
As I said I haven't touched 0441, 0946 or 2954 lines.
Here is my entire NV dump shortly - you can have a look vs. your values
http://forum.xda-developers.com/showthread.php?p=56215728
So just brainstorming now.
Did you activate all possible gsm bands in NV manager and was able to write to your phone?
Are your APN settings intakt?
botwa2000 said:
Hmm. At this point I had my connection back after reboot.
As I said I haven't touched 0441, 0946 or 2954 lines.
Here is my entire NV dump shortly - you can have a look vs. your values
http://forum.xda-developers.com/showthread.php?p=56215728
So just brainstorming now.
Did you activate all possible gsm bands in NV manager and was able to write to your phone?
Are your APN settings intakt?
Click to expand...
Click to collapse
My APN is fine yeah.
All 0441, 0946 and 2954 show 0 when I read from phone. If I write the values from the NV calculator on QXDM it says error, parameter bad.
By NV manager do you mean QPST Service Programming / UMTS System?
This is what I have when I click on Read from phone:
hey everyone,
I'm looking for an answer to CA issues(LTE plus/4G+) on another device and I want to check out op3t qcn file for LTE configs. if you could upload your phone's qcn file,It would be a big help. I just want to check nvids related to LTE.
also please state your device model and if you have LTE Plus on your phone carrier.
note : if you're concerned about your phone's IMEI, please google "how to change IMEI", you will use a hex editor tool to change it or you could simply use qualcomm's qrct software to export only nvids related to LTE by simply opening your qcn on qrci software, type LTE in Filter field, hit Enter key on your keyboard, select all of them by using your mouse, then select write all to> qcn. it will export it.
this is my thread regarding the issue that I'm looking into :
https://forum.xda-developers.com/redmi-note-3/help/carrier-aggregation-issue-xiaomi-phones-t3624585
this is the guide for creating qcn file from your device :
1. Opening DIAG - Assuming you got your phone rooted, run this command from ADB
adb shell
su
setprop sys.usb.config diag,adb
2. Now your devices wil either detected as unknown device (or Qualcomm Diag Port/USB Modem if you already have the diag driver) on Device Manager
3. Install the driver from requirement list number one, and you will have "HTC USB Modem" listed in your device manager (skip this step, if you already have your own qualcomm usb diag driver installed)-(remember to disable signature enforcement if you use WIN8/10)
4. Now fire up QPST and go to "Port" tab, and choose "Add New Port" ,
5. On "Serial/USB Port" tab, unchecked the option of "Show Serial & USB...bl bla bla" option, you will see your phone listed there as a "COM#" (# is a number depending on your PC) choose it, and click "OK"
6. Now choose "Start Clients" from the Menu tab above, and choose "Software Download"
7. Airplane Mode your Phone
8. Choose "Backup" Tab, and click browse for QCN file, select ".qcn" from save as type, type name of the file and click save then click start.
https://forum.xda-developers.com/oneplus-3/how-to/guide-unlock-additional-lte-bands-t3519563
Do not upload this file. It contains the content of the EFS partition including the IMEI's of your phone...
virusmoere said:
Do not upload this file. It contains the content of the EFS partition including the IMEI's of your phone...
Click to expand...
Click to collapse
you could simply change it via hex editor! or you could export only nvids related to lte via qrct.
You have some QCNs here:
https://forum.xda-developers.com/oneplus-3/how-to/guide-unlock-additional-lte-bands-t3519563
BTslo said:
You have some QCNs here:
https://forum.xda-developers.com/oneplus-3/how-to/guide-unlock-additional-lte-bands-t3519563
Click to expand...
Click to collapse
yeah,you're right. thanks. I just quickly read it and thought it's only got the modifications.
Welcome to my first thread!
Many of you are wondering how to get the One UI Beta for the Verizon Samsung Galaxy S9 (SM-G960U).
I will try my best to answer on how to get the One UI Beta for the Verizon Samsung Galaxy S9 (SM-G960U).
Remember, this is a Qualcomm variant of the Samsung Galaxy S9.
Your phone will not be bricked in any sort of way unless you are on a different device. This has been tested on a Verizon Samsung Galaxy S9 Qualcomm variant and it should work on those devices respectively.
This guide is for Windows-based OSes!
The steps will be listed down below:
1. Download the latest unlocked firmware from Updato.
- Link: https://updato.com/firmware-archive-select-model?record=8AC04973FA8A11E89F15FA163EE8F90B
2. Download the latest patched ODIN.
- Link: https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501
3. Download the latest Samsung USB drivers.
- Link: https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
4. Download the latest Platform Tools.
- Link: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
5. Unzip all the files into different folders.
6. Install the Samsung USB drivers onto your computer.
7. Restart your computer.
8. Turn on your phone.
9. Go to "About phone" > "Build number" and tap on it until the toast message says, "Developer mode has been turned on".
10. Go back.
11. Press on "Developer options".
12. Look for "USB debugging" and toggle it on.
13. Go back to your computer.
14. Go to your Platform Tools folder you have unzipped from step 5.
15. While you are in it and you can see some .exe files such as adb.exe, press Shift + Right mouse click.
16. You will be able to see "Open PowerShell window here".
17. Press on that.
18. PowerShell will open up.
19. Type in PowerShell, "cmd".
20. Plug in your phone to your computer.
21. Type in that PowerShell window, which now has cmd, "adb devices".
22. Unlock your phone.
23. You will see that your phone asks you, "Allow USB debugging?"
24. Press "OK"
25. Type in that PowerShell window, "adb reboot bootloader"
26. Your phone will go to Download mode now.
27. Go locate the ODIN .exe file.
28. Open it up
29. Locate the BL file for the file that starts with "BL_..."
30. Locate the AP file for the file that starts with "AP_..."
31. Locate the CP file for the file that starts with "CP_..."
32. Locate the CSC file for the file that starts with "HOME_CSC_..."
33. Press "Start" after all that is done (Make sure that in the "Log" section, it says something like "Added!").
34. Take a short coffee break.
35. You should be back on your phone with no information lost.
36. Back up all your information to the Cloud if you want or your SD card.
37. Perform a reset on the device by going to "General management" > "Reset" > "Factory data reset".
38. After the reset, you should set up all your settings, etc.
39. Download the Samsung+ application from Google Play Store (Try to join the Beta program if possible, you just have to scroll down on the application information).
40. Open up Samsung+
41. Sign in with your Samsung account.
42. Grant all permissions.
43. You should see the "Join One UI Beta program" banner or something like that.
44. Wait some time after registering and you should get the update.
45. Manually check for updates in Settings.
46. You're done!
Note:
It took me more than 2 weeks for me to get the update. You should be on the unlocked firmware for your Verizon Samsung Galaxy S9 Qualcomm variant. The reason why it takes so long is because the program is first-come-first-serve and they usually release the updates in batches...
These are the explanations for some of the steps:
1. You will need to download the latest unlocked firmware (SM-G960U1 XAA) because none of the other firmwares will work, as far as I know.
2. You will need to download the latest patched ODIN because none of the older ODIN applications will work with the Samsung Galaxy S9. I really don't know what the differences are, but it just works (I'm still a newb).
3. You will need to download the latest Samsung USB drivers because that's how your computer reads your phone. Without this, it will be harder for your computer to read the device and use adb. Also, without the Samsung USB drivers, you will not be able to see your device added in ODIN.
4. You will need to download the latest Platform Tools because you need to be able to use adb in order to boot your device from the actual Android OS to your bootloader.
Hope you liked this tutorial! If you are still confused on steps, I can definitely help you! If it's a question a lot of people are asking, I can always update the thread with the most asked question.
Good luck!
Reserved
Reserved 1
NOTE - THIS GUIDE IS ONLY FOR THE REALME GT NEO 2T (RMX3357)
For the X7 Max or GT Neo/GT Neo Flash Edition, please refer to the excellent guide by @mahotlov found here.
(The X7 Max subforum seemed the best place for this guide, but please let me know if there's a better place!)
------------------------------------------------------------------------------------------------------------------Preamble: I recently purchased a Realme GT Neo 2T under the assumption it could take Realme X7 Max ROMs. The specs and design were an exact match, and since Realme has a history of releasing existing phones with new model numbers and sparklier plastic, I felt pretty good about compatibility. I quickly learned I was mistaken - both stock and custom ROMs for the X7 Max cause the display on the Neo 2T to stop working. Flashing back the stock bootloader fixed the display, but the phone would only boot into recovery, which had no touch support. Flashing the stock recovery brought back touch support, but nothing I tried could get the ROM to boot. Clearly there are changes under the hood.
Unfortunately, that left precious few options for turning the Neo 2T into a usable phone. The hardware is amazing for the price, and ColorOS is pretty decent, but the amount of non-removable bloatware and lack of Android Auto and Hey Google to activate Google Assistant was a dealbreaker for me. In the end, I decided to take matters into my own hands.
------------------------------------------------------------------------------------------------------------------
This guide will show you how to:
- Unlock your bootloader.
- Root your phone. (Magisk)
- Bypass SafetyNet. (Universal SafetyNet Fix Magisk module)
- Install Android Auto and Google apps as system apps. (BusyBox-NDK and Terminal Systemizer Magisk modules)
- Remove Realme bloatware. (ADB)
- Flash device with SP Tools and stock ROM to recover from a softbrick or restore to factory state. (SP Tools)
(Some sections are still being written and will be available soon.)
------------------------------------------------------------------------------------------------------------------
THE GUIDE ASSUMES YOU ARE USING WINDOWS 10. SOME STEPS MAY BE DIFFERENT FOR OTHER OPERATING SYSTEMS
PLEASE READ THROUGH ALL INSTRUCTIONS FIRST BEFORE PROCEEDING. ALL REQUIRED FILES CAN BE FOUND ATTACHED TO THIS POST.
UNLOCKING YOUR BOOTLOADER WILL VOID YOUR WARRANTY. THIS PROCESS WILL WIPE ALL DATA FROM YOUR PHONE. I AM NOT RESPONSIBLE FOR LOST DATA. I AM ALSO NOT RESPONSIBLE IF YOU DAMAGE OR KILL YOUR DEVICE, YOUR PROPERTY, YOUR LOVED ONES OR YOURSELF BY FOLLOWING THESE INSTRUCTIONS. YOU HAVE BEEN WARNED!
------------------------------------------------------------------------------------------------------------------
STEP 1: Unlock your bootloader.
Spoiler: Click here for instructions.
First, we need to enable developer mode. On the Neo 2T:
- Open Settings.
- Choose "About Phone".
- Choose "Version - Baseband & Kernel"
- Tap "Build Number" until developer mode is enabled.
Next, we need to turn on USB Debugging and allow OEM Unlock. On the Neo 2T:
- Go back to Settings.
- Choose "Additional Settings".
- Choose "Developer Options".
- Turn on "OEM Unlock" and "USB Debugging".
We need to get the Deep Testing app to unlock the bootloader. On your PC:
- Download "DeepTesting_GT_NEO_2T.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "DeepTesting_GT_NEO_2T.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to request unlocking of the bootloader. On the Neo 2T:
- Open the "File Manager" app.
- Choose the "APK" option.
- Find "DeepTesting_GT_NEO_2T.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
- Click "Start Applying".
- Tick the checkbox to agree to the disclaimer. Due to a bug, the disclaimer text itself may or may not appear.
- When you see "Application Submitted", click "Back."
- Go grab a coffee. It can sometimes take up to an hour for the bootloader unlock request to be approved.
- You can close the app and use your phone as normal in the meantime. Periodically open the app and click "Query Verification Status" to check your request. Once you see "Application Approved" we are done with this step.
- Unplug the Neo 2T from your PC.
- Click "Start Deep Testing".
- The Neo 2T will reboot into "Fastboot" mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
Now we need to install the ADB drivers. On your PC:
- Download "ADB_DRIVERS.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Right-click on your start menu button and choose "Device Manager".
- Find the device called "Android".
- Right-click the device and choose "Update Driver".
- Choose "Browse My Computer for Drivers".
- Choose "Let Me Pick From a List of Available Drivers On My Computer".
- Click "Have Disk".
- Click "Browse".
- Navigate to the folder where you extracted the files.
- Choose "android_winusb.inf".
- Choose "Android Bootloader Interface".
- Click "Finish" to close the driver wizard once it has finished.
We need to use Fastboot to unlock the bootloader. On your PC:
- Download "ADB_FASTBOOT.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flashing unlock
Your phone will now ask you to confirm unlocking of the bootloader. On the Neo 2T:
- REMINDER: THIS WILL WIPE ALL YOUR DATA!
- Read the text on the screen and follow the instructions to confirm the bootloader unlock.
Next we reboot the phone. On your PC:
- Enter this command: fastboot.exe reboot
- Your phone will now warn you during boot that the bootloader is unlocked.
- Unplug the Neo 2T from your PC.
Now we need to enter Fastboot again. On the Neo 2T:
- Allow the phone to fully boot to the initial setup wizard.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We will use Fastboot to get into recovery mode. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe reboot recovery
- Wait for phone to reboot into recovery
Finally, we will wipe the data partition to ensure a clean state for future steps. On the Neo 2T:
- Select your language.
- Select "Wipe data".
- Select "Format data".
- Enter the code displayed on the screen.
- Select "Format".
- Data will be wiped. Select "OK" when finished. Phone will reboot.
- Once the phone has booted, proceed through the first time setup until you reach the home screen.
- Setup WiFi or verify/configure a data connection which will be needed for the next steps.
- If still plugged into your PC, or upon the next connection, the phone will show a popup to allow USB debugging. Check "always allow from this computer" and select OK.
- We can now move on to rooting!
STEP 2: Root your phone.
Spoiler: Click here for instructions.
First we need to reboot the phone into fastboot. On the Neo 2T:
- Unplug the Neo 2T from your PC.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We need to use Fastboot to root the phone. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flash boot magisk.img
- Enter this command: fastboot.exe flash vbmeta --disable-verity --disable-verification vbmeta.img
- Enter this command: fastboot.exe reboot
- Wait for phone to reboot.
Complete Magisk setup. On the Neo 2T:
- Open Magisk from your app drawer.
- Accept the request to install the full version of Magisk.
- Allow Magisk to install apps in the resulting popup.
- Open Magisk from your app drawer.
- Accept the request to reboot to complete installation.
- Once the phone has rebooted, the process is complete and we can move on to bypassing SafetyNet!
STEP 3: Bypass SafetyNet.
Spoiler: Click here for instructions.
First we grab the SafetyNet module for Magisk. On your PC:
- Download "safetynet-fix-v2.2.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "safetynet-fix-v2.2.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the module. On the Neo 2T:
- Open the "Magisk" app.
- Open Settings.
- Turn on "Zygist (Beta)" and "Enforce DenyList".
- Exit settings.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "safetynet-fix-v2.2.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button that appears to reboot the phone.
- Once the phone has rebooted, the process is complete and we can move on to installing Android Auto and Google apps as system apps!
STEP 4: Install Android Auto and and Google apps as system apps.
Spoiler: Click here for instructions.
First we grab the BusyBox-NDK and Terminal Systemizer modules for Magisk. On your PC:
- Download "busybox-v1.34.1.zip" attached to this post.
- Download "terminal_systemizer_v17.4.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apks to the Neo 2T. On your PC:
- Copy the "busybox-v1.34.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
- Copy the "terminal_systemizer_v17.4.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the BusyBox-NDK module. On the Neo 2T:
- Open the "Magisk" app.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "busybox-v1.34.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the back button.
We're ready to install the Terminal Systemizer module. On the Neo 2T:
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "terminal_systemizer_v17.4.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button to reboot the phone.
Time to get the Google Play Store app. On your PC:
- Download "Google_Play_Store_29.9.16-21.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "Google_Play_Store_29.9.16-21.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the Google Play Store. On the Neo 2T:
- Open the "Files" app.
- Choose the "APK" option.
- Find "Google_Play_Store_29.9.16-21.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
We need to install our apps before we can systemize them. On the Neo 2T:
- Open the Google Play Store and sign in.
- Update any apps that have updates available.
- Use the Google Play Store to install Android Auto, Google Assistant, and the Google app.
We need to use ADB to systemize Android Auto and Google Assistant. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Have your phone unlocked and at the ready, then enter this command: su
Allow root for ADB Shell. On the Neo 2T:
- Select "Forever" on the superuser request popup for Shell. Click "Grant".
Now we can systemize Android Auto and Google. On your PC:
- Enter this command: systemize
- Type 1 and hit enter to choose "Systemize Installed Apps (Listed)".
- You should see a numbered list of apps after a few seconds of loading. Find the numbers for "Android Auto" and "Google" and type them with a space in between. For example, if you see "1 - Android Auto" and "2 - Google", type 1 2 followed by enter.
- Type 2 and hit enter to choose "/system/priv-app" for the first app.
- Type 2 and hit enter to choose "/system/priv-app" for the second app.
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Once rebooted, Android Auto will soon disappear from your app launcher now that is a system app. This is by design.
- Use the Google Play Store to install "Android Auto for Phone Screens".
- Open the "Android Auto for Phone Screens" app. Complete all setup steps.
- Open the "Android Assistant" app. Complete all setup steps.
- Open the "Google" app. Go to More > Settings > Google Assistant > Hey Google & Voice Match.
- Turn on "Hey Google". Complete all setup steps.
- In the Google Assistant settings in the Google app, you should now be able to turn on "Hey Google" voice activation.
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Upon reboot, Android Auto should now work both on the phone and with Android Auto compatible vehicles head units.
- Hey Google should now work as long as the screen is on.
- Time for debloating!
STEP 5: Remove Realme bloatware.
Spoiler: Click here for instructions.
First we need to install an alternative input method, since we will be removing the stock keyboard. On the Neo 2T:
- Use the Google Play Store to install an input method of your choice, such as GBoard.
Now we can run the debloat script. On your PC:
- Plug the Neo 2T into your PC if it is not already.
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Double-click the RMX3357_A14_DEBLOAT_NO_ROOT.bat file to run the non-root debloat script.
- Press Enter to run the script.
- Close the window or press Enter to exit once finished.
We need to use ADB to remove a few system apps. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Enter this command: su
- Enter this command: pm uninstall --user 0 com.android.email
- Enter this command: pm uninstall --user 0 com.coloros.safecenter
- Enter this command: pm uninstall --user 0 com.heytap.book
- Enter this command: pm uninstall --user 0 com.heytap.market
- Enter this command: pm uninstall --user 0 com.heytap.themestore
- Enter this command: pm uninstall --user 0 com.nearme.gamecenter
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- You're done! Enjoy your debloated phone!
UH OH: Unbricking and Factory Restore.
Spoiler: Click here for instructions.
Click here for the ROM, use SP tools to flash. Guide coming soon, for now use the guide here.
------------------------------------------------------------------------------------------------------------------Realme GT Neo 2T Tips:
- If you find yourself needing to force your phone to power off for any reason, on the Neo 2T you must hold Vol+, Vol- and Power at the same time for around 10 seconds.
- The stock messaging app is com.android.mms, otherwise known as Mms.apk. It seemingly cannot be removed without breaking SMS/MMS.
- Removing Breeno will replace it with Google Feed when swiping left on the stock launcher fi the Google app is installed.
- There's a good chance the APN settings the phone chose are incorrect or nonexistent. Double-check them to make sure you have working data and MMS for your SIMs.
- Android Auto forces the phone to 60Hz and locks the settings, even once disconnected. Seems to be a common issue across a bunch of phones. Reboot to fix.
- If an app isn't showing notifications or is otherwise misbehaving:
>>> Make sure the app has been opened at least once since the phone was last powered on or rebooted.
>>> Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
>>> If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
>>> Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].
------------------------------------------------------------------------------------------------------------------
Spoiler: SOURCES
Guide by @mahotlov I shamelessly stole bits from: https://forum.xda-developers.com/t/x7-max-and-gt-neo-flash-ubrick-instructions.4337339/
Magisk: https://github.com/topjohnwu/Magisk
SafetyNet-Fix: https://github.com/kdrag0n/safetynet-fix
BusyBox NDK: https://github.com/Magisk-Modules-Repo/busybox-ndk
Terminal Systemizer: https://github.com/Magisk-Modules-Repo/terminal_systemizer
Reserved #1.
Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic
J_Eudes said:
Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic
Click to expand...
Click to collapse
Unfortunately there is no global ROM for the GT Neo 2T, I specifically asked Realme and they said they have no plans to release one.
Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!
dewidoj461 said:
Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!
Click to expand...
Click to collapse
Sure, here you go.
Hey, Is there a notification solution? to come from everyone?
AngelXTR91 said:
Hey, Is there a notification solution? to come from everyone?
Click to expand...
Click to collapse
Haven't had any issues with notifications myself. I'd check these:
- Make sure the app has been opened at least once since the phone was last powered on or rebooted.
- Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
- If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
- Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].
Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)
AngelXTR91 said:
Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)
Click to expand...
Click to collapse
Unfortunately I'm not sure why that might be happening. I don't have a smartwatch and I don't use Telegram or Viber. I can tell you that Slack and Wyze both keep giving me notifications well after 5 of them. Maybe someone else might know.
My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"
dewidoj461 said:
My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"
Click to expand...
Click to collapse
As much as I'd love to find some sort of global ROM for this phone, that looks identical to my build number etc. when I first got the phone and probably the China ROM. Latest now is A14. When I asked, Realme was pretty adamant that this phone will never see a global ROM. They had also installed Google Play and a long list of languages for me before shipping, but these just bolt on to the stock China ROM.
I'm not sure how to tell 100% if it's actually the China ROM or not, but I'd give "Hey Google" a try, or Android Auto if you have an AA compatible vehicle. Would also be curious to know if your phone came with a bunch of bloatware apps and Breeno.
As for backing up, SP Tools is what worked for me. I recommend taking a proper backup ASAP just in case something goes wrong later. That said, I'm not sure how to anonymize the files it spits out (empty data partition, remove your IMEI etc) so it's safe to share.
I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
As for the SP Flash Tool, how do I load the DA? This error appears after selecting the scatter file and clicking readback.
dewidoj461 said:
I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
Click to expand...
Click to collapse
Oh wow. A proper global ROM for this phone would be amazing. I'll see if I can figure out how to turn a backup into something flashable. In the meantime I think I'm going to email Realme again and see if their tune has changed.
Would it be possible to share where you bought the phone? I got mine from "realme Direct Store" on AliExpress.
I bought it from a reseller in shopee malaysia. I've asked the seller for the source to no avail, they just said it was the supplier who installed the rom.
I sent Realme an email directly, hopefully I get a more favorable answer this time. Will update if I hear anything. My AndroidFileHost account finally got upload perms so if I manage to get the ROM out of them it'll be easy to share.
Managed to take a proper backup after reading the guide by mahotlov linked in your thread. Just let me know which files you'd need anytime and I'd be willing to share.
Edit: Wifi and bluetooth no longer works after flashing your magisk.img & vbmeta.img. Restored my backup and it works again, interesting
I have a DM from someone else who also has an India A13 ROM shipped with their Neo 2T, so this is definitely a thing, but Realme responded to me yesterday and is still claiming it doesn't exist. They are having similar issues with the China ROM I uploaded breaking things. I seriously hope there aren't multiple hardware versions under the RMX3357 model number messing everything up.
As for your backup, I think it should be possible to just pick some of the files from your backup and use them to replace the matching .img file in the China ROM upload. This is assuming the partition structure and other things are the same and only the contents of the partitions are different (which it should be, but you never know). Only thing I'm not 100% sure on is which partitions would be safe to share and which ones might have personal info like IMEI or bits of your data partition.
dewidoj461 said:
Just let me know which files you'd need anytime and I'd be willing to share.
Click to expand...
Click to collapse
Please check here scatter to backup phone on sp flash tool and give me link download ROM_0-55 except ROM_14,15,18,19,24(ram, nvdata, nvcfg, protect1, protect2) in folder SP Flash tool.
Andy_men2 said:
Please check here scatter to backup phone on sp flash tool and give me link download all ROM_0-55
Click to expand...
Click to collapse
I would advise against this @dewidoj461. One of those ROMs has your IMEI info in it, and if you had been using the phone before your backup there is likely personal info somewhere too, especially if SIMs were installed. Maybe the intent here is not malicious but that user account is brand new and you would absolutely be giving sensitive information by supplying your full backup.
EDIT: I'm also suspicious about that RAR. The scatter file is only 54kb while that RAR is 2.1MB.