Database Users

I don't know what to do now

hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,

I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.

Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app

If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method

sfetaz said:
I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.
Click to expand...
Click to collapse
I hope there is program like that
Backwardsblade said:
Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think so.
I try but don't find the device
frederuco said:
If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method
Click to expand...
Click to collapse
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21

1090t said:
I hope there is program like that
I don't think so.
I try but don't find the device
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21
Click to expand...
Click to collapse
unzip first. inside another zip file.

goodintentions said:
unzip first. inside another zip file.
Click to expand...
Click to collapse
Yah, i do that

.........................

why is the only rom i can install and work is the: Android Revolution HD ?!

1090t said:
why is the only rom i can install and work is the: Android Revolution HD ?!
Click to expand...
Click to collapse
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.

1090t said:
hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,
Click to expand...
Click to collapse
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.

goodintentions said:
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.
Click to expand...
Click to collapse
it doesn't work i just wait there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is that right why to boot in to rom (from cold-boot) ?
horndroid said:
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.
Click to expand...
Click to collapse
I try many time with these the Recovery still same
even with the old version ..nothing

1090t said:
it doesn't work i just wait there
is that right why to boot in to rom (from cold-boot) ?
I try many time with these the Recovery still same
even with the old version ..nothing
Click to expand...
Click to collapse
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.

feisty_noodle said:
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.
Click to expand...
Click to collapse
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.

The op's problem is very similar to this one http://forum.xda-developers.com/showthread.php?t=1549062 which has been resolved.

goodintentions said:
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.
Click to expand...
Click to collapse
You are right, I may have misinterpreted the OP.
Still, I think the solution is the same.
When the device boots into recovery and can be cold-booted into ROM, the most likely culprit is the 'boot-recovery' flag which is set in the /misc partition. When the system sees that upon boot, it goes straight into recovery.
It should be the recovery's job to blank out that flag at some point, but CWM 5.5.0.4 (and, perhaps this recovery the OP is using) does not do this.
So, the solution is to reset it with the 'echo ...' command (or blanking out the first few bytes of /dev/block/mmcblk0p3) in shell.
My suggestion is very conservative.

I'll gave try and let u know

when i connect to the computer nothing shows up
even the Asus sync don't found it
I'll gave try on Linux

any help

[Q] Rooted, but stock rom with custom recovery. Can't install OTA 4.3?

I keep getting notification that 4.3 is downloaded, but I cant seem to install it with my custom recovery mod. Do I need to do it a different way?
Thanks all.

m374llic4 said:
I keep getting notification that 4.3 is downloaded, but I cant seem to install it with my custom recovery mod. Do I need to do it a different way?
Thanks all.
Click to expand...
Click to collapse
theres numerous info on this already but im feeling helpful
answer a few questions please:
cwm or twrp?
any modifications tu build.prop? ( this would include the fix to enable LTE)
stock kernel?
stock radio?

I'll jump in as op has gone awol.
Stock everything bar unlocked and rooted twrp
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

uploder said:
theres numerous info on this already but im feeling helpful
answer a few questions please:
cwm or twrp?
any modifications tu build.prop? ( this would include the fix to enable LTE)
stock kernel?
stock radio?
Click to expand...
Click to collapse
Sorry, have been busy at work.
CWM 6.0.2.3
Only modification besides running the SU app is I just recently installed the .33 modem with the sound fix for 4g. Stock kernel.

m374llic4 said:
Sorry, have been busy at work.
CWM 6.0.2.3
Only modification besides running the SU app is I just recently installed the .33 modem with the sound fix for 4g. Stock kernel.
Click to expand...
Click to collapse
I'm in the same boat. I'm running stock 4.2.2. ROM. Rooted, CWM 6.0.3.5, and I installed the AIO LTE .zip (I can't remember if I'm currently on the .33 or .27 radio). I received the 4.3 update OTA and just tried to install. I put me in CWM and asked me if I want to "install unkown zip" . I assumed that was the OTA update and selected yes. It seemed to do the install and reboot. However, I'm still on 4.2.2. Stranger still, when check for updates, it says I'm current.

