[Q] Moto X won't boot after xposed soft reboot? - Moto X Q&A

I was installing the "xad" xposed module and went to soft reboot. After that the phone won't turn on anymore. It'll show the boot logo and then just stay like that until the phone dies.
I can get into fastboot, but I'm not exactly sure what to do from there. Could I somehow just uninstall xposed frameworks?
Also I was rooted on the 4.4 AT&T leak when this happened.

Oh and it shows up in Windows as "Fastboot ghost S"

You could probably just flash the system.IMG from your phones sbf file through fasboot

Exposed leaves a flashable exposed Disabler zip but you need twrp to flash it, if you can't do that then try fastboot erase userdata but you'll lose all your stuff
Sent on my Moto X

flashallthetime said:
Exposed leaves a flashable exposed Disabler zip but you need twrp to flash it, if you can't do that then try fastboot erase userdata but you'll lose all your stuff
Sent on my Moto X
Click to expand...
Click to collapse
That appears to have fixed it. Thanks!

Epsilon707 said:
That appears to have fixed it. Thanks!
Click to expand...
Click to collapse
What worked? The flashabke zip or use data?
Sent from my A2109A using Tapatalk 4

flashallthetime said:
What worked? The flashabke zip or use data?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Wiping userdata. I don't really mind losing all my data, honestly. I was just worried my phone was done for. Thanks again.

Soft reboots seem to put my phone into a deep sleep or something. Screen powers down like any other reboot but doesn't power back on. Holding the power button fires the phone back up to the lockscreen like a normal soft reboot should.
Now that I'm reading what I typed, I wonder if I'm not waiting long enough to let the phone do its thing.

Related

Nexus one wont start up

Helloo...
I had my nexus one updated to cm 6.1.1 stable.
The next day i noticed he keeps restarting the phone.
I thought let me pull out de battery and turn the phone on.
Now its stuck at the coloured x and i cant get in recovery.
When i boot into recevory it gets stuck again at the coloured x.
I have flashed stock kernel frg33 and flashed amon recovery with fastboot and tried the passimg method to but it still gets stuck.
My phone is rooted and unlocked bootloader.
What can i do now?
Thnxx in advance
Can you get into bootloader by--> holding down volume-dwn, then pressing the power button, and the releasing the power button while still holding down volume-dwn?
You might need to remove you battery in between tries of this (plus pressing the power button i hear, with the battery removed to drain and remaining power..for 5 secs at least).
If that doesn't work, you could try the three finger salute for Android: Volume dwn+trackball pressed, then tapping power button and letting go of power button, and then the other two.
in most cases you will still be able to use adb
try running 'adb reboot recovery'
Like i sad, i can boot into recovery using the bootloader. But when it start up in recovery it gets stuck at the coloured x.
Fastboot is working but i cant get the adb to work.
Fastboot sees my device an adb doesnt.
What can i do to make adb work?
I installed new sdk and htc sync.
Running on windows 7
try to flash a new recovery through fastboot
download amon ra
open up a cmd
"cd " to directory where you downloaded it
rename amon-ra-recovery.xxxx.img to recovery.img
fastboot flash recovery recovery.img
then try to boot to recovery again
I tried that 10 times but it doesnt work.
Still gets stuck at the coloured x
Fastboot flash the system, bootloader, userdata, etc, and seem if it will boot to system?
Sent from my Nexus One using XDA App
this might sound a bit daft but try taking your sdcard out of the phone and rebooting to recovery
Tried that all. But doesnt work
What sort of error messages are you getting?
Sent from my Nexus One using XDA App
Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App
Nothing!!
Everything what i try to do goes wel.
Update with passimg goes wel.
Fastboot system, boot, userdata, bootloader, everything goes wel.
I dont get any error.
But when i start my phone it gets stuck by the coloured x.
Looks like hardware failure, then...
Sent from my Nexus One using XDA App
Oke that is not good cause i have no waranty anymore.
danger-rat said:
Have you tried to erase cache and dalvik through fastboot commands?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What is the fastboot command to erase dalvik?
Good question - I've used the erase cache command, and just assumed there would be an erase dalvik command. I may be wrong...?
Sent from my Nexus One using XDA App
Ashvan said:
Oke that is not good cause i have no waranty anymore.
Click to expand...
Click to collapse
When did you get your phone?
Sent from my Nexus One using XDA App
I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?
What is a dalvik cache exactly?
Does nobody knows the fastboot command to erase it?
Ashvan said:
I bought it second hand in september this year. I think its a year old now.
But since i have everything unlocked the waranty is void?
Click to expand...
Click to collapse
The very first nexus phones are just coming up to a year old, so the chance is that yours is still in warranty. Call HTC, and see what they say...
Sent from my Nexus One using XDA App

A bizarre series of events and my desperate recovery attempt [cliffhanger!]

