Database Develop

Lost imei number and device number

My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?

BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...

Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.

I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick

Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...

mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work

mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help

Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time

No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)

[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!

Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!

mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help

That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.

mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it

Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)

Asus Zenfone GO (ZB551KL) IMEI NULL ( 0 )

Like the topic says, my ZB551KL Zenfone Go won't register network operators and i suspect it's because the IMEI of the phone is 0 after applying official update. I've tried to Root the phone by downgrading to version WW_V13.2.8.13 and installing KingRoot and using Xposed IMEI modules but this fuxed up the phone and sent it into a bootloop. So i reinstalled the WW_V13.2.8.13 firmware again (the only firmware that KingRoot will work on, so basically the only way to root the phone) and rooted the phone again and tried to open the diagnostics port through adb shell, but when i execute the command: "setprop sys.usb.config diag,adb" it says setprop: not found.....so i am guessing i can't open the diagnostics port this way. And Xposed IMEI changer won't work cause Xposed fux up my phone into a bootloop.
So if anyone has any idea how i could change my IMEI back to what it originally was i am all ears. I was reading something about using a HEX editor, but i don't know how to get the IMEI files out of the phone or how to write them back into the phone.
And yes i've tried installing every official firmware, factory reset many times etc.... IMEI is 0 until i somehow change it myself. And when i do my SIM cards will be able to register on the network again. So any help is very much appreciated.

Honestly, they should just ship android with rooting options. Rooting newer devices is a huge pain in the neck right now.

This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.

How we can root zb551kl

same problem here.. pls help

dbfonseca said:
This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.
Click to expand...
Click to collapse
yep enable diag port take the hell out of me

i enabled diagnotic mode
eyobaaa said:
yep enable diag port take the hell out of me
Click to expand...
Click to collapse
how to recover imei from zero ?? i enabled diagnostic mode on this device

Basically you have to boot to fastboot then flash CSC firmware (also called RAW firmware) to enable qualcomm diag port.
Note that there are 2 kinds of this: 1 is the kind that connects via QDLoader 9008/QFIL to recover from hardbrick, and one that installs a very raw form of android and enables the diag port. You need the latter. Since I don't have the files anymore, you basically run this bat script file that connects via fastboot and hot-boots its own kernel that allows the diag port.
Then use this program called FactoryTool_WriteIMEI_v1.0.2 (Factory_tool_wingtech_v1.0.2.0.exe) to write the IMEI (since official qpst dont support dual Sim). You may need to fire up QPST/QFIL to get a proper com port for the software to work. Then flash first old firmware and you're good to prevent it getting corrupt again.
---
Problem is that this seems to be a symptom of a failing board since ever since the LCD started to flicker when in battery mode and OK when USB is plugged in. Baseband and IMEI becomes corrupt again when you update your system. Also periodically phone shuts down and becomes a 9008 device (hardbrick) but also comes back. Left it alone for days and it was fine after but problem came back after trying a game (solder cracks?) Will try to reflow the motherboard.
May I ask if you changed your LCD? This started happening to mine when I installed a system update after replacing the LCD+digitizer. It seems the phone is downloading the Chinese software update since it detects the (chinese?) panel and installs an incompatible Chinese modem baseband firmware. Upgrading to latest downloadable firmware also corrupts the IMEI slowly (Sim 1 first then Sim 2).

Sony XZ1 Compact Driver Fastboot

Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
{
"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"
}
Thanks you :good:

Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.

Didgesteve said:
If you're stuggling to find the ADB drivers for your phone, I'm not sure that you should be trying to root your phone, no offence.
Rooting it will break the camera completely. There is a DRM fix, which does leave all the functions of the camera working. But I wouldn't go down that route personally. The 'fix' was actually stolen from another developer and released without permission. The Dev who's running the drm fix thread didn't build the fix and has no idea how it works. Read for yourself, support is very patchy, it's a difficult thing to get right. You need to apply the right patches in the right sequence on top of a 8.49 CE firmware build, or it wont work.
It's a fix not a workaround, you destroy your TA keys buy unlocking your phone and you will never get them back.
Also you're dependent on the Dev (sToRm//) compiling a new fix to go with any new firmware released.
You could never update again without his help, and right now, he's got the hump.
Click to expand...
Click to collapse
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison

Braindeadz said:
Thanks you for you help, i think you are right but it's very difficult to tell me i don't "root" my phone because every smartphone i have in my life was root. I buy a Sony phone for the first time and maybe the last because it's what i like with Android, Root, change ROM, again and again. Maybe Modpunk release a stable LineageOS ?
I buy this phone because it is small, very small, snap 835, sd card, speakers on the front and fingerprint on the right but i hope Oneplus make a little phone like this a day
I feel like I'm in prison
Click to expand...
Click to collapse
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.