SHPhone said:
I'm in the same boat. I'm running stock 4.2.2. ROM. Rooted, CWM 6.0.3.5, and I installed the AIO LTE .zip (I can't remember if I'm currently on the .33 or .27 radio). I received the 4.3 update OTA and just tried to install. I put me in CWM and asked me if I want to "install unkown zip" . I assumed that was the OTA update and selected yes. It seemed to do the install and reboot. However, I'm still on 4.2.2. Stranger still, when check for updates, it says I'm current.
Click to expand...
Click to collapse
The OTA won't install with a non-stock radio (I think) & the AIO flashable makes changes to the build.prop which will also prevent the OTA from installing.

3rdstring said:
The OTA won't install with a non-stock radio (I think) & the AIO flashable makes changes to the build.prop which will also prevent the OTA from installing.
Click to expand...
Click to collapse
Bingo! The AIO enabler does in fact make changes to your build prop which will cause the update to fail every time. Here's what I did. Flashed the stock 4.2.2 boot and system imgs via fastboot.(used the toolkit ) after which I manually flashed the stock radio (.48) and stock kernel. It worked after that. Gimmie a few and I'll link the files needed.
Sent from my Nexus 4 using xda app-developers app

ok here they are. of course before you do anything make a nandroid backup just incase.
stock kernel, and image are here. http://forum.xda-developers.com/showthread.php?t=2145848
you want to download the stock 4.2.2 image and extract the boot and system imgs to be flashed via fastboot.
also since my initial ota failed and I didnt want to wait for my phone to get it again I just downloaded the stock 4.3 image.
its the first link "4.3-JWR66V-from-4.2.2 JDQ39"
stock radio is here. you want .48 and you just flash in cwm
http://forum.xda-developers.com/showthread.php?t=2087227
---------- Post added at 02:17 AM ---------- Previous post was at 01:59 AM ----------
almost forgot. after you flash the 4.3 upgrade you also need to flash the latest superuser in cwm. after that once you reboot cwm will ask if you want to disable recovery flash. select yes

uploder said:
almost forgot. after you flash the 4.3 upgrade you also need to flash the latest superuser in cwm. after that once you reboot cwm will ask if you want to disable recovery flash. select yes
Click to expand...
Click to collapse
you mean select No

ksilver89 said:
you mean select No
Click to expand...
Click to collapse
I mean yes. disable recovery flash so he keeps cwm. but if he wanted stock recovery then he'd select no

uploder said:
I mean yes. disable recovery flash so he keeps cwm. but if he wanted stock recovery then he'd select no
Click to expand...
Click to collapse
That way he'd lose root, right? or they have not using install-recovery.sh to root anymore?

Just re root again after

[Q] /system/etc/gps.conf

adb sideload the kitket update zip is fails with following error:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?

alexroz said:
adb sideload the kitket update zip is fails with following error:
View attachment 2408712
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
Click to expand...
Click to collapse
look here:
http://forum.xda-developers.com/showthread.php?t=2525947
you MUST reflash a kind of stock/not gps moddified version :/

Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.

EvilAaron said:
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
Click to expand...
Click to collapse
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.

eksasol said:
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
Click to expand...
Click to collapse
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers

EvilAaron said:
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
Click to expand...
Click to collapse
The flashing will required an unlocked bootloader, so if its not unlocked you will lose all data when unlocking it. (Doing a factory reset in stock recovery also wipe everything.)
I don't really know what else you can do, if there were never any modifications, then the problem is due to Google having too much protections and issues for their OTA packages.

Unlocked so can do the method in your guide. But she says she wants to clean up her phone so a clean start will probably perform better and she gets the clean slate she wants, problem solved Though OTA checks annoy me now lol
thx for the feedback and guides

[OTA] Stock XNPH25R OTA

Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000

I'm getting binary update script error by flashing with TWRP

I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!

With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?

Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.

iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me

Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")

I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok

Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?

ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.

housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO

truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One

housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO

truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One

housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO

Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app

truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.

fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.

ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?

Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk

Full stock receiving an update today

