A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?
It looks like I need to reflash the stock recovery image. I believe I have that (as long as the stock recovery is the same for all moto x phones (verizon, sprint, tmo, att, etc).
The problem I am having now is that I don't know how to flash the stock recovery image. All the instructions that I find require the phone to be in fastboot mode, but I have a locked boot loader....so. ..wud am I supposed to do??
dzlvs8 said:
A little background info. I have a Verizon Moto X.
I installed Pwnmymoto, the xposed installer, and xposed.
when I reboot with the pwnmymoto it says that I am rooted, but I dont see the root directory. xposed also doesnt make any changes that I specify.
So I thought, hey its time to factory data reset and try again.
Factory data reset did not work. It just rebooted my phone and all my data was still there.
Then I uninstalled pwnmymoto and the two exposed apps via the phones app list and tried to factory data reset and I got the same error.
Help! I haven't attempted to factory data reset using adb because I'm too stupid to figure out how to do it with adb, no matter how many times I google it. (yes I do have adb already).
Where do I go from here? Back to the Verizon store and hope that they dont notice that I tried rooting the phone?
Click to expand...
Click to collapse
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
_MetalHead_ said:
You gotta read up next time before taking the plunge. The pwnmymoto root hijacks your phone's stock recovery to boot into a version of android that is writeable to /system. It leaves a copy of your recovery on /sdcard so in the event you want to return to stock, you can just flash it back through adb, which is what you need to do. Once you flash your recovery back, you will then be able to factory reset. Also, the reason why your mods aren't sticking is because you likely aren't booting into the "recovery mode" version of the OS with the write protection off.
Click to expand...
Click to collapse
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?
dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Click to expand...
Click to collapse
Well your phone is technically rooted when you boot normally, but you don't have write capabilities to /system which is why nothing is sticking. You need to boot the phone into recovery mode to make those changes, and then reboot normally to use them. To boot into the recovery mode with write protection off you need to power your phone down, and power it back up while holding volume down. That gets you into the bootloader and from there you choose recovery and then your phone will reboot with write protection off. It's kind of annoying to have to do it this way but blame Motorola for locking the phone down as well as they did.
To flash the stock recovery back, you need to put the recovery file in your adb folder and then the command is "fastboot flash recovery recovery.img" without the quotes, but if you are unfamiliar with adb I don't recommend doing it. You can just flash the whole stock image with RSDLite and start from square one. I've not personally used RSDLite but here is a video tutorial for you- http://forum.xda-developers.com/showthread.php?t=2446515
dzlvs8 said:
Yeah, I got a little cocky when setting up pwnmymoto. I am actually in rooted mode when using xposed (according to the pwnmymoto app). Like I said, I have gone into the pwnmymoto app and rebooted the device with it and when i go back into pwnmymoto it says that I am rooted, then I try to use the xposed thingy and when I apply the settings my nav and notification bar reset, but nothing changes.
Soooo, dumb question. How do I reflash the stock recovery image? I see it on my storage card. All I know is to go into adb.exe via the command prompt, but I'm too stupid to know what to do after that. I have done a lot of searches online for how to do it, but everything I come up with involves fastboot.
Is it "adb restore recovery-stock.img"?
Click to expand...
Click to collapse
also just a quick note:
"adb reboot recovery" will boot you into recovery/writeable system
"adb reboot bootloader" will boot you into fastboot for using rsdlite which is all described in the instructions given by metalhead
Related
I apologize in advance if this same issue has been replied to elsewhere. I'm in kind of a unique situation and couldn't find an answer anywhere.
I'm got an N1 with 2.3.6 stock ROM, rooted. Recently I downloaded Titanium Backup PRO and while attempting to integrate dalvik cache to ROM, my phone rebooted into a bootloop. I'm assuming this is a bootloop. I get the colorful splash screen, it freezes for a second of two, then continues on, and on, and on....
Is there a way to get me out of this loopwithout having to wipe all my data, so I can backup all my stuff before I flash a custom ROM?
Everything I see about bootloops, mentions unlocking the bootloader and wiping all your data. I've seen downgrading using PASSIMG and loading stock rom. I'd really just like a simple way to get out of this loop hell and get my phone back up. It's in teh ship now getting it's power button fixed.
Thanks in advance
first thing i do on bootloops is pull battery
if no go pull battery and then pwr on by pressing pwr and trackball at same time--you can then get to recovery and maybe wipe dalvik and cache and reboot
i have never used TB for anything other than backup/restores, so can't help with dalvik integration
You might be able to fix it by wiping your cache from recovery.
Sent from my Nexus One using xda premium
Thanks for the advice! I'll give it a try as soon as I get my phone back from being fixed.
Hey guys, I hope you can help. I got my phone back with new power button, Yay! When I try to boot into recovery, teh Nexus X logo comes on for a moment and then I get a white triangle with an orange exclamation point. Do I need to use ADB to try and go to recovery and wipe my cache? I've never installed a recovery image. Do I need to do that or should there be a stock image already on my phone? Am I SOL?
One more thing that might help. I notice that when I go into HBOOT, the phone searching for 4 images from my SD card and can't find them. They go by too fast to write them all down but I think some are PASSIMG, PASSDIAG, etc. Again, do I need to load a recovery like clockworkmod on my phone first and then go into recovery to attempt to wipe my cache?
I get the same passimg all the time--no problem
If your phone came back from repair, you are probably unrooted and hence the triangle. At least that is the way I remember it, but has been two years since I rooted
If that is comfirmed by someone else, you wil need to reroot and install a recovery
A good time, if you haven't, to install android sdk and root/install recovery the right way and have full adb/fastboot features
there other ways I am not familiar with
does the lock show unlocked on the screen, they could have relocked bootloader
the wiki has the instructions, just have to navigate to the htc smartphones and N1
jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk
Thanks I'll check. I only had teh power button fixed and not by HTC so I doubt they unrooted it. I'm still in a bootloop but I can use superoneclick still, so I'll give that a try.
so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.
holtonhj said:
so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.
Click to expand...
Click to collapse
You really know nothing huh. The triangle is the recovery. Press power button and volume up at the same time, it will the show you some options like wipe cache.
n1newbie said:
jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Did you miss the "stuck in boot loop" part?
sorry,
meant that the triangle is your stock recovery--
you install recovery thru fastboot not adb
i would still, if you haven't, install android sdk on pc-unlock bootloader (fastboot oem unlock) and fastboot recovery--all in wiki
i think it was mentioned--holding down pwr and tb will get you into fastboot mode--phone connected and usb debugging selected on phone
you'll just have more flexibility with flashing roms etc and getting out of trouble
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
fellhound said:
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
Click to expand...
Click to collapse
Fastboot erase cache
shane1 said:
Fastboot erase cache
Click to expand...
Click to collapse
i tried to install stock but i can't with "adb reboot fastloader" beacuse it restarts every 10-20 seconds"
and according to http://forum.xda-developers.com/showthread.php?t=2444957
We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.
After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.
there is not a single drop of help with fastloader
edit: i managed to enable usb depuration by clicking several times on status/kernel version
i can run the command now, moto x responds and just Fast reboot, does not enter into fastloader
reached a dead end, now im desperated
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
flashallthetime said:
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
Click to expand...
Click to collapse
wow, finally, i was dying, now it does not reset itself.
How can i know if i have custom recovery? i though it was the normal one, wasn't aware pwnmymoto install custom recovery..
should i install stock rom anyways?
now i am downloading OTA again, now that i don't have root and pwnmymoto installed maybe it will work
will report results in 5 minutes
Thanks for the help guise
EDIT: lel no, after redownloading OTA update, it's still halfbricking with reboots.
I have recovered it again cleaning cache, but i wish to get OTA
Any ideas?
P.D all this trouble just to put 2 files into /system/ to enable Playstation mobile geez ;_;
fellhound said:
bump
Click to expand...
Click to collapse
I specifically know very little about pwnmymoto root method, my boot loader is unlocked, so I rooted the old fashion way. I know pwnmymoto hijacks the stick recovery. You may want to rsdlite back to stock, I believe there's a fxz with the latest update and root with jcases new method. Unless someone with more experience with pwnmymoto replies
Sent on my Moto X
You need to either flash the stock recovery and system through fastboot, or just RSD the whole thing (which deletes all your data). That's the only way you'll get it to accept the OTA update. Without the stock recovery, it will keep boot looping when you try to install the OTA.
Yes. Restore to stock. Threads galore. Once you boot you'll get an OTA prompt that'll work no problem.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/moto-x/general/moto-x-unbrick-ota-update-loader-v30-t3153725
I have Moto X Verizon Dev eition on 4.4. unlocked bootloader, Installed TWRP few weeks back with SuperSU for root. Worked perfect.
4.4.2 upgrade messages kept coming up, but I just ignored them by hitting back button.
This morning, while I was typing something and I was about to hit send, that message popped up and instead of hitting send, i hit INSTALL NOW. no warning, no confirmation, it said "power off" and started process of updating.
But the problem is that I still have twrp and is rooted, so everytime it reboots it goes to Team Win Recovery page and if I reboot from there, it goes back to normal boot up but then reboots automatically in 15 secs and goes on in an infinite loop.
I cannot start/stop anything when it boots up normally because I have literally 15 secs before it reboots automatically.
Any idea? On teamwin reocovery page, should I goto wipe>> factory reset? and then upgrade and so the whole TWRP and SuperSu again?
and of course, i am to stupid to have no backups made
KhAjUr said:
I have Moto X Verizon Dev eition on 4.4. unlocked bootloader, Installed TWRP few weeks back with SuperSU for root. Worked perfect.
4.4.2 upgrade messages kept coming up, but I just ignored them by hitting back button.
This morning, while I was typing something and I was about to hit send, that message popped up and instead of hitting send, i hit INSTALL NOW. no warning, no confirmation, it said "power off" and started process of updating.
But the problem is that I still have twrp and is rooted, so everytime it reboots it goes to Team Win Recovery page and if I reboot from there, it goes back to normal boot up but then reboots automatically in 15 secs and goes on in an infinite loop.
I cannot start/stop anything when it boots up normally because I have literally 15 secs before it reboots automatically.
Any idea? On teamwin reocovery page, should I goto wipe>> factory reset? and then upgrade and so the whole TWRP and SuperSu again?
Click to expand...
Click to collapse
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
jayboyyyy said:
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
Click to expand...
Click to collapse
Awesome. gorked like a charm.
just a note for someone else trying this.... first time i booted up after doing a "fastboot clear cache", i got a warning saying failed to load info. I clicked okay and I would get no service. Rebooted normally again, and everything worked fine.
Thanks again fro the response.
So are you now on 4.4.2?
The Tallest said:
So are you now on 4.4.2?
Click to expand...
Click to collapse
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
KhAjUr said:
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
Click to expand...
Click to collapse
If you're stock rooted, you just need to flash the stock recovery (available from the moto dev site) and make sure you don't have any missing or modified system files. You can then just take the OTA like normal, then reflash TWRP after.
KhAjUr said:
Nope. I rolled back. seems like I will have to roll back the root and then install 4.2.2 and then root again or something. Too much mess to go to 4.2.2. There are no specific and detailed directions for vzw dev edition rooted phone that I could find, so would leave it alone for now.
Click to expand...
Click to collapse
There are a lot of threads discussing this.
If you have a Dev Edition X with an unlocked bootloader, as long as you have stock recovery on the phone, and are close enough to stock, you can just take the 4.4.2 OTA and re-root using the same TWRP and SuperSU process. (more details -> http://mark.cdmaforums.com/MotoX-OTA.html which is based on many threads here on XDA)
Downgrading to 4.2.2, etc.. while rooting was for locked bootloaders only.
jayboyyyy said:
turn phone off. boot into bootloader/fastboot mode. run "fastboot erase cache". your reboots will stop. then use tibu to freeze motorola ota and you wont get ota things pop up anymore.
Click to expand...
Click to collapse
I'm fairly positive this will fix my problem since I'm experiencing the exact same thing as the OP.
However, I'm still new to bootloaders and rooting, etc...
Can someone breakdown what jayboyyyy is saying here? I can get into my TWRP bootloader. How do I run "fastboot erase cache"? Do I use the built in terminal command? Do I need to plug into my computer? Do I need to point my cmd to the TWRP I originally downloaded and installed on my phone?
I really do not want to mess this up. Like I said, I'm sure this is the fix for my phone. Thanks in advance!
TWRP is recovery, not bootloader / fastboot
You will need to plug into your computer, you should probably read more before you break things worse tho.
Start here: http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358
vennardk said:
I'm fairly positive this will fix my problem since I'm experiencing the exact same thing as the OP.
However, I'm still new to bootloaders and rooting, etc...
Can someone breakdown what jayboyyyy is saying here? I can get into my TWRP bootloader. How do I run "fastboot erase cache"? Do I use the built in terminal command? Do I need to plug into my computer? Do I need to point my cmd to the TWRP I originally downloaded and installed on my phone?
I really do not want to mess this up. Like I said, I'm sure this is the fix for my phone. Thanks in advance!
Click to expand...
Click to collapse
TWRP is a RECOVERY, not bootloader.
Do you remember how you flashed TWRP on your phone? You booted the phone into Fastboot/Bootloader mode. Connected the phone to PC via USB cable, then from command prompt on the PC used the Fastboot or mFastboot command... Same thing. However in this case the command to clear your phone's cache is... mfastboot erase cache
The other option is, you can see if there is an "erase cache" menu option while in TWRP as that would work too.
Then to take an OTA, you need to flash stock recovery back on your phone. If you try to accept an OTA while TWRP or other custom recovery is on your phone, you will get stuck in a boot loop like this.
I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?
if any files have changed in the system, any, and just one, then you can not update via ota.
simms22 said:
if any files have changed in the system, any, and just one, then you can not update via ota.
Click to expand...
Click to collapse
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...
RichCowell said:
I've had a look through various threads on here to try to get my Nexus 6 updating to 5.1...
I'd unlocked the bootloader and rooted it a long time ago, and was trying to find a way to do it without wiping it, but decided to just re-lock the bootloader and do it from scratch, only 3 months old but no harm in a fresh start...
Anyway, I locked the boot loader, it erased successfully, but still fails to update...
I've seen people refer to side-loading, but can't seem to see the best place for a guide to do that...
Shouldn't it update as normal now I've relocked the bootloader? Can anyone point me in the right direction while it's still blank?
Click to expand...
Click to collapse
Click the OTA link in my signature for some more information.
RichCowell said:
Even after relocking / wiping? What a nuisance!
Can you point me in the right direction for sideloading 5.1? I've downloaded it, but not sure how to get it on...
Click to expand...
Click to collapse
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Agreed, factory image should get you back to Ota ready.
simms22 said:
relocking just locks the bootloader, wiping just deletes the user data. so, if any files get changed, they still stay changed, even after a factory reset. flashing the factory img would change this(another way to get 5.1).
Click to expand...
Click to collapse
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
for the future, if you are flashing a factory img, then yes.
RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Same thing. Everything has to be 100% stock.
No need to wipe if you don't relock your bootloader.
RichCowell said:
Okay, getting on with it now, thanks guys...
For future reference, when the next update comes out, can I just side-load without having to wipe everything again?
Click to expand...
Click to collapse
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?
RichCowell said:
Possibly spoke too soon - the last steps of the instructions didn't happen...
When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
I got the small Android on its side / error image, so pressed Power Button & Volume Up, the phone just rebooted, did an upgrading thing and booted as normal...
Should I re-do something now before I set everything back up or should it be okay to use?
Click to expand...
Click to collapse
if it booted fine, and your about phone says 5.1, then youre fine.
simms22 said:
if it booted fine, and your about phone says 5.1, then youre fine.
Click to expand...
Click to collapse
Awesome, thanks
Need to decide now whether to bother rooting to make future updates easier...
I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?
sarshadd said:
I'm on a Google purchased, at&t sim, 5.0.1 Nexus 6 -- Locked boot loader, stock everything.
Mac OSX 10.9.5 Mavericks.
I enabled debugging, authorized my computer, and can see my device listed with the ./adb devices command when it's on. However, once I boot into the boot loader, or stock recovery, I lose my adb connection, and therefore cannot side load the OTA.
Everything I've found points to it being a Windows driver issue, but I'm on Mac...
Any advise?
Click to expand...
Click to collapse
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.
rootSU said:
adb only works in stock recovery for adb sideload. I've never done it but my assumption is that you must be in the sideload menu
Only fastboot works in the bootloader.
Click to expand...
Click to collapse
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
What does it say when you sideload?
sarshadd said:
Yup -- I am in the side-load menu, with yellow text, asking for the file to be pushed across adb.
Click to expand...
Click to collapse
After you put the boot loader in sideload mode, unplug and replug the USB cable, then run adb sideload.
Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?
THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app
So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.
I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app
Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk
I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!
I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app
As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app