Hey guys,
I've recently decided to try and root my device again (I had rooted Marshmallow previously, but went back to stock). Problem is: it won't work.
Here's what I tried so far:
1) Chainfire Autoroot (latest version for Nougat): device won't boot. It's stuck at the Samsung logo fading in and out. I let it sit for about 20 minutes, without any changes.
2) TWRP with Magisk v12 and samsung-antiroot-removal 2.4: it performs the process but says it couldn't mount /data. After reboot -> the same Samsung logo issue as with 1.
3) TWRP with no-verity-opt-encrypt 5.1 and SR3-SuperSU v2.79. Very same as with 2. I should note that I didn't wipe my device though.
Does anybody have an idea what's actually going on there? I would really like to root my device again. Preferrably without losing any data on it.
Cheers and thanks in advance,
Mark
Unfortunately the problem is without wiping data, the rooting process does not properly.
Rooting has to modify some files both in the boot loader and kernel. Some of your apps also have modified the boot loader for the apps to start properly.
when you try to root it causes a conflict with the existing modifications caused by the apps leading to a boot loop.
That is why it recommended you sync your phone prior to rooting, wipe data so that you have a clean boot image, root and then restore your app back up.
magisk v 13 has automated the rooting process during installation, it seems to work I done it several times already after updating my rom but I also clear data first.
Cosmic Blue said:
Unfortunately the problem is without wiping data, the rooting process does not properly.
Rooting has to modify some files both in the boot loader and kernel. Some of your apps also have modified the boot loader for the apps to start properly.
when you try to root it causes a conflict with the existing modifications caused by the apps leading to a boot loop.
That is why it recommended you sync your phone prior to rooting, wipe data so that you have a clean boot image, root and then restore your app back up.
magisk v 13 has automated the rooting process during installation, it seems to work I done it several times already after updating my rom but I also clear data first.
Click to expand...
Click to collapse
Thank you. So it seems I will have to bite the bullet, wipe all data and start from scratch (more or less). Unfortunately every good backup solution requires root access. :/ But as far as I remember the Google Drive backup should work pretty well in regards to apps and their respective settings. *fingers crossed*
Related
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Hey all,
Was attempting to get to systemless root for Android Pay after being on a standard system-modified root. Followed the guide linked below:
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105
All went well until I attempted to install a Layers theme and got a SystemUI crash. No worries, restored from TWRP backup made just before Layers. Still bootlooped. Attempted to restore my Nandroid backup, still no dice. Any idea what might be wrong? Thanks for any help.
ever get it fixed? and how I am assuming you resolved?
I fixed being stuck in boot after a restore by only flashing system, data, boot, and vendor in TWRP.
proper vendor image?
From what I have read lately, Systemless root doesn't work with Android Pay any more. Google has patched it a month ago.
Read: http://www.xda-developers.com/android-pay-no-longer-working-with-systemless-root/
About TWRP restore. The function has evolved to be a little complex than earlier, and many users, especially those who are new, seem to have problems with it. You should most probably backup the old entries, like System, Data, Cache, and Boot. Vendor could be left alone if you're not downgrading or upgrading. Same goes for the recovery, since TWRP will be there already.
You should of did a total wipe, factory reset plus system. Then tried restore. You might of also needed to delete overlays folder.
The topic should be SM-A300H can't encrypt. The other issue I solved.
So this is my issue: Encryption doesn't install correctly. I am using lollipop.
After choosing encrypt my device in settings/security it reboots, and shows the green android symbol, but nothing more happens. It shows the green android character for about 15 seconds, and then it boots as usual without encrypting the system.
I did a wipe with TWRP 3.0.2-1-ashyx because of the encryption problem, I wanted to try out with a fresh install and see if it was possible to encrypt the system but it did not make a difference.
I had rooted the device with Kingroot before the wipe, and kingroot was still installed even after doing the wipe which is odd. I tried uninstalling kingroot after the wipe as well but encrypt still didn't work, same problem.
So if there's a solution to this problem I would be grateful if you can help me.
Additional question: in case I cannot get encryption to work for some yet unknown reason, is there any 3rd party app I can try that will encrypt the entire system? I am not looking to encrypt single files, only full system encryption is good enough.
*deleted*
Flash the stock firmware then boot to recovery and factory reset.
You should then be able to encrypt.
Be forewarned that if you do encrypt you will no longer be able to mount data or storage in twrp.
OK, I played with Titanium Backup and removed some Samsung apps like S health... Now I am stuck at boot loop and phone wont start. I am on stock rom 6.01 rooted. tried everything I could read:
- installed TWRP - did not quite work, gave me an error "is not seadroid"
- installed CWM - I can boot into it, but not much I can do to fix the boot, I tried wiping the partition cache and dalvik, but not help
- installed root again with stock recovery, nothing..
If I install the latest version of stock firmware, will I loose my app data? All I care about is to preserve my notes from ColorNote I read somewher that if a rom does not have userdata img, it wont wipe. Does the stock firmware have that? I am just looking for a way to get back in, backup stuff, and then reflash properly.
I tried going the adb route, but nothing there either. In cmd it says now unlock your phone for the pull command to compete, which obviously I cannot do.
Any other options to save my ColorNotes and Pictures?
OK, I was able to execute:
adb pull / C:\Myfile
This copied system files pretty much. How do I copy the app data or personal data - that's what I actually need
Got lucky...
I had to flash the latest stock firmware, but because I was running it anyway, just not the latest security patch, I the system ended up upgrading and all my files were preserved. It is as if I simply got the monthly patch.
im having big problems about vendor. for start im giving some info:
device: mi a1 (tissot)
current os: lineage OS 17.1
root: yes
twrp: can install or use just booting .img
i unlocked my device and installed twrp. there is no problem.
i wanted flash lineage OS and i wiped my device. gives error about cannot mount /vendor
i installed treble supported twrp and installed lineage OS. flashed magisk. installed microg...
then i tried flash mapsv1.zip which is recommended for microg. then booom. another /vendor error.
now i can boot device. i can use everything except gps. google maps app cannot found location. yandex maps can found and i can use it until lock screen or going main screen (or another app). then it starts stopping everytime until i clen its data and cache. then again... in chrome when i open google maps and try found my location chrome stops.
i tried to change /vendor/etc/gps.conf. its still same.
what to do now guys? im worrying about if i try re-flash rom it doesnt flash and device bricked. any solution without re-flash rom? what causes to cannot mount /vendor after solved it?
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
KaaMyA said:
What exactly did you wipe? I think you wiped vendor, or bumped your O.S. from an old firmware. However, wiping system, data and Dalvik was more than enough.
To solve this, the worst thing to do is trying to hook around. Just reflash the latest original firmware and start again.
Keep in mind that you might need to backup your stuff first.
Use adb pull and push commands in case your device is rebooting too much. Check if device works well this time.
Next, open adb access from device and reboot fastboot to reflash your custom recovery, then reboot recovery and wipe just these items. Finally, complete Rom flashing procedure, depending of your needs.
Click to expand...
Click to collapse
Dalvik cache , system, data, and cache. My device is not rebooting too much. Sory if i couldn't explain. Everything working fine except when an app tries use my location, app stops running, i cant flash anything right now.
İ thought anyone knows mapsv1.zip file(microg.org) and which files are replaced or added by this file when flash it. And can i do it manually? Btw i can read and write /vendor file with solid explorer
İf needed to re-flash rom thats ok but i think lineage OS was perfect for me until this error. And a last thing: can i backup my settings. (İ already took backup of everything in stock when unlocked bl)
Thank you for help
Edit: gps problems started when i tried flash mapsv1
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
KaaMyA said:
ROM could be perfect, but what I doubt is how perfectly you followed the procedure. Again, better start from zero, being sure you have all the prerequisites (latest firmware included). My humble opinion.
Click to expand...
Click to collapse
Okey ilk try it and share the result night. But is it possible to backup settings of phone?
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
KaaMyA said:
Well, that's why in step 0 is always recommended to backup you phone. At this level you should have nothing in settings, since you wipe it all... However, that's better, that's the goal of a Clean Install after all. Each ROM has its own flavour and is not recomendable to overwrite these values from a backup, if you're changing ROMs. What you could do, was to backup your apps and some settings with a third app like Swift Backup, or older Titanium Backup, before starting it all, or else, making a complete backup from recovery, in case you end with a problem with newly installed ROM (recommendation here is disable any screen security lock before doing Backups).
Click to expand...
Click to collapse
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Nurullah44 said:
İ did it all. Step by step. But i realized something. That errors doesnt matter on my device. Bcs when i flashing stock mi flash tool said failed but i booted system and everything working fine. İ installed persistent twrp. Same error. Then wiped. Same error but wipe completed. Than i flashed this zips single and booted everytime: lineage os, magisk, backup of migrate. Everytime it said cannot mount vendor but all of this apps and os and recovery working fine
Thank you for your helps
[Helping alone ]
Click to expand...
Click to collapse
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
portox said:
if you didn't treblized your device then its not a problem. I have this error too but that's because there is no vendor partition to mount. as been said by unipo:
https://forum.xda-developers.com/mi...-3-3-1-0-tissot-manager-t3976117/post81326153
Click to expand...
Click to collapse
Are you sure? Bcs i can view and change /vendor in root path. Treblizing is updating and repairing system partitions right? İ am using treble support twrp, flashed stock rom via mi flash(said error but worked fine) then how to treblize a device? And is this required for anything(like a rom, an app)?