No Os installed + TWRP + No driver & adb detection - Moto X Q&A

After rooted, wiped ALL stuffs (included OS...my bad) in TWRP, reboot and became a brick now...
I tried to do "ADB slideload" to transfer a rom.zip back to the phone, but window7 shows -- no driver for XT1060 under "Device Manager"....
Please help. This is my only phone...
So far I tried:
1) uninstall / install "MotorolaDeviceManager_2.4.5", but driver still doesn't show up.
2) Did that on both window 7 or Mac, same result. (Maybe Linux might work?)
3) In terminal, adb devices just gave me nothing.
4) In TWRP, mount, I checked all boxes, nothing happened.
5) In TWRP, Advanced, ADB Sideload, it just keep "running" even window has no driver.
Thanks so much for helping!
Chris

You need to redlite back here's how to rsdlite http://forum.xda-developers.com/showthread.php?t=2446515
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Make sure you flash your existing firmware just to prevent from having more issues
Sent on my Gummy running Lenoto X

Thanks again!
For the firmwares (http://sbf.droid-developers.org/phone.php?device=0), which one should I download? My device is Moto X - Developer Edition (GSM / ATT)
flashallthetime said:
You need to redlite back here's how to rsdlite http://forum.xda-developers.com/showthread.php?t=2446515
Here's the firmware thread http://forum.xda-developers.com/showthread.php?t=2538394
Make sure you flash your existing firmware just to prevent from having more issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse

chrischau421 said:
Thanks again!
For the firmwares (http://sbf.droid-developers.org/phone.php?device=0), which one should I download? My device is Moto X - Developer Edition (GSM / ATT)
Click to expand...
Click to collapse
At&t 4.4 third one from the top, that's kitkat 140.44.5
Its not really bricked but you will have to reflash recovery and root again
Sent on my Lenoto A2109 tablet

I am having the same situation. My phone is not getting detected at all by the computer. What to do ?

Related

[Q] [VZN] XT1060 MotoX DEV 4.4.2 update

Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
dray_jr said:
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
Click to expand...
Click to collapse
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Cozume said:
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Click to expand...
Click to collapse
as for the logo i am not sure i think you should be ok .
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go,
and anytime i flash something i always wipe the cache/davlik
dray_jr said:
and anytime i flash something i always wipe the cache/davlik
Click to expand...
Click to collapse
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Cozume said:
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Click to expand...
Click to collapse
you dont have too but it is recommended
dray_jr said:
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go
Click to expand...
Click to collapse
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Melarsa said:
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Click to expand...
Click to collapse
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Got it, that's what I'll do when the time comes. Thanks!
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
piccit said:
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
Click to expand...
Click to collapse
I thought it might be different because I'm rooted, and encrypted.
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
flashallthetime said:
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not using a custom ROM though.
fbiryujin said:
I'm not using a custom ROM though.
Click to expand...
Click to collapse
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
flashallthetime said:
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
So far no official update available to me even after flashing the stock image from Moto. My biggest goal here is to find a way to backup and restore nandroids from the encrypted phone.
Flash and relock Moto X manually
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
_slam said:
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
Click to expand...
Click to collapse
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
_slam said:
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
Click to expand...
Click to collapse
1) You don't need to do much. Revert the Entitlement hack you did, you need the one that came on the device, not a hacked one.
2) Flash the stock recovery back to your phone. You'll need the stock recovery to install the OTA. Just do it the same way you flashed TWRP to your phone but use the stock recovery.img file from the 4.4 .sbf ( http://sbf.droid-developers.org/download.php?device=0&file=5 )
You will NOT lose root flashing the stock recovery, you will NOT lose root taking the OTA.
After updating, use Xposed and the Moto Tether module for tethering instead of using a hacked version of the app.
shadowmonk36 said:
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
Click to expand...
Click to collapse
If you have the Dev edition from VZW, it's simple to install the OTA.
This is what I did as I had root and xposed installed.
1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard
2. Flash stock 4.4 recovery image via fastboot.
3. Flash 4.4 system image using mfastboot (must use mfastboot)
4. Boot into recovery
5. Apply update and selected the OTA zip.
6. Reboot
7. Power down and boot back into fastboot.
8. Flash TWRP, allow it to root, reboot.
9. Reinstall Xposed framework.
All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.
Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.
Sent from my Dev Edition Moto X

[Q] VZW DEV 4.4 to 4.4.2 update failure opinion Question

