Regulatory domain, Wifi channels 12 and 13 - Xperia Arc General

Hi all!
I have noticed that my Arc S does not receive AP on channels 12 and 13. After doing some searches I concluded that the Regulatory domain must be set to US which is incorrect in my case, as I live in Europe.
I tried following this guide http://forum.xda-developers.com/showthread.php?t=1067944 to enable these channels, of couse doing the necessary modifications for this to work on a SE, but with no results unfortunatly.
My phone still has a locked bootloader and I cannot try custom roms, but will a custom rom solve this problem?
Moveover I am curious to know if this is a problem of the kernel module used which is locked to 11 channels or if it is because of some setting hardcoded in android itself.
Thank you!

as i can see, for the european area the only restriction is the signal power<20db, channels 11-13 are allowed and are working in Europe! My arc S is also locked but i can see channels 11-13.

Tkx for you reply labrok!
Then I cannot understand. I verified this using an app on the market called "Wifi Analyser", and the fact is that even in the wifi connect menu, all AP with these channels are not visible.
Also in the sqllite database available with the command
# /system/bin/sqlite3 /data/data/com.android.providers.settings/databases/settin
gs.db "select * from secure"
I can see:
wifi_num_allowed_channels|11
If I try to change this number to 13, it allows the change, but whenever I deactivate/activate the wifi, the number goes back to 11..
What is the version of the firmware that you are running?
I have 4.0.2.A.0.42.
Tkx!

