Database Info

Convert Demo Mode to Retail Mode phone

Some guy on Craigslist sold my not-very-smart sister an HTC 8X Windows Phone 8 for $250. After playing with it for 2 mins she did not realize that it is locked in demo (store) mode and probably stolen from a store. I've no idea to be honest. But she is out $250 w/ this demo mode phone and asking me to try to fix it.
I would like to try to flash this demo mode HTC 8X phone into a regular AT&T windows 8 phone or unlocked windows 8 phone.
I previously flashed a Windows 7.0 Samsung Focus phone w/ Mango through the wonderful instructions on this forum. I'm tempted to try it again, but I would appreciate any guidance on:
1. Finding the right ROM for a HTC 8X phone. It says:
OS version: 8.0.9905.12
Firmware revision: 1532.20.10012.502
Hardware revision number: 0002
PM23300 on the back.
I'm based in the US. Again, it is an 8X HTC in demo mode. I've no idea if it is security locked. Or how to even tell if it is security locked.
2. Basic instructions on how to flash it. I am intelligent enough to have gone from 7.0 Nodo phone to Mango w/ no issues following instructions on here. But I don't code (at least for the last 7-8 yrs)...
3. Any add'l steps, risks, cautions, caveats, etc. I should consider. Should I just not even bother w/ this phone, because I don't want to be responsible for bricking it... (ie. try to sell it on Ebay and recover some $)
Any help would be really appreciated! Thx.

There is an icon in the apps list called: "Windows Retail Mode"
And if I use it, it prompts me with RAC:
I assume it is some code to convert this phone to retail mode from demo mode. Any idea how to get the RAC password? It also allows me to try to enter an admin password.

It is probably locked as AT&T ships their 8X locked. However, you can check it out by entering the bootloader. Just power off your phone and hold volume down + camera and press power. Release power button only and it will enter the bootloader.
Also, please don't double post.

Enter bootloader and flash with RUU.

jValdron said:
It is probably locked as AT&T ships their 8X locked. However, you can check it out by entering the bootloader. Just power off your phone and hold volume down + camera and press power. Release power button only and it will enter the bootloader.
Also, please don't double post.
Click to expand...
Click to collapse
not sure if it is locked or not. its says following at bootloader screen
It says
PM2330002 P S
SBL1-001.532.008
SBL2-001.532.009
SBL3-001.532.010
TZ-001.532.015
UEFI-0.0.1532.20(157404)
OS-1.00.502.12
eMMC HNX 7400MB F-81
CID-CWS__001
RADIO-1.10.32.19.19_3_15.39.32.19
MSM8960 v3.1-p3 0x406b50e1
Krait::Fast Q6:Fast VDDCX:Slow 0x30c00
Touch FWS1:1195017,13106,41434467
Vdd_dig - 0.5v, 0x4

WPMan said:
Enter bootloader and flash with RUU.
Click to expand...
Click to collapse
anyway you can tell me which file specifically?
Is it RUU_ACCORD_U_APO_00_HTC_Europe_2.00.401.03_1.11b32.19.23_2_15.42.32_RETAIL_ENC_RELEASE
?
Are you sure this is the right file for this phone?

prophets212 said:
anyway you can tell me which file specifically?
Is it RUU_ACCORD_U_APO_00_HTC_Europe_2.00.401.03_1.11b32.19.23_2_15.42.32_RETAIL_ENC_RELEASE
?
Are you sure this is the right file for this phone?
Click to expand...
Click to collapse
Yes that is correct. You can find the link on the RUU thread, on the last few pages I think.

Is it fixed
Did you fix it? Having the same issue.
Thanks.

Hey! I'm have the same situation as you! I've been trying to see what I can do with a demo 8X as well. I'm going to try to do what WPMan said to do and tell you what happens.
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
Ok, so, I had an issue. I put the phone into bootloader mode, plugged it up to my computer, ran the RUU_ACCORD_U_APO_00_HTC_Europe_2.00.401.03_1.11b.32.19.23_2_15.42.32_RETAIL_ENC_RELEASE file, but I get this error.
"ERROR [244] : INVALID MODEL ID"
I should also mention that my bootloader screen shows some different information than prophets212 does.
Here's what it says:
PM2322002 P S
SBL1-001.532.008
SBL2-001.532.009
SBL3-001.532.010
TZ-001.532.015
UEFI-0.0.1532.20(156382)
OS-1.00.531.06
eMMC SMS 14910MB F-15
CID-T-MOB010
RADIO-1.10.32.19.19_3_15.39.32.19
MSM8260A v3.2.1-p1 0x707910e1
Krait:Fast Q6:Fast VDDCX:Slow 0x30c00
Touch FWS1:1195017,13106,41434467
Vdd_dig - 0.5v, 0x4
Anyone have any ideas as to what I should do now?
Thanks for help in advance!

