Related
Hello everyone,
I tried rooting my Note 4 using Chainfire's [SM-N910*] CF-Auto-Root :
http://forum.xda-developers.com/not...-auto-root-t2897428/post55865442#post55865442
However after Odin finishes and shows "pass", the phone does not reboot in recovery mode nor shows the red android, it loops on the samsung logo and written in the top left corner of the screen 3 lines reading :
Recovery booting ...
Recovery is not seandroid enforcing
Set warranty bit : recovery
I used the correct file for my phone, and now i cannot enter recovery mode, only download mode is accessible.
Any advice is greatly appreciated.
Flash stock firmware with odin and try again
The message is normal it comes up when you root your phone. Do you have a custom recovery installed?
sawdoctor said:
The message is normal it comes up when you root your phone. Do you have a custom recovery installed?F
Click to expand...
Click to collapse
I didnt have custom recovery and it happened, i fixed my boot loop and i still want to root it but each time i try it goes back to the boot loop. My note 4 is SM-N910F
Alex_popa said:
I didnt have custom recovery and it happened, i fixed my boot loop and i still want to root it but each time i try it goes back to the boot loop. My note 4 is SM-N910F
Click to expand...
Click to collapse
indentical same problem
SM-910F
4.4.4
N910FXXU1ANKA
help please
Probably should have mentioned my build number and what not too...
healthyboy said:
Hello everyone,
I tried rooting my Note 4 using Chainfire's [SM-N910*] CF-Auto-Root :
http://forum.xda-developers.com/not...-auto-root-t2897428/post55865442#post55865442
However after Odin finishes and shows "pass", the phone does not reboot in recovery mode nor shows the red android, it loops on the samsung logo and written in the top left corner of the screen 3 lines reading :
Recovery booting ...
Recovery is not seandroid enforcing
Set warranty bit : recovery
I used the correct file for my phone, and now i cannot enter recovery mode, only download mode is accessible.
Any advice is greatly appreciated.
Click to expand...
Click to collapse
nikboss77 said:
indentical same problem
SM-910F
4.4.4
N910FXXU1ANKA
help please
Click to expand...
Click to collapse
I had a same problem but I found easy solution. If you have a bootloop install latest CWM recovery, open ODIN (I used newest version) and uncheck Auto Reboot, select CWM in AP and flash it, after that phone will stay still in Download mode. Then unplug usb from PC and remove battery for 5-7sec, give it back and turn phone on - your phone will boot into CWM recovery for sure ...then I flashed latest TWRP
bondro said:
I had a same problem but I found easy solution. If you have a bootloop install latest CWM recovery, open ODIN (I used newest version) and uncheck Auto Reboot, select CWM in AP and flash it, after that phone will stay still in Download mode. Then unplug usb from PC and remove battery for 5-7sec, give it back and turn phone on - your phone will boot into CWM recovery for sure ...then I flashed latest TWRP
Click to expand...
Click to collapse
Thanks I wanted to ask you once I am in recovery with cwm as I install TWRP? Also from odin?
And how to proceed with CF-Auto-Root?
Sorry for my ignorance....
nikboss77 said:
Thanks I wanted to ask you once I am in recovery with cwm as I install TWRP? Also from odin?
And how to proceed with CF-Auto-Root?
Sorry for my ignorance....
Click to expand...
Click to collapse
Download corespond file from cf auto root page , put your phone into download mode ( VOL - home button and lock screen button ) then select in odin AP file : CF-Auto-Root-trlte-trltexx-smn910f.tar.md5 , start , and wait a few seconds to boot ! Cheers
ManDone.vRs said:
Download corespond file from cf auto root page , put your phone into download mode ( VOL - home button and lock screen button ) then select in odin AP file : CF-Auto-Root-trlte-trltexx-smn910f.tar.md5 , start , and wait a few seconds to boot ! Cheers
Click to expand...
Click to collapse
I know what to do, I have been doing this all along but it goes into a mad boot loop. The Red Android doesn't pop up on screen either. I thought for a second I bricked my phone when it happened but luckily I was able to restore it. Any other suggestions??
Alex_popa said:
I know what to do, I have been doing this all along but it goes into a mad boot loop. The Red Android doesn't pop up on screen either. I thought for a second I bricked my phone when it happened but luckily I was able to restore it. Any other suggestions??
Click to expand...
Click to collapse
It is in fact ... I did the root samsung in many of my friends ... always the same procedure with odin. But this does not load Note4 just the red robot and immediately goes into loop.I do not understand where it can be the error or incompatibility
Plz Help
Sorry for posting on this forum but i cant find any help on the N910H forum. Hi am having the exact same problem phone cant boot to download mode and not recovery. i tried to odin back to stock same problem, i tried twrp, philz and cwm recovery. it says pass in Odin but the phone wont reboot past the android logo and cant boot to recovery.Model number is SM-N910H
Had the same issue, fixed it however flashing CF auto root always results in a boot loop.
Is there any other way of rooting the note 4 without Odin?
At this point I realized that more than anyone has this problem of our loop in doing root on your Notes 4, now in addition to figure out if there is a solution to this problem, I would like to know if this problem is present on the Notes 4 with the same model, firmware updates etc. etc .... or this Note 4 that we are "bad"?
I successfully rooted my note 4 SM-N910F using this method.
Search zedomax note 4 root. It should be the first result.
Sorry I wasn't able to link the video I was not allowed to submit an external link until I have 10 posts.
My phone did this weird thing where it erased twrp so straight after passing in odin I took out the battery and entered twrp. From there it was easy. Hope this helps anyone else with this problem
Alex_popa said:
Is there any other way of rooting the note 4 without Odin?
Click to expand...
Click to collapse
You can flash a flashable SuperSU from chainfire's website using CWM or TWRP recovery.
But if you are on stock TW 5.1.1, you can't root it just yet, it will cause bootloop.
Flash stock 5.1.1 again to fix bootloop
i flashed again to the stock 5.1.1 and i still get stuck on Samsung Galaxy Logo i tried every thing wipe data and wipe cache and i remove battery for million time and i even rooted the phone and start but still freezing on galaxy logo and then Re download the latest Official Rom From sammobile and still Stuck on Galaxy logo the problem came to me when i install Twrp on my rooted note 4 and it's stucked on twrp so i downloaded the latest Rom and still get freeze on Galaxy Logo please help me :/
Same problem here. Flashed SM-N910F (International, Qualcomm): CF-Auto-Root-trlte-trltexx-smn910f.zip but stuck in bootloop, all i get is the threeuk logo and the music. Tried with auto reboot on and off but with no luck.
breeg said:
Same problem here. Flashed SM-N910F (International, Qualcomm): CF-Auto-Root-trlte-trltexx-smn910f.zip but stuck in bootloop, all i get is the threeuk logo and the music. Tried with auto reboot on and off but with no luck.
Click to expand...
Click to collapse
If you're on 5.1.1 then you need a root capable kernel to be flashed too...
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 was flashing twrp with flashify when I just rebooted in recovery and since that moment my phone is stuch on an infinite bootloop showing me the:
"Recovery booting (recovery is not seandroid enforcing...)"
I'm plugging off the battery for some hours, but when plugged in nothing changed.
My phone has the usb port broken, so I can use it only to charge the battery, but no pc will recognize it.
Since the fact that I can't access download mode, or recovery mode to restore a nandroid backup, It's insane to buy a usb port to change it on the phone and try to link to a pc?
I mean, is there a way to access download mode?
Does JIG usb work in this situation of hard brick?
Any advice?
Thanks for answering.
whychange said:
Hi,
I was flashing twrp with flashify when I just rebooted in recovery and since that moment my phone is stuch on an infinite bootloop showing me the:
"Recovery booting (recovery is not seandroid enforcing...)"
I'm plugging off the battery for some hours, but when plugged in nothing changed.
My phone has the usb port broken, so I can use it only to charge the battery, but no pc will recognize it.
Since the fact that I can't access download mode, or recovery mode to restore a nandroid backup, It's insane to buy a usb port to change it on the phone and try to link to a pc?
I mean, is there a way to access download mode?
Does JIG usb work in this situation of hard brick?
Any advice?
Thanks for answering.
Click to expand...
Click to collapse
You need a working usb to flash a custom recovery or an offical fw. I thought flashify needs root access to work?. Or if you already have root, you could adb to flash twrp but it's too late now.
Try getting into download mode. When it asks to proceed or cancel, choose cancel. Some people are lucky that the phone boot into system again but they need to fix the broken recovery later.
Sent from my SM-G925F
Rosli59564 said:
You need a working usb to flash a custom recovery or an offical fw. I thought flashify needs root access to work?. Or if you already have root, you could adb to flash twrp but it's too late now.
Try getting into download mode. When it asks to proceed or cancel, choose cancel. Some people are lucky that the phone boot into system again but they need to fix the broken recovery later.
Sent from my SM-G925F
Click to expand...
Click to collapse
After 2 months of battery out, finally I got download mode to work, and pressing cancel my phone started.
Thanks.
But now it seems that there is no custom recovery installed, so when i go in custom recovery, the loop starts again.
How may I install again a custom recovery, knowing that:
1) I can't connect to pc, cm 12.1 has a bug, no pc recognizes my phone;
2) rom manager doesn't install any custom recovery on my phone;
3) flashify made my phone in boot loop, and I can't understand what I was wrong 2 months ago.
Thank you, man.
See your other post man .
Flash the tar version of TWRP using Odin. If there is no tar version, you can use Cygwin to convert an img file to a tar file.
Hi All,
Got a S5 G900I here that's doing my head in! Stuck in the infamous bootloop at the Samsung logo.
I have been a long time reader of these forums and have prior experience from flashing Samsung phones but this one is driving me mad!
I can put the phone into Download mode without an issue, phone is detected in Odin and I can flash any firmware I try to it (Have tried original 4.4.2 , 5.0 and latest 6.0.1 firmwares from SamMobile). Odin goes through the entire process, reports as "Pass" but then the device goes straight back into the reboot loop and will never fully boot up.
I can also use Odin to push TWRP / CWM / PhilzTouch recoveries, however the device will never boot into the recovery partition. I get the blue "Recovery Booting" message briefly, then the device bootloops again.
Does anyone have any further suggestions to try and get this phone operational again?
I have tried multiple versions of Odin, multiple firmware versions, different computers, different USB cables, different USB ports etc.
I look forward to hearing back from you
Try this :
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
andra.soul.catcher said:
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
Click to expand...
Click to collapse
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
AS93 said:
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
Click to expand...
Click to collapse
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
andra.soul.catcher said:
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes when I am booting into recovery mode and can see the blue text "Recovery Booting" in the corner of the screen I let go of the power button - device still boot loops.
Have flashed recovery then removed battery - still cannot get it into recovery.
I have seen some Samsungs have hardware issues with their NAND chips but in these cases there are a lot of errors relating to NAND displayed on the screen when I've seen it be a hardware issue. None of these appear on this phone - convinced it has something to do with software.
I found these threads - exactly the same issue as me, and at the end it says they fixed it by flashing a specific bootloader however I have a G900I and the phone in this thread was a G900F
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926/
https://forum.xda-developers.com/galaxy-s5/help/samsung-s5-sm-g900f-stock-flash-caused-t3771105
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926
Have tried countless different versions of ODIN / recovery / stock firmware , including the "service firmware with the separate files G900IDVU1BOE1_CL4826466_QB4839040_REV00_user_low_ship_MULTI_CERT"
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