Database Develop

[How To] Downgrade 2.2 To 2.1

Not sure if this has already been posted somewhere, but after my experience I figured it might be useful to someone. If it's been posted already ignore this and move on with your day/night
1. flash sbf
2. phone will go in the boot loop of death, thats fine lol.. when rsdlite says 100 percent pull the battery
3. put the battery back in, hold down the home button plus the power button till you see the moto logo followed by the triangle
4. hit search button, your now in recovery
5. do a factory restore
6. once complete reboot phone
7. thank god and swear you wont flash your phone ever again (ofcourse only to do it in a day or so after you have calmed down)
rsdlite and sbf can be found in this thread CLICK

If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.

taypotts said:
If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.
Click to expand...
Click to collapse
not sure if you can use bootstrap in froyo, and besides if you ever need to go back to a unrooted state this is the way to go :: cough warranty ::

taypotts said:
If you made a nandroid backup of 2.1 couldn't you just restore that? I'm pretty sure you can. I remember doing it with the Moto Droid.
Click to expand...
Click to collapse
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App

iB4STiD said:
Not sure if this has already been posted somewhere, but after my experience I figured it might be useful to someone.
Click to expand...
Click to collapse
Could you explain?
I am holding off on switching to 2.2, always do to let everyone else find the bugs.
What was your experience?

bad4u6669 said:
Could you explain?
I am holding off on switching to 2.2, always do to let everyone else find the bugs.
What was your experience?
Click to expand...
Click to collapse
what i meant by my experience was downgrading 2.2 to 2.1, My g/f has the droid x, and i am the one to root or mod her phone for her. She wanted to try out froyo and liked the rom alot. there are little bugs i noticed
1. odd little animation hiccup when scrolling home screens
2. lag in gallery
3. what seemed like market delay (but the market has been slow lately, same thing on my vibrant and g1)
but this is a test build not a "final rom"
Like i said downgrading the phone is a little different than other android phones Ive used and i thought this post may help someone out. Im the type of person who wont mod something unless i know i can get back to where i started and with this sbf and "how to" you wont have to worry about that.

pjsockett said:
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
also i believe it updates the radio and kernel.. thanks pj for explaining that

If I wanted to go to 2.1 ,don't see why...at the moment.
Before I do a SBF would it be ok to to do a data wipe and a partition wipe in recovery mode then do the SBF bootrecovery deal???
Thank You

after you upgrade to 2.2 koush has a new DroidXBootstrap.apk out
go back to his website and DL it and reinstall then rerun bootstrap.
after that rom manager can do backups or recoveries.
sucks you all get bootloop with sbf, ive done it twice now and has worked fine
keeps all my apps and stuff
goodluck

pjsockett said:
Do not restore a 2. 1 nandroid in 2. 2. The update changes the bootloader and recovery versions which aren't part of the backup. The phone will just hang at the MOTO logo. I learned this the hard way. You have to use the sbf. You can then apply your nandroid to get everything back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I'm kinda confused what you mean? I did a nandroid backup of 2.1 with the latest bootstrap and clockworld.
I just remember using a nandroid on my girl's moto droid and I went from 2.2 all the way back to 2.0.1.

when trying to sbf on my Mac I get this -bash: ./sbf_flash: Permission denied? Any suggestions I have been asking for 2 days now hopefully someone can help. Thanks

taypotts said:
I'm kinda confused what you mean? I did a nandroid backup of 2.1 with the latest bootstrap and clockworld.
I just remember using a nandroid on my girl's moto droid and I went from 2.2 all the way back to 2.0.1.
Click to expand...
Click to collapse
I also did the same from my Eris. The major difference is that the recovery on those devices were completely replaced not just patched. When you restore a 2.1 nandroid from a 2.2 droid x the android 3e recovery is not replaced. When the system tries to boot it sees that as an invalid recovery image and won't boot, it just hangs at the moto logo forever. When you upgarde to 2.2 on a Droid or an Eris your still using clockwork recovery or amon ra's recovery and not upgrading to the android 3e system recovery. Maybe it was just a fluke that it didn't work for me but it makes sense as to why it would fail, otherwise we would be able to have a full custom recovery.

