This ROM has been tested and retested... IF you cannot follow instructions provided DO NOT FLASH,IF your wanting tweaks etc DO NOT FLASH OR ASK FOR THEM THERE ARE OTHER ROMS WITH YOUR WANTS AND DESIRES,IF you are uneasy about flashing firmware DO NOT FLASH THIS ROM,DO NOT USE ANY PART OF THIS ROM WITHOUT PERMISSION, IF your wanting to use another kernel (99% stock is included) etc,DONT ASK HERE IF ISSUES ARISE (ASK THE KERNEL DEV) Folks who use this want a clean stable ROM..IF you are a flashaholic,id suggest copying pics,music etc to computer format your data partition then flashing.
Whats included:
Extra Themes
Eye Experience
Extra Camera Modes
Xposed ONLY included in 4.4.4 and below for now
Integrated VVM (Dialer and Messages)
Isis (Working with Xposed Modules) ONLY WORKING 4.4.4 and below for now
Speed Tweaks
Battery Tweaks
SD Card Tweaks
Screen Touch Tweaks(more sensative)
Dalvik Tweaks
Hardware Tweaks (Qualcomm)
Network Tweaks (Qualcomm)
Stock recovery
Twrp recovery
Weather images updated Thanks Basil3 Not included in latest 5.0.2
Read write module Thanks Flar ONLY WORKING on 4.4.4 and below for now
Rooted
Stock file manager
Quick office Removed in 5.0.1
Extreme Power Saving
S-OFF IS MANDITORY!!!!
BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
***Current 5.0.1 Lollipop Flashing Instructions***
If you have not flashed the 5.0.1 firmware it is included:
CID's that will flash correctly
cidnum: BS_US001
cidnum: BS_US002
cidnum: CWS__001
****S-OFF is necessary to proceed with flashing firmware package****
Extract firmware.zip from zip, copy to adb/fastboot location,reboot phone into bootloader connecting it via fastboot option,run commands listed below
Also included in this firmware package is the modified hboot with red text removed
IF you do flash this firmware package the commands to do so are as such:
* 1.fastboot oem rebootRUU
* 2.fastboot flash zip firmware.zip(if needed re-run this command)
* 3.fastboot reboot-bootloader
After flashing this firmware package stock recovery will be installed,extract twrp_2_8_3_0_m8.img from zip, copy to adb/fastboot location reflash twrp recovery that is included by running command:
fastboot flash recovery twrp_2_8_3_0_m8.img or latest twrp image
Now after flashing twrp reboot device into recovery,do these steps as it is important!!
factory wipe device,click advanced wipe and select data,system,cache and dalvik wipe these partitions.(TWRP will reload,do not flash until after rebooting recovery) Once this is finished reboot recovery and proceed to flash this ROM.
ATT_4_28_502_1_M8_Lollipop_No_CIQ_Firmware and ROM(is full firmware with modified boot.img and hboot.img,will need to reflash twrp)
https://goo.gl/0gGHLr(current)
ATT_4_16_1540_8_M8_Lollipop_Firmware and ROM
http://goo.gl/iumj9r(depreciated)
ATT_ISIS_3_42_502_1_M8 ***Use Instructions below for 4.4.4*** (Firmware not included)
http://goo.gl/YM12mn (depreciated)
3_42_502_1 Firmware Bundle (is full firmware with modified boot.img and hboot.img,will need to reflash twrp)
http://goo.gl/U7gocS (depreciated)
DEPRECIATED
Updating Firmware:
1. Copy ROM to storage
2. Copy Firmwarezip to adb/fastboot location
3. Drag twrp openrecovery-twrp-2.7.1.0-m8.img to adb/fastboot location
4. Reboot phone to bootloader/fastbootusb(adb reboot bootloader)
5. Once connected via fastbootusb
6. Open command prompt,
7. Run these commands:
* 1.fastboot oem rebootRUU
* 2.fastboot flash zip 2.22.1540.3_firmware.zip or whatever the latest builds firmware zip is called.
* 3 repeat #2 command to finish firmware flashing.
Already modified to work on cid's,so no need to change cid
cidnum: BS_US001
cidnum: BS_US002
cidnum: CWS__001
* 4.fastboot reboot-bootloader
8. Once rebooted, run these commands:
* 1.fastboot flash recovery openrecovery-twrp-2.7.1.0-m8.img or whatever latest twrp image is
* 2.fastboot reboot-bootloader
* 3.Boot into recovery,factory reset,flash rom (IF ROM has been wiped off data partition,copy rom zip to fastboot/adb location and run adb sideload from recovery..Or adb push nameofrom.zip /sdcard/. Then flash
Modified hboot is already included to remove developer text
After installing ROM:
REMINDER *You MUST flash the latest 2.22.1540.3/.4 or whatever the latest builds firmware zip is called firmware(Included)* ,Once booted DO THESE NEXT STEPS FIRST BEFORE ANYTHING ELSE!!!!,ROM is rooted,has read/write protection disabled,has at&t apn's ...Set Superuser permissions to grant always(no prompts)...Update Xposed Framework and installer...Reboot when prompted....Download Rootcloaker Module, install and activate it....reboot run isis....THEN finish setting up ROM...I dont have a secure sim,butit asks for it,so that means its a go...this also has visual voicemail integrated into system(dialer/messaging app)...I suggest disabling animations in developer options to get the full effect of rom speed...
Enjoy
Download:
M8 - 2.23.502.3(depreciated)
http://goo.gl/3DiIQz FULL WIPE REQUIRED
Mirror: http://goo.gl/9wNs1J (Thanks krazyace35)
ATT 1.16 Radio fix (Thanks runsoverfrogs)
** S-OFF IS MANDATORY **
Radio Download: ONLY For 2.23.502.3
http://goo.gl/vB9dA7(depreciated)
Copy radio-1.16.zip to adb/fastboot loacation
Open cmd
Run commands as shown below
fastboot oem rebootRUU
fastboot flash zip radio-1.16.zip
fastboot reboot-bootloader
Make sure radio has flashed correctly reboot...
Modded Hboot(Thanks santod040):
M8 - 2.23.502.3
No Red Text: http://goo.gl/ins3or(depreciated)
Download:
M8 - 2.22.1540.3
http://goo.gl/uoRz8X(depreciated)
Download:
M8 - 2.22.1540.4
http://goo.gl/yE6s5V (depreciated)
Download:
M8 - 3.28.1540.5 (Read flashing instructions included in download)11-11-2014 Update :good:
http://goo.gl/S5hpMC(depreciated)
Blinkfeed update 11-11-2014
http://goo.gl/iYYAEp(depreciated)
Blinkfeed update 12-10-2014
http://goo.gl/FHpxlV(depreciated)
For those who want to update to newest versions for developer build,you must have stock operating system and recovery and soff to run any of these files
Download:
2.22.1540.4 ota
http://goo.gl/7mec4o (Upgrade original stock device,not for custom roms) (depreciated)
Download:
3.28.1540.5 ota
http://goo.gl/MHF4ie(Upgrade original stock device,not for custom roms) (depreciated)
Download:
3.28.1540.5 Firmware only unmodified (Latest 4.4.4 Update,S-OFF REQUIRED)
http://goo.gl/tyhRRZ(depreciated)
Download:
2.22.1540.4 firmware only unmodified(Latest 4.4.3Update,S-OFF REQUIRED)
http://goo.gl/FJ7Hhv(depreciated)
Mirrors for ROM's(Thanks tarund)
http://goo.gl/7AuuJf
Changelog:
08-09-2014: App updates....Speed increase,some other minor fixes
08-13-2014 App updates...Minor tweakage
08-27-2014 New base 2.22.1540.4
08-29-2014 New base AT&T Official 2.23.502.3 Debloated and carrieriq removed
09-08-2014 Fixed double/not sending txt issue (I think),Kernel enhancement
9-10-2014 Reverted back to TWRP 2.6.3.3 as used recovery,Reverted Some edits back to stock.
10-19-2014 New Base 4.4.4 3.28.1540.5
11-06-2014 Updated HTC apps, 3rd party apps & some other stuff I dont recall off top of my head.
11-10-2014 Updated LTE configs,Some Camera Enhancements
1-20-2015 Developer Lollipop Release
5-19-2015 Official AT&T Lollipop Release
Thanks for this possible fix as well if the dble txt is still happening
runsoverfrogs said:
I fixed my hanging double text by rolling my radio back from 1.19 to 1.14 Edit WNC 1.16 works as well) baseband
Click to expand...
Click to collapse
Donations:
Thank you...
bruce7373
swapgut
orvon.freeman
co.ag.2005
vegasdiceshooter
cortez.i
ozziedog
effezie
fuzz_33594
Alpione
mimart7
aka120
Vegasdiceshooter
Isis111
Thanks to
ccb101
californiarailroader
orvon freeman for getting me the files
HolyAngel for helping with update script
homeslice for helping with carrieriq
Big thanks to my testers
manup456
mobb315
zero209
pumpiron579
ccb101
tarund
Judge Joseph Dredd
redpoint
swapgut
Already have the firmware installed can i just flash rom
Nice work, flashed firmware, installed rom, isis working vvm great job wnc
Firmware also includes unsecured boot image modded hboot suggested to flash it,then flash rom afterwards.
vegasdiceshooter said:
Already have the firmware installed can i just flash rom
Click to expand...
Click to collapse
Enjoy....
Pumpiron579 said:
Nice work, flashed firmware, installed rom, isis working vvm great job wnc
Click to expand...
Click to collapse
This Rom is kick ass! Way better than any Euro Rom imo.
Glad my boy is back in the building great work bro.
Sent from my HTC One_M8 using Tapatalk
Flashed and its a great ROM much better for AT&T than European ROMs
Glad your enjoying it...
vegasdiceshooter said:
Flashed and its a great ROM much better for AT&T than European ROMs
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Firmware also includes unsecured boot image modded hboot suggested to flash it,then flash rom afterwards.
Click to expand...
Click to collapse
So is the z-data file that wipes the phones removed from the firmware?
Read o.p. BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
GermanGuy said:
So is the z-data file that wipes the phones removed from the firmware?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Read o.p. BACKUP Pictures,Music,Etc. just in case device is wiped when flashing firmware
Click to expand...
Click to collapse
I did read the OP. Just had the simple question of whether the z-data file has been removed. If that file is removed, the phone should not get wiped.
No its not, and will not be removed from download,this ensures no bugs from things left on storage...and also ensure the storage doesnt encrypt because of stuff left over from other roms...So if you want to remove it thats on you,not resposible for anything that goes wrong.
GermanGuy said:
I did read the OP. Just had the simple question of whether the z-data file has been removed. If that file is removed, the phone should not get wiped.
Click to expand...
Click to collapse
This is developer edition firmware and Rom though right? Or is the developer edition the same for the most part as att?
Sent from my HTC One_M8 using Tapatalk
Yes developer edition is same device only difference is ones locked and ones not.The base for the rom is developer edition correct...
Johnny424 said:
This is developer edition firmware and Rom though right? Or is the developer edition the same for the most part as att?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thanks for the 2.22.1540 firmware, and great instructions. While I've flashed firmware before and familiar with the process, its nice to not have the proper command syntax right here.
Also great forethought to have it packaged with the ROM, and a good explanation of the process.
Anyone having issues with keeping wifi on? Mine keeps turning off...
Nope has been flawless what have you added/modified? Did you follow the instructions included or did you do it the way you wanted to?(Just a question..Not being rude).
diehardbattery said:
Anyone having issues with keeping wifi on? Mine keeps turning off...
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Nope has been flawless what have you added/modified? Did you follow the instructions included or did you do it the way you wanted to?(Just a question..Not being rude).
Click to expand...
Click to collapse
Installed Sense Toolbox, changed the theme of the statusbar icons. At first I thought maybe it was the theme and the icon just wasn't showing, but when I went to wifi settings, it wasn't connected to anything. Made some other tweaks in there, mostly visual.
Installed Battery Stats Permission, SD Full access, and Xposed Call blocker. That's it.
And I did follow the directions to the letter.
Related
I been searching around all over the place and I am just hitting my head against the wall. Any help would be appreciated.
This is my setup: hboot 1.5 S-ON, I have unlocked using the HTC method. I have Revolutionary CWM recovery installed.
I am looking to update the Kernel and Radio/PRI of the phone to the latest versions. (I haven't done it in a very long time.)
By what I read, since I have hboot 1.5 updating the kernel seems close to impossible. I did read that I may have to go to a Stock Rom and update via sprint OTA to get the latest updates then unlock again? That doesnt sound right to me.
I am all types of confused. Part of this was started because I wanted to try the MeanROM (link:http://forum.xda-developers.com/showthread.php?t=1466362) and also update my phone. Everything I try to do fails or I cant do because of the 1.5 or the S-ON.
Hopefully i am making some sense. I dont know what I have to do to get the latest kernel or if it even is possible.
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
megabiteg said:
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
For the EVO 3D, much like the EVO 4G, the custom ROMs generally do not contain the radio or pri images.
There are some different reasons for this, but one of the common reasons being some users claim to experience different radio performance based on their geographic loation in relation to different versions of the radio and pri images.
luis4ever said:
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
Click to expand...
Click to collapse
The only clarification to this post would be having recovery.img in the root of your SD card is not required for rebooting into recovery mode. In order for a custom recovery to load, when rebooting into recovery mode, the recovery.img has to have been flashed previously. Flash Image GUI can also flash the recovery.img to the recovery partition so when you reboot into recovery, the proper custom recovery loads. Most users flash custom recoveries infrequently when compared to how often they flash ROMs so the process for flashing the recovery process isn't covered as often.
In general, regarding the OP's original question of flashing the "MeanROM", the Flash Image GUI thread provides a great beginner step by step guide I wrote to help walk thru the general overview and process. I've quoted it below for easy reference.
Appreciate all the support of Flash Image GUI! I'll echo the optimism for hboot 1.5 s-on unlocked users, most everything is still possible. HTC just requires an extra few steps which can be frustrating, but once they are learned, the process is fairly smooth.
Hope the clarification helps iron out any confusion on the details!
HTC Unlock - Hboot 1.5 Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using HTC method for Hboot 1.5 users
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
Click to expand...
Click to collapse
Okay, here's the situation.
I just flashed hboot 1.58 from here: http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7
Beforehand, I flashed Freeza's AIO package posted on 8/1/2012, the one that updates everything but the kernel, recovery, and hboot: http://forum.xda-developers.com/showthread.php?t=1673377
On my bootloader screen I have:
***LOCKED***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
RADIO-1.09.00.0706
OpenADSP-v02.6.0.2226.00.0217
eMMc-boot
May 17, 2012,15:06:44
I'm using the latest 4EXT recovery, which is v.1.0.0.5 RC6 Testing, build: 46
I've tried _EVERYTHING_ to get this ROM going: format all partitions (except SD Card), wipe dalvik-cache, even the superwipe. Afterwards I would go into the setup and try to install the ROM. ROM installs, but on reboot I get stuck on a white HTC screen. This used to happen a lot to other people, but I understand this was (mostly) kicked in the rear end.
I've also set all the VPU/CPU speeds to the stock settings in the installation, and still no dice. Just so ya know, I can even install the latest deodexed gingerbread stock ROM for this device, and it works, for the most part (it bootloops until I install the hboot 1.40 revolution version).
Any help would be greatly appreciated.
****EDIT**** I got it to work; see post #10 if you are/were in the same pickle as me
It looks like you've done everything right. How long does it sit in the HTC screen?
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
It looks like you've done everything right. How long does it sit in the HTC screen?
Click to expand...
Click to collapse
hi coal, thanks for the reply.
and the phone sits on the HTC screen indefinitely (either till the battery dies or I pull it).
My guess would be incorrect kernel.
sudo passwd root
ZWYATT said:
My guess would be incorrect kernel.
Click to expand...
Click to collapse
see that's what I was thinking too, but..
1. the full AIO freeza package has the kernel but has the potential to reset S-OFF (due to it including hboot 1.58)
and 2. you flash a ROM, the kernel usually comes with it..?
I could not get Tribs rom to push the kernel.
You gotta find a compatible kernel, copy to sd, install via 4ext, then install rom.
sudo passwd root
thanks ZWYATT. is it possible to edit the other freeza update pack to update just the kernel only, or could it be possible to extract just the kernel from the update pack and install VIA 4ext?
and since this'll be my first time flashing a kernel, I just install from zip like always, right?
From what I read, freeza doesn't touch the kernel.
Yep, just dload a compatible kernel, it will be a zip file, and choose install zip in 4ext.
You'll have to ask Trib about extracting a kernel from his rom. I do not know if he wants, or cares, if people do that.
sudo passwd root
ZWYATT said:
From what I read, freeza doesn't touch the kernel.
Yep, just dload a compatible kernel, it will be a zip file, and choose install zip in 4ext.
You'll have to ask Trib about extracting a kernel from his rom. I do not know if he wants, or cares, if people do that.
Click to expand...
Click to collapse
Cool, thanks. As for Trib's ROM, all I know is people can use it as a base, but if people can extract the kernel from his ROM, I have no idea. it'd be nice if he'd check this thread since I can't post in his thread until I have at least ten posts.
EDIT: If it is allowed to extract the kernel from the ROM, can I take the kernel folder and make it into a zip file, then install via 4EXT?
I got it working, thanks to everyone (even Trib over PM, thanks A MILLION )!!!!
Here's how I did it:
***DISCLAIMER*** I take *NO* responsibility for bricks, voided warranties, your boss getting mad at you over the alarm app not working as it should, etc.
Pre-requisites:
* an HTC Evo 3D
* Latest version of Trib's SolidROM (you can either use the Custom or Stock GUI; I used the Stock GUI)
* fully functional adb and fastboot
* HTC drivers installed on your computer
* Virus's AIO package (found in step two)
* PG86IMG.zips of HBOOT 1.4 Revolutionary and HBOOT 1.58 (found in the OP)
* a kernel compatible with SolidROM (if you don't have one, here's one that Trib gave me: http://animeondroid.host22.com/boot.img)
* Latest version of 4EXT Recovery
0. Open a command prompt and navigate to your platform-tools folder
1. Make backups of anything that's important to you, this includes:
* Apps/Data (Use Titanium Backup or similar)
* SMS Text messages (I use SMS Backup & Restore)
* Contacts that aren't otherwise stored on your Google/Exchange/etc accounts
* And finally, ALWAYS NANDROID BACKUP YOUR CURRENT INSTALLATION!! This cannot be stressed enough.
2. Copy over the Virus AIO PG86IMG.zip found here to your SD card.
3. Reboot into bootloader and install Virus's AIO package (don't worry, it won't override your S-OFF)
4. Reboot into recovery and delete the PG86IMG.zip from the root of your SD Card
5. Wipe all partitions except SD Card (additionally, if you have the superwipe.zip feel free to use it also, justin case)
6. Wipe Dalvik Cache; optionally, wipe battery cache (if you haven't wiped it in awhile, now would be a good time to do so as preventative maintenance)
7. Enable smart flash if you haven't done so
8. Install Trib's SolidROM (personally I kept the Processing Unit (3D, 2D, Central) clock speeds as close to stock as I can and enabled V-sync)
9. Enable USB storage after installing the ROM
10. Put the PG86IMG.zip (the one that contains hboot 1.4 revolutionary) onto the root of your SD Card
11. Reboot into bootloader, get into the main screen, and let it install the hboot 1.4 revolutionary PG86IMG.zip; after you install the hboot, you get a black screen on reboot and a blinking power light, this is normal, don't worry. Just unplug your device from your computer and plug it in again
12. Reboot into recovery, enable USB Storage, and delete the PG86IMG.zip from your SD Card
13. Reboot into bootloader, get into fastboot, copy over a compatable ICS kernel into your platform-tools directory in your android SDK, and flash it (Trib was nice enough to give me a copy of his boot.img, see the pre-requisites; thanks A MILLION!!! ); command should be fastboot flash boot boot.img (assuming you're in your platform-tools directory in your android-sdk folder or you set it as part of your path variable, and you named your kernel boot.img)
14. Reboot into recovery, enable USB Storage, and copy over the hboot 1.58 PG86IMG.zip to the root of your SD Card
15. Reboot into bootloader and install hboot 1.58
16. Reboot normally and you should be in Trib's SolidROM!!!
Have fun and enjoy! Oh yeah, don't forget to read over the OP and the thread for SolidROM for all known issues, updates, patches, etc: http://forum.xda-developers.com/showthread.php?t=1808332
Okay. So I see Trib has a new version of his ROM out... problem is, it intermittently likes to reboot.
I've tried EVERYTHING:
* wipe all partitions EXCEPT SD Card, followed by a superwipe
* I _finally_ got my bootloader unlocked, so I tried trib's method of flashing the stock RUU first, THEN his ROM
and either way, it reboots at random.
I even tried flashing the old kernel on his new ROM (and vice versa) to rule out the kernel, but unfortunately things get worse, as I can't even get on 4G or WiFi!!!
Here's a weird bug I got in the Play Store...
Update a user app, any of them. Swipe the progress bar. The update will automatically install and appear to work just fine o.o
However, do this to any of the Sprint bloat apps and it won't work (except voicemail, since it has its own updater)
Anyone else seem to get this?
Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away
Disclaimer: I am not responsible for any malfunctions of your device or any damage, disintegration, or insanity that results to you or your phone if said event occurs. However I will help out in anyway I can if your device dies after an install of this ROM
Now for the cool stuff, the ROM features are:
It is Deodexed
It is Zipaligned
It has the new GAPPS
It has been Debloated ~200-300mb
Features to come:
Viper4Android
Pure Performance X
Pure Graphics
Xposed Framework (will be optional)
and a couple others.
Rom bugs:
Cant install apps from playstore!!! (if you want to help me out with figuring this out that would be much appreciated)
Steps to flash
1.Flash ROM
2.Clear DATA
3.Flash Gapps Package
4.Boot into bootloader and flash the boot.img from your pc via fastboot with the command fastboot flash boot boot.img
5.Boot go through the setup and wait for the Play Store to update
Links:
ROM
Gapps
Boot.img
Credits for the boot.img go to summer.cat
post pictures, please!
Some people fixed the play store issue simply by changing the timezone of their android device, i think it was a CM branch bug.
If I took the 4.4.4 OTA update, is there any way for me to get root at the current time?
So I can flash this through my safestrap recovery and run 4.4.4 on my Maxx that is rooted with WP Off?
I'm just trying to make sure that Im not reading this wrong, thats all.
Thanks for all of your hard work!
CurbThePain said:
Disclaimer: I am not responsible for any malfunctions of your device or any damage, disintegration, or insanity that results to you or your phone if said event occurs. However I will help out in anyway I can if your device dies after an install of this ROM
Now for the cool stuff, the ROM features are:
It is Deodexed
It is Zipaligned
It has the new GAPPS
It has been Debloated ~200-300mb
Features to come:
Viper4Android
Pure Performance X
Pure Graphics
Xposed Framework (will be optional)
and a couple others.
Rom bugs:
Cant install apps from playstore!!! (if you want to help me out with figuring this out that would be much appreciated)
Steps to flash
1.Flash ROM
2.Clear DATA
3.Flash Gapps Package
4.Boot into bootloader and flash the boot.img from your pc via fastboot with the command fastboot flash boot boot.img
5.Boot go through the setup and wait for the Play Store to update
Links:
ROM
Gapps
Boot.img
Credits for the boot.img go to summer.cat
Click to expand...
Click to collapse
Jaocagomez said:
post pictures, please!
Some people fixed the play store issue simply by changing the timezone of their android device, i think it was a CM branch bug.
Click to expand...
Click to collapse
If someone could test that and see if it actually works on this rom that would be amazing and I will post pictures asap.
Blade765 said:
So I can flash this through my safestrap recovery and run 4.4.4 on my Maxx that is rooted with WP Off?
I'm just trying to make sure that Im not reading this wrong, thats all.
Thanks for all of your hard work!
Click to expand...
Click to collapse
Please do not quote the the op. But yes. You can also always go back to the old 19.5.3 4.4 rom. But dont forget to flash the boot.img provided in the op post. Lastly you will still have wp off. But for some od reason there are a lot of google play issues with this rom. Ive redone all of my work 2 times and it still ends up with the same issues.
If you want to stay rooted with wp off stay on 4.4 but you can still flash this. So basically no you cant get root on 4.4.4 ota to my knowledge. Yet.
Works on the MINI
Just wanted to say THANK YOU!
This worked on my DROID MINI (was on 4.4 Rooted WP Off/ SafeStrapped)
Here we have a collection of RUUs, firmware, untouched system backups, and stock rooted ROMs...
Latest RUU
Sprint_HTC_One_M9_4.27.651.4_RUU
0PJAIMG RUUs
0PJAIMG_Sprint_HTC_One_M9_4.27.651.4_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.41_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.21_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.13_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.4_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_2.11.651.19_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_2.6.651.11_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_1.32.651.30_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_1.32.651.17_RUU.zip
*credit to @Rydah805 for the 1.32.651.17 RUU
Rename to 0PJAIMG.zip, copy to sd card, boot into download mode, it should scan card & prompt to install
***NOTE*** S-ON users can ONLY flash signed firmware!!!
Firmware
4.27.651.4 Signed Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=457095661767155280
4.27.651.4 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=817550096634761570
4.27.651.4 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=745425885120723749
4.27.651.4 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=817550096634761569
Previous Firmware
3.41.651.41 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224405571
3.41.651.41 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224405569
3.41.651.41 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224405570
3.41.651.31 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224398913
3.41.651.31 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862681927
3.41.651.31 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224398912
3.41.651.21 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862669390
3.41.651.21 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862669389
3.41.651.21 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862669388
3.41.651.13 Signed Firmware from OTA for S-ON users(fastboot flashable): https://www.androidfilehost.com/?fid=24651430732238190
3.41.651.13 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24651430732238219
3.41.651.13 Modified Firmware from OTA, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=24651430732238218
3.41.651.13 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=24686680535467780
3.41.651.4 Full Signed Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24407100847294492
3.41.651.4 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24407100847294493
3.41.651.4 Modified Firmware from OTA, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=24407100847294494
2.11.651.19 Full Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811177
2.11.651.19 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811176
2.11.651.19 Modified Firmware from OTA, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811175
2.11.651.19 Radio only from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811174
2.6.651.11 Full Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347767489
2.6.651.11 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347770518
2.6.651.11 Modified Firmware from OTA, removed recovery & aboot (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347767490
2.6.651.11 Radio only from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347767491
1.32.651.30 Full Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934554030
1.32.651.30 Modified Firmware from OTA, removed recovery & aboot (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934554191
1.32.651.30 Radio only from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934554197
1.32.651.17 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934552130
1.32.651.17 Radio only from RUU (fastboot flashable): http://206.174.247.158/public/android_dev/1.32.651.17_radio_only.zip
*credit to @deakelem for the .17 radio zip, thx!
Flash Firmware via bootloader (requires micro sd card)....
-rename firmware to 0PJAIMG.zip
-copy 0PJAIMG.zip to ext_sd card
-boot into bootloader or download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader or download mode
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
OTAs
OTA_HIMA_WHL_N70_SENSE80_SPCS_MR_Sprint_WWE_4.27.651.4-3.41.651.41_release_500479.zip
OTA_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.4-2.11.651.180_release_470372.zip
OTA_HIMA_WHL_L51_SENSE70_SPCS_MR_Sprint_WWE_2.11.651.19-2.6.651.11_R3_release_449495.zip
OTA_HIMA_WHL_L51_SENSE70_SPCS_MR_Sprint_WWE_2.6.651.11_R3-1.32.651.30_R_release_439101.zip
OTA_HIMA_WHL_L50_SENSE70_SPCS_Sprint_WWE_1.32.651.30_R-1.32.651.17_R2_release_427417.zip
Stock Rooted ROMs
Before flashing this Stock Rooted ROM or making any system change, make sure you have done a clean SYSTEM IMG BACKUP using TWRP 2.8.6.0 or newer!!! See post# 2 for more information.
Stock Rooted 3.41.651.41 ROM
Bad_Boyz_Sprint_ONE_M9_4.27.651.4_stock_rooted.zip
-SuperSu & BusyBox added
Previous Stock Rooted ROMs
Bad_Boyz_Sprint_ONE_M9_3.41.651.41_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.31_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.21_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.13_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.4_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_2.11.651.19_stock_rooted_deodexed.zip
Bad_Boyz_Sprint_ONE_M9_2.6.651.11_Deodexed_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_2.6.651.11_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_1.32.651.30_Deodexed_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_1.32.651.30_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_1.32.651.17_Stock_Rooted.zip
-SuperSu & BusyBox added
-unsecure boot.img
-init.d support
XDA:DevDB Information
[RUU][Firmware][Stock Rooted ROM][Stock Backup]Sprint HTC One M9 | 1.32.651.17, ROM for the Sprint HTC One (M9)
Contributors
OMJ, chas123, benny3
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Stable Release Date: 2015-04-05
Created 2015-04-05
Last Updated 2017-08-02
Reserved
here is a nice batch tool from @Sneakyghost I edited for Sprint...(Tasker_1.2.8.bat was edited, and stock Sprint recovery added).
original thread can be found from HERE, go give him a thanks!
Extract to folder & run Tasker_1.2.8.bat
DOWNLOAD Android_Tasker_1.2.8_Sprint_M9
Sneakyghost said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The "Android_Tasker" Batch Tool - a thing i am using for myself since 2012 and which i am sharing just because i have it. It is neither good nor special, but its the way i work and people who follow the instructions here might find it easier to use the same setup as we do.
It also has the "FUU" method included - details on that method will be added at a later stage. We do not consider the FUU a good option to flash Firmware anymore because we realized that getting away from ADB and Fastboot with toolkits makes troubleshooting harder at a later stage - people relying entirely on toolkits and tools will mostly not understand what is happening and helping there is much harder.
Since everything i do basically works out of the C:\Android\com path, all my zipped-up stuff extracts to that location. The FUU and the Task-Batch-Script both work from that location. This is simply to enable easier and faster creation of new zip’s if they all use the same base structure.
If you prefer to work from a different location. you can specify a different path in the installer. However, the batch scripts do not adjust automatically, which means if you use another path, you might need to open up the scripts in an editor and adjust some paths manually.
Preview:
DOWNLOAD
MD5: 84A4968A9C698FA328A6C13DCB1D764F
The installer is just a simple WinRAR self extracting archive - there is NOTHING BAD in there i swear! Open it with WinRAR 5 and look inside. You will see if you don't trust me.
Changelog:
1.2.8
Splash1 converter works now. Flashing Splash1 now needs a reboot to Bootloader - it's not working in Download Mode! (limited DD support on the M9 and general flashing system changes).
Swapped out recoveries for newer versions.
Finally added the complete file set from RUU 3.0.1.15 - the newest M9 RUU. ADB and Fastboot are identical to the previous version from Llabtoofer though.
Screenrecord removed - can’t be bothered figuring out why it doesn’t work anymore. Probably SELinux and general Android 5.x security like with the screenshot function. Not really needed either. There are other solutions.
1.2.7
Swapped out recoveries for newer versions.
Swapped out ADB and Fastboot for a newer pack (thanks @LlabTooFeR) - now this Tool is fully M9 compatible and even flashes large RUU.zips.
1.2.6
Changed everything to M9 files and methods. I HOPE I didn't oversee anything. Please test carefully!
Added stock_recovery_1.32.401.8.img
Added TWRP Recovery 2.8.6.0 fixed version from Captain_Throwback SOURCE Post #2 Beta version
Added original HIMA Splash1 - S-OFF phones only!
Previous versions:
1.2.5
Added TWRP Recovery 2.8.5.2 from Captain_Throwback (All M8 devices)
Fixed Recovery Screenshot option (20)
1.2.4
Added newer RUU structure (2.0.16.2014 - from 4.16.1540.8 Dev Edition RUU)
Added Stock Recovery 4.16.401.10.img (WWE)
Changed the License and SFX texts again (Installer) - never happy with it.
1.2.3
Fixed some serious crap nobody reported. I just found out myself.
Added Stock Recovery 4.16.1540.8 (sorry still don't have the WWE recovery, but i guess they are identical)
Added TWRP 2.8.4.0 from the M8 tree of Dees_Troy.
1.2.2
Added Stock Recovery3.28.401.7
1.2.1
Added Microsoft's vcredist_x86_2008_SP1.exe to the installer because the ARUWizard is build on the x86 Visual Studio 2008 runtime. This resolves the "side-by-side configuration" error.
Added 3.28.401.6 stock recovery and splash
Added newer RUU structure (doesn't do any difference though, just keeping it up to date)
Added TWRP 2.8.0.3 (it still has slight issues with MTP which will be fixed soon but for now, this is good enough)
Changed a few lines in the script (minor, cosmetical stuff)
Updated the INFO PDF (option 24)
Known Issues:
Kernel Flashing needs fixing - can only work in fastboot now due to SELinux and related crap.
The partition Dumper is not correctly working, probably also due to SELinux.
Anyone used to like @squabbi's fully GUI based toolkit? He's picked it up on the M9 as well - maybe you like GUI better than commandline. Then head over here: http://forum.xda-developers.com/showpost.php?p=59949972&postcount=1
Click to expand...
Click to collapse
Reserved
*IMPORTANT INFO* taken from this thread!!!
Captain_Throwback said:
Frequently Asked Questions (FAQ)
1. Why is this device different than my previous HTC device?
With the M9, HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents."
2. Which version of TWRP am I supposed to use?
Right now, the latest official version (2.8.7.0) is the best version to use.
3. Why is there a "System" backup option and a "System Image" backup option now?
The "System" option is the standard tar backup. The "System Image" option is only relevant if your system is unmodified. This allows you to make a fully stock backup that can be restored later to take an OTA.
NOTE: If you are using a FAT32-formatted card, a "System Image" backup will fail, due to the 4GB file limit on that format. For a successful System Image backup, NTFS or exFAT-formatted storage must be used (either SD card or USB-OTG)
4. How am I supposed to root?
If you would only like to root via SuperSU, after making a stock backup, flash the BETA version of SuperSU posted here which properly mounts system, even when TWRP has it mounted read-only.
5. I tried to install x ROM, but it won't boot. Should I use TWRP 2.8.5.0 to flash it?
No, you shouldn't. You should use the version of TWRP recommended above. If the ROM updater-script is done properly, even if your device has system mounted read-only, the ROM should still flash fine. If your ROM chef/team has chosen to mount the partitions some other way, then you may have to mount system manually in order for the ROM to flash successfully. This can be done in the Mount menu, by unchecking the "Mount system as read-only" box and then checking the box next to System to mount it. The very act of booting 2.8.5.0 will change the system checksum, making it impossible to get a fully stock backup.
6. So what's the proper procedure to root without breaking OTA?
There is no way to take an OTA after you root. However, prior to rooting, you can take a fully untouched system image backup with TWRP, which can be used to restore a fully stock system to the device in order to take an OTA.
7. How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled on the M9's ABOOT, so TWRP must be fastboot flashed over stock recovery. The firmware zip included in the OTA will include a usable stock recovery image. That can be extracted and flashed after stock system is restored so that the OTA can be applied.
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
11. How do I get that new stock theme from the Screenshots tab?
See here.
12. What if I'm unlocked but unrooted and don't have access to a computer? How can I install TWRP?
See here.
Hima-Specific Peculiarities/Issues
IT IS NOT RECOMMENDED TO USE ANY VERSION OF TWRP PRIOR TO 2.8.6.0. The previous version(s) mount system read-write and will break the system checksum on initialization, making it impossible to get a fully stock system backup.
As of TWRP 2.8.6.0, in order to preserve system intergrity to complete a fully stock system backup, system is mounted as read-only. Starting with the official TWRP 2.8.6.1, TWRP will detect whether system is unmodified and give you the option to leave it as read-only or mount it read-write. The box to select/deselect this option is in the "Mount" menu.
Current TWRP "bugs" for Hima
One cannot simply flash zips larger than 2GB (upstream bug)
Battery may read 66% when booting into recovery (plugging into USB appears to correct this issue)
Touch may occasionally stop working when using AROMA (may be related to device overheating)
Beta Versions
These versions will include fixes not currently merged into the official source. The new beta naming convention with always start with the official base, followed by author (in this case, me) and beta version. This should help to eliminate some of the version number confusion of previous betas.
Beta Changelog:
Code:
[I][URL=http://forum.xda-developers.com/devdb/project/dl/?id=13383]2.8.7.1_CPTB-B1[/URL][/I]
[SIZE="2"]Includes all official 2.8.7.0 & [URL="http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720/post61580654"]2.8.7.1 test build[/URL] patches, and the following additional patch(es):[/SIZE]
[LIST]
[*][URL=https://gerrit.omnirom.org/12728][WIP] gui: stock theme rework[/URL]
[*][URL=https://gerrit.omnirom.org/14003]Update CUSTOM_LUN_FILE from AOSP USB config[/URL]
[*][URL=https://gerrit.omnirom.org/14002]Update path for libcryptfs_hw to proper variable[/URL]
[*][URL=https://gerrit.omnirom.org/14009]Properly set sys.usb.config when ums is enabled.[/URL]
[*][URL=https://gerrit.omnirom.org/13971]Add seclabel to recovery service[/URL]
[*][URL=https://gerrit.omnirom.org/11756]Allow devices to override USB init[/URL][/LIST]
Older Beta versions (current official version is newer):
Code:
[SIZE=2][I][URL="http://forum.xda-developers.com/devdb/project/dl/?id=13016"]2.8.6.1_CPTB-B2[/URL][/I]
[SIZE="1"]Includes all CPTB-B1 patches, and the following additional patch(es):[/SIZE]
[LIST]
[*][URL="https://gerrit.omnirom.org/13818"]Fix ORS scripts displaying an error after completing[/URL][/LIST]
[I][URL="http://forum.xda-developers.com/devdb/project/dl/?id=13015"]2.8.6.1_CPTB-B1[/URL][/I]
[SIZE="1"]Includes the following patches not yet merged to the official:[/SIZE]
[LIST]
[*][URL=https://gerrit.omnirom.org/12728][WIP] gui: stock theme rework[/URL]
[*][URL="https://gerrit.omnirom.org/13746"]minuitwrp: fix crash when taking a screenshot.[/URL]
[*][URL="https://gerrit.omnirom.org/13747"]partition: recreate tw_internal_path(/data/media/0), after wipe media from data or format /data.[/URL]
[*][URL="https://gerrit.omnirom.org/13793"]Fix system read only behavior during boot[/URL][/LIST]
[/SIZE]
Device specific page on our website
Download link to current and past versions
Click to expand...
Click to collapse
Reserved
Thanks J.
Thanks for this. Going to save a lot of headaches.
solver404 said:
Thanks for this. Going to save a lot of headaches.
Click to expand...
Click to collapse
thx for the stock backup!
For some strange reason my dialer does not work i cannot receive calls nor make them
same here with the dialer
londawg314 said:
same here with the dialer
Click to expand...
Click to collapse
Are you using the stock rooted rom or the system backup?
Macropoutsis said:
Are you using the stock rooted rom or the system backup?
Click to expand...
Click to collapse
I am using the stock ROM .. I backed up my ROM and flashed this ROM .. I than returned to my backup and the dialer works fine ..
Do changes to the /system partition persist a reboot with this or do we need to wait for S-OFF for that?
StickyEyez said:
For some strange reason my dialer does not work i cannot receive calls nor make them
Click to expand...
Click to collapse
londawg314 said:
same here with the dialer
Click to expand...
Click to collapse
I'll have to test it when I get the chance...not sure why it wouldn't work, as it's stock from dump
m03sizlak said:
Do changes to the /system partition persist a reboot with this or do we need to wait for S-OFF for that?
Click to expand...
Click to collapse
not sure, I'll have to test this too, may need to wait for s-off
OMJ said:
I'll have to test it when I get the chance...not sure why it wouldn't work, as it's stock from dump
not sure, I'll have to test this too, may need to wait for s-off
Click to expand...
Click to collapse
about the dialer. this actually happened to me the first time with the stock rom after i rooted before i tried flashing any roms.
londawg314 said:
about the dialer. this actually happened to me the first time with the stock rom after i rooted before i tried flashing any roms.
Click to expand...
Click to collapse
Good to know, add that to the list of bugs on the stock rom
Sent from my unknown using XDA Premium 4 mobile app
londawg314 said:
about the dialer. this actually happened to me the first time with the stock rom after i rooted before i tried flashing any roms.
Click to expand...
Click to collapse
Same here. I ended up having to do 3 factory resets before things stabilized.
I have the same issue too. However I did not have this issue with the stock unrooted version. I had to go back to my backup to get the phone working again.
OP updated w/ RUU & extracted firmware!!! credit to @Rydah805 thx bro!
OMJ said:
OP updated w/ RUU & extracted firmware!!! credit to @Rydah805 thx bro!
Click to expand...
Click to collapse
Rydah and I got that RUU link
question bro
how do you decrypt the RUU?
flex360 said:
Rydah and I got that RUU link
question bro
how do you decrypt the RUU?
Click to expand...
Click to collapse
http://forum.xda-developers.com/one-m9/development/dev-how-to-extract-one-m9-rom-dump-image-t3062808