So I started having trouble after flashing a rom. The old infinite htc boot logo. The troubling part was when I tried to reboot to recovery and TWRP blackscreened and device turned off.
I tried re-flashing recovery.img with identical results.
Now my phone locked while attempting a fastboot flash boot.img with a known working boot.img just in case the rom I flashed had a corrupt boot image.
I left the cmd window open and its been "sending boot.img" for about forty-five minutes now. I am terrified to ctrl+c the command or restart my device.
So boned or no boned?
On a scale of one to boned how boned where do I fall on the bonage spectrum?
Any ideas on what to do next, or if rebooting to fastboot is safe?
You have to wait the final of the sending.
Probably your USB cable is *****d up, and i'm advising you because i had the same issue.
A flash of a boot.img was of 15 mins.
Tried fastboot erase cache to get back into twrp?
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 9.1.0
Bulletproof 4.3
Afraid to stop the current fastboot operation to try to clear cache. Tried running from another window and it just sits there, cursor blinking, like its waiting for the other operation to complete.
Waiting for it to complete seems fruitless as its been almost two hours now for a 5836kb flash.
-update-
Okay so I took a couple valium and quickly switched out the usb cable. The cmd window running the flash operation crashed, but fastboot on the device became responsive again. I feel like this is a fact that might be useful to others in the future.
Fastboot stalls out--don't panic, just disconnect the usb cable...
I'm still scared to reboot it, even to reboot to fastboot. Is fastboot part of boot.img? If this botched op boned up my boot.img is it possible that fastboot might not work after a reset?
Gonna give cache erase a shot and report results.
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
hypocritelecteur said:
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
Click to expand...
Click to collapse
After the cache's erase you can boot in recovery.
Guich said:
After the cache's erase you can boot in recovery.
Click to expand...
Click to collapse
Phone still reboots right after TWRP logo is displayed!
hypocritelecteur said:
Phone still reboots right after TWRP logo is displayed!
Click to expand...
Click to collapse
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Yeah, I tried that before posting but for sake of thoroughness I did it again.
erased cache
reflashed m7 twrp
erased cache
Going to try CWM now.
Really appreciate the guidance and support in a problem you have no personal stake in. Being on the receiving end of the goodwill of strangers makes me all warm and tingly.
Also switched USB cables and did a fastboot reboot to make sure commands were being passed on... nothing wrong on that front.
Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Aaaand CWM worked for whatever reason.
Odd, since I've never had a problem with TWRP before but plenty with CWM... Every duck has its day I guess.
---
Well... CWM loads properly but executing any command that touches phone data causes a reboot.
Factory reset -> reboot
Install zip from sdcard -> reboot
Trying sideload next... it goes into sideload mode fine. I'm guessing that as soon as it tries to write something it will reboot, but I'll have to wait till I've re-downloaded and double checked md5s like a paranoid bastard first.
adb sideload ohdeargod.zip
---
Hmm, wiping cache partition alone works.
--
Noticed that on booting into CWM it displays the message:
Warning: No file contexts.
--
formating /system alone works
formatting dalvik causes reboot
formatting data causes reboot
--
sideload seems to have worked although its taking a long time to boot. I'll give it another 15 minutes.
Which firmware are you running?
Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Guich said:
Which firmware are you running?
Click to expand...
Click to collapse
Aaaand bingo gringo. It's booted.
Its a tmo m7. I haven't touched firmware afaik.
Resolved just in time for me to take it sailing today and drop it into lake Huron.
hypocritelecteur said:
[snip]....drop it into lake Huron.
Click to expand...
Click to collapse
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Okay so I have a brand new HTC TMO One I got last week and its waterlogged. I drilled a hole in the back of the case to drain it and then left it on the radiator to make sure all that moisture is gone. I can't get it to post to TWRP.
Please help.
Deciding after recent events that XDA can be a dangerous place for sarcasm. So--thanks all, problem solved, no, no phone was damaged during the making of this thread. It was just my business partner, Lloyd, who fell in and became waterlogged. No amount of drilling or radiator baking could revive him.
Please help.

Moto X bricked after OTA UPDATE HELP

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

[Q] Stuck at Unlocked Bootloader Screen (XT1063)

I left my phone charging overnight. Woke up, and saw that my XT1063 was stuck on the Unlocked Bootloader screen.
1. Tried to do a Factory reset from the fastboot screen and it went back to the same white screen.
2. Went into recovery and I see this message at the bottom of the screen
http://postimg.org/image/u8zi9d5ud
3. I have tried to format the cache/dalvik cache. Nothing has changed. I used fastboot and booted into TWRP and get this result.
http://postimg.org/image/5emdm1rij
4. Tried format/wipe cache from fastboot. Nothing changes. Tried flashing other versions of TWRP and Phil's CWM, stock recovery remains.
Is there anything that can be done? I'd like some help really as I've only has 3 months with this phone. I'm willing to do anything right now
There's nothing I can do?
I'm assuming nothing can be done...
I m by no means a professional, but it looks like some of your partitions are corrupt. If there is any way to flash the stock ROM, do that. But failing that, I'm really not sure what to do.Maybe do a search on google to see if others have fixed it on other devices, then try the same?
xN1ghtShadoWx said:
I m by no means a professional, but it looks like some of your partitions are corrupt. If there is any way to flash the stock ROM, do that. But failing that, I'm really not sure what to do.Maybe do a search on google to see if others have fixed it on other devices, then try the same?
Click to expand...
Click to collapse
I've searched and tried those methods. for one, I can;t use ADB. Is there any way to format the cache partitions? When I try to do a wipe function from stock recovery, it gives back the same message.
So I have a useless moto g :crying:
In would just do the following command in fastboot:
"fastboot erase cache"
If this doesn't work, I'm really not sure
Sent from my Nexus 7 using XDA Free mobile app
Tried that too :'( oh man...
So if you try that, does it give you an error message or does it just not work? If this is the case, you may be dealing with a bricked phone ?
Sent from my Nexus 7 using XDA Free mobile app
xN1ghtShadoWx said:
So if you try that, does it give you an error message or does it just not work? If this is the case, you may be dealing with a bricked phone
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
This is what i get -
http://postimg.org/image/3q9zqob4x/

[HELP] Moto X won't boot to OS after strange happenings...

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

Categories

Resources