i rooted my phone succesfully and tried to edit my build prop but the phone automatically reboots and everything is reverted
Can someone help me?
A750FN(a7 2018) rooted with magisk
Thx for any replies and help.
Related
I tried to use the easy root to root my thunderbolt. For some reason it hasnt worked. Now i cant reset my phone to the factory set up. Its like i have a partial root.
It shows i have baseband verison- 1.16.00.0223r
kernel version-
2.6.32.21-gb05544a
sat feb 19 01:07:14 CST 2011
I just want the factory firmware back
please help
thank you
I attempted to root my US version G930U (Marshmallow 6.0.1 build number MMB29M.G9300UEU4APL2 with Android security patch level Dec 1, 2016) following the instructions in this link: https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I never got to the install SuperSu. The phone seems to boot normally but then restarts itself after about 30 secs. I've tried putting it in Airplane mode, turning WiFi off, removing sim card, reflashing the boot image nothing seems to help. Any ideas or guidance would be greatly appreciated! Thank you.
breezers said:
I attempted to root my US version G930U (Marshmallow 6.0.1 build number MMB29M.G9300UEU4APL2 with Android security patch level Dec 1, 2016) following the instructions in this link: https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I never got to the install SuperSu. The phone seems to boot normally but then restarts itself after about 30 secs. I've tried putting it in Airplane mode, turning WiFi off, removing sim card, reflashing the boot image nothing seems to help. Any ideas or guidance would be greatly appreciated! Thank you.
Click to expand...
Click to collapse
hi mate
You may have better luck if you ask in the right forum
https://forum.xda-developers.com/verizon-galaxy-s7
or in the thread you followed to root the phone
This section is for the international version (exynos)
I am trying to root my Samsung Galaxy J1 Mini and am not having any luck, here are some details from the About Device in settings:
Details: Samsung Galaxy J1 Mini SM-J105Y
Model : SM-J105Y
Android v : 5.1.1
Baseband v: J105YDVU0AQI1
Kernel v : 3.10.65-12258773
[email protected] #2
Thu Nov 28 13:40:24 KST 2017
Build number : LMY47V.J105YDVS0AQK1
SE For Android Status: Enforcing
SEPF_SM-J105Y_5.1.1_0073
Tue Nov 28 13:49:58 2017
Security Software Version: ASKS v1.2 Release 161011
Android Secutiry patch level: 1 November 2017
I have OEM Unlock and USB debugging enabled in developer options
I tried rooting using Kingoroot on PC and Kingroot on the phone itself, both say my phone is unsupported
I have tried to root this phone using cf-root images gathered from firmware.mobi (link https://desktop.firmware.mobi/device:483/firmware:14717 ), this comes up with the error RECOVERY IS NOT SEANDROID ENFORCING before rebooting normally
I have also tried using TWRP, but all the tutorials show pressing vol+ & menu & power to access, but this does not work with my phone either (it takes ages even to power on then just sits at the RECOVERY IS NOT SEANDROID ENFORCING until I remove the battery & reboot)
Is there any way to root this model of J1 mini? I am at the end of my tether here
Sparky Kestrel said:
Details: Samsung Galaxy J1 Mini SM-J105Y
Model : SM-J105Y
Android v : 5.1.1
Baseband v: J105YDVU0AQI1
Kernel v : 3.10.65-12258773
[email protected]4714 #2
Tue Mar 13 11:40:40 KST 2018
Build number : LMY47V.J105YDVS0ARC1
SE For Android Status: Enforcing
SEPF_SM-J105Y_5.1.1_0073
Tue Mar 13 11:50:08 2018
Security Software Version: ASKS v1.2 Release 161011
SMR Mar-2018 Release 1
Android Secutiry patch level: 1 March 2018
Click to expand...
Click to collapse
I remember having trouble finding out how to root my J1 Mini.
My device info differs slightly from yours (marked in red in the quote) so I can't guarantee we have the exact same phone. I suspect it's because I have a later firmware version than you (and my phone is rooted!).
Search for SM-J105: ROOT + TWRP Fácil! and you will find the video that got me rooted (sorry I can't post links).
When I initially rooted, the video description contained direct links to the needed files. The current video description links to a site where you can scroll down to "ROOT SM-J105Y" and download the files; I assume they are the same as the files I used.
I can't guarantee this will work so make sure you have a way to restore your phone in case anything goes wrong.
It might be worth looking up Magisk as this seems to be the new way to root phones however I haven't tried it.
Thanks for the info, but searching for that just showed a load of Youtube videos, most of which just show the exact same methods that don't work for me, so unless you can post a direct link then I don't even know what I should be looking for really.
And I looked up info on Magisk, but that requires TWRP to be installed, which as I noted above I just can not get to work no matter what.
I must have the only Samsung phone in the known multiverse that can't be rooted.
Enter firmware.mobi (desktop.firmware.mobi) and search for your sm-j105y. Chose the exact type of your phone's security patch, build date, etc. Configure CF-Auto-Root (better don't modify anything), generate the pack, wait for it to be ready, download start automatically, unpack it, read instructions very, very carefully and root your phone.
I did it successfully with my sm-j106h.
Video:
www . youtube . com/watch?v=I31ZMO35Eoo
Files:
garagemandroid . blogspot . com/2016/12/sm-j105.html
(remove spaces from links)
I've checked the files and they are the same ones I used to root my own phone.
I have since tried out magisk and it works using TWRP from the files above.
Magisk also works and seems to be a better way of rooting but I haven't managed to get xposed working with it.
@shahinul: read my first post again, I already tried firmware.mobi, I even put a link to what I downloaded there. It doesn't work.
jatan666 said:
Video:
www . youtube . com/watch?v=I31ZMO35Eoo
Files:
garagemandroid . blogspot . com/2016/12/sm-j105.html
(remove spaces from links)
I've checked the files and they are the same ones I used to root my own phone.
I have since tried out magisk and it works using TWRP from the files above.
Magisk also works and seems to be a better way of rooting but I haven't managed
to get xposed working with it.
Click to expand...
Click to collapse
Thanks for the link jatan. After loading the video, I thought "hey this looks familiar" and sure enough, my comment was there about it not working.
Since my last post, the new firmware update (the one that you already had, with the same info you marked in red above) came up, but would not install (it came up something about not having the right recovery image or something, and to take it to a Samsung repair centre), after trying a number of different methods, I finally went into recovery and wiped the cache which did the trick and allowed the latest official firmware to install successfully, so now I am on the same firmware you documented in your first post.
So, since I am on the same firmware as you, I thought I'd try again, but now, even using the package you linked to, when trying to install the image file, this time it won't even install, instead coming up with
SECURE CHECK FAIL : (recovery)
even though I still have OEM UNLOCK and USB DEBUGGING enabled in developer options.
That's it, I completely give up now. I honestly must have the only Samsung phone that is simply incapable of being rooted by every method known to man.
I think if I wanted to continue, it would be quicker and easier for me to do what a friend suggested and go to a pawn shop and pick up a second hand S4 or something.
omg so actually impossible to root j1105y and 106h; i find since few day and nothing twrp work and no roms custom available too
Hello,
I'm hoping someone can help me with the following issue. For a long time I used a custom ROM(NNE 3.1) and was able to call out and to be called. Until recently the Phone App just started to crash on any number I wanted to dial to. Since I haven't reset the phone for a long time, I chose to try out some newer ROMs, assuming the calling out/in problem would be solved.
However, whatever custom ROM I'm trying, calling doesn't work anymore. After re-flashing the stock firmware(Stock Samsung Android 7 - G920FXXU5EQI6_G920FPHN5EQI2_PHN) with Odin, I was able to call and to be called again.
After which I thought/hoped, maybe the stock ROM would have fixed the Phone App issue, so I tried various custom ROMs installed with TWRP, but with none of them the Phone App works. Not even with the exact same ROM I've been using for a long time. (I backed-up that ROM back then, and re-flashed the exact same file this time [NNe 3.1]).
What am I missing here? Some Samsung hardware security feature that got flipped back somehow?
Help is much appreciated...the stock firmware is so slow...
Thanks in advance!
Device: SM-920F
ROM Name: Stock
Android version: 7.0
Baseband version: G920FXXU5EQI4
Kernel version: 3.10.61-10958180 - [email protected] #1 - Sep 18 2017
Build number: NRD90M.G920FXXU5EQI6
Status SE for Android: Enforcing, SEPF_SECMOBILE_7.0_0005 - Sep 18 2017
Knox: 2.7.1
Security patch level: August 1st, 2017
Hello Guys,
I Just wanted to know how I root my pixel 3 with android 12 just guide mn or is there already a thread than give me a link but plz for android 12
Rooting Android 12 works exactly the same as Android 11 on the Pixel 3.
Since there were no obvious guides, I just wrote one for the Pixel 3. Here you go.
Thanks for help
Can u tell me is there any twrp for android 12
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Hmm so how we install custom roms
rocketrazr1999 said:
Not that I know of, at least it doesn't work on my rooted P3 running Android 11
Click to expand...
Click to collapse
Update... Android 12 can be rooted using Magisk Canary
I was able to take an OTA update to Android 12 on my BL unlocked, rooted, custom kerneled Pixel 3! I started the update accidentally by hitting that pop up reminder and after a minute of thinking what to do (i did not want to lose my data!!!), I held down the power button to force it to reboot during the update. I have had this work to stop an OTA update and restore it perfectly to previous state. Anyway, it did NOT work this time, and it updated to A12 perfectly! No loss of data, no loss of custom kernel, but i did of course lose root. Also.... when i checked the update version in settings, it wanted to update AGAIN, from Oct 21 to Feb 22 (which is just an Emergency Dialer patch). My phone still shows Oct 21 security patch in settings, but shows the Feb 22 firmware (...016.C1), which suggests the patch was only a tiny fix to the 911 Dialer and did not affect anything else. So this time i let it update, which i started to think was stuck or looping after waiting about an hour, but finally i checked the progress and it was done, requesting a reboot! So i rebooted it and behold, its now running final security update to the Pixel 3, and all i need to do now is root with Magisk and install SafetyNet Fix. Which is the ONLY thing i can think of as to how it was able to do a factory OTA update while rooted and BL unlocked! The SafetyNet Fix patch may be so good that it bypasses the Google security measure that refuses to allow OTA updates on rooted, unlocked Pixel 3s. Yup, on a GOOGLE PIXEL! I used to have to unroot and install the factory kernel to do an OTA sideload on my old Essential in order to update and not lose data, but i was told that you could not update to new Android versions without losing your data on the P3, so Ii just figured my Sept 21 A11 firmware was the final update until a phone upgrade. Anyway, just wanted to pass on the good news that you CAN perform a factory OTA update from A11 to A12 on the Pixel 3 WHILE rooted and unlocked and with a custom kernel, but I of course have to recommend you do so on your own, and if anyone has an unused or non-daily driver P3 that want to confirm this good news, please do so and help convince the disbelievers ! The ONLY thing i would recommend is that you have the latest "Android 12" version of SafetyNet Fix installed with the switches on in Magisk, which is what i had. Its the only thing i can think of that would allow Google's Safety Net to bypass the security restrictions. OK then, hope a few of you give it a try to show im not a nutcase, lol.
Question kind of related to this... Was the P3 kernel updated in Android 12 to fix that race condition that causes freezes if using systemless hosts? With A11 I always had to make sure I installed a custom kernel before Magisk and enabling systemless hosts to keep my P3 from freezing.