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
Related
I've been trying to fix this for the last week. I tried to boot the SWITCH ROM to use google edition and sense. I'm stuck in Bootloop.
I've looked through a lot of threads, with no luck.
Phone boots up
I only get a black screen with the notification bar. Can't do anything with that.
I can access bootloader.
Re-flashing a ROM hasn't worked.
Wiping data/cache/delvik hasn't helped
The all-in-tool doesn't work. I have to type in all the commands myself.
Has anyone fixed their One from a bootloop, or know how to get it back to stock 1.31?
Thanks in advance.
huebenthal said:
I've been trying to fix this for the last week. I tried to boot the SWITCH ROM to use google edition and sense. I'm stuck in Bootloop.
I've looked through a lot of threads, with no luck.
Phone boots up
I only get a black screen with the notification bar. Can't do anything with that.
I can access bootloader.
Re-flashing a ROM hasn't worked.
Wiping data/cache/delvik hasn't helped
The all-in-tool doesn't work. I have to type in all the commands myself.
Has anyone fixed their One from a bootloop, or know how to get it back to stock 1.31?
Thanks in advance.
Click to expand...
Click to collapse
First things first hopefully you read this reply better than you read the post about Switch Rom
About MoDaCo.SWITCH
MoDaCo.SWITCH is a unique ROM concept for the HTC One which allows you to have two ROMs on your device (Sense and Google Play Edition) but maintaining a single set of data that is shared between the two.
Switch has been in development for a while now and it is rather complex internally, so we will have a number of Beta phases where we are certain to find (and hopefully fix) any issues.
Pre-requisites
Switch is tested on a European WWE unlocked HTC One that was originally running the 2.24 ROM. S-OFF is recommended but not mandatory. S-OFF can be achieved using the revone utility.
NOTE: This ROM is for GSM devices only.
You need to RUU http://forum.xda-developers.com/showthread.php?p=44243635
Konfuzion said:
First things first hopefully you read this reply better than you read the post about Switch Rom
About MoDaCo.SWITCH
MoDaCo.SWITCH is a unique ROM concept for the HTC One which allows you to have two ROMs on your device (Sense and Google Play Edition) but maintaining a single set of data that is shared between the two.
Switch has been in development for a while now and it is rather complex internally, so we will have a number of Beta phases where we are certain to find (and hopefully fix) any issues.
Pre-requisites
Switch is tested on a European WWE unlocked HTC One that was originally running the 2.24 ROM. S-OFF is recommended but not mandatory. S-OFF can be achieved using the revone utility.
NOTE: This ROM is for GSM devices only.
You need to RUU http://forum.xda-developers.com/showthread.php?p=44243635
Click to expand...
Click to collapse
Thanks for the reply. I did not read through the SWITCH thread in great detail, which is of course on me. I will try this later when I have time. If it works, I'll spread the word to others.
huebenthal said:
Thanks for the reply. I did not read through the SWITCH thread in great detail, which is of course on me. I will try this later when I have time. If it works, I'll spread the word to others.
Click to expand...
Click to collapse
NP good luck let us know how it turns out for you.
PM me your teamviewer information
http://teamviewer.com/download
Indirect said:
PM me your teamviewer information
http://teamviewer.com/download
Click to expand...
Click to collapse
BOY, you guys thank your lucky stars you have INDIRECT here, i'd say
Aldo101t said:
BOY, you guys thank your lucky stars you have INDIRECT here, i'd say
Click to expand...
Click to collapse
yep indirect and bigdaddy deff the most helpful in the fourm!!
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Bob the Swede said:
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Click to expand...
Click to collapse
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Thank you!
alray said:
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Click to expand...
Click to collapse
Thank you so much! Now I get what is what I might need help finding the right place or thread showing me how to flash the ROM etc. I will look around too of course now that I know what the problem is.
I need help...
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
The link posted by @alray above comes with the download and instructions for flashing TWRP. And the second link takes you directly to the rom.
The only way it could be easier is if he comes to your house and flashes it all for you
Hahaha, I'm sorry, that's embarrassing.
Bob the Swede said:
Hahaha, I'm sorry, that's embarrassing.
Click to expand...
Click to collapse
just take your time and read a lot ..it's all pretty simple once you get a grasp on whats going on
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
you will first need to upgrade your firmware like said in the rom thread. Click on the link in that thread "Latest Radios and Firmware are REQUIRED and can be found here"
follow instruction to flash the latest firmware in that thread
then flash twrp 2.8.0.1 (also linked in the rom thread just above "Latest Radios and Firmware..." link.
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then push the rom to your phone (either using adb push/adb sideload/usb otg) and install it using twrp.
like cisa said above, if you follow the instructions in that thread andtake your time, everything will be good.
THANK YOU!!!
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Bob the Swede said:
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Click to expand...
Click to collapse
:highfive:
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!
I saw in another post that the kernel source got released, Im new to this, I was reading a post about how to create custom roms and all that, and i was wondering , we do need root access to get the system files and all that to begin working on a rom ?
What i wanted to do was basically a full stock lollipop rom, but with the Axon Software ( Camera, Dolby Digital, and a few other things ).
I dont have any background expirience creating roms, but whats leading me to this is , loving the phone but hating the toggles, and a few other software bugs ive encountered.
I have some programming knowledge, and I will make this my little side project if theres any chance for it to be done. If anyone has some background and wanna help/teach me, ill be thankfull.
This is the link I been following.
http://forum.xda-developers.com/showthread.php?t=1801690
I have no programming knowledge, but I'll gladly provide moral support and encouragement in this endeavor! A stock lollipop rom with ZTE features would be spectacular.
StaticMoot said:
I have no programming knowledge, but I'll gladly provide moral support and encouragement in this endeavor! A stock lollipop rom with ZTE features would be spectacular.
Click to expand...
Click to collapse
I know right ? Well, If by any chance it can be done, ill keep trying. I guess first we need root.
I would like to support this and I have some java and c++ programming experience. The only problem is that there hasn't been any word on root methods or bootloader unlock methods. Supposedly ZTE phones come bootloader unlocked already, but I haven't been able to prove this since we can't access the bootloader via fastboot :/ if we can at least get root that would be a good start.
Marshmallow on Axon Elite?
Hi all,
I came across this poat while checking for new ROMS. If this checks out I would happily go for the Elite as the price point and features are value for money. For those of you who do have it can you confirm that this is actually a Marshmallow ROM.
Moderator Edit : Links Removed
Thanks all
Danaim said:
Hi all,
I came across this poat while checking for new ROMS. If this checks out I would happily go for the Elite as the price point and features are value for money. For those of you who do have it can you confirm that this is actually a Marshmallow ROM.
Moderator Edit : Links Removed
Thanks all
Click to expand...
Click to collapse
What's up with all of the surveys?
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone.
---------- Post added at 07:27 AM ---------- Previous post was at 07:24 AM ----------
Sub-Negro said:
What's up with all of the surveys?
Click to expand...
Click to collapse
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone. Also would like to know the XDA source mentioned as am sure it won't have ads to download.
Danaim said:
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone.
---------- Post added at 07:27 AM ---------- Previous post was at 07:24 AM ----------
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone. Also would like to know the XDA source mentioned as am sure it won't have ads to download.
Click to expand...
Click to collapse
I am on the Lux model and it's full of Chinese software that I can't even read and I have no access to google apps.
Sub-Negro said:
I am on the Lux model and it's full of Chinese software that I can't even read and I have no access to google apps.
Click to expand...
Click to collapse
I was hoping to get the Elite and be able to flash it as the phone had a lot of potential!
You need to install Google Play Services and Google Services Framework. You will need to sideload these apk's. You will need to Google them.
Please, how can i upgrade my ZTE AXON Elite to Android 6.0? Is it posisible? Thanks
Marshmallow isn't available for this device yet.
When will a custom ROM appear for the Axon Pro?I hate all these chinese stuff and i would like to have the option to reset the phone and redo all the Gmail account,without the phone asking me for the last gmail account.I bought the phone from a friend and i did a reset later that day and it kept asking me for the old account.It sayd that the phone was reset and needs the old account and i couldn't go forward because it kept connecting to google and asked for the old account.I had to use my friends account again to use the phone.I want a simple rom,without this stupid connection to google and other chinese stuff.Any idea when a rom will be available?
No clue but now that you have your friends Google account you should be able to delete it and add your own.
I'm surprised that there isn't any custom roms for this phone yet,i mean its a phone with 4gb of ram,810 Snapdragon so its pretty powerful.
[/COLOR]
raduch said:
When will a custom ROM appear for the Axon Pro?I hate all these chinese stuff and i would like to have the option to reset the phone and redo all the Gmail account,without the phone asking me for the last gmail account.I bought the phone from a friend and i did a reset later that day and it kept asking me for the old account.It sayd that the phone was reset and needs the old account and i couldn't go forward because it kept connecting to google and asked for the old account.I had to use my friends account again to use the phone.I want a simple rom,without this stupid connection to google and other chinese stuff.Any idea when a rom will be available?
Click to expand...
Click to collapse
Why didn't you just do a factory reset? Also, Chinese stuff?
Jonathan.Parker2005 said:
[/COLOR]
Why didn't you just do a factory reset? Also, Chinese stuff?
Click to expand...
Click to collapse
I did a factory reset and it keeps saying that the phone was reset and i need to enter the gmail account that was previously entered.I also tried entering 15-20 time in a row ,because a lot of people say on forums that on note 4 and other phones if you enter the wrong account,the phone will reset and it will let you enter another account.On ZTE this doesn't work .
Jonathan.Parker2005 said:
[/COLOR]
Why didn't you just do a factory reset? Also, Chinese stuff?
Click to expand...
Click to collapse
He probably has a Chinese model. I have the Lux so I know exactly what he is talking about.
Sub-Negro said:
He probably has a Chinese model. I have the Lux so I know exactly what he is talking about.[/QUOTEA friend of mine is a ballet dancer and he bought it when he was on tour in Shanghai,so i think it's the chinese model.
Click to expand...
Click to collapse
Nothing new for the AXON PRO?
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
sturmeh said:
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
Click to expand...
Click to collapse
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
mattzeller said:
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
Click to expand...
Click to collapse
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
sturmeh said:
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
Click to expand...
Click to collapse
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
eatsleep said:
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
Click to expand...
Click to collapse
Buy it directly from Google and the bootloader won't be locked, only if you buy it through a carrier like Verizon will the bootloader be locked
Sent from my SCH-R220
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
fkofilee said:
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
Click to expand...
Click to collapse
The worst possible thing you could write...
ldeveraux said:
The worst possible thing you could write...
Click to expand...
Click to collapse
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
fkofilee said:
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
Click to expand...
Click to collapse
If your intent was truly altruistic, you wouldn't feel the "burden" of stating it publicly. So no, it doesn't matter.
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Confirmation number: 57C48888US937054E
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Appreciate all you do Chainfire, seriously. Can't wait for you to work your magic
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
hutzdani said:
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Click to expand...
Click to collapse
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Ker~Man said:
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
Click to expand...
Click to collapse
Totally agree. Thanks for speaking up!
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Sent from my Pixel XL using Tapatalk
tveith said:
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Totally agree. Thanks for speaking up!
Click to expand...
Click to collapse
What ever but tour the same guys who's going to be asking for OTAs and asking devs to do this that and the other as fast as humanly possible.
If you want it that bad do it your self or sit and wait like a good little child.
No dev is going to rush something because of some people in a forum get a grip, like I said it's their time and it will be ready when it's ready.
You might think I'm going off on one but read the rules page for Christ's sakes.
sionicion said:
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Click to expand...
Click to collapse
The chance you'll have to erase is always present when rooting. Even when your device is fully prepared something may go wrong. At least you have already unlocked your bootloader, which reduces that chance.
File-based encryption will probably not be a reason to for wiping, though. It works fine in the dev version of SuperSU with Android 7.0 on a 5X.
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
mrnovanova said:
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks interesting, but without twrp you sure are taking a big chance if something goes wrong.
Sent from my Pixel using Tapatalk