Phone: Samsung Galaxy j2 Pro 2018 SM-J250G (j2y18ltextc)
This is the second time I tried flashing, so I know a few things.
I successfully flashed the official twrp version for the phone using odin, but when I boot to recovery, it says: Recovery is not seandroid enforcing and Set warranty bit: recovery. Then after I swipe to allow modifications I can't flash anything because entering /storage and /sdcard doesn't show up anything and when i try to access it via terminal its "access denied". Also note that it gets stuck in bootloop. I've done this for all the twrp versions supposedly for my device but still the same results, please help.
Related
I found a solution to fix "RECOVERY IS NOT SEANDROID ENFORCING" error and hanged on boot logo and having root.
I tried to root my s6 edge with chainfire auto root and that was a mistake because my device hanged on boot logo with a message saying "RECOVERY IS NOT SEANDROID ENFORCING". i have searched for 4 hours here and in other forums with no luck, all of them said i have to re-flash the stock firmware again. so here is what you have to do
download these files
1. Kernel https://mega .co.nz/#!Nc9AjRwI!EB5-e_qpV41yGr-ADd1V6Sr8E0HFiLF8h7tOTApvby Y ( remove the space )
2. TWRP 2.8.7.1 https://dl.twrp.me/zeroltetmo/twrp-2.8.7.1-zeroltetmo.img.tar
3. Odin 3.10.7 http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361
4. SuperSU https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
flash the kernel first.
then flash the recovery twrp
boot into twrp and push the superSU zip file to your internal memory using adb command.
install the superSU file and reboot then bingo.
if you still have the message on booting, you have to freeze the security logagent
Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.
I found an old phone that seems to be stuck on the Samsung boot logo, so i tried to install the original ROM (S4 Mini) but i coudn't because when i flashed it with ODIN, obviously the phone restarted. but it booted on TWRP, and no matter what option i choose it gave me the ''unable to mount storage'' error as final result, showing me that i had 0 mb on internal storage and such. I tried everything i could but nothing seems to work, tried to flash other recovery by ODIN but when i restart the phone TWRP keeps appearing, it's like a nightmare!!
Device: S4 Mini GT-I9190
TWRP Version: 3.2.3-0
I have the same issue. does your sd card work?
Hello There,
I have Redmi Note 5 Pro with unlocked bootloader. But unable to root it no matter what.
Let Me Explain The Situation.
1. After flashing TWRP, it asks for "decryption password" which is nowhere to be found on internet. But in order to decrypt it i had to format the phone. GOOD Now Storage is Detected in TWRP.
2. But if i boot phone in System and again boot it in Recovery then TWRP is replaced with Stock Recovery.
1 & 2 are in INFINITE LOOP now.
3. So OTG...... OTG is not even recognizing by TWRP, but OS is detecting it.
4. TWRP "Enable MTP" also not working.
So Let Me Know If I am Forgetting Something.
Please Help Me To Root IT.
PS : I have past experience of Rooting/ Flashing rom / Unlocking Bootloader etc.
I guess the main problem you're having is that your phone keeps replacing TWRP with the stock recovery once you boot into system. I've had same problem on different devices. To prevent this from happening you should not boot into system immediately after flashing twrp, rather you should boot directly into twrp recovery (try "fastboot boot recovery.img" command after flashing twrp - I'm assuming that your twrp img is saved as "recovery.img") and flash Magisk before booting into system. By flashing Magisk before booting into system your phone would no longer replace twrp, and then your phone would be rooted as well. At least that worked for me.
And also use orangefox rather than twrp on this phone
Hi!
So it appears I have soft-bricked my phone. At least I hope this is a soft one, but looks harder and harder with every minute.
What I did:
- I have an A5 2017 initially running Android 8.0.0 build A520FXXUGCTKA.
My plan was to install Lineage for MicroG on it. I followed the instructions on the Lineage website, encountered immediately an absence of OEM unlock button, solved it with flashing latest stock ROM with CSE which also reset the device and doing the date/time trick (+- 8 days), after which OEM unlock appeared and I had both it and USB debugging on.
So I proceeded to install TWRP and was able to successfully boot into it, after which I followed the next fatal steps:
Now tap Wipe. <<did this
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage. <<did this, and it suddenly gave me a bunch of errors about being "unable to mount /data"
I disliked this and decided that I have to solve this before proceeding to step 3 of the guide. So I found somewhere a solution to go to Advanced Wipe, select the Data partition and repair it, which I did, but after this step I think it recommended to reboot the phone, which I unfortunately did... and I was stuck in Samsung boot with only the logo loading. I panicked and immediately tried to go back to recovery, which stopped the loop and game me the red message Only officially released binaries are allowed to be flashed.
So the status of the phone right now is:
- I cannot go into recovery mode anymore. It gives the red message about official binaries.
- Phone doesn't load into system either. It again gives the red message.
- I can go into Download mode and see the following status:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-A520F
CURRENT BINARY: CUSTOM
( I did not actually go to step 3 of the guide and try to upload the custom ROM. But I suspect this is because it now sees the ROM as changed/damaged)
SYSTEM STATUS: Official
RMM STATE: Prenormal
(This line was absent when I managed to turn on the OEM unlock finally. Now it's back)
FRP LOCK: OFF
Secure Download: Enabled
- I cannot upload ROMs via Odin anymore. The device isn't seen by it with Download mode like before. The drivers were installed by me previously and I was able to upload via Odin. I tried to reinstall them with zadig, but instead of 2 entried named Gadget Serial like before, zadig now only sees one Gadget serial and one Unknown device #1.
I tried to flash ROM in parts to the partitions directly (binaries, img) via Heimdall (using phone.pit mapping I downloaded a bit earlier via Heimdall). Heimdall said that it was a success on each download part, but also wrote 0% near the progress and it seems that it did nothing.
To me, phone looks now as if it sees its ROM as damaged, but ignores any attempts to get anything on it anymore. Which is logical because it seems to have either locked itself in a new state or restored to the state where the USB debugging and OEM unlock are not turned on. And I can't obviously get the system to load to turn them on.
Maybe somebody encountered a similar situation and knows how to get it out of this state or what this might be?