Develop Bugs

Downgrade from JPH to 2.1

Hi all,
Can anyone tell me how (if possible) to downgrade back to 2.1 (JM5 or JM8) successfully as each time i try all i get on the first reboot is an error (cannot see error as to quick) which then reboots?

DemolitionManHD said:
Hi all,
Can anyone tell me how (if possible) to downgrade back to 2.1 (JM5 or JM8) successfully as each time i try all i get on the first reboot is an error (cannot see error as to quick) which then reboots?
Click to expand...
Click to collapse
And you didnt read the big explanation of how to do it in first posts in jm6 (not sure), jm7, jm8 and ji1 threads why?

dupel said:
And you didnt read the big explanation of how to do it in first posts in jm6 (not sure), jm7, jm8 and ji1 threads why?
Click to expand...
Click to collapse
Which post?

DemolitionManHD said:
Which post?
Click to expand...
Click to collapse
Ever heard of search function? Or at least look through 2-3 pages, its not that hard.

dupel said:
Ever heard of search function? Or at least look through 2-3 pages, its not that hard.
Click to expand...
Click to collapse
Not to be funny but looking through there is a number of post referring to this, thats why i ask which one you are referring to

yep. downgrade straight off the bat, JPC is the wicked error rom which raped yer efs

Just page 2 (and when you started this thread - page one) contains 2 topics by the name:
Release: I9000XWJM8 - Multi CSC(s) Europe (and ji1 obviously) with deteiled instructions on how to install, downgrade and possible solutions to problems.

azuresystem said:
yep. downgrade straight off the bat, JPC is the wicked error rom which raped yer efs
Click to expand...
Click to collapse
Is there a way without errors, if i could see the error as it reboots of screen to fast.

Oops. My bad please ignore

format the drive, i.e hardreset it before you reflash pull out yer sim n external SD etc
1 : hard reset
2 : DLmode
3 : flash yer rom
4 : recovery mode
5 : new hardreset
6 : start up yer rom
if you still keep getting errors i have no clue, only managed to get those while the sd still being in the phone and another partition mounted on the sd
best of luck and read the guides

azuresystem said:
format the drive, i.e hardreset it before you reflash pull out yer sim n external SD etc
1 : hard reset
2 : DLmode
3 : flash yer rom
4 : recovery mode
5 : new hardreset
6 : start up yer rom
if you still keep getting errors i have no clue, only managed to get those while the sd still being in the phone and another partition mounted on the sd
best of luck and read the guides
Click to expand...
Click to collapse
Cheers m8

Interesting to know why would want to downgrade to eclair?

Hi, mainly for reference and current issues i have
Sent from my GT-I9000 using XDA App

nandihno said:
Interesting to know why would want to downgrade to eclair?
Click to expand...
Click to collapse
Possibly as JPH sux big time.. just spent hours trying all sorts of combinations and man it spoils the phone.
Hope Samsung get the REAL release working well..
TrOjAn

TrOjAnUK said:
Possibly as JPH sux big time.. just spent hours trying all sorts of combinations and man it spoils the phone.
Hope Samsung get the REAL release working well..
TrOjAn
Click to expand...
Click to collapse
You should try it with the rombie mod. It freakin rocks

Woolios said:
You should try it with the rombie mod. It freakin rocks
Click to expand...
Click to collapse
yes it's awesome, but also a battery monster

azuresystem said:
yep. downgrade straight off the bat, JPC is the wicked error rom which raped yer efs
Click to expand...
Click to collapse
JPH raped my EFS too. I had JPC doing it, fixed it by deleting /efs/nv*. Funny thing is, right after flashing JPH it had my normal nordic product code - but later it had changed to KOR. Very strange. I wonder if it might have happened when I rooted it? Well, anyway, be careful out there, check product code before up/downgrading.

[ROM][DISCONTINUED] ext-sdcard-based - StockG2

discontinued ... due to real root
will post up a real ROM soon.
~enom~

yessss some enomther work on the G2. FIRST

Thank You..
Enom, Thank You soo much for this gift..
Can you please post Screenshots of the Manup Version.. Thanks.

