Database Develop

Does PAC man rom work with safestrap?

I would ask in the thread but I don't have enough posts to ask in there. I have the verizon version, by the way.

Polasja said:
I would ask in the thread but I don't have enough posts to ask in there. I have the verizon version, by the way.
Click to expand...
Click to collapse
Not sure what you mean by that.
And no, PAC works on unlocked BLs only. Unless someone makes it SS compatible

Well ****. I can't unlock my bootloader, unfortunately. Do you think that motorola will allow all phones to unlock the bootloader later on?

Polasja said:
Well ****. I can't unlock my bootloader, unfortunately. Do you think that motorola will allow all phones to unlock the bootloader later on?
Click to expand...
Click to collapse
Unfortunately, its not up to Motorola alone. BL unlock has to be granted by the carrier too. And I dont see VZ doing it anytime soon. Then again, with the Moto X, it doesnt matter all that much. You loose stuff like Active Notification and Touchless Control when you flash AOSP. So, not sure why anyone would want that. Some of the customization that ROMs offer can be had through XPosed Framework.
Someone please feel to correct me if I am wrong.

That would make sense as to why the bootloader hasn't been unlocked yet. I am not really familiar with how all of this stuff works. One of the main reasons why I root my phone is so I can mess with the kernels and achieve better battery life and performance, but I can see why people wouldn't want to switch to AOSP or AOKP because of that Active Notification. Thanks for the helpful information and the quick replies.

[Q] do you think it's possible to flash...

I know this is not the Q&A thread. Don't shoot me. But i figured this was a dev question. Does anybody think or have tried flashing the stock droid ultra ROM to the moto x since they are VERY SIMILAR phones? Is it possible? Can it be done? Has anybody tried? If not and I was to try it do you think I can flash stock moto x IMG files back to normal? Or will i fubar my bootloader. Running Moto x Dev edit Verizon. These are questions that have been running through my head. Just thought I might ask. And is anybody willing to help me look into it? Thank you for taking the time to read and reply.

ryanzurlo88 said:
I know this is not the Q&A thread. Don't shoot me. But i figured this was a dev question. Does anybody think or have tried flashing the stock droid ultra ROM to the moto x since they are VERY SIMILAR phones? Is it possible? Can it be done? Has anybody tried? If not and I was to try it do you think I can flash stock moto x IMG files back to normal? Or will i fubar my bootloader. Running Moto x Dev edit Verizon. These are questions that have been running through my head. Just thought I might ask. And is anybody willing to help me look into it? Thank you for taking the time to read and reply.
Click to expand...
Click to collapse
Very similar is never close enough. Any ROM for a different phone will not work for a different device. Some exploit methods work on multiple devices but never Roms and kernals.

Imacellist said:
Very similar is never close enough. Any ROM for a different phone will not work for a different device. Some exploit methods work on multiple devices but never Roms and kernals.
Click to expand...
Click to collapse
I only asked cause if cm11 pac-rom etc could do it maybe we could. Thanks for answering though. It was worth a shot. I just miss my droid ultra?

They are the same phone in almost every way and yes the builds are compatible, or at least the 4.2.2 and 4.4 builds were last year. When the leaked T-Mobile 4.4 build came out, I was running it perfect on my vzw moto x DE and at least one other person was running it on their droid ultra/maxx with no issues.

So your question for the devs was just answered by non devs. If you KNEW you were posting in the wrong thread, but wanted to make sure you got noticed please follow the rules next time. It's not like you didn't know this does not belong here.

Only try this if you have an unlocked boot loader. If you are locked then you are out of luck. Still recommend finding a build for your phone.
Sent from my XT1060 using XDA Premium 4 mobile app

Travisdroidx2 said:
So your question for the devs was just answered by non devs. If you KNEW you were posting in the wrong thread, but wanted to make sure you got noticed please follow the rules next time. It's not like you didn't know this does not belong here.
Click to expand...
Click to collapse
i posted here thinking maybe devs have already tried it and/or have a workaround for it. i'm not going to start a fight with you over the internet cause thats just petty.

Moved here as this does not belong in the Development Section, OP please read the Forum Rules on posting.

Twrp heads up Safeguard yourself Use Correct twrp