prophets212 said:
Some guy on Craigslist sold my not-very-smart sister an HTC 8X Windows Phone 8 for $250. After playing with it for 2 mins she did not realize that it is locked in demo (store) mode and probably stolen from a store. I've no idea to be honest. But she is out $250 w/ this demo mode phone and asking me to try to fix it.
I would like to try to flash this demo mode HTC 8X phone into a regular AT&T windows 8 phone or unlocked windows 8 phone.
I previously flashed a Windows 7.0 Samsung Focus phone w/ Mango through the wonderful instructions on this forum. I'm tempted to try it again, but I would appreciate any guidance on:
1. Finding the right ROM for a HTC 8X phone. It says:
OS version: 8.0.9905.12
Firmware revision: 1532.20.10012.502
Hardware revision number: 0002
PM23300 on the back.
I'm based in the US. Again, it is an 8X HTC in demo mode. I've no idea if it is security locked. Or how to even tell if it is security locked.
2. Basic instructions on how to flash it. I am intelligent enough to have gone from 7.0 Nodo phone to Mango w/ no issues following instructions on here. But I don't code (at least for the last 7-8 yrs)...
3. Any add'l steps, risks, cautions, caveats, etc. I should consider. Should I just not even bother w/ this phone, because I don't want to be responsible for bricking it... (ie. try to sell it on Ebay and recover some $)
Any help would be really appreciated! Thx.
Click to expand...
Click to collapse
Dear Member...
Mine HTC 8X has CID-11111111.
After following forum, i tried to debrand the 8X.
Before trying to debrand, i did hard reset by pressing Vol - & Power On and then Vol +,Vol -,Power Button & Vol -.
Now the phone is not in demo mode. It looks like retail phone. No need to debrand the phone.
Thanks to the forum............

Cant unlock bootloader on refurbished pixel 2

I recently bought a refurbished pixel 2 from a phone repair shop and i went through the process to unlock the bootloader, enabling dev options, enabling oem unlocking and usb debugging, ect. but when i boot into the bootloader and run
Code:
fastboot flashing unlock
, it throws an error
Code:
FAILED (remote: 'Flashing Unlock is not allowed')
fastboot: error: Command failed
but when i run fastboot flashing get_unlock_ability it returns
Code:
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total time: 0.000s
result of 'adb shell getprop sys.oem_unlock_allowed' is 1
result of 'adb shell getprop ro.boot.cid' is 00000000
im running linux and ive tried running the command as sudo and just launching a root terminal to no avail. If anyone can help, it would be very much appreciated
EDIT: Now im even a bit more confused. i ran
Code:
fastboot oem device_info
and it returns
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
[B](bootloader) Device critical unlocked: true[/B]
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
so if critical is unlocked why cant i just unlock the bootloader?

How do you know that the pixel was refurbished? I bought one (as new) as well but I fear that it might be refurbished. Is there something to look up in order to check that?

N5X_ita said:
How do you know that the pixel was refurbished? I bought one (as new) as well but I fear that it might be refurbished. Is there something to look up in order to check that?
Click to expand...
Click to collapse
any phone this old listed as new or brand new is 100% refurbished in china using the ****tiest parts and then boxed in a really poor recreation of the stock box and shipped off to a distributor in your country

Any update? Same issue here

maybe you need to use the "oem unlock" command instead of "flashing unlock".

#5
I also have the same problem

is it possible to unlock via some type of APK without PC

I know that the refurbished pixel 2s that Google sends as replacements have locked bootloaders.
Also the Verizon wireless variant of the pixel 2 has a locked bootloader
So it could be that who ever refurbished your device locked the bootloader permanently
Sent from my Pixel 3a XL

I also have the same problem. Reported it to google and they have no solution at this time.
Can I root it with magisk without having to unlock the bootloader first? I know I won't be able to flash twrp to the recovery image though.
If something wen't wrong, could I sideload the last ota and get everything back as long as I can boot to the bootloader?

xp99 said:
I also have the same problem. Reported it to google and they have no solution at this time.
Can I root it with magisk without having to unlock the bootloader first? I know I won't be able to flash twrp to the recovery image though.
If something wen't wrong, could I sideload the last ota and get everything back as long as I can boot to the bootloader?
Click to expand...
Click to collapse
Im fairly certain that you need to have unlocked bootloader to root the phone.
Sent from my Pixel 3a XL

eyeyousee said:
maybe you need to use the "oem unlock" command instead of "flashing unlock".
Click to expand...
Click to collapse
oem unlock gives the same error

