I need to copy/create new device. Let's say I have in Google Play device list 1 device: Lenovo 8..., now i need NOT TO CHANGE THE EXISTING id, imei or whats ever, but to create a new one, pretending i bought another one. So in the list will appear ANOTHER device. I tried to change imei, id, model, manufacturer but all this gives just RENAMING same device NOT creating new.
Related
I've read a few posts regarding the device ID changing from OS to OS flashes. I've been using Black from the beginning and it didn't seem to change the Device ID. Slingmedia and other programs installed OK.
I recently flashed LVSW ROM and it changed the ID. I had to get new registration codes from my programs because of this. I am afraid to flash new ROMS often now because of changing the device ID. These companies probably won't continue to change the codes for us forever.
I thought that the device ID is static based on the hardware itself. How can this change with a new OS? Can it be changed back without flashing another ROM? Can it be prevented from changing with a new flash?
The device ID is generated dynamicly after every hardreset.
http://blogs.msdn.com/jasonlan/arch...card-wipe-and-encryption-what-s-the-deal.aspx
Very interesting, but I wonder if other apps are using ( and used in WM5 ) the "same" ID ... In any case, there's gotta be a way to see and change it one way or another. "The doors are everywhere, you just have to know how to open them"
doedoe said:
The device ID is generated dynamicly after every hardreset.
http://blogs.msdn.com/jasonlan/arch...card-wipe-and-encryption-what-s-the-deal.aspx
Click to expand...
Click to collapse
I don't believe this at all. I think it's more likely the device is taking a one-way hash to the manually input device ID (see below) and SIM ID, plus some randomizer to create a unique identifier for the storage card encryption. My guess is this process runs when you check the box to encrypt the card. If anyone knows this to be different, please share how to locate the unique device ID.
Some ROMs has the Device ID (Settings -> System -> About -> Device ID) pre-populated with things like TyTn, or other text. I think the differences in some of the earlier ROMs was screwing everybody up because close attention wasn't paid to this. The first thing I've done each time I re-flash is change this to WM_[my-windows-logon], because when the device syncs with Activesync the first time, it goes with some combination of what's there plus your logon. Anyway, I've manually set this to WM_[myname] (yes, this is an example, 'myname' is not my logon) before syncing with Activesync. I've done this on Black 2.5, 3.0.1, one of LVSW's ROMs, and Custel's 2.5. I have yet to need a new sling code or tomtom code.
Maybe I didn't do such a great job of explaining this, but all you have to do is look at Activesync and see what it thinks your device ID is. If you've registered software, pay attention to this name and simply enter it after a re-flash. Multiple flashes means you need to delete the device partnership in Activesync each time, and when you manually code it to WM_(yournamehere) or whatever you have now, I bet you have no problem with sling or tomtom.
If anyone can confirm this, we should place it in the wiki.
Device ID
The device ID does not change after every hard reset, however with certain roms it can change the ID, at this time there is no fix for the changing ID problem. I also have a few programs that are teathered to the device ID instead of the IMEI.
My advice is, Keep track of which roms you load and on what dates you load them. Do like I do, before you install a new rom, run a Sprite backup (or whatever program u use) on your device (do a full, including storage card) backup. Then if your ID changes, you can reinstall the rom that worked with all your apps and run the backup app, I have had to do this several times and all of my apps are still working and registered.
You just have to decide what is more important, the rom, the working (registered) app, or continuing to ask for a replacement registration key.
100Tbps said:
Maybe I didn't do such a great job of explaining this, but all you have to do is look at Activesync and see what it thinks your device ID is. If you've registered software, pay attention to this name and simply enter it after a re-flash. Multiple flashes means you need to delete the device partnership in Activesync each time, and when you manually code it to WM_(yournamehere) or whatever you have now, I bet you have no problem with sling or tomtom.
Click to expand...
Click to collapse
It may work for those apps, but it isn't that easy for Infogation Odyssey (TomTom competitor), to name one. Has to be some deeper hashing algorithim in the ROM or whatnot. It changed around the time the 17xxx builds started appearing and I've always wondered if it could have a "dogfood" link.
Here are some MSDN articles on the issue:
http://blogs.msdn.com/jehance/archive/2004/07/12/181116.aspx
http://blogs.msdn.com/jehance/archive/2004/07/12/181067.aspx
http://blogs.msdn.com/windowsmobile/archive/2006/01/09/510997.aspx
We need a good programmer to figure this out
My Experiences
I have suffered from this very problem. My device ID stayed the dame from WM5, to XDA 0.1 > XDA 0.2 > Black 2.0 > Black 2.5
I then went to Black 3.0.1 and my device id changed. Infact, after getting a new licence string, the program that needed it (PocketHeroes) would bomb out whenever it tried to verify the new licence. This problem persisted in LVSW 3.3.
Now I am on Black 3.5 and my device id has reverted. My origional licence works fine and the app is 100% stable. My only guess is that a certain build of the kernal had a flaw with the deviceid and this has been naturally replaced by a newer version.
Device ID
The device ID (name) that is used for activesync is not the same as the device ID used for certain programs. The device ID that we are refereing to is a 12 digit code that looks like XXXX-XXXX-XXXX where X = the ID for each device.
lewnetoons said:
The device ID (name) that is used for activesync is not the same as the device ID used for certain programs. The device ID that we are refereing to is a 12 digit code that looks like XXXX-XXXX-XXXX where X = the ID for each device.
Click to expand...
Click to collapse
How can I see this 12 digit code?
Anybody going to write a program to change this? if legal!
lewnetoons said:
...clip...
My advice is, Keep track of which roms you load and on what dates you load them. Do like I do, before you install a new rom, run a Sprite backup (or whatever program u use) on your device (do a full, including storage card) backup. Then if your ID changes, you can reinstall the rom that worked with all your apps and run the backup app, I have had to do this several times and all of my apps are still working and registered.
You just have to decide what is more important, the rom, the working (registered) app, or continuing to ask for a replacement registration key.
Click to expand...
Click to collapse
I say, that is a great suggestion. :thumbsup
What's happening here is the platform ID portion of the Device ID is changing. This is because many roms here (including mine) use IMGFS components from the Universal. When this occurs, the platform ID portion of the Device ID changes from Hermes to Universal as well.
It appears that even the Official WM6 released today does indeed change the Device ID for instance with Tomtom Traffic.
I am having to take this original wm6 off now and stick with a development version of wm6 until i can convince tomtom to change my device id which they wont do. They are so useless....
just so other users are aware.
I have a broken screen on my Universal, and have just sourced a second one, and am trying to decide whether to Flash and restore to the "new" one, or swap the hardware over to the old one and continue running.
So my first point is - what set of ROM's do I have on my existing device?
Is there a way of getting this firmware information via a tool from the PC, e.g. something through active sync?
The phone is internal working order, I can still run some applications that I know the keystrokes for - but you cannot see anything on the screen!
if I determine a set of ROMs I'm happy to flash the new one, install my backup software, and do a full restore to it.
Trying to determine what my backup software will do for me in this respect.
(Currently using Sprite Backup WM2005)
I can install software that can grab or push information - but only as long as it does not require any interaction on the old device!
My Mobiler ???
Does anyone know or have any idea where the Kindle Serial Number is located in the device? (not through the menu but stored within the device), the reason I ask is because I am testing eldarerathis' FFF extended bootloader and I was tinkering with flashing Stock ROM (rooted) to the alternate partitions, funny thing is that for some reason the OS is unable to retrieve the Serial Number and so you can't register the device with Amazon. I've looking through every file within the ROM and I have not been able to identify anything that could possibly give me a hint of where the Serial Number is located.
Any thoughts, ideas, suggestions are greatly appreciated.
jopaez said:
Does anyone know or have any idea where the Kindle Serial Number is located in the device? (not through the menu but stored within the device), the reason I ask is because I am testing eldarerathis' FFF extended bootloader and I was tinkering with flashing Stock ROM (rooted) to the alternate partitions, funny thing is that for some reason the OS is unable to retrieve the Serial Number and so you can't register the device with Amazon. I've looking through every file within the ROM and I have not been able to identify anything that could possibly give me a hint of where the Serial Number is located.
Any thoughts, ideas, suggestions are greatly appreciated.
Click to expand...
Click to collapse
If it was sitting in some file, it would be much too easy to spoof and lead to sharing Prime accounts, etc. It would have to be embedded in the hardware somewhere. That's my way of telling you that I have no idea why that setup would have a hard time retrieving the serial number.
jopaez said:
Does anyone know or have any idea where the Kindle Serial Number is located in the device? (not through the menu but stored within the device), the reason I ask is because I am testing eldarerathis' FFF extended bootloader and I was tinkering with flashing Stock ROM (rooted) to the alternate partitions, funny thing is that for some reason the OS is unable to retrieve the Serial Number and so you can't register the device with Amazon. I've looking through every file within the ROM and I have not been able to identify anything that could possibly give me a hint of where the Serial Number is located.
Any thoughts, ideas, suggestions are greatly appreciated.
Click to expand...
Click to collapse
Why are things like this in the Dev section? This needs to be moved to Q&A
The only reason is I feel there is a better chance of getting a response for this type of question from active devs than most regular users. If not agreed by a moderator I'll gladly move this to the Q&A.
I recently bought a Kindle Fire from Ebay and I'm unable to register it on Amazon.
The amazon reps told me that the serial number is blacklisted and recomanded me to return the device to sender and ask for refund.
Well, I'm unable to do that and I don't want to install a custom rom on it.
The serial should be located within the software, and there should be a way to change it (like adding IMEI - see the guide in the dev section).
will it work with fastboot ? does this change the serial number or jst the number that 'adb devices' will display ?
fastboot -s <serial number> specify device serial number
Any help will be greatly appreciated.
you say you dont want to install a custom rom but its really the best and easyiest way around it... I recommend this one http://forum.xda-developers.com/showthread.php?t=1439916
Emeraldu said:
I recently bought a Kindle Fire from Ebay and I'm unable to register it on Amazon.
The amazon reps told me that the serial number is blacklisted and recomanded me to return the device to sender and ask for refund.
Well, I'm unable to do that and I don't want to install a custom rom on it.
The serial should be located within the software, and there should be a way to change it (like adding IMEI - see the guide in the dev section).
will it work with fastboot ? does this change the serial number or jst the number that 'adb devices' will display ?
fastboot -s <serial number> specify device serial number
Any help will be greatly appreciated.
Click to expand...
Click to collapse
It wouldn't do you any good to change the serial number. There's a corresponding security key number paired with it, so changing one won't help without the other. Since Modaco is just an enhanced version of the stock software, it wouldn't be any different either in terms of obtaining Amazon services on the device (sorry pooch).
Contact ebay/paypal and file a dispute.
Hi,
Due to a repair under warranty, my IMEI stayed the same and my Device Id changed. Therefor I can't unlock my device anymore.
LG is unwilling to cooperate with changing the IMEI DeviceId combination in there database. I could file a complaint with my provider who changed the behaviour of my phone after a repair. The cunsumer authority in my country said that I would win the lawsuit but I don't want to put in the effort...
I still know my old device Id. Is there a way to change the device Id and use the old unlock file?
Is the Device Id LG asks for the same Id as the Android device id?
Thanks a lot!!
Frans
No you can't change the device id, it's fused into the device. Your best bet is to keep bugging LG to accept your new IMEI/DevId combination.
Found a tool called Qualcomm flash tool. Maybe it will do the job. Just need to know where it's stored.
Hello,
while attempting to root my Blackview BV6000s (containing Mediatek MT6737T chip) I lost both IMEI's. Although I succeeded in rooting the phone, I was not able to restore the IMEI.
1) If I use Mediatek Engineering apk, when I send the string "AT+ EGMR=1,7,"IMEI_1″ I receive the error "This Command is not allowed in user build". I have read a lot of forum posts where they say to put a blank after "AT+", but it doesn't work placing the blank in any place: before or after the "+", or without blank at all. Always the same result: "This Command is not allowed in user build". I have tried all the versions of MTK engineering apk that I found inside and outside google play store
2) It is not possible to get any connection with "MTK Droid tool". Same result with MauiMETA
3) With SN write tool, when I plug the USB cable the phone powers on and the Blackview logo is shown, and after few seconds a red "FAIL" message is shown by the SN writer tool. It seems that the phone is not able to enter in "meta mode"
4) I have generated an IMEI file named "MP0B_001" and I have copied it in the right place with the root browser, but after the reboot the IMEI are still empty. I remark that when I try to set the write permissions, the root browses pops up an error message saying that the file system doesn't allow changing the permissions of the files. Then I packed the MP0B_001 in a zip file and I installed it with the TWRP recovery. The installation with TWRP doesn't show any error, but then after the reboot the IMEI are still invalid (null). Note: in ALL the posts that describe how to install the MP0B_001, they indicate /data/nvram/md/NVRAM/NVD_IMEI/MP0B_001 as the path where the file is stored. But in my phone the path is different, and precisely it is /nvdata/md/NVRAM/NVD_IMEI/MP0B_001. This makes me think that nobody have tried to apply this procedure to BV6000s. Anyhow, I tried to pack and install the zip with both paths, with the same unsuccessful result.
5) The only way I could write something in the 2 IMEI's is with Chamelephon. However there must be an incompatibility between Chamelephon and my phone. In fact, after applying the new IMEI's and rebooting, when reading the IMEI I find random strings instead of null strings. What is odd is that one of the 2 SIM cards succeeds in connecting with to the mobile networks and receive calls and SMS, even with this corrupted IMEI, while the other SIM still gives "invalid IMEI" error. I tried to find newer versions of Chameleon, but it seems that only version 1.0 exists
6) I tried to install all the ROM's that are compatible with MT6737T but the results of attempts 1-5 are the same.
In conclusion, it seems quite impossible to fix the IMEI. I have the impression that nobody tried to fix the IMEI on this specific phone, or that the producer has decided to "punish" whoever tries to root the phone, by preventing the repairing the IMEI. All the forum posts and guides, on which I based the attempts that I have described in this post, are not referring explicitly to BV6000s. Before resigning myself, I decided to create this post. Maybe it could be helpful also to other persons, if a solution exists and is described here.
Best regards
I have solved the issue and I am reporting here the solution for the benefit of those who should face the same problem.
I had to remove the encryption from the phone. I have installed the "no verity" package (no-verity-opt-encrypt-6.1.zip) with TWRP recovery and formatted the data section. This made necessary to reinstall all the applications from scratch. Further information: https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
Then I used ghost phone (from google play store) to fix the IMEI; anyway after removing the encryption also Chamelephon was working.
***
Now I am in doubt whether I should restore the encryption.
If I restore the encryption, I am afraid that this could cause the loss of IMEI's again, or re-introduce some other annoying restrictions.
If I leave it not encrypted, I am afraid that my phone is more vulnerable to rootkits and similar malwares.