dscottjr81 said:
when trying to sbf on my Mac I get this -bash: ./sbf_flash: Permission denied? Any suggestions I have been asking for 2 days now hopefully someone can help. Thanks
Click to expand...
Click to collapse
From my understanding sbf_flash is for linux only. To flash on mac you need to use rsd lite with a virtual windows os.
http://www.droidforums.net/forum/droid-hacks/38671-flashing-sbf-mac.html

i cant get my phone to flash. i have done this 2 before with my droid x on 2.1 but now that i am on 2.2 every time i try to use RSDlite, i connect my phone and select my SBF but the START button will not light up so i cannot proceed. any thoughts.. im running windows 7 64 and i have all the drivers working for my phone.

failed sbf flash
Hey guys, i got an error in RSD that says "Failed flashing process. Failed flashing process. Phone[0000]: Phone is not compatible with muli-interface super-file. (0x703B); phone connected
Any ideas, i'm really new to android stuff, been using WM forever.
Thanks for the help

please ignore me as I can't read apparently
if anyone else sees this remeber to copy the pst_flash file to the Program Files/Motorola/RSDLite directory

tacticalmedicokc said:
please ignore me as I can't read apparently
if anyone else sees this remeber to copy the pst_flash file to the Program Files/Motorola/RSDLite directory
Click to expand...
Click to collapse
thanks. i had the same problem.

RAZR recovery on Droid 4?

Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283

jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?

I didn't think safestrap was working with the D4?

jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom

Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk

jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.

I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.

mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok

Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App

greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.

Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App

Send me your email addy in a message and ill send you a pic of it

Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?

Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.

Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.

Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.

Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.

Yes there is quite a few. Ill let you know as soon as i can

[ROM][JB+, 4.2.2]OFFICIAL AOKP for Droid 4 [LATEST BUILD 5-23-13][NIGHTLIES]

****ALL CREDIT FOR THIS GOES TO HASHCODE AND DHACKER****
I saw this rom on hashcode's rom page, but didn't see a thread for it here. So I decided to create one.
Discuss bugs, experiences, questions on this thread I guess.
Installation procedure should be the same as CM10.1:
"Using this ROM requires Safestrap v2.11 OR SAFESTRAP 3.X currently. As things progress we may add support for Bootstrap or others in.
In all cases moving from ICS to JB, I recommend a full wipe and Titanium Backup restore of just apps+data.
If moving from KEXEC STOCK there might be some issues where you will need to wipe and restore. Be aware.
INSTRUCTIONS FOR FLASHING:
1. Download the ROM from the above link
2. Grab Jellybean GApps
3. Place both files on your SD card
4. Reboot into Safestrap by pressing [menu] at the splash screen
5. If necessary format /system when swapping from ICS to JB to make sure that GApps and other files are reset correctly
6. Also if necessary do a wipe of data/cache (when moving between ICS and JB)
7. Flash the .zip files as normal
8. Reboot and let the phone sit for about 1 minute while it re-indexes files, etc."
Click to expand...
Click to collapse
Able to be installed on ANY slot in safestrap 3.x.
Build 6 and on is kexec, needs to be installed on romslot-2, as pointed out by Kwyrt
http://goo.im/devs/aokp/maserati
jsnweitzel's AOKP builds, among other Droid 4 goodies: https://www.dropbox.com/sh/mhmmrku5e4x8boj/hbd5BE-Nae
The rom runs same as CM10.1, but has some other awesome features added to it
If you have any questions for Hashcode about this, I think it would be best to contact him on twitter at http://twitter.com/Hashcode0f

alex94kumar said:
****ALL CREDIT FOR THIS GOES TO HASHCODE AND DHACKER****
I saw this rom on hashcode's rom page, but didn't see a thread for it here. So I decided to create one.
Discuss bugs, experiences, questions on this thread I guess.
Installation procedure should be the same as CM10:
http://rombot.org/ROMs/maserati/aokp/
The rom runs same as CM10, but has some other awesome features added to it
SCREENSHOTS
(hashcode, if you see this and anything needs to be added, PM me or post it here, ill edit this OP post accordingly)
Click to expand...
Click to collapse
Global Data and Voice calls working?
What are Things that are added apart from hashcode ROM?
Saw the screenshots, very beautiful.. Lot of features seems added.:good::good:

