Edit: The official ATT 4.4.2 sbf has been released, and this rom was built from that.
This CWM/TWRP flashable zip is from the sbf of 165.44.1.ghost_att.ATT.en.US (ATT xt1058). The modem and kernel are within the zip and must be flashed manually. The instructions below are mostly for rooted, locked ATT phones using safestrap.
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Unlocked phones: You can flash the zip and manually flash boot.img, NON-HLOS.bin and fsg.mbn.
ATT locked phones:
If you can still get root, then you can use safestrap to install this zip of ATT 4.4.2 /system and get root again. Also within the zip is the official ATT 4.4.2 boot.img, NON-HLOS.bin and fsg.mbn (for fastboot). This zip does not alter your bootloader.
Prerequisite:
Rooted Moto x
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA..
Safestrap 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-442-165.44.1.ghost_att-ss.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
extract boot.img, NON-HLOS.bin and fsg.mbn from the .zip to the fastboot directory of your PC
enter safestrap recovery (twrp) and activate the stock-slot
twrp: wipe/factory reset (WARNING. THIS WILL WIPE YOUR USERDATA. This step may be optional for some users.)
twrp: flash rom (motox-442-165.44.1.ghost_att-ss.zip) to the stock-slot (be patient)
twrp: immediately flash supersu .zip
twrp: reboot to bootloader (home -> reboot -> bootloader)
on pc: execute fastboot commands (below).
Fastboot commands: Note: If you use MotoWPNoMo, then you should skip "flash recovery"
Code:
fastboot flash boot boot.img
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
Downloads:
motox-442-165.44.1.ghost_att-ss.zip: http://www.androidfilehost.com/?fid=23329332407589378
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
If you hang up during flashing the rom, I had success by flashing supersu first. Then it worked like a charm. Very helpful for me!
Sent from my XT1058 using Tapatalk
I was coming from 4.2.2 and flashing this without updating the modem to at least 4.4 will cause problems:
1. Security setting cannot be opened
2. User apps cannot be uninstalled
Updating my modem to 4.4 resolves both problem.
The sbf was released, and I made a new CWM/TWPR flashable zip using the sbf. The new zip contains the official 4.4.2 modem in addition to the kernel.
I tested the new zip on my phone, and the link is in the op.
Coming from 4.4 rooted I installed safestrap and followed these instructions. I had errors reported back with the following commands:
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
but the phone is now on 4.4.2
rmead01 said:
Coming from 4.4 rooted I installed safestrap and followed these instructions. I had errors reported back with the following commands:
fastboot flash recovery boot.img
fastboot flash modem NON-HLOS.bin
but the phone is now on 4.4.2
Click to expand...
Click to collapse
What error did you get?
What kernel version are you running? Still running the 4.4 version?
I think the files are right. I just successfully compared those files in the zip against other copies, and they are the same copies working on my phone.
Ctrl-Freak said:
What error did you get?
What kernel version are you running? Still running the 4.4 version?
I think the files are right. I just successfully compared those files in the zip against other copies, and they are the same copies working on my phone.
Click to expand...
Click to collapse
kernel version reads "3.4.42-g27de6975 build from 2/24/14
the flash boot boot.img command went through no problem. It was just the recovery command that failed.
flash recovery boot.img - variable not supported preflash validation failed (remote failure)
trying the modem a second time it went through and I again flashed the fsg.mbn and erased the modemst1/2 and did a cache erase
rmead01 said:
kernel version reads "3.4.42-g27de6975 build from 2/24/14
the flash boot boot.img command went through no problem. It was just the recovery command that failed.
flash recovery boot.img - variable not supported preflash validation failed (remote failure)
trying the modem a second time it went through and I again flashed the fsg.mbn and erased the modemst1/2 and did a cache erase
Click to expand...
Click to collapse
Strange. I double checked it:
Code:
fastboot flash recovery boot.img
sending 'recovery' (10240 KB)...
OKAY [ 0.810s]
writing 'recovery'...
OKAY [ 1.713s]
finished. total time: 2.523s
You don't have the 4.4.2 bootoader do you? (Doesn't make sense that you would be doing this if you already had 4.4.2 + root.)
The kernel version is right.
Ctrl-Freak said:
Strange. I double checked it:
Code:
fastboot flash recovery boot.img
sending 'recovery' (10240 KB)...
OKAY [ 0.810s]
writing 'recovery'...
OKAY [ 1.713s]
finished. total time: 2.523s
You don't have the 4.4.2 bootoader do you? (Doesn't make sense that you would be doing this if you already had 4.4.2 + root.)
The kernel version is right.
Click to expand...
Click to collapse
Not sure. Bootloader version 30.B2
I had 4.4 rooted and downloaded the files in your post. Was I suppose to remove the the 3 files from the zip or just copy them out? I extracted them but left the 3 files also in the zip file. I copied the zip file to my sdcard. installed safestrap. made a nandroid. flash the zip, flashed the SU, followed the fastboot commands and that's what I got.
---------- Post added at 10:41 AM ---------- Previous post was at 10:26 AM ----------
Here's my input though. I'm on 4.4.2. I'm rooted. I have the 4.4.2 kernel version. My phone actually feels much snappier. Not sure if that's from the cache clear or not but it's extremely noticable how much smoother it is. I have safestrap installed and can reboot to it. All in all i'd call this a success
I think I get it. You are on the 4.4 bootloader which stops the recovery trick. But.. you've used MotoWPNoMo so the recovery is not necessary.
Sound right?
Glad it is working.
I'm new to using safestrap but having looked around I understand some of the basics of what I need to know.
however I may have misunderstood the safestrap instructions: is it necessary to install the rom in the stock slot? or can we install to another slot in order to preserve the stock slot for 'safety'
Ctrl-Freak said:
I think I get it. You are on the 4.4 bootloader which stops the recovery trick. But.. you've used MotoWPNoMo so the recovery is not necessary.
Sound right?
Glad it is working.
Click to expand...
Click to collapse
Exactly it! :good:
frenchie007 said:
I'm new to using safestrap but having looked around I understand some of the basics of what I need to know.
however I may have misunderstood the safestrap instructions: is it necessary to install the rom in the stock slot? or can we install to another slot in order to preserve the stock slot for 'safety'
Click to expand...
Click to collapse
Kitkat 4.4 does not work in a rom slot. I am guessing 4.4.2 is the same.
If you are running the 4.4 bootloader and MotoWPNoMo, you do not need to flash recovery. If you do try to flash recovery, just ignore the error.
I made a note in the op. Thanks rmead01.
Is this the AT&T equivalent of this: http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/?
natezire71 said:
Is this the AT&T equivalent of this: http://rootzwiki.com/topic/116025-romsafestrap-unlockedxt1060-stock-rooted-vzw-164552-kitkat-442/?
Click to expand...
Click to collapse
Yes
I was running Android 4.4 already when doing this process. I skipped the step of wiping user data and followed the steps exactly. (I flashed SuperSU FIRST, then the ROM, then SuperSU again before rebooting to the bootloader. Maybe was unnecessary but wanted to be sure it got in there). I had no issues at all and when the bootloader commands were done I pressed the power to select reboot in the bootloader. Phone rebooted, optimized 327 apps, and I'm done. 4.4.2 running great with root and no loss of any data.
Major thumbs up for posting this!! Thank you and god bless XDA-developers!! This forum is invaluable!!!!
Oh I am on a locked bootloader by the way. AT&T locked but safestrap worked great.
Apollo_316 said:
... (I flashed SuperSU FIRST, then the ROM, then SuperSU again before rebooting to the bootloader. Maybe was unnecessary but wanted to be sure it got in there)...
Click to expand...
Click to collapse
I do not think flashing supersu first is helpful. When you flash the ROM, it erases /system, and all of the su binaries would be erased.
Ctrl-Freak said:
I do not think flashing supersu first is helpful. When you flash the ROM, it erases /system, and all of the su binaries would be erased.
Click to expand...
Click to collapse
I figured it was pointless but a previous poster in this thread said they did that too and my bottom line was ensuring I don't lose root above all else. Thanks for pointing that out though. I remember it was formatting /system for a while and I wondered about superSU being in there but wasn't sure what was going to happen.
I'm on rooted 4.4, AT&T locked bootloader, write protection off.
If I install this via safestrap, after this is installed and I'm on 4.4.2 rooted with write protection off, can I then remove safestrap while maintaining my rooted, write protect off, 4.4.2 update?
Sent from my XT1058 using XDA Premium 4 mobile app
Related
As I was using CM 4.4.2, everything was going fine, I had 3 bars of LTE, and then I tried to make a call and it said mobile networks not available, I checked my signal in the status bar and it still said LTE and data still worked fine. I went to my phone settings and checked it and it said my mobile network was unknown, and my phone number was 000-000-0000. I wiped, and flashed CM10.2(4.3) and it did the exact same thing, only this time it said my phone number, but still, I couldn't make any calls or text, I've tried flashing two sense 5 roms and none of them display my phone number or let me call or text, but upon changing the subscription type from global to LTE/CDMA, it gives me LTE data, but that's it...Can anyone please help me?
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
rejectedjs said:
So basically follow this guide? http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
santod040 said:
No, I was never implying to relock or return to s-on.
Flash my rooted stock odexed Rom and a stock recovery and do a factory reset.
Follow my guide above....
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
rejectedjs said:
Alright...I know I'm being annoying, but I want to thank you for helping anyway. Where do I find a stock recovery and how do I flash it?
Click to expand...
Click to collapse
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
rejectedjs said:
It worked! Thanks so much dude, this problem has been bugging me since I was in school earlier today, and you helped me out within minutes, I wish I could press the thanks button multiple times.
Click to expand...
Click to collapse
No problem bud.
Glad that worked out for you.
Same process always fixes 3g/4g issues after flashing many roms for me, on all of my devices.
:good:
This exact thing happened to me a few weeks ago. Busted my ass trying to fix it, after a few days of no service i finally got it.
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
The way you fixed it seems a lot easier than what I did. I returned to s-on, 1.15 hboot and the oldest firmware. Now my phone's bootloader will always say tampered too, since i had to HTC dev unlock it to get root.
santod040 said:
Stock DNA Recovery Image
To flash the Recovery:
Place the file in your fastboot/adb directory on your computer.
Put the device in fastboot mode:
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
The image is easily installed via an unlocked bootloader with the following command:
Code:
fastboot flash recovery imagename.img
For example, I provided a recovery img named dnastockrecovery.img
So you would type:
Code:
fastboot flash recovery dnastockrecovery.img
The image must be in your fastboot working directory.
Or you can use Flashify from the Play Store.
I recommend getting used to and familiar with doing it via fastboot though.
Click to expand...
Click to collapse
:good: Can't thank you enough.
I have a second DNA that I have not been able to use.
Since Moonshine S-off I have not had any data connection. It has been very frustrating.
Followed your steps and now it's back up and running.
Awesome my friend, just awesome. Thank you.
quick question
santod040 said:
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash stock recovery.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
LuckyPuppy said:
Regarding the instructions you listed above, are these run from the phone or adb/fastboot? Going to perform this after work tonight and just wanted to be sure. Thank you!
Click to expand...
Click to collapse
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
how to
sdamark said:
Flash stock based Rom --- Done from Recovery
Flash stock recovery --- Done from Fastboot
Perform a factory reset --- Done from Bootloader
:good:
Click to expand...
Click to collapse
Awesome! Thank you so much!
Where is there a stock rom
thayl0 said:
Where is there a stock rom
Click to expand...
Click to collapse
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
sdamark said:
> HTC Droid DNA > Droid DNA Android Development > [ROM] OTA-DNA-Sence 5-3.06.605.4 Stock Deodexed Debloated Rooted
This one will work fine. It's the one I used. Stock based ROM.
Click to expand...
Click to collapse
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
thayl0 said:
I figured that out after i commented.
when u go to flash your custom rom back to you need to do a dirty clean or can it be a clean flash by wiping cache system sdcard everything.
Click to expand...
Click to collapse
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
sdamark said:
You'll have to install a custom recovery first. I use TWRP. Install your custom ROM onto the sd card. Boot into recovery, make a nandroid, wipe in recovery> Data, Cache, and Dalvic, then install your ROM and reboot.
Click to expand...
Click to collapse
why would i do a dirty install?
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
uNdea said:
Have same issue, lost signal..
Flashed stock 3.06, but can't flash stock recovery.. every time i try to flash, it Fails
(sending 'recovery' (8188 KB).
OKAY [ 0.938s]
writing 'recovery'...
FAILED (remote: not allowed)
Same when i try to install other version of TWRP (have 2.5.0.0 installed) or CWM.
phone is not unlocked by htcdev, but i have s-off. (Can't unlock at htcdev through, getting error 160 every time)
Any help would be greatly appreciated
Click to expand...
Click to collapse
You do know flashing 3.06 ruu makes it stock recovery. Not sure of you flashed a Rom or a ruu
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Edit: I have also uploaded a Guru_Reset of this if anyone is interested (Thanks to @crushalot)
Download it Here
for instructions look here >> http://forum.xda-developers.com/showthread.php?t=2358738
WARNING!!! include optional flashable radio.
..here is the Stock Nandroid before the phone was rooted
http://www.androidfilehost.com/?fid=23501681358543596
MD5: b01ad6da065b19c7aff36f77724a5b74
Extract zip, copy 'HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted' folder to /sdcard/TWRP/BACKUPS//HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery
It's also recommended to Factory Reset in TWRP after Restoring the Firmware
http://www.androidfilehost.com/?fid=23501681358543599
MD5: 1a8b1482d4525488c89335df07dc24f2
reboot into fastboot USB
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot
Be Very Careful with the firmware posted below, I actually put my HTC One into QHSUSB_DLOAD Flashing this. I was able to fix it (Thanks to dexter93) but be very careful and do not flash a 3.xx.502.x firmware with the one posted below !!
http://forum.xda-developers.com/showthread.php?t=2770684
This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA, or manually, you most likely have a device stuck in QHSUSB_DLOAD. This tool is for you
Click to expand...
Click to collapse
For Completeness here's the 5.12.502.2.firmware.zip
http://www.androidfilehost.com/?fid=23501681358543602
MD5: 4d671edd6bcf1876c44c3798aaaebb0c
Flash with fastboot oem rebootRUU
fastboot oem rebootRUU
fastboot flash zip 5.12.502.2.firmware.zip
fastboot flash zip 5.12.502.2.firmware.zip
Greetings,
Please stay on topic.
Thanks,
BD619
Hey, quick question:
do I need S-Off for this to work?
kml.krk said:
Hey, quick question:
do I need S-Off for this to work?
Click to expand...
Click to collapse
no, I don't think so
A little help. I have S-Off, Unlocked bootloader, and am rooted. The only mods to my stock rom are rooting and a tweak to enable wifi hotspot. Will your instructions still work to update my phone to latest firmware? Do I have to unroot first and relock my bootloader?
clsA said:
As the title says ..this is the Stock Nandroid before the phone was rooted
Edit: I have also uploaded a Guru_Reset (Thanks to @crushalot) of this if anyone is interested just shoot me a PM
http://www.androidfilehost.com/?fid=23501681358543596
MD5: b01ad6da065b19c7aff36f77724a5b74
Extract zip, copy 'HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted' folder to /sdcard/TWRP/BACKUPS/<serialnum>/HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery
http://www.androidfilehost.com/?fid=23501681358543599
MD5: 1a8b1482d4525488c89335df07dc24f2
reboot into fastboot USB
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot
Be Very Careful with the firmware posted below, I actually put my HTC One into QHSUSB_DLOAD Flashing this. I was able to fix it (Thanks to dexter93) but be very careful and do not flash a 3.xx.502.x firmware with the one posted below !!
http://forum.xda-developers.com/showthread.php?t=2770684
For Completeness here's the 5.12.502.2.firmware.zip
http://www.androidfilehost.com/?fid=23501681358543602
MD5: 4d671edd6bcf1876c44c3798aaaebb0c
Flash with fastboot oem rebootRUU
fastboot oem rebootRUU
fastboot flash zip 5.12.502.2.firmware.zip
fastboot flash zip 5.12.502.2.firmware.zip << Yes Two times (First time updates hboot)
fastboot reboot
Click to expand...
Click to collapse
Worked nicely, thanks.
Edit: Also, it's very very very recommended to Factory Reset in TWRP after Restoring the Firmware. If not done right after Restore, the device may malfunction in some areas, and may (very little) lead to Bricking. I have done this before, when flashing the USA Firmware Version of HTC One's Sense 6. Had to return to Stock due to some recent news in my Data, not connecting to the AT&T Towers, and other stuff. That being said, I've done the old fastboot oem lock and relocked my bootloader, and never again will I ever flash a ROM or anything on my device. Thanks again.
Code:
C:\Program Files (x86)\Android\sdk\platform-tools>fastboot flash recovery 5.12.5
02.2.recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12426 KB)...
OKAY [ 1.482s]
writing 'recovery'...
OKAY [ 0.891s]
finished. total time: 2.373s
C:\Program Files (x86)\Android\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.034s
SMaximus7 said:
A little help. I have S-Off, Unlocked bootloader, and am rooted. The only mods to my stock rom are rooting and a tweak to enable wifi hotspot. Will your instructions still work to update my phone to latest firmware? Do I have to unroot first and relock my bootloader?
Click to expand...
Click to collapse
I don't know what firmware your on now
it's critical you don't try and skip a version
you have to go 3.xx -->> 4.xx ->> 5.xx
3.xx ->> 5.xx can send you into the QHSUSB_DLOAD Brick
Be careful
clsA said:
I don't know what firmware your on now
it's critical you don't try and skip a version
you have to go 3.xx -->> 4.xx ->> 5.xx
3.xx ->> 5.xx can send you into the QHSUSB_DLOAD Brick
Be careful
Click to expand...
Click to collapse
Sorry I should have mentioned I'm on 4.18.502.7. So I guess the question would be, is it ok to flash this over what I have, or should I install the 4.18.502.7 RUU first to take me to complete stock and then flash this?
Also, can someone point me in the direction of a 4.18.502.7 stock recovery?
Thanks for the help.
SMaximus7 said:
Sorry I should have mentioned I'm on 4.18.502.7. So I guess the question would be, is it ok to flash this over what I have, or should I install the 4.18.502.7 RUU first to take me to complete stock and then flash this?
Also, can someone point me in the direction of a 4.18.502.7 stock recovery?
Thanks for the help.
Click to expand...
Click to collapse
Here you go
https://www.dropbox.com/s/u1ldcszwq5fc0f0/4.18.502.7 stock_recovery.img
clsA said:
Here you go
https://www.dropbox.com/s/u1ldcszwq5fc0f0/4.18.502.7 stock_recovery.img
Click to expand...
Click to collapse
im in the same boat... do i flash this from TWRP or from stock boot loader?
ubnjacked said:
im in the same boat... do i flash this from TWRP or from stock boot loader?
Click to expand...
Click to collapse
what are you trying to gain by flashing just recovery ?
fastboot flash recovery stock_recovery.img
4.18.502.7 stock_recovery - Delete the part in Red
clsA said:
what are you trying to gain by flashing just recovery ?
fastboot flash recovery stock_recovery.img
4.18.502.7 stock_recovery - Delete the part in Red
Click to expand...
Click to collapse
im trying to get the stock recovery on... i currently was using rom manager and want to change to stock sorry really kinda noob when it come to this phone, my old htc inspire was super easy =)
I think this is just what I need -- I can restore just system from the this TWRP backup in my TWRP recovery and then essentially have an 5.5 --> 6.0 upgrade same as OTA would do if I weren't S-ON/unlocked and could actually apply OTA updates??
I want to avoid having to reconfigure or reinstall anything. I know I take my own risk and if trouble, will have to factory reset.
Dont know if that will work....good luck
Almost does. Booted up just fine and all my apps and settings/config was there other than the wallpaper and Blinkfeed settings. Feeling great right up until the spontaneous reboot, lol. OK, now I'll just do a full restore of this backup and then do a Titanium Backup restore for my apps and settings. Hopefully, that works no prob...
Your gonna have issues again,never restore system data/settings....apps ok
StephenMSmith said:
Almost does. Booted up just fine and all my apps and settings/config was there other than the wallpaper and Blinkfeed settings. Feeling great right up until the spontaneous reboot, lol. OK, now I'll just do a full restore of this backup and then do a Titanium Backup restore for my apps and settings. Hopefully, that works no prob...
Click to expand...
Click to collapse
Really? I've done it in the past (flashed an RUU for 4.x and then restored system settings and user apps) w/o issue. Will report on this attempt shortly.
This worked fine. I retired user apps and system data (not system apps of course ). All my setting intact except for the sense stuff. No problems at all.
Last post in here as to not hijack thread, it is always best to reinstall and set up apps from scratch on new rom, the way you and many others do this restore,your settings from an older system/rom may overwrite the newer improvements enhancements in the newer rom, your walking two steps forward and 6 backwards...just my thoughts on it
@clsA sent you a pm
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
You unlock your bootloader?
if no, apply the steps in http://forum.xda-developers.com/showthread.php?t=2753110
If not work, go back to stock 4.4.4, not 4.4.2 and repeat the process to unlock bootloader and flash twrp and cm11 again.
noRetail said:
You unlock your bootloader?
if no, apply the steps in http://forum.xda-developers.com/showthread.php?t=2753110
If not work, go back to stock 4.4.4, not 4.4.2 and repeat the process to unlock bootloader and flash twrp and cm11 again.
Click to expand...
Click to collapse
I unlocked bootloader
Without unlocking bootloader there is no way to root without root there is nonway to flash cm11... LoL
Adarsh1998 said:
I unlocked bootloader
Without unlocking bootloader there is no way to root without root there is nonway to flash cm11... LoL
Click to expand...
Click to collapse
OK, with bootloder unlock try restore stock recovery in http://forum.xda-developers.com/moto-e/general/stock-recovery-recovery-img-t3031437
If not work try restore entirely rom stock 4.4.4 (I prefer this action)
After this apply the twrp and cm11, or, if you like lollipop?
Steps followed by me to get lillipop working 100% in xt1021 brazillian retail.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws (Get stock 4.4.4 for your country)
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw (Get SOAK OTA for your country)
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
noRetail said:
OK, with bootloder unlock try restore stock recovery in http://forum.xda-developers.com/moto-e/general/stock-recovery-recovery-img-t3031437
If not work try restore entirely rom stock 4.4.4 (I prefer this action)
After this apply the twrp and cm11, or, if you like lollipop?
Steps followed by me to get lillipop working 100% in xt1021 brazillian retail.
Get the zip file in https://mega.co.nz/#!wVsQmajI!tmEkvt...jtAS2GwF5fncws (Get stock 4.4.4 for your country)
Extract the files
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Apply your Google Account
Get the zip file in https://mega.co.nz/#!IJ9SVCaT!watj3-...GnKkg8od_kthLw (Get SOAK OTA for your country)
Put this zip file in root internal memory
In Fone go to Settings, About Phone, System Updates
After detect and apply update your Moto E have Lollipop 5.0.2
if you have a bootloader unlocked warning in boot phone after update to lillipop
Get the zip file in https://mega.co.nz/#!MFVkCQ7J!W7SmL3...rWDXoHW5hz6l44
unzip the file
In Fastboot mode apply the commands bellow in root user (I use Linux Mint 64)
commands :
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
I think u miss understood my question.
Im able to boot into all rom. Cm11, stock. 4.4.2, stock 4.4.4. Stock 5.0.1 but the problem is that when i press reboot the phone goes to the recovery. in recovery i hv to goto reboot bootloader option in bootloader i hv to choose normal powerup option
Adarsh1998 said:
I think u miss understood my question.
Im able to boot into all rom. Cm11, stock. 4.4.2, stock 4.4.4. Stock 5.0.1 but the problem is that when i press reboot the phone goes to the recovery. in recovery i hv to goto reboot bootloader option in bootloader i hv to choose normal powerup option
Click to expand...
Click to collapse
Yes, i don't have unserstand, sorry my mistake, you try factory reset?
noRetail said:
Yes, i don't have unserstand, sorry my mistake, you try factory reset?
Click to expand...
Click to collapse
All i tried no use
Adarsh1998 said:
All i tried no use
Click to expand...
Click to collapse
this is bad, I try to go back to stock 4.4.4 to clean the phone and if everything is ok would install the cm11 again, I see no other solution, sorry not help much.
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
Try wipe partition system, this may work
GabrielRW said:
Try wipe partition system, this may work
Click to expand...
Click to collapse
How in twrp?
flash kernel again
Adarsh1998 said:
When I switch on my device. I always boot to recovery. If I select reboot it also reboot to recovery.if I goto twrp and choose reboot to system it also reboot to recovery again if I need to boot to system I have to boot into bootloader and choose normal power up... What to doo
The problem comes after I flashed twrp via fast boot on StockRom
Also in cm11 plz help
I'm currently on Cm11 stable build
XT1022
Click to expand...
Click to collapse
i did the same thing before.
flash kernel with proper command
you have flashed recovery with kernel command maybe
Adarsh1998 said:
How in twrp?
Click to expand...
Click to collapse
Yes, go to advanced wipe, make a full wipe except sdcard and flash again the ROM. Sorry for my bad english
kushal.purkar said:
i did the same thing before.
flash kernel with proper command
you have flashed recovery with kernel command maybe
Click to expand...
Click to collapse
How to pl, help
Where is link?
this may help
Adarsh1998 said:
How to pl, help
Where is link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-e/development/downgrade-5-0-x-to-4-4-4-stock-firmware-t3031073
Hi,
After much read of guides, I post here my SIMPLE guide for OTA upgrades when your Moto G is unlocked and you use systemless root and TWRP.
This guide is safe and works!
For example, with this guide you can upgrade from STOCK MPJ24.139-23.4 to MPJ24.139-63:
Warning: I assume you know the concepts "fastboot", "systemless root" and TWRP.
For the original stock firmware search here for your exact MODEL and VERSION: http://mirrors.lolinet.com/firmware/moto/athene/official/
1) Reboot to TWRP and make a FULL BACKUP of your current firmware. Use the SD-Card and not the internal memory.
2) To Apply the OTA you need to restore BOOT.IMG and SYSTEM.IMG.
2a) If you rooted your device, for sure your BOOT.IMG isn't the original one. You can:
- Option 1: Restore it from an original backup of your firmware (if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "boot.img" and flash it in the fastboot mode using "fastboot flash boot boot.img".
2b) If you use Systemless SuperSU then your system partition can be untouched. In case of doubt, or if the patch shows an error, you can restore it...
- Option 1: Restore it from one backup of your firmware (only if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "system.img_sparsechunk.0-7" and flash them in the fastboot mode using these 8 commands (execute one, wait until completes, then execute the next one):
Code:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
3) Boot to the TWRP Custom Recovery (you don't need to restore the original Recovery partition).
4) Download the OTA (Blur_Version.24.24.4.athene.retail.en.US.zip) or copy it from the downloaded directory. Copy the ZIP file to a computer, extract the file "/META-INF/com/google/android/updater-script" and edit it... Remove these three lines (this only removes the check of the running build, because you like to execute it inside TWRP):
Code:
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-63/64:user/release-keys" ||
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-23.4/4:user/release-keys" ||
abort("Package expects build thumbprint of 6.0.1/MPJ24.139-63/64:user/release-keys or 6.0.1/MPJ24.139-23.4/4:user/release-keys; this device has " + getprop("ro.build.thumbprint") + ".");
After that, copy (repack) this edited file to the ZIP file of the OTA. I suggest to change the name of the ZIP, for example to "Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip". Now, you can run this patch file running TWRP.
5) Copy the patch OTA file to the SD-CARD, boot to the TWRP and apply the OTA... After several minutes the task completes. Reboot and check if the update is done and all works well. Your data needs to be already there...
6) Reboot into the fastboot mode and reflash the TWRP Custom Recovery using "fastboot flash recovery twrp-3.0.2-0-athene.img". Then boot in the recovery mode and do another Backup (for save untouched "system.img" and "boot.img" partitions).
7) Now you can re-root using the TWRP mode and SuperSU 2.78 in Systemless mode (remember to execute "echo SYSTEMLESS=true>>/data/.supersu" prior to install the SuperSU.zip)
I hope this helps you!
This guide only uses the minimum and required steps.
:good:
If you like to download one already patched OTA, then download it from here (join the two files first!):
Part 1: http://www.sendspace.com/file/dkws7p
Part 2: http://www.sendspace.com/file/xaompg
Part 1: http://www.sendspace.com/file/e3of46
Part 2: https://www.sendspace.com/file/a3tl4r
CRC:
filename=Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip
size=508332365
crc32=AFEC5752
Thank you, I was wondering about just this. Will come In handy.
Do you need to resign the zip with signapk?
Thanks for you guide!
I used it to update my Lenovo P2 to Nougat.
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Indianvixen9 said:
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Click to expand...
Click to collapse
I've heard this from a few people. I got the Amazon variant little more than a week ago. Unlocked BL and rooted lickety splits, no issues.
I consider myself pretty tech savvy, but the post might as well have been in Swahili. Can it be dumbed down any further?
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
t0mm13b said:
Do you need to resign the zip with signapk?
Click to expand...
Click to collapse
No, just re-zip! :victory:
Dbush72 said:
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
Click to expand...
Click to collapse
Done! :highfive:
Thank you for the reply and refreshing the download links
As far as I can tell you are flashing this via TWRP which is why the zips dont need signed is that correct?
I have an xt1625 non-amazon version that im working with.
I tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml which didnt work with this error:
E3005: "EMMC:/dev/block/bootdevice/by-name/boot:
has unexpected contents
I also tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
Failed with the same error as last time
I also tried flashing Blur_Version.24.31.48.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml which does seem to pass the version checks but gives this error:
"eom/app/BRApps2/oat/arm/BRApps.odex" has unexpected contents.