Related
I installed the new OTA update earlier today and then did the one click mod.
Then installed CWM Recovery using the guide on this site.
Everything went perfectly the first try. I have ROM Manager installed also.
Browsing works fine.
When trying to download an app it errors out in the info bar and says, "Download was unsuccessful." Sometimes AppBrain will say connection error after opening.
Gmail app gives me a connection error, as does Google Talk.
I've tried clearing the data and cache for all these apps including the Download Manager and rebooting. I'm treading in unfamiliar waters and I'm not sure what to try next. I'd love some help please!
Was so excited that everything went flawlessly and now this...
I waited for the OTA update before rooting just so I'd be as legit as possible. I'm not sure if the root caused the problems or if flashing CWM caused the problems, so I've been trying to find a way to go in reverse and get rid of CWM, but I haven't found anything that's made sense yet. From what I gather I'd have to put the stock Recovery back, and I don't know how to do that. All I have is a ROM Manager backup that I performed after the CWM install.
I'm confused and I hope someone can point me in a safe direction.
Fixed itself. Glad I was patient enough not to try something stupid.
See, I was out of cell service while rooting. Once I got into 3g service this morning everything started working. Even turned airplane mode on and everything works via wireless now.
Haven't a clue why, but I'm thankful nonetheless. : )
phones been fine for 440 hours (uptime since last time this happened) - since i lost the virtual keys last time and had to use sonys software to reinstall everything.
now after a reboot this happened again. disabled all xposed mods and the menus returned but now with orbot and folder mount running i had endless reboots. only after uninstalling the other 2 apps did this stop.
anyone else had anything like this?
wish i had recovery - stupid win8 and locked bootloaders
sony update service with full wipe.
did that last time. 2 weeks later happened again. stopped when i made changes mentioned in OP
Looks like you've been using an incompatible Xposed module or possibly other mod(s). Install them one by one again and see what triggers the crash (if you feel like re-flashing your ROM again)
Btw, it's fully possible to unlock your bootloader using Win8. It's a little wonky, but it's possible (unless your bootloader is unlockable). Or you know, you can install Recovery for locked bootloaders, but you can't flash custom ROMs, but you can make NAND backups.
A little off topic: I installed uTorrent yesterday since i had to download a torrent, and after i was done with it and uninstalled it, my ZU crashed and rebooted. Once it booted up again it crashed again, and again and again. Luckily i had a NAND backup on my SD card, so that problem solved itself, but lesson learned; no uTorrent anymore.
"Fun" fact: This also happened with uTorrent on my Galaxy Note.
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
tommo123 said:
i thought that last time so after the last wipe i did just that. enabled them one by one and a reboot after each one.
very weird. all up an running again, same xposed modules running and no probs after a reboot.
i used utorrent on my note 2 and that was fine. very odd.
i really need to get around to getting a recovery going
Click to expand...
Click to collapse
Recovery is not a problem once you're rooted. Go to this thread, download and run the file, press "Oui oui, mademoiselle" or something like that and voila, you got Recovery. Easy peasy. It'll take you five minutes. Just remember to make a NAND backup once it's up and running. It's a life saver, as you already know.
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
tommo123 said:
ah, i kept this thread open
but was sure in another thread it mentioned problems with windows 8 as you have to disable driver signature verification or something.
Click to expand...
Click to collapse
Yup! Good going mate! I see you made it without any issues
So I got the compatibility patch on my LG-H901. Thinking nothing of it I agreed to install and reboot. Once I had done so, I now have the Yellow Boot Warning at every boot. And also a bunch of my system apps stopped working. Camera, Phone, Music ETC. I don't remember ever flashing a ROM that would trigger the warning seeing as how I got the update to 6.0.1 a few days before and hadn't done anything since. So I flashed back to stock with LGUP through KDZ Full Wipe, and the problems still persist. Now I'm complete stock and the compatibility update is waiting in the update center again. This is my first post and I'd really appreciate the help. (P.S Speakers won't work , and Google apps seem to not work properly either.)
I'm very new to the rooting community, and I'm well aware of all of the problems. I've messed around, and bricked my phone many times but always knew how to fix it by flashing the custom rom. I've did whole of April until I figured out the proper rooting my model's for 6.0.1 software, and the 7.1.1 software. I eventually got tired of repeating this process, so in May (after I properly rooted my device and everything worked perfectly) I backed up everything including my system in TWRP.
Now the problem is, after using the xui tuner from xposed installer a bit, my phone seemed working for a bit, and lockscreen worked, but it randomly kept restarting at the boot animation . I grew impatient and restarted my phone properly a couple times but it kept rebooting after I unlocked my phone or just waited at my lockscreen. I then started got scared that I damaged something in my system or software, so I went to use TWRP to restore my backup (which I also literally backed up on this Tuesday). It apparently was successful, until the bootlogo freezing and saying my kernal wasn't SEANDROID ENFORCING.
Then now, I kept reformatting my data and restarting but it wouldn't work, it kept failing. So I gave up, and flashed my stock rom. This worked, but I obviously lost all my data. So to possibly help someone, I want to list what I think could've been the problem. (Still new, so I may list alot of unlikely things. Also random order)
1. I didn't format my data before the first restore, thus it failing.
2. Improper backup, I either backed up unnecessary partions like radio, or TWRP just didn't backup properly.
3. My sd card, I had many problems with my sd card before doing this type of stuff, but it went away during may. During may however, I backed up my magisk modules to it too, but they didn't appear on TWRP. Meaning it may have stopped working again. It also deleted my root folder, where I held the magisk zip and uninstaller.
Now this could bring another problem, I was using Magisk and Xposed installer, while also having my stock framework, xposed framework, and sony framwork (this was to use remote play), and in result my phone couldn't handle it and the module from both Magisk and Xposed.
4. I backed up my system while using the ashyx encryption zip, meaning when TWRP restored encrypted files?
5? XUI Tuner, I modified too many things with the app and probably did something to to the root directory. (Most likely Unlikely)
6. I modified my build prop by adding more code like the android users function, and TWRP probably couldn't back that up so it restored wrong like in 2
7? I modified TWRP by using a custom theme in the recovery, making certain functions like backup and restore not work?
8. I was using an old version of TWRP, 3.0.2 instead of 3.2 because 3.2. However, this is because 3.2 didn't work with my phone, and neither did 3.1.
I now flashed the stock rom, and everything works again. I just have to re-root. I didn't lose much data really, and I backed up some stuff in samsung cloud anyway. I just wanted to make this thread so I can fix the problem properly in the future, in which someone else may need it too. This model of samsung phone really isn't popular in the community, so it really would be helpful to other people. The solution could also work for other J700 variants, especially J700T1 since it's the most similar.
P.S. This is also just a small thing to help people too. Rooting this model is actually pretty easy, there's just a catch for one version of it.
6.0.1 can easily be rooted, especially with autoroot. It's works well, and you don't have to lose anydata at ALL! However magisk is untested.
7.1.1 on the other hand does require to format it's data to work so you have to back up anything you want to keep.. Superuser for me made wifi and the flashlight inaccessible, so I had to use Magisk. Which worked fine. There are two different versions of this root though. (Tested Once) One is basically like how the stock rom and has the manual, mobile data quick setting, and battery settings. to get it, don't use ashyx encrptyion . The other is like how you got it your device and set it up normally, no manual or extra settings, and requires ashyx encryption for this. The one I used was the ashyx encrpytion, and I was fine using this method because I kinda already lost everything over and over so I didn't care (end of april).
Edit: Turns out the stock version happens when you flash the stock rom, then immediately flash a custom recovery, and formatting the data without launching the the phone. I think this happens because when you get your phone, and activate it with a carrier sim card it downloads the additional files for that carrier which allows and when you format the data it formats the carrier version instead of the default system on the phone.
I hope we can find a solution for the kernal problem, so other people can fix this properly.
I would also like to ask if someone can make a odin and TWRP flashable kernal file of both the 6.0.1 and 7.1.1 versions of the SM-J700 variants, but for now in this thread the J700T is fine, unless all variants have the same stock kernal. This could be a solution and very helpful.
I have a USA T-Mobile Samsung Galaxy J7 J700TUVU3BQK3 phone and Can someone give me links to where I need to download the firmware ROM for this phone & all the different software I would need to root this phone or modify-backup its operating system??? My computer operating system is windows and also does anyone know how to setup a multiple operating systems on a computer where u can choose to either boot to different versions of windows and lynux.?? Computer Lenovo Gaming Laptop & HP Pavilion Laptop.
After rooting my s9+ with the modified Magisk, my phone sometimes becomes unresponsive. I cannot identify any sort of trigger for this to happen, it just does. The AOD displays but does not update. The notification LED still blinks, but when I go to unlock the phone it freezes and I am forced to soft reset it. I am root with Magisk and have TWRP installed. I followed Max Lee's tutorial on how to root the S9+. Any ideas on why this is happening and how to fix it?
Hey, Did you have any luck with this, i am having the exact same issue?
having the same problem i followed Max Lee video and everything work fine until the phone started freezing
same issue on the G960F/DS....
wonder who can help us regarding with this issue.
For everyone having this freezing after rooting...attention to detail is absolute paramount, go back and re-read the twrp thread by jesec. For those (possibly those having freezing issues) who find that challenging, here is a snippet of jesec exact words..." Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection".
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
To reiterate...flash a custom kernel before root or be SCREWED
I'm not saying this is 100% u guys issue, but seems kinda likely?
can someone post links or steps on how to fix this freezing lock screen issue, i tried reading the threads but did not find anything, thanks
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
crs_dev said:
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
Click to expand...
Click to collapse
Can we flash this Elementalx over the N965F_Root_for_OEM_issue_devices/Magisk we already installed ?
I already installed the TWRP, No-verity opt encrypt and the N965F_Root_for_OEM_issue_devices package on my friend's 960F.
I would be really greatful if anyone could help me with this.
I had the same issue after having troubles initially getting Lineage flashed and working on my S9.
I removed Magisk, reset and it still was freezing after a lock.
I reflashed Lineage through TWRP and now all seems to be back to normal with no freeze after lock.
Possibly try the steps I did and see if they worked out for you.
hey guys, you solved the issue?
i experience same Problem..
Any one notice , this issue occurs after we apply lock screen password or biometric security. in my device i notice, when i apply lockscreen password or biometric lock my phone freeze. after i remove all lock and set default to swipe...its not freezing. anyone sees that
I solved the same issue (1 hour ago, so I hope it's fixed now) installing first:
ElementalX Kernel
and than installing:
G965_Root_for_OEM_issue_devices_V5 (the lastest available right now)
Following the instruction on the XDA Thread
Hope this can be helpfull to solve it
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
KevAngelo14 said:
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
Click to expand...
Click to collapse
What is the different in Soldie between Patched Kernel and ELS custom kernel?