Related
Hello,
I have some questions regarding full encryption and/or sd-encryption under JB:
I read, that encryption under ICS is an awefull experiance and especially combined with custom roms/recoverys often resultet in dataloss. Since the new policy at work would demand full encryption for private devices brought to work, i wonder, if encryption under JB delivers a better experiance or if i should use a secondary purpose just for work. I specially wonder, if:
encryption works now with custom roms/recoverys (e.g.: what happens if i encryptet my device and do a factory reset to flash a new rom)
flashing/backup routine works like usual (TWRP should be able to handel encryption on my HOX)
encryption makes any difference when connecting my device to my pc to manage sd-card data
the data stored on my device will really be safe or if this encryption is as poor as ms office encryption
encryption result in performance loss for games
Since i have no experiance with encryption on android, i woulde be very thankfull for any comment on this topic.
Cheers!
bump.
noone have encryptet a device yet? don't wanna brick my HOX (since we don't have S-OFF this might be a problem if something goes wrong)
bump again.
So, since noone knows about this, this thread can be closed i guess. Thanks.
I'm not sure about all your questions, as I've never encrypted my phone and used it for long enough to find out, but from what I've noticed, transfer speeds between the phone and computer are slower than normal when encryption is enabled.
Thanks for your repley.
This wouldn't be a problem, more interesting is the question if an rom update / new rom install is still possible. Since the sd-card is encryptet, i wonder, if it will still be accessible to a custom recovery. How did you install a new rom after encryption and did you loose your sd-data?
doumer said:
Thanks for your repley.
This wouldn't be a problem, more interesting is the question if an rom update / new rom install is still possible. Since the sd-card is encryptet, i wonder, if it will still be accessible to a custom recovery. How did you install a new rom after encryption and did you loose your sd-data?
Click to expand...
Click to collapse
I am using TWRP for flashing ROMs on my encrypted maguro. Problems started with latest Xylon v15 ROM only, i.e. phone freezes after entering encryption password.
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse
I upgraded from a rooted 4.4.2 using muniz instructions last night and using the DeOdexed ROM, and then used his batch DeBloater on Extreme to remove all the crap. The upgrade wiped my phone (not a bad thing, I wanted to start fresh), so I'm at a fresh starting point other than what is mentioned above. Thanks muniz btw, you're awesome.
From here I wanted to turn on Phone encryption, as an extra security measure. Encrypting the external SD card went fine, but encrypting the phone did not... It displayed the little encrypting android screen for a few seconds and then went black, button presses did nothing. After waiting over an hour I pulled the battery and restarted. I got informed that the encryption failed and the phone would be restored to factory default. No biggy, just back where I was an hour ago.
So the question is, before I try this all over again, does the encryption work with this custom ROM and debloated? Is there anything special I can do or might be doing wrong? And will this interfere with root or anything else I may want to install in the future?
Does anyone use the built in encryption with their android?
BeanBagKing said:
Does anyone use the built in encryption with their android?
Click to expand...
Click to collapse
You need to disable superuser, reboot phone, enable the encryption and then re-root. I did this and everything was working fine until one of my kids entered my pin wrong a few times in a row and the phone did a factory reset... I upgraded to OC1 rather than go through all the trouble again.
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.
HI to all
Strange behaviour with my phone. As title says, I cannot add PIN or fingerprint.
I have unlocked bootloader, flashed TWRP and rooted with Magisk 23. On Dev Settings OEM lock is enabled but I can switch it off if I want. It is not dimmed as it should be. I have checked bootloader unlock status via Fastboot - "fastboot getvar all" and it says (bootloader) unlocked: yes
Has anyone any idea why PIN or fingerprint cannot be added?
I have to say that I am bit frustrated with this phone, always something is not working as it should. Never know what tomorrow happens.
This my second One Plus Nord 2. First one I had 2 months, during that period of time it was 3 times at service. Once motherboard was changed. What they did other (2) times I do not know. And now this new one, which I got as replacement bec older sucks , is starting to suck too
Is metadata responsible for PIN or fingerprint? It holds keys for security, so maybe if I flash new metadata would it help/fix problems or is it device specific?
Any ideas, thank you
I had this exact same issue as well, and it seems to be linked to the way TWRP restores/saves the data partition in my case. My fix was to boot into recovery and wipe/reformat all data.
After a fresh wipe, my issues were resolved, but i had to manually redownload and setup all apps again. I did multiple tests and the issue would always come if i restored my data partition; whether i flashed it via TWRP or via fastboot. It's likely the way TWRP saves the data partition was my issue.
Zombnombs said:
I had this exact same issue as well, and it seems to be linked to the way TWRP restores/saves the data partition in my case. My fix was to boot into recovery and wipe/reformat all data.
After a fresh wipe, my issues were resolved, but i had to manually redownload and setup all apps again. I did multiple tests and the issue would always come if i restored my data partition; whether i flashed it via TWRP or via fastboot. It's likely the way TWRP saves the data partition was my issue.
Click to expand...
Click to collapse
HI and thank you for reply
Do you mean stock recovery? I have tried TWRP - format data, didn't help.
If you format data using TWRP my experience is that TWRP will uninstall itself in the process, so you'll boot into stock recovery after that anyway.
I would honestly suggest doing both. If you have TWRP, reformat and wipe using TWRP wipe. Next time you boot to recovery, it should be stock. Do another reformat+wipe on stock recovery. Should do the trick.
Never mind, I did not want to steal your topic. Open my own!
exis_tenz said:
Never mind, I did not want to steal your topic. Open my own!
Click to expand...
Click to collapse
hi. yes, we have different problem but i have to agree, always something strange happens with this phone. kinda sucks
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
exis_tenz said:
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
Click to expand...
Click to collapse
i had same too, 2 times service flashed stock back and 1 time change motherborad. now they gave me new one, but still prbs. am fed up too
exis_tenz said:
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
Click to expand...
Click to collapse
jis251 said:
i had same too, 2 times service flashed stock back and 1 time change motherborad. now they gave me new one, but still prbs. am fed up too
Click to expand...
Click to collapse
Funnily enough, both of your issues are caused by TWRP not flashing partitions correctly, at least from my testing.
In Jis's case, (RE: Current thread) it's because TWRP does not flash the DATA partition correctly, and prevents the phone from being able to set a lockscreen password (and therefore the Data partition cannot be encrypted). And without a lockscreen, the stockOS does not allow you to set biometrics such as fingerprints/face unlock, though theoretically in this case, both sensors work perfectly, it's a simple software restriction.
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Remember, @TheMalachite 's release of TWRP is an unofficial release and we're just glad to have it working at all. That said though, I wonder if TheMalachite is aware of these issues?
Zombnombs said:
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Click to expand...
Click to collapse
Thing is: I didn't flash ANYTHING in TWRP. It's a clean recovered stock rom done by an official OnePlus servicecenter.
Zombnombs said:
Funnily enough, both of your issues are caused by TWRP not flashing partitions correctly, at least from my testing.
In Jis's case, (RE: Current thread) it's because TWRP does not flash the DATA partition correctly, and prevents the phone from being able to set a lockscreen password (and therefore the Data partition cannot be encrypted). And without a lockscreen, the stockOS does not allow you to set biometrics such as fingerprints/face unlock, though theoretically in this case, both sensors work perfectly, it's a simple software restriction.
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Remember, @TheMalachite 's release of TWRP is an unofficial release and we're just glad to have it working at all. That said though, I wonder if TheMalachite is aware of these issues?
Click to expand...
Click to collapse
This is completely unrelated to TWRP itself. OxygenOS for Nord 2 use ColorOS base which is know to give such issues (Also happen with OPPO and Realme devices on ColorOS and RealmeUI)
exis_tenz said:
Thing is: I didn't flash ANYTHING in TWRP. It's a clean recovered stock rom done by an official OnePlus servicecenter.
Click to expand...
Click to collapse
Then they messed up your persist image and/or calibration data in some way or fashion. Take it back and complain they messed up your stuff. Probably some novice technicians who made a mistake would be my guess.
TheMalachite said:
This is completely unrelated to TWRP itself. OxygenOS for Nord 2 use ColorOS base which is know to give such issues (Also happen with OPPO and Realme devices on ColorOS and RealmeUI)
Click to expand...
Click to collapse
Ah, that's good to know. So it seems everything is the fault of ColorOS.
Camera works, fingerprint doesn't...