Related
This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar
*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...
i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance
seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch
manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.
GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)
So I'm guessing no one knows the answer to my problem considering almost a moth has passed...
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too
Hi.
I have this phone since two years, and when I started modding I noticed a bunch of bugs that only I have.
For example, TWRP V3,-3.1.1 doesnt't work for me. I can flash it, but when the "swipe to allow modifications" screen displays, if I touch anywhere it reboots in system mode.
I asked before and nobody seems to have my same errors.
The only version that works for me is 3.1.0, but I have a bug whit ROMs.
It flashes ROMs correctly, but when the ROM boots, my phone just turn off and the red/green led of death starts blinking, luckly I managed to recover my phone from that.
My phone is an ALE-L21, i didn't install anything incompatible, so I don't know what I am doing wrong.
Sorry for my bad english
Lemon476 said:
Hi.
I have this phone since two years, and when I started modding I noticed a bunch of bugs that only I have.
For example, TWRP V3,-3.1.1 doesnt't work for me. I can flash it, but when the "swipe to allow modifications" screen displays, if I touch anywhere it reboots in system mode.
I asked before and nobody seems to have my same errors.
The only version that works for me is 3.1.0, but I have a bug whit ROMs.
It flashes ROMs correctly, but when the ROM boots, my phone just turn off and the red/green led of death starts blinking, luckly I managed to recover my phone from that.
My phone is an ALE-L21, i didn't install anything incompatible, so I don't know what I am doing wrong.
Sorry for my bad english
Click to expand...
Click to collapse
You need to flash required version of emui to install a particular rom. Maybe this is happening because you didn't meet the requirements. For example to flash RR you need to flash B895 before. Then the rom will have no bugs.
Suleiman01 said:
You need to flash required version of emui to install a particular rom. Maybe this is happening because you didn't meet the requirements. For example to flash RR you need to flash B895 before. Then the rom will have no bugs.
Click to expand...
Click to collapse
I did, I still have that problem
Lemon476 said:
I did, I still have that problem
Click to expand...
Click to collapse
The emui rom you flashed worked fine?
Suleiman01 said:
The emui rom you flashed worked fine?
Click to expand...
Click to collapse
Yes it did.
I did everything I had to do, and not only once.
Lemon476 said:
Yes it did.
I did everything I had to do, and not only once.
Click to expand...
Click to collapse
So the emui rom b895 booted properly. But when you flash Resurrection Remix your phone got stuck at black screen.
Correct me If I am wrong.
.
Also after you flashed emui which twrp did you flash because when you flash emui it replaces twrp with huawei's recovery.
Suleiman01 said:
So the emui rom b895 booted properly. But when you flash Resurrection Remix your phone got stuck at black screen.
Correct me If I am wrong.
.
Also after you flashed emui which twrp did you flash because when you flash emui it replaces twrp with huawei's recovery.
Click to expand...
Click to collapse
I flashed with the only twrp that works for me, TWRP 3.1.0, emui booted properly. When I flashed Resurrection Remix, all went good, but when boot animation end my phone just turn off and a red and green led starts blinking
Anyone has my same problem with twrp?
It is very rare but it happens ...
Unlock your the bootloader again! I think you have get some issue in that process.
Try to flash this TWRP: https://forum.xda-developers.com/p8lite/orig-development/twrp-t3609582
boot in bootloader [ with phone off press vol - and plug the usb ], wait a few secs
Copy the TWRP image in to ADB folder and open cmd in that folder, write this code :
Code:
fastboot flash recovery TWRP_3.1.1-0_ALICE.V4.img
Then unplug the usb and press vol+ and power untill reboot and screen turn ON then release the keys.
Tell me if TWRP is working fine...
.
Lemon476 said:
I flashed with the only twrp that works for me, TWRP 3.1.0, emui booted properly. When I flashed Resurrection Remix, all went good, but when boot animation end my phone just turn off and a red and green led starts blinking
Click to expand...
Click to collapse
You should try to flash twrp 3.1.1 after flashing emui (it might work on that version of emui) and then flash RR otherwise do what persona78 said.
persona78 said:
It is very rare but it happens ...
Unlock your the bootloader again! I think you have get some issue in that process.
Try to flash this TWRP: https://forum.xda-developers.com/p8lite/orig-development/twrp-t3609582
boot in bootloader [ with phone off press vol - and plug the usb ], wait a few secs
Copy the TWRP image in to ADB folder and open cmd in that folder, write this code :
Then unplug the usb and press vol+ and power untill reboot and screen turn ON then release the keys.
Tell me if TWRP is working fine...
.
Click to expand...
Click to collapse
I tried, phone still reboots in system..
Lemon476 said:
I tried, phone still reboots in system..
Click to expand...
Click to collapse
Show me a print screen when you flash TWRP...
.
So I flashed a custom rom and it required a specific TWRP recovery. But after installing the custom rom I had to install another TWRP recovery otherwise it wouldn't boot into OS (this recovery was probably unsupported and thus my phone was forced to boot into OS)
So every time I wanted to boot into recovery mode I had to use an app like flashify and flash the first recovery to boot into recovery mode. And after finishing I had to flash the "unsupported" recovery again in order to boot into OS.
Now with the "unsupported" recovery, I installed Xposed and some modules and then restarted the device. And..........boom! The phone is stuck in a boot loop! And I can't even boot into recovery mode.
Now here's the other nightmares I'm getting:
1. Cant use ADB to flash a new recovery because my device is "unauthorized" and in order to fix that I need to go to developers option which is not possible (because of boot loop)
2. Uninstall Xposed: button combinations aren't working and I cant go to recovery mode to flash the uninstaller zip
3. vol up + vol down + power button doesn't open recovery because the recovery is "unsupported"
4. Can't even boot to fastboot mode by holding vol down + power. It tries to boot into OS and starts boot looping
5. Can't use sp flash tool to flash stock rom or recovery because whenever I connect the phone to PC, the phone tries to boot into OS and....you guessed it starts boot looping.
Now I'm out of ideas and really depressed. If anyone can help me out with this I'll be grateful forever.
My device is: Lenovo k4 note
Chipset: MediaTek MT6753
Currently on this recovery: https://androidfilehost.com/?fid=673368273298981920
Got this recovery from here (recovery2): https://forum.xda-developers.com/k4-note/development/unofficial-resurrection-remix-5-8-2-t3570195
Thanks!
Update: The problem is solved after flashing stock rom via sp flash tool
Can you please help me im havifng the same problem
scarecow47 said:
Update: The problem is solved after flashing stock rom via sp flash tool
Click to expand...
Click to collapse
I think the pc cant dtect my device same problem bro after installing new rom it keeps on rebooting after the lenovo logo. Cant also access the recovery mode. Please help me
Bro I'm not an expert. Someone from XDA discord server helped me with this. And I actually forgot the exact thing I did to be honest. I downloaded the sp flash tool on pc and downloaded the stock rom. Then flashed it to the phone. You have to connect your device via USB before. For a detailed guide you can search on YouTube with something like "how to flash stock rom via sp flash tool"
Or ask in the discord server. They will surely help you.
How did you flash that? Can you please explain step by step
Check this link: https://firmwarefile.com/lenovo-k4-note-a7010a48
You can download the stock rom from here. And there is also a tutorial on how to flash it. I followed it. Hope that helps!
scarecow47 said:
Check this link: https://firmwarefile.com/lenovo-k4-note-a7010a48
You can download the stock rom from here. And there is also a tutorial on how to flash it. I followed it. Hope that helps!
Click to expand...
Click to collapse
Thanks, the problem is my phone is struck on the Lenovo logo, it's not turning off but my computer deducted it as Lenovo device
If ADB can detect your device then you can just flash a new recovery and you should be fine. But as I said I'm not an expert so I'd suggest you to ask for help on the XDA discord server. That's where I got help from.
Did anyone found the solution?
Thanks
Can any one find the solution of that problem , because my lenovo k4 note also stuck on boot looping logo... and vibrate like bootup time
hi guys i tried to flash my C9000 but now my phone is in bootloop and i can't enter recovery it says
recovery booting
recovery is not seandroid enforcing
set warranty bit recovery what to do plz help
i tried skyneel .com guide
i flashed twrp on my phone
Hi bro. İ have same problem 8 months ago and i know this fix.
First. Sorry for my bad english.
You must wait the battery fully discharge. Because you cant make anything now.
When fully discharged phone. You plug charge and press wolume down+power+home. You can go to download mode this way. You must flash the original firmware via odin.
And if you want flash twrp again this step is required.
Go Settings page in odin and untick the auto reboot.
And manually go to recovery mode by download menu after install.
ahmetk711 said:
Hi bro. İ have same problem 8 months ago and i know this fix.
First. Sorry for my bad english.
You must wait the battery fully discharge. Because you cant make anything now.
When fully discharged phone. You plug charge and press wolume down+power+home. You can go to download mode this way. You must flash the original firmware via odin.
And if you want flash twrp again this step is required.
Go Settings page in odin and untick the auto reboot.
And manually go to recovery mode by download menu after install.
Click to expand...
Click to collapse
So should i flash twrp directly or do i have to first flash the original firmware then flash twrp and also can you post original firmware download link because all the links are paid like sammobile etc
hatib237 said:
So should i flash twrp directly or do i have to first flash the original firmware then flash twrp and also can you post original firmware download link because all the links are paid like sammobile etc
Click to expand...
Click to collapse
Flash twrp directly and go to recovery after installation. Dont make any reboots before going to twrp.
ahmetk711 said:
Flash twrp directly and go to recovery after installation. Dont make any reboots before going to twrp.
Click to expand...
Click to collapse
So after flashing i should go in recovery and do what
hatib237 said:
So after flashing i should go in recovery and do what
Click to expand...
Click to collapse
Dont do anything bro. But you must go to recovery after flashed the twrp. İf you dont go to recovery it seems to bootloop one more time. Ok.
ahmetk711 said:
Dont do anything bro. But you must go to recovery after flashed the twrp. İf you dont go to recovery it seems to bootloop one more time. Ok.
Click to expand...
Click to collapse
Ok i and to access recovery the button is volume up + home +power right
ahmetk711 said:
Dont do anything bro. But you must go to recovery after flashed the twrp. İf you dont go to recovery it seems to bootloop one more time. Ok.
Click to expand...
Click to collapse
I was trying to access to recovery but couldn't i tried holding buttons but didn't work
hatib237 said:
hi guys i tried to flash my C9000 but now my phone is in bootloop and i can't enter recovery it says
recovery booting
recovery is not seandroid enforcing
set warranty bit recovery what to do plz help
i tried skyneel .com guide
i flashed twrp on my phone
Click to expand...
Click to collapse
its for bad recovery file
you have to wait until your battery dead.
then connect to pc and turn on the phone and hold (Power + Home + vol Dwn )
flash TWRP 3.2.1 c9ltechn (only this version)
reboot
if not worked flash nougat 7.1 rom
g900h said:
its for bad recovery file
you have to wait until your battery dead.
then connect to pc and turn on the phone and hold (Power + Home + vol Dwn )
flash TWRP 3.2.1 c9ltechn (only this version)
reboot
if not worked flash nougat 7.1 rom
Click to expand...
Click to collapse
will the 3.2.1 work on 7.1.1 c9000 HK
hatib237 said:
I was trying to access to recovery but couldn't i tried holding buttons but didn't work
Click to expand...
Click to collapse
Ok, do the 3button combination as if you are booting into download mode. As soon as screen goes black, keep power and home key pressed down but move to volume up. You have to be quick before it boots to download. This will get you to recovery.
SM-N950U Chimera Rom 2.0
hatib237 said:
will the 3.2.1 work on 7.1.1 c9000 HK
Click to expand...
Click to collapse
Yes 100% Tested.
but Im not sure its work on oreo(8)
Without root
Twrp how i flash withoit root i want my device back help me i flash all time file combination file repiar firmaware but nothing work agian show recovery booting
Problem solved! i was installing the wrong version of twrp this is the correct version: https://eu.dl.twrp.me/j5xnlte/
I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Should I consider installing a different recovery? like maybe CWM?
It has a costume rom on i guess it says "Hebrew by daniel mouyal for bt" in the about tab in the settings...
I tried using ADB to install but when it's in download mod it can't find the phone so when i enter the install command:"fastboot flash recovery twrp-2.8.x.x-xxx.img" it says: "waiting for device"
Well I've been installing the wrong version of twrp lol sry!
So just in case someone else hits the same problem it's not the twrp i posted before but this one:
https://eu.dl.twrp.me/j5xnlte/
When recovery is finished flashing in Odin, remove your battery to turn the device off.
Then put the battery back in and press vol+ and power button and home button at the same time.
Your device should then boot into twrp.
If you reboot before doing this the android operating system will ovewrite twrp with stock recovery and you will have to start the process again
Also you used the wrong twrp. J53gxx is 2015 model j500h and j5xnlte is j510fn not j510h. You must be careful or else you may seriously damage your device.
Use this twrp here for your device j510h
garylawwd said:
When recovery is finished flashing in Odin, remove your battery to turn the device off.
Then put the battery back in and press vol+ and power button and home button at the same time.
Your device should then boot into twrp.
If you reboot before doing this the android operating system will ovewrite twrp with stock recovery and you will have to start the process again
Also you used the wrong twrp. J53gxx is 2015 model j500h and j5xnlte is j510fn not j510h. You must be careful or else you may seriously damage your device.
Use this twrp here for your device j510h
Click to expand...
Click to collapse
Thank you for the response!
I managed to figure out the issue it was the wrong twrp version.. I can't update the title though
That's no problem.
What I would suggest though is to post how you fixed your issue in case anyone has problems in the future they can be referred to your thread here
garylawwd said:
That's no problem.
What I would suggest though is to post how you fixed your issue in case anyone has problems in the future they can be referred to your thread here
Click to expand...
Click to collapse
I did in my second post I posted the correct link to the correct version of twrp
I'll edit it so it's more visible