Database Info

How to unlock bootloader

How I have a Droid RAZR Maxx HD 9.16.6xt926 android 4.1.2 build number 9.8.1Q-62VQW-MR-2. Last night I rooted my phone at least I think I did because the superuser is in my apps screen and I ran a app that read my phone is rooted I But when I shut phone off and go into recovery it days my bootloader is locked Does anyone have a ideal to unlock this??? Also does that mean I cant install custom room???

monkeyjjk said:
How I have a Droid RAZR Maxx HD 9.16.6xt926 android 4.1.2 build number 9.8.1Q-62VQW-MR-2. Last night I rooted my phone at least I think I did because the superuser is in my apps screen and I ran a app that read my phone is rooted I But when I shut phone off and go into recovery it days my bootloader is locked Does anyone have a ideal to unlock this??? Also does that mean I cant install custom room???
Click to expand...
Click to collapse
there is an option in this tool http://forum.xda-developers.com/showthread.php?t=2307439 to unlock your boot loader. it is a good all around tool to have on hand.

bweN diorD said:
there is an option in this tool http://forum.xda-developers.com/showthread.php?t=2307439 to unlock your boot loader. it is a good all around tool to have on hand.
Click to expand...
Click to collapse
I used that tool last night to root it went through right but when I tried to unlock the bootloader it wouldn't work and my phone said its still locked. Any I deals????

monkeyjjk said:
I used that tool last night to root it went through right but when I tried to unlock the bootloader it wouldn't work and my phone said its still locked. Any I deals????
Click to expand...
Click to collapse
can you post a screenshot of your "about phone" screen from the settings menu plz.

Sent from my DROID RAZR HD using xda app-developers app

See my phone says root but can't get my boot loader unlocked
Sent from my DROID RAZR HD using xda app-developers app

Do you kmow link to unlock the bootloader
Sent from my DROID RAZR HD using xda app-developers app

monkeyjjk said:
Do you kmow link to unlock the bootloader
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
i dont rely on those root checkers, download an app that needs root and make sure it gets granted. also go into the settings of su and make sure the binaries are up to date, they usually are not. after that try the unlock tool again, im betting you have outdated binaries.

monkeyjjk said:
Do you kmow link to unlock the bootloader
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
I believe the utility dowloads an .apk that you have to open to get the bootloader unlocked. When I unlocked the BL on my M, I just used the stand-alone Motopocalypse tool.
http://wiki.cyanogenmod.org/w/Template:Motopocalypse

RikRong said:
I believe the utility dowloads an .apk that you have to open to get the bootloader unlocked. When I unlocked the BL on my M, I just used the stand-alone Motopocalypse tool.
http://wiki.cyanogenmod.org/w/Template:Motopocalypse
Click to expand...
Click to collapse
i should have known this lol
"This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader."
thx

bweN diorD said:
i should have known this lol
"This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader."
thx
Click to expand...
Click to collapse
I've tried that link and did what it told me to do went through the steps and at the end the phone shows its still locked. By any chance this phone is refurbish phone could this be the reason why it won't unlocked

bweN diorD said:
i should have known this lol
"This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader."
thx
Click to expand...
Click to collapse
Your screenshot shows that you are not on the latest update, so you should be able to unlock it, unless someone already had previously updated it then rolled back to that version. However, that version is 2 OTAs ago, so I would think it has never been updated. When I ran the stand alone Apocalyse utility, I had to run it about five times. Finally, during the last (and successful) try, I decided to wake up the phone. When I did this, there was a screen from my SuperSU asking to grant SU access to ADB. I granted it and the utility completed immediately and I was finally unlocked. When you run the Motopocalypse utility, you need to be booted into the OS.

What apocalypse utility link you rooted with do you have one. I have no luck with this . I able to wipe the phone install root but can't unlock the boot loader. So I gave up and figure out how to take root out and go back to stock. I give up unless someone else ideal how to do it.
Sent from my DROID RAZR HD using xda app-developers app

