How fix or change my SERIAL NUMBER : 0123456789ABCDEF - Android Q&A, Help & Troubleshooting

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)

Related

Serial # changed after unbrick ?

I unbricked my 16 gm tablet using parted and ubuntu wipe. Now I can't register with B&N. I notice the serial # in the info screen is different. I believe I somehow have Adam Outlers old serial # in my machine. Is there a way to edit this in ADB ? Currently have cm7 internal with ADB working. I'd like to option of returning to stock if need be Thanks Again
sailerph said:
I unbricked my 16 gm tablet using parted and ubuntu wipe. Now I can't register with B&N. I notice the serial # in the info screen is different. I believe I somehow have Adam Outlers old serial # in my machine. Is there a way to edit this in ADB ? Currently have cm7 internal with ADB working. I'd like to option of returning to stock if need be Thanks Again
Click to expand...
Click to collapse
according to adamoutler's thread, his total wipe ubuntu flash doesn't affect the rom partition which contains your serial information. so that shouldn't be the problem...
ShinnAsuka said:
according to adamoutler's thread, his total wipe ubuntu flash doesn't affect the rom partition which contains your serial information. so that shouldn't be the problem...
Click to expand...
Click to collapse
Well, I don't know what I did, but I definitely have a wrong serial # in my device. Is it possible to edit the serial # and how Thanks
sailerph said:
Well, I don't know what I did, but I definitely have a wrong serial # in my device. Is it possible to edit the serial # and how Thanks
Click to expand...
Click to collapse
Try this link. http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
tobdaryl said:
Try this link. http://forum.xda-developers.com/showthread.php?t=1610069&highlight=serial
Good Luck!
Click to expand...
Click to collapse
Would anyone be able to simplify/expand this tutorial ? ADB is working. Confused after serial # Recovery
what do I do with Veronica's mmcblk0p5 image ? Are we copying/pulling/editing/pushing ? basically ? Thanks

Try to unlock TF201 with unknown serial number

