N8000 RADIO Baseband firmware collection - Support N8000 - Share your baseband!

N8000 RADIO Baseband firmware collection - Support N8000 - Share your baseband! - Galaxy Note 10.1 General

I'm starting a N8000 RADIO collection because we're having discrepancies where WiFi works on N8000 for certain ROMs for some people, but not others.
N8000 Baseband Google Drive folder
Here is a current list of Basebands in the Google Drive folder
VERSION Original Stock ROM Comment
N8000XXUDNH1 (South Africa Vodafone Android 4.4 ROM) WiFi works on @TheMorpheus Android 5.0.2 but no @lirokoa ROM's (or derivatives)
Share your baseband and help us all develop better N8000 ROMs
You will find your baseband version in Settings > About > Baseband.
If you have a N8000 with a baseband not listed above, please upload it to https://uploadfiles.io/ or a similar free filesharing site and I'll try add it to the Google Drive (so it'll be available permanently) in a timely manner.
How to dump your N8000's Baseband
You need to run a command as root on your device. I find the quickest, most convenient way is with `adb shell` and `adb pull ...`. But you could do it in a root terminal on the device and upload it from the device also.
Here are detailed instructions for doing it with ADB shell and pull (replace XXXXXXXXX with your baseband version)
1. Enable Dev Options: Go to settings > About > Software info > Tap build number 9x until Developer options is enabled.
2. Enable ADB as Root: In Settings > Developer options: Enable ADB and root over ADB
3. cd /tmp/
4. adb shell
su
dd if=/dev/block/platform/dw_mmc/by-name/RADIO of=/data/XXXXXXXXX.radio
exit
5. adb pull /data/XXXXXXXXX.radio
6. Upload XXXXXXXXX.radio for free at https://uploadfiles.io/
7. Post here
Share the link here with the basic info as per this example mentioning the latest/best ROM (in your opinion) that your device works with:
XXXXXXXXX (?Country? ?Network? Android ? ROM) WiFi works on Android ?version? ?romname? ##.# by @foo
Thank you for contributing to the N8000 community and facilitating new ROM development.

Details of WiFi issues on @lirokoa ROM's (and derivatives)
https://forum.xda-developers.com/ga...ent/rom-lineageos-14-1-nougat-t3884079/page40
In a nutshell: Not working on WPA2-PSK(AES) networks.
Although some N8000's work fine. So I'm hoping it's just a matter of swapping the Baseband.

Reserved 2

Google Drive folder is empty (?)

Related

Regulatory domain, Wifi channels 12 and 13

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.

[OFFICIAL] Japanese SGS III (SC-03E) Rooting, ROMs, Kernels & Guides

DISCLAIMER: You will be flashing your phone at your own risk. You are solely responsible for anything you do to your phone, so make sure you are well informed and well prepared before deciding to flash or install anything on your device.
The purpose of this thread is to provide a 'reference site' for anything related to ROMs and kernels, be it original stock, modified stock or custom images for the Samsung Galaxy S III Japanese versions, starting with model SC-03E.
All comments and feedback are welcome and appreciated.
Reminders:
After flashing a new ROM image, it is highly recommended to perform a cache wipe and factory reset. Please avoid posting about problems repeatedly which can be easily solved by this procedure.
If you find that someone has been helpful in assisting you, then please do not shy away from hitting the THANKS button below their post; this is the preferred action instead of creating a new post just to show your gratitude
BEFORE ASKING HOW TO DO SOMETHING, READ THIS GUIDE
Some questions are being asked over and over again in this thread without bothering to read through it or looking for the answer here in the OP. Especially for the 'lazy' ones among us, we'll attempt to make a new and fresh, additional, reference pointer right here at the top of the very first post. Please consider taking a look at @lparryU's guide BEFORE posting your next question.
"How-to: Root, Unlock, Enable Osaifu Keitai/Felica, CWM, cook & flash custom ROM for SC-03E"
PIT File
Use this PIT file when flashing with Odin, and ONLY if you have scr*wed up your default partitioning scheme due to specifying an incorrect one during a previous flash. Normally there is NO NEED to specify a PIT file when flashing with Odin!
m3.pit (SC-03E)
Factory Firmware (stock)
samsung-updates.com and www.sammobile.com host some of the stock images.
Due to hotfile.com's demise, and my limited storage and bandwidth resources in my mediafire subscription, stock images will be available on demand only. Sorry for the inconvenience.
Pre Rooted stock ROMs
(Flashing the following ROM components will trigger the custom binary counter)
All the rooters contain a sample debloat script as well. it is located in the file /preload/Proxyme/debloat.sample. If your /sdcard already has an older debloat script in /sdcard/Proxyme/debloat.sh, it will not be overwritten by the rooter (in case you made changes to it for an older rom). So to be sure of using the most recent script for the targeted version of the firmware check the version in the /preload/Proxyme location. As a reminder, you can execute the debloat script (or any other one) from within Proxyme WITHOUT enabling SU, because it will always run in an environment with elevated privileges.
Jelly Bean 4.3
SC03EOMUBNH2 (Proxyme) (Build Date 2014-08-19)
This zip archive contains an Odin flashable file. It is not the complete stock image, so you MUST have OMUBNH2 already running on your phone or you will need to download it from the above reference sites, which carry complete stock firmware images, and flash it before continuing with this file. Instructions are included.
mediafire
uploaded.net
torrent, mirror2
(Flashing these ROMs will NOT trigger the custom binary counter)
Jelly Bean 4.3
XXUENE4 GT-I9305 Based (Proxyme) (Build Date 2014-05-16)
This image will clear data/cache implicitly upon initial boot, so backup your stuff before flashing
This one includes the Samsung Chinese IME with support for full screen handwriting and the QUERTY layout with extra row of numerical keys at the top
torrent, mirror1, mirror2
mega.co.nz
uploaded.net
SC03EOMUBND2 (Proxyme) (Build Date 2014-04-02)
This image will not clear data, but please consider wiping data/cache manually before posting about issues not related to Proxyme
mega.co.nz
torrent, mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
SC03EOMUBND2_PROXYME20140419.z01
SC03EOMUBND2_PROXYME20140419.zip
Jelly Bean 4.1.2
MI4 GT-I9305(TGY) Based (Build Date 2013-09-26)
Rooting instructions are displayed in RootInfo app
Wipe Data/Cache if you are experiencing problems.
Display Languages: English(UK/US), Chinese(Trad/Simpl) and Korean
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg;zh_CN)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
MR8 GT-I9305(TNL) Based (Build Date 2013-09-26)
Rooting instructions are displayed in RootInfo app
Wipe Data/Cache if you are experiencing problems.
Display Languages: (en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU;sk_SK; sl_SI; uk_UA; uz_UZ; az_AZ; hy_AM; ka_GE; es_US; pt_BR; ar_AE;zh_CN;zh_TW;ja_JP)
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
MG3 GT-I9305(SFR) Based (Build Date 2013-07-31)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
Data and cache are wiped, so backup your data prior to flashing with Odin.
Display Languages: (en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU;sk_SK; sl_SI; uk_UA; uz_UZ;az_AZ; hy_AM; ka_GE;es_US; pt_BR; ar_AE)
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
Jelly Bean 4.1.1
SC03EOMAMJ4 ( 2013-10-18 )
Depending on what's running on your phone currently, you may have to consider performing a manual factory reset and wipe the cache and data partitions.
Rooting Instructions:
Default state is - not rooted - Proxyme has been included in this rom,
Proxyme offers live su binary control, and without the need to 'root' the phone, you have...
- SSH server with virtually unlimited user accounts, configurable with specific UID, GID, home directory and shell,
- execution of scripts with elevated privileges (sample debloating script included),
- tag along scripts for root ON and root OFF actions,
- busybox switch
(Unpack the .tar.md5 file from any one of the following zip archive and flash with Odin)
torrent - full stock root ready (Proxyme)
Uploaded.net - full stock root ready (Proxyme)
MF1 (Build Date 2013-06-10)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
mediafire (unpack tar.md5 file from this multi-part zip archive and flash with Odin)
MC3 (Build Date 2013-03-18)
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
MB1 (Build Date 2013-02-08)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
Chainfire's SuperSU has been included for your convenience.
hotfile - link dead (unpack tar.md5 file from this zip archive and flash with Odin)
.
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
MA6 (Build Date 2013-01-24)
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
Custom ROMs
(Flashing these ROMs COULD (and usually will) trigger the custom counter)
Probam Rom
Go to this post... and this post... Courtesy @sasbudi
Slimbean 4.3 NTT Docomo SC-03E
Go to this post... Courtesy @majidkhan
Carbon 4.2.2 for NTT Docomo SC-03E
http://forum.xda-developers.com/showpost.php?p=45164630&postcount=550 Courtesy @majidkhan
PACman (Paranoid AOKP CyanogenMod) 4.2.2
http://forum.xda-developers.com/showpost.php?p=43996579&postcount=489 Courtesy @Edgrr000
CyanogenMod
Instructions for flashing CM10.1 Courtesy @lparryU
Getting CM10 to work on SC-03E with Osaifu-keitai... Courtesy @FlyingFlipFlop and @lparryU
http://forum.xda-developers.com/showpost.php?p=42076531&postcount=313
http://forum.xda-developers.com/showpost.php?p=42076531&postcount=302
http://forum.xda-developers.com/showpost.php?p=42094976&postcount=303
rXTREME.v10.0
Link to post Courtesy @Edgrr000
KBC Developers github wiki
Contains everything everyone in here needs, Samsung custom kernel, with visible hidden partition for using triangle away on stock rooted,
and having all Japanese things working too. And the cm10.1 links. Its in Japanese but easily translated. (courtesy of @Robobob1221)
https://github.com/kbc-developers/release/wiki
Paranoid Android (GT-I9305)
Link to post Courtesy @Edgrr000
Misc
How to Convert ROMs for the SC-03E By @DroidZombie
Japanized Rom Tool By @LeathSeraph
http://lt.imobile.com.cn/forum.php?mod=viewthread&tid=10282917
Hints & Tips
Follow this trail...