I'm just grasping at straws here, but did you try *relocking* the device from the critical_unlock, and the unlocking it with the regular unlock command?

I'm on a Pixel 2 warranty replacement from Google directly. The OEM Unlock option is enabled in developer settings as is USB Debugging. The computer has been authorized by the Pixel.
I'm getting those same errors. It's definitely not a Verizon Wireless phone since it's a Canadian phone sold directly by Google.
I'm guessing there is no workaround for this yet. Why would it be listed as bootloader unlock allowed in developer options yet fail when you go to fastboot flashing unlock?

13kai13 said:
I'm on a Pixel 2 warranty replacement from Google directly. The OEM Unlock option is enabled in developer settings as is USB Debugging. The computer has been authorized by the Pixel.
I'm getting those same errors. It's definitely not a Verizon Wireless phone since it's a Canadian phone sold directly by Google.
I'm guessing there is no workaround for this yet. Why would it be listed as bootloader unlock allowed in developer options yet fail when you go to fastboot flashing unlock?
Click to expand...
Click to collapse
maybe there is some sort of failsafe in the kernel that stops it from being bootloader unlocked if a component on the board has been replaced? or maybe google just says "frick you, pay more money if you want root"
but that's just a theory.... A GAY THEORY

Hi I just bought a refurb Pixel 2 on Amazon. When i go to developer options I see the "OEM unlocking" option is completely greyed out. Even after i enabled usb debugging.
Does that mean that my bootloader is impossible to be unlocked? And how is one able to know if they have the Verizon variant?

fc3211 said:
Hi I just bought a refurb Pixel 2 on Amazon. When i go to developer options I see the "OEM unlocking" option is completely greyed out. Even after i enabled usb debugging.
Does that mean that my bootloader is impossible to be unlocked? And how is one able to know if they have the Verizon variant?
Click to expand...
Click to collapse
The refurbished units whether is a Google refurbished or Verizon unit all have locked bootloaders [emoji58]
Sent from my Pixel 3a XL

This is why I regret doing a warranty through Google Fi. I even had it replaced twice. Both times, the bootloader was locked. It appears to be unlock-able, but then this happens.
Does anyone know if this is limited to just the Pixel 2? I never had this problem with the Nexus 5X phones I had.

My Verizon Pixel 3 can get to EDL mode, is there a way to unlock the bootloader?

I can run adb reboot edl, and it works.
from there I don't know what to do, but I would like to unlock the bootloader, but the option is grayed out like it is for all verizon P3s.
I'm on SW version a2.
I can still return the phone, and I will if I can't unlock the bootloader, but it seems no one has figured out how yet, and I was reading that people were trying to get to EDL mode and couldn't. for some reason mine does EDL fine.
Thanks for any input.
other small question, if I return this pixel 3, what should I look for on ebay or elsewhere to find an unlockable P3.
I understand that the imei number that starts with 35 is verizon. what Imei should I look for to find a unlockable p3?

The MEID on my unlocked P3 bought from Google starts with 99.

dcarvil said:
The MEID on my unlocked P3 bought from Google starts with 99.
Click to expand...
Click to collapse
Thank you so much for the info. I'll see if I can track one down.

Question Question about variant XT2131-1

Is this variant to new for rebooting? XT2131-1 bought from bestbuy w/o activation so it's supposed to be unlocked for carrie
I was able to use it on metro/tmoble without issue but cannot seem to get the bootloader unlocked, grayed out
Errors on moto's site for unlocked, not eligible, is it because it's to new?
Eatspizza

eatspizza said:
Is this variant to new for rebooting? XT2131-1 bought from bestbuy w/o activation so it's supposed to be unlocked for carrie
I was able to use it on metro/tmoble without issue but cannot seem to get the bootloader unlocked, grayed out
Errors on moto's site for unlocked, not eligible, is it because it's to new?
Eatspizza
Click to expand...
Click to collapse
It may take 14 days for oem unlocking to be available.
Edit: It should only 3 days for oem unlock to be available after connecting wifi or carrier.

Thank you - I'll give it a go in 24hrs or so
Do you know if any roms off hand are available for my version of stylus? Seems to be different processor then other stylus

eatspizza said:
Thank you - I'll give it a go in 24hrs or so
Click to expand...
Click to collapse
Sorry, it usually only takes 72 hours for oem unlock to work, but the device needs to connect to wifi or carrier.
Which cid does the device have?
Code:
fastboot getvar all
Look for this line
Code:
(bootloader) cid:

