Hi,
I'm using only stock rom, rooted and with xposed mods on my Nexus devices. Because of trying some things out, I want to have a stock rom update.zip from the latest Factory Image on my device to have the security to flash it back to stock without a computer.
So, I've managed with some help this update.zip. It's absolutely pure stock. Not rooted, not deodexed or anything else (to root, there is a link below)
I think, some of you are thinking the same and so I want to share this update zip. I hope you have fun with it.
It works with CWM and TWRP Recovery!
Romversion
KOT49H Hammerhead
Tweaks / Changes
Nothing
Download
Stock ROM KOT49H Hammerhead
MD5 Checksum: 864626c54510b0c0eb3dac8a23e66f45
Thanks to
vetzki
caho
for their kindly help!
Infos
- You want root, you only have to flash, this file here, too: SuperSU Download
- the install process is slow. Please wait, it really installs. It takes about 5 Minutes. If someone has the ability to show me how to make it faster: Please, please!!!
Have Fun!
So, do you recommend a full wipe and cache clear when installing this?
Let's say I want to go stock in anticipation of a new update to android. I would go to Recovery (I use twrp), wipe data/erase everything from my previous rom, and then flash update.zip (and supersu at the same time), and I'll be set with stock everything including kernel, etc?
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
xybur said:
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
Click to expand...
Click to collapse
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Mo'HAWK said:
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Click to expand...
Click to collapse
Gotcha, thanks for the help/clarification.
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
A full wipe is indeed better if you come from another rom.
But with a nandroid backup, you can try.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Click to expand...
Click to collapse
FormelLMS said:
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
Click to expand...
Click to collapse
Hello,
All is here about OTA and root: [INFO] Nexus 5 OTA Help-Desk...
Thanks!
So it's right.
Flash this rom, don't delete or change a file. No new Kernel and you can receive the update.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
very wrong. first off, Google does not check. secondly, you can get an update while having root, as long as you do not change system files. why do you think we get so many "i updated ota and lost root" threads?
I'm just curious, I thought that the recovery was supposed to be stock to receive ota updates? Tia
Sent from my Nexus 5 using JellyBombed Tapatalk 2
Would you care to share how did you make flashable stock room?
Sent from my Nexus 5 using Tapatalk
Hey,
this thread here shows the most:
http://forum.xda-developers.com/showthread.php?t=2285831
You have to know, that you need the extracted system.img as the system folder in your update.zip.
Then you need the boot.img unextracted.
This is a all easy. A bit complicated is the meta-inf folder.
I've used this folder from other aosp roms.
I have to learn that now, too.
Sent from my IPhone 7s
Download link not working????
Sent from my Nexus 5 using XDA Free mobile app
Related
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
fa7592 said:
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
Thank you very much. I appreciate the quick response and the help.
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
would I just have to reflash the kernel I'm on now if I were to update that way?
Sent from my SAMSUNG-SGH-I747 using xda premium
jrbaker624 said:
would I just have to reflash the kernel I'm on now if I were to update that way?
Click to expand...
Click to collapse
No. There's a zip file there with the OTA but with the bootloader and kernel updates removed. You can flash that to keep your kernel. There's another zip file there with just the bootloader if you want to update that, too. Just flash both (No Bootloader No Kernel, the Bootloader).
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
UPDATE:
okay so I followed the steps in the thread you provided, and when I go to flash the update zip in recovery mode, i get an error and it aborts the installation. Heres the error:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
I am also getting same error I was on team epics recovery then saw it wouldn't work for that recovery so I flashed a new recovery and still get the same error.
Tried flashing the no boot loader zip. And the no boot loader and no kernel zip
Sent from my SAMSUNG-SGH-I747 using xda premium
fa7592 said:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
Click to expand...
Click to collapse
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
fa7592 said:
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
Click to expand...
Click to collapse
Download OTA Rootkeeper from the play store, save root, then install the OTA. Reboot and OTA rootkeeper restore root.
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded that one instead of the third one you had linked all together and it worked. Thank you
Sent from my SAMSUNG-SGH-I747 using xda premium
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
fa7592 said:
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
Click to expand...
Click to collapse
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
drothenberger said:
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
Click to expand...
Click to collapse
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
fa7592 said:
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
Click to expand...
Click to collapse
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
drothenberger said:
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
Click to expand...
Click to collapse
Oh okay. In that case I'll go ahead and put in that custom ROM and report back when everything is done. Again, thanks for the help and patience.
Okay, so I have applied the ROM and everything is good! Well for the most part. At times when there isn't a WiFi signal available and it has to use mobile data, the 4G LTE doesn't work. It will connect to HSPA or 3G. And it happens in areas I know has 4G LTE available. But other than that everything seems to be working good. Just thought I'd share in case anyone was thinking of using the AOKP ROM.
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Both files are now uploaded!
Thanks man! Getting it now for that "just in case" moment.
Sent from my HTC One X+ using Tapatalk 2
droidiac13 said:
Thanks man! Getting it now for that "just in case" moment.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
That was the purpose of it
hasoon2000 said:
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Click to expand...
Click to collapse
Wow you are fast. Thanx
Sent from my HTC One X+ using xda premium
Excuse the newbie questions I am about to ask. Feel free to point me in a different direction.
I was working on a friends phone and I unintentionally loaded the wrong boot.img when attempting to root his phone.
Now his phone is stuck at the boot screen.
When i try to run recovery it just sits there at the recovery screen with a red !.
I downloaded your files but I cant load it to the phone because my PC wont load the mass storage device. (
I am stuck. I appreciate any help I can get at this point.
dekend said:
Excuse the newbie questions I am about to ask. Feel free to point me in a different direction.
I was working on a friends phone and I unintentionally loaded the wrong boot.img when attempting to root his phone.
Now his phone is stuck at the boot screen.
When i try to run recovery it just sits there at the recovery screen with a red !.
I downloaded your files but I cant load it to the phone because my PC wont load the mass storage device. (
I am stuck. I appreciate any help I can get at this point.
Click to expand...
Click to collapse
Pull boot.IMG from my zip. Place it in the kernels folder of my toolkit. Boot into bootloader. Press "with this command" to flash the boot.img.
Support is done for the night. Goodnight!
Sent From My HTC Amaze 4G via Someone's Room
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
wmg316 said:
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
Click to expand...
Click to collapse
Yes and yes. You might need to relock the bootloader if you flash a stock RUU (not officially available for AT&T yet). Once installed you can unlock and root again.
wmg316 said:
Questions about the AT&T Stock ROM. When you say "for people who want to go back to complete stock"....
Will this lose root then? Also, will it replace TWRP recovery?
Thanks!
Click to expand...
Click to collapse
Since there is no RUU, this is a flashable zip in TWRP. You can flash this to get your phone up and running. However, this will not replace TWRP.
If your phone is messed up and you want root as well, flash the deodexed and rooted ROM.
hasoon2000 said:
Since there is no RUU, this is a flashable zip in TWRP. You can flash this to get your phone up and running. However, this will not replace TWRP.
If your phone is messed up and you want root as well, flash the deodexed and rooted ROM.
Click to expand...
Click to collapse
Oh! OK. My phone is not messed up, I am just waiting on an AT&T deodexed ROM to be made!
So...that leads me to one more question, and I'll leave you alone!
The 'AT&T Stock Deodexed Rooted Base (Devs Only)' ROM in the OP is a fully operational ROM? The statement in the OP "One will be a deodexed, rooted, base for any dev to use to make a ROM" made me think these were base files to be used to create a ROM. So if it is a fully operational ROM, I could use that, right...even if my phone is NOT messed up? (well, that was two questions). I am still stock at the moment...
wmg316 said:
Oh! OK. My phone is not messed up, I am just waiting on an AT&T deodexed ROM to be made!
So...that leads me to one more question, and I'll leave you alone!
The 'AT&T Stock Deodexed Rooted Base (Devs Only)' ROM in the OP is a fully operational ROM? The statement in the OP "One will be a deodexed, rooted, base for any dev to use to make a ROM" made me think these were base files to be used to create a ROM. So if it is a fully operational ROM, I could use that, right...even if my phone is NOT messed up? (well, that was two questions). I am still stock at the moment...
Click to expand...
Click to collapse
It's a fully operational ROM. You can flash it even if your phone isnt messed up. So think of it as a custom ROM. You can just flash it in TWRP.
Downloading now! This marks day 3 with no phone! I hope this ends my nightmare. Thank you so much.
hasoon2000 said:
It's a fully operational ROM. You can flash it even if your phone isnt messed up. So think of it as a custom ROM. You can just flash it in TWRP.
Click to expand...
Click to collapse
Thanks. Just to make sure I have the steps straight (in a manual method):
Copy 'evitareul_dev_base.zip' to my internal memory ("/storage/internal memory/" in Solid Explorer)
Unlock device with Unlock Code from HTC.dev
Install AT&T Recovery provided in the All-In-One Tool; reboot to bootloader and flash recovery
fastboot flash recovery recovery.img
Enter Recovery and flash the 'SuperSU.zip' from the all-in-one tool folder
At this time I would be stock and rooted, correct?
Return to bootloader and install kernel provided in the 'AT&T Stock Deodexed Rooted Base (Devs Only)'
fastboot flash boot boot.img
Return to recovery and perform wipes....here is where I am unsure after reading the "Important and Read" threads about the /data/media. I am accustom to doing these wipes from TWRP on my OneX: (1) factory reset, (2) wipe dalvik cache and (3) wipe System....Is that what I need to do for the OneX Plus?
Install 'evitareul_dev_base.zip' ROM from recovery
I appreciate your response! I don't want to mess anything up...I guess I'm over precautious!!
I wiped, guess i wiped the wrong thing, now rom wont boot. i can get to recovery, twrp, but how do i now get this zip on to the phone since i cant boot? mount in twrp im not seeing anything on my computer. ATT X+
@nugzo. Did you have the zip on the device prior to entering recovery and performing the wipes?
EDIT: If so, what wipes did you perform?
wmg316 said:
@nugzo. Did you have the zip on the device prior to entering recovery and performing the wipes?
EDIT: If so, what wipes did you perform?
Click to expand...
Click to collapse
yes i did but it was the wrong zip. It was mikes 1986 rom, at the time i didnt realize it wasnt for ATT. So after wiping, i guess i wiped the stock rom. Wiped system, data, and davlik. now it just sits at HTC quietly brilliant screen.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
trying the sideload adb in twrp but that didnt work, says no device found. when i do adb devices my device shows though. now i, trying to get this stock rooted installed.
Wiping System, Data, Dalvik definitely wipes the stock ROM!
Hmmmm. Mike's OP states nearly on the first line of his thread: "Not working with AT&T One X+ LTE"
All that I've read is that you have to have the ROM on the device before booting to recovery...but there was a statement that it could be adb pushed:
http://forum.xda-developers.com/showthread.php?p=34358646#post34358646
With "no device found"...I'm not sure what to do...Hopefully one of the devs will ring in for you.
title
hasoon2000 said:
I'm making 2 ROMs right now.
One will be a deodexed, rooted, base for any dev to use to make a ROM. No need to ask for permission, just give me credit. That's all I ask.
There other will be for people who want to go back to complete stock that do not have the RUU.
AT&T Stock ROM (credits to olorolo for providing the nandroid!)
http://d-h.st/e2m
AT&T Stock Deodexed Rooted Base (Devs Only)
http://d-h.st/qmd
Click to expand...
Click to collapse
thanks. im sorry im noob i think are many people look around for this maybe if you include AT&T in the thread title more people are happy. excuse my english. thanks againg.
---------- Post added at 08:59 AM ---------- Previous post was at 08:00 AM ----------
hi i have unlimit internet no lte (i dont wan it because change my monthly pay) with my past at&t vivid i change the apn and still with unlimit internet with 5 to 7 mb speed with my international HOX i change the apn and still with unlimit iternet but no more than 3mb speed. now with your AT&T Stock Deodexed Rooted Base can i change the apn and still with my unlimit internet. i dont wan LTE. thanks. i go now to buy my new at&t HOX+.
Lloir said:
providing you dont touch the "wipe internal memory" button all is good, i use TWRP and i've been performing about 20-30 wipes a day, and my internal sd is still intact with my TWRP backups
Click to expand...
Click to collapse
from the other thread
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is also available.
NOTE: if you flash the deodexed version and have problems with root, flash UPDATE-SuperSU-v2.02.zip from here. I don't anticipate any root problems, but just in case, this will fix it.
100% stock: STOCK-4.4.2-P5200(fixed).zip
Deodexed + rooted: STOCK-DEODEXED-ROOTED-4.4.2-P5200(fixed).zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Restl3ss said:
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is in the works. Bear with me.
100% stock: STOCK-4.4.2-P5200.zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Click to expand...
Click to collapse
Very good work done by you! Yesterday I spent hours to unzip the file but unsuccessfully. I will try it right now! Thanks a lot!
Restl3ss said:
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5200. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is in the works. Bear with me.
100% stock: STOCK-4.4.2-P5200.zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.
Click to expand...
Click to collapse
I tried but it doesn't flash. Received "failed" message. I am using the latest TWRP by angel666. Any idea what I am doing wrong?
edsoedso said:
I tried but it doesn't flash. Received "failed" message. I am using the latest TWRP by angel666. Any idea what I am doing wrong?
Click to expand...
Click to collapse
I've got the same problem.
Hold on, I'm working on it
@edsoedso
@Max4000
I think I've fixed it. Reuploading now. Bear with me.
The problem was a fairly stupid one. I edited the assert to fit P5200 instead of P5210 (I'm using the same updater-script I used for the wifi model stock kitkat).
Problem is, I used mac textedit instead of gedit. One preserves linux encoding, the other does not. Can you guess which is which?
I believe it was Homer Simpson who said, "DOH".
Anyway, edited the updater-script with gedit and just removed the assert completely, so once it's done uploading you should be able to flash without issue.
Restl3ss said:
@edsoedso
@Max4000
I think I've fixed it. Reuploading now. Bear with me.
The problem was a fairly stupid one. I edited the assert to fit P5200 instead of P5210 (I'm using the same updater-script I used for the wifi model stock kitkat).
Problem is, I used mac textedit instead of gedit. One preserves linux encoding, the other does not. Can you guess which is which?
I believe it was Homer Simpson who said, "DOH".
Anyway, edited the updater-script with gedit and just removed the assert completely, so once it's done uploading you should be able to flash without issue.
Click to expand...
Click to collapse
Do not worry, I installed stock 4.4.2 using odin, than TWRP and superuser. It looks great! Please work on 4.4.2 Pimpdroid and let us known the results. Regards!
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
just uploaded a deodexed + rooted build. If you have any troubles with root flash SuperSU from the link in OP.
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
khaledreno said:
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
Click to expand...
Click to collapse
I always do a factory reset, format data, and full wipe with any ROM Can you move your files to your PC via USB cable?
khaledreno said:
do i need to clear data and cache beforce flashing ? cuz i don't have sd card so if i clear data the rom will delete.
Click to expand...
Click to collapse
I flashed without wiping and had big problems. You should really do a full wipe.
Restl3ss said:
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
Click to expand...
Click to collapse
I just saw your note. I am downloading both versions, flash them and let you know.
i have downloaded both versions but instal failed
any way does any one know which site i can download the MD5 of the software without corruption ?
Restl3ss said:
@Max4000
@edsoedso
Fixed version is now uploaded. Enjoy
@edsoedso
I know you've already got kk working, but would you be willing to try this zip to make sure it works? I think i've ironed it out but i'd like to be sure. Can't test myself as I have the WiFi model
Click to expand...
Click to collapse
@Restl3ss:
I flashed both versions using TWRP 2.6.3.0 and everything went well. The first unrooted rom after completing flashing offered to install superuser and I did it. The second rom version did not offered it so I rebooted to TWRP and installed superuser from sd card. I am keeping the second version on my tablet. Looks nice and works very well. I will remove some system apps that I do not use and free some additional memory.
It seems that battery is draining faster than 4.2.2. Does anybody note it? Any solution? Thank you!
I have tried the rootet and fixed version, , but it doesn´t work, it hangs on boot!
Installed with TWRP 2.7.1.0, may i have to install this ROM with Odin ?
jamalau said:
I have tried the rootet and fixed version, , but it doesn´t work, it hangs on boot!
Installed with TWRP 2.7.1.0, may i have to install this ROM with Odin ?
Click to expand...
Click to collapse
hey man you need to wipe system, data,cache and dalvik-cache
then flash the zip and it should work
edsoedso said:
@Restl3ss:
I flashed both versions using TWRP 2.6.3.0 and everything went well. The first unrooted rom after completing flashing offered to install superuser and I did it. The second rom version did not offered it so I rebooted to TWRP and installed superuser from sd card. I am keeping the second version on my tablet. Looks nice and works very well. I will remove some system apps that I do not use and free some additional memory.
Click to expand...
Click to collapse
Is there an update zip for recovery? I have 2.6.1 twrp and get error message during install. Can i update to latest twrp or philz by Flash, or do i have to connect the tab to PC, and need to do the beginners Steps?
Thanks for advices
Aaah, i got it... A flashable philz for p5200...
quitschibu84 said:
Is there an update zip for recovery? I have 2.6.1 twrp and get error message during install. Can i update to latest twrp or philz by Flash, or do i have to connect the tab to PC, and need to do the beginners Steps?
Thanks for advices
Aaah, i got it... A flashable philz for p5200...
Click to expand...
Click to collapse
Can you post the link for the Philz 5200 recovery?
thks
https://developers.google.com/android/nexus/images?hl=en
Wow nice !!!
Let's Rock!
Can't wait for pure nexus to update to N
Sent from my Nexus 6P using Tapatalk
YES!
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
I only flash via fastboot and when going between versions I'd personally want to do a fully clean flash. Mind you I reverted to MM after trying N for a couple days, but again, I'd never flash a full factory image via Flashfire.
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
Unless a lot of users have certified that flashing via dlash fire works, I would recommend a clean flash via fastboot. This way you are flashing the images the most direct way possible. Doing this will also reduce possible entry points for issues.
First person to find an .mbn file in the boot.img or bootloader.img gets SO much cred.
Oh my .. Time to flashing silently
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
kaslopis said:
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
Click to expand...
Click to collapse
There's a thread called "Android N: What doesnt work" here in general
david279 said:
There's a thread called "Android N: What doesnt work" here in general
Click to expand...
Click to collapse
Most of the apps on that list that I use did not have the stated issues... None of them did.. I'm not sure if that list is up to date.
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
E30Nova said:
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
Click to expand...
Click to collapse
You aren't alone. Went back a day ago myself.
Sent from my Nexus 6P using Tapatalk
From what I've seen, this version isn't all that superb. Being on 6 isn't so bad
I've honestly had zero issues with the factory image for N. I wiped everything and clean flashed the image flat. Once I restored all my apps (around 80), so far it seems very smooth. No issues with lag in either the system or the fingerprint scanner.
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Soured Lie said:
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Click to expand...
Click to collapse
Flash-all is still broken afaik, better flash the individual img`s in fastboot.
Hey y'all,
Sorry to bother here. I looked around but couldn't find anything. I'm running NRD90M on my phone. I install TWRP and I rooted my 6P + unlocked bootloader. However I just downloaded the full image on google NRD90U. I'd like to put back my phone to stock with this new image and be able to just keep it stock and receive OTA. Can someone help me out or giving me a link where there's a tutorial. I already downloaded Fastboot/ADB and installed my drivers.
PS: It's find if it wipes everything. I just want it clean.
Thanks!
StangATX
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.