Didgesteve said:
I know, every phone I've ever owned I rooted, it's almost a habit, but with this bootloader Sony is giving us the finger. The main reasons I wanted to root were usually to get a better battery and to mod the framework to make it look better, but the battery with this phone is already good, it doesn't need any help.
If you want to mod the looks then it's possible to do that too.
I don't want to be negative and put you off trying to do amazing things with your phone, but I thought you should know the details before you start.
Edit: yes, I think LineageOS is very close now, perhaps when that is working I might move to that.
Click to expand...
Click to collapse
Thanks for your tips, I'm waiting for LineageOs now, it seems like a better idea.
Thanks you Didgesteve

Braindeadz said:
Hi everyone,
I would like to root my device but i need the drivers, i search and install what i find on the web and sony website but every time when my divice is in fastboot mode it not recognize by windows.
I think this thread can be usefull for many persons so i open it.
Mobile : Sony XZ1 Compact
This is a screenshot of my device when i plug it in fastboot mode :
Thanks you :good:
Click to expand...
Click to collapse
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..

crummmcakes said:
I ran into a similar issue when trying to use Emma. It only runs on Windows, so I had to go through this as well.
First, download and install Android Studio for your OS:
developer . android .com/studio/ index. html
(Note: Android Studio is not required, just the SDK. But Android Studio will install the SDK for you in a standard location. This might make things easier for you.)
Once this is done, launch it to install the SDK. You can select all defaults.
Once the SDK is installed, click Configure in the bottom-right of Android Studio and select SDK Manager. On the first screen, select the SDK Tools tab in the middle. Here you will want to select Google USB Driver and click Apply. This should install the driver.
Then, go back to the device in the device manager and right-click the device and select Update Driver.
After that, I followed the steps here:
stackoverflow . com /questions/14559734/ install-adb-interface-driver-for-android
to get the driver installed. This was because I kept getting an error that the system could not find the Android ADB Interface.
For the record, the Google USB Driver was installed on a Windows 10 box in the following location:
%localappdata%\Android\Sdk\extras\google\usb_driver
Hope this helps you out..
Click to expand...
Click to collapse
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.

hage_JK said:
Unfortunately, these drivers do not contain the correct drivers. I do not have any idea, I've been desperate.
Click to expand...
Click to collapse
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?

crummmcakes said:
What do you mean by "these drivers do not contain the correct drivers"? Did they fail to install for you?
I just spun up a new Windows 7 VM to test this out again, and it worked for me.
What steps are you taking exactly?
Did you receive any errors when you tried to install the driver this way?
How is your device appearing in the device manager?
Click to expand...
Click to collapse
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas

Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10

Dean F said:
Hi, is there a solution to this? I am also looking for the fastboot driver. I have no issue with ADB driver... its just fastboot. My Z5 with fastboot is ok.... but Z1C not. Im running windows 10
Click to expand...
Click to collapse
Sometimes the drivers don't install properly in Windows 10, although it doesn't tell you they failed to install (helpful). You need to start Windows in safe mode and look for 'Disable driver signing'
Also, if you've used your computer for another device, then it's likely those drivers are still in it kicking about and probably getting in the way. You might have better luck going to another computer that has never been used for ADB and starting fresh.

Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!

van_vugt said:
Hi everyone,
Dunno if this is the right thread to post my question but the subject is Fastboot so I am trying my luck. Want to unlock the bootloader of my phone via Sony website... step 1 and 2 are no problem and I have my unlock code. Unfortunately I can't get my phone into FASTBOOT mode. Connected cable to laptop, hold volume button up and connected phone to cable but nothing happens. Is there anyone that can help me out?
thnx!
Click to expand...
Click to collapse
It's been mentioned before on a different thread.

Didgesteve said:
It's been mentioned before on a different thread.
Click to expand...
Click to collapse
Thnx... overlooked that thread. Will try that!

hage_JK said:
The device in fastboot will appear in the device manager as Android as the first stick.
Drivers dowload from Sony developed or Android SDK reports not found driver.
Drivers from Sony or Google they work in USB debugging but not driver in fastboot, still reports Android without drivers.
Testing on Windows 10 x64 and Windows 7 x32
Thank you in advance for any ideas
Click to expand...
Click to collapse
Did you use the standalone SDK, or did you use Android Studio?
If you used Android Studio, what do you see in: %localappdata%\Android\Sdk\extras\google\usb_driver\
If you did not use Android Studio, would you be willing to try it? I only suggest it since it installs everything to specific locations, so perhaps removing an additional variable could be useful.
Otherwise, Didgesteve's suggestion seems like a good next step.