I know TWRP topic has been live I'm just adding this info as a Safeguard heads up for using the Correct twrp for those that never flashed before .
Just wanted to post for those realizing twrp is available to Not flash the wrong one .
Zerofltespr.img is INCORRECT for tmobile s6.I say this because there are 4 to choose from when u use the links to it
It a just a heads up cause that file falls next to the Tmobile version if you are looking for the Tmo.
Make sure to choose 2.8.6.0 zeroflte.img it is 25.2mb
Not 2.8.6.0 zerofltespr.img.
It will not allow you to navigate thru twrp or reboot.
I did this by mistake
If you do by mistake JUST CF AUTO ROOT again and it will restore stock recovery
Sent from my SM-G920T using XDA Free mobile app

Not sure if we need a whole thread on this. People should just read and pay attention before they flash stuff to their phone
Period.

This isn't a New wide spread topic it's a small WARNING tutorial TO save people from a very easily made mistake .I expected this type of response. But the greater number of considerate people would appreciated such a small but usefully tip expecially when you could see this mistake easily being made .
It's a necessary sub topic in regards to 920t TWRP recovery.
Sent from my SM-G920T using XDA Free mobile app

It all good man. Just would be more appropriate to put that info here http://forum.xda-developers.com/showthread.php?t=3080833 where everyone else is talking about recovery flashing. We don't need a whole thread on this.

This is a good warning. I'm pretty experienced with these thing and am careful. I used Flashify to install TWRP because I'm at work. I selected S6 zeroflte and it gave me two options 2.8.6.0 and 2.8.6.0. So I selected the first one and installed it. Had I paid closer attention, after you select the one you want, it confirms the image name and sure enough, the first option turned out to be the Sprint version. So I had to do it again to flash the right one. I by chance stumbled across this thread just an hour prior to running into this issue, so I figured I flashed the wrong recovery. All is well now!

Thanks man for the appreciation. .I'm glad u seen it how i did .All I did was catch hell with this tip
Sent from my SM-G920T using XDA Free mobile app

Thanks for the warning. My cp is down at the moment so I'm in a holding pattern....

Wow thanks for this warning. I've been thinking of flashing TWRP for a while now and this really helped me get it done properly. Used Flashify as well and checked to make sure it was working fine.

Barging in.
Any rom developers out there, should I make zerofltetmo version of TWRP? Basically updating the default.prop to only flash versions for zerofltetmo, or do you all want to use zeroflte?

bigbiff said:
Barging in.
Any rom developers out there, should I make zerofltetmo version of TWRP? Basically updating the default.prop to only flash versions for zerofltetmo, or do you all want to use zeroflte?
Click to expand...
Click to collapse
zeroflte is fine, unless you foresee a reason we should have our own?

@bigbiff Great to see you stop by! So as long as this works for us I don't see anything wrong with just keeping it simple. Is it just the cdma and gsm variants that are different? Just trying to understand this so that I can say I learned something new today! Lol I will say that I am thrilled that you and the TWRP team work so fast and have made huge developments in device recoveries. I thank you for the work that you have done here! Much respect....

shojus said:
@bigbiff Great to see you stop by! So as long as this works for us I don't see anything wrong with just keeping it simple. Is it just the cdma and gsm variants that are different? Just trying to understand this so that I can say I learned something new today! Lol I will say that I am thrilled that you and the TWRP team work so fast and have made huge developments in device recoveries. I thank you for the work that you have done here! Much respect....
Click to expand...
Click to collapse
So far Edge is different between CDMA and GSM, and non-edge CDMA and GSM. So really 4 variants. But one of the big issues seems to be the disparate firmware or OEO issues that people are having flashing the versions I have released. It's hard to get a straight story between real issues and OEO.

bigbiff said:
So far Edge is different between CDMA and GSM, and non-edge CDMA and GSM. So really 4 variants. But one of the big issues seems to be the disparate firmware or OEO issues that people are having flashing the versions I have released. It's hard to get a straight story between real issues and OEO.
Click to expand...
Click to collapse
Well, I have not really had much time to flash anything on this new device but everything that I have has been fine. I will keep you posted in your main thread if I run into any issues but thanks for the response!