Thank you
Thank you for doing this. Stock android looks so dull.
Do we know if this will still work with the ota update? I would really like a new radio.....

This is too cool!
Wow! thanks. I don't have the G2 yet but am eagerly anticipating its arrival. This will tide me over and let me play with the phone, get rid of the bloatware stuff. Your shot is in the mail!

Would you be willing to post some screen shots of the themed rom or direct me to where there are already some ?

soundslikemitch said:
Thank you for doing this. Stock android looks so dull.
Do we know if this will still work with the ota update? I would really like a new radio.....
Click to expand...
Click to collapse
bled82 said:
Would you be willing to post some screen shots of the themed rom or direct me to where there are already some ?
Click to expand...
Click to collapse
mpmilestogo said:
Wow! thanks. I don't have the G2 yet but am eagerly anticipating its arrival. This will tide me over and let me play with the phone, get rid of the bloatware stuff. Your shot is in the mail!
Click to expand...
Click to collapse
PlankLongBeard said:
Enom, Thank You soo much for this gift..
Can you please post Screenshots of the Manup Version.. Thanks.
Click to expand...
Click to collapse
mcp2009 said:
yessss some enomther work on the G2. FIRST
Click to expand...
Click to collapse
Thanks ... and yea I'll post some screenshots in 30 minutes or so ...
And ... no idea on radio's, OTA's, etc ... yet.
~enom~

very awesome, I will try this just for fun, but I don't think I'll use it full time, I will wait for full root I think.

questions...
Awesome work! Thanks man!
Question 1: do you see things reverting/disappearing over time with this rom... like root does but other files and things too? For example do Market installs survive a reboot? Do Market installs done while in root-mode survive a reboot or leaving of root-mode?

Corylulu said:
very awesome, I will try this just for fun, but I don't think I'll use it full time, I will wait for full root I think.
Click to expand...
Click to collapse
texasaggie1 said:
Awesome work! Thanks man!
Question 1: do you see things reverting/disappearing over time with this rom... like root does but other files and things too? For example do Market installs survive a reboot? Do Market installs done while in root-mode survive a reboot or leaving of root-mode?
Click to expand...
Click to collapse
Thanks ... and yeah ... we can only hope this is temporary for us all!
And yes ... everything sticks through reboots
Best results with (2 ext3 partitions though) ... as described in the OP ... if you use a single ext3 partition ... the on emmc OS and the ext3 OS will have to change portions of the /data userspace stuff on each boot, which could lead to several issues ... thus I *highly* recommend the 2 ext3 partition setup.
But in general everything should stick through reboot ...
-
-
-
-
-
-
ALL ... updated the OP with screenshots of the manup456 prethemed version.
~enom~

.very nice.

Absolutely sexy, cant wait to rock this on my G2. Thanks!!!

Ok so i finished all the steps and after setup i got install complete then i ran start rom and nothing happened the device does not respond to touchscreen or home button , please help. I am running the manup's theme it installed without issue i have 3 partions when i run startrom it never launches . The first install failed due to error with rsync file , i then started all over and re-ran all the adb commands and then setuprom and startrom and stuck at termianl app with nothing happening ?

Thanks Enomther!
One thing I've noticed while running Manup's theme is the analog clock widget would disappear leaving only the hands in place still. I'm not running the third partition.

Worked like a charm on 2 partitions, gonna try and get Benji to partition it 3 way tomorrow =)

When running setuprom, it seem to hang at "Syncing user /data ... "

Same here, error at rsync...

kdmytro said:
Same here, error at rsync...
Click to expand...
Click to collapse
MattKilla said:
When running setuprom, it seem to hang at "Syncing user /data ... "
Click to expand...
Click to collapse
bled82 said:
Ok so i finished all the steps and after setup i got install complete then i ran start rom and nothing happened the device does not respond to touchscreen or home button , please help. I am running the manup's theme it installed without issue i have 3 partions when i run startrom it never launches . The first install failed due to error with rsync file , i then started all over and re-ran all the adb commands and then setuprom and startrom and stuck at termianl app with nothing happening ?
Click to expand...
Click to collapse
Make sure if that your 2nd and 3rd partitions on your sdcards are "primary ext3" partitions. Otherwise you will experience strange results such as these. :/
I may update and put in some more error checking prior to installation.
~enom~

