Hi, anyone can help me? I have IMEI Null on my device, need a working QCN file, also with 1111111111111 parameter for IMEI, I can edit for my IMEI after.
Big thanks!
1944 said:
Hi, anyone can help me? I have IMEI Null on my device, need a working QCN file, also with 1111111111111 parameter for IMEI, I can edit for my IMEI after.
Big thanks!
Click to expand...
Click to collapse
Hello, with which program can I get this file for you from my device?
incorrect section.
go to "ASUS ZENFONE 4 (2017) QUESTIONS & ANSWERS"
henrique araujo said:
Hello, with which program can I get this file for you from my device?
Click to expand...
Click to collapse
You need root, if you already have root follow theses steps:
plug your phone to computer then turn on adb mode, when youre on adb type
Code:
adb shell
then
Code:
su
then type this
Code:
setprop sys.usb.config diag,adb
there should be a adb msg again on your phone asking you to press ok, let your pc or laptop install the driver for diagnostic, after open QPST, go to Software Download, choose backup QCN, done!
Thanks
hi, any chance to activate diag port? "setprop sys.usb.config diag,adb" doesn't work!
thank's in advance
Related
So as the title suggests whenever I run the crackin.bat file in order to prepare my legend to be downgraded, it always displays the
cr--rw---- 1 1001 2002 90 line instead of the needed crwxrwxrwx 1 1001 2002 90 line.
I have looked everywhere to find a solution to this problem yet no matter where I look, everybody seems to be able to fix this by just either turning off and on their phone or wiping it. But I have tried all of those and, I have also tried doing this step on a different computer and reinstalling the needed files yet to no avail.
So if anybody has a possible workaround please do share it so I can finally root my phone after many tedious hours.
Sorry for the noob question and many thanks in advanced to anyone who can help me.
Azaruc said:
- Get visionary+
- Temproot your legend with it
- Use commandline with adb on your pc to flash misc1-2.img.
type the following commands from the folder where you have adb;
Code:
adb shell
su
accept the notification on your phone if one comes up
and then in the command line type this;
Code:
/data/local/flash_image misc /data/local/misc1-2.img
That should be enough to make it possible to run the 1.31 RUU.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11863394&postcount=2
Ahh, thank you. I had come across that before but i just didn't think that it would help! Silly me.
Ok, is there an IRC chat for the legend somewhere, im STILL getting this error. I can't find visionary+ anywhere where im sure enough its not going to mess up my phone, and i aparently am missing the files needed however none of the guides have downloads of everything i need.
PLEASE can someone help me? im so confused nothing is making sense. I get to copying files from DxDrx but that is nonexistant, what am i missing?
Ok, i got passed this step by doing these steps
1: download visonary here
http://forum.xda-developers.com/atta...3&d=1290501865
or here
http://content.modaco.net/dropzone/com.modaco.visionaryplus.r13.apk
or you can get it off the market
Then download hack4legend here http://www.multiupload.com/I3ZALKWB6A and unzip it somewhere (this is adb and the rooting tools)
2: install and open up visonary on your phone and do a temp root on your phone.
3: open up cmd and type in the following
cd "your hack4legend path here but with out the "" "
adb shell
su
4: after you do that on your computer you should see a notification on your phone come up, it might take a little. Accept it.
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
6: run the 1.31 RUU and your good.
Hope this helps
Unreal_628 said:
Ok, i got passed this step by doing these steps
5: type this into the command promt
/data/local/flash_image misc /data/local/misc1-2.img
Click to expand...
Click to collapse
/data/local/flash_image: not found
what am i doing wrong? i had to copy the contents of hack4legend to my adb folder so i have adb, is that it? do i have to change the drectory somewhere?
Mmm, if their is a platform tools sub folder in the android sdk try putting the hack 4 legend in there and re trying. It will either have to go in there or the tools sub folder in the android sdk.
And also make sure that when you use the cd command make sure to not just go to the android ask folder but into the platform - tools/tools depending on where you put your hack, try putting it in both and using different paths. Also you might wanna try updating the adb module "android sdk platform - tools revision 3" through the sdk manager.
And as allways make sure you have usb debugging on and have your phone connected to the computer through charge mode only.
VRoot Cleanup Tool - Easily replace VRoot with SuperSU
From your Windows PC​
OK everyone, here's the deal. I did the VRoot the toher day on my phone and it worked great. The problem is that it can be tricky to get the old Chinese Superuser app and SU binaries updated to SuperSU. As a result I decided to put this tool together to help update the VRoot files to SuperSU, and get rid of the old VRoot ones. What this means is that you can now clean up the Chinese Super User app and completely install SuperSU with a single click, from your Windows PC.
How to use:
Download Root Cleanup from here: https://www.dropbox.com/s/sto74q58uq4r1bj/root_cleaner.zip
Extract it to a folder on your computer.
Open the new folder and double click the clean_root.bat file.
Follow the directions.
** You will want to make sure that USB debugging is on (which it should be from VROOT) and that VRoot is closed when you run this. **
Also note I only have one phone to test with, and it worked great on the one I have. Please let me know if you have any other issues and I will try my best to help. Also, as always, not responsible for problems . <3
Edit: I just got asked via PM if this is to be run after freezing VRoot, etc. So I wanted to add here in case anyone else wondered. With this tool you do not need to freeze VRoot, delete any files, etc. My script will literally take care of everything for you. So, run VRoot and the phone will reboot. You can immediately close VRoot on your computer and run this to completely replace VRoot with SuperSU, and remove VRoot files.
This is my first time writing something like this, but so far I have a lot of people who told me it works fine. Please let me know if you have issues and Ill do my best to help! I went ahead and created this thread at the request of some people who have had good success with this on the other thread here: http://forum.xda-developers.com/showthread.php?t=2511815&page=29
Update: V4 is up - this version makes sure that ADB is accessible. Thank you @k1mu for helping me with this!
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
fabrilas said:
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
Click to expand...
Click to collapse
My guess would be these lines:
adb shell "su -c 'rm /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm /dev/com.mgyun.shua.su.daemon'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su.daemon'"
The issue is that I cant remember if com.mgyun.shua.su and com.mgyun.shua.su.daemon are directories or files. If you could confirm for me which they are then I will be happy to fix my tool!
Thx
Angie
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Works also with Galaxy S4 Italy Gt-i9505 :good:
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
LilTechPrincess said:
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
Click to expand...
Click to collapse
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
ComputerBro2 said:
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
Click to expand...
Click to collapse
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
k1mu said:
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
Click to expand...
Click to collapse
Thank you very much for the help! Im still a newb! haha Anyhow, I updated my tool with your suggestion.
LilTechPrincess said:
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
Click to expand...
Click to collapse
No the adb won't start on my phone
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Bfitz26 said:
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No it freze on this
rm failed for /sdcard/install-recovery.sh, No such file or directory
when i disconnect the pone say not found for 4 or 5 times and finish
---------- Post added at 08:49 PM ---------- Previous post was at 08:28 PM ----------
I tri 3 times
try to wipe all data.
Next try is to reinstall last firmware update whit odin or it trip my knox 0x0 to 0x1 ?
MexyHKR said:
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Click to expand...
Click to collapse
Thats not a big deal. Basically, I removed the /sdcard/install-recovery.sh from the script earlier and forgot to not try and delete a file that doesnt exist... Ill fix that! haha That doesnt hurt anything at all. Sowwy!
Ok now im freeze on Cleaning Up Files....
Your link is down
Tomsgt said:
Your link is down
Click to expand...
Click to collapse
The link has 2 hh's in the http
eklipz3 said:
The link has 2 hh's in the http
Click to expand...
Click to collapse
thanks did notice that
Finaly dont work on my GS4
PDA: I9505XXUEMJ7
MODEM: I9505XXUEMJ7
CSC: I9505ITVEMJ8
Try 2 times after full wipe and emergency firmware restore.
Freeze on Cleaning etc...
Now need to go sleep 1:06AM in italy
Good night and sorry for bad speak
I speak like a fish trying to speak Russian
Hello,
I've just received new phone, Alcatel One Touch Fire E (6015X).
This phone has got installed FirefoxOS,
my question is can I install android somehow?
I was looking for that information however not found anything what would help me.
kmlnvm said:
Hello,
I've just received new phone, Alcatel One Touch Fire E (6015X).
This phone has got installed FirefoxOS,
my question is can I install android somehow?
I was looking for that information however not found anything what would help me.
Click to expand...
Click to collapse
Hello,
I'm looking for a recovery image of this phone, do you know of any location to find one? Or could you possibly make one very please to help such people out? Hamachi (Flame) builds dont work.
uxuxux said:
Hello,
I'm looking for a recovery image of this phone, do you know of any location to find one? Or could you possibly make one very please to help such people out? Hamachi (Flame) builds dont work.
Click to expand...
Click to collapse
if you could tell me how to extract it from my phone, i can make it for you
jecustoms said:
if you could tell me how to extract it from my phone, i can make it for you
Click to expand...
Click to collapse
Hey, thanks for your offer. I found a guide for the Alcatel Flame, but I think we are interested in Step 5 only.
Code:
Step 5: Create backup images
Now start shell on the phone using adb shell command and dump backup images to SD card:
$ cat /dev/mtd/mtd0 >/mnt/sdcard/boot.img
$ cat /dev/mtd/mtd1 >/mnt/sdcard/system.img
$ cat /dev/mtd/mtd5 >/mnt/sdcard/userdata.img
$ cat /dev/mtd/mtd7 >/mnt/sdcard/recovery.img
When finished (you may also dump some more MTD partitions if you like), transfer those files to your computer. You may again use ADB for that:
$ mkdir hamachi-backup
$ I="boot.img system.img userdata.img recovery.img"
$ for i in $I; do adb pull /mnt/sdcard/$i hamachi-backup/; done
I can't link yet but it's from Krzysztof Adamski's blog, the full post is titled Alcatel One Touch Fire Hacking (Mini)Guide.
Maybe it would be enough, as the alcatel source for this device is not available yet on their sourceforge page, I'm not sure if it's possible to make a full recovery image without that.
I found another mention of such thing on the b2g-dev mail list
Code:
> You can backup the partitions from a working phone using 'dd' to dump
> them (you can find the relevant devices under /dev/block) and then use
> fastboot to flash them on the bricked phone (provided that fastboot
> still works).
first of all, i am a total noob..
"Now start shell on the phone using adb shell command"
what does it mean? how can start it?
Hello,
Following erasure of all data in recovery mode ( wipe date / cache / system) , I finally managed to reinstall a origin ROM .
Unfortunately , I did not know I had deleted all of my data.
I managed to get the IMEI code with SN_Writer_Tool_v1.1632.00 : Working
Unfortunately data remains that I can not change .
my serial number (SN ) is: 0123456789ABCDEF . I do not know from where it comes but it has nothing to do with the original number.
Can you give me the manipulation that allows me to restore this No. ??
I also noticed that the SNID / NS were "invalid" on the phone.
NVRAM is not present ?? I do not think I have a bootloader too.
HELP !!!
thank you
jblefou62 said:
Hello,
Following erasure of all data in recovery mode ( wipe date / cache / system) , I finally managed to reinstall a origin ROM .
Unfortunately , I did not know I had deleted all of my data.
I managed to get the IMEI code with SN_Writer_Tool_v1.1632.00 : Working
Unfortunately data remains that I can not change .
my serial number (SN ) is: 0123456789ABCDEF . I do not know from where it comes but it has nothing to do with the original number.
Can you give me the manipulation that allows me to restore this No. ??
I also noticed that the SNID / NS were "invalid" on the phone.
NVRAM is not present ?? I do not think I have a bootloader too.
HELP !!!
thank you
Click to expand...
Click to collapse
Help please. I did find any answer in the forum.
what phone is that?
My mediatek soc phablet came stock with the same serial number.
It is very possible your problem with imea number is unrelated to your serial number. I suggest finding a stock complete rom and start again from fresh.
OLderDan said:
It is very possible your problem with imea number is unrelated to your serial number. I suggest finding a stock complete rom and start again from fresh.
Click to expand...
Click to collapse
Hello,
my phone is a Acer Z410.
I use a recovery rom from acer to format it.
i think the problem is link with the NVRAM because is missing too.
I try to change barecode with MAIU but i don't have file et i don't know where i car download a NVRAM datebase for it....
This works for me on Oukitel K6000 Plus:
https://stackoverflow.com/questions...o-phone-are-connected-on-a-pc-can-i-change-th
echo -n "XXXXXXXXXXXXXXXX" > /sys/class/android_usb/android0/iSerial
Untill reboot, but it's a starting point.
jblefou62 said:
Help please. I did find any answer in the forum.
Click to expand...
Click to collapse
same happen to my celpon . my unit is Blu Grand Max - G110Q
How to change serial number ?
0123456789ABCDEF looks like a emulator or AOSP serial number
Check your default.prop or build.prop serial number
Code:
adb shell getprop | grep serial
[ril.serialnumber]: [0123456789ABCDEF ]
[ro.boot.serialno]: [0123456789ABCDEF ]
[ro.serialno]: [0123456789ABCDEF ]
and change it to yours
Code:
adb shell setprop ro.serialno YOURSERIALNUMBER
Edit build.prop or default.prop for persistent
Yablio said:
0123456789ABCDEF looks like a emulator or AOSP serial number
Check your default.prop or build.prop serial number
and change it to yours
Edit build.prop or default.prop for persistent
Click to expand...
Click to collapse
I already checked it in build.prop but the serial number is not there.
France Mari said:
I already checked it in build.prop but the serial number is not there.
Click to expand...
Click to collapse
not much info about this, sadly. Got this generic serial number issue right now on a Blackview Max 1, MT6763
Yablio said:
adb shell setprop ro.serialno YOURSERIALNUMBER
Click to expand...
Click to collapse
adb shell (even under su) doesn't give permission, is there a way to get permission to write
Code:
ro.boot.serialno
ro.serialno
Global_V12.0.7.0 (redmi note 9)
Hello,
I'm using some scripts that gather information from phones. Mainly IMEI number. However this stopped working;
adb shell service call iphonesubinfo 1
Normally it would return something like that:
Result: Parcel(
0x00000000: 00000000 0000000f 00350030 00320095 '........1.2.3.4.'
0x00000050: 00380035 00330030 00654083 00320058 '4.5.6.7.8.9.0.1.'
0x00000060: 00370097 00000033 '2.3.4... ')
But... with S22+ it does this:
Result: Parcel(fffffffc ffffffff 00000000 '............')
Something have changed... any one have any idea how to get IMEI from S22+ via ADB?
PS: phone is rooted, model SM-S906B
PPS: this method was working form S6 to S21
Edit:
It seems to be an FW issue, on first released S906BXXU1AVA7 it was working (with and w/o root).
Now I have issues on S906BXXU1AVC6.
BR, Doman.
use phone info from samsung, you have a lot of info
pitelasssss said:
use phone info from samsung, you have a lot of info
Click to expand...
Click to collapse
Nope. ADB only. I know that there are apps...
Update; I can confirm that this is an FW issue. I've rolled back to S906BXXU1AVA7 and all is ok. Any thoughts?
Update 2; well... I know "whats up" now. Staring from S906BXXU1AVBF (second available FW) there is a change in Android 12 that deprecated some functions... there is possibility for a workaround, but it's not elegant. I'm currently working on it.
I am having the same issue. Were you able to make any progress?
Hey, yes, I have a method... you need to call a code *#06# an then retrieve IMEI from it.
Here's a working example:
adb shell "imei=$(input keyevent KEYCODE_CALL;sleep 1;input text '*#06#'; uiautomator dump --compressed /dev/stdout|sed s/\>\<\/\\n/g|grep -A1 IMEI|tail -n1|sed -e 's/.*text=\"//' -e 's/\".*//'); echo ${imei:0:16}"
The above line is not mine, I'm doing it a bit differently, but it still works.
You guys able to rewrite original imei?
i'm in trouble with my s22 U
This even works for older devices,
Code:
adb shell service call iphonesubinfo 1 s16 com.android.shell | cut -d "'" -f2| grep -Eo '[0-9]'| xargs| sed 's/\ //g'
Let me know if this works!
Thank you
luckk said:
You guys able to rewrite original imei?
i'm in trouble with my s22 U
Click to expand...
Click to collapse
I haven't tryed to change IMEI on any new phone, as I remember it was a hassle 10 years ago...
uncommonthinker said:
This even works for older devices,
Code:
adb shell service call iphonesubinfo 1 s16 com.android.shell | cut -d "'" -f2| grep -Eo '[0-9]'| xargs| sed 's/\ //g'
Let me know if this works!
Thank you
Click to expand...
Click to collapse
Ha! It works on Android 13 (S23) and Android 8 (S8). Thats awesome, thanks!
I mean:
adb shell service call iphonesubinfo 1 s16 com.android.shell
The whole oneliner doesn't work on windows (but can be run in linux/android shell).
BR, Doman.
Doman2011 said:
I haven't tryed to change IMEI on any new phone, as I remember it was a hassle 10 years ago...
Ha! It works on Android 13 (S23) and Android 8 (S8). Thats awesome, thanks!
I mean:
adb shell service call iphonesubinfo 1 s16 com.android.shell
The whole oneliner doesn't work on windows (but can be run in linux/android shell).
BR, Doman.
Click to expand...
Click to collapse
Cool
Hi,
I have created a script to extract device information (including IMEI) which theoretically works on all Android versions.
For those interested: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/device-info.sh
Note: My script also works on Windows, it just need BusyBox for Windows to be executed.
ale5000 said:
Hi,
I have created a script to extract device information (including IMEI) which theoretically works on all Android versions.
For those interested: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/device-info.sh
Click to expand...
Click to collapse
These service calls can vary for the different versions of Android! You should be aware of this because you don't know what will happen for all the different devices and versions. It could be very dangerous for users to execute them.
Where to find info on Android's "service call" shell command?
Using adb shell or a terminal emulator on the device, entering this will clear all notifications (requires su) service call notification 1 This will send an sms (doesn't require su) service call...
stackoverflow.com
WoKoschekk said:
These service calls can vary for the different versions of Android! You should be aware of this because you don't know what will happen for all the different devices and versions. It could be very dangerous for users to execute them.
Where to find info on Android's "service call" shell command?
Using adb shell or a terminal emulator on the device, entering this will clear all notifications (requires su) service call notification 1 This will send an sms (doesn't require su) service call...
stackoverflow.com
Click to expand...
Click to collapse
Have you looked at the script?
It execute the right command for every Android version.
Doman2011 said:
PS: phone is rooted, model SM-S906B
PPS: this method was working form S6 to S21
Edit:
It seems to be an FW issue, on first released S906BXXU1AVA7 it was working (with and w/o root).
Now I have issues on S906BXXU1AVC6.
BR, Doman.
Click to expand...
Click to collapse
Anybody seeing Odin silently disappearing when trying to flash April security patch level firmware (Snapdragon S22+ SM-S9060)? Was fine all previous firmwares...
Edit: Post removed
I need to use adb cuz the screen is shattered. How do I pull imei while in stock recovery?
Rootmaster906 said:
I need to use adb cuz the screen is shattered. How do I pull imei while in stock recovery?
Click to expand...
Click to collapse
Stock recovery only accepts 'adb sideload'. There is no cmd to pull IMEI.
WoKoschekk said:
Stock recovery only accepts 'adb sideload'. There is no cmd to pull IMEI.
Click to expand...
Click to collapse
Can you assist me then? I cannot get any information off the phone because the screen is shattered and I can't see what is on it and my uncle forgot his password to get into it and we need the IMEI to do a trade-in
Rootmaster906 said:
Can you assist me then? I cannot get any information off the phone because the screen is shattered and I can't see what is on it and my uncle forgot his password to get into it and we need the IMEI to do a trade-in
Click to expand...
Click to collapse
IMEI is also written on the phone's package.