sd_shadow said:
Sorry, it usually only takes 72 hours for oem unlock to work, but the device needs to connect to wifi or carrier.
Which did does the device have?
Code:
fastboot getvar all
Look for this line
Code:
(bootloader) cid:
Click to expand...
Click to collapse
Right now, It's on WiFi and I got it on MetroPCS network.
Not even 5hrs since I got it online through metro and my home wireless.
I'll check it in 72hrs and let you know if it doesn't work
It is a pretty nice phone for $400! Great internal storage, 256GB though I got 256GB sd card and 6gb ram, 2 more then my G7

sd_shadow said:
Sorry, it usually only takes 72 hours for oem unlock to work, but the device needs to connect to wifi or carrier.
Which cid does the device have?
Code:
fastboot getvar all
Look for this line
Code:
(bootloader) cid:
Click to expand...
Click to collapse
72 hours passed but still cannot unlock
Here is the cid from bootloader you mentioned in earlier post
(bootloader) cid: 0x0032

eatspizza said:
72 hours passed but still cannot unlock
Here is the cid from bootloader you mentioned in earlier post
(bootloader) cid: 0x0032
Click to expand...
Click to collapse
Cid should be good,
You could try a factory reset, and reconnect to internet.
Or contact Motorola

sd_shadow said:
Cid should be good,
You could try a factory reset, and reconnect to internet.
Or contact Motorola
Click to expand...
Click to collapse
Thanks - I've posted in there forum and will see what they say.
My G7 was also cid 32 and could unlock after 72hrs so we'll see about this one soon enough

sd_shadow said:
Cid should be good,
You could try a factory reset, and reconnect to internet.
Or contact Motorola
Click to expand...
Click to collapse
OEM Unlocked now - so to find some ROMs

eatspizza said:
OEM Unlocked now - so to find some ROMs
Click to expand...
Click to collapse
Good, did you factory reset?

sd_shadow said:
Good, did you factory reset?
Click to expand...
Click to collapse
I had not - I randomly checked the oem lock in developer options and it was available so i did the bootloader unlock.
Also got it rooted by getting the boot img file from LMSA and patching with magisk then running the patched boot in bootloader.
No ROMs seen at this moment to try/test.

Same boat, hopefully we get some roms soon.
This is the subsection for the 5G (XT2131-1, and probably a few more) version of the Moto G Stylus 2021, make sure to keep an eye in both subsections.

eatspizza said:
Is this variant to new for rebooting? XT2131-1 bought from bestbuy w/o activation so it's supposed to be unlocked for carrie
I was able to use it on metro/tmoble without issue but cannot seem to get the bootloader unlocked, grayed out
Errors on moto's site for unlocked, not eligible, is it because it's to new?
Eatspizza
Click to expand...
Click to collapse
I'm having the same issue

[Help] Bricked phone stuck in bootloop

I have an old Asus Zenfone 4 that randomly got stuck in a boot loop while it was recharging, and now I don't know how to fix it, or even if it is possible to fix. The only thing that still works is fastboot mode (recovery mode doesn't work either, so SD cards are out of question).
I have tried a number of things to factory reset the phone and see if it changes anything, but it seems impossible to unlock its partitions for flashing: commands such as fastboot flashing unlock, fastboot oem asus-go or anything similar just throw errors saying that the command doesn't exist, or if it does, that I don't have permission to run them. For this same reason, I couldn't use things such as TWRP as I can't flash any of the partitions on my phone. Additionally, I have tried to enable adb through fastboot oem, but even though the command is successful, whenever I get the system info, it says that adb debugging is still off.
Does anyone know a way to either unlock this device or factory reset it without unlocking?

Another old-ish device killed by the silent OTA update of the OEM!
The deadly mistake of connecting an old-ish device to OEM servers for fresh install.

Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.

OldNoobOne said:
Check with unauthorized service centers who have <Miracle Box> if they can flash with fastboot. Or authorized service centers might charge but they could revive the device.
Click to expand...
Click to collapse
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.

rafk12 said:
By what you are saying... Is it actually impossible for me to unlock the bootloader? I have no problem with service centers, but it would be much better and quicker if there was was a way for me to unlock it.
Click to expand...
Click to collapse
I threw away two old chaina phones just because I made the mistake of reflashing the original OS and tried to update from OEM servers..BOOM! Dead Phone!
The moment OEM servers detect an old device connected to their servers for an update, they kill the device so that new devices can be sold in the market, why would this happen to a device which was working perfectly under a Custom ROM before? I dont update the device from OEM channelsbecause OEM might try to kill the device after warranty period, instead I update through the Custom ROM channel.

Maybe some chip got fried while charging the device, among the asian brands shamshung & WonPlus have durable components but other asian brands maximum 4 years before the components like display etc. or even the chipset components begin to fail. Or it could be the OEM update thing too