Thanks Enomther.. excellent!

looks awesome, im going to need to get my g1 back to partition my card.
Will installing this rom still allow us to recieve an OTA update?

[Q] We Can Now Dual Boot With Boot Manager App!!!

Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Update: I'm now running 2 AOSP roms Kushdeck's 1.3b2(main rom) and SalvageMod 1.4 and a Sense rom SynergyRls1 and haven't noticed any major issues. Gps works on each rom as well as 4g. Synergy does have some lag and for this reason took some patience and a little longer to initially set up but it works decently for running off of an sdcard. On a side note I've heard claims that Synergy does have some lag issues running normally.
I plan on ordering a better sdcard with a faster class rating such as class 4 or 6 so hopefully this will decrease lag but overall I'm very impressed with Boot Manager. If nothing else this gives you a chance to test drive roms without having to go through the whole process of replacing your daily driver.
PLEASE READ: I've reached out to one of the developers of this app who's from XDA and asked for his help in answering the problems some of you are having. I wish I could help more especially since this a paid app and you guys deserve to have an app that work. Below are the links to email support through the app website as well as the one of the developers Conap who's from XDA. Maybe if they receive enough emails they will shoot over to this thread to help.
Sorry I can't help more. All I can do is verify that it's working on my Evo but don't have enough advanced skills to do a lot more.
App Support Address: [email protected]
Conap Contact (One of the Devs from XDA): http://forum.xda-developers.com/member.php?u=2468293 (I just pm'd him)

aerajan said:
Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Click to expand...
Click to collapse
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.

mattykinsx said:
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.
Click to expand...
Click to collapse
Yea that's a good point. I'm running Kushdeck's 1.3b2 gb aosp as my main rom and didn't even think of that.

https://market.android.com/details?id=com.drx2.bootmanager

Alright, this looks really great. Love the idea. Just wondering for those who have it, since there are different kernels associated with each ROM (going from CM to Synergy) would you have to go back in and wipe battery stats? Also, would vipermod carry from ROM to ROM or would you need to set it up for every ROM?
How much room on the SD card would you need to boot 5 ROMS?
edit: quite a bit of room, have over a gig on sd card and can't load synergy. Have to do some cleaning later. Wish it could import nands, that would rock.
edit 2: cleared room, installed synergy on slot 1, rebooted, hanging on evo 4g screen..... bah

Im trying this now. I have Mikg as my phone rom and installing miui as a test. Will report back when I do some testing on kernals and battery life.

I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App

i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.

yeah crazy... stuck in splash screen sooooo yay no bueno thus far...

locoboi187 said:
I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
alaman68 said:
i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.
Click to expand...
Click to collapse
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
jbrawley1 said:
yeah crazy... stuck in splash screen sooooo yay no bueno thus far...
Click to expand...
Click to collapse
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.

It takes a while. Since it's booting from your sdcard it's not quite as fast the first time as when you normally flash a rom. Mine stayed on splash screen for a little while to the first time I rebooted. Also try another rom just to see if that works for you.

aerajan said:
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.
Click to expand...
Click to collapse
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App

Omfg will download and test this out ASAP and report back results!!
Sent from my PC36100

locoboi187 said:
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Ext 2 because it's compatible with more roms.

aerajan said:
Ext 2 because it's compatible with more roms.
Click to expand...
Click to collapse
still no go, error building the boot
Sent from my PC36100 using XDA Premium App

Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Also if you go back to OP I've posted links to email support or one of the devs who's from XDA. I pm'd him personally asking if he's willing to shoot over here and try to help. If you get the time send him a PM. Maybe if enough people from here contact him he will help.

aerajan said:
Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Click to expand...
Click to collapse
Thanks
Sent from my PC36100 using XDA Premium App

It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).

pottyvick said:
It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).
Click to expand...
Click to collapse
I wonder what steps the other guy took to get it working on his evo
Sent from my PC36100 using XDA Premium App

