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
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.
Hi all,
I have a stock S3 which has downloaded a 87.46 MB update though OTA.
But when rebooting for installation, it says that signature check has failed and if I confirm installation anyway, it is aborted shortly.
Then I tried to update through Kies (in fact I am not sure it is the same file as OTA has no particular name) and my S3 get stuck on the downloading page.
So the only way to get out of this, is to remove battery as advised by Kies after a long time.
I have also been advised to install the OTA downloaded file directly in recovery mode, but I can't find the file in /cache. The folder is empty.
Does anybody know what can be done ?
Limerick_fr said:
Hi all,
I have a stock S3 which has downloaded a 87.46 MB update though OTA.
But when rebooting for installation, it says that signature check has failed and if I confirm installation anyway, it is aborted shortly.
Then I tried to update through Kies (in fact I am not sure it is the same file as OTA has no particular name) and my S3 get stuck on the downloading page.
So the only way to get out of this, is to remove battery as advised by Kies after a long time.
I have also been advised to install the OTA downloaded file directly in recovery mode, but I can't find the file in /cache. The folder is empty.
Does anybody know what can be done ?
Click to expand...
Click to collapse
Look on www.sammobile.com/firmware for your rom and flash it with Odin 3.04, See item 2 and 3 in my siganture. First shutdown Kies, also in windows task manager.
Thanks but I must confess that I am not able to find the 87.46 MB file which is downloaded through OTA.
How can to be sure to take the good file ?
Limerick_fr said:
Thanks but I must confess that I am not able to find the 87.46 MB file which is downloaded through OTA.
How can to be sure to take the good file ?
Click to expand...
Click to collapse
No, look for the whole file on sammobile.
So it is really impossible to update first with this file ?
I would rather try first with this one, especially because I wouldn't like to reinstall everything right now.
And even if I take the whole file, I don't even know which belongs specially to my S3...
Limerick_fr said:
So it is really impossible to update first with this file ?
I would rather try first with this one, especially because I wouldn't like to reinstall everything right now.
And even if I take the whole file, I don't even know which belongs specially to my S3...
Click to expand...
Click to collapse
What you could try is a data/factory reset and wipe cache in recovery, and try again. Hold volume up, menu botton an d power button to get into recovery.
gee2012 said:
What you could try is a data/factory reset and wipe cache in recovery, and try again. Hold volume up, menu botton an d power button to get into recovery.
Click to expand...
Click to collapse
Will I loose anything doing this reset ? Do you mean data or factory reset ? It is the same ?
Woah woah, not so fast.
Are you rooted? If so, ota don't work when rooted. You need to get back to stock recovery not cwm.
If you are looking in the cache folder you are supposed to let the download finish, then delay the update taking action. Then You'll will find the update .
Sent from my GT-I9300 using xda app-developers app
kofiaa said:
Woah woah, not so fast.
Are you rooted? If so, ota don't work when rooted. You need to get back to stock recovery not cwm.
Click to expand...
Click to collapse
Yes I am rooted but I have been told that it was possible anyway.
I also tried to temporary unroot and aked if SuperSU could do it. Had no answer about it and the possibility to come back to root after updated.
If you are looking in the cache folder you are supposed to let the download finish, then delay the update taking action. Then You'll will find the update .
Click to expand...
Click to collapse
It's exactly what I did but no file in /cache folder :silly:
Okay, now I have unrooted my phone with SuperSU, reboot and redownload again this 87.46 MB file.
Before installing it (choosing a 3 hours delay), I went to /cache with Explorer+ (AntTek doesn't let me go to that folder because I don't have permission anymore) and there is still any file inside.
So I try to install with the normal process and still have the signature check failed and the installation aborted.
I really don't know what's going on with this update. After at least 12 downloads, the file has always the same size, but I can't access to it...
Download the full file from sammobile.com / samfirmware.com and flash it through Odin as already advised.
There is absolutely no difference to flashing the OTA, only that OTA are smaller since they do not include the full firmware but only the differences to your old one.
Yes, okay I agree.
But I don't know which file to download corresponds to that OTA update.
And most of all, I guess this OTA won't need me to re-install all my apps and setup (maybe I am wrong about it), and then wonder if it won't be the case if I update and install the full ROM (which I confirm, I don't know which it is...).
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
I really like the way my OneMax w/verizon is and am not really interested in updating. The automatic firmware downloads is eating up my data daily. I just accepted to install it so it would stop, but it won't install due to error (it's a rooted device). I have S-Off on the phone right now and used the SuperSu unroot feature to try and let the update do it's thing just so it would stop downloading. Now, the root checker apps say I'm not rooted (but i think i still am). I tried the virtuous manual stock update but it gives me a installation aborted message while in recovery mode. Any help would be appreciated!
I think you need to have stock recovery & stock rom installed to accept the ota.
jerrycycle said:
I think you need to have stock recovery & stock rom installed to accept the ota.
Click to expand...
Click to collapse
so i have to fully unroot, update my phone then root again?
FrankieTheSqueeler said:
so i have to fully unroot, update my phone then root again?
Click to expand...
Click to collapse
Yes, if you want the update you will.
one last question, my device won't pop up on ABD devices on my PC anymore. Am I still rooted?
FrankieTheSqueeler said:
one last question, my device won't pop up on ABD devices on my PC anymore. Am I still rooted?
Click to expand...
Click to collapse
you only need to have stock recovery installed AND 100% stock system files. no system mods whatsoever.
assuming you enabled USB debugging under the developer options on the phone....you may need to update your version of adb/fastboot.
The root question....are you s off? If so that question is irrelevant as you only need to flash a custom recovery and flash the latest su zip from there to root any ROM...even the stock ota.
Sent from my SM-T320 using Tapatalk
dottat said:
you only need to have stock recovery installed AND 100% stock system files. no system mods whatsoever.
assuming you enabled USB debugging under the developer options on the phone....you may need to update your version of adb/fastboot.
The root question....are you s off? If so that question is irrelevant as you only need to flash a custom recovery and flash the latest su zip from there to root any ROM...even the stock ota.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply!
Yeah I have S-off on the phone. I will update the ADB version and retry. I don't know why I thought the su would be able to do a one-click unroot. All it ended up doing was just confusing me. I'm new to rooting and flashing, and it's fun figuring these things out. You guys are really helpful around here. I'll look for a tutorial on how to flash a custom recovery.
UPDATE 05/28/15 This works fine without doing the xposed part on Lollipop. No speed issues. It may be totally unnecessary now but I am not going to retry it to see. It may once again become necessary to follow these instructions when we get xposed for lollipop.
There are a number of threads about these two topics, I am going to consolidate my findings here.
First off root works great on the Sprint variant, secondly so does Xposed with S-Health and private mode. You just have to be careful how you set them up. There have been a lot of posts about freezing S-health and Private mode then clearing data but from my experience that is hit or miss. There are four basic steps to getting everything working and it should be done from a factory reinstall of software. The files you will need are in the following threads/links
Chainfire Autoroot - http://autoroot.chainfire.eu/
Chainfire File Link - http://download.chainfire.eu/617/CF-Root/CF-Auto-Root/CF-Auto-Root-tbltespr-tbltespr-smn915p.zip
Xposed - http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Xsecure - http://forum.xda-developers.com/xposed/modules/app-xshealth-bypass-secure-storage-t2878708
Teamwin Recovery - http://www.techerrata.com/browse/twrp2/trltespr
Root using Chainfire autoroot for Sprint it will fail just pull the battery and boot to download to install the teamwin recovery (buttons HOME, VOLUME DOWN, AND POWER) boot to recovery then install supersu. Before leaving recovery set the screen timeout off and lower the brightness to 10.
Skip past Google and Samsung setup. You can fill out the first and last name screen (only opportunity to name phone, first boot).
Download and install Xposed (not Wanam) download and install XSecure Health module install Xposed framework reboot
Activate Xsecure Health module reboot
Clear Data for Health Service and S-Health reboot
Run Private mode and set up, run S-Health and setup.
Setup your Google and Samsung accounts
If you do these steps exactly without doing anything else I can promise you will have a rooted Sprint version with Xposed, Shealth, and private mode working. When I say exactly I am serious there are a lot of things that can/will mess you up like
Signing into google or samsung on reboot after installing factory software
Starting private mode before setting up xposed
Shortcutting by doing a factory reset instead of a factory software reinstall
Restoring your data Nandroid backup (Use Titanium etc for a program by program reinstall of apps)
BTW the problem here is a little bit deeper than uninstall xposed everything works. There is a something that is changed in the software with either xposed or wanam that can permanently kill private mode until you do a factory install. At the moment I am doing Nandroids before any change I make in Xposed.
worked like a charm. Thank you very much.
blackinjun said:
Root using Chainfire autoroot for Sprint it will fail just pull the battery and boot to download to install the teamwin recovery
Click to expand...
Click to collapse
Is it absolutely necessary to install the custom recovery to achieve root? I only ask because I prefer to leave the stock recovery
Sent from my SM-N915P using XDA Free mobile app
metal666fukhead said:
Is it absolutely necessary to install the custom recovery to achieve root? I only ask because I prefer to leave the stock recovery
Sent from my SM-N915P using XDA Free mobile app
Click to expand...
Click to collapse
Sorry it is because the SU has to be installed outside of the system. There may be a way to then use TWRP or CWM to reinstall the stock recovery but I have not researched that.
Thanks blackinjun for this, I just got a Sprint variant of the Note Edge. I believe that I'm on NK1, it's been a while since I rooted a device, last one was about 2 years ago on my Galaxy S4. Will try it this weekend.
blackinjun said:
Sorry it is because the SU has to be installed outside of the system. There may be a way to then use TWRP or CWM to reinstall the stock recovery but I have not researched that.
Click to expand...
Click to collapse
@metal i now think it may be better to keep the custom recovery. Ive found that when su says it needs an update it asks to reboot ro twrp or cwm to update. I have twrm and it worked flawlessly.
Sent from my SM-N915P using Tapatalk
@Hired no prob
Sent from my SM-N915P using Tapatalk
worked for me as well just like you said..one problem im seeing though..well not sure if it matters..but while makeing my back of stock system,i see in red letters cant mount cace several times,but it completes the back up,and says sussefull..im backing up to my external sd card..i flashed the super user zip first before back up,flashed latest zip,hope this diddnt matter,did you mean to let twrp install it?..or ok to flash the zip?..anyhow,should i worry about the red letters 'cant mount cacge'??...i dont like it when i see any red letters while in recovery,just looks bad to me,like something is wroung...
blackinjun said:
@metal i now think it may be better to keep the custom recovery. Ive found that when su says it needs an update it asks to reboot ro twrp or cwm to update. I have twrm and it worked flawlessly.
Sent from my SM-N915P using Tapatalk
Click to expand...
Click to collapse
I have a client that I rooted their Note Edge but they really want Stock Recovery. Do you know how to put stock recovery back on there?
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
sand1303 said:
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
Click to expand...
Click to collapse
Download the zip file not the IMG.tar
Is it possible to do this. If my phone is already rooted?
I randomly found a YouTube video they walked me through rooting my phone before I knew shealth would have not work. This was a couple months ago I guess. So I'd like to get it back. Though doing factory reset isn't something that I'd prefer to do. But if it comes to it.
I'd assume just follow the rest of the steps in your tutorial?
sand1303 said:
what am i doing wrong. i download the tar file for twrp but it won't show up when i open the odin because it is showing up as a .img file. if i just change it to .tar it fails
Click to expand...
Click to collapse
You didn't unzip it right? Make sure you download the one with the .tar extension
ya thats what i was doing. i downloaded the .tar and unzipped it. flashing it without unzipping it worked fine
DevXen said:
Is it possible to do this. If my phone is already rooted?
I randomly found a YouTube video they walked me through rooting my phone before I knew shealth would have not work. This was a couple months ago I guess. So I'd like to get it back. Though doing factory reset isn't something that I'd prefer to do. But if it comes to it.
I'd assume just follow the rest of the steps in your tutorial?
Click to expand...
Click to collapse
this trick will work if your already rooted. Clear your D. Cache and cache and start from the download/install xposed portion of the instructions. This is what I ended up doing and haven't had any issues at all.
For those who have moved to lollipop has anyone tried this method
Sent from my SM-N915P using Tapatalk
+1, Would like to know how to root now that I have Lollipop............links, instructions, etc.
Same process as rooting kk i had no probl3ms with s health or private mode
Sent from my SM-N915P
Which method in Post #1 did you use?
Root using chainfire odin twrp ,xposed does not work on lolipop,so no other steps.
Sent from my SM-N915P