Related
Hi All
This is a tutorial for changing the phone product code and should work with Wave I/II/III
This tutorial works under 32-bit copy of Windows only
Steps:-
1.First of all download this file : http://www.mediafire.com/?yahd09ptzv3ubir
2.Extract the file with WinRAR & you will get 3 other files
a.QPST b.Revskills c.Samsung qualcomm driver
3.Grab your Wave and enter the code *#197328640#
Choose [8] Common >>>[7]Service Configuration>>>[2]DIAG Service Config.>>>[2]Usb DM/CP....Then exit this menu
4.Connect your Wave to the PC...If it asks for a Usb mode choose Usb Debugging
5.You will notice that your PC will detect a new hardware and will ask you for its driver>>>Use Samsung qualcomm driver
6.Install both QPST & Revskills
7.Use QPST to assign a COM Port for the phone
{
"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"
}
8.Now open Revskills and follow the Pics
to see current product code use Display NVItem and use 2757 as item no.
to change that code you need to write new one in Hex editior
Use write NVItem and use 2757 as item no. to write the new product code
proof of product code change
9.Grab your Wave and enter the code *#197328640#
Choose [8] Common >>>[7]Service Configuration>>>[2]DIAG Service Config.>>>[3]Usb UART/AP....Then exit this menu and restart the phone
Revskills part on youtube
If anyone got any question about this please ask
Best Regards
Thank u very much, will try tomorrow. maybe this will help to get my wave back in line with samsung kies. My product code was baaxen but with flashing to 2.0 it changed to baakor and kies would not let me update. hope this will help.
kolk11 said:
Thank u very much, will try tomorrow. maybe this will help to get my wave back in line with samsung kies. My product code was baaxen but with flashing to 2.0 it changed to baakor and kies would not let me update. hope this will help.
Click to expand...
Click to collapse
i hope it works for you
Is it possible to change the product code from GT-S8500BAAXTC to SHW-M210SBAASKT which is the same product with S8530 using this method even also vice versa? Because only Samsung Apps Korea is blocked to download an apps from global models such as S8500 and S8530. Not only from global to Korean model but also Korean model cannot download an apps from other countries.
Sent from my GT-I9100 using XDA App
If the phone's IMEI is not Korean maybe you will end up with a blocked phone that can't access Samsung Apps at all
I don't recommend doing this
This tutorial is for fixing product code if it was changed by accident and not tested for other purposes
Best Regards
I think Samsung Apps doesn't check the IMEI because there was a way to download an app from UK Samsung Apps by Korean model (SHW-M210S).
Actually, it was not that technical method, it just needed fast hands and good eyes
Of course, Sammy blocked it again last week.
Didnt work (yet)
So I tried to get back in line with kies and to turnback my productcode to XEN
SO far didnt work this is what i did:
I flashed back to an old full 1.0 bada firmware version and tried to change my productcode after that. I can connect to qpst and revskill but...
Revskill gives me when I fill in Item 2757; 26
When i click check commands i get: unknown response
Maybe i should flashback to bada 2.0 after that change productcode and then go back to my old updatable dutch firmware
or am i overlooking something
Edit: changed firmware to XXJID (bada 1.2) now I get error: failed in call to write file
Will reboot everything and try again
Did you use QPST to assign the COM Port number???
Assign that number then use it with revskills
If you phone COM Port is not listed in revskills
Make sure that your PC can find your phone as a Samsung HS-USB in the device manager
Don't write command number in revskills...it gets written after pressing let's go
Watch the youtube video for more understanding
Best Regards
mylove90 said:
Did you use QPST to assign the COM Port number???
Assign that number then use it with revskills
If you phone COM Port is not listed in revskills
Make sure that your PC can find your phone as a Samsung HS-USB in the device manager
Don't write command number in revskills...it gets written after pressing let's go
Watch the youtube video for more understanding
Best Regards
Click to expand...
Click to collapse
To bad still getting error failed in call to writefile (see my edit previous post)
Going to flash back to bada 2.0 change productcode and than flash to old updatable firmware
Update; Flashed some back and forward and reinstalled revskills. Now i can see my productcode which is BAAKOR and I want it to be BAAXEN.
So what do I have to change now and where u say: to change that code you need to write new one in Hex editior. What do I have to put in where in order to change my productcode
New code in hex editor
The tutorial tells me: to change that code you need to write new one in Hex editor
How do I know what values should be filled in there to change my productcode to BAAXEN
it is 47542D533835303042414158454E
Did you manage to connect your phone finally ?!
My mistake
Yes after reinstalling revskill I managed to connect.
this afternoon I will change to BAAXEN with the info you provided
Hope this will work (btw how do you know it should be the input u suggested?)
I used PC software called HXD hex editior
Made a new text document and write string data in it in the right side and as you can see in the picture it converted string data to hex value and that is it
Best Regards
mylove90 said:
I used PC software called HXD hex editior
Made a new text document and write string data in it in the right side and as you can see in the picture it converted string data to hex value and that is it
Best Regards
Click to expand...
Click to collapse
Okee but how do u know what string data to write to change productcode to baaxen? (trying to learn / understand)
kolk11 said:
Okee but how do u know what string data to write to change productcode to baaxen? (trying to learn / understand)
Click to expand...
Click to collapse
You don't need to memorise or know what code to write.
You can use this online hexadecimal editor.
Open the link, and paste the value you wish to convert to hex.
Example, to convert GT-S8500BAAXEN.
Just copy GT-S8500BAAXEN into the upper column of the page, and press Convert.
The value 47542d533835303042414158454e will display at the bottom column.
Any idea for S8600 Product Codes? Especially for :
I've tried GT-S8600HKATPL, but this seems wrong...
Code:
GT-S8600??????
S8600BOKJ1 (SW Version)
S8600TPLKJ1 (CSC Version)
Confirmed, because downloadable
Code:
[B]GT-S8600HKAXEF[/B] (France)
S8600XXKJC (SW Version)
S8600OXAKJB (CSC Version)
See KIES/FUS...
http://forum.xda-developers.com/showpost.php?p=19085697&postcount=19
Maybe now also S7250 and S5380 online?
Best Regards
Succesfull
I managed to connect to revskills (after reinstalling twice) and updated succesfully to BAAXEN and Yes kies told me there was an update available. So now Im back in line with kies with the latest official firmware. Now waiting for samsungs update to bada 2.0 cause the beta versions were promissing!
Thank u all for help and information!
Thanx mate, posted in badablog.ru
Hello,
I have a Wave 3 S8600 that when connected to Kies in registry has the product code set to XXXXXXXXXXXXXX . I tried changing the product code in the registry but kies 2 is ignoring this it seems.
Do you know how can I change this using PST? I tried the steps described in first post but my phone doesn't have Usb DM/CP. It has:
1. USB DM []
2. UART [*]
3. USB ACM []
Upon setting the Usb DM and after that connecting to PC it doesn't do anything, QPST is not seeing any new port. According to kies registry should be on Com 13
I am using a Windows 7 32 bit.
Thanks
S8600 is only Qualcomm CPU as I know...
Which Firmware you have...
*#1234#
Btw. You could make please Screenshots from Menu... it seems little bit different...
Maybe somewhere else also to change... to have access to Qualcomm Diagnostic port...
Best Regards
All right everyone here I will give u the method of writing IMEI & No Sim Detection problem of Karbonn A5/W619/Walton Primo & Karbonn A7/S01..
Many of the User of A5 are having problem with the IMEI & Mobile network lost and no sim is detecting while upgrading or downgrading Baseband.
As I have been searching for solution about a month and there is no specific solution regarding this problem..Through some ideas from different sites & developer and experimenting with my own device I have managed to write back both IMEI & enabled mobile network.
Note: For A7 user Please download AP of your device not this one.
Software & Other Requirement:
1.Stock AP of Karbonn A5/W619/Walton Primo (Original Stock GB Rom).
Link : http://jabadbd24.blogspot.com/2013/03/walton-primo-karbon-a5-downgrade-to-gb.html
2.Baseband- V3025 & V3070 both.
3.Fastboot 1.0.2.4 (for downloading AP+BP to device).
4.Drivers.
5.QPST Modem Tool V1.1 (for writing IMEI).
Link : http://www.mediafire.com/download/c9nv2zc1a233s13/Qualcomm_Modem_Tools%20V1.1.rar
6.QPST 2.7 (for restoring network).
Link : http://www.mediafire.com/download/kna2s9x3z06gcuu/QPST_2.7_378.zip
*********************************** FB ID= facebook.com/dj.rifat*****************************************************
Procedure:
A. (BP+AP) Download:
1.If u have upgraded your device to ICS then u have to Downgrade to GingerBread. First goto recovery mode(CWM/TWRP).Goto mount and select all and wipe data,system,boot,cache,android secure,SD-ext.Then Power off the device.
2.Then Update BP.First with V3025 (591347_8376_WCDMA_V3025) & then with V3070 (591347_8376_WCDMA_V3070).
[note: before updating V3070 baseband,Copy and replace 'appsboot.mbn' & 'appsboothd.mbn' this two files from the AP folder to V3070 folder in ur PC.]
{
"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"
}
3.Then update Gingerbread AP in Fastboot mode (green screen on device).
4.Turn on mobile while it is connected with the PC.PC will detect new hardware.One from them u installed before while BP Download..
5.Goto Device Manager of PC.U will find three new hardware.Install driver for them.As Shown below:
B. Write IMEI
1)Unzip “Qualcomm_Modem_Tools_V1.1.rar”, open Qualcomm_Modem_Tools.exe, (Turn on ADB Debugging from Application>Development>ADB Debugging from ur mobile)
interface as blew:
(2) Select port. Port should be same as modem port.
(3) Write IMEI. Input new IMEI, click “write”.
(4) Complete writing IMEI.
(5) Then click read, confirm the new IMEI is successful written
C.Fixing NO sim problem and Network.
Now Install ''QPST 2.7.398.exe'' on PC.
(1) Open “QPST Software Download”(Start>Programs>QPST Software Download) and click Restore, interface as below:
(2) Power on handset, connect usb cable and select port by pressing browse as shown below.
(3) Now press the 2nd browse button and navigate to the folder of V3070 Baseband folder ( '591347_8376_WCDMA_V3070' this folder) and select ''591347_8376_WCDMA_V3070.qcn'' file. Now press START ,if you have done everything correctly it will go good.
(4)Restart your mobile.Now goto to Backup Tab and type a name in QCN file column according to ur choice for better understanding which qcn file is the working backup and select location where you wanna save it and press start.This qcn file is important because if u lost ur IMEI sometimes during upgrade or downgrade restoring this file will
recover ur IMEI & network.
This way I have solved my problem.I apologize As I am not a expert in this field if any mistake done by me.
If you don't understand any steps or having problem please let me know will try my best to help you.
You can also find me in facebook/dj.rifat if need help.
Thanks.
Hit like If I have helped you.
Gr8 work bro.. i appritiate your work..!
Rifat.ahmed08 said:
All right everyone here I will give u the method of writing IMEI & No Sim Detection problem of Karbonn A5/W619/Walton Primo & Karbonn A7/S01..
Many of the User of A5 are having problem with the IMEI & Mobile network lost and no sim is detecting while upgrading or downgrading Baseband.
As I have been searching for solution about a month and there is no specific solution regarding this problem..Through some ideas from different sites & developer and experimenting with my own device I have managed to write back both IMEI & enabled mobile network.
Note: For A7 user Please download AP of your device not this one.
Software & Other Requirement:
1.Stock AP of Karbonn A5/W619/Walton Primo (Original Stock GB Rom).
Link : http://jabadbd24.blogspot.com/2013/03/walton-primo-karbon-a5-downgrade-to-gb.html
2.Baseband- V3025 & V3070 both.
3.Fastboot 1.0.2.4 (for downloading AP+BP to device).
4.Drivers.
5.QPST Modem Tool V1.1 (for writing IMEI).
Link : http://www.mediafire.com/download/c9nv2zc1a233s13/Qualcomm_Modem_Tools%20V1.1.rar
6.QPST 2.7 (for restoring network).
Link : http://www.mediafire.com/download/kna2s9x3z06gcuu/QPST_2.7_378.zip
*********************************** FB ID= facebook.com/dj.rifat*****************************************************
Procedure:
A. (BP+AP) Download:
1.If u have upgraded your device to ICS then u have to Downgrade to GingerBread. First goto recovery mode(CWM/TWRP).Goto mount and select all and wipe data,system,boot,cache,android secure,SD-ext.Then Power off the device.
2.Then Update BP.First with V3025 (591347_8376_WCDMA_V3025) & then with V3070 (591347_8376_WCDMA_V3070).
[note: before updating V3070 baseband,Copy and replace 'appsboot.mbn' & 'appsboothd.mbn' this two files from the AP folder to V3070 folder in ur PC.]
3.Then update Gingerbread AP in Fastboot mode (green screen on device).
4.Turn on mobile while it is connected with the PC.PC will detect new hardware.One from them u installed before while BP Download..
5.Goto Device Manager of PC.U will find three new hardware.Install driver for them.As Shown below:
B. Write IMEI
1)Unzip “Qualcomm_Modem_Tools_V1.1.rar”, open Qualcomm_Modem_Tools.exe, (Turn on ADB Debugging from Application>Development>ADB Debugging from ur mobile)
interface as blew:
(2) Select port. Port should be same as modem port.
(3) Write IMEI. Input new IMEI, click “write”.
(4) Complete writing IMEI.
(5) Then click read, confirm the new IMEI is successful written
C.Fixing NO sim problem and Network.
Now Install ''QPST 2.7.398.exe'' on PC.
(1) Open “QPST Software Download”(Start>Programs>QPST Software Download) and click Restore, interface as below:
(2) Power on handset, connect usb cable and select port by pressing browse as shown below.
(3) Now press the 2nd browse button and navigate to the folder of V3070 Baseband folder ( '591347_8376_WCDMA_V3070' this folder) and select ''591347_8376_WCDMA_V3070.qcn'' file. Now press START ,if you have done everything correctly it will go good.
(4)Restart your mobile.Now goto to Backup Tab and type a name in QCN file column according to ur choice for better understanding which qcn file is the working backup and select location where you wanna save it and press start.This qcn file is important because if u lost ur IMEI sometimes during upgrade or downgrade restoring this file will
recover ur IMEI & network.
This way I have solved my problem.I apologize As I am not a expert in this field if any mistake done by me.
If you don't understand any steps or having problem please let me know will try my best to help you.
You can also find me in facebook/dj.rifat if need help.
Thanks.
Hit like If I have helped you.
Click to expand...
Click to collapse
Thank you very much. can u please tell about karbonn a7 plus stock AP where to find. i m having this mobile and facing the same problem.
Thank you so much!!!
I made an account just to say thank for this GUIDE. I was looking and waiting for a year for this GUIDE. THANK YOU SO MUCH!!!:good:
#Respect
Just register an account to post reply. Great work bro, help me pick my phone up from hell :laugh::good::good::good:
vktisnow said:
Thank you very much. can u please tell about karbonn a7 plus stock AP where to find. i m having this mobile and facing the same problem.
Click to expand...
Click to collapse
got my problem solved. thanks a lot for this awesome guide
Anybody can give proper link for the Files.. Most of them are DEAD !!!
i found Port number (COM6).. after this i am unable to write IMEI number(getting error Write IMEI fail). i have entered my old imei number.
when i dial *#06# in my mobile displaying as below:
IMEI1:
IMEI2:
both blanks...(So i entered old IMEI numbers).
And from where can i get new IMEI numbers?
can you please help me on this.
Does this work for SM-A520FDS?
Hi
I have the "GT-I9195XXUBML1 deodexed" rom. In my previous device (n7000) I has the Netmonitor app and I could change the band by "Field Test" > "Debug Screen" menu.
On S4 mini i haven't the "Field Test" Menu (Debug Screen) and the code *#*#4636#*#* is not working..
How I can open the Debug Screen in i9195? Did I must paste any app to /system/app/ ? Or What?
EFS (IMEI) Backup tool N910U/F/L/K/C/P/T/G/H/R/6W/8W N915G(note4 Edge)(support to other variant soon)
{
"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"
}
This is simple EFS backup tool. We are very well knowing about what EFS is and why it is MUST to backup on every rooted device. If you don't know then Read this.
Right now this tool support only SM-910U and support to other variant will be added when it is available.
Download :
Pro Version
XDA version (free)- Attached at end of this post.
Difference between Free/Play store
-Both version makes backup in same format and no difference in backup.
-Free version will save file in MyEFS and if you make next backup it will replace older one. While play store version everytime creates new folder with date ,Time and your IMEI stamp so you can keep multiple backup as well no confulsion about which backup is made when and on which device. Also it makes copy of build.prop so you can get idea you were on which ROM when backup created)
-On free version you have to select option according your device model, if you select wrong your EFS backup will be wrong On play store version it will auto detect your model and make backup accordingly. In case your model not supported it will give warning msg.
-Play store version give notification in case backup not created OR you select wrong model and will have option to contact developer in such case.
-Weekly Auto backup feature available on play store version.
This tool using generic name of partition block and you can restore with simple adb shell
dd if=/path of backup files/ of=/partition block according your device
ChangeLog
1.0 - Initial release for N910U
1.1 - Updated for making backup of other efs related partition as well added support for N910F (all 1.0 user request to make new backup with new version)
1.2 - Added support for N910K
1.3 - Added support for N910C
1.4 - Added support for N910P
1.5 - Added support for N910T and N910G
1.6 - Added support for N910H/R/W8/6W
1.7 - Added support for N910L
1.8 - (Major Update - Recommended for all to update)
-Added support for N9100
-Backup location changed to IntSD/MyEFS for ready to use Pro version (now both have same location)
-Now it removes old backup before creating new backup to insure that created backup is new. still you can check date of created files)
1.9 - Added support for N915G (Note4 Edge)
2.0 - Added support for system less root. New UI.
XDA:DevDB Information
Dr.Ketan IMEI Tool, ROM for the Samsung Galaxy Note 4
Contributors
dr.ketan
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-11-19
Last Updated 2017-04-05
EFS Info
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others. In latest samsung device this information store in other partition so requires to make backup of that partition too.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM on newer ROM it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Exit "Permanent Safe Mode" This condition represent with loss of IMEI + yellow text box on homescreen with device info.here is Screenshot
Here is different method to remove it.
Method1 :
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Code:
OFF
To:
Code:
ON
Reboot device.
Method2:
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Method3
Install attached safemode_exit apk as regular app. Open from drawer - Grant su permission - Reboot when asked.
e:failed to mount /efs(invalid argument) error with bootloop
This condition usually happens with using unsupported tool (usually from play store).
To recover this, needs to use adb shell
Code:
adb shell
mke2fs / dev/block/mmcblk0p[COLOR="Red"]x[/COLOR]
mount-w-t ext4 / dev/block/mmcblk0p[COLOR="red"]x[/COLOR] / efs
x means your device EFS partition number
PS : It needs CWM and busybox installed.
Other model user have rooted device contact me to add support for their device.
no work for 910k
Thanks dr ketan.
Sent from my SM-N910U using Tapatalk
What is with N910F ?
19stephan77 said:
What is with N910F ?
Click to expand...
Click to collapse
Do you have N910F with root access?
Sent from my SM-N900 using xda premium
dr.ketan said:
Do you have N910F with root access?
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Dr, for SM-910F if i could help..
friedrich420 said:
Dr, for SM-910F
Click to expand...
Click to collapse
Can you make some space on Inbox so i can send msg?
Thank you.
dr.ketan said:
Can you make some space on Inbox so i can send msg?
Thank you.
Click to expand...
Click to collapse
yep.. i keep forgetting..
i have n910K with root
Thanks doc!
This basic thing and most important thing! :thumbup:
With this, This tool will help people.
..hope it will decrease the number of people reporting: I lost my imei or I lost network connectivity after so and so...how can I.... ?
Sent from my Note ? using xda premium
Hopefully people will read this.
[quote name="dr.ketan" post=56004124]Do you have N910F with root access? <br />
<br />
<br />
Sent from my SM-N900 using xda premium[/QUOTE]<br />
<br />
Dr, for SM-910F if i could help..<br/>
Yes I have N910F rootet. Does it work?
910F is ready. Will update soon
Sent from my SM-N900 using xda premium
Great. Thank you. Upload today?
19stephan77 said:
Great. Thank you. Upload today?
Click to expand...
Click to collapse
I am waiting report for one more model. I will update tomorrow
Looking forward to this on my 910T
dr.ketan said:
I am waiting report for one more model. I will update tomorrow
Click to expand...
Click to collapse
Any possibilties with N910G? I just rooted it, if I'm can be of any help...
Tool updated
ChangeLog
1.1 - Updated for making backup of other efs related partition as well added support for N910F
All 1.0 user request to make new backup with new version
Play store version may take 3-4 hrs to appear new update
.
INFO
I sold my P10 Lite, based on Huawei's decision to no longer provide bootloader unlock codes.
For a generic version of this project (ADB-Overlay) have a look at this thread.
The latest build of this project is still available.
---
Hello together,
here is a toolkit for the P10 Lite, it's designed to work primary with root (THE MOST TIME) so be careful what u are doing, specially if u are using the "Explorer". (Deleting the wrong file/folder on root lvl, could bring u in bad trouble!)
-
To all who used already my P9 Lite toolkit, there is currently not all available which u know from the old version, but i'll extend this toolkit in the next days. So, no worries about missing functions, they'll appear in some of the next builds.
-
About the usage,
- For a basic UI-Help just press F1
- If ur device is not detected u can switch off the "Device check" on the "Disclaimer" view (If u own a P10 which is not detected pls share a screenshot of the "adb devices -l" (l = lowercase L) command)
- U can also switch the (su -c) usage off (in the explorer view), BUT! after u performed any action which requires root, the trigger will be automatically switched on. (There is no other option, because my dll know only, use root or don't do so... There is no use root part-wise)
But anyways, i'm NOT responsible for any damage to your device!
Little preview of what u get
{
"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"
}
Tested Devices
Huawei P10 Lite [WAS-LX1A] [SINGLE-SIM]
Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4
(Installed ADB/Fastboot driver)
Download
Mirror: See attachments
Mirror #1: GoogleDrive
XDA:DevDB Information
WAS-Lxx [EU] Toolkit, Tool/Utility for the Huawei P10 Lite
Contributors
k1ll3r8e
Version Information
Status: Stable
Current Stable Version: 0.0.0.5
Stable Release Date: 2018-08-01
Created 2018-03-30
Last Updated 2018-08-15
How-To
[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging (see the screenshot)
(Only in adb mode my toolkit can detect ur device)
3. Make sure that u granted adb access on ur device
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.
U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:WAS-Lxx model:WAS-Lxx device:XXXXXXX
If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.
[Q:02] What does the Lxx Cxxx Bxxx mean?
The Lxx is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.
Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL
More comming soon...
Big THX for some of those "identifier" goes to:
@lost3
@baduncle
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
[Q:04] How can i manually boot into a specific mode?
Bootloader:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]
[adb] = adb reboot bootloader
[fastboot] = fastboot reboot bootloader
E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[adb] = N/A
[fastboot] = N/A
Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[adb] = adb reboot recovery
[fastboot] = N/A
Normal Boot:
[device] = Power button / Power button menu
[adb] = adb reboot
[fastboot] = fastboot reboot
Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[adb] = N/A
[fastboot] = N/A
[Q:05] Does the Dual-Sim upgrade survive an OTA?
Yes, the Dual-Sim modification will stay until u flash another oeminfo.
[Q:06] I upgraded to Dual-SIM and there is only one IMEI shown?
That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim or as shown the "0000000000000000".
Changelog
2018-08-01 - 0.0.0.5
* Added a Remote-Desktop
* Added a "partition selector" (recovery [Nougat], recovery_ramdisk [Oreo])
* Added a rooting option for Oreo
* Fixed a few bugs
* Realigned a few container
2018-04-21 - 0.0.0.4
* Added on the Device-Info view the BusyBox check
* Added the Phone control
* Added the Root menu (just waiting for permissions to include a zip)
* Added some features to the Explorer "View" menu (e.g. Sync with Treeview, Layout, Sort)
* Added a Display-Trigger to the "Power-Button" menu
2018-04-10 - 0.0.0.3
* Fixed a crash which appeared during device connection on the Explorer view
* Switched the whole window stuff to my new GlassWindow
* Added a AlphaChannelSlider (left beside the [--] button) for those which don't like transparent windows
* Added a Device-Info view
2018-04-01 - 0.0.0.2
* Fixed the icon bug (Big Icons, List)
* Re-positioned the "View" menu and made 2 of them, one for each view
* Refactored the "Button" layout, that they match now with the rest of the dark theme
* Added a fallback color "#2C2C2C" for those who got maybe the error message that the Glass-Effect couldn't be applied
* Added the "Shell-Tools" menu
* Added the 1st tweak (Pro-Mode)
Bug-Tracker
*FIXED in 0.0.0.2
- Noticed already the missing icons in the "Explorer" (Big Icons + List)
(Bug is already solved and will be fixed in the next version)
Known-Issues
- The "Explorer" "Big Icons" looking a bit ugly, that's because the p/invokes won't give me the "Extra Large" icons... I still work on it, so maybe it's fixed in the next version.
--
Drag 'n' Drop on any Explorer view, from outside the Application won't work until u run everything as Admin... That's a Windows UAC restriction and based on the fact, that we need the right's to create/delete/modify files/folders under Win8++ on the system HDD. (Like ADB pull for export of the oeminfo and custom.bin)
Missing Tweaks from the P9 Lite Toolkit
- As the screenshot shows, i managed to activate the "Double-Tap" menu, but that's all... The Double-Tap it self doesn't work... So there will be no "tweak" for this. - (Additional Info: The Double-Tap works^^ But ONLY on the lock-screen... And ONLY to turn the screen off... What a joke...)
- USB-OTG, is not available because, so far i know, u need a special kernel for it. (Which i can't provide, atm)
- AppTwin, because it should be enabled on any P10 Lite by default
Little - Update (1+2+3+4)
- I added a screenshot of the upcoming release, with integrated "Phone" control. (Currently only Call/Dial works)
- Added another screeny, now (Call/Dial/Add) is possible. Add, needs still interaction on the device side, like which "provider" (Device, Google, etc.) u want to choose. Dial, will insert the number in the default dialer, or it gets captured by any USSD protection. Call, will immediately start a call to the provided number.
- Just tested to send USSD-Codes like "*#06#", but it seems that u really have to type them... Even sending "*#06" and manually type the "#" doesn't work... U have to delete and re-type the whole USSD-Code...
- Added the final look of the "Phone". (At least, Add, Call, Dial, Hang-Up) is now possible.
For those which also use XAML, here are the control-button-geometries i created:
Menu-Button
Code:
<Path Fill="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="2,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,14" RadiusX="1.5" RadiusY="1.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Call-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,9 8,13 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Hang-Up-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,13 13,5 M 5,5 13,13" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Dial-Button
Code:
<Path Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="9,9" RadiusX="8.5" RadiusY="8.5"/>
<EllipseGeometry Center="6,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,14" RadiusX="0.5" RadiusY="0.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Delete-Button
Code:
<Path Data="M 0,7.7 5,2 16,3 16,12 5,13 Z M 8,5 13,10 M 8,10 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
WAS-LX1AC432B204dual
oeminfo
WAS-LX1AC432B206dual
oeminfo
I tested it on my WAS-LX1 C10 DS/ It works.
Perfect
Thank you !
rom issue
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Use only stock ROMs for now, cuz there's no daily driver Customs for P10 Lite yet. Stock Oreo is really good. You can use HwOTA to flash stock ROMs.
nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
k1ll3r8e said:
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
Click to expand...
Click to collapse
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---------- Post added at 12:18 PM ---------- Previous post was at 11:59 AM ----------
k1ll3r8e said:
If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent.
Click to expand...
Click to collapse
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
nsx82 said:
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
Click to expand...
Click to collapse
Heyho,
np
-
Yes, the "Lx1" are always the SS and the "L[1-9]1" are the DS variants. - Btw. u can't see the "real ID" under "Settings -> Info" to see the "real ID" u have to look in the "current" oeminfo.
-
I wrote a tool for this kind of tweaking/exploring, have a look at it, u can get it here
EDIT:
About the issue with the display/animations, it could also be a problem with the HW... I have seen a few forum posts about "factory delivered" broken chips etc.... Maybe there is something else wrong, if it was really from the 1st day u got it.
Regards,
Sebastian
Little Update
Heyho together
-
Here is a little preview of the upcoming update.
* Added a Remote-Desktop (touch, swipe and keyboard are working so far)
* Improved the speed
* Fixed a few minor bugs
Release should be in 2-3 days
Version 0.0.0.5 is online!
Regards,
Sebastian
k1ll3r8e said:
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
Click to expand...
Click to collapse
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
callmeWhiskers said:
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
Click to expand...
Click to collapse
Heyho,
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Regards,
Sebastian
k1ll3r8e said:
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Click to expand...
Click to collapse
Thank you very much for clarifying and shedding some light on this, Sebastian!
From what I've read, reconstructing (files) from checksums doesn't (really/easily) work - though in theory (if enough additional parameters are given, and IMEI/IMSI are kind of short strings) it could be reverse engineered - unless I interpreted my research findings wrong :victory:
I assume it's safe though
Liebe Grüße nach Delmenhorst!
Hi world(first post since android(previous windows mobile member of xda)),
I have P10 lite for almost a year(not rooted for warranty issues).
I wanted to perform a stock firmware backup before I endulge in rooting/custom ROM.
Is that possible with TWRP(with or without rooting), and are there any how-to's?
Sorry for being such a newbie, just like to upgrade to 8.0 and revert back to stock in case of a problem or warranty issues.
Thank you.
Recovery