well... ive gotten this to work with Miui as main rom, and Synergy Kingdom port 7/23 but confirmed i dont believe that synergy rls 1+God Mode ive tried tons this wont work...
pretty cool you can switch between aosp and sense pretty easily i like this lots hope in the future it becomes more stable and compatible!

Clockworkmod for Ion

Anyone tried building a clockworkmod image from builder.clockworkmod.com? If we can get a good image maybe we can mod the rootingkit to flash that image instead of the Xperia S one. I am going to try in a day or two, but this will be my first time trying.

Just a follow up on this: I think I finally found the right way to build this, but I am afraid it will take more than a few attempts to get it right. I did find the dev/block locations to pull. I just have to get everything finalized on my new Ubuntu partition so I can do this properly. (Man, a lot more work then what I thought it would be)

popfan said:
Just a follow up on this: I think I finally found the right way to build this, but I am afraid it will take more than a few attempts to get it right. I did find the dev/block locations to pull. I just have to get everything finalized on my new Ubuntu partition so I can do this properly. (Man, a lot more work then what I thought it would be)
Click to expand...
Click to collapse
I'm willing to test for you. when you are ready, just message me.
That goes for ALL devs for this phone... I am NOT afraid to test, so hit me up. Email and personal number via PM if you prefer faster more reliable communication.

Pl. Look into this.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Sent from my LT28h using xda premium

ganeshbiyer said:
Pl. Look into this.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
I was using that, but the problem is that is not updated for the newer stuff. I am using http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-os-x-part2/ as a guide which has more compressive information about how to build it.

Ok, I was able to find what I think was the kernal but the recovery sector is messed up a little I think, due to having a bad recovery sector. Looks like I am going to have to root without the Clockworkmod recovery built into it, so I can extract the recovery sector correctly.

Well, I think I might be able to fix the Xperia S one as I could not figure out how to extract the right folders and stuff. I was looking at the recovery.fstab and it has the wrong mounts for us. So I think that if I fix them then we can have a usable recovery.

popfan said:
Well, I think I might be able to fix the Xperia S one as I could not figure out how to extract the right folders and stuff. I was looking at the recovery.fstab and it has the wrong mounts for us. So I think that if I fix them then we can have a usable recovery.
Click to expand...
Click to collapse
Doesn't look like it worked.

[RECOVERY] TWRP-2.7.0.0-moto_msm8960-hdpi.img YOUR, pre Nov 8, TWRP IS BAD!

Update twrp 2.7, see Dhackers link for the img. Use Recovery Tools from Play to flash from home.
Seems that only Dhackers latest TWRP is the one to use.
Thanks to cyanidium for making it evident to me anyway.
Dhackers msm8960 goodies: http://androidhosting.org/Devs/Dhacker29/msm8960/
BTW Does anyone know what "twrp263-M44.img" is?
Attachments: the ...M44 is 1 day newer & works.
Just extract these to get the fastboot img.
More details
http://forum.xda-developers.com/showthread.php?t=2612883
More conformation http://forum.xda-developers.com/showpost.php?p=49978993&postcount=79
This one is not Dhacker latest anyway :
http://forum.xda-developers.com/showpost.php?p=45688558&postcount=1
Md5 starts with 791.
Want to try Philz.
http://forum.xda-developers.com/showthread.php?t=2545120
Want The latest 2631? w/ SDext usb mount. What is the rub?
This Photon Q TWRP, with full SD mount & more, works on the M! See attachments for the flash-able ver. Now for the rub: screen input requires the mirror of the buttons. I am uploading the very zip from the twrp mounted SD while the phone is in recovery. BE CAREFULL.... It is really not that hard to use. Think of it as a game also.
Md5 : 7630baf88ec9d6c2a144a2ee86ec9bb7

I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
No settings, just bad! Thanks for the conformation Watson! We on a train with a new engine!!!

Germanese said:
I also had issues flashing some roms with 791.
e33 I was able to flash my brains out with 8 different roms with in 2 hours time span.
791 I had to resort back to Flashing Stock Rom via RSD and start over few times after softbrick.
So not sure what it is maybe slight tweaks in the settings ?
Click to expand...
Click to collapse
How long have you known about it?

