Related
I know i cannot install recovery and custom rom on this baseband yet, so my question is. Is it possible to root , and then install titanium to remove the bloats ? will doing this damage my phone when i want to factory reset it later ? . thank you
You can root. But do not delete the bloat. Only freeze with Titanium Backup
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
so when i need to factory restore , i have to unfreeze them ?
sjhotwings said:
so when i need to factory restore , i have to unfreeze them ?
Click to expand...
Click to collapse
Depends on which apps your freezing/considering bloat. Its probably safer to unfreeze first before you reset in the event you accidentally freeze something that is required for the phone to function properly. Heres a list, BUT I didnt see which firmware they were using.
http://forum.xda-developers.com/showthread.php?t=2265296
Please read forum rules before posting
Questions and Help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
should have posted this in the MF3 question and answers thread 3 post down...may get more help...
sjhotwings said:
I know i cannot install recovery and custom rom on this baseband yet, so my question is. Is it possible to root , and then install titanium to remove the bloats ? will doing this damage my phone when i want to factory reset it later ? . thank you
Click to expand...
Click to collapse
If you root on MF3 then your stock recovery will be corrupted. Factory reset through the phone will not work and make your phone in bootloop. There is no ODIN/factory reset at this time. So please be careful
Your best bet if you want to root is to carefully know what you're doing.
As for your other question if it's possible. Yes, it is possible to root but read above as I have warned you. Since you can root on MF3, you will also be able to install titanium backup to freeze the bloats. Do not remove/uninstall ANY of the bloats in case something goes wrong.
If you choose to unroot later: http://forum.xda-developers.com/showthread.php?p=45340743#post45340743
Good luck
Phewww..i followed the link and got the phone unrooted. So i guess i can factory restore now ? correct ? haha thanks
I unrooted my S4 before sending it back for a warranty exchange. I factory reset it and it worked fine.
Sent from the other side of the Milky Way with my S4.
mrro82 said:
I unrooted my S4 before sending it back for a warranty exchange. I factory reset it and it worked fine.
Sent from the other side of the Milky Way with my S4.
Click to expand...
Click to collapse
thank you
"If you root on MF3 then your stock recovery will be corrupted."
haremmon said:
If you root on MF3 then your stock recovery will be corrupted. Factory reset through the phone will not work and make your phone in bootloop. There is no ODIN/factory reset at this time. So please be careful
Your best bet if you want to root is to carefully know what you're doing.
As for your other question if it's possible. Yes, it is possible to root but read above as I have warned you. Since you can root on MF3, you will also be able to install titanium backup to freeze the bloats. Do not remove/uninstall ANY of the bloats in case something goes wrong.
If you choose to unroot later: http://forum.xda-developers.com/showthread.php?p=45340743#post45340743
Good luck
Click to expand...
Click to collapse
I have been using CM as my OS since around the first stable release. I am now on 10.2 JB 4.2.2 Yet when I go in and look at my About Phone it says MF3. I have installed root for about a week and all was well and working with CWM (corrected) recovery. I even upgrade to a later version (corrected). Then some app (I can't remember which unfortunately) put on a different recovery with tiny letters - the purpose of which so it can script a full install so I didn't have to do it every step myself. When it installed it, I encountered the horrific blue letters of "Booting Recovery..." and it will not get past that.
I can't load any other recovery no matter what method tried, and I have tried many, and many different recoveries. I think I found out after installing the apk from the verizon section SAFESTRAP program some things. First there appears to no way to delete the cache partition. Both the cache and the recovery partitions can be empty. The recovery partition is not always empty but usually that is the case.
I have the sinking feeling I am the victim of what you said at first "If you root on MF3 then your stock recovery will be corrupted." But I dont see how this is possible considering I had CM 10.2 4.2.2 (corrected) when root was installed. But my symptoms fit what you have said above. Can you explain a lot more about what this is about and and details inside the phone as to what is known so far? I have a MS in CS so I have a good background, even though I am very limited on what I can do on computers today. Details!
I am willing to do most anything to get back to a starting point.
HP
heartspeace said:
I have been using CM as my OS since around the first stable release. I am now on 10.2 JB 4.2.2 Yet when I go in and look at my About Phone it says MF3. I have installed root for about a week and all was well and working with Rouge recovery. I even upgrade to 1.5.0 Rouge. Then some app (I can't remember which unfortunately) put on a different recovery with tiny letters - the purpose of which so it can script a full install so I didn't have to do it every step myself. When it installed it, I encountered the horrific blue letters of "Booting Recovery..." and it will not get past that.
I can't load any other recovery no matter what method tried, and I have tried many, and many different recoveries. I think I found out after installing the apk from the verizon section SAFESTRAP program some things. First there appears to no way to delete the cache partition. Both the cache and the recovery partitions can be empty. The recovery partition is not always empty but usually that is the case.
I have the sinking feeling I am the victim of what you said at first "If you root on MF3 then your stock recovery will be corrupted." But I dont see how this is possible considering I had CM 10.2 4.2.1 when root was installed. But my symptoms fit what you have said above. Can you explain a lot more about what this is about and and details inside the phone as to what is known so far? I have a MS in CS so I have a good background, even though I am very limited on what I can do on computers today. Details!
I am willing to do most anything to get back to a starting point.
HP
Click to expand...
Click to collapse
How do you have cm 10.2 4.2.1? That doesn't make any sense.
heartspeace said:
I have been using CM as my OS since around the first stable release. I am now on 10.2 JB 4.2.2 Yet when I go in and look at my About Phone it says MF3. I have installed root for about a week and all was well and working with Rouge recovery. I even upgrade to 1.5.0 Rouge. Then some app (I can't remember which unfortunately) put on a different recovery with tiny letters - the purpose of which so it can script a full install so I didn't have to do it every step myself. When it installed it, I encountered the horrific blue letters of "Booting Recovery..." and it will not get past that.
I am willing to do most anything to get back to a starting point.
HP
Click to expand...
Click to collapse
Yea jd and I are confused.
Just to make sure you are on our train, are you sure it says "1337UCUAMF3" under Baseband Version in the 'About device' and not "1337UCUAMDL"?
haremmon said:
Yea jd and I are confused.
Just to make sure you are on our train, are you sure it says "1337UCUAMF3" under Baseband Version in the 'About device' and not "1337UCUAMDL"?
Click to expand...
Click to collapse
I think he's trolling. He says he has 3 different firmware on his phone.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
He even mentions rouge recovery. Non existent on our device.
Sent from my GT-I9505G using Tapatalk 2
Sorry for the typo!
jd1639 said:
How do you have cm 10.2 4.2.1? That doesn't make any sense.
Click to expand...
Click to collapse
Sorry that is 4.2.2 - a typo.
I have CM 10.2 JB 4.2.2
---------- Post added at 12:42 AM ---------- Previous post was at 12:40 AM ----------
jd1639 said:
I think he's trolling. He says he has 3 different firmware on his phone.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I am not trolling. I have a solid past on many forums. A Recovery is not the same as a firmware. I do admit to one type.
---------- Post added at 12:56 AM ---------- Previous post was at 12:42 AM ----------
Febby said:
He even mentions rouge recovery. Non existent on our device.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Rouge Recovery is available for Xoom, which I also have. Sorry, I crossed paths there and got them confused in the name of the recovery program. The recovery program was clockworkmod with with touch.
HP
Picture of About Device for Not Nice Skeptical Types & Helpful Types
heartspeace said:
Sorry that is 4.2.2 - a typo.
I have CM 10.2 JB 4.2.2
---------- Post added at 12:42 AM ---------- Previous post was at 12:40 AM ----------
I am not trolling. I have a solid past on many forums. A Recovery is not the same as a firmware. I do admit to one type.
---------- Post added at 12:56 AM ---------- Previous post was at 12:42 AM ----------
Rouge Recovery is available for Xoom, which I also have. Sorry, I crossed paths there and got them confused in the name of the recovery program. The recovery program was clockworkmod with touch.
HP
Click to expand...
Click to collapse
Check out attachment for About Device Info.
First, cm 10.2 is android 4.3. But it really doesn't matter because your on mf3 firmware. You can't flash a recovery or rom.
jd1639 said:
First, cm 10.2 is android 4.3. But it really doesn't matter because your on mf3 firmware. You can't flash a recovery or rom.
Click to expand...
Click to collapse
I guess I got confused with all the numbers I'm sorry about that guys. When did AT&T sneak mf3 on to my phone considering I have had custom OS is on here since I remember?
heartspeace said:
I guess I got confused with all the numbers I'm sorry about that guys. When did AT&T sneak mf3 on to my phone considering I have had custom OS is on here since I remember?
Click to expand...
Click to collapse
Can you still boot into a custom recovery?
Total Noob here as evident in this being my first post, but googling about how to NOT installl this Kit Kat update that has popped up on my Verizon Note 3 today has brought me here.
Is there any way I can disable this update from happening? I have heard great things about rooting and custom ROMS, and have heard that updating may jeopardize this.
So can I turn off Verizon's ability to update my phone? I delayed this, but my Note 3 wants to install the files it downloaded at 2 a.m.
Can someone give me a crash course to help me, and/or a quick way to prevent this?
Many Thanks.
Step 1 - Root your phone
hugenut said:
Total Noob here as evident in this being my first post, but googling about how to NOT installl this Kit Kat update that has popped up on my Verizon Note 3 today has brought me here.
Is there any way I can disable this update from happening? I have heard great things about rooting and custom ROMS, and have heard that updating may jeopardize this.
So can I turn off Verizon's ability to update my phone? I delayed this, but my Note 3 wants to install the files it downloaded at 2 a.m.
Can someone give me a crash course to help me, and/or a quick way to prevent this?
Many Thanks.
Click to expand...
Click to collapse
This method has worked for me twice. Latest was today:
youtube.com/watch?v=ukajWoxI3Tg&index=12&list=PLSQtCJEhU8pillzM7CZlSqFwApt7tKeWV
SKIP ALL THE STUFF ABOUT ODIN AND FLASHING FIRMWARE!!!! If you are stock JB, you don't need to do this part.
Then to get all the Chinese stuff off your phone, follow this tutorial:
youtube.com/watch?v=L5ebYM9CDkI&index=13&list=PLSQtCJEhU8pillzM7CZlSqFwApt7tKeWV
Finally, Install titanium backup, and freeze the program that is trying to force and over the air update. I came to the forum looking for the name of that file. Best I can find so far is: LocalFOTA v2_1308_1_1 -- but there my be others. Come back to the forum when you're rooted and search for it.
Best of luck!
hugenut said:
Total Noob here as evident in this being my first post, but googling about how to NOT installl this Kit Kat update that has popped up on my Verizon Note 3 today has brought me here.
Is there any way I can disable this update from happening? I have heard great things about rooting and custom ROMS, and have heard that updating may jeopardize this.
So can I turn off Verizon's ability to update my phone? I delayed this, but my Note 3 wants to install the files it downloaded at 2 a.m.
Can someone give me a crash course to help me, and/or a quick way to prevent this?
Many Thanks.
Click to expand...
Click to collapse
The best way to not update it, is to not update it. It isn't automatic. But after updating mine, my phone is better than ever. Noticeably faster transitions & animations, and great battery. Everything works better with 4.4.2 than it did with 4.3.
Sent from my SM-N900V using Tapatalk
BlastTyrantKM said:
The best way to not update it, is to not update it. It isn't automatic. But after updating mine, my phone is better than ever. Noticeably faster transitions & animations, and great battery. Everything works better with 4.4.2 than it did with 4.3.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Im having issues with gmail. With 4.3, if you zoomed and tapped it automatically fit to screen......now it doesnt line wrap.......cant find a single way to fix, ergo my visit here to xda Are you having any issues with line wrap since updating? I know with the browser google purposely turned that off with their webview, but i didnt know that extended to gmail
wickets said:
Im having issues with gmail. With 4.3, if you zoomed and tapped it automatically fit to screen......now it doesnt line wrap.......cant find a single way to fix, ergo my visit here to xda Are you having any issues with line wrap since updating? I know with the browser google purposely turned that off with their webview, but i didnt know that extended to gmail
Click to expand...
Click to collapse
I don't use Gmail, so I don't know if it's working or not. I'm using Mailbox and it does have that feature and it works. Even has a multi-level zoom w/ text wrapping.
Sent from my Nexus 7 using Tapatalk
BlastTyrantKM said:
I don't use Gmail, so I don't know if it's working or not. I'm using Mailbox and it does have that feature and it works. Even has a multi-level zoom w/ text wrapping.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes, mailbox is fantastic and it does have the autofit feature........unfortunately its gmail only so if you have an outlook account etc you cant use it
thanks for the input....much appreciated
hugenut said:
Total Noob here as evident in this being my first post, but googling about how to NOT installl this Kit Kat update that has popped up on my Verizon Note 3 today has brought me here.
Is there any way I can disable this update from happening? I have heard great things about rooting and custom ROMS, and have heard that updating may jeopardize this.
So can I turn off Verizon's ability to update my phone? I delayed this, but my Note 3 wants to install the files it downloaded at 2 a.m.
Can someone give me a crash course to help me, and/or a quick way to prevent this?
Many Thanks.
Click to expand...
Click to collapse
The only way you can really stop it is to root and delete a file called sdm 1.0. That is the update checker. But if you are going that far you might as well install a custom rom. There are several good kk roms available now. The biggest thing to keep in mind is that if you ever want to root, you can't take the ota. There will probably never be a root method for the ota version. The leaked nc2 build is kk that is rooted by default and is the base for all available kk roms.
Sent from the magical land of Baja(ROM)
---------- Post added at 07:18 PM ---------- Previous post was at 07:13 PM ----------
If you need detailed instructions on rooting and upgrading, check out this thread http://forum.xda-developers.com/showthread.php?t=2740466
This guy is awesome and has the best instructional threads for those in need
Sent from the magical land of Baja(ROM)
Tidewater said:
The only way you can really stop it is to root and delete a file called sdm 1.0. That is the update checker. But if you are going that far you might as well install a custom rom. There are several good kk roms available now. The biggest thing to keep in mind is that if you ever want to root, you can't take the ota. There will probably never be a root method for the ota version. The leaked nc2 build is kk that is rooted by default and is the base for all available kk roms.
Sent from the magical land of Baja(ROM)
---------- Post added at 07:18 PM ---------- Previous post was at 07:13 PM ----------
If you need detailed instructions on rooting and upgrading, check out this thread http://forum.xda-developers.com/showthread.php?t=2740466
This guy is awesome and has the best instructional threads for those in need
Sent from the magical land of Baja(ROM)
Click to expand...
Click to collapse
That worked for me... finally a fix thanks so much
Sent from my SM-N900V using XDA Premium 4 mobile app
gotghost29 said:
That worked for me... finally a fix thanks so much
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are soooo very welcome
Sent from the magical land of Baja(ROM)
I just followed the guide to flash back to NCG kernel, reroot and flash NE9 kernel. So far everything is lovely except for after a phone call I always get an error: "Unfortunately, Context Service has stopped." Any idea what this is and how to fix it?
wrongway213 said:
I just followed the guide to flash back to NCG kernel, reroot and flash NE9 kernel. So far everything is lovely except for after a phone call I always get an error: "Unfortunately, Context Service has stopped." Any idea what this is and how to fix it?
Click to expand...
Click to collapse
Are you on a custom ROM, if so witch one?
Misterxtc said:
Are you on a custom ROM, if so witch one?
Click to expand...
Click to collapse
No, stock ROM. Never flashed a ROM, Knox 0x0.
I believe I found a solution. I have installed Greenify, but it was disabled under my accessibility services. Apparently that's how it is set by default after downloading it, even when rooted. I turned Greenify on under Settings < Accessibility < Greenify and rebooted my phone. I made a few calls and received one and no more Context Service Errors for me. I am quite curious as to what Context Services are and why Greenify would cause those errors as I do not see any information on it relating to the S5, so if anyone has any idea why this happens, feel free to shed some light on it.I wonder also if Context Services are safe to freeze..
Problem returned with a vengeance after several reboots. Now I boot the phone sometimes and there are no errors, other times and constant FCs. Could I have somehow gotten a corrupt Context Service apk when I flashed to Stock Odin, or the NCG or NE9 kernels? Anyone know what Context Services actually is and if it's safe to freeze if there isn't a fix? I found a similar thread for someone having this issue on the At&T variant and someone replied that his Context Service apk was possibly corrupt and that he PM'd him a new one. http://forum.xda-developers.com/att-galaxy-s5/help/context-services-stopped-t2837895/post54614539 If this is something that is possible to do, I would greatly appreciate it.. I've looked both on Google and here and there seems to be very little info on Context Services, so I do not wanna freeze something that's unsafe to freeze, but these errors are killing me. Any help will be greatly appreciated.
Edit: Totally removed Greenify and the problem is gone. I would love to use Greenify, but I would like to know I can do so without causing issues. Does anyone know how Greenify would cause ContextService FCs?
Logcat
i have a logcat of the issue occurring, both by itself and induced via having my girlfriend call my phone. i took this to the xposed forum first and was told it appears not to be module related. if anyone can give me any input on this, i would really appreciate it
i thought it was just me.. however stock rom works fine for me its my custom build i get the fc on.. i dont have greenify in my rom so not sure if thats the root cause or not.. i will try something and report back
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 03:46 PM ---------- Previous post was at 03:29 PM ----------
ok so clearing data/cache doesnt help.. i also deleted it and pulled one from stock base pushed and set perms with no luck either.. ill keep searching but were not the only ones with this issue..
mines a deal breaker cuz it fcs after every call as well as i cant send sms lol
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
i thought it was just me.. however stock rom works fine for me its my custom build i get the fc on.. i dont have greenify in my rom so not sure if thats the root cause or not.. i will try something and report back
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 03:46 PM ---------- Previous post was at 03:29 PM ----------
ok so clearing data/cache doesnt help.. i also deleted it and pulled one from stock base pushed and set perms with no luck either.. ill keep searching but were not the only ones with this issue..
mines a deal breaker cuz it fcs after every call as well as i cant send sms lol
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
i've figured out if i try to install ANY modules by wanam, the issue occurs. greenify isn't the problem, i know that much. let me know if you find any progress and i''ll do the same for you.
wrongway213 said:
i've figured out if i try to install ANY modules by wanam, the issue occurs. greenify isn't the problem, i know that much. let me know if you find any progress and i''ll do the same for you.
Click to expand...
Click to collapse
i flashed back but can you by chance go to a rom it was working on? ive read somewhere that if you have it working then back it up with tibu then on new rom restore its data and it might fix it.. it doesnt work pullin from rom for some reason
Sent from my SM-G900V using XDA Free mobile app
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
so its always fcd since youve got the device?
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
wrongway213 said:
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
also theres a dif between stock slot and rom slot 1.. im on stock slot
Sent from my SM-G900V using XDA Free mobile app
No, since I flashed back to NCG, rerooted and flashed NE9 it's been happening. I've never flashed a rom, just rooted on stock slot in safestrap
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure if this will help but from what I've read ss has a problem when using a rom slot instead of the stock slot I've seen a lot of the rom devs change the procedure from using a rom slot to using the stock slot.
http://bit.ly/1brshoa
bad bone said:
I'm not sure if this will help but from what I've read ss has a problem when using a rom slot instead of the stock slot I've seen a lot of the rom devs change the procedure from using a rom slot to using the stock slot.
http://bit.ly/1brshoa
Click to expand...
Click to collapse
yeah i'm in stock slot, not rom slot. didn't mean to post that, but thank you anyways
Anyone know if a Nandroid backup from before I ever originally took the OTA, stock rooted NCG, would fix my problems, and more importantly, if it would trip Knox or not if I restored it via Safestrap?
I haven't read anywhere of someone trying it yet. I was wondering too good question
http://bit.ly/1brshoa
wrongway213 said:
Anyone know if a Nandroid backup from before I ever originally took the OTA, stock rooted NCG, would fix my problems, and more importantly, if it would trip Knox or not if I restored it via Safestrap?
Click to expand...
Click to collapse
lol read the many posts about it floating around.. i restored my ne9 rom just fine many times.. nothing we can do with the vzw s5 will trip knox at this time so dont know why you even mention it lol we cant flash bootloaders
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
lol read the many posts about it floating around.. i restored my ne9 rom just fine many times.. nothing we can do with the vzw s5 will trip knox at this time so dont know why you even mention it lol we cant flash bootloaders
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
plenty of posts saying safestrap won't trip knox, had not heard from anyone as to what restoring a nano would do until i specifically asked this question yesterday though... you referring to a certain thread containing these many posts? because until i asked, the safestrap thread even made NO mention of nano backups as they relate to knox...
Never had that but I did get documents have stop once an it never did it again not sure what was up with that ?
Is there an actual fix for the "Unfortunately, Context Service has stopped" error? I really made a stupid mistake yesterday and froze some system apps in Titanium Backup. At first I was getting a bootloop when the OS tried to load the apps and thought I was going to have to wipe data, but I used adb push to send the entire system/app folder to my phone (got the files/folder from my wife's phone who has the same phone on same ROM - I'm 90% sure it is the rooted KOT49K/ANCG build of Verizon GS5). This adb push allowed my phone to boot entirely, but now everytime I boot the phone up, I get the Contest Service error message. So I just backed up Contest Service 2.0.3 using Titanium Backup on her phone, then put the 3 files it created onto my phone and tried using Titanium to restore Context Service 2.0.3 to my phone but to no avail. I tried restoring app only and also restoring app+ data but the restore never completes in TB (ive changed TB to INDIRECT mode too) but it doesn't fix the problem. When I start the restore, it does stop the error message from constantly appearing but only until the next reboot.
So does anyone know how I can stop from getting this error message? I have another working Verizon GS5 on the same ROM at my disposal.
version N910PVPU2BOE1
276.98MB
Factory reset protection
Bug Fixes
http://www.androidpolice.com/2015/0...-galaxy-note-4-with-factory-reset-protection/
I'm downloading it now.
Already took it and re rooted lol
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
Cant use emotion kernel anymore
Oh we got hd calling too i love it
I've had HD calling since OB7...
Can I ask how you rooted your Note 4. Is there a guide or link that will walk me in steps.
I have Sprint Note 4 and would like to root (I don't care about custom ROM.. just want rooted so that I can remove some apps and use hotspot).
Thanks!!
Got it. Just need the stock tar in case I make an oopsy.
Can I ask how you rooted your Note 4. Is there a guide or link that will walk me in steps.
I have Sprint Note 4 and would like to root (I don't care about custom ROM.. just want rooted so that I can remove some apps and use hotspot).
Thanks!!
pbedard said:
Already took it and re rooted lol
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
Cant use emotion kernel anymore
Click to expand...
Click to collapse
It's all over the place. Cf auto root.
Updated this morning and now my camera keeps saying it stopped working [emoji34]booooo
Sent from my SM-N910P using Tapatalk
Clear caches and/or factory reset.
Can anyone who took the update confirm the lollipop hotspot still works?
http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163
I don't even use it but i like the idea of having it just incase.
Thank you
It breaks it
Mine works. I was rooted and flashed the stock tar. Took the update. Rooted again and my hotspot still works.
Can anyone else chime in on the Wifi hotspot hack? Does it break it or not for stock unrooted?
Itchiee said:
Can anyone who took the update confirm the lollipop hotspot still works?
http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163
I don't even use it but i like the idea of having it just incase.
Thank you
Click to expand...
Click to collapse
Stock Non-rooted N4, took the new OTA. Rebooted once, things are smooth. Hotspot still works.
I'm the guy who found that hotspot trick. I'm downloading the update now. After it installs, I'll test to see if hotspot still works, and I'll also check to see if you can still access/edit APNs via my previous method.
UPDATE: It still works, absolutely no change whatsoever in the process or results.
LOL. I was wondering how people were able to odin the stock tar then reroot and still have working hotspot. I know if you odin the stock Lollipop rom tar without first wiping everything you will have leftover data but other than that, all of the system & framework files get overwritten thus undoing any hotspot mod. So i'm baffled by these reports. Maybe some of you used a different method to hack hotspot?
tx_dbs_tx said:
LOL. I was wondering how people were able to odin the stock tar then reroot and still have working hotspot. I know if you odin the stock Lollipop rom tar without first wiping everything you will have leftover data but other than that, all of the system & framework files get overwritten thus undoing any hotspot mod. So i'm baffled by these reports. Maybe some of you used a different method to hack hotspot?
Click to expand...
Click to collapse
My guess is probably the Galaxy Tools way.
If there's one thing I learned..wait
If it aint broke, why fix it
Sent from my SM-N910P using Tapatalk
ibcenu said:
If there's one thing I learned..wait
If it aint broke, why fix it
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
That's a very good habit to have my friend Saves you 99.95 of all problem by "experimenting" or trying to make "improvements" LOL
why the heck well yeas it happened to me 2 Finally I recieved my killswitch. I never had TegraOTA update active...it happened just right after a regular reset with an recovery Image. .I am really sad now I have to apologize! I LOVED MY PYRO!....
This is just a warning keep on the custom side with your pyros! **** that stock Mellow!
Ill try my best to not cry..but heck...
cheers guys maybe someday I'll be back with another pyro!
love
bencozzy said:
My Pyro is stock I asked nvidia to whitelist the serial because it's a development device.
Click to expand...
Click to collapse
U had luck with your request?
bencozzy said:
They told me they did when I requested the Vulkan api build. I also never requested a replacement not sure if that plays into their decision making.
Click to expand...
Click to collapse
Uh, yeah. The whole killswitch process only starts when you fire up your replacement tablet for the first time & set up an internet connection.
That is the ultimate reason why you put your radios to Airplane before flashing, and even before booting, you flash the remove TegraOTA zip file in TWRP.... heck, even a clean flash would be good too.
deleted
daniyo27 said:
That is the ultimate reason why you put your radios to Airplane before flashing, and even before booting, you flash the remove TegraOTA zip file in TWRP.... heck, even a clean flash would be good too.
Click to expand...
Click to collapse
Removing the SIM if you've got the LTE version, clean flashing if using stock images & skipping the WiFi setup. Imo that's the best way to do it, you get all the time in the world to remove TegraOTA whichever way you're comfortable with.
It's honestly a bit sad that some people don't take the time to do this stuff properly.
Here is what I think happened: i had Recovery erased..you know why. So I were on stock with nethunter and suffered from random reboots. That's why I tried reflash it. Once the regular Recovery was installed i got Killswitch es ???*
NVM, just realized he did it through a manual flash, not OTA.
NVM again, I am bad at reading. So he flashed a recovery image then got the OTA after he rebooted. So again, why is Nvidia still pushing this update if they have known it was bricking devices since January.
deleted
Can you explain please all the steps you did until the kill? Ibinstalled 4.1 stock update from.nvidia site on my pyro. Before booting the os i deleted tegraota with the zip and erased recovery with fastboot. But i havent turned on the wifi yet.
Sent from my LG-E975 using XDA Free mobile app
deleted
So now you have the pyro on stock with the original update and connected to internet. But is killed?
Sent from my LG-E975 using XDA Free mobile app
---------- Post added at 08:29 AM ---------- Previous post was at 08:18 AM ----------
The problem is that i cant install a custom rom
Sent from my LG-E975 using XDA Free mobile app
deleted
Can you tell me please which version of xposed? Id like to unstall it. I also freezed with titanium almost all nvidia apps and services. If the kill switch is an update sent by nvidia servers, deleting tegra ota would be safe, and also the recovery, so nothing can be flashed. Did you check if the kill is triggered for your pyro?
Sent from my LG-E975 using XDA Free mobile app
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
So, if the kill is contained in the stock images and you were connected to internet while using the stock image, you would have been affected by the kill switch. But youbsay its working, so i think theres no kill in.the stocks
Sent from my LG-E975 using XDA Free mobile app
deleted
I installed 4.0.1 before the 4.1 and tablet worked (but never cinnected). Can you "system update" on your settings after flashing the nomoreota zip?
Sent from my LG-E975 using XDA Free mobile app
deleted
Its not green. Its the nirmal g updater. When.i.was stock 5.1.2 i deleted manually tegraota apk and "system update" on settings was disappeared. Maybe the g updater is another way to kill the tablet?
Sent from my LG-E975 using XDA Free mobile app
Is your pyro working now?
Sent from my LG-E975 using XDA Free mobile app
Yes?