I have been running Stock based AOKP for about a week now and it runs well. The only issue I have with it is no flash for the camera.
I also have been building my own from hashcode and dhacker29 source. I noticed that the stock-aokp build on rombot is a couple of days old. Here is one I did yesterday that is android 4.1.2 : http://forum.xda-developers.com/showthread.php?p=31584441#post31584441

yeah, there are workarounds for most of the bugs in this rom

NEW BUILD, 10-14, updated in OP. This AOKP build has been merged with JB 4.1.2

The ota updater is fixed now too. No more prompts to update to an older rom. But no flash for the camera still.
Sent from my XT894 using Tapatalk 2

im just waiting for camera flash or mms to work... id be happy with just one of those

He's about to go beta with ssv3, I'm sure then they will focus on the kenex builds and get everything working.
Sent from my DROID4 using Tapatalk 2

I think you mean kexec?

I just updated to SS3 and followed all of the instructions, once I rebooted to the new recovery my phone bricked. I was running CM10 on the DROID 4 and now I'm stuck in a boot loop. I tried flashing RSD fastboot files but still no go. Any suggestions?

f0r71fy said:
I just updated to SS3 and followed all of the instructions, once I rebooted to the new recovery my phone bricked. I was running CM10 on the DROID 4 and now I'm stuck in a boot loop. I tried flashing RSD fastboot files but still no go. Any suggestions?
Click to expand...
Click to collapse
Just to be clear, you are actually bootlooping, not getting any error messages, yes?
Second, try wiping data in stock recovery.
Let us know if that works!

f0r71fy said:
I just updated to SS3 and followed all of the instructions, once I rebooted to the new recovery my phone bricked. I was running CM10 on the DROID 4 and now I'm stuck in a boot loop. I tried flashing RSD fastboot files but still no go. Any suggestions?
Click to expand...
Click to collapse
Not sure if I can help, but certainly interested in what happened to cause it. Did you boot back to stock and uninstall the older safestrap first? If you can still get to the recover there must be some way to get it working again.

podspi said:
Just to be clear, you are actually bootlooping, not getting any error messages, yes?
Second, try wiping data in stock recovery.
Let us know if that works!
Click to expand...
Click to collapse
I ended up doing this right after i made my post and it booted up.

I to boot looped my phone, so i wiped data and factory reset in stock recovery, which once it booted, i disabled super user than re enabled it, which then i was able to update it and get busy box installed than install SS3 and everything is back to normal

Glad to hear it all worked out for you

This latest build is awesome. I got a good battery life and smooth as butter. Love it so far and definitely my daily driver. I just found that checking global options makes gsm function. But,signal won't come out. Cdma ruim works fine.
Sent from my XT894 using Tapatalk 2

I have stock camera working on 10-14 build! it has never worked on any previous build, I've done nothing different.
however, there is still no camera flash.

I've seen this problem on other AOKP ROMs... how do I disable the AOKP Statistics notification that keeps popping up? Already ticked and unticked the report checkbox. I just cleared Settings data/cache so maybe that will change it.
Also, how about we "kang" the lockscreen options from CM10. Miss those already.

Freezing??
Has anyone experienced their D4 freezing up and then rebooting itself?

Briteyez83 said:
Has anyone experienced their D4 freezing up and then rebooting itself?
Click to expand...
Click to collapse
Yup, last night when I was trying to use the Alarm Clock, and then again today with the Camera. This one has some neat features (Status/Notificaiton Bar customizations are outstanding) however its not quite un-alpha enough to use as a daily driver for myself. I will be keeping an eye on this one though, its looking very promising.

[Q] new OTA update bricked my phone

I need some help. My phone is capable of booting into fastboot mode, but doesn't seem to be able to boot normally.
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?

doctor_evil said:
I need some help. My phone is capable of booting into fastboot mode, but doesn't seem to be able to boot normally.
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
Click to expand...
Click to collapse
In the fastboot screen whats version is your booloader ?
Sent on my Gummy running Lenoto X

