Related
I Think i have bricked my nexus s ......it wont startup and goes to do first setup but force closes....i can access recovery but when i flash a rom it aborts ....only just bought it
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
afishpie said:
U can odin it back to stock. Check out the android dev forums
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Please can you elaborate...or point me in right direction......recovery is now only accessible by flashing it first....phone just wont do anything
download a 2.3.3 nandroid backup and restore to it using clockwork recovery
ignore odin.
http://forum.xda-developers.com/showthread.php?t=884093
update to 2.3.3 using http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
or just download CM7 and flash that along with gapps (wipe dalvik/cache/factory)
and your phone is not bricked. the definition of a bricked phone is a phone who cannot access recovery/fastboot/etc.. can access absolutely nothing
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
distortedloop said:
Well, he does say that his attempts to flash a rom always abort...
OP, we need more details.
Are you using Clockwork Recovery? Which version? Try an older/newer version...
What ROM are you trying to flash? Have you tried others?
What happens when you try a normal boot? You say you get as far as the first setup screen?
Have you tried a Factory Reset of the phone from within recovery (stock or clockwork)?
Click to expand...
Click to collapse
Many thanks to both of you.....for your help .....so much appreciated......i have got past first setup screen after applying a nandroid backup......it finally worked after 5 times trying....but i have stock android recovery but rom manager on phone .....how can i get clockwork mod back as everytime i flash it.....i get to use it for that one instance ans then it returns to stock android recovery
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
menov321 said:
I think it might be okay now ....after titanium said busybox was installed....i dont think it was done correectly.....after downloading busy box from market....recovery seems to be sticking rather then reverting back to android. Just to check....is there anything i should do to check all is well on my phone and also while flashing i think i changed build number from IR to GH (what are the implications of this move? many thanks...phew
EDIT- NO recovery still wont stay....any ideas?
Click to expand...
Click to collapse
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
sano614 said:
That's normal. See below:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
menov321 said:
Thankyou SOOO MUCH.....you put my mind at rest......can you maybe help me with one other thing.....WHEN I MESSED UP EARLIER i flashed a different rom build.....does this have any negative affect on the phone....my stock rom was a IR something but i flashed a GR or GH something....
Click to expand...
Click to collapse
No it doesn't. You're fine. The latest is android 2.3.3 with GRI40.
Sent from my Nexus S using Tapatalk
I just bought a brand new xt890. It has just arrived and I realised that it is running on Android 4.0.2 ICS. I got no idea what to start with first, root, upgrade to jellybean, recommendable firmwares or any other must get upgrades/modifications? What about back-up and stuff?
Update before rooting then custom rom
Sent from my GT-I8160 using xda app-developers app
ken_alpha24 said:
Update before rooting then custom rom
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
Sorry to be asking this; but how do you proceed to Update? Is there things I need to take note off like what country the current firmware is from etc?
OTA
Sent from my GT-I8160 using xda app-developers app
textus said:
Sorry to be asking this; but how do you proceed to Update? Is there things I need to take note off like what country the current firmware is from etc?
Click to expand...
Click to collapse
To update your device to jb, make sure that the battery is at least 80% and that you're connected to a wlan.
Then go to settings -> about phone -> system updates. It will pop up a message that there is a OTA-update available. Click on download and after the download is finished on install. The phone flash the OTA automatically.
gesendet von meinem Motorola RAZR i rooted+unlocked
Thanks for the replies! I have updated it is now on 4.1.2. Is there different rooting instructions for different flex versions? How should I go about rooting next?
Also, when I first powered-on my device I did not get the android start screen and activation. Does that mean the phone is not brand new? How do I check if the phone is brand new? I ordered it online and it got shipped over, as far as I can tell there seem to be no scratches or scruff marks.
There is thanks button
Sent from my GT-I8160 using xda app-developers app
I've hit the thanks!
Is there different rooting instructions for different flex versions? How should I go about rooting next?
Also, when I first powered-on my device I did not get the android start screen and activation. Does that mean the phone is not brand new? How do I check if the phone is brand new? I ordered it online and it got shipped over, as far as I can tell there seem to be no scratches or scruff marks.
Hey,
Congratz on your new phone, you will like it as many of us do
The first thing to do is unlocking your phone. There is a great guide in the development section and general section somewhere.
After that install custom recovery and root your device.
No specifik notes are needed
Your phone is genuine, but if u want to know for sure just do a full wipe/factory reset in recovery. Most of the time u can't see it on the outside.
Sent from my XT890 using xda app-developers app
1) I think my phone is already unlocked. How do I then install custom recovery? Is that in the Google Play Store?
2) About rooting... is there different rooting instructions for different flex versions? How should I go about rooting?
3) If I do a full wipe/factory reset then how will I know if it was used before? Wouldn't the wipe make it look new?
4) If I am to do a factory reset will that be after the backup in the same app? Thanks!
textus said:
1) I think my phone is already unlocked. How do I then install custom recovery? Is that in the Google Play Store?
2) About rooting... is there different rooting instructions for different flex versions? How should I go about rooting?
3) If I do a full wipe/factory reset then how will I know if it was used before? Wouldn't the wipe make it look new?
4) If I am to do a factory reset will that be after the backup in the same app? Thanks!
Click to expand...
Click to collapse
1. You need to unlock the bootloader. If it's already unlocked then you see a warning while turning on the phone ( before red m logo appears). Otherwise there is a nice guide by mattlgroff how to unlock the bootloader
http://forum.xda-developers.com/showthread.php?t=1928551
Just read the OP and follow the steps.
For custom recovery have a look here -> http://forum.xda-developers.com/showthread.php?p=41479852
2. No. There is only one root-method if you're on jb. Just flash the zip from this thread -> http://forum.xda-developers.com/showthread.php?t=2123369
Or you flash a custom ROM (which are prerooted).
3. After a factory reset you will maybe (it does not have) see the first start dialogue.
4. Sorry don't know what you mean
gesendet von meinem Motorola RAZR i rooted+unlocked
4) I meant that I wasn't sure if the phone is completely brand new. Is there any way to check the software to see if it has been used before? Because if I do a factory wipe, then it will look like it is new when it might not be. Also when I switched on for the first time I was not asked to activate android and sign in.
5) After unlocking the bootloader and backing up and flashing a custom load, I can no longer have OTA updates rights? Also should I do a factory wipe before unlocking the bootloader or after? Thank you.
textus said:
4) I meant that I wasn't sure if the phone is completely brand new. Is there any way to check the software to see if it has been used before? Because if I do a factory wipe, then it will look like it is new when it might not be. Also when I switched on for the first time I was not asked to activate android and sign in.
5) After unlocking the bootloader and backing up and flashing a custom load, I can no longer have OTA updates rights? Also should I do a factory wipe before unlocking the bootloader or after? Thank you.
Click to expand...
Click to collapse
you can check on which google account you are loged in. But that is the only way i think.
You can get ota updates after unlocking, but it isnt a good idea to install them, it can brick your device maybe. But what does it matter all updates and firmwares are on this site and u can flash them with a recovery or use the fastboot files
textus said:
4) I meant that I wasn't sure if the phone is completely brand new. Is there any way to check the software to see if it has been used before? Because if I do a factory wipe, then it will look like it is new when it might not be. Also when I switched on for the first time I was not asked to activate android and sign in.
5) After unlocking the bootloader and backing up and flashing a custom load, I can no longer have OTA updates rights? Also should I do a factory wipe before unlocking the bootloader or after? Thank you.
Click to expand...
Click to collapse
It will automatically do a factory reset while unlocking bootloader.
gesendet von meinem Motorola RAZR i rooted+unlocked
I am at the installing recovery phase. What is the difference between TWRP, stock and CWM? Which one do I install?
Recovery's
Stock:
- only install signed zip files like ota packages. No custom allowed.
- wipe to factory
CWM:
- from koush, the maker of the base custom recovery's
- install custom zips. For root etc or other roms
- backup/restore your full rom
- wipe to factory and more
- USB Mount
- fix permissions of your ROM
- more things i forgot
TWRP:
- cwm as base, but sort of rewritten
- everything that cwm does
- multi zip install
- compres backups
- build in file manager
- touch friendly ui
It is what u like. A very stable cwm that does everything u need or twrp that does more than that, but not from CM or kouch.
Sent from my GT-P5110 using XDA Premium HD app
When I run CWM Recovery from the cmd prompt menu, it says device found then stock recovery complete. But I chose CWM, and even tried it twice. When I try TWRP it writes correctly and say TWRP is completed but when I chose CWM again, it gives the same problem saying stock recovery complete. Am I suppose to think that it is now CWM? When I went back to my phone it did not seem like there was a wipe to factory. How do I know if the custom recovery phase is successful?
I can't seem to enter bootloader now. I tried pressing power button and volume down at the same time and then releasing the power button when I feel a vibration but continuing to press the volume down. It just boots normally. I can't seem to root.
Also is it possible to root without a microSD card and SIM card?
I just used the recovery flasher to reboot to recovery and it now shows a green android lying down with its front panel open and a triangular red warning exclamation mark sign on it.
Edit: Sorry for being so spammy after rebooting several times (like 15 times) and tinkering around, I managed to root it. But I am not quite sure how to check if I am successful.
Is there any way to get rid/change the warning unlocked bootloader message in the beginning?
textus said:
I can't seem to enter bootloader now. I tried pressing power button and volume down at the same time and then releasing the power button when I feel a vibration but continuing to press the volume down. It just boots normally. I can't seem to root.
Also is it possible to root without a microSD card and SIM card?
I just used the recovery flasher to reboot to recovery and it now shows a green android lying down with its front panel open and a triangular red warning exclamation mark sign on it.
Edit: Sorry for being so spammy after rebooting several times (like 15 times) and tinkering around, I managed to root it. But I am not quite sure how to check if I am successful.
Is there any way to get rid/change the warning unlocked bootloader message in the beginning?
Click to expand...
Click to collapse
oke, i am at the point that i dont understand your story fully anymore.
First off, a picture of a green android lying down means u are in stock recovery.
But now i see your edit, i assume u have managed to flash CWM or TWRP on your device and got it booting in recovery. After that u installed the zip file with the root files in it. Something with root2... (I dont know the name, never used it) If u have done those things u can install titanium backup to see if u are rooted. On startup of the app it wil give u a popup with the message if u want to give this app root rights. If u see this u are rooted.
U cant get rid of the warning messages. if u want to know why, do a little search in i think the development section.
for booting to bootloader: hold power + volume down. release power just after the first shutdown of the device, so u have only the volume down button pressed when the device boots for the second time in a row
The first thing to do is a backup of u rom!!!! when u got for sure a custom recovery on your device!
I have the feeling that u dont have many experience in android and rooting and stuff. It is wise to do some studying about it
textus said:
I can't seem to enter bootloader now. I tried pressing power button and volume down at the same time and then releasing the power button when I feel a vibration but continuing to press the volume down. It just boots normally. I can't seem to root.
Also is it possible to root without a microSD card and SIM card?
I just used the recovery flasher to reboot to recovery and it now shows a green android lying down with its front panel open and a triangular red warning exclamation mark sign on it.
Edit: Sorry for being so spammy after rebooting several times (like 15 times) and tinkering around, I managed to root it. But I am not quite sure how to check if I am successful.
Is there any way to get rid/change the warning unlocked bootloader message in the beginning?
Click to expand...
Click to collapse
When you see the superuser app in appdrawer you're rooted. Or install a root app from Google play ( for example titanium backup)
Don't know of there is a way to remove unlocked bootloader warning. But IMO the warning message isn't a problem.
gesendet von meinem Motorola RAZR i rooted+unlocked
I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?
phisher177 said:
I installed CWM and got cyanogenmod onto my phone without any hassle, eventually decided that a rooted stock rom for my sprint phone would be best for the time being.
my method was to pick up the rooted stock from from galaxyS4root (1.40 gb) and install it using CWM after doing a total wipe, the package also performed automatic wipes upon installing. no issues so I went ahead and rebooted, CWM alerted me saying that the package was not rooted and if I wanted to root, my answer was "yes."
the phone gets as far as the "galaxy S4" splash screen, then goes black and stays that way. The phone gets warm when doing this so I know its trying to do something. The only fix is to reboot into CWM and reinstall cyanogenmod.
Anyone else experience this? what can I do to fix it?
Click to expand...
Click to collapse
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.
xxaddictedxx said:
i had this problem after first rooting as well. all i had to do was update the SU binaries and then root sticks. i would also do the wipes yourself just in case the package is missing something. and the obvious....check the MD5 and make sure its right and make sure your downloading the correct file for your phone.
Click to expand...
Click to collapse
CM10's built in SU didn't seem to think the binaries needed updated, installed chainfire's SU and it wanted to update CWM.
it asked me about disabling recovery flash, to which i said yes. Its not the root im having an issue with though, its getting stuck at a black screen.
either way, update didn't work.
Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.
phisher177 said:
Ended up using odin to push the latest stock firmware on, then trying to root using the walkthroughs on here which resulted in the same outcome, black screen.
I was getting my deoxed and rooted rom from galaxyS4root.com, so I started checking the MD5, it never matched out of the 5 times I downloaded it. Watch out I guess.
Click to expand...
Click to collapse
did you try one of the roms on xda? if MD5 dosent match then thats your problem
I just got the OTA update to Android 4.4, and being eager to get it installed, hit the install button right away. I told a few people I was going to be a few minutes while installing the update... and tapped the button.
That was three hours ago, roughly.
I'm on a rooted nexus 4 with CWM Touch edition installed as a recovery. I don't know exactly what version right now but it was the latest when I installed it a few months ago.
The install launched CWM, and I waited as the loading bar filled. Right at the end it gave an error message - in a panic I didn't take note of what it was, hit the onscreen buttons and went through a window telling me I might have lost SU permissions - which I told it to fix. The startup animation (with four dots, the new 4.4 animation I guess?) started... and continued for more than five minutes.
I was still panicking and instantly launched back into CWM, downloaded a (I think correct, checked it multiple times, as on does...) update zip from the web, and flashed it via adb sideload. This gave me an "Error 7" and a failed install. I tried again, same result. Then gave up and hit the restart button in the hope that one of the attempts had indeed worked...
I now have a Nexus 4 sitting on my desk playing a nice dotty animation, and it's been doing that for fifteen minutes as of now. I'm intending to leave it as such hoping that it will actually turn on and it's just having a very long boot.
So, the question. Anyone have any ideas how to save my Nexus?
I'd rather like to end up with the data on the device intact (stupidly did not back up before installing and can't get any files off it until an install works) and possibly with Android KitKat running on it, as was the original aim of tonight, but if neither are possible, I'd at least like to end up with a functioning phone... just with any stock rom.
Thanks in advance.
P.S. I'm not new to flashing ROMs manually - my last phone was a ZTE Blade which never ran any ROM well, so I must have flashed on that phone at least ten times, including via ADB.
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
totally-not-me said:
Ignore the above - I fixed the problem by using fast boot to flash the stock rom from developers.google.com/android/nexus/images ....
I feel really stupid now. But it worked perfectly. All I did was open the flash-all.sh and copy the commands out line by line, but removing the -w from the final command to dodge wiping the device. Anyone confident in Terminal or similar should be fine
Sorry for the thread being created but I really thought I couldn't fix this xD
Click to expand...
Click to collapse
Your post saved me from a complete wipe and reinstall, so thank you for sharing your fix. I had a very similar issue but my Status 7 appeared to be because of my previous root and the new install not being able change the permissions on some /system files.
Now I just need to re-enable root via the NRT.
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
dethrat said:
at least you've learnt something. Ota updates will always fail if you have any cwm recovery installed. Not like it hasn't been discussed before. Guess you won't be making that mistake again.
Can't say anything makes be panic not like nexus devices are hard to recover ☺
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
Not blaming you xda has almost become useless in terms of finding real info in the past week. Bombardment of repeated posts about 4.4
Sent from my Nexus 4 using Tapatalk
Lokitez said:
I'm in a similar boat.
My wife accepted the OTA update with TWRP installed and ended up in a boot loop. We didn't care about the data on the device, so thinking I could start from scratch, I did an Advanced Wipe of everything in TWRP. Now the phone has no OS on it.
I tried doing an adb sideload KitKatNexus4.tgz, but it gives me an error of a corrupted .zip every time.
I'm stumped.
Click to expand...
Click to collapse
Sideloading is only for flashable zip packages, not official factory images that required using fastboot. Use the guide links in my signature for instruction to flash factory image.
Or you can use sideload to flash flashable stock roms: http://forum.xda-developers.com/showthread.php?t=2527806
Unless your wife is really into flashing, I suggest just leaving it everything stock.
thankyousam said:
To be fair, there are several posts around where people have simply updated their version of CWM and then reported the 4.4 upgrade has worked. I think I must have used the OTA Rootkeeper before as I don't recall these issues (other than losing root) during the 4.3 upgrades.
Click to expand...
Click to collapse
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
RickyBO89 said:
where did you find these posts? the only thing that I'm reading is people constantly saying "CWM will break OTA" or "you can't flash OTA with custom recovery" (this is clearly wrong)
I have the latest CWM recovery (6.0.4.3) and I don't want to lose it or flash stock recovery and CWM back. with 4.3 I remember that everything went good and I didn't have a lot of problems, the only thing I had to do was to unroot before flashing the OTA from CWM... but this time I'm reading a lot of conflicting posts so I'm a bit worried to try this by myself without some sort of feedback from any other user
Click to expand...
Click to collapse
It will softbrick the device, or atleast fail. I don't even have to try CWM, but with TWRP, if I make any changes to the /system partition it failed. I suggest you just flash a stock 4.4 rom: http://forum.xda-developers.com/showthread.php?t=2010887
Ok, I'm new at this, here's what I've got, hopefully someone can shed some light:
-My RAZR M is fully encrypted
-It is successfully rooted
-I have installed Rom Manager with CWM 6 as the custom recovery
-I want to make a NANDROID backup (to eventually install Carbon), but whenever I try to reboot into the backup/recovery mode, it won't, it goes to what I think is the ADB screen? Not sure tho, this screen says "Connect data USB." Then, when I do, it just changes state and says USB connected, nothing else happens. Then I just reboot the phone normally and everything still works.
So after googling and researching a lot, I'm assuming since my phone is encrypted it won't access the CWM because it never asks me for my password to decrypt the internal storage. Ok cool, but here's my question now tho; if I perform a Factory Reset from the settings menu, will it actually do the reset and reinstall itself since I have CWM installed??
Thanks for any help.
Anyone got any ideas??
Is your bootloader unlocked?
Sent from my XT907 using xda app-developers app
Hmm. Is this screen where it says "Device is LOCKED" mean that my bootloader is locked? Btw, this is the screen that I referred to in my first post. It comes up whenever I try to select "Recovery"
Your bootloader is locked and on that version it can not be unlocked... So... unfortunately you can not install a custom recovery... Well you can use safestrap but the ROM selection is very limited...
Sent from my XT907 using xda app-developers app
So you say I cannot install a custom recovery, do you mean a different ROM that I would "recover" to install it? Or do you mean ClockworkMod (and its various counterparts)? Because in the ROM Manager app, it says I have CWM 6.0.4.4 as my "current recovery" (see attached screenshot)
Please forgive me if this is a dumb question lol but like I said, I'm new at this whole thing
It does say that huh unsure as to why... i do have a locked M around here somewhere ill see if it does the same thing to it...When I say custom recovery I do refer to cmw n twrp... With a locked bootloader you can not install those... we have for safestrap as a recovery for locked bootloaders it's been a year since I used it but I believe you can make backups on it... I would just sit tight and.wait on kit kat it shouldn't be to much longer... till then just freeze all the bloat and use xpossed to your liking... When kk comes out I'm sure development will pick up for locked bootloaders again..anyone else with more experience care to provide more in depth assistance..
Sent from my XT907 using xda app-developers app
So any further advice on what I can or can't do?
I would like to perform a factory reset on my device to get rid of this stupid encryption (it slows everything down), but with CWM installed (supposedly?), can I still do a factory reset? I guess what I'm trying to get at is what does the factory reset option use to re-flash everything from? The recovery partition where CWM is now supposedly installed? Will that affect the factory reset?
I hope this makes sense, I don't want to brick my phone...
Alrighty, for anyone interested:
I never tried the factory reset. What I did do is try the OTA KitKat update just like 2 hours ago. That was a mistake; upon downloading and automatically rebooting to start the upgrade, my phone would not reboot, it got stuck at the AP Fastboot screen with the error code 0x56 (see attached picture).
So, I powered off and powered on my phone, at which point it powered up normally, until after about 2 minutes on the home screen, it automatically rebooted itself (to presumably "continue" trying to install the OTA). Then it got stuck again on the AP Fastboot screen. This continued over and over and I soon realized I soft bricked my phone.
Did some further research, found the House of Moto program (http://www.droidrzr.com/index.php/topic/28162-house-of-moto-22/) which saved my life. If anyone is having any issues similar to the situation I was having, or just issues with the KitKat OTA, this House of Moto program will restore your phone to completely stock. Just follow the instructions on that web page exactly. Kudos to the dude who developed that.