Hi all!
Just a quick synopsis. I've held off for a while. I've read just about everything related as it's come across here over the past few weeks.
I've been perfectly happy with where I sat:
VZW Dev Ed, Rooted, TWRP, xPosed, Tehter & Gravity Box modules.
I'm not fond of ADB commands, etc. but can work my way through them.
Today, I decided to to take a quick stab at things (a little differently).
So, here's what I did:
1) Unfroze some bloat
2) Unistalled xposed Framework
3) USED Flashify to backup my TWRP
4) USED Flashify to install stock recovery
5) Downloaded OTA
6) Installed 4.4.2 update
7) It FAILED
So, I restored my TWRP recovery through Flashify; re-installed xPosed Framework; refroze the bloat and I'm back to where I was before.
The only thing that I really think might have caused the update to fail was the fact that I had AOSP Browser installed. (with its related installer)
So, that's my question here....opinions...would that cause the update to fail?
I've since tried to uninstall that browser with the related installer but it keeps getting hung and force closes when trying.
Opinions? (other than..."please, use ADB commands")
I'm assuming flashing my system ui might take care of that?
Thanks for ideas. I know I'll take the time to get it done "proper". Just haven't been pressed to do it yet.
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
hlaalu said:
Unfreeze everything and make sure the tether hack is reversed. I believe it tells you where it failed in recovery when it's doing its thing. I'm in the same boat as you, but I'm just going to wait until Moto releases the new image.
Click to expand...
Click to collapse
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Dburgessme2 said:
Well, it's the tether module (not the hack)...so uninstalling xPosed would take care of that I'd think.
When Moto releases the new image...what's your plan? Able to flash that without losing data, etc?
Click to expand...
Click to collapse
Hmm double check that it checks for subscription when tethering to make sure it changed the files back?
I'm a little rusty with fastboot, but it doesn't wipe your data unless you ask it to:
Code:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
[B]$ fastboot erase userdata[/B]
$ fastboot erase cache
$ fastboot oem lock
So I think if you just don't do the fastboot erase userdata command your data is safe. I'll wait for someone with more experience to confirm that.
But even if that's not the case, I'll still wait because we have to fastboot for root and recovery anyways, might as well just do everything in one go.
Schaweet said:
Did you run the xposed cleaner zip or just uninstall it? It easier to just flash the system and recovery images via mfastboot. It takes two seconds assuming you have the Sdk installed and Moto drivers installed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Roland Stone said:
Are you using the VZW specific stock recovery.img directly obtained from the Motorola website that you extracted yourself from the zip file you got there? I wouldn't necessarily trust any other stock recovery floating around.
Click to expand...
Click to collapse
Nope, I didn't extract it myself. I'll have to do that to make sure I've got the "real deal".
Thanks!
DB's Nexus 7
Dburgessme2 said:
I only used the Uninstall from within itself. Where is the cleaner zip? Might have to do a search.
Thanks!
DB's Nexus 7
Click to expand...
Click to collapse
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Schaweet said:
It's the xposed disabler zip that is put in the root of your SD card when you install xposed.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Just flash it through recovery I assume?
DB's Nexus 7
Yes
Flashing the system and recovery images is still the most fail safe method. It doesn't erase your settings or data.
Sent from my Dev Edition Moto X
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
awerner68 said:
Flashing the stock recovery did the trick for me. No data loss either.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Easiest thing to do is fxz save data with HoM. If you don't have HoM set up you can modify the fxz XML. File to not erase user data and fxz. You should be able to update then. The fxz puts stock recovery back so you don't have to flash anything. Update install twrp root done.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
So, fxz the 4.4.2 image for vzw 1060 through rsd lite? But remove "erase data" line from the xml file first. Then, TWRP recovery back (root). That about right?
I think the last thing I used rsd lite for was on old Droid X.
Any quick refresher would be appreciated.
Thanks!
DB's Moto X
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
bigv5150 said:
Yeah that is pretty much it. As far as what line to delete I'm not sure I use HoM it does it all autmatically. Only tips I can give you is don't use USB 3 it doesn't work with rsd only USB 2 if you plug in your phone and don't see it in rsd change USB port. Make sure debugging is checked.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
OK. And now I have to ask... What is HoM? (googled with no good results)
DB's Nexus 7
Dburgessme2 said:
So, what method did you use to update? Fastboot/ADB commands or the "on phone" method I described in first post?
Click to expand...
Click to collapse
I downloaded the .ZIP file and flashed it with TWRP. Using TWRP to replace itself.
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
bigv5150 said:
HoM (House of Moto) its a script that allows you to do a full fxz or a save data fxz. It just makes fxz'ing easier here is the site
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20-for-now/
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
And, this HoM should work with the Vzw 1060 Dev Ed?
DB's Moto X