aviwdoowks said:
How long have you known about it?
Click to expand...
Click to collapse
I came across this issues first time trying to flash Paranoid and Pacman.
Which left me soft Bricked or in Bootloops. At the time i was just too fed up and went back to stock
second time i encountered that, was with the first stable KitKat by Dhacker.
That's when i decided to start clean and deleted all my Pre downloaded files and I was forced to download the new E33 from Dhacker.
And along with that all my other Roms and Files. I kind of figured something was bad with my TWRP file. But never thought of it since 791 wasnt found by my search engine.
And this December when I was flashing my GFs phone that's when I confirmed that the 791 didn't work for any of my roms.
Because I couldn't find Dhackers E33 through Google.De search (Some odd way searches come up differently if you search from different country)
And it did the same issues I had the First time around. That's when i dug around more and found Dhackers TWRP.
After using that I was able to flash Roms like a mad man until I found a Rom that my GF was comfortable using and liked.

Germanese said:
I came across this ....GF was comfortable using and liked.
Click to expand...
Click to collapse
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Ohh well now we all know!
Thanks again for the history.
This screwed up my data partition & I could not determine if it was philz or this. Then I decided the stop one, as I would go to the other & then data restore failure, so I used just philz & the problem went away!

aviwdoowks said:
It's news to me. Did you post about it? Jbaumert has a 1000 + DL of a bad recovery! Your GF distracted you? Lol.
Click to expand...
Click to collapse
Nah i didn't post about it back then and recent we were side tracked ahahaha.
And I actually just got back couple days ago ... work ugh hate it already ...
There maybe a post few months back, me asking somewhere about which TWRP people are using,
because I had my doubt on which one to use; but no one really bothered to respond.
Then i just decided to flash away with what ever, since most errors resulted in an Harmless SoftBrick.
Since i figured a way around to that soft-brick, my thought was, what worse could happen, I did worse before LOL
I won't take credit, just stumbled upon it... That's all you. Just here to Confirm that i did have issues with that version.
Since then I been trying to see CWM for KitKat LOL

Hmm...
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?

Twilla said:
So I should be using this (xt907- twrp263-M44 -flashable.zip) instead of the TWRP here?
Click to expand...
Click to collapse
Yes or the e33.
Not sure which is better. Philz is newest & I have an ini file to help you set it up see #2 post.

Update.
Haha. But not a joke. PHOTON Q twrp 2631 up.

twrp 2631 maybe provided by arrrghhh!
http://forum.xda-developers.com/showpost.php?p=49857073&postcount=176
If you want to be synched to his Q versions, go thank him!
That means a good screen version for our m.

Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!

Coronado is dead said:
Installed the m33 in TWRP and every backup I have made thus far has been corrupt. Back to the old one!
Click to expand...
Click to collapse
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.

aviwdoowks said:
I do wonder, if perhaps, the trouble you had with Bones & this could be related?
Just a thought.
Click to expand...
Click to collapse
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.

Coronado is dead said:
Very possible. I am trying to flash back to another Twrp2630 and I am getting an error I have never seen "Variable not supported." Very strange.
Click to expand...
Click to collapse
May I suggest philz new version just out.
Allows you to format many /'s now.
I use only it now.
Not pocket proof like twrp. Beware

New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907

aviwdoowks said:
New 2632 twrp, see the op for Dhackers link to his img.
Here is mhous33's flashable version.
http://batakang.com/ftp/?dir=devs/mhous33/xt907
Click to expand...
Click to collapse
It works fine (I have flashed Dhackers *img) but if we want to flash any ROM we must change updater.script and add moto_msm8960 to device list on it.
I have success flashed BeanStalk after I add moto_msm8960 to updater.script
P.S. Also unified ROMs flashed great!
P.P.S. Gummy is most stable for me from unified ones

Flash TWRP-2.7.0.0-moto_msm8960-hdpi.img with Recovery Tools. See OP.

Would anyone know if Dhacker's TWRP works on the XT905 model as well?

Yes. But that is just good advice. I do not have one.