I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?

k_basara said:
I have the exact same problem. Sony driver and Google driver both don't work. Driver sign in Windows 10 is disabled. How can I don now?
Edit: After followed the steps showed in this video the drivers are successfully installed but when unlocking the bootloader it says "command not allowed". Do I have to unlock it if I want to root my phone?
Click to expand...
Click to collapse
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options

Didgesteve said:
Yes, unlocking your phone is the first part of rooting your phone. Unlocking is a one way process, you can't ever undo it and it will break your camera, completely. Be aware of that before you continue, the threads are full of people crying about broken phones that can't be re-locked.
It might be your phone is not allowed to be unlocked. Some phone providers in the UK sell phones that cannot be unlocked, mostly because they don't want the headache of people claiming unlocked phones be repaired.
Type *#*#7378423#*#* into your phone dialer to access the service menu.
Then look under Service info/configuration.
Under Rooting Status it should say Bootlock unlock allowed - yes.
If it says no then forget it.
Edit: you also need to allow OEM unlocking in the developer options
Click to expand...
Click to collapse
Yes, I forgot to allow OEM unlock in my phone settings.
I gave up unlocking my phone anyway, compare to years ago, stock rom nowadays isn't that unacceptable after all.

Hi - after months I finally solved the fast boot issue by using the above mentioned video: https://www.youtube.com/watch?time_continue=105&v=nQjg6ePnGAc
Basically - the key is that there are 2 steps:
1. Connect phone in usb debugging mode - then install sony adb driver using device manager and "have disk"
2. Boot into fastboot - and again install sony adb driver using device manager and "have disk"
Result = fastboot now working!

today I root my XZ1C
I have lots of problems with fastboot and i have other solution
for ADB i use driver from Sony ( installed by device manager )
but for fastboot
I use "Android ADB Interface" installed with Android Studio (you can choose it device manager --> update driver --> manual install --> installed on pc --> google or on my PC it was Samsung and there was google --> Android ADB Interface )
thats was only think that work for my device
I lost today 3/4h for this one think
maybe it will help someone to safe this time
Enjoy !

G900A Galaxy S5 Android 6.0 Odin Update Files - Without Wiping!

Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in QD1, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576350

Worked great..Thanks! But....
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again

3rdRockfromSun said:
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
Click to expand...
Click to collapse
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again

iBowToAndroid said:
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
Click to expand...
Click to collapse
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?

3rdRockfromSun said:
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
Click to expand...
Click to collapse
https://www.att.com/deviceunlock/

Thanks in advance for any help, short version at top, details below.
-- Short version:
Please help me recover my data, and phone if possible.
I need the data, esp texts and notes, for both personal (some family members have passed on) and business.
I have a new Galaxy S21 and / or PC Smart Switch ready to receive data backup if we can evacuate it from the S5.
ODIN flash seems to pass but has 'Resizing Data' fail, and phone still won't boot past AT&T logo screen.
All web searches seem to say Factory Reset is my last option, but I don't want to lose the data.
Please share ANY advice on how I can recover the data.
-- More details:
Phone = SM-G900A Samsung Galaxy S5 AT&T
Use = pristine, never rooted, modded, or unfortunately backed up
Status = will not boot, passes screen 1 'Galaxy S5', screen 2 'Samsung script', then stops on screen 3 'AT&T globe logo'
More details = Used clean for ~7 years, then on day x, saw phone automatically complete a system update (green screen, sprockets, "your phone is updating"), which was surprising as it's years after it is no longer supported by AT&T. After that update, I continued to use the phone that day, but it then rebooted automatically and stuck on the AT&T globe logo.
Attempts to fix = soft reset, battery pull, can't get into SAFE MODE, can get into and out of recovery mode, found this firmware (THANKS @iBowToAndroid), used multiple ODIN (Odin3 v3.13.3_3B_PatcheD, Odin3 v3.14.1_3B_PatcheD) to flash it (my first Android flashing experience). On flashing process, ODIN on PC shows 'PASS' and log shows "<OSM> All threads completed. (succeed 1 / failed 0)", but phone shows 'Resizing Data' failed:
"
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Resizing Data...
Can't open dir '/data/user/0/com.sec.knox.bluetooth' (Permission denied)
E:failed the resizing-data
"
PFA screen shots

Martin2019 said:
Thanks in advance for any help, short version at top, details below.
Click to expand...
Click to collapse
Trying the "wipe cache partition" is the only thing I can think of