Edit 21/04/13
I have been able to write a serial number. I have the number written in the parameters.
I haven't been able to unlock with the unlock tools but maybe that's coming from my number I can't even register on the Asus website.
Here what I have done in a teminal on the tab :
Code:
su
mkdir /Removable/p5
mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
//Note or Copy the numbers in the file /Removable/p5/UUID (even if you lost it the number is in /sys/devices/platform/cardhu_misc/cardhu_chipid)
//From that point I delete the files /Removable/p5/SSN and /Removable/p5/UUID
//Then create new files SSN and UUID (I work with Root Browser) then paste the number in each respective files.
//To finish
umount /Removable/p5
reboot
The difference is that this time I rewrite UUID.
Hi everyone,
Thanks to the tools of motochopper here I have been able to root my device.
But as some people I have problem with no serial number and no more warranty. I know the tool Ratchet but it's not working on JB.
I have notice that the ratchet tools can't work cause of the missing file /sys/devices/platform/cardhu_misc/cardhu_backup_chipid.
After a few try I couldn't be able to create that file. It only contains a number the chipid : the UUID.
So from the code of Ratchet here (Ratchet source code) I tried to do the same command.
Code:
adb shell
su
mkdir /Removable/p5
mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
//From that point I edit the file /Removable/p5/SSN (even had to create it the first time)
//Didn't touch UUID the number was the same of chipid
umount /Removable/p5
But still after a wipe data, the same result "Unknown".
Do you any idea how to create a file in /sys/devices/platform/cardhu_misc/
Or if 5th and 6th parameters of mount() are important (0,0). Maybe all the partition as to be re-written As the tools should do.
Or if we could recompile the code with FILE *cardhu = fopen("/sys/devices/platform/cardhu_misc/cardhu_chipid", "rb");
Thanks if some people could help me to learn a little more about that.
I don't know how to compile for Android device or to write fonction mount() to linux command "mount".
Or maybe all of this is wrong and the serial number is not anymore store in P5 partition.
ratchet won't help you unlock. and don't ask questions in this section
The source code of Ratchet has at least helped me to write a serial number in my tf201.
Now Asus France check on their database my serial number.
If I can register on the Asus website the Unlock tool will maybe work.
nico42 said:
The source code of Ratchet has at least helped me to write a serial number in my tf201.
Now Asus France check on their database my serial number.
If I can register on the Asus website the Unlock tool will maybe work.
Click to expand...
Click to collapse
Can you please upload the new version for JB have also been trying to rewrite my s/n with old version but jb has changed the partitions!
jimgb17 said:
Can you please upload the new version for JB have also been trying to rewrite my s/n with old version but jb has changed the partitions!
Click to expand...
Click to collapse
I only use command in a terminal on the tab.
As I wrote in the the first post I do :
Code:
su
mkdir /Removable/p5
mount -t vfat /dev/block/mmcblk0p5 /Removable/p5
//Note or Copy the numbers in the file /Removable/p5/UUID (even if you lost it the number is in /sys/devices/platform/cardhu_misc/cardhu_chipid)
//From that point I delete the files /Removable/p5/SSN and /Removable/p5/UUID
//Then create new files SSN and UUID (I work with Root Browser) then paste the number in each respective files.
//To finish
umount /Removable/p5
reboot
That's why I was asking if someone could help me to recompile the code. For now I didn't compile the code and maybe never I have to see if there are lots of difference compare of 32 or 64 system and which compiler to use.
My JB version is 10.4.2.18 Jelly Bean. http://forum.xda-developers.com/showpost.php?p=21065580&postcount=3
back when I was on ICS I successfully changed the serial number but still wasn't able to unlock, so it's probably not going to help
Glebun said:
back when I was on ICS I successfully changed the serial number but still wasn't able to unlock, so it's probably not going to help
Click to expand...
Click to collapse
Yes it could help users unable to unlock after rma!
Once you get your serial back you can call Asus and tell them you cant unlock after an rma!
if your s'n in unknown then asus will ask to rma again to get serial back on device.
if we can rewite the serial to the device without rma then
we can send serial and other info to asus then asus can send the information to head office then we can get our devices unlocked via asus tool.. head office can sort the problem!!
android is open source and its not fair for asus to stop us using out own images!
At least asus usa knows this and is trying to help users that cant unlock.
Have a look at this thred
http://forum.xda-developers.com/showthread.php?t=1764917&page=59

[Ask Any Question] Clone Phone Question Thread [Newbie Friendly]