[Q&A] [GUIDE][HOW-TO] Root Moto G 2014 WITHOUT flash a custom recovery

Q&A for [GUIDE][HOW-TO] Root Moto G 2014 WITHOUT flash a custom recovery
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.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][HOW-TO] Root Moto G 2014 WITHOUT flash a custom recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Error
thomstrack said:
What is this?
I have seen several people wanting to root on your Moto G 2014 and not doing because they do not want to install a custom recovery, and stick with the stock recovery to receive OTA updates. After some research and a little study, i made this procedure and it worked perfectly on my Moto G XT1069. Here we go!
Note:
Tested on Moto g 2014 DTV XT1069 (Sotck KitKat 4.4.4), but should work on other versions of Moto G 2014 also.
Requirements:
- Unlocked bootloader
- Usb debugging enable on your phone.
- Adb and Fastboot into your PC: Donwload
- Custom recovery: Donwload
- Latest SuperSu: Download
Instructions:
- Copy SuperSu from your SDcard;
- Open CMD or Terminal into the folder where you placed the Custom recovery and reboot on bootloader:
Code:
adb reboot bootloader
- After reboot in bootloader, boot on temp custon recovery:
Code:
fastboot boot recovery_file_downloaded.img
- Your phone will restart in temporary Custon Recovery.
- Now just flash the SuperSU (which you copied to your sdcard before)
- Reboot system
- Enjoy!
Credits:
Snoop05 (Adb and Fastboot drivers)
adrianom (TWRP Custom recovery)
Chainfire (SuperSu)
Click to expand...
Click to collapse
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Moto G2014 (XT1063) - With Lollipop
blopez23 said:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Moto G2014 (XT1063) - With Lollipop
Click to expand...
Click to collapse
This error its in adb, adb don't find device.
You need install Adb and Fastboot into your PC and Motorola drivers.
Wolfcity said:
Is it possible to root the moto g (after unlockling the bootloader) with "fastboot boot recovery.img" without making any changes but the installed Super SU-zip like in this thread for Lenovo? http://forum.xda-developers.com/showthread.php?t=2597590
Can I use the recovery from here? http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 ?
and enter bootloader, type fastboot command
fastboot boot CWM_Touch_Titan.img
and then flash SuperSU zip from Recovery?
Click to expand...
Click to collapse
I asked about this procedure in another thread a little while ago and just to be sure:
If I do so I can recieve lollipop ota with the unlocked bootloader,only thing to do may be using full unroot in superSU?
Nothing more to do?
Anyone?
Sent from my XT1068 using XDA Free mobile app
thomstrack said:
This error its in adb, adb don't find device.
You need install Adb and Fastboot into your PC and Motorola drivers.
Click to expand...
Click to collapse
Motorola driver's and adb are installed, I may need to try again
I rooted my phone following the post, now i had a little problem, when the phone started super su was installed correctly, everything looked right, but when i took a photo i couldn't save it. I don't know what to do, thanks for the guide ?, now i hope that somebody help me.
Moto G XT1063 Android 5.0.2 Stock
eltejeiro said:
I rooted my phone following the post, now i had a little problem, when the phone started super su was installed correctly, everything looked right, but when i took a photo i couldn't save it. I don't know what to do, thanks for the guide , now i hope that somebody help me.
Moto G XT1063 Android 5.0.2 Stock
Click to expand...
Click to collapse
Where do you try to save the photos? External SD or internal storage? Have you tried to save some other data there? Maybe you have no write permisson?
Else you can try another photo app just to check that out.
Wolfcity said:
Where do you try to save the photos? External SD or internal storage? Have you tried to save some other data there? Maybe you have no write permisson?
Else you can try another photo app just to check that out.
Click to expand...
Click to collapse
I tried to save in both, internal storage and external sd, but anything worked, with other kind of data it's the same, you know how can i change the write permisson?
Thanks for answering ☺☺

Trying To Flash A Firmware Update, Running Into Multiple Issues (Driver, Zip Related)

Alright so there's a new firmware from Moto that I'm trying to flash, specifically this one:
purejoy said:
XT1095 lollipop 5.0 LXE22.46-11 stock firmware: http://motofirmware.com/files/file/1043-tmo-xt1095-50-lxe2246-11-cid9-cfcxmlzip/
Click to expand...
Click to collapse
For whatever reason my ADB drivers don't detect the phone when I'm in recovery. I can't locate the drivers for the XT1095 device either whenever I try to do it manually. I have the Moto drivers installer which worked fine for when the device isn't in recovery, I just can't use it with ADB for whatever reason.
With ADB sideload no longer an option I figured why not flash it from the SD card. Well, I get an invalid signature error which won't flash the update either.
So now I'm in between a rock and a hard place. Can anyone help me get out, please & thanks?
You can't flash that from sdcard, or the recovery. Boot into boot loader mode and flash it there from computer.
Oh yeah, enable developer mode inside android and enable USB debugging too.
Yes, flash the firmware via RSD lite or fastboot utility.