SC-03E Hints & Tips
Hints & Tips
Guides.. with several links and specifically for unlocking your phone with the proper ROM (has the LK5 modem which is the go to for unlocking and working with other carriers), and instructions to do just about everything you need to get done with this phone
How to Convert ROMs for the SC-03E (By @DroidZombie)
Instructions for flashing CyanogenMod ROMs (By @lparryU)
Unlocking
Unlocking Guide - Courtesy of XDA member @majin
Yet Another Unlocking Guide
Custom Binary Counter
.Reset Guide .By @majin
Tethering
Tethering Guide By @majin
How to change Tethering preset APN By @majin
Change Roaming Status
Reference post By @majin
Proxyme Rooting
Proxyme Guide
Fixing Lost IMEI
How to repair your SC-03E's IMEI number and restore its network connection
Miscellaneous
SC-03E Dial Pad Codes

SC-03E Docomo S3 LTE - Just Another Unlocking Guide
This (sim) unlocking guide has been primarily inspired by the very comprehensive guide initially written and posted by @majin in his post.
WARNING: This unlock procedure will automatically wipe the phone's cache and data partitions, effectively performing a factory reset; you are strongly advised to backup your data prior to executing this guide.
Prerequisites:
Windows PC running Odin3 in an administrator account (tested with Odin3 v3.07)
USB cable to connect phone to PC (preferably original cable for reliability)
Internet access to download firmware image(s)
Google account to access Play Store
The following list outlines the required steps in order to successfully unlock your SC-03E:
If you have data on the phone, which is of any importance to you, then I highly recommend that you make appropriate backups first
If present, remove the sim card and sdcard (there's no need to have a Docomo sim card for this procedure to work)
Download this stock firmware image, which is based on MB1 and includes the appropriate modem component to assist in wiping the NV stored network locking data structures. In addition, this firmware image is root-ready; meaning that you can toggle root mode by pressing VolumeUp/VolumeDown/Power button combination briefly to switch modes.
Initiate Odin Download mode on the SC-03E (Turn the phone off, then simultaneously press VolumeDown/Home/Power buttons until the Download Mode splash screen appears and requires you to press VolumeUp to continue or VolumeDown to cancel if you find yourself suddenly struck by an overwhelming feeling of stage-fright)
Unpack the SC03EOMAMB1_LK5MDM.tar.md5 firmware image from the above-mentioned/downloaded zip archive and flash the file with Odin3 (specify the image file in Odin's PDA section)
As soon as Odin completes the flashing process, it will instruct the phone to reset; be patient while the phone starts up, because it will require more time to setup and configure itself after a factory reset.
If you have reached this step, then we're assuming the phone has booted successfully and you are presented with the configuration wizard. You need to at least enter your Google account credentials in order to access the Play Store.
Install the (free) ServiceMode Shortcut app (author: KABASOFT) from the Play Store.
Another (paid) option is the ShowServiceMode For Galaxy LTE app (author: Jaken's Laboratory).
Start the service mode app and tap the ServiceMode option, which will in turn fire up the ServiceMode main menu
Select [1]UMTS->[1]DEBUG SCREEN->[8]PHONE CONTROL->[6]NETWORK LOCK->[3]PERSO SHA256 OFF
Now use the phone's android menu soft button to select Back in the popup menu to return to the NETWORK LOCK menu
Tap [4]NW LOCK NV DATA INITIALLIZ and wait for about a minute before returning to the NETWORK LOCK menu; when you tap this option again, it should state PERSO_NV_INIT is SUCCESSFUL
You may now power off the phone to insert a sim card from your favorite telco operator and restart the phone
From this point onward, it is possible to flash any other firmware image without affecting the unlocked state
Enjoy!

SC-03E Dial Pad Codes
This list is most probably not complete. Please post or send a PM if you know about codes not listed here, your input will be highly appreciated!
*#0*# ........................... Hardware Testing
*#06# .......................... Show IMEI number
*#0011# ....................... GSM Status Information
*#0228# ....................... Battery Status
*#0782# ....................... RTCTimeRead (Show Time)
*#1111# ....................... ServiceMode - READ FTA SW VERSION
*#1234# ....................... Show Software Version
*#2222# ....................... ServiceMode - READ FTA HW VERSION
*#2663# ....................... Touch Screen/Key Firmware Update
*#7284# ....................... PhoneUtil - UART & USB Configuration
*#7353# ....................... Quick Test
*#7594# ....................... Factory Mode - Shutdown Configuration
*#9090# ....................... ServiceMode - DIAG CONFIG
*#9900# ....................... SysDump
*#34971539# ................ Camera Firmware Check

IMEI Repair Procedure
How to repair your SC-03E's IMEI number and restore its network connection.
Keywords: IMEI: null/null Unknown + Baseband: Unknown + no connection with QPST + no IMEI backup + phone signal lost
Disclaimer
This procedure is intended to be applied in a last resort scenario only. You must check thoroughly what the actual cause is for your phone having lost its imei number. It may very well be merely due to an incompatibility issue between the baseband code and the efs version, and thus easily fixed by flashing a proper modem component. Writing to partitions in your phone's internal storage device, re-partitioning it, flashing with the Odin tool or operating the QPST Qualcomm engineering tool carries many risks, which include hard-bricking the phone. You are solely responsible for anything you do to your phone and by carrying out the steps detailed in this procedure, you are agreeing to accept all responsibility for any and all outcome of the procedure, even if you end up with an expensive door-stop.
Try This First
Before panicking and diving into this procedure to perform all of its steps, note that your specific problem/case might not require such an extensive procedure. There could very well be a much simpler solution for your case, so I strongly advise you to put some effort into diagnosing your problem properly (best as you can given the resources you have at your disposal) BEFORE continuing.
I will be adding topics to this section based on the feedback we get, which will hopefully help everyone to improve diagnostics and find out if there are quicker/better way to solve any specific case.
BASEBAND UNKNOWN (Courtesy of @majin)
About the devices with "BASEBAND UNKNOWN" not recognized by QSPT, for first users should try with one of these:
1) enter *#9090# and check if "[2] DM/DUN over HSIC (*)" is selected, then to try to use QSPT to fix/restore the IMEI/EFS-folder, (if users have some old working backup too).
3) Try to use EFS Professional Suite to restore the right permissions on the NV files.
4) Use "Qualcomm NV Tools" (included in "EFS Professional Suite") to write directly their IMEI and to do some other test.
If they can't anything of that, then they really need to make all the "Chinese steps".
Click to expand...
Click to collapse
Introduction
This procedure is based on the following two posts, which are identical content-wise, and may be from the same individual. Credit goes to user xt890612 of forum site bbs.shendu.com and user softbank_1001 of forum site bbs.91dongji.com. Special thanks to xda member @majin for the find/input/feedback and having tested the procedure on his SC-03E.
- bbs.91dongji.com
- bbs.shendu.com
The issues we will attempt to resolve are:
IMEI corrupt or 0
Baseband Unknown status
QPST does not recognize the phone
What to Expect
If the procedure has been followed correctly and applied successfully, then take note of the following points.
IMEI restored
Network connection restored
Device serial number not the same as your original one (we will try to resolve this in the future)
No SIM network lock (Do not apply this procedure if you only want to SIM unlock a device with no issues)
You should be feeling happy, so please lookup the sources mentioned above and thank them
Preparations & Prerequisites
You will need the following tools and files, so please check each item in the list below and make sure you have them ready before commencing with the first step of the procedure.
An SC-03E which can at the very least boot into Odin Download Mode (soft-bricked). If the bootloader is corrupt, you will need some kind of JTAG service to revive the phone, because this procedure will not help your case.
Windows PC
Odin v3 (preferably Odin3 v3.09 or v3.07) - Google is your best friend
Google QPST.2.7.378.zip and download this Qualcomm engineering tool. Install it on the PC.
ADB tool/program. ADB, Android Debug Bridge, is included with Google’s Android SDK.
Hex editor. Google 'Hex editor' and download your preferred or favourite variant. Try HexEdit.exe.
Download SC-03E_IMEI-REPAIR.ZIP (mirror, torrent) and unpack the files in this archive to a work directory
Download one of the pre-rooted or root ready rom images, which are still functional/bootable on your phone, from the OP/reference post (this item is only required if your phone does not boot into Android at all, even after resetting it, and is not rooted)
Step 1 - Flash a Bootable Rooted ROM Image
If your phone currently has firmware, which boots properly and can give you root access, then skip this step. If not, then use Odin to flash the rooted image you have downloaded earlier. Consider resetting the phone afterwards by entering recovery mode to clear data and cache.
Step 2 - Enable USB Debugging
Enable USB debugging by setting the checkmark in the following option in settings:
Settings->Developer options->USB Debugging
Step 3 - Connect the Phone
If necessary, wait for all PC drivers to install and initialize.
Step 4 - Prepare Phone Internal Storage
Copy all 15 mmcblk* files, which were unpacked from the SC-03E_IMEI-REPAIR.ZIP zip archive earlier, to the phone's internal sd card after connecting it to the PC. The files must be located in the root of folder /sdcard.
It is important that you consider verifying data integrity of the mmcblk* files you have copied to the phone. Root Browser is recommended and can assist in this process. The following list consists of the MD5 checksums generated for the files in the SC-03E_IMEI-REPAIR.ZIP zip archive.
b5cfa9d6c8febd618f91ac2843d50a1c *mmcblk0p1
30fd6dfc09a70c8bcf345dc8c9e2781a *mmcblk0p10
c71fb4dfba643299159b97c6065fdb54 *mmcblk0p11
95557d70252c9b0af3f95a2244cd93ab *mmcblk0p12
e35b35efb73dd8320bdae08ec463372c *mmcblk0p13
31bc9037b092df1abbcf7550938d553d *mmcblk0p14
96995b58d4cbf6aaa9041b4f00c7f6ae *mmcblk0p15
b5cfa9d6c8febd618f91ac2843d50a1c *mmcblk0p2
dbad1316e91f5dcf0b89ad3e456f3bf8 *mmcblk0p3
713a67b9605c02f6cdd0346dfa1cab1e *mmcblk0p4
130715b90924c2394e1acd758059dd90 *mmcblk0p5
4029a1de061c375547aa3096a14562dc *mmcblk0p6
67bb0d7fbec2e250c5e2bd75dd9816f3 *mmcblk0p7
9e4a4230f51545ffd352cb7988f4bc9f *mmcblk0p8
edc27dbf0cc8b29df3ba31e21b552a98 *mmcblk0p9
4459508535b3c064f6afc6d1c6119b9e *sc03e.qcn
Step 5 - ADB
Now open a cmd window and start the ADB tool by typing the following command at the cmd prompt, followed by the enter key. In many cases, you will first have to cd (change directory) to the directory where the adb.exe program is located (hint, if you've installed the Android SDK, look for the location where it was installed and search its subdirectories for adb.exe):
>adb shell
If the shell in the adb session starts successfully, the following prompt is presented:
[email protected]:/ $
Type su followed by the enter key to get root access. If the $ sign in the prompt does not change in a # sign, then you have no access to root and you should revert back to step 1 to make sure you have a rooted firmware image on the phone.
[email protected]:/ $su <enter>
[email protected]:/ #
Step 6 - Restore Partitions
This step must be taken with great caution. You will be directly writing to partitions in the internal storage device and a mistake can end in disaster. Copy the following lines, each terminated by the enter key to initiate the command. Note that the lines with mmcblk0p10 to p14 can take a long (5 minutes or more) time to complete, so be patient.
dd if=/sdcard/mmcblk0p1 of=/dev/block/mmcblk0p1 <enter>
dd if=/sdcard/mmcblk0p2 of=/dev/block/mmcblk0p2 <enter>
dd if=/sdcard/mmcblk0p3 of=/dev/block/mmcblk0p3 <enter>
dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 <enter>
dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5 <enter>
dd if=/sdcard/mmcblk0p6 of=/dev/block/mmcblk0p6 <enter>
dd if=/sdcard/mmcblk0p7 of=/dev/block/mmcblk0p7 <enter>
dd if=/sdcard/mmcblk0p8 of=/dev/block/mmcblk0p8 <enter>
dd if=/sdcard/mmcblk0p9 of=/dev/block/mmcblk0p9 <enter>
dd if=/sdcard/mmcblk0p10 of=/dev/block/mmcblk0p10 <enter>
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11 <enter>
dd if=/sdcard/mmcblk0p12 of=/dev/block/mmcblk0p12 <enter>
dd if=/sdcard/mmcblk0p13 of=/dev/block/mmcblk0p13 <enter>
dd if=/sdcard/mmcblk0p14 of=/dev/block/mmcblk0p14 <enter>
dd if=/sdcard/mmcblk0p15 of=/dev/block/mmcblk0p15 <enter>
Close the cmd window and restart the phone. If the phone does not boot into Android (could be bootlooping due to incompatible data elements), then perform a reset in recovery mode by wiping data and cache.
At this point you should confirm that the baseband has been restored in settings.
Step 7 - Restoring IMEI
Get ready to make changes to the sc03e.qcn file, which was unpacked from the
SC-03E_IMEI-REPAIR.ZIP zip archive earlier, using the hex editor.
Load the sc03e.qcn file in a hex editor and search for the following hexadecimal byte value sequence:
08 0A 21 43 65 87 09 21 43
The file contains two instances of the sequence as is shown above. Both sequences must be changed to your IMEI number and the way it is done is outlined below.
Note that when searching for the above sequence, in most hex editors you are supposed to also specify the search type, whether it be a text search or byte (binary search. You want the latter type.
Start with looking up your device's IMEI number. It is printed on the label in the battery compartment and on a label or sticker on the original box, if you still have it. The IMEI number consists of 15 digits, so please write it on a sheet of paper in order to help you visually 'construct' a hexadecimal sequence, which in turn can be used to update both instances of the abovementioned sequence in the file. This sequence has three fixed nibble values, which must remain unchanged in the final sequence. The following sample shows x's in the sequence which represent the part to be initialised to your IMEI number. The fixed (constant) parts are the 08 and the A in xA.
08 xA xx xx xx xx xx xx xx
In order to correctly fit your 15 digit IMEI number into the sequence, use the following guide to construct it. Here, we use the dummy IMEI number 012345678901234 for reference only.
...0..12.34.56.78.90.12.34 (IMEI number to convert)
08.0A.21.43.65.87.09.21.43 (byte sequence to be constructed)
As you can see, the first digit of the IMEI number is paired with the A of the second byte in the sequence; it is placed left of the A, thus becoming the most significant nibble of the byte. The remaining digits are paired to form 7 groups in order, where each pair's digits are swapped as is shown above.
When you have finished changing the two instances of the search sequence to reflect your IMEI number, save the sc03e.qcn file, exit from the hex editor and move on to the next step.
Step 8 - Restore Configuration From QCN File
Enter the following string in the stock phone dialpad:
*#7284#
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Immediately after entering the trailing # sign, as is shown in the above image, the service mode screen shown in the next image will appear.
Tap on the Qualcomm USB Settings button to display the list of USB options you can choose from. This is shown in the next image.
Select the RNDIS + DM + MODEM option followed by tapping the OK button to return to the previous screen. Now use the back button to return to the dialpad.
Next, enter the following string in the stock phone dialpad to enter the DIAG CONFIG service mode screen:
*#9090#
Immediately after entering the trailing # sign, as is shown in the above image, the service mode screen shown in the next image will appear.
Select the [2]DM/DUN over HSIC (*) option. Note that the phone will immediately reboot as soon as you tap on this option in order for it to take effect.
Let's start the QPST Configuration program in Windows and select the Ports tab to add the new port, which has been assigned to the phone's USB communication protocol. Make sure to select the port with label USB/QC Diagnostic before clicking on the OK button.
If the port has been correctly initialised and selected, SURF9615 (0) should be displayed in the Phone column of the Ports tab, as is shown in the image below.
Finally, select the Start Clients menu and navigate to the QPST Software Download item to start its corresponding program.
In the QPST Software Download program, select the Restore tab and then specify the path to the qcn file which you have edited earlier. Hit the Start button to start uploading the new configuration file to the phone. After the upload is done, reboot the phone and check the IMEI number to verify everything went ok.
Finalizing
Enter the following string in the stock phone dialpad:
*#7284#
The service mode screen appears, so again, tap on the Qualcomm USB Settings button to display the list of USB options you can choose from. To restore the default USB settings, select the RNDIS + DM + MODEM option followed by tapping the OK button to return to the previous screen. Now use the back button to return to the dialpad, or hit the home button to continue using the phone normally.
That's it...enjoy your phone!
Notes & Feedback
Serial Number (Courtesy of @majin)
About the wrong Serial Number, [between step 6 and 7] if users have still on board the Chinese Rooted ROM (or if they flashed any other correct Rooted ROM), they can easily edit the file "\efs\FactoryApp\serial_no" by the phone itself (status is 1000:0000 rwxr--r-- 744)
Then they can flash any other favorite ROM [anyway, to make all easier, I suggest some 4.1 ROM, same as the Chinese one.]
Click to expand...
Click to collapse

hey i cant posting outside url
error message
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"

aki0306 said:
hey i cant posting outside url
error message
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Click to expand...
Click to collapse
8 more posts to go and you're in. Why don't you head over to this thread and see if you can contribute or give feedback to any of the queries from other members. Once you get into a dialog or discussion, you'll hit that magic 10 easy.
Your message to davidcsv was also relayed to that thread, and it would help to introduce yourself to the group and gain some 'trust' wrt your firmware images.

---------- Post added 5th March 2013 at 12:46 AM ---------- Previous post was 4th March 2013 at 11:58 PM ----------
MB1 Root Rom JB4.1.1
MA6 Root Rom JB4.1.1
MC3 Root Rom Android File Host JB4.1.1
★MC3 Rom no need rename but need flash stock MC3 Rom before flash root Rom
how to flash
flash from odin
1.flash stock rom
ex if u wanna flash MB1 root, u have to flash MB1 stock Rom before flash Root Rom
2.into recovery, wipe/factory reset
3.unzip Root Rom and rename file
★you guys have to rename file when unzip root Rom★
ex SC03E-ROOTED-system_MB1.tar.md5
　　　　　　　　　　　　　↓
　　SC03E-ROOTED-system.tar.md5
4.Flash Root Rom from odin
5.boot
6.installe Supersu or Superuser on play store
cation MB1 & MA6 Root Rom is "same name of file"
thx for kbc-developers
hv fun guys!!!!
---------- Post added at 12:51 AM ---------- Previous post was at 12:46 AM ----------
Custom Rom Link
jump to china forum
this Rom on MA6 Rom

damn.. didn't know this thread existed.
I will link this to the first post in my thread and have it closed.
if you could close my thread so all the talk can go here, it would be much more beneficial/easy to keep track of things.
---------- Post added at 02:01 PM ---------- Previous post was at 01:46 PM ----------
I can confirm that the root method worked for MB1...
LETS GET THE PARTY STARTED! Seriously, I am having a drink afterwork!

lol,trying with my phone.
update result soon.
my phone is rooted now.
but still waiting for custom one that removed needless app.
"Get PIT for mapping" <-------is this dangerous?

Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?

skylinerxz said:
Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?
Click to expand...
Click to collapse
I was just going to ask this...

didoka_702 said:
lol,trying with my phone.
update result soon.
my phone is rooted now.
but still waiting for custom one that removed needless app.
"Get PIT for mapping" <-------is this dangerous?
Click to expand...
Click to collapse
Get PIT for mapping is harmless, because the flashing process with Odin is just getting the current partitioning configuration as is stored in the phone. Just stay away from the PIT options in Odin (PC).
Why don't you just remove unwanted system apps with Titanium Backup?

skylinerxz said:
Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?
Click to expand...
Click to collapse
Do you mean one of the CWM recovery flavors or the Android builds (like for example CM 10.x)?

davidcsv said:
Do you mean one of the CWM recovery flavors or the Android builds (like for example CM 10.x)?
Click to expand...
Click to collapse
i would like CM10.x ! + CWM recovery flavors!
you got a lab rat available for this!

davidcsv said:
Get PIT for mapping is harmless, because the flashing process with Odin is just getting the current partitioning configuration as is stored in the phone. Just stay away from the PIT options in Odin (PC).
Why don't you just remove unwanted system apps with Titanium Backup?
Click to expand...
Click to collapse
sorry.already did that with tianium backup but still not edit my post.

IparryU said:
i would like CM10.x ! + CWM recovery flavors!
you got a lab rat available for this!
Click to expand...
Click to collapse
Who wants to try CWM Touch recovery? It is embedded in the latest upload of the MB1 stock root ready firmware image. The links are available in the original post in the pre-rooted stock ROMs section.
The procedure is as usual, flash with Odin (PC). Then, when your phone has booted into Samsung's stock Android, at any moment press VolumeUp/VolumeDown/Power at the same time and only briefly. This should root the phone (install su binary) and install the CWM Touch recovery... I say 'should' because I have only been able to test this procedure on my Korean version of the S3; in this case, CWM's recovery has been adapted for the SC-03E. There's no visual or audio confirmation when you've pressed those three buttons, so check with your favorite root-requiring app or with the included SuperSU app.
IF rooting works with this image, then the difference with the one presented by aki0306/kbc-developers is that theirs will always root the phone during startup; meaning you have the convenience of always starting up in a rooted environment. This mechanism will only root it when you need it (three button press detailed above); I'm still assuming that when you reboot, each time su (root) is removed by Docomo's security measures in the boot environment... if you want no root then reboot. As soon as someone can confirm whether this new mechanism works, I can turn it into a toggle kind of switch, so you can root and unroot without having to restart the phone.

davidcsv said:
Who wants to try CWM Touch recovery? It is embedded in the latest upload of the MB1 stock root ready firmware image. The links are available in the original post in the pre-rooted stock ROMs section.
The procedure is as usual, flash with Odin (PC). Then, when your phone has booted into Samsung's stock Android, at any moment press VolumeUp/VolumeDown/Power at the same time and only briefly. This should root the phone (install su binary) and install the CWM Touch recovery... I say 'should' because I have only been able to test this procedure on my Korean version of the S3; in this case, CWM's recovery has been adapted for the SC-03E. There's no visual or audio confirmation when you've pressed those three buttons, so check with your favorite root-requiring app or with the included SuperSU app.
IF rooting works with this image, then the difference with the one presented by aki0306/kbc-developers is that theirs will always root the phone during startup; meaning you have the convenience of always starting up in a rooted environment. This mechanism will only root it when you need it (three button press detailed above); I'm still assuming that when you reboot, each time su (root) is removed by Docomo's security measures in the boot environment... if you want no root then reboot. As soon as someone can confirm whether this new mechanism works, I can turn it into a toggle kind of switch, so you can root and unroot without having to restart the phone.
Click to expand...
Click to collapse
just finish custom my phone today @@
ill try this one tomorrow
and i have already backed up my phone with
+back all user data and app with titanium back up
+back up efs folder using root explorer
+back up QCN file using EFS pro by this thread
any process i need to do after this?

didoka_702 said:
just finish custom my phone today @@
ill try this one tomorrow
and i have already backed up my phone with
+back all user data and app with titanium back up
+back up efs folder using root explorer
+back up QCN file using EFS pro by this thread
any process i need to do after this?
Click to expand...
Click to collapse
That should cover it
I use Whatsapp, so I always make a seperate backup of its database folder as well (folder /mnt/sdcard/WhatsApp)... it contains the message history and all the media that's been sent over.

so i test this one recently and here is MY result (i usually hold up down volume first and then press power button)
+first time:check with Supersu.it said cannot install SuperSU cause of SU binary is not installed.
+restart and try again,this time i installed Titanium back up.and its said that the phone isnt rooted
+restart and try again,no worked
+and at the 5th 6th time everytime i try to press volume up down power to install Su binary,the phone restart.
//so its my result.anyone esle?
//and couldnt get to recovery mode :| now i back to aki rom till the new one came out.

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.

XT1644 - Custom ROM - Verizon support in USA

Hi Experts,
I have an XT1644 (G4 Plus USA variant) that has been running InvictaOS 7.1.2 very well for almost 2 years now. This ROM has been extremely stable for me. I tried several of the other custom ROMs before I settled on Invicta.
Problem: I have not been able to get StraightTalk using Verizon towers LTE working in this ROM or the others when I tried 2 years ago. The stock ROM worked fine for this.
Is anyone using a custom ROM that is working on ST Verizon? If so, please share.
Thanks!

Bump. Anyone know of a a way for me to get Verizon LTE working in a custom rom instead of stock?

I had this problem with omni a long time ago. You can keep trying various roms til you find one that works.
or
1) reload stock rom and root it
2) adb shell from computer terminal / cmd prompt
3) - in adb shell:
su (or use adb root to start adb as root, you want to see # not $)
content query --uri content://telephony/carriers/preferapn
copy this to a text file on your computer.
I assume yours will be different... but for reference here is my regular Verizon output on LOS14.1:
Row: 0 _id=1458, name=Verizon, numeric=311480, mcc=311, mnc=480, apn=VZWINTERNET, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=, authtype=-1, type=default,dun,supl, current=1, protocol=IPV4V6, roaming_protocol=IPV4V6, carrier_enabled=1, bearer=0, bearer_bitmask=30471, mvno_type=, mvno_match_data=, sub_id=-1, profile_id=0, modem_cognitive=1, max_conns=1023, wait_time=0, max_conns_time=300, mtu=0, edited=0, user_visible=1, read_only=0
Reload custom rom, and find the apnconf file and update it to match.
or do it manually, let it load up an apn and try to get signal
adb shell
su (or adb root)
content query --uri content://telephony/carriers/preferapn (this should look slightly different than stock)
Note: content also has create, delete, and update.
example for changes: (xxxx is the id number from your previous command)
content update --uri content://telephony/carriers --where "_id=xxxx" --bind bearer:s:"0"
In lOS14 there's an option to use root over ADB in developer options, then you just need to use "adb root" on your computer before adb shell, not sure about invictaOS
Changes will probably need a restart to take effect.

[GUIDE/TUTORIAL/HOWTO] HTC One M9 any model from Stock to Android 12

[GUIDE/TUTORIAL/HOWTO] HTC One M9 from Stock to Android 12
[GUIDE/TUTORIAL/HOWTO] HTC One M9 any model from Stock to Android 12
This detailed step-by-step guide helps you transform your HTC One M9 (any model) to a powerful one with Android 12.
Make sure you have the HTC One M9 model, in Android, go to Settings > About > Phone identity and check Model number.
### FM Radio doesn't work with Android 11.
Models supported:
- Himauhl (Europe WWE | GSM | MID 0PJA10000)
- Himaul or Himaulatt (AT&T, Developer Edition, Unlocked | GSM | MID OPJA11000)
- Himaultmus (T-Mobile | GSM | MID OPJA12000), not sure you can get Android 7
- Himauhl (Chunghwa Telecom | GSM | MID 0PJA13000)
- Himawhl (Sprint | CDMA | MID OPJA20000)
Himawl (Verizon | CDMA | MID OPJA30000) is not guaranteed, see: https://forum.xda-developers.com/f/verizon-htc-one-m9.4125/
* MID = Model ID
CHANGELOG
v1. Initial release
1) DOWNLOAD
- djibe HTC One M9 pack : https://bit.ly/djibe-onem9-pack
(includes HTC USB Drivers, recovery TWRP 3.6.2_9-0 for all M9, Magisk Root, adb, fastboot.exe and htc_fastboot.exe).
Unzip the djibe folder from the zip on root folder of C:\ drive.
- ROM for Himaul or Himawl: Unofficial LineageOS 18.1: https://forum.xda-developers.com/t/rom-11-0-0-himaul-himawl-lineageos-18-1-unofficial.4199175/unread
Download latest build here: https://mirror.codebucket.de/claymore1297/LineageOS/18.1/hima
Android 12.1 / LOS 19.1 is WIP (no telephony yet): https://forum.xda-developers.com/t/rom-12-1-0-himaul-himawl-lineageos-19-1-unofficial.4378803/unread
Or you can use AICP 17.1 right below
- ROM Android 12 for other Hima models: Android Ice Cold Project Official 17.1: https://forum.xda-developers.com/t/rom-12-1-0-hima-android-ice-cold-project-17-1-unofficial.4399865/
Download latest build here: https://dwnld.aicp-rom.com/
### Localisation (GPS) must stay turned ON to get Telephony
Or try crDroid 7.12
- NikGapps-SL ARM64 Core or Basic: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-SL/
- Charge phone to 100%
- 8+ GB MicroSD card formatted in FAT32
- Copy ROM + Google Apps +/- Magisk root zipfiles without unzipping content. Insert microSD in phone.
WARNING. This tutorial uses Microsoft Windows.
WARNING. Warranty is now void.
WARNING. Read carefully the sentences starting with ###.
2) BACKUP DATA AND INSTALL DRIVERS
Disable Antivirus.
Install drivers from my pack:
right click on HTCDriver.exe > click on Run as administrator and continue the setup.
Connect HTC One (while phone on) to PC, let drivers install.
In Windows explorer, HTC One should be available.
### If not make sure phone connection is in File transfer mode (see Android notifications).
### Phone is still not visible in Windows Explorer ? See fix at end of tutorial.
Collect all personal photos, videos, etc ... and backup these on PC.
Use an app like Backupyourmobile/SMS Backup & Resotre to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Disconnect phone.
### If your phone is Simlocked/carrier locked/Network locked, don't go further.
Visit official website of your network carrier (or call their support) to retrieve your desimlock code.
Ask them for details on how to remove simlock.
How do I know my phone is simlocked ? When you insert a SIM card from another operator, network is inaccessible.
Only a stock ROM can remove simlock.
To go back from custom ROM to stock, see dedicated section at the end of tutorial.
2) KNOW YOUR MODEL
Shutdown phone.
Start in fastboot mode: hold Power + Volume- until it vibrates and release both buttons.
Wait until hTC download mode shows up.
On mine I see:
SECURITY: *** UNLOCKED ***
model: htc_himawhl
CID-11111111
SECURITY UNLOCKED means S-OFF for SECURITY-OFF, otherwise S-ON. With S-ON you can upgrade firmwares but cannot use previous versions.
3) UPGRADE TO LATEST OFFICIAL ROM
In Android, go to Settings > About > Software information.
Android version is 7 and HTC Sense version is 8.0.
If Android is already 7, go to next chapter.
But before, search for IMEI and note this number somewhere safe (we never know).
Otherwise, we need to flash suitable stock Android 7 Nougat firmware, depending on your model.
In Settings > About > Software information, note down Software version (in case of future error).
For me it is 3.41.651.4 (651 is the SKU part, meaning Sprint US ROM).
See Sneakyghost's and Behold_this' SKU-, CID- and MID-List: https://docs.google.com/spreadsheets/d/10H7RftecZZKb5tT2zpShfYNFAfSe-imhhqtVfeMPVDA/edit?pli=1#gid=0
Now tap on More > tap 7 times on Build number. It unlocks Developer options.
Go back to Settings menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Switch ON USB debugging option.
Connect phone, a message appears on phone : Allow USB debugging?
check Always allow and confirm by tapping on OK.
But before upgrading to Android 7 Nougat, you need the latest Android 6 official ROM available for your model.
- Himaul or Himaulatt: RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.16.exe
- Himaultmus, not sure you can get Android 7: http://downloadmirror.co/android/29Ri/RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
- Himawhl: https://www.androidfilehost.com/?w=files&flid=334967 or https://downloadmirror.co/1KrL/RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe
- Himawl: http://downloadmirror.co/android/29...0105_CNV_1.26_002_release_469809_signed_1.zip
RUU*.exe: launch installer, connect phone (from within Android started or in Download mode) and follow executable steps.
Wait during flash.
After reboot, you have access to HTC software updates.
Go to Settings > System updates > HTC software update > CHECK NOW
Install available updates.
Repeat after each update until update 4.x is fetched.
Here you go with Android 7.
### I succeeded with Sprint model, tell us here if you experience problems with other models.
### Flash a RUU in *.zip format
### Copy RUU zipfile to microSD card and insert in phone. Shutdown phone.
### Start in fastboot mode: hold Power + Volume- until it vibrates and release both buttons.
### Use Volume- to Reboot to Bootloader. Confirm with Power.
### Use Volume- to BOOT TO RECOVERY MODE. Confirm with Power.
### Once in recovery, use Volume- to: Apply update from SD card
### Use Volume to select RUU zipfile
### Wait during flash
4) UNLOCK BOOTLOADER
Save IMEI, go to Settings > About > Phone identity > IMEI (15 digits).
In Settings > About > Software information > More.
Tap 7 times on Build number. It unlocks Developer options.
Go back to Settings menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Check ON OEM unlocking and USB debugging options.
Go to Settings > Security > Screen lock > None
Go to Settings > Storage > Phone storage, scroll down and make sure Phone storage encryption is unchecked.
Now, open a Windows command on my "flash" folder (hold Shift + right click on folder -> Open a windows command here).
Or type cmd in Windows address bar and hit enter to launch a Command prompt in actual folder.
Enter command :
Code:
adb devices
, confirm by pressing Enter.
Command returns :
Code:
List of devices attached
HT53****** device
### If no device is found, uninstall and reinstall properly the drivers while antivirus is off. Or see fix at the end of this tuto.
### Or start fresh on another PC.
Now type :
Code:
adb reboot bootloader
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Use volume keys to switch to Download mode !!!
### With HTC One M9, fastboot commands have to be sent from Download mode (took me hours to figure it out, thanks @DigiGoon).
Type :
Code:
fastboot devices
Command returns :
Code:
HT53**** fastboot
### You may have to fix drivers again (see fix at the end of tuto)
Type :
Code:
fastboot oem get_identifier_token
, confirm by pressing Enter.
Command returns multiple lines.
Select with your mouse all the lines from
Code:
<<<< Identifier Token Start >>>>
(included)
to the line
Code:
<<<<< Identifier token end >>>>>
(included).
Now on keyboard copy (Ctrl + C combo), then open Notepad.
In Notepad, paste those lines (Ctrl + V combo).
Now manually remove all the (bootloader) strings from each line.
Your notepad should now look like this :
<<<< Identifier Token Start >>>>
37A5DBF4FE5F0D9F4425E54AA91AFDBF
2A20E9C67C3BB4FAE60263F76BDEC6AC
847BF9FFB11DAEA4AB88AC8710435449
9BC12E93DF4C54FFE3D064C4C810C49A
2CDAF2E0CD3A164FED4A568CB0FD2AC6
C01AA991733D949C00987062D691DE91
8AA1C97CEBC3ACE83FECE75A1D03CE72
62414C7DC36A73AFCBF433E1EBE2EDC7
E272F73309632D3EF8C86E472B65E8EF
37E46B52FE3F94FC69D1854CA3DE6F48
C3E10001B233A70B1EAF35134F51FCC6
353E0CC98534E6E60A241A7063D0BE2F
A5B752E75C1C47E6F739BDBE67D024DA
3292A14278247557632639802722A86C
E61424F7666AE085AA9905096FEED1AD
5ECBBD867544E95ABDDA277690B8CB55
<<<<< Identifier Token End >>>>>
Now visit this website: https://www.htcdev.com/bootloader/
Register on the site. Confirm registration with your email.
In the select menu, choose HTC One M9, click Begin Unlock Bootloader button.
Agree to legal terms.
Next page, go to the bottom and click continue to step 5.
In the bottom of this page, in the lower textarea "My Device Identifier Token",
copy and paste the multiple lines you just edited (my example is just above).
Click Submit.
HTC tells you: Token Submitted Successfully!
Open your mailbox (associated to your HTC account).
Copy the Unlock_code.bin file attached to email in my "flash" folder you unzipped.
In Windows command, type:
Code:
fastboot flash unlocktoken Unlock_code.bin
, confirm with Enter.
Command should return:
Code:
Device is unlocked
4) FLASH TWRP RECOVERY
Using the same Windows command prompt, enter:
Code:
fastboot devices
to make sure phone is still available.
Then
Code:
fastboot flash recovery twrp-3.6.2_9-0-hima.img
Command returns :
Code:
finished. total time: x.xxxs
Now enter:
Code:
fastboot reboot-bootloader
Press Volume- to navigate to BOOT TO RECOVERY MODE, and confirm with Power button.
Phone reboots to TWRP recovery (with red message alert).
5) BACKUP STOCK SYSTEM
In TWRP, check Never show this screen and Swipe to Allow Modifications.
You land on TWRP Home screen.
Always make a backup of your stock system. We never know when a weird bug will decapitate the system.
Go to Backup menu, select all partitions and Backup to microSD card (Select Storage button).
Backup the generated TWRP folder content from your microSD card to PC.
6) WIPE PARTITIONS
Back to Home menu, go to Wipe > Format data, type yes and confirm with bottom righ icon.
Go to Wipe > Advanced wipe.
Select Dalvik / ART Cache, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to Wipe menu.
### Don't wipe SDcard
Got ot Reboot > Recovery
7) FLASH ROM AND GAPPS +/- ROOT/MAGISK
Back to Home screen, tap on Install > choose aicp*.zip
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active)
then Add more Zips -> open_gapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end (can be long).
### To flash Magisk, go to Reboot > Recovery and flash Magisk after reboot.
We need to format Data once more to remove an encryption that took me time to figure out.
Go back to Wipe one more > Format Data > yes
When format complete, tap on Reboot system
Wait during long first boot.
Setup Android.
8) You can use Backupyourmobile to restore data,
use GPS Status & Toolbox app to enhance GPS fix.
That's it.
Enjoy,
djibe
THANKS to TWRP team, AICP team, All M9 contributors.
You can find all my tutorials at: https://github.com/djibe/Android-tutorials
##################################################
## Unlock bootloader without Unlock key from HTCDev
See: https://forum.xda-developers.com/t/...loader-without-htcdev-s-off-required.3092036/
## Seek help for your model:
- Sprint: https://forum.xda-developers.com/t/...tc-one-m9-4-27-651-4-updated-4-13-17.3073355/
## Change 4G/LTE region
Edit build.prop
Reboot to recovery > Mount > select System
adb devices
adb root
adb remount
adb pull /system/build.prop
Edit with Notepad++
add ro.telephony.default_network=20
save file
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop

djibe89 said:
Himaultmus (T-Mobile | GSM | MID OPJA12000), not sure you can get Android 7
Click to expand...
Click to collapse
What is the "not sure" based on?

mmortal03 said:
What is the "not sure" based on?
Click to expand...
Click to collapse
Hi,
I didn't find a RUU for this model during a quick search.
Do you know more about an official firmware ?

djibe89 said:
Hi,
I didn't find a RUU for this model during a quick search.
Do you know more about an official firmware ?
Click to expand...
Click to collapse
I don't own this model, but I believe the T-Mobile Nougat firmware is: 0PJAIMG_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6_Radio_01.01_U114401021_126.03.70206G_2_F_release_497408_signed_2_4.zip

mmortal03 said:
I don't own this model, but I believe the T-Mobile Nougat firmware is: 0PJAIMG_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6_Radio_01.01_U114401021_126.03.70206G_2_F_release_497408_signed_2_4.zip
Click to expand...
Click to collapse
Himaul is the International model isn't it ?
I'll dig deeper.
Thx for asking.
Struggling with Verizon model exhausted me

djibe89 said:
Himaul is the International model isn't it ?
Click to expand...
Click to collapse
I believe himaul can refer to a couple of U.S. variants, the AT&T and the T-Mobile. The AT&T variant appends 'att' to the end, and the T-Mobile may append 'tmus' (but I don't have a T-Mobile variant in front of me to verify this).

Hello, I just bought a One M9 model htc_himawhl, and I would like to install android 12 on it.
The device is S-OFF and the bootloader indicate "Software status: Official" and "LOCKED".
I have a few questions about your tutorial.
What advantages we get when we unlock the bootloader ? I installed TWRP 3.7 yesterday, I suppose I can install any custom rom no ?
You didn't gives htc_himawhl compatible Android 12 rom, which one can work with in the list you given ?
I had an HTC U Ultra before this phone (which is now dead...), the process was much more easier because it was an international model. :/
Thanks in advance for your answer !

SofianeLasri said:
Hello, I just bought a One M9 model htc_himawhl, and I would like to install android 12 on it.
The device is S-OFF and the bootloader indicate "Software status: Official" and "LOCKED".
I have a few questions about your tutorial.
What advantages we get when we unlock the bootloader ? I installed TWRP 3.7 yesterday, I suppose I can install any custom rom no ?
You didn't gives htc_himawhl compatible Android 12 rom, which one can work with in the list you given ?
I had an HTC U Ultra before this phone (which is now dead...), the process was much more easier because it was an international model. :/
Thanks in advance for your answer !
Click to expand...
Click to collapse
Hi, normaly you need to unlock bootloader to boot a custom ROM.
To find a suitable ROM you should read the Sprint model section of XDA

@SofianeLasri , if you need VoLTE in your country/with your carrier, unfortunately, none of the recent custom ROMs for this phone have VoLTE/IMS registration working. It is being worked on, but there are no guarantees. You should read and follow the following thread for details/updates on this: https://forum.xda-developers.com/t/...ce-cold-project-17-1-official.4399865/page-12

What a shame, I buy a phone that I think is known on the custom rom scene, and I come across an abandoned operator model...

SofianeLasri said:
What a shame, I buy a phone that I think is known on the custom rom scene, and I come across an abandoned operator model...
Click to expand...
Click to collapse
Custom models are pain for obsolescence

Database Users

welcome