looks to be the one that I shouldn't have installed the OTA update. why in the F would they send me an update that isn't compatible with my bootloader version?
Well they're getting it back for a repair, I didn't pay 399 for a developer edition phone just to have a dang paperweight because they sent me an incompatible OTA update.

doctor_evil said:
looks to be the one that I shouldn't have installed the OTA update. why in the F would they send me an update that isn't compatible with my bootloader version?
Well they're getting it back for a repair, I didn't pay 399 for a developer edition phone just to have a dang paperweight because they sent me an incompatible OTA update.
Click to expand...
Click to collapse
They didn't send you a incompatible boot loader, the ota's always come with a new boot loader, so what I like to know is, what version is your boot loader , its Motorola's fault that you accepted the ota while having a custom recovery, had you read my thread here http://forum.xda-developers.com/showthread.php?t=2639102
You wouldn't have any issues.
If you don't want my help, thats fine by me, getting tired of this ota crap anyways
Sent on my Gummy running Lenoto X

Clearly you don't really want us to help or you would have answered the previous posters question. You also gave no details into if you had rooted the phone or unlocked the bootloader.
From the bootloader screen select the "factory" option.

I may agree with the op here. Moto supplied me with a 4.4 version for my dev ed. If I take an update, have an issue and moto still only provides 4.4 sbf what a I supposed to do?
However, OP you do need to supply more information as we can only speculate as to what your issue is.
Sent from my SM-P600 using Tapatalk

edthesped said:
I may agree with the op here. Moto supplied me with a 4.4 version for my dev ed. If I take an update, have an issue and moto still only provides 4.4 sbf what a I supposed to do?
However, OP you do need to supply more information as we can only speculate as to what your issue is.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Its not moto's fault, its up to the user to make sure you read the sticky notes, read the threads and search, moto puts out the ota for unrooted users.
Sent on my Gummy running Lenoto X

flashallthetime said:
Its not moto's fault, its up to the user to make sure you read the sticky notes, read the threads and search, moto puts out the ota for unrooted users.
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
However I purchased a Dev Ed phone. Motorola supplied me with a recovery firmware to restore my device to stock. I therefore expect the Factory supplied firmware to not brick my phone. If Motorola makes changes in an update that would cause previous versions of their software to damage phones when used as supplied Motorola needs to bear some of the responsibility. They can build a failsafe into the update that would prevent an attempt of a downgrade, supply upgrades that can safely be downgraded, add some kind of notification or not market "Dev Ed" phones for mass consumption.
Sent from my SM-P600 using Tapatalk

But the update clearly and concisely says, YOU CANNOT roll back to a previous firmware after applying said update.
Onus is on the user at that point.

I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.

Tx Redneck said:
But the update clearly and concisely says, YOU CANNOT roll back to a previous firmware after applying said update.
Onus is on the user at that point.
Click to expand...
Click to collapse
Does it? I never saw that going to 4.4. As long as they put a new sbf up all should be fine.
Sent from my SM-P600 using Tapatalk
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
Did you call Motorola?
Sent from my SM-P600 using Tapatalk

doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
UPDATE:
I tried again to select the factory option in fastboot and unlike the previous times I had tried, this time seems to have fixed it. It booted up into Android OS. I think I'll try the OTA once again and see if this time is more successful, as if it screws up again I have a repair rma number and a fedex shipping label, but hopefully it does better this time.

doctor_evil said:
UPDATE:
I tried again to select the factory option in fastboot and unlike the previous times I had tried, this time seems to have fixed it. It booted up into Android OS. I think I'll try the OTA once again and see if this time is more successful, as if it screws up again I have a repair rma number and a fedex shipping label, but hopefully it does better this time.
Click to expand...
Click to collapse
ok OTA successful this time.
does anyone know if it's possible to boot the moto-x off a custom recovery using fastboot like we could for the galaxy nexus? I'd like to get root reinstalled but I don't want to mess with the current recovery, which should help I would think in regards to being able to install OTA updates without major issues.

doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
Maybe try this out.. option 2 http://forum.xda-developers.com/showthread.php?t=2446515

