This is a sort of continuation of the work in this thread: http://forum.xda-developers.com/showthread.php?t=1798750
I only started this because I could not get the files located in that thread to work on Epinters CM10 build. With help from quetzalcoatl2435, we have a successful .zip with the modified files to work in this ROM.
The "Atrix-softbutton...cm10.zip" will activate the vitural soft keys and turn off the lights for the capacitive keys. With this file the capacitive keys still work.
"DisableAllCapacitiveKeys.zip" does just that, disables the capacitive keys all together.
"AtrixSoftKeys...zip" combines the two together into one file so the virtual soft keys are enabled and the capacitive keys are disabled completely.
The last file will return you to stock without soft keys and working capacitive keys!
Flash at your own risk, I have only tested this on Epinters ROM (personally), it may work for others.
Copy the file to your sdcard, Nandroid, flash, and enjoy your new mod!
Tested and working on Epinters 8/22 build.
Happy flashing!
try changing the false to true in this line of bools:
<bool name="config_forceDisableHardwareKeyboard">false</bool>
i did my own .zip with the tutorial posted on the thread you linked when leo stopped updating it
but my atrix's hardbuttons are dead, so i don't have how to test if worked or not
PS: i know, my english sucks
lstat said:
First I would like to say that I know this has been posted in the Dev. Section but I have reasoning for posting it again, secondly I have my fingers crossed this section will work, I see the buttons as a Dev. mod AND themeing. Mods, feel free to move if I am in the wrong! :good:
I am currently running Epinters CM10 build and love it, I really wanted the virtual soft keys, though. Losing a small amount of screen space wasn't to big a deal, its not really THAT much real-estate. I pulled the idea for doing this from this thread: http://forum.xda-developers.com/showthread.php?t=1798750 . All credit goes to the OP and any others mentioned before, I only created this for myself.
I was ecstatic when I found that thread, but every file the OP posted sent my phone into a boot loop and I was determined to make it work. Through a ton of searching I finally figured out what to do and what files needed to be edited. I have successfully gotten the virtual soft keys on CM10 and they work great! I know that I am not the only person who has had issues with adding these so I thought I would post it here for others relief!
Unfortunately this .zip file only turns on the soft keys and shuts off the capacitive lights for the hardware buttons, the capacitive buttons still work but I am going to look into that once I find the correct files that need to be edited. I have only tested this on Epinters CM10 build from 8/15. I cannot promise it will work on any other ROM although I would assume JB ROMS should be alright with this.
Remember to make a Nandroid, if this doesnt work for you, you need to have a backup so you arent reflashing your entire phone!
Simply add this to your SD card, flash, and reboot!
If this messes your device up in anyway I take no responsibility, but feel free to let me know what files I need to edit for the capacitive buttons functions!
Otherwise, cheers!
Click to expand...
Click to collapse
Errrm... I made a keymap that killed all 4 capacitive keys. It's on the first post of the thread you referred to...
Edit - Here's the link: https://dl.dropbox.com/u/19567156/DisableAllCapacitiveKeys.zip. It's flashable.
I will check that out, thanks for the heads up.
Currently I am trying to create an update.zip that contains the /usr/keylayout files that need replaced. I have all the needed files but the file always 1) aborts installation, 2) fails with (status 0)
At the moment I am trying to figure this out but I am going to checkout that line.
quetzalcoatl2435 said:
Errrm... I made a keymap that killed all 4 capacitive keys. It's on the first post of the thread you referred to...
Click to expand...
Click to collapse
I tried flashing it and it sent my Atrix into a boot loop, also. If it didnt then I wouldnt be trying to build one on my own....
lstat said:
I tried flashing it and it sent my Atrix into a boot loop, also. If it didnt then I wouldnt be trying to build one on my own....
Click to expand...
Click to collapse
K. Lemme check it. Last time I used it, it worked fine. It shouldn't do a bootloop since it only changes the keymap files, not the framework.
Thanks, I just tried again and got a boot loop once more. As I said, the modded framework I edited works fine on epinters CM10 and the one from that thread did not; I figure I will try the keymap files, also. I know I am not the only one that has had these problems which is why I started this in the first place.
Any help I can get is greatly appreciated.
update: Just did a fresh backup and flashed your linked file one more time; it actually worked this time. I finally have the cap. keys disabled with soft keys enabled. Thanks for the help! Hopefully a few more people can benefit from this now!
Yep, I just tested my keymaps with your framework. Works fine.
Edit: I made a unified framework + keymap flashable zip in case anyone's interested.
And one to restore things back to stock.
Using this. It''s working great!
quetzalcoatl2435 said:
Yep, I just tested my keymaps with your framework. Works fine.
Edit: I made a unified framework + keymap flashable zip in case anyone's interested.
And one to restore things back to stock.
Click to expand...
Click to collapse
Files attached to OP.
Is there any advantage to having soft keys over capacitive keys? Or is it purely cosmetic?
nh777 said:
Is there any advantage to having soft keys over capacitive keys? Or is it purely cosmetic?
Click to expand...
Click to collapse
Soft keys are cool. Nah, it's mostly cosmetic, but it gives you a Nexus "feel". Plus you get to see the actionbar in action (see what I did there?) with this mod.
BTW, I haven't seen this thread updated for the latest (22/8) version yet, so I updated these myself.
Soft keys + disabled cap keys.
Restore stuff back to normal.
I hope lstat doesn't mind. I don't intend to hijack his thread, though, so I will remove these links if he asks me to.
Remember, these are only tested on epinter's 22/8 version. Use at your own risk.
quetzalcoatl2435 said:
Soft keys are cool. Nah, it's mostly cosmetic, but it gives you a Nexus "feel". Plus you get to see the actionbar in action (see what I did there?) with this mod.
BTW, I haven't seen this thread updated for the latest (22/8) version yet, so I updated these myself.
Soft keys + disabled cap keys.
Restore stuff back to normal.
I hope lstat doesn't mind. I don't intend to hijack his thread, though, so I will remove these links if he asks me to.
Remember, these are only tested on epinter's 22/8 version. Use at your own risk.
Click to expand...
Click to collapse
Im not worried about hijacking, go ahead and keep it coming! I will link back to the OP once more!
update: Files are up on OP.
lstat said:
Im not worried about hijacking, go ahead and keep it coming! I will link back to the OP once more!
update: Files are up on OP.
Click to expand...
Click to collapse
Do the 8/22 files work for 8/23 build?
rmkilc said:
Do the 8/22 files work for 8/23 build?
Click to expand...
Click to collapse
I'm still downloading the 23/8 version, so I can't really tell yet, but you can check if there are changes in the framework-res yourself by comparing the file from the 22/8 version with the 23/8 version. If the contents are the same, then it's safe to assume they will work without problems. If they are different, then it *might* work, but it's not recommended.
Well now there is 8/23B.
Been busy with other stuff today, didnt realize there was another update! Downloading now to test, I will report back shortly.
rmkilc said:
Well now there is 8/23B.
Click to expand...
Click to collapse
That's what I'm currently downloading. Dev-host is slow as molasses...
Edit: Download finally finished. There are framework changes, don't flash the 22/8 mod on 23b/8.
7 tries later, I finally got it. :banghead:
Sent from my Xoom using Tapatalk 2
Still waiting for the download to finish, grr.
rmkilc said:
7 tries later, I finally got it. :banghead:
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
got it as in installed the current files over the new 8/23b?
Related
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
mattbollenbach said:
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Click to expand...
Click to collapse
thank for link
mattbollenbach said:
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Click to expand...
Click to collapse
That doesn't work for everyone, so a more permanent solution will have to be devised.
craig.cabrey said:
That doesn't work for everyone, so a more permanent solution will have to be devised.
Click to expand...
Click to collapse
i've done this mod that exact same way on my aria with 4 different roms with no issues at all every time.
you really just need to save the qwerty.kl file and push it to the phone. reboot into recovery, go to the partitions menu, mount the system partition, push the file via adb, reboot your phone and voila.
jaex said:
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
Click to expand...
Click to collapse
SEARCH...!
Please take a moment to review the forum rules with regards to searching existing threads prior to creating a new one, and also regarding the proper sections to post in. Moving to General as this is not a Development thread.
you really just need to save the qwerty.kl file and push it to the phone. reboot into recovery, go to the partitions menu, mount the system partition, push the file via adb, reboot your phone and voila.
Click to expand...
Click to collapse
oh my gosh that seems painfully complicated considering the simplicity of the issue. that's kinda funny really
mattbollenbach said:
i've done this mod that exact same way on my aria with 4 different roms with no issues at all every time.
you really just need to save the qwerty.kl file and push it to the phone. reboot into recovery, go to the partitions menu, mount the system partition, push the file via adb, reboot your phone and voila.
Click to expand...
Click to collapse
I've done that. The qwerty.kl method just simply isn't working for some people.
This worked for me
Couldn't figure out how to add attachments to this post, and it won't let me add an external link since it's a new forum account. google ojwake-signed.zip or something.
Steps: Load file to SD card, boot in to recovery mode, install zip, locate this zip on flash card, reboot.
(ojwake-signed.zip)
Don't remember where i got this, but kudos to that guy!
Neverwhere10
HTC Aria Liberated B005.
gdeadfan said:
oh my gosh that seems painfully complicated considering the simplicity of the issue. that's kinda funny really
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Just to make it even easier on you
EDIT-Short Version...Download file from link above
-:Have Clockwork Recovery Installed and know how to use ADB:-
-DOWNLOAD ATTACHED to linked post qwerty.kl (may need 7zip to extract file from archive...)
-BOOT into CLOCKWORK recovery with NO USB PLUGGED INto phone!!!
-PARTITIONS>MOUNT /SYSTEM
-adb push qwerty.kl /system/usr/keylayout|adb reboot
As far as I know, this ridiculously simply method of pushing qwerty.kl has worked for everyone except the few that didn't boot into clockwork correctly, once they booted into clockwork correctly it then worked for them.
I updated the instructions to be crystal clear for all you noobs. If pushing a file to your android device is too painfully complicated for you, I suggest you read/search more and figure out what you are actually doing.
Neverwhere10's steps are just as painfully complicated, but at least he is providing some constructive input.
Thanks!
Worthless thread is worthless.
jaex said:
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
Click to expand...
Click to collapse
Thanks for asking this question when you did...
mattbollenbach said:
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Click to expand...
Click to collapse
Thank you so much for the link... this is great.. love it... like jeezy
This mod is built into the CM6 rom.
Sent from my Liberty using XDA App
There is also a setting in one of the menus if you are using any of attn1's cm roms for this same thing. I currently have my aria set this way and I am using cm008 as of right now.
Sent from my Liberty using XDA App
If you have not already seen it, or if an application is an acceptable solution, widgetlocker is a nifty program.
jaex said:
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
Click to expand...
Click to collapse
Sent from my HTC Liberty using XDA App
This is an interesting question, maybe we should take a test to see, and I want to ask and optical sensor is the same?
I have TnT-Lite installed and love the rom, but I cannot use my hardware keys. I am hoping that someone can enlighten me on where I might find the file/s to modify. I do have a backup of the Stock ROM.
fKngFtd said:
INFORMATION
Click to expand...
Click to collapse
Reserved space!
May be a long shot but search the apps and themes string for the screen calibration app one of devs put together from other sources. A lot of button and screen dead space has been solved by using it.
Its a place to start anyway. Good luck.
Sent from my Chromatic Magic using XDA Premium App
I could not help you but I would appreciate if you could give me some help.
The thing is, I have bricked my luvpad even before I completed backing it up (yeah, I know that it is stupid)
You have mentioned that you have a full backup of the stock ROM.
Would you kindly share those images with me (and us) so that I can nvflash it and revive my luvpad?
I know that it is a lot to ask (lots of big files to be uploaded) but I look forward to your help... you are the only hope... m(_ _)m
Thank you in advance
Nevermind. I managed to get it running again.
Sent from my harmony using Tapatalk
neocpe said:
Nevermind. I managed to get it running again.
Sent from my harmony using Tapatalk
Click to expand...
Click to collapse
can you shed some light on how you got your luvpad up and running again? I'm stuck without any hardware buttons so I can get into clockwork recovery but I can't select anything because my Home, Back and Menu buttons don't work.
NVFLASH
ucsblaw said:
can you shed some light on how you got your luvpad up and running again? I'm stuck without any hardware buttons so I can get into clockwork recovery but I can't select anything because my Home, Back and Menu buttons don't work.
Click to expand...
Click to collapse
You can use a program called "NVFLASH" attached is a 7z file. You might have to do some reading on how to use nvflash. I haven't used it in months. I believe it has the stock recovery and the working clockworkmod with buttons and all.
I am looking for a "ZIP" to flash Google apps with Market. Does anyone know of one or have the zip? I like the TNT rom, but I dislike how I cannot use the hardware buttons, unless someone has a fix. The luvpad isn't owned by me, it is my co-workers but I am all about the Android community and having the best experience with all android devices. Thank you and I hope I have helped you.
"Thank You" button works.
Here's a link, have Google translate it.
http://sumapho.wordpress.com/2010/12/18/luvpadnvflashでrom焼き/
Sprint Moto X [XT1056] Stock ROMS
By using any of these you agree that I am not responsible for ANYTHING that can or may happen to your phone
Click to expand...
Click to collapse
Like this guy said:
iKrYpToNiTe said:
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please!
Click to expand...
Click to collapse
-----------------------------------------------------------------
KIT KAT 4.4.4
System Version: 212.44.28
Software update 08/2014
Code:
[B]DETAILED ENHANCEMENTS:[/B]
Android™ 4.4.4, KitKat® - Android 4.4.4, KitKat, is the latest release of the Android platform. This release includes several stability, framework and security fixes in addition to accuracy improvements to the power profile.
Camera - Improved image quality - Improved camera image quality including better consistency of exposure, more realistic flash coloring, improved photos in low light conditions using front camera.
Camera - Pause video recording - Added the ability to pause video recording with a convenient pause/resume button on the viewfinder.
Updated Phone dialer - Updated Phone dialer with a new graphical layout and colors to improve consistency and usability.
Motorola Alert application - New Motorola Alert application sends periodic alerts with your location to your selected contacts. Now available for download from the Google Play Store.
ROM LINK
212.44.28
md5: d1fb4c2259855abf74dfadbad5ccdbc2
FIRMWARE LINK
LINK
-----------------------------------------------------------------
BIG thanks to:
iKrYpToNiTe
chad.goodman
NineInchNails
Rizal Lovins
ibanez7
motofirmware.center
JustCMH
HOT-SPOT UNLOCK:
iKrYpToNiTe said:
All you have to do is add net.tethering.noprovisioning=true to your build.prop file and then you can remove or freeze the entitlement check app if you want to. Sprint model requires ro.mot.tether_dun_required to change from 1 to 0.
For people who don't want to mess with modifying their build.prop file or use xposed. I made an app which requires Root, that will run a setprop command to bypass the check until you reboot. If you want it to last after a reboot you can select apply of boot to run the command after every reboot. This was tested and confirmed by cvhovey thanks to him for testing it for me, since I have free tethering. This is my first app so I hope you Enjoy it! I want to say thanks to jcase's slapmymoto and the developer of adaway, I used their github sources as references when I couldn't get something working. Also androidicons for the icon template, and Poliva for setpropex, and jduck for getting setpropex working on KitKat.
Download Links
v1.2 http://www.androidfilehost.com/?fid=23501681358557764(v1.2 is signed with a different key than v1.0/v1.1 so it will display a msg box telling you this just click okay)
Click to expand...
Click to collapse
RECOVERY LINKS
CWM Advanced Edition- PhilZ Touch
TWRP
SUPERUSER LINKS
SuperSU
CWM Superuser (Koush)
DID YOU MAKE AN EXPENSIVE BRICK?
[HOW-TO] Resurrecting A Bricked Moto X
FEW WAYS TO GET BACK TO STOCK
Easy Guide to Restore Stock Firmware on Moto X using RSD Lite
Moto X Toolkit v1.4.3 [Backup/Restore,Drivers,Return to stock,Root,Bootani]
Script FlashFirmware (simple and safe method to flash firmware)
Getting a moto x back to stock on mac os x
BAD BATTERY DRAIN LATELY? TRY THIS
hardware reset of the processor and terminates all running commands
LEAVING THIS HERE IN CASE I FORGET HOW TO TAKE A DUMP
Code:
[B]dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/System.img.ext4
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/Boot.img[/B]
Thanks for this! Thanks soo much for the hard work!
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
They are both up. md5's should be posted right, they were manually entered. I'm carving pumpkins with the boys, so........hopefully all is good. If not, let me know and I'll attack it when able to.
AbstractXart said:
FINALLY! The first rom for the Sprint variant :').... I Love you! haha.
Click to expand...
Click to collapse
pfft, and mine was what?
looks good gokart
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
gokart2 said:
Just trying to get things going...lol. Didn't see anything for Sprint ver, must have missed yours? BTW....I seen a shabby looking penguin on a program to turn system.img into system files in the kithcen......is that you?
Click to expand...
Click to collapse
nah, the last big script i did for people was teh first nexus toolkit, nowadays i hop around trying to help out unloved devices (hence teh name of the team i made Official Unloved Devices Hit Squad ). people needed this anyways, my stock rom was based on the pre-ota camera fix apparently. i had considered getting this phone on republic wireless so i wanted to scope out how development was coming, saw nothing was going on and figured id help out .
shabbypenguin said:
pfft, and mine was what?
looks good gokart
Click to expand...
Click to collapse
Wha?! I never saw it Shabby. My bad, let me rephrase,
FINALLY! The second rom for the Sprint variant :').... I Love you! haha.
Hey guys, I just wanted to update and say it won't boot on the Verizon dev edition like the T-mobile rom will. It freezes for me on the Moto Earth boot animation. Noo! Well darn, I was wanting to try the sprint rom to see if I could get google wallet tap to pay working on my vzw dev phone since no one has figured out how to make tap to pay work on the non-sprint variants.
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
gokart2 said:
YES!!!! It worked!!! LOL. Anyway, have you/anyone noticed anything when trying to alter the stock boot.img? Seems like anything I tried (not a whole bunch really) with the kernel/boot.img made it non-bootable? Pretty much if it hits the bootloader unlocked screen and doesn't vibrate.....its a no go? Wondering if theres some type of checksum for the boot.img? Not too sure about wallet ATM. Don't really use it, and this is based off the OTA so....I'd assume it should be fine? I remember some stuff way back on this, may have to step back and see if there's something to utilize. This isn't my first rodeo.....but it's the first one I've entered.:laugh:
Click to expand...
Click to collapse
what command are you using to pack the boot.img?
skiwong20 said:
I booted the deodex version just fine on my vzw Dev edition. I wiped my data and wiped cached before flashing. I didn't try g wallet
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
shabbypenguin said:
what command are you using to pack the boot.img?
Click to expand...
Click to collapse
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
jimmypop13 said:
Yeah I wipe three times before flashing and I wiped cache and dalvik again before booting. I wonder what the issue is. I downloaded the odex and not deodex but I don't see it being the difference between booting and freezing. Hmm. I'm back on the T-Mobile rom now. I'll have to try again with the deodex tomorrow
Click to expand...
Click to collapse
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
Click to expand...
Click to collapse
i take it then you arent packing the Device tree file to the boot.img.
http://pastebin.com/tSGxTmYq save this script, run it against stock boot.img. youll get a DTB.img, extract your boot.img, edit what you want in ramdisk or swap zimages. then use a modified mkbootimg to include the dtb file as part of it all
gokart2 said:
Was just using the kitchen tool. Anytime I touched the boot.img it wouldn't boot up..... Or it would not vibrate at the splash screen, boot up, but not "see" user touches on the screen. Acted like the digitizer was totally off. Something I noticed is if it vibrates at the splash, it was good. No vibrate, definitely something would be wrong. Going to take my time with it next week.
I recommend wiping system and data too and trying. Just make a backup first. And/or try using your normal boot.img instead of the one in the zip.
Click to expand...
Click to collapse
I got the sprint deodex rom booting on my vzw dev edition doing like you said. But sadly I found google wallet would not work. It just sat saying "finishing up a few things." So I guess unfortunately there is a hardware issue preventing wallet from working on the non-sprint variants. That sucks!!!
I don't understand why but I noticed between the t-mobile, verizon, and sprint roms that the signal bars are slightly different on every one. Sprint's seems to be stretched out a little more and have an extra bar or two. I hate all of them though because the grey has some funky white lines through it where the separations are instead of being solid grey. I don't know what was wrong with the stock android signal bars that none of the carriers wanted them
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
d4mi3n said:
I have a question regarding safestrap, can I use it to unlock my bootloader and just flash this to my nand? I dont want to waste my space on rom slots :\
Click to expand...
Click to collapse
Honestly have no clue about SS. I would have to say no. No sure what needs to be done for it to be SS flashable.
Added 4.4 links. Thank abiezer for letting me link to his deodex 4.4 build HERE!
I plan on adding the SPRINT specific firmwares, and more in due time.
First off I would like to please ask everyone to thank the anonymous donor for this file because we wouldn't be seeing it today without them.
For all those that have been waiting, it's not the official release - but it is stable enough for daily driver use.
I haven't had much time to test this but the only issue I had with it was flashing it.
If it gets stuck trying to get to recovery pull the battery and flash again.
I am marking this a full restore because it looks like it wiped data, including pictures. YMMV.
At the moment I'm only putting the original file up.
I'll try to get an Odin one-click and a nodata version up later.
Link to NI3 folder:
http://www.rwilco12.com/downloads.p... Galaxy S5 (Sprint) (SM-G900P)/Stock ROMs/NI3
Steps:
1) Download EXE file, double-click to extract.
2) Put the phone in download mode.
If you've never done this before, easiest way is to shut the phone down completely.
Then hold Vol Down + Power until you see a warning screen. Press up to proceed.
3) Open Odin (I used 3.07), place in PDA slot and flash.
4) Profit!
Please feel free to leave feedback on the flash and ROM but please keep in mind I have no special contact to relay that feedback.
Do me a favor please - if you're going to reply don't clutter my thread with spam. Thank you.
Reminds me of that old Monty Python skit. LOL
Spam spam spam.
Changelog at someone's first opportunity please.
Screenshots too if there's anything worthwhile to show off.
tdunham said:
Reminds me of that old Monty Python skit. LOL
Spam spam spam.
Changelog at someone's first opportunity please.
Screenshots too if there's anything worthwhile to show off.
Click to expand...
Click to collapse
Only CL details I have:
anonymous source said:
...couple of Sprint bug fixes, SSL Google fix, and hd voice indicator (finally!)
Click to expand...
Click to collapse
And of course, the new version.
Boot screen logo (android) looks new typefont to me.
Will try rooting this shortly.
Very nice thanks a bunch
woot something new to play aorund with, TY once again gents. lol
Any noticeable changes as far as looks? Or just code and software related?
88EVGAFTW said:
Any noticeable changes as far as looks? Or just code and software related?
Click to expand...
Click to collapse
There is a problem with the screen not turning off when making a call. Other than that it seems smooth so far. Wifi calling is only new feature that i have tested, and it seems to work fine.
You cant root with towelroot you have to use cf-autoroot which trips knox. Since i had tripped it already WTF not. http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Screen shots please?
Sergekarol said:
There is a problem with the screen not turning off when making a call. Other than that it seems smooth so far. Wifi calling is only new feature that i have tested, and it seems to work fine.
You cant root with towelroot you have to use cf-autoroot which trips knox. Since i had tripped it already WTF not. http://forum.xda-developers.com/showpost.php?p=51421067&postcount=2
Click to expand...
Click to collapse
I have that screen on while on a call problem with my not yet rooted S5 on NE5 from time to time. That one may not be new. I wonder if its possibly a hardware issue?
garwynn said:
First off I would like to please ask everyone to thank the anonymous donor for this file because we wouldn't be seeing it today without them.
For all those that have been waiting, it's not the official release - but it is stable enough for daily driver use.
I haven't had much time to test this but the only issue I had with it was flashing it.
If it gets stuck trying to get to recovery pull the battery and flash again.
I am marking this a full restore because it looks like it wiped data, including pictures. YMMV.
At the moment I'm only putting the original file up.
I'll try to get an Odin one-click and a nodata version up later.
Link to NI3 folder:
http://www.rwilco12.com/downloads.p... Galaxy S5 (Sprint) (SM-G900P)/Stock ROMs/NI3
Steps:
1) Download EXE file, double-click to extract.
2) Put the phone in download mode.
If you've never done this before, easiest way is to shut the phone down completely.
Then hold Vol Down + Power until you see a warning screen. Press up to proceed.
3) Open Odin (I used 3.07), place in PDA slot and flash.
4) Profit!
Please feel free to leave feedback on the flash and ROM but please keep in mind I have no special contact to relay that feedback.
Click to expand...
Click to collapse
Hiya, ty again! ! Question. The other files on "wilco"- can that be flashed w/o computer my friend?
Any chance this build includes improved Android Wear support?
garwynn said:
Do me a favor please - if you're going to reply don't clutter my thread with spam. Thank you.
Click to expand...
Click to collapse
Hiya. Sry to bother ya. But the. Tar file on wilco, can I use that w/o a computer?
Jrowe820 said:
Hiya. Sry to bother ya. But the. Tar file on wilco, can I use that w/o a computer?
Click to expand...
Click to collapse
I would also like to know this, I just downloaded it but dont want to attempt to try it and not have a phone until I can get back to my place later
Finally getting around to deodexing and rooting this build.
Wish me luck.
If anyone has it ready to go and is just going through testing, let me know so I don't spend hours getting it ready.
Has anyone tried to go back to ne5 after update?
tdunham said:
Finally getting around to deodexing and rooting this build.
Wish me luck.
If anyone has it ready to go and is just going through testing, let me know so I don't spend hours getting it ready.
Click to expand...
Click to collapse
I started it yesterday but work got in my way, how far along are u
vinman12 said:
I started it yesterday but work got in my way, how far along are u
Click to expand...
Click to collapse
I now have a bootable odexed version. I probably wont do deodexed right away, its not worth the extra effort. Going to try getting one done that is rooted with busybox to post later.
Edit: And it seems to be fine with the NE5 modem too so no worries there.
I'm on my way home I may deodex it. Will post back if I do.
Oh great, I was just getting my rom ready to release an update, lol. Thanks for working on this guys.
after a long wait for the firmware to be released of the S4 running OH7 , it still has not been released. However i decided to make it myself and now we finally have it. I have tested it on my S4 that came with OH7 build originally. So here you go guys, Firmware containing OH7 running lollipop 5.0.1 with stock kernel 3.4 of mon Sep. 7 2015.
little guide to help you install the firmware if you need it.
you will find the firmware link below that i have uploaded and as for odin you can just google it. now im sure you can use other versions of odin but always safest to be up-to-date.
you will need: OH7 firmware file (Download link at the bottom), odin 3.10.7, WinRar and USB data cable
steps:
1. put phone into download mode by holding the home+vol up+power keys at the same time.
2. plug your phone into your PC (be sure drivers for the phone are installed correctly)
3. open up your handy tool of Odin
4. open up the firmware file you have downloaded in Winrar and extract it, you will then be given an MD5 File containing the firmware
5. click on "AP" in odin and browse for the file (odin might not respond after that but be patient, it will)
6. after the program responds, double check that F. Reset time and Auto Reboot are the ONLY ones ticked/checked
7.Go ahead and hit start and sit back for a few minutes and let odin do its thing
8. after all goes well and in the top box says "PASS!" then your phone will reboot and be good as new.
Just a heads up that this firmware is meant and made for the prepaid variant of the Verizon S4. I wouldnt recommend trying it on the postpaid S4 for the postpaid firmware has negative effects on the prepaid variant so id assume it have the same outcome on postpaid variant. Also im not responsible like anyone else out there if you brick your phone by not following the steps correctly or flashing it incorrectly in some way. Just a disclaimer that everyone puts out on here. hope this helps everyone. enjoy!
If the link becomes a broken link, let me know and i will update. i just need to move the file from time to time due to high data traffic
Link Update
https://mega.nz/#!Uk412ZwR!IT_c5Lq6hxbs_CbDVJZKIEv9pAMony8vdUgvvVq0zuE
now that i have released the stock firmware of OH7, i am trying to Deodex this also but keep getting failed start ups. i used LBD 2.5 to try an deodex and followed the guide but i hear start up sound not even a second and it stops and it dont show the verizon logo. i used flashfire to flash the deodexed files. so that being said, could some actual dev, deodex this firmware for i cannot? id really appreciate it and id share the deodexed firmware on the thread as well with of course giving proper credit to whomever can deodex it. thanks!
bjf189 said:
now that i have released the stock firmware of OH7, i am trying to Deodex this also but keep getting failed start ups. i used LBD 2.5 to try an deodex and followed the guide but i hear start up sound not even a second and it stops and it dont show the verizon logo. i used flashfire to flash the deodexed files. so that being said, could some actual dev, deodex this firmware for i cannot? id really appreciate it and id share the deodexed firmware on the thread as well with of course giving proper credit to whomever can deodex it. thanks!
Click to expand...
Click to collapse
This needs to be maken into a rom first as well before deodexed but i can do both actually if you don't know how to build a rom.
Sent from my SM-G935V using Tapatalk
Well if you could do both, I'd really appreciate it. I can't even begin to understand how to extract an md5. So confusing. Plus gotta get it to work with flash fire. I tried other roms with flashfire and kept getting system not responding. So I always had to Odin back to stock and on the custom rom I never get even a boot animation. So I'm not sure what's up with it
stang5litre said:
This needs to be maken into a rom first as well before deodexed but i can do both actually if you don't know how to build a rom.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
What you think?
bjf189 said:
Well if you could do both, I'd really appreciate it. I can't even begin to understand how to extract an md5. So confusing. Plus gotta get it to work with flash fire. I tried other roms with flashfire and kept getting system not responding. So I always had to Odin back to stock and on the custom rom I never get even a boot animation. So I'm not sure what's up with it
Click to expand...
Click to collapse
Flash fire is horrible. Use v24 seems to be the best atm. I can do both. In the middle of mod'ing the s5 rom I made. But after I build it I would have you test it 1st before deodexing as you want to make sure it boots 1st before moving on.
Sent from my SM-G935V using Tapatalk
stang5litre said:
Flash fire is horrible. Use v24 seems to be the best atm. I can do both. In the middle of mod'ing the s5 rom I made. But after I build it I would have you test it 1st before deodexing as you want to make sure it boots 1st before moving on.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I think I tried your rom before. Your username was on a rom that I tried. It was non mdk which was said to use. I used flashfire beings I can't have safestrap on lollipop. It's all I could use to flash things thanks to a locked bootloader. But I'll try your suggestion and I can surely test what you put out for the s4. Just need an idea of what to use to flash things. And you talking version 24 of flashfire? Cause I already use that an got those outcomes. Also if it makes it any easier on you, could you just rebuild your ultranote5 rom for the prepaid variant? Whichever is easier for you. I loved the feature list that you had for it though I couldn't get it to get past the boot screen cause it would like freeze at the animation but at the same time there wasn't even an animation. Just a quick Samsung sound that doesn't even finish. Wish I knew more about rom development but it can get get complex I think.
bjf189 said:
now that i have released the stock firmware of OH7, i am trying to Deodex this also but keep getting failed start ups. i used LBD 2.5 to try an deodex and followed the guide but i hear start up sound not even a second and it stops and it dont show the verizon logo. i used flashfire to flash the deodexed files. so that being said, could some actual dev, deodex this firmware for i cannot? id really appreciate it and id share the deodexed firmware on the thread as well with of course giving proper credit to whomever can deodex it. thanks!
Click to expand...
Click to collapse
Not sure if it's still an issue or not, but I had similar problems before. Flashfire didn't seem to be finishing backups or flashes. I think I was using v18 or 19. Setting the screen timeout to 10 minutes fixed it, no problems after that and I just set it back when I'm done.
F1a5hP01ntX said:
Not sure if it's still an issue or not, but I had similar problems before. Flashfire didn't seem to be finishing backups or flashes. I think I was using v18 or 19. Setting the screen timeout to 10 minutes fixed it, no problems after that and I just set it back when I'm done.
Click to expand...
Click to collapse
My screen never shut off when I used flashfire. So I'm not sure. Could be something in flashfire being it was made for the s4. Not the prepaid variant. So maybe some code in it is different in the postpaid. Who knows
bjf189 said:
My screen never shut off when I used flashfire. So I'm not sure. Could be something in flashfire being it was made for the s4. Not the prepaid variant. So maybe some code in it is different in the postpaid. Who knows
Click to expand...
Click to collapse
Ah, not sure about that. I'm pretty sure my screen would shut off and then reboot shortly afterward as if it finished properly. I also just remembered that flashfire used to rearrange the order that the operations were added and would move the wipe toward the bottom of the list, usually after the flash. I would double check that the order is correct before starting if you haven't already. Those two were the only problems I had. Hope those tips help in some way.
F1a5hP01ntX said:
Ah, not sure about that. I'm pretty sure my screen would shut off and then reboot shortly afterward as if it finished properly. I also just remembered that flashfire used to rearrange the order that the operations were added and would move the wipe toward the bottom of the list, usually after the flash. I would double check that the order is correct before starting if you haven't already. Those two were the only problems I had. Hope those tips help in some way.
Click to expand...
Click to collapse
Well far as I know I'm using the up to date version which is .24. I haven't had the screen off issue or the rearranging problem. Flashfire showed what it was doing and what order it did it in. Everytime I used it, if the screen went black, it would say rebooting...after all was finished. So maybe the version you had was just buggy which the dev did say its a work in progress. Stuff like that, I'd be surprised if they got it to work perfectly with no bugs
stang5litre said:
Flash fire is horrible. Use v24 seems to be the best atm. I can do both. In the middle of mod'ing the s5 rom I made. But after I build it I would have you test it 1st before deodexing as you want to make sure it boots 1st before moving on.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I am more then willing to test any roms out as well. My new Galaxy S4 prepaid is only for tethering on my unlimited data, so I need a rom that I can install Xposed Framework on. Any rom that comes out and needs testing for OH7 based phones, I am onboard with.
TheXev said:
I am more then willing to test any roms out as well. My new Galaxy S4 prepaid is only for tethering on my unlimited data, so I need a rom that I can install Xposed Framework on. Any rom that comes out and needs testing for OH7 based phones, I am onboard with.
Click to expand...
Click to collapse
Well I am looking to install xposed as well but we gotta wait for the dev to have free time to rebuild a rom to the oh7. Well at least he has two people willing to test now for him. How did you get unlimited data with Verizon? They so stingy with data
Sorry been busy. Will build it tonight. Already deodexed. Just got to build it. If all you doing is using it for a hot spot why waste time building a rom for it. Dl a app and use your hot spot. I use foxfi on my s7 edge. Works np.
Let me know. Thought this was for people to actually use.
Sent from my SM-G935V using Tapatalk
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
bjf189 said:
Well far as I know I'm using the up to date version which is .24. I haven't had the screen off issue or the rearranging problem. Flashfire showed what it was doing and what order it did it in. Everytime I used it, if the screen went black, it would say rebooting...after all was finished. So maybe the version you had was just buggy which the dev did say its a work in progress. Stuff like that, I'd be surprised if they got it to work perfectly with no bugs
Click to expand...
Click to collapse
Black screen means the order was incorrect and wipe was moved to the end.
Sent from my SM-G935V using Tapatalk
stang5litre said:
Sorry been busy. Will build it tonight. Already deodexed. Just got to build it. If all you doing is using it for a hot spot why waste time building a rom for it. Dl a app and use your hot spot. I use foxfi on my s7 edge. Works np.
Let me know. Thought this was for people to actually use.
Sent from my SM-G935V using Tapatalk
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
Black screen means the order was incorrect and wipe was moved to the end.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I'm not looking to use it for the hotspot. I already can use it without any problems. I'm just wanting a custom rom/modded stock rom, I hate full stock and I love being deodexed. I'm sure more people will use your rom once they discover it.
If you believe that flashfire moved the order around, what can I do to stop that? The log in it says what it's doing and it says it's going in correct order so im not sure. Ive been using v24 which is latest I think
bjf189 said:
I'm not looking to use it for the hotspot. I already can use it without any problems. I'm just wanting a custom rom/modded stock rom, I hate full stock and I love being deodexed. I'm sure more people will use your rom once they discover it.
If you believe that flashfire moved the order around, what can I do to stop that? The log in it says what it's doing and it says it's going in correct order so im not sure. Ive been using v24 which is latest I think
Click to expand...
Click to collapse
Flash Fire moves it on its own right before you flash. You have to press and hold wipe and drag it to the top. It does this a lot. Pain in the arse. Ok I'll build it then just wasn't sure
Sent from my SM-G935V using Tapatalk
stang5litre said:
Flash Fire moves it on its own right before you flash. You have to press and hold wipe and drag it to the top. It does this a lot. Pain in the arse. Ok I'll build it then just wasn't sure
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I did that cause it put it at the bottom at default. I moved it to the top but still got same outcome. Maybe it's something to do with the kernel an bootloader bring different? That's my guess
bjf189 said:
I did that cause it put it at the bottom at default. I moved it to the top but still got same outcome. Maybe it's something to do with the kernel an bootloader bring different? That's my guess
Click to expand...
Click to collapse
What were you flashing?
Sent from my SM-G935V using Tapatalk
stang5litre said:
What were you flashing?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Well I tried out your ultra note5 and non mdk one. I believe the ultra note wouldn't show the boot animation and cut off booting sound after a second then did nothing. The other one which was the non mdk one, didn't show boot animation but made the Samsung sound correctly but after booting into the system like ten minutes later of waiting, I get a pop up of system is not responding. If I ignore it an let it load another ten minutes or so, the setup wizard opens but if I hit wait or close on the system not responding box, it all closes and goes to black screen again and just repeats
bjf189 said:
Well I tried out your ultra note5 and non mdk one. I believe the ultra note wouldn't show the boot animation and cut off booting sound after a second then did nothing. The other one which was the non mdk one, didn't show boot animation but made the Samsung sound correctly but after booting into the system like ten minutes later of waiting, I get a pop up of system is not responding. If I ignore it an let it load another ten minutes or so, the setup wizard opens but if I hit wait or close on the system not responding box, it all closes and goes to black screen again and just repeats
Click to expand...
Click to collapse
Uploading stock rom for you to try....androidfilehost keeps losing connection.. You already built the rom from what i read a page back. So do you want me to just Upload the deodexd stuff for you to insert?
Sent from my SM-G935V using Tapatalk