This is a question thread for people who have Clone Phones by HDC, Goophone, Tengda, iHD, and other manufacturers' phones that are based upon an existing phone by a major manufacturer.
The design of this thread is equal to this
Make sure to read the Forum Rules before posting
Anyone can answer.
All questions are welcome!
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Hi Xda,
I have a fake Lenovo S960c (didn't knew before i purchased it) , after i rooted it with kingo user, because there was a malware which was located only by rooting . the malware was removed , but after few months the same type of malware came again but this time there was two or three malware which was causing my battery to drain and i couldn't charge my phone battery to 100% . My Antivirus Showed my Mediatek file had a malware , i didnt know so i uninstalled that file after my phone restarted it is caught in bootloop and won't go beyond the lenovo logo.
Please advise how can i solve this problem as i have been scammed when i bought this phone from Aliexpress,
thinking this was a real MTK6595 MODEL original Lenovo phone. I have written below my phone's real spec which
i got using Mtk droid tools for your reference. please advise how can i fix my phone again.
Hardware: Mtk6572 (Mtk6595 is fake)
Model: S960c
Build Number : S5_JB3_3G_EMMC_QHD_32_4_XLD_Z12_LENO
Build Date : 20150417-064045
Andriod v: 4.4.3
Baseband: ____
Kernel v: 3.4.5([email protected])(gcc version 4.6x-google 20120106 (prerelease)(GCC)#1 SMP Fri Apr 17
18:02:31 CST 2015
sufyan nuhammad said:
Hi Xda,
I have a fake Lenovo S960c (didn't knew before i purchased it) , after i rooted it with kingo user, because there was a malware which was located only by rooting . the malware was removed , but after few months the same type of malware came again but this time there was two or three malware which was causing my battery to drain and i couldn't charge my phone battery to 100% . My Antivirus Showed my Mediatek file had a malware , i didnt know so i uninstalled that file after my phone restarted it is caught in bootloop and won't go beyond the lenovo logo.
Please advise how can i solve this problem as i have been scammed when i bought this phone from Aliexpress,
thinking this was a real MTK6595 MODEL original Lenovo phone. I have written below my phone's real spec which
i got using Mtk droid tools for your reference. please advise how can i fix my phone again.
Hardware: Mtk6572 (Mtk6595 is fake)
Model: S960c
Build Number : S5_JB3_3G_EMMC_QHD_32_4_XLD_Z12_LENO
Build Date : 20150417-064045
Andriod v: 4.4.3
Baseband: ____
Kernel v: 3.4.5([email protected])(gcc version 4.6x-google 20120106 (prerelease)(GCC)#1 SMP Fri Apr 17
18:02:31 CST 2015
Click to expand...
Click to collapse
Most likely, the malware was caused by a required system app. Maybe the dialer, MMS, or search app? Whenever the app sweeps your phone to check and sees there is no malware app, it connects to a server and, unbeknownst to you, installs it as a system app.
Do you know the actual manufacturer? In antutu it would show Zen, Alps, Wen, Next, or another OEM name. If so, that helps a lot in recovering your OEM mtk phone.
Your phone is recognized by mtk droid tools right? If so, you should be able to go into recovery as well. Even make cwm which should help
Sent from my SGH-M919 using XDA Free mobile app
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Qiangong2 said:
Most likely, the malware was caused by a required system app. Maybe the dialer, MMS, or search app? Whenever the app sweeps your phone to check and sees there is no malware app, it connects to a server and, unbeknownst to you, installs it as a system app.
Do you know the actual manufacturer? In antutu it would show Zen, Alps, Wen, Next, or another OEM name. If so, that helps a lot in recovering your OEM mtk phone.
Your phone is recognized by mtk droid tools right? If so, you should be able to go into recovery as well. Even make cwm which should help
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
First of all thanks for your kind Reply , really appreciated , when its comes to android, I am a toddler , not much experience in installing or flashing roms or making recoveries either. Please guide me step by step way , like a child
how to fix my phone again , as my hard earned money will go down the drain. if try to flash or do something else,
already i made it stuck on boot loop.
:good::good:
Regards
Sufyan
sufyan nuhammad said:
First of all thanks for your kind Reply , really appreciated , when its comes to android, I am a toddler , not much experience in installing or flashing roms or making recoveries either. Please guide me step by step way , like a child
how to fix my phone again , as my hard earned money will go down the drain. if try to flash or do something else,
already i made it stuck on boot loop.
:good::good:
Regards
Sufyan
Click to expand...
Click to collapse
No problem, I'm happy to help.
1. Is your phone still recognized when you plug it in to mtk droid tools?
2. Do you know what the actual manufacturer of your phone? If so, what?
3. What was the name of the file you deleted? (not needed, but it might help)
Qiangong2
Hardware: MT6572 (MTK6595 IS FAKE) MODEL :S960c
Qiangong2 said:
No problem, I'm happy to help.
1. Is your phone still recognized when you plug it in to mtk droid tools?
2. Do you know what the actual manufacturer of your phone? If so, what?
3. What was the name of the file you deleted? (not needed, but it might help)
Qiangong2
Click to expand...
Click to collapse
Yes , its does when i connect it to the droid tools it says in the message window,
Attention fake hardware in kernel or firmware doesn't correspond to phone
Attention File/system/Recovery-from-boot-p which restore factory recovery in case of phone
switching on in a normal mode is found.
also in left side menu the beside yellow light there is a message which says ,
S960c system/bin/su is found! Via root button it is possible to get root shell.
then when i press root button this message appears ,
to try to receive root shell through already established su .
I press yes to the button, after a while this error pop's up ,
Loss of communication with the device! the program will be closed.
I press OK then the software window is gone.
I am sorry, really don't know the actual manufacturer of the phone , i even did an tutu test but really , i only remember is the fake specs that mesmerized me a lot nothing else ,
The Files I deleted where Mediatek file , i bingo as the Anti Virus showed serious Malware in them.
sufyan nuhammad said:
Yes , its does when i connect it to the droid tools it says in the message window,
Attention fake hardware in kernel or firmware doesn't correspond to phone
Attention File/system/Recovery-from-boot-p which restore factory recovery in case of phone
switching on in a normal mode is found.
Click to expand...
Click to collapse
The first "Attention" shouldn't matter, it's just reading the build.prop which claims that it is an MT6595 instead of an MT6572. The second "Attention" is more interesting. I've actually never seen that one before, but it seems like there was some error in the ROM, and (when there is) it defaults to booting to factory/stock recovery.
also in left side menu the beside yellow light there is a message which says ,
S960c system/bin/su is found! Via root button it is possible to get root shell.
then when i press root button this message appears ,
to try to receive root shell through already established su .
I press yes to the button, after a while this error pop's up ,
Loss of communication with the device! the program will be closed.
I press OK then the software window is gone.
Click to expand...
Click to collapse
You may already have root, or it may not be there anymore. Try opening adb (from the adb button) and type:
Code:
adb devices
If your phone is recognized, type:
Code:
adb shell
Then (if it works) type:
Code:
su
if you see a # sign right next to where you type, then you have root.
I am sorry, really don't know the actual manufacturer of the phone , i even did an tutu test but really , i only remember is the fake specs that mesmerized me a lot nothing else ,
Click to expand...
Click to collapse
That's okay, it will just be harder to find information about your device firmware, not impossible though.
The Files I deleted where Mediatek file , i bingo as the Anti Virus showed serious Malware in them.
Click to expand...
Click to collapse
That should be fine... Mediatek files can be required or useless. Most of the time they only activate if you enter factory test mode. Since they had malware in them, they shouldn't be needed.
Qiangong2 said:
The first "Attention" shouldn't matter, it's just reading the build.prop which claims that it is an MT6595 instead of an MT6572. The second "Attention" is more interesting. I've actually never seen that one before, but it seems like there was some error in the ROM, and (when there is) it defaults to booting to factory/stock recovery.
You may already have root, or it may not be there anymore. Try opening adb (from the adb button) and type:
Code:
adb devices
If your phone is recognized, type:
Code:
adb shell
Then (if it works) type:
Code:
su
if you see a # sign right next to where you type, then you have root.
That's okay, it will just be harder to find information about your device firmware, not impossible though.
That should be fine... Mediatek files can be required or useless. Most of the time they only activate if you enter factory test mode. Since they had malware in them, they shouldn't be needed.
Click to expand...
Click to collapse
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
---------- Post added at 11:29 AM ---------- Previous post was at 11:22 AM ----------
sufyan nuhammad said:
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
Click to expand...
Click to collapse
i tried all your commands mentioned above while pressing Adb Terminal Buttton, in the end the command line showed # as you have mentioned , now what should i do please advise. once again thanks for your efforts brother.
sufyan nuhammad said:
Sorry i forgot to tell you that when my phone was in OK condition , i did root it with kingo root , so do you think , it
is still rooted while caught in boot loop. sorry for not telling you the complete details. So should i follow the above mentioned details , also where would i find the adb button , is it when i connect the phone through droid tools it will appear there or you are talking about phone recovery menu.
---------- Post added at 11:29 AM ---------- Previous post was at 11:22 AM ----------
i tried all your commands mentioned above while pressing Adb Terminal Buttton, in the end the command line showed # as you have mentioned , now what should i do please advise. once again thanks for your efforts brother.
Click to expand...
Click to collapse
You have root so you are stuck in bootloop. The bootloop seems to be caused by mediatek file now...
Have you removed any other files? Also, where was the file placed that you removed?
Qiangong2 said:
You have root so you are stuck in bootloop. The bootloop seems to be caused by mediatek file now...
Have you removed any other files? Also, where was the file placed that you removed?
Click to expand...
Click to collapse
As i mentioned before i only removed the file from settings, then click app, then all files , from there i uninstalled mediatek file and iBingo file nothing else. . Please advise what to do now.
sufyan nuhammad said:
As i mentioned before i only removed the file from settings, then click app, then all files , from there i uninstalled mediatek file and iBingo file nothing else. . Please advise what to do now.
Click to expand...
Click to collapse
The mediatek file is the problem then. We need to figure out what exactly the file is and also whether it is a customised file or a generic. If it is generic, then we can just copy it from another MT6572 phone with the same screen aspect ratio. If it is customised, then we need to somehow recover the file, or just get a copy of the stock firmware from the manufacturer.
On a side note: have you tried pulling a copy of your stock ROM out using adb? It may be able to shine some light onto what exactly the file affected. If you can't, that's fine. We'll just move on
Qiangong2 said:
The mediatek file is the problem then. We need to figure out what exactly the file is and also whether it is a customised file or a generic. If it is generic, then we can just copy it from another MT6572 phone with the same screen aspect ratio. If it is customised, then we need to somehow recover the file, or just get a copy of the stock firmware from the manufacturer.
On a side note: have you tried pulling a copy of your stock ROM out using adb? It may be able to shine some light onto what exactly the file affected. If you can't, that's fine. We'll just move on
Click to expand...
Click to collapse
Sorry, Brother i don't really know if the file is generic or Customised one, i only remember when i uninstalled mediatek and i bingo , the first error which came up was some google gaaps type error , it asked me to repair it i clicked OK , then my phone restarted and when into boot loop. I wish i new how to do adb backup and copy my stock ROM , as i said earlier not a pro , not even a rookie , just a dumb toddler who doesn't know much about android apps and system mechanics . sorry to put you in a mess brother. thanks for your cooperation
sufyan nuhammad said:
Sorry, Brother i don't really know if the file is generic or Customised one, i only remember when i uninstalled mediatek and i bingo , the first error which came up was some google gaaps type error , it asked me to repair it i clicked OK , then my phone restarted and when into boot loop. I wish i new how to do adb backup and copy my stock ROM , as i said earlier not a pro , not even a rookie , just a dumb toddler who doesn't know much about android apps and system mechanics . sorry to put you in a mess brother. thanks for your cooperation
Click to expand...
Click to collapse
Okay, go into adb from mtk droid tools, and type:
Code:
adb shell
Then (once it connects) type:
Code:
su
Now you have root. Next type this:
Code:
cat /proc/partitions
To find out which partition contains your system.img, your boot.img, and your data.img.
If none of the partitions say system or boot. Then make a copy of the partition list and upload it. We'll go from there.
Qiangong2 said:
Okay, go into adb from mtk droid tools, and type:
Code:
adb shell
Then (once it connects) type:
Code:
su
Now you have root. Next type this:
Code:
cat /proc/partitions
To find out which partition contains your system.img, your boot.img, and your data.img.
If none of the partitions say system or boot. Then make a copy of the partition list and upload it. We'll go from there.
Click to expand...
Click to collapse
i followed the instructions and type the command adb shell , from there , the com and line became like this
[email protected]:/$ when i typed su beside this this error came {-} connection to ui timed out , i still went with the last command and when i wrote cat /proc/partitions , this is whats happened afterwards,
major minor #blocks name
7 0 1254 loop0
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 665600 mmcblk0p4
179 5 385024 mmcblk0p5
179 6 1355776 mmcblk0p6
179 7 1332992 mmcblk0p7
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3933184 mmcblk1
179 97 3929088 mmcblk1p1
[email protected]:/ $ mmc
Did i do something wrong or is this what you are looking for , please advise me .
sufyan nuhammad said:
i followed the instructions and type the command adb shell , from there , the com and line became like this
[email protected]:/$ when i typed su beside this this error came {-} connection to ui timed out , i still went with the last command and when i wrote cat /proc/partitions , this is whats happened afterwards,
major minor #blocks name
7 0 1254 loop0
179 0 3795968 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 665600 mmcblk0p4
179 5 385024 mmcblk0p5
179 6 1355776 mmcblk0p6
179 7 1332992 mmcblk0p7
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3933184 mmcblk1
179 97 3929088 mmcblk1p1
[email protected]:/ $ mmc
Did i do something wrong or is this what you are looking for , please advise me .
Click to expand...
Click to collapse
This is what we're looking for. mmcblk0 is the entire device. it seems like mmcblk0p4 is the system.img as it is the largest partition within device mmcblk0.
use this:
Code:
cat dev/block/mmcblk0p4 /sdcard/system.img
Which should save your system partition as a .img file on your sdcard which, once transferred to your computer, you can open with the applications ext2read and ext2explore (both on sourceforge)
Repeat previous code, replacing mmcblk0p4 with: mmcblk0p6, mmcblk0p7, and mmcblk0p5. those should bring out your boot.img and your recovery.img at least. use the perl scripts I've attached to unpack those. the instructions are in the readme file.
You are gonna be hard pressed to learn android on a knock off device. No real developer will even touch it.
Qiangong2 said:
This is what we're looking for. mmcblk0 is the entire device. it seems like mmcblk0p4 is the system.img as it is the largest partition within device mmcblk0.
use this:
Code:
cat dev/block/mmcblk0p4 /sdcard/system.img
Which should save your system partition as a .img file on your sdcard which, once transferred to your computer, you can open with the applications ext2read and ext2explore (both on sourceforge)
Repeat previous code, replacing mmcblk0p4 with: mmcblk0p6, mmcblk0p7, and mmcblk0p5. those should bring out your boot.img and your recovery.img at least. use the perl scripts I've attached to unpack those. the instructions are in the readme file.
Click to expand...
Click to collapse
i started in adb, then command line by typing cat dev/block/mmcblk0p4 /sdcard/system.img but it said
'cat' is not a recognized as an internal or external command, operable program or batch file.
then i retyped adb shell , then su then i typed this cat dev/block/mmcblk0p4 /sdcard/system.img
this error show up
/system/bin/sh: cat: dev/block/mmcblk0p4 / permission denied
/system/bin/sh: cat: /sdcard/system.img / no such file or directory
1 :[email protected]:/ $
now what should i do , please advise.
sufyan nuhammad said:
i started in adb, then command line by typing cat dev/block/mmcblk0p4 /sdcard/system.img but it said
'cat' is not a recognized as an internal or external command, operable program or batch file.
then i retyped adb shell , then su then i typed this cat dev/block/mmcblk0p4 /sdcard/system.img
this error show up
/system/bin/sh: cat: dev/block/mmcblk0p4 / permission denied
/system/bin/sh: cat: /sdcard/system.img / no such file or directory
1 :[email protected]:/ $
now what should i do , please advise.
Click to expand...
Click to collapse
You could always just do a backup in mtk droid tools.
To do this,
1) connect your phone to the computer
2) open mtk droid tools
3) when the information shows up, click root button to get root shell (if you don't already have root shell). Then, click the root, backup, and recovery tab.
4) click backup. It is now starting to backup your phone. It doesn't matter if you pack it or not at the end.
All of the files should be in the mtk droid tools backup folder.
Qiangong2 said:
You could always just do a backup in mtk droid tools.
To do this,
1) connect your phone to the computer
2) open mtk droid tools
3) when the information shows up, click root button to get root shell (if you don't already have root shell). Then, click the root, backup, and recovery tab.
4) click backup. It is now starting to backup your phone. It doesn't matter if you pack it or not at the end.
All of the files should be in the mtk droid tools backup folder.
Click to expand...
Click to collapse
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
please tell what to do .
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
sufyan nuhammad said:
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
please tell what to do .
Click to expand...
Click to collapse
also this message was included
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
sufyan nuhammad said:
when i click root in droidtools . this message then this message shows up
to try to receive root shel through already established su? i clicked yes , after a while in the left side message screen it shows : error su inaccessible . i retried again this time i click no , but this time in the message screen there was a different message :
Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
please tell what to do .
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
also this message was included
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Click to expand...
Click to collapse
please help me if you are not busy, waiting for your reply.

HELP! Need QCN file for ZE554KL

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

Question S22+ IMEI via ADB not working

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.

Categories

Resources