Related
I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.
UberSprode said:
I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.
Click to expand...
Click to collapse
You know there's a way to unlock your bootloader for $43ish. Many success stories. Your phone playing life would improve greatly.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Hi friends,
I have just bought Moto G 2nd generation smart phone with 16 gb internal memory. To root device, I tried to unlock bootloader. But it didn't go smooth. When I hit command fastboot oem unlock <key>, I got success message with status Device unlocked. Status 3.
But what the heck this status 3?. I am not getting any info about this.
Google search is showing that, at time of unlocking bootloader, few messages are shown like 'unlocked' then 'restarted' and device restarts. But this didn't happen with me. So I manually restarted my device for custom recovery. And flashed rom using TWRP2.7.1.1-titan-motog-2014. This command also showed me success message. Before this I copied UPDATE-SuperSU-v2.02.zip in device.
But after restarting and hitting recovery, device is not showing any thing and just black screen and then turning off.
Apart from this device is working fine, with normal boot.
P.S. RootChecker is showing that Root access is not properly installed on this device.
So what is the way out to root the device again properly?
Thanks in advance.
zoozope said:
Hi friends,
I have just bought Moto G 2nd generation smart phone with 16 gb internal memory. To root device, I tried to unlock bootloader. But it didn't go smooth. When I hit command fastboot oem unlock <key>, I got success message with status Device unlocked. Status 3.
But what the heck this status 3?. I am not getting any info about this.
Google search is showing that, at time of unlocking bootloader, few messages are shown like 'unlocked' then 'restarted' and device restarts. But this didn't happen with me. So I manually restarted my device for custom recovery. And flashed rom using TWRP2.7.1.1-titan-motog-2014. This command also showed me success message. Before this I copied UPDATE-SuperSU-v2.02.zip in device.
But after restarting and hitting recovery, device is not showing any thing and just black screen and then turning off.
Apart from this device is working fine, with normal boot.
P.S. RootChecker is showing that Root access is not properly installed on this device.
So what is the way out to root the device again properly?
Thanks in advance.
Click to expand...
Click to collapse
Status=0 is Locked never been unlocked
Status=2 is relocked HAS been unlocked
status=3 is UNLOCKED
you will never get status 0 back its a once only condition (some says a poly fuse blows- i personally think it's more a case of write once memory has a marked added, and thus cant be reverted back)
but dont worry there is no need to relock boot loader to 2 (as 2 and 3 both void warranty)
Boot loader lock or unlock has NO relation to being able to receive OTA updates or installing them.
TWRP is now 2.8.40 for moto g 2014 use search
super su is now 2.45 again search
So here is what happened...
my phone was running krypton 1.4.1 (4.4.4) rom. i decided to try a cm12 rom. the cm12 rom was bootlooping so i decided to go back and restore a nandroid. however my phone was encrypted on the 4.4.4 rom and when i went back into twrp and it asked for my password before the nandroid, it said wrong password. i was basically locked out and couldnt nandroid restore.
i then did some readying to try to push the rom adb but that wouldnt work. so i did a user erasedata to get rid of the encryption (it worked). so then i tried multiple different things for adb and fastboot to try to fix it. my device would not show up in adb so i tried to reinstall drivers. they installed but my phone will still not show in adb.
at this point it just bootloops at the twrp screen or i can just have it sit at bootloader....
does anyone have the xt1060 4.4.4 sbf? all the links do not have it anymore.
thanks
Check Motorola's website
Skeetch79 said:
Check Motorola's website
Click to expand...
Click to collapse
they dont have the sbf. i downloaded the whole zip from them already. they just have the file for adb. i cannot get adb working since phone is messed
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images download the right one for your device and use this to sbf
Skeetch79 said:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images download the right one for your device and use this to sbf
Click to expand...
Click to collapse
oh ok this is what i downloaded from them. i didnt see an sbf file in it though. is the whole package considered the sbf?
I think this is only OTA, but it's the only thing I could find..
http://motofirmware.center/files/file/151-vzw-xt1060-444-kxa2112-l126-cfc-1ffxmlzip/
I'm sure someone has a copy of the SBF that they had downloaded somewhere.
Also refer here: http://www.droidrzr.com/index.php?/topic/61124-House-of-Moto-[4.1]
Use the link to the zip file and the above link to restore your device
Those might be FXZ, but this one appears to have FXZ files too, which should be flashable with RSD Lite: http://www.drdevs.com/devs/FXZ-files/XT1060 (Moto X VZW)/
the problem i have is adb wont detect my device. i think it was because when i flashed cm12 i was not able to boot it up and select debugging even tho i have the drivers installed
fury683 said:
Those might be FXZ, but this one appears to have FXZ files too, which should be flashable with RSD Lite: http://www.drdevs.com/devs/FXZ-files/XT1060 (Moto X VZW)/
Click to expand...
Click to collapse
thanks i got it downloaded. rsd lite wont detect my device though. either will adb.
@sruel3216 Isn't the flashing done through fastboot? Mabually Power off device and the hold power button and volume down for 4 seconds then release both! Connect device while in fast boot to pc.
Once is fast boot and successfully connected to pc with drivers installed and device recognized then start flashing with rsd
Skeetch79 said:
@sruel3216 Isn't the flashing done through fastboot? Mabually Power off device and the hold power button and volume down for 4 seconds then release both! Connect device while in fast boot to pc.
Once is fast boot and successfully connected to pc with drivers installed and device recognized then start flashing with rsd
Click to expand...
Click to collapse
thats whats not working. it wont recognize there is a device through fastboot or adb. it was working today and then once i tried to restore back through twrp it would not let me becuase i needed my password since my phone is encypted. i entered my password and twrp said it was wrong. so people told me to do a user erasedata through adb. it got rid of the encryption but now my phone just bootloops at twrp screen and adb or fastboot or rsd lite cannot see my device...
sruel3216 said:
thats whats not working. it wont recognize there is a device through fastboot or adb. it was working today and then once i tried to restore back through twrp it would not let me becuase i needed my password since my phone is encypted. i entered my password and twrp said it was wrong. so people told me to do a user erasedata through adb. it got rid of the encryption but now my phone just bootloops at twrp screen and adb or fastboot or rsd lite cannot see my device...
Click to expand...
Click to collapse
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
KidJoe said:
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
Click to expand...
Click to collapse
All i can get to is bootloader. however adb and fastboot will not detect my phone is plugged in even when i power off and hold down volume + power.
I cant really get to twrp. all it does is bootloop at the twrp splash screen
I have all drivers, sdk, etc installed on my comp and it worked earlier that day. once i went back from 5.0 rom to 4.4.4 rom, the encryption i had on my phone got all messed up and it got screwed up from there
KidJoe said:
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
Click to expand...
Click to collapse
OMG sir i think you may have saved me!
EDIT: It has booted!!! thank you sir! Will i need to unlock my bootloader again? it is a dev edition
sruel3216 said:
OMG sir i think you may have saved me!
EDIT: It has booted!!! thank you sir! Will i need to unlock my bootloader again? it is a dev edition
Click to expand...
Click to collapse
If you got the unlock code from Moto and used it to unlock your bootloader, then no. You will not need to unlock again. Once the bootloader is unlocked, it will stay unlocked unless YOU relock it (fastboot oem lock), even then, if you have the code from Moto, you could unlock again if you needed to.
If you used a tool like Sunshine to unlock the boootloader, my understanding is that the bootloader will also stay unlocked. However, if you relock it, you wont be able to unlock it again.
KidJoe said:
If you got the unlock code from Moto and used it to unlock your bootloader, then no. You will not need to unlock again. Once the bootloader is unlocked, it will stay unlocked unless YOU relock it (fastboot oem lock), even then, if you have the code from Moto, you could unlock again if you needed to.
If you used a tool like Sunshine to unlock the boootloader, my understanding is that the bootloader will also stay unlocked. However, if you relock it, you wont be able to unlock it again.
Click to expand...
Click to collapse
Sweet got it all rooted again and running. thanks a lot!
So I'm currently running the newest version of Blisspop on my phone. I was at work earlier this evening, and my phone rebooted. However it never came back. Its stuck on the "Warning Bootloader Unlocked" screen. I was able to access fastboot, however whenever I would choose anything it would immediately go right back to the warning screen. Except when I choose recovery. It goes to the recovery splash logo, and freezes there. I don;t know what to do, as I don't have USB Debugging enabled on the device. Is there anything anyone can do to help me? Thanks guys!
Better you flash stock firmware via fastboot mode by PC and take a complete backup of stock ROM before you proceed.
I would, however, I can't enable USB Debugging.
I am from India and I exchanged my iPhone 4S for a Moto X 2014 just this evening wanting to try my hands on the Android experience.
I do not know what the seller did to this phone but I now have two issues. I tried to call the seller immediately after I noticed these problems when I came home but the number is switched off. Shame on him!
After Google'ing I found this forum for android support so I hope posting the problems here would give me some solution
Problem #1: Every time when I boot my phone, it has the warning screen which says "Warning unlocked bootloader".
Problem #2: The warning went off and landed me on the home screen. I connected to my WiFi and saw that there is a software update. I downloaded it and chose to install it. It kept rebooting for 4-5 times and then said "System Update - Failed".
Can anyone please be patient enough to give me step by step solution with download links to get my Moto X2 back in shape as how it was out of the box?
I googled a lot for the keywords "relock bootloader moto x 2014", "unroot moto x 2014" and plenty of links with different download links came up. I do not know which one to trust. I am not dumb and I can easily follow instructions. So, please anyone wanna help?
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Nek0x90 said:
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Click to expand...
Click to collapse
Thank you for the reply. Attached the screenshot.
i64.tinypic.com/2nu3asn.png
I fiddled around to find out how to get into the Fastboot mode... and I observed something weird there..
AP Fastboot Flash Mode (S)
60.16 (sha-#some checksum number key with date 2015-04-02 and time#
CPU: MSM8974AC EA1.1
eMMC: 2048MB Samsung RV=07 PV=0B TY=57
Battery OK
Device i UNLOCKED. Status Code: 3
Software status: Official
I mean Seriously? I see the word Samsung in a Moto phone? I so regret buying from this seller... too much for a first Android phone :crying:
Well I also managed to Google more and installed the device drivers and the Fastboot software in my Windows PC.
Booted my device in fastboot mode and issues the below commands:
fastboot devices
#my device was shown#
fastboot oem lock
#told me to use the command with begin#
fastboot oem lock begin
#Said something like the image is ready#
Nothing happened then though. I powered on my device and I still see that warning. Still the software update is failing. :crying::crying::crying:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Nek0x90 said:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Click to expand...
Click to collapse
I am not trying to unlock my bootloader. I am trying to restore it back to the "out of the box" state. I mean I want to lock it and I want it to be in the state how it usually is when bought from the store.
Ok... I google'd how to go into the recovery mode and found this link (teamandroid.com/2015/01/08/enter-recovery-mode-moto-x/).
I followed those steps:
1. Turn OFF your phone.
2. Press and hold the Volume Down button for 2-5 seconds. While holding the Volume Down button, press the Power Button for 1-2 seconds and release.
3. I used the Volume down key to highlight "Recovery" and clicked on the power button to select it.
4. My screen went off. I mean the light gone.
Then I had to press and hold the power on button, it booted my phone with that warning unlocked bootloader message.
What am I doing wrong?
UPDATE:
I did a fastboot, connected phone to PC and issued the below command from PC and get below error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
UPDATE 2:
I enabled the developers option (by tapping on the Build number multiple times)
So, I installed an app called MobileUncle Tools.
I then opened the app from my mobile and clicked on "Reboot into recover".
It says "Please root your Android first".
OK.. so looks like the phone is not rooted - which is good.
Only the bootloader is unlocked. All I need to figure out is - re-lock my bootloader and make the system update go through successfully.
Any help please?
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Nek0x90 said:
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Click to expand...
Click to collapse
I have one question for you:
What do you mean by "Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery".
My understanding is - you are saying my stock firmware is intact because it said Official in the fastboot screen. Right?
Ok... now back to the recovery check... I think I did it.
1. I went in the fastboot mode
2. Used volume down key to scroll down to Recovery option (2nd option)
3. Pressed Volume up key to select it
4. The phone rebooted (The white screen "warning unlocked bootloader" message was displayed this time too)
5. I saw a dead android symbol with the word "No command."
6. I pressed Power and Volume Up key. I saw the recovery screen I guess. There were many options - Wipe data, Wipe Cache, Install from SD, etc.
What do I need to check there?
EDIT:
Ok I noted this number from there:
Android system recovery <3e>
LPE23.32-25.1
followed by the options
reboot system now
apply update from sdcard
etc.
I think this is what has happened:
Google says "LPE23.32-25.1" is the Android 5.1 Lollipop update (v23.16.1, build LPE23.32-25.1)
However, the current Android version on my device "About" screen is 4.4.4
The OTA system update, my device telling me about is Android 5.0 Lollipop version: 22.21.19.en.EU (which is a lower version than my recovery's version)
My menu options look all white and after google'ing I realize that it has Android L's menu. Please see the screenshot i65.tinypic.com/14l4mmb.png
Could that be that reason? What can I do t rectify it?
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
joseph_1802 said:
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
Click to expand...
Click to collapse
THANK YOU SO MUCH for clearing that point 1 and 2. That is a relief!
Point #3 - "Your solution will be to manually flash the correct firmware or use RSD Lite."
What do I flash? OTA 5.1 (because my bootloader is from 5.1) or OTA 22.21.19.en.EU (because that is what I see in my phone's Software Update Available screen.
Where do I download those OTA files?
How do I flash using RSDLite? Any guide?
Thank you!
UPDATE:
Found the guide forum.xda-developers.com/showthread.php?t=2231249
I only need to know what I version I need to flash AND where can I download it from. Please?
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Nek0x90 said:
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Flower07 said:
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Click to expand...
Click to collapse
No it's not a problem. This will give you the latest version with the stagefright patch.
Sent from my XT1095 using Tapatalk
It is .3 because it has the stagefright patch, the .1 version doesn't have that patch but both of them are basically the same, so there's no problem if you flash one or another.