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.
Related
Hey all,
apologize in advance if this was asked before. i have performed a search and could not locate a definite answer.
i have SG3 ATT1747ucalem rooted using the guide on this forum.
since 2 days ago i have a notification for an OTA from ATT.
i have read the thread here and from users instructions installed voodoo OTA keeper.
i then tried to perform the OTA,
it keep going into recovery and then fail on "e: signature verification failed"
i have tried to temp unroot the device and try again - fail.
tried to toggle the verification off and apply the OTA - fail.
my question is this:
is there any way (or a thread to read) where there are instructions on how to apply the OTA update without loosing your root?
please let me know, thank you.
m.a.s.e said:
Hey all,
apologize in advance if this was asked before. i have performed a search and could not locate a definite answer.
i have SG3 ATT1747ucalem rooted using the guide on this forum.
since 2 days ago i have a notification for an OTA from ATT.
i have read the thread here and from users instructions installed voodoo OTA keeper.
i then tried to perform the OTA,
it keep going into recovery and then fail on "e: signature verification failed"
i have tried to temp unroot the device and try again - fail.
tried to toggle the verification off and apply the OTA - fail.
my question is this:
is there any way (or a thread to read) where there are instructions on how to apply the OTA update without loosing your root?
please let me know, thank you.
Click to expand...
Click to collapse
did you install clockworkmod recovery?
mrRobinson said:
did you install clockworkmod recovery?
Click to expand...
Click to collapse
Yes Sir,
i do have it installed.
??????????
So if we didn't move to another rom and just rooted is it ok to do the update.
OK tried it didn't work because of Clockwork
m.a.s.e said:
Yes Sir,
i do have it installed.
Click to expand...
Click to collapse
you need stock recovery to do it. you can either reflash root66 to get stock recovery back, use voodoo ota root keeper and do the ota update. or i think someone make the update into a cwm flashable zip and you can just flash that in cwm.
rgtorres09 said:
So if we didn't move to another rom and just rooted is it ok to do the update.
OK tried it didn't work because of Clockwork
Click to expand...
Click to collapse
yea you need stock recovery. I forget if it was att or verizon (all these forums jumble in my head) but someone made the update into a cwm flashable zip. its not hard to do if you can find that.
mrRobinson said:
you need stock recovery to do it. you can either reflash root66 to get stock recovery back, use voodoo ota root keeper and do the ota update. or i think someone make the update into a cwm flashable zip and you can just flash that in cwm.
yea you need stock recovery. I forget if it was att or verizon (all these forums jumble in my head) but someone made the update into a cwm flashable zip. its not hard to do if you can find that.
Click to expand...
Click to collapse
thank you for your reply. i think its best if i will wait for a CMW update version. hope soneone will do it fast enough thank you,
If you are rooted in V10G with Tmobile P769, then you can bypass OTA and go straight to rooted V20D JB with CWM already installed.
Here is a copy of rooted CWM back up of P769 V20D
http://forum.xda-developers.com/showpost.php?p=40775018&postcount=772
The latest lock boot loader CWM (v1.5) for JB is here.
http://forum.xda-developers.com/showpost.php?p=36620368&postcount=1
The radio update zip file is here.
http://forum.xda-developers.com/showpost.php?p=40844363&postcount=37
1) First delete the version 1.4 CWM
>>> 1. Delete /system/bootstrap directory
>>> 2. Delete /system/bin/e2fsck file
>>> 3. Rename /system/bin/e2fsck.bin file to e2fsck
2) Download and install version 1.5 CWM
3) If you have Titanium Back up, make a fresh back up.
4) Download and copy V20D back up folder to clockworkmod back up folder.
4.5) Download and copy radio.zip to SD.
5) Reset and go into CWM.
6) set the back up format to 'tar'
7) run Back up to external SD. This will give you a latest back up of you V10G.
8) run Restore from external SD and find the V20 back up folder.
8.5) run Install Zip from SD for the radio.zip file. NOTE this update takes 2-3 min. Do not panic.
9) When the opration is finished, reboot.
You should be in a fresh rooted V20D JB. Now download Titanium Back up and restore your apps.
Please thank the file contributors in their posts for their effort.
__________. _________________________________________________________________________
Original post is not related to above and removed to lessen the confusion.
removed.
mjb1994 said:
(ge.tt/547NI4f/v/0) there is the link for my whole cache including the OTA.
As for android updating, it has been 14 min and it just now finished fully booting
I will post again after I restore root
Update: I was able to successfully restore root with Voodoo OTA RootKeeper
Just like everyone else has stated although, While in SuperSU the first re-installation failed, but you just go back into the app and install it again and it successfully installs the su binaries
I find it hilarious and awesome that I haven't had to re root the phone since I got it in February and rooted with 10e (when the method was easy). I used Voodoo for 10G and now with 20D
The whole process took a good 15 min.
Click to expand...
Click to collapse
here's MJB's entire cache folder, it may or may not have the SBin.
removed.
Need the KDZ file t flash in!
csrow said:
Here is the link to the OTA zip file posted by Lelus.
https://dl.dropboxusercontent.com/u/54534987/ad6729f33f2f.ota_update_V10g_MR_FINAL_to_V20d_JB_QA_FINAL.zip
Just need to find the other file to see if it can trigger the update.
Click to expand...
Click to collapse
hi. I can't find original post of this. I d-loaded zip but don't know how to apply properly without losing root. can you either point me to the thread or tell me if I should just use voodoo then flash with CWM?
removed.
I have restored the rooted backup. Works great except for loss of service. The update included new radio. Anyone able to make a flash able zip?
Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
Somairotevoli said:
I have restored the rooted backup. Works great except for loss of service. The update included new radio. Anyone able to make a flash able zip?
Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Not sure if there is a way to upgrade radio via cwm. You can try replacing /system/bin/rild to one from ics
TFT_xKripple said:
here's MJB's entire cache folder, it may or may not have the SBin.
Click to expand...
Click to collapse
where ? no link
Well, I was going to write and tell people I can't get the OTA update and also seem to be unable to reinstall the stock apps so it will pick up the OTA update (rooted with 10g from another user), but....NEVER MIND! Will try this method and see if it works.
One question - in the instructions it says delete 1.4. Ok, from the link page I get that, but curious....wouldn't installing 1.5 just erase and overwrite 1.4 anyway? Why the need to delete it, other than just having a clean install? Doesn't matter to me really, just curious.
did everything you said below and I got the MD5 mismatch! It aborted the JB update in CWM. . and suggestions?
csrow said:
If you are rooted in V10G with Tmobile P769, then you can bypass OTA and go straight to rooted V20D JB with CWM already installed.
Here is a copy of rooted CWM back up of P769 V20D
http://forum.xda-developers.com/showpost.php?p=40775018&postcount=772
The latest lock boot loader CWM (v1.5) for JB is here.
http://forum.xda-developers.com/showpost.php?p=36620368&postcount=1
1) First delete the version 1.4 CWM
2) Download and install version 1.5 CWM
3) If you have Titanium Back up, make a fresh back up.
4) Download and copy V20D back up folder to clockworkmod back up folder.
5) Reset and go into CWM.
6) set the back up format to 'tar'
7) run Back up to external SD. This will give you a latest back up of you V10G.
8) run Restore from external SD and find the V20 back up folder.
9) When the restore is finished, reboot.
You should be in a fresh rooted V20D JB. Now download Titanium Back up and restore your apps.
Enjoy.
__________. _________________________________________________________________________
Original old post : IGNORE
I am looking for a file which I think is needed for the JB update to occur for Tmobile 769.
The actual OTA ZIP file has been already posted but I am looking for the file
/sbin/recovery.
If you are rooted and have received "OTA is ready message", before you update your phone, please look for the above file and post it here for us.
TIA
Click to expand...
Click to collapse
Nathan.7118391 said:
did everything you said below and I got the MD5 mismatch! It aborted the JB update in CWM. . and suggestions?
Click to expand...
Click to collapse
I've had this happen on my nexus 7 before. Redownload the file and copy it over again. Something got fudged up while moving it around.
---------- Post added at 10:40 PM ---------- Previous post was at 10:39 PM ----------
Prof24 said:
Well, I was going to write and tell people I can't get the OTA update and also seem to be unable to reinstall the stock apps so it will pick up the OTA update (rooted with 10g from another user), but....NEVER MIND! Will try this method and see if it works.
One question - in the instructions it says delete 1.4. Ok, from the link page I get that, but curious....wouldn't installing 1.5 just erase and overwrite 1.4 anyway? Why the need to delete it, other than just having a clean install? Doesn't matter to me really, just curious.
Click to expand...
Click to collapse
Im pretty sure installing 1.5 over 1.4 is totally fine(I did). Never hurts to be too safe though.
1) You may be able to just install V1.5 on top of V1.4. I don't know. It's just two deletes and one rename to get rid of V1.4.
2) If you are getting MD5 mismatch, make sure you do not rename the file directory. Try downloading again and you can also check using an external MD5 checker app.
Does this flash the radios too? Those are also needed.
Everything seems to work fine without flashing baseband.
Sent from my LG-P769 using xda premium
kevev said:
Does this flash the radios too? Those are also needed.
Click to expand...
Click to collapse
Yes, the radio seems fine. It looks like the 4 radio fls files were patched during the update. Actually, the signal level has improved around -5 dB. Just make sure you turn off the wi-fi calling option from the set up.
If you leave the option on, it will keep on try to turn off the radio.
P.S. - Anyone know how to get rid of Quick slide apps on the notification area?
So are we saying this CWM zip does not flash the radios?
It would be good to flash the new radios. It may help with cell reception.
More bars does not mean better reception if you have not flashed the radios. It just means that the new software is not reading what it is expecting from radio.
Will this work for rooted 10e as well?
csrow said:
Yes, the radio seems fine. It looks like the 4 radio fls files were patched during the update. Actually, the signal level has improved around -5 dB. Just make sure you turn off the wi-fi calling option from the set up.
If you leave the option on, it will keep on try to turn off the radio.
P.S. - Anyone know how to get rid of Quick slide apps on the notification area?
Click to expand...
Click to collapse
Is there an issue with the Wi-Fi calling option on JB? I use it in my house due to bad reception, will updating cause issues? Anyone know? Thanks!
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
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.
Here is the factory update zip. One may be able to flash it from stock recovery (will need to be renamed to "update.zip"), but no promises. I'm hoping a dev can take advantage of it.
update note 3 lollipop.zip
https://docs.google.com/file/d/0B2iEgzRTFjrQN2g4OTlpM19IUDQ/edit?usp=docslist_api
wow!
Awesome! Downloading now
Fantastic... I'm getting a footer is wrong - signature verification failed error, since I am rooted and probably tripped knox (had TWRP, now on stock recovery) device status custom. Any ways I can get this to work without having to odin back to stock? Just so much of a hassle I'd like to avoid if at all possible.
Delirious17 said:
Fantastic... I'm getting a footer is wrong - signature verification failed error, since I am rooted and probably tripped knox (had TWRP, now on stock recovery) device status custom. Any ways I can get this to work without having to odin back to stock? Just so much of a hassle I'd like to avoid if at all possible.
Click to expand...
Click to collapse
This might be your ticket:
http://forum.xda-developers.com/note-3-sprint/general/loolipop-pre-rooted-twrp-flash-t3088490
Is this one corrupt like the others or is it good?
Sent from my SM-N900P using XDA Free mobile app
Greaper88 said:
This might be your ticket:
http://forum.xda-developers.com/note-3-sprint/general/loolipop-pre-rooted-twrp-flash-t3088490
Click to expand...
Click to collapse
I know how to pull the update.zip. I did it for the previous update. Samsung has it encrypted. You have to act like you are gonna install the update and soon as it is done preparing to install it wants to reboot in to stock recovery to install. That's when you have to do a battery pull and use your pc to pull the unencrypted zip. Going of of bad memory but it's something like that. I know the reason everyone get a corrupt update.zip is its encrypted and the install will unencrypt just before install. Once install is aborted the proces will delete the files making you re download the update.
Sent from my SM-G900P using Tapatalk
Delirious17 said:
Fantastic... I'm getting a footer is wrong - signature verification failed error, since I am rooted and probably tripped knox (had TWRP, now on stock recovery) device status custom. Any ways I can get this to work without having to odin back to stock? Just so much of a hassle I'd like to avoid if at all possible.
Click to expand...
Click to collapse
JonSCSL said:
I know how to pull the update.zip. I did it for the previous update. Samsung has it encrypted. You have to act like you are gonna install the update and soon as it is done preparing to install it wants to reboot in to stock recovery to install. That's when you have to do a battery pull and use your pc to pull the unencrypted zip. Going of of bad memory but it's something like that. I know the reason everyone get a corrupt update.zip is its encrypted and the install will unencrypt just before install. Once install is aborted the proces will delete the files making you re download the update.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
OK. Good to know.
UPDATE!
DId the odin MK4 but everything was kept, no resetting/reinstalls required!
Then was able to download the update and all is well.
Does anybody know how to trigger the ota process if you have an update.zip on the device?
My device has modified bootloader, so I'm not eligible for OTA... but with Wanam Exposed you can fake Offical status, and it'll download the OTA, but fail to install.
If before it fails, you copy the update.zip from /data/fota/update.zip .. then you have a copy.
My issue now though is that the normal OTA process won't let me continue with the OTA dialogs... and if I try to flash the zip in stock recovery, it can't seem to open it.
Is there a way to trigger the Samsung OTA process, with root, and have it properly process and unencrypt the update.zip upon flashing?
Cheers!
Levistras said:
Does anybody know how to trigger the ota process if you have an update.zip on the device?
My device has modified bootloader, so I'm not eligible for OTA... but with Wanam Exposed you can fake Offical status, and it'll download the OTA, but fail to install.
If before it fails, you copy the update.zip from /data/fota/update.zip .. then you have a copy.
My issue now though is that the normal OTA process won't let me continue with the OTA dialogs... and if I try to flash the zip in stock recovery, it can't seem to open it.
Is there a way to trigger the Samsung OTA process, with root, and have it properly process and unencrypt the update.zip upon flashing?
Cheers!
Click to expand...
Click to collapse
Pulling the copy corrupts it.
To get to lollipop you have to factory reset, odin to nk4 then accept ota.
Sent from my SM-N900P using XDA Free mobile app