doctor_evil said:
ok OTA successful this time.
does anyone know if it's possible to boot the moto-x off a custom recovery using fastboot like we could for the galaxy nexus? I'd like to get root reinstalled but I don't want to mess with the current recovery, which should help I would think in regards to being able to install OTA updates without major issues.
Click to expand...
Click to collapse
Unfortunately, I don't believe it's possible to fastboot boot recovery. It's how I did everything with my Galaxy Nexus and Nexus 7. I was disappointed to find out it isn't possible with the Moto X Dev edition even though I didn't buy one.

nhizzat said:
Unfortunately, I don't believe it's possible to fastboot boot recovery. It's how I did everything with my Galaxy Nexus and Nexus 7. I was disappointed to find out it isn't possible with the Moto X Dev edition even though I didn't buy one.
Click to expand...
Click to collapse
has anyone tried it with the google play edition of the moto-g? I'm wondering if there is a way to convert from a regular retail rom over to a GPE rom for the moto-x after google starts selling it. I remember reading about them going to sell a GPE of it. Hopefully the GPE rom would be friendlier than the retail rom

doctor_evil said:
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
Click to expand...
Click to collapse
I know you have fixed this now, but if you see the android with the red triangle and ! use the key combination pwr & up vol. That gets you into stock recovery and from there you should be able to boot up.

I have no idea what happened but TWRP restore killed it

Ok so I took the OTA lollipop update, rooted and the phone was rocking. Installed TWRP backed up including cache and boot. I did factory reset and restored from backup file and I couldn't get past the boot animation. I downloaded these files http://forum.xda-developers.com/mot...g-lxe22-39-6-pure-edition-stock-boot-t2940437 and ran these commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Then, I lost the boot animation, only had the boot image. Then a lot of mfastboot stuff and I am back at on a fresh unrooted KK...... Any ideas wtf happened? Was it TWRP, restoring the cache or what? This is my fist no Sammy device so it's a learning experience.

I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk

dobbs3x said:
I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.

TWRP has been horribly quirky for me on my Moto X. I can't even get it to boot into recovery half the time, among other things.
Sent from my iPhone 6 using Tapatalk

cam30era said:
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.
Click to expand...
Click to collapse
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.

dobbs3x said:
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.
Click to expand...
Click to collapse
Aahh. Good point. I've made a backup and flashed .zips. But have not tried to restore a backup. Thanks for the heads up.

I now know the restore of TWRP backups is what did it. I have successfully recreated the issue twice with the exact same results.

Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
Currently what I have done is just:
- unlocked the bootloader via moto site.
- fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
- installed/updated SuperSU via Playstore
- installed updated Binary via SuperSU
Back when I had the Nexus 5, I would change the DPI with DPI changer, but on some ROMs, flashing an updated GAPPS/etc would break the ROM, because of the DPI Changer... (I would just do a NAND restore/TWRP restore) How can I full-proof my current setup so that when I mess up I can always have something to fall back on?
From what I read above flashing TWRP is no ideal yet as NAND backups don't restore? is that right?
I'm just running stock Bootloader/Recovery right now, and I'm not sure how to fail-proof myself.
If I stick to default bootloader/recovery can I just flash default KitKat/Lollipop image to restore/fix any issues?
Lastly, on boot, that "Unlocked Bootloader" message comes up, it's not the worst, but from what I understand people flash a bootloader/recovery that removes that warning?
Thanks for help.

Shemploo said:
Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
.
Click to expand...
Click to collapse
Edit build.prop :good:

TigerDNA said:
Edit build.prop :good:
Click to expand...
Click to collapse
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop

Shemploo said:
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop
Click to expand...
Click to collapse
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.

TigerDNA said:
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.
Click to expand...
Click to collapse
Maybe someday, but right now I do not have time to learn, and the few times I tried to learn to program was a long time ago and it did not go well.
I would certainty like to go into Android programming, but for my short time needs, I guess I'm wondering how, if anything.. one can do to have an easy fix to breaking the OS/ROM, since TWRP back-ups don't seem to work for this device right now.
What is hard brick?, can anything I mess up software wise be restored via flashing factory images?