I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.

Milkman00 said:
I just happened to do a software check, and it is downloading a new version. Any ideas? I was already on Lollipop.
Click to expand...
Click to collapse
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.

pre4speed said:
More than likely security update for stagefright vulnerability. S5 got theirs a week or so ago.
Click to expand...
Click to collapse
400 megs for Stagefright? That seems pretty big.

OC2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Milkman00 said:
400 megs for Stagefright? That seems pretty big.
Click to expand...
Click to collapse
Yeah it was 380 for the S5 too.

Thanks for the info. This was the only site that had ANY information about the update.

I'm on Lollipop, but Rooted. Will this update take away root by any chance?

My question exactly!

sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
Typically these updates do remove root. Best to wait until someone has a root method figured out for the new update.

sibenj said:
I'm on Lollipop, but Rooted. Will this update take away root by any chance?
Click to expand...
Click to collapse
I just updated via the OTA method on AT&T. Rebooted twice. I still have root (verified by Root Checker). Here's my About page:
Here's the root checker pic:
I now have OC2. Update OTA with confidence!
I originally rooted OC1 (Lollipop) by following the Root/OC1 method.
EDIT: I just checked for stagefright vulnerability (via Stagefright detector). It reports that my device is NOT VULNERABLE. Nice.
I took the chance because this site has helped me in sooo many ways. It's the least I could do. Thanks everyone.

I'm rooted and my update failed at 26%
Sent from my SAMSUNG-SM-N900A using Tapatalk

Update failed for me at 25% too. I'm rooted OC1.

Does this update do more than just fix the stagefright exploit?
If not, then kmokhtar already posted a flashable update fix for stagefright which works great.

Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...

Why is this 'update' 5.0? I could have sworn it was just up to 5.1.1

KestrelX said:
Could you post a link to that? I have been unable to find it via xda search, google search, browsing in note 3 forums...
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...stagefright-vulnerability-fix-note-3-t3175087

Can confirm that the update worked for me on rooted OC1, now shows OC2 and I retained full root on my phone.

ATT Ota file
https://mega.nz/#!TdE02KwJ!m4pkNivN9q2ZB7hGuXFiq872UoB8D-F-QpiPVX4sWI0

mine worked I am still rooted no problems no failure

peterson65 said:
mine worked I am still rooted no problems no failure
Click to expand...
Click to collapse
Those like me who have installed modded apps like S6 and have mixed in deodexed files, the OTA will fail. the OTA installer MD5 checks the system files and if any fail it will abort the Update. Any deodexed system files will also abort the Update
How to updated to OC2 if your OTA failed
1. Download and unzip and copy this Folder to OC1 stock root backup to your TWRP backup folder,
\TWRP\BACKUPS\0b70b440\N900A_OC1_Lollipop_Stock_Rooted_Backup
2. Copy OC1 kernel recovery installer to your sdcard SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
*** You can also go ahead and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk and NC2 Flasher to your sdcard ***
3 Download the OC2 OTA 2400258.cfg
rename the 2400258.cfg OC2 to 2400258.zip and copy to your sdcard
4 Install the OC1 backup,
N900A_OC1_Lollipop_Stock_Rooted_Backup.zip
5. Install OC1 Kernel
SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip
6. (I did a factory wipe , but Warning you will loose UserData settings and Apps you installed) You might try without but if you had a custom SystemUI and Touchwiz as I did it might FC because you have setting in Userdata pertaining to the Custom apps that you will over write with the OC1 backup.
7. Select Reboot and then select Recovery to boot to stock recovery and install as a update from external storage. mine installed with no issues.
8. To get safe strap back working Download and copy Safestrap-HLTEATT-NC2-3.75-B03[1].apk to sdcard (if you have not done yet)
9. Download and copy NC2 Flasher by benwaffle
10. Install Safestrap-HLTEATT-NC2-3.75-B03, run app and install recovery ( do not press reboot to recovery, it will only take you to stock recovery)
11. Install NC2 Flasher app and then use it to boot to recovery.
12. Do a backup of your new OC2
Now you can customized and do what you want