Related
After so many chinese roms testing my roms making custom roms..installing beta roms...and any kind of rom...i lost my IMEI so after i try everything i send it to service so im without phone and its easter holidays here on greece...You will find many posts here who to backup your IMEI but i will make this one so if a Admin can make it sticky so noone will have any more problems...
Caution if you havent took your IMEI backup do it and keep your backup like a treasure..you can't flash your IMEI if you loose it and you have to go to service to change your board!!
1)Download 5iromtoolbox: http://pikachukaki.googlecode.com/files/ToolBox5iromV1.0.4.2.apk
2)Open the app
3)Press backup IMEI
4)Connect your phone with USB cable and go to your pc
5)Open your sd card through windows explorer or whatever you use
6)Seek the folder /sdcard/5irom/imeibackup/
7)Copy the imeibackup folder to your pc to a folder that you will not by accident format ^_^
8)You are ok...now you can make whatever you like...
To restore your IMEI
1)Take your imeibackup folder from your pc
2)Paste it on your sd card on folder /sdcard/5irom/imeibackup/
3)Open the 5iromtoolbox
4)Press Restore IMEI and restart your phone!!
Just take it..is very important so you will not have to send your phone to service!!H
Hope i help!!
--------
Solution to flash your lost imei!
1) Enable debugging by USB in the settings
2) * # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings put the Manufacture mode. (Most likely it is already selected, then select Normal mode and re-manufacture mode)
3) * # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Qualcomm backround open settings put the background open. Password 0
4) Install the DFS DFS_3.3.0.7.exe (1.99 MB) Number of downloads: 5
, connect your phone to your computer.
5) will be found new hardware (multiple devices). You need to install drivers DBAdapter_Reserved_Interface.zip (60.41 KB) Number of downloads: 4
on the device vid_12d1 & pid_1035 & mi_04 (Open Device Manager, right-click on the device properties -> Information -> ID equipment). The equipment is established as a COM port.
5) Run the DFS, click Ports, select the port with the signature DBAdapter Reserved Interface (double click) to close.
6) Press the SPC, the bottom will Device Unlocked.
7) In the DM to select Qualcomm.
8) Back the tab Programming, in a field to enter your IMEI IMEI, then click the Read and Write Status.
9) Check Imei, may appear after a reboot, if not try a few more times to try to set the port speed to 115200 (box to the left of DM)
As soon as the IMEI restored change:
* # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings to put on the Manufacture mode google mode (or normal if you do not get up google)
* # * # 2846579 # * # * -> ProjectMenu - > Background settings -> Qualcomm backround open settings put close
If someone has 0 IMEI and havent found another way to fix it could try this and tell us if its working!!
Write your IMEI and your IMEI only!!!
Pikachukaki> why you not answering me in private question? i'm not for fight, just interesting
Sent from my ragelis
bronxitas said:
Pikachukaki> why you not answering me in private question? i'm not for fight, just interesting
Sent from my ragelis
Click to expand...
Click to collapse
There is nothing to answer you...you send me your opinion and its ok...you said you found duplicates...go yel [email protected]!!my rom working properly...so thats ok with me!!if you don't like it you can use official huawei!
Does this work for the u8800 to? the not pro version xD
theminikiller said:
Does this work for the u8800 to? the not pro version xD
Click to expand...
Click to collapse
Yeah...i think its 99% universal for all android phones!!not quite sure cos samsung stores IMEI on a folder that we don't have!!
ok ty, then ill do it now xD
Thanks! I just tried to backup my IMEI on my U8800 and it worked good. Don't know about restore though yet. I hope I won't need to...
thanks!!
What am i doing wrong?
My phone is Chinese and
it's rooted with SuperOneClick.
When backing up IMEI 5irom
(after granting superuser permission)
6 seconds later,
the folder /sdcard/5irom/imeibackup/
is empty.
and when starting 5irom again
the IMEI Backup dispays:
IMEI not backed up yet.
What am i doing wrong?
Also how many and
what files should be inside
the /imeibackup/ folder?
Any info would be greatly appreciated.
ff
ffinder said:
My phone is Chinese and
it's rooted with SuperOneClick.
When backing up IMEI 5irom
(after granting superuser permission)
6 seconds later,
the folder /sdcard/5irom/imeibackup/
is empty.
and when starting 5irom again
the IMEI Backup dispays:
IMEI not backed up yet.
What am i doing wrong?
Also how many and
what files should be inside
the /imeibackup/ folder?
Any info would be greatly appreciated.
ff
Click to expand...
Click to collapse
check your sd card cos if you haven't one it make the folders on internal but it didn't save anything!!after successfully saves imei it gives you 4 folders and one that says imei has 4 *.img files in it!!
5IromToolBox
When i clicked IMEI Backup
message is that
"back fail,check your root privileges! "
Details Of My Device Is:
Model number : u8800 pro
Android version : 2.3.5
base band version : 404020
Kernel version : 2.6.35.7-perf [email protected]#1
Build number : U8800PV100R001C213B519
ffinder said:
My phone is Chinese and
it's rooted with SuperOneClick.
When backing up IMEI 5irom
(after granting superuser permission)
6 seconds later,
the folder /sdcard/5irom/imeibackup/
is empty.
and when starting 5irom again
the IMEI Backup dispays:
IMEI not backed up yet.
What am i doing wrong?
Also how many and
what files should be inside
the /imeibackup/ folder?
Any info would be greatly appreciated.
ff
Click to expand...
Click to collapse
does it have mtk based cpu? this won't work on it, but there's another procedure for that..
hi
i used this tool on my Mi410 which is a variant of U9000 and i have the folder called
the folder /sdcard/5irom/imeibackup/ totally 4 files assuming this means i have sucessfully backup my imie
haree said:
hi
i used this tool on my Mi410 which is a variant of U9000 and i have the folder called
the folder /sdcard/5irom/imeibackup/ totally 4 files assuming this means i have sucessfully backup my imie
Click to expand...
Click to collapse
Me too, i think it's all ok, but I have only 3 files with Aurora ROM: 10.img 11.img 5.img. I upload that files to my DropBox too.
haree said:
hi
i used this tool on my Mi410 which is a variant of U9000 and i have the folder called
the folder /sdcard/5irom/imeibackup/ totally 4 files assuming this means i have sucessfully backup my imie
Click to expand...
Click to collapse
you need 3 imgs on imei folder....
my imei is already zero will it work with me
efray said:
my imei is already zero will it work with me
Click to expand...
Click to collapse
if you didnt get backup your phone no...now your screwed you need to go to service for board change!!im sorry!
so if i didnt is there anything dangerous
i asked coz i dialed customer service of my network they ask for the imei as they didnt see it
thanx for 4 cooperation
efray said:
so if i didnt is there anything dangerous
i asked coz i dialed customer service of my network they ask for the imei as they didnt see it
thanx for 4 cooperation
Click to expand...
Click to collapse
the phone didnt work normally without imei...when i lost mine wifi didn't work and i couldn't install official rom!!
when i was on aurora imei was zero but i installed official ics successfully
wifi data and all othe functions works great i cant see any difference
and i rooted the phone successfully
wat i wana ask is there any risk of loosing my phone
thnx
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.
Hi all, i've purchased an SM-G900F but there is a problem, it has rooted.
I've noticed those :
- I can see IMEI number (if i do #*06#) but my EFS folder is empty
- When turn on WiFi , the device will reboot automatically and appear " Factory Mode is On"
- i can make first call with sim , after i'm unable to call , but the 3G network works
- Whit ES File Explorer i've see that my efs folder is empty (But i can see my IMEI with secret code)
- In Device Info i see one time "Official Status" and another time "Personalized Status"
I'm tinking that old owner is a very st......d guy. Howewer these are all information :
Model : SM-G900F
Version : 4.4.2
BASEBAND : NE2
BUILD : NE2
What do you think? How i can solve the problems?
EDIT 1 : i've formatted from recovery , now it ask me to insert the samsung account of old owner...
- Use Phone INFO ★Samsung★ app to obtain more detailed information about your device, including Model, Baseband, Bootloader, CSC, IMEI, S/N, etc...
- May be the Reactivation lock has been enabled. You should ask the ex-owner for the account.
qwertyup88 said:
Hi all, i've purchased an SM-G900F but there is a problem, it has rooted.
I've noticed those :
- I can see IMEI number (if i do #*06#) but my EFS folder is empty
- When turn on WiFi , the device will reboot automatically and appear " Factory Mode is On"
- i can make first call with sim , after i'm unable to call , but the 3G network works
- Whit ES File Explorer i've see that my efs folder is empty (But i can see my IMEI with secret code)
- In Device Info i see one time "Official Status" and another time "Personalized Status"
I'm tinking that old owner is a very st......d guy. Howewer these are all information :
Model : SM-G900F
Version : 4.4.2
BASEBAND : NE2
BUILD : NE2
What do you think? How i can solve the problems?
EDIT 1 : i've formatted from recovery , now it ask me to insert the samsung account of old owner...
Click to expand...
Click to collapse
reactivation lock is on. you will need to contact old owner. There is also a way to "fix" that but not sure if it is appropriate for XDA.
kabloomz said:
reactivation lock is on. you will need to contact old owner. There is also a way to "fix" that but not sure if it is appropriate for XDA.
Click to expand...
Click to collapse
Can you send me an email ? i really need hepl
vndnguyen said:
- Use Phone INFO ★Samsung★ app to obtain more detailed information about your device, including Model, Baseband, Bootloader, CSC, IMEI, S/N, etc...
- May be the Reactivation lock has been enabled. You should ask the ex-owner for the account.
Click to expand...
Click to collapse
The guy was not traceable now. He's vanished ....
You are kinda between a rock and a hard place if reactivation lock is enabled and you don't have the login to toggle that. In most cases that means that the phone is stolen and this is an explicit anti theft feature. You need that login from the original owner. Or if you have the original receipt, you might be able to convince a Samsung repair center to disable the reactivation lock for you.
In any event, as to your original question the most likely cause of the problem is a corrupt configuration file, namely a text file named "factorymode". You can try this repair from the command line or a root aware text editor.
Code:
echo -n ON > /efs/FactoryApp/factorymode
.
fffft said:
You are kinda between a rock and a hard place if reactivation lock is enabled and you don't have the login to toggle that. In most cases that means that the phone is stolen and this is an explicit anti theft feature. You need that login from the original owner. Or if you have the original receipt, you might be able to convince a Samsung repair center to disable the reactivation lock for you.
In any event, as to your original question the most likely cause of the problem is a corrupt configuration file, namely a text file named "factorymode". You can try this repair from the command line or a root aware text editor.
Code:
echo -n ON > /efs/FactoryApp/factorymode
.
Click to expand...
Click to collapse
Just now the guy told me account and password . Now i'm able to use my phone !!!!! But now i see that the efs folder is empty...
qwertyup88 said:
Just now the guy told me account and password . Now i'm able to use my phone
Click to expand...
Click to collapse
Great. But you neglected to tell us if you tried (or even noticed) the suggestion to check your factory mode configuration file. The contents should show "ON" (yes, "ON") and the permissions 0644. Your efs folder may appear empty to you when it really isn't. It depends on whether you have your file browser (or command line options) set to display hidden and system files or not.
.
fffft said:
Great. But you neglected to tell us if you tried (or even noticed) the suggestion to check your factory mode configuration file. The contents should show "ON" (yes, "ON") and the permissions 0644. Your efs folder may appear empty to you when it really isn't. It depends on whether you have your file browser (or command line options) set to display hidden and system files or not.
.
Click to expand...
Click to collapse
y factory mode is on , because i can't acces my wifi, and it appear that factory mode is on. I've set to see hidden files , but now i haven't root on my device
Edit: terminal emulator say : no such file or directory
Edit 2 : Solved with terminal emulator and busy box Thanks to @leoaudio13 for his dump
These are the command for mount efs :
su
mke2fs /dev/block/mmcblk0p12
mount -w -t ext4 /dev/block/mmcblk0p12
reboot
After then , with text editor i've disabled FactoryApp in efs folder tanks to all
.
For the benefit of anyone else reading this thread, do not repeat the steps in the post above until
you understand what they do. A typo in those steps could easily cause you endless grief.
Glad you go it working.
If those steps fixed your issue, then you mislead us with erroneous information earlier. You said that you had an empty efs folder earlier. But those steps would not have been necessary or effective if that was accurate. You must have had a missing efs partition. There is a considerable difference between an empty and nonexistent item and that datum would have led us to a solution.
On a normal phone, there would be an extant efs folder and it would be automatically mounted at boot. A missing folder strongly suggests that the wrong firmware or a flash error took place. Presumably by the previous owner.
Anyone using the make filesystem command mke2fs /dev/block/mmcblk0p12 should be very careful with typos as an incorrect address could cause major corruption that would be difficult to recover from.
.
Originally Posted by qwertyup88 View Post
Hi all, i've purchased an SM-G900F but there is a problem, it has rooted.
I've noticed those :
- I can see IMEI number (if i do #*06#) but my EFS folder is empty
- When turn on WiFi , the device will reboot automatically and appear " Factory Mode is On"
- i can make first call with sim , after i'm unable to call , but the 3G network works
- Whit ES File Explorer i've see that my efs folder is empty (But i can see my IMEI with secret code)
- In Device Info i see one time "Official Status" and another time "Personalized Status"
I'm tinking that old owner is a very st......d guy. Howewer these are all information :
Model : SM-G900F
Version : 4.4.2
BASEBAND : NE2
BUILD : NE2
What do you think? How i can solve the problems?
EDIT 1 : i've formatted from recovery , now it ask me to insert the samsung account of old owner...
Click to expand...
Click to collapse
Ive got almost the same problem, i bought my s5 to a friend who visited Philippines from Korea, He acquired the Phone in a Pawnshop in korea, i restore the phone and now it asked me for a password which i dont know, send it to the Technician, Force to delete the account (dont know how) but the problem is that, Phone has NO SIGNAL from then on, it has a NO signal above instead of a bar signal, EFS folder is empty, IMEI was null 000000000000000.
Anybody has the same experience? how can i fix this? please help.
Not perfectly solved .... After first call it don't connect to the network. Only after reboot it connect.
Any suggestions ?
qwertyup88 said:
Not perfectly solved .... After first call it don't connect to the network. Only after reboot it connect.
Any suggestions ?
Click to expand...
Click to collapse
could be a block imei by the operator? if it is POSSIBLE to solve? or it could be due however to the efs folder, or the firmware, modem?
edreab86 said:
Ive got almost the same problem, i bought my s5 to a friend who visited Philippines from Korea, He acquired the Phone in a Pawnshop in korea, i restore the phone and now it asked me for a password which i dont know, send it to the Technician, Force to delete the account (dont know how) but the problem is that, Phone has NO SIGNAL from then on, it has a NO signal above instead of a bar signal, EFS folder is empty, IMEI was null 000000000000000.
Anybody has the same experience? how can i fix this? please help.
Click to expand...
Click to collapse
it's a different problem , you have a null imei , in your case it's more difficult to resolve.
Originally Posted by qwertyup88
it's a different problem , you have a null imei , in your case it's more difficult to resolve.
Click to expand...
Click to collapse
As you can read i said, Ive got almost the same problem, i don't say we have the same problem. in a sense that previous owner account or the reactivation lock is present. sorry if i made a statement that bothers you, just looking for a solution.
hello guys, always about the efs folder I was reading this post: http://forum.xda-developers.com/showthread.php?t=2705524.
according to you through this tool is possiblile restore the backup I had done with samsung tool? I would like to try this because the efs folder on my sm-g900f is 23kb, but the backup I had done with samsung tool is 14mb !! what do you think?
Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery . IMEI is not recovered
its easy to recover imei in MTK based devices but when it comes to qualcomm based devices
it is a big mess
This is my First Tutorial
how to recover lost IMEI in yureka yunqiue & other some qualcomm devices
im not responsible if anything wrong happen to your device
Tools you need
QXDM professional
usb hs-diagnostic 9006 driver
adb tool & driver
terminal app
now lets begin
1) Root your bricked phone & install terminal app (Note :- assuming you flashed stock rom or custom rom & you are facing imei lost issue )
now grant terminal app su permission by typing
SU in the app
in terminal type this code
Code:
setprop sys.usb.config diag,adb
now connect you phone to the usb
if you have installed the drivers correctly your phone will be detected by you system in diagnostics mode
now here is the trick
IMEI information is located inside the NV_ITEMS ==550
open qxdm professional
goto communication
browse to NV_ITEMS
now search for 550 in Item number
select the option dual sim (sim 0 stands for SIM1 and 1 stands for SIM2)
Code:
IMEI example "123456-78-9012340"
sort it out 1 ,23 ,45 ,67 ,89 01 ,23 ,40
{ 0x08, 0x1A, 0x32, 0x54, 0x76, 0x98, 0x10, 0x32, 0x04 }
As you can see i have sorted it out & swaped the values
0x08 is the length keep it as it
0x1A = first digit of IMEI with A
0x32 = swaped 23 to 32
.
.
after you are done putting value of your IMEI in sim 1 press the write button & wait few sec
now repeatg the step for sim2
Reboot Your Phone & voila
Hit Thanks if you think i have helped you
I just debricked my yureka plus and tried many tutorials to recover my imei numbers but didn't worked now i will try this and let you know what happens next!
It Works
Ty for this tutorial it worked for me
I recovered my IMEI using this TY again :victory:
Thanks a million for your help dude. Yours is the only method which worked on my Yu Yureka with cm12.1
I spent endless hours and wasted almost 3 gb of useless downloads. God bless you and may all your projects shine brightly in all your future ventures. Wish I could hit that thanks button a few hundred times........
Warmest regards
this tutorial it worked for me
I recovered my IMEI using this step but network not show and not show sim card
QXDM returns "read only" error. When i edit the contents with the correct ones and press write, the error is seen below as nv contents read only mode
sohail0098 said:
QXDM returns "read only" error. When i edit the contents with the correct ones and press write, the error is seen below as nv contents read only mode
Click to expand...
Click to collapse
same thing happened to me also.
i am using oneplus 2 and lost imei of one sim
what device you are using?
did you got any fix for that?
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
botnet.py said:
Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery .
Click to expand...
Click to collapse
i followed the exact steps but encountered one problem.
using oneplus 2 and trying to recover one lost imei
when i select slot 1 for second sim it says it is not active and even when i try to edit and write it says its write protected.
any help in that case?
ashu01 said:
same thing happened to me also.
i am using oneplus 2 and lost imei of one sim
what device you are using?
did you got any fix for that?
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
i followed the exact steps but encountered one problem.
using oneplus 2 and trying to recover one lost imei
when i select slot 1 for second sim it says it is not active and even when i try to edit and write it says its write protected.
any help in that case?
Click to expand...
Click to collapse
share screenshot .....& did u selected dual sim ?& double check if ur phone is rooted properly
ashu01 said:
same thing happened to me also.
i am using oneplus 2 and lost imei of one sim
what device you are using?
did you got any fix for that?
---------- Post added at 03:57 AM ---------- Previous post was at 03:54 AM ----------
i followed the exact steps but encountered one problem.
using oneplus 2 and trying to recover one lost imei
when i select slot 1 for second sim it says it is not active and even when i try to edit and write it says its write protected.
any help in that case?
Click to expand...
Click to collapse
Just reinstall your rom by wiping internal storage also. Then let the phone boot. Don't install gapps for quicker bootup. Then after restoring imei flash the rom of your choice. Try cm nightly first for recovering imei.
sohail0098 said:
Just reinstall your rom by wiping internal storage also. Then let the phone boot. Don't install gapps for quicker bootup. Then after restoring imei flash the rom of your choice. Try cm nightly first for recovering imei.
Click to expand...
Click to collapse
you got your IMEI back??
i have tried many things..
could you please list the steps you have done.
and how you got rid of that write protected issue?
ashu01 said:
you got your IMEI back??
i have tried many things..
could you please list the steps you have done.
and how you got rid of that write protected issue?
Click to expand...
Click to collapse
I was on cm13 unofficial build. I tried qxdm professional but there was this write protected error. I connected my device in fastboot mode and erased system. Then hotbooted TWRP (latest) and flashed the same rom again after wiping data and internal storage using rm rf. Then i let the rom boot up. (Without Gapps). Then i again tried the same steps as mentioned above. And after i got imei back, i rolled to my favourite rom. Hope you get back your imei soon.
lost yureka imei number and baseband unknown
botnet.py said:
Hi friends We often suffer hard brick in our devices .
Even after flashing stock recovery . IMEI is not recovered
its easy to recover imei in MTK based devices but when it comes to qualcomm based devices
it is a big mess
This is my First Tutorial
how to recover lost IMEI in yureka yunqiue & other some qualcomm devices
im not responsible if anything wrong happen to your device
Tools you need
QXDM professional
usb hs-diagnostic 9006 driver
adb tool & driver
terminal app
now lets begin
1) Root your bricked phone & install terminal app (Note :- assuming you flashed stock rom or custom rom & you are facing imei lost issue )
now grant terminal app su permission by typing
SU in the app
in terminal type this code
Code:
setprop sys.usb.config diag,adb
now connect you phone to the usb
if you have installed the drivers correctly your phone will be detected by you system in diagnostics mode
now here is the trick
IMEI information is located inside the NV_ITEMS ==550
open qxdm professional
goto communication
browse to NV_ITEMS
now search for 550 in Item number
select the option dual sim (sim 0 stands for SIM1 and 1 stands for SIM2)
Code:
IMEI example "123456-78-9012340"
sort it out 1 ,23 ,45 ,67 ,89 01 ,23 ,40
{ 0x08, 0x1A, 0x32, 0x54, 0x76, 0x98, 0x10, 0x32, 0x04 }
As you can see i have sorted it out & swaped the values
0x08 is the length keep it as it
0x1A = first digit of IMEI with A
0x32 = swaped 23 to 32
.
.
after you are done putting value of your IMEI in sim 1 press the write button & wait few sec
now repeatg the step for sim2
Reboot Your Phone & voila
Hit Thanks if you think i have helped you
Click to expand...
Click to collapse
i have lost yureka imei number how to recover imei number? can i recover it by flashing stock rom? currently i am using cm12.1 in my phone. sim is not detected network is not recognize what should i do. should i follow this guide or flash stock rom? plz help me
Please provide links for qxdm professional
Recoverd imei bt no signals on lte H.E.L.P............
sohail0098 said:
I was on cm13 unofficial build. I tried qxdm professional but there was this write protected error. I connected my device in fastboot mode and erased system. Then hotbooted TWRP (latest) and flashed the same rom again after wiping data and internal storage using rm rf. Then i let the rom boot up. (Without Gapps). Then i again tried the same steps as mentioned above. And after i got imei back, i rolled to my favourite rom. Hope you get back your imei soon.
Click to expand...
Click to collapse
Hello Sohail,
Greetings from Karnataka,
Bro, Im in dire need of IMEI fix, WRT Yu Yureka.
Is it possible to help me?
Ive also created a thread, with relevant info :
https://forum.xda-developers.com/yureka/orig-development/yu-imei-issue-t3605198
Thanks
ashu01 said:
you got your IMEI back??
i have tried many things..
could you please list the steps you have done.
and how you got rid of that write protected issue?
Click to expand...
Click to collapse
Have you installed stock ROM v1?
If the above post doesn't work then you can follow this ..My Name Suman Das..I myself have done this.
Believe Me you will be successfull..
Step 1:Search Google for ".qcn" file for yunique / yureka whatever you have...
Step 2: Download qpst configuration tool. and istall it on your computer..
Step 3: Root Your Phone..Kingroot or SuperSu .zip can be used..
Step 4: Download And Install Terminal Emulator apk from any where..
Step 5:Connect your phone to PC With USB Debugging mode enabled..
Step 6: Open terminal Emulator...and Type this commands to Enable Diag mode of oyur mobile into PC..
adb shell(then enter)
su(then enter)
setprop sys.usb.config diag,adb(then enter)
After this your phone will be connected to PC In Diag Mode..then you are ready to Restore the Downloaded .qcn file ..
Step 7: Go To PC Open QPST Configuration & Check Ports for Qualcomm Port DIAG In Device Manager..
Step 8: Now you will see your Phone in QPST Configuration .Now click on Start Clients In the Menu Bar Of QPST and go to Software Download..
Step 8: Click on Port Browse option and select your phone.Then Go to Restore.And browse for your ".qcn" file and click on restore...
and then You have successfully Restored your phone back .then Simply restart your phone and it's ready..
---------- Post added at 12:41 PM ---------- Previous post was at 12:19 PM ----------
sourabhlangoo said:
Recoverd imei bt no signals on lte H.E.L.P............
Click to expand...
Click to collapse
If the above post doesn't work then you can follow this ..My Name Suman Das..I myself have done this.
Believe Me you will be successfull..
Step 1:Search Google for ".qcn" file for yunique / yureka whatever you have...
Step 2: Download qpst configuration tool. and istall it on your computer..
Step 3: Root Your Phone..Kingroot or SuperSu .zip can be used..
Step 4: Download And Install Terminal Emulator apk from any where..
Step 5:Connect your phone to PC With USB Debugging mode enabled..
Step 6: Open terminal Emulator...and Type this commands to Enable Diag mode of oyur mobile into PC..
adb shell(then enter)
su(then enter)
setprop sys.usb.config diag,adb(then enter)
After this your phone will be connected to PC In Diag Mode..then you are ready to Restore the Downloaded .qcn file ..
Step 7: Go To PC Open QPST Configuration & Check Ports for Qualcomm Port DIAG In Device Manager..
Step 8: Now you will see your Phone in QPST Configuration .Now click on Start Clients In the Menu Bar Of QPST and go to Software Download..
Step 8: Click on Port Browse option and select your phone.Then Go to Restore.And browse for your ".qcn" file and click on restore...
and then You have successfully Restored your phone back .then Simply restart your phone and it's ready..
Download Link For Softwares---https://drive.google.com/folderview?id=0B-0bWbXeDJt4dGMyVkF2TnBSVWs
Got the solution
I was struggling for many days and it was so simple though I got my IMEIs back by just flashing Volte modem file. A huge thanks to that person who somewhere in some thread mentioned this step.You are great bro.
codeddanny said:
I was struggling for many days and it was so simple though I got my IMEIs back by just flashing Volte modem file. A huge thanks to that person who somewhere in some thread mentioned this step.You are great bro.
Click to expand...
Click to collapse
You mean if i reflash the volte modem, i can get back my imei?
Sent from my YU5510 using Tapatalk
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.