I got my xperia neo L drowned. but now it is waterlocked. But still I can use my phone only I can view the display, touch panel is not working.
I want some adb commands to do some tasks in it.I had usb debugging enabled. I confirmed that my phone is connected to the adb shell
but still when i used this command "adb shell svc wifi enable" the output is "killed" what is the actual problem
how can i get rid of it.
dmanojkmr said:
I got my xperia neo L drowned. but now it is waterlocked. But still I can use my phone only I can view the display, touch panel is not working.
I want some adb commands to do some tasks in it.I had usb debugging enabled. I confirmed that my phone is connected to the adb shell
but still when i used this command "adb shell svc wifi enable" the output is "killed" what is the actual problem
how can i get rid of it.
Click to expand...
Click to collapse
Never mind these errors. I tried a different way to navigate in android.
using the key events
Code Numbers for ADB Input
You can use key codes directly like
adb shell input keyevent 7 # for key ’0′
adb shell input keyevent 8 # for key ’1′
adb shell input keyevent 29 # for key ‘A’
adb shell input keyevent 54 # for key ‘B’
we can also send string as a text, like
adb shell input text “ANDROID”
The below text is the whole list of all keyevent names with their
respective codes numbers…
0 –> “KEYCODE_UNKNOWN”
1 –> “KEYCODE_MENU”
2 –> “KEYCODE_SOFT_RIGHT”
3 –> “KEYCODE_HOME”
4 –> “KEYCODE_BACK”
5 –> “KEYCODE_CALL”
6 –> “KEYCODE_ENDCALL”
7 –> “KEYCODE_0″
8 –> “KEYCODE_1″
9 –> “KEYCODE_2″
10 –> “KEYCODE_3″
11 –> “KEYCODE_4″
12 –> “KEYCODE_5″
13 –> “KEYCODE_6″
14 –> “KEYCODE_7″
15 –> “KEYCODE_8″
16 –> “KEYCODE_9″
17 –> “KEYCODE_STAR”
18 –> “KEYCODE_POUND”
19 –> “KEYCODE_DPAD_UP”
20 –> “KEYCODE_DPAD_DOWN”
21 –> “KEYCODE_DPAD_LEFT”
22 –> “KEYCODE_DPAD_RIGHT”
23 –> “KEYCODE_DPAD_CENTER”
24 –> “KEYCODE_VOLUME_UP”
25 –> “KEYCODE_VOLUME_DOWN”
26 –> “KEYCODE_POWER”
27 –> “KEYCODE_CAMERA”
28 –> “KEYCODE_CLEAR”
29 –> “KEYCODE_A”
30 –> “KEYCODE_B”
31 –> “KEYCODE_C”
32 –> “KEYCODE_D”
33 –> “KEYCODE_E”
34 –> “KEYCODE_F”
35 –> “KEYCODE_G”
36 –> “KEYCODE_H”
37 –> “KEYCODE_I”
38 –> “KEYCODE_J”
39 –> “KEYCODE_K”
40 –> “KEYCODE_L”
41 –> “KEYCODE_M”
42 –> “KEYCODE_N”
43 –> “KEYCODE_O”
44 –> “KEYCODE_P”
45 –> “KEYCODE_Q”
46 –> “KEYCODE_R”
47 –> “KEYCODE_S”
48 –> “KEYCODE_T”
49 –> “KEYCODE_U”
50 –> “KEYCODE_V”
51 –> “KEYCODE_W”
52 –> “KEYCODE_X”
53 –> “KEYCODE_Y”
54 –> “KEYCODE_Z”
55 –> “KEYCODE_COMMA”
56 –> “KEYCODE_PERIOD”
57 –> “KEYCODE_ALT_LEFT”
58 –> “KEYCODE_ALT_RIGHT”
59 –> “KEYCODE_SHIFT_LEFT”
60 –> “KEYCODE_SHIFT_RIGHT”
61 –> “KEYCODE_TAB”
62 –> “KEYCODE_SPACE”
63 –> “KEYCODE_SYM”
64 –> “KEYCODE_EXPLORER”
65 –> “KEYCODE_ENVELOPE”
66 –> “KEYCODE_ENTER”
67 –> “KEYCODE_DEL”
68 –> “KEYCODE_GRAVE”
69 –> “KEYCODE_MINUS”
70 –> “KEYCODE_EQUALS”
71 –> “KEYCODE_LEFT_BRACKET”
72 –> “KEYCODE_RIGHT_BRACKET”
73 –> “KEYCODE_BACKSLASH”
74 –> “KEYCODE_SEMICOLON”
75 –> “KEYCODE_APOSTROPHE”
76 –> “KEYCODE_SLASH”
77 –> “KEYCODE_AT”
78 –> “KEYCODE_NUM”
79 –> “KEYCODE_HEADSETHOOK”
80 –> “KEYCODE_FOCUS”
81 –> “KEYCODE_PLUS”
82 –> “KEYCODE_MENU”
83 –> “KEYCODE_NOTIFICATION”
84 –> “KEYCODE_SEARCH”
85 –> “TAG_LAST_KEYCODE”
From https://groups.google.com/forum/#!topic/android-developers/pHBcP2JBT5A
Related
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
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;
Fully Deodexed Stock Untouched MRA58K Base for ROM Devs to use to maybe kick out some Deodexed Marshmallow ROMs to bake in some goods
General Information - Background
I took an immense amount of time doing this and trying to figure out. I am not skilled enough to develop my own ROM at this stage of the fame. I have a lot to learn I guess you could say. I am hoping the ROM developers can take this saving them an immense amount of time and put something together. They do a lot for us, so hoping maybe this can help cut down some time for them. I also am implementing 3Minit Battery Mod as well by request. You have over 1100 batteries to choose from on the fly that you can resize or change without a restart at all. Hopefully we can get these mods going!!!
Download Section - FYI NOTHING IS FLASHABLE
MRA58K_PureStock_Untouched_Fully_Deodexed - Only framework, priv-app, app
MRA58K_PureStock_Untouched_Fully_Deodexed.zip
MRA58K_PureStock_Untouched_Fully_Deodexed_Full_ROM_NOT_FLASHABLE
MRA58K_PureStock_Untouched_Fully_Deodexed_Full_ROM_NOT_FLASHABLE.zip
Deodex Log
Code:
10-10-2015:01-00-20 => Framework Folder Exists
10-10-2015:01-00-20 => boot.oat Exists
10-10-2015:01-00-20 => App Folder Exists
10-10-2015:01-00-20 => Priv-App Folder Exists
10-10-2015:01-00-20 => Deodexing Started
10-10-2015:01-00-20 => Extracting Boot.oat
10-10-2015:01-00-20 => Copying Boot.oat to Working Directory - SUCCESS
10-10-2015:01-00-35 => Boot.oat Extraction Complete
10-10-2015:01-00-35 => Odexed System Apps Count: 65
10-10-2015:01-00-35 => Deodexing System Apps
10-10-2015:01-00-36 => 1 of 65 - atfwd - SUCCESS
10-10-2015:01-00-37 => 2 of 65 - BasicDreams - SUCCESS
10-10-2015:01-00-39 => 3 of 65 - Bluetooth - SUCCESS
10-10-2015:01-00-40 => 4 of 65 - BluetoothMidiService - SUCCESS
10-10-2015:01-00-49 => 5 of 65 - Books - SUCCESS
10-10-2015:01-00-50 => 6 of 65 - CalculatorGoogle - SUCCESS
10-10-2015:01-00-57 => 7 of 65 - CalendarGooglePrebuilt - SUCCESS
10-10-2015:01-00-57 => 8 of 65 - CaptivePortalLogin - SUCCESS
10-10-2015:01-00-58 => 9 of 65 - CertInstaller - SUCCESS
10-10-2015:01-01-05 => 10 of 65 - Chrome - SUCCESS
10-10-2015:01-01-09 => 11 of 65 - CloudPrint2 - SUCCESS
10-10-2015:01-01-11 => 12 of 65 - DMAgent - SUCCESS
10-10-2015:01-01-12 => 13 of 65 - DMConfigUpdate - SUCCESS
10-10-2015:01-01-13 => 14 of 65 - DocumentsUI - SUCCESS
10-10-2015:01-01-14 => 15 of 65 - DownloadProviderUi - SUCCESS
10-10-2015:01-01-21 => 16 of 65 - Drive - SUCCESS
10-10-2015:01-01-32 => 17 of 65 - EditorsDocs - SUCCESS
10-10-2015:01-01-48 => 18 of 65 - EditorsSheets - SUCCESS
10-10-2015:01-02-01 => 19 of 65 - EditorsSlides - SUCCESS
10-10-2015:01-02-02 => 20 of 65 - FaceLock - SUCCESS
10-10-2015:01-02-08 => 21 of 65 - FitnessPrebuilt - SUCCESS
10-10-2015:01-02-15 => 22 of 65 - GoogleCamera - SUCCESS
10-10-2015:01-02-16 => 23 of 65 - GoogleContactsSyncAdapter - SUCCESS
10-10-2015:01-02-17 => 24 of 65 - GoogleEars - SUCCESS
10-10-2015:01-02-19 => 25 of 65 - GoogleHindiIME - SUCCESS
10-10-2015:01-02-20 => 26 of 65 - GoogleHome - SUCCESS
10-10-2015:01-02-23 => 27 of 65 - GoogleJapaneseInput - SUCCESS
10-10-2015:01-02-26 => 28 of 65 - GooglePinyinIME - SUCCESS
10-10-2015:01-02-32 => 29 of 65 - GoogleTTS - SUCCESS
10-10-2015:01-02-39 => 30 of 65 - Hangouts - SUCCESS
10-10-2015:01-02-40 => 31 of 65 - HiddenMenu - SUCCESS
10-10-2015:01-02-41 => 32 of 65 - HTMLViewer - SUCCESS
10-10-2015:01-02-42 => 33 of 65 - ims - SUCCESS
10-10-2015:01-02-42 => 34 of 65 - KeyChain - SUCCESS
10-10-2015:01-02-45 => 35 of 65 - KoreanIME - SUCCESS
10-10-2015:01-02-47 => 36 of 65 - LatinImeGoogle - SUCCESS
10-10-2015:01-02-48 => 37 of 65 - LiveWallpapersPicker - SUCCESS
10-10-2015:01-03-01 => 38 of 65 - Maps - SUCCESS
10-10-2015:01-03-11 => 39 of 65 - Music2 - SUCCESS
10-10-2015:01-03-23 => 40 of 65 - Newsstand - SUCCESS
10-10-2015:01-03-24 => 41 of 65 - NfcNci - SUCCESS
10-10-2015:01-03-25 => 42 of 65 - PacProcessor - SUCCESS
10-10-2015:01-03-25 => 43 of 65 - PartnerBookmarksProvider - SUCCESS
10-10-2015:01-03-34 => 44 of 65 - Photos - SUCCESS
10-10-2015:01-03-35 => 45 of 65 - PlayAutoInstallConfig - SUCCESS
10-10-2015:01-03-44 => 46 of 65 - PlayGames - SUCCESS
10-10-2015:01-03-46 => 47 of 65 - PlusOne - SUCCESS
10-10-2015:01-03-53 => 48 of 65 - PrebuiltBugle - SUCCESS
10-10-2015:01-03-56 => 49 of 65 - PrebuiltDeskClockGoogle - SUCCESS
10-10-2015:01-04-00 => 50 of 65 - PrebuiltExchange3Google - SUCCESS
10-10-2015:01-04-06 => 51 of 65 - PrebuiltGmail - SUCCESS
10-10-2015:01-04-13 => 52 of 65 - PrebuiltKeep - SUCCESS
10-10-2015:01-04-17 => 53 of 65 - PrebuiltNewsWeather - SUCCESS
10-10-2015:01-04-18 => 54 of 65 - PrintSpooler - SUCCESS
10-10-2015:01-04-19 => 55 of 65 - ShamuLayout - SUCCESS
10-10-2015:01-04-20 => 56 of 65 - Stk - SUCCESS
10-10-2015:01-04-22 => 57 of 65 - talkback - SUCCESS
10-10-2015:01-04-23 => 58 of 65 - TimeService - SUCCESS
10-10-2015:01-04-27 => 59 of 65 - Tycho - SUCCESS
10-10-2015:01-04-28 => 60 of 65 - UserDictionaryProvider - SUCCESS
10-10-2015:01-04-35 => 61 of 65 - Videos - SUCCESS
10-10-2015:01-04-35 => 62 of 65 - VZWAPNLib - SUCCESS
10-10-2015:01-04-43 => 63 of 65 - Wallet - SUCCESS
10-10-2015:01-04-45 => 64 of 65 - WebViewGoogle - SUCCESS
10-10-2015:01-04-56 => 65 of 65 - YouTube - SUCCESS
10-10-2015:01-04-56 => Odexed Private Apps Count: 58
10-10-2015:01-04-56 => Deodexing Private Apps
10-10-2015:01-04-56 => 1 of 58 - AndroidForWork - SUCCESS
10-10-2015:01-04-57 => 2 of 58 - AppDirectedSMSProxy - SUCCESS
10-10-2015:01-04-57 => 3 of 58 - BackupRestoreConfirmation - SUCCESS
10-10-2015:01-04-58 => 4 of 58 - BuaContactAdapter - SUCCESS
10-10-2015:01-04-59 => 5 of 58 - CalendarProvider - SUCCESS
10-10-2015:01-05-00 => 6 of 58 - CallLogBackup - SUCCESS
10-10-2015:01-05-00 => 7 of 58 - CarrierConfig - SUCCESS
10-10-2015:01-05-01 => 8 of 58 - CellBroadcastReceiver - SUCCESS
10-10-2015:01-05-02 => 9 of 58 - CNEService - SUCCESS
10-10-2015:01-05-06 => 10 of 58 - ConfigUpdater - SUCCESS
10-10-2015:01-05-06 => 11 of 58 - ConnMO - SUCCESS
10-10-2015:01-05-08 => 12 of 58 - ContactsProvider - SUCCESS
10-10-2015:01-05-10 => 13 of 58 - CQATest - SUCCESS
10-10-2015:01-05-11 => 14 of 58 - DCMO - SUCCESS
10-10-2015:01-05-11 => 15 of 58 - DefaultContainerService - SUCCESS
10-10-2015:01-05-12 => 16 of 58 - DiagMon - SUCCESS
10-10-2015:01-05-13 => 17 of 58 - DMService - SUCCESS
10-10-2015:01-05-14 => 18 of 58 - DownloadProvider - SUCCESS
10-10-2015:01-05-15 => 19 of 58 - Entitlement - SUCCESS
10-10-2015:01-05-15 => 20 of 58 - ExternalStorageProvider - SUCCESS
10-10-2015:01-05-16 => 21 of 58 - FusedLocation - SUCCESS
10-10-2015:01-05-18 => 22 of 58 - GCS - SUCCESS
10-10-2015:01-05-19 => 23 of 58 - GoogleBackupTransport - SUCCESS
10-10-2015:01-05-23 => 24 of 58 - GoogleContacts - SUCCESS
10-10-2015:01-05-27 => 25 of 58 - GoogleDialer - SUCCESS
10-10-2015:01-05-28 => 26 of 58 - GoogleFeedback - SUCCESS
10-10-2015:01-05-31 => 27 of 58 - GoogleLoginService - SUCCESS
10-10-2015:01-05-32 => 28 of 58 - GoogleOneTimeInitializer - SUCCESS
10-10-2015:01-05-34 => 29 of 58 - GooglePackageInstaller - SUCCESS
10-10-2015:01-05-36 => 30 of 58 - GooglePartnerSetup - SUCCESS
10-10-2015:01-05-36 => 31 of 58 - InputDevices - SUCCESS
10-10-2015:01-05-36 => 32 of 58 - Launcher2 - FAILED - Copy Error
10-10-2015:01-05-36 => 33 of 58 - LifetimeData - SUCCESS
10-10-2015:01-05-37 => 34 of 58 - ManagedProvisioning - SUCCESS
10-10-2015:01-05-38 => 35 of 58 - MediaProvider - SUCCESS
10-10-2015:01-05-39 => 36 of 58 - MmsService - SUCCESS
10-10-2015:01-05-39 => 37 of 58 - MusicFX - SUCCESS
10-10-2015:01-05-47 => 38 of 58 - Phonesky - SUCCESS
10-10-2015:01-06-04 => 39 of 58 - PrebuiltGmsCore - SUCCESS
10-10-2015:01-06-04 => 40 of 58 - ProxyHandler - SUCCESS
10-10-2015:01-06-07 => 41 of 58 - Settings - SUCCESS
10-10-2015:01-06-08 => 42 of 58 - SettingsProvider - SUCCESS
10-10-2015:01-06-11 => 43 of 58 - SetupWizard - SUCCESS
10-10-2015:01-06-11 => 44 of 58 - SharedStorageBackup - SUCCESS
10-10-2015:01-06-12 => 45 of 58 - Shell - SUCCESS
10-10-2015:01-06-13 => 46 of 58 - SprintDM - SUCCESS
10-10-2015:01-06-13 => 47 of 58 - StatementService - SUCCESS
10-10-2015:01-06-16 => 48 of 58 - SystemUI - SUCCESS
10-10-2015:01-06-17 => 49 of 58 - TagGoogle - SUCCESS
10-10-2015:01-06-18 => 50 of 58 - Telecom - SUCCESS
10-10-2015:01-06-19 => 51 of 58 - TelephonyProvider - SUCCESS
10-10-2015:01-06-21 => 52 of 58 - TeleService - SUCCESS
10-10-2015:01-06-22 => 53 of 58 - TriggerEnroll - SUCCESS
10-10-2015:01-06-23 => 54 of 58 - TriggerTrainingService - SUCCESS
10-10-2015:01-06-31 => 55 of 58 - Velvet - SUCCESS
10-10-2015:01-06-31 => 56 of 58 - VpnDialogs - SUCCESS
10-10-2015:01-06-32 => 57 of 58 - VZWAPNService - SUCCESS
10-10-2015:01-06-32 => 58 of 58 - WallpaperCropper - SUCCESS
10-10-2015:01-06-32 => Odexed Boot Framework Apps Count: 11
10-10-2015:01-06-32 => Deodexing Boot Framework Apps
10-10-2015:01-06-33 => 1 of 11 - apache-xml - SUCCESS
10-10-2015:01-06-33 => 2 of 11 - bouncycastle - SUCCESS
10-10-2015:01-06-33 => 3 of 11 - conscrypt - SUCCESS
10-10-2015:01-06-33 => 4 of 11 - core-junit - SUCCESS
10-10-2015:01-06-33 => 5 of 11 - core-libart - SUCCESS
10-10-2015:01-06-34 => 6 of 11 - ext - SUCCESS
10-10-2015:01-06-35 => 7 of 11 - framework - SUCCESS
10-10-2015:01-06-35 => 8 of 11 - ims-common - SUCCESS
10-10-2015:01-06-35 => 9 of 11 - okhttp - SUCCESS
10-10-2015:01-06-35 => 10 of 11 - org.apache.http.legacy.boot - SUCCESS
10-10-2015:01-06-35 => 11 of 11 - voip-common - SUCCESS
10-10-2015:01-06-36 => Deodexing Classes2 - SUCCESS
10-10-2015:01-06-36 => Deodexing Completed
Thanks
@jolly_roger_hook - He asked if I could deodex and because of him I decided to try - He and I are maybe going to work together and see if we can get a ROM together...Don't hold us to that. I asked if he knew how and he is looking into it. So Maybe, maybe not
@joeldroid - For his batch deodexer tool
@txuki2005 - For showing me some great tools and tricks for Android M on how to deodex / extract
bdorr1105 said:
Fully Deodexed Stock Untouched MRA58K Base for ROM Devs to use to maybe kick out some Deodexed Marshmallow ROMs to bake in some goods
General Information - Background
I took an immense amount of time doing this and trying to figure out. I am not skilled enough to develop my own ROM at this stage of the fame. I have a lot to learn I guess you could say. I am hoping the ROM developers can take this saving them an immense amount of time and put something together. They do a lot for us, so hoping maybe this can help cut down some time for them. I also am implementing 3Minit Battery Mod as well by request. You have over 1100 batteries to choose from on the fly that you can resize or change without a restart at all. Hopefully we can get these mods going!!!
Download Section - FYI NOTHING IS FLASHABLE
MRA58K_PureStock_Untouched_Fully_Deodexed - Only framework, priv-app, app
MRA58K_PureStock_Untouched_Fully_Deodexed.zip
MRA58K_PureStock_Untouched_Fully_Deodexed_Full_ROM_NOT_FLASHABLE
MRA58K_PureStock_Untouched_Fully_Deodexed_Full_ROM_NOT_FLASHABLE.zip
Deodex Log
Code:
10-10-2015:01-00-20 => Framework Folder Exists
10-10-2015:01-00-20 => boot.oat Exists
10-10-2015:01-00-20 => App Folder Exists
10-10-2015:01-00-20 => Priv-App Folder Exists
10-10-2015:01-00-20 => Deodexing Started
10-10-2015:01-00-20 => Extracting Boot.oat
10-10-2015:01-00-20 => Copying Boot.oat to Working Directory - SUCCESS
10-10-2015:01-00-35 => Boot.oat Extraction Complete
10-10-2015:01-00-35 => Odexed System Apps Count: 65
10-10-2015:01-00-35 => Deodexing System Apps
10-10-2015:01-00-36 => 1 of 65 - atfwd - SUCCESS
10-10-2015:01-00-37 => 2 of 65 - BasicDreams - SUCCESS
10-10-2015:01-00-39 => 3 of 65 - Bluetooth - SUCCESS
10-10-2015:01-00-40 => 4 of 65 - BluetoothMidiService - SUCCESS
10-10-2015:01-00-49 => 5 of 65 - Books - SUCCESS
10-10-2015:01-00-50 => 6 of 65 - CalculatorGoogle - SUCCESS
10-10-2015:01-00-57 => 7 of 65 - CalendarGooglePrebuilt - SUCCESS
10-10-2015:01-00-57 => 8 of 65 - CaptivePortalLogin - SUCCESS
10-10-2015:01-00-58 => 9 of 65 - CertInstaller - SUCCESS
10-10-2015:01-01-05 => 10 of 65 - Chrome - SUCCESS
10-10-2015:01-01-09 => 11 of 65 - CloudPrint2 - SUCCESS
10-10-2015:01-01-11 => 12 of 65 - DMAgent - SUCCESS
10-10-2015:01-01-12 => 13 of 65 - DMConfigUpdate - SUCCESS
10-10-2015:01-01-13 => 14 of 65 - DocumentsUI - SUCCESS
10-10-2015:01-01-14 => 15 of 65 - DownloadProviderUi - SUCCESS
10-10-2015:01-01-21 => 16 of 65 - Drive - SUCCESS
10-10-2015:01-01-32 => 17 of 65 - EditorsDocs - SUCCESS
10-10-2015:01-01-48 => 18 of 65 - EditorsSheets - SUCCESS
10-10-2015:01-02-01 => 19 of 65 - EditorsSlides - SUCCESS
10-10-2015:01-02-02 => 20 of 65 - FaceLock - SUCCESS
10-10-2015:01-02-08 => 21 of 65 - FitnessPrebuilt - SUCCESS
10-10-2015:01-02-15 => 22 of 65 - GoogleCamera - SUCCESS
10-10-2015:01-02-16 => 23 of 65 - GoogleContactsSyncAdapter - SUCCESS
10-10-2015:01-02-17 => 24 of 65 - GoogleEars - SUCCESS
10-10-2015:01-02-19 => 25 of 65 - GoogleHindiIME - SUCCESS
10-10-2015:01-02-20 => 26 of 65 - GoogleHome - SUCCESS
10-10-2015:01-02-23 => 27 of 65 - GoogleJapaneseInput - SUCCESS
10-10-2015:01-02-26 => 28 of 65 - GooglePinyinIME - SUCCESS
10-10-2015:01-02-32 => 29 of 65 - GoogleTTS - SUCCESS
10-10-2015:01-02-39 => 30 of 65 - Hangouts - SUCCESS
10-10-2015:01-02-40 => 31 of 65 - HiddenMenu - SUCCESS
10-10-2015:01-02-41 => 32 of 65 - HTMLViewer - SUCCESS
10-10-2015:01-02-42 => 33 of 65 - ims - SUCCESS
10-10-2015:01-02-42 => 34 of 65 - KeyChain - SUCCESS
10-10-2015:01-02-45 => 35 of 65 - KoreanIME - SUCCESS
10-10-2015:01-02-47 => 36 of 65 - LatinImeGoogle - SUCCESS
10-10-2015:01-02-48 => 37 of 65 - LiveWallpapersPicker - SUCCESS
10-10-2015:01-03-01 => 38 of 65 - Maps - SUCCESS
10-10-2015:01-03-11 => 39 of 65 - Music2 - SUCCESS
10-10-2015:01-03-23 => 40 of 65 - Newsstand - SUCCESS
10-10-2015:01-03-24 => 41 of 65 - NfcNci - SUCCESS
10-10-2015:01-03-25 => 42 of 65 - PacProcessor - SUCCESS
10-10-2015:01-03-25 => 43 of 65 - PartnerBookmarksProvider - SUCCESS
10-10-2015:01-03-34 => 44 of 65 - Photos - SUCCESS
10-10-2015:01-03-35 => 45 of 65 - PlayAutoInstallConfig - SUCCESS
10-10-2015:01-03-44 => 46 of 65 - PlayGames - SUCCESS
10-10-2015:01-03-46 => 47 of 65 - PlusOne - SUCCESS
10-10-2015:01-03-53 => 48 of 65 - PrebuiltBugle - SUCCESS
10-10-2015:01-03-56 => 49 of 65 - PrebuiltDeskClockGoogle - SUCCESS
10-10-2015:01-04-00 => 50 of 65 - PrebuiltExchange3Google - SUCCESS
10-10-2015:01-04-06 => 51 of 65 - PrebuiltGmail - SUCCESS
10-10-2015:01-04-13 => 52 of 65 - PrebuiltKeep - SUCCESS
10-10-2015:01-04-17 => 53 of 65 - PrebuiltNewsWeather - SUCCESS
10-10-2015:01-04-18 => 54 of 65 - PrintSpooler - SUCCESS
10-10-2015:01-04-19 => 55 of 65 - ShamuLayout - SUCCESS
10-10-2015:01-04-20 => 56 of 65 - Stk - SUCCESS
10-10-2015:01-04-22 => 57 of 65 - talkback - SUCCESS
10-10-2015:01-04-23 => 58 of 65 - TimeService - SUCCESS
10-10-2015:01-04-27 => 59 of 65 - Tycho - SUCCESS
10-10-2015:01-04-28 => 60 of 65 - UserDictionaryProvider - SUCCESS
10-10-2015:01-04-35 => 61 of 65 - Videos - SUCCESS
10-10-2015:01-04-35 => 62 of 65 - VZWAPNLib - SUCCESS
10-10-2015:01-04-43 => 63 of 65 - Wallet - SUCCESS
10-10-2015:01-04-45 => 64 of 65 - WebViewGoogle - SUCCESS
10-10-2015:01-04-56 => 65 of 65 - YouTube - SUCCESS
10-10-2015:01-04-56 => Odexed Private Apps Count: 58
10-10-2015:01-04-56 => Deodexing Private Apps
10-10-2015:01-04-56 => 1 of 58 - AndroidForWork - SUCCESS
10-10-2015:01-04-57 => 2 of 58 - AppDirectedSMSProxy - SUCCESS
10-10-2015:01-04-57 => 3 of 58 - BackupRestoreConfirmation - SUCCESS
10-10-2015:01-04-58 => 4 of 58 - BuaContactAdapter - SUCCESS
10-10-2015:01-04-59 => 5 of 58 - CalendarProvider - SUCCESS
10-10-2015:01-05-00 => 6 of 58 - CallLogBackup - SUCCESS
10-10-2015:01-05-00 => 7 of 58 - CarrierConfig - SUCCESS
10-10-2015:01-05-01 => 8 of 58 - CellBroadcastReceiver - SUCCESS
10-10-2015:01-05-02 => 9 of 58 - CNEService - SUCCESS
10-10-2015:01-05-06 => 10 of 58 - ConfigUpdater - SUCCESS
10-10-2015:01-05-06 => 11 of 58 - ConnMO - SUCCESS
10-10-2015:01-05-08 => 12 of 58 - ContactsProvider - SUCCESS
10-10-2015:01-05-10 => 13 of 58 - CQATest - SUCCESS
10-10-2015:01-05-11 => 14 of 58 - DCMO - SUCCESS
10-10-2015:01-05-11 => 15 of 58 - DefaultContainerService - SUCCESS
10-10-2015:01-05-12 => 16 of 58 - DiagMon - SUCCESS
10-10-2015:01-05-13 => 17 of 58 - DMService - SUCCESS
10-10-2015:01-05-14 => 18 of 58 - DownloadProvider - SUCCESS
10-10-2015:01-05-15 => 19 of 58 - Entitlement - SUCCESS
10-10-2015:01-05-15 => 20 of 58 - ExternalStorageProvider - SUCCESS
10-10-2015:01-05-16 => 21 of 58 - FusedLocation - SUCCESS
10-10-2015:01-05-18 => 22 of 58 - GCS - SUCCESS
10-10-2015:01-05-19 => 23 of 58 - GoogleBackupTransport - SUCCESS
10-10-2015:01-05-23 => 24 of 58 - GoogleContacts - SUCCESS
10-10-2015:01-05-27 => 25 of 58 - GoogleDialer - SUCCESS
10-10-2015:01-05-28 => 26 of 58 - GoogleFeedback - SUCCESS
10-10-2015:01-05-31 => 27 of 58 - GoogleLoginService - SUCCESS
10-10-2015:01-05-32 => 28 of 58 - GoogleOneTimeInitializer - SUCCESS
10-10-2015:01-05-34 => 29 of 58 - GooglePackageInstaller - SUCCESS
10-10-2015:01-05-36 => 30 of 58 - GooglePartnerSetup - SUCCESS
10-10-2015:01-05-36 => 31 of 58 - InputDevices - SUCCESS
10-10-2015:01-05-36 => 32 of 58 - Launcher2 - FAILED - Copy Error
10-10-2015:01-05-36 => 33 of 58 - LifetimeData - SUCCESS
10-10-2015:01-05-37 => 34 of 58 - ManagedProvisioning - SUCCESS
10-10-2015:01-05-38 => 35 of 58 - MediaProvider - SUCCESS
10-10-2015:01-05-39 => 36 of 58 - MmsService - SUCCESS
10-10-2015:01-05-39 => 37 of 58 - MusicFX - SUCCESS
10-10-2015:01-05-47 => 38 of 58 - Phonesky - SUCCESS
10-10-2015:01-06-04 => 39 of 58 - PrebuiltGmsCore - SUCCESS
10-10-2015:01-06-04 => 40 of 58 - ProxyHandler - SUCCESS
10-10-2015:01-06-07 => 41 of 58 - Settings - SUCCESS
10-10-2015:01-06-08 => 42 of 58 - SettingsProvider - SUCCESS
10-10-2015:01-06-11 => 43 of 58 - SetupWizard - SUCCESS
10-10-2015:01-06-11 => 44 of 58 - SharedStorageBackup - SUCCESS
10-10-2015:01-06-12 => 45 of 58 - Shell - SUCCESS
10-10-2015:01-06-13 => 46 of 58 - SprintDM - SUCCESS
10-10-2015:01-06-13 => 47 of 58 - StatementService - SUCCESS
10-10-2015:01-06-16 => 48 of 58 - SystemUI - SUCCESS
10-10-2015:01-06-17 => 49 of 58 - TagGoogle - SUCCESS
10-10-2015:01-06-18 => 50 of 58 - Telecom - SUCCESS
10-10-2015:01-06-19 => 51 of 58 - TelephonyProvider - SUCCESS
10-10-2015:01-06-21 => 52 of 58 - TeleService - SUCCESS
10-10-2015:01-06-22 => 53 of 58 - TriggerEnroll - SUCCESS
10-10-2015:01-06-23 => 54 of 58 - TriggerTrainingService - SUCCESS
10-10-2015:01-06-31 => 55 of 58 - Velvet - SUCCESS
10-10-2015:01-06-31 => 56 of 58 - VpnDialogs - SUCCESS
10-10-2015:01-06-32 => 57 of 58 - VZWAPNService - SUCCESS
10-10-2015:01-06-32 => 58 of 58 - WallpaperCropper - SUCCESS
10-10-2015:01-06-32 => Odexed Boot Framework Apps Count: 11
10-10-2015:01-06-32 => Deodexing Boot Framework Apps
10-10-2015:01-06-33 => 1 of 11 - apache-xml - SUCCESS
10-10-2015:01-06-33 => 2 of 11 - bouncycastle - SUCCESS
10-10-2015:01-06-33 => 3 of 11 - conscrypt - SUCCESS
10-10-2015:01-06-33 => 4 of 11 - core-junit - SUCCESS
10-10-2015:01-06-33 => 5 of 11 - core-libart - SUCCESS
10-10-2015:01-06-34 => 6 of 11 - ext - SUCCESS
10-10-2015:01-06-35 => 7 of 11 - framework - SUCCESS
10-10-2015:01-06-35 => 8 of 11 - ims-common - SUCCESS
10-10-2015:01-06-35 => 9 of 11 - okhttp - SUCCESS
10-10-2015:01-06-35 => 10 of 11 - org.apache.http.legacy.boot - SUCCESS
10-10-2015:01-06-35 => 11 of 11 - voip-common - SUCCESS
10-10-2015:01-06-36 => Deodexing Classes2 - SUCCESS
10-10-2015:01-06-36 => Deodexing Completed
Thanks
@jolly_roger_hook - He asked if I could deodex and because of him I decided to try - He and I are maybe going to work together and see if we can get a ROM together...Don't hold us to that. I asked if he knew how and he is looking into it. So Maybe, maybe not
@joeldroid - For his batch deodexer tool
@txuki2005 - For showing me some great tools and tricks for Android M on how to deodex / extract
Click to expand...
Click to collapse
I'm looking into it still I've got Linux installed now but there is a lot more to it
Sent from my Nexus 6 using Tapatalk
jolly_roger_hook said:
I'm looking into it still I've got Linux installed now but there is a lot more to it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yea I can imagine bro, I don't know the first thing about it lol
Sent from my Nexus 6 using Tapatalk
bdorr1105 said:
Yea I can imagine bro, I don't know the first thing about it lol
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
There is a guide in xda University on how to do it I'm gonna try but even if I get it done it'll be like stock nothingness lol
Sent from my Nexus 6 using Tapatalk
jolly_roger_hook said:
There is a guide in xda University on how to do it I'm gonna try but even if I get it done it'll be like stock nothingness lol
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hahah yea but then you add 3Minit..hahahahah...then you have 1 mod lol
bdorr1105 said:
Hahah yea but then you add 3Minit..hahahahah...then you have 1 mod lol
Click to expand...
Click to collapse
That's what I am basically running now. So at least this would be deodexed. I can't wait. I'll test if you need.
Make it so that layers manager is built in, and works, as that is what a lot of potential flashers will be looking for. Plus the 3Minit battery mod.
Strip out some or most of the Google apps that can be downloaded from the Playstore. Maybe a good solid kernel other than stock, for people who use multirom, that uses the kexec patch, and you have a kick butt rom.
Just thinking out loud. Lol.
"Chance Favors the Prepared"
glockman4519 said:
That's what I am basically running now. So at least this would be deodexed. I can't wait. I'll test if you need.
Make it so that layers manager is built in, and works, as that is what a lot of potential flashers will be looking for. Plus the 3Minit battery mod.
Strip out some or most of the Google apps that can be downloaded from the Playstore. Maybe a good solid kernel other than stock, for people who use multirom, that uses the kexec patch, and you have a kick butt rom.
Just thinking out loud. Lol.
"Chance Favors the Prepared"
Click to expand...
Click to collapse
Here are some ideas jolly, all are easy enough to do... Maybe throw in some center clock
Sent from my Nexus 6 using Tapatalk
Yes, now that is a good sounding rom.
"Chance Favors the Prepared"
I looked through the files a lot of them on here are not deodexed correctly.. The framework files that have same file sizes didn't deodex correctly. Trying to fix them now manually
Sent from my Nexus 6 using Tapatalk
mrjaydee82 said:
I looked through the files a lot of them on here are not deodexed correctly.. The framework files that have same file sizes didn't deodex correctly. Trying to fix them now manually
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks, appreciate it, what are you using for deodex....This was a painful process with Joel Droids, I had to manually pull the army file down 1 directory? Any info would be great, or tool that you are using
If you want to compile custom android firmware, you can get started here: https://source.android.com/source/initializing.html
You'll need a proper Linux distribution to work on (a virtual machine is good for beginners). I suggest Ubuntu for Linux newbies. All information you need on installation is here: http://ubuntu.com
You'll also need to get familiar with Git. There are many wonderful resources out there on the internet on how to use it. Also, make sure to push your work to a Git host like GitHub or BitBucket.
Hope this helps!
Best of luck,
Criggs
AOSPA
{
"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"
}
Base MRA58K
Deodex
Rooted
Busybox
init.d support
SELinux permissive
Disabled forced encryption
hC-b8-M stable kernel
https://mega.nz/#!9ptUkCyS!WfMu_KMffI1xY806rvsUm-LrTA2XwXen-jiKwBKkDZs
takes about 6 minutes to start
sorry for my English
I am downloading now to try it out. I didn't realize you guys had made it this far yet. This is great.
"Chance Favors the Prepared"
Hello everyone welcome to my little guide on how to change the mac address of the mi pad 4.
Code:
IM NOT RESPONSIBLE FOR ANYTHING YOU DO WITH YOUR DEVICE! U KNOW THE RISKS
I plan to release a app or at least binary in the next few days to speed up the process for u
Requirements:
- Root
- a hex editor
- a Mi Pad 4
MAKE A BACKUP OF THE PERSIST FOLDER BEFORE!!!
Open the Hex editor
Open the file /persist/wlan_mac.bin (obvious name xiaomi)
The layout of the file is as follows:
It contains 3 mac addresses - one primary and two for fallback(s)
The addresses are displayed in HEX - every hex digit represent two numbers of the mac address
a possible content would be:
20 a4 0f 5b 34 24 20 a4 0f 5c 34 24 20 a4 0f 5a 34 24
To change the actual address simply change like a few bytes of the first address
20 a4 0f 5b 34 24 -> 21 a2 ff 4b 24 34
and reboot the phone.
DO NOT ADD ANY DIGITS THE FILE HAS TO BE 24 BYTES BIG!!
Thats all but be careful with changing the digits not ALL possible combinations are allowed by routers!
Remember that HEX digits are: a-f and 0-9
Feel free to leave a reply or leave a thanks if i helped u.