monkeyjjk said:
What apocalypse utility link you rooted with do you have one. I have no luck with this . I able to wipe the phone install root but can't unlock the boot loader. So I gave up and figure out how to take root out and go back to stock. I give up unless someone else ideal how to do it.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
if you are on the latest update the unlock tool does not work and there is no way to unlock.

hiii
hi ..im new in XDA..
my phone is XT926 and rooted.. i wanna upgrade it to android 4.4.2 or 5.0
in past 3days worked in this & tried Motopocalypse & motorola site for unlocking bootloader but i didnt reach any success!!!
is unlocking bootloader necessary to upgrade android? and is there another way to unlocking?
i will be thanksfull if some one help me

amirka28 said:
hi ..im new in XDA..
my phone is XT926 and rooted.. i wanna upgrade it to android 4.4.2 or 5.0
in past 3days worked in this & tried Motopocalypse & motorola site for unlocking bootloader but i didnt reach any success!!!
is unlocking bootloader necessary to upgrade android? and is there another way to unlocking?
i will be thanksfull if some one help me
Click to expand...
Click to collapse
1. Please use the search function in the forums; your questions have been answered literally hundreds of times.
2. Please read the post immediately above yours, and in fact, some or all of the posts in any thread, before adding your post to it.
3. If you have a question that really hasn't been answered elsewhere, after searching, please don't post the identical question in more than one place, especially in threads that don't have anything to do with your question (like you did in the other thread).

Unlocked my bootloader for nothing

Peace be upon everybody, and good morning/evening
Last night I remained using my PC for a whopping 9 hours of work to figure out how to unlock my E6633 bootloader - and I finally figured it out.
The whole process was bumpy and the Sony Mobile Developers tutorial didn't wholly work out, but it had some vital info for the process. I had to unlock the boot loader using the Flashtool (thankfully), and I had some lack of luck at the beginning, which involved a journey to find the lost driver for my Z5, and to install it in the Device Manager (took some time). And then I took a "detour", since facing another roadblock, by creating a folder in C:\Users\<User>\.flashTool\registeredDevices named by my devices code (that appears when you enter adb devices in cmd), then inside of that folder I've created a .txt named ulcode.txt which contains the serial code provided by Sony Mobile to unlock your boot loader. And I've gotta tell you, it was all a pain in the bass.
More frustratingly, this whole procedure has resulted in zero luck with rooting the goddamn device (thanks Sony), and now I'm stuck with an unrooted bootloader-unlocked device . I'm sure this requires taking another detour. I've failed in every way I know to flash the modified stock kernel for some reason. I've tried cmd to flash the kernel and it comes back with FAILED <Remote: command not allowed>. I've also tried Flashtool to root it directly, and it turned out to be non-working as well.
Now, I'm not going to complain about this whole situation, even though I'm recalling how easy rooting my good old Galaxy S3 was. I'm now looking for a solution for that last tiny bit of the puzzle, and I'm sure there are other fellow members who are facing the same hitch.
Cheers .

Is oem unlocking ticked? It sounds like your bootloader is still locked.
All I did to unlock mine was type the command Sony provided with the unlock code and unlocked it with fastboot, took maybe 10 seconds?
Sent from my E6653 using Tapatalk

After unlocking the bootloader does the phone reset to factory settings? Just to make sure that you succeed unlocking.

Go to developer options and check if oem unlock is ticked

This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.

bishshoy said:
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
Click to expand...
Click to collapse
Then buy a Samsung...
Sent from my E6653 using XDA Free mobile app

Everything is explained here

