Related
Hi All,
I have a non-DE XT1060 with an unlocked bootloader. I am attempting to flash a custom recovery, but I am running into issues. When I go into fastboot, it shows the device is indeed unlocked, but says Status Code: 3, where it would normally say Status Code: 1.
I am guessing this is part of my issue, since when I run the command ADB DEVICES, my device does not appear on the list. However, when I run the command ADB FASTBOOT DEVICES, it will list my device out. Because of this, I am having trouble flashing a custom recovery and obtaining root.
If anyone knows what Status Code: 3 actually means or has other ideas what might be going on, I would appreciate your help. I did a fair amount of searching online already, but nothing seemed quite the same as the issue I was having. Thanks in advance for any help.
I recently unlocked my device with the same status code 3 and had difficulties flashing the recovery also... In the android development section theres a post called recovery unlocked they mention that the correct command to flash would be mfastboot instead of fastboot (i guess its a motorola thing) also Adb commands don't run while in fastboot...
I think I had a misunderstanding of what fastboot was, but your reply prompted me to read more and I get it now. That being said, when I attempt to flash the recovery via fastboot, I receive the error: (bootloader) Variable not supported!
For the record, it does respond to commands such as fastboot devices and fastboot reboot-bootloader
Never had that outcome but having the latest adb/fastboot files would make things easier... If it still occurs
Is your command prompt path correct to the same folder as your recovery.img and your fastboot and mfastboot.exe files?
Yeah, you beat me to it... I had the directory wrong... needed C:\adb\
D'oh!! Thanks for your help though.
i have status 3 its normal or not ?
Apparently its normal as it all worked fine for me once I had the correct directory.
JustROLLIN said:
Apparently its normal as it all worked fine for me once I had the correct directory.
Click to expand...
Click to collapse
sure ? all have unlock bootloader have status 3 ?
maxou88 said:
sure ? all have unlock bootloader have status 3 ?
Click to expand...
Click to collapse
Status code 3 is perfectly normal and it indicates an unlocked bootloader in the case of the moto x. Nothing to worry about there. Every unlocked moto x displays status code 3. :good:
Oh ok thx my friend
my phone MOTO E stucks on warning bootloader unclocked.....plz help me...????
while doing fastboot its shows its not recognized by internal or external command...
samwathegreat said:
Status code 3 is perfectly normal and it indicates an unlocked bootloader in the case of the moto x. Nothing to worry about there. Every unlocked moto x displays status code 3. :good:
Click to expand...
Click to collapse
If you relock the bootloader will the status code change and will the software status change from modified to whatever it says before it was unlocked?
HELP please
mine is the moto g turbo edition XT1557 running marshmellow 6.0
and i unlocked the bootlocker status code 3
while trying to boot the phone it vibrates once and gets stuck on the "warning boot locker unlocked screen"
tried the logo thing, the wipe data thing. Noting is working can anyone help me ???
Q&A for [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
MotoX Pure - UnRoot To Update Firmware
I used the Jcase method (fastboot boot pure2014sb.img) to root my new MotoX Pure. Worked great. However, the next day I received a notification on the phone that a firmware update is available: "New FIrmware Available" "Update to get the lastest Motorola Sensor. . ."
Because this method uses fastboot boot vs fastboot flash, I don't understand how I can go back to stock in order to update firmware.
Wondering if someone could school me on what the heck it actually means to fastboot boot vs fastboot flash. Basically looking for a way to be able to un-root, apply firmware update, and then re-root.
A
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
tyea said:
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
if they said they would, then i'm glad. getting worried here lol
root moto x 2014 followed by ota lollipop update
The moto x is delivered with KitKat initially and then updated via ota later once powered up etc. If I follow your method as soon as I get the phone and then later accept the ota update to lollipop, will it cause problems or lose root?
bootloop
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
deelv said:
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
Click to expand...
Click to collapse
The same thing happened to me but I've gotten out of the boot loop by getting to fastboot (hold down the power button till the screen turns off and then you have to guess and hold the power and volume down button for about 5 seconds and then release the power button but hold down the volume button until you see the fastboot. If it doesn't get to fastboot try it again.)
When you're at the fastboot, connect to a computer and cmd a command "fastboot erase userdata" and then "fastboot erase cache" to pretty much factory reset and get you out of the boot loop. Then it should boot and tell you to set up the device.
I would recommend looking for the root boot image from chainfire them self, they recently released it. Just look for your model # (e.g. xt1095) and "fastboot boot (insert boot image)"
My Moto x 2014 is currently rooted with chainfire's boot image. It works like a charm.
XT1092 bootloop after OTA
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
HamRack said:
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
Click to expand...
Click to collapse
Boot this boot.img : http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Its for xt1095 but some have confirmed working on xt1092
Sent from my Moto X 2014 Pure Edition
does it work on Android 5.0?
Yes, I'm currently running Android 5.0 Lollipop.
Sent from my Moto X 2014 Pure Edition
Bootloop
Stuck in a bootloop. Followed all your instructions carefully. :/ Not able to boot into bootloader.
Formatted Telus Moto X (2014) SD card and all data ... recovered.
I might make a tutorial video on how to recover from a mistake like mine, and I may not have done it correctly, but the phone is back operational.
What I did to screw it up :
1) Unlocked the bootloader and installed TWRP without doing research about development for the phone
2) The phone is already almost stock android and that's one of it's selling points so I don't know why I wanted to unlock and root
3) Got frustrated and wiped / formatted internal SD ... since I use to flash ROM's on my older Huawei this way ... it must be the same right ... smh.
4) Freaked the eff out, had thoughts of just running it over with the car because that qualifies under my 2-year warranty, since I voided it by unlocking.
5) Thought I knew it all when I really don't understand most of the lingo still
What I did to 'TRY' to fix it :
1) Scoured the internet for ROMS / Zips.
2) I was in 'Android Studio' ... unnecessary.
3) Tried flashing .zips in TWRP by draggin and dropping .zips ... contanst 'FAILED' signs.
4) Tried sideloading as I was grasping at straws by this point. 'FAILED'
5) Considered buying an OTG cable.
6) Spent hours going in circles
What I did to fix it :
1) Downloaded the SDK ... 'adt-bundle-windows-x86_64-20140702'
2) Installed the 'Google USB drivers' as I checked 'Device Manager' and there was an exclamation ... this is why when I went typed 'ADB devices' nothing showed up. I 'manually' installed the drivers. VOILA, first step.
3) Found a .ZIP file I believe was the correct one ... ;RETCA_XT1097_4.4.4_KXE21.187-42_cid14_CFC.xml.zip' (From this website I believe)
4) Watched a few youtube tutorials on how to flash from within 'SDK' > 'Platform-Tools'
5) Extracted the .ZIP file into 'Platform-Tools'
6) Had phone booted into fastboot mode
7) Opened the CMD from within 'Platform-Tools' with that .ZIP file within that folder, held 'SHIFT' 'Right-click" > 'Run CMD'
8) This is where I didn't do it properly, but the phone is booted for now and working ... with these Commands
- fastboot flash boot boot.img;
- fastboot.exe flash system system.img_sparsechunk.0
- fastboot.exe flash system system.img_sparsechunk.1
- fastboot.exe flash system system.img_sparsechunk.2
- fastboot.exe flash system system.img_sparsechunk.3
- fastboot.exe flash system system.img_sparsechunk.4
Got that nice Motorola earth screen and booted to the welcome screen. Froze. I reset. Froze. Walked away from phone, came back and tried to see if I could press 'OK' and it worked.
All-in-All , not worth it for the average consumer and not worth it for someone such as myself who was stupid and just wanted to 'play around' with a brand new 2-year warrantied $500 phone.
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.
Have the same problem and try to solve it with Motorola. No luck at the moment.
lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot
simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.
rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).
You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.
beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...
You're all using the newest fastboot?
flash the factory img
edit.. nevermind, i see ive already said that
Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.
Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.
Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking
toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.
You don't need adb.
sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)
Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?
jewnersey said:
Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?
Click to expand...
Click to collapse
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?
Evolution_Freak said:
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?
Click to expand...
Click to collapse
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
just saw your thread.. ugh
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Glad you're OK. :good:
jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Good job:good: