This CWM/TWRP flashable zip is 4.4.4 from my dump of 212.44.26.ghost_att.ATT.en.US (ATT xt1058).
The stock ATT 4.4.4 kernel is within the zip and must be flashed manually.
Safestrap and root are 'baked in', but the rom is otherwise stock.
I am using the modem from 4.4.2 without issue, and I plan to create a new zip when the official sbf is available.
The instructions below are mostly for rooted, locked ATT phones using safestrap.
This zip does not alter your bootloader.
I was able to upgrade from 4.4.2 without a wipe/factory reset.
This rom installs Safestrap. (I welcome exact instructions on removing this from the rom.)
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Instructions for ATT locked phones:
If you can still get permanent root (pre 4.4.2 bootloader), then you can use safestrap to install this zip of ATT 4.4.4 and get root again.
Prerequisite:
Rootable Moto x (not temporary root)
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE.
Instructions:
root (thanks jcase)
install safestrap (thanks Hashcode and Team Win)
Make a nandroid and copy it off the phone!?
download zip to sdcard (motox-444-212.44.26.ghost_att-from-dump-ss.zip, link below)
extract boot.img to the fastboot directory of your PC
enter safestrap recovery (twrp) and activate the stock-slot
twrp: flash rom (motox-444-212.44.26.ghost_att-from-dump-ss.zip) to the stock-slot
twrp: reboot to bootloader (home -> reboot -> bootloader)
on pc: execute fastboot commands (below) then power on normally.
install supersu (thanks chainfire) from play store
Fastboot command to flash the kernel:
Code:
fastboot flash boot boot.img
Fastboot command for locked phones not using MotoWPNoMo with pre 4.4 bootloaders:
Code:
fastboot flash recovery boot.img
Thanks to touchpro247 for making the raw OTA available. Also thanks to iKrYpToNiTe for his safestrap selinux metadata code.
Download:
motox-444-212.44.26.ghost_att-from-dump-ss.zip: http://www.androidfilehost.com/?fid=23622183712458373
anyone try this one yet?
Installed this on my DE. Works perfectly. I actually have better reception. I'm on ATT btw.
Thanks a lot!
Sent from my XT1058 using XDA Free mobile app
bahhh now all I need is one from VZW
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
goonigoogoo said:
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
Click to expand...
Click to collapse
Because this came from my /system dump, it has safestrap there. I'm not sure of the easiest way to perfectly remove it, and I welcome input on the issue.
I'll update the op.
hey guys i have a 1053 rooted i am a noob sorry how can i get this to work for me
g4ess said:
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yep. Works well. I now have visual voicemail.
Sent from my XT1058 using XDA Free mobile app
can't get it to install how to u manually flash kernel
Sent from my XT1053 using XDA Free mobile app
Weapondrift said:
bahhh now all I need is one from VZW
Click to expand...
Click to collapse
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Has anyone seen if Faux's kernel will work? I'm waiting for my phone to charge before I flash. I'll report whether or not if no one else does.
Edit: So far, it's working great on my 1053 DE with Faux's latest kernel on AT&T.
nice
Thanks Ctrl-Freak for this. I appreciate you putting it together. I just upgraded from 4.4.2 to 4.4.4.
C:\>adb shell getprop ro.boot.write_protect
0
Click to expand...
Click to collapse
Sorry if this question is aggravating but if I flash this on my rooted XT1053 will it wipe my internal? Just trying to be sure, never flashed anything carrier specific. I flash and reboot right? Or do I also need the kernel? I read the OP but I'm wondering if I do all of that and or need safestrap.
Edit: I think I got it.
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
Click to expand...
Click to collapse
I should clarify. I had the old root from 4.2 that was on the phone when I purchased it. Updating to 4.4.4 was coming from 4.4.2 previously.
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely.
...
Click to expand...
Click to collapse
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
iSecks said:
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Click to expand...
Click to collapse
nope. That didn't do anything
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
beefgoat said:
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
Click to expand...
Click to collapse
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
You were quite right. I'm having battery issues (now) and my WiFi/Bluetooth won't turn on at all, even in safe mode. Was getting 52 hours consistently on battery, now I'm down to 36 hours tops! Phone started being 'awake' while the screen was off. I went back and flashed the boot, all good now. I'll report back on the battery issue. Thank you guys for setting me strait! :highfive:
Possible anyone knows how to disable the annoying OTA updates permanently? Remedied for now, being on 4.4.4, but I was trying to avoid 4.4.4 for now and the update notification that I couldn't kill, greenify, stop on boot, etc., is what drove me to this post. I'd love to turn these off and upgrade at my leisure in the future.
This is what I've been waiting for. Android OS is where it's supposed to be. Thank you Ctrl Freak for the upload.
OK, the pic didn't upload.
Related
Anyone know where I can find the AT&T Factory ROM i forgot to do a backup and need to put this ROM back on the device.
i can not find it.maybe few months later,you can get it here.
Is it weird that there's no RUU? It's been a while since I had an GTC phone so I don't remember how long it took to have one on a new phone.
gunnyman said:
Is it weird that there's no RUU? It's been a while since I had an GTC phone so I don't remember how long it took to have one on a new phone.
Click to expand...
Click to collapse
I feel like it is weird, though the One is the only device I got close to release. My Vivid and Inspire were both purchased a few months after release, and iirc the ATT RUUs were available when I got it, but I guess that doesn't mean they were available at release.
Wasuhz said:
Anyone know where I can find the AT&T Factory ROM i forgot to do a backup and need to put this ROM back on the device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Actually, this leads to a nagging question I have as a first time rooter. I want to use the stock ATT Rom, but root the phone so I can install apps than requre root access and am all about taking back total contole of my device.
SO If I want to keep the stock rom and just root it, I would need to back up the device?
So if someone could throw me a bone How would I gain root access to the device whilst keeping the stock ROM?
I plan on using Hasoon's Tool kit.
android_lurker said:
Actually, this leads to a nagging question I have as a first time rooter. I want to use the stock ATT Rom, but root the phone so I can install apps than requre root access and am all about taking back total contole of my device.
SO If I want to keep the stock rom and just root it, I would need to back up the device?
So if someone could throw me a bone How would I gain root access to the device whilst keeping the stock ROM?
I plan on using Hasoon's Tool kit.
Click to expand...
Click to collapse
flash the stock rom through recovery and then flash superuser.zip in recovery. boom. rooted on stock
If you are completely stock then Once you unlock your bootloader flash twrp recovery. Then boot to recovery. Then reboot from recovery. Twrp is smart enough to recognize you don't have root and prompt you to install superuser and binaries. After that I found a busybox flashable zip via google, as the busybox installer from the market wouldn't work for me. This leaves you on a stock odexed Rom with root. Note that unlocking your bootloader will wipe data..so backup anything important first
Sent from my HTC One using Tapatalk 2
sk8erwitskil said:
flash the stock rom through recovery and then flash superuser.zip in recovery. boom. rooted on stock
Click to expand...
Click to collapse
oh hell yes thank you for the assistance.
so I will flash the stock rom instead of say CWM then flash supersu after that? Where do I like "get" the stock rom from? will it already be on the sd card?
Delete me..
grukko said:
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
Hi i just want to know how do you flash the stock odex?
BADBOY1412 said:
Hi i just want to know how do you flash the stock odex?
Click to expand...
Click to collapse
i just used twrp. after that i flashed the stock recovery back using fastboot.
grukko said:
i just used twrp. after that i flashed the stock recovery back using fastboot.
Click to expand...
Click to collapse
If you're talking about the ATT stock recovery, Can you please post it....I been looking for that
android_lurker said:
oh hell yes thank you for the assistance.
so I will flash the stock rom instead of say CWM then flash supersu after that? Where do I like "get" the stock rom from? will it already be on the sd card?
Click to expand...
Click to collapse
1) unlock bootloader
2) fastboot flash cwm (you can use the shiny new one i just posted in the orig dev section )
3) boot to recovery and make a backup
4) flash the pre-rooted stock rom here http://forum.xda-developers.com/showthread.php?t=2242319
5) reboot and enjoy
grukko said:
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
did the international stock recovery work for you ? i was able to flash it but when i try to go into recovery its just black screen no recovery. Your reply appreciated
Thanks
If you flash stock recovery successfully and you try to boot to said recovery, you won't have any options to do anything. I never cared to look at it on this device but usually all you'll see is a triangle with an exclamation point. That's stock recovery. If you want to flash anything, you can't use stock
Sent from my HTC One using Tapatalk 2
Not sure what's up but I have been searching all over the work pc's for a HTC one ruu with no damn luck even talked to a few buddies in tech support and they have not seen one as of yet
Sent from my HTC One using Tapatalk 2
homeslice976 said:
If you flash stock recovery successfully and you try to boot to said recovery, you won't have any options to do anything. I never cared to look at it on this device but usually all you'll see is a triangle with an exclamation point. That's stock recovery. If you want to flash anything, you can't use stock
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
cool , i was confused because i have only used samsung phones before and their stock recovery has some menu options to do factory reset etc.
Stock recovery has a menu, just press volume up.
grukko said:
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
I don't think anyone's still following this thread, but did you relock the bootloader before returning it? i was thinking of just flashing recovery back. I don't think anyone at the store would bother to look at that anyway. Whenever I go there, the employees seem to know less than nothing about phones lol.
I've just received my OTA KitKat 4.4 update on my HTC One, but it won't successfully install. i tap "install now" on my phone, the phone reboots and goes into TWRP recovery. i found the zip file, flashed it with TWRP, and it seems to have unpacked it because i now have a file with the same name as the KitKat 4.4 update zip file that contains a "META-INF" file and a "patch" file, but when i reboot system, i'm still running Android 4.3 with Sense 5.0 according to Settings>About>Software information. what is going on? am i doing something wrong? do i need to relock my bootloader? uninstall TWRP? if i do need to uninstall TWRP, then how? i don't even see it listed under Settings>Apps. i was really looking forward to running KitKat and i've been trying to update to it all night, so much so that my wife is now mad at me for spending so much time "playing" with my phone! if anyone can help me, i would greatly appreciate it. i'm a newb when it comes to TWRP, but i've had an HTC Tilt, Tilt 2, and a Vivid, all unlocked, rooted, and with custom roms. i was even trying to learn to cook my own roms for my Vivid, so i know (basically) what i'm doing, but i am familiar with using the "install from internal SD card" option in recovery, which i don't even have anymore. now when i enter my bootloader, scroll to "recovery" and select it, my phone boots up into TWRP recovery, which i'm not liking thus far. seems like more of a pain than the simple "install from internal SD" process that i'm familiar with. i'd much prefer to use the process i'm familiar with than TWRP if that is possible. if anyone can help me with any of these issues, PLEASE PLEASE PLEASE do so. reply to this post, pm me, or email me. doesn't make any difference to me. i'll take any help or advice i can get at this point!
Chris
HTC One
and if you need any of the following info...
Android 4.3, Sense 5.0
Software Number: 3.22.1540.1
Kernal Version: 3.4.10-g9579b75
[email protected]#1
SMP PREEMPT
Build Number: 3.22.1540.1 CL252721 release-keys
Baseband Version: 4A.17.3250.20_10.40.1150.04L
You have to install the stock recovery to take an OTA Update
check my post here http://forum.xda-developers.com/showpost.php?p=47992226&postcount=469
you can pull the stock recovery from the guru reset I posted above and just flash it
4.4 for at&t update hasnt been released as far as i know i have a at&t htc one and no update
Sent from my HTC One using XDA Premium 4 mobile app
tat2messiah said:
4.4 for at&t update hasnt been released as far as i know i have a at&t htc one and no update
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
he's on developer edition
Oh gottcha
Sent from my HTC One using XDA Premium 4 mobile app
clsA said:
You have to install the stock recovery to take an OTA Update
check my post here http://forum.xda-developers.com/showpost.php?p=47992226&postcount=469
you can pull the stock recovery from the guru reset I posted above and just flash it
Click to expand...
Click to collapse
How do I pull it? I take it your talking about extracting it from the zip file, right? If not, then how do I "pull" it? If so, what do I do after that? Just flash it with twrp? Also, does the "volume up + power" procedure get you to the "install from internal sd card" option? Sorry for all the questions, but it seems that a lot has changed since I got my Vivid & used to flash a new ROM every few days. I finally flashed HoliRaider Final Version by bananacakes & liked it so much that I used it for the next 2 1/2 years. It looks like a lot of stuff has changed since then. By the way, I actually have the zip file for the update. I copied it to my PC before I finally decided to select "do not install" & started looking for help. Thanks!
Chris Sifford
Arlington, TX
want the zip update?
I have the zip file saved on both my phone & my PC. Never know when it might come in handy.
clsifford said:
I have the zip file saved on both my phone & my PC. Never know when it might come in handy.
Click to expand...
Click to collapse
yeah you just remove recovery.img from the Guru reset and flash it
are you sure your phone is unchanged from stock otherwise ?
to flash the stock recovery it's done from fastboot and command window
extract the stock recovery to your fastboot folder then the command
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
after this is when you can boot to stock recovery (the one with the red triangle)
and then you can flash the ota.zip you downloaded
just keep referring to my other post for the correct steps to take
clsA said:
yeah you just remove recovery.img from the Guru reset and flash it
are you sure your phone is unchanged from stock otherwise ?
to flash the stock recovery it's done from fastboot and command window
extract the stock recovery to your fastboot folder then the command
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
after this is when you can boot to stock recovery (the one with the red triangle)
and then you can flash the ota.zip you downloaded
just keep referring to my other post for the correct steps to take
Click to expand...
Click to collapse
I had flashed a Viper Rom, but I didn't like it. Flashed Android Revolution, but still wasn't satisfied, so I went back to a stock rom. But I did flash it from twrp, so it may not actually be stock. come to think of it, I haven't seen the red triangle since I've been running this Rom, so it most likely isn't stock (i assume). Right?
As far as the "up volume + power" goes, do I do that INSTEAD of "down volume + power" or do it on the red triangle screen? Sorry, I just want to have all my ducks in a row this time.
clsifford said:
I had flashed a Viper Rom, but I didn't like it. Flashed Android Revolution, but still wasn't satisfied, so I went back to a stock rom. But I did flash it from twrp, so it may not actually be stock. come to think of it, I haven't seen the red triangle since I've been running this Rom, so it most likely isn't stock (i assume). Right?
As far as the "up volume + power" goes, do I do that INSTEAD of "down volume + power" or do it on the red triangle screen? Sorry, I just want to have all my ducks in a row this time.
Click to expand...
Click to collapse
fastboot reboot-bootloader will get you to the bootloader the same as power+volume down
after the stock recovery is installed from the bootloader you choose recovery you'll see the red triangle screen (after a few seconds) this is where you do the power+volume up to see the flash options
choose install from phone storage
click 0 then find the OTA file you downloaded and install it.
If your phone is not Stock it will FAIL, if that's the case you need to start from scratch by running the guru reset and following the instructions I already gave you. So you know I did the total reset and was on kitkat in about 20 min it's not that hard just follow the mini tutorial and don't skip any steps
tat2messiah said:
4.4 for at&t update hasnt been released as far as i know i have a at&t htc one and no update
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for the delayed response. Spent the last couple of days trying to figure out what I was doing wrong in learning to sideload a ROM. Anyway, yeah, I received the OTA update for4.4 KitKat. Finally succeeded in flashing a stock 4.3 Jelly Bean ROM, received the OTA 4.4 update, and am now running KitKat! Thanks to everyone for all of your help! I was starting to think I bricked my phone.
Well i used to have a hox+ with Android Revolution custom rom and a custom kernel. I tried to power it up but it stucks at htc logo,then reboots and goes straight to twrp recovery. I tried to flash again the rom via adb but i can't see my device in cmd. I found and dowloaed htc drivers my htc,plus adk and htc sync manager but still no luck..any ideas what is going on here?
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
i360droid said:
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
Click to expand...
Click to collapse
fastboot is not recognised etc...........any ideas?
smavr said:
fastboot is not recognised etc...........any ideas?
Click to expand...
Click to collapse
ok, add me on skype, i360faceplant, i will walk you through it step by step
i360droid said:
ok, add me on skype, i360faceplant, i will walk you through it step by step
Click to expand...
Click to collapse
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
smavr said:
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
Click to expand...
Click to collapse
what was up with it?
i360droid said:
what was up with it?
Click to expand...
Click to collapse
Well, i just made a mistake at adb sideload...
smavr said:
Well, i just made a mistake at adb sideload...
Click to expand...
Click to collapse
lol
i360droid said:
lol
Click to expand...
Click to collapse
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
ahighfield said:
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Click to expand...
Click to collapse
to get into bootloader, hold down the vol down and power, the home lights will flash (atleast they do when its booting), it will reboot, when you get the htc logo, let go of power button. and now try a stable er version of the rom.
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
ahighfield said:
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
Click to expand...
Click to collapse
ok, dont do an ota update in cm, you need s-off, which you cant get on the hox+
flash the rom, flash the boot image, boot, reboot into recovery, SIDELOAD gapps and that should work. use cm10 for the moment, as cm11 has an annoying system ui crash loop bug.
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
ahighfield said:
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The phone will boot loop, as the kernal is different to the rom
**You can begin the following process from any 4.4.x Build/ROM or higher, but you must already have Root Access. Safestrap Users must flash from "Stock" Slot Only**
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
**Caution!** The following process is only for the Verizon I545 S4 Variant. Use on any other device may result in a hardbrick!
***FlashFire v19 Recommended***
Downloads:
- I545_OC1_Stock_Rooted_ROM_wNK4_BL
- I545_OC1_Stock_DeOdexed_ROMwNK4_BL
Attention! Set your screen timeout to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and use default "Reboot" setting.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the Verizon splash screen for about 2 - 3 minutes (10 - 15 mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
- When reporting an issue please always include your starting firmware, FF version, and relevant details.
Optional:
- I545_OC1_TetherAddOn (Flash using FlashFire's "Flash zip or ota" option).
- I545_OC1_Batch_Debloater (Customizable)
Notes:
1. FlashFire has a bug which sometimes causes a premature reboot during the flash resulting in getting stuck on the Samsung boot screen. To avoid this press the Volume Key every few seconds during the flash. Seeing "Rebooting....." at the end of the flash usually indicates a successful flash.
2. The above process will not affect your Knox Warranty Flag.
3. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery to OC1 and your Bootloader to NK4 (the NK4 bootloader allows for downgrading your firmware to NC5).
4. Safestrap will no longer function after updating to OC1.
5. If you do not already have root access (or to unbrick) flash the Full Wipe NC5 Odin .tar (Caution!: do not flash if you took the OC1 ota update), root with Towelroot, then proceed with the above process.
6. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@dgutierrez04 - for capturing both the NK4 and OC1 ota updates.
Reserved
Muniz_ri i finally got around to it. I flashed it and everything booted up fine. Right now i am running lollipop and no crashes yet. The only bug i found is the WIFI. if you depend on wifi a lot do not update it yet. it seems to be broken. but everything else seems to work. Also the playstore doesn't seem to want to download apps. but how it says FOLLOW INSTRUCTIONS. if you need to read it 5 times do it. But once again nice Job Muniz_ri.
Update I figured how to fix the playstore. U need to wipe data from the playstore app for it to work. If u can't download any apps. So is back to just the wifi issue.
thanks @muniz_ri
everything works fine with me except WIFI.
is there any way to fix WIFI issue?
Update: Works great, WIFI is working now
This was a fast process but I'm also having wifi problems. It's like the phone doesn't see the antenna. Thanks for the work so far!
Worked simply and well, except for WiFi. Thanks
jr4594 said:
This was a fast process but I'm also having wifi problems. It's like the phone doesn't see the antenna. Thanks for the work so far!
Click to expand...
Click to collapse
It's the 4.4.2 bootloader on the 5.0 system. I will see what can be done.
Let's first make certain that the ROM updated the modem/non-hlos correctly. Someone that flashed the ROM please flash the following using Odin: I545_OC1_Stock_Modem.tar.md5
muniz_ri said:
It's the 4.4.2 bootloader on the 5.0 system. I will see what can be done.
Let's first make certain that the ROM updated the modem/non-hlos correctly. Someone that flashed the ROM please flash the following using Odin: I545_OC1_Stock_Modem.tar.md5
Click to expand...
Click to collapse
U flash it where on Odin in the AP box?
dgutierrez04 said:
U flash it where on Odin in the AP box?
Click to expand...
Click to collapse
Correct
muniz_ri said:
Correct
Click to expand...
Click to collapse
After flashing the tar the problem still persist.
DELETE
jgkim said:
wifi fix - custom recovery install Hulk-Kernel TW5
http://forum.xda-developers.com/gal...ernel-hulk-kernel-v1-stweaks-based-t3050469#2
Click to expand...
Click to collapse
No, you can't flash custom recovery or kernels on a locked bootloader device.
DELETE
jgkim said:
Install Step
In 4.4 kitkat unlock custom recovery(CWM, TWRP)
install i9505 stock lollipop rom (Albe95 , Kushan, Omega, ETC)
wipe data/factory reset
install I545_OC1_Stock_Rooted_ROM_wNK4_BL_MOD zip (only boot.img and system.img.ext4)
wifi fix - Hulk-Kernel TW 5 install(i9505 wifi fix tw 5 kernel )
Click to expand...
Click to collapse
The Verizon variant of the S4 has a locked bootloader... Since the bootloader is locked, no way to install custom recovery.
jgkim said:
Install Step
In 4.4 kitkat unlock custom recovery(CWM, TWRP)
install i9505 stock lollipop rom (Albe95 , Kushan, Omega, ETC)
wipe data/factory reset
install I545_OC1_Stock_Rooted_ROM_wNK4_BL_MOD zip (only boot.img and system.img.ext4)
wifi fix - Hulk-Kernel TW 5 install(i9505 wifi fix tw 5 kernel )
Click to expand...
Click to collapse
While this may work on your device, it will not work for this one. Verizon locks down theirs by locking their bootloaders. The international version (i9505) AFAIK does not have this problem. As stated above, you can not flash kernels on a device with a locked bootloader.
I'm new to the whole android flashing. So sorry for the noob questions.
Noob Question #1
Will this wipe my phone? If I do have to wipe it I don't mind. It's just going to be a pain to get it up and working again.
Noob Question #2
Added a picture of my About Phone. Will my phone work?
Sorry for the noob questions. But I have to start somewhere.
Sent from my SCH-I545 using XDA Free mobile app
yellowcooln said:
I'm new to the whole android flashing. So sorry for the noob questions.
Noob Question #1
Will this wipe my phone? If I do have to wipe it I don't mind. It's just going to be a pain to get it up and working again.
Noob Question #2
Added a picture of my About Phone. Will my phone work?
Sorry for the noob questions. But I have to start somewhere.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
This ROM is still in testing. Stongly suggest Noobs do not flash at this time.
This is great hopefully the WiFi issue gets solved soon
Sent from my SCH-I545 using XDA Free mobile app
Delete
I rooted my phone. I do know what I am doing. I'm just worried that I will need to reinstall everything.
Sent from my SCH-I545 using XDA Free mobile app
OTA zip (Qualcomm) retail 3.3.2018 "Blur_Version.26.11.27.owens.retail.en.US"
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
Thanks, @Chad The Pathfinder. Good to see you here.
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
shezzy83 said:
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
Click to expand...
Click to collapse
It is for the retail XT1775 only. It's an official OTA update.
---------- Post added at 06:21 PM ---------- Previous post was at 05:40 PM ----------
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
I can probably make this work to flash with TWRP, but you'll need to have your system, oem and boot.img original stock before flashing. If anyone is willing to test it for me, I will modify the ota zip when I have a chance. I have the Boost XT1766 so I can't test it myself. Let me know if anyone is willing to test it because if not, I won't waste my time modifying the ota.
Sent from my Moto E (4) Plus using XDA Labs
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Chad The Pathfinder said:
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Click to expand...
Click to collapse
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Chad The Pathfinder said:
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Click to expand...
Click to collapse
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Chad The Pathfinder said:
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Click to expand...
Click to collapse
I'm uploading the ROM now. I just got done modifying the ota zip and I'll give you links as soon as they're done uploading. I made a deodexed Sprint variant version. Was planning on deodexing the retail version also. I may as well wait for the newer version though. The trick is, you need to deodexed the oem apps and framework also or it won't boot.
Sent from my Moto E (4) Plus using XDA Labs
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Chad The Pathfinder said:
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Click to expand...
Click to collapse
Yes. It'll be a little while, uploads are going really slow and keep failing on AFH. I had it almost uploaded twice and it keeps failing.
Sent from my Moto E (4) Plus using XDA Labs
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
I have been having issues uploading to AFH too. Man, I wish they would finally get this fixed.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
Finally got it
ROM: https://www.androidfilehost.com/?fid=746010030569959248
OTA:
So, here's what I want you to do.
1. Make a backup before you do anything.
2. Flash a Magisk uninstaller.
3. Flash the ROM. (if it should fail to flash, please get a recovery log so I can see exactly what failed.)
4. Flash the OTA zip. (again, if it should fail to flash, please get a recovery log so I can see exactly what failed.)
5. If everything flashes ok, reboot recovery to make sure you don't lose twrp.
6. Make a system backup.
7. Use fastboot to pull the boot.img, modem.img, fsg.mbn, and the oem.img.
Edit: actually, if you could pull everything you see in a stock firmware package and pull them so they have the same name and file extension, that would be great.
I'll be working until about 8 tonight. (3.5.18) I'll work on it tonight and let you know what happens.
Edit: I managed to get the "Blur_Version.26.11.27.owens.retail.en.US--XT1775_TWRP_flashable" down loaded but the other was taking too long and failed a couple of times. I will try again when I can.
so glad you guys are working on this My daughter and her moms xt1775 just popped the update message and im not "allowed" to work on them too often so i cant experiment with you. So a twrp flashable update would be great if i dont have to unroot reroot stock.img etc etc it will be a painless (for me) update.
A Sort-of Related Question
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
koop1955 said:
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
Click to expand...
Click to collapse
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Of course, sent to you via PM.
I don't think that it is a quality of your zip, I think it is related to my earlier attempt at installing the OTA itself.