Hello Guys! Yesterday I was experimenting with my Yureka and accidently I lost IMEI of my phone. I searched YuPlayGod as well as XDA. There are some methods to recover/restore/change IMEI but unfortunately they are not working or they are too difficult to follow for a normal user. I kept searching for the solution and finally came to this. This work is not mine and the credit goes to the respective authors. I just have wrote this tutorial for the reference!
Beware: Changing IMEI is illegal. This tutorial is for those who are having their valid IMEI and have accidently lost during flashing or recoving from a brick. Please refer to your country law for the same.
**Although this tutorial is fully tested as I just have recovered my IMEI, yet I take no responsibility if something wrong happens with your device.**
Difficulty level: Easy
Things Required:
A PC or a laptop with windows as the Operating System, ADB driver installed
Qualcomm USB Composite Device 901D Driver (Link Given)
CKT Qwrite_Writer Tool (Link Given)
2 valid IMEIs to write. Refer to the box or bill for IMEI. It must be there
Your Yureka and a USB data cable
Step 1
Assuming your Yu is rooted. If not, Root it. Enable USB debugging. Install Terminal Emulator and type in the following commands in sequence
$ su
# setprop sys.usb.config diag,adb
Click to expand...
Click to collapse
This basically enables USB Diag mode of your phone. Now connect your phone to PC. You would see something like “Installing device driver software” which would fail eventually. Don't worry! We are about to install the Driver.
Step 2
Extract Qualcomm USB Composite Device 901D Driver at a easy to reach location and install it. There is no executable to install. You will have to install it manually using the Device Manager. See Post 2 for instruction.
Step 3
Assuming you have done the previous 2 Steps. Now the original task begins. Extract CKT Qwrite_Writer Tool to any easy to reach location and run an executable “Qwrite_Writer.exe”. You should see the following window.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The left side is to write the IMEI, Right side is to Read.
In left side, IMEI_1 : Enter your first IMEI and check the checkbox associated with it.
In left side IMEI_2: Enter your second IMEI and check the checkbox associated with it.
** Leave other things as it is. Do not touch any other setting as you may mess with it **
Now Click the start button at the Right side of the Message Box. And voila! You got your IMEI back :laugh: :good:
Downloads:
Qualcomm USB Composite Device 901D Driver: https://www.androidfilehost.com/?fid=385035244224398036
CKT Qwrite_Writer Tool: https://www.androidfilehost.com/?fid=673368273298918104
Credit:
To the original authors of the respective stuffs.
How to install Qualcomm USB Composite Device 901D Driver
How to install Qualcomm USB Composite Device 901D Driver
------------------------------------------------------------------------------
After enabling USB Diag Mode, connect your phone to PC/Laptop. Go to Control Panel and Open Device Manager. In Device Manager you will see your phone in Other Devices section. As AO5510 in my condition. Right click it and chose “Update driver software”. Then “browse my computer for driver software”. Then “Let me pick a list of device driver on my computer”. Then Next > Have Disk > Browse > and browse to the folder where you extracted the Qualcomm USB Composite Device 901D Driver. You would see a file named “htcser.inf”. Select that file and hit Ok and then follow the On-Screen-Process to finish the installation.
androidfilehost.com/?fid=385035244224398035 (IMEI WRITER SOFTWARE) this given link is not working . please update it soon.
rohitjaiswal said:
androidfilehost.com/?fid=385035244224398035 (IMEI WRITER SOFTWARE) this given link is not working . please update it soon.
Click to expand...
Click to collapse
Link updated in OP
Link not working
itsdroid said:
Link updated in OP
Click to expand...
Click to collapse
CKT Qwrite_Writer Tool: fid=673368273298918104
not working 404 error
it worked...thanks
Related
This guide is for anyone having issues with their HTC Hero drivers. It is aimed at Windows users and the guide was performed on Windows 7 x64 but relevant to older systems with minor adjustments (use common sense).
Most of it will be pictures, i'll try to fill in the rest in future and give it some layout but for the most part this process is easier to see than describe. Very much a work in progress.
Note: Unplug your phone from your pc for these processes until told otherwise. Remove any version of HTC Sync prior to 2.0.33 before doing these processes.
Might Need Apps:
HTC Sync for Android v1.5
HTC Sync for Android v2.1
USB Deview
Remove Old Drivers:
1. Start USBDeview by running the exe in the zip file
2. Remove any drivers which read like the following:
3. Reboot your machine
Installing The Correct Drivers:
1. Install the latest version of HTC Sync (2.0.40 or 3.0.5422)
2. Reboot
3. Right Click on Computer in your start menu and choose "Manage"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Select Device Manager on the left hand side.
5. Plug your phone into the PC and let the drivers install (you should see changes in device manager in real time). Under "ADB Interface" you should now see "My HTC" as seen in the picture.
This is correct and you should move onto the "Bootloader Drivers" section below. If you don't see this then carry on.
6. Right click on whatever you get under "ADB Interface" and do the following:
- Choose Update Driver Software...
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- Have Disk
- Browse
- C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 (last folder may be different)
- Select "androidusb.inf"
- OK
- Next
- Finish
You should now have the correct HTC Hero drivers installed. Move onto bootloader drivers section.
Bootloader Drivers:
Note: assumes you have the latest version of HTC Sync installed prior to doing this and have followed the driver process above to arrive here.
1. Switch off your phone and then hold Volume Down when you press the Power On button (Vol Down + Power).
2. You should have a white screen with some coloured text and 3 android's on skateboards. This is bootloader mode.
3. Now plug your phone into your pc and watch device manager change (this can take a minute or two). If "ADB Interface" doesn't show up or you get an "Unknown Device" error (perfectly normal - i think) then press the Back button and wait a couple of minutes then press volume Down again. This switches to Fastboot mode and back to Bootloader mode. AFAIK the drivers are the same so you should be able to do this process in either mode. You should get the driver "HTC Bootloader" or similar in your device manager. You need to repeat the steps above to change that to My HTC instead.
4. Right click on whatever you get under "ADB Interface" and do the following:- - Choose Update Driver Software...
- Browse my computer for driver software
- Let me pick from a list of device drivers on my computer
- Have Disk
- Browse
- C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 (last folder may be different)
- Select "androidusb.inf"
- OK
- Next
- Finish
You should now have the correct HTC Hero bootloader drivers installed. This will allow you to correctly install a RRU from HTC.
Brilliant guide! I have added it to my sig!
Nice one, thanks
Wow this worked 100% installed perfectly
thanks
Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh:
All right, so you have updated your phone's ROM or you have purchased Windows 10 Pro, you plug your USB cable from the phone to the computer. Phones get charge, if you choose PTP (to transfer photos) it works, but if you select MTP or USB storage you hear a sound like if you had disconnected the cable and phone is not recognized.
This is related to a driver problem. To fix it:
1 - Plug the USB and select MTP connection
2 - Go to your Device Manager (Press Win+R, on the search box write "mmc devmgmt.msc" without quotes). You can use any other way you know to enter D. Manager.
3 - You should see something similar to "Portable devices". Display the flange (if not).
4 - Now right click on something similar to "Unknown Device" (yellow highlighted text) with a yellow tringle in the icon.
5 - Choose "Update driver software"
6 - Select "Browse my computer for driver software"
7 - Select "Let me pick from a list of device drivers on my computer"
8 - You get a list with a lot of possible drivers.
9 - Choose Mobile Devices/Android Phone/Android USB Devices (you should have at least one of them)
10 - Select "MTP USB Device" from the second screen's list of drivers.
*If you do not see Portable Devices in Device Manager then maybe you don't have installed drivers properly. In that case, first download drivers from here and install them. Then follow this guide.
Some screenshots of the proccess (it is in Spanish but what you have to do is the same and is translated in the steps).
1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2
3
4
5
6
7
8
That is the most common solution to the problem. If your problem is not fixed with that, then try this:
Published on Microsoft Answers:
Question:
After anniversary update, MTP is not working.
I tried with different devices as well as on many PCs.
In device manager I get this:
The drivers for this device are not installed. (Code 28)
A service installation section in this INF is invalid.
Click to expand...
Click to collapse
Solution:
1 - Go to C:\Windows\INF
2 - Type "wpdmtp.inf" in search bar provided to the right of the address bar in Windows 10.
3 - Once you found it, just right click on it and select install. It will take a very few seconds.
4 - Connect your device to the pc. It should be recognized now.
I hope this can be useful for you.
Any doubt, ask in comments
Hello N4 Owners/Users.
lately I've been working on IOS & iCloud Activation Lock Security, which is a Job I honestly do not wish you have, because is not a great business at all but, going more deep in this post I'm glad to post it because I've been trying to send iCloud Accounts stored on a PDF at my Nexus 4, a device that I've purchased last month at eBay and is incredible how this device with Unofficial ports runs faster and without bugs, of course using PURE Nexus ROM.
first things first, I must specify that I was sideloading ZIP's, APK, ROMS through ADB SIDELOAD commands, so that the first sign of a properly working USB Port, I didn't noticed yet that I was unable to set up my device as MTP and transfer photos or WhatsApp Folder to my PC.
2 weeks later I've noticed that MTP was not working, even changing "Charge Option" to "Transfer Files" so I just put my knowledge on going, the first thing was download the USB driver at Google SDK webpage, which delivers USB Drivers apart instead with the whole SDK, I've just proceed to download it, I've installed it and for my surprise the MTP was still not working...
what do now ?
Steps:
1. Download the proper driver designed by google
Google Nexus 4 Drivers.
2. Make sure your PC is not on secure boot, for this you should reboot your PC and enter to BIOS Setup to make sure secure boot is not activated, if it is, please turn it off.
3. reboot again and let your PC boot, you may notice that the boot sequence UI display a little messed up, but is normal.
4. go to UWP Settings and Select "UPDATE & SECURITY"> "RECOVERY"> "Advance startup" and hit at "Restart Now"
5. your PC is going to restart again & you'll see a menu of likely 10 or 9 options, we need deactivate the option 7.
7). Disable Driver Signature Enforcement.
Click to expand...
Click to collapse
doing this your PC will restart again or maybe it just boot the Windows or UEFI Logo.
6. Find & Run CMD as administrator and execute the code below.
bcdedit /set TESTSIGNING ON
Click to expand...
Click to collapse
Restart your PC Again.
wait, you need the MTP or really are you craying for such restarts?
okay, that's what I though.
7. Disable ADB on your device and connect it to PC, Open device manager and look for "Android ADB Interface"
8. Right Click on the device and select "Update driver", Select "Browse My Computer for driver software"
9. locate drivers folder you've already downloaded following this guide and after that, you must have this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select "Let me pick from a list of available drivers on my computer"
If are 2 MTP entries, install them and reboot your PC, and that's all people, MTP working.
Now go back at CMD as Administrator and set this
bcdedit /set TESTSIGNING OFF
Click to expand...
Click to collapse
Now Restart and enter at BIOS, restore secure boot, done!
Hit "thanks" button if this helped you recovering MTP Access and your PC at your N4.
Hello there, I have been searching for something for hours and just can't figure this out. So I have an old Galaxy Note 3 and want to get Lineageos running on it. Have done this before a few times with other phones, but here from the official guide I have to use Odin.
So what happens is that when the phone ist just regularly on I can see it in Odin, I can also see it when I do adb devices. I have usb debugging on and have set it to trust my computer.
However, as soon as I boot into download mode the phone becomes invisible to the computer, no return to adb, not visible in Odin.
Any ideas what I could be missing? Thanks so much!
Do you see other devices in the device manager?
Show the phone screen in download mode.
What OS on the PC? What version of drivers from Samsung? What variant of Odin?
Thank you for your fast reply! Really appreciate it! Of course I left out some info....
In the windows device manager I see other devices, I also see the note 3 when it is just regularly turned on, just not when in download mode. The note shows up in device manager as SAMSUNG Android ADB Interface and as SAMSUNG Mobile USB Composite Device. Using Odin 3.14, also tried 3.13 at some point.
OS in Windows, can't do Odin in others, can I? Played around with Heimdall on a Linux computer, but that did not go anywhere and can't find much documentation. Did not flash anything, just tried to see if I could get it visible.
Version of drivers from Samsung, how do I check that? I downloaded them from Samsung as in the official instructions.
Now the Download screen might be part of the issue here, I have been searching around with that, it seems that the last thing it says is "UDC start" is not what it is supposed to do... should be attached. Thanks again!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the phone is in download mode, Windows sees the SAMSUNG Mobile USB CDC Composite Device as a serial bus controller, and Odin sees the COM port.
Install the latest drivers from Samsung (if you have older ones) and the latest adb from Google.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Thank you! Just reinstalled the drivers from samsung (already had them, but can't hurt), restarted, but no difference yet.
To clarify, by "installing the latest adb" you mean download the plattform tools, unzip, and then open a command line in the folder? That allows me to run adb commands, like I can do adb devices and will see the phone, just not when it is in download mode.
When in download mode my device manager does show me a Serial USB Device (COM5), however Samsung is not part of the name. It is the device though, as it disappears when unplugged. But since it does not state that it is a samsung device, I am thinking maybe that points to a driver issue in some way?
Oh wow, something just happened. I went to the Serial USB Device I talked about, deactivated, re-activated, told it to re-install drivers, than suddenly it moved down the list to the USB controllers and has the exact name you started. And Odin sees it now!
bilboBeutlinhh said:
Oh wow, something just happened. I went to the Serial USB Device I talked about, deactivated, re-activated, told it to re-install drivers, than suddenly it moved down the list to the USB controllers and has the exact name you started. And Odin sees it now!
Click to expand...
Click to collapse
Glad you got it sorted! Cheers
Thanks again! And in case anyone finds / reads this, it seems that just installing the Samsung drivers might not install them all, checking in the device manager when download mode is active and running an update of drivers from there made the difference.