Related
Is possible without installing modded firmwares? I mean, doing it by hand, avoiding flashing again? Stune or TkFileExplorer can do this?
Thanks - sorry for asking but i've searched a lot finding nothing
Yes you can but (with stune) you have to install the region code after and that made a reset of your phone.
Gremo said:
Is possible without installing modded firmwares? I mean, doing it by hand, avoiding flashing again? Stune or TkFileExplorer can do this?
Thanks - sorry for asking but i've searched a lot finding nothing
Click to expand...
Click to collapse
Unfortunately, it is not possible to activate socialhub premium without modifying first the firmware.
Especially, you need to modify the samsung socialhub web address (or simply replace the "clientstrings-en_US.lan" file) that is in ShpApp.app of the firmware.
This file cannot be edited by STune. It does not even show up in STune. The one that shows up in STune is the one from the FactoryFs file.
When you edit this file with STune, it is automatically overwritten by the original file from ShpApp.app. And you are back to square one.
So it is very necessary to edit the ShpApp.app and flash the firmware before socialhub will be active. You can edit the csc and other files with STune.
spacks said:
Unfortunately, it is not possible to activate socialhub premium without modifying first the firmware.
Especially, you need to modify the samsung socialhub web address (or simply replace the "clientstrings-en_US.lan" file) that is in ShpApp.app of the firmware.
This file cannot be edited by STune. It does not even show up in STune. The one that shows up in STune is the one from the FactoryFs file.
When you edit this file with STune, it is automatically overwritten by the original file from ShpApp.app. And you are back to square one.
So it is very necessary to edit the ShpApp.app and flash the firmware before socialhub will be active. You can edit the csc and other files with STune.
Click to expand...
Click to collapse
Thanks for explanation.
I need first to flash S8500XXJID and then S8500XIKA1 (target firmware). If i've understood correctly, i have to:
1) Download trix (any working link? ) and work with S8500XXJID
2) Edit CSC_S8500_Open_Europe_Common_OXA_XXJID.csc and edit Customer.xml
3) Open ShpApp.app and edit clientstrings-en_US.lan with the new address (will it change in future? )
4) Flash S8500XXJID (full)
5) Flash S8500XIKA1 (light)
Should i edit csc and app also for S8500XIKA1? Can I only modify S8500XIKA1?
ty
Gremo said:
Thanks for explanation.
I need first to flash S8500XXJID and then S8500XIKA1 (target firmware). If i've understood correctly, i have to:
1) Download trix (any working link? ) and work with S8500XXJID
2) Edit CSC_S8500_Open_Europe_Common_OXA_XXJID.csc and edit Customer.xml
3) Open ShpApp.app and edit clientstrings-en_US.lan with the new address (will it change in future? )
4) Flash S8500XXJID (full)
5) Flash S8500XIKA1 (light)
Should i edit csc and app also for S8500XIKA1? Can I only modify S8500XIKA1?
ty
Click to expand...
Click to collapse
Answers:
1. Download Trix from here: http://www.megaupload.com/?d=51WOVLLD
2. Edit only the CSC for S8500XIKA1.
(No need to edit the csc of S8500XXJID as it will be overwritten by the csc of S8500XIKA1).
3. It's easier to replace the clientstrings-en_US.lan with the one from http://www.multiupload.com/VYQX8PFOG9 (It is correct and needs no edit).
NB:
i. Replace the clientstrings-en_US.lan file in BOTH ShpApp.app and FactoryFs (S8500XXJID (full))
ii. Replace the clientstrings-en_US.lan file in ONLY PFS_S8500..pfs (S8500XIKA1 (light))
4. First flash S8500XXJID (full)
5. Lastly flash S8500XIKA1 (light)
Suggestion:
Browse this forum for more tutorials on how to activate socialhub premium (there are many of them).
spacks said:
Answers:
1. Download Trix from here: http://www.megaupload.com/?d=51WOVLLD
2. Edit only the CSC for S8500XIKA1.
(No need to edit the csc of S8500XXJID as it will be overwritten by the csc of S8500XIKA1).
3. It's easier to replace the clientstrings-en_US.lan with the one from bada 2.0
or the one from http://www.multiupload.com/VYQX8PFOG9 (These ones are correct and needs no edit).
NB:
i. Replace the clientstrings-en_US.lan file in BOTH ShpApp.app and FactoryFs (S8500XXJID (full))
ii. Replace the clientstrings-en_US.lan file in ONLY PFS_S8500..pfs (S8500XIKA1 (light))
4. First flash S8500XXJID (full)
5. Lastly flash S8500XIKA1 (light)
Suggestion:
Browse this forum for more tutorials on how to activate socialhub premium (there are many of them).
Click to expand...
Click to collapse
Oh really thanks man the only problem is there is no clientstrings-en_US.lan in ShpApp.app and FactoryFs_S8500_Open_Europe_Common.ffs from JID:...
The clientstrings-en_US.lan file is in App\Osp\Applications\2482tqy39g\Data
And it's possible to active socialhub premium with stune but it's easier to make it directly from a firmware.
that's so annoying I link TriX at NokiX site, then everyone link some copies of what they downloaded earlier - at the end people complain the program is buggy, the script is not working, the procedure entry point couldn't be located
download from NokiX site so you always have the current build with updated scripts if something has changed. Short how to is prepared too...
Hi kubica Have you got the link please?
Is there some new scripts for trixBada?
You will find all stuff at http://nokix.sourceforge.net/trix/
there is no currently new scripts - everything still work, even with new bada 2.0, so there is no need for do that
I'm getting the error "social hub has expired. Contact...", so what's wrong?
I edited a configuration file for Bluetooth(main.conf) in which i changed the device discoverable for value to be 0 (by default 120). then i left the folder as is (r/w) mode and saves and rebooted.
rescue mode is available(volume up - home -power)
boot loops continously
Kies not recognising when connecting when the device is turned off
there is a backup of the file at the same folder..
if you can provide me too ..how do i upload to my phone.
need help ASAP.
try installing firmware with odin
Other better ideas!
I am pretty sure that this matter was triggered because of that tweak..(editing of the file). I hope that restoring the original file would help.
Do you know about adb...?
Also i forgot where the actual bluetooth configurations file was in the root folder structure
adb will not work on device in recovery/download mode
to use adb mobile needs to be running
you can flash cwm in your mobile then upload the file and send me the link i will make a flashable zip and upload it then you can flash it
adb is running...just
Adb is running (while the phone keeps on showing boot animation-samsung logo-bootanimation-samsung logo-bootanima....) but it seems that it has permissions issues..i unrooted my phone before using adb .
i can access adb shell and list root directories but cannot enter further directories such as data\ permission denied
I donot have the file that i changed and quiet cannot remember it..
Check on your mobile and see for
data/misc/bluetoothd/
if it has files such as music.conf,main.conf etc etc..then this is the needed folder..
can you create a update.zip
like i used for rooting/ unrooting .that doesnt need CWM
that empties the directory ,because it has some backup files .bak created by root explorer
loads files from your mobile
i am currently unrooted ..do i need root?
actually adb works during splashscreen
get the original file and push it through the system, set permission and it should work
if all else fails,..... odin
download update.zip from http://dl.xda-developers.com/attach...5498d4d803e6a/4fcc0dd2/7/6/3/0/8/8/update.zip and place it in the root of your sdcard
go to recovery flash it you will get root then you can use adb
if it is not flashing first flash cwm through Odin then flash this update.zip through cwm
The file you sent is invalid. corrupt..?
what does this do..exactly.
i already have a update.zip and update-unroot.zip to root unroot my device
so
do i need root permission to use adb..because commands like
adb root gives"error not available in production devices"
&
adb shell
$ su
etc are showing permission denied.
if you have the original files on your galaxy y.. can you make update.zip with the above instruction
if adb works..i dont exactly remember the file path that i changed..so using the hints above please can you send me the file path
My aim here is to use odin or factory reset only at the last.
just root the device by flashing the root.zip in recovery and then use
adb shell
su
and it will work
No still get permission denied.... like always.
cd data
ls
open directory failed, Permission denied.
1. flash cwm recovery through odin
2. then upload the original file
3. I will create a update.zip and will upload it
4. you will need to flash it in cwm recovery
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
y2k2r2d2 said:
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
Click to expand...
Click to collapse
http://db.tt/2NStXBF8
flash it in recovery but it may not work as I don't have galaxy y I have a different mobile
it didnt allow installation both through cwm and recovery mode
& now
i messed up with CWM
backup-restore feature
create backup
edited the system.tar
put the original file
calculated md5 for new system,tar
edited the nandroid.md5 with appropriate editor and filled with the new calculated md5 of system.tar
advance restoore....select system files...
md5 check pass
restore fail
now boot stuck at initial screen
pretty sure even wipe data wont work
So i Had to resort to ODIN..Thanks for your time mate...
humm
I also think Odin is the last choice
this guide is just to get the ha and aaa keys!!!
ok first you have to root the samsung prevail...i believe this will also work for the replenish(search for root methods)
once rooted you will need to go to the app market on the phone and download android terminal emulator.... open the emulator app and run this command:
su
# dd if=/dev/stl5 of=/sdcard/cdma.rfs
then plug your phone to computer with usb, turn storage space and copy the cdma.rds file off sd to desktop and use the magic iso
to extract to desktop(http://www.magiciso.com/)
open magiciso:
select file..open ..change file types to AllFiles(*.*) and open the cdma.rf file you extracted and go to NVM folder then open the NUM folder and copy the 465, 465_1, 466, 466_1, 1192, 1194 files onto desktop or a folder ...these are the files needed.
now download winhex (http://download.cnet.com/WinHex/3000-2352_4-10057691.html)
open winhex and drag and drop each of the files into winhex(it will open them all in one window)
EDIT: you only need 466_1 and 1192 to get the AAA keys the pics i have attached show you the aaa key highlighted...1192 is for profile 0..... and 466_1 is for profile 1
the HA keys are the same for both (736563726574 )
i will update the rest tonight... (how to get the ha and aaa keys)
if this has been covered on xda let me know or just remove..thanks
Excelent, thats what i needed to know, ONLY 1192 and 466_1 are needed. Pictures are perfectly clear, the rest can be read with CDMA Workshop (paid version)
Cannot open files with winhex
I know this is an old thread but it is the only one I found that is close to my issue.
I followed these instructions to the letter but i get an error with winhex that says " Please check the path and your access rights" " The System cannot find the file specified".
Even tried as administrator.
I have been at this for days with no luck..
Any help would be appreciated.
Model:SPH-M820-BST
Android Version : 2.3.5
Baseband Version: S:M820.07
Kernel: 2.6.35.7
Build: Gingerbread.EJ06
Hardware: M820.07
Thanks
kybat
mejori said:
this guide is just to get the ha and aaa keys!!!
ok first you have to root the samsung prevail...i believe this will also work for the replenish(search for root methods)
once rooted you will need to go to the app market on the phone and download android terminal emulator.... open the emulator app and run this command:
su
# dd if=/dev/stl5 of=/sdcard/cdma.rfs
then plug your phone to computer with usb, turn storage space and copy the cdma.rds file off sd to desktop and use the magic iso
to extract to desktop
open magiciso:
select file..open ..change file types to AllFiles(*.*) and open the cdma.rf file you extracted and go to NVM folder then open the NUM folder and copy the 465, 465_1, 466, 466_1, 1192, 1194 files onto desktop or a folder ...these are the files needed.
now download winhex
open winhex and drag and drop each of the files into winhex(it will open them all in one window)
EDIT: you only need 466_1 and 1192 to get the AAA keys the pics i have attached show you the aaa key highlighted...1192 is for profile 0..... and 466_1 is for profile 1
the HA keys are the same for both (736563726574 )
i will update the rest tonight... (how to get the ha and aaa keys)
if this has been covered on xda let me know or just remove..thanks
Click to expand...
Click to collapse
kybatman said:
I know this is an old thread but it is the only one I found that is close to my issue.
I followed these instructions to the letter but i get an error with winhex that says " Please check the path and your access rights" " The System cannot find the file specified".
Even tried as administrator.
I have been at this for days with no luck..
Any help would be appreciated.
Model:SPH-M820-BST
Android Version : 2.3.5
Baseband Version: S:M820.07
Kernel: 2.6.35.7
Build: Gingerbread.EJ06
Hardware: M820.07
Thanks
kybat
Click to expand...
Click to collapse
dont know what that error is..you might try uninstalling and re-installing winhex ? sorry i have never gotten that error
here seems to be a fix ? try at your own risk...
http://www.techknow.me/forum/index.php?topic=1188.0
mejori said:
this guide is just to get the ha and aaa keys!!!
ok first you have to root the samsung prevail...i believe this will also work for the replenish(search for root methods)
once rooted you will need to go to the app market on the phone and download android terminal emulator.... open the emulator app and run this command:
su
# dd if=/dev/stl5 of=/sdcard/cdma.rfs
then plug your phone to computer with usb, turn storage space and copy the cdma.rds file off sd to desktop and use the magic iso
to extract to desktop
open magiciso:
select file..open ..change file types to AllFiles(*.*) and open the cdma.rf file you extracted and go to NVM folder then open the NUM folder and copy the 465, 465_1, 466, 466_1, 1192, 1194 files onto desktop or a folder ...these are the files needed.
now download winhex
open winhex and drag and drop each of the files into winhex(it will open them all in one window)
EDIT: you only need 466_1 and 1192 to get the AAA keys the pics i have attached show you the aaa key highlighted...1192 is for profile 0..... and 466_1 is for profile 1
the HA keys are the same for both (736563726574 )
i will update the rest tonight... (how to get the ha and aaa keys)
if this has been covered on xda let me know or just remove..thanks
Click to expand...
Click to collapse
Thank you for the info BUT aren't we suppose to get the NV item 466_1 over to the phone somehow? Every time I try to enter NV 466_1 it will not let me. Any help would be great, please PM or reply! THANKS!
For everyone else who can't get winhex to work, just download another tool like HxD.
I have this problem that has me stumped on whats going on. There is no CSC folder in my phone, no CSC info available when using the samsung phone info app, and when I try to use any USSD code in the dialer it says "Connection problem or invalid MMI code". I'm able to see my IMEI in the settings and app just fine and I've backed up and restored my EFS folder but nothing has changed. I have tried reflashing the CSC part of the firmware but nothing changes, no CSC folder appears or anything.
In the CSC info part of the samsung phone info app it reads as follows:
Product Code: SM-G925TZWATMB
Original CSC Code: TMB
Firmware CSC Code: blank
Active CSC Code: blank
Available CSC Codes: blank
CSC Country: blank
Mobile Operator: AT&T/310410
Phone info:
G925T (unlocked)
Kernel: Twisted v2 6.0.1
Recovery: TWRP
Rom: DPBG Stock (UK BTU 6.0.1)
Network: AT&T
Also, I made a nandroid backup prior to flashing the BTU rom and looked through it for the CSC folder but it wasn't there either. Really I could care less about the CSC, what bothers me and led me to this is that none of the USSD codes work on my phone.
Hi. Did you ever resolve this? I have the same problem. I just flashed the latest firmware onto my new S7, but only the AP file as per instructions. I did not included the CSC/HOME_CSC or other files.
[Edit: I fixed my problem by flashing the additional files. As I already had the AP file, I flashed the BL, CP and CSC (HOME_CSC_ASX). Everything works fine now]
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Cyteezy said:
can you please help me on step 13 because every time i reboot the device the by-name folder contents reset to the original value. my by-name folder backup is 72 mb while when i look in the folder after i reboot it is only 170 bytes
---------- Post added at 06:12 AM ---------- Previous post was at 06:07 AM ----------
also when i wait for a while after rebooting for like 4-6 hours when i looked at my baseband and imei it is not unknown anymore
and my sim is restored but when i reboot again the baseband value and imei is set back to unknown. this happened even before im not following your solution. can it be a hardware issue? would really appreciate any help thx
Click to expand...
Click to collapse
I didn't get you. Do not backup the whole by-name folder. Just copy the files mentioned above. And when you go into the custom ROM, just restore the files copied in the same by-name folder.
No. It might not be a hardware problem.
PraneethMv said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
Code:
adb devices
iii) now use the command
Code:
adb reboot-bootloader
In fastboot use this command to unlock bootloader
Code:
fastboot oem unlock
Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Code:
expdb
nvdata
nvram
proinfo
protect1
protect2
secro
8) Copy these files in some place where it is safe ( I have copied it to Internal Storage in a folder named PartitionsBackup)..
9) Next, go back to root folder again, and open data/nvram/md/NVRAM/NVD_IMEI and copy the MP0B_001 file to internal storage. Do Not copy this file in the same place as the previous files, but remember where you have copied this file.
These are all the partitions that store the device's IMEI .
10) After copying everything mentioned, Reboot to recovery and flash the desired Custom Rom.
11) Make sure the rom is rooted, and again install FX File Explorer from play store, enable root access as above.
Do Not Forget To Backup Everything Before Doing Anything!
12) Now select the files that you have copied in internal storage (Assuming PartitionsBackup). And copy those files. ( Note: Do Not Copy the MP0B_001 file!)
13) Now open root folder, go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder and paste all the files you have copied, and if asked select Merge/Overwrite files.
14) Reboot.
15) Now go back to internal storage, copy the MP0B_001 file where you have saved it. Go back to root folder and open data/nvram/md/NVRAM/NVD_IMEI and copy the file, select Merge/Overwrite. Now long press the file and select Security, update permissions as Read, Write for both root and radio. Dis-select everything else.
16) Reboot aand Done! Voila ! You should get back the IMEI for your device :victory:
I know its a long post, but it works for Custom ROMs.!
Hope it helps!
Hit Thanks If you feel it works! :highfive:
Click to expand...
Click to collapse
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
MisledMew said:
Hey Guys,
Yep, I know there are a whole lot of threads for imei problem fix, but I've seen a lot of threads with solutions only working either for stock rom, or there is some random imei showing up on your device. This is a thread on fixing imei problem working for custom ROMs. Yes! . I have tried this AOSP Extended and Resurrection Remix OS 5.8.3 both by mohancm and I'm pretty sure it will work on any custom ROM. This fix is based on partitions backup from your stock rom, so there will be no issues.
This solution was given by Senior Member @KaMyKaSii, so all thanks to him! Lets get started!
Requirements:
1) Your device ( Obviously )
2) Stock ROM Marshmallow.
3) Rooted Device
4) Maui Meta 3G/ SN Write Tool (Optional)
Procedure:
1) If you are on Custom Rom, flash marshmallow stock ROM (Search the forums, there a lot of threads), using SP Flash Tools.
2) After going to stock rom, next step is unlocking bootloader, there are many threads on doing this, but I'll sum it up here if you
want:
i) Go to Developer Settings>OEM Unlocking. Enable the option. Also enable USB Debugging Mode.
ii) Connect to a computer and open adb on it. Check if the device is connected using the command
iii) now use the command
In fastboot use this command to unlock bootloader Do as it says and reboot.
iv) Now again after rebooting go to bootloader and flash TWRP.
3) Root your device by flashing MagiskSU or SuperSU.
4) Now, download and install FX File Explorer from play store, Open it and enable Root Access from Settings>Add-Ons And
Themes in file explorer.
5) Now go back and open System (Root) folder in file explorer.
Note: If you haven't already restored, restore your imei, bluetooth address and serial number using Maui Meta or SN Write Tool.
6) In system root, grant Root permissions, and go to dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name folder.
7) In that folder, copy the files mentioned below:
Can anyone help me in restoring IMEI in stock ROM?
While flashing using SN writer or maui meta tool it says "Have been in meta mode. Long press power button to normal reboot". After that nothing. It boots back and I still see the INVALID IMEI message.
Click to expand...
Click to collapse
SN write tool can be a little complicated to do. I personally prefer Maui Meta 3G. You can search for guides on SN write tool. There are many....
Facing problem with maui meta 3g
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Ni$hant said:
On my mobile it shows its in "Have been in meta mode. Long press power button to normal reboot".
it won't work ahead .... some error like kernel checksum and no permission grant type.. rather i installed drivers of mediatek its not working...
plz help out
Click to expand...
Click to collapse
Do you have all drivers installed correctly? ADB, VCOM, USB Drivers?
Also, That message screen is Meta Mode. From that screen only you can do the IMEI process.
Note: This Only works for stock rom. Use this guide.
https://forum.hovatek.com/thread-12328.html
For custom Roms, use my guide.
Device: Lenovo A2016a40 (MY6735M) also known as Lenovo vibe b
Android Version - 6.0 Marshmallow
I can't find any folder named 'nvram' on 'data' directory of root folder