celderic said:
Is oem unlocking ticked? It sounds like your bootloader is still locked.
All I did to unlock mine was type the command Sony provided with the unlock code and unlocked it with fastboot, took maybe 10 seconds?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
It is indeed ticked and I'm positive that the bootloader is unlocked.
Yes I tried the easy way of doing it with cmd but it just didn't work out. Kept returning with FAILED <Remote: command did not succeed> and that's why I resorted to the other way of creating those files in the flashtool folders (as explained in the OP).
gm007 said:
After unlocking the bootloader does the phone reset to factory settings? Just to make sure that you succeed unlocking.
Click to expand...
Click to collapse
It didn't reset to factory settings. Does that mean it wan't unlocked?
dylanel98 said:
Go to developer options and check if oem unlock is ticked
Click to expand...
Click to collapse
It is ticked along with debugging just in case.
bishshoy said:
This difference in rooting experience that the OP had with the GS3 and now with the Z5 raises a question in my mind. Is the modding community more focused on popular devices? This is often a deal breaker for some people. If the 6P or the GS6 gets more ROMs and mods and faster root exploits than the Z5, then I myself would prefer those devices over the Z5.
Click to expand...
Click to collapse
I think maybe the developers at Sony are narrowing down the possibility of modifying their devices.
Funkmasterchilla said:
Everything is explained here
Click to expand...
Click to collapse
Checking it out...

Funkmasterchilla said:
Everything is explained here
Click to expand...
Click to collapse
I went through the steps in that thread and without any problems until the part with
Code:
fastboot –i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXX
I have checked the recognition of my device by entering fastboot devices and it recognized my device successfully.
The X's above being the code provided by Sony, the cmd window (of minimal adb and fastboot) returned with
Code:
FAILED (remote: Command did not succeed)
Although, the step prior to this one which is to unlock the bootloader using Flashtool has succeeded.
It's really mind-boggling...

As far as i know that unlocking bootloader will reset ur phone to factory settings.
And not sure but i think you need to remove a number from the code sony sent to you.

Take a look here: http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
Bootloader unlock is under # STEP 1 - GENERAL GUIDE
I hope this will help

Also check if you're bootloader is allowed to be unlocked.

Type in dialer *#*#7378423#*#* (*#*#SERVICE#*#*)
Service info > configuration > rooting status.
If it says bootloader unlock allowed :YES you can unlock it, if it says NO u can't unlock it.
If it says rooted or unlocked, you've successfully unlocked it already.

UM, I have E6633 and everything works fine... I used flashtool to unlock bootloader.

langeveld024 said:
Type in dialer *#*#7378423#*#* (*#*#SERVICE#*#*)
Service info > configuration > rooting status.
If it says bootloader unlock allowed :YES you can unlock it, if it says NO u can't unlock it.
If it says rooted or unlocked, you've successfully unlocked it already.
Click to expand...
Click to collapse
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk

mrbubba999 said:
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Yes you cannot unlock bootloader.
I think you have branded phone,locked by carrier.

mrbubba999 said:
Mine says no to unlock, does that mean it can never be unlocked? If so, why would that be?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Carrier lock, unfortunately as far as I know since the very first Z series impossible to unlock unless u contact the carrier and they unlock it for u.
Keep in mind that they might charge u for that.

langeveld024 said:
Carrier lock, unfortunately as far as I know since the very first Z series impossible to unlock unless u contact the carrier and they unlock it for u.
Keep in mind that they might charge u for that.
Click to expand...
Click to collapse
That sucks, means my foray into Sony phone ownership might be short lived! Perhaps I should have stuck with a nexus and got the upgrade and a 6P
Sent from my E6653 using Tapatalk

mrbubba999 said:
That sucks, means my foray into Sony phone ownership might be short lived! Perhaps I should have stuck with a nexus and got the upgrade and a 6P
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
Yeah or next time only buy carrier free Sony

Thank you all, guys! I tried everything you told me but guess what! Nothing worked unfortunately...

Error message with Windroid 3.1 in getting unlock code, any welcome please.

Using Windroid 3.1 to unlock moto g 2015 osprey, drivers installed and works perfectly on wife phone. On trying to unlock my phone i get error message.
Houston, we have a problem
An error has occured! a log file has been placed in the Logs folder.
The same error occurs whether oem locking is on or not. Also i am having communication fails when using fastboot, yet the phone is recognised and read to but not written.
Where would i find this log file please and any help offered i would be grateful.

bantamroberts said:
Using Windroid 3.1 to unlock moto g 2015 osprey, drivers installed and works perfectly on wife phone. On trying to unlock my phone i get error message.
Houston, we have a problem
An error has occured! a log file has been placed in the Logs folder.
The same error occurs whether oem locking is on or not. Also i am having communication fails when using fastboot, yet the phone is recognised and read to but not written.
Where would i find this log file please and any help offered i would be grateful.
Click to expand...
Click to collapse
Try adb and fastboot instead of Windroid

