So, after I finally managed to unbrick my phone, I am still left with the problem of the IMEIs being 111111111111111 and 222222222222222.
There are countless threads on this topic on these forums, but I could not get anything to work. Either they use tools with links which aren't available anymore or their solutions just plain don't work.
Something I tried more than others is generating an MP0B_001 file and pushing it over to /data/nvram/md/NVRAM/NVB_IMEI/ (Not entirely sure about the last folder name. I just tab-completed...)
However, using the generated file, changing owner and group to radio:radio and setting permissions to 660, I get no valid IMEI. *#06# is simply blank and the phone info screen says "Unknown".
Now, here's the best thing: Even after moving the original file and fixing ownership and permissions, it still does not restore the IMEI. I'm really not sure what is going on here.
What else can I do? I tried rooting my phone and installing mobile uncle, but that didn't seem to work at all. Engineering mode is missing CDS Information, so that is a no-go. Mtk Droid Tools I haven't found a working download yet. (It's also windows-only. No clue how well that is going to work with wine. I'm on Linux.)
I'm really at a loss. As far as I know, changing your IMEI is illegal in Germany. Using such an obviously fake one is just asking for trouble.
I finally figured it out! I had been at this for hours when I posted this thread and, of course, right after I post it, I manage to fix it. (Well, two hours after posting. In the grand scheme of things, right after.)
On https://www.leakite.com/2016/04/how-to-change-modify-of-fix-null-imei.html method #2 finally worked. However, the pttycmd1 is not in /dev directly, but in /dev/radio. I also had to reflash since /dev/radio was empty. (Probably due to various other attempts to change the IMEI, which made it disappear entirely)
If somebody stumbles upon this with the same problem, here's what you do:
- root your phone
- enable usb debugging
- enter an adb shell (alternatively, you can use a local root terminal)
- Execute:
su
echo 'AT+EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
- reboot
This is by far the easiest method I have found so far and ended up being the only one that worked. Why is this not recommended more often?
I agree, these methods should be more widely available on web forums etc. At moment I have tried IMEI changer but the trouble is on a dual sim phone, it seems to change both IMEIs to the same number! So far from ideal.
Just curious on method above, does one not actually put in the "" marks and just enters the actual two IMEIs?
---------- Post added at 11:32 AM ---------- Previous post was at 11:20 AM ----------
I agree, these methods should be more widely available on web forums etc. At moment I have tried IMEI changer but the trouble is on a dual sim phone, it seems to change both IMEIs to the same number! So far from ideal.
Just curious on method above, does one not actually put in the "" marks and just enters the actual two IMEIs?
Very useful I have a umi plus and I have to do A complete reset (download only) losing IMEI now I have the solution ... thank you so much
Xandaros said:
I finally figured it out! I had been at this for hours when I posted this thread and, of course, right after I post it, I manage to fix it. (Well, two hours after posting. In the grand scheme of things, right after.)
On https://www.leakite.com/2016/04/how-to-change-modify-of-fix-null-imei.html method #2 finally worked. However, the pttycmd1 is not in /dev directly, but in /dev/radio. I also had to reflash since /dev/radio was empty. (Probably due to various other attempts to change the IMEI, which made it disappear entirely)
If somebody stumbles upon this with the same problem, here's what you do:
- root your phone
- enable usb debugging
- enter an adb shell (alternatively, you can use a local root terminal)
- Execute:
su
echo 'AT+EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
- reboot
This is by far the easiest method I have found so far and ended up being the only one that worked. Why is this not recommended more often?
Click to expand...
Click to collapse
I completely agree, this is the easiest method and it just works, no software needed (if made via terminal software on the phone itself). But the commands you posted are slightly wrong. there should be a space between the AT+ and the EGMR:
Code:
su
echo 'AT+ EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+ EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
uuzi said:
I completely agree, this is the easiest method and it just works, no software needed (if made via terminal software on the phone itself). But the commands you posted are slightly wrong. there should be a space between the AT+ and the EGMR:
Code:
su
echo 'AT+ EGMR=1,7,"IMEI1"' >/dev/radio/pttycmd1
echo 'AT+ EGMR=1,10,"IMEI2"' >/dev/radio/pttycmd1
Click to expand...
Click to collapse
Good night, I did the twrp and I think I deleted some files from the DEV folder, because my IMEI does not appear anymore. I'm with the TWRP and rooted device. Some tip to reset my IMEI. My handset is a power 3 ulefone
Thank you!
I lost IMEI after flashing stock ROM on my Elephone S8 and there was no option to set in Engineering Mode.
100% the easiest way to fix
I have a Acer Liquid E700 E39 that has /dev/radio empty too.
This happened after i flashed a stock rom.
What can i do?
Thanks in advance.
Great share for restoring IMEI, thank you!
Related
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Hello.
I am sending this pm regarding the translation for flashing the Fujitsu f-05d sold by Docomo in Japan. I cannot reply in the development section due to my low post count.
My phone is an f-05d. I do not have a t-01d but, according to the original rooting guide for the f-05d, the users are reporting success in rooting the t-01d as well.
I will not really translate for you. Rather, I will explain what I did to root my f-05d.
Here is a rough summary of the steps I followed:
For starters, you need to make sure that adb recognizes your phone when connected to the PC via USB. This means that you need to install the Android SDK and the USB driver for your t-01d by Fujitsu.
I had trouble getting adb to recognize my phone, as Window$ insisted in recognizing it as an USB drive. What I did, among other things, was:
In the phone settings, go to Applications > Development and check USB Debigging and Stay awake.
Install the Google USB Driver package, in the extras section of the Android SDK Manager.
With the phone connected to the PC, go to Window$ device manager > Universal Serial Bus Controllers and uninstall (use the delete key from your the keyboard) every mass storage device that appeared when my phone was connected. Disconnect and reconnect the usb cable.
Only until I did this final step was my phone recognized and listed as Android Phone > Android Composite ADB Interface in the device manager. If your device is not recognized, you just cannot continue. Look for help about this, or else you cannot move on with this method of rooting.
Confirm that your phone is recognized as Android Phone > Android Composite ADB Interface in the Window$ device manager. Do not continue until it is.
From the Android SDK manager, install the package android sdk platform-tools.
You need download F05Droot.zip from the original blog page your linked before. I will not link to the file directly, but you should have no problem finding it. Extract the files within into the program directory \Android\android-sdk\platform-tools (this is my path).
You need to download a replacement for the file lsm_disabler.ko that is inside the F05Droot.zip. Get it from here and extract it an replace the one inside the platform-tools directory.
By the way, this platform-tools directory is the one that has the adb executable file. Just a heads up.
You need to download su. I cannot tell you where to get it. I just do not know where I got mine from, but was easy so go for it When you have it, extract it and put it in the platform-tools directory.
Confirm that the platform-tools directory includes these files:
Code:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
su
lsm_disabler.ko
f05dsu.bat
There will be more, but these are the ones needed for this to work.
Now, get ready to root. Connect your phone to the PC.
Go to your phone settings > setting my body > step/activity counter app > pedometer use and confirm it is checked on.
In the platform-tools directory, look for f05dsu.bat and run it. A DOS window will open. This is the funny part. Unless you are doing this from a Japanese version of Window$, or from a Window$ with Japanese locale active, you will see a lot of strange symbols instead of Japanese characters... which would be the same for almost anyone anyway Regardless, you will see a prompt to Press any key to continue . . .. At this point, you do not need to do anything on your phone, other than visually checking that the check mark on the pedometer is set.
On the DOS window press any key, your will see more garbage and another prompt to press any key. This is the important part. See if you can find among all those symbols this pattern: OFF/ON. If you do see it, it means we are on track.
Now that you were able to see the OFF/ON, go to your phone and uncheck the pedometer (OFF) and check it again (ON).
In the DOS window, press any key. Your phone will reboot. The message in the DOS window says that you must wait for the phone to boot up and for Window$ to recognize your usb connection to the phone.
When/if your phone is recognized by Window$, go to the DOS window and press any key.
Again, press any key and your phone will reboot.
The DOS window has a message indicating that you must now install superuser and busybox. When your phone reboots, go to the android market and install from there when you have the time.
You can now close the DOS window because, unless there was any error, you are now rooted, my friend
From the market, install a terminal, or an app that includes a terminal. I use Rom Toolbox because it has a terminal and scripts to mount the /system as rw.
Open whatever terminal you chose and, at the $ prompt type su
If new prompt is #, type soff
You will need to run these commands every time before trying to mount /system as rw.
That is all. I hope you can root your phone.
Just a petition, post this message in the forums, as it may help others who have similar difficulties. It sure could have helped me if someone had done before me.
Have a nice one and please forgive my English.
Click to expand...
Click to collapse
update 15/4
On 13/4 finally i got my phone rooted
I have to run f05droot.bat instead of f05dsu.bat
After I have run the f05dsu.bat, for the steps, no error popout.
then I open the terminal type su, it reply me "permission denied".
I know it is not successful, after several run, the situation still the same.
after that have checked the contents of f05droot.bat and f05dsu.bat.
They are very similar but the f05droot.bat will push the superuser and busybox into the device at the same time.
(so I added those files in the directory \Android\android-sdk\platform-tools )
Therefore, i tried that and its works finally.
I feel really exciting at that moment.
I hope this post can help they T-01d user to root the phone.
personally I really like this phone ^~^
the su file is also important
Anyone try it? Does it work?
I have got the source code from its web
But I dont know how to use that and lead me to root the machine
ttp://spf.fmworld.net/oss/t-01d/data/download.html
Can you post a review of this device?
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Click to expand...
Click to collapse
If you have time, can you please post a mini review of the device? I wanted to buy one too and I'm quite excited reading your review!
Thanks and more power!
Here is the mini review
Screen color is perfect except black and accurate. Speed is good in comparing with SGS2. Battery life is similar to SGS2. Form factor is better than SGS2. Camera is outstanding, thanks to the 1.3MP camera. Waterproofing design is what I like. The bad is upgrading is only possible in Japan. Digital TV is useless. Sound level is a bit low.
personally i like this phone very much especially the outlook.
my personal review is the following:
1. same as above the screen is perfect
2. the camera is also excellent
3. while you have a phone call, it change mode automatically depends on the environment
4. if i switch off all the data things, this phone can stand more than one day
(so i wont blame the battery, because I think we use too many network related stuffs)
5. i have to admit that the firmware is not quite stable (fortunately the phone can be upgrade to 4.0 after july)
for the rooting process, it seems like someone has success:
(i think that is temp root)
search "T-01D 軟解, tofu-keitai" in google (that is chinese unfortunately)
redcarrot said:
Greeting,
It was heard that rooting T-01D are similar as F-05D.
I found a website regarding rooting F-05D, but I dont read Japanese, just want to know if anyone have tried the enclosed method to root T-01D?
or could anybody do the translation, since the terms become quite strange after using the online translators
The following link is ref. of rooting F-05D:
ttp://ayati.cocolog-nifty.com/blog/2012/01/f-05droot-1d0b.html
(should be "http" rather than "ttp")
The source code of T-01D have been provided also, but I have no idea how to use it and root the machine:
ttp://spf.fmworld.net/oss/t-01d/data/download.html
(should be "http" rather than "ttp")
Thank you very much in advance?
Update of 4/4
the following t-01d rooting procedures is provided by Magimaster
Click to expand...
Click to collapse
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
hi HaoyuWen,
i have followed the steps, when i type su in the terminal simulator, it comes out segmentation fault su, do you have any idea.
I use titanium backup to check and it said my t-01d is not rooted.
for the pedometer on/off things, do i need to press the home key and go back to the pedometer to do the switch?
Thank you very much in advance
HaoyuWen said:
It really work!~
I rooted my T-01D with this method!
And it's permanent root!!
Many thanks!~
Click to expand...
Click to collapse
So both F-05D and T-01D can use this ?
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
finally i got my phone rooted
you have to run f05droot.bat instead of f05dsu.bat
the su file is also important
redcarrot said:
yes, but i havnt got that work yet.
just want to know when I get the device rooted, will the device screen shows the device is rooted?
Click to expand...
Click to collapse
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
wth_is_life said:
You can install a root checker to see
^ Please update it on the front page
Gonna get mine soon, so excited to hear this
Click to expand...
Click to collapse
I think I brick my T-01D. Don' know why, I do exactly the same what I have been told here... Now It ends up infinite boot loop
Anybody help me please?
Hey there everyone, sadly this guide isn't working for me. Everything in the guide goes smoothly and I do exactly what is listed but after my phone reboots the final time I still have no root access. I run f05droot.bat instead of f05dsu.bat like the user said but to no avail, I even ran f05dsu.bat and still nothing.
Anyone else have trouble? Maybe it is because I am on a certain FW? I am on 2.3.5
Baseband Version C_L1_M23
Kernel version: 2.6.35.7 [email protected] #1
and Build number is V43R41C
Just wondering as I really want root to disable all of these RAM-hogging default applications.
Bump? Anyone?
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
kinchung said:
As far as I know, this rooting method cannot be done on FW V43R41C.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
Aw Thanks for the notice, of course it's my firmware. Any idea about ICS? It was supposed to come out in July but yeah..
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
kinchung said:
I don't know about ICS for t-01d. My sc-01d has been already upgraded to ICS, the performance is improved a lot. sh-01d also gets ICS today.
Sent from my SC-01D using Tapatalk 2
Click to expand...
Click to collapse
I see, I read about the T-01D (among many others) getting updated from articles like this: http://forums.hardwarezone.com.sg/e.../docomo-update-ics-4-0-18-models-3662812.html
I'm sure the T-01D would perform pretty awesome and maybe pre-installed software would not be as big a deal as it is now. Maybe since your SH-01D is getting updated, T-01D isn't far behind. The only thing I have to see is if I can update out of Japan.
I don't have sh-01d but galaxy tab 10.1 sc-01d instead. My t-01d also upgraded to V43R41C last month during visiting Japan. Upgrade of t-01d may not be possible outside Japan as Software Update cannot be executed without docomo sim and network.
Sent from my SC-01D using Tapatalk 2
I live in Japan and after more than 6 months I have successfully and permanently rooted both my Sharp 003 SH Galapagos and the 005SH Galapagos (Softbank not Docomo). My next concern is how to SIM unlock. I have been reading the posts about hacking the nv_bin file. I have searched through all of the the files (Root FTP thank you!) but there was no such file. I am happy to send along any screenshots or data files if that helps.
Thanks in advance.
Search Sharp 003SH Root Success and Sharp 005SH Root success on Youtube for more info
Can't really help you. Don't know anything about it. But I would like to know how you ended up rooting this phone of ours.
Its not a file on the filesystem. The sim locking in these phones is in the radio image; which can be accessed when you use the custom build kernel thats in the latest rootkit (I assume thats what you are using).
See the 2ch root/ROM thread for more details, but basically it is done through ADB, manually backing up the "_modem" partition; stripping the spare/ECC bytes and then extracting the radio OS using QualcommDumpAnalyser
I have managed to extract this image, but no idea where to go from there. None of the other device info seems to apply to this (HTC, Samsung, LG, any other Android that has had its sim-lock discovered in the radio)
Advice i got from the guys on 2ch: "Qualcomm's NAND code is neither difficult, nor unique, so if you know what you are looking for its not hard"
003SH 005SH Sim unlock
Thanks very much for giving me a new direction. I'll get started on it right away and let you know how it progresses.
It just sucks that the guys who know how to unlock it are staying quiet, saying its "taboo"
FYI, stripping the Spare/ECC bytes can be done manually (i wrote a C program to do it), but there is an option in the RevSkills app to do it all for you - i recommend doing that.
Of course we face another issue once we find the actual unlock - recalculating the ECC bytes after making the change; the only way to access the radio is with raw data access.
P.S. hope you have warranty on your phones - this is very likely to brick at least one phone until we get it right
---------- Post added at 12:30 PM ---------- Previous post was at 12:24 PM ----------
In the spirit of open cooperation, here are the instructions i was given, translated and simplified
In ADB Shell, type su to get the # prompt, then:
cat /proc/mtd <Enter>
Confirm that you have the "_modem" partition available. If not, you need to reflash with the custom build kernel
Dump the image to file with the following command:
dump_image -r -D -F _modem /sdcard/backupimages/modem.img
Access this with anything as "raw dump" and all blocks will get read as ECC error, so definitely dont do this
ECC positioning is different to Linux, so take care
The following maps out how 512bytes of data and 10 bytes of ECC info are stored in a 528 byte block:
0000 - 01CF (0-463): Data
01D0 - 01D1 (464-465): Unused (0xff)
01D2 - 0201 (466-513): Data
0202 - 020B (514-523): ECC
020C - 020F (524-527): Unused (0xff)
Use RevSkills application to extract the data portions:
Menu⇒Calculators/Generators⇒Android MTD Nand remove Spare and ECC
Extract all of the Data only portions out of the raw dump, and then use QualcommDumpAnalyser to read it and split up the various parts. I did notice that i wasnt able to get the AMSS block out with QualcommDumpAnalyser - i copied that out manually by calculating the byte positions shown in QDA.
003SH bootloader key sequence?
Eternalardor,
I'd be happy to swap information. Perhaps you could shed some light on the question of the bootloader for the Sharp 003SH and 005SH? There seems to be no discernible key sequence (Power+home+Volume up etc.) to access the bootloader. I feel like I've tried them all. Can you tell me this critical piece of information?
Is a form of the USB Jig necessary to access it?
Looking forward to your response.
003SH SIM unlock
Dominik,
Here are the results of the original /proc/mtd (before rooting)
boot
cache
misc
recovery
ipl
system
persist
log
battlog
calllog
ldb
userdata
I don't see the _modem partition. Should I?
I have also included a screenshot of the results showing size. I have most of them backed up as .img files too.
FYI: .img backed up sizes. Perhaps this will help you to ponder where the _modem partition may have gone. Maybe it's been renamed?
boot 11,264KB
cache 3,072KB
misc 1,024KB
recovery 11,264KB
ipl 15,360KB
system 419,840KB
persist 30,720KB
ldb 45,056KB
userdata 405,120KB
There is no bootloader menu AFAIK. If you install the custom kernel, you will have the option of a quasi-recovery mode, by pressing the home button between 7-12 seconds after the Galapagos logo is seen (or was that the Softbank logo)
Anyway, looking at the screenshots, it seems you do not have the custom kernel.
How did you achieve root on your phone?
To do this, you need to use the "003sh_005sh_dm009sh-rootkit" from at least 5/27 (recommend _0614); which is available on the 2ch forums. This includes 2 possible ways of achieving root:
1. A modified standard kernel (boot image), which, when flashed gives you regular root access
2. A custom compiled kernel, which has full root, a bunch of power profiles, and heaps more features (inc that quasi recovery), as well as access to the "_modem" image.
Judging from your youtube videos, you speak some Japanese, so the Japanese menus in the rootkit shouldnt be much trouble.
http://www1.axfc.net/uploader/Si/so/142435
This is what i used.
Go here for help/instructions http://anago.2ch.net/test/read.cgi/android/1337845757/
And dont even think about typing in English on there, or you will be ignored and/or told to go away
This all looks familiar. I have been using the root kit (5/27) to get where I am now - step by blessed step. It was pretty straight forward BUT I have never seen the option to write to the system partition. It is in all the instructions but the only option I have with respect to the system partition is to back it up. I'm confused as to why it doesn't seem to show up for me. I am using a Japanese machine so all the characters are displayed and I can read the instructions but I can't find help anywhere as to why I don't have that particular (and critical) option. I can see a lot of new and cool options in the 6/14 release. I'm excited and would like to get it installed.
I'll let you know how it goes. Thanks for your help .... keep it coming!
And another thing
Could you explain a little more about "having" the custom kernel? Using the root kit, I wrote to the Recovery partition then the Boot partition then rebooted from the Recovery partition and all seemed well. As I said above, I have never been able to write to the System partition despite it appearing in all the instructions. I suspect that is what is holding me back from the latest and greatest custom kernel. Still, I am enjoying all the same functionality that everyone else seems to be enjoying in root. What am I missing?
Eep, you wrote to the boot partition before trying the recovery? Brave!
The steps should be:
Write image to recovery partition;
Then reboot to recovery partition (from the menu) and confirm it all works without errors.
Then write image to boot partition
And then turn off the phone, and reboot (the last part is only my instructions - you could just select "reboot to boot partition" from the menu)
You are doing this on your 005SH right? It should be the same for the 003SH, but i only have the 005SH. In the rootkit there is 2 options when you say "burn custom image":
1 カスタムビルドrootedカーネル（リカバリーキット機能付き）
2 S4080 標準rootedカーネル（簡易リカバリー機能付き）
Q 中止してメインメニューへ戻る
You must do the first one, the CUSTOM rooted kernel, to get any of the really cool features. The second option is only if you just want root access for a particular app or something. AFAIK the second option doesnt even disable MIYABI LSM, which prevents you from mounting the system dir as R/W
But either way, writing to the System dir is not important for what we are doing. You need the Custom kernel, which gives you access to the "_modem"
Edit, i just noticed in your screenshots above, you didnt even get root in ADB shell?
Type
ADB Shell<Enter>
Then type
su<enter>
The cursor should change to a #, this means root. You may get a prompt on the phone from Superuser asking you to give root access to "shell". Once you have this try the cat /proc/mtd again
jcroot003sh,
can you tell me how to root 003sh?
Use the link i provided in my previous post
http://forum.xda-developers.com/showpost.php?p=27989085&postcount=8
You can use a translator if you dont understand Japanese, but the general instructions are in the post above yours
I translated it for a friend, but that is at work, so wont be able to put it up until monday.
DominikB said:
Use the link i provided in my previous post
http://forum.xda-developers.com/showpost.php?p=27989085&postcount=8
You can use a translator if you dont understand Japanese, but the general instructions are in the post above yours
I translated it for a friend, but that is at work, so wont be able to put it up until monday.
Click to expand...
Click to collapse
Thank you for your replying. I will wait for your translated version. You are really a good person.
Progress
I have successfully found and dumped the "_modem" image. Exactly as you stated - forgot the "su" command in ADB. Thanks. The next problem is editing out the code. I am way above my head here so I will do some research before bugging you for a step-by-step for that.
Also, the bootloader worked. I didn't realize how to do it until I read the notes in the 6/14 release. I successfully put a previously dead phone back on it's feet EXACTLY to the point of my current phone simply by backing up and then restoring partitions through the bootloader. Very slick and easy.
Will get to work. I'll be in contact soon with my progress on the SIM unlock.
I have spent a bit of time looking at it, it certainly isnt easy (Certainly isnt a "lock=yes" section). I assume the actual locking portion is encrypted/compressed/or just compiled, because it would be too easy otherwise (be happy to be proven wrong). For starters, i cannot even find my IMEI number in the dump file... I think that this dump only includes the radio code, not the NV RAM which contains the IMEI and SIM Lock status. If that is the case then the solution should be to change the portion of the radio code that queries the NV RAM, so that it doesnt care if the SIM lock is supposed to be applied.
Extracting the spare/ECC bits out should be done with the RevSkills app; extracting the relevant portions, that is a bit of a cludge; QualcommDumpAnalyser can show the start/end positions, but doesnt extract the AMSS part (AFAIK thats where the code will be). You need to use a hex editor to cut that part out manually... And i am still not 100% sure what the block size is on this NAND.
Good luck!
And if there *are* any experienced hackers out there willing to help out, i can offer some monetary help (as will a few of my fellow Japanese smartphone owning friends) as this will be valuable for not just these 2 phones (there is an army of 007SH owners waiting on this unlock)
Shall we give the 007/009 a shot?
I can see mountains of the 007SH on the auction (mostly pink). Perhaps I should pick one up and take it for a spin. I am happy to try to do something to help out for all the help I am receiving.
Or perhaps the 009SH?
How hard would it be to crack the 007? The 009SH looks like it is supported in the latest release kit.
Thoughts?
Currently, the 003/005SH are going to be the easiest, because they have the custom kernel which allows access to the "_modem" image. To do it on the 007SH we need to build a custom kernel (compiled from the sources available on the ktai-dev site), and add the modem access code (this is in the src directory of the rootkit). Not impossible, but i dont have a Linux machine to compile the sources.
However i think that the code will be fairly universal. Once we find it on the 005SH we will know what we are looking for on the 007SH as well. That will make many people happy
Anyway, my 005SH is under warranty/anshin plan so i dont mind if it gets bricked (especially now that we can take nand backups).
First things first though - examining the 005SH modem image. Does anyone know whether the NAND is a 16kb or 128kb block size? Or is it something completely different?
P.S. The DM009SH is just the Disney Mobile version of the 003SH
Linux machine no problem
I have a Linux server running 24/7 so compiling the kernel is easy. Don't let that be the holdup. I'll keep working on the 003SH _modem image.
DominikB,
I can't open this site [anago.2ch.net/test/read.cgi/smartphone/1319287551/] on channel2 for free. This site had been moved to the past-log storehouse. So.... I even can't look at Japanese version for rooting 003sh. It is very helpful if you can show me the steps for rooting 003sh.
I realize this is a pretty new phone and since it is a lower end device it is probably not a priority for developers, but just wanted to ask.
Does anyone know if there is a way to root this phone?
I just can't find a way to root this phone LG K3, I'm trying to ADB sideload TWRP but I get the failed verification signature + no fastboot available..... Could someone explain please?
Just to update I have tried KingRoot, both the mobile and PC versions, and it did not work.
LG K3 Root
Any further developments with this? Has anyone tried TowelRoot or any of the other methods listed here: http://www.xda-developers.com/root/
Thanks in advance...
I have tried kingo and a few others and they all have failed pretty badly...
I have searched for TWRP but cannot find a version for the k3... its like it doesn't exist..
Anyone found any news?
wolfxwinds said:
I have tried kingo and a few others and they all have failed pretty badly...
I have searched for TWRP but cannot find a version for the k3... its like it doesn't exist..
Anyone found any news?
Click to expand...
Click to collapse
I haven't found anything to date. Google searches lead to dead ends, and there is nothing here or in the Android Central forums. I am encouraged by the fact that a few more people have expressed interest in rooting the K3. In my - admittedly brief - experience with rooting, it seems like the path forward is simply to hope that a tech-oriented person, developer or otherwise, will buy a K3 and take the time to fool around with it.
To anyone who has searched for a method to root the LG K3 and ended up here, please take the time to create a username and post on this forum. Perhaps if more people show interest, it will lead to something...
want root
unclevername said:
I haven't found anything to date. Google searches lead to dead ends, and there is nothing here or in the Android Central forums. I am encouraged by the fact that a few more people have expressed interest in rooting the K3. In my - admittedly brief - experience with rooting, it seems like the path forward is simply to hope that a tech-oriented person, developer or otherwise, will buy a K3 and take the time to fool around with it.
To anyone who has searched for a method to root the LG K3 and ended up here, please take the time to create a username and post on this forum. Perhaps if more people show interest, it will lead to something...
Click to expand...
Click to collapse
Really want root. There is too much bloatware on this device and I would love to get the integrate sd card as internal working. LG disabled it on all their devices sadly. If there is anyone out there who would be willing to help, we would be ever so grateful! Thanks!
I have a spare one with a shattered but working (Thanks to the skinomi on it!) screen I'd be willing to offer up for analysis. I'm trying to root for much the same reasons...bloatware being prime. More than half the internal memory is taken up by system apps and their updates! It wouldn't be so bad if all the amazon crap was moveable, but being system apps, are not...but who the hell puts trial ware on as a system app? It means that I can have only two or three user apps, even with most of their data moved to the sd card, before running into space issues when installing updates.
meowwl said:
I have a spare one with a shattered but working (Thanks to the skinomi on it!) screen I'd be willing to offer up for analysis. I'm trying to root for much the same reasons...bloatware being prime. More than half the internal memory is taken up by system apps and their updates! It wouldn't be so bad if all the amazon crap was moveable, but being system apps, are not...but who the hell puts trial ware on as a system app? It means that I can have only two or three user apps, even with most of their data moved to the sd card, before running into space issues when installing updates.
Click to expand...
Click to collapse
It's a pretty crappy phone as is...way too much boatware, not always responsive, and the battery runs out quickly. Needs root!
---------- Post added at 06:35 PM ---------- Previous post was at 06:28 PM ----------
There is another thread about the K3 here: http://forum.xda-developers.com/general/help/to-root-lg-k3-t3479758
Some of us are offering donations to anyone who can root it and post the instructions.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
Nothing yet huh
tgkobaljr said:
Nothing yet huh
Click to expand...
Click to collapse
Look over here.
It's more active, at least.
Anything yet
How hard is it to find a root for this overly bloated phone? This cheapy phone can't be that hard for some techy to crack.
KingRoot, Z4Root, FramaRoot, TowelRoot omfg NONE of them work. I wasted my time. Please don't waste yours.
Adoptable Storage with LG K3 (K100)
ironsa said:
Really want root. There is too much bloatware on this device and I would love to get the integrate sd card as internal working. LG disabled it on all their devices sadly. If there is anyone out there who would be willing to help, we would be ever so grateful! Thanks!
Click to expand...
Click to collapse
There is a way to enable adoptable storage, I did it & now have my K3 working with an extra 32gb card mounted as adoptable. I found these instructions somewhere online but can't remember the link. Here they are though, thanks to whoever posted them. Note that you will get an error if you get the disk name wrong but I found mine after a couple of attempts (it's mentioned in the instructions below). This also worked for my K8 with a 64gb sd card.
Give it a go.
""""Notes: remember to use PTP rather than MTP option when connecting phone to laptop. If no device shown in ADB, use LG laptop software suite
When ADB is downloaded choose “Run as Administrator”.
Press Y to “install ADB and Fastboot”, Y all users and Y to install the necessary drivers.
Then allow it to install the Google device driver.
OPEN COMMAND PROMPT on your PC
Navigate to SDK Folder ((C:\adb )) and open Command Prompt
(Shift + Right-click anywhere in the folder > Open Command Prompt Here).
Type this command and hit enter.
-----------------------------------------------
adb devices
-----------------------------------------------
You should now see your device listed .
Type the following commands exactly as shown, pressing the ENTER key after each one:
----------------------------------------------------------------------------------------------------------
adb shell sm list-disks
adb shell sm list-volumes all
adb shell sm set-force-adoptable true
adb shell sm partition disk:179,64 private (Note: check the disk name, mine was 179,128)
adb shell sm set-force-adoptable false
adb shell sm list-volumes all
----------------------------------------------------------------------------------------------------------
NOTE: the fourth command partitions your SD card, and may take 2-3 minutes (or longer) to complete, depending on the size of your card. plus make sure you have a reliable and fast SD Card.
Disconnect your phone from the USB cable and reboot it. The reboot is crucial. Your phone may (or may not) take a bit longer to boot this time.
Once your phone is fully booted, tap Settings > Developer Options and disable USB Debugging, clicking “OK” to any messages that may appear.
Go to Settings > Storage & USB and tap your SD card. Tap the three dots in the upper-right corner and choose “Migrate data”:
Done""""
Rooting an lg
SODA8297 said:
I just can't find a way to root this phone LG K3, I'm trying to ADB sideload TWRP but I get the failed verification signature + no fastboot available..... Could someone explain please?
Click to expand...
Click to collapse
lg phones 4.0. And upwards has some malware virus blockers alot of these mods contain phish codes to steal your contacts or passwords also account details...
I got to 90% on my kingroot then it took 9 minutes to finish then after installing i got an error message ..
The only way to bypass the warning is to find a Root recovery program like Twrp so buy some more memory....download that then you can try ......im doing all of this to remove bloat and find deleted files in the 7 days before the system empties the trash
Hi Everyone,
I have a phone, the Huawei Ascend P7 -L10.
Some weeks earlier I tried to install Spotify in my phone, but I didn't manage to install it. After several attempts I end up crocking my phone.
It happened when I found some app that had apparent solution to solve Spotify installation problem. I don't remember the name of the app. Anyway, I found it effective so I tried to follow the instructions given. I made it, then the changes were effective. What the app does is to change the phone model and respective carrier.
All the dilemmas started when I decided to restart the phone.
Here goes what I've done so far after the incident.
1. I tried by myself to restore/upgrade the system. I've experience doing this.
2. I took the phone to the 1st Repair Agency - they did not fix it
3. I took to the 2nd Repair Agency - the same thing, they fail to fix it
Note: When you try to restore the phone it gives the following information “update failed!"
and when you normally try to switch the phone on it stop on black screen and nothing else, I've also tried wipe cache, wipe data everything but nothing. Please help!!
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
es0tericcha0s said:
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
Click to expand...
Click to collapse
Thanks for your replay. My device is rooted one, but the problem is, I can't login not even connect it via cable (using e.g. HiSuite). So, how can I pick up the file from phone?
Hello guys, first of all: thank you very much for your Forum; I'm learning a lot even if I remain a complete noob!
I'm trying to use LineageOS 17.1 (lineage-17.1-20210118-UNOFFICIAL-a3y17lte, recovery OrangeFox 11.01) on Galaxy A3 2017 (SM-A320FL), and I did something really stupid trying to make Link2App work.
I had problems to format properly the miniSD using Android's apps, and I could not remove the card from the phone (the slot's opening is damaged). So then I tried to format the card using ADB + BusyBox + fdisk, BUT I did it while I was distracted by other job's issues, and I didn't realize I was working on the internal SD instead of on the removable card (yes, complete idiot...).
Result: a brand new empty partition table in my phone, permanently stuck in Download mode (impossible even to power off it).
I tried to restore the phone using this procedure, but it failed midway. By the way, I could Odin-flash TWRP and then restore the partitions using the repartion script. Eventually, I fleshed my OrangeFox and LineageOS: the system is now perfectly working, but the phone doesn't recognize any more my SIM and IMEI (dialing: *#06#) is blank.
I had a Fox's "light" backup, but it didn't solve anything.
I'm still having the original box with the IMEI number on the label, but I didn't find a suitable procedure to use it.
Kies3: the SM-A320 phone seems too old to allow the Initialization procedure described here (yes, the phone was unplugged)
There are many apps promising miracles (for instance: ToolHero, MTK Engineering Mode, IMEI Generator Pro, EFT Dongle...); however, I tried some, and they seem to me just ****ty pieces of software, requiring the original system or dubious paid services.
Dialing codes* procedure (like Method 1 here). I cannot remove SIM or battery to complete the procedure. Besides, my phone doesn't react to the code; probably they are country or SIM specific...
Line command (terminal emulator or ADB): this seems to be the most promising method; however, the line
Code:
echo 'AT +EGMR=1,7,"MY_IMEI_NUMBER"'>/dev/pttycmd1
doesn't do anything on my device
IMEI generator: I tried to generate a new MP0B_001 file using this guide. The download link is broken, then I downloaded the files from another source, and I prefer to add to my system just the MPB_001, without flashing the "repair" tool. Besides, I don't have any /nvram folder in my $root/data/ directory... (the only IMEI related folder is in $root/eps/).
Any suggestion to solve this mess? Thank you very much!
Daniele
* EDIT: after typing *#*#197328640#*#* the phone window closes.
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
jwoegerbauer said:
Look inside here:
3 METHODS to restore your IMEI number on Android
Most people face a common issue with IMEI number that is losing them. Particularly, it happens when you get a locked second-hand mobile or in Mediatek devices.
www.gizmogo.com
Click to expand...
Click to collapse
Thank you very much for your answer! The 2-3 methods seem promising; however, I isolated the problem and solved it before receiving your message.
The problem: after messing with the partitions, I tried to restore my system, downloading the files via Freja. However, I select the wrong CSC, using my SIM provider code (TIM) instead of the generic code for Italy (ITV).
I noticed it exploring the light backup I had done in TWRP (only System partition): a CSC_version.txt was there, pointing to A320FLOXA9CTK1 (ITV version, while I restored using A320FLTIM8CTH1, TIM carrier version). ITV was also mentioned in the file $ROOT/eps/imei/mps_code.dat (dunno if this is relevant)
Solution: Odin + the right firmware did the trick. I had my IMEI back and the phone working, then I came back flashing TWRP, Orangefox and, eventually, LineageOS.
Everything is working now, and, of course, I backed up EPS partition (now).
Many thanks!
daniele