Is there a Moto Marshmallow ROM with CDMA support I can flash on my XT1096?

I use Verizon and have a XT1096 that I unlocked the bootloader on and installed CM 13. I really miss the Moto specific features so I'm looking to go back to a Moto ROM. Are there any Moto Marshmallow ROMs that will run on my XT1096 and still connect to Verizon radios?
Thanks!

Please see this thread: http://forum.xda-developers.com/moto-x-2014/development/rom-xt1096-verizon-flashable-stock-rom-t3327345
Please read the whole thread and ask questions as required.

donslade said:
Please see this thread: http://forum.xda-developers.com/moto-x-2014/development/rom-xt1096-verizon-flashable-stock-rom-t3327345
Please read the whole thread and ask questions as required.
Click to expand...
Click to collapse
Awesome, thank you. This is exactly what I'm looking for, not sure how I missed it. Though it seems like it is still a bit too unstable for my liking. I will definitely be keeping an eye on the thread to see how it progresses and I'll probably make the jump soon.
Thanks!

[ROM][Stable]Stock Debloated 1.23.1550.3 MetroPCS

This Is My First Shot at making something for this device,so please bear with me.
This Is A Custom Stock ROM that has been debloated and slimmed down a bit to my personal liking.
ive used SuperR's Kitchen on Ubuntu to bring this to you guys.
i used Captain_Throwbacks Metro Base ROM as a starting point.
i will include my list of apps that i have removed in the second post.
i would suggest a factory reset and dalvik/ART wipe
as always,if your device explodes or stops working,i assume no responsibility for any damages or data loss.
flash at your own risk.
if anyone has any suggestions and/or input,please feel free.
im no developer,just taking a shot at this.
the goal is to remove as much bloatware as possible,whilst maintaining stability.
:highfive:
i added /data/app support as well as busybox & deodexed the ROM.
im currently uploading my first build to google drive and will share links shortly.
bear with me as i dont have the best internet connection.
DeZiREv5K
OP Updated with newer build.
Code:
6-14-16 build changelog
--Removed HTC Launcher(replaced with google now launcher)
--updated play store to latest version
--updated HTC Service pack to latest and integrated back into ROM(no longer needs Seperate download)
--attempted to add back the official metropcs device unlock app(Thanks [user=3100103]@sandix[/user] !)
6-16-16 build changelog
---removed google play launcher & replaced with nova launcher(issue with installment on first boot)
6-19-16 build changelog
-- changed ZIP compression method(v3 was too large)
This is A Flashable Zip,should flash in TWRP.
Special Thanks to the following folks:
@sandix for the continuous hard work in the forums here
@Captain_Throwback for his stock rooted metroPCS ROM.
@SuperR. for his Excellent Kitchen!!!
@nightbreed813 for his thread layout & list of modifications to his ROM

This Is My Bloat_Custom File that i edited by hand to suppliment in the kitchen.
these are all the apps/folders that were removed prior to building.
Code:
system/app/BasicDream*
system/app/Calculator*
system/app/CalculatorWidget*
system/app/Chrome*
system/app/Cloudex*
system/app/CloudPrint*
system/app/Drive*
system/app/DriveActivator*
system/app/Exchange3Google*
system/app/FaceLock*
system/app/Font_Helvetica*
system/app/Font_XinGothic*
system/app/Font_Yuen*
system/app/Gmail2*
system/app/GoogleTTS*
system/app/Hangouts*
system/app/HoloSpiralWallpaper*
system/app/HtcCarGps*
system/app/HtcBackupReset*
system/app/LiveWallpapaers*
system/app/HtcLogLevel*
system/app/HTC_Connect*
system/app/HTCZero*
system/app/IMEMurasuIndic*
system/app/IMEMurasuViet*
system/app/IME_TP_Basic*
system/app/IME_TP_ValueAdd*
system/app/Kidmode-google*
system/app/Maps*
system/app/MPCS_Blockit*
system/app/MPCS_Metro411*
system/app/MPCS_MyMetro*
system/app/NoiseField*
system/app/PhaseBeam*
system/app/Photos*
system/app/PrintStudio*
system/app/talkback*
system/app/YouTube*
system/priv-app/HtcDotMatrix*
system/priv-app/HtcFileManager*
system/priv-app/HtcDLNAMiddleLayer*
system/priv-app/MPCS_MetroAppStore*
system/priv-app/iCloudTransfer*
system/priv-app/MPCS_MetroZONE*
system/priv-app/MPCS_RSU*
system/priv-app/LMIRescue*
system/priv-app/Velvet*
system/priv-app/LMIRescueSecurity*
system/priv-app/HtcSoundrecorder*
system/priv-app/Twitter*
system/priv-app/MirrorLink_MirrorLinkService*
system/priv-app/MPCS_Lookout*
system/priv-app/PolarisOffice*
system/priv-app/Mail*
system/priv-app/HTCSpeakCyberon*
system/priv-app/Facebook*
system/media/audio/notifications*
system/media/audio/ringtones*
system/media/audio/alarms*