As I tried to explain in my post , this is not possible as the phone will not write the data sent. Thinking this is why windroid returns an error.

bantamroberts said:
As I tried to explain in my post , this is not possible as the phone will not write the data sent. Thinking this is why windroid returns an error.
Click to expand...
Click to collapse
Did you enable OEM Unlocking the Developer Options menu? Still required...
I would also recommend doing it manually, the commands are easy and the process is simple... if something goes wrong you can see exactly what fails. Tools like Windroid are not really useful for simple tasks like this.

done oem unlock in developer options but not manually as im unsure how. please elaborate.

bantamroberts said:
done oem unlock in developer options but not manually as im unsure how. please elaborate.
Click to expand...
Click to collapse
Gotta be 50 tutorials on-line, there is only one real, official way...
You need at least fastboot (you can get it from Minimal ADB & Fastboot)
Then follow the Moto official method which even using a tool you have to go through anyway to get the tokem

acejavelin said:
Gotta be 50 tutorials on-line, there is only one real, official way...
You need at least fastboot (you can get it from Minimal ADB & Fastboot)
Then follow the Moto official method which even using a tool you have to go through anyway to get the tokem
Click to expand...
Click to collapse
Done this, error message failed to get unlock data. remote failure.

bantamroberts said:
Done this, error message failed to get unlock data. remote failure.
Click to expand...
Click to collapse
So you have OEM Unlocking enabled in Developer Options and fastboot is still complaining?
What model and variant? Is this a carrier locked phone or a Moto retail version?
Sent from my MotoG3 using Tapatalk

acejavelin said:
So you have OEM Unlocking enabled in Developer Options and fastboot is still complaining?
What model and variant? Is this a carrier locked phone or a Moto retail version?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
its a xt1541 on tesco mobile and unlocked with sim code.

How to root Cricket Wireless Alcatel Idol 4?

Hello! I've been searching the net far and wide for a way to root my Alcatel idol 4. Its the cricket model. I was able to unlock the boot loader and turn on USB debugging but besides that I haven't had any luck rooting my device.
Has anyone tried and has success or know any methods that could work?
Thank you!

jinxxie said:
Hello! I've been searching the net far and wide for a way to root my Alcatel idol 4. Its the cricket model. I was able to unlock the boot loader and turn on USB debugging but besides that I haven't had any luck rooting my device.
Has anyone tried and has success or know any methods that could work?
Thank you!
Click to expand...
Click to collapse
How did you unlock the bootloader? I'm not able to do it. Fastboot doesn't see the phone when I boot to bootloader.

Chief_Nodnarb said:
How did you unlock the bootloader? I'm not able to do it. Fastboot doesn't see the phone when I boot to bootloader.
Click to expand...
Click to collapse
It's in the developer options called "OEM unlocking" 5th option down from the top.

apb91781 said:
It's in the developer options called "OEM unlocking" 5th option down from the top.
Click to expand...
Click to collapse
That's been done since I got the phone. Still doesn't make a difference, fast boot commands have been stripped from this phone.

Chief_Nodnarb said:
That's been done since I got the phone. Still doesn't make a difference, fast boot commands have been stripped from this phone.
Click to expand...
Click to collapse
try this SETTINGS>BACKUP AND RESET>DEVICE RESET. this will restore all settings to default state while keeping dev-ops and all apps and data

Sorry if I'm speaking out of turn, as I'm not highly experienced...>BUT, I went thru what your referring to with my OnePlus phone. The option in the developer options that says "OEM Unlocking" for bootloader is nothing more than an option in the Android system that allows the bootloader to be unlocked should the mfg allow it. Whether this is on/off makes no difference for this being unlocked. It just has to be turned on for the unlocking to work. I had this Idol 4 for a short time but returned it due to the fastboot commands being removed.

OEM Unlocking issue [SOLVED]

I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.

Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170

depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.

Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?

depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?

rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.

geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net