iBowToAndroid said:
Trying the "wipe cache partition" is the only thing I can think of
Click to expand...
Click to collapse
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
The string seems to indicate a 'user data' permission error?
Is there any way to debug the logic of the firmware or slog through the 'Recovery Logs' to determine and resolve the cause of the permission error?
When the problem began, I had an SD card and SIM card loaded.
I've since removed both in trying to address this, also per 'web advice'.
Any chance putting them back in helps somehow?
Any other options available via apply update from SD card or ADB?
Any way to setup the Android OS as a secondary drive to another machine to pull data out that way?
I've done similar things with Windows OS in PC environment, but I'm not seeing anyone trying that with Android.
If I am really stuck with factory reset, are there any data recovery programs I could try afterward that work with the G900A?
So far I've looked at Dr Fone, Tenorshare, EaseUS, FonePaw, and D-Back, and none seem to work with the AT&T model variant.
Maybe that's just because they don't have access to AT&T firmware available to install, but if I clear the stuck boot via FR, they then might be able to get some of my data back via drive scan - whatever data is not truly overwritten by the FR?

Martin2019 said:
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
Click to expand...
Click to collapse
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset

iBowToAndroid said:
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
Click to expand...
Click to collapse
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.

Martin2019 said:
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Click to expand...
Click to collapse
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times

iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Totally agree, and totally on me for not having a backup.
I was just foolish enough to not know yet how easy it is to back up.
Give me 10 minutes of life again now in this phone, I use Smart Switch to backup, and I'm off to a new phone, or even FR on this one and reload.
Now where did I put my Delorean...

iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Have you ever tried a 'combination key' approach to get data access?
As in...
Smart Switch on PC won't connect, but ODIN does show 'Added'.
I don't understand the granular details, but hoping you might...
Could we use both Smart Switch and ODIN in some combination sequence that would allow Smart Switch to pull the data off to a Smart Switch PC backup that I could then throw onto a new phone?

When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?

iBowToAndroid said:
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
Click to expand...
Click to collapse
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?

Martin2019 said:
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Click to expand...
Click to collapse

Any 3rd party software will require ADB to be enabled. Smart Switch is the only one that *might* work just over MTP, but I'm pretty sure MTP doesn't fully load until the device is booted. Even if it did, you would likely need to allow on the popup message. Does the phone show up as a device/drive when it's plugged in while sitting on the AT&T logo?

I think you're asking "does the phone show up as a device/drive" in something like a windows file explorer, and the answer is unfortunately no, or at least not that I've found yet - I've tried several times now, and I'm still trying any combinations I can.
For now...
I can get EaseUS to show 'MTP USB device' per the pic attached in my last, but can't really get it to connect past that point, as it asks for USB Debugging, which it appears I can't do due to stuck in boot loop.
Smart Switch seems to try to connect for awhile, then says it failed to connect, so I think I'm then left with 'Samsung Smart Switch Emergency Software Recovery' (PFA).
Do you have experience using it?
Do you know if it could work to reload the firmware / OS without wiping the data?
AT&T Advanced Technical Support guy says it gives you an option to choose whether or not using it resets the phone (wipes your data), so he thinks (hopes) that would work, but he didn't sound certain at all.
I understand your point on the pop up message user prompt for File Transfer Mode. I used that mode many times in the past, so I'm hoping it might default on the phone so we wouldn't need to answer the pop up prompt to reach that status , but I'm obv not sure about that.
Per the speculation in my last, do you know of any combination approach we might use to get the desired result, like maybe... use ADB somehow to change 1 parm value to reach MTP mode, then use that progress step to enable Smart Switch to connect so we could offload the data?
Thanks again for your help

1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
2. But if the phone never shows up as a device/drive (would show up under "Portable Devices" in Windows Dev Man), then it's not loading fully - and it normally doesn't do that until it boots past the carrier splash screen.
3. Even if it did boot fully and showed up as a device/drive, the MTP pop-up prompt shows up every single time you connect the device. There's no way around that. So the device would show as empty, with no files or folders, until you tapped "Allow" on the popup.
4. No, there's nothing else you can do to turn on any other connection modes

iBowToAndroid said:
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
Click to expand...
Click to collapse
Device Manager does show an entry for the phone connected via USB cable:
Under 'Disk Drives' as
SAMSUNG MZMTE256HMHP-000MV
Under 'Universal Serial Bus Controllers' as
SAMSUNG Mobile USB Composite Device
Please tell me that helps us somehow?

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

Can we get a video of how to do this?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.

AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.

#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks

#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.

Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project

So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader

MOD EDIT:
This is the latest version
这是最新版本

#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?

for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"

gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them

Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.

gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com

any luck with that? can I backup my firmware before doing it?

darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.