TO DO List:
edit updater script to change out rom title
check what works and what does not
(Possibly) remove More files/Free up more space
upload newer build as first one fail with status 7 in recovery.(assert error)

Check my build and compare to yours to see what can be removed. I'm sure you will find a lot more that can be done.

when will a working link be available? very excited for this rom

talking_llama said:
when will a working link be available? very excited for this rom
Click to expand...
Click to collapse
i already uploaded a newer build,will update OP with working link.
@sandix ,thank you very much i definitely will do that!

worked for me, thank you!

sweet. finally a flashable rom for our metro variant. was debating on trying nightbreed's rom, as someone mentioned in that thread that they tried it and it worked. didn't want to kill the phone though as it is a daily driver. will report after using.

Ipoke Smot said:
sweet. finally a flashable rom for our metro variant. was debating on trying nightbreed's rom, as someone mentioned in that thread that they tried it and it worked. didn't want to kill the phone though as it is a daily driver. will report after using.
Click to expand...
Click to collapse
Let me know how it works out.also,if you have any suggestions feel free to throw them out here.

so i assume i have to install TWRP and flash this?

corrado85 said:
so i assume i have to install TWRP and flash this?
Click to expand...
Click to collapse
Yeah it's required

Just looking at channel log I'm assuming this is still relevant. I'm on V3 and with some frustration (I don't have Wi-Fi and had to trick my 6yr old laptop to boot up) I got it running well.
As someone who has hard bricked smart phones since the xv6800, this is a first good go. Inspires me to start cooking my own roms.
Suggestion: A file browser would have made it so much smoother. No one with half a brain will ***** about es file explorer or root browser being cooked in. Fortunately bad habits inspired me to always backup original stock. Most people would've been screwed there. Dirty flash. Pdanet. Got it all up and going.
Keep up the good work. Look forward to any tweakings you find out of my league
Sincerely,
Satisfied end user
Sent from my HTC Desire 626s using Tapatalk

trekie4ever said:
Just looking at channel log I'm assuming this is still relevant. I'm on V3 and with some frustration (I don't have Wi-Fi and had to trick my 6yr old laptop to boot up) I got it running well.
As someone who has hard bricked smart phones since the xv6800, this is a first good go. Inspires me to start cooking my own roms.
Suggestion: A file browser would have made it so much smoother. No one with half a brain will ***** about es file explorer or root browser being cooked in. Fortunately bad habits inspired me to always backup original stock. Most people would've been screwed there. Dirty flash. Pdanet. Got it all up and going.
Keep up the good work. Look forward to any tweakings you find out of my league
Sincerely,
Satisfied end user
Sent from my HTC Desire 626s using Tapatalk
Click to expand...
Click to collapse
Thank you for the input,much appreciated.also,i updated OP with a newer build that uses nova launcher as default and puts back a few apks that got cutout by mistake.

My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks

sgeto said:
My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks
Click to expand...
Click to collapse
This ROM is based off of the original Stock MetroPCS USA variant,i didnt add anything that would potentially affect your simlock status.ive only removed stuff that was already there.
If youre not in the US and youre not using MetroPCS Variant of the phone,you shouldnt be flashing this ROM to be 100% honest.flashing incompatable firmwares across devices can sometimes lead to bricks.whats your Carrier and device?

sgeto said:
My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks
Click to expand...
Click to collapse
https://www.mediafire.com/?451vq4nmp7paz2a

i2andog said:
https://www.mediafire.com/?451vq4nmp7paz2a
Click to expand...
Click to collapse
That APK will just crash,as the required lib files etc to accompany the APK are missing.

GotHeart said:
This ROM is based off of the original Stock MetroPCS USA variant,i didnt add anything that would potentially affect your simlock status.ive only removed stuff that was already there.
If youre not in the US and youre not using MetroPCS Variant of the phone,you shouldnt be flashing this ROM to be 100% honest.flashing incompatable firmwares across devices can sometimes lead to bricks.whats your Carrier and device?
Click to expand...
Click to collapse
I agree. It's very unusual.
I got this phone from a local phone shop. The owner seem to have unlocked the phone with some kind of service. I contacted my carrier who wrote down a couple of numbers from inside the phone (including the original phone number) and boom, I was able to use the phone with my number.
I have a theory about the error. Maybe you could see if that makes sense:
Maybe the phone isn't locked. But after a factory reset it keeps trying to "activate" the phone using the methods given by sprint.
There's this one step during the initial setup (right after factory resetting the phone) where it tries to register the phone, and fails. This step takes at least tem minutes and returns an error that locks up the phone.
I think the phone assumes that it's locked because it's not able to "reach" sprint servers and denies all incoming and outgoing calls/messages because of this.
If you know a way out of this please let me know.
Another user also provided me with an app that seems to be solving the issue. But it's not marshmallow compatible. Any ideas on that one as well?
Thanks a lot. And great debloating work you did there
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
GotHeart said:
That APK will just crash,as the required lib files etc to accompany the APK are missing.
Click to expand...
Click to collapse
Please tell me more about this app. Cam it solve my issue?
Thx

sgeto said:
I agree. It's very unusual.
I got this phone from a local phone shop. The owner seem to have unlocked the phone with some kind of service. I contacted my carrier who wrote down a couple of numbers from inside the phone (including the original phone number) and boom, I was able to use the phone with my number.
I have a theory about the error. Maybe you could see if that makes sense:
Maybe the phone isn't locked. But after a factory reset it keeps trying to "activate" the phone using the methods given by sprint.
There's this one step during the initial setup (right after factory resetting the phone) where it tries to register the phone, and fails. This step takes at least tem minutes and returns an error that locks up the phone.
I think the phone assumes that it's locked because it's not able to "reach" sprint servers and denies all incoming and outgoing calls/messages because of this.
If you know a way out of this please let me know.
Another user also provided me with an app that seems to be solving the issue. But it's not marshmallow compatible. Any ideas on that one as well?
Thanks a lot. And great debloating work you did there
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
Please tell me more about this app. Cam it solve my issue?
Thx
Click to expand...
Click to collapse
Again,what is your Carrier?if youre using anything other than MetroPCS USA,you should not use this ROM.thats #1.#2 is if youre using sprint,you should get the RUU to return the phone to factory software,and i assume youre using sprint because our Metro devices havent gotten MM yet,and you mentioned it.
And yes,CDMA/Sprint phones will not work correctly if theyre not provisioned from the carrier correctly.so if the activation is failing,then youre not going to be able to use the device to send messages etc until its activated correctly.
Suggestion,try using nightbreeds MM ROM thats for those kinds of carriers.

GotHeart said:
Again,what is your Carrier?if youre using anything other than MetroPCS USA,you should not use this ROM.thats #1.#2 is if youre using sprint,you should get the RUU to return the phone to factory software,and i assume youre using sprint because our Metro devices havent gotten MM yet,and you mentioned it.
And yes,CDMA/Sprint phones will not work correctly if theyre not provisioned from the carrier correctly.so if the activation is failing,then youre not going to be able to use the device to send messages etc until its activated correctly.
Suggestion,try using nightbreeds MM ROM thats for those kinds of carriers.
Click to expand...
Click to collapse
Oh lesson learned. I'm from Yemen and my carrier is YemenMobile (CDMA). I don't know why but I assumed that the phone won't mind the ROM since it was kinda unlocked. SORRY.
The phone was saying Sprint when I bought it. I think I'm going to get back to factory and see if that does the trick. :-/
My extended apologies