I found a com port source to reset Samsung pattern .. but this seems not work on new Android Versions .. any expert help me to work this source with new Android Versions 4.x.x. .. what is new string to write to port for new Android version.
Code:
procedure TF_Main.BsendClick(Sender: TObject);
var
iPos: Integer;
result: string;
begin
if Port.Text='' then
begin
log1.Items.Add('First Select Port!');
exit;
end;
Log1.clear;
MainPort:= Port.text;
ComPort1.Port:='' + MainPort;
ComPort1.BaudRate:=br115200;
if ComPort1.Connected then
ComPort1.Close;
try
ComPort1.Open;
except
Log1.Items.Add('Port COM already open!');
ComPort1.Close;
exit;
end;
if ComPort1.Connected then
begin
Log1.Items.Add('try open Port.....');
end;
WritePort('41 54 45 30 0D 0A');
Application.ProcessMessages;
Sleep(550);
F_Main.ComPort1.ReadStr(result,200);
result:=StrToHex(result);
iPos:=Pos('4F4B',result);
if(iPos >0) then else
begin
Log1.items.Add('Phone no detected,check conection!');
exit;
end;
[B][COLOR="Red"]WritePort('41 54 2B 43 47 4D 4D 0D 0A');[/COLOR][/B]
Application.ProcessMessages;
sleep(100);
F_main.ComPort1.ReadStr(result, 200);
result:= StrToHex(result);
iPos := Pos ('0D0A', result);
if (iPos > 0) then
begin
Model:= hextostr(Copy(result, iPos + 4, length(result)-20));
Log1.Items.Add('Port open sucessfull');
Log1.items.add('[' + Model + ']');
end;
[B][COLOR="Red"]WritePort(' 41 54 2B 57 49 46 49 49 44 52 57 3D 31 2C 30 0D 0A ');[/COLOR][/B]
Application.ProcessMessages;
sleep(100);
F_main.ComPort1.ReadStr(result, 200);
result:= StrToHex(result);
iPos := Pos ('0D0A', result);
if (iPos > 0) then
begin
patternunlock:= hextostr(Copy(result, iPos + 4, length(result)-20));
Log1.items.add('[ Pattern Unlock DONE!!! :) ]');
end;
end;
Related
Hi 2 All!
Please, can you help me in solving with the following problem.
I have download file bootloader.exe to my hp ipaq 1930 and I run it.
Now I see hp logo on white font and some numbers (bootloader version?) 1.07 and under it 1.07
Certainly, hard reset and removing the battery for 2-3 days didn't help. As I was said I need only to run update from big pc. I have another 1930, alive. I made rom-image to sd card using mtyy
Flashing with the card with rom-image didn't help to my injuried 1930
I contacted hp and they said to me that
the rom version for hp1940 1.00.03 is compatible. Then I ran the update, before that changing in the *.nbf file 1940 to 1930 and started flashing. It went to 75% and stoped saying Update error.
Then I was said to fullfill sd card with one symbol (Z). Then I made again a rom-image and I copied all hex values above code Z into a new file. I founf 2 entering starting from FE 03 00 EA and deleted the values above. Then I copied from 1940 nbf the following information^
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 68 70 20 69 50 41 51 20 68 31 39 34 30 00 00 31 hp iPAQ h1940..1
00000010 2E 31 30 2E 32 30 20 45 4E 47 00 00 00 00 0F F6 .10.20 ENG.....?
00000020 71 77 00 00 0C 01
and in the dress from E1-21 wrote checksum value in 32 bit and length of the file in the addresses from 22-25. Then I copied the file into the folder from 1940 with the name=the name of the *.nbf file in the folder. I started update. It began and stoped on 50% saying "Update eroor"
Are there any ideas? Thanks a lot.
Or perhaps somebody has firmware for 1930/35? Thanks a lot
Maybe these people could help you, they must have the image if they are offering the service.
http://www.ipaqrepair.co.uk/ipaqpart447.html
Thanks. Here is the *.nbf file for 1930. http://www.megaupload.com/?d=HROH0ZOO It must have the same nema, as it is in the folder, where 1940 utiilty unpack it's files.
Copy it where the 1940 romupdateutility unpacked it's files. Then run again the utility
Alva said:
Thanks. Here is the *.nbf file for 1930. http://www.megaupload.com/?d=HROH0ZOO It must have the same nema, as it is in the folder, where 1940 utiilty unpack it's files.
Copy it where the 1940 romupdateutility unpacked it's files. Then run again the utility
Click to expand...
Click to collapse
hello could you please re-upload file?
Rom? where is the rom for 1930? please help me
Can please someone say me what's the chip of FM radio that our devices use?
thanks.
Gee I just spent at least 15 minutes looking for that answer too.
Show me the ps output with BT on and I can probably tell you the family. btld or brcm_patchram_plus are components of the proprietary Broadcom BT stack which is the most common.
btipsd would be a TI device.
Just hciattach without any of the above might require checking the /init.*.rc files for the options to hciattach. Firmware files are also a clue, as is dmesg output.
Of course you might have a rarer Silicon Labs chip and lsmod might show it, or some fm device driver pseudo file in /dev/ and perhaps Si4709_driver.ko or similar somewhere.
If you have a working hcitool and bt is enabled this HCI Get Version command would show something similar to this:
adb shell hcitool cmd 4 1
< HCI Command: ogf 0x04, ocf 0x0001, plen 0
> HCI Event: 0x0e plen 12
01 01 10 00 04 00 00 04 0D 00 1F 1D
If you have a working hcitool on a Broadcom family device the following would be shown when the radio and RDS are on:
adb shell hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
> HCI Event: 0x0e plen 7
01 15 FC 00 00 01 03
And here's the equivalent on a TI device:
adb shell hcitool cmd 3f 133 20 2 0
< HCI Command: ogf 0x3f, ocf 0x0133, plen 3
20 02 00
> HCI Event: 0x0e plen 6
01 33 FD 00 00 03
Here's my output
Code:
# hcitool cm 4 1
hcitool cm 4 1
# hcitool cmd 3f 15 0 1 1
hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
Send failed: File descriptor in bad state
# hcitool cmd 3f 133 20 2 0
hcitool cmd 3f 133 20 2 0
< HCI Command: ogf 0x3f, ocf 0x0133, plen 3
20 02 00
Send failed: File descriptor in bad state
#
What does Descriptor means?
D4rKn3sSyS said:
Here's my output
Code:
# hcitool cm 4 1
hcitool cm 4 1
# hcitool cmd 3f 15 0 1 1
hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
Send failed: File descriptor in bad state
# hcitool cmd 3f 133 20 2 0
hcitool cmd 3f 133 20 2 0
< HCI Command: ogf 0x3f, ocf 0x0133, plen 3
20 02 00
Send failed: File descriptor in bad state
#
What does Descriptor means?
Click to expand...
Click to collapse
If you ran these commands with Bluetooth (BT) enabled, then in this case it means you have a proprietary BT stack.
In general: http://en.wikipedia.org/wiki/File_descriptor
mikereidis said:
If you ran these commands with Bluetooth (BT) enabled, then in this case it means you have a proprietary BT stack.
In general: http://en.wikipedia.org/wiki/File_descriptor
Click to expand...
Click to collapse
its broadcom bt. with brcm_patchram_plus you can check in se sources und platform/system/bluetooth/
here is kernel config:
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
slade87 said:
its broadcom bt. with brcm_patchram_plus you can check in se sources und platform/system/bluetooth/
here is kernel config:
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
Click to expand...
Click to collapse
OK, thanks much.
In that case my app should be usable on this phone in the currently experimental "HCI UART" mode, where a daemon speaks directly with the UART. It only works with BT off though, but I'm hoping to find a better HCI access method. Also need root.
I should post a new experimental version on the thread in my sig in an hour or so. One warning though; on many phones where my app tunes and gets RDS data etc, there is no audio. I'm working on "tricks" for that issue also.
mikereidis said:
OK, thanks much.
In that case my app should be usable on this phone in the currently experimental "HCI UART" mode, where a daemon speaks directly with the UART. It only works with BT off though, but I'm hoping to find a better HCI access method. Also need root.
I should post a new experimental version on the thread in my sig in an hour or so. One warning though; on many phones where my app tunes and gets RDS data etc, there is no audio. I'm working on "tricks" for that issue also.
Click to expand...
Click to collapse
thank you for your development!
I do not plan to "make 10 helpful posts", but i have question for "[HOWTO] GT-I9100 Free SIM Unlock via nv_data.bin by Odia" ( http: //forum.xda-developers.com/showthread.php?t=1064978 ). If moderator thinks, that the question deserves to be in its right place, please move it.
5. If the hash is 7D 3E 17 CF CD 81 6C AC D4 E0 25 FA A6 50 04 FD D1 7D 51 F8 ignore it since that is 00000000
6. Put the hash into the BF exe for example:-
ighashgpu.exe /h:EF63BF26E2382917D96850CCF9632458EE6E6C77 /t:sha1 /c:d /max:8 /min:8 /salt:0000000000000000
and wait for it to finish, do that for each hash which is not zeros, the Found password: [50681318] is the code.
Click to expand...
Click to collapse
I don't understand how sha1 of 506813180000000000000000 is EF63BF26E2382917D96850CCF9632458EE6E6C77
or how sha1 of 000000000000000000000000 is 7D 3E 17 CF CD 81 6C AC D4 E0 25 FA A6 50 04 FD D1 7D 51 F8.
if i do
echo -n "0000000000000000000000000"|sha1sum
i get 8e17426f851a81f65e3626c12d5ba83132207f6f
and
echo -n "506813180000000000000000"|sha1sum
d9d4ec51debfaba4e603003e594705b81a22e2ca
can somebody explain?
Thanks
explanation
I had the same question today, finally found the solution. Similar to you, I have misinterpreted salt parameter in the quoted command example:
ighashgpu.exe /h:EF63BF26E2382917D96850CCF9632458EE6E6C77 /t:sha1 /c:d /max:8 /min:8 /salt:0000000000000000
Salt is not 16 zero digits, but 8 zero bytes (represented as hexadecimal). Try it yourself, note the e parameter of echo (enable interpretation of backslash escapes):
echo -ne "00000000\0\0\0\0\0\0\0\0"|sha1sum
7d3e17cfcd816cacd4e025faa65004fdd17d51f8 -
Hi
I just changed some stuff like images in a kernel using Android Kernel Kitchen 0.3.1.
Now I wanna test my changes.
My questions is->
What are worst case scenarios possible?
I am ready to go for boot loops and etc. but are there any consequences that may cause real hard brick of my phone? (Like---> it will never start again! or you need to take it to service center for repair!)?
Jaskaran498 said:
Hi
I just changed some stuff like images in a kernel using Android Kernel Kitchen 0.3.1.
Now I wanna test my changes.
My questions is->
What are worst case scenarios possible?
I am ready to go for boot loops and etc. but are there any consequences that may cause real hard brick of my phone? (Like---> it will never start again! or you need to take it to service center for repair!)?
Click to expand...
Click to collapse
What you can expect are boot loops, inability to get even see the boot splash, non-working wifi/ USB / touch / camera/ anything that needs a driver, random reboots. Personal experience: yesterday I was playing with changing part of the initramfs without changing the whole boot.img. It turns out that I needed to update the header size and checksum. Without this, it would hang for some seconds and then reboot (or not start at all). This was all fixable from recovery.
What can happen if you are not careful is a brick because you flash the wrong partition. Otherwise, you can always enter recovery mode and flash the kernel (for the i9300, it is mmcblk0p5). If you are not sure, look for the magic ANDROID! header:
Code:
# dd bs=64 count=1 if=/dev/block/mmcblk0p5 2>/dev/null | hexdump -C
00000000 41 4e 44 52 4f 49 44 21 80 bc 44 00 00 80 00 40 |[email protected]|
00000010 2e 1e 05 00 00 00 00 41 00 00 00 00 00 00 f0 40 |[email protected]|
00000020 00 01 00 40 00 08 00 00 00 00 00 00 00 00 00 00 |[email protected]|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040
So, the absolute worst-case scenario is when you accidentally flash the wrong partition. If you picked your EFS partition and do not have a backup, then your IMEI and stuff are gone.
Note: be sure not to wipe your recovery partition (mmcblk0p6), that requires you restore the recovery using download mode (I have not experienced this yet).
Lekensteyn said:
What you can expect are boot loops, inability to get even see the boot splash, non-working wifi/ USB / touch / camera/ anything that needs a driver, random reboots. Personal experience: yesterday I was playing with changing part of the initramfs without changing the whole boot.img. It turns out that I needed to update the header size and checksum. Without this, it would hang for some seconds and then reboot (or not start at all). This was all fixable from recovery.
What can happen if you are not careful is a brick because you flash the wrong partition. Otherwise, you can always enter recovery mode and flash the kernel (for the i9300, it is mmcblk0p5). If you are not sure, look for the magic ANDROID! header:
Code:
# dd bs=64 count=1 if=/dev/block/mmcblk0p5 2>/dev/null | hexdump -C
00000000 41 4e 44 52 4f 49 44 21 80 bc 44 00 00 80 00 40 |[email protected]|
00000010 2e 1e 05 00 00 00 00 41 00 00 00 00 00 00 f0 40 |[email protected]|
00000020 00 01 00 40 00 08 00 00 00 00 00 00 00 00 00 00 |[email protected]|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040
So, the absolute worst-case scenario is when you accidentally flash the wrong partition. If you picked your EFS partition and do not have a backup, then your IMEI and stuff are gone.
Note: be sure not to wipe your recovery partition (mmcblk0p6), that requires you restore the recovery using download mode (I have not experienced this yet).
Click to expand...
Click to collapse
Kk, thanks.
But what do i do if it does not start at all like u said (what i want is that it should at least be able start in recovery or download if possible).
Since its my first time messing with kernel, i am total n00b then
If it cannot proceed to the "normal" boot, then get into recovery by holding Volume Up + Power + Home for ten seconds while booting (I usually do that when I see the Samsung logo end release when it has restarted, showing the logo again (about ten seconds).
From there, use Install from zip (if you have a "update zip" that contains boot.img and some metadata) or (what I do) use adb push to put the image in /tmp/. Then use dd to write the boot image. Example (I use Linux):
Code:
laptop$ adb push boot-new.img /tmp/boot.img
laptop$ adb shell
# cat /tmp/boot.img > /dev/block/mmcblk0p5
Just in case of hardware failure, I also verify the md5sum:
Code:
laptop$ md5sum boot-new.img
laptop$ du -b boot-new.img # determine file size, say 1234
(android) # dd if=/dev/block/mmcblk0p5 bs=1234 count=1 | md5sum
The two outputs must match, otherwise something went wrong (unlikely, but still).
Lekensteyn said:
If it cannot proceed to the "normal" boot, then get into recovery by holding Volume Up + Power + Home for ten seconds while booting (I usually do that when I see the Samsung logo end release when it has restarted, showing the logo again (about ten seconds).
From there, use Install from zip (if you have a "update zip" that contains boot.img and some metadata) or (what I do) use adb push to put the image in /tmp/. Then use dd to write the boot image. Example (I use Linux):
Code:
laptop$ adb push boot-new.img /tmp/boot.img
laptop$ adb shell
# cat /tmp/boot.img > /dev/block/mmcblk0p5
Just in case of hardware failure, I also verify the md5sum:
Code:
laptop$ md5sum boot-new.img
laptop$ du -b boot-new.img # determine file size, say 1234
(android) # dd if=/dev/block/mmcblk0p5 bs=1234 count=1 | md5sum
The two outputs must match, otherwise something went wrong (unlikely, but still).
Click to expand...
Click to collapse
I know all this but what i m saying is that can there be conditions where neither i will be able to boot recovery nor download (even by volume+power+home method)?
Unless you do really stupid things like overwriting /dev/block/mmcblk0 or other partitions on http://cleanimport.xda/index.php?threads/2362743/, you will be safe.
Jaskaran498 said:
I know all this but what i m saying is that can there be conditions where neither i will be able to boot recovery nor download (even by volume+power+home method)?
Click to expand...
Click to collapse
Recovery has it's own kernel. It doesn't use the one you're modifying
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Hello friends, I need a little help with the usid / mac_ether script
i am starting to study about android and i would like to ask you:
First I would like someone to help me record a serial
at box amlogic
1: Firmware already passed Amlogic Customization tools (key usid, mac marked for write)
2: in the SN part I always want the serial to be written to be this ... 8e.05-17.06-10500171 <---------- SN
3: on mac's part i want this recorded
EC: 2C: A9: 51: 52: 31
3: usid script
[Group1]
usid = ShiningStar <1> MBX <2>
param_1_format =% 04x
param_1_start = 0000
param_1_end = FFFF
param_1_used = 0x0
param_1_total = 1000
param_2_format =% 04x
param_2_start = 0000
param_2_end = FFFF
param_2_used = 0x0
param_2_total = 1000
[Size]
Size = 22
[fragment]
fragment =
4: mac script
[Group1]
start = 00: 0f: a3: 45: 9b: 12
end = 00: 0f: a3: 45: a1: 34
total = 1540
used = 2
current =
[fragment]
fragment =
5: Help me understand how to put the above information into the script to write it to the box.