[Q] How badly is my device ****ed up?

Ok, so here's the deal. I flashed RETAILDSDSALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml on my 2014 EU Moto G XT1068 and now ADB is unauthorized on my PC when I try to boot it up but the device isn't even detected in Fastboot, so I can't flash jack ****, but I can access the stock recovery and ADB Sideload from there.
The phone is stuck in a boot loop - it just sticks to the WARNING - BOOTLOADER UNLOCKED screen.
What do I do? Any help is greatly appreciated.
LesbianDoritos said:
Ok, so here's the deal. I flashed RETAILDSDSALL_XT1068_4.4.4_KXB21.85-23_cid7_CFC.xml on my 2014 EU Moto G XT1068 and now ADB is unauthorized on my PC when I try to boot it up but the device isn't even detected in Fastboot, so I can't flash jack ****, but I can access the stock recovery and ADB Sideload from there.
The phone is stuck in a boot loop - it just sticks to the WARNING - BOOTLOADER UNLOCKED screen.
What do I do? Any help is greatly appreciated.
Click to expand...
Click to collapse
if you came down from 5.0.2 to 4.4.4 without a full factory reset / wipe it hangs..... fixable
this zip in my signature has everything you need
download the 4.4.4 easy installer in my signature (choose correct .23 version -dsdsall) has instructions, all drivers , adb files and firmware and a auto restore script - that should fix
reefuge said:
if you came down from 5.0.2 to 4.4.4 without a full factory reset / wipe it hangs..... fixable
this zip in my signature has everything you need
download the 4.4.4 easy installer in my signature (choose correct .23 version -dsdsall) has instructions, all drivers , adb files and firmware and a auto restore script - that should fix
Click to expand...
Click to collapse
Ok, so all I need to do is run your script? I didn't attempt to downgrade, I was already on 4.4.4 when I flashed everything.
Now that you say it I do want to try out Lollipop. Can I just run your 5.0.2 script? Will it boot?
Thanks.
LesbianDoritos said:
Ok, so all I need to do is run your script? I didn't attempt to downgrade, I was already on 4.4.4 when I flashed everything.
Now that you say it I do want to try out Lollipop. Can I just run your 5.0.2 script? Will it boot?
Thanks.
Click to expand...
Click to collapse
yes 5.02 easy will install as well , but then if you want to go back to 4.4.4 you will need a unlocked boot loader
but lets get you phone up and running
try 4.4.4 1st to fix phone then if all ok , you can try 5.0.2
reefuge said:
yes 5.02 easy will install as well , but then if you want to go back to 4.4.4 you will need a unlocked boot loader
but lets get you phone up and running
try 4.4.4 1st to fix phone then if all ok , you can try 5.0.2
Click to expand...
Click to collapse
OK, fair enough. Which one should I download? There are four choices here, and I'm not sure which is the correct one for my device
LesbianDoritos said:
OK, fair enough. Which one should I download? There are four choices here, and I'm not sure which is the correct one for my device
Click to expand...
Click to collapse
your phone is a xt1068 dual sim? correct?
any will flash if a xt1068
but you want 'B'
reefuge said:
your phone is a xt1068 dual sim? correct?
any will flash if a xt1068
but you want 'B'
Click to expand...
Click to collapse
Ok, I am downloading now.
Does your script require full ADB access? Because if so that may be a problem... I can only use ADB to sideload packages from the recovery.
LesbianDoritos said:
Ok, I am downloading now.
Does your script require full ADB access? Because if so that may be a problem... I can only use ADB to sideload packages from the recovery.
Click to expand...
Click to collapse
read instructions in zip should explain clearly
but as you wait you will find adb , dll's, motorola drivers , mfastboot all in extracted folder and firmware- it all runs from inside the folder
reefuge said:
read instructions in zip should explain clearly
but as you wait you will find adb , dll's, motorola drivers , mfastboot all in extracted folder and firmware- it all runs from inside the folder
Click to expand...
Click to collapse
My phone is back now. Thank you so much for your help, seriously!
LesbianDoritos said:
My phone is back now. Thank you so much for your help, seriously!
Click to expand...
Click to collapse
:good: Glad it worked

Categories

Resources