Related
Download the normal unlock files before you do anything!!! You can find them in the forum.
KIES needs to be off...
1 - You need your phoned to be rooted
2 - Put your phone in usb debug mode
3 - Plug in the usb cable (don't use kies or storage mode)
4 - In the run window type CMD
5 - Go to the folder where you extracted the unlock files. Example c:\Generate Unlock Windows\Generate Unlock Windows
Type dir , you should see a file called adb.exe
6 - Type adb kill-server
Type adb shell
Type su (on your phone you should see the root explorer asking if you want to allow access, choose yes xD duh)
Type cp /efs/nv_data.bak /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak /sdcard
Type cp /efs/nv_data.bak.md5 /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak.md5 /sdcard
7 - Closed the window.
8 - The file with the code is now on your sdcard, start storage mode and copy the files to the c:\Generate Unlock Windows\Generate Unlock Windows folder (in windows xD)
Be sure that the nv_data.bak and nv_data.bak.md5 are in the same folder as sgux.exe
9 - Edit the Generate_Code.bat
Delete all the code and paste this:
@echo off
cls
echo ===============================================================
echo ===============================================================
echo Generate unlock code for any Samsung Galaxy S
echo ===============================================================
echo ===============================================================
echo Extract code
.\sgux .\.nv_data.bak
.\sgux .\nv_data.bak
echo ===============================================================
echo ===============================================================
echo Please donate to DagentooBoy for the script
echo Please donate to rbnet.it and marcopon for the SGUX utility used in the script
echo ===============================================================
echo ===============================================================
echo Script complete!
pause
10 - Your codes should appear! Save them and send them to you gmail account so you have them for life!
I TAKE NO CREDIT FOR THIS!!!! Just want to help!
Can you please Help me?
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
I've tried to get the code with : .nv_data.bak, nv_data.bin, nv_jpc and bml3.bak. In each case, I got the code 00000000.
I found this in a forum hope this will help
quiron said:
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
Click to expand...
Click to collapse
same result here, followed the procedure, ended up with network code 00000000. any help?
If you need help on unlocking a 2.2 device. Please contact me.
can anybody post a link to which normal unlock files are needed, there are too many unlock files in the forum
rhcp0112345 said:
If you need help on unlocking a 2.2 device. Please contact me.
Click to expand...
Click to collapse
Yes I need it, and I am certainly not the only one.
Can you publish a guide how to proceed ?
I did manage to get rid of this bloody unlocking problem after 9 hours of struggle. I followed the advice here:
http://forum.xda-developers.com/showthread.php?p=7946031#post7946031
I don't know how it worked, I don't care how it worked, its just that now i have a full working sgs with jp3 froyo software installed.
Next rom will definitely be official froyo, no more flic-flacs for me till then.
Fallback after a KOR productcode modification by firmware JPC
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!
It also means that a simlocked phone can be used with another SIM by modifying the same way the nv_data.bin...
Anyway I wont update this phone to JPC. I'll await the next one... JPD seems to be online but no infos yet on the status of this firmware.
in which line did you find the KOR?
i cant find it? >_<
Greg82uk said:
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!
Click to expand...
Click to collapse
I'm clueless here, would you mind posting a step by step including the software used?
gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
Looks promising!
Does it have to be JM6 or can JM7 work as well ?
Can anyone with JPC and a locked phone try this and report if it works ?
If we go back to JM6 do the editing and fix the product code then back it up on the PC, update to JPC and push this back to the phone this should work right ?
Any news if its possible to restore the IMEI ?
Ok I'm stupid and I can't make a md5 file of 32 bytes with md5summer for windows, somebody can help me?
edit de file with notepad and delete the 1st 3 lines and the count 32 bytes and delete all the rest.
I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .
quiron said:
I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .
Click to expand...
Click to collapse
It means your phone is configured as TMN (dont know which country it is) but if it asks you for unlock code => your SIM is not TMN.
Change TMN to whatever your SIM is... Check in regedit for a history. Anyway downgrade to a previous firmware because JPC is suspected of breaking the nv_data.bin
I don't know if this trick works with another firmware, but theorically it should works the same way...
Nb: do not delete any line in your nv_data.bin ! This is a stupid remark, it can brick your phone.
the solution to 00000000 unlock code
finaly the solution to 00000000 unlock code
http://forum.xda-developers.com/showpost.php?p=7957950&postcount=10
or
http://forum.xda-developers.com/showthread.php?p=7957950&posted=1#post7957950
works to me.
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
stefano_te said:
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
Click to expand...
Click to collapse
I think it's enough that you throw it into the SystemUI.apk(have a look inside that apk, if it's not there then it is in secframework.apk) (/res/.../XHDPI). Open the apk in winrar (you might have to rename it from .apk to .zip) and drag and drop the new files. Decompiling isn't necessary for this sort of thing.
Also, check this out:
http://forum.xda-developers.com/showthread.php?t=1918500
I did this a long time ago so some of what I just said might be wrong, if you need more help then just say so.
I would like to use as a basis the stock rom 4.1.2 : N7000XXLT9_N7000ITVLT3_ITV.zip
I used the kitchen to create workfolder following all the steps suggested by the program , I found the following problems:
1 ) during the procedure appeared to me the following warning :
Warning : A valid boot.img is not found . You have the option to add a
' fake ' boot.img So THAT the features of the kitchen can still
function normally.
This boot.img will be automatically removed from your ROM 's
ZIP file When Is It built .
Add boot.img (y / n)? (default: y) "
is this normal? how to solve ?
2 ) Working folder information ( v)
Android OS version: 4.1.2
Device: GT- N7000
Model: GT- N7000
ROM Name : JZO54K.N7000XXLT9
CSC version: It 's normal that there is nothing written here ?
Rooted ( Superuser app + su) : NO
Rooted ( unsecured boot.img ) : UNKNOWN how I fix this ?
BusyBox installed : NO
BusyBox run-parts support: UNKNOWN UNKNOWN how I fix this ?
Apps2SD (Apps to EXT) enabled: NO
/ data / app enabled: NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support: NO
/ system / framework is deodexed : NO
/ system / app is deodexed : NO
modem.bin found: YES
ROM will wipe all data : NO
3) throughout the META-INF folder there are only 2 files: update-script; update-script.bak
4) scripts / get_api_level: line 18: more: command not found
5) I checked the update-script and there are 3 warning in the report:
7/101: copy_dir PACKAGEystem SYSTEM:
8/101: format PRELOAD:
>> WARNING: Partition not recognized
9/101: copy_dir PACKAGEreload PRELOAD:
>> WARNING: PRELOAD: not found in working folder
10/101: symlink dumpstate SYSTEM:bin/dumpcrash
11/101: symlink toolbox SYSTEM:bin/cat
82/101: set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
83/101: run_program PACKAGE:create_preload_symlinks
>> WARNING: create_preload_symlinks not found in working folder
84/101: set_perm 0 3003 06755 SYSTEM:bin/ip
How do I resolve this? I tried a lot of on-line but have not found anything. My goal is to make me a custom rom from the last stock (LT9) ... what should I do?
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
ThaiDai said:
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
Click to expand...
Click to collapse
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
stefano_te said:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
Click to expand...
Click to collapse
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
ThaiDai said:
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
Click to expand...
Click to collapse
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
stefano_te said:
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
Click to expand...
Click to collapse
No. Because you do this partly when using the kitchen step by step. Or when changing your updater-script.
The kitchen is a great help and simplifies cooking a rom - but it still is a little bit more complicated than heating baby food in the microwave. And if you really want your "custom" rom you should start to learn what happens in each step. And this can't be done by revealing everything...
I try to get shared preferences in the exposed class.
This is a straight forward issue in android java. I do not know whether the permissions are the problem but things are not as straight with Xposed.
Xposed asks to provide the name of the file and the package at init Zigote. I have tried many versions and none of them seems to work. Also, the file which I make may not be available when init Zygote is called, however, I take XposedBridge wants to just register the name of the file and, probably, to prepare to override some permissions when the file is created.
I also try to double the call to the Xposed Shared Method inside the hooked method. I check for the existence of the shared preference file before. Everything is there but the reload method does not seem to reload and the file is not read but defaults are loaded by getInt and getFloat.
There is probably something more to be done, although the examples I have seen do not do anything, yet they override other methods inside init Zygote which I do not need to do.
All I need is to read a simple file from an Xposed Module.
PLEASE, INFORM.
Here is what I have tried :
I have tried many different variation and XposedBridge methods for 4 hours. I have also
tried many name variations with and without .xml.
In the standard Java for Android, there is just one get method to read a shared
preferences file. This does not seem to be the case with exposed.
I do have :
@override
public void initZygote(StartupParam startupParam) throws Throwable {
MODULE_PATH = startupParam.modulePath;
prefs = new XSharedPreferences("PackageName", "SharedPreferenceFileNameWithotDotXml");
}
MODULE_PATH is not used, although I have tried many other methods where was.
Because the file changes on the fly, I called :
prefs.reload();
before I read the data. I tried without this call too. I also tried to get another
prefs before the reload :
prefs = new XSharedPreferences("PackageName", "SharedPreferenceFileNameWithotDotXml");
prefs.reload();
Then I try to read the data from the file :
theStart=prefs.getInt("Start", 2);
theValue=prefs.getFloat("Value", 102.0f);
I always get the defaults 2 and 102.0 although the file is there and the values of the
file are different. I have read the file.
In standard java for android philosophy, just the initialisation in init zygote and
prefs.reload() are sufficient to load the changing values of the shared preferences
file into prefs and then into the variables.
Xposed seems to be different.
I have been told there is a way to read the data from the file. I have tried most
anything and cannot. What is the way to do so. Must be simple and straight as in the
standard java for android. I must not do everything necessary.
Please, inform.
I have also tried to read the file manually from the Xposed class. Access denied. Tried
just in cases. Access denied, again.
Tried to make the shared preferences file with Activity.MODE_WORLD_READABLE. Still
access denied to be read manually.
Even with Activity.MODE_WORLD_READABLE, Xposed cannot read the file as previously
explained.
Tried :
@override
public void initZygote(StartupParam startupParam) throws Throwable {
prefs = new XSharedPreferences(TheNameOfTheXposedClass.class.getPackage().getName
());
prefs.makeWorldReadable();
}
Then, in the hooked method :
prefs.reload();
theStart = prefs.getInt("Start", 2);
theValue = prefs.getFloat("Value", 102.0f);
Still returns only the default, although the file is there. I think, in all attempts,
XSharedPreferences() cannot get the name of the package and or or the name of the file.
The file is in /data/data/NameOfPackage/shared_prefs/NameOfFile.xml
Tried :
@override
public void initZygote(StartupParam startupParam) throws Throwable {
prefs = new XSharedPreferences
("/data/data/NameOfPackage/shared_prefs/NameOfFile.xml");
prefs.makeWorldReadable();
}
with and without .xml
Still nothing.
PROBLEM SOLVED.
Thank you for your reply. Everything was WORLD READABLE : in the non Xposed class and in the Xposed class on a number of occasions.
Also, I have used the hard values for the package and path.
The problem was not related to Java and Android but to Android arrangements and how much Xposed can cope with. The Android permissions for to access the file from the Xposed class had to be elevated which is unusual but this is what solved the problem, I think. Someone also reported the same problem and the same solution : http://forum.xda-developers.com/xposed/development-xsharedpreferences-issue-t2931396
In the non Xposed class, I have used the same solution just with a hard coded path and file. After I make the shared preferences file in the non Xposed class, I gave more permissions by :
File theSharedPrefsFile;
theSharedPrefsFile = new File("/data/data/PackageName/shared_prefs/FileName.xml");
theSharedPrefsFile.setReadable(true, false);
This seems to have solved the problem.
I am not sure of how reliable the solution is, though. I still check in the Xposed class whethere there is such a file or not. I have not tested what happens when the file is not there initially. Must do.
theXposedCommunicationPreferenceFile = new File("/data/data/PackageName/shared_prefs/FileName.xml");
if (theXposedCommunicationPreferenceFile.exists() == false) XposedBridge.log("Check in hooked method cannot find the file");
Hope everything would be OK.
Even though everything should be OK, I am not sure how reliable the dependence of permissions is.
I have also tried the secure reload :
StrictMode.ThreadPolicy oldPolicy;
oldPolicy = StrictMode.allowThreadDiskReads();
try {
prefs.reload();
} finally {
StrictMode.setThreadPolicy(oldPolicy);
}
I am not sure how reliable this is either so I put another simple reload on top :
prefs.reload();
StrictMode.ThreadPolicy oldPolicy;
oldPolicy = StrictMode.allowThreadDiskReads();
try {
prefs.reload();
} finally {
StrictMode.setThreadPolicy(oldPolicy);
}
I think, neither of these has made any difference and the real solution was the higher permissions to access the shared preference file given in the non Xposed class, again :
File theSharedPrefsFile;
theSharedPrefsFile = new File("/data/data/PackageName/shared_prefs/FileName.xml");
theSharedPrefsFile.setReadable(true, false);
Pretty nasty problem and difficult to find solution although published in the XDA Forum the searchability of post in the said forum is not very good.
Yet another sleepless night.
StevenStanleyBayes said:
I think, neither of these has made any difference and the real solution was the higher permissions to access the shared preference file given in the non Xposed class, again :
Click to expand...
Click to collapse
I know this is a pretty old thread but I have elevated the permission level to 777 of both the dir and preferences file and yet cannot access the file from the xposedClass is there any chance you are still developing xposed modules and can help
I'm trying to make an application that sends a .tar file through a socket through android. The .tar file is generated on the fly, so in memory, and it is a tar file of the entire /sdcard directory, as we can't assume the phone has enough space to make the .tar file.
In the computer end I make an adb forward tcp:8000 tcp:800; netstat -w 10 localhost:8000 > out.tar;
Then I execute the application through Android Studio, a snippet of the code is:
Code:
Log.i(TAG, "Launching Socket");
Socket sk = new Socket("127.0.0.1", 8000);
Log.i(TAG, "Socket Launched");
TarOutputStream out = new TarOutputStream(new BufferedOutputStream(sk.getOutputStream()));
tarFolder(null, "/sdcard", out);
For some reason when trying to execute the code I get the error:
Code:
java.net.ConnectException: failed to connect to /127.0.0.1 (port 8000): connect failed: ECONNREFUSED (Connection refused)
I know the error is self-explanatory but I can't figure out how to fix it. Any clues? I haven't really worked with sockets in Android before so I don't know if I'm doing the socket part wrong or maybe the pardigm of reidrecting the port 8000 to localhost is just wrong.
I would really appreciate an expert's opinion.
Thank you very much!
arnauec said:
I'm trying to make an application that sends a .tar file through a socket through android. The .tar file is generated on the fly, so in memory, and it is a tar file of the entire /sdcard directory, as we can't assume the phone has enough space to make the .tar file.
In the computer end I make an adb forward tcp:8000 tcp:800; netstat -w 10 localhost:8000 > out.tar;
Then I execute the application through Android Studio, a snippet of the code is:
Code:
Log.i(TAG, "Launching Socket");
Socket sk = new Socket("127.0.0.1", 8000);
Log.i(TAG, "Socket Launched");
TarOutputStream out = new TarOutputStream(new BufferedOutputStream(sk.getOutputStream()));
tarFolder(null, "/sdcard", out);
For some reason when trying to execute the code I get the error:
Code:
java.net.ConnectException: failed to connect to /127.0.0.1 (port 8000): connect failed: ECONNREFUSED (Connection refused)
I know the error is self-explanatory but I can't figure out how to fix it. Any clues? I haven't really worked with sockets in Android before so I don't know if I'm doing the socket part wrong or maybe the pardigm of reidrecting the port 8000 to localhost is just wrong.
I would really appreciate an expert's opinion.
Thank you very much!
Click to expand...
Click to collapse
I finally managed to fix this, the problem was that I was doing a redirection of ports using adb forward, but I wanted to go from the phone to the computer so I was supposed to use adb reverse.
Closing thread.
Hi fellows
I'm a kind of newbie in the Android world, but I created a set of shell scripts to work with Topway TS10 Firmware:
---------------------------------------------------------------------------------------------------------------
TS10-Firmware-WorkbenchScripts intended to mount the Topway TS10 Firmware, make modifications and reassemble the firmware They can retrieve the firmware from specified location and after modification, they can put the firmware into another specified location
Files:
1-) config.ini = A file to setup parameters, paths for the original firmware and patched firmware, temp directory to work with firmware files and mount point to edit the firmware
2-) import_original.sh = Retrieves the files .0 .1 .2 and .3 from the location specified in config.ini
3-) import_patched.sh = Retrieves the same files that 'import_original.sh' but from the patched location specified in the config.ini (normally a firmware that you've already patched before)
4-) unpack.sh = Unpack the imported firmware and create the mount moint (as specified in the config.ini file) to work with the firmware
5-) repack.sh = Unmount the modified firmware from the mount point, delete the mount point, split the firmware in files .0 .1 .2 and .3 and move it to the patched directory as specified in config.ini
6-) inject_tweaks.sh = Modify locale, dataroaming and remove (if necessary) the values in ro.fota.device to avoid message "UI unauthorized, please contact the supplier"
7-) inject_mods.sh = This will copy all the contents of the '_mods' folder inside firmware. I.E. I put a 'gps_debug.cfg' inside 'system/etc/' and it will be injected into firmware overwritting the existent
inject_su.sh = This will inject su binary into firmware as a daemon, this is dangerous as the firmware is permanently rooted and the apps don't ask for permissions (they already have the root access) USE AT YOUR OWN RISK
9-) clean_local.sh = This script will unmount the firmware and delete it, it will also delete temporary files. as its name says, it cleans the dir !
External (included) tools:
tools/twt (Topwaytool) forked from https://github.com/mkotyk/topwaytool
_mods folder containing a sample file 'gps_debug.cfg'
N'joy it !
---------------------------------------------------------------------------------------------------------------
News
This will allow you to have root privileges in original firmware, but read VERY CAREFULLY as this method int NOT SAFE at all
At least for me it do the trick as I expected
I'll have my Topway TS10 THEME1 HU in a week and, if I am brave enough, I'll give it a go.
mariodantas said:
News here
https://github.com/mariodantas/TS10-Firmware-Workbench
This will allow you to have root privileges in original firmware, but read VERY CAREFULLY as this method int NOT SAFE at all
At least for me it do the trick as I expected
Click to expand...
Click to collapse
Is this way to root ownice k7 radio that i wish?? TT wow.....
This will ROOT, but everything inside will have ROOT privileges, UNSAFE, but as I said, for me, it did the trick and I'm happy with this !
mariodantas said:
This will ROOT, but everything inside will have ROOT privileges, UNSAFE, but as I said, for me, it did the trick and I'm happy with this !
Click to expand...
Click to collapse
Hello mariodantas.
I'm trying to utilize the project you made to mount firmware and inject su.
I'm a little new to some of this, so any guidance would be grateful.
Question:
How do i know what the mount point should be while using unpack.sh in config.ini?
! Creating _mountpoint folder...
Step 4 of 4 - Mounting ready raw firmware into '_mountpoint/' folder
mount: exec /Library/Filesystems/auto.fs/Contents/Resources/mount_auto for /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint: No such file or directory
mount: /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint failed with 72
READY !!!, you can go into '_mountpoint/' folder.
But _mountpoint folder is empty.
Andason74 said:
Hello mariodantas.
I'm trying to utilize the project you made to mount firmware and inject su.
I'm a little new to some of this, so any guidance would be grateful.
Question:
How do i know what the mount point should be while using unpack.sh in config.ini?
! Creating _mountpoint folder...
Step 4 of 4 - Mounting ready raw firmware into '_mountpoint/' folder
mount: exec /Library/Filesystems/auto.fs/Contents/Resources/mount_auto for /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint: No such file or directory
mount: /Users/me/Desktop/TS10-Firmware-Workbench-main/_mountpoint failed with 72
READY !!!, you can go into '_mountpoint/' folder.
But _mountpoint folder is empty.
Click to expand...
Click to collapse
What is your platform ? OSX ?
mariodantas said:
What is your platform ? OSX ?
Click to expand...
Click to collapse
Yes, OSX. I was checking more last night and maybe the issue is how mac handles the "auto" for file type.
Yes it sould be the mount command for OSX, but i can't help with OSX sorry, maybe you can clone the repo and after find the solution issue a pull request ?
after rooting the firmware doesn't seem to pass the checksum, everything is not working please help me ts10 1.2 ols10. ownice
Hello, have to check what's wrong with my code against 1.2 ols10 firmware, will check tonight and come back ASAP !
Cannot open file patch /init.rc.patch do not such how to fix please
Ok will check tonight !
@binharmani please add this to your config.ini
#Super User Folder
SUPERUSERFOLDER="_ superuser"
Click to expand...
Click to collapse
thank bro tool is ok . amazing good job
Thanks fellow
you can modify the "build.prop" manually after using "unpack.sh" by entering into "_mountpoint", modifying what you need and then repack the file and reflash in your headunit
How to set 775 file build.prop on linux
binharmani said:
How to set 775 file build.prop on linux
Click to expand...
Click to collapse
chmod 0775 build.prop
you should use a command line instead of the interface !
Mario good morning, if possible for you check the metode for change image car on display of ownice K7 ? Image in centrale display is very bad ifnpossible change png image with other car .......?
hello!
i've managed to use your tool, but there is a mention:
i've used it in a ubuntu vm (latest) and the mountpoint directory is empty if i don't run everything as root
repacked ok after this
my question is if i have to add the other files originally found in my original firmware folder with the newly repacked firmware files.
original firmware content (TS10.1.2_20210505.171701_TW1-V2):
a53f244a-9cbf-11ea-bb71-8bb1f7c98e0b.*
a71a8002-9cbf-11ea-b64e-578022b8a84a
ab2e7e2e-9cbf-11ea-bb71-fbb02866c44e
repacked firmware content:
a53f244a-9cbf-11ea-bb71-8bb1f7c98e0b.*