If you flashed the Stock ROM using “Download All + Format” option in SP Flash Tool or you wiped NVRAM partition accidently then you probably lost IMEIs, WiFi/Bluetooth Mac Address and Serial No.
Disclaimer:
Code:
/*
*Your Warranty is now void.
*Neither me nor the developers of tools are responsible.
*You are doing this at your own risk and will
*solely be responsible if something happens to the device.
*Make sure you only use the original “IMEI_1, IMEI_2,
*WiFi/Bluetooth Address, Serial Number” that came with your phone.
*/
Note:
Although, I have tried to keep this guide as simple as possible, I am assuming that you have already flashed Stock ROM using this thread/guide:
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
Which also means the required drivers i.e. “MTK (USB DA COM, Preloader USB VCOM, USB Port, USB VCOM) Driver” and “Lenovo USB Driver” in the thread mentioned above are also installed.
Requirements:
Lenovo K8 Note with Stock ROM.
Original IMEI_1, IMEI_2, WiFi/Bluetooth Mac Address, Serial Number. (Find on Phone’s box)
SN Write Tool (Download)
Database Files
ADB Tools (Inside SN_Write_Tool\Android)
Basic ADB know-how.
And a PC. (obviously)
USB Debugging:
Before we proceed, make sure “USB Debugging” is enabled on phone:
Navigate to, Settings > System > About Phone > Build Number (Tap 7 times) to enable “Developer Options”.
Now, Enable “USB Debugging” in Settings > System > Developer Options.
Flashing Procedure:
Extract SN Write. (For Example, Location: “E:\ SN_Write_Tool_v1.1916.00”)
Open SN Write Tool (SN_Writer.exe).
Make sure all the Preliminary steps mentioned in below sections have been performed – Obtaining DB files, Configuring SN Write Tool, Understanding Barcode.
Switch off the phone, while keeping the cable unplugged
Click “Start”.
Enter Original IMEI_1, IMEI_2, WiFi/Bluetooth Mac Address, Barcode and press “Ok”
Connect your phone.
Now your phone will automatically boot in Meta Mode.
Wait for the Process to finish.
Now you will see “Pass” message if everything completes successfully.
Now it will again ask to enter the details. Click “Cancel”
The phone will now switch off. Then boot it manually.
That’s it. Your phone is now back to normal. Now, you can see Serial No. in adb too.
Obtaining Database(DB) files:
In order to restore everything we need 2 Database files, which can be obtained by following the procedure below:
Extract SN_Write Tool. (For Example, Location: “E:\ SN_Write_Tool_v1.1916.00”)
Navigate to “Android” folder inside SN_Write_Tool folder.
Keep Shift Key Pressed and Right Click inside the folder. Select “Open Command / PowerShell window here”.
Type
Code:
adb devices
You will receive a prompt on your phone. Select “Ok”. The device will appear in the list. (Something like “0123456 device”)
Now, type these commands:
Code:
adb pull /vendor/etc/mddb Database
adb pull /system/etc/apdb Database
Now, navigate to “E:\ SN_Write_Tool_v1.1916.00\Android\Database”. There will be around 23 Files. We only Need 2 files from that.
APDB_MT6797_S01_alps-trunk-o0.tk_W19.10 (Approx. size 145kb)
MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_O_Vxx_x_ulwctg_n.EDB (Approx. size 59mb)
Note: Name and size may slightly vary depending upon your firmware.
Copy the above two files to some other destination (optional).
Note: If you are using PowerShell then, instead of “adb” type “./adb”
Configuring SN Writer Tool:
Open “SN_Writer.exe” inside “E:\ SN_Write_Tool_v1.1916.00”.
Now Click “System Config”.
Check “Dual IMEI” (Do not check “Dual IMEI Same” under that).
In Write options select Barcode, IMEI, BT Address, WiFi Address. (If you don’t have WiFi/BT Address then don’t check/select them).
Check “Load AP DP from DUT” and “Load Modem DB from DUT”.
Click “MD1_DB” and select the file that you pulled using ADB i.e.
“MDDB_InfoCustomAppSrcP_MT6797_S00_MANNING_O_Vxx_x_ulwctg_n.EDB”
Click “AP_DB” and select the file that you pulled using ADB i.e.
“APDB_MT6797_S01_alps-trunk-o0.tk_W19.10”
Now click “Save”.
{
"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"
}
Understanding Barcode:
It took me lots n lots of trial & error and googling before finding the correct (probably) Barcode format that we need to use in SN Writer. Trust me, it was not an easy task. Below are three iterations of barcode, use any:
First Iteration (recommended):
The Barcode field consists if two parts, call them Spaces and Serial No.
Total Length(33 Characters) = (25 Spaces) + SN(8)
For Example,
If my SN written on the box is “XYZ1223W”, my barcode will be (without quotes):
Code:
“ XYZ1223W”
or
Second Iteration (recommended 2):
In this iteration, we'll assume that the Barcode field in SN Write Tool is a combination of three parts. Lets call it First (PN), Second and Third Part (SN). You can find PN & SN on the box of phone. I am not sure about the second part with 15 characters. You can leave the second part, just give 15 Spaces.
Total Length(33 Characters) = PN(10) + (15 Spaces) + SN(8)
For Example,
If my PN written on the box is “AB1D1112IN” and SN is “XYZ1223W”, my barcode will be (without quotes):
Code:
“AB1D1112IN XYZ1223W”
or
Third Iteration:
There can also be a third iteration for barcode, though I am not sure about this and is completely based on my assumption. In the second part, as mentioned above we are leaving 15 spaces, but in this, we will use the product barcode of 13 characters (Refer Barcode No. 2 in the attached image below) instead of 15 spaces
For Example,
If my barcode (no. 2 in image above) of 13 charcters is “0123456789012”, then in SN Writer we will write (without quotes):
Total Length(33 Characters) = PN(10) + (Space) + (13) + (Space)+ SN(8)
Code:
“AB1D1112IN 0123456789012 XYZ1223W”
Note the space after each part, which makes up for two characters that we require.
As you can see in the Screenshot attached in this post, “Lenovo Help” app recognizes the device as it is meant to be recognized.
WiFi/Bluetooth Mac Address:
Though, it is not a big deal if you lost WiFi/Bluetooth Mac Addresses. They will still work fine even without it.
If you didn’t backup nvram before or didn’t note down WiFi/Bluetooth Mac address then you can’t get it back. But, if you did TWRP backup of nvram then you can restore it and get back both the original Mac addresses.
FAQs:
SN Writer not booting phone into Meta Mode automatically.
Make sure drivers are installed
or
Boot Manually in Meta Mode using Power Button + Volume Down. Check Already in Meta Mode.
Do I need to be on Stock ROM?
Yes.
Changelog:
27 September 2020:
Update post.
Added one more iteration of barcode.
Added more Screenshots.
Correct minor typos.
thanks alot man
I managed to get apdb files but when i try your command to get mddb i get that error
adb: error: failed to copy '/etc/mddb' to 'Database\mddb': read failed: Is a directory
any help?
and how to know if my bluetooth or wifi mac address is missing and where to find them because nothing of that is written on the phone box
softmaster3 said:
thanks alot man
I managed to get apdb files but when i try your command to get mddb i get that error
adb: error: failed to copy '/etc/mddb' to 'Database\mddb': read failed: Is a directory
any help?
and how to know if my bluetooth or wifi mac address is missing and where to find them because nothing of that is written on the phone box
Click to expand...
Click to collapse
Edit: Solved
Android will automatically generate Wi-Fi / Bluetooth address if not found. No need to worry about that. Thats why I I have mentioned in the post that it will still work fine even without it.
You mentioned wrong paths, /etc/apdb is fine but /etc/mddb doesn't exist(empty folder was created in latest update but still no contents in it). mddb is under /vendor/etc/mddb. Just to avoid confusion and even to make this guide suitable for users who pull the file from TWRP make the /etc/apdb to /system/etc/apdb
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
softmaster3 said:
thanks alot man
I managed to get apdb files but when i try your command to get mddb i get that error
adb: error: failed to copy '/etc/mddb' to 'Database\mddb': read failed: Is a directory
any help?
and how to know if my bluetooth or wifi mac address is missing and where to find them because nothing of that is written on the phone box
Click to expand...
Click to collapse
instead of "adb pull /etc/mddb" use "adb pull /vendor/etc/mddb"
M.A.P said:
You mentioned wrong paths, /etc/apdb is fine but /etc/mddb doesn't exist(empty folder was created in latest update but still no contents in it). mddb is under /vendor/etc/mddb. Just to avoid confusion and even to make this guide suitable for users who pull the file from TWRP make the /etc/apdb to /system/etc/apdb
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
instead of "adb pull /etc/mddb" use "adb pull /vendor/etc/mddb"
Click to expand...
Click to collapse
thanks a lot guys
u two just made my day
and M.A.P u r a life saver i cant thank you enough for ur work on treble for k8 note and ur help here
M.A.P said:
You mentioned wrong paths, /etc/apdb is fine but /etc/mddb doesn't exist(empty folder was created in latest update but still no contents in it). mddb is under /vendor/etc/mddb. Just to avoid confusion and even to make this guide suitable for users who pull the file from TWRP make the /etc/apdb to /system/etc/apdb
Click to expand...
Click to collapse
Done. Thanks for suggestion.
i did write the serial, check warranty and its good
but noticed that the serial written on phone box is 12 Character long not just 8 and sn writer did write 8 only not the whole 12
is that correct??
softmaster3 said:
i did write the serial, check warranty and its good
but noticed that the serial written on phone box is 12 Character long not just 8 and sn writer did write 8 only not the whole 12
is that correct??
Click to expand...
Click to collapse
May I see the image of your box. PM me the image.
done
softmaster3 said:
thanks a lot guys
u two just made my day
and M.A.P u r a life saver i cant thank you enough for ur work on treble for k8 note and ur help here
Click to expand...
Click to collapse
Your welcome, I'm always ready to help
Hi, with the help of your guide, i have recovered my phone. But the problem is still same as it restarts repeatedly,sometimes it worked for 1 day but then again rewstarting. Is there any permanent solution for this?
psbtheone said:
Hi, with the help of your guide, i have recovered my phone. But the problem is still same as it restarts repeatedly,sometimes it worked for 1 day but then again rewstarting. Is there any permanent solution for this?
Click to expand...
Click to collapse
Show your phone to a technician. It may be due to battery or some other reason.
Im getting remote object does not exist error for both commands
WP7 Barcode
Hi,
I was wondering how did you find the correct Barcode format? I have spent 2 days trying with different combinations and I still have not succeeded in restoring the serial number in my Oukitel WP7. It still gives me the generic serial number 123456789ABCDEF.
oxord said:
Hi,
I was wondering how did you find the correct Barcode format? I have spent 2 days trying with different combinations and I still have not succeeded in restoring the serial number in my Oukitel WP7. It still gives me the generic serial number 123456789ABCDEF.
Click to expand...
Click to collapse
Did some Trial and Error to figure out correct (probably) barcode format. In addition to this, you'll also need specific database files for your phone in order restore it.
kk9999gada said:
Did some Trial and Error to figure out correct (probably) barcode format. In addition to this, you'll also need specific database files for your phone in order restore it.
Click to expand...
Click to collapse
Man this thing is driving me crazy. I have tried every single combinations and did so many googling and there are not a lot of information about this. The other problem is that the Oukitel WP7 does not have a Product Number written on the box or on the back of the device, there is only a serial number and a barcode with 13 numbers under it. I even tried the FCC ID that is written at the top. I have been spending few days trying. I think the only way to know the correct format is to ask someone who has the same device to view it using Maui Meta by viewing the hex format or exporting the NVRAM to an ini file. I doubt anyone would help me with this though. I have the database files from the stock image. Anyways thanks man
oxord said:
Man this thing is driving me crazy. I have tried every single combinations and did so many googling and there are not a lot of information about this. The other problem is that the Oukitel WP7 does not have a Product Number written on the box or on the back of the device, there is only a serial number and a barcode with 13 numbers under it. I even tried the FCC ID that is written at the top. I have been spending few days trying. I think the only way to know the correct format is to ask someone who has the same device to view it using Maui Meta by viewing the hex format or exporting the NVRAM to an ini file. I doubt anyone would help me with this though. I have the database files from the stock image. Anyways thanks man
Click to expand...
Click to collapse
That would be better.
There is no need for Part No. or Barcode (both can be replaced with spaces). The only thing required is Serial No.
kk9999gada said:
That would be better.
There is no need for Part No. or Barcode (both can be replaced with spaces). The only thing required is Serial No.
Click to expand...
Click to collapse
I tried that as well with so many different ways and with spaces and without. I guess the length also matters. I even filled all 63 characters to see if anything changed in settings but it still showed the generic serial number. I am starting to wonder if sn tool is writing the data in the correct location. I am sure I am using the correct database files because I got them from the factory image from the official website and I am able to write the IMEIs correctly.
I am thinking now to go through the serial number which is 16 characters from left to right. Each time I add a space on the left and no spaces after the serial so first try would be only the serial then a 1 space before it then two spaces before it until I reach the 63 characters. This is like 50 restarts and if that does not work I will try in a same manner but this time full up spaces after the serial and do the same by adding one space on the left each time so first try would be the serial number and the remaining will be spaces up to 63 characters the second time will be one space before the serial and remaining spaces after it up to 63 and so one. I know it's crazy but if all that does not work I am not sure what else to do.
Hi
This happened to me with this dangerous spflash tool. WIPED everything. I followed this guide , It PASSES without any errors but doesnt write anything to my phone. Box has a code bar like this 6 970502 270581 then MEID code of 14 characters , than IMEI1 code and a IMEI2 code and finaly a S/N code of 15 characters.
As i said it PASS but doesnt show IMEI, version base band , bluetooth address, Serial number ,
Thank you very much spflash tool. Had to get another phone.
Phone is a MEDIATEK mt6763T.
Only thing that i dont understand from guide is how to enter Serial number in sn writer. Did it many ways. 33 characters and 64 characters with spaces.
If anyone has any idea , please show me the way. thx.
Related
Hello All,
I would like to share will all my experience with the Galaxy S, and because there is a lot of information in the web, I will try to put all the information that I collect about the Galaxy S in this post.
My Galaxy S I9000 have this Firmware Version: I9000XWJPF/I9000OXX/I9000XXJPP/I9000XWJPF
All the ROM that I try, from me this is the better one. All working and the problem with the 3 button is fixed and you are able to enter in recovery/download mode.
Download my ROM - http://everyrandom.com/sgs/lookup.php?productcode=GT-I9000HKATPH&lookup=premade
The ROM is encrypted, to decrypted use the DecoderTest.exe (Download Decoder.zip)
Decrypt string is 3222896
How to decrypt the file! : decodertest.exe filename pwd
In this case, put the files on the same folder and run the command on the cmd decodertest.exe GT-I9000_I9000XWJPF_I9000OXXJP8_I9000XXJPP_I9000XWJPF_XW_TPH.zip.enc 3222896
Access to Recovery mode/Download Mode
To access recovery mode, follow these steps carefully:
1) After powering off, remove and reinsert the battery (just to ensure it has fully shut down – this isn't strictly required).
2) Hold down the home key and volume up simultaneously.
3) Keeping those buttons help, hold down power.
4) Once the screen turns on, release the power button but keep holding the other two.
5) Release the other two buttons once the phone has entered recovery mode. If the start animation begins to play, the phone has not entered recovery mode.
To access download mode, follow these steps carefully:
1) After powering off, remove and reinsert the battery (just to ensure it has fully shut down – this isn't strictly required).
2) Hold down the home key and volume down simultaneously.
3) Keeping those buttons help, hold down power.
4) Once the screen turns on, release the power button but keep holding the other two.
5) Release the other two buttons once the phone has entered download mode. If the start animation begins to play, the phone has not entered download mode
Get Download Mode without 3-button combo using homemade JIG
Get Download Mode without 3-button combo using homemade JIG when nothing else is working and your phone is DEAD - http://forum.xda-developers.com/showthread.php?t=819551
I have this problem and I build one from me and work perfect - http://forum.xda-developers.com/showthread.php?t=819551&page=50
My Homemade JIG
{
"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"
}
Unlock Galaxy S I9000
See this post (It's very good): http://forum.xda-developers.com/showthread.php?t=761045
I unlock with the following method, but you can use one different on the post above.
ALL METHODS FOR NEWER PHONES REQUIRE ROOT... PLEASE GO GET ROOT ON YOUR PHONE AND THEN COME BACK.
I cannot be held responsible for anything that happens to your phone
Step 1. I use the SuperOneClick application http://forum.xda-developers.com/showthread.php?t=803682
You NEED to put your phone on USB Debugging mode
Unplug your USB Cable
Go to Settings > Applications > Development
check USB Debugging
You NEED to install make sure the Android drivers for your phone are installed
Make sure you DO NOT mount your SD card.
If you still can't get something to run, try doing it in recovery mode.
And click on Shell Root
Step 2. - Retrieve nv_data.bin file
use "adb shell" or a terminal emulator to get a terminal prompt and run the following commands
Code:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
Step 3. - Edit nv_data.bin file
mount the internal SD Card on your computer
make a backup copy of the nv_data.bin file on your computer
using your favorite HEX editor open the nv_data.bin on the sdcard
jump to address 0x181468
you should see a string like this
ff 01 00 00 00 00 46 46
there are 5 different types of locks in 5 different bytes
the FF byte should be left alone
the first byte after the FF is the network lock
the next byte is the network subset lock
the next byte is the sp lock
the next byte is the cp lock
the last byte appears to be a data lock.
the 46 46 should be left alone
Change any 0x01 to 0x00 (or 0x00 to 0x01 to lock for warranty)
save and close file
unmount SD Card
Step 4. - Replace nv_data.bin file
I want to say it again so no one misses it MAKE SURE YOU HAVE A BACKUP OF YOUR NV_DATA.BIN FILE BEFORE YOU CONTINUE!!!!!
use "adb shell" or a terminal emulator to get a terminal prompt and run the following commands
Code:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
your phone is now unlocked... enjoy
Make sure that Network Lock is the only thing on... go to phone and enter *#7465625#
Another useful page to unlock the phone http://www.mobiletechworld.com/2010/08/23/sim-unlock-your-samsung-galaxy-s-in-less-than-five-minutes-without-rooting-it/
Firmware/ROMS Galaxy S I9000
I9000 Firmware/How to flash with only one file/How to flash with three files/Flash tools/Flash tutorials - http://www.samfirmware.com/WEBPROTECT-i9000.htm
How to install Froyo (In Portuguese) - http://www.pcdiga.net/showthread.php?37994-TUTORIAL-Instalar-%28Android-2.2%29-FROYO-I9000XXJPM-via-ODIN-no-Samsung-Galaxy-S
Samsung Galaxy S Custom ROM List - http://alchemistar.blogspot.com/2010/10/samsung-galaxy-s-custom-roms-list-1014.html
[Tutorial] SGS TMN » Tudo-em-um!! (In Portuguese) - http://www.androidpt.com/index.php?option=com_kunena&func=view&catid=74&id=60548&Itemid=30
How to Upgrade Galaxy S to Android 2.2 [Tutorial] - http://www.techlivez.com/2010/07/how-to-upgrade-galaxy-s-to-android-2-2-tutorial/
GUIDES, TUTORIALS...
HOWTO, FAQ, Guides, Tutorials, Flash/Root/ADB/ROM. MUST READ! - http://forum.xda-developers.com/showthread.php?t=723596[/B][/SIZE]
How To: Use Odin To Upgrade Samsung Galaxy S GT-I9000 To Froyo - http://www.addictivetips.com/mobile/how-to-use-odin-to-upgrade-samsung-galaxy-s-gt-i9000-to-android-2-2-froyo-download/
How to Use Android ADB Command Line Tool - http://www.londatiga.net/it/how-to-use-android-adb-command-line-tool/
How, What & Where - http://www.samsunggalaxysforum.com/tutorials/how-what-where/
[WINDOWS APP] Kies Registry Patcher 1.7.0.0, patch registry on latest Kies - http://forum.xda-developers.com/showthread.php?t=835628
I9000 Codes
Page Source: http://forum.gsmhosting.com/vbb/f258/samsung-galaxy-s-working-codes-1046184/
These codes have been obtained by decoding various .apk files present in the phone firmware.
*#*#4636#*#*
This code can be used to get some interesting information about your phone and battery. It shows following 4 menus on screen:
* Phone information
* Battery information
* Battery history
* Usage statistics
*#*#7780#*#*
This code can be used for a factory data reset. It'll remove following things:
* Google account settings stored in your phone
* System and application data and settings
* Downloaded
It'll NOT remove:
* Current system and bundled applications
* SD card files e.g. photos, music files, etc.
PS: Once you give this code, you get a prompt screen asking you to click on "Reset phone" button. So you get a chance to cancel your operation.
*2767*3855#
Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
PS: Once you give this code, there is no way to cancel the operation unless you remove the battery from the phone. So think twice before giving this code.
*#*#34971539#*#*
This code is used to get information about phone camera. It shows following 4 menus:
* Update camera firmware in image (Don't try this option)
* Update camera firmware in SD card
* Get camera firmware version
* Get firmware update count
WARNING: Never use the first option otherwise your phone camera will stop working and you'll need to take your phone to service center to reinstall camera firmware.
*#*#7594#*#*
This one is my favorite one. This code can be used to change the "End Call / Power" button action in your phone. Be default, if you long press the button, it shows a screen asking you to select any option from Silent mode, Airplane mode and Power off.
You can change this action using this code. You can enable direct power off on this button so you don't need to waste your time in selecting the option.
*#*#273283*255*663282*#*#*
This code opens a File copy screen where you can backup your media files e.g. Images, Sound, Video and Voice memo.
*#*#197328640#*#*
This code can be used to enter into Service mode. You can run various and change settings in the service mode.
, GPS and Test Codes:
*#*#232339#*#* OR *#*#526#*#* OR *#*#528#*#* - WLAN test (Use "Menu" button to start various tests)
*#*#232338#*#* - Shows WiFi MAC address
*#*#1472365#*#* - GPS test
*#*#1575#*#* - Another GPS test
*#*#232331#*#* - Bluetooth test
*#*#232337#*# - Shows Bluetooth device address
*#*#8255#*#*
This code can be used to launch GTalk Service Monitor.
Codes to get Firmware version information:
*#*#4986*2650468#*#* - PDA, Phone, H/W, RFCallDate
*#*#1234#*#* - PDA and Phone
*#*#1111#*#* - FTA SW Version
*#*#2222#*#* - FTA HW Version
*#*#44336#*#* - PDA, Phone, CSC, Build Time, Changelist number
Codes to launch various Factory Tests:
*#*#0283#*#* - Packet Loopback
*#*#0*#*#* - test
*#*#0673#*#* OR *#*#0289#*#* - Melody test
*#*#0842#*#* - Device test (Vibration test and BackLight test)
*#*#2663#*#* - Touch screen version
*#*#2664#*#* - Touch screen test
*#*#0588#*#* - Proximity sensor test
*#*#3264#*#* - version
CHANGE CSC!!!
It's very simple, just use this code *#272*PHONEIMEI*
For Portugal choose TPH
THIS WILL RESET YOUR PHONE
Source (In Portuguese) - http://www.androidpt.com/index.php?option=com_kunena&func=view&catid=74&id=80703&Itemid=30
GAMES AND SOFTWARE!!!
Games and Software to Android - http://forum.mobilism.org/viewforum.php?f=398&sid=45f53874a94379957b31b2c8e3c1f4b1
Android Games and Applications - http://droidappz.org/
Connect Samsung Galaxy S to Ad-hoc Network
Connect Samsung Galaxy S to Ad-hoc Network(NOT TESTED YET) - http://www.blogsolute.com/fix-connect-samsung-galaxy-s-to-ad-hoc-network/11907/
Once again I cannot be held responsible for anything that happens to your phone
I want to thank everyone who worked hard to give us these solutions, tips, manuals, firmware, ect ... NICE WORK!!!
Thanks Mutega
Thanks for your tips.
You're tha man !
Sticky?
10 chars.
Change CSC is: *#272*PHONEIMEI#
Regards
will this firmware work on a i9000b?
hello there.......nice post man!.
question: what version is your phone?,i have a i9000b bought in argentina,(carrier-personal) and neither recovery/download mode works. so i can't do anything till i get 3 button mode back.
best regards.
I already had one that was not working the 3 buttons, after I unlock and put this ROM GT-I9000XXJP8 the 3 buttons start working.
You can you the adb (This comes with the tools of the AndroidSDK) to enter in recovery and download mode.
Recovery mode: adb.exe reboot recovery
Download mode: adb.exe reboot download
You NEED to put your phone on USB Debugging mode
Unplug your USB Cable
Go to Settings > Applications > Development
check USB Debugging
Cheers
Fellows, how do I check my battery mAmps? Any code for that? I got a new one, supposedly 1600 mAmp but ...how do I verify it's really 1600?
The only code I know is this one *#*#4636#*#*
You can check this code and more codes here! http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
Cheers
mutega said:
The only code I know is this one *#*#4636#*#*
You can check this code and more codes here! http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
Cheers
Click to expand...
Click to collapse
Thanks, but that only gives me the %. What i'm after is the actual capacity, the mAh. Wanna check if the vendor's info - 1600 mAh - is in fact true.
Great post, bookmarked!
I use prohram called Android Assistant (free on market) and it give me data wich you need. I remember that almost every batteri app i tried have those info.
Sent from my GT-I9000 using XDA App
Sorry for wrong info. Android Assistant DOSENT have info you want. Still, battery aps do.
Sent from my GT-I9000 using XDA App
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.
WORK IN PROGRESS.. UNTIL NOW NOT GETTING 100%
This was for CM11s, Don't try on CM12s
As soon as we found right procedure we'll Update here
This tutorial is not for newbies.. If you are not little advance user don't do this
After reboot Values reset to Orignal setting (Reset)
need to prevent NV recovery
1. Download Files Here containing all the necessary files and extract it on desktop.
2. Enable Android Debugging on your phone and connect it to your computer,
3. Open up ADB and type the following:
Code:
adb shell
su
setprop sys.usb.config diag,adb
4. Launch Device Manager go to & expand Other Devices,
Right click Android (or something related) listed under that menu
Choose Update Driver Software,
Browse my computer for driver software,
Let me pick from a list of device drivers on my computer,
Just Click Next,
Have Disk,
Browse to where you extracted YU Diagnostics Driver folder
Inside you will find 32bit and 64bit versions, pick one as per your OS
Select htcdiag.inf (for 32bit) or HtcUsbMdmV64.inf (for 64bit) file that you will Open.
Accept all warning messages and let the installation of the driver complete.
5. Once everything is done installing, under Modems or Ports (Com & LPT) in Device Manager you will find HTC USB Modem.
Right click and select Properties; in this you will see Port: COM<number>. Remember that COM<number> or write it down.
6. Open QPST v2.7 Build 4.11 > run as administrator setup.exe (Don’t run QPST.2.7.411.msi)
7. Open QPST Configuration from Start Menu,
Go to the Ports tab,
Click on Add New Port (right bottom corner);
In the Port field type in the COM<number> you wrote down/remembered from step 5 and in Port Label type YU and finally click OK (left bottom corner).
If you've followed all the steps correctly until here, you should be able to see something like this in the Active Phones tab:
View attachment 3258366
Keep QPST Configuration window open
8. Open QXDM-3.12.714 > run as administrator setup.exe (Don’t run QXDMInstaller.msi)
9. Open QXDM Professional (run as administrator),
go to Options menu,
Select Communications
Set Target port to your phone COM<number> you wrote down/remembered from step 5 from dropdown list, Press OK.
View attachment 3258367
10. Back to QXDM main window, in the "View" drop-down menu, selects NV Browser
View attachment 3258368
now the fun part begins
View attachment 3259381
Put check mark on Dual SIM (as shown above SS) for apply all setting to both SIMs (Thanks to @tirta.agung)
11. Inside the NV Browser window,
Scroll down and click on line 01877 (rf_bc_config)
Click the Read button save original value in notepad in case something goes wrong.
Replace Input value with 3460734838925427584
Click on Write button.
12. Inside the NV Browser window,
Scroll down and click on line 00946 (band_pref_16_31);
Click the Read button, save original value in notepad in case something goes wrong.
Replace Input value with 0x0FF8 (please don't be an idiot and don't edit the empty one with "nam" in the name)
Click on Write button.
13. Inside the NV Browser window,
scroll down and click on line 02954 (band_pref_32_63);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 805765120 (please don't be an idiot and don't edit the empty one with "nam" in the name)
click on Write button.
14. Inside the NV Browser window,
scroll down and click on line 00441 (band_pref);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 0x380 or 0xFFFF (please don't be an idiot and don't edit the empty one with "nam" in the name)
click on Write button.
If you have problem with selection, you can edit it directly from your phone: *#*#4636#*#* /Phone information /Menu /Select radio band > Automatic
15. Inside the NV Browser window,
scroll down and click on line 06828 (lte_bc_config);
click the Read button, save original value in notepad in case something goes wrong.
replace Input value with 1904863 (please don't be an idiot and don't edit the empty one with "ext" in the name)
click on Write button.
16. Now Close QXDM; Wait 30 seconds,
disable Android Debugging on your phone,
unplug it and reboot your device;
Once it comes back on, it might take a minute or two for it to acquire signal so don't panic.
DO this on your own risk.. No body is responcible for any lost
Conclusion:
The only real way to know if the whole thing got applied is to do steps 1 through 10 again (obviously skipping installations)
and reading all values or if you are in an area where you previously had bad or no reception.
You can see unlocked GSM/UMPTS bands from the *#*#4636#*#* /Phone information /Menu /Select radio band
For more features of QXDM i.e. recover lost IMEI or ESN go HERE (Thanks to @tirta.agung)
Credits:
Thanks to @BlackSoulxxx for his original work with the Qualcomm baseband software, for the modified Drivers and for the LTE NV values
Thanks to @olokos for his original tutorial
Thanks to @devilsshadow for his original tutorial
Thanks to @Albirew for his original tutorial
Thanks to @tirta.agung for bringing the original thread to my attention & Guide me in many ways
Thanks to @fards for finding the diagnostics command that made all this possible
Thanks to @hem12 who raised my will for finding these tutorials.
Thanks to @d3athwarrior for post this tutorial.
Reserved
Don't forget to put check marks on dual sims, and apply all settings to sim0 and sim1 (see attachment). By the way before u messed things up, back up your modemst1, modemst2, fsc, and fsg.
By the way we can also use qxdm to recover lost imei, just go to 0550, and insert your imei for SIM 1 (sim0 in qxdm) and SIM 2 (sim1 in qxdm), for example:
Code:
If your IMEI was: 954091051099226, then the boxes would look like so:
8
9a
45
90
1
15
90
29
62
or also recover lost esn (item no 0 and 5597) or meid (1943 and 5598).
Great guide, guys !:good::good::good:
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
BlackSoulxxx said:
Great guide, guys !:good::good::good:
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
Click to expand...
Click to collapse
Yes you'r right.. I don't want to leave anyone in credit for them work :good:
OPO removed :Hawkeye:
but that works for me..
Need help for prevent NV recovery from you all
If it's the same as the 1+1, replacing /system/bin/rmt_storage with a version not locked would prevent nv recovery (do you know if NV values were sticking in an older version? If so, take it's rmt_storage and try to replace current one with older one, I think it's worth trying)
Albirew said:
If it's the same as the 1+1, replacing /system/bin/rmt_storage with a version not locked would prevent nv recovery (do you know if NV values were sticking in an older version? If so, take it's rmt_storage and try to replace current one with older one, I think it's worth trying)
Click to expand...
Click to collapse
Hmmm, as far as I know, all NV settings, including IMEI, or MEID, ESN, etc, resides in your modemst1 and modemst2 partition. If you don't believe me and eager to try, first make a backup of those two partitions, then format or wipe the two partition inside your phone (use fastboot to do this), I'll bet for your YU, now your IMEI and NV settings are all gone.
To be honest, I just found out from this thread that there is an rmt_storage in CM phones, wkwkwkwkw, . If the rmt_storage function is trough, then CM is locking the phone NV settings from the HLOS side not Non-HLOS side. I'll do some research on this rmt_storage.
Need Help from your side
tirta.agung said:
Don't forget to put check marks on dual sims, and apply all settings to sim0 and sim1 (see attachment). By the way before u messed things up, back up your modemst1, modemst2, fsc, and fsg.
.....
or also recover lost esn (item no 0 and 5597) or meid (1943 and 5598).
Click to expand...
Click to collapse
BlackSoulxxx said:
Great guide, guys !:good::good::good:
Some error down there: "OPO" and huge load of credited people that seem dont fit in here. Clearly copied from OPO thread?
Click to expand...
Click to collapse
Albirew said:
If it's the same as the
.....
current one with older one, I think it's worth trying)
Click to expand...
Click to collapse
Now current status is
when I connect mobile
it shows me like that
Even I change USB config to diag,adb
thru ADB or manually
this time its present in default.prop
I try both
trying to disable MTP in mobile USB connection is not working
Window for Settings > Storage > 3dot > USB computer connection is working
but when I disable MTP.. its not working3
So need help from your side..
how I enter / install diag mode
@tirta.agung
I read your complete Guide regarding unbrick YU
but as that post has multipal guides ... I little confused ..
Sorry I am Xtreme noob for all that
Can you guide me an easy way to connect with QPST for enable LTE band
Can I try
Guide #3. REVIVING YOUR IMEIs (That for 32bit or 64bit)??
for connect QXDM
ekhasti said:
@tirta.agung
I read your complete Guide regarding unbrick YU
but as that post has multipal guides ... I little confused ..
Sorry I am Xtreme noob for all that
Can you guide me an easy way to connect with QPST for enable LTE band
Can I try
Guide #3. REVIVING YOUR IMEIs (That for 32bit or 64bit)??
for connect QXDM
Click to expand...
Click to collapse
Yes use guide number three, and download the necessary file there. By the way, to use the guide you have to be in stock CM kitkat.
How to use these tools for Xperia C6602
Long story short, did it work in the end for more than 1 person?
thanks for the post. but i have a Lollipop rom. I will wait for you to update the thread ....
Can we try this in lollipop??? Is there any update on this???
ekhasti said:
WORK IN PROGRESS.. UNTIL NOW NOT GETTING 100%
CM12s
As soon as we found right procedure we'll Update here
Click to expand...
Click to collapse
Hi there, attached is boot.img and a hack rmt_storage for CM 12.1. Just flash the boot.img to your phone and connect it with QXDM. Your phone will be recognized as qualcomm diagnostic port 903A. Copy and paste (you can use TWRP's file manager to do this) the rmt_storage to "/system/bin" and change its permission (chmod) to 0755. This will make your changes stick upon reboot.
By the way, to use all these files, you need to be on stock CM 12.1. I haven't tried it on any other ROM.
Bro...im on cm12.1 ...rooted...I didn't understand the procedure... Pls can u explain step by step ..pls....wats that qxad ..? Is a software...? Wer I get that..,pls reply bro
Sent from my AO5510 using XDA Free mobile app
tirta.agung said:
Hi there, attached is boot.img and a hack rmt_storage for CM 12.1. Just flash the boot.img to your phone and connect it with QXDM. Your phone will be recognized as qualcomm diagnostic port 903A. Copy and paste (you can use TWRP's file manager to do this) the rmt_storage to "/system/bin" and change its permission (chmod) to 0755. This will make your changes stick upon reboot.
By the way, to use all these files, you need to be on stock CM 12.1. I haven't tried it on any other ROM.
Click to expand...
Click to collapse
Now i upgraded to cm13.....can these two files work for me....pls reply
Sent from my AO5510 using XDA Forums
@ekhasti
I have tried doing this on Yureka - CM11 XNPH05Q. Installed all the drivers & softwares successfully. When I startup the QPST config to add a new port,
1. I have to uncheck the "Show serial and USB/QC diag ports only" to make the HTCUSBModem port visible.
2. Although I am able to add the port successfully I am unable to see the phone number, it says "No Phone".
Since it is unable to get the phone details I am unable to proceed further. Nothing is visible/editable QXDM. either.
I have manually edited the build.prop file to make sure USB debugging is enabled but to no avail. Please check the attached files, what is it that I am missing?
P.S - I am able to get my IMEI number using *#06#
Any suggestion Guys???
bluebl0od said:
Any suggestion Guys???
Click to expand...
Click to collapse
Guys, I am eagerly waiting for your updates
I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
{
"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"
}
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!
will update screenshots and pics soon
this is a holding place
Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?
954wrecker said:
Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?
Click to expand...
Click to collapse
Did you try the link I provided?
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Was merely trying to delute the guide to a step by step process leaving out no details for people not familiar with root.
954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Did the link work for you? I fixed some link issues in my html link I hope it works as flawlessly for everyone as it did myself.
The page looked the exact same when I agreed to the huge list of terms, but yours took me to the correct place to get the unlock code instead if the servers are busy page. Thanks for the help
Stuck on stock for 3 days really makes the non stock ROMs 10000% smoother! That emui is a trainwreck, it's going to be impossible to go back to that mess.
kobos311 said:
I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!
Click to expand...
Click to collapse
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?
It's already been found (on the first part) just type fastboot oem unlock fastboot and adb go hand in hand.
Remember once your bootloader is unlocked you will have to go through the initialization process and toggle developer options on again
AsapJuno said:
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?
Click to expand...
Click to collapse
Please follow the guide as stated.dont deviate thank you.
definitely tried that. Wouldn't be commenting if I didn't. Can you help
Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI code
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
AsapJuno said:
definitely tried that. Wouldn't be commenting if I didn't. Can you help
Click to expand...
Click to collapse
ASAP Juno, it's already detected your device via adb adb/fastboot are linked just type the commands don't worry about checking fastboot.
any other methods for retrieving the pin code ?
jusdef said:
Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI cod
Click to expand...
Click to collapse
kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?
jusdef said:
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?
Click to expand...
Click to collapse
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help
So when I install SuperSU, wipe, and reboot... it boots back into twrp
kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
kobos311 said:
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help
Click to expand...
Click to collapse
Wrong user, I didnt say I did not have imei's and I can't do a Nandroid backup if my phone isnt rooted. I'm trying to unlock my bootloader so I can take the steps to root and install TWRP. Huwai site will not let me submit the request without the pin #.
I want(ed) to develop a small app for my DZ09 clone smartwatch.
Unfortunately (and it took me a while to realize this) it uses a MT6261DA SoC which means .vxp apps are not an option
However, it does have a hidden (*#00000000#) "AppStore" app, which means it might still be possible to write/launch my own apps
In case anyone is interested, I downloaded all available apps. Simply download and extract the .zip file into the root directory of your microSD card. You don't need to activate them
https://gofile.io/?c=qp7AvP
To be continued?
Reverse engineering is fun
https://youtu.be/Fk3a33H3Cp8
Here is a soundboard app, created by yours truly
Instructions:
Download the attached zip file and copy its contents to x:\zmaee\00000102\ (where "x" is the drive letter of your microSD card). Then use the hidden AppStore app (*#00000000#) to launch the app. To exit the app, swipe from the top of the screen to the bottom.
Link is no working plz send another link
kemo6006 said:
Link is no working plz send another link
Click to expand...
Click to collapse
There's nothing wrong with the link, it still works.
very interesting. and thanks for sharing. I may have questions later, but for now, just wanted to up your thanks meter and mark the thread subscribed.
unfortunately some how it's not working for me it's say checking for 2 minutes then no games shown
{
"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"
}
kemo6006 said:
unfortunately some how it's not working for me it's say checking for 2 minutes then no games shown
Click to expand...
Click to collapse
That's weird. Are you sure you extracted the zip file correctly to the root of your microSD card? It should look like this:
x:\zmaee\00000001\00000001.app
x:\zmaee\00000001\00000001.md
x:\zmaee\00000001\icon.zbmp
x:\zmaee\00000001\cfg\class.dat
x:\zmaee\00000001\cfg\class_item.dat
x:\zmaee\00000001\cfg\hotlist.dat
x:\zmaee\00000001\cfg\iconsize.dat
x:\zmaee\00000001\cfg\menu.dat
x:\zmaee\00000001\cfg\menu_item.dat
x:\zmaee\00000001\cfg\menu_text.dat
x:\zmaee\00000001\cfg\rolltxt.dat
x:\zmaee\00000001\cfg\update.dat
x:\zmaee\00000001\cfg\zmnotice.dat
x:\zmaee\00000001\hoticons\1033.zbmp
x:\zmaee\00000001\hoticons\1076.zbmp
x:\zmaee\00000001\hoticons\1142.zbmp
etc.
EDIT: I was able to reproduce your issue by deleting the x:\zmaee\lib folder, which means you did not extract the zip file to the root of the microSD card or not all files were extracted.
I tried with no luck same issue also with new micro sd card it is may be firmware issue or my device has no enough ram
here is my device ram test
=============== Memory Detection Report ===============
Internal RAM:
Size = 0x0000D000 (52KB)
External RAM:
Type = SRAM
Size = 0x00400000 (4MB/32Mb)
NOR Flash:
Device ID = "[MXIC] MX25L3291FWJI_09" (274)
Size = 0x00400000 (4MB/32Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
============ RAM Test ============
Data Bus Test :
[D0][D1][D2][D3][D4][D5][D6][D7][D8][D9][D10][D11][D12][D13][D14][D15]
OK!
Address Bus Test :
[A1][A2][A3][A4][A5][A6][A7][A8][A9][A10][A11][A12][A13][A14][A15][A16][A17][A18][A19][A20][A21]
OK!
RAM Pattern Test :
Writing ...
0x44332211,
0xA5A5A5A5,
0xA5A5A500,
0xA500A500,
0xA5000000,
0x00000000,
0xFFFF0000,
0xFFFFFFFF,
OK!
Increment/Decrement Test :
Writing ...
OK!
kemo6006 said:
I tried with no luck same issue also with new micro sd card it is may be firmware issue or my device has no enough ram
here is my device ram test
Click to expand...
Click to collapse
Here is what you can do to help me figure out what is wrong:
1. Delete the "zmaee" folder on the microSD card.
2. Insert a SIM card that has mobile data.
3. Use the secret code to launch Game Center, it will connect to the internet and download the necessary files.
4. Exit Game Center, zip the "zmaee" folder and send it to me so I can have a look.
_tim_ said:
Here is what you can do to help me figure out what is wrong:
1. Delete the "zmaee" folder on the microSD card.
2. Insert a SIM card that has mobile data.
3. Use the secret code to launch Game Center, it will connect to the internet and download the necessary files.
4. Exit Game Center, zip the "zmaee" folder and send it to me so I can have a look.
Click to expand...
Click to collapse
i tried this methods i cant install game center its say Library Update then User Init then Time out and i looking in zmaee folder found 2 folders first one called Lib and contain two files zmsys001.dll and zmsys001.so and other folder called tmp and its empty.
kemo6006 said:
i tried this methods i cant install game center its say Library Update then User Init then Time out and i looking in zmaee folder found 2 folders first one called Lib and contain two files zmsys001.dll and zmsys001.so and other folder called tmp and its empty.
Click to expand...
Click to collapse
It looks like it can't load zmsys001.dll or zmsys001.so. That explains why Game Center is broken. I think there's something wrong with your watch.
can you send me your watch firmware to test on my watch may be fix this issue
kemo6006 said:
can you send me your watch firmware to test on my watch may be fix this issue
Click to expand...
Click to collapse
That won't be necessary, I found the cause of your problem and a solution. If you check "SSC Info" (*#00000000#) then you will see that your "UsrId" value is "0". When user id is 0 the watch tries to get a new user id from the zmaee server but this no longer seems to work. I wrote a small app that can set a random user id.
- download zip file
- create x:\zmaee\000004d1 folder and extract zip file into this folder
- launch "Browser" app
- tap on "set random user id"
- tap on "exit"
- remove x:\zmaee\000004d1 folder
_tim_ said:
That won't be necessary, I found the cause of your problem and a solution. If you check "SSC Info" (*#00000000#) then you will see that your "UsrId" value is "0". When user id is 0 the watch tries to get a new user id from the zmaee server but this no longer seems to work. I wrote a small app that can set a random user id.
- download zip file
- create x:\zmaee\000004d1 folder and extract zip file into this folder
- launch "Browser" app
- tap on "set random user id"
- tap on "exit"
- remove x:\zmaee\000004d1 folder
Click to expand...
Click to collapse
i try this method but when Push get user id still 0
this app generate 10 digit random numbers may be length to big for user id.
kemo6006 said:
i try this method but when Push get user id still 0
this app generate 10 digit random numbers may be length to big for user id.
Click to expand...
Click to collapse
I reflashed my firmware, my user id got reset to 0, I launched my user id app, tapped on "get user id", it said "0", tapped on "set random user id", it displayed a number, I tapped on "get user id", it showed that same number. If your user id stays 0 then the "set user id" function I am using, which works on my watch, doesn't seem to work on your watch.
This is the firmware that I used:
https://drive.google.com/open?id=0B_hRh3DjuBoeaUxsZFlmZzIzS28
can you edit the length to be 6 or 7 digit and try again
kemo6006 said:
can you edit the length to be 6 or 7 digit and try again
Click to expand...
Click to collapse
Yes.
_tim_ said:
Yes.
Click to expand...
Click to collapse
also this modification not working i try to install you flash into my watch i got this messege
is it safe to total format and try again (notice i already have readback backup for my watch)
and my firmware release date is 12-18-2017
finaly here is my backup firmware you may find fix for game center issue.
https://my.pcloud.com/publink/show?code=XZmG8ukZyafdNv40I7RJ783DlJjN3hTwiiIy
Thank you for your patient
kemo6006 said:
also this modification not working i try to install you flash into my watch i got this messege
is it safe to total format and try again (notice i already have readback backup for my watch)
and my firmware release date is 12-18-2017
Click to expand...
Click to collapse
I don't know what that error means, but my firmware is probably not going to be useful anyway because I flashed your firmware on my watch and the touchscreen doesn't work. Different touchscreen controllers.
kemo6006 said:
finaly here is my backup firmware you may find fix for game center issue.
Thank you for your patient
Click to expand...
Click to collapse
I will try to decompress/decompile your firmware to see what the "set user id" function does.