Related
This Howto describes whole procedure to install Android 2.3.4 Gingerbread to Samsung Galaxy S I9000/I9000M
BEWARE: Following theese steps can be potentially dangerous. You are going to undergo potentially risky operation. In bad case, or if you do something wrong, you may brick your phone. Feel free to ask, if you are unsure.
First try to boot your phone in Download Mode (described in the howto, so look for it). If it works, follow Instructions in [Block 2]
If it does not work, ie. you can't boot your phone in Download Mode, then start with Instructions in [Block 1]
First of all, download I9000XXJVQ_by_Virnik.rar and extract it somewhere (for example on your desktop). All files mentioned in this howto are compressed in this package. Enter FLASH directory you have extracted. All things needed are categorized in it's specific folders.
You will get following folders from it (Inside extracted FLASH folder):
- Kernel
- Odin
- ROM
- Theme
And for the Theme, there are two Theme versions in the big RAR archive. DeepBlue and DeepPurple. Both can be outdated, so check their threads, to have latest one.
We will use all of them in [Block 2] of this howto.
Please understand, that Ficeto's Deodexed JVQ ROM zip package in this big archive is not same as official Ficeto's ROM, I have changed installed kernel and modem, to suit my needs. I have also removed few unnecessary apps from it.
[Block 1]
If you have problem with button combo, which means that your phone ignores Download mode and startup normally, follow theese instructions:
Preparations: Make sure you have the drivers installed (i.e Kies is recognizing the phone), adb available and "USB Debugging" turned on in "Settings -> Applications -> Development" menu. Type *#0228# in the dialer and check Voltage value (without USB plugged in) is atleast 3800(mV).
1] Unplug the phone from the computer (if connected)
2] Kill all Kies related software (tray agent, etc)
3] Start Odin
4] Plug in the phone to the computer
5] Start a new command prompt and navigate to the folder / drive where adb is located. If you haven´t downloaded adb yet, get it here.]
6] Type "adb reboot download" to the command prompt and press enter.
7] Switch to Odin and select the Aries_P-SBL.tar.md5 as PDA file. Make sure "Phone Bootloader Update" is ticked and re-partition is unticked. Do not select any other files but "Aries_P-SBL.tar.md5".
8] Press "Start" button to launch the update process. It will take around three seconds to complete. After the update phone will reboot automatically.
Thanks Richthofen for this part of my howto]
[Block 2]
If your phone is NOT branded and SIM-Locked, your way to new firmware is much more shorter. Follow theese instructions:
01] Enter Odin folder and startup Odin.
a) Click PIT Button, select s1_odin_20100512.pit file
b) Click PDA Button, open ROM/Stock folder and select CODE.tar file.
c) Click PHONE Button, open ROM/Stock folder and select MODEM.tar file.
d) Click CSC Button, open ROM/Stock folder and select CSC.tar file.
e) Tick "Re-Partition and if you were using Froyo previously, "Phone Bootloader Update" tick boxes
02] Power off your phone and make sure you have SIM card out, SD card out. Disconnect USB.
03] Press and hold 3-button combo, to boot your phone in Download mode (Volume down, Home, Power)
04] Connect your phone to the PC via USB cable.
05] In odin, ID:COM field shall change color to yellow, and in Message window, you will see message "Added"
06] Now press Start button.
07] Go and take cigarette, coffee, etc. This will take up to 5 minutes.
08] Phone will reboot itself. Disconnect USB. Pull out battery, once it is booted, and place it back.
09] Press and hold 3-button combo, to boot your phone in Download mode (Volume down, Home, Power)
10] Switch back to Odin, and press "Reset Button"
a) Click PDA Button, open Kernel folder and select CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.tar file
b) Make sure Re-Partition Button IS NOT ticked
c) Connect your phone to the PC via USB cable.
d) In odin, ID:COM field shall change color to yellow, and in Message window, you will see message "Added"
e) Now press Start button.
11] After successfull flash, phone will reboot itself, and Odin will write Success message.
12] Let your phone boot, meanwhile disconnect USB.
13] Once you'll set your language (you can skip all other configuration wizzard's steps), go to the Settings->Applications->Development->USB Debugging and tick it.
14] Connect USB to the phone now. You will notice information "USB Connected" in the notifications. Click it. Mount internal storage. Phone's internal SD card will become visible for the windows as a flash drive.
15] Delete everything from the SD Card, or move it somewhere to your desktop as a backup.
16] Copy XXJVQ_Deodexed_Zipaligned_MultiCSC_signed.zip file from ROM/Deodex directory to your phone's internal SD card.
17] Now it is time to choose. Are you boy, or girl? Because boys will most likely want their phone to be in blue color, girls will prefer Ping/Purple color. After you're decided, copy file of your choose from Theme directory to the internal SD card. You can take a look how it will look like in DeepBlue Theme or DeepPurple Theme threads. It is definitelly worth to look there, because Theme packages in the big RAR archive is not up-to-date as Theme zips in those threads are.
18] Time for another kind of magic. We will use another button combo, this time recovery mode. Press Volume Up, Home, Power
19] In the Recovery Mode, use Volume Up/Down to move in the menu. Select "Install zip from sdcard" and then press Power. Then select XXJVQ_Deodexed_Zipaligned_MultiCSC_signed.zip to install and confirm by pressing Power.
20] Progress bar will show up for a while. After that, select "Reboot system now"
21] Once It'll boot (this will take few minutes, because dalvik cache has been wiped, and needs to be regenerated from new files, and then filesystem conversion will start, so be patient), power off your phone again, and start in recovery.
22] Back in recovery Mode, use Volume Up/Down to move in the menu. Select "Install zip from sdcard" and then press Power. Then select DeepBlueTheme_JVQ_By_Virnik_v099-5.zip file or DeepPurpleTheme_JVQ_By_Virnik_v090-5.zip file to install and confirm by pressing Power. Reboot your phone once it's finished.
OPTIONAL:
Install Neldar's BLN app (paid) from the Market, and enable BackLight Notifications for incomming calls, SMS, emails, and so on.
Performance tips:
Download Tegrak from the Market, and try to overclock your phone to 1100MHz (which is absolute safe on every SGS). Test it a little with games and such, and then try higher value, for example 1200MHz. If your phone freeze, then stay with lower values, if not, you can try even higher value (1400MHz).
Most phones will handle 1200MHz maximum without any bad side effects. My own phone for example, can handle 1152MHz without freezing, and 1200MHz makes my phone freeze from time to time, so you can test it yourself.
You can test with Quadrant or Linpack, to see how your overclock affect overal performance of your phone ;-)
Vocabulary:
Button COMBO:
- Button Combo is trick, in which three buttons are pressed simultaneously, to force some action on the phone.
- Typically, phone can reboot in Download Mode, and Recovery mode. Some providers are disabling this. For this reason, first part of the howto has been created.
a) Download Mode Combo - Power off your phone. Now press Volume Down, Home, Power. If you did everything right and your phone dont have this disabled, your phone will start in Download Mode. You can verify it very easily, because you will have yeallow triangle in the centre of the screen with green Android robot with shovel in hands in the centre. Download Mode is used to flash your phone. Simply, it instruct phone to await data load from your computer. Dont worry, if you start download mode accidentaly, simply restart. It does not break anything.
b) Recovery Mode Combo - Power off your phone. Now press Volume Up, Home, Power. If you did everything right and your phone dont have this disabled, your phone will start in Recovery Mode. You can verify it very easily, because you will have text menu on the screen. You can move between each line by Volume Up (for moving selection UP), Volume Down (for moving selection DOWN) and Home to enter (start chosen action). In Recovery mode, you can apply update from sdcard (typically root kit, or anything inside update.zip, which have to rewrite/update something in the system), Factory Reset, or fix problems (some old versions of One Click Lag Fix broke system up, because it failed to create/delete ext2 partition, which ****ed up internal storage), such as clear phone app cache, reformat internal sdcard, and such.
{
"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"
}
Answers and questions:
Q: Can I use this for updating my Indian/Mexican/Japan phone?
A: Yes. But do not forget that this is european firmware, which means it will allow you to choose from european languages. If you want your phone in your own languages, you will need to choose different firmware from samfirmwares, depending where are you from. Then you can use that firmware, it does not change anything in the howto, except for the firmware nationality.
Q: I have my phone SIM-Locked, what can I do?
A: Follow second part of the howto first.
Q: I have my phone branded/download mode ignored, what can I do?
A: Follow second part of the howto first.
Q: Will it rewrite my files to Korean ones?
A: No. It will use european firmware, if you stick close to this howto.
Q: Will different nationality firmware change anything in this howto? Do I have to follow little bit different instructions?
A: No. You may miss some language support or Swype in your language, but that changes nothing.
Q: Can I hug you?
A: You can - if you are disease free, but I will not travel from my home town. In adition, you will also need to find me yourself ;-)
Q: Where are the files I need to proceed with this howto?
A: Few lines after this sentence Just choose your mirror, and enjoy.
(will be updated, once somebody asks something important)
PS: Once everything finished, install Quadrant from Android Market. Quadrant is very good benchmark. Write here your score please. Better than that, download Quadrant before whole procedure, write down your score, then start upgrade procedure. After finished, compare both numbers - before and after. Now you can feel the difference, aren't you? :-D
PS2: Tired of baterry live time? Here is another tweak. Download SetCPU from Android market. Give it root permission (simply agree, when it asks upon app start), set it to start at boot. Set frequency (min, max) to 1000MHz and policy to ondemand. Create new profile, set it to underclock phone's CPU when display is off to 200MHz. Done. To be sure, restart your phone. From now on, when your phone goes to sleep (simply laying in your pocket with display off), it underclock itself, which save batterry a lot.
PS3: Another baterry eating problem is number of running apps in the background. From Android Market, download Advanced Taskkiller (paid app, but worth it).
Install, setup it to start at boot, to kill unneeded processes every 30 minutes. BEWARE! You will have to set Settings and few other apps u like to be ignored in the Advanced Task manager!
PS4: Want to have nice UI, like the HTC's one? Download Launcher Pro (and pay for it to upgrade to Plus version). Then download Beautiful Widgets (paid too).
Play a little with its settings. Again, it is well worth it.
UPDATE:
Before you proceed, you shall install Busybox from the Market. Run it, and let it download and install busybox environment (to tell it straight - linux commands for the commandline, many apps for the root users uses them).
If you are concerned about Product Code and it's changing, here are procedure to do this. Keep in mind that JPY WILL NOT OVERWRITE your product code. It is fault of older firmware flashed previously. And as whole howto, it will be manual procedure again:
Check you actual Product Code by writing *2767*4387264636# in your dialer.
Then there will be a line that says:
[2] PCode:"your phone model type"
Due to previous flash, it can be wrong. So now we will change it to the proper value:
Text Mode Method:
Download Terminal Emulator from the Market
- Open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with HxD Editor and search for ''KOR'' - change this to the product code matching your country (red marked text should be changed). Im czech, so mine is XEZ. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿ[COLOR="Red"]KOR [/COLOR] GT-I9000HKD[COLOR="red"]KOR[/COLOR]
- Now simply save your changes.
- Connect your SGS with usb, upload ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin /efs/nv_data.bin
Also enter: rm -rf /efs/nv_data.bin.md5
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
GUI Medthod:
Download Android Mate from the Market
- Open the Android Mate, and switch to File Explorer bookmark at the top
- navigate to the /efs folder
- by ticking, select nv_data.bin, and from the bottom menu, choose copy.
- navigate to your sdcard directory (/sdcard for internal SD, or /sdcard/external_sd for external SD, does not matter)
- press Paste from the bottom menu.
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with HxD Editor and search for ''KOR'' - change this to the product code matching your country (red marked text should be changed). Im czech, so mine is XEZ. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿ[COLOR="Red"]KOR [/COLOR] GT-I9000HKD[COLOR="red"]KOR[/COLOR]
- Now simply save your changes.
- Connect your SGS with usb, upload ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Android Mate again, select File Explorer, find and tick your changed nv_data.bin, and press Copy from the bottom menu
- navigate again to the /efs directory, and press Paste from the Bottom Menu.
- tick "nv_data.bin.md5" file, and press Delete from the Bottom Menu (it will be autocreated after reboot)
- exit Android Mate, and reboot your phone.
Available Country Product Codes are here:
ATO -Austria (A1, bob, T-Mobile A, Orange AT, tele.ring, 3, yesss!, aon)
AUT - Switzerland (sunrise, Swisscom, Orange CH)
CNX - Romania (Vodafone RO)
COA - Romania (Cosmote)
COS - Greece (Cosmote)
CRO - Croatia (T-Mobile)
CYO - Greece (MTN, CYTAVODA)
EUR - Greece (WIND GR, vodafone GR, COSMOTE)
HAT - Romania (RO Orange, Vodafone RO, Cosmote)
IRD - Slovakia (Orange, T-Mobile SK, 02 - SK)
KOR - Korea (SEC Test)
MET - Ireland (Meteor)
MOT - Slovenia (Mobitel)
MOZ - Switzerland (Sunrise, Swisscom, Orange CH)
MSR - Serbia (Telenor)
MTL - Bulgaria (MTEL)
O2C - Czech Republic (O2 - CZ)
O2I - IE (02.ie)
ORO - Romania (RO Orange)
SEB - Baltic (LMT GSM, LV TELE2, LV BITE, LT Omnitel, LT Bite, LT TELE2, EE EMT, EE ELISA, EE TELE2)
SIM - Slovenia (Si.mobil)
SMO - Serbia (mt:s, Telenor, Vip SRB)
SUN - Switzerland (Sunrise)
TMZ - Czech Republic (T-Mobile CZ)
TOP - Serbia (Vip SRB)
TPH - Portugal (P TMN, P Optimus, vodafone P)
TRA - Croatia (T-Mobile HR, HR VIP, TELE2)
TSR - Serbia (mt:s)
TWO - Croatia (TELE2)
VDH - Hungary (vodafone HU)
VDI - Ireland (vodafone IE)
VIM - Makedonia (VIP MK)
VIP - Croatia (HR VIP)
VVT - Bulgaria (vivacom)
XEH - Hungary (T-mobile H, pannon, vodafone HY, vodafone HU VMAX
XEO - Poland (Plus, Era, Heyah, Orange, Play)
XEZ - Czech Republic (T-Mobile CZ, O2 - CZ, Vodafone CZ
XFA - South Africa (Vodacom, Vodacom Lesotho, MTN, Cell C, Virgin)
XFC - South Africa (Vodacom, Vodacom Lesotho, MTN, Cell C, Virgin)
XFE - South Africa (Vodacom, MTN, Cell C, Virgin)
XFM - South Africa (Vodacom, Vodacom Lesotho, MTN, Cell C, Virgin)
CPW - UK & IRE (O2 UK, Orange UK, T-Mobile, Virgin Mobile, Vodafone UK, TESCO, BT Mobile, H3G, Asda, O2 IRL, Vodafone IE, Meteor, H3G IE, Tesco Mobile Ireland)
DBT - Germany (T-Mobile D, Vodafone.de, E-Plus, o2 - de)
ITV - Italy (TIM, Vodafone, WIND, H3G)
XEF - France (Orange F, F SFR, BOUYGTEL, NRJ (SFR), Virgin, Tele2, Auchan, Carrefour, NRJ (ORANGE), Orange (340 01), Orange (647 00), Debitel, Leclerc, Digicel)
XEO - Poland (Plus, Era, Heyah, Orange, Play)
XEU - UK & IRE (O2 UK, Orange UK, T-Mobile, Virgin Mobile, Vodafone UK, TESCO, BT Mobile, H3G, Asda, O2 IRL, Vodafone IE, Meteor, H3G IE, Tesco Mobile Ireland)
BMC = Bell Mobility Canada
SER - United Kingdom (O2)
XEE - Nordic Countries (Telenor and others)
XSO - Singtel
MOB - Austria A1 (Mobilcom)
TMH - T-Mobile Hungary
XEN - Netherelands
If you like this thread and if it helped you, please vote for it with five stars, and to be at front page ;-)
If I did help you, please do feel free to thank me by Thanks button.
Works for me!
Thx dude, now thats what I call a How-to !
MagicOnline said:
Thx dude, now thats what I call a How-to !
Click to expand...
Click to collapse
No problem. You know, I can call myself professional in IT, but I know what are people asking, what they want. I know that feel, when you do not understand something and somebody still forces you to find out everything yourself. It is really stupid, because such behaviour can make things worst. If noob is forced to do something risky without any experience, without any concrete help, he can break his own device. This is why I have created this. To help such noobs. And please, do not take word "noob" badly - I have full respect to such people, because even if I am IT expert myself, I am actually noob in many other things.
Will this work on the Canadian GT-I9000M? I've been very reluctant to flash the European firmware onto my SGS, because I've seen how it is just different enough to cause "problems" (read: brick).
Thanks.
mymanchris said:
Will this work on the Canadian GT-I9000M? I've been very reluctant to flash the European firmware onto my SGS, because I've seen how it is just different enough to cause "problems" (read: brick).
Thanks.
Click to expand...
Click to collapse
please read carefully again. Just download canadian firmware instead. all other steps are OK and will work for you
PS: When I bought my phone, I wanted to flash it. It was branded and locked. So I edited Kies registry to canadian firmware info, to update via Kies (and unlock it), which reflashed my phone with canadian firmware. I didnt used it for long (five minutes maybe), because I have used it only to access Download mode. It worked.
But again, If you fear, do not flash. It is simple, risk is high, as you said - you can brick it. But due my experiences, if you can access Download mode or Recovery, there is everytime way back without bricking. Completelly bricked phone means that you have Button Combo's disabled. Then there is no way back except for waranty procedure.
So first make sure you have unlocked and unbranded firmware. If you don't, then unbrand and unlock first.
Nice and comprehencive how-to, but unfortunately, the first part about getting the 3 button combo does not work, at least not on my phone. Kies "upgraded" my phone to JM1.
Any ideas? TIA
KingOfSola said:
Nice and comprehencive how-to, but unfortunately, the first part about getting the 3 button combo does not work, at least not on my phone. Kies "upgraded" my phone to JM1.
Any ideas? TIA
Click to expand...
Click to collapse
Use Kies again, this time regedit to theese values:
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\X]
"SoftwareRevision"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
"ProductCode"="GT-I9000HKDXEU"
"HIDSWVER"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
upper post updated. Sorry, my misstake. Older FW provider disabled download mode too.
KingOfSola said:
Nice and comprehencive how-to, but unfortunately, the first part about getting the 3 button combo does not work, at least not on my phone. Kies "upgraded" my phone to JM1.
Any ideas? TIA
Click to expand...
Click to collapse
I'm not sure what you did with the 3BR to try and fix it, but I followed this advice here: http://forum.xda-developers.com/showthread.php?t=785201 ... and I have mine working fine running JM1 too.
Virnik0 - I came here from the other thread you had 'hijacked' and wanted to follow up the brief discussion.
I switched from KOR to XEU simply by the built-in feature (where it lists all the codes), after backing up my device (contacts etc...). My phone is now running the XEU version so I'm happier now than when I was.
I'm slightly annoyed that even after backing up my contacts etc... it doesn't save the groups I had saved my contacts in! In fact, after the normal reset that changing the country code does, there was no groups to choose from so I had to create these manually, and go through every contact one by one which was very time consuming. Do you have a better way of doing this? I currently have groups; Family, Friends & Work. Although I 'only' have 25 contacts, I've yet to add another 100 and don't want to do this until I'm happy with the way things are.
I'm still yet to try this method you posted, but I do see myself trying this out in the next few days. However, I've heard that the 2.2 update that you're able to get still contains some bugs, and the update that is due to be rolled out is still being worked on before release, which means I may be better off waiting. Your thoughts?
SamuraiHQ said:
I'm not sure what you did with the 3BR to try and fix it, but I followed this advice here: http://forum.xda-developers.com/showthread.php?t=785201 ... and I have mine working fine running JM1 too.
Virnik0 - I came here from the other thread you had 'hijacked' and wanted to follow up the brief discussion.
I switched from KOR to XEU simply by the built-in feature (where it lists all the codes), after backing up my device (contacts etc...). My phone is now running the XEU version so I'm happier now than when I was.
I'm slightly annoyed that even after backing up my contacts etc... it doesn't save the groups I had saved my contacts in! In fact, after the normal reset that changing the country code does, there was no groups to choose from so I had to create these manually, and go through every contact one by one which was very time consuming. Do you have a better way of doing this? I currently have groups; Family, Friends & Work. Although I 'only' have 25 contacts, I've yet to add another 100 and don't want to do this until I'm happy with the way things are.
I'm still yet to try this method you posted, but I do see myself trying this out in the next few days. However, I've heard that the 2.2 update that you're able to get still contains some bugs, and the update that is due to be rolled out is still being worked on before release, which means I may be better off waiting. Your thoughts?
Click to expand...
Click to collapse
I am not sure what bugs are you talking about. I didn't run into single one, JPM should be final 2.2 Froyo release from Samsung. About your contacts grouping problem, try this:
Move your contacts to groups as you like them to be.
Then backup your contact to Google
Then switch airplane mode on, disable wifi, and delete your contacts.
After then, switch airplane mode off, and wait for google sync.
Once done, export your contacts to sdcard.
then import them again.
Now it should be ok.
About the XEU and KOR problem - some people reports (and I ran in the same problems) that after flash, first boot, KOR makes problems creating internal storage. It simply refuses to format sdcard, recovery mode do not help. I am unsure if this is because of firmware itself, or different folder tree format...
ARGGGGHHHH!!!
I've just run into another problem. I just started Kies, and it required an update (which went fine). It's now version 1.5.3.10093_82 but upon connection with my device, the phone screen flickers like it's having an epileptic seizure. The 'MTP Application' on my phone flickers between that, and my home screen. Everything is closed down as normal - and a reboot of my device hasn't fixed this.
I'm thinking the new update has just screwed something up here, as I've never had a problem connecting before. Why does Samsung have to be so bad at everything???
Edit - Thanks for the contact info. I'll give that a try in a bit.
SamuraiHQ said:
ARGGGGHHHH!!!
I've just run into another problem. I just started Kies, and it required an update (which went fine). It's now version 1.5.3.10093_82 but upon connection with my device, the phone screen flickers like it's having an epileptic seizure. The 'MTP Application' on my phone flickers between that, and my home screen. Everything is closed down as normal - and a reboot of my device hasn't fixed this.
I'm thinking the new update has just screwed something up here, as I've never had a problem connecting before. Why does Samsung have to be so bad at everything???
Edit - Thanks for the contact info. I'll give that a try in a bit.
Click to expand...
Click to collapse
Is it your KOR to XEU switched firmware? As I said, KOR firmware should not even boot, but obviously you have managed to make it work...somewhat.
If your download mode works, use my instruction steps to flash it to JPM (JPK first, then JPM, because we need CSC and modem to be used first), and see if it works. It should. If you run into problem where it cant format internal storage after flash (here it comes - KOR firmware to XEU makes this), reboot to recovery, and press factory reset, clean cache, and then internal storage format. then reboot again.
It should work now.
Well I'm assuming it was originally a KOR firmware that was installed, after following the advice here to fix my missing 3BR mode last week. I have since changed the KOR to XEU by using the *#272*HHMM# code. The device reports that it's XEU as does the registry after connecting to Kies the other day.
I think it's the new update, and I've just emailed Samsung now to see what the hell they've done.
I'd rather have this issue fixed before I plan on trying your guide, as I will need to use Kies at some stage, and if I can't use it - I'll be in a world of hurt.
SamuraiHQ said:
Well I'm assuming it was originally a KOR firmware that was installed, after following the advice here to fix my missing 3BR mode last week. I have since changed the KOR to XEU by using the *#272#HHMM# code. The device reports that it's XEU as does the registry after connecting to Kies the other day.
I think it's the new update, and I've just emailed Samsung now to see what the hell they've done.
I'd rather have this issue fixed before I plan on trying your guide, as I will need to use Kies at some stage, and if I can't use it - I'll be in a world of hurt.
Click to expand...
Click to collapse
Hey, hold on!
Are your Download Mode accessible? If yes, than you are clean!
If you have Download Mode available right now, you do not need Kies!
Kies is needed only if somebody have their Download Mode disabled by provider/vedor!
Kies detects firmware by itself, so it is possible that you have gotten into mixed state, in which KOR switched to XEU firmware is detected by Kies as KOR, and overwritten something...
So I am suggesting you to try Download Mode first. If You can access it, you can flash rightaway, and have a pleasure with new JPM
Virnik0 said:
Use Kies again, this time regedit to theese values:
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\X]
"SoftwareRevision"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
"ProductCode"="GT-I9000HKDXEU"
"HIDSWVER"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
upper post updated. Sorry, my misstake. Older FW provider disabled download mode too.
Click to expand...
Click to collapse
Still no go with the 3BR unfortunately.
My initial values where:
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
GT-I9000HKDNEE
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
And after the "upgrade":
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
GT-I9000HKDNEE
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
Virnik0 said:
Hey, hold on!
Are your Download Mode accessible? If yes, than you are clean!
If you have Download Mode available right now, you do not need Kies!
Kies is needed only if somebody have their Download Mode disabled by provider/vedor!
Kies detects firmware by itself, so it is possible that you have gotten into mixed state, in which KOR switched to XEU firmware is detected by Kies as KOR, and overwritten something...
So I am suggesting you to try Download Mode first. If You can access it, you can flash rightaway, and have a pleasure with new JPM
Click to expand...
Click to collapse
Yes it's accessible - it's what I did last week to fix my 3BR
I'm reinstalling Kies now (old version), in any case as I'd like it to work as it should.
Well if I don't need Kies to complete this process then I may as well start this shortly... after I've made myself a drink haha.
Looks like I need to start downloading some files. I already have Odin 1.3 installed, so it's just the smaller files. Thanks for your help.
KingOfSola - See my post on the other page. It works, trust me!
SamuraiHQ said:
Yes it's accessible - it's what I did last week to fix my 3BR
I'm reinstalling Kies now (old version), in any case as I'd like it to work as it should.
Well if I don't need Kies to complete this process then I may as well start this shortly... after I've made myself a drink haha.
Looks like I need to start downloading some files. I already have Odin 1.3 installed, so it's just the smaller files. Thanks for your help.
KingOfSola - See my post on the other page. It works, trust me!
Click to expand...
Click to collapse
Download just one...it is marked by blue font at the bottom of my howto. It has 1GB, and you can find both firmwares in it, root kit, OCLF, battery MOD, and such.
Virnik0 said:
Download just one...it is marked by blue font at the bottom of my howto. It has 1GB, and you can find both firmwares in it, root kit, OCLF, battery MOD, and such.
Click to expand...
Click to collapse
Thank you
WOW! I don't speak Czech, but even I understand a 119 minute wait if I don't register (300kB/s), and a 17 minute wait if I do. I'm not sure about speed on this one aha. I think you should provide your login name and password
KingOfSola said:
Still no go with the 3BR unfortunately.
My initial values where:
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
GT-I9000HKDNEE
I9000XWJM2/I9000NEEJM1/I9000XXJM1/I9000XWJM2
And after the "upgrade":
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
GT-I9000HKDNEE
I9000XXJM1/I9000OXAJM1/I9000XXJM1/I9000XXJM1
Click to expand...
Click to collapse
What are you exactly trying to do?
Is your Download Mode accessible?
Have you tried regedit tweak?
To be successfull with kies (and enable Download Mode), you have to:
Startup Kies, press Update Button, then switch to regedit (DO NOT CLOSE KIES)
regedit, change appropriate values, close regedit.
Back in Kies, press upgrade Button
After reboot, you will have to switch your phone off (it vibrate shortly, once it is finally powered off)
Then press Volume Down, Menu, Power and hold all three buttons till it powers itself up. You need to press theese buttons in precise order and hold, which means that first you will press volume down and during the time you are holding it pressed, press menu (now you are holding two buttons), and then press power, while still holding all three buttons. After phone powers itself up, you shall se yellow triangle on the screen. Now you are ready to continue with Odin (second section of my howto)
Virnik0 - I recommend more download links. The one you're using requires payment for a 'quicker' download and shorter waiting time, or it's 2 hours for free and slow speed.
I do have a list of file hosting sites, but http://www.filedropper.com/ is very good.
I'm also learning Czech the hard way
SamuraiHQ said:
Thank you
WOW! I don't speak Czech, but even I understand a 119 minute wait if I don't register (300kB/s), and a 17 minute wait if I do. I'm not sure about speed on this one aha. I think you should provide your login name and password
Click to expand...
Click to collapse
I dont have any login from uloz.to server. It is completely free, even for uploaders. And if you want to understand what is written there, you can use google translator.
Or, if you know some other server where I can upload it to, just let me know. I can even upload it to your server, if you have fast line enough.
Just wait till download is finished as a free guest access
Go take coffee, cigarette, girl or any other entertaiment you want, I think it is worth it.
PS: Uploading took me 3 minutes :-D I am sitting at 1Gb/s optic wire
I wasn't joking, when I wrote that I am admin
EDIT: OK, uploading to file dropper now. Will give new link to the first post once it is uploaded.
PHOENIX UNLEASHED JS8
Its not just a rom, its a Cauldron of Awesomeness!!
WINNING!!!
It's that time again, Team Phoenix has now brought you Phoenix version Ultimate JS7!! This is the same great Phoenix ROM everyone knows and loves plus so much more!
Screen Shots
{
"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"
}
DOWNLOAD PHOENIX ULTIMATE JS7!
MIRROR
What it includes:
1. JK4 Modem
2. Speed Mod version C w/ memory tweaks
3. Security patch
4. FUGU Tweaks
5. New default font
6. New email apk
7. Telenav GPS
8. My(Adam's GPS File combo)
9. Lagfix, tweaks and BLN install on first boot(easy to change if this is not to your liking.)
I am sure there is more!
Included Apps
1. Tibu
2. Telenav voice guided GPS
3. XDA app
4. Latest SGS tools
5. Faster Fix GPS
6. My modded dialer from Phoenix 6.0
7. Voodoo Sound
8. Updated, themed market
9. Market Finger print is now fixed(Thanks to Geohentix for bringing it to my attention).
MODEMS
Alternate Modems
More Modems Here
KERNELS
Firebird
Glitterballs
SuckerPunch Voodoo
SuckerPunch non-Voodoo
Di11Pickle
Very much appreciated but by no means required. Thank you!
Credits:
Team Phoenix
Di11igaf-always considered by me to be a silent part of Team Phoenix
JoeDV
ETheRealRemnant-Telenav finder
Comdei
blank to move to first post
Change log
Change log from 7.0 to Phoenix Ultimate!
*JK4 modem
*Clean call recording mod
*Pandora works
*Dialer includes MMS option instead of 2nd VM button
*Updated SGS Tools
*Phoenix themed Miui Music apk
*Volume link in settings
*Stay on while plugged in added to settings
*Video player added back in
I think there is more but I need sleep.
Change log from whatever the last release was to PHOENIX UNLEASHED!
Code:
Phoenix Unleashed:
Theme updated
Removed Telenav(source of battery drain)
put clock back in status bar but added toggles to remove whole clock or just am/pm
Updated to latest Captivate Tools(SGS tools)
FUGU Tweaks (great with JS8)
Speed Mod version D Kernel
Good 'ol JK4 modem
I know there is more but it is 2 am, give me a break!
FYI-Reverted to classic Phoenix Theme
So is this one
FAQ
Will be Updating soon
DO NOT FLASH WITH THE USB PLUGGED IN!! YOU WILL NOT HAVE SIGNAL WHEN THE PHONE BOOTS.
3.5 starts here
Recovery:
Hold vol down + vol up
Hold power button
I wait for att screen, (keep holding)then for screen to go off,(keep holding) then the second time the att screen comes up release power button.
Download mode/odin: LINK TO ODIN ONE CLICK STOCK
1.Start odin first
2.Plug in usb to computer
3.Hold down vol up + vol down(not power)
4.Plug usb into phone
5.When you see the android with shovel, your in download mode!
How to flash PHOENIX Roms.
Roms Should be Flashed will 100% battery
1. BACK UP!!!
2. Use Odin One click to Flash Stock
2a. Wait for it to reboot and then re-enable debugging, hook phone back up to pc and Master Clear
3. Load Clock Work update zip (attached at end of post) and new rom file to Phone memory
4. Remove sim and external SD, and unplug from USB
5. Boot into Recovery and reinstall packages (You may have to reinstall packages twice to get to clockwork recovery)
6. Once in Clock work recovery (Green Text) Select install zip from SDcard
7. Next Select Choose zip from sdcard
8. Scroll down to Phoenix ( Current version) and select.
9. If prompted on reboot to select an option choose with backup and restore. (for auto lagfix)
10. Let it finish and dont touch it till you see the launcher screen. Will this take awhile? YES
How To Disable Vodoo
1.Open A file Explorer ex. Root Explorer
2.Navigate to the Vodoo Folder
3.Inside the Vodoo Folder create a Folder Named disable-lagfix
4.Reboot
5.It will seem to hang on the boot screen Just leave it alone till it fully boots
Or Download attached zip file, unzip and move folder to vodoo folder and reboot and then sit back and wait. It will take awhile so just leave it be
Wipe Battery Stats1. Connect the phone to the charger with the phone powered on, and allow the phone to charge until it shows 100%
2. Disconnect the phone from the charger, and power it off.
3. Reconnect the phone to the charger with the phone powered off, and allow the phone to charge until the battery indicator shows 100% (you can use vol-up/vol-down to make the indicator come back up when the screen goes to sleep).
3a. Repeat step 1, 2, 3
4. Disconnect the phone from the charger and power it on.
5. Once the phone is powered completely on, power it off again and reconnect it to the charger until the battery indicator shows 100%.
6. Disconnect the phone, power it on, and use it.
7. Use ADB or a Terminal Emulator to run the following command:
Code:
su
rm /data/system/batterystats.bin
7a. Reboot into clock work Recovery, and choose advanced CWM features and select wipe battery stats
How to back up your APPS + data (not system data) with Titanium Backup
Go to the market and download and install Titanium Backup
Load up Titanium Backup and allow super user.
Go into Preferences and change Backup Folder name to external_sd/TitaniumBackup (this will save a copy of the files to your external SD card for restoring after flash) then click back and it will reload.
Now go to batch and select backup all user apps. Select the apps you want and hit run batch (top of the screen) once it is finished (you will know as there is a notification in the drop down that it is done) Double check you external sd for the Titanium Backup folder, if it is there then you are good, if not double check the spelling. Make sure it is an underscore between external and sd. ex. external-sd = Wrong..... external_sd = right so it should read external_sd/TitaniumBackup
Ok So you Fully Bricked your Captivate Here is a last ray of hope
Download mode/JIG: ITEMS YOU WILL NEED TO BUY:
-301k OHM Resistor, no more no less & -MicroUSB Board
-Upon receiving items, go here.
-Remove SIM and MicroSD Card
-Plug in JIG and voila, you are back in download mode
-load up odin and flash back to stock
Themes and Stuff
Disable Vodoo before flashing themes like blackfroyo with recovery.
Voltage Settings (If Kernal Supports OC/UV)
VoltageApp settings will stick until reboot, but to get them to stay after rebooting, this is what worked for me; You will need Root Explorer for this one
Setup Voltage App like you want
Menu>Apply for Now
Menu>Save as boot settings
Open Root Explorer
Navigate to /etc/init.d
Locate file saved for boot settings (S_volt_scheduler)
Rename "S_volt_scheduler" to "S_98_volt_scheduler"
Save
Reboot
Open VoltageApp to verify settings stuck
AT&T Wap Settings
ATT
wap.cingular
not set
not set
[email protected]
not set
not set
http://mmsc.cingular.com
wireless.cingular.com
80
310
410
not set
internet+mms
Power Cycle without pulling battery
Hold volume up and power for 10 sec. (This will reboot your phone without a battery pull)
Backing Up your NV_data
Thread With more info
The reason its important to back up your NV_data (Non-volitile) is this has your imei, product code, unlock codes and model. This informatioin is not recreated with a JF6 OCD (One click downloader)
Certain Roms write data to your NV_data
(i think it was JPC leak from I9000 that was the first one. it changed everyones product code to I897ZKAKOR)
Axura changes the product code to I959ZKATMB or something like that
The Correct Product code for our Captivate is I897ZKAATT.
If your IMEI says 004999010640000 begin_of_the_skype_highlighting 004999010640000 end_of_the_skype_highlighting begin_of_the_skype_highlighting 004999010640000 begin_of_the_skype_highlighting 004999010640000 end_of_the_skype_highlighting end_of_the_skype_highlighting this is incorrect also and you may find your phone to stop making calls as this is like a debugging or prototype imei
Finally, if your unlock code is FFFFFFFF, you need this repair in order to unlock your code
All of these can be fixed with Helroz's Repair_nv_data.zip Found Here: http://perso.numericable.fr/helroz/P...ir_nv_data.zip
I did not create the software or any of the instructions, THis is credited to Helroz in the vibrant forum (please thank and donate to him) he came up with all of this, Im just sharing knowlage.
this can be found here: Unlocking Tmo Vibrant
http://forum.xda-developers.com/show...&postcount=103
Just read the read me first. then the .Doc Make sure you are at Stock JH7 (I didnt try jf6) and root with busy Box (Super One click by CLShort Fuse worked for me)
Then Step 2,3 and 4. Monitor your phone for SU access attempts, it has several and be patient and read what its asking you to look for,
Now if you havent Backed up your NV_data then now is the time. I Use root explorer and just copy the /efs folder to a safe place (I have a copy on my ext. sd card and a backup hard drive)
You can also Use SGS tools (not SGS tool Box) to do a product code check. This also copies all of the pertenant NV_Data files to a folder on your internal SD card. you can use these also if you want.
Flashing JPP Modem to enable 850
The only guaranteed method for enabling 850 on jpp that is proven to work every time is to:
Flash stock using odin
Flash jg8 modem
Flash rom with jpp modem
Hopping around to other modems and back to jpp after this will kill 850 as well.
For some this is not an issue as they are in areas where 850 is not utilized by AT&T but for others jpp will cause headaches if they try using it without following these steps.
Themes and Graphics
Disable Vodoo before flashing themes like blackfroyo with recovery. (if Running vodoo)
How to change Boot Animation.
1.Find the animation that you want (most be compatible with captivate)
2.Copy bootanimation.zip (it must be named this) with a file explorer that gets you to system files ex. Root explorer to system/media
3.Reboot
Fonts
http://forum.xda-developers.com/showthread.php?t=801160
http://forum.xda-developers.com/showthread.php?t=748916
Phoenix Patches
All Patches and Fixes attached below
Phoenix 1.5= Email and phone APK. Copy to system/app , clear data in email app and reboot
Email FC after changing email Fix
Thanks to Newter55 for the find
Download the libcamera.so from here: http://dl.dropbox.com/u/11343737/libcamera.so
Use root explorer or whatever method you prefer and make a backup copy of /system/lib/libcamera.so just in case you need to get it back.
Copy the libcamera.so you downloaded from above link over the existing one in /system/lib.
Delete or rename the existing email.apk in /system/app to test that this fix works.
Reboot phone.
Open Barcode Scanner and enjoy the fact that it no longer force closes.
This will allow people to use whatever email.apk they prefer...or if they are like me they can get rid of the apk altogether.
Ok Guys I wipped out all the Flaming in the thread. I have reopened it after the rules were met.
Here's a quick and dirty conversion to boot animation of that "Operation Phoenix" video if anyone wants it.
Download bootanimation.zip
app
Jeepsdaddy said:
How do you change the GPS server settings and wipe GPS data?
Click to expand...
Click to collapse
Sgs tools app, secret codes, lbs test mode, change supl settings, delete gps data
Sent from my SGH-I897 using XDA App
Also if anyone has issues with charge death or random shutoffs while charging. http://forum.xda-developers.com/showthread.php?t=887315
That kernel works well with this ROM.
Hey Adam thanks for all your hard work. This is my wallpaper
this looks so good adam!
A big congrats to you and your team...
Awaiting a full battery for the flashing to begin!
Smaller versions of the Operation Phoenix boot animation. It still looks fine even in the 10fps version IMO.
Tinyier uglier animated GIF rendition:
Small 10fps Version Download
Medium 16fps Version Download
Large 30fps Version Download
BTW, I Can't find the post now, but thanks to whoever originally found this animation.
zelendel said:
I agree with the sound. I even have a fire wav file that I used back on one of the boot animations for an old WM rom if you want adam
Click to expand...
Click to collapse
Hey Zel, Where did you get that Avatar, it would be sweet if we could light that on fire! Android Phoenix!
adamholden85 said:
NO FLAMING ALLOWED!! That is my # 1 rule. Smoke has helped me out tremendously. Let the past be the past. What's done is done. Smoke is the man in my book.
Click to expand...
Click to collapse
Sorry mate, wasn't meant as a flame.
Was just trying to say that there really isn't a leagl ground to try and shut down Phoenix, and I believe I speak for everyone when I say we would rather see you be able to develop Phoenix and make it all it can be, without the threat of a gun to your head.
All aside, I am looking forwards to hear what great things come out in the coming weeks.
Also, make sure you take time off and enjoy New Years with your family!
Yes we may be part of your family, but you gotta look after the RL ones too.
zelendel said:
Good morning everyone. As far as last night goes, it was taken care of so moving forward I am so looking forward to a 2.2.1 base with Phoenix beauty.
Click to expand...
Click to collapse
Morning...after 3pm.. Sheeshh
Felklaw said:
Personally, I have the following:
-Auto brightness (but use Screen Filter for night time)
-I initially had this set, but have since set it back to never sleep. Not really noticing big difference, and where I work and live, both are Wi-Fi already set up in my phone. Plus when Wi-Fi is off, I found my phone syncing would then use 3G on AT&T's stupid ass limited rates....
-Bluetooth off when not using it
-GPS turned off when not using it
-Have not touched the sync frequency
I had terrible battery the first few times, one MAJOR thing to do is go into SGS Tools and ensure you Update Stock Apps --> 3D Gallery
That stock gallery is a known battery raper. After doing that, I had 24hrs uptime and had 63% battery left.
Means I can go 2 days with moderate to medium usage (calls, texts, web browsing, games and App Market)
Gotta be happy with that!
Click to expand...
Click to collapse
+1 on all the steps but I wasnt aware of the gallery issue. If I read it right, this has the one baked in you reference. I have never gotten battery life to that level but following these steps did help me as well. You must have one bada$$ battery! Good post.
Good news/bad news
Good news, we are not getting shut down. Master's case was not strong enough. Bad news, who am I kidding, there isn't any. We are still moving firmwares though to get up with the times.
adamholden85 said:
Good news, we are not getting shut down. Master's case was not strong enough. Bad news, who am I kidding, there isn't any. We are still moving firmwares though to get up with the times.
Click to expand...
Click to collapse
Awesome news
adamholden85 said:
Good news, we are not getting shut down. Master's case was not strong enough. Bad news, who am I kidding, there isn't any. We are still moving firmwares though to get up with the times.
Click to expand...
Click to collapse
Excellent news.
Means 1 less stress for you and the team.
how can i chage the battery icon it looks like a christmas bell
Here is a free template I found that kinda looks cool if someone who knows html wants to screw with :
Preview : http://www.phoenix-hq.com
html files and images : http://phoenix-hq.com/Colorus.zip
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.
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 #.
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.