same version, phone is European like yous so it uses same region settings,router TP-link TL-WR1043ND WITH ddwrt and router`s region set to Canada (to gain an extra 3db of power) i can set it till channel 13 and i can see it and i can connect too, to use channel 14 i must change region to japan but channel 14 is not usable from my arc s! but channels 12-13 working, they are not so good for an N network but my phone can see them an connect to them, maybe you should try to reflash your phone!

It's good to know that it works ok and that the problem lies only in software. I have asked some other users of the Arc S/Neo and they report the same problem
Maybe with your help we can solve this problem once and for all for everyone.
If your phone is rooted all I need you to do, is send me your Wifi drivers, running the following commands on the adb shell. Adb comes with the android sdk and is located at C:\Program Files (x86)\Android\android-sdk\platform-tools and then run "adb shell" command on a command line. You also need to activate the usb debugging on your phone.
Code:
su
cp /system/lib/modules/tiwlan_drv.ko /mnt/sdcard
cp /system/lib/modules/sdio.ko /mnt/sdcard
You now should have 2 files on the root of your sdcard, sdio.ko and tiwlan_drv.ko.
Can you please send these files to me?
I will then replace them on my phone and effectively determine if the problem is actually caused by the drivers or by the Android system itself.
Thank you so much for your help!!

My friend my phone is not rooted, if there is a way to help you, but because my phone is new I cannot root it and avoid my guarrantee.
Sent from my LT18i using XDA App

Thank you anyway labrok! I will keep searching for someone that has this working and with root to see if I can solve my problem

Ok, actually I found out how you can do this without root and without touching the warranty.
I will guide you through the process.
Install the Android SDK available at http://developer.android.com/sdk/index.html
Activate the USB debugging on "Applications"->"Development"->"USB Debugging"
Then open a command line prompt on windows and go to the directory where you installed android, typically C:\Program Files\Android\android-sdk\platform-tools, with the command
Code:
cd "C:\Program Files\Android\android-sdk\platform-tools"
Copy the driver files now from the phone with the commands
Code:
adb pull /system/lib/modules/tiwlan_drv.ko
adb pull /system/lib/modules/sdio.ko
The command prompt should look like this
Code:
C:\Program Files\Android\android-sdk\platform-tools>adb pull /system/lib/modules
/tiwlan_drv.ko
4636 KB/s (973324 bytes in 0.205s)
C:\Program Files\Android\android-sdk\platform-tools>adb pull /system/lib/modules
/sdio.ko
1618 KB/s (26520 bytes in 0.016s)
Files tiwlan_drv.ko and sdio.ko should be on C:\Program Files\Android\android-sdk\platform-tools folder now. Zip them and send them to me plz

i will try, but i think is not drivers problem.More likely its region restrictions, in Greece its allowed channels from 1-13, maybe in your is different than Greece! but i will send you the drivers as soon as possible!

I'm having the same issues with Xperia Arc S in Bulgaria. The phone has set it's wifi radio to operate on channels 1-11 so any networks on channels 12, 13 and 14 aren't visible to me.
Pure Android has the option to set the regulatory domain, but SE has decided to disable (or hide) it.
Here you can see how to set it on a non-SE Android: firdouss.com/2011/07/wifi-network-android-reason/
I've asked SE to check this on their forum too:
talk.sonyericsson.com/message/127760

Thank you the_mouse_bg!
I have bootloader unlocked my Arc S and tried a few roms like CM7.2, MIUI where I can see all 13 channels fine, so from this I have concluded that the problem is really from the firmware as due to the lack of answers on this topic, I was getting really worried this could be a hardware problem from my phone..phewwww
I now have stock firmware .42 with DooMKernel installed and the regulatory domain does appear in the menu but fails to be changed
I asked in the DooMLord's kernel topic to see if I can in any way debug this problem to try to solve it as I'm still little experienced with linux android workings.
Let's see if we can solve this issue asap!!

Regulatory domain (Wi-Fi channels 12 and 13) fix for the factory (default) ROM
I managed to fix the regulatory domain in order to be able to use the wireless channels 12 and 13 in the factory ROM. I only tested this procedure in the Xperia Pro (MK16a) and using the factory GingerBread ROM, although the procedure should be similar for other Xperia models and for the ICS ROM.
Well, it still needs rooting, but for those worried about the warranty it should be better than unlocking the bootloader or installing another ROMs, because you can root your phone, apply the fix, then unroot it, and nobody will ever know the phone was once rooted unless they do a deep forensic analysis.
How the regulatory domain works in Xperia devices
Sony added a class named "com/android/server/WifiService$RegulatoryDomain" which isn't part of standard AOSP. This class checks in which country you currently are based on the current MCC (Mobile Country Code), extracted from the first 3 digits of the current PLMN. Then there is a list of MCCs of countries on which 13 Wi-Fi channels are allowed. If your MCC is on the list, it enables 13 channels, otherwise it only enables 11 channels.
If your current MCC is not on the list, your wifi_num_allowed_channels setting has no effect. It is always reseted to 11.
Note that this is an "Android framework-level lock", not a "Linux-level or driver-level lock", because if you try to run iwlist (you can build yours from this svn repo) it shows channel 12 and 13 Wi-Fi networks even without any modification to the factory ROM.
The problem
The problem is that not all countries which allow 13 Wi-Fi channels are listed in the "WifiService$RegulatoryDomain" class. Apparently, there are typo errors in some MCCs.
For example, Brazil is MCC 724, but the class lists MCC 742, which according to this listing is a non-existent MCC. So it's apparently a typo error. They typed 742 instead of 724.
Fixing it
First, root your device. I used FlashTool for this.
Then, copy /system/framework/services.jar from your device to your computer using adb. Then unpack it (unzip or 7zip or whatever), use baksmali for disassembling classes.dex, and open "com/android/server/WifiService$RegulatoryDomain.smali" in a text editor.
Look for something like:
Code:
const/16 v7, 0x24
const-string v8, "742"
aput-object v8, v6, v7
iput-object v6, p0, Lcom/android/server/WifiService$RegulatoryDomain;->mHighChannelsMccs:[Ljava/lang/String;
This is where the 13-channels-allowed MCC list is being built. The "742" is the apparently non-existent MCC. Just replace it by the MCC of your country. Look at this listing or look at the first 3 digits of the PLMN:
Code:
$ adb logcat | grep PLMN
E/WifiService( 241): Could not get PLMN!
E/WifiService( 241): Could not get PLMN!
E/WifiService( 241): Could not get PLMN!
I/WifiService( 241): PLMN = 72410
I/WifiService( 241): PLMN = 72410
In my case I just replaced "742" by "724".
Then use smali for assembling the code back to the classes.dex file, and repack the services.jar file using jar, zip or another tool.
Finally, copy your modified services.jar to your device's /system/framework/services.jar using adb, and reboot your phone. Now everything should work.
About the attached file
My modified services.jar is attached for reference. Remember it is for the Xperia Pro factory GB ROM. If you use ICS or if you have another Xperia device, you need to baksmali/modify/smali your own jar file as described above.

Related

HTC Stocks currency problem

The HTC Stocks app has the best widget of all other currency apps, so I was using it on my 1.5 Hero for displaying the EURO/GBP (EURGBP=X) rate.
After the 2.1 rom update I have a strange problem. When I try to add a new ticker for "eurgbp=x", I get the error message: "Unable to recognize the company name or stock symbol you typed. Please try again." However, this worked in the past like a charm. I have to note that adding "gbp=x" or "usd=x" works fine, with no problem at all.
Maybe this problem is related to an updated version of the Stocks app in the new rom. Is anyone experiencing the same problem? I haven't found a similar thread for a Sense Android phone. The same problem exists in the latest rom of HD2, but people have figured a work-around, by changing a file under "Application Data\HTC\", but this file doesn't exist on Android.
Any help would be more than welcome!
I experience the same problem (although I'm on VillainRom12). Previously adding currencies (EURUSD=X etc) was working, but right now I am unable to find it. This could be HTC problem as it was working fine on 1.5, but this could be also some Yahoo search glitch (I am unable to search for that quotes on mobile version of the Yahoo Finance page, while the desktop version works fine). The only workaround to that was to edit manually SQLite database of Stocks application (but this may require root - I can provide details if necessary). Once I added appropriate entries to the list of stocks, it seems to be working fine (it is displaying my currencies, but the search still does not work).
One other deficiency I found was the fact that graphs are not cached anymore - If I open the application and check for example a daily graph, I need to update it in order to see any chart - each time, even if I switch from 1D to 5D and back. It is also automatically updated each time I visit given tab, if I enable the automatic updates. Previously this app displayed previously cached graph. I'm not sure whether this happens also on stock 2.1 ROM.
Now that you mention it, I have the same problem with the graphs in the 2.1, too. It worked (showed the cashed graph) in the 1.5, but not any more. Blank graph until it updates.
Can you provide me some guidance about how to edit the Stocks' database? At least a link to something similar would be much appreciated. Can I access the phone's system folder without rooting it, through my PC (Win, Linux, whatever)?
eeVoskos said:
Can you provide me some guidance about how to edit the Stocks' database? At least a link to something similar would be much appreciated. Can I access the phone's system folder without rooting it, through my PC (Win, Linux, whatever)?
Click to expand...
Click to collapse
I'm new in the business, so I'm not sure if the root is necessary. You can try it, anyway to see if you will be able to push and pull files from the directory where Stocks stores its database.
Here's what I did:
Enable USB Debugging in Settings -> Applications -> Development -> USB Debugging
Download Android SDK from http://developer.android.com/sdk/index.html
In command line go to subdirectory tools of Android SDK
Close Stocks app and remove Stocks widget from the screen
Connect Phone via USB
... (Beginning of the optional part) ...
Go to Android shell
Code:
adb shell
List any processes to see if there's a com.htc.android.Stock process (like in this case)...
Code:
ps | grep Stock
7605 10007 130m S com.htc.android.Stock
7619 0 2156 S grep Stock
Kill any Stock processes (using the value in the first column):
Code:
kill 7605
Exit to command line
Code:
exit
... (End of the optional part) ...
Pull the Stock database:
Code:
adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
Sample output:
Code:
d:\Projects\Android\tools>adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
568 KB/s (5120 bytes in 0.008s)
Backup, just in case:
Code:
copy stock.db stock_backup.db
Run sqlite3
Code:
sqlite3 stock.db
Enable headers in sqlite:
Code:
.headers on
List contents of quotes table:
Code:
select * from quotes;
Sample output:
Code:
sqlite> select * from quotes;
_id|_name|_symbol|_price|_change|_percent|_open|_high|_low|_volume|_link|_type|_sequence|_updatetime
2|CHF/PLN|CHFPLN=X|3.08299994468689|0.0116999996826053|0.381900012493134|3.07209992408752|3.08550000190735|3.07010006904602|0|http://m.yahoo.com/htcwf/search?p=CHFPLN=X||0.0|1278490511305
3|USD/PLN|USDPLN=X|3.27649998664856|0.0200999993830919|0.617200016975403|3.25550007820129|3.27959990501404|3.24499988555908|0|http://m.yahoo.com/htcwf/search?p=USDPLN=X||100.0|1278490511305
4|EUR/PLN|EURPLN=X|4.1217999458313|0.0151000004261732|0.367700010538101|4.11250019073486|4.12349987030029|4.10799980163574|0|http://m.yahoo.com/htcwf/search?p=EURPLN=X||200.0|1278490511305
5|EUR/USD|EURUSD=X|1.25789999961853|-0.00469999993219972|-0.376199990510941|1.26170003414154|1.26259994506836|1.25689995288849|0|http://m.yahoo.com/htcwf/search?p=EURUSD=X||300.0|1278490511305
6|EUR/CHF|EURCHF=X|1.33689999580383|-0.000899999984540045|-0.0710000023245811|1.33879995346069|1.33910000324249|1.33609998226166|0|http://m.yahoo.com/htcwf/search?p=EURCHF=X||400.0|1278490511305
sqlite>
Note the last _id (here 6) and add new currency with _id higher by 1 (so here, 7):
Code:
insert into quotes (_id, _name, _symbol) values (7, "EUR/GBP", "EURGBP=X");
Check if it has been added:
Code:
select * from quotes;
Sample output:
Code:
sqlite> select * from quotes;
_id|_name|_symbol|_price|_change|_percent|_open|_high|_low|_volume|_link|_type|_sequence|_updatetime
2|CHF/PLN|CHFPLN=X|3.08299994468689|0.0116999996826053|0.381900012493134|3.07209992408752|3.08550000190735|3.07010006904602|0|http://m.yahoo.com/htcwf/search?p=CHFPLN=X||0.0|1278490511305
3|USD/PLN|USDPLN=X|3.27649998664856|0.0200999993830919|0.617200016975403|3.25550007820129|3.27959990501404|3.24499988555908|0|http://m.yahoo.com/htcwf/search?p=USDPLN=X||100.0|1278490511305
4|EUR/PLN|EURPLN=X|4.1217999458313|0.0151000004261732|0.367700010538101|4.11250019073486|4.12349987030029|4.10799980163574|0|http://m.yahoo.com/htcwf/search?p=EURPLN=X||200.0|1278490511305
5|EUR/USD|EURUSD=X|1.25789999961853|-0.00469999993219972|-0.376199990510941|1.26170003414154|1.26259994506836|1.25689995288849|0|http://m.yahoo.com/htcwf/search?p=EURUSD=X||300.0|1278490511305
6|EUR/CHF|EURCHF=X|1.33689999580383|-0.000899999984540045|-0.0710000023245811|1.33879995346069|1.33910000324249|1.33609998226166|0|http://m.yahoo.com/htcwf/search?p=EURCHF=X||400.0|1278490511305
7|EUR/GBP|EURGBP=X|||||||||||
sqlite>
Quit sqlite:
Code:
.quit
Push the file back to the phone:
Code:
adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
Sample output:
Code:
d:\Projects\Android\tools>adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
341 KB/s (5120 bytes in 0.014s)
Restart phone.
See if that worked
I hope HTC (or Yahoo) will be able to fix that, because the above is really a long process...
Anyway, I can't make it work. Entering "ps | grep Stock" gives me a "grep: permission denied" error message. I did some searching and I believe this is what people mean by saying "you need root access", right? I'll come back when I'm rooted (i.e. when I find a decent guide for rooting 2.1).
Thanks for your time & effort man. I really appreciate it.
eeVoskos said:
Anyway, I can't make it work. Entering "ps | grep Stock" gives me a "grep: permission denied" error message.
Click to expand...
Click to collapse
You can try to omit the "optional" part (steps 6-9) - the ps thing was just to make sure that Stock isn't running. But I noticed anyway that it never ran in the background when I closed it on the phone. Try to adb pull and adb push and see if you'll get any permission issues. If you do, then you indeed need a root (sorry I can't check that as I'm rooted)
A couple of days ago I updated the ROM of my HTC TD2, with the most recent one of HTC (WM6.5, Sense 2.5.20113030.0). Afterwards I noticed that I also could not get the stock app to accept the code EURUSD=X.
You mention the following
The same problem exists in the latest rom of HD2, but people have figured a work-around, by changing a file under "Application Data\HTC\", but this file doesn't exist on Android.
Click to expand...
Click to collapse
Can you tell me what that work-around is or point me to it? Hopefully this can help me.
Thank you in advance.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=706732
eeVoskos said:
Check this thread:
Click to expand...
Click to collapse
Thank you for the link (which I am not allowed to repost ).
Last Monday I wrote an e-mail to HTC about this problem and a couple of days later I got a reply. They told me they tried to search for the currency rate (eurusd) and that they got a result. So I tried again and lo and behold I got a result as well. Searching for eurusd=x gave me a result while last weekend it was not working.
So I tried several other currency rates and they all rendered a result, also eurgbp=x. Perhaps it is also fixed for the Android app.
[Extra information added below]
Tried again and nothing
I was connected with a data connection to my carrier, so I switched to my wifi connection. Tried again and... result.
So it seems to be a difference in communication between an ordinary data connection and a wifi connection. Maybe this will help someone
Wird problem. I tried it too on both UK and Greek carriers and on WiFi, but nothing. No result for either of them: "eurgbp=x", "eurgbp", "eurusd=x", "eurusd". I have been trying occasioanly more than one month now.
I think I should drop them an email too...
Why don't you do a soft (temporary) root and make the database entries as described in here? I did it and now I got all the stuff I need, and no trace of root on the device.

Programming modem with QPST/QXDM on Boost Desire 626S

Hello everyone. It's been heavily requested that I create a guide on how to program the values I provided in one of the posts on my previous boot image thread into the Boost Desire 626S modem so I decided to take the job into my own hands for your convenience.
First you will need QPST, QXDM, and the modem diag usb driver if it is not already installed on your computer. Here are the links:
QPST:
https://www.sendspace.com/filegroup/XynIcslf8H6Qm2TsJ5z4ZEocT85CdvbS
QXDM:
https://www.sendspace.com/filegroup/XynIcslf8H6Qm2TsJ5z4ZEocT85CdvbS
DIAG DRIVER:
https://www.sendspace.com/filegroup/XynIcslf8H6Qm2TsJ5z4ZEocT85CdvbS
1 --- INSTALLING SOFTWARE / DRIVERS
Run QPST.2.7.425 from the QPST folder in the QPST.zip archive and install it by clicking next through the dialog box at each step.
Run QXDMInstaller from the QXDM folder in the QXDM.zip archive and install it by clicking next at each step as well.
Run HTC CDMA LTE DIAG Modem Driver v3.0.2.0 from the inside the DIAGDRIVER.zip archive and you've got everything you need to now program the Boost Desire 626S modem.
2 --- SETTING UP USB DEBUGGING
---First you will need to enable usb debugging.
---Connect your Desire 626S to a usb port on your computer.
---Open the settings app and scroll to about and select it.
---Next, select software information then select more and tap on build number 7 times.
---This will enable access to Developer Options in the settings app.
---Tap back three times and you will now see developers options as selectable in the settings app.
---Tap on developer options and scroll down a bit to USB debugging option.
---Make sure it has a blue checkmark next to it so it is enabled.
3 --- SETTING UP DIAG USB ACCESS
---Now we will enable usb diag access to allow communications with QPST/QXDM.
---On your computer with the phone still connected, open a command prompt as administrator and type adb shell then hit enter.
---Or if you are using minimal adb and fastboot installation, open the shortcut for it as administrator and type adb shell then hit enter.
---On your phone, tick the box next to always allow and tap ok.
---You might have to type in adb shell again and hit enter.
---Do so and you will see [email protected]_a32ewhl:/ $ at the prompt which means you have shell access.
---Now we need root shell access.
---With the shell access, type in su and hit enter.
---Allow the root access for adb shell in the supersu prompt that pops up on your phone.
---You will now see [email protected]_a32ewhl:/ # in the command prompt window.
---Congrats you now have root access.
---With root shell access type this in and hit enter in the command prompt window:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
---You might hear a ding and you have now enabled diag access to use QPST/QXDM in order to program the modem.
4 --- SETTING UP MODEM DIAG COMMUNICATION
---To open QXDM, click the orb in the bottom left hand corner to open the start menu and then click all programs.
---Scroll to QXDM Professional and click it and then click the next QXDM Professional shortcut under it.
---QXDM will now open so now it's time to access the diag port to the modem.
---Click on options in the bar towards the top of the window and then click on communications.
---Under target port, click on the box that says disconnect and click on the available COM port whether it might be COM1-5 then click ok.
5 --- PROGRAMMING MODEM NV ITEM VALUES
---Now we are down to the nitty gritty, actually programming the values for the bands in the modem. It is actually quite easy to do if you figure out what needs to be done.
---Click on the box next to view on the second bar down and click on the NV browser option to open it.
---In the NV browser window you will see some of the first typical NV items that might be included in a modem firmware but we are looking for the certain ones we want to edit to change bands and functionality.
---Left click the up and down arrows on the scroll bar and hold the left mouse button to slowly scroll from item value to item value if you need to, and slowly drag the knob on the scroll bar up and down if you require quicker navigation through the NV items.
---Once you reach an NV item you want to change, for instance, item 1877, click it and in the box under fields section you will see the input field used to change the following value field are both 0, followed by the respective nv items true name.
---To retrieve the content of each field for item 1877 or any nv item, click the read button in the bottom right hand side of the nv browser window, and you will be presented with the fields contents.
---For example NV item 1877 has a default value field content of 78135687 on my Boost Desire 626S so input field is also the same but this input field is what we change.
---Click the value under input once to select it then click it again and it will be editable with the caret blinking and 78135687 highlighted.
---Type in or copy and paste the value you wish to use for the value field in this input field once it is highlighted then hit enter on the keyboard and click write in the bottom right hand side of the window to make the new value stick.
---Congrats you have changed the value for an NV item.
---After writing new values, click offline in the bottom right hand side of the nv browser and wait 5 seconds.
---You will see the signal bar on your phone go blank.
---Click reset and the signal on your phone will be restored.
---Follow these last few steps when writing new values to ensure they stick.
---Reboot your phone and the values will stick.
6 --- GETTING MSL/SPC CODE FOR YOUR PHONE
---Scroll to item ID 00085 with description security code and click it to select it then click read in the bottom right hand side of the NV browser window
---In the input and value fields you will be presented with the MSL/SPC for your phone.
---Use this MSL/SPC code to program/edit the modem nv item values in EPST menus accessed by using ##3282# in the dialer.
---Also type in spc ****** in the text field in the command bar below the view bar in the QXDM window and hit enter, the six stars being the six digits of your MSL/SPC.
---Enter the MSL/SPC in the latter manner before writing new values to the modem for safe measure to ensure they stick.
---Quick note, enter *#*#4636#*#* in the dialer to open the testing menu, and tap phone information then scroll down to set preferred network type, and tap the down arrow to the right then scroll to and tap the network type you would like to use.
7 --- HERE ARE SOME RELEVANT NV ITEMS AND THE VALUES TO WRITE TO THEM....
----------------
Items 6828 and 6829
35184372088830
all lte
----------------
Item 65633
0x00001FFFFFFFFFFE
all LTE Bands
----------------
Item 441
32767
all 3G
----------------
Item 946
65535
all 3G
----------------
Item 1878
32
max HW band
----------------
Item 2954
4294967295
all 3G
----------------
Item 1877
18446744073709551615
all 3G
----------------
Item 4548
18446744073709551615
all 3G
----------------
Item 11
B only
Channel 384 and 777
----------------
Item 12
B only
Channel 384 and 777
----------------
Item 441
0x2
Channel B
----------------
Item 442
0xFFFF
All Roam
----------------
Item 10
LTE Only
Band Pref
----------------
Item 5
0x0
Slot Cycle Index
-------------------
Item 4
0x9A
Station Class Mark
----------------
Item 179
0
Voice Privacy
----------------
What next?
---------- Post added at 11:36 AM ---------- Previous post was at 11:19 AM ----------
I meant how do I use d softwares to edit LTE bands
Thanks a lot man. I've successfully programmed the values and although I have a Sprint version and the LTE bands are different in my country, I was able to get the values from NV calculator on play store. I've not had time to check if they work albeit I programmed 3g bands a while back and band 2100 which works in my country failed to work, I hope the LTE works. Thanks once again
You're Welcome
doyin116 said:
Thanks a lot man. I've successfully programmed the values and although I have a Sprint version and the LTE bands are different in my country, I was able to get the values from NV calculator on play store. I've not had time to check if they work albeit I programmed 3g bands a while back and band 2100 which works in my country failed to work, I hope the LTE works. Thanks once again
Click to expand...
Click to collapse
You're Welcome. Glad it worked for you.
@anthonykb
---With root shell access type this in and hit enter in the command prompt window:
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
---You might hear a ding and you have now enabled diag access to use QPST/QXDM in order to program the modem.
Click to expand...
Click to collapse
Great work !!
Do you have any reference to other commands for switching the download / service modes?
To flash boot-loaders and such !!
I have the board support package for the msm8909 chipset and I am working on building the required programmers.
Just need to write my partition.xml ( I have the GPT info. )
My plan is to make a Qfil flashable Service Rom.
Update: Bands were successfully programmed as I stated earlier but sadly, they don't work. I just hope and pray someone somewhere is making a from scratch custom kernel for this device
@doyin116
Did that for Lollipop ( Completed ) For Marshmallow they didn't release the source yet.
I don't think it will be a problem to use the CAF source. ( Will Find out soon. )
Here is my kernel.
http://forum.xda-developers.com/desire-626/development/kernel-wip-port-lollipop-5-1-source-t3470476
Here's my source.
https://github.com/Bigcountry907/kernel_htc_a32eul
I just synced the CAF Android 7.0 source.
It's gonna be a wile cause I been developing this by my self but it is in the works.
I have built the UBERTC cortex a9 toolchains and compiled the kernel inline with the recovery both in omnirom 6.0 and omnirom7.0.
Omnirom 7.0 uses Ninja for building. https://ninja-build.org/
I didn't know if this would cause a problem but it didn't. None I couldn't fix anyway.
So I have used the 5.1 kernel source and built it successfully in newer android versions.
It could be the combination of ninja and the UBERTC toolchain that make it work. IDK.
What do you need in the kernel? I might have it built.
BigCountry907 said:
@doyin116
Did that for Lollipop ( Completed ) For Marshmallow they didn't release the source yet.
I don't think it will be a problem to use the CAF source. ( Will Find out soon. )
Here is my kernel.
http://forum.xda-developers.com/desire-626/development/kernel-wip-port-lollipop-5-1-source-t3470476
Here's my source.
https://github.com/Bigcountry907/kernel_htc_a32eul
I just synced the CAF Android 7.0 source.
It's gonna be a wile cause I been developing this by my self but it is in the works.
I have built the UBERTC cortex a9 toolchains and compiled the kernel inline with the recovery both in omnirom 6.0 and omnirom7.0.
Omnirom 7.0 uses Ninja for building. https://ninja-build.org/
I didn't know if this would cause a problem but it didn't. None I couldn't fix anyway.
So I have used the 5.1 kernel source and built it successfully in newer android versions.
It could be the combination of ninja and the UBERTC toolchain that make it work. IDK.
What do you need in the kernel? I might have it built.[/QUOTE
Came across your kernel but from my understanding, it was meant for the METRO PCs version of 626s while mine is the Sprint version. I also tried to downgrade from marshmallow to lollipop but wasn't successful because it seemed the tutorial again was for METRO PCs. As to what I need in the kernel, I heard Qualcomm has an anti-tamper settings or so that prevents flashed bands from working but can be by passed by a built from scratch kernel.
My questions now are: can I flash your kernel on my 626s albeit the Sprint version and if yes, how do I downgrade to 5.1 on my Sprint version. If no, could you please create a custom kernel for the Sprint version? Thanks
Click to expand...
Click to collapse
Maybe I can get you a ruu of lolipop.
Let me go see.
Most likly I need to build you a kernel.
BigCountry907 said:
@doyin116
Did that for Lollipop ( Completed ) For Marshmallow they didn't release the source yet.
I don't think it will be a problem to use the CAF source. ( Will Find out soon. )
Here is my kernel.
http://forum.xda-developers.com/desire-626/development/kernel-wip-port-lollipop-5-1-source-t3470476
Here's my source.
https://github.com/Bigcountry907/kernel_htc_a32eul
I just synced the CAF Android 7.0 source.
It's gonna be a wile cause I been developing this by my self but it is in the works.
I have built the UBERTC cortex a9 toolchains and compiled the kernel inline with the recovery both in omnirom 6.0 and omnirom7.0.
Omnirom 7.0 uses Ninja for building. https://ninja-build.org/
I didn't know if this would cause a problem but it didn't. None I couldn't fix anyway.
So I have used the 5.1 kernel source and built it successfully in newer android versions.
It could be the combination of ninja and the UBERTC toolchain that make it work. IDK.
What do you need in the kernel? I might have it built.
Click to expand...
Click to collapse
BigCountry907 said:
Maybe I can get you a ruu of lolipop.
Let me go see.
Most likly I need to build you a kernel.
Click to expand...
Click to collapse
Would really appreciate you building me a kernel. Thanks in advance
@doyin116
I got my hands on a RUU for sprint lolipop.
I will upload when I get a chance.
Right now i'm in kernel mode so you might get lucky.
Hopefully I can add the sprint config to my tree and build it.
I'm trying that with the vzw 526. So if all goes well........
After I make recovery for 526 I will compile you a kernel.
BigCountry907 said:
@doyin116
I got my hands on a RUU for sprint lolipop.
I will upload when I get a chance.
Right now i'm in kernel mode so you might get lucky.
Hopefully I can add the sprint config to my tree and build it.
I'm trying that with the vzw 526. So if all goes well........
After I make recovery for 526 I will compile you a kernel.
Click to expand...
Click to collapse
I'm glad. Is there a time frame for all of this to be done?
I will upload this ruu tonight. Over the weekend I will put together the kernel over the weekend.
You will have to test it. I don't think I can flash sprint to my device. It's metro. But I am s-off.
BigCountry907 said:
@doyin116
I got my hands on a RUU for sprint lolipop.
I will upload when I get a chance.
Right now i'm in kernel mode so you might get lucky.
Hopefully I can add the sprint config to my tree and build it.
I'm trying that with the vzw 526. So if all goes well........
After I make recovery for 526 I will compile you a kernel.
Click to expand...
Click to collapse
BigCountry907 said:
I will upload this ruu tonight. Over the weekend I will put together the kernel over the weekend.
You will have to test it. I don't think I can flash sprint to my device. It's metro. But I am s-off.
Click to expand...
Click to collapse
No problem. I'm up for it
@doyin116n116
Here is the 5.1 ruu for sprint.
https://drive.google.com/open?id=0B8jitdIyh2NtUHQ2YWd5T2RCUFk
Download it and rename the file 0PM9IMG.zip.
See the downgrade post for metro pcs and edit the mainver in the misc partition as shown there.
You can just flash the misc.img that is posted on that thread.
Copy the 0PM9IMG.zip to your sdcard.
Boot the phone into download mode.
It will ask you if you want to install the ruu.
Hit the vol up key to install it.
If it reboots the first time back to download mode then hit vol up again.
It will flash for sure.
And don't worry.....it is easier to go back to MM than it is to go to LP.
BigCountry907 said:
@doyin116n116
Here is the 5.1 ruu for sprint.
https://drive.google.com/open?id=0B8jitdIyh2NtUHQ2YWd5T2RCUFk
Download it and rename the file 0PM9IMG.zip.
See the downgrade post for metro pcs and edit the mainver in the misc partition as shown there.
You can just flash the misc.img that is posted on that thread.
Copy the 0PM9IMG.zip to your sdcard.
Boot the phone into download mode.
It will ask you if you want to install the ruu.
Hit the vol up key to install it.
If it reboots the first time back to download mode then hit vol up again.
It will flash for sure.
And don't worry.....it is easier to go back to MM than it is to go to LP.
Click to expand...
Click to collapse
@BigCountry907 I'm having issues flashing the misc.img. I flashed through adb fastboot flash misc.img and it said unknown partition 'misc.img' error: cannot determine image file name for 'misc.img'. I flashed through twrp and it said could not find meta-inf/com/Google/Android/update-binary in the zip file. Through adb I did adb push misc.img /sdcard/".
"adb shell"
"su"
"dd if=/sdcard/misc.img of=/dev/block/bootdevice/by-name/misc" and it succeeded but when I flashed the 5.1 ruu it said ru_zip_error.
Could it be that the downgrading process is for metro PCs/ do I have to be unrooted or can I get detailed process of flashing it if I did it wrong. Alternatively, is there a tool I can use to access the misc.img partition and edit it myself?
@doyin116
I am creating a new how to thread.
We have got this thread way off topic.
The new thread is here.
http://forum.xda-developers.com/desire-626/general/how-to-downgrade-sprint-desire-626s-to-t3498653
Give me a little wile to write it up.
If a Moderator would like to move post #7 through post #17 to there that would be good.
How do we request a moderator to do that?
Old thread on old phone, I realize... but hoping someone might catch this & assist me. Having issues with gather SPC using QXDM 03.14.594 on 626s 0PM92 - Sprint MM ROM running on I-Wireless [T-Mobile].
While attempting READ on 00085, response is: "No DIAG response received".
Concerned about programming NV values in EPST w/o it. Any thoughts?
Update: After upgrading both qxdm/qpst, I'm getting a return on read from phone. Has it possibly been set as: 000000?

Xiaomi Mi Bunny Watch Q internationalization

Please somebody help to modify firmware to enable international GPRS connections
What we currently have:
1. Mi Bunny Watch Q is Working on MT6261 SOC
2. Operating system is modified 2011 year Nucleos RTOS, which was widely used in older featurephones
3. Firmware is not available for separate downloading. Watch updating is OverTheAir (via Bluetooth connection from your smartphone with original APP, and, PROBABLY via GPRS connection) firmware files are called
SH08_PCB01_gprs_MT6260_S00.MAUI_11B_W13_08_MP_V15.bin
My current firmware version is MAUI.11B.W13.08.MP.V15
updates are downloaded from http://upgrade.imibaby.net/upgradeWatch
also you can find http://sw105-online.imibaby.net/ link in firmware - probably for watch activation
All we have now - full ROMdump of my watch divided to parts with Readback Extractor mtk
Also we can get acess to NVRAM and FAT partition with MauiMETA_v9.1635.23 tool (you need NVRAM database file for MT6261 chip - i've gt one from Keneksi X8 firmware kit ( or from official site ) also i have used scatter file from Keneksi to download ramdump with SP Flash Tool
Also there is good tool Binwalk which i don't know how to use well
4. Watch activation procedure looks like: ( english user manual for similar product )
-turn on the watch (lights on and sound prompt)
-insert SIMcard (sound prompt)
-----------we are currently here------------------
-GPRS connection is automatically established
-and watches time should set up the time (you get a sound prompt) /what notifies server of pairing ready status/ - this should be a sign and confirmation of successful internet connection
-you scan QR code in your user-manual (smartphone receives pairing settings from server) and establish connection between smartphone and WATCH
...
5. Watch officially supports only Chinese SIM cards. Confirmed by manufacturer. Chinese cellular operators settings are preinstalled. MNC MCC and APN can be found in firmware like 460 46000 46002 46007 etc
i have tryed to change MCC and MNC to my operators (25501) (my operator supports any APN so i got luck here)
and have got a breakthrough here - watch began to establish GPRS connections via "internet" APN
but no luck - time is not set up, i've got no "successful connection" sound prompt, and it is still impossible to activate it.
I have contacted manufacturer via Weibo and WeChat.
Everywhere i got refused with corporate security reasons, BUT at the very beginning i think some very helpful manager answered and tryed to give help (later he disappeared)
He requested from me to fill up XML form with my cellular operator's settings and sent image explaination
Hello,Mr Pumpkin
There is some instructions you can follow.
First,please make sure the sim card support calling in or calling out.
Secondly,be sure the sim card supports 2G GPRS connection.
You can consult the local operators about specific parameters.
The "code" parameter and "apn" parameter in the following table must be filled in correctly.
The other parameters are alternative.
Code:
<?xml version="1.0" encoding="UTF-8" ?>
- <Account>
- <AcntHdr>
<AcntVer>1.0</AcntVer>
</AcntHdr>
- <AcntBody>
- <SIM Operator="BEELINE" Code="25502">
- <Item Bearer="GPRS">
<AppType>WAP</AppType>
<Title>Beeline WAP GPRS</Title>
<APN>wap.beeline.ua</APN>
<Authentication>NONE</Authentication>
<Homepage>http://wap.beeline.ua</Homepage>
<Proxy Enable="Yes" ProxyAddress="172.29.18.192" ProxyPort="8080" />
<PrimaryDNS>null</PrimaryDNS>
<SecondDNS>null</SecondDNS>
<IPAddress>null</IPAddress>
<Subnet>null</Subnet>
<ConnectionType>HTTP</ConnectionType>
</Item>
Click to expand...
Click to collapse
There is excellent site with lots of information
https://www.dr-lex.be/hardware/china_phone_flashing.html
Also some discussion is going on MIUI forum and russian 4pda forum
International Apn settings
The answer from the Chinese manufacturer is an xml file that we should add to the device ROM. It is not so different to the following thread
https://forum.xda-developers.com/showthread.php?t=2387346
I have my bunny watch 2, that I have paired during a visit to Sz, and will try to add the xml file today. Hopefully we can get a connection.
EASolana said:
The answer from the Chinese manufacturer is an xml file that we should add to the device ROM. It is not so different to the following thread
https://forum.xda-developers.com/showthread.php?t=2387346
I have my bunny watch 2, that I have paired during a visit to Sz, and will try to add the xml file today. Hopefully we can get a connection.
Click to expand...
Click to collapse
Excellent desicion! I will try to do it.
I can assume, that developer didn't offered me this thing because we actually don't have access to ROM. We can get there only with MAUI META tool. Also the watch is not based on Android, so we will have to find correct folder to place the file and guess correct name for it.
Also XML should be specifically formatted, and we have this format from developer.
Easier said than done, but still I got some progress today.
After reviewing the ROM I was able to find several At commands to control the device.
I'm missing the sintaxis on many of them, but I was able to directly perform and receive a call from the Hyper terminal.
I named the xml file default.xml and placed on the root directory and several others but no luck achieving a Apn configuration.
Also I browsed the fat and nvram looking for hints on how the device was configured while using the Chinese card, but no luck there.
If I'm able to find the device configuration At command it should be pretty straightforward.
Just as a note, the App is fully Chinese, no options on the menu are translated.
EASolana said:
Easier said than done, but still I got some progress today. .
Click to expand...
Click to collapse
Some of terminal AT+ commands work excellent (like ATD Most interesting one is AT+DEBUG_ON and AT+DEBUG_OFF it changes usb connection type. ( With debug on you will get 2 usb devices (usb com, and modem)
About app - i have translated it to russian, if it can help )
Connecting outside of china
Well, today I got connection from outside of China.
I played with several of the At commands that were supposed to actually configure the settings, and all seemed to make the terminal hang.
But after rebooting the phone it got a connection. Now it's fully working.
I used the AT+CGDCONT command.
Then I reviewed again the Fat to look for changes and the only file that was modified is store_info. Dat file.
That file was loaded in the same back up you made, with China Mobile settings, and now mine has got the unicom settings.
For the information it contains it looks fairly similar to the format the engineer gave you a solution for.
EASolana said:
Well, today I got connection from outside of China
Click to expand...
Click to collapse
Excellent news. Now i just would like to have some more details, on how i could repeat your success.
AT+CGDCONT is not working for me - no answer from watch to this command.
Can you provide some more info. What MCC and MNC does your cellular operator has? What version of firmware do you use.
Did you actually implemented any changes to your firmware?
Which terminal software do you use? Which COM device you selected? Was DEBUG mode active?
Or what should i do to get my watch connected?
Thank you.
Hello,
EASolana said:
I have my bunny watch 2, that I have paired during a visit to Sz, and will try to add the xml file today. Hopefully we can get a connection.
Click to expand...
Click to collapse
Did you connected with a Chinese Sim card and then changed it to a foreign one?
So I first activated my device in China with a Xiaomi Sim card.
Then traveled back to Hk, and tried with Hk local China unicom, China Mobile and three Sim cards. None worked.
Then I tried the at command for setting up the Apn settings on the device. The commands would not give an OK response, so I do not know exactly which one worked.
Then rebooted the device, and it can connect with Three and China mobile cards. UNICOM still not working.
I saw the change in the file mentioned above. It changed from one operator to the other.
HK is not so far from China, so i think there could be native support for your operators.
Anyway, could you please provide other then China Mobile store_info.dat file from your FAT partition, and a ROMdump to compare. I think you have a more fresh watch firmware. Thank you
Today I'm in China so I will not be able to upload the files to a G drive location, tomorrow I should be able to upload them.
I have bought a new device today (this time the mini GPS, 6261 based) and done a backup before the network registration and after.
I can confirm that all changes are happening to the file named "store_info.dat", and all the new data is matching to the xml format you were given. But written on a low level way inside the .dat file.
The GPRS - APN settings are independent of the GSM settings. So you will need 2G settings for your local operator, be sure you are registered in the network by performing a call to your SIM Card number then modify the store_info file with your specific operator parameters. Be sure to do this on the Hex editor so file length is constant after your perform the modification.
EASolana said:
So you will need 2G settings for your local operator, be sure you are registered in the network by performing a call to your SIM Card number then modify the store_info file with your specific operator parameters. Be sure to do this on the Hex editor so file length is constant after your perform the modification.
Click to expand...
Click to collapse
I am bothered with MCC and MCC settings. All i can see in DAT file is apn for internet wap and mtp, but no readable data about cellular operator
Update: i have sniffed through the firmware again, and i got that China, Hong-Kong and Taiwan are natively supported by the watch... Probably you will get some problems with diferrent cellular operators, but all 3 MCC codes 460 466 and 454 are in firmware
If you keep looking in the firmware, just bellow the MCC codes you will actually find the APN settings. Keep searching to the bottom of the file and you will find the W. A. P... U. N.I.C.O.M... C.H.I.N.A...M.O.B.I.L.E part of the string, that means that beside replacing your MMC on the top of the file above by replacing the 460, 466, 454 codes, you also have to look toward the end of the file and replace the 460000, 454000, 46600 codes with your combination of MCC and MN settings.
Since you cannot add length to the file, remember to find an operator WAP setting that will fit in the current.
EASolana said:
460000, 454000, 46600 .
Click to expand...
Click to collapse
all of them? - i was trying all of this, except editing DAT file
Please, share your DAT file
Also please, tell me MCC and MNC of your HK cellular network, on which you have managed to make everything work (perferably for the first time with your watch)
By the way, sniffing around MTK6261 source code led me to interesting things
setting are really preinstalled
custom_config_account.c file from "Source_code_of_6261\code_6261A_L1\custom\common" gives a clue.
I think for now - i have to chose one cellular operator, and fix all it's settings to fit my needs
Yes! I did it!!!!!! Woohoo!!!!
FlamingPumpkin said:
all of them? - i was trying all of this, except editing DAT file
Please, share your DAT file
Also please, tell me MCC and MNC of your HK cellular network, on which you have managed to make everything work (perferably for the first time with your watch)
Click to expand...
Click to collapse
These are the operators that i have tried in HK.
China Mobile
Name: CMHK
APN: cmhk
MCC = 454
MNC = 12
MMSC = http://mms.hk.chinamobile.com/mms
454 07 Unicom
454 11 Hongkong Telecom
454 00 CSL
454 16 PCCW
454 06 Smartone-Vodafone
Attached is the DAT file.
Where you got the source code from?
Source_code_of_6261\code_6261A_L1\custom\comm on
EASolana said:
Where you got the source code from?
Source_code_of_6261\code_6261A_L1\custom\comm on
Click to expand...
Click to collapse
https://mega.nz/#F!JMsgDCYR!qn39qDJ5LzOz1TkUbdqvtQ
Time to sum up progress.
Activation option #1
Have your Chinese Seller activate the device using a Chinese Sim card before shipping, and this should ensure full communication in China, Hong Kong, Taiwan. (460.466.454) and possibly in the following places:
208 - France, 404 - India, 405 - India, 454 - Hong Kong, 455 - Macao, 466 - Taiwan, 502 - Malaysia, 505 - Australia, 510 - Indonesia, 515 - Philipines, 520 - Thailand, 525 - Singapore.
Given that MCC codes for several operators in those countries are included in the list inside the FW.
If you are choosing this way, you need to remember the device is only 2G - GMS 900/1800 compatible, so before you waste time, ensure you carrier is compatible. Australia has just dumpled 2G support so don't even try.
You can execute the following AT code before purchasing the SIM card, and it will tell you the carriers that the device could possibly connect: AT+COPS=?
It will reply the MCC Codes and operator name, with that information you can look for a valid unlocked and activated sim card.
Since device was activated in china it will easily go trough the regular process of scanning the QR code and adding the device to your APP.
Activation Option #2.
Modifiy the MCC parameters inside the FW and include your specific operator details.
FlammingPumpking, you can help us comment on how you succeed with activation.

Guide to avoid registering a new GSF android_id at each clean install

As you may noticed since last week google wants us, the custom rom users to manually register our android_id to the link https://www.google.com/android/uncertified/
It looks simple isn't it?
But there's a catch. Each google account can register up to 100 ids. So if you keep registering new ids after every clean install you'll more likely to hit that 100 ids limit soon. That's even worse for fhe rom developers as they may flash up to 20-30 roms a day.
I'm figuring out that in a different way though. The procedure I'm following is:
A. BEFORE ANYTHING
If you're doing this first time:
1) Copy this database from /data/data/com.google.android.gsf/databases/gservices.db
2.1) Open the database with a sql editor or from adb shell or a terminal emulator in sqlite3, see android_id with this sql command:
SELECT *
FROM main
WHERE name="android_id";
2.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "SELECT * FROM main WHERE name = \"android_id\";"'
3) Then save the value you're seeing to somewhere else, and register to your account at https://www.google.com/android/uncertified/
B. THEN FOR EVERY CLEAN INSTALL
1) Backups and wipes.
2) Flash rom (pt roms with vendors have the firmware included).
3) Flash gapps.
4) Optionally flash a custom kernel.
5) Reboot and configure your device.
6) Flash magisk, reboot.
THEN THIS PART IS IMPORTANT:
7.1) Again copy this database /data/data/com.google.android.gsf/databases/gservices.db and open in a sql editor (or with sqlite3 in terminal emulator, or adb shell) and execute this sql command:
UPDATE main
SET value=XXXXXXXXXXXXXXXXXXX
WHERE name="android_id";
7.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "UPDATE main SET value=XXXXXXXXXXXXXXXXXXX WHERE name = \"android_id\";"'
Note: XXXXXXXXXXXXXXXXXXX is your android_id as you've learned and registered to your account before (You can see the android_id s you've registered at the same google link).
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Deleted
Deleted
muff99 said:
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Click to expand...
Click to collapse
Yes that works too but this is the manual method for the gsf android_id. Wifi only devices doesn't have IMEI for example.
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
G4B33 said:
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
Click to expand...
Click to collapse
Yes so now we don't have to do that much of hacky-wacky stuff just to get gsf certified status anymore. #YayGoogle? ?
What if you don't do that?
seems not working. After rebooting, it went back to previous id
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
ccelik97 said:
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
Click to expand...
Click to collapse
I think the display will always stay on "not certified", but you are atill able to use the Google services (which unregistered custom ROM users are not any more, if I understood correctly).
This is just a guess on my side, I have not tested this (and I can't since I added all kinds of IDs to that registration page ...).
All in all the information flow from Google on this topic has been spectacularly bad, imho.
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
image45 said:
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
Click to expand...
Click to collapse
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
muff99 said:
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
Click to expand...
Click to collapse
Do I need to convert it or is that an accepted way to submit the information please?
If I try to resubmit it advises already registered.

A Noobs Guide to Verizon Galaxy Note 4 Hardware Repair,Root,Bootloader,Twrp,ROM's

A Noobs guide to Galaxy Note 4 Verizon Motherboard Hardware repair and replacement
and Other Samsung Galaxy Note 4 repair ( Att, Tmobile etc ) starting in thread 2 ( user input welcome ) ​
My Overheat Heat and flash problem issues leading to
OEM Motherboard replacement and acquiring ROOT again​
OP Note : read the whole guide or for that matter any OP​
Thanks to many XDA-Developers forums, if you are not quoted or mentioned here I will add you !!
Device : Samsung Galaxy Note 4 Verizon SM-910V this OP ONLY !!!
Code:
[COLOR=Red][B]Your warranty is now void.[/B][/COLOR]
*most likely you don't have a warranty because you broke it, ROM'd it, its old and past warranty anyway !**
So, There is no warranty anyway, not even if you did anything in this thread to it
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or your getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this guide
before flashing it! (thanks @hsbadr)
YOU are choosing to make these modifications, and if
you point the finger at anyone for messing up your device, we will laugh at you
Symptoms : ROMs not flashing/installing , crashing, High heat, low battery life on new battery hardware note working specifically fingerprint.
Problems : digging through many forums 2 years later to root and unlock the bootloader, it took DAYS
Solution: keep track of my progress and make a useful step by step NOOB guide for Everything !
Section 1: Repairs
Then the rest of the sections are for Rooting, Installing TWRP custom recovery, fixing bootloader , and installing ROMS
Section 2: Flashing via ODIN and the correct rootable OEM rom 5.1.1 on a windows PC
section 2a: Flashing via Heimdall on a Linux device --need comments
Section 3: Achieve temporary root to install bootloader fix
Section 4: Use of ADB to (windows and linux ) to copy over bootloader fix
Section 5: install TWRP custom recovery and your first rom
Section 1: Repairs
If you have to replace the motherboard, and you have any other futzy component, might as well order it at this point, your going through pretty much the same process. I am only doing the motherboard, but the cameras and USB board are right there as well on this repair
I have been running a rooted Verizon Galaxy note 4 since Cynogenmod crashed and switched to Lineageos 14 and then 15.
Here is the forum
https://forum.xda-developers.com/no...eo-8-1-0-unofficial-lineage-15-1-rom-t3760969​
After several suggestions and searches, many users hinted I may be getting a Bad internal memory,
which refuses to write anymore.
So I had to go to Walmart and buy a LG Straight talk phone to use as my daily driver,
Then I ordered a new motherboard from China, 29.00 on Aliexpress.
See OP thread #2 below!! It was not fun searching for it, but I saved $20 to $40 from buying on ebay
What I bought may not be available from this seller, but here is the link. Use a desktop browser, it will show "suggested" other devices...
Code:
[URL]https://www.aliexpress.com/item/with-Android-System-Original-unlocked-for-Samsung-Galaxy-Note-4-N910V-Motherboard-Good-Working-Free-Shipping/32802513232.html?spm=a2g0s.9042311.0.0.66e04c4dpohrQm[/URL]
When I received it , it was time to look for a repair procedure on YouTube.
Hardware needed: thin shim and 00 size phillips, AND a blank cheap SD card you don't mind losing. It may be unusable after we are done
Cell Phone repair tool kit really helps save your fingernails !
Complete note 4 teardown video:
Code:
[media=youtube]ZND9Q73wjr8[/media]
Just the Motherboard video
Code:
[media=youtube]5KpT755hNpM[/media]
In the second video, you can see the phone booting up as a test to see if you have all the connections correct.
Because it came from china, its a good idea to setup your user and
download the app CPUz before you put all the screws back in,
and check to see if you have a real or fake chipset.
Yaayyyy mine was real . Thanks Aliexpress.
Button it up and do a factory reset (it booted up set up as a no user) so I wanted a fresh install oem with my user.
Section 2: Installing the Correct rootable OEM rom so we can install Anything else.
FIRST check to see if you have the emmc brickbug or you will BRICK it !!
1. Google play store install eMMC Brickbug
If your long number starts with 15xxxxxxxxxxxxxxxxx, YOU are Golden ! if not STOP, get another board ! or you are going to waste time , and get another board !
The Galaxy Note 4 Verizon had a special custom locked bootloader installed after the 4.4.4 release to 5.0.1 and made it very difficult to get
root access to your device.
I saw the notice
DON'T UPDATE YOUR BOOTLOADER TO ANYTHING AFTER THE LATEST BUILD AS OF 4/19/16
warning about a week to late. So I finished out my 2 year contract and watched the forums.
Seriously noobs, don't update your new motherboard ...
The rom pre-installed on my replacement motherboard was already setup booted to a running 5.0.1 oem rom, I could not root it.. with any method I remember downgrading my 6.x.x to 5.1.1 in one of the many forums listed here at XDA
This one was the one I used back then, and It turned out that is where I started..
Only a Verizon Samsung Galaxy note 4 Developer Edition has the ability to install custom roms, and most likely the motherboard you bought or have is NOT a developer edition
IF you have a eMMC that starts with 15 we can reprogram it a developer edition
Thanks to @hsbadr
Here are most of the downloads we need:
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
2. Download Odin, Download TWRP, and Samsung_unlock_n4-fix
3. On your windows PC, create a folder c:/Odin and extract the Odin zip file there, and copy the TWRP image there
4. Download the following OEM root able ROM to your c:/Odin folder
Code:
[URL]https://forum.xda-developers.com/devdb/project/dl/?id=18880[/URL]
5. Plug your phone into a USB port on your Windows PC
6. Install the necessary drivers if they don't automatically install from Samsung
Code:
[URL]https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows[/URL]
7. Set up your phone for flashing ROM and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Power Off phone
Enter Download Mode - press and hold in this order <down arrow> <home> <power> until screen comes on. release buttons.
press up arrow to enter download mode
8. Open windows explorer and go to your c:/Odin folder. You should have an odin exe file, and the twrp file, and the large rom file.
a. right click odin exe and open as administrator
b. check to see if your connected to your phone. you should see a blue box in upper left with a com under it.
If you unplug your phone, you should hear the disconnect notice and the com and blue bar will go off, and when you connect, the com and blue bar and reconnect noise should appear.
9. click the AP button box, select the ROM file that you downloaded above.
NOTE : this ROM will disable WIFI so you wont be able to use the play store unless you have cellular connection.
you will have to transfer other files via usb cable !
Click start, do not unplug! until it stops.
10. Device will reboot. Remove cable, and battery before boot completes
11. Enter recovery mode . Press in order ,<volume up><home><power>
wait for the little android dude to do his thing, then there will be a menu. select factory reset, and reset and let it reboot
Set up minimal user or as a new phone with no user and check the settings in step 7
Set up your phone for flashing roms and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Yayy, you now have a rootable device
Section 3 Achieve temporary root to install bootloader fix
In my try to obtain temporary root, I tried every method in all the forums ( go ahead and look and try )
The only 2 programs that reported to work is Kingroot, and Kingoroot. These are APK's that are NOT in the play store
you will have to download them and install them as unknown sources. I was only able to install kingroot . Kingoroot apk would not install
in both my 5.0.1 original on my motherboard, as well as what we just installed 5.1.1 I was unsucessful at obtaining root with these programs
Then I remembered Kingoroot has a windows version that installs on the PC <dangerous dont install yet>
On your PC you will need AVG antivirus to catch the malware ( other antivirus may work but this is what I had ) my PC is windows 7 ultimate
Advanced Users only :Recommend running a virtual machine with windows so as to keep your PC completely malware free. just delete the VM after this process !
This section you will need on your Note 4 from the Play Store : root checker
You will need a throw away SD card
You will need read through section 4 and 5 and get all files and programs there ready to install use and or transfer
0.5 update your AVG
1. With AVG installed on my PC, and my phone connected as a mtp with usb I downloaded and installed Kingoroot for windows.
https://www.kingoapp.com/
NOTE after not being able to install forum recommended kingoroot apk's i dint want wast time install the newest kingoroot apk from the website. Maybe it will work for you. If you do get kingoroot apk to work on your Note 4 let me know.
2. In the install process for kingoroot windows version AVG will quarantine a file.
there will be a couple popups .. close them
when its installed it will open and start talking to your phone.
3. press the root button.
It will take 30 sec to a minute to install some files on your phone and achieve root, there will be a new floating toolbar on the phone. root will disappear after a reboot, but not the resident programs this root is pretty stable, but i was not able to install SuperSUME (paid version ) as recommended in a XDA guide to obtain permanent root for this 5.1.1 rom. If your successful with super SUme with this let me know.
4. Open root checker to verify ! yayy.
5. Cleanup instructions when finished with this guide below
Section 4: Use of ADB to (windows and Linux ) to copy over bootloader fix
1. Your Note4 phone should be running with root, make sure phone is connected
Explanation : ADB is a Google provided tool for the android platform. It communicates with your phones operating system , transfers files , and actuates programs remotely in the background. totally necessary for development of ROM's, TWRP, and programs for every android device
You may or may not know that your android device is running a Linux kernel, with some Linux programs, with custom folders and custom files and settings, and the touch screen is the GUI graphical user interface touch input.
ADB is a command line user interface, when you turned this on in Developer settings, the kernel is listening constantly on the USB com port and some times on the WiFi com port for commands. if you don't need it turn it off, it could be a security hole, but we need it on.
It works great on windows, mac, or Linux varieties
2. Install on your computer
Code:
[URL]https://developer.android.com/studio/releases/platform-tools[/URL]
If you have linux, your distribution may have a package you can install from your distribution. Then it will be in your path as a command
3. Windows users , extract or install into c:/ADB and add that to your PATH variable if you want to use it all the time as a command
4. Open a command prompt window (search command or cmd , right click open as administrator)
5. If you have ADB folder in your path or are running Linux change directories to the folder where you downloaded the Samsung n4 fix file
6. You should still have root
type
Code:
adb devices
The ADB daemon ( little server program ) will start and return some information.
your phone will have a popup screen and should ask for permission, click allow
again type
Code:
adb devices
7. You should see something like this
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device.
If you see something listed like the above adb is working. Now on to the next command to move the Samsung_unlock_n4-fix to the phone.
type dir ( or ls -al for Linux users ) to verify Samsung_unlock_n4-fix is in your directory
8. Send Unlocker to Phone with adb
Type or copy and paste the following command:
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/
You should see successful output .
If you don't, check your PATH, check if your in the right folder, or make sure samsung_unlock_n4-fix is in your adb folder
9. Activate the unlocker. This requires root and a reboot. After the reboot you have to go and reactivate root in Section 3.3 above
type the following
Code:
adb shell
Congratulations you are now looking at the linux command line interface on your phone . the $ prompt means you are in the shell
10. activate superuser mode ( kind of like administrator in windows but more powerful )
type
Code:
su
then press enter key
YOU SHOUD NOW SEE a # prompt
This means you succeed in root. If you dont see a # you missed a step above somewhere , or your root was unstable and took too long to get to this point,that is why I said read thru this section and get ready..
Ok at this point we have the file we needed transfered, we have root, now we need to upgrade the permissions on the file so #root level of the operating system can use it !
The next command does all that then executes the command to upgrade your phone to developer edition !
Copy and paste the following command series and press enter.the && joins each command
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
The device will reboot and flash the developer code.
You should see some sort of progress in the window.
When done ,unplug the cable and pull the battery to shut down phone.
11. Make sure you have a cheap throwaway SD card installed !
One More Time to unlock the boot loader !! section 3 and 4 short version
Put the battery and cable back in and turn the phone back on and make sure its plugged in your PC.
Now repeat the kingoroot PC to gain temp root
open a command prompt or shell
type or copy paste the following to verify its connected
Code:
adb devices
transfer the fix
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/ && a
open the shell on your phone
Code:
adb shell
gain super user rights
Code:
su
unlock the boot loader
same command series
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
You will see your phone do a series of outputs then reboot. when it reboots, disconnect the cable.
If this step is sucessful your phone will keep rebooting. This is NORMAL . after the first or second reboot, pull the battery and pull the sd card, and set the sdcard aside. It will need to be thrown out or repartititioned to be usable. or you can keep it as a memento on your charm bracelet.
Your bootloader is NOW UNLOCKED . keep phone off until you read the next section
Section 5a: install TWRP custom recovery
Currently right now you have 5.1.1 installed with some Chinese malware on your phone and PC,
A custom developer edition and an unlocked boot loader. Lets fix them all.
Turn on phone download mode . <down volume><home><power> then volume up to enter download mode
Open Odin again ( see above )
Connect phone ( look for com and blue bar )
Select AP button, and browse to TWRP file
Press start. when finished phone will restart.
Don't let it boot all the way back up! , pull battery, and install good SD card, and if you read this section you downloaded what you needed for a new ROM onto your sdcard
Turn off the automatic rebooting in the custom tab, DO NOT select the PIT tab
Press start
Once it finishes it will say Success or FAILED
IF it says FAILED start the whole process over! you didn't unlock the bootloader !
If success, Power off the phone with the pull battery method and disconnect your cable
Press and hold these buttons immediately to enter TWRP ,
<volume up> <home> <power>.
Swipe to allow changes in TWRP.
Select backup , change to SD card, You can also plug in a memory device into the USB port. If it sees it you will be able to use that for backup space
BACKUP everything . You now have a custom recovery installed, a unlocked bootloader, and a rootable ROM Backed UP !
If you feel you want to do this all over again if you flash the OEM Samsung ROM via Odin by accident like I did, ha ha skip the next steps
Select the backup button, select all the partitions, select the source, where you want to store it.
Name the backup rooted-backup-everything-5.1.1
Select start and go make some coffee or a sandwich. its about 4 gigabytes compression, so it may take about 5 to 10 minutes
Clean up -
uninstall windows kingoroot PC and do a virus check
check for hidden folders and registry entries
Section 5b. Install your first ROM
Cleanup : After your backup WIPE your phone twice
THIS IS TO guarantee, no Kingoroot or kingroot stuff is in the phone !!!
WIPE IT TWICE !!!
Some guides (listed below ) say to adb sideload over a root file , then install an older rom. I haven tried this. Let me know if you did and are successful.
Whatever ROM you use, please post a success story in the reply's. I am interested in how you all do.
I have tried every note 4 ROM and this is the most succesful for me and most stable
I have been using this ROM for a while, and the lineageos 14 version too
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
In most all ROMS, you can update the bootloader (TWRP) by TWRP app if rooted
you can update the modem ( a partition that contains original Samsung code to run the cell and wireless ) via ODIN
Roms and patches and other goodies can be installed via TWRP by downloading to your device or transfering them to your sd card
Oem ROMS must be installed via ODIN, and will WIPE all you just accomplished. so unless your selling your device, or giving it to grandma DONT.
If you copied the rom ( usually a zip file ) and the necessary files, and have upgraded your bootloader and modem to the newest,
Now install your ROM, and after your initial setup, come back to TWRP and do a full backup !
every time you try a new rom, and get it set up, do a backup. that way you can switch and test to your hearts desire till you run out of SD memory.
The cool thing is you can backup to an external memory device ! more room !
Follow the directions in the OP of your ROM to install. Enjoy
All the above info was gleaned from the following pages
Thanks to @beaups for discovering exploit !!!
Thanks to @hsbadr [HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910VVRU2CQL1]
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144[/URL]
and his files
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
Thanks to @ryanbg [Official] Note 4 Verizon Bootloader Unlock
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913[/URL]
and @urgodfather
Code:
[URL]https://forum.xda-developers.com/showpost.php?p=66381707&postcount=342[/URL]
Thanks to @chriskader [HOWTO] Converting your Retail Note 4 to a Developer Edition Note 4
and @Mickey387 for discovering how to compile the note 4 32bit hardware drivers into Oreo !!
and @_mone @ripee
for maintaining and working hard on
[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][trlteduos]
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
some of this was also posted on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked
Update:
Looking for a motherboard for a 910 that's not a v?
Thanks to user @maralexbar I need to update some info
Method 1 use eBay. Find your correct motherboard easily.
Method 2. Save some money use Ali Express ( China )
If you use Ali, and don't find your motherboard on a direct search, keep digging.
I forgot to mention this.
Looking for my Verizon motherboard, I found lots of parts like the USB internal connector etc. But no mobo. I had to go thru the store listing of the seller of the USB connector to find a vendor that had a mobo. Then I tried comparing different vendors. So do some digging. There is a billion people on Ali express selling stuff. Don't give up.
Plus Ali wants happy international buyers. So if you get a bogus item, you get your money back.
reserved #2
reserved #2
reserved #3
Reserved #3
reserved #4
Reserved #4
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
b1ggjoe said:
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
Click to expand...
Click to collapse
Your more than welcome
Announcement:
